hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6 Solutions | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.0 Mapping Solutions to Key Issues | Table 6.0-1: Mapping Solutions to Key Issues
Key Issues
Solutions
KI#1
KI#2
KI#3
1
X
2
X
3
X
4
X
X
X |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1 Solution #1: SMS over IP (4G and 5G) | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.1 Introduction | This solution addresses Key Issue 2 on Priority support for SMS over IP based on MPS subscription, for mobile originated and mobile terminated Short Messages.
Figure 6.1.1-1: SMS over IP entities providing MPS priority for mobile originated short messages
Figure 6.1.1-2: SMS over IP entities providing MPS priority for ... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.2 Functional Description | Upon receiving a Short Message, the SMS-GMSC checks with the HSS/UDM/UDR whether the MPS for messaging indication is available is activated for the UE. If so, the SMS-GMSC sets the transport priority (e.g. DSCP and DRMP/Message Priority header) with a value appropriate for MPS and forwards the Short Message.
When the I... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.3 Procedures | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.3.1 General | This clause describes the following procedures:
- Procedures for Short Message handling, MO, in clause 6.1.3.2;
- Procedures for Short Message handling, MT, in clause 6.1.3.3. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.3.2 Procedures for Short Message handling, MO | The procedure is based upon the procedure in TS 23.204 [3], clause 6.7 as illustrated in Figure 6.1.3.2‑1 below.
Figure 6.1.3.2-1 (TS 23.204 [3] Figure 6.7:) Successful IM origination to SMS procedure
The following steps refer to steps in clause 6.7 of TS 23.204 [3] as a baseline, and are enhanced for MPS treatment for... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.3.3 Procedures for Short Message handling, MT | The procedure is based upon the procedure in TS 23.204 [3], clause 6.14 as illustrated in Figure 6.1.3.3‑1 below.
Figure 6.1.3.3-1 (TS 23.204 [3] Figure 6.14): SMS over IP mobile terminated
The following steps refer to steps in clause 6.7 of TS 23.204 [3] as a baseline, are enhanced for MPS treatment for SMS over IP.
3... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.1.4 Impacts on services, entities, and interfaces | This solution will impact the following entities:
- SMS-GMSC: retrieves the MPS for messaging information from the HSS, sets transport priority on the Short Message.
- IP-SM-GW: adds Resource-Priority information to the Instant Message, adds transport priority to the Short Message.
- P-CSCF: sets RPH if MPS for messagi... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2 Solution #2: MPS support for SMS over NAS | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.1 Introduction | NOTE: It is assumed that all NFs in a PLMN involved in the SMS over NAS delivery support MPS treatment when the feature is deployed.
This solution provides methods to support MPS treatment for SMS over NAS, for UEs with subscription data that indicates that SMS with MPS handling is included i.e. subscription data in th... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.2 Functional Description | The solution requires the UE to have an MPS subscription as specified in TS 23.501 [7].
- The UE subscription data in the UDM contains an additional parameter indicating MPS treatment for message as part of the MPS subscription. This parameter is provided to related NFs involved in SMS over NAS (i.e. AMF and SMSF). The... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.3 Procedures | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.3.1 Registration procedure for SMS over NAS | The procedure is based on clause 4.13.3.1 of TS 23.502 [8] as illustrated in Figure 6.2.3.1-1.
Figure 6.2.3.1-1: Registration procedure supporting SMS over NAS
The following steps, referring to steps in clause 4.13.3.1 of TS 23.502 [8] as baseline, are enhanced for the MPS treatment for SMS over NAS.
1. The MPS-subscri... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.3.2 MO SMS over NAS procedure | The procedure is based on clause 4.13.3.3 and 4.13.3.5 of TS 23.502 [8], as illustrated in Figure 6.2.3.2-1 below.
Figure 6.2.3.2-1: MO SMS over NAS
The following steps, referring to steps in clause 4.13.3.3 of TS 23.502 [8] as baseline, are enhanced for the MPS treatment for SMS over NAS.
1. The MPS-subscribed UE indi... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.3.3 MT SMS over NAS procedure | The procedure is based on clauses 4.13.3.6, 4.13.3.7 and 4.13.3.8 of TS 23.502 [8] as illustrated in Figure 6.2.3.3-1 below.
Figure 6.2.3.3-1: MT SMS over NAS
The following steps, referring to steps in clause 4.13.3.6 of TS 23.502 [8] as baseline, are enhanced for the MPS treatment for SMS over NAS.
'2. The SMS-GMSC in... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.2.4 Impacts on services, entities, and interfaces | UDM:
- Supports the MPS subscription data with additional indication MPS for message.
AMF:
- Supports receiving a new indication for MPS for messaging in the subscription data.
- Supports SMS related Message Priority header handling based on the MPS for message indication.
- Paging priority treatment for MPS for messag... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3 Solution #3: IMS Messaging | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.1 Introduction | This solution addresses Key Issue 1 on Priority support for IMS messaging based on MPS subscription.
The following are enabled by this solution when the MPS for messaging indication is activated:
- Instant Messages in the IMS will be handled at the application level with priority (using Resource-Priority information).
... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.2 Functional Description | Entities that handle the IMS message or session find out whether MPS for messaging has been activated or deactivated by checking the UE's MPS for messaging indication in/from the HSS or the UDR as described in the Overall activation-deactivation for MPS for messaging solution, clause 6.4.
When receiving an Instant Mess... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.3 Procedures | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.3.1 General | This clause describes procedures for:
- Immediate messaging, in clause 6.3.3.2;
- Immediate messaging with multiple targets, in clause 6.3.3.3;
- Session based messaging handling, in clause 6.3.3.4. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.3.2 Procedures for immediate messaging | The procedure is based upon the procedure in TS 23.228 [4], clause 5.16.1.1.1 as illustrated in Figure 6.3.3.3‑1 below.
Figure 6.3.3.3-1 (TS 23.228 [4] Figure 5.47): Immediate Messaging procedure to registered Public User Identity
The following steps refer to steps in clause 5.16.1.1.1 of TS 23.228 [4] as a baseline, a... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.3.3 Procedures for immediate messaging with multiple targets | The procedure for immediate messaging with multiple targets is the same as the procedure for immediate messaging except that a messaging application server duplicates the original MESSAGE and sends it out to multiple targets indicated in the MESSAGE.
Figure 6.3.3.4-1: Immediate Messaging with multiple targets procedure... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.3.4 Procedures for session messaging | NOTE: The procedure is based upon the procedure in clauses 5.7a.2 and 5.16.2.2.1 of TS 23.228 [4]. The details added below for MPS are highlighted.
The following procedure shows the establishment of a message session between two registered UEs where the UEs are able to exchange messages end-to-end.
Figure 6.3.3.5-1 (TS... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.3.4 Impacts on services, entities, and interfaces | This solution will impact the following entities:
- P-CSCF: for MO, sets Resource-Priority information when it receives SIP MESSAGEs and SIP INVITEs for UEs that have MPS for messaging enabled. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4 Solution #4: Overall activation and deactivation of MPS for messaging | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.1 Introduction | This solution addresses Key Issues 1, 2 and 3 and assumes a common activation/deactivation of MPS for messaging that applies to both IMS messaging and SMS (over NAS and over IP). |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.2 Functional Description | Activation/deactivation controls whether the user is given MPS priority for messaging. The MPS for messaging activation/deactivation status for a UE in the HSS/UDM/UDR controls whether entities that handle IMS messages or sessions for messaging and entities that control SMS (over NAS or over IP) need to enforce MPS for... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.3 Procedures | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.3.1 General | The EPC procedures are given below, with differences for 5GC noted in parenthesis.
Figure 6.4.3-1: Activation
To activate MPS for messaging for a UE:
1. The Application Function sends an activation request to the SCEF (the NEF in the 5GC) via T8 (via N33 in the 5GC).
2. The SCEF (the NEF in the 5GC) forwards the reques... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.3.2 Activation/Deactivation based on HSS-method - Alternative 1 | Continuing the procedure from clause 6.4.3.1, upon activation, after the HSS (UDM/UDR in 5GC) has authorized a Service User for MPS for messaging, the HSS informs the S-CSCF via Cx/N72 with the MPS for messaging indication. Subsequently, the S-CSCF informs the P-CSCF (e.g. using a regEvent).
Upon deactivation, the HSS ... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.3.3 Activation/Deactivation based on UDR method - Alternative 2 | Continuing the procedure from clause 6.4.3.1, upon activation, after the HSS (UDM/UDR in 5GC) has authorized a Service User for MPS for messaging, the SPR (UDR in 5GC) informs the PCRF (PCF in 5GC) with the MPS for messaging indication. Subsequently, the PCRF (PCF in 5GC) informs the P-CSCF via Rx/N5 about the MPS for ... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 6.4.4 Impacts on services, entities, and interfaces | This solution will impact following entities:
- NEF: relays activation and deactivation requests and responses between UDM and AF
- N52: Need to add MPS configuration data in Nudm_ParameterProvision.
- N37: Need to add MPS configuration data.
- SCEF: relays activation and deactivation requests and responses between HSS... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 7 Evaluation | |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 7.1 SMS over IP | Single solutions each for 4G and 5G are described in clause 6.1 of this report. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 7.2 MPS support SMS over NAS | Single solutions each for 4G and 5G are described in clause 6.2 of this report. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 7.3 IMS Messaging | Single solutions each for 4G and 5G is described in clause 6.3 of this report. |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 7.4 Overall activation and deactivation of MPS for messaging | Overall activation and deactivation supports the MPS Service User in activating and deactivating MPS for messaging. Two alternatives, an HSS and a UDR method, are described in clause 6.4, solution 4. Both methods focus primarily on how the P-CSCF obtains the MPS for messaging subscription so that the P-CSCF can add Res... |
521c6d66d2eb6cfc5eccb013f72aa7ae | 23.700-75 | 8 Conclusions | The work will proceed based on: It is recommended to use as the basis of normative work the solutions in clauses 6.1, 6.2, 6.3 and 6.4 considering furthermore following assumptions and/or clarifications: 1. MPS priority treatment for SMS over NAS, SMS over IP and IMS messaging requires an MPS subscription and MPS for m... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 1 Scope | Editor's note: This clause will describe the scope for this study item.
This technical report studies further enhancements to the IMS network architecture, interfaces and procedures to support the next generation real time communication services requirements on the following aspects:
1. Study on the enhancements to fra... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 3 Definitions of terms and abbreviations | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1], in TS 23.501 [2] , in TS 23.228 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1], in TS 23.501 [2] or in TS 23.228 [5].
Animated Avatar: Rendered... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1], in TS 23.501 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] or in TS 23.501 [2].
3PCC 3rd Party Call Control
API Appli... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 4 Architectural Assumptions and Principles | The following architectural assumptions and principles shall be considered during the study:
- IMS reference architecture defined in TS 23.228 [5] is used as basis architecture.
- Solutions should have minimal impact to IMS architecture and procedures.
- IMS enhancements to support media handling of avatar calls should... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5 Key Issues | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.1 Key Issue #1: Extensible IMS mechanism supporting IMS events in the context of DC communication | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.1.1 Description | This key issue investigates needed architectural and procedural enhancement to IMS to support an extensible mechanism that enables trusted and untrusted applications to subscribe to and receive reports about IMS events related to IMS services in the context of Data Channel communication.
The KI covers following aspects... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.2 Key issue #2: Impact on IMS architecture, interfaces and procedures to support IMS capability exposure in the context of IMS data channel session | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.2.1 Description | This KI will address the following aspects:
- Study enhancements to IMS architecture, interfaces and procedures to expose IMS services in the following IMS data channel related scenarios:
- IMS data channel initiation, update and release. This includes the initiation, update and release of application and bootstrap dat... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.3 Key Issue #3: Data channel interworking with MTSI UE | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.3.1 Description | Providing service experience of specific IMS data channel applications to subscribers using MTSI UE when appropriate can significantly extend the accessibility of IMS data channel applications. Since MTSI UE does not support IMS data channel, solutions are required to ensure interworking with legacy media types that MT... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.4 Key Issue #4: Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.4.1 Description | Study how to enhance the IMS architecture and procedures to support third party identities in IMS sessions, including:
- Study and if needed, define a mechanism how the serving IMS network can authorize the usage of third party identities in an IMS session.
- Study and if needed, define a mechanism how the terminating ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.5 Key Issue #5: Handling of PS data off exemption for services over IMS DC | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.5.1 Description | This key issue studies how IMS architecture, procedures need to be enhanced to support PS Data off for services over IMS DC. In particular, this key issue will study:
- Whether and how to enhance the current 3GPP PS Data Off Exempt service information (e.g. list of 3GPP PS Data Off Exempt services) to support 3GPP PS D... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.6 Key Issue #6: Support of Standalone IMS Data Channel Sessions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.6.1 Description | This key issue aims to study enhancements of IMS architecture, interfaces, and procedures to support standalone IMS data channel session. This includes studying following aspects:
- How to support standalone IMS bootstrap and application data channel sessions without accompanying audio/video/messaging media in an IMS s... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.7 Key issue #7: Support multiplexing multiple DC applications over single SCTP connection | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.7.1 Description | This key issue addresses the request from GSMA NG to SA WG4 and SA WG2 concerning the use of single SDP m= line for multiple DC applications. The solutions of this KI will address the following aspects:
- Study whether and how to modify IMS DC architecture, interfaces, procedures and functionalities of IMS DC specific ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.8 Key Issue #8: Support of IMS Avatar Communication | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 5.8.1 Description | This key issue aims to study enhancements of IMS architecture, interfaces, and procedures to support IMS based Avatar communication. This includes studying following aspects:
- Define and identify the impacts from Avatar communication between two or more users in the context of IMS.
- Study the identifiers required for... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6 Solutions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
1
2
3
4
5
6
7
8
1
X
2
X
3
X
4
X
5
X
6
X
7
X
X
8
X
9
X
10
X
11
X
12
X
13
X
14
X
15
X
16
X
17
X
18
X
19
X
20
X
21
X
22
X
23
X
24
X
25
X
26
X
27
X
28
X
29
X
30
X
X
31
X
32
X |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1 Solution #1: Architectural Enhancements in Support of exposure of IMS events using HSS Subscription | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.1 Description | In this solution, DCSF subscribes to events defined in Table AA.2.4.2.2-1 in clause AA.2.4.2 of TS 23.228 [5] and other possible IMS events related to a given IMS user of interest via HSS. When the event is fulfilled, the IMS AS notifies the event to DCSF directly.
Additionally, in this solution, it is also proposed th... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.1 DCSF Subscription to IMS Events Via HSS | To subscribe to IMS events defined in Table AA.2.4.2.2-1 in clause AA.2.4.2 of TS 23.228 [5] and any other IMS event, DCSF subscribes to HSS for that purpose by sending the Nhss_ImsEE-Subscribe Request and includes the requested event, as well as the subscriber Identity (e.g. IMPU) in the request. When any of the reque... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.2 Subscription to IMS events via NEF | 6.1.2.2-1: AF Subscription to IMS events via NEF
Figure 6.1.2.2-1 depicts a typical call flow for an AF subscribing to an IMS event for a UE.
1. UE performs initial IMS Registration.
2. S-CSCF performs third party Registration with the IMS AS instance allocated to the registering UE.
3. IMS AS registers in HSS using Nh... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.3 Additional Services and Operations in Support of IMS Event subscription | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.3.1 Enhancements to HSS Services | Nhss_imsUECM service operations are modified to support registering a UE IMS AS instance, list of supported events/event categories.
Table 6.1.2.3.1-1
Service
Service Operations
Operation Semantics
Example Consumer(s)
Nhss_ImsUE Context
Register
Request/Response
S-CSCF, IMS AS instance
Management (Nhss_ImsUECM)
Deregis... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.3.2 Enhancements to Nimsas Services | Service provided by IMS AS are also enhanced to enable HSS to subscribe to an IMS AS instance for IMS events of interest related to a given IMS user. To that effect, a new service is introduced for IMS Event Exposure as depicted below.
Table 6.1.2.3.2-1
Service
Service Operations
Operation Semantics
Example Consumer(s)... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.2.3.3 Enhancements to Nnef Services | A new service is introduced for IMS Event Exposure as depicted below:
Table 6.1.2.3.3-1
Service
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_ImsEventExposure (ImsEE)
Subscribe
Subscribe/Notify
AF
Unsubscribe
Subscribe/Notify
AF
Notify
Subscribe/Notify
NEF |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.1.3 Impacts on existing services, entities and interfaces | HSS impacts:
- Stores IMS AS instance serving a UE at initial IMS registration including the list of supported events/event categories.
- Receive requests of subscription to notification from DCSF and NEF for a UE related events.
- Subscribe to an IMS AS instance for a UE for IMS related events on behalf of the DCSF or... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2 Solution #2: Event subscription and notification enhancements for DC applications | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.1 General | This solution addresses Key Issue #1 Extensible IMS mechanism supporting IMS events in the context of DC communication.
This solution follows the Rel-18 IMS data channel architecture in TS 23.228 [5] and support both scenarios that DC application server interacts with IMS network via N33 and via DC4.
Figure 6.2.1.1: IM... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.2 Report of registration events | This solution proposes to introduce report of registration events from IMS AS to DC application server via DCSF by which DC application server have a chance to subscribe the upcoming events from IMS network.
When the IMS AS receives third party registration request from S-CSCF, it triggers registration event report to ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.3 Determination the interaction mode between DC application server and IMS network | If the DCSF supports both interaction with DC application server directly or via DC3, when it notifies the DC application server about the IMS events, it determine which interaction mode is used based on the service data received from UDM/HSS. In this case the service data stores the information of interaction mode per... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.4 Discovery and selection of NFs | IMS AS discovers and selects the DCSF using existing Rel-18 mechanism.
The DCSF discovers and selects NEF via NRF. If a NEF only serves to specific subscribers, the NEF registers itself to NRF with the IMPU range it serves. The DCSF discovers and selects NEF using the IMPU in the REGISTER request to discover the NEF se... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.5 Definition of group of IMS subscriber | The DC application server supports generating a group of served IMS subscribers and subscribes IMS events for the group in a single service invocation. The group of served IMS subscribers can be all IMPUs in implicitly registered IMPU set or any combination of IMPUs it serves.
Editor's note: Whether and how to indicate... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.1.6 Subscription and notification of IMS events | During the registration event report procedure in clause 6.2.1.2, the DC application server has known the notification address of further event subscription for a specific IMPU or implicitly registered IMPU set, i.e. the DCSF or the NEF.
When a DC application server wants to subscribe the IMS events to the IMS network,... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2 Services | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.1 DCSF services | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.1.1 General | The following table shows the DCSF Services and Service Operations.
Table 6.2.2.1.1-1
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Ndcsf_DCSessionEventControl
Subscribe
Subscribe/Notify
NEF, DC AS
Unsubscribe
Subscribe/Notify
NEF, DC AS
Notify
Subscribe/Notify
NEF, DC AS |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.1.2 Ndcsf_DCSessionEventControl | 6.2.2.1.2.1 Ndcsf_DCSessionEventControl_Subscribe service operation
This service operation is used to enable the consumer to subscribe interested session related and data channel related events from the DCSF.
In this service operation, the consumer provides the session ID of the related IMS session, the list of event s... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.2 NEF services | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.2.1 General | The following table shows the NEF Services and Service Operations.
Table 6.2.2.2.1-1
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_DCSessionEventControl
Subscribe
Subscribe/Notify
DCSF, DC AS
Unsubscribe
Subscribe/Notify
DCSF, DC AS
Notify
Subscribe/Notify
DCSF, DC AS |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.1.2 Nnef_DCSessionEventControl | 6.2.2.1.2.1 Nnef_DCSessionEventControl_Subscribe service operation
This service operation enables the consumer to subscribe session and DC related events from NEF.
In this service operation, the consumer provides the session ID of the related IMS session, the list of event subscription information including IMS public ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.2.3 IMS AS services | The IMS AS service is enhanced to support reporting additional IMS registration event to the DCSF. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.3 Procedures | Figure 6.2.3.1: IMS DC architecture in TS 23.228 [5]
1. IMS registration procedure.
2. The S-CSCF send third party registration request to IMS AS, which includes IMPU or implicitly registered IMPU set.
3. The IMS AS notifies the registration event of the UE to DCSF using the same notification mechanism in Rel-18.
4. Th... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.2.4 Impacts on Existing Nodes and Functionality | IMS AS:
- support notification of registration event to DCSF.
DCSF:
- determine which interaction mode is used based on the service data received from UDM/HSS.
- support notification of registration event to NEF or DC application server.
- support subscription from DC application server and notification of IMS events t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3 Solution #3: Subscription and Notification for DC Events | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.1 Description | The subscription and notification for data channel events are introduced in TS 23.228 [5]. The services and their operations provided by IMS AS are defined as following:
Table 6.3.1-1
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nimsas_SessionEventControl
Subscribe
Subscribe/Notify
DCSF
Notif... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.1.1 Nimsas_SessionEventControl_Subscribe service operation | Service operation name: Nimsas_SessionEventControl_Subscribe
Description: This service operation enables NF consumers (e.g. DCSF) subscribe session events related to a specific served IMS subscriber or a list of IMS subscribers requesting use of data channel media.
Inputs, Required: NF type, Event type.
In this Release... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.1.2 Nimsas_SessionEventControl_Notify service operation | Nimsas_SessionEventControl_Notify service operation is specified in clause AA.2.4.2.2 of TS 23.228 [5]. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.1.3 Nimsas_SessionEventControl_Unsubscribe service operation | Service operation name: Nimsas_SessionEventControl_Unsubscribe
Description: This service operation enables NF consumers (e.g. DCSF) unsubscribe session events related to a specific served IMS subscriber or a list of IMS subscribers requesting use of data channel media.
Inputs, Required: Subscription Correlation ID
Inpu... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.2 Procedures |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.