hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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
DCSF
Editor's note: Whether the service operation type is Subscribe/Notify (and provided by DCSF) or Request/Response (and provided by DC AS) is FFS.
|
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, Required: Session ID, MF-side MDC2 endpoint information (e.g. IP address, port number), certificate fingerprint of DC AS for end-to-end security between UE and DC AS in case MDC2 is in "UDP/DTLS/SCTP", "TCP/TLS" or "SCTP/DTLS" mode, trigger Information.
Inputs, Optional:
Outputs, Required: Result. The result contains the following data elements: session id, DCAS-side MDC2 media resource information, destination URL used by DCSF to send subsequent operations.
Outputs, Optional: None.
|
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, fingerprint of the UE, trigger Information
Outputs, Required: Result.
Outputs, Optional: None.
|
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, Optional: None.
|
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
TriggerInfo
O
0..1
Triggering information to invoke for example dcas media management
Editor’s note: The TriggerInfo data type needs to be defined as common data and is FFS.
NOTE: An additional data type is required (existing defined operation only contains RCD related info) to trigger the service to invoke DCSF (and locate the correct DCAS) for this session.
|
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 to a report on one subscribed event.
sessionId
SessionId
M
1
The session ID is the identity of the IMS session for which the event relates to.
This IE contains the information in the Call-ID header which is the typical header of SIP message.
sessionInfo
SessionInfo
C
0..1
The sessionInfo is the IMS session related information, e.g. the calling and called identity. It shall be contained when the attribute eventType of the notificationEvent is one of the "SESSION_ESTABLISHMENT_REQUEST",
"MEDIA_CHANGE_REQUEST", "EXTERNAL_SESSION_CREATE", "SESSION_ESTABLISHMENT_SUCCESS" (NOTE).
mediaInfoList
map(MediaInfo)
C
1..N
Media info list includes a list of media related information, e.g. media identity, media type and media specifications.
The mediaId attribute within the MediaInfo data type is the key of the map.
It shall be contained when the attribute eventType of the notificationEvent is one of the "SESSION_ESTABLISHMENT_REQUEST", "SESSION_ESTABLISHMENT_PROGRESS",
"SESSION_ESTABLISHMENT_ALERTING",
"SESSION_ESTABLISHMENT_SUCCESS",
"MEDIA_CHANGE_REQUEST",
"MEDIA_CHANGE_SUCCESS",
"MEDIA_CHANGE_FAILURE", or
"MEDIA_CHANGE_CANCEL".
psDataOff
PsDataOffStatus
C
0..1
It indicates the active/inactive status of PS Data Off for the served UE.
It shall be present if the attribute eventType of the notificationEvent is set to one of the following:
- "SESSION_ESTABLISHMENT_REQUEST", when IMS session establishment is invoked;
- "PS_DATA_OFF_STATUS_CHANGE", when the status change of PS Data Off happens without any other changes to the IMS session;
It may be present in other cases if the change of PS Data Off status happens together with other events (e.g. media changes).
mediaInfoSet
array(MediaInfoExternal)
C
0..1
Media information set includes a set of media information.
It shall be contained when the attribute eventType of the notificationEvent is one of the
"EXTERNAL_SESSION_UPDATE"
"EXTERNAL_SESSION_CREATE"
afInstance
string
O
0..1
The string identifying the served DCAS service instance
triggerinformation
TriggerInfo
O
0..1
Triggering information to invoke dcas media management
NOTE: The sessionInfo shall be present when the attribute eventType of the notificationEvent is set to "SESSION_ESTABLISHMENT_SUCCESS" and the originating IMS AS received the redirected-to party identity via the History-Info header field in the 200 OK responses to the initial INVITE request.
|
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 flow is simplified for illustration purposes. The IMS Parameter Provisioning flow is defined in clause AF.4 of TS 23.228 [2] and uses an IMS AS instance that does not need to be the one assigned to the specific IMS user. Since the provisioned parameters are stored as repository data in HSS, the IMS AS assigned to the IMS user will retrieve the DCAS provided service triggers from HSS.
Editor's note: How the IMS Parameter Provisioning procedure can support provisioning of service triggers for any UE is FFS.
2. The IMSAS responds the request to the DC AS confirming the provisioned data stored for the DCAS.
3. IMS session and BDC has been established.
4-11. UE#1 requests the establishment of P2A ADC establishment. IMSAS evaluate the service triggers provided in step 1. IMSAS provide the service triggers and the DCAS instance to the DCSF. DCSF determines the DC control policy and request media endpoint for the MDC2 from the IMSAS. IMS AS to request MF to reserving the originating media resources.
12. DCSF request the DC AS to establish a media endpoint for the MDC2 via Ndcas_Media_Management_Create message. The message includes calling and called parting id, application id/DCAS instance, session id, MF-side MDC2 media resource info. source URL used by DC AS to send subsequent ADC Control message and the certificate fingerprint of UE.
13. DC AS allocates DC AS-side MDC2 media resource for this session. DC AS respond to the DCSF with the DC AS endpoint for the MDC2 via Ndcas_Media_Management_Create response. The message contains: result, session id, DCAS-side MDC2 media resource information, destination URL used by DCSF to send subsequent Ndcas_Media_Management messages to update or terminate the connection. Update might contain e.g. the certificate fingerprint of UE.
14-16. DCSF updates the media resources in the MF via IMS AS, based on the received the DC AS-side MDC2 media resources information. Then, the IMS AS sends response to DCSF.
17-29. IMS AS performs SDP negotiation with terminating network. With a successful SDP negotiation, the application data channel established.
|
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 flow is simplified for illustration purposes. The IMS Parameter Provisioning flow is defined in clause AF.4 of TS 23.228 [2] and uses an IMS AS instance that does not need to be the one assigned to the specific IMS user. Since the provisioned parameters are stored as repository data in HSS, the IMS AS assigned to the IMS user will retrieve the DCAS provided service triggers from HSS.
Editor's note: How the IMS Parameter Provisioning procedure can support provisioning of service triggers for anyUE is FFS.
2. The IMSAS responds the request to the DC AS confirming the provisioned data stored for the DCAS.
3. IMS session and BDC has been established.
4-11. UE#1 requests the establishment of P2A ADC establishment. IMSAS evaluate the service triggers provided in step 1. IMSAS provide the service triggers and the DCAS instance to the DCSF. DCSF determines the DC control policy and request media endpoint for the MDC2 from the IMSAS. IMS AS to request MF to reserving the originating media resources.
12. DCSF request the DC AS to establish a media endpoint for the MDC2 via Ndcas_Media_Management_Create message. The message includes calling and called parting id, application id / DC AS ID, session id, MF-side MDC2 media resource info. source URL used by DC AS to send subsequent ADC Control message and the certificate fingerprint of UE.
13. DC AS allocates DC AS-side MDC2 media resource for this session. DC AS respond to the DCSF with the DC AS endpoint for the MDC2 via Ndcas_Media_Management_Create response. The message contains: result, session id, DCAS-side MDC2 media resource information, destination URL used by DCSF to send subsequent Ndcas_Media_Management messages to update or terminate the connection. Update might contain e.g. the certificate fingerprint of UE.
14-16. DCSF updates the media resources in the MF via IMS AS, based on the received the DC AS-side MDC2 media resources information. Then, the IMS AS sends response to DCSF.
17-24. IMS AS performs SDP negotiation with terminating network. And the IMS AS notifies the DCSF about the successful result of the SDP negotiation.
25. 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 media resource information of the terminating network. Then, the IMS AS sends response to DCSF.
26-33. IMS AS continues performing SDP negotiation with the originating network. With a successful SDP negotiation, the application data channel established.
|
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 MDC2 configuration;
- sending the certificate fingerprint of DC AS for end-to-end security between UE and DC AS.
DCSF:
- receiving subscription of the event UE-initiated P2A/P2A2P ADC establishment;
- notifying about the event of UE-initiated P2A/P2A2P ADC establishment;
- sending MF-side information for MDC2 configuration;
- sending the certificate fingerprint of UE for end-to-end security between UE and DC AS;
- sending request to create DC AS-side for the MDC2;
- receiving DC AS-side information for MDC2 configuration;
- receiving the certificate fingerprint of DC AS for end-to-end security between UE and DC AS;
- requesting IMS AS for MDC2 configuration.
IMS AS:
- receiving provisioning of trigger information from the DCAS;
- receiving MDC2 configuration request from DCSF;
- instructing MF for MDC2 configuration.
MF:
- receiving MDC2 configuration instructions from IMS AS;
- performing MDC2 configuration.
|
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 P2A or P2A2P session
- 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 P2A or P2A2P events with DCSF and get notified when DCSF detects the events.
- After receiving notification, If DC AS accepts P2A application data channel establishment request, DC AS sends an MDC2 reserved media resource in the newly proposed Ndcsf_MediaControl service operation message.
- DCSF after receiving MDC2 endpoint information from DC AS, invoke IMS AS to provide the MDC2 endpoint address of DC AS and request for MDC2 endpoint from MF side.
- DCSF provides the MF side MDC2 endpoint address to DC AS in response to Ndcsf_MediaControl service operation.
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.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 endpoint addresses between DC AS and MF.
NOTE: This solution identifies changes to existing specifications, these changes are shown using RED text.
Discovery of DCSF by DC AS:
The trusted DC AS can directly discover the DCSF with the help of HSS and in case untrusted DC AS, 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 DCSF address with the NEF/ DC AS.
Subscription with DCSF by DC AS:
Upon successful discovery, DC AS shall subscribe with DCSF for the UE initiated P2A or P2A2P session establishment events.
Providing MDC2 endpoint address by DC AS:
Upon notified by DCSF about establishment of P2A or P2A2P call, DC AS provides its MDC2 endpoint address with DCSF.
Table 6.14.1-1 List of events supported by DCSF
Event
Description and Detection criteria
Which NF detects the event
P2A pr P2A2P Application Data Channel established
Detected when an Application Data Channel is established.
Network detects that an Application data channel offer takes DC Application Server as target endpoint and requires to anchor in the MF
DCSF
|
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
AF, DC AS
Notify
Subscribe/Notify
AF, DC AS
6.14.2.2.2 Update to Nnef_ImsEventExposure (ImsEE) service (clause 5.2.6.39.2 of TS 23.502 [8])
The following describes the updated service operations for the IMS Event Exposure service:
|
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 identity, Event Filters, Notification Target address, Notification Correlation Information, Expiry time, Subscription Correlation ID (in the case of modification of the event subscription), AF Identifier.
IMS Public subscriber identity entry is only present for subscriber specific IMS events.
NOTE 1: The semantics of the Event ID and Event Filters are transparent to the NEF.
Outputs, Required: When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can expire based on the operator's policy).
Outputs, Optional: If applicable to the event type, the current status related to the subscribed event type is included, if Immediate Reporting Flag is included in the request within Event Reporting Information and if available (see clause 4.15.1).
NOTE: If the current status related to the subscribed event type is available and included in the response, it is not considered as an event report (i.e. it is not considered a one-time notification on event detection). That is, it is not deducted from the maximum number of reports if included in the request within the Event Reporting Information.
|
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 Data
Get
Request/Response
S-CSCF, I-CSCF, AS, DCSF
Management (_ImsSDM)
Subscribe
Subscribe/Notify
S-CSCF, AS
Unsubscribe
Subscribe/Notify
S-CSCF, AS
Notification
Subscribe/Notify
S-CSCF, AS
Update
Request/Response
AS, DCSF
Ims UE Context
Registration
Request/Response
S-CSCF, IMS AS, DCSF
Management (_ImsUECM)
DeregistrationNotification
Subscribe/Notify
S-CSCF
Deregistration
Request/Response
S-CSCF, IMS AS, DCSF
Authorize
Request/Response
I-CSCF
Update
Request/Response
S-CSCF
RestorationInfoGet
Request/Response
S-CSCF
RestorationInfoUpdate
Request/Response
S-CSCF
AsInfoGet
Request/Response
NEF
DcsfInfoGet
Subscribe/Notify
NEF, DC AS
DcsfInfoUnsubscribe
Subscribe/Notify
NEF, DC AS
DcsfInfoNotify
Subscribe/Notify
NEF, DC AS
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.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 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.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 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.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 about the following events, when applicable, (1) the UAS NF/NEF.
Inputs, Required: Public Identity.
Inputs, Optional: Private Identity.
Outputs, Required: Result.
Outputs, Optional: None.
|
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, Required: Result.
Outputs, Optional: None.
|
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: DCSF address.
Inputs, Optional: IMPU, IMPI.
Outputs, Required: Result.
Outputs, Optional: None.
|
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_MDC2
Create
Request/Response
NEF, DC AS
Update
Request/Response
NEF, DC AS
Delete
Request/Response
NEF, DC AS
|
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 for end-to-end security between UE and DC AS in case MDC2 is in "UDP/DTLS/SCTP", "TCP/TLS" or "SCTP/DTLS" mode.
Inputs, Optional: securitySetup if DC AS initiates the DTLS negotiation.
Outputs, Required: Result.
Outputs, Optional: None.
|
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, e.g. NEF, AF.
|
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
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 (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.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 correspond to the Notification), DC application ID, certificate fingerprint of UE for end-to-end security between UE and DC AS in case MDC2 is in "UDP/DTLS/SCTP", "TCP/TLS" or "SCTP/DTLS" mode.
Inputs, Optional: Calling party and called party IDs, application ID, securitySetup if UE initiates the DTLS negotiation.
Outputs, Required: Result.
|
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 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.14.3.1-1 shows only SBA services. Corresponding Sh procedure is not included in the Figure.
|
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 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 DC AS.
The P2A and P2A2P call flow is addressed in clause 6.11.3.
|
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 information in a new service operation message.
- subscribing with HSS to discover the DCSF address.
DCSF:
- receiving third party registration from IMS AS.
- registering DCSF address in HSS.
- receiving subscription for UE-initiated P2A/P2A2P ADC establishment event from NEF or DC AS and sending MF-side MDC2 endpoint information in notification message.
- receiving DC AS-side MDC2 endpoint information in a new service operation message.
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.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 solution has the following principles:
- The calling UE A has subscribed to the DC based CRS service.
- 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.
- 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 calling UE A notifies the calling event to the DC AS; the DC AS triggers the A2P DC establishment process to the called UE B.
|
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 service will not coexists with the legacy CRS service; it means the UE will subscribe only one of the CRS services.
Figure 6.15.2-1: Procedure of A2P ADC establishment in alerting phase for CRS
The steps in the procedure are as follows:
1. UE A initiates SIP INVITE including Audio/Video/BDC SDP; step 1-14 of Figure AC.7.1-1 in TS 23.228 [2] for BDC establishment apply.
2. BDC has been established for UE B and UE B may download the application list and the application for CRS service.
3. Based on the subscription of UE A, IMS AS-1decides to notify the DC AS at the network serving the UE A this BDC establishment event.
NOTE: It assumes that the DC AS has subscribed the BDC establishment event of UE A.
4. The IMS AS-1 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 IMS AS-1 receives 180 Ringing from the terminating network.
7. The DC AS decides to establish A2P ADC to UE B to deliver the DC early media for CRS.
8. The DC AS establishes A2P ADC with UE B; 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].
UE B may download the application used in the alert phase.
The DC AS may send the A2P ADC addition request to the IMS AS-1 prior to the 180 Ringing. The IMS AS-1 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 B 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 B. The user of UE B experiences with the early media for CRS.
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 calling network the IMS session establishment event.
13. The DC AS releases the A2P ADC with UE B.
14. Subsequent procedures continue.
|
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 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.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/AF needs to create an IMS session with audio/video media and DC media at the same time.
OMA has specified a RESTful Network API for Audio Call, but it cannot support DC media. If a 3rd party AF/AS wants to create an IMS session with audio and DC media, it has to invoke the OMA API to create a IMS session with audio firstly and then it invokes Nnef_ImsSessionManagement API specified by 3GPP to add DC media in the established IMS session. It means that the 3rd party AF/AS need to utilize two sets of APIs with different styles (OMA style and 3GPP style) and it cannot use both audio and DC media at alerting phase.
To ease the development of the 3rd party AF/AS and enable that audio and DC media can be used at alerting phase, both Nnef_ImsSessionManagement, Nimsas_ImsSessionManagement and Nmf_MediaResourceManagement service specified in Release 19 need to be enhanced to support audio and video media.
The main principles of the solution are to align with and expand on existing specified functionality:
- to add exposure capabilities to introduce support for establishment, modification and release of MMTel media (e.g. audio & video).
- addition of MMTel media (e.g. audio & video) exposure capabilities is in the context of data channel (e.g. enhancing audio/video services with DC capabilities or enhancing DC services with audio/video services capabilities).
NOTE: The term MMTEL media refers to media that is not sent through/ via a data channel.
|
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 addition of MMTel media (e.g. audio, video) to the existing specified relevant service operations. The proposal builds on aligning with already specified functionality where the establishment, modification and release of MMTel media (e.g. audio, video) is supported in the following services:
- Nimsas_MediaControl_MediaInstruction service operation (see clause AA.2.4.3.2 of TS 23.228 [2])
- Nmf_MRM_Create service operation (see clause AA.2.5.2.2 of TS 23.228 [2]).
3GPP stage 3 has also defined support for audio / video (for example, see clause 6.1.6.3.4 of TS 29.175 [9]).
The extended functionality will for example enable a DC AS to add, modify or release MMTel media (e.g. audio/video) to / from a standalone ADC or enable a person / user to add, modify or release MMTel media (e.g. audio/video) towards DC AS (for DC enabled services).
The IMS AS services that are amended to indicate support of MMTel media (e.g. audio / video) in addition to the existing DC media are described in clause 6.16.4 Service definition enhancements.
Support for MMTel media (e.g. audio/video) shall also be included in the yet undefined services on DC3 & DC4 reference point.
The following two example procedures show the addition of MMTel media (e.g. audio and video) in addition to an A2P application data channel, between the UE-1 and DC AS over MDC2. As result, the MMTel media is anchored in the MF.
|
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 of an adding an IMS audio session with a standalone A2P application data channel
0. The DC AS decides to add an IMS audio session with an already established standalone A2P application data channel with UE A.
1. The DC AS sends a Nnef_ImsSessionManagement_Update request to the NEF requiring to add an IMS audio session as addition to an already created standalone A2P application DC with UE A.
The DC AS sends the session ID (of previously created ADC) and UE A's IMPU in addition to the media operation set including the parameters for the media type set as "Audio" to NEF. The DC AS may include a Notification Target Address and Correlation ID to the Nnef_ImsSessionManagement_Update request to be notified for the progress of the session creation.
2. If the NEF authorizes the request, the NEF queries the HSS with Nhss_ImsUECM_AsInfoGet service operation to retrieve the IMS AS instance serving UE A.
3. The NEF sends a Nimsas_ImsSessionManagement_Update request to the IMS AS-1 requiring to add an IMS audio session. The request includes the session ID (of previously created ADC) and UE A's IMPU in addition to the media operation set. The media operation set includes the parameters for the media type set as "Audio", binding info & the MDC2 media endpoint. The NEF may include a Notification Target Address and Correlation ID to the Nimsas_ImsSessionManagement_Update request to be notified of the session create progress.
4. The IMS AS-1 validates the user subscription data and checks the IMS audio & DC capability of UE A to determine whether the request should be notified to DCSF-1. If UE A does not have subscription of IMS data channel and MMTel media (e.g. audio), then the request shall be rejected with appropriate cause and the subsequent steps are skipped. If the IMS AS-1 allows the request to proceed, it returns a successful Nimsas_ImsSessionManagement_Update response to the NEF.
5. The NEF returns a successful Nnef_ImsSessionManagement_Update response generated by the IMS AS-1 to the DC AS.
6. The IMS AS-1 sends a Nimsas_SessionEventControl_Notify request to the DCSF-1 with event set to ExternalSessionCreateEvent. The notification includes the necessary parameters based on the information extracted from the media operation set (including MediaInfoList: MediaType - "Audio") received in step 3 and other stored parameters in the IMS AS-1 if applicable.
7. After receiving the session event control notification, the DCSF-1 determines the policy how to process the A2P media audio establishment request based on the related parameters in the notification and/or DCSF-1 service specific policy.
8. The DCSF-1 determines that the A2P media audio requires the DCAS audio to be anchored in MF-1.
9. The DCSF-1 instructs the IMS AS-1 to set up the A2P audio by sending a Nimsas_MediaControl_MediaInstruction request.
10. Based on the instruction from DCSF-1, the IMS AS-1 interacts with the MF-1 to allocate audio media resource towards UE A and MDC2 media resource towards the DC AS.
11. The IMS AS-1 returns the Nimsas_MediaControl_MediaInstruction response to the DCSF-1.
12. DCSF send a connection (audio) establishment request offer to DCAS including the MDC2 media resource.
13. DCAS accepts the request and provides MDC2 media resource (audio).
14. The DCSF-1 instructs the IMS AS-1 to set up the audio by sending a Nimsas_MediaControl_MediaInstruction request.
15. Based on the instruction from DCSF-1, the IMS AS-1 interacts with the MF-1 to request update of DCAS side media resource information.
16. The IMS AS-1 returns the Nimsas_MediaControl_MediaInstruction response to the DCSF-1.
17. The DCSF-1 returns the Nimsas_SessionEventControl_Notify response to the IMS AS-1.
18. The IMS AS-1 generates a re-INVITE request in which the SDP offer contains the media information of the audio A2P application required by the DC AS, binding information and the session ID.
The IMS AS-1 sends the re-INVITE request to UE A.
19. DC media negotiation may be completed through 18X/PRACK/200 OK(PRACK)/200 OK(INVITE)/ACK procedure.
20. The IMS AS-1 requests MF-1 to update UE-A side media (Audio) resource information.
21. UE A established audio with DC AS.
22. If the NEF included a Notification Target Address in the Nimsas_ImsSessionManagement_Update request in step 3, the IMS AS-1 notifies the NEF for the progress of the audio session creation with the Nimsas_ImsSessionManagement_Notify request.
23. If the DC AS included a Notification Target Address in the Nnef_ImsSessionManagement_Update request in step 1, the NEF notifies the DC AS for the progress of the session creation with the Nnef_ImsSessionManagement_Notify request.
24. The DC AS returns a Nnef_ImsSessionManagement_Notify response to the NEF.
25. The NEF returns a Nimsas_ImsSessionMangement_Notify response to the IMS AS-1.
|
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 set up Signalling Procedure
The steps in the call flow are as follows:
0.a. It is assumed that DC AS has provisioned triggers in IMS AS to be informed of media setup (e.g. audio (setup) media request).
0.b. As in the base signalling procedure (AC.7.2.2-1), steps 0-3 of clause AC.7.2.1 applies. It is assumed that audio A-B has also been established.
Editor's note: Steps 1-3 are to be updated.
NOTE 1: The SIP re-INVITE (step 1) is initiated by the served users UE (in this case UE#1).
4. After receiving the session event notification, the DCSF determines the policy about how to process the application data channel / audio establishment request based on the related parameters (i.e. associated DC application binding information) in the notification and/or DCSF service specific policy.
5. The DCSF determines that the added Application Data Channel / audio media of the offer takes DC Application Server as target endpoint and requires to anchor in the MF.
6. The DCSF invokes Nimsas_MediaControl service operation to instruct IMS AS to terminate the media flow of the originating UE to MF. The instruction also includes information to be consumed by the MF that the audio media shall be relayed via the MDC2 interface.
7. The IMS AS invokes Nmf_MRM_Create(List of Media Termination Descriptors) service operation to instruct MF on application data channel / audio establishment and data channel / audio media resource reservation based on the DC / audio media information received from DCSF.
8. The IMS AS notifies the MediaControl instruction control response to DCSF.
9. The DCSF stores the media resource information and sends a P2A (audio / DC) application data channel establishment request (including the MDC2 media resource received from MF) to the DC Application Server via DC3/DC4.
10. DC Application Server accepts the P2A application data channel establishment request, returning an MDC2 reserved media resource as answer and is prepared for UE#1 traffic through MDC2.
NOTE 2: Details on how DCSF communicates with the DC Application Server is for study as part of KI#3.
11. DCSF requests IMS AS to update the MF resource with MDC2 media endpoint information of DC Application Server.
12. IMS AS updates the MF resource.
13. IMS AS notifies the MediaControl instruction control response to DCSF.
14. DCSF replies to the notification received in step 3.
15-16. IMS AS sends the re-INVITE to remote network side and UE#2, via the originating S-CSCF, which does not include application data channel request in the SDP for the application data channel.
17-19. UE#2 and terminating network returns a 200 OK response with SDP answer for audio/video.
20. IMS AS notifies the DCSF about the successful result of the MediaChangeRequest event.
21. DCSF replies to the notification.
22-23. The IMS AS includes SDP answer for application data channels / audio to UE#1 in 200 OK response and sends 200 OK response to S-CSCF and P-CSCF.
24. The originating network P-CSCF executes QoS procedure for application data channel / audio media based on the SDP answer information from the 200 OK response.
25. CSCF returns the 200 OK response to UE#1.
26. UE#1 send ACK to the terminating network.
27. The application data channel / audio between UE#1 and DC Application Server is established via MF. MF forwards data channel / audio traffic between UE#1 and DC Application Server based on MDC2 media point information received in steps 9 and 12.
|
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 Subscriber or the identity of the consumer NF, e.g. DC AS.
Called ID: It is the public identity of called IMS Subscriber.
Media information set: Includes a set of media information indicating how the media used in the created session. Each media information contains:
- Media Correlation ID: It identifies the media component to be created. It is allocated by the consumer NF.
- Media Type: It indicates the media type used in the created session, e.g. Data Channel, Audio or Video.
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters:
- When the Media Type is Audio or Video, it includes:
- Codecs and Formats;
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- App Binding Information;
- Target ID(s): the public identity(ies) of the IMS Subscriber the DC is targeted;
NOTE: For P2P ADC, the Calling ID and Called ID of the session are used as the Target IDs.
- If PA2 or P2A2P is selected, the MDC2 media endpoint address(es) of the application layer is included.
- When DC Type is BDC;
- Target ID: the public identity of the IMS Subscriber the DC is targeted;
- the MDC1 media endpoint address.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [2].
Outputs, Required: Result indication.
Outputs, Optional: None.
|
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).
Inputs, Required: Session ID, Media operation set.
Session ID: It is the identity of session that this request targeted to.
Media operation set: Includes a set of media operations commands indicating how to modify the media used in the specific session. Each media operation command contains:
- Media Correlation ID: It identifies the media component to be created.
- Operation Type: It indicates adding, updating or removing the corresponding media.
- Media Type: It indicates the type of operated media (e.g. Data Channel, Audio or Video).
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters:
- When the Media Type is Audio or Video, it includes:
- Codecs and Formats;
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- App Binding Information;
- Target ID: the public identity of the IMS Subscriber the DC is targeted;
- If P2A or P2A2P is selected, if the Operation Type indicates adding or updating the media, the MDC2 media endpoint address of the application layer is indicated.
- When DC Type is BDC:
- Target ID: the public identity of the IMS Subscriber the DC is targeted
- if the Operation Type indicates adding or updating the media, the MDC1 media endpoint address.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [2].
Outputs, Required: Result indication.
Outputs, Optional: None.
|
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 set.
Calling ID: It is the public identity of calling IMS Subscriber or the identity of the consumer NF, e.g. DC AS.
Called ID: It is the public identity of called IMS Subscriber.
Media Information set: Includes a set of media information indicating how the media used in the created session. Each media information contains:
- Media Correlation ID: It identifies the media component to be created. It is allocated by the consumer NF.
- Media Type: It indicates the media type used in the created session, e.g. Data Channel, Audio or Video.
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters.
- When the Media Type is Audio or Video, it includes:
- Codecs and Formats;
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- Application Binding Information; and
- Target ID(s): the public identity(ies) of the IMS Subscriber the DC is targeted;
NOTE 2: For P2P ADC, the Calling ID and Called ID of the session are used as the Target IDs.
- If P2A or P2A2P is selected, the MDC2 media endpoint address(es) of the application layer is included.
- When DC Type is BDC:
- Target ID: the public identity of the IMS Subscriber the DC is targeted.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [2].
Outputs, Required: Result indication.
Outputs, Optional: Session ID allocated by IMS AS.
|
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, Required: Session ID, Media operation set.
Session ID: It is the identity of session that this request targeted to.
Media operation set: Includes a set of media operations commands indicating how to modify the media used in the specific session. Each media operation command contains:
- Media Correlation ID: It identifies the media component to be created.
- Operation Type: It indicates adding, updating or removing the corresponding media.
- Media Type: It indicates the type of operated media (e.g. Data Channel, Audio or Video).
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters.
- When the Media Type is Audio or Video, it includes:
- Codecs and Formats;
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- Application Binding Information; and
- Target ID: the public identity of the IMS Subscriber the DC is targeted;
- If P2A or P2A2P is selected, if the Operation Type indicates adding or updating the media, the MDC2 media endpoint address(es) of the application layer is included.
- When DC Type is BDC:
- Target ID: the public identity of the IMS Subscriber the DC is targeted.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [2].
Outputs, Required: Result indication.
Outputs, Optional: None.
|
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 function specification information requested by the application layer, e.g. DCSF, to be applied on the media stream by the MF.
Inputs, Required: List of Media Termination Descriptors.
Each Media Termination Descriptor of the list includes:
- Termination ID: A unique identity of the termination within the media context resource. The identity is allocated by the producer and must be set to value 'null' by the consumer when adding a termination to a context.
- List of Media Stream Descriptors belonging to the Termination.
Each Media Stream Descriptor of the list includes:
- Media ID: A unique identity of the media stream within the media context instance. The Media ID value is set by the consumer.
- associated Media ID: This parameter only exists when a multiplexed media is de-multiplexed to multiple media and is used to associate different media streams which are de-multiplexed from a multiplexed media component. This parameter is set to the value of the media ID of the original multiplexed media.
NOTE 1: Different Termination IDs associated with the same Media ID or associated media ID corresponding to the same Media ID represent the media stream flow for data forwarding.
- Remote Mb Specification: Media Specification specifying SDP parameters of a remote media endpoint e.g. media stream IP address and ports allocated at the remote UE.
NOTE 2: In the case of reserving termination media resource before receiving media negotiation information from the UE, Remote Mb Specification should be set to Null.
- Media Function Specifications: Specification of the media function to be applied to the media stream as requested by the application layer, which includes:
- Media Function Type: The value is set based on the type of the media function required, e.g. "DC media function type, Audio, Video or AR media function type.
- Media Function Description: Application specific media function description specifying how the media function shall handle and process the media stream. Data content depends on type of media function.
If the Media Function Type is "Audio" or "Video", then the Media Function Description incudes:
- Codecs and Formats;
If the Media Function Type is "DC Media Function", then the Media Function Description incudes:
- Media proxy configuration (HTTP or UDP) applicable to the media flow.
- Remote MDC1/MDC2 media endpoint address.
- Replacement HTTP URL per Stream ID allocated by the application layer representing the application list (e.g. graphical user interface) provided to the IMS subscriber via the MDC1 interface.
- Data Channel Mapping and Configuration information when originating/terminating data channel media flows on the Mb interface.
- Maximum Message Size: This attribute defines the maximum size to be expected.
- Data Channel Port: This attribute identifies the port for the Data Channel.
- Data Channel SCTP Port: This attribute identifies the SCTP port for the Data Channel.
- Security Setup: This attribute identifies the security setup of the DTLS connection.
- Security Certificate Fingerprint: This attribute identifies the security certificate fingerprint.
- Security Transport Identity: This attribute identifies transport layer identity
NOTE 3: Some of the above attributes are optional depending on the scenario and proxy configuration.
If the Media Function Type is "AR Media Function", then the Media Function Description includes:
- AR Media Specification: Description of additional media specification information needed for AR communication services from application layer, which includes:
- Media Processing Specification: It specifies the how the media stream should be processed.
NOTE 4: The detail of Media Processing Specification is defined by SA4 and needs to be further aligned.
- Avatar Media Specification: Description of additional media specification information needed for avatar communication services from application layer, which includes:
- Resource URL: URL that allocated by DC AS for MF to retrieve the avatar representation.
- Rendering mode: identifies the mode of rendering avatar media, i.e. UE centric, network centric with MF rendering, network centric with DC AS rendering.
- Media Processing Specification: It specifies how the media stream should be processed.
NOTE 5: Avatar Media Specification are optional depending on the scenario.
Inputs, Optional: None.
Outputs, Required: Result indication for the entire list, Media Resource Context ID, List of allocated Media Termination Descriptor Resource information. For each Media Termination Descriptor; the Termination ID and the list of media stream descriptors corresponding to the input list of media stream descriptor:
Media Resource Context ID uniquely identifies the media resources created by the MF. This identity shall be used as reference when updating or deleting the created media resource.
List of allocated Media Termination Descriptor Resource information includes one or multiple Media Termination Descriptor Resources allocated. The list will include same number of terminations, in the same order as provided in the request. Each Media Termination Descriptor Resource includes:
- Termination ID: Unique identity allocated by the consumer. The identity shall be used when updating/deleting the Media Termination.
- List of Media Stream Descriptor Resource information elements allocated within the media termination. The list will include same number of media streams, in the same order as provided in the request.
Media Stream Descriptor Resource information includes:
- Media ID: Unique identity of the media stream within the media context instance allocated by the consumer. This is identical to the Media ID used in the input.
- associated Media ID: identical to the associated Media ID received from the consumer.
- Local Mb Specification: Media specification specifying SDP parameters representing the media endpoint of the provider e.g. media stream IP address and port.
- Media Application Function Output Description: Optional media application function description including information required by the application layer. The Media Application Function Output Description shall be relayed to the DCSF by the consumer NF. Data content depends on type of media function. If the Media type is "DC media function", the Media Application Function Output Description includes:
- MDC1/MDC2 media point information (IP address/port number, etc.) which shall be relayed to the DCSF by the consumer NF.
Outputs, Optional: None.
|
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 configuration for Audio / Video.
- receiving MF-side (audio/video) information for MDC2 configuration.
DCSF:
- receiving subscription of the event ExternalSessionCreateEvent (with MediaType=Audio/Video).
- requesting IMS AS for MDC2 (audio/Video) configuration.
- sending MF-side (audio/video) information for MDC2 configuration to DC AS.
- sending request to create DC AS-side for the MDC2 (Audio/Video).
- receiving DC AS-side information for MDC2 (Audio/Video) configuration.
- requesting IMS-AS for MF (Audio/Video) configuration in e.g. controlling which media transformation the MF has to carry out.
IMS AS:
- Enhance Nimsas_ImsSessionManagement API to support audio and video media when creating, updating and removing an IMS session.
- receiving MDC2 (Audio/Video) configuration request from DCSF.
- instructing MF for MDC2 (Audio/Video) configuration.
- have to re-anchor voice media towards an MF/from MF based on DCSF instructions.
MF:
- Enhance Nmf_MediaResourceManagement API to support creating, updating and removing audio and video media.
- support Codec, formats and relevant audio/video media capabilities.
- receiving MDC2 (Audio/Video) configuration instructions from IMS AS.
- performing MDC2 (Audio/Video) configuration for DC AS service like e.g. translation & transcription services.
|
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 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.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 establishment success, application data channel establishment failure.
Inputs, Optional: application binding information, MF-side MDC2 address, indication of requesting DC AS-side MDC2 address.
Outputs, Required: Result.
Outputs, Optional: DC AS-side MDC2 address.
NOTE: The DC AS-side MDC2 address is required if the indication of requesting DC AS-side MDC2 address is present in the input.
|
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 DCSF decides to notify DC AS based on the implicit subscription.
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. The DCSF needs to indicates that it is requesting an MDC2 endpoint address from the DC AS side.
If the event ID is application data channel establishment request, then the DCSF will expect the Ndcsf_MediaControl_MediaInstruction from the DC AS.
4. The DC AS sends 200 OK indicating it receives the notification.
5. The DC AS sends Ndcsf_MediaControl_MediaInstruction to the DCSF to inform the MDC2 endpoint of the DC AS.
6. The DCSF sends 200 OK.
7. Steps 11-20 in 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 in clause AC.7.2.2 of TS 23.228 [2] applies.
|
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 detects this is an application data channel establishment request. The DCSF decides to notify DC AS based on the implicit subscription.
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. The DCSF needs to indicates that it is requesting an MDC2 endpoint address from the DC AS side.
If the event ID is application data channel establishment request, then the DCSF will expect the Ndcsf_MediaControl_MediaInstruction from the DC AS.
4. The DC AS sends 200 OK indicating it receives the notification.
5. The DC AS sends Ndcsf_MediaControl_MediaInstruction to the DCSF to inform the MDC2 endpoint of the DC AS.
6. The DCSF sends 200 OK.
7. Steps 6-8 in 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 in 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 in clause AC.7.2.3 of TS 23.228 [2] applies.
|
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 information to DC AS.
- receiving DC AS side MDC2 related media information from DC AS.
6.X Solution #X: <Solution Title>
Editor's note: This Rapporteur is picky - please use unique descriptive titles for all solution proposals.
6.X.0 High-level solution Principles
Editor's note: Where possible similar/overlapping solution proposals should be documented as a single solution in the TR.
Documentation of more than one solution from the same company for the same KI is allowed but it shouldn't be expected that all of them will be documented in the TR.
6.X.1 Description
Editor's note: This clause will describe the solution principles and architecture assumptions for corresponding key issue(s). Further (sub-)clause(s) may be added to capture details.
6.X.2 Procedures
Editor's note: This clause will describe the high-level procedures and information flows for the solution.
6.X.3 Impacts on Services, Entities and Interfaces
Editor's note: This clause captures impacts on existing services, entities and interfaces.
|
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.1.Z) and can either be then marked as not pursued or postponed to a future release.
|
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 Agreements" clause. If the interim agreement has impacts on another clause in the TR and if there is consensus, that TR clause can be updated.
By consensus interim agreements can become part of the final conclusions of the study.
The Overall Evaluation clause previously used in TR skeletons should not be used.
There should be a Topics for further consideration clause per Key Issue. It is recommended that this is used e.g. to capture common issues that need to be resolved for multiple solutions.
Annex A:
Change History
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA2#170
S2-2507417
-
-
-
Skeleton approved at SA2#170
0.0.0
2025-08
SA2#170
S2-2507417, S2-2507546, S2-2507547, S2-2507551, S2-2507610, S2-2507611, S2-2507612, S2-2507614, S2-2507615, S2-2507648, S2-2507655, S2-2507656
-
-
-
Baseline Doc, Scope, References, Architectural Assumptions Key issue 1, 2 &3, Solution 1, 2, 3, &4
0.1.0
2025-10
SA2#171
S2-2509268,
S2-2509270,
S2-2509274,
S2-2509275,
S2-2509276,
S2-2509277,
S2-2509598,
S2-2509599,
S2-2509600,
S2-2509621,
S2-2509622
-
-
-
Solution #2 update & add new solutions (#6, #7, #8, #9, #10, #11, #12,#13 and #14)
0.2.0
2025-11
SA2#172
S2-2510816,
S2-2510820,
S2-2510822,
S2-2510825,
S2-2510828,
S2-2510830,
S2-2510916,
S2-2510917,
S2-2510918,
S2-2510919,
S2-2510920,
S2-2510921,
S2-2510952,
S2-2510953
-
-
-
Solution updates & add new solutions (#15, #16, and #17)
0.3.0
2025-12
SA#110
SP-251349
-
-
-
MCC Editorial update for presentation to TSG SA#110 for information
1.0.0
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2".
[4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System".
[5] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[6] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".
[7] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[8] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
[9] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[10] ATIS J-STD-110: "Joint ATIS/TIA Implementation Guideline for J-STD-110, Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification".
[11] GSMA NG.119: "Emergency Communication".
[12] 3GPP TS 23.221: "Architectural requirements".
[13] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[14] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[15] 3GPP TS 23.540: "5G System: Technical realization of Service Based Short Message Service; Stage 2".
[16] 3GPP TS 29.338: "Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)".
[17] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[18] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[19] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[20] NENA-STA-024.1.1-2025: "Conveyance of Emergency Incident Data Objects (EIDO) between Next Generation (NG9-1-1) Systems and Applications". (https://www.nena.org/page/standards#NENA-STA-010).
[21] NENA SMS Text-to-9-1-1 Resources for PSAP & 9-1-1 Authorities. (https://www.nena.org/page/textresources).
[22] ATIS J-STD-110: "Joint ATIS/TIA Implementation Guideline for J-STD-110, Joint ATIS/TIA Native SMS/MMS Text to 9-1-1 Requirements and Architecture Specification".
[23] 3GPP TS 24.229: "IP multimedia call control protocol based on SIP and SDP; stage 3".
[24] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3".
[25] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[26] IETF RFC 4566: "SDP: Session Description Protocol".
[27] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)".
|
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>
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 4 Architectural Assumptions and Requirements
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 4.1 Architectural Assumptions
| Editor's note: This clause documents the common architecture assumptions identified for the study.
- The architectures for SMS over NAS (see TS 23.272 [7], TS 23.401 [5], TS 23.501 [2], TS 23.502 [3]) and SMS over IP (see TS 23.204 [8]) and the architectural principles of Emergency Services (see TS 23.167 [9]) will be used as a basis.
- SMS over IP can be applied for both 3GPP access and non-3GPP access (either over EPS or 5GS).
- The Short Message Service to Emergency Response Centre shall be supported also for roaming UEs, where roaming subscribers' SMS is routed to a local PSAP, according to the local regulations of the UE's location.
- For SMS over NAS over EPS, 3GPP access (including TN and NTN) is in scope.
- For SMS over NAS over 5GS, 3GPP access (including TN and NTN) and non-3GPP access are in scope.
- UEs in limited service state are not in scope of this document.
- Short Messages initiated by the Emergency Response Centre in response to a Short Message to the Emergency Response Centre sent from the UE are treated as regular Short Messages.
- Short Messages can be routed to different Emergency Response Centres, depending on the type of emergency service.
- The identification of the type of emergency service (police, ambulance, fire brigade, etc.) is based on the same mechanism used for emergency calls (see TS 23.167 [9]).
- This study builds upon requirements specified in clause 36 of TS 22.101 [6]. For SMS over IP emergency routing, existing IMS emergency services architecture in TS 23.167 [9] shall be leveraged.
- The payload structure of the SMS to Emergency Response Centre should be consistent across SMS over NAS and SMS over IP transport mechanisms to ensure uniform PSAP processing capabilities.
- Short Messages initiated by the Emergency Response Centre in response to the Short Message to the Emergency Response Centre are treated as regular Short Messages.
Editor's note: Whether the delivery of SMS to Emergency Response Centre shall be exclusively via an SMSC is FFS.
- Solutions need not cater to solve the problem of UE non-detectable SMS to Emergency Response Centre.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 4.2 Architectural Requirements
| Editor's note: This clause defines the architectural requirements that serve as the foundation for the study.
Solutions shall be defined both for networks supporting IMS and networks not supporting IMS.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 5 Key Issues
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 5.1 Key Issue #1: Identification of SMS to Emergency Response Centre and Emergency Service Type
| |
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 5.1.1 Description
| Based on the requirements in TS 22.101 [6], the EPS and 5GS shall have the capability to route a Short Message where the destination is an emergency number to a local Emergency Response Centre (i.e. a PSAP) according to the local regulation.
This key issue aims to study solutions to:
- identify whether an SMS should be routed to a PSAP;
- identify the type of emergency service (police, ambulance, fire brigade, etc.) required;
- address both the case of the UE detecting and the UE not detecting an SMS that is to be routed to Emergency Response Centre;
- consider the scenario where the serving PLMN does not support routing an SMS to an Emergency Response Centre.
|
9c43cb92c6eaab1e5d4db7c1c4cfea9a | 23.700-65 | 5.2 Key Issue #2: Support of SMS Delivery to Emergency Response Centre via NAS
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.