hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.1 General
| This subclause contains procedures for ad hoc group call across a one or more MCPTT systems, and associated functions such as emergency call, Imminent peril call, broadcast call and others.
The ad hoc group calls can use the participants list provided by either an initiator of the call or MCPTT server. The MCPTT serve... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.2 Information flows
| 10.19.2.1 Ad hoc group call request (MCPTT client – MCPTT server)
Table 10.19.2.1-1 describes the information flow ad hoc group call request from the MCPTT client to the MCPTT server.
Table 10.19.2.1-1: Ad hoc group call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.2.15 Ad hoc group call add user notification (MCPTT server – MCPTT server)
| Table 10.19.2.15 -1 describes the information flow Ad hoc group call add user notification from one MCPTT server to another MCPTT server. This notification is to provide the list of MCPTT IDs meeting the criteria specified in the ad hoc group communication get userlist request from one MCPTT server to another MCPTT ser... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.2.16 Ad hoc group call remove user notification (MCPTT server – MCPTT server)
| Table 10.19.2.16-1 describes the information flow Ad hoc group call remove user notification from one MCPTT server to another MCPTT server. This notification is to provide the list of MCPTT IDs no longer meeting the criteria specified in the ad hoc group communication get userlist request from one MCPTT server to anoth... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.2.17 Ad hoc group call release notification (MCPTT server – MCPTT server)
| Table 10.19.17 -1 describes the information flow Ad hoc group call release notification from one MCPTT server to another MCPTT server. This notification is to indicate to stop evaluating the criteria to determine the participants list if another MCPTT server is having the criteria specified in the ad hoc group communic... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3 Procedures
| 10.19.3.1 Ad hoc group call procedures in single MCPTT system
10.19.3.1.1 Ad hoc group call setup
Figure 10.19.3.1.1-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user.
Pre-conditions:
1. The authorized user at MCPTT client 1 wants to invite MCPTT users at MCPTT client 2, MCPT... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.1.8.1 General
| Call forwarding of MCPTT ad hoc group calls allows users to configure forwarding of incoming ad hoc group call requests (with or without Floor control) to another MCPTT user depending on the following conditions:
- Immediate
- No answer within a configured period (manual commencement mode)
- Based on manual user inp... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.2 Ad hoc group call involving multiple MC systems
| 10.19.3.2.1 Procedure for ad hoc group call setup – Participants list provided by the Initiator
Figure 10.19.3.2.1-1 illustrates the procedure for ad hoc group call setup procedure initiated by an authorized user wherein either a list of participants or an ad hoc group ID from an ad hoc group emergency alert is provid... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.2.4 Modification of ad hoc group call participants by the MCPTT server
| Figure 10.19.3.2.4-1 below illustrates the MCPTT server modifying the ad hoc group call participants procedure involving multiple MCPTT systems.
Pre-conditions:
1. The MCPTT user at MCPTT client 1 is authorized to initate ad hoc group call.
2. The MCPTT server 1 of the primary and MCPTT server 2 of the partner MCPT... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.2.8.1 General
| Call forwarding of MCPTT ad hoc group calls involving multiple MCPTT systems allows users to configure forwarding of incoming ad hoc group call requests (with or without Floor control) to another MCPTT user in a partner MC system under the same conditions as defined for the single MCPTT system scenario in clause 10.19.... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.2.8.2 Call forwarding of an ad hoc group call towards a partner MCPTT system
| Figure 10.19.3.2.8.2-1 below illustrates the ad hoc group call setup procedure initiated by an authorized user when call forwarding of the ad hoc group call is applied and a target MCPTT user is in a partner MCPTT system.
NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when us... |
85bf19f2724bd70687927dc10941722c | 23.379 | 10.19.3.2.8.3 Call forwarding of an ad hoc group call occurring in a partner MCPTT system
| Figure 10.19.3.2.8.3-1 below illustrates the ad hoc group call setup procedure when a target MCPTT user is in a partner MCPTT system and call forwarding initiated by an authorized user occurs in the partner MCPTT system.
NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when usi... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 1 Scope
| The present document specifies the application layer architecture and procedures to support the MMTel service, and also specifies the service enabler layer capability exposure procedures and related APIs for enablement aspects of MMTel service
This work takes into consideration the existing stage 1 and stage 2 work wi... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 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.
-... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 3 Definitions of terms, symbols and abbreviations
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 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].
MMTel service: An MTSI service as specified in 3GPP TS 26.114 [4] with or without Data channel supp... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 3.2 Symbols
| Void
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 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
DCAR Data Channel Application Repository
DCMTSI Data Cha... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 4 Overview
| The MMTel Enabler provides the Application enablement for MMTel service, mainly including the following aspects:
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 1 DC Application management: providing the management capabilities of Data Channel Applications and data channel application profile to PLMN operators which provide MMTel service with IMS Data Channel
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 2 DC Application downloading control: providing the capabilities to control the downloading of Data Channel applications on UE to PLMN operators which provide MMTel service with IMS Data Channel. The downloading is controlled by the data channel application profile downloaded to the UE.
| 3 usage of MMTel service: providing capabilities to application providers/Vertical service provider to use MMTel service including:
a. call between application and DCMTSI client:
b. Third-Party Call;
c. Person-to-Application (P2A) Application Data Channel; and
d. Application-to-Person (A2P) Application Data Channe... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5 Architectural requirements
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.1 General
| This clause specifies architectural requirements for MMTel Enabler.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.2 Data Channel Application management requirements
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.2.1 Description
| This clause specifies the Data Channel Application management requirements for MMTel Enabler.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.2.2 Requirements
| [AR-5.2.2-a] The MMTel Enabler shall provide capability for MMTel service provider to upload, update and delete the Data Channel applications on DCAR via MMTel Enabler .
[AR-5.2.2-b] The MMTel Enabler shall provide capability for MMTel service provider to configure, update, get and delete the Data Channel application ... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.3 MMTel service enablement requirements
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.3.1 Description
| This clause specifies the MMTel service enablement requirements for MMTel Enabler.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 5.3.2 Requirements
| [AR-5.3.2-a] The MMTel Enabler shall provide capability for application without IMS capabilities to establish, modify or terminate a call with an Application supporting MMTel service.
[AR-5.3.2-b] The MMTel Enabler shall provide capability for application providers/Vertical service provider to use MMTel service includ... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6 Architecture
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.1 General
| This clause specifies the architecture of MMTel Enabler.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.2 MMTel Enabler architecture
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.2.1 General
| Figure 6.2-1 shows the MMTel Enabler architecture.
In this release, the MMTel Enabler Server is hosted within the PLMN operator network which supports the MMTel services capabilities exposure.
Figure 6.2.1-1: MMTel Enabler architecture
The MMTel functional entities on the UE and the server sides are MMTel Enable... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.2.2 MMTel Enabler Server architecture model supporting IMS Session Management
| The MMTel Enabler Server provides MMTel services capabilities including IMS Session Management capabilities and Data Channel related capabilities to Application Server.
NOTE 1: The MMTel Enabler Server architecture model supporting IMS Session Management will be updated after the IMS Session management capabilities p... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3 Functional entities
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.1 General
| The functional entities for MMTel Enabler are described in the following subclauses.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.2 MMTel Enabler Server
| The MMTel Enabler Server provides the server side functionalities corresponding to the MMTel service.
The MMTel Enabler Server supports:
- the Application Server and Controlling Application Server to discover, to authenticate and to get authorization the MMTel/MMTel service APIs provided by the MMTel Enabler Server;... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.3 MMTel Enabler Client
| The MMTel Enabler Client provide the client side functionality needed in MMTel service. The MMTel enabler client is not IMS enabled and therefore it interacts with DCMTSI Client in the same UE to control the downloading behavior on DCMTSI Client based on the DC application profiles provided by the MMTel Enabler Server.... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.4 Application Server
| The Application Server communicates with the MMTel Enabler Server over the MMTel-2 reference point to invoke the MMTel service related capabilities to communicate with the UE, e.g. establishes a MMTel session with or without IMS data channel to the UE, or establishes an application data channel to the UE. It may also c... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.5 Controlling Application Server
| The Controlling Application Server is a specific Application Server that is only used by the MMTel service provider, i.e. MNO, to manage the service configuration related information, e.g. DC application profiles, needed in MMTel service. It communicates with the MMTel Enabler Server over the MMTel-3 reference point to... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.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.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.7 SEAL Client
| The following SEAL Clients for MMTel enablement service are supported:
- Notification management client as specified in clause 17 of TS 23.434 [6];
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.3.8 SEAL server
| The following SEAL servers for MMTel enablement service are supported:
- Notification management server as specified in clause 17 of TS 23.434 [6];
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4 Reference points
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.1 General
| The reference points for MMTel Enabler are described in the following subclauses.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.2 MMTel-1 (between the MMTel Enabler Client and the MMTel Enabler Server)
| The MMTel-1 reference point supports the interactions between a MMTel Enabler Client and the corresponding MMTel Enabler Server. This reference point supports:
- the MMTel Enabler Client to download the DC application profile from MMTel Enabler Server;
- the MMTel Enabler Server to notify the MMTel Enabler Client in... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.3 MMTel-2 (between the MMTel Enabler Server and the Application Server)
| The interactions between the Application Server and the underlying network are provided by the MMTel Enabler Server via MMTel-2 reference point to ensure the security access of the underlying network. This reference point supports:
- the Application Server to discover MMTel service APIs, to authenticate, to get author... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.4 MMTel-3 (between the MMTel Enabler Server and the Controlling Application Server)
| The interactions between the MMTel Enabler Server and the Controlling Application Server are referred to MMTel-3 reference point. This reference point supports:
- the Controlling Application Server to manage the service configuration related information needed in MMTel service; and
- the Controlling Application Serv... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.5 MMTel-4 (between the MMTel Enabler Client and the DCMTSI Client)
| The interaction between MMTel Enabler Client and DCMTSI Client is referred to MMTel-4 reference point. This reference point is internal interaction in the dialler application on the UE and implementation specific.
NOTE: The functionalities of the MMTel-4 reference point is out of scope of the present document.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.6 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.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.7 SEAL-C
| The following SEAL-C reference points for MMTel enablement service are supported:
- NM-C reference point for notification management as specified in 3GPP TS 23.434 [6];
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.8 SEAL-S
| The following SEAL-S reference points for MMTel enablement service are supported:
- NM-S reference point for notification management as specified in 3GPP TS 23.434 [6];
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 6.4.9 SEAL-UU
| The following SEAL-UU reference points for MMTel enablement service are supported:
- NM-UU reference point for notification management as specified in 3GPP TS 23.434 [6];
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 7 Identities
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 7.1 General
| The following clauses list identities that are used in this technical specification.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 7.2 Application ID (APPID)
| The APPID is a globally unique value that identifies a Data Channel Application. It is assigned by the MMTel Enabler Server. The value of this IE is also used to set the "req-app-id" parameter in "a=3gpp-req-app" media-level SDP attribute as specified in 3GPP TS 26.114 [4] when the application requests application data... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 7.3 MMTel Enabler Client ID (MMTECID)
| The MMTECID is a used to identify an MMTel Enabler Client within the MMTel Service. Its value is the same as the identity of the DCMTSI Client that interacts with the MMTel Enabler Client.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8 Procedures and information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.1 General
| This clause provides procedures and information flows necessary for application enablement aspects for MMTel including information elements used in the procedures.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2 DC application and profile management
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.1 General
| The following clauses specify procedures and information flows for DC application and profile management.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2 DC application and profile configuration
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2.1 General
| DC application and profile configuration enables a Controlling Application Server to configure the DC application and profile with the MMTel Enabler Server.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2.2 Procedure
| Figure 8.2.2.2-1 illustrates the DC application and profile configuration procedure.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and mutual authentica... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2.3 Information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2.3.1 DC application and profile configuration request
| Table 8.2.2.3.1-1 describes information elements for the DC application and profile configuration request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.2.3.1-1: Information elements in DC application and profile configuration request
Information element
Status
Description
Requester... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.2.3.2 DC application and profile configuration response
| Table 8.2.2.3.2-1 describes information elements for the DC Application and profile configuration response from the MMTel Enabler Server.
Table 8.2.2.3.2-1: Information elements for DC application and profile configuration response
Information element
Status
Description
DC application and profile configuration res... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3 DC application and profile update
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3.1 General
| DC application and profile update enables a Controlling Application Server to update the DC application and profile with the MMTel Enabler Server.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3.2 Procedure
| Figure 8.2.3.2-1 illustrates the DC application and profile update procedure.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and mutual authentication is... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3.3 Information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3.3.1 DC application and profile update request
| Table 8.2.3.3.1-1 describes information elements for the DC application and profile update request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.3.3.1-1: Information elements in DC application and profile update request
Information element
Status
Description
Requester Identity
M
... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.3.3.2 DC application and profile update response
| Table 8.2.3.3.2-1 describes information elements for the DC application and profile update response from the MMTel Enabler Server.
Table 8.2.3.3.2-1: Information elements for DC application and profile update response
Information element
Status
Description
DC application and profile update response list
M
A list... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4 DC application deletion
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4.1 General
| DC application deletion enables a Controlling Application Server to delete DC application with the MMTel Enabler Server.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4.2 Procedure
| Figure 8.2.4.2-1 illustrates the DC application deletion procedure.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and configured with the necessary cred... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4.3 Information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4.3.1 DC Application delete request
| Table 8.2.4.3.1-1 describes information elements for the DC Application delete request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.4.3.1-1: Information elements in DC Application delete request
Information element
Status
Description
Requester Identity
M
The identity of the DC A... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.4.3.2 DC Application delete response
| Table 8.2.4.3.2-1 describes information elements for the DC Application delete response from the MMTel Enabler Server.
Table 8.2.4.3.2-1: Information elements for DC Application delete response
Information element
Status
Description
DC Application delete response list
M
A list of Application deletion response. T... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5 Getting DC application profile information
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5.1 General
| Getting DC application profile information enables a Controlling Application Server to get the DC application profile information from the MMTel Enabler Server.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5.2 Procedure
| Figure 8.2.5.2-1 illustrates the procedure of getting DC application profile information.
Pre-conditions:
1. The Controlling Application Server has connected to the serving network successfully.
2. Both the Controlling Application Server and MMTel Enabler Server have established a secured connection and mutual authe... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5.3 Information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5.3.1 Getting DC application profile information request
| Table 8.2.5.3.1-1 describes information elements for the Getting DC application profile information request from the Controlling Application Server to the MMTel Enabler Server.
Table 8.2.5.3.1-1: Information elements in Getting DC application profile information request
Information element
Status
Description
Reque... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.2.5.3.2 Getting DC application profile information response
| Table 8.2.5.3.2-1 describes information elements for the Getting DC application profile information response from the MMTel Enabler Server.
Table 8.2.5.3.2-1: Information elements in Getting DC application profile information response
Information element
Status
Description
Successful response
O
Indicates that th... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3 Control the downloading of data channel applications
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.1 General
| The following clauses specify procedures and information flows for Controlling of the data channel applications downloading.
|
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2 DC application profiles downloading on UE
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.1 General
| Application profiles downloading enables a MMTel Enabler Client to download the DC application profile from MMTel Enabler Server and use it to control the downloading behavior of the DCMTSI Client in the same UE. This procedure is a detailed HTTP interaction procedure in the bootstrap data channel which established as ... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.2 Procedure
| Figure 8.3.2.2-1 illustrates the DC application profiles downloading procedure.
Pre-conditions:
1. The bootstrap data channels between UE and MF have been established as specified in Annex AC.7.1 of 3GPP TS 23.228 [3].
NOTE 1: In an implementation, the DCSF can support the DC application profile functionality of MMT... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.3 Information flows
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.3.1 Get Root application request
| Table 8.3.2.3.1-1 describes information elements for the Get Root application request from the MMTel Enabler Client to the MMTel Enabler Server.
Table 8.3.2.3.1-1: Information elements in Get Root application request
Information element
Status
Description
UE Information (see NOTE)
M
The UE related information re... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.3.2 Get Root application response
| Table 8.3.2.3.2-1 describes information elements for the Get Root application response from the MMTel Enabler Server to the MMTel Enabler Client.
Table 8.3.2.3.2-1: Information elements for Get Root application response
Information element
Status
Description
Result
M
Indicates the success or failure of Get Root ... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.3.3 Get DC application profile List request
| Table 8.3.2.3.3-1 describes information elements for the Get DC application profile List request from the MMTel Enabler Client to the MMTel Enabler Server.
Table 8.3.2.1-3: Information elements in Get DC application profile List request
Information element
Status
Description
MMTel Enabler Client version (see NOTE)... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.2.3.4 Get DC application profile List response
| Table 8.3.2.3.4-1 describes information elements for the Get DC application profile List response from the MMTel Enabler Server to the MMTel Enabler Client.
Table 8.3.2.3.4-1: Information elements in Get DC application profile List response
Information element
Status
Description
DC Application profile list
M
A l... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.3 DC application profiles updating on UE
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.3.1 General
| There are two modes in this procedure:
the MMTel Enabler Server notifies the MMTel Enabler Client in the UE to send application request messages to the MMTel Enabler Server to request the profiles of data channel applications;
the MMTel Enabler Server sends the profiles to the UE directly after the UE subscribes to... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.3.2 Procedure
| |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.3.2.1 The MMTel Enabler Client request DC application profiles based on notification
| The MMTel Enabler Server can notify the MMTel Enabler Client in the UE to send application request messages to the MMTel Enabler Server to request the DC application profiles, the detailed procedure is illustrated in Figure 8.3.3.2.1-1.
NOTE: The MMTel Enabler Server can instruct the MMTel Enabler Client to request ro... |
8d3dfbdf4c4d4401221ddf8bde92f8eb | 23.392 | 8.3.3.2.2 The MMTel Enabler Server notifies the DC application profile to the MMTel Enabler Client
| The MMTel Enabler Server notifies the DC application profiles to the MMTel Enabler Client is illustrated in Figure 8.3.3.2.2-1.
Pre-condition:
1. The bootstrap data channels have been established as specified in 3GPP TS 23.228 [3].
Figure 8.3.3.2.2-1: MMTel Enabler Server notifies the DC application profile list... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.