hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.5 Solution #5: Early Media in Alerting Phase (CAT) Based on DC AS Initiated A2P DC
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.5.0 High-level solution Principles
| This solution addresses Key Issue #1: ADC establishment in alerting phase for early media.
The solution focuses on the DC based Customized Alerting Tones (CAT) service which is subscribed by the called party and it will provide customized content to the calling party as an early media during the calling process. The same principle could be applied to both calling and called party-side subscription and providing the A2P ADC to either side of the UE. The different procedures only vary in the request that the DC AS sends to the IMS AS.
The solution has the following principles:
- The called UE B has subscribed to the DC based CAT service.
- The calling UE A and the network serving the called UE B have the early media capability and UE A has negotiated with the serving network regarding this capability.
- The solution needs an enhancement of the subscribe/notify framework for event monitoring procedure to notify the DC AS the calling event which needs an A2P DC to deliver the early media
- The solution reuses the IMS DC capability exposure procedure to establish an A2P DC which is used to transmit the early media to the UE.
- The IMS-AS serving the called UE B notifies the calling event to the DC AS; the DC AS triggers the A2P DC establishment process to the calling UE A.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.5.1 Description
| This solution provides a procedure on how to establish an A2P ADC in alerting phase to provide customized DC content to the calling party as an early media.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.5.2 Procedure
| The pre-condition of the following procedure is that the called UE B has subscribed to the DC based CAT service and the calling UE A and the serving network of called UE B have the early media capability and UE A has negotiated with the serving network regarding this capability. It assumes that the DC based CAT service will not coexists with the legacy CAT service; it means the UE will subscribe only one of the CAT services.
Figure 6.5.2-1: Procedure of A2P ADC establishment in alerting phase
The steps in the procedure are as follows:
1. UE A initiates SIP INVITE including Audio/Video/BDC SDP; step 1-13 of Figure AC.7.1-1 in TS 23.228 [2] for BDC establishment apply.
2. BDC has been established for UE A.
3. Based on the subscription of UE B, IMS AS-2 decides to notify the DC AS at the network serving UE B this BDC establishment event.
NOTE 1: It assumes that the DC AS has subscribed the BDC establishment event of UE B.5.
4. The IMS AS-2 sends the Nimsas_ImsEE_Notify Request to the NEF the calling event including the calling UE A and the called UE B information, as well as IMS Session ID.
5. The NEF sends the Nnef_ImsEE_Notify Request to the DC AS the calling event including the corresponding information.
6. The DC AS decides to establish A2P ADC to UE A to deliver the DC early media.
7. UE B sends 180 Ringing to IMS AS-2.
8. The DC AS establishes A2P ADC with UE A; and step 1-21 of Figure AG.2.1.1-1 in TS 23.228 [2] for adding ADC to an existing IMS session apply with the following differences.
- The A2P ADC is added to an IMS session in establishment phase not an existing IMS session.
- The SIP signal UPDATE is used instead of re-INVITE in the procedure of AG.2.1.1 in TS 23.228 [2].
- The destination of A2P ADC is UE A rather than UE B in the terminating network.
UE A may download the application used in the alert phase.
The DC AS may send the A2P ADC addition request to the IMS AS-2 prior to the 180 Ringing. The IMS AS-2 will hold the request until it receives the 180 Ringing from the UE B.
9. The UE B/terminating network and UE A/originating network exchange 180 Ringing, SIP signals.
10. The A2P ADC between UE A and the DC AS which goes through the MF is activated and the early media (customized alerting tones) of this IMS session is delivered from the DC AS to UE A. The user of UE A experiences with the early media.
11. The user of UE B picks up the phone and the UE B/terminating network and UE A/originating network exchange 200 OK (INVITE) SIP signal.
12. The IMS AS-2 notifies the DC AS at the called network the IMS session establishment event.
13. The DC AS releases the A2P ADC with UE A.
14. Subsequent procedures continue.
NOTE 2: The detailed steps for interaction between the IMS-AS and the DCSF, the IMS-AS and the MF are not illustrated in the procedure, which reuse the corresponding steps in Figure AC.7.1-1 and Figure AG.2.1.1-1.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.5.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- supporting ADC establishment in alerting phase.
IMS AS:
- supporting report of IMS session establishment events to DC AS;
- supporting A2P DC establishment for delivering early media.
MF:
- receiving early media from DC AS and providing it to UE through A2P DC.
DC AS:
- supporting receiving IMS session establishment events from IMS AS through NEF;
- supporting initiating and releasing A2P DC for delivering early media.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6 Solution #6: Support Alerting phase P2A ADC establishment through Autolaunch/Autoload Parameter
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.0 High-level solution Principles
| This solution supports application data channel establishment during the alerting phase. This solution is based on the following high-level solution principles:
- The bootstrap data channel media negotiation will follow the existing procedure defined in clause AC.7 of TS 23.228 [2] and that the bootstrap data channel will be established before SIP 180 message from the terminating party.
- In order to optimize the user experience during data channel establishment in the alerting phase, the IE Autolaunch and/or Autoload defined in Table 8.2.2.3.1-2 of TS 23.392 [7] will be used by the UE to automatically launch the application that need to be used during the alerting phase. The configuration of data channel application profile is defined in TS 23.392 [7].
- Only P2A/A2P application data channel is supported. Any P2P or P2A2P application data channel should be established after the 200 OK of initial SIP INVITE. This solution only focuses on the P2A application data channel procedures.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.1 Description
| This solution proposes to support application data channel establishment during the alerting phase to enhance specific subscription-based services. Some examples of such services include:
- Customized Alerting Tone (CAT)
- Customized Ringing Signal (CRS)
- Originating Identification Presentation (OIP)
- Terminating Identification Presentation (TIP)
NOTE 1: The established ADC could be used either as the complement of existing services or be used to replace the existing services.
This solution supports establishment of 4 types of P2A application data channel during the alerting phase:
- From originating network to originating subscriber. (e.g. CAT, TIP)
- From originating network to terminating subscriber. (e.g. CRS, OIP)
- From terminating network to originating subscriber. (e.g. CAT, TIP)
- From terminating network to terminating subscriber. (e.g. CRS, OIP)
In the P2A (i.e. the UE initiates the application data channel),the overall procedure is as following:
1. UE-A initiates the session. The bootstrap data channel is established before the 180 ringing.
2. The DCSF sends the data channel application profile contained in the root application/application list. The profile contains the Autolaunch/Autoload parameter based on configuration or subscription. UE-A/UE-B automatically download and launch the application based on the Autolaunch/Autoload parameter.
3. The application established the ADC after the 180 ringing.
NOTE 2: If the 200 OK of the SIP INVITE is received by UE-A before the application download completion, the UE needs to continue with the call establishment and skip step 3 above. Whether the UE will stop the download immediately or complete the download after the call establishment is up to UE implementation.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.2 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.2.1 Application Download Procedure
| The TS 23.392 [7] defines the Autolaunch/Autoload parameter in the data channel application profile, which could be used to automatically download and launch data channel application used during the ringing phase.
NOTE 1: The privacy and user consent issue should comply with the definition in NOTE 3 and NOTE 4 in Table 8.2.2.3.1-2 of TS 23.392 [7] in SA WG6. The security aspect should be considered in SA WG3.
Figure 6.6.2.1-1: Application Download Procedure
1. Steps 1-14 of clause AC.7.1 of TS 23.228 [2] applies to establish IMS session and bootstrap data channel.
2. UE-A/UE-B sends HTTP Get request to download the root application/application list from its serving network.
3. DCSF-A/DCSF-B sends the root application/application list through the HTTP get response. The root application/application list contains the data channel application profiles, which one of the profiles may contain the Autolaunch/Autoload parameter. The configuration of data channel application profile is defined in TS 23.392 [7].
Editor’s note: How the SA WG6 architecture of application and application profile download maps to the existing SA WG2 architecture is FFS. Whether the autolaunch parameter could be used during early session is FFS. Further collaboration with SA WG6 might be needed.
NOTE 2: Steps 2-3 are out of scope of SA WG2 and defined in SA WG6.
NOTE 3: It is also possible that UE-A sends HTTP Get request to the DCSF-B and UE-B sends HTTP Get request to the DCSF-A. The procedure will follow the existing specification.
4. Optionally, UE-A/UE-B can automatically download and launch a given data channel application if it contains Autolaunch/Autoload parameter in its data channel application profile. The definition and usage of the parameter are defined in TS 23.392 [7].
NOTE 4: How the UE authorize the download are based on the existing procedure defined in SA WG6 and UE implementation. It is also up to the UE implementation and local regulations that whether the UE need to inform the user and/or acquire consent from the user before initiating the download based on the Autolaunch/Autoload parameter.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.2.2 Originating-side Application Data Channel Establishment Procedure in P2A Mode
| The UE-A/UE-B may initiate application data channel establishment procedure after the corresponding data channel application has been downloaded and launched. The depicted procedure starts after the UE-B sends the 180 ringing to the UE-A.
Figure 6.6.2.2-1: Originating-side Application Data Channel Establishment Procedure in P2A Mode
1. UE-B sends 180 ringing message indicating it starts to ring.
2. UE-A sends SIP Update to establish P2A application data channel for application downloaded with the procedure specified in Clause 6.6.2.1.
3. Steps 2-21 of clause AC.7.2.2 of TS 23.228 [2] applies to establish P2A ADC with the difference that the SIP Update instead of SIP re-INVITE has been used.
The DCSF can optionally instruct the IMS AS to anchor the audio and/or video channel to the MF/DC AS if any additional media needs to be sent to the UE based on the subscription and type of services that requesting the ADC, e.g. play additional alerting tone alongside with the established ADC.
4. The IMS AS forwards the 200 OK response of SIP Update from terminating UE to the UE-A.
5. The terminating network sends 200 OK of SIP INVITE, indicating the session has been established.
6. UE-A sends ACK.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.2.3 Terminating-side Application Data Channel Establishment Procedure in P2A Mode
|
Figure 6.6.2.3-1: Terminating-side Application Data Channel Establishment Procedure in P2A Mode
1. UE-B sends 180 ringing indicating it starts to ring.
2. UE-B sends SIP Update to establish P2A application data channel for application downloaded with the procedure specified in clause 6.6.2.1.
3. Steps 2-21 in clause AC.7.2.2 of TS 23.228 [2] applies to establish P2A ADC.
The DCSF can optionally instruct the IMS AS to anchor the audio and/or video channel to the MF/DC AS if any additional media needs to be sent to the UE based on the subscription and type of services that requesting the ADC, e.g. play additional alerting tone alongside with the established ADC.
4. The IMS AS forwards the 200 OK response of SIP Update from originating UE to the UE-B.
5. The terminating network sends 200 OK of SIP INVITE, indicating the session has been established.
6. UE-A sends ACK.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.2.4 Terminating Application Data Channel After the Call Established
|
Figure 6.6.2.4-1: Terminating Application Data Channel After the Call Established
1. The terminating network sends 200 OK of SIP INVITE, indicating the session has been established.
2. UE-A sends ACK.
3. UE-A initiates a SIP reINVITE request to terminate the ADC based on clause AC.7.6 of TS 23.228 [2].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.6.3 Impacts on Existing Nodes and Functionality
| UE:
- supporting ADC establishment in alerting phase.
- supporting Autolaunch/Autoload parameter in the DC App profile.
IMS AS/DCSF/MF/DC AS:
- supporting ADC establishment in alerting phase.
MF:
- providing early media to UE through DC/audio/video based on the instruction from DC AS.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.7 Solution #7: IMS DC Events Supported by DCSF
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.7.0 High-level solution Principles
| This solution addresses Key Issue #2: enhancements to capability exposure framework for eMMTel services, especially how to support IMS DC events supported by DCSF.
The solution has the following principles:
- The DCSF can expose some IMS DC events to NEF or AF.
- The exposure interfaces will reuse DC3 between DCSF and NEF and DC4 between DCSF and AF.
- The AF supports subscribing the events exposed by the DCSF and receiving the IMS DC events from the DCSF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.7.1 Description
| This solution provides a procedure on how to support IMS DC events supported by DCSF.
The Table 6.7.1-1 which is the modification of Table AD.2.5.2-1 List of events for monitoring capability in clause AD.2.5.2 of TS 23.228 [2] includes the IMS DC events supported by DCSF.
Table 6.7.1-1: (modified Table AD.2.5.2-1of TS 23.228 [2]) List of events for monitoring capability (changes in RED)
Event
Description and Detection criteria
Which NF detects the event
Bootstrap Data Channel established
Detected when a Bootstrap data channel is established.
Network detects that a Bootstrap data channel is established when the SDP for an established IMS DC includes the media for a Bootstrap data channel with the corresponding Bootstrap DC stream ID according to TS 26.114 [3].
IMS AS
Bootstrap Data Channel Release
Detected when an established Bootstrap data channel is released.
Network detects that a Bootstrap data channel is released when an IMS DC that includes an SDP with the media for a Bootstrap data channel with the corresponding Bootstrap DC stream ID according to TS 26.114 [3] is released, or an IMS DC is updated to remove the media for a Bootstrap data channel with the corresponding Bootstrap DC stream ID according to TS 26.114 [3].
IMS AS
Application Data Channel established
Detected when an Application Data Channel is established.
Network detects that an Application data channel is established when the SDP for an established IMS DC includes the media for an Application data channel with the corresponding Application DC stream ID according to TS 26.114 [3]. The Application DC stream ID can be explicit or any stream ID.
IMS AS
Application Data Channel Release
Detected when an Application data channel is released.
Network detects that an Application data channel is released when an IMS DC that includes an SDP with the media for an Application data channel with the corresponding Application DC stream ID according to TS 26.114 [3] is released, or an IMS DC is updated to remove the media for an Application data channel with the corresponding Application DC stream ID according to TS 26.114 [3].
IMS AS
Application Data Channel requires interworking is established
Detected when an Application Data Channel that requires interworking is in the process of establishment.
Network detects that an P2A Application data channel is in process of establishment and the MDC2 resources are assigned for the Application data channel.
IMS AS
Application operation
Detected when an application is operated.
Network detects that an application is operated, e.g. downloading.
DCSF
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.7.2 Procedure
| The procedure for DCSF event exposure is very similar to the subscribe/notify procedure for non-subscriber specific IMS events in clause AD.3.3 of TS 23.228 [2]. The following differences apply:
- the subscribing destination is DCSF rather than IMS AS;
Figure 6.7.2-1: Procedure for subscribe/notify of events supported by DCSF
The steps in the procedure are as follows:
1. The AF subscribes to NEF initiating the Nnef_imsEE_Subscribe Request for non-subscriber specific IMS DC events supported by the DCSF.
2. If the subscription to the non-subscriber specific IMS event is authorized by the NEF, the NEF locates all DCSF instances that support the requested IMS DC events via NRF or by local configuration.
3. For each DCSF instance that supports the requested IMS DC event, NEF subscribes to the DCSF for the requested IMS event via DC3.
4. The DCSF returns to the NEF the Subscription Response via DC3.
5. The NEF returns to AF the Nnef_ImsEE_Subscribe Response.
6. At some point, the requested IMS DC event is detected by the DCSF.
7. The DCSF sends a notification to the NEF.
8. The NEF sends Nnef_ImsEE_Notify Request to the AF.
NOTE 1: For the trusted AF, the AF may send the subscription request to the DCSF and receive the event notification from the DCSF via DC4 directly.
NOTE 2: For the subscribing request from AF when it is subscriber specific, the NEF may discover the DCSF from the HSS; and it is assumed that the DCSF has registered to the HSS as described in other Solution #9.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.7.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DCSF:
- supporting detecting IMS DC events which are subscribed by an AF;
- supporting IMS DC event subscription and notification;
- supporting registering to the HSS.
NEF:
- supporting transferring the subscription request from AF to DCSF;
- supporting transferring the event notification from DCSF to AF.
AF:
- supporting subscription and receiving IMS DC events detected by DCSF.
HSS:
- supporting registration and discovery of the DCSF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8 Solution #8: Subscription and notification of DC application downloading events
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8.0 High-level solution principles
| This solution targets KI2.
This solution enables an AF (a DC AS) to subscribe to and being notified about events related to the downloading of DC applications. Four types of events are supported: these events can be related to specific or any UE(s), as well as independent or dependent on application(s) (see clause 6.8.1). Subscription requests optionally include filter information to control the granularity and frequency of notifications. inducing usage of NWDAF to enforce statistics or predictions on the notifications related with application download. The AF (DC AS) can use the corresponding notifications to assess the popularity of applications (especially P2P applications).
Once the IMS AS has received a subscription request from the AF as defined in Annex AD.3 of TS 23.228 [2] and when a BDC is established, the IMS AS, based on the type of the DC application downloading events (see clause 6.8.1), provides the subscription to the selected DCSF handling the BDC (this assumes the definition of an IMS AS event requiring the IMS AS is to forward to the selected DCSF). The solution does not assume a 1-1 mapping between IMS AS and DCSF. The selected DCSF is responsible for detecting these events and reports the relevant information directly to the AF/DC AS (or to the NEF).
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8.1 Types of DC application downloading events
| To support enhanced exposure capabilities, the IMS DC exposure framework provides mechanism for a DC AS to subscribe to events related to the downloading of DC applications. Four types of DC application downloading events are supported:
- Type 1: Subscriber-specific and DC application-specific event: The subscription request relates to one or more UEs (identified by their IMPUs) and one or more DC application identifiers. A notification shall be triggered only when one of the UE(s) downloads one of the DC applications.
- Type 2: Subscriber-specific and DC application-agnostic event: The subscription request relates to one or more UEs, without indicating any specific DC application identifier. The DC AS identifier shall be included in the subscription request. A notification shall be triggered when one of the specified UE(s) download any DC application associated with the subscribing DC AS. Notifications for DC applications associated with other DC ASs shall not be provided.
- Type 3: Subscriber-agnostic and DC application-specific event: The subscription request relates to one or more DC application identifiers, without specifying any UE. A notification shall be triggered when a UE downloads the specified DC application(s).
- Type 4: Subscriber-agnostic and DC application-agnostic event: The subscription request shall not specify any UE or DC application identifier. The DC AS identifier shall be included in the subscription request. A notification shall be triggered when a UE downloads any DC application associated with the subscribing DC AS. Notifications for DC applications associated with other DC ASs shall not be provided.
NOTE 1: It is assumed that the DCSF can determine that a DC application is associated with a DC AS either via configuration or via proper application naming convention.
Subscription requests optionally include filter information to enable the DC AS to specify criteria for event reporting, such as periodic notifications or reporting of event statics to prevent excessive signalling for individual events. The IMS network may negotiate the event filter parameters with the DC AS to ensure alignment with network capabilities, resource availability and operational policies.
The event subscription provided to the DCSF contains the AF Id of the DC AS allowing the DSCF to control whether to send a notification related to a given application to the DC AS.
NOTE 2: This is to ensure that a DC AS can receive notifications only about "its own applications".
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8.2 Procedure of DC application downloading event subscription and notification
| Figure 6.8.2-1 depicts a signalling flow diagram for DC application downloading event subscription and notification.
Figure 6.8.2-1: Procedure of DC application downloading event subscription and notification
1. The AF (DC AS) sends a subscription request (see clause 6.8.1) to the DC application download event(s) to IMS AS via the NEF. For Type 1 or Type 2 event targeting specific UE(s), clause AD.3.2 of TS 23.228 [2] is followed. For Type 3 or Type 4 event targeting any UE, clause AD.3.3 of TS 23.228 [2] is followed.
The IMS AS instance(s) locally store the subscription request(either globally for subscription targeting Any UE or in association with the IMS registration for subscription targeting an individual UE). The IMS AS needs to understand the event type and the targeted UE(s), but does not need to understand other information about this event in the subscription request.
NOTE 1: This corresponds to a new IMS AS event requiring the IMS AS to forward the corresponding event subscription to the selected DCSF.
2. The UE requests BDC establishment as defined in clause AC.7.1 of TS 23.228 [2]. During this process, the IMS AS selects a DCSF.
3. The IMS AS on behalf of the NEF/DC AS forwards the event subscription request received in step 1 to the selected DCSF for: when the IMS AS notifies the DCSF of the session establishment event by sending Nimsas_SessionEventControl_Notify (SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, etc.) it provides the DC AS / NEF subscription request to the DCSF.
4. The DCSF responds to the IMS AS, indicating successful subscription.
5. The UE downloads a DC application via the established BDC.
6. The DCSF checks whether the downloaded DC application is associated with the DC AS having issued the subscription request and whether the Event is authorized for this UE. If it does not, the event shall not be notified.
NOTE 2: This is to ensure that a DC AS can receive notifications only about "its own applications". To be able to detect whether the downloaded DC application is associated with the DC AS having issued the subscription request either the DSCF can be configured with the mapping between DC applications and the AF ID associated with the DC AS or the application Id (negotiated with the DC AS) contains a reference to this AF ID,
7-8. The DCSF notifies the NEF of the DC application downloading event. The NEF responds to the notification.
9-10. The NEF notifies the DC AS of the DC application downloading event. The DC AS responds to the notification.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8.3 Procedure for reporting DC application usage event analytics
| Figure 6.8.3-1 depicts a signalling flow diagram for reporting of DC application usage event analytics.
The AF / DC AS requests for analytics of DC application usage (e.g. download) events providing criteria for analytics reporting, e.g. reporting the number of DC app A downloading within the next 10 days or per period of 10.
If no analytics filter is provided, the procedure in clause 6.8.2 applies.
NOTE 1: Analytics of DC application downloading events allows providing AF / DC AS with information about DC application usage without burdening AF / DC AS each time there is an application download.
Figure 6.8.3-1: Procedure for analytics related with DC application usage event subscription
1. The AF (DC AS) sends a subscription request (Nnef_AnalyticsExposure_Subscribe) for the DC application download event(s) (see clause 6.8.1) to the NEF, including a Notification Target Address (+ Notification Correlation ID) for this subscription request. The difference with similar step in clause 6.8.2 is that filter information specifying criteria for analytics event reporting, is provided as part of the subscription request. Target of Analytic Reporting may indicate an individual UE or any UE.
2. NEF creates a Notification Target Address (+ Notification Correlation ID) for the received subscription request. The NEF selects a NWDAF (that supports the newly defined analytics related with DC application usage event subscription) and sends the subscription request to the NWDAF using Nnwdaf_AnalyticsSubscription_Subscribe including the Notification Target Address (+ Notification Correlation ID).
3. NWDAF creates a NWDAF Notification Target Address (+ Notification Correlation ID) for receiving the DC application downloading related event report. NWDAF responds to the NEF including the NWDAF Notification Target Address (+ Notification Correlation ID).
4. NEF subscribes to IMS network for the event described in the subscription request and includes the NWDAF Notification Target Address (+ Notification Correlation ID) received in step 3 in the subscription request. The way of subscription follows clauses AD.3.2 and AD.3.3 of TS 23.228 [2], as described in step 1 of clause 6.8.2. This subscription is on behalf of the NWDAF.
5. Event detection by DCSF as defined steps 2-6 in clause 6.8.2.
6-7. The DCSF reports the detected event to the NWDAF using the NWDAF Notification Target Address (+ Notification Correlation ID) received in step 4. The NWDAF responds to the report.
8-9. NWDAF aggregates the events based on the Notification Correlation ID contained in the messages from step 6 and generates the analytics result. NWDAF notifies NEF about the analytics result using Notification Target Address (+ Notification Correlation ID) received in step 2 via Nnwdaf_AnalyticsSubscription_Notify. The NEF responds to the notification.
10-11. The NEF determines the DC AS based on the Notification Correlation ID received in step 1 and notifies the DC AS about the analytics result via Nnef_AnalyticsExposure_Notify. The DC AS responds to the notification.
As an alternative described in Figure 6.8.3-2, the NWDAF may directly subscribes to the IMS network.
NOTE 2: Only One of alternative will be specified: either the alternative described in Figure 6.8.3-1 or the alternative described in Figure 6.8.3-2 where the NWDAF directly subscribes to the IMS network.
Figure 6.8.3-2: Procedure for analytics related with DC application usage event subscription (NWDAF directly subscribes to the IMS network)
- Steps 1 and 2 are the same as in figure 6.8.3-1.
- Step 3: The NWDAF subscribes to the IMS network for the event described in the subscription request and includes the NWDAF Notification Target Address (+ Notification Correlation ID). The way of subscription follows clauses AD.3.2 and AD.3.3 of TS 23.228 [2], but where the NWDAF initiates the subscription instead of the NEF.
- Step 4: The NWDAF answers to the subscription request and the answer is provided by the NEF to the DC AS.
- The rest of the steps are as in figure 6.8.3-1.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.8.4 Impacts on services, entities and interfaces
| The variant with DC application usage event analytics assumes a deployment where the IMS network can access to a NWDAF; this means the definition of a new Reference point in TS 23.228 [2].
DC AS:
- Requesting new events on about DC application downloading.
- Providing analytics filter information about the DC application downloading event for procedure of DC application downloading event analytics in clause 6.8.3.
NEF:
- Definition of new event about DC application downloading.
IMS AS:
- Forwarding of new event subscription request to DCSF based on event type and target UE(s).
- Definition of an IMS AS event requiring the IMS AS to forward the corresponding subscription to the selected DCSF.
DSCF:
- Receiving new event subscription request.
- checking the association between DC application and DC AS.
- Notifying of the event to the consumer (DC AS, or to NWDAF for DC application downloading event analytics).
NOTE: For DC application downloading event analytics, the DCSF interfaces NWDAF when sending notifications to NWDAF but based on SBA principles, the DCSF does not need to be aware which entity it is sending a notification to.
NWDAF (DC application usage event analytics):
- Generating analytics about DC application downloading events based on the filter information and the received event reports.
- (if Figure 6.8.3-2 applies) subscription following clauses AD.3.2 and AD.3.3 of TS 23.228 [2], where the NWDAF initiates the subscription instead of the NEF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9 Solution #9: Capability exposure of IMS DC events supported by DCSF
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.0 High-level solution Principles
| This solution addresses Key Issue #2: Capability exposure of IMS DC events supported by DCSF.
The main principle of this solution for support capability exposure of IMS DC events supported by DCSF as follows:
- The trusted AF or untrusted AF via NEF shall discover and select the DCSF.
- To discover DCSF address, DC AS subscribe with HSS and HSS notifies once DCSF register its address in HSS.
- Similar to third party registration done by S-CSCF to IMS AS, IMS AS does third party registration with DCSF and then DCSF register its address in HSS.
- Upon successful discovery and selection, DCSF subscribes for the establishment of supported events with DCSF and get notified when DCSF detects the events.
NOTE: This solution involves DCSF during registration of IMPU while it was invoked during session earlier. The implications of this approach will not be discussed further in this solution.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.1 Description
| This solution proposes how the trusted AF and untrusted AF via NEF discovers the DCSF and subscribes to get notification for the supported events by DCSF.
Discovery of DCSF:
The trusted AF can directly discover the DCSF with the help of HSS and in case of untrusted AF, the discovery happens through NEF. For this purpose, HSS can expose one service operation using which DC AS/NEF will subscribe and get notification about the DCSF address for the UE.
When UE registers with IMS network, S-CSCF does third party registration with IMS AS and then IMS AS registers its address with HSS. Similarly, this solution proposed IMS AS does third party registration with DCSF and then DCSF registers its address with HSS. When HSS receives the subscription request for DCSF address from NEF or trusted AF and the DCSF address is not present in HSS (i.e. in the case when the IMPU is not yet registered or de-registered) then HSS stores the subscription request. Once HSS comes to know the DCSF address (i.e. when IMPU does IMS registration and DCSF register its address to HSS), HSS notifies the DCSF address with NEF/AF.
Subscription and Notification with DCSF:
Upon successful discovery, AF/NEF shall subscribe with DCSF for the supported events and get notified when DCSF detects the event.
Table 6.9.1-1 List of events supported by DCSF
Event
Description and Detection criteria
Which NF detects the event
Successful Application download to UE
Detected when an Application Data Channel is established.
DCSF detects that UE has been successfully downloaded one specific application
DCSF
NOTE: This solution identifies changes to existing specifications, these changes are shown using RED text.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1 General
| The following table shows the required service operation.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1 HSS Service
| The following table shows the services exposed by an SBI capable HSS.
Table 6.9.2.1.1: (Updated Table AA.2.1.1-1 from TS 23.228 [2]): IMS Services provided by an SBI capable HSS
Service
Service Operations
Operation Semantics
Example Consumer(s)
Get
Request/Response
S-CSCF, I-CSCF, AS, DCSF
ImsSubscriber Data
Subscribe
Subscribe/Notify
S-CSCF, AS
Management (_ImsSDM)
Unsubscribe
Subscribe/Notify
S-CSCF, AS
Notification
Subscribe/Notify
S-CSCF, AS
Update
Request/Response
AS, DCSF
Registration
Request/Response
S-CSCF, IMS AS, DCSF
DeregistrationNotification
Subscribe/Notify
S-CSCF
Deregistration
Request/Response
S-CSCF, IMS AS
Ims UE Context
Authorize
Request/Response
I-CSCF
Management (_ImsUECM)
Update
Request/Response
S-CSCF
RestorationInfoGet
Request/Response
S-CSCF
RestorationInfoUpdate
Request/Response
S-CSCF
AsInfoGet
Request/Response
NEF
DcsfInfoGet
Subscribe/Notify
NEF, AF
DcsfInfoUnsubscribe
Subscribe/Notify
NEF, AF
DcsfInfoNotify
Subscribe/Notify
NEF, AF
ImsUE Authentication (_ImsUEAU)
Get
Request/Response
S-CSCF
ImsEventExposure
Subscribe
Subscribe/Notify
NEF, Trusted AF
(_ImsEE)
Unsubscribe
NEF, Trusted AF
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1.0 Nhss_ImsUECM_Registration service operation (modified)
| Clause AA.2.1.2.1 of TS 23.228 [2] is modified to:
Service operation name: Nhss_ImsUECM_Registration
Description: If S-CSCF is the consumer, this service operation registers the serving S-CSCF assigned to an IMS User. If authentication is not to be performed, this operation also sets the registration state. The S-CSCF is implicitly subscribed to be notified when it is deregistered in HSS. This notification is done by means of Nhss_ImsUECM_DeregistrationNotification operation.
If IMS AS is the consumer, this service operation registers the IMS AS instance assigned to an IMS user.
If the DCSF is the consumer, this service operation registers the DCSF instance assigned to an IMS user.
Inputs, Required: Public Identity, S-CSCF name and Registration Type (e.g. Initial Registration, Unregistered) if the S-CSCSF is the consumer, IMS AS instance Id if the IMS AS is the consumer, DCSF instance Id if the DCSF is the consumer.
Inputs, Optional: Private Identity.
Outputs, Required: Result indication.
Outputs, Optional: List of registered Private Identities sharing the same Public Identity which is being registered, S-CSCF Restoration indication.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1.1 Nhss_ImsUECM_Deregistration service operation (modified)
| Service operation name: Nhss_ImsUECM_Deregistration
Description: This service operation deregisters the S-CSCF allocated to a public identity if the consumer is S-CSCF and deregisters the IMS AS instance assigned to the public identity if the consumer is IMS AS.
Inputs, Required: S-CSCF name if the S-CSCSF is the consumer, IMS AS instance ID if the IMS AS is the consumer, DCSF instance Id if the DCSF is the consumer, Deregistration Type.
Inputs, Optional: User Identity (Private Identity and/or Public Identity), P-CSCF Restoration indication, Session Priority.
Outputs, Required: Result indication.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1.2 Nhss_ImsUECM_DcsfInfoGet service operation
| Service operation name: Nhss_ImsUECM_DcsfInfoGet
Description: Service consumer like NEF or DC AS subscribes with HSS to receive the DCSF address assigned for the UE. The request creates an implicit subscription to get notified about the following events, when applicable, (1) the DCSF address is removed from HSS (IMPU is de-registered) 2) DCSF address is added to HSS (IMPU is registered) 3) DCSF address is updated.
Inputs, Required: Public Identity.
Inputs, Optional: Private Identity.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1.3 Nhss_ImsUECM_DcsfUnsubscribe
| Service operation name: Nhss_ImsUECM_DcsfUnsubscribe
Description: This service operation enables consumers to unsubscribe from the event.
Inputs, Required: Subscription correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.1.4 Nhss_ImsUECM_DcsfNotify
| Service operation name: Nhss_ImsUECM_DcsfNotify
Description: This service operation enables the HSS to notify the consumer with the updated DCSF address where there is a change of DCSF happens for the UE.
Inputs, Required: DCSF address.
Inputs, Optional: IMPU, IMPI.
Outputs, Required: Result.
Outputs, Optional: None.
Inputs, Optional: securitySetup if DC AS initiates the DTLS negotiation.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2 DCSF Service
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2.1 Ndcsf_SessionEvent
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2.1.1 General
| Service description: This service enables the consumer to subscribe with the supported events by DCSF and get notified when the event is detected.
The following operations are available for this service:
- Subscribing and unsubscribing with events supported by DCSF.
- Notifying after event is detected to consumers, e.g. NEF, AF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2.1.2 Ndcsf_SessionEvent_Subscribe
| Service operation name: Ndcsf_SessionEvent_Subscribe
Description: This service operation enables consumers to subscribe to the event of P2A or P2A2P ADC session establishment.
Inputs, Required: Notification Target address, Event ID
Only one Event ID is currently defined: successful download of specific application by UE.
Inputs, Optional: Target list of User IDs (IMPUs), list of Application ID
When no IMPU is given, the subscription is assumed to be non-UE specific and thus to apply to Any UE (otherwise an explicit Any UE target indication may be defined).
Outputs, Required: Result, Subscription correlation ID when the subscription is accepted.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2.1.3 Ndcsf_SessionEvent_Unsubscribe
| Service operation name: Ndcsf_SessionEvent_Unsubscribe
Description: This service operation enables consumers to unsubscribe from the event.
Inputs, Required: Subscription correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.2.1.2.1.4 Ndcsf_SessionEvent_Notify
| Service operation name: Ndcsf_SessionEvent_Notify
Description: This service operation enables the DCSF to notify the NF subscriber about the subscribed event.
Inputs, Required: Session ID, DC Application ID.
Inputs, Optional: Calling party and called party ID.
Outputs, Required: Result.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.3.1 DCSF instance registration in HSS
| Figure 6.9.3.1-1depicts a signalling flow diagram for an DCSF registering in HSS the DCSF instance assigned to a registering UE.
Figure 6.9.3.1-1: DCSF Instance Registration in HSS
1. UE performs initial IMS Registration.
2. S-CSCF performs third party Registration with the IMS AS instance assigned to the registering UE.
3. IMS AS performs third party Registration with the DCSF instance assigned to the registering UE. This is over http and not SIP.
4. DCSF assigned to the UE/IMPU registers in HSS using Nhss_ImsUECM_Registration service operation or using Sh interface.
NOTE: Figure 6.9.3.1-1 shows only SBA services. Corresponding Sh procedure is not included in the Figure.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.3.2 DCSF address discovery by AF
| Figure 6.9.3.2-1 depicts a signalling flow diagram for discovering DCSF address by AF.
.
Figure 6.9.3.2-1: DCSF address discovery by DC AS
1. DCSF address is already registered as per Fig 6.9.3.1-1 solution.
2. AF discovers DCSF by sending Nnef_ImsUECM_DcscfInfoGet service operation to NEF.
3. NEF discovers DCSF by sending Nhss_ImsUECM_DcscfInfoGet service operation to HSS
4. HSS provides DCSF address in Nhss_ImsUECM_DcscfInfoGet response service operation to NEF.
5. NEF provides DCSF address in Nnef_ImsUECM_DcscfInfoGet response service operation to AF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.3.3 Subscription for IMS DC events supported by DCSF
| Figure 6.9.3.3-1depicts a signalling flow diagram for subscriptions for IMS DC events supported by DCSF.
Figure 6.9.3.2-1: DCSF address discovery by DC AS
1. AF subscribes with NEF using Nnef_ImsEE_Subscribe request.
2. NEF provides Nnef_ImsEE_Subscribe Response.
3. Based on the requested events, NEF decides that the request need to be sent to DCSF. It is assumed that NEF has discovered DCSF based on clause 6.9.2. NEF then sends the Ndcsf_ImsEE_Subscribe request with IMPU and Application ID, event ID as input.
4. DCSF provides Ndcsf_ImsEE_Subscribe Response.
5. DCSF detected that the application which was subscribed by NEF has been downloaded by the UE.
4. DCSF sends Ndcsf_ImsEE_Notify to NEF.
7. NEF sends Nnef_ImsEE_Notify to AF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.9.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
AF/NEF:
- subscribing with DCSF for specific application download by UE event and get notified when the event is detected by DCSF.
- subscribing with HSS to discover the DCSF address.
DCSF:
- receiving third party registration from IMS AS.
- registering DCSF address in HSS.
- receiving subscription for specific successful application download event from NEF or AF and notifying when UE successfully downloads the application.
HSS:
- receiving subscription from AF/NEF for discovering DCSF address.
- notify with DCSF address once DCSF register its address to HSS.
IMS AS:
- IMS AS does third party registration with DCSF over http (not SIP).
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10 Solution #10: DC3/DC4 Enhancement to Support Subscription, Notification and Instruction for P2A and P2A2P DC establishment
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.0 High-level solution Principles
| This solution addresses Key Issue #3: Supporting dynamic configuration of MDC2 endpoints. This solution enhances the current P2A and P2A2P ADC establishment procedure defined in clauses AC.7.2.2 and AC.7.2.3 of TS 23.228 [2].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.1 Description
| This solution requires the DC AS to subscribe to the call events from DCSF so that DC AS can give media instruction after receiving the notification from DCSF. This solution defines two services to enable DC AS to subscribe to the DCSF and to instruct DCSF.
This solution also enhances and unifies the timing of notifying DC AS in the current P2A and P2A2P ADC establishment procedure defined in clauses AC.7.2.2 and AC.7.2.3 of TS 23.228 [2].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.1 General
| The following table shows the DCSF Services defined.
Table 6.10.2-1: NF services provided by the DCSF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Subscribe
Subscribe/Notify
NEF, DC AS
Ndcsf_EventExposure
Unsubscribe
Subscribe/Notify
NEF, DC AS
Notify
Subscribe/Notify
NEF, DC AS
Ndcsf_MediaControl
MediaInstuction
Request/Response
NEF, DC AS
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.2 Ndcsf_EventExposure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.2.1 General
| Service description: This service enables the consumer to subscribe and to be notified when the given event is detected.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.2.2 Ndcsf_EventExposure_Subscribe
| Service operation name: Ndcsf_EventExposure_Subscribe
Description: This service operation enables consumers to subscribe to specific events.
Inputs, Required: Notification Target address, Event ID
Three Event ID is currently defined: application data channel establishment request, application data channel establishment success, application data channel establishment failure.
Inputs, Optional: Target list of User IDs (IMPUs), list of Application binding information
When no IMPU is given, the notification will be sent to the consumer for all users.
When no application binding information is given, the notification will be sent to the consumer for all IMS DC applications.
Outputs, Required: Result indication, Subscription correlation ID when the subscription is accepted.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.2.3 Ndcsf_EventExposure_Unsubscribe
| Service operation name: Ndcsf_EventExposure_Unsubscribe
Description: This service operation enables consumers to unsubscribe from the subscription.
Inputs, Required: Subscription correlation ID.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.2.4 Ndcsf_EventExposure_Notify
| Service operation name: Ndcsf_EventExposure_Notify
Description: This service operation enables the DCSF to notify the consumer about the subscribed event.
Inputs, Required: Session ID, Event ID
Inputs, Optional: User IDs of calling party and called party, application binding information.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.3 Ndcsf_MediaControl
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.3.1 General
| Service description: This service enables the consumer to give media instruction to DCSF. In this release, the instruction is only used to establish P2A and P2A2P data channel.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.2.3.2 Ndcsf_MediaControl_MediaInstruction
| Service operation name: Ndcsf_MediaControl_MediaInstruction
Description: This service operation enables the consumer to provide instruction to the DCSF.
Inputs, Required: Session ID, Media information of MDC2 interface.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.3.1 Service Subscription Procedure
|
Figure 6.10.3.1-1: service subscription procedure
1. DC AS sends Ndcsf_EventExposure_Subscribe to DCSF to subscribe to specific ADC establishment event. The DC AS can find the DCSF using NRF or configuration.
If the subscription request is non-subscriber specific, the DC AS will send this request to all DCSF. If the subscription request is subscriber specific, the DC AS will send this request to any DCSF. The DCSF will write the subscription request in the DCSF repository data in the HSS using Nhss_imsSDM_Update service, which will be retrieved by DCSF during the data channel establishment procedure.
2. DCSF sends 200 OK.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.3.2 P2A Application Data Channel Establishment Procedure
| Figure 6.10.3.2-1 depicts the P2A application data channel establishment procedure.
Figure 6.10.3.2-1: P2A ADC establishment procedure
1. Steps 0-3 of clause AC.7.2.2 of TS 23.228 [2] applies.
2. The DCSF receives notification from IMS AS and detects this is an application data channel establishment request. The DCSF decides to notify DC AS based on the subscription from DC AS.
3. The DCSF sends Ndcsf_EventExposure_Notify to the DC AS. This step is to notify the DC AS that an application data channel establishment request is received.
4. The DC AS sends 200 OK indicating it receives the notification.
5. The DC AS sends Ndcsf_MediaControl_MediaInstruction to instruct the DCSF about the MDC2 related media information.
6. The DCSF sends 200 OK indicating it receives the instruction.
NOTE: It is up to operator's configuration and implementation that how the DCSF knows that the DC AS will send instruction to the DCSF. A possible implementation is that the DCSF will continue the following steps after a fix timer is expired.
7. Steps 11-20 of clause AC.7.2.2 of TS 23.228 [2] applies.
8. The DCSF sends Ndcsf_EventExposure_Notify to the DC AS. This step is to notify the DC AS that the application data channel establishment success event. The DCSF will also forward MDC2 related information from the MF to the DC AS.
9. The DC AS sends 200 OK indicating it receives the notification.
10. Steps 21-27 of clause AC.7.2.2 of TS 23.228 [2] applies.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.3.3 P2A2P Application Data Channel Establishment Procedure
| Figure 6.10.3.3-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application use case.
Figure 6.10.3.3-1: P2A2P Application Data Channel Establishment Procedure.
1. Steps 0-3 of clause AC.7.2.3 of TS 23.228 [2] applies.
2. The DCSF receives notification from IMS AS and detects this is an application data channel establishment request. The DCSF decides to notify DC AS based on the subscription from DC AS.
3. The DCSF sends Ndcsf_EventExposure_Notify to the DC AS. This step is to notify the DC AS that an application data channel establishment request is received.
4. The DC AS sends 200 OK indicating it receives the notification.
5. The DC AS detects that this is a P2A2P ADC so it allocates two sets of MDC2 endpoints. The DC AS sends Ndcsf_MediaControl_MediaInstruction to instruct the DCSF about the MDC2 related media information.
6. The DCSF sends 200 OK indicating it receives the instruction.
NOTE: It is up to operator's configuration and implementation that how the DCSF knows that the DC AS will send instruction to the DCSF. A possible implementation is that the DCSF will continue the following steps after a fix timer is expired.
7. Steps 6-8 of clause AC.7.2.3 of TS 23.228 [2] applies. The DCSF shall send all the MDC2 media related information received from the DC AS to the MF. In this case, the MF receives two sets of MDC2 endpoints.
8. Steps 10-18 of clause AC.7.2.3 of TS 23.228 [2] applies. The DCSF will instruct the MF via IMS AS to update the media related information after receiving SDP answer from the terminating side.
9. The DCSF sends Ndcsf_EventExposure_Notify to the DC AS. This step is to notify the DC AS that the application data channel establishment success event. The DCSF will also forward MDC2 related information from the MF to the DC AS. In the P2A2P scenario, two sets of endpoint information shall be sent to the DC AS.
10. The DC AS sends 200 OK indicating it receives the notification.
11. Steps 19-26 of clause AC.7.2.3 of TS 23.228 [2] applies.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.10.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DC AS:
- sending subscription request to the DCSF.
- receiving notification from the DCSF which may include MDC2 related media information.
- sending DC AS side MDC2 related media information to DCSF.
DCSF:
- receiving subscription from DC AS.
- writing subscription information of subscriber-specific subscription request in the DCSF repository data in the HSS.
- notifying the session events to the DC AS.
- sending MF side MDC2 related media information to DC AS.
- receiving DC AS side MDC2 related media information from DC AS.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11 Solution #11: DC3/DC4 based on DCSF services
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.0 High-level solution principles
| This solution addresses Key Issue #3: Supporting dynamic configuration of MDC2 endpoints.
The DC AS can subscribe to events related with MDC2 channels, targeting specific UE(s) or any targeting any UE. The subscription can be either implicitly or explicitly established. For an implicitly establishment, the subscription is configured at the DCSF. For an explicitly established, the subscription request is delivered to IMS AS by following the procedure defined in clause AD.3.2 of TS 23.228 [2] or in clause AD.3.3 of TS 23.228 [2]. Once, the UE(s) initiates a P2A/P2A2P ADC establishment, the IMS AS selects a DCSF instance for handling the ADC as defined in clauses AC.7.2.2 and AC.7.2.3 of TS 23.228 [2] and forwards the DC AS subscription information to the selected DCSF instance. The subscription at DCSF lasts only as long as the corresponding end user session.
The solution does not assume a 1-1 mapping between IMS AS and DCSF.
Upon receipt of a P2A/P2A2P ADC establishment request meeting the subscription filter conditions, the DCSF invokes a new Ndcsf_SessionEvent_Notify to notify the DC AS of the event that MDC2 needs to be established. This notification includes MF-side information required for MDC2 configuration, a Resource URL where the DCSF expects further instructions from the DC AS, and security information enabling security between UE/MF and DC AS.
Based on the received notification from the DCSF, the DC AS derives the DC AS-side MDC2 configuration information, DC AS's certificate fingerprint for security between UE/MF and DC AS, and optionally QoS requirement for the DC application. and the DC AS transfers this information to the DCSF via a new Ndcsf_ADCControl_Create operation towards the Resource URL received in Ndcsf_SessionEvent_Notify.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.1 Description
| This solution specifies the DCSF services exposed over the DC3/DC4 interface to support UE-initiated P2A and P2A2P ADC establishment. Specifically, the following services are defined: Ndcsf_SessionEvent and Ndcsf_ADCControl. The associated service parameters and corresponding procedures are defined in clause 6.11.2.
The DC AS subscribes to (or is subscribed to) events notifications related with MDC2 channel establishment need . Such an event subscription can be explicitly initiated by the DC AS or implicitly configured in the DCSF. Events can be UE related (i.e. targeting specific UE(s)) or UE unrelated (i.e. targeting any UE) and associated with filter conditions such as P2A/P2A2P ADC associated with specific applications.
Upon receipt of a P2A or P2A2P ADC establishment request meeting the subscription filter conditions, the DCSF invokes Ndcsf_SessionEvent_Notify to notify the DC AS of the MDC2 channel establishment event. This notification includes MF-side information and security information (e.g. UE's certificate fingerprint) for security between UE/MF and DC AS required for MDC2 configuration. Based on the notification received, the DC AS derives the DC AS-side MDC2 configuration information and security information (e.g. DC AS's certificate fingerprint) for security between UE/MF and DC AS, optionally QoS requirement for the DC application. DCAS transfers this information to the DCSF via the Ndcsf_ADCControl_Create service operation. The DCSF subsequently proceeds with the MDC2 configuration based on the information received from the DC AS.
This enhancement to the DC3/DC4 interface is crucial for ensuring consistent and up-to-date MDC2 media resources between the DCSF and the DC AS. The DC AS and the MF may dynamically deploy/insert MDC2 terminations and thus use the dynamically determined IP address. The DC port and/or DC SCTP port may be dynamically associated to the session by the MF and/or the DC AS. Furthermore, the network (DCSF) may need to provide the DC AS with the UE certificate fingerprint received from the UE over IMS signalling.
The current P2A/P2A2P data channel procedures lack a mechanism for MDC2 media resource negotiation, leading to potential inconsistencies of MDC2 media resource between the two MDC2 endpoints. This proposed enhancement, by enabling the MDC2 media negotiation and dynamic configuration, significantly improves the robustness and flexibility of these procedures, preventing failures due to outdated or missing MDC2 media resource information.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.1 General
| The following table shows the DCSF Services and DCSF Service Operations.
Table 6.11.2-1: NF services provided by the DCSF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Subscribe
Subscribe/Notify
IMS AS
Ndcsf_SessionEvent
Unsubscribe
Subscribe/Notify
IMS AS
Notify
Subscribe/Notify
NEF, Trusted AF/DC AS
Create
Request/Response
NEF, Trusted AF/DC AS
Ndcsf_ADCControl
Update
Request/Response
NEF, Trusted AF/DC AS
Delete
Request/Response
NEF, Trusted AF/DC AS
NOTE: The security information transferred between DCSF and DC AS for security between UE/MF and DC AS will be aligned with SA WG3.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.2 Ndcsf_SessionEvent
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.2.1 General
| Service description: This service enables the consumer to subscribe to and to be notified about events related with MDC2 channels.
The following operations are available for this service:
- Subscribing and unsubscribing to receive event related with MDC2 channels.
- Notifying the event to consumers, e.g. NEF, trusted DC AS.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.2.2 Ndcsf_SessionEvent_Subscribe
| Service operation name: Ndcsf_SessionEvent_Subscribe
Description: This service operation enables consumers to subscribe to the event related with MDC2 channels (in this release only event is defined “the establishment of a MDC2 channel is needed”).
Inputs, Required: Notification Target address, Event ID
NOTE: The Notification Target address contains the Notification target address of the NEF or of the subscribing trusted DC AS.
Only one Event Id is currently defined: establishment of a MDC2 channel is needed.
Inputs, Optional: Target list of User IDs (IMPUs), list of Application binding information
When no IMPU is given, the subscription is assumed to be non-UE specific and thus to apply to Any UE (as an alternative, to be decided by stage 3, an explicit Any UE target indication may be defined).
Outputs, Required: Result, Subscription correlation ID when the subscription is accepted.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.2.3 Ndcsf_SessionEvent_Unsubscribe
| Service operation name: Ndcsf_SessionEvent_Unsubscribe
Description: This service operation enables consumers to unsubscribe from an event .
Inputs, Required: Subscription correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.2.4 Ndcsf_SessionEvent_Notify
| Service operation name: Ndcsf_SessionEvent_Notify
Description: This service operation enables the DCSF to notify the NF subscriber about the subscribed event.
Inputs, Required: Session ID, MF-side MDC2 endpoint information (e.g. IP address, port number), Resource URL(for any Ndcsf_ADCControl operation that would correspond to the same session), DC application ID
One or two MF-side MDC2 addressing information are provided depending on whether the session is established in P2A or P2A2P mode.
Inputs, Optional: Calling party and called party IDs, application ID, security Setup if UE initiates the DTLS negotiation, certificate fingerprint of UE for security between UE/MF and DC AS in case MDC2 is in "UDP/DTLS/SCTP", "TCP/TLS" or "SCTP/DTLS" mode.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.3 Ndcsf_ADCControl
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.3.1 General
| Service description: This service enables the consumer to create, update or terminate an ADC.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.3.2 Ndcsf_ADCControl_Create
| Service operation name: Ndcsf_ADCControl_Create
Description: This service operation enables the consumer to create information used by the DCSF for ADC establishment in an IMS session.
Inputs, Required: Session ID, DC AS-side MDC2 endpoint information (e.g. IP address, port number),.
One or two MF-side MDC2 addressing information are provided depending on whether the session is established in P2A or P2A2P mode.
Inputs, Optional: securitySetup if DC AS initiates the DTLS negotiation, certificate fingerprint of DC AS for security between UE/MF and DC AS in case MDC2 is in "UDP/DTLS/SCTP", "TCP/TLS" or "SCTP/DTLS" mode, QoS requirement for the DC application.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.3.4 Ndcsf_ADCControl_Delete
| Service operation name: Ndcsf_ADCControl_Delete
Description: This service operation enables the consumer to provide information used by the DCSF for ADC termination in an IMS session.
Inputs, Required: Session ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.2.3.4 Nimsas_MediaControl_MediaInstruction
| Nimsas_MediaControl_MediaInstruction as defined in clause AA.2.4.3.2 of TS 23.228 [2] is updated to add optional QoS information in the Media instruction.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.3.1 Person-to-Application (P2A) Application Data Channel Setup
| Figure 6.11.3.1-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application use case.
Figure 6.11.3.1-1: P2A ADC establishment with a trusted DC AS
0. A subscription of the DC AS about the need for establishment of a MDC2 channel is created; this subscription is either implicitly configured at the DCSF (e.g. based on the DC Application), or explicitly provided to the IMS AS following the exposure framework defined in Annex AD of TS 23.228 [2]
1. IMS session and BDC are established. The IMS AS selects a DCSF as specified in Figure AC.7.1-1 step 2 of TS 23.228 [2]
2-9. UE#1 requests the establishment of P2A ADC establishment. The IMS AS forwards the DC AS subscription request to the selected DCSF instance as part of a modified step 3 of Figure AC.7.2.1-1 of TS 23.228 [2]: when the IMS AS notifies the DCSF of the session establishment event by sending Nimsas_SessionEventControl_Notify (SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, etc.), the IMS AS provides the DC AS subscription request to the DCSF. The DCSF determines the DC control policy and indicates the IMS AS to request MF for reserving the originating media resources.
NOTE 1: The IMS AS does not need to know whether the DC is requested for P2A ADC establishment. It sends the subscription via Nimsas_SessionEventControl_Notify and it is up to DCSF to determine whether the subscription applies (as the DC is requested for P2A ADC establishment)
10. The DCSF notifies DC AS about the need to establish a MDC2 channel (indicating the session is established in P2A mode) using Ndcsf_SessionEvent_Notify message. The message includes calling and called parting id, application id, session id, MF-side MDC2 media resource info, Resource URL to be used by DC AS to send subsequent ADC Control message and the certificate fingerprint of UE. The DC AS responds to (acknowledges) the notification message.
11. The DCSF waits for ADC control instruction (Ndcsf_ADCControl_Create). If such instructions are not provided then DCSF has the ADC establishment procedure aborted (Nimsas_MediaControl_MediaInstruction).
12. DC AS allocates DC AS-side MDC2 media resource for this session. DC AS sends Ndcsf_ADCControl_Create message with the allocated DC AS-side MDC2 media resource information. The message includes session id, DC AS-side MDC2 media resource info and may include the certificate fingerprint of DC AS and possibly QoS requirement for the DC application.
NOTE 2: Work on the handling of security information like certificate fingerprints is to be co-ordinated with SA WG3.
13. The DCSF sends response of Ndcsf_ADCControl_Create to DC AS.
14-17. The DCSF updates the media resources in the MF via IMS AS, based on the received the DC AS-side MDC2 media resources information and the received QoS requirement. This follows already specified interactions (steps 11 to 14 of Figure AC.7.2.2-1 of TS 23.228 [2]) adding QoS requirements to Nimsas_MediaControl_MediaInstruction request if QoS requirements have been received in step 12. Then, the IMS AS sends response to DCSF.
18-29. IMS AS performs SDP negotiation with terminating network. With a successful SDP negotiation, the application data channel is established. This follows already specified interactions with the addition that the IMS AS when new QoS requirements are provided in Nimsas_MediaControl_MediaInstruction provides them in sip/sdp signalling towards the UEs.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.3.2 Person-to-Application-to-Person (P2A2P) Procedure
| Figure 6.11.3.2-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application to person use case.
Figure 6.11.3.2-1: P2A2P ADC establishment with a DC AS
0. As in step 0 of Figure 6.11.3.1-1.
1. As in step 1 of Figure 6.11.3.1-1.
2-9. UE#1 requests the establishment of P2A2P ADC establishment. The IMS AS forwards the DC AS subscription request to the selected DCSF instance: when the IMS AS notifies the DCSF of the session establishment event by sending Nimsas_SessionEventControl_Notify (SessionEstablishmentRequestEvent, Session ID, Calling ID, Called ID, etc…), the IMS AS provides the DC AS subscription request to the DCSF.
NOTE 1: The IMS AS does not need to know whether the DC is requested for P2A2P ADC establishment. It sends the subscription via Nimsas_SessionEventControl_Notify and it is up to DCSF to determine whether the subscription applies (as the DC is requested for P2A2P ADC establishment).
The DCSF determines the DC control policy and indicates the IMS AS to request MF for reserving the originating and terminating media resources.
10. DCSF notifies DC AS about the session establishment (indicating the session is established in P2A2P mode) using Ndcsf_SessionEvent_Notify message. The message includes calling and called parting id, application id, session id, MF-side MDC2 media resource info, Resource URL used by DC AS to send subsequent ADC Control message and the certificate fingerprint of UE. DC AS responds to (acknowledges) the notification message.
11. DCSF waits for ADC control instructions (Ndcsf_ADCControl_Create). If such instructions are not provided then DCSF has the ADC establishment procedure aborted (Nimsas_MediaControl_MediaInstruction).
12. DC AS allocates DC AS-side MDC2 media resource for this session. DC AS sends Ndcsf_ADCControl_Create message to the DCSF with the allocated DC AS-side MDC2 media resource information. The message includes session id, DC AS-side MDC2 media resource info and may include the certificate fingerprint of DC AS and possibly QoS requirement for the DC application.
NOTE 2: Handling of security information like certificate fingerprints is to be co-ordinated with SA WG3.
13. The DCSF sends response of Ndcsf_ADCControl_Create to DC AS.
14-21. IMS AS performs SDP negotiation with terminating network. And the IMS AS notifies the DCSF about the successful result of the SDP negotiation. This follows already specified interactions
22. DCSF updates the media resources in the MF via IMS AS, based on the received the DC AS-side MDC2 media resources information, the received media resource information of the terminating network, and the received QoS requirement. Then, the IMS AS sends response to DCSF. This follows existing procedures e.g. Steps 8 of Figure AC.7.2.3-1 of TS 23.228 [2] adding QoS requirements to Nimsas_MediaControl_MediaInstruction request if QoS requirements have been received in step 12.
23-29. IMS AS continues performing SDP negotiation with the originating network. With a successful SDP negotiation, the application data channel is established. This follows already specified interactions with the addition that the IMS AS when new QoS requirements are provided in Nimsas_MediaControl_MediaInstruction provides them in sip/sdp signalling towards the UEs.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.11.4 Impacts on services, entities and interfaces
| The solution has the following impacts:
DC AS:
- Subscribing to the event of "establishment of a MDC2 channel is needed" and receiving corresponding notifications containing MF-side information for MDC2 configuration.
- Sending DC AS-side information for MDC2 configuration in Ndcsf_ADCControl_Create that may include QoS requirement for the DC application.
- Sending/receiving certificate fingerprints for security between UE/MF and DC AS.
DCSF:
- Receiving subscription to the "event of establishment of a MDC2 channel is needed" and sending corresponding notification, containing MF-side information for MDC2 configuration.
- Receiving DC AS-side information for MDC2 configuration.
- Sending/receiving certificate fingerprints for security between UE/MF and DC AS.
- Receiving QoS requirement for the DC application.
IMS AS:
- This solution assumes the definition of an IMS AS event requiring the IMS AS is to forward to the selected DCSF.
- Sending subscription request to the DCSF instance.
- Using optional QoS requirements added to Nimsas_MediaControl_MediaInstruction.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12 Solution #12: Support dynamic configuration of MDC2 endpoints with new DCSF services
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.0 High-level solution Principles
| This solution addresses KI#3: Supporting dynamic configuration of MDC2 endpoints.
This solution takes the existing Rel-18 procedures of P2A and P2A2P DC establishment as the basis and updates the existing steps between DCSF and DC AS by defining new service of DCSF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.1 Description
| This solution defines a new service of DCSF which is used to request to establish, update or delete a MDC2 connection. This service exchanges the MDC2 media points information on MF and DC AS to each other. The connection ID is allocated by DCSF and is used to correlate the MDC2 connection.
The interaction between DCSF and DC AS is designed as event exposure of MDC2 connection request to exchange the MDC2 media endpoint information. By this principle, the DC AS from third party customer is not required to provide any service when using IMS DC services from the operator. Accordingly the DCSF services use Subscription/Notification mode. In this solution implicit subscription is used based on the following consideration:
- If explicit subscription is used, it is very difficult to ensure the DCSF selected by the DC AS to subscribe is the same DCSF selected by the IMS AS during DC establishment, especially when multiple DCSFs are deployed in a pool.
- Explicit subscription saves cost interaction.
The solution supports both P2A and P2A2P DC management. When P2A DC is established, the media information of one pair of MDC2 media points between MF and DC AS is exchanged. When P2A2P DC is established, the media information of two pairs of MDC2 media points for originating side and terminating side between MF and DC AS is exchanged.
This solution uses event notification and notification response messages to exchange MDC2 media endpoints information. The reliable transmission of the messages is ensured by the transportation layer, e.g. TCP or SCTP.
To support implicit subscription and notification, the solution also clarifies that the DCSF selects the correct DC AS and get the address of the selected DC AS URL based on binding information which indicates which DC AS is serving the application. The mapping of the app id and the DC AS URL is locally configured on DCSF or is retrieved from the application data in the HSS. This mechanism has been specified in Rel-19 to enable the DCSF to fetch Avatar ID list from a DC AS (see clause AC.11.1 of TS 23.228 [2]).
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.2 Procedures
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.2.1 P2A DC procedure
| This procedure depicts the procedure of UE initiated P2A DC establishment, P2A DC modification and P2A DC deletion, which reuses the P2A DC establishment procedure in clause AC.7.2.2 of TS 23.228 [2] as the basis and updates original steps 9 and 10 to clarify the interaction between DCSF and DC AS.
Figure 6.12.2.1-1: Procedure of P2A DC establishment
The steps in the procedure are as follows:
Steps 0-8 are the same with steps 0-8 in clause AC.7.2.2 of TS 23.228 [2];
9. The DCSF selects the DC AS serving this session based on the binding information of this P2A DC. The DCSF gets the DC AS URL of the selected DC AS by local configuration or retrieves it from DCSF service specific data stored in HSS.
10. The DCSF invokes Ndcsf_MDC2Connection_Create service operation as defined in clause 6.12.3.2 to request the selected DC AS to establish MDC2 connection with the MF for the P2A DC. The service operation includes the MDC2 media endpoint information on the MF.
11. The DC AS responds to Ndcsf_MDC2Connection_Create service operation with connection ID and its MDC2 media endpoint information for the MDC2 connection.
12-28. The same with steps 11-27 in clause AC.7.2.2 of TS 23.228 [2].
29-30. The UE initiates IMS session modification to update the established P2A DC. The MDC2 media endpoint on the MF is updated and the information is returned to the DCSF.
31. The DCSF invokes Ndcsf_MDC2Connection_Update service operation as defined in clause 6.12.1.3.3 to notify the DC AS the media endpoint on the MF for the established P2A DC is updated. The service operation includes the connection ID and the updated MDC2 media endpoint information on the MF.
32. The DC AS updates its media endpoint accordingly and responds to Ndcsf_MDC2Connection_Update service operation with updated MDC2 media endpoint information.
33-34. The IMS session is updated.
35. The UE releases the P2A DC or the whole IMS session.
36-37. The DCSF notifies the DC AS the P2A DC is deleted. The DC AS removes its media resource of the P2A DC.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.2.2 P2A2P DC procedure
| This procedure depicts the procedure of UE initiated P2A2P DC establishment, P2A2P DC modification and P2A2P DC deletion, which reuses the P2A2P DC establishment procedure in clause AC.7.2.3 of TS 23.228 [2] as the basis and updates original step 9 and 10 to clarify the interaction between DCSF and DC AS.
Figure 6.12.2.1-1 Procedure of P2A2P DC establishment
The steps in the procedure are as follows:
Steps 0-8 are the same with steps 0-8 in clause AC.7.2.3 of TS 23.228 [2];
9. The DCSF determines to establish P2A2P DC and invokes Ndcsf_MDC2Connection_Create service operation to request the DC AS to establish MDC2 connection with the MF for the P2A2P DC. The service operation includes the MDC2 media endpoint information for originating side and terminating side on the MF.
10. The DC AS responds to Ndcsf_MDC2Connection_Create service operation with connection ID and its MDC2 media endpoint information for originating side and terminating side.
11-26. The same with steps 11-27 in clause AC.7.2.3 of TS 23.228 [2].
27-28. The UE initiates IMS session modification to update the established P2A2P DC. The MDC2 media endpoint on the MF is updated and the MDC2 information of originating side is returned to the DCSF.
29. The DCSF invokes Ndcsf_MDC2Connection_Update service operation as defined in clause 6.12.1.3.3 to notify the DC AS the media endpoint for originating side on the MF for the established P2A2P DC is updated. The service operation includes the connection ID and the updated MDC2 media endpoint information on the MF.
30. The DC AS updates its media endpoint accordingly and responds to Ndcsf_MDC2Connection_Update service operation with updated MDC2 media endpoint information.
31. The IMS session is updated.
32. The UE releases the P2A DC or the whole IMS session.
33-34. The DCSF notifies the DC AS the P2A DC is deleted. The DC AS removes its media resource of the P2A DC.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3 DCSF Services
| This solution defines DCSF services to support interaction between DCSF and DC AS for establishing the P2A or P2A2P DC.
Table 6.12.3.1-1: DCSF services
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Ndcsf_MDC2ConnectionRequest
CreateNotify
Subscription/Notification
DC AS
UpdateNotify
Subscription/Notification
DC AS
DeleteNotify
Subscription/Notification
DC AS
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3.1 Ndcsf_MDC2Connection
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3.1.1 General
| Service description: This service enables the consumer to be requested to establish, update or delete MDC2 connection towards the MDC2 endpoint on the MF.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3.1.2 Ndcsf_MDC2Connection_CreateNotify service operation
| Service operation name: Ndcsf_MDC2Connection_CreateNotify
Description: This service operation enables DCSF to notify the consumer of the event of establishing a MDC2 connection with the MF towards the MDC2 endpoint on the MF and responds with its own MDC2 endpoint information on the MF.
Inputs, Required: Session ID, Connection ID, DC type, remote MDC2 media endpoint information.
Session ID is the identity of the IMS session to which the MDC2 connection belongs.
Connection ID is the identity of the MDC2 connection. It is allocated by the DCSF.
DC type indicates the type of the established DC, i.e. P2A, P2A2P.Remote MDC2 media endpoint information contains the following:
- Endpoint type: Originating side, Terminating side.
- The IP address and port of the MDC2 media endpoint on MF.
NOTE: If the DC is P2A DC, only media endpoint information of originating side is included.
Inputs, Optional: Calling ID, Called ID, Session case, Event initiator.
Calling ID is the public identity of the calling IMS subscriber. Called ID is the public identity of the called IMS Subscriber. The Calling ID and Called ID can be used by DC AS to decide whether a P2A2P DC should be further established.
Outputs, Required: Result indication.
Outputs, Optional: Local MDC2 media endpoint information if the result is successful.
Local MDC2 media endpoint information contains the following:
- Endpoint type: Originating side, Terminating side.
- The IP address and port of the MDC2 media endpoint on MF.
NOTE: If the DC is P2A DC, only media endpoint information of originating side is included.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3.1.3 Ndcsf_MDC2Connection_UpdateNotify service operation
| Service operation name: Ndcsf_MDC2Connection_UpdateNotify
Description: This service operation enables DCSF to notify the consumer to the event of updating an existing MDC2 connection on the MF.
Inputs, Required: Session ID, Connection ID, updated remote MDC2 media endpoint information.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: Local MDC2 media endpoint information if the result is successful.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.3.1.4 Ndcsf_MDC2Connection_DeleteNotify service operation
| Service operation name: Ndcsf_MDC2Connection_DeleteNotify
Description: This service operation enables DCSF to notify the consumer to the event of deleting an existing MDC2 connection on the MF.
Inputs, Required: Session ID, Connection ID.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.12.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DCSF:
- Supports to select the DC AS serving the session based on the binding information of this P2A DC.
- supports Ndcsf_MDC2ConnectionRequest service to interact with DC AS to establish, update or delete MDC2 connection for P2A or P2A2P DC.
DC AS:
- supports Ndcsf_MDC2ConnectionRequest service to interact with DCSF to establish, update or delete MDC2 connection for P2A or P2A2P DC.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13 Solution #13: DC3/DC4 enhancements with new media management
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.1 Description
| This solution addresses KI#3.
This solution specifies the DCAS services exposed over the DC3/DC4 interface to support UE-initiated P2A and P2A2P ADC establishment. Specifically, the following new service function is defined: Ndcas_Media_Management. the associated service parameters and corresponding procedures are also defined.
The DC AS provisions the service triggering (triggering information) criteria for establishing P2A/P2A2P ADC at the DCSF using the Nimsas_ImsParameterProvision_Create service operation (see clause AA2.4.6 of TS 23.228 [2], v19.0.0). Such provisioning can be explicitly initiated by the DC AS or implicitly configured per DC AS in the IMS AS and/or in the service document in HSS (Repository data). Triggering can be user specific or user unrelated (i.e. PSI) and associated with filter conditions such as P2A/P2A2P ADC associated with specific applications. Upon receipt of a P2A or P2A2P ADC establishment request meeting the triggering filter conditions, the IMS AS invokes Nimsas_SessionEventControl_Notify to notify the DCSF of a media change request event and the availability of an P2A/P2A2P ADC. This notification includes the SDP information for the P2A/P2A2P ADC representation on the Mb interface. Based on the notification received, the DCSF will request anchoring of media in the MF for the originating MF-side of the MDC2 interface. The DCSF will then provide the originating MF-side of the MDC2 to the DCAS and request the DCAS-side for the MDC2 via the Ndcas_Media_Management_Create service operation. The DCSF will provide the received media information from the DCAS to IMS AS over the Nimsas_mediaControl service with the requested MDC2 configuration based on the information received from the DC AS.
Note that the proposal utilizes the principle that configuration/trigger can be sent to any (not all) IMS AS, according to operator choice and the data will be then stored in HSS over N71 as repository data (using the same mechanisms as defined in clause AF.4 of TS 23.228 [2]) and can subsequently be used by any IMS AS serving specific subscriber or non-subscriber specific triggers.
The use of IMS Nimsas_SessionEventControl_Notify was purposefully done in order to reuse (thus no need for new interfaces in DCSF, etc.). The provisioning paradigm used is a request-resp interface and it is not connected to IMS events (as covered in KI#2) ensuring that all IMS ASs can avail of the data even if not always applicable only to a specific subscriber. These triggers are static in nature and are similar to iFC triggers.
This enhancement to the DC3/DC4 interface is crucial for ensuring a time sensitive and 3GPP SBA principle compliant consistent handling of MDC2 media resources between the DCSF and the DC AS. The DC AS and the MF may dynamically deploy/insert MDC2 terminations and thus use the dynamically determined IP address. The DC port and/or DC SCTP port may be dynamically associated to the session by the MF and/or the DC AS. Furthermore, the network (DCSF) may need to provide the DC AS with the UE certificate fingerprint received from the UE over IMS signalling using the Dcas_Media_Management_Update service operation.
The current P2A/P2A2P data channel procedures lack a 3GPP SBA service self-containment complaint mechanism for MDC2 media resource negotiation, leading to potential inconsistencies of MDC2 media resource between the two MDC2 endpoints. This proposed enhancement, by enabling the MDC2 media negotiation and dynamic configuration, significantly improves the robustness and flexibility of these procedures, preventing failures due to outdated or missing MDC2 media resource information. The DCSF availing of the DC AS offered / provided service, Dcas_Media_Management ensures that it is the resource control entity when interworking with DC AS.
Furthermore, this solution ensures that DC AS can be selected by DCSF (for establishing P2A/P2A2P ADC) on a per session basis without creating long lived dependencies between the entities.
NOTE: This solution identifies changes to existing specifications, these changes are shown using RED text.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2 Service definition
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.