hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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, ... |
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.
Outpu... |
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, Optio... |
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_MDC2Con... |
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 als... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.1 General
| The following table shows the DC AS Services and DC AS Service Operations.
Table 6.13.2-1: NF services provided by the DC AS
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Ndcas_Media_Management
Create
Request/Response
DCSF
Update
Request/Response
DCSF
Delete
Request/Response
... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.2 Ndcas_Media_Management
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.2.1 General
| Service description: This service enables the consumer (DCSF) to create, update or terminate a media resource controlled by the producer (DCAS).
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.2.2 Ndcas_Media_Management_Create
| Service operation name: Ndcas_Media_Management_Create
Description: This service operation enables the consumer to create a media resource (e.g. ADC (P2A, P2A2P) or other media resources like audio/Video. The information is used by the DCAS to create a resource and establish a media resource in an IMS session.
Inputs... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.2.3 Ndcas_Media_Management_Update
| Service operation name: Ndcas_Media_Management_Update
Description: This service operation enables the consumer to update a media resource information used by the DCAS.
Inputs, Required: Session ID, MF-side MDC2 endpoint information (e.g. IP address, port number), destination URL
Inputs, Optional: certificate, finger... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.2.4 Ndcas_Media_Management_Delete
| Service operation name: Ndcas_Media_Management_Delete
Description: This service operation enables the consumer to provide information used by the DCAS for media termination in an IMS session
Inputs, Required: Session ID, mediaInformation, destination URL
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.3 Nimsas_ImsParameterProvision Service API
| 6.13.2.3.1 Type: ImsPpDataEntry
Table 6.13.2.3.1-1 New Parameters for:Table 6.5.6.2.2-1: Definition of type ImsPpDataEntry, TS 29.175 [9]
Attribute name
Data type
P
Cardinality
Description
rcdServerInformation
RcdServerInfo
O
0..1
The RCD server information provisioned to the IMS AS.
triggerinformation
Tr... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.4 Nimsas_SessionEventControl Service API
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.2.4.1 Type: SessionEventNotification
| The parameters that are new are: afInstance, triggerinformation
Table 6.13.2.4.1-1: New Parameters for Table 6.1.6.2.2-1 of TS 29.175 [9]: Definition of type SessionEventNotification
Attribute name
Data type
P
Cardinality
Description
notificationEvent
NotificationEvent
M
1
The NotificationEvent corresponds t... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.3.1 Person-to-Application (P2A) Application Data Channel Setup
| Figure 6.13.3.1-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application use case.
Figure 6.13.3.1-1: P2A ADC establishment with a trusted DC AS
1. The DCAS provisions service triggers using the Nimsas_ImsParameterProvision.
NOTE: The IMS Parameter Provisioning fl... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.3.2 Person-to-Application and Application-to-Person (P2A2P) Procedure
| Figure 6.13.3.2-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application use case.
Figure 6.13.3.2-1: P2A2P ADC establishment with a trusted DC AS
1. The DCAS provisions service triggers using the Nimsas_ImsParameterProvision.
NOTE: The IMS Parameter Provisioning ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.13.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DC AS:
- provisioning service triggers for the UE-initiated P2A/P2A2P ADC establishment;
- receiving MF-side information for MDC2 configuration;
- receiving the certificate fingerprint of UE for end-to-end security between UE and DC AS;
- sending DC AS-side information for M... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14 Solution #14: Dynamic MDC2 endpoint configuration IMS Data Channel
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.0 High-level solution Principles
| This solution addresses Key Issue #3: Supporting dynamic configuration of MDC2 endpoints.
The main principle of this solution for support of dynamic MDC2 endpoint configuration for IMS Data Channel during UE initiated P2A and P2A2P session as follows
- The DC AS shall discover and select the DCSF handling the UE for ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.1 Description
| This solution proposes how the DC AS discovers the DCSF and subscribes to get notification for the UE initiated P2A and P2A2P session and then shares the MDC2 endpoint addresses. This will overcome the existing gaps of the P2A and P2A2P session which does not provide any flexibility in dynamically exchanging MDC2 endpo... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.1 General
| The following tables shows the required service updates in TS 23.502 [8] and TS 23.228 [2].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.2 NEF Service
| The following shows the required NEF service updates in TS 23.502 [8].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.2.1 Service Summary table Update
| The NEF services for IMS Event exposure is already defined in table 5.2.6.1-1 of TS 23.502 [8].
Table 5.2.6.1-1: NF Services provided by the NEF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_ImsEventExposure
Subscribe
Subscribe/Notify
AF, DC AS
Unsubscribe
Subscribe/Notify
A... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.2.2.1 Update to Nnef_ImsEE_Subscribe service operation
| Service operation name: Nnef_ImsEE_Subscribe
Description: The NF consumer (for e.g. AF or DC AS) subscribes for a specific IMS event.
Inputs, Required: Event-ID(s) representing the event of interest, Event Reporting Information as defined in Table 4.15.1-1.
Inputs, Optional: List one or more IMS Public Subscriber id... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2 HSS Service XX Check Numbering XX
| The following shows the required HSS service updates in TS 23.228 [2].
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2.1 Service Summary table Update
| The HSS services for IMS Services provided by an SBI capable HSS are already defined in table AA.2.1.1-1 of TS 23.228 [2].
Table 6.14.2.3.2.1-1: Update to Table AA.2.1.1-1 of TS 23.228 [2]: IMS Services provided by an SBI capable HSS
Service
Service Operations
Operation Semantics
Example Consumer(s)
ImsSubscriber... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2.2 Update to Nhss_ImsUECM_Registration service operation
| The following describes the Nhss_ImsUECM_Registration service operation from clause AA.2.1.2.1 of TS 23.228 [2], and the updates for this solution.
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 ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2.3 Update to Nhss_ImsUECM_Deregistration service operation
| 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.14.2.3.2.4 Nhss_ImsUECM_DcsfInfoGet service operation
| The following describes a new service for IMS UE Context Management used for this solution:
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... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2.5 Nhss_ImsUECM_DcsfUnsubscribe
| The following describes a new service for IMS UE Context Management used for this solution:
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, Requi... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.3.2.6 Nhss_ImsUECM_DcsfNotify
| The following describes a new service for IMS UE Context Management used for this solution:
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: DC... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4 DCSF Service
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.0 General
| The following table shows the new DCSF Services and new DCSF Service Operations added to table AA.2.4.1-1 of TS 23.228 [2].
Table 6.14.2.4.0-1: Updated Table AA.2.4.1-1 from TS 23.228 [2]: NF services provided by the DCSF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Ndcsf_ADCControl_MDC... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.1 Ndcsf_ADCControl_MDC2 service operation
| Service operation name: Ndcsf_ADCControl_MDC2
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.2 Service Description
| This service enables the consumer to create, update or terminate an ADC.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.3 Ndcsf_ADCControl_MDC2Create
| Service operation name: Ndcsf_SessionEvent_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), certificate fingerprint of DC AS... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.4 Ndcsf_ADCControl_MDC2Update
| Service operation name: Ndcsf_ADCControl_Update
Description: This service operation enables the consumer to update information used by the DCSF for ADC updating in an IMS session.
Inputs, Required: Session ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.4.5 Ndcsf_ADCControl_MDC2Delete
| 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.14.2.5 Ndcsf_SessionEvent
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.5.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.14.2.5.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: establishment of a MDC2 channel is needed
In... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.5.3 Ndcsf_SessionEvent_Unsubscribe
| Service operation name: Ndcsf_SessionEvent_Unsubscribe
Description: This service operation enables consumers to unsubscribe from the event of P2A or P2A2P ADC session establishment.
Inputs, Required: Subscription correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.2.5.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.14.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.3.1 DCSF instance registration in HSS
| Figure 6.14.3.1-1depicts a signalling flow diagram for an DCSF registering in HSS the DCSF instance assigned to a registering UE.
Figure 6.14.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 regist... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.3.2 DCSF address discovery by DC AS
| Figure 6.14.3.2-1depicts a signalling flow diagram for discovering DCSF address by DC AS.
.
Figure 6.14.3.2-1: DCSF address discovery by DC AS
1. DCSF address is already registered as for the Figure 6.14.3.1-1.
2. DCAS discovers DCSF by sending Nnef_ImsUECM_DcscfInfoGet service operation to NEF.
3. NEF discovers D... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.14.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DC AS/NEF:
- subscribing the event of UE-initiated P2A/P2A2P ADC establishment.
- receiving notification about the event of UE-initiated P2A/P2A2P ADC establishment.
- receiving MF-side MDC2 endpoint information in the notify message.
- sending DC AS-side MDC2 endpoint infor... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.15 Solution #15: Early Media in Alerting Phase (CRS) Based on DC AS Initiated A2P DC
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.15.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 Ringing Signal (CRS) service which is subscribed by the calling party and it will provide customized content to the called party as an early media during the calling process.
The ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.15.1 Description
| This solution provides a procedure on how to establish an A2P ADC in alerting phase to provide customized DC content to the called party as an early media for CRS.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.15.2 Procedure
| The pre-condition of the following procedure is that the calling UE A has subscribed to the DC based CRS service and the network serving the calling UE A and the called UE B have the early media capability and the UE B has negotiated with the serving network regarding this capability. It assumes that the DC based CRS s... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.15.3 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
UE:
- Supporting ADC establishment in alerting phase for CRS.
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 D... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16 Solution #16: Enhancements to capability exposure framework and IMS AS service to support audio, video capability in addition with DC capability
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.1 High level Solution principles
| This solution addresses KI#2.
Release 19 NG_RTC_Ph2 has specified IMS data channel capability exposure procedures and the related services to enables the AF/AS to request the IMS AS via the NEF to create or release an IMS session with DC media or modify the DC media in a specific IMS session. But in some cases, the NF... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.2 Description
| The solution specifies enhancements to the IMS exposure framework ensuring that exposure capabilities for session establishment, modification and release are media agnostic, i.e. other MMTel media (e.g. audio, video) are also supported in addition to the existing specified DC media.
The solution caters for the additio... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.3 Procedures
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.3.1 DC AS initiated IMS audio session addition with a standalone A2P application data channel
| Figure 6.16.3.1-1 depicts a signalling flow diagram initiated by DC AS for adding MMTel media (e.g. audio) to a standalone Application Data Channel A2P application data channel with UE A. This signalling flow extends the flow described in clause AG.2.2.2 of TS 23.228 [2].
Figure 6.16.3.1-1: Establishment procedure o... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.3.2 Person-to-Application (P2A) MMTel media (audio) and Application Data Channel Setup
| Figure 6.16.3.1-2 depicts a signalling flow diagram for adding an IMS audio session in a in a person to application use case. This signalling flow extends the flow described in clause AC.7.2.2-1 of TS 23.228 [2] where a P2A ADC is setup.
Figure 6.16.3.2-1: Person-to-Application (P2A) audio & application Data Channel... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.1 Nnef_ImsSessionManagement service
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.1.1 General
| The Media Type and Media Parameter set parameter in the following clauses need to be extended to support audio and video media. To be clear, revision mode is used to update the service definition of Nnef_ImsSessionManagement API in the following clauses.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.1.2 Nnef_ImsSessionManagement_Create service operation
| Service operation name: Nnef_ImsSessionManagement_Create
Description: This service enables the consumer NF to create an IMS session with the requested media (e.g. standalone data channel media).
Inputs, Required: Calling ID, Called ID, Media information set.
Calling ID: It is the public identity of calling IMS Subsc... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.2.1.3 Nnef_ImsSessionManagement_Update service operation
| Service operation name: Nnef_ImsSessionManagement_Update
Description: This service operation enables the consumer NF to modify the data channel media in a specific IMS session, such as adding or removing bootstrap data channel(s) or application data channel(s), modify media parameters for the targeted data channel(s).... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.2 Nimsas_ImsSessionManagement Service
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.2.1 General
| The Media Type and Media Parameter set parameter in the following clauses need to be extended to support audio and video media. To be clear, revision mode is used to update the service definition of Nimsas_ImsSessionManagement API in the following clauses.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.2.2 Nimsas_ImsSessionManagement_Create service operation
| Service operation name: Nimsas_ImsSessionManagement_Create
Description: This service enables the consumer NF to create an IMS session with the requested media (e.g. standalone data channel media).
NOTE 1: Only data channel media is supported in this Release.
Inputs, Required: Calling ID, Called ID, Media Information... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.2.3 Nimsas_ImsSessionManagement_Update service operation
| Service operation name: Nimsas_ImsSessionManagement_Update
Description: This service operation enables the consumer NF to modify the media in a specific IMS session, such as adding or removing bootstrap data channel(s) or application data channel(s), modify media parameters for the targeted data channel(s).
Inputs, R... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.3 Nmf_MediaResourceManagement (MRM) service
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.3.1 General
| The Media Type and Media Parameter set parameter in the following clauses need to be extended to support audio and video media. To be clear, revision mode is used to update the service definition of Nmf_MediaResourceManagement API in the following clauses.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.4.3.2 Nmf_MRM_Create service operation
| Service operation name: Nmf_MRM_Create
Description: The consumer NF requests the MF to create a media context including one or multiple media terminations and reserve media resources for anchoring one or multiple media streams of Mb interface in each termination. The consumer NF may also include media application func... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.16.5 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
NEF:
- Enhance Nnef_ImsSessionManagement API to support audio and video media when creating, updating and removing an IMS session.
DC AS:
- sending establishment, modification and release requests for MMTel Audio / Video.
- sending DC AS-side information for MDC2 configurati... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17 Solution #17: DC3/DC4 Enhancement to Support Implicit Subscription and Notification for P2A and P2A2P DC establishment
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.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.17.1 Description
| This solution does not require the DC AS to subscribe to the call events from DCSF. Instead, the DCSF is implicated subscribed to and will notify the DC AS about the ADC establishment request event when receiving the notification from IMS AS. The DC AS will send the its MDC2 endpoint in the response if needed.
This so... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.2 Service definition
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.2.1 General
| The following table shows the DCSF Services defined.
Table 6.17.2-1: NF services provided by the DCSF
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Ndcsf_EventExposure
Notify
Subscribe/Notify
NEF, DC AS
Ndcsf_MediaControl
MediaInstuction
Request/Response
NEF, DC AS
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.2.2 Ndcsf_EventExposure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.2.2.1 General
| Service description: This service enables the consumer to be notified when the given event is detected.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.19.2.2.2 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.
Three Event ID is currently defined: application data channel establishment request, application data channel establishmen... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.2.3 Ndcsf_MediaControl
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.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.17.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.17.3 Procedure
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.3.1 P2A Application Data Channel Establishment Procedure
| Figure 6.17.3.1-1 depicts the P2A application data channel establishment procedure.
Figure 6.17.3.1-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.17.3.2 P2A2P Application Data Channel Establishment Procedure
| Figure 6.17.3.2-1 depicts a signalling flow diagram for establishing an Application Data Channel in a person to application use case.
Figure 6.17.3.2-1: P2A2P Application Data Channel Establishment Procedure
1. Steps 0-3 of TS 23.228 [2] Annex AC.7.2.3 applies.
2. The DCSF receives notification from IMS AS and det... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 6.17.4 Impacts on Services, Entities and Interfaces
| The solution has the following impacts:
DC AS:
- receiving notification from the DCSF which may include MDC2 related media information.
- sending DC AS side MDC2 related media information to DCSF in the notification response.
DCSF:
- notifying the session events to the DC AS.
- sending MF side MDC2 related media ... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 7 Interim agreements
| |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 7.1 Agreed Principles
| 7.1.Y Agreed Principles for KI#Y
Editor's note: This clause will include the principles that are agreed as work progresses for the specific KI#Y. This may be populated directly or e.g. also when a topic in clause 7.2.Y gets resolved and a principle is agreed.
|
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 7.2 Topics for further consideration
| 7.2.Z Topics for further consideration for KI#Z
Editor's note: This clause will include the topics for further consideration as work progresses for the specific KI#Z. Eventually this clause should only contain topics for further consideration that did not result in agreements (i.e. in agreed principle(s) in a clause 7... |
7d12b515375832bdb38ea519e14adcb0 | 23.700-56 | 8 Conclusions
| Editor's note: This clause will capture conclusions for the study.
Where there is consensus, interim agreements (e.g. solution principles descriptions) should be documented in the TR as soon as possible during a study.
These can be documented in the TR as "7.1.Y Agreed Principles for KI#Y" in the "Interim Agreement... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 1 Scope
| The study item aims at investigating how to specify architectural and procedural enhancements to support Short Message Service to Emergency Response Centre in both EPS and 5GS for both roaming and non-roaming UEs, based on the requirements specified in TS 22.101 [6].
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 3 Definitions of terms, symbols and abbreviations
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.