hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.3.2 Procedures
| The procedure of establishing application data channel during alerting phase.
Figure 6.3.3-1: ADC establishment in early media phase
1. UE-A sends an initial SIP INVITE request to the originating IMS AS through P-CSCF and S-CSCF with an initial SDP offer for audio/video and for the bootstrap data channel establishm... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.3.3 Impacts on Services, Entities and Interfaces
| Editor's note: Impacts are FFS.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.4 Solution #4: IMS ADC establishment during alerting phase when initial INVITE does not have BDC offer
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.4.0 High-level solution Principles
| The main principle of this solution for support of application data channel establishment during alerting phase of normal IMS DC session as follows:
- The calling party will receive bootstrap data channel offer from the terminating network during alerting phase.
- The calling party will establish the bootstrap data c... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.4.1 Description
| This clause proposes a solution for supporting application data channel establishment during alerting phase when calling party has not offered bootstrap data channel in the initial INVITE.
In this proposal, one scenario is explained how the called party (e.g. restaurant customer service) network is providing bootstrap... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.4.2 Procedures
| The procedure of establishing application data channel during alerting phase.
Figure 6.4.3-1: ADC establishment in early media phase
0. The terminating user has opted for an interactive ring back tone service from its network. That is, for every incoming SIP INVITE, the network will send an SDP offer for bootstra... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.4.3 Impacts on Services, Entities and Interfaces
| This solution may have the following impacts to existing entities and interfaces:
IMS AS:
- Terminating IMS AS will provide a new offer for IMS bootstrap data channel based on the interactive ringback tone service subscription of called party user.- Terminating IMS AS will notify the session establishment to the sele... |
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 s... |
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 servi... |
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 A... |
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 ... |
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... |
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 Tabl... |
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 Proc... |
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 clau... |
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 a... |
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 T... |
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 suppor... |
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 ev... |
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... |
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 ... |
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) t... |
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 perio... |
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 applic... |
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 ... |
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 purp... |
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... |
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-CSC... |
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 con... |
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 ... |
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: No... |
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, ... |
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 b... |
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 register... |
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 ... |
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... |
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.... |
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 notifyi... |
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, ... |
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 establishm... |
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.
... |
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 t... |
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 D... |
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 an... |
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 inform... |
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 subscriptio... |
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.
T... |
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/No... |
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, truste... |
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 N... |
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 corr... |
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 addressi... |
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 eithe... |
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 o... |
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... |
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 DCS... |
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... |
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.1... |
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
UpdateNotif... |
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.