hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.2.1 Subscription procedure for a specific IMS Subscriber | Figure 6.3.2.1-1 depicts a flow diagram for subscription procedure for a specific IMS Subscriber.
Figure 6.3.2.1-1: Subscription procedure for a specific IMS Subscriber
The steps in the subscription flow are as follows:
DCSF subscribes session events related to a specific served IMS subscriber requesting use of data ch... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.2.2 Subscription procedure for a list of IMS Subscribers | Figure 6.3.2.2-1 depicts a flow diagram for subscription procedure for a list of IMS Subscribers.
Figure 6.3.2.2-1: Subscription procedure for a list of IMS Subscriber
The steps in the subscription flow are as follows:
DCSF subscribes session events related to a list of IMS subscribers whose member in the list requests... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.3.3 Impacts on Existing Nodes and Functionality | IMS AS:
- Supporting service operation of subscribing session events related to a specific served IMS subscriber or a list of IMS subscribers requesting use of data channel media.
DCSF:
- Supporting the use of subscription service operation for session events related to a specific served IMS subscriber or a list of IMS... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.4 Solution #4: Event subscription and notification of IMS DC for related subscribers | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.4.1 Description | This clause proposes solution for handling IMS NW providing mechanism for providing event notification of IMS DC for related subscribers to the subscribed node, which includes network function like DCSF and Application Function like any third party.
This proposal is to enhance by reusing the existing IMS DC service exp... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.4.2 Procedures | The procedure of subscription and notification for IMS DC for one of the subscriber or list of subscribers.
Figure 6.4.2-1
1. IMS AS sends the support for list of IMPUs and IMS DC in Nnrf_NFManagement_NFRegister channel while registering to NRF.
2. NRF will store IMS AS profile.
3. NRF will provide Nnrf_NFManagement_NF... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.4.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to existing entities and interfaces:
IMS AS:
- IMS AS will register its profile with NRF by providing its support for list of IMPUs and IMS DC.
DCSF/NEF/AF:
- Discovery of IMS AS using NRF by providing input as IMS DC and list of IMPUs to NRF and then subscribing with all th... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5 Solution #5: IMS event subscription mechanism | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.1 Description | This solution addresses the Key Issue#1 "Extensible IMS mechanism supporting IMS events in the context of DC communication", which covers:
- Identification of IMS events that Network Function/Application function can subscribe to. The IMS events can include events related to a specific IMS subscriber / groups of IMS su... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.1.1 IMS events that NF/AF can subscribe to | The IMS events include:
- IMS data channel application events. When a specific subscriber downloads some IMS data channel application from the DCSF, the event is reported by the DCSF.
- IMS session events. When the session status and media of a specific IMS session change, the event is reported by the IMS AS. Some of t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.2 Procedures | The following clauses illustrate how the NF service consumer subscribes and unsubscribes the events of a specific IMS subscriber generated by the DCSF and the IMS AS, and how the subscribed events are reported to the NF service consumer.
The NF service consumer in the sub-clauses below can be either the NFs inside IMS ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.2.1 Event subscription mechanism of DCSF | Figure 6.5.2.1-1 illustrates that the NF service consumer subscribes the event(s) of a specific IMS subscriber generated by the DCSF.
Figure 6.5.2.1-1: Create a subscription of the DCSF
1. The NF service consumer invokes Nnrf_NFDiscovery API of the NRF, carrying with the UE identity, e.g. IMPU, IMPI, IMSI or MSISDN, to... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.2.2 Event subscription mechanism of IMS AS | For the IMS AS instance serving the specific subscriber can't be founded by the NRF through the UE identity, such as IMPU, IMPI, IMSI or MSISDN and the IMS AS serving the specific subscriber may change if some network failure happens, this clause shows a solution that the subscription information to the IMS AS is store... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.5.3 Impacts on Existing Nodes and Functionality | The impacts on the DCSF:
- Support to expose the IMS data channel application event subscription and notification mechanism.
The impacts on the IMS AS:
- Support to retrieves the subscription information from the subscriber's data stored in the HSS.
- Support to expose IMS session status and media event notification.
T... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6 Solution #6: IMS capability exposure architecture | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1 Description | This solution addresses Key Issue#2 "Impact on IMS architecture, interfaces and procedures to support IMS capability exposure in the context of IMS data channel session" which covers:
- Identification of IMS events that Network Function/Application function can subscribe to. The IMS events can include events related to... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.1 Architecture Description | The following Figure 6.6.1.1-1 shows the high-level architecture of the solution.
Figure 6.6.1.1-1: Architecture of IMS capability exposure
The following network function is introduced in this architecture, whose function description are described in clause 6.6.1.2.
- IMSEF: IMS Exposure Function, is supported by the N... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.2 Network Function Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.2.1 IMS Exposure Function (IMSEF) | IMSEF is a dedicated NEF instance and is used for exposure of IMS capabilities to the DC AS, i.e. to support the IMS domain specific features/APIs and potentially the NEF features/APIs that are specified for capability exposure towards the DC AS to implement IMS services such as audio, video and data channel session.
W... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.3 Network Function Service Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.3.1 IMSEF Services | Figure 6.6.1.3.1-1: Reference Architecture for the Nimsef Services; SBI representation
Figure 6.6.1.3.1-2: Reference Architecture for the Nimsef Services; reference point representation
The IMSEF provides the following services to the DC AS:
- Control operations of IMS session with data channel media, such as initiatin... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.3.2 DCSF Services | Figure 6.6.1.3.2-1: Reference Architecture for the Ndcsf Services; SBI representation
Figure 6.6.1.3.2-2: Reference Architecture for the Ndcsf Services; reference point representation
The DCSF provides the following services to the IMSEF and the DC AS:
- Control operations of IMS session with data channel media, such a... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.1.3.3 IMS AS Services | The Nimsas SBI and the DC1 reference point have been specified in clauses AA.1.2 and AA.1.3 of TS 23.228 [5].
Figure 6.6.1.3.3-1: Reference Architecture for the Nimsas Services; SBI representation
Figure 6.6.1.3.3-2: Reference Architecture for the Nimsas Services; reference point representation
Two services of the IMS ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.2.1 General Description | Figure 6.6.2.1-1 illustrates the network model of IMS session with data channel media using 3rd Party Call Control procedure.
Figure 6.6.2.1-1: Network model of an IMS session with data channel media using 3PCC procedure
The 3rd Party DC AS establishes and manages an IMS session with data channel media between UE A and... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.2.2 Establishing an IMS session with data channel media | Figure 6.6.2.2-1 below illustrates how to establish an IMS session with data channel media using 3PCC procedure. According to the session creation API invoked by the 3rd Party DC AS, the IMS network initiates an IMS session with data channel media.
Figure 6.6.2.2-1: Establishing an IMS session with data channel media u... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.2.3 Terminating an IMS session with data channel media | Figure 6.6.2.3-1 and Figure 6.6.2.3-2 below illustrate how to terminate an IMS session with data channel media using 3PCC procedure. The terminating procedure in Figure 6.6.2.3-1 is triggered by UE A sending a BYE request and that in Figure 6.6.2.3-2 is triggered by the 3rd Party DC AS invoking a release session API pr... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.2.4 Modifying an IMS session to add data channel media | Figure 6.6.2.4-1 below illustrates how to modify an established IMS session to add data channel media using 3PCC procedure. It's assumed that the 3rd Party DC AS has established an IMS session with audio and video media between UE A and UE B using 3PCC procedure.
Figure 6.6.2.4-1: Modifying an IMS session to add data c... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.6.3 Impacts on Existing Nodes and Functionality | MMTel AS:
- Support IMS session handling with data channel media under the control of the DCSF, such as initiating, continuing, modifying, terminating and querying an IMS session and playing tones in an IMS session. The data channel media can be carried in the initial INVITE or be added at the subsequent stage.
- Suppo... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7 Solution #7: Solution for IMS capability exposure via DC3/DC4 | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.1 Description | The architecture to enable IMS capability exposure in the context of IMS data channel (DC) sessions is based on Figure AC.2.1-1 in clause AC.2.1 of TS 23.228 [5] and is depicted in Figure 6.7.1-1.
Figure 6.7.1-1: IMS capability exposure architecture
This solution defines the exposure of IMS capabilities related to DC s... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.1.1 Events to be exposed over DC3/DC4 | With this solution, there are two types of events, which can be exposed via DC3/DC4 interfaces (see Figure 6.7.1-1) from DCSF to DCAS via Ndcsf services.
The first type of events are call related events:
- establishing, updating, answering, terminating of IMS calls.
The second type of events are DC related events:
- es... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.1.2 DC AS requesting a service over DC3/DC4 | DCAS can request DC establishment, DC update, DC termination and DC application download via DC3/4. For that purpose, DCAS provides following information on DC3/DC4:
- Type of DC, which can be P2A, P2A2P, P2P and bootstrap;
- Action type, which can be establishment, update, termination, and download;
Editor's note: The... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.1.3 Information to be exposed to the DCAS via DC3/DC4 | One Ndcsf service can provide session control capabilities (e.g. Ndcsf_dc_session_control). This service allows DCAS to create a DC session and take control on DC session via DCSF.
DCSF can return to DCAS the following information on DC3/DC4:
- response code (success or failure);
- other information, e.g. session ident... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.2.1 Event Subscription and Notification | By event subscription and event notification, all events (i.e. call and DC related events) are subscribed and notified via DCSF. The NEF or DC Application Server discovers first a DCSF to subscribe for call and DC related events. For DC related events, the subscription request and notification response are handled by t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.2.2 Person-to-Person (P2P) Application Data Channel Setup | Based on Figure AC.7.2.1-1 in clause AC.7.2.1 of TS 23.228 [5], Figure 6.7.2.2-1 depicts a call flow for establishing an Application Data Channel triggered by IMS capability exposure in a person to person use case.
Figure 6.7.2.2-1: Person-to-Person (P2P) application data channel set up triggered by IMS capability expo... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.2.3 Person-to-Application (P2A) Application Data Channel Setup | Based on Figure AC.7.2.2-1 in clause AC.7.2.2 of TS 23.228 [5], Figure 6.7.2.3-1 depicts a call flow for establishing an Application Data Channel in a person to application use case. Note that there are two options to reserve the MDC2 media resources. The first option is that the media resources are reserved by DC Appl... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3 Service definition | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.1 Enhancements to DCSF services | One Ndcsf service can provide event capability exposure (e.g. Ndcsf_EventExposure).
Table 6.7.3.1-1
Service
Service Operations
Operation Semantics
Example Consumer(s)
Ndcsf_EventExposure
Subscribe
Subscribe/Notify
NEF, DCAS
Unsubscribe
NEF, DCAS
Notify
NEF, DCAS |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.1.1 Ndcsf_EventExposure service | 6.7.3.1.1.1 General
This service enables the consumer NF to subscribe and get notified of events.
The following events can be subscribed by a NF consumer:
- IMS session control events of a specific IMS subscriber.
- IMS data channel related events.
The following service operations are defined for the Ndcsf_EventExposur... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.2 Enhancements to IMS AS services | Based on Table AA.2.4.1-1 of TS 23.228 [5], the following service provided by IMS AS are enhanced:
Table 6.7.3.2-1
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nimsas_SessionEventControl
Subscribe
Subscribe/Notify
DCSF
Unsubscribe
Subscribe/Notify
DCSF
Notify
Subscribe/Notify
DCSF |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.2.1 Nimsas_SessionEventControl service | 6.7.3.2.1.1 General
This service enables the consumer NF to subscribe and get notified of events.
The following events can be subscribed by a NF consumer:
- IMS session control events of a specific IMS subscriber.
- IMS media control events of a specific IMS subscriber.
The following service operations are defined for ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.3 Enhancements to HSS services | One Ndcsf service can provide event capability exposure (e.g. Ndcsf_EventExposure).
Table 6.7.3.3-1
Service
Service Operations
Operation Semantics
Example Consumer(s)
Nhss_IMSASDiscovery
GET
Get
DCSF |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.3.3.1 Nhss_IMSASDiscovery service | 6.7.3.3.1.1 General
This service enables the consumer NF to discover an IMS AS, which is able to handle the call-related event based on the event information given by the consumer NF.
The following service operation is defined for the Nhss_IMSASDiscovery service:
- Nhss_IMSASDiscovery_Get.
6.7.3.3.1.2 Nhss_IMSASDiscove... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.4 Enhancements to Sc interface | The DCSF can retrieve the IMS AS identity/address from the HSS using the Sc interface.
NOTE: The details of the Sc enhancements are for stage 3. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.7.5 Impacts on existing nodes and functionality | Impacted nodes and functionality are as follows:
- DC Signalling Function (DCSF): The DCSF interacts with the DCAS for exposes DC resource and session control related capabilities to IMS capability exposure via DC3/DC4. The DCSF sends call related event subscription to IMS AS via DC1. The DCSF receives call related eve... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.8 Solution #8: Interworking between a DCMTSI UE and an MTSI UE by using messaging | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.8.1 Description | This solution addresses Key Issue #3 "Data channel interworking with MTSI UE" and focuses on how to support interworking by using messaging.
For the MTSI UE, the legacy media types usually include video media, audio media, message etc. This solution proposes a method to send a file from DCMTSI UE to MTSI UE by using me... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.8.2 Procedures | Figure 6.8.2-1: Person-to-Application (P2A) Application Data Channel set up Signalling Procedure
Precondition:
UE#1 is a DCMTSI UE, UE#2 is a MTSI UE.
The user of UE#1 wants to transfer a file, e.g. a photo, to the user of UE#2 during the call.
The steps in the call flow are as follows:
0-27. Step 0-27 from clause AC.7... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.8.3 Impacts on Existing Nodes and Functionality | This solution has some requirements on the existing IMS nodes below:
DCSF:
- Determine that the peer UE or the network of peer UE does not support data channel.
- Send peer UE's SIP URI and an indication to DC Application Server to indicate it to send a SMS with hyperlink to peer UE.
DC Application server:
- Send a SMS... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9 Solution #9: Data Channel Interworking mechanism between DCMTSI UE and MTSI UE | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.1 Description | This solution addresses Key Issue#3 "Data channel interworking with MTSI UE" to support data channel interworking mechanism between DCMTSI UE and MTSI UE, which covers:
- how to enhance IMS architecture and procedures to provide some form of IMS data channel applications service experience by data channel interworking ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.2.1 Interworking between a DCMTSI client and an MTSI client | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.2.1.1 General | The procedures described in this clause is applied to some data channel use cases in which it's a audio session and only unidirectional interaction is needed between both UEs. Real-time Screen Sharing as specified in TR 22.873 [16] is used as an example to describe the procedure. For example, in Real-time Sharing Scree... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.2.1.2 Interworking between a DCMTSI client in terminal and an MTSI client in terminal during BootstrapData Channel establishment | Figure 6.9.2.1.2-1 demonstrates the procedure of UE-initiated bootstrap data channel establishment between network A and UE A (a DCMTSI client in terminal), while an IMS audio call is established between UE A and UE B (an MTSI client in terminal).
Figure 6.9.2.1.2-1: Bootstrap data channel establishment procedure for i... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.9.2.1.3 Interworking between a DCMTSI client in terminal and an MTSI client in terminal during Application Data Channel establishment | The following procedure uses Real-time Screen Sharing application as the example. When UE A retrieves Real-time Screen Sharing application from the DCSF A and runs the application, the following procedure shown in Figure 6.9.2.1-3 is performed to transfer UE A's mobile screen data to UE B.
Figure 6.9.2.1.3-3: Applicati... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10 Solution #10: Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10.1 Description | This solution corresponds to KI#4 on Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions.
In this solution, the IMS network is enhanced to support the identity verification and authorization of 3rd party user identity during an IMS call.
This solution proposes ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10.2.1 How Originating IMS network invokes the signing on behalf of 3rd party (PBX Scenario) | Figure 6.10.2.1-1: How Originating IMS network invokes the signing on behalf of 3rd party (SIP trunk)
1. The 3rd party PBX sends a SIP INVITE that contains the IMPU of the calling UE and that may or may not contain the 3P ID e.g. provided in a new header on behalf of 3rd party subscriber to IBCF.
2. The IBCF forwards t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10.2.2 How Originating IMS network invokes the signing on behalf of 3rd party (Single SIP registration) | Figure 6.10.2.2-1: How Originating IMS network invokes the signing on behalf of 3rd party (single SIP registration)
1. The originating SIP UA sends a SIP INVITE that contains the IMPU of the calling UE and that may or may not contain the 3P ID e.g. provided in a new header on behalf of 3rd party subscriber to P-CSCF.
2... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.10.3 Impacts on services, entities and interfaces | This solution addresses the requirements of KI#4 and is applicable to both UNI (SIP UA) and NNI (IP PBX) case. The solution reuses existing STIR/SHAKEN architecture with enhancements that the STI-AS and STI-VS needs to support the signing and verification of the Rich Call Data identity header.
The solution relies on a ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11 Solution #11: Enhancement of STIR/SHAKEN framework to support delivery of third party ID | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11.1.1 Introduction | SHAKEN (Signature-based Handling of Asserted Information Using toKENs) is defined as a framework that utilizes protocols defined in the IETF STIR Working Group that work together in an end-to-end architecture for the authentication and assertion of a Caller ID by an originating service provider and the verification of ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11.1.2 Third party ID related data storage and retrieval | The content of third-party specific user identities used in IMS should be aligned with the definitions in draft-ietf-sipcore-callinfo-rcd-08 [19] and may include the calling person's name and job title, information related to the organization the caller is associated with and information related to the caller's locatio... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11.2 Procedures | Figure 1: Procedure of third party specific user identity signing
1. UE-A or third party PBX creates a SIP INVITE with the Public User Identity that has subscribed for the delivery of third party user identity information.
2. CSCF matches the originating Public User Identity with filter criteria, and determines to forw... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.11.3 Impacts on Existing Nodes and Functionality | IMS AS is enhanced to support following functionalities:
- Triggering the signing of third-party specific user ID with the Signing Server for originating call.
- Triggering the Verification Server for the verification of the signature for terminating call.
- Interworking with the repository to retrieve the third party ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.12 Solution #12: Verification of calling party when using third party specific identity | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.12.1 Description | This paper proposes solution for IMS network to authorize the user when user uses third party identity in the IMS session. The following are the main principles of the solution:
- Authentication and Authorization of third party identity in each session irrespective of it is needed or not will add delay to the call setu... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.12.2 Procedures | Figure 6.12.2-1: Third Party Identity verification used in an IMS session
The detailed procedure is described in Figure 6.12.2-1.
1. Third party will provision the list of IMPUs along with the third party identity, which is common for all IMPUs. If the IMPUs use unique third party identities, which is different for eac... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.12.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to existing entities and interfaces:
HSS:
- Third Party will provision with list of IMPUs along with third party identity and the need for third party identity authentication and authorization.
S-CSCF:
- S-CSCF at originating side, based on parameter, which indicates the nee... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.13 Solution #13: Support of Third Party User Identities in IMS using STIR/SHAKEN | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.13.1 Description | The Ms reference point as described in TS 24.229 [10], Annex V.2, is used to request signing of an Identity header field or request verification of a signed assertion in an Identity header field. This enables calling number verification using signature verification and attestation information based on the STIR/SHAKEN f... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.13.2 Procedures | The procedures to sign and verify PASSporT tokens follow the descriptions in TS 24.229 [10] with the main difference that besides telephone numbers also other information as described in draft-ietf-sipcore-callinfo-rcd-08 [19] and draft-ietf-stir-passport-rcd-26 [18] can be used for signing and verification. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.13.3 Impacts on existing nodes and functionality | Following nodes are impacted by this solution.
HSS:
- HSS stores one or several URL(s) pointing to resources on Web servers where the terminating network or terminating party can download the respective data, e.g. Rich Call Data or an Avatar representation to be used in the IMS call. Optionally, HSS may directly store ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14 Solution #14: Standalone IMS data channel without extra subscription | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.1.1 General | This clause provides solution against Key Issue #6 Support of Standalone IMS Data Channel Sessions.
This solution uses the architecture of IMS data channel as specified in TS 23.228 [5] as the basis and has no requirement to enhance the architecture.
The following scenarios are supported in this solution:
- The UE esta... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.1.2 Subscription of standalone data channel | Support of standalone data channel is under the condition that the UE and IMS network both support data channel and the data channel service is already subscribed. Moreover, supporting standalone data channel can significantly extend the scope and the flexibility of using IMS data channel applications, which allows ope... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.1.3 Capability negotiation of standalone data channel | Supporting of standalone data channel is based on the capability of supporting data channel and can be seen as a specific case of handling SDP for data channel media component. Therefore it is reasonable to assume that UE and IMS network who generally support IMS data channel can support handling SDP of standalone data... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.2.1 Establishment of an IMS session with standalone application data channel | The user may trigger to establish an IMS session with standalone application data channel if the UE has previously downloaded the application and provided to the user. In this case the UE may establish a new IMS session with only application data channel media. In the example below, the MF is not used to anchor the App... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.2.3 Session modification | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.2.3.1 Change an IMS session to a standalone data channel session | When the user wants to delete the media components of audio/video/messaging of an IMS session and only leave data channel for further usage, the user may click a button to just release the voice/video/message session but the session is not released. By this the UE sends re-INVITE request with the SDP offer setting all ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.14.2.3.2 Add audio/video/message media to a standalone data channel session | When the user want to add the media components of audio/video/messaging to a standalone data channel, the user may keep the DC application and select the called party on the phone and initiates a voice/video/messaging session with the called party. By this the UE sends re-INVITE request with the SDP offer including med... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.15 Solution #15: Solution to support standalone bootstrap data channel | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.15.1 Description | This solution addresses Key Issue #6 " Support of Standalone IMS Data Channel Sessions " and focuses on how to support establishing a (standalone) bootstrap data channel without accompanying application data channel.
When the UE initiates establishment of a standalone bootstrap data channel, the UE includes a specific ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.15.2 Procedures | When a UE initiates an IMS session with standalone bootstrap data channel, the procedure specified in clause AC.7.1 of TS 23.228 [5] applies with the following differences:
- If the UE initiates a bootstrap data channel the SDP offer in step 1 only includes media component for originating bootstrap data channel;
- The ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.15.3 Impacts on Existing Nodes and Functionality | This solution has some requirements on the existing IMS nodes below:
DCSF:
- Determines that the UE requests to establish a standalone bootstrap DC based on the called ID.
- Creates only the originating side media information.
IMS AS:
- Terminates the IMS session based on the specific Request URI.
Editor's note: Furthe... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16 Solution #16: Supporting of standalone IMS DC sessions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.1 Description | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.1.1 General | This clause provides solution against Key Issue #6: Support of Standalone IMS Data Channel Sessions.
This solution provides an analysis of potential impacts to IMS architecture in supporting standalone IMS DC session and proposed a solution based on the analysis.
Editor's note: The usage scenario of standalone IMS DC i... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.1.2 The existing clarification on the restriction of standalone IMS DC | Following clarification is specified in TS 23.228 [5]:
UE can establish an IMS Data Channel simultaneously while establishing an IMS audio/video session or upgrade an ongoing IMS audio/video session through a re-INVITE to an IMS Data Channel session.
Following clarification is specified in TS 24.229 [10]:
IMS data chan... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.1.3 Analysis on the impact of standalone IMS DC to existing NFs | If the P-CSCF, S-CSCF or IMS AS was performing policy restriction i.e. not allow support for IMS DC without MMTEL then the following would have to be present in the specifications of previous releases e.g. Rel-18.
P-CSCF: When the P-CSCF receives any SIP request containing an SDP offer, the P-CSCF shall examine the med... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.1.4 Proposal | Since none of the above exists in specifications of previous releases, in summary, the support of standalone IMS DC sessions can be achieved without impact to the existing NFs and therefore it can work with legacy NFs of previous releases.
Editor's note: This proposal is to be updated if any impact to existing IMS NFs ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.2 Procedures | Figure 6.16.2-1 demonstrate the signalling flow for establishing an IMS session with standalone data channels (bootstrap and/or application data channels).
Figure 6.16.2-1: Establishment of standalone IMS DC session procedures
1. UE-1 sends the SIP INVITE request with an initial SDP to the S-CSCF, via P-CSCF. The SDP o... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.16.3 Impacts on existing services, entities and interfaces | UE:
- Initiates IMS session with standalone IMS DC;
- Terminates IMS Session with standalone IMS DC. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.