hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.38.2 Impacts on existing services, entities and interfaces | Impacts for signalling storm detection:
NWDAF:
- Supports the new Analytic ID for the signalling storm detection analytics.
- Supports collecting the amount of signalling received by and sent from the NFs and finer granularity information from UE to derive signalling storm detection.
Impacts for signalling storm mitiga... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39 Solution #39: NWDAF Analytics based Signalling Strom Prediction | |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39.1 Description | The 5G core network, with its exponential growth in connected devices (e.g. IoT devices), complex control plane traffic (considering the number of network functions and corresponding services) and unexpected misconfiguration or failure of NFs, is susceptible to "signalling storms," which overwhelm the network function ... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39.2 Procedures | Figure 6.39.2-1 depicts the procedure for the proposed solution where NWDAF collects input data including the metrics/KPIs of the service operations, and produce the notification of the abnormal control plane signalling pattern, which is a trigger to take a prevention/mitigation action in other entities.
Figure 6.39.2-... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39.2.1 UE registration signalling storm prevention/mitigation using Control Plane Signalling Abnormality Analytics | The proposed procedure can be used to prevent/mitigate various signalling storm scenarios. Figure 6.39.2-2 depicts how it is applied for the UE registration signalling storm scenario.
Figure 6.39.2-2: UE registration signalling storm prevention/mitigation using Control Plane Signalling Abnormality Analytics
1a. NWDAF s... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39.2.2 Inter-NF Signalling storm prevention/mitigation by SCP using NWDAF Analytics | Figure 6.39.2.2-1: Inter-NF Signalling storm prevention/mitigation by SCP using NWDAF Analytics
1. The NF service consumer intends to communicate with an NF service producer. The NF service consumer sends the service request to an SCP. The request may include discovery and selection parameters necessary to discover and... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 6.39.3 Impacts on existing services, entities and interfaces | The solution has the following impacts:
NWDAF:
- Extending functionalities to produce Control Plane Signalling Abnormality Analytics ID.
- Collects training data for signalling storm detection and prediction.
- Trains ML model for signalling storm detection.
5GC NFs (e.g. AMF/SMF/NEF/SCP):
- Extending service to report... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 7 Overall Evaluation | Editor's note: This clause will provide a general evaluation and comparison of the solutions per Key Issue #<X>. |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 8 Conclusions | |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 8.1 Conclusions for KI#1: Enhancements to LCS to support Direct AI/ML based Positioning | The conclusions for supporting Direct AI/ML based Positioning is based on the following principles:
Principle #1: The LMF is enhanced to perform location calculation based on ML model. The interaction between LMF and MTLF is only for model provisioning and possibly, based on coordination with RAN WGs, for data collecti... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 8.2 Conclusions for KI#2: 5GC Support for Vertical Federated Learning | P#2.1: VFL related new functionalities include:
P#2.1.1 VFL Server: An NWDAF or AF that integrates local training results for the local ML model update in VFL training process. It also coordinates the VFL training process by discovering and selecting VFL clients. In VFL inference process, The VFL server aggregates loca... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 8.3 Conclusions for KI#3: NWDAF-assisted policy control and QoS enhancement | Following conclusions are proposed for KI#3:
Based on PCF request, NWDAF may provide assistance information analytics to PCF to assist the QoS determination and/or modification of QoS parameters. The PCF may take the assistance information into account to determine QoS parameters for a QoS flow, based on the operator's... |
c8f50ee24a14933c33290076ea3625ad | 23.700-84 | 8.4 Conclusions for KI#4: NWDAF-assisted Network Abnormal Behaviour Mitigation and Prevention | It is agreed to use following principles as baseline for normative work. - By means of statistics and predictions, NWDAF supports assistance to signalling storm mitigation and prevention by statistically learning the expected normal level of signalling and identifying a significant deviation indicating a signalling sto... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 1 Scope | The present document studies the following aspects:
1) service aspects for supporting the eMMTel service based on requirements from stage 1, e.g. eMMTel specified in 3GPP TS 22.261 [2] and SA WG1 Rel-18 eMMTEL WID;
2) the service enabler layer capabilities exposure based on architecture and procedures specified in Anne... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 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.
- Fo... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 3 Definitions of terms, symbols and abbreviations | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 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].
eMMTel service: An IMS multimedia telephony service as specified in 3GPP TS 24.173 [20] with Data ch... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 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].
DC Data Channel
DCMF Data Channel Media Function
DCMTSI Data Channel Multim... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4 Analysis of gaps | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4.1 Introduction | The subsequent sub-clauses contain the results of an analysis of existing architecture and APIs in application layer frameworks against the requirements of enabling eMMTel service. This analysis has been performed as a starting point of the study to get a better understanding of existing functionality and the gaps. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4.2 Analysis of OMA OneAPI framework | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4.2.1 Description | OMA OneAPI framework provides Call Control and Configuration capabilities via NGSI-4, NGSI-5, NGSI-6 and NGSI-7 interfaces (see OMA-AD-NGSI [4]) in enabler layer. The interfaces extend the interface provided by Parlay X. The OneAPI Call Control profile of the RESTful Network APIs defines a subset of the HTTP operations... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4.2.2 Detailed analysis | This clause provides the results of a high-level gap analysis of the OMA OneAPI framework needed to support the enabling of eMMTel service, based on OMA inputs. Table 4.2.2-1 provides the results of this analysis and lists the gaps identified.
Table 4.2.2-1: OMA OneAPI framework analysis results
Capabilities needed to ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 4.2.3 Analysis result | OMA oneAPI framework does not support Data channel services as specified in Annex AC.2 of 3GPP TS 23.228 [3] Some ideas of the basic functionalities of OMA OneAPI can be considered to be used for reference of this study. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 5 Architectural Assumptions and Principles | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 5.1 Architectural Assumptions | The following architecture assumptions are applied to all KIs in the study:
- The architecture of IMS and Support of Data channel in IMS specified in 3GPP TS 23.228 [3] is used as basis network architecture for supporting eMMTel service.
- The CAPIF architecture specified in 3GPP TS 23.222 [9] is used as basis framewor... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 5.2 Architectural Principles | The following architectural principles apply for all KIs in the study:
- Solutions are expected to have no introduction of any normative impact to underlying 3GPP network architecture including core network and IMS. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6 Key Issues | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.1 Key Issue #1: Application calling service based on eMMTel service | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.1.1 Description | Currently, in order to perform a call application providers and vertical service providers have to develop applications using specific protocols to access Call Control functions provided by network elements. This approach requires a high degree of network expertise, or they can use Third Party Call specified in 3GPP TS... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.2 Key Issue #2: Download data channel application to UE | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.2.1 Description | In eMMTel service, different specific service may have different requirement for the data channel application. E.g. in the pre-call service, e.g. Multimedia CLIP (Calling Line Identification Presentation), COLP (Connected Line Identification Presentation) described in 3GPP TR 22.873 [10], the data channel application s... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.3 Key Issue #3:support of eMMTel call between application with IMS capability and application without IMS capability | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.3.1 Description | The architecture and workflow of supporting Data Channel services in IMS are specified in the Annex AC of 3GPP TS 23.228 [3]. DC Application Server is introduced in the architecture and it is used to handle the application logic of DC applications transferred in the Data Channel, i.e. DC Application Server is not relat... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.4 Key Issue #4:support of providing application layer caller information to callee | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.4.1 Description | There are several primary business functions that organizations use MMTEL services for, including internal communication in a organization, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. (Detailed use cases see 3GPP TR 22.... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.5 Key Issue #5: Support of virtual number | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.5.1 Description | Virtual number is a widely used value added calling service which the real number of user is hid by the service provider to protect the privacy of user. This virtual number is used by one or both parties in a call and is not used in multi-device scenario, i.e. virtual number is not used by the secondary devices, as spe... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.6 Key Issue #6: Multiple call control handling coordination among different Application Servers | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.6.1 Description | OMA OneAPI provides Third Party Call capabilities for the call control. Besides in 3GPP TS 23.228 [3] and 3GPP TS 23.700-87 [13], it is proposed that DCSF can open DC event notification and control capabilities to the upper application layer through NEF or DC4 interfaces. In clause AC.2.2.1 of 3GPP TS 23.228 [3], it is... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.7.1 Description | It is specified in clause 6.2.10 of 3GPP TS 26.114 [14] that the data channel application is uploaded prior to the DCMTSI call where it is intended to be used. And as specified in Annex AC.5 of 3GPP TS 23.228 [3], the DC Application is uploaded to DCAR. However, how to upload the data channel application to the network... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 6.8.1 Description | Traditional multiparty service provides a mobile subscriber with the ability to have a multi-connection call, i.e. a simultaneous communication with more than one party. It also has very practical application scenarios with the support of data channel, e.g. the salesperson of the wealth management company is explaining... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7 Architectural requirements | Editor's Note: Whether more architectural requirements are needed is FFS and this clause may be updated based on the solutions and conclusion of the present document. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.1 General | Editor's Note: This clause provides the generic architectural requirements identified. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.2 Service configuration requirements | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.2.1 Description | This clause specifies the service configuration requirements for MMTel Enablement service. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.2.2 Requirements | [AR-7.2.2-a] The MMTel Enablement service shall provide capability to control the downloading of data channel applications on UE by providing data channel application profile to UE.
[AR-7.2.2-b] The MMTel Enablement service shall provide capability for MMTel service provider to configure the application layer informati... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.3 Service enablement requirements | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.3.1 Description | This clause specifies the service enablement requirements for MMTel Enablement service. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 7.3.2 Requirements | [AR-7.3.2-a] The MMTel Enablement service shall provide capability for application without IMS capabilities to establish, modify or terminate a call with an Application supporting MMTel service. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8 Solutions | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1 Solution #1: eMMTel Enabler architecture | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.1 Description | This solution resolves the architecture of eMMTel Enabler. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2 eMMTel Enabler architecture model | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.1 General | Figure 8.1.2.1-1 shows the architectural model for the eMMTel Enabler.
The eMMTel Enabler Server is hosted within the PLMN operator network which supports the MMTel/eMMTel services capabilities exposure.
Figure 8.1.2.1-1: eMMTel Enabler architecture
The eMMTel functional entities on the UE and the server sides are eMMT... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2 Functional entities description | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2.1 General | The functional entities for eMMTel Enabler are described in the following subclauses.
Editor's note: The functionalities of the eMMTel client and the eMMTel Enabler server are FFS and to be updated per solution. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2.2 eMMTel Enabler Server | The eMMTel Enabler Server provides the server side functionalities corresponding to the eMMTel service.
The eMMTel Enabler Server supports:
- the Application Server and Controlling Application Server to discover, to authenticate and to get authorization the MMTel/eMMTel service APIs provided by the eMMTel Enabler serve... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2.3 eMMTel Client | The eMMTel Client provide the client side functionality needed in eMMTel service.
The eMMTel Client interact with DCMTSI Client in the same UE to control the downloading behavior on DCMTSI Client based on the data channel application profiles provided by the eMMTel Enabler Server.
NOTE 1: the DCMTSI client is responsib... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2.4 Application Server | The Application Server communicates with the eMMTel Enabler server over the eMMTel-2 reference point to invoke the eMMTel service related capabilities to communicate with the UE. It may also communicate with Application Client to provide Application specific logic.
NOTE: The functionalities of the Application Server is... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2.2.2.5 Controlling Application Server | The Controlling Application Server is a specific Application Server that only used by the eMMTel service provider, i.,e. MNO, to manage the necessary information, e.g. data channel application profiles, needed in eMMTel service. It communicates with the eMMTel Enabler server over the eMMTel-3 reference point to invoke ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.2.6 Application Client | The Application Client is an entity in the application layer to implement and perform the application service logic for its own service.
NOTE: The Application Client can be the data channel application client. The functionalities of the Application Client is out of scope of the present document. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3 Reference points | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3.1 General | The reference points for eMMTel Enabler are described in the following subclauses.
Editor's note: The functions of the reference points are FFS and to be updated per solution. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3.2 eMMTel-1 (between the eMMTel client and the eMMTel Enabler server) | The eMMTel-1 reference point supports the interactions between a eMMTel client and the corresponding eMMTel Enabler server. This reference point supports the necessary application layer interactions needed in eMMTel service. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3.3 eMMTel-2 (between the eMMTel Enabler server and the Application Server) | The interactions between the Application Server and the underlying network are provided by the eMMTel Enabler server via eMMTel-2 reference point to ensure the security access of the underlying network. This reference point supports the Application Server to discover eMMTel service APIs, to authenticate, to get authori... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3.4 eMMTel-3 (between the eMMTel Enabler server and the Controlling Application Server) | The interactions between the eMMTel Enabler server and the Controlling Application Server are referred to eMMTel-3 reference point. This reference point supports the Controlling Application Server to manage the necessary information needed in eMMTel service. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.1.2.3.5 App-1 (between the Application Client and the Application Server) | The App-1reference point supports the communication between Application Client and Application Server to provide the Data Channel Application specific logic.
NOTE: The functionalities of the App-1 reference point is out of scope of the present document. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2 Solution #2: Application calling service between application and DCMTSI client | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2.1 Description | This solution resolves Key Issue #1 and Key Issue #3 about Application calling service between application and DCMTSI client via eMMtel enabler.
IMS capability exposure is being discussed in SA2, IMS Core network exposures create/update/release an IMS session with data channel capability via N33/DC4/MDC2/MDC3. In this ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2.2 Procedures | 8.2.2.1 Service Enabler Description
Figure 8.2.2.1-1: Reference Architecture for the Nemes Services
The eMMTel Enabler Server provides the following services to the application:
- Control operations of Call with/without data channel media, such as initiating, modifying, terminating and querying a Call information, and
... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2.2.2 Establishing a Call with data channel media | Figure 8.2.2.2-1 below illustrates how to establish a Call with data channel media between application and DCMTSI client. The eMMTel Enabler Server acts as a DC AS based on SA2's IMS exposure capability architecture, according to the session creation API invoked by the eMMTel Enabler Server, the IMS network initiates a... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.2.3 Impacts on Existing Nodes and Functionality | In this solution, the procedures use the basic capability exposured by IMS core which is under studied by SA2. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.3 Solution #3: downloading of data channel application profiles to UE | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.3.1 Description | This solution resolves Key Issue #2 about downloading data channel application to UE.
In this procedure, a list of necessary information regarding each Data Channel Application is stored in the eMMTel Enabler Server based on the configuration information set by data channel application provider or eMMTel service provid... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.3.2 Procedures | The eMMTel Client in the UE sends an application request messages to eMMTel Enabler Server to request the data channel application profile list is illustrated in Figure 8.3.2.1-2.
NOTE 1: The eMMTel Client interact with DCMTSI Client in the same UE to control the downloading behavior on DCMTSI Client based on the data ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.3.3 Impacts on Existing Nodes and Functionality | This solution detailed specifies the procedures of downloading Data Channel Application profile list to UE.
In this solution, the procedure is handled by eMMTel client and eMMTel Enabler Server and goes over the top of the DCSF. Therefore, this solution has no impact on 5GC/IMS. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.4 Solution #4: configuration of DC application profile | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.4.1 Description | This solution resolves the 2nd requirement in Key Issue #2 about downloading data channel application to UE, i.e. the application layer should support to provide and control the capability to data channel application provider to set this indicator.
In this solution, the eMMTel Enabler Server provides APIs to the Contro... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.4.2 Procedures | The procedure of Controlling Application Server configuring DC application profile is illustrated in figure 8.4.2-1.
Pre-conditions:
1) The Controlling Application Server has connected to the serving network successfully.
2). Both the Controlling Application Serverand eMMTel Enabler Server have been configured with the... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.4.3 Impacts on Existing Nodes and Functionality | This solution detailed specified the procedures of configuration of DC application profile.
The DC Application Profiles are also handled by eMMTel Enabler Server therefore there is no impacts on existing nodes and functionality. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.5 Solution #5:updating of data channel application profiles to UE | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.5.1 Description | This solution resolves Key Issue #2 about download data channel application to UE.
There are two modes in this procedure: one is the eMMTel Enabler Server notifies the eMMTel Client in the UE to send application request messages to the eMMTel Enabler Server to request the profiles of data channel applications; another ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.5.2 Procedures | 8.5.2.1 The eMMTel Client request profiles based on notification from the eMMTel Enabler Server
The difference between this procedure and solution#3 of the current specification was the first step which indicates the eMMTel Enabler Server can notify the eMMTel Client in the UE to send application request messages to th... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.5.3 Impacts on Existing Nodes and Functionality | In this solution, the procedure is handled by eMMTel client and eMMTel Enabler Server and go over the top of the DCSF. Therefore, this solution has no impact on 5GC/IMS.
8.6 Solution #6: Third-Party Call service
8.6.1 Description
This solution resolves Key Issue #1 about Third-Party Call service via eMMTel Enabler Serv... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.6.2.2 Establishing a Third-Party Call | Figure 8.6.2.2-1 below illustrates how to establish a Third-Party call between two users. the eMMTel Enabler Server acts as a middle layer between the Third-Party call application and IMS Core network, according to the session creation API invoked by the eMMTel Enabler Server, the IMS network initiates an IMS session w... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.6.2.3 Terminating a Third-Party Call with data channel media | Figure 8.6.2.3-1 below illustrate how to terminate a Third-Party Call between two users. The terminating procedure in Figure 8.6.2.3-1 is triggered by the Third-Party call application invoking a release session API provided by the eMMTel Enabler Server.
Figure 8.6.2.3-1: Terminating a Third-Party Call
1. The 3rd Party ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.6.2.4 Modifying a Third-Party Call without data channel media to add data channel media | Figure 8.6.2.4-1 below illustrates how to modify an established Call without data channel media between two users to add data channel media. It is assumed that a Call with audio and video media has established between two users.
Figure 8.6.2.4-1: Modifying a Call to add data channel media
1. The 3rd Party call applicat... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.8 Solution #8: Multiple call control handling coordination among different Application Servers | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.8.1 Description | This solution resolves Key Issue #5 about multiple call control handling coordination among different Application Servers.
In this solution, when receiving call control request from multiple Application Servers, the eMMTel Enabler Server provides call control handling consolidation, e.g. to merge same control commands,... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.8.2 Procedures | The procedure of multiple call control handling coordination among different Application Servers is illustrated in figure 8.8.2-1.
Pre-conditions:
1) The Application Servers and eMMTel Enabler Server have been configured with the necessary credentials to enable authenticating one another.
2) The call control handling p... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.8.3 Impacts on Existing Nodes and Functionality | Editor's note: This solution depends on the capabilities provided by IMS for call control interactions and call event exposure which are developing by SA2 in Rel-19. The impacts on existing nodes and functionality is FFS.
8.9 Solution #9: Supporting the multiparty service with the data channel capability
8.9.1 Descript... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.9.2 Procedures | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.9.2.1 Service Enabler Description | Figure 8.9.2.1-1: Reference Architecture for the Nemes Services
The eMMTel Enabler Server provides the following services to the application:
- Control operations of multiparty Call with data channel media, such as initiating, modifying, terminating;
- Subscribe and unsubscribe to multiparty Call events of the specific... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.10 Solution #10: providing application layer caller information to callee | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.10.1 Description | This solution resolves Key Issue #4 about support of providing application layer caller information to callee. This solution is a application solution which will not impact the IMS/5GC.
NOTE1: In this release, this solution only applies to the call between MMTel call between application with IMS capability and applicat... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.10.2 Procedures | Upon receiving an incoming mmtel session, the eMMTel Client in the UE sends an application request messages to eMMTel Enabler Server to fetch the caller information from eMMTel Enabler Server via eMMTel-1 reference point. The procedure is illustrated in Figure 8.10.2-1.
Pre-condition:
a. The application layer caller in... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.10.3 Impacts on Existing Nodes and Functionality | This solution depends on the interaction between eMMTel Client in the UE and the DCMTSI client in the same UE. This interaction is internal interaction in the dialler application on the UE and will not impact the existing 5GC/IMS.
Editor's note: whether DCMTSI client can be utilized for the eMMTel operations is FFS. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.11 Solution #11: configuration of application layer caller information on MMTel Enabler server |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.