hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 of application and profile update response.
This list contains a response for each DC application and profile. The detailed information is listed in Table 8.2.3.3.2-2.
Table 8.2.3.3.2-2: Information elements in DC application and profile update response list
Information element
Status
Description
Successful response
O
Indicates the DC application and profile update resquest was successful.
Failure response
O
Indicates that the DC application and profile update resquest failed
> Cause
O
Indicates the cause of DC application and profile update resquest failure.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.4 DC application deletion
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.4.1 General
|
DC application deletion enables a Controlling Application Server to delete DC application with the MMTel Enabler Server.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 credentials to enable authenticating one another.
Figure 8.2.4.2-1: DC application deletion
1. The Controlling Application Server sends a DC Application delete request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.2.4.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server initiates authentication procedures with the Requester Identity. If the registration is successful, the MMTel Enabler Server requests the DCAR to delete the DC application and profile (DC applications and profile need to be deleted at the same time) and delete the mapping of APPID and DC application profile.
3. The MMTel Enabler Server deletes the DC application and profile on DCAR.
4. The MMTel Enabler Server sends a DC Application delete response to the Controlling Application Server. The response message includes information elements as specified in clause 8.2.4.3.2.
Editor's note: The detailed interactions between the MMTel Enabler Server and DCAR are FFS.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.4.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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 Application provider
(VAL service provider) performing the request.
Security credentials
O
Security information required by the MMTel Enabler Server.
Number of DC Application included
M
Indicates total number of DC Application included in this request
List of APPID
M
List of identifiers of the DC application to be deleted.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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. The detailed information is listed in Table 8.2.4.3.2-2.
Table 8.2.4.3.2-2: Information elements in DC Application delete response list
Information element
Status
Description
Successful response
O
Indicates the deletion of the DC Application was successful
Failure response
O
Indicates the deletion of the DC Application was failed
> Cause
O
Indicates the cause of failure
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.5 Getting DC application profile information
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 configured with the necessary credentials to enable authenticating one another.
Figure 8.2.5.2-1: Getting DC application profile information
1. The Controlling Application Server sends a DC application and profile information retrieval request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.2.5.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server initiates authentication procedures with the Requester Identity. If the registration is successful, the MMTel Enabler Server gets the DC application Profile information based on the APPID included in the Getting DC application profile information request.
3. The MMTel Enabler Server sends a Getting DC application profile information response to the Controlling Application Server. The response message includes information elements as specified in clause 8.2.5.3.2.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.2.5.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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
Requester Identity
M
The identity of the DC Application provider
(VAL service provider) performing the request.
Security credentials
O
Security information required by the MMTel Enabler Server.
Number of DC Application included
M
Indicates total number of DC Application included in this request
APPID list
M
A list of APPID for the request.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 the Getting DC application profile information request was successful.
> List of DC application profile information
O
List of DC application profile information as defined in Table 8.2.2.3.1-2.
Failure response
O
Indicates that the Getting DC application profile information request failed.
> Cause
O
Indicates the cause of Getting DC application profile information request failure.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3 Control the downloading of data channel applications
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.1 General
|
The following clauses specify procedures and information flows for Controlling of the data channel applications downloading.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.2 DC application profiles downloading on UE
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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 on DCMTSI Client in the same UE. This procedure is a detailed HTTP interaction procedure in the bootstrap data channel which established as per Annex AC.7.1
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 have been established as specified in 3GPP TS 23.228 [3].
Figure 8.3.2.2-1: MMTel Enabler Client in the UE requests the DC application profile list
1. The MMTel Enabler Client in the UE sends a Get Root application request to MMTel Enabler Server to get the Root application. The request message includes information elements as specified in Table 8.3.2.3.1-1. The application type is used by MMTel Enabler Server to suggest DC applications for download.
NOTE 1: In a implementation, the DCSF may support the DC application profile functionality of MMTel Enabler Server function, the DCSF may also interact with the MMTel Enabler Server to support this procedure, i.e. The MMTel Enabler Client sends a request to the DCSF, which then sends the request to the MMTel Enabler Server. The response in the opposite direction is also sent to the MMTel Enabler Client through the DCSF.
NOTE 2: The interaction between DCSF and MMTel Enabler Server is implementation specific in this release.
2. The MMTel Enabler Server checks whether the Root application version included in the Get Root application request is the newest version of the Root application. If the Root application version IE is not included, the Root application version is not considered as newest.
3. The MMTel Enabler Server sends a Get Root application response to the MMTel Enabler Client in the UE. The response message includes information elements as specified in Table 8.3.2.3.2-1.
If Root application is locally stored in the MMTel Enabler Client, validity of the application will be updated to the value received in Root application validity IE.
NOTE 3: When service provider wants the UE to delete the stored Root application, the response message includes negative value in the Root application validity IE.
NOTE 4: The root application can also be implementation specific.
4. The MMTel Enabler Client in the UE send a Get DC application profile List request to MMTel Enabler Server to get the DC application profile list available for this user. The request message includes information elements as specified in Table 8.3.2.3.3-1.
5. The MMTel Enabler Server sends a Get DC application profile List response to the MMTel Enabler Client in the UE. The response message includes information elements as specified in Table 8.3.2.3.4-1. The response message includes list of Data Channel Application profile.
The MMTel Enabler Client locally stores the downloaded DC application profiles and displays the related application information from the DC application profile on the Root application. Users can select and download corresponding DC applications based on the profile information on the Root application. The MMTel Enabler Client may stores the downloaded DC Application which may be obsoleted in the condition of, e.g. the validity is expired, update available for application, etc.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.2.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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 required to identify the Root application (e.g. device type, device vendor, etc)
Root application version
O
The newest version of the Root application stored in the MMTel Enabler Client in the UE.
This IE presents if Root application is locally stored in the MMTel Enabler Client.
NOTE: The MMTel service provider can provide the MMTel Enabler Client with different Root application based on this IE.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 application request.
Update needed
M
Indicates whether the Root application is needed to be updated by the MMTel Enabler Client in the UE
Root application version
O
The newest version of the Root application.
This IE presents only if the Root application is needed to be downloaded or updated by the MMTel Enabler Client in the UE.
Root application validity
O
The validity of the Root application. This IE presents only if the Root application is needed to be downloaded or updated by the MMTel Enabler Client in the UE.
Root application (see NOTE)
O
The Root application provided by the MMTel
service provider, e.g. layout, and/or home page etc of the Data Channel Application list.
This IE presents if the update of the Root application in the UE is needed, i.e. the Root application version included in the Get Root application request is not equal to the newest version on the MMTel Enabler Server.
NOTE: The detailed information of this IE is implementation specific and out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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)
M
The version of MMTel Enabler Client
application type
O
type of application (e.g. emergency, conference, XR, etc.)
Begin index
O
The starting index of the first Data Channel Application required in the Data Channel Application list.
This IE presents if the requested Data Channel Application is not the first one in the Data Channel Application list, e.g. when the Data Channel Application list is needed to be shown in multiple pages, this IE is needed to be included when request the pages other than the first page.
The default value of this IE is 0 if this IE is absent.
Number of application profile required
O
The total number of DC application profiles required in this request
NOTE: The MMTel service provider can provide the MMTel Enabler Client with different DC application profile list based on this IE.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 list of DC application profiles available for this user. Each element in this list contains a DC application profile of this Data Channel Application.
The detailed information elements of DC application profile are listed in Table 8.3.2.1-5.
Table 8.3.2.3.4-2: Information elements in DC application profile
Information element
Status
Description
APPID
M
Identifier of the Data Channel Application
Application Name
O
Name of the Data Channel Application
Service Type
O
Service type of the Data Channel Application, used to help the user understand the type of services provided by the application
Application Icon
O
Icon of the Data Channel Application
Application Version
O
The newest version of the application.
Application Validity
O
The latest validity of the application.
Application Loading Phase
O
Indicates when this Data Channel Application is allowed to be used. The values of this IE include:
Precall only:the Data Channel Application is allowed to be used before the MMTel call session is established, i.e. after the 18x response is sent/received and before the 200 OK of the initial SIP INVITE request is sent/received.
Incall:the Data Channel Application is allowed to be used after the MMTel call session is established, i.e. after the 200 OK of the initial SIP INVITE request is sent/received.
Autoload (see NOTE 1)
O
Indicates whether this Data Channel Application is needed to be load to the UE automatically.
Autolaunch (see NOTE 1)
O
Indicates whether this Data Channel Application is needed to be downloaded to the UE and run automatically.
If Work Without Peer DC
O
Indicates whether this Data Channel Application can be used if Data Channel is not supported by the other party of the call.
Supported Scenario
O
Indicates supported media type required for this Data Channel Application. The values of this IE include:
Voice call only: this Data Channel Application can be used if and only if the corresponding call is a voice call.
Video call only: this Data Channel Application can be used if and only if the corresponding call is a video call.
Voice and video call: this Data Channel Application can be used in both voice call and video call.
Condition
O
Indicates whether this Data Channel Application can be used if under this condition. The values of this IE include but not limited:
Service area: the application is allowed to be used in a certain area.
Time period: the application is allowed to be used for a certain period of time.
3gpp Qos Hint
O
Indicates the QoS requirement of this Data Channel Application which is used to set the value of “a=3gpp-qos-hint” attribute in SDP for the data channel(s) used by the application.
PersonalDataCollection (see NOTE 2)
O
Indicates whether this Data Channel Application will collect the user personal data.
PersonalDataCollectionInfoURL (see NOTE 2)
O
URL to retrieve the description of the purpose of mandatory and optional personal data to be collected (along with related consent opt-in/opt-out procedures), their processing their protection etc.
NOTE 1: These IEs can be applied only if the specific service using this data channel application is agreed to be used by the user based on the subscription of this specific service, or explicitly agreed to be applied by the user on the UE.
NOTE 2: These IEs are mandatory when regulatory requirements request that the user has to be informed if the personal data are collected by the application and how they are treated.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.3 DC application profiles updating on UE
|
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 the profile notification.
The two detailed procedures of DC application profiles updating on UE and the related information flow are specified in clause 8.3.3.2 and 8.3.3.3.
NOTE : The updating procedures go over the top of DCSF. The detailed procedures to update data channel applications to the UE are out of scope of 3GPP TS 23.228 [3].
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.3.2 Procedure
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
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 root application and DC application profiles as required. e.g. root application version update, offline of a data channel application, etc.
Pre-condition:
1. The bootstrap data channels have been established as specified in 3GPP TS 23.228 [3].
Figure 8.3.3.2.1-1: MMTel Enabler Client request DC application profiles based on notification
1. The notification channel has been established between notification management client and notification management Server as specified clause 17.3.3 of TS 23.434 [6].
2. The MMTel Enabler Client subscribes to the MMTel Enabler Server for receiving notifications.
3. The MMTel Enabler Server sends a Root application and profile update notification to notify the MMTel Enabler Client in the UE to get the Root application or DC application profile. The Root application and profile update notification includes information elements as specified in Table 8.3.3.3.1-1.
The step 4 to step 8 are same as steps 1 through 5 in clause 8.3.2.2.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
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 to UE
1. The notification channel has been established between notification management client and notification management server as specified clause 17.3.3 of TS 23.434 [6].
2. The MMTel Enabler Client subscribes to the MMTel Enabler Server for receiving notifications.
3. The MMTel Enabler Server checks the provision of Root application and DC application profile list is needed, e.g. the UE has IMS DC capability, an application version or application profile update is available, etc.
NOTE: The detail additional checklists in this step are out of scope of the present document.
4. The MMTel Enabler Server sends a Root application notification message to the MMTel Enabler Client in the UE. The notification message includes information elements as specified in Table 8.3.3.3.2-1.
The MMTel Enabler Server sends a data channel DC application profile List notification to the MMTel Enabler Client in the UE. The notification message includes information elements are as same as the elements in Table 8.3.2.3.4-1.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.3.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.3.3.1 Root application and profile update notification
|
Table 8.3.3.3.1-1 describes information elements for the Root application and profile update notification from the MMTel Enabler Server to the MMTel Enabler Client.
Table 8.3.2.3.1-1: Information elements in Root application and profile update notification
Information element
Status
Description
Urgent
O
Indicates whether the operation is urgent to UE, i.e. whether the Root application and profile need to be updated immediately. E.g. the update of Root application and profile is urgent if the available DC Application for the user is changed
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.3.3.3.2 Root application notification
|
Table 8.3.3.3.2-1 describes information elements for the Root application notification from the MMTel Enabler Server to the MMTel Enabler Client.
Table 8.3.3.3.2-1: Information elements for Root application notification
Information element
Status
Description
Update needed
M
Indicates whether the Root application is needed to be updated by the MMTel Enabler Client in the UE
Root application version
O
The newest version of the Root application.
This IE presents only if the Root application is needed to be updated by the MMTel Enabler Client in the UE.
Root application (see NOTE)
O
The Root application provided by the MMTel service provider, e.g. layout, and/or home page etc. of the Data Channel Application list.
This IE presents if the update of the Root application in the UE is needed, i.e. the Root application version included in the Get Root application request is not equal to the newest version on the MMTel Enabler Server.
NOTE: The detailed information of this IE is implementation specific and out of scope of the present document.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4 Application calling enablement
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.1 General
|
The following clauses specify procedures and information flows for Application calling enablement.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2 Application calling service API with Data Channel capability
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.1 General
|
The MMTel Enabler Server exposes the Application calling service API with Data Channel capability to the Applications in order to support establishing a call between Application and DCMTSI client.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.2 Procedure
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.2.1 Establishing an Application Call with Data Channel capability between non-IMS application and DCMTSI client
|
Figure 8.4.2.2.1-1 illustrates the operation to establish an Application Call with Data Channel capability between non-IMS application and DCMTSI client.
Pre-conditions:
1. The Application is authorized to use Application calling service API provided by the MMTel Enabler Server.
2. The MMTel Enabler Server is authorized to use IMS DC capability APIs as defined in 3GPP TS 23.228 [3].
3. The MMTel Enabler Server is authorized to use OMA ThirdPartyCall API as specified in OMA-TS-REST_NetAPI_ThirdPartyCall [7].
Figure 8.4.2.2.1-1: Establishing a Application Call with Data Channel capability between non-IMS applications and DCMTSI client
1. The Application sends an Application Call with DC capability establishment request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.4.1.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server can utilize the OMA Third Party Call API [7] to establish a Call session with audio and/or video media as specified in OMA-TS-REST_NetAPI_ThirdPartyCall and obtain the result of the Third-Party Call establishment. The MMTel Enabler Server can also obtains the IMS Session ID associated with the Third Party Call as specified in RFC 7989 [7989], and handles the mapping between the OMA call session ID and the IMS session ID.
NOTE 1: The OMA call session ID attribute in the OMA Third Party Call API is generated by the entity implementing the OMA APIs, which is different from the IMS session Id.
3, The MMTel Enabler Server utilizes the DC update capability of the IMS core network to add DC media to the existing Application Call Session as specified in Annex AC of 3GPP TS 23.228 [3]. The IMS core network returns the update result.
3. The MMTel Enabler Server sends an Application Call establishment response to the Application. The response message includes information elements as specified in clause 8.4.1.3.2.
NOTE 2: In this release, the MMTel Enabler Server is deployed in the PLMN operator domain.
Editor's note: The flow will need to be updated once SA2 work is done to specify NEF exposure of IMS session management (Nnef_ImsSessionManagement).
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.3.1 Application Call establishment request
|
The information elements of Application Call establishment request are as same as the elements in Table 8.4.3.3.1-1.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.2.3.2 Application Call establishment response
|
The information elements of Application Call establishment response are as same as the elements in Table 8.4.3.3.2-1.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3 Third-Party Call service API with Data Channel capability
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.1 General
|
The MMTel Enabler Server exposes the Third-Party Call service API with Data Channel capability to the Vertical service provider in order to support establishing a call between two UEs.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.2 Procedure
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.2.1 Establishing a Third-Party Call with Data Channel capability
|
Figure 8.4.3.2.1-1 illustrates the operation to establish a Third-Party Call with Data Channel capability.
Pre-conditions:
1. The Vertical service provider is authorized to use Third-Party Call service API provided by the MMTel Enabler Server.
2. The MMTel Enabler Server is authorized to use the IMS DC capability APIs as defined in 3GPP TS 23.228 [3].
3. The MMTel Enabler Server is authorized to use OMA THIRD PARTY CALL API as specified in OMA-TS-REST_NetAPI_ThirdPartyCall [7].
Figure 8.4.3.2.1-1: Establishing a Third-Party Call with Data Channel capability
1. The Vertical service provider sends a Third-Party Call with DC capability establishment request to the MMTel Enabler Server. The request message includes information elements as specified in clause 8.4.3.3.1.
2. Upon receiving the request, the MMTel Enabler Server validates if the requester is authorized for the request, If the requester is authorized then the MMTel Enabler Server utilizes the OMA Third Party Call API [7] to establish a Third-Party Call session with audio and/or video media as specified in OMA-TS-REST_NetAPI_ThirdPartyCall and obtain the result of the Third Party Call establishment. The MMTel Enabler Server obtains IMS Session ID associated with the Third Party Call as specified in RFC 7989 [10],the OMA API call Session ID and handles the mapping between OMA call session ID and the IMS session ID
NOTE : The OMA call session ID attribute in the OMA Third Party Call API is generated by the entity implementing the OMA APIs, which is different from the IMS session Id.
3. the MMTel Enabler Server utilizes the DC update capability of the IMS core network to add DC media to the existing Third-Party Call Session as specified in 3GPP TS 23.228 [3], and the IMS core network returns the update result.
4. The MMTel Enabler Server sends a Third-Party Call with DC capability establishment response to the Vertical service provider. The response message includes information elements as specified in clause 8.4.3.3.2.
NOTE 2: In this release, the MMTel Enabler Server is deployed in the PLMN operator domain.
Editor's note: The flow will need to be updated once SA2 work is done to specify NEF exposure of IMS session management (Nnef_ImsSessionManagement).
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.3.1 Third-Party Call with DC capability establishment request
|
Table 8.4.3.3.1-1 describes information elements for the Third-Party Call with DC capability establishment request from the Application Server to the MMTel Enabler Server.
Table 8.3.2.3.1-1: Third-Party Call with DC capability establishment request
Information element
Status
Description
Related OMA API Element
Originating ID (see NOTE)
M
The identifier of the caller.
The first element in the participant list, which considered to denote the “A-Party” specified in OMA Third Party Call API [7]
Terminating ID (see NOTE)
M
The identifier of the callee.
The second element in the participant list, which considered to denote the “B-Party” specified in OMA Third Party Call API [7]
Media information
M
Identifier of one or more media type(s) which is expected to be used in the call, i.e. the media type(s) to be applied to the participants in the call session. In this IE, the media type(s) includes
a) audio;
b) video;
c) audio and video.
The detailed media information, e.g. the information included in the SDP of mmtel call session is negotiated by the underlying network.
If the parameter is absent, the media type(s) and detailed media information are all negotiated by the underlying network.
The mediaInfo of the CallSessionInformation specified in OMA Third Party Call API [7]
DC media information
O
Identifier of whether DC media is expected to be used in this call
N/A
Application Profile requested
O
The DC application profile expected to be used in this call
N/A
Notification information
M
The address where the call related notification, e.g. whether the call between UE A and UE B is established successfully or not, is sent to.
The callbackReference of the CallSessionInformation specified in OMA Third Party Call API [7]
NOTE: The Originating ID and Terminating ID may or may not be MSISDN based identifier, i.e. a private identifier in the Application domain,. If Originating ID or Terminating ID is not MSISDN based identifier, the MMTel Enabler Server will translate it into a routable ID in the IMS domain and record the mapping relationship between the Originating ID/Terminating ID and the routable ID.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.3.3.2 Third-Party Call with DC capability establishment response
|
Table 8.4.3.3.2-1 describes information elements for the Third-Party Call with DC capability establishment response from the Application Server to the MMTel Enabler Server.
Table 8.3.2.3.2-1: Third-Party Call with DC capability establishment response
Information element
Status
Description
Related OMA API Element
Call establishment result
M
Indication if the Call establishment is success or failure.
The HTTP response codes of the created call session as specified in OMA REST_NetAPI_Common [11]
Session ID (see NOTE 1)
O
The identifier of the call session.
The callSessionId as specified in OMA Third Party Call API [7]
Failure Cause (see NOTE 2)
O
The reason for failure
The Policy Exception and Service Exception fault as specified in OMA Third Party Call API [7]
Originating ID (see NOTE 3)
M
The identifier of the caller.
The first element in the participant list, which considered to denote the “A-Party” specified in OMA Third Party Call API [7]
Terminating ID (see NOTE 3)
M
The identifier of the callee.
The second element in the participant list, which considered to denote the “B-Party” specified in OMA Third Party Call API [7]
Media information
M
Identifier of one or more media type(s) which is expected to be used in the call, i.e. the media type(s) to be applied to the participants in the call session. In this IE, the media type(s) includes
a) audio;
b) video;
c) audio and video.
The detailed media information, e.g. the information included in the SDP of mmtel call session is negotiated by the underlying network.
If the parameter is absent, the media type(s) and detailed media information are all negotiated by the underlying network.
The mediaInfo of the CallSessionInformation specified in OMA Third Party Call API [7]
DC media information
O
Identifier of whether DC media is expected to be used in this call
N/A
Application Profile requested
O
The DC application profile expected to be used in this call
N/A
NOTE 1: This IE shall only be present when the Call establishment result is Success.
NOTE 2: This IE shall only be present when the Call establishment result is Failure.
NOTE 3: The Originating ID and Terminating ID may or may not be MSISDN based identifier, i.e. a private identifier in the Application domain,. If Originating ID or Terminating ID is not MSISDN based identifier, the MMTel Enabler Server will translate it into a routable ID in the IMS domain and record the mapping relationship between the Originating ID/Terminating ID and the routable ID.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4 Establishing an Application Call with Data Channel capability (A2P)
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.1 Procedure
|
Figure 8.4.4-1 illustrates the operation to establish an Application Call with Data Channel capability between the Application and the MMTel Enabler Server in order to add an A2P Data Channel to an existing IMS session of the user on UE1 in alignment with the A2P flow specified in 3GPP TS 23.228 [3].
Pre-conditions:
1. The Application can use DCH (supports the media set information for DCH) and is authorized to use the service API provided by the MMTel Enabler Server.
2. The MMTel Enabler Server is authorized to use IMS DC capability APIs as defined in 3GPP TS 23.228 [3].
3. The MMTel Enabler Server is authorized to use the NEF exposed IMS session management capabilities as specified in 3GPP TS 23.502 [12].
4. The MMTel Enabler Server is subscribed to the AEF (NEF) for IMS session events information e.g., media changes such as requested for the specific DCH Application, for a list of users.
NOTE: How the IMS session ID is provided by the NEF exposure of IMS events in 3GPP TS 23.502 [12] is out of scope of this specification.
5. The DCH Application Server is subscribed to the MMTel Enabler Server for events related to the DCH application.
6. An IMS MMTel session is ongoing for User (UE1) with another user who requests the DCH Application to provide some DCH media to the user on UE1.
Figure 8.4.4-1: Establishing a Application Call with Data Channel capability
1. The user sends a request, via the 5GC and IMS, to add DCH media for a specific DCH Application. The NEF notifies the MMTel Enabler Server of the new IMS session event for the for the media changes related to the DCH Application. The request includes parameters such as the session ID, MDC2 endpoint, A2P type.
2. The MMTel Enabler Server requests an IMS session update to the NEF, providing the Session ID and MDC2 endpoint address. The NEF propagates the request to the IMS core which sets the media operation. The NEF sends the response to the MMTel Enabler to the IMS session Update request.
3. The MMTel Enabler Server sends the response to the DCH Application Server including the Session ID for the Add media request.
4. Once the IMS system completed the media preparation for the IMS session, the NEF sends an IMS session management notification request to the MMTel Enabler Server with MDC2 resource information for the Session ID. The DCH Application Server responds (acknowledges) the MMTel Enabler Server notification.
5. The MMTel Enabler Server notifies the DCH Application Server of the MDC2 resource information for the Session ID.
6. The MMTel Enabler Server acknowledges the NEF notification.
Post-condition: The UE1 upon getting the updated IMS session information for the DCH media proceeds to download the DCH Application.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.2 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.2.1 Application Add Data Chanel media to UE1 session (A2P) request
|
Table 8.4.4.2.1-1: Application Add Data Chanel media to UE1 session (A2P) request
Information element
Status
Description
Data Channel APPID
M
The identifier of the DCH application
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Media resource information
O
The media information to be passed via the Data Chanel. It includes information described in 3GPP TS 23.502 [12] clause 5.2.6.40.
Application Profile requested
O
The DC application profile expected to be used in this call.
Notification address
M
The address where the call related notification, e.g. whether the call between UE A and UE B is established successfully or not, is sent to.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.2.2 Application Add Data Chanel media to UE1 session (A2P) response
|
Table 8.4.4.2.2-1: Application Add Data Chanel media (A2P) response
Information element
Status
Description
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Successful response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request was successful
Failure response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request has failed
> Cause
O
Indicates the cause of request failure
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.2.3 Notify Application of DCH media info (A2P) request
|
Table 8.4.4.2.3-1: Notify Application of DCH media info (A2P) request
Information element
Status
Description
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Notification address
M
The address where the call related notification, e.g. whether the call between UE A and UE B is established successfully or not, is sent to.
Media resource information
O
The media information to be passed via the Data Chanel. It includes information described in 3GPP TS 23.502 [12] clause 5.2.6.40.
Application Profile requested
O
The DC application profile expected to be used in this call.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.4.2.4 Notify Application of DCH media info (A2P) response
|
Table 8.4.4.2.4-1: Notify Application of DCH media info (A2P) response
Information element
Status
Description
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Successful response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request was successful
Failure response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request has failed
> Cause
O
Indicates the cause of request failure
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.5 Application calling service API with Data Channel capability
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.5.1 Procedure
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.5.1.1 Establishing an Application Call with Data Channel capability (P2A)
|
Figure 8.4.5.1.1-1 illustrates the operation to establish an Application Call with Data Channel capability between a user (on UE1) and a Data Chanel (DCH) Application via the MMTel Enabler Server.
Pre-conditions:
1. The Application can use DCH (supports the media set information for DCH) and is authorized to use the service API provided by the MMTel Enabler Server.
2. The MMTel Enabler Server is authorized to use IMS DC capability APIs as defined in 3GPP TS 23.228 [3].
3. The MMTel Enabler Server is authorized to use the NEF exposed IMS session management capabilities as specified in [8].
4. The MMTel Enabler Server is subscribed to the AEF (NEF) for IMS session events information for the specific DCH Application (using the DCH Application Called party ID).
NOTE: How the IMS session ID is provided by the NEF exposure of IMS events in 3GPP TS 23.502 [12] is out of scope of this specification.
5. The DCH Application Server is subscribed to the MMTel Enabler Server for events related to the DCH application.
6. An IMS MMTel session is ongoing for User (UE).
Figure 8.4.5.1.1-1: Establishing a Application Call with Data Channel capability (P2A)
1. The user (on UE1) sends a request, via the 5GC and IMS, to add DCH media for a specific DCH Application.
2. The P2A session establishment is handled via 5GC and IMS system.
3. NEF notifies the MMTel Enabler Server of the new IMS session event for the DCH Application.
4. The MMTel Enabler Server notifies the DCH Application Server of the new request for DCH media.
5. The DCH Application Server accepts the request and provides the MDC2 media resource requested.
6. The MMTel Enabler Server utilizes the IMS session update capability exposed by the NEF [8] to request addition of the DCH media to the existing IMS MMTel Call Session.
7. The NEF further interacts with the IMS system to request the DCH media addition to the ongoing MMTel session and IMS further handles this as specified in Annex AC of 3GPP TS 23.228 [3].
Post-condition: The Application data channel is activated.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.5.2 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.4.5.2.1 Notify DCH Application of MDC2 media (P2A) request
|
Table 8.4.5.2.1-1: Notify DCH Application of MDC2 media (P2A) request
Information element
Status
Description
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Media resource information
O
The MDC2 media information requested by the UE1 to be sent over the Data Chanel. It includes information described in 3GPP TS 23.502 [12] clause 5.2.6.40.
8.4.5.2.2 Notify DCH Application of MDC2 media (P2A) response
Table 8.4.5.2.2-1: Notify DCH Application of MDC2 media (P2A) response
Information element
Status
Description
Session ID
M
The session identifier of the session on which MMTel Enabler Server must add the new media.
Successful response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request was successful
Failure response
O
Indicates the Notificaiton of Application of DCH media info (A2P) request has failed
> Cause
O
Indicates the cause of request failure
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.5 Multiple call control handling coordination among different Application Servers
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.5.1 General
|
When receiving call control requests from multiple Application Servers, the MMTel Enabler Server provides call control handling consolidation and coordination.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.5.2 Procedure
|
Figure 8.5.2-1 illustrates the procedure of multiple call control handling coordination among different Application Servers.
Pre-conditions:
1. The Application Servers and MMTel Enabler Server have been configured with the necessary credentials to enable authenticating one another.
2. The call control handling policy (e.g. the priority of each Application Server) is pre-configured in MMTel Enabler Server.
3. Application Servers have completed call event subscription to MMTel Enabler Server and the MMTel Enabler Server subscribes the call event from DCSF/IMS core.
4. The MMTel Enabler Server is authorized to use IMS DC capability APIs as defined in 3GPP TS 23.228 [3].
Figure 8.5.2-1: Multiple call control handling coordination among different Application Servers
1. DCSF/IMS Core node sends call event notification, i,e, Nimsas_SessionEventControl_Notify as specifed in 3GPP TS 23.228 [3], to MMTel Enabler Server (e.g. SessionEstablishmentRequestEvent, MediaChangeRequestEvent., etc.).
2. The MMTel Enabler Server checks which Application Server has subscribed this call event notification.
3. The MMTel Enabler Server sends Call event notification to Application Server(s) which subscribed this call event notification. The Call event notification request includes information elements as specified in Annex AA.2.4.2 of 3GPP TS 23.228 [3].
4-5.Application Servers receive call event notification and sends Call control request (e.g. create new call session, terminate call session or call control, etc.) based on its own service logic. The Call control request includes information elements as specified in Annex AA.2.4.3 or Annex AA.2.4.4 of 3GPP TS 23.228 [3].
6. The MMTel Enabler Server receives call control requests from different Application Servers.It checks whether these call control requests are contradictory and makes call control handling decision based on service policy and service priority (e.g. if no conflict happens, to decide call control request execution sequence; if conflict happens, to deny call control request from certain AS with lower priority, etc.).
7-8.The MMTel Enabler Server sends call control responses to each Application Server based on the call control handling decision including that whether the call control request is accepted and the failure reason if the call control request is not accepted. The call control response includes information elements as specified in Annex AA.2.4.3 or Annex AA.2.4.4 of 3GPP TS 23.228 [3].
9. The MMTel Enabler Server sends call control requests decided in step 6 from Application Servers (or permitted Application Servers in conflict scenario) to DCSF/IMS core network by using Nimsas_MediaControl Service or Nimsas_ImsSessionManagement Service as specifed in 3GPP TS 23.228 [3].The DCSF/IMS core network sends a corresponding response (e.g, whether the call is established successfully or not) as specifed in 3GPP TS 23.228 [3] to the MMTel Enabler Server.
10. The MMTel Enabler Server sends the call control result notification request to the permitted Application Servers in conflict scenario decided in step 6. The call control result notification includes information elements as specified in clause 8.5.3.1. The Application Server sends the corresponding control result notification response to the MMTel Enabler Server.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.5.3 Information flows
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
8.5.3.1 Call control result notification
|
Table 8.5.3.1-1 describes information elements for call control result notification request from the MMTel Enabler Server to the Application server.
Table 8.5.3.1-1: Call control result notification request
Information element
Status
Description
Final result of the call control request
M
Indicates the final result of the call control request provided by the IMS
Media resource information set
O
If media resource information set is provided by IMS, include the media resource information set in this notification
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
9 Deployment Guideline
| |
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
9.1 General
|
This clause describes deployments of the functional model specified in clause 6.
|
b8be9e3ad9dc823e02fec5f1340281ad
|
23.392
|
9.2 MMTel Enabler server deployed in PLMN operator domain
|
The MMTel Enabler server is recommended to be deployed in the PLMN operator domain. Figure 9.2-1 illustrates the MMTel Enabler server deployed in PLMN operator domain. Figure 9.2-1: MMTel Enabler server deployed in PLMN operator domain The Application server can be deployed in PLMN operator domain or Application service provider domain and interacts with MMTel Enabler server via MMTel-2 reference point and MMTel-2e reference point respectively.The Application server deployed in PLMN operator domain, e.g. Application server 2 can only interact with the MMTel Enabler server deployed in the same PLMN operator domain, i.e. MMTel Enabler server 2. The Application server deployed in Application service provider domain, e.g. Application server 1, can interact with MMTel Enabler servers deployed in different PLMN operator domains, i.e. MMTel Enabler server 1 and MMTel Enabler server 2, based on business agreement between PLMN operator and Application service provider. In this case, the MMTel-2 reference point becomes MMTel-2e reference point. The Controlling Application server can only be deployed in PLMN operator domain and interacts with MMTel Enabler server via MMTel-3 reference point. The Controlling Application server can only interact with the MMTel Enabler server deployed in the same PLMN operator domain. NOTE: In this release, the MMTel Enabler Server is deployed in the PLMN operator domain. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2023-07 SA6#62-Ad Hoc-e - - - Proposed skeleton approved at S6#62-Ad Hoc-e 0.0.0 2023-07 SA6#62-Ad Hoc-e Implemented pCRs approved in S6#62-Ad Hoc-e: S6a240100, S6a240101, S6a240102, S6a240103, S6a240282 Editorial changes by the rapporteur 0.1.0 2023-10 SA6#63 Implemented pCRs approved in S6#63: S6-244639, S6-244640, S6-244641, S6-244642, S6-244643, S6-244644 Editorial changes by the rapporteur 0.2.0 2023-11 SA6#64 Implemented pCRs approved in S6#64: S6-245625, S6-245626, S6-245627 Editorial changes by the rapporteur 0.3.0 2024-12 SA#106 SP-241697 Submitted to SA#106 for information 1.0.0 2025-02 SA6#65 Implemented pCRs approved in S6#65: S6-250072, S6-250074, S6-250077, S6-250078, S6-250079, S6-250150, S6-250372, S6-250373, S6-250374, S6-250375, S6-250376, S6-250379, S6-250380, S6-250381, S6-250382, S6-250383, S6-250384, S6-250549, S6-250550 Editorial changes by the rapporteur 1.1.0 2025-03 SA#107 SP-250194 Submitted to SA#107 for approval 2.0.0 2025-03 SA#107 SP-250194 MCC Editorial update for publication after TSG SA approval 19.0.0
|
495b59b986f98d41912141cabbec196e
|
23.401
|
1 Scope
|
The present document defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
The Radio Access Network functionality is documented only to the extent necessary to describe the overall system. TS 36.300 [5] contains the overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
ITU-T Recommendation I.130 [3] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [4] defines Stage 2 of the method.
TS 23.402 [2] is a companion specification to this specification.
An Evolved Packet System architecture optimised for the support of Cellular IoT (Internet of Things) applications is also defined in this document.
The Evolved Packet System also provides support for the E-UTRAN to control a Dual Connectivity radio connection that uses a combination of E-UTRA and another radio access technology (e.g. NR). TS 36.300 [5] contains the overall description for Dual Connectivity.
Enhancements to support interworking of EPS with 5GS are captured in TS 23.501 [83] and TS 23.502 [84].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
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.402: "Architecture enhancements for non-3GPP accesses".
[3] ITU‑T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
[4] ITU‑T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities".
[5] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[6] 3GPP TS 23.203: "Policy and charging control architecture".
[7] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[8] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2".
[9] 3GPP TS 23.003: "Numbering, addressing and identification".
[10] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".
[11] 3GPP TS 43.022: "Functions related to MS in idle mode and group receive mode".
[12] 3GPP TS 25.304: "UE procedures in idle mode and procedures for cell re-selection in connected mode".
[13] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[14] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
[15] 3GPP TS 43.051: "GERAN Overall description - Stage 2".
[16] 3GPP TS 25.401: "UTRAN overall description".
[17] IETF RFC 1034 (1987): "Domain names – concepts and facilities" (STD 13).
[18] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[19] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[20] Void.
[21] Void.
[22] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".
[23] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification".
[24] 3GPP TS 23.251: "Network Sharing; Architecture and functional description".
[25] IETF RFC 4039: "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)".
[26] IETF RFC 768: "User Datagram Protocol".
[27] 3GPP TS 23.221: "Architectural requirements".
[28] 3GPP TS 23.008: "Organization of subscriber data".
[29] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase X; Stage 2".
[30] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[31] IETF RFC 3588: "Diameter Base Protocol".
[32] IETF RFC 4861: "Neighbor Discovery for IP Version 6 (IPv6)".
[33] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification".
[34] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[35] IETF RFC 4960: "Stream Control Transmission Protocol".
[36] 3GPP TS 36.413: "Evolved Universal Terrestrial Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[37] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[38] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[39] Void.
[40] 3GPP TS 33.102: "3G Security; Security architecture".
[41] 3GPP TS 33.401: "3GPP System Architecture Evolution: Security Architecture".
[42] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".
[43] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[44] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
[45] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[46] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[47] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[48] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[49] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ) service description; Stage 1".
[50] Void.
[51] 3GPP TS 32.240: "Charging architecture and principles".
[52] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[53] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) List; Management Object (MO)".
[54] 3GPP TS 23.261: "IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2".
[55] IETF RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP".
[56] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[57] 3GPP TS 23.271: "Functional stage 2 description of LCS".
[58] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[59] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".
[60] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2".
[61] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3".
[62] IETF RFC 3376: "Internet Group Management Protocol, Version 3".
[63] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
[64] IETF RFC 3927: "Dynamic Configuration of IPv4 Link-Local Addresses".
[65] IETF RFC 4291: "IP Version 6 Addressing Architecture".
[66] 3GPP TS 22.368: "Service Requirements for Machine-Type Communications (MTC); Stage 1".
[67] 3GPP TS 22.011: "Service Accessibility".
[68] 3GPP TS 22.153: "Multimedia priority service".
[69] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".
[70] IETF RFC 6603: "Prefix Exclude Option for DHCPv6-based Prefix Delegation".
[71] 3GPP TS 23.002: "Network Architecture".
[72] 3GPP TS 23.007: "Restoration procedures".
[73] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[74] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[75] 3GPP TS 23.380: "IMS Restoration Procedures".
[76] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)".
[77] IETF RFC 5795: "The RObust Header Compression (ROHC) Framework".
[78] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification".
[79] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications".
[80] 3GPP TS 22.101: "Service aspects; Service principles".
[81] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[82] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities".
[83] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[84] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[85] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
[86] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[87] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access -E-UTRA); Medium Access Control -MAC) protocol specification".
[88] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[89] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[90] 3GPP TS 38.401: "NG-RAN; Architecture description".
[91] 3GPP TS 29.674: "Interface between the UE radio Capability Management Function (UCMF) and the Mobility Management Entity (MME); Stage 3".
[92] 3GPP TS 36.410: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles".
[93] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[94] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[95] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
[96] 3GPP TR 23.700-29: "Study on Security and Privacy Aspects of 5G Satellite Access; Phase 3".
|
495b59b986f98d41912141cabbec196e
|
23.401
|
3 Definitions and abbreviations
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions 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].
MME Pool Area: An MME Pool Area is defined as an area within which a UE may be served without need to change the serving MME. An MME Pool Area is served by one or more MMEs ("pool of MMEs") in parallel. MME Pool Areas are a collection of complete Tracking Areas. MME Pool Areas may overlap each other.
Serving GW Service Area: A Serving GW Service Area is defined as an area within which a UE may be served without need to change the Serving GW. A Serving GW Service Area is served by one or more Serving GWs in parallel. Serving GW Service Areas are a collection of complete Tracking Areas. Serving GW Service Areas may overlap each other.
PDN Connection: The association between a PDN represented by an APN and a UE, represented by one IPv4 address and/or one IPv6 prefix (for IP PDN Type) or by the UE Identity (for Non-IP and Ethernet PDN Types).
Default Bearer: The EPS bearer which is first established for a new PDN connection and remains established throughout the lifetime of the PDN connection.
Default APN: A Default APN is defined as the APN which is marked as default in the subscription data and used during the Attach procedure and the UE requested PDN connectivity procedure when no APN is provided by the UE.
eCall Only Mode: A UE configuration option that allows the UE to attach at EPS and register in IMS to perform only eCall Over IMS, and an IMS call to a non-emergency MSISDN or URI for test and/or terminal reconfiguration services. For a short period following either such call, an incoming call (e.g. callback from a PSAP or HPLMN operator) or other incoming session (e.g. for USIM reconfiguration) is possible. At other times when the UE is configured in this mode, the UE is required to refrain from any signalling to a network. Use of eCall Only Mode is configured in the USIM for the UE.
PDN Connection to the SCEF: The association between a UE, represented by the UE Identity, and a PDN represented by an APN to external packet data network via SCEF to allow transfer of Non-IP data. It includes establishment and persistence of T6 connection between MME and SCEF (see TS 29.128 [79]).
Emergency attached UE: A UE which only has bearer(s) related to emergency bearer service.
NOTE 1: The above term is equivalent to the term "attached for emergency bearer services" as specified in TS 24.301 [46].
LIPA PDN connection: a PDN Connection for local access (e.g. for IP or Ethernet access) for a UE connected to a HeNB.
en-gNB: As defined in TS 37.340 [85].
SIPTO at local network PDN connection: a PDN connection for SIPTO at local network for a UE connected to a (H)eNB.
Correlation ID: For a LIPA PDN connection, Correlation ID is a parameter that enables direct user plane path between the HeNB and L-GW.
SIPTO Correlation ID: For a SIPTO at local network PDN connection, SIPTO Correlation ID is a parameter that enables direct user plane path between the (H)eNB and L-GW when they are collocated.
Local Home Network: A set of (H)eNBs and L-GWs in the standalone GW architecture, where the (H)eNBs have IP connectivity for SIPTO at the Local Network via all the L-GWs.
Local Home Network ID: An identifier that uniquely identifies a Local Home Network within a PLMN.
Presence Reporting Area: An area defined within 3GPP Packet Domain for the purposes of reporting of UE presence within that area due to policy control and/or charging reasons. In the case of E-UTRAN, a Presence Reporting Area may consist in a set of neighbor or non-neighbor Tracking Areas, or eNodeBs and/or cells. There are two types of Presence Reporting Areas: "UE-dedicated Presence Reporting Areas" and "Core Network pre-configured Presence Reporting Areas" that apply to an MME pool.
RAN user plane congestion: RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time.
NOTE 2: Short-duration traffic bursts is a normal condition at any traffic load level, and is not considered to be RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator configuration) is considered a normal mode of operation and might not be RAN user plane congestion.
IOPS-capable eNodeB: an eNodeB that has the capability of IOPS mode operation, which provides local connectivity (e.g. for IP or Ethernet) and public safety services to IOPS-enabled UEs via a Local EPC when the eNodeB has lost backhaul to the Macro EPC or it has no backhaul to the Macro EPC.
IOPS network: an IOPS network consists of one or more eNodeBs operating in IOPS mode and connected to a Local EPC.
Local EPC: a Local EPC is an entity which provides functionality that eNodeBs in IOPS mode of operation use, instead of the Macro EPC, in order to support public safety services.
Macro EPC: the EPC which serves an eNodeB when it is not in IOPS mode of operation.
Nomadic EPS: a deployable system which has the capability to provide radio access (via deployable IOPS-capable eNodeB(s)), local connectivity (e.g. for IP or Ethernet) and public safety services to IOPS-enabled UEs in the absence of normal EPS
Multi-USIM UE: a UE with multiple USIMs, capable of maintaining a separate registration state with a PLMN for each USIM at least over 3GPP Access and supporting one or more of the features described in clause 4.3.33.
IOPS-enabled UE: is an UE that is configured to use networks operating in IOPS mode.
Cellular IoT: Cellular network supporting low complexity and low throughput devices for a network of Things. Cellular IoT supports IP, Ethernet and Non-IP traffic. Unless otherwise stated in this specification, Cellular IoT and all functionality applicable to Cellular IoT also apply to satellite access.
Narrowband-IoT: a 3GPP Radio Access Technology that forms part of Cellular IoT. It allows access to network services via E-UTRA with a channel bandwidth limited to 180 kHz (corresponding to one PRB). Unless otherwise indicated in a clause, Narrowband-IoT is a subset of E-UTRAN. Unless otherwise stated in this specification, Narrowband-IoT also includes satellite access.
LTE-M: a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type E-UTRAN RAT type, and defined to identify in the Core Network the E-UTRAN when used by a UE indicating Category M in its UE radio capability. Unless otherwise stated in this specification, LTE-M also includes satellite access.
WB-E-UTRAN: in the RAN, WB-E-UTRAN is the part of E-UTRAN that excludes NB-IoT. In the Core Network, the WB-E-UTRAN also excludes LTE-M. Unless otherwise stated in this specification, WB-E-UTRAN also includes satellite access.
DCN-ID: DCN identity identifies a specific dedicated core network (DCN).
For the purposes of the present document, the following terms and definitions given in TS 23.167 [81] apply:
eCall Over IMS: See TS 23.167 [81].
RLOS attached UE: A UE is attached only for accessing Restricted Local Operator Services (see TS 23.221 [27]).
IAB-donor: For the purposes of this specification, this is a NR Secondary RAN node is further described in TS 37.340 [85] that supports Integrated access and backhaul (IAB) feature and provides connection to the core network to IAB-nodes. It supports the CU function of the CU/DU architecture for IAB defined in TS 38.401 [90].
IAB-node: A relay node that supports wireless in-band and out-of-band relaying of NR access traffic via NR Uu backhaul links. It supports the UE function and the DU function of the CU/DU architecture for IAB defined in TS 38.401 [90].
Feeder link: as defined in TS 36.300 [5].
Service link: as defined in TS 36.300 [5]
Store and Forward Satellite operation: An operation mode that provides to the UE a communication service when the serving satellite has a discontinuous connection to the ground network and such connection is not available when the satellite is interacting with the UE.
S&F Mode: The mode in which the UE, RAN and core network entities perform Store and Forward Satellite operation.
NTN payload: as defined in TS 36.300 [5].
NTN Gateway: as defined in TS 36.300 [5].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
3.2 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].
5GS 5G System
AF Application Function
ARP Allocation and Retention Priority
AMBR Aggregate Maximum Bit Rate
CBC Cell Broadcast Centre
CBE Cell Broadcast Entity
CIoT Cellular IoT
CSG Closed Subscriber Group
CSG ID Closed Subscriber Group Identity
C-SGN CIoT Serving Gateway Node
CSS CSG Subscriber Server
DAPS Dual Active Protocol Stacks
DCN Dedicated Core Network
DeNB Donor eNode B
DL TFT DownLink Traffic Flow Template
DRX Discontinuous Reception
ECGI E-UTRAN Cell Global Identifier
ECM EPS Connection Management
ECN Explicit Congestion Notification
EMM EPS Mobility Management
eNodeB evolved Node B
EPC Evolved Packet Core
EPS Evolved Packet System
E-RAB E-UTRAN Radio Access Bearer
E-UTRAN Evolved Universal Terrestrial Radio Access Network
GBR Guaranteed Bit Rate
GUMMEI Globally Unique MME Identifier
GUTI Globally Unique Temporary Identity
GW Gateway
HeNB Home eNode B
HeNB GW Home eNode B Gateway
HFN Hyper Frame Number
IAB Integrated Access and Backhaul
IMEI/TAC IMEI Type Allocation Code
IOPS Isolated E-UTRAN Operation for Public Safety
IoT Internet of Things
ISR Idle mode Signalling Reduction
LAA Licensed Assisted Access
LBI Linked EPS Bearer Id
L-GW Local GateWay
LIPA Local IP Access
LWA LTE/WLAN Aggregation
LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel
MBR Maximum Bit Rate
MME Mobility Management Entity
MMEC MME Code
MTC Machine-Type Communications
MT-EDT Mobile Terminated Early Data Transmission
M-TMSI M-Temporary Mobile Subscriber Identity
NB-IoT Narrowband IoT
NR New Radio
NR-U New Radio Unlicensed
NTN Non-Terrestrial Network
OCS Online Charging System
OFCS Offline Charging System
OMC-ID Operation and Maintenance Centre Identity
P‑GW PDN Gateway
PCC Policy and Charging Control
PCRF Policy and Charging Rules Function
PRA Presence Reporting Area
PDCP Packet Data Convergence Protocol
PMIP Proxy Mobile IP
PSAP Public Safety Answering Point
PSM Power Saving Mode
PTI Procedure Transaction Id
QCI QoS Class Identifier
RACS UE Radio Capability Signalling optimization
RCAF RAN Congestion Awareness Function
RFSP RAT/Frequency Selection Priority
RLOS Restricted Local Operator Services
RN Relay Node
RUCI RAN User Plane Congestion Information
S&F Store and Forward
S‑GW Serving Gateway
S-TMSI S-Temporary Mobile Subscriber Identity
SDF Service Data Flow
SIPTO Selected IP Traffic Offload
TAC Tracking Area Code
TAD Traffic Aggregate Description
TAI Tracking Area Identity
TAU Tracking Area Update
TI Transaction Identifier
TIN Temporary Identity used in Next update
UCMF UE radio Capability Management Function
URRP-MME UE Reachability Request Parameter for MME
UL TFT UpLink Traffic Flow Template
ULR-Flags Update Location Request Flags
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4 Architecture model and concepts
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.1 General concepts
|
Local breakout of traffic via the visited PLMN is supported, when network policies and user subscription allow it. Local breakout may be combined with support for multiple simultaneous PDN connections, described in clause 5.10.
CIoT EPS Optimisations provide improved support of small data transfer, described in clause 4.11.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2 Architecture reference model
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2.1 Non-roaming architecture
|
Figure 4.2.1-1: Non-roaming architecture for 3GPP accesses
Figure 4.2.1-2: Non-roaming architecture for 3GPP accesses. Single gateway configuration option
NOTE 1: Also in this configuration option, S5 can be used between non collocated Serving Gateway and PDN Gateway.
NOTE 2: Additional interfaces for 2G/3G access are shown in TS 23.060 [7].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2.2 Roaming architecture
|
Figure 4.2.2-1: Roaming architecture for 3GPP accesses. Home routed traffic
NOTE 1: Additional interfaces/reference points for 2G/3G accesses are documented in TS 23.060 [7].
The figures 4.2.2-2 and 4.2.2-3 represent the Roaming with local breakout case with Application Function (AF) in the Home Network and in the Visited Network respectively. The concurrent use of AF's in the home network and AF's in the visited network is not excluded.
Figure 4.2.2-2: Roaming architecture for local breakout, with home operator's application functions only
NOTE 2: See TS 23.203 [6] for the role of and functions related to Home and Visited PCRF and S9/Rx reference points.
NOTE 3: In figure 4.2.2‑2, the control plane signalling and the user plane for accessing to Home Operator's services traverse over the SGi reference point via the Visited Operator's PDN.
Figure 4.2.2-3: Roaming architecture for local breakout, with visited operator's application functions only
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2.3 Reference points
|
S1-MME: Reference point for the control plane protocol between E-UTRAN and MME.
S1-U: Reference point between E-UTRAN and Serving GW for the per bearer user plane tunnelling and inter eNodeB path switching during handover. S1-U does not apply to the Control Plane CIoT EPS Optimisation.
S3: It enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state. This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO).
S4: It provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.
S5: It provides user plane tunnelling and tunnel management between Serving GW and PDN GW. It is used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.
S6a: It enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between MME and HSS.
Gx: It provides transfer of (QoS) policy and charging rules from PCRF to Policy and Charging Enforcement Function (PCEF) in the PDN GW.
S8: Inter-PLMN reference point providing user and control plane between the Serving GW in the VPLMN and the PDN GW in the HPLMN. S8 is the inter PLMN variant of S5.
S9: It provides transfer of (QoS) policy and charging control information between the Home PCRF and the Visited PCRF in order to support local breakout function.
S10: Reference point between MMEs for MME relocation and MME to MME information transfer. This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO).
S11: Reference point providing control plane between MME and Serving GW. In addition, in order to support Control Plane CIoT EPS Optimisation, the S11-U reference point provides user plane between MME and Serving GW.
S12: Reference point between UTRAN and Serving GW for user plane tunnelling when Direct Tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage of S12 is an operator configuration option.
S13: It enables UE identity check procedure between MME and EIR.
S17: It enables procedures for RACS between MME and UCMF.
SGi: It is the reference point between the PDN GW and the packet data network. Packet data network may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi for 3GPP accesses.
Rx: The Rx reference point resides between the AF and the PCRF in the TS 23.203 [6].
NOTE 1: Except where stated otherwise, this specification does not make an explicit assumption as to whether an interface is intra-PLMN or inter-PLMN.
When data forwarding is used as part of mobility procedures different user plane routes may be used based on the network configuration (e.g. direct or indirect data forwarding). These routes can be between eNodeB and RNC, eNodeB and SGSN, RNC and S‑GW or between S‑GW and SGSN. Explicit reference points are not defined for these routes. These user plane forwarding routes can cross inter-PLMN boundaries (e.g. in the case of Inter-PLMN HO).
Protocol assumption:
- The S1-U is based on GTP-U protocol;
- The S3 is based on GTP protocol;
- The S4 and S11 are based on GTP protocol;
- The S5 is based on GTP protocol. PMIP variant of S5 is described in TS 23.402 [2];
- The S8 is based on GTP protocol. PMIP variant of S8 is described in TS 23.402 [2].
- S3, S4, S5, S8, S10 and S11 interfaces are designed to manage EPS bearers as defined in clause 4.7.2.
NOTE 2: Redundancy support on reference points S5 and S8 should be taken into account.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2.4 Warning System architecture
|
Refer to TS 23.041 [48] and TS 23.002 [71] for the Warning System architecture.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.2.5 Radio Capability signalling optimization architecture
|
Figure 4.2.5-1: RACS architecture
Figure 4.2.5-1 depicts the EPS architecture supporting RACS. RACS is further described in clause 5.11.3a. EPS architecture supporting provisioning of UCMF is described in TS 23.682 [74].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3 High level functions
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.1 General
|
The following list gives the logical functions performed within this system. Several functional groupings (meta functions) are defined and each encompasses a number of individual functions:
- Network Access Control Functions.
- Packet Routing and Transfer Functions.
- Mobility Management Functions.
- Security Functions.
- Radio Resource Management Functions.
- Network Management Functions.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2 Network access control functions
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.1 General
|
Network access is the means by which a user is connected to the evolved packet core system.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.2 Network/Access network selection
|
It is the means by which a UE selects a PLMN/Access network from which to gain connectivity. The network/access network selection procedure varies for different access technologies. For 3GPP access networks, the network selection principles are described in TS 23.122 [10]. For 3GPP access networks, the access network selection procedures are described in TS 36.300 [5], TS 43.022 [11] and TS 25.304 [12].
Architectural impacts stemming from support for network/access network selection procedures for non-3GPP access and between 3GPP access and non-3GPP accesses are described in TS 23.402 [2].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.3 Authentication and authorisation function
|
This function performs the identification and authentication of the service requester, and the validation of the service request type to ensure that the user is authorised to use the particular network services. The authentication function is performed in association with the Mobility Management functions.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.4 Admission control function
|
The purpose of admission control is to determine if the requested resources are available, and then reserve those resources.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.5 Policy and Charging Enforcement Function
|
This includes all the functionality of PCEF as defined by TS 23.203 [6]. The PCEF encompasses service data flow detection, policy enforcement and flow based charging functionalities as defined in TS 23.203 [6].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.2.6 Lawful Interception
|
Lawful interception is the action, performed by a network operator / access provider / service provider, of making available certain information and providing that information to a law enforcement monitoring facility.
4.3.2a Support for Dual Connectivity
Dual Connectivity involves two RAN nodes, i.e. Master and Secondary RAN nodes (see TS 36.300 [5] for the definitions), in providing radio resources to a given UE (with active radio bearers), while a single S1-MME termination point exists for an UE between a MME and the E-UTRAN. The E-UTRAN architecture and related functions to support Dual Connectivity with E-UTRAN is further described in TS 36.300 [5]. Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node is further described in TS 37.340 [85].
Dual connectivity defines "Master Cell Group (MCG) bearer" and "Secondary Cell Group (SCG) bearer" alternatives (see TS 36.300 [5]). For E-RABs configured as "MCG bearers" the U-plane termination points are maintained, whereas for E-RABs configured as "SCG bearers" it enables changing the U-plane termination point in the E-UTRAN by means of S1-MME signalling without changing the S1-MME termination point.
Dual Connectivity also defines a "split bearer" alternative TS 36.300 [5]. The "split bearer" in the E-UTRAN is transparent to the core network entities (e.g. MME, S-GW etc.) with the exception of the CSG membership verification by the MME when the Secondary eNodeB is a hybrid access eNodeB.
The E-UTRAN uses the per-UE information supplied by the MME and local E-UTRAN configuration data to determine whether or not to use Dual Connectivity for that UE, and, on a per EPS bearer basis the E-UTRAN decides whether to use an MCG bearer or SCG bearer, and, whether or not that bearer is a "split bearer".
NOTE 1: Typically, the MME and SGW cannot determine whether the RAN termination point(s) for the S1-U interface are located on a Master RAN node that has multiple IP addresses, or, on a Secondary RAN node.
If the UE has indicated support for Dual Connectivity with NR and MME has an Access Restriction for NR for a UE (either signalled from the HSS, or, locally generated by VPLMN policy in the MME) then the MME shall signal this to the E-UTRAN as part of Handover Restriction List and to the UE in Attach and TAU Accept as defined in clauses 5.5.2.2.3, 5.5.2.4.3, 5.3.2.1, 5.3.3.1, 5.3.3.2 and D.3.6 respectively. An eNodeB supporting Dual Connectivity with NR checks whether the UE is allowed to use NR. If the UE is not allowed to use NR, the eNodeB shall not establish Dual Connectivity with NR as a secondary RAT.
The MME uses "UE support for dual connectivity with NR" for SGW and PGW selection when the UE indicates support for NR and there is no Access Restriction for NR for the UE.
An E-UTRAN cell, based on operator configuration, broadcasts whether it is capable of supporting dual connectivity with locally available NR secondary cell(s).
At inter-RAT handover from NR or GERAN/UTRAN, the Access Restriction for NR is either already in the MME's UE context, or, is obtained from the HSS during the subsequent Tracking Area Update procedure (i.e. not from the source AMF/SGSN or source RAN). In both inter-RAT handover cases, any NR Access Restriction is then signalled to the E-UTRAN.
NOTE 2: This signalling of the Access Restriction during the TAU after the inter-RAT handover procedure means that there is a small risk that NR resources are transiently allocated.
The eNodeB, at which the S1-MME terminates, performs all necessary S1-MME related functions (as specified for any serving eNodeB) such as mobility management, relaying of NAS signalling, E-RAB handling, etc. and manages the handling of user plane connection of S1-U.
Additional functional characteristics are:
- User location information reporting is based on the identity of the cell that is serving the UE and supported by the eNodeB terminating S1-MME. The cell identity of the Primary cell in the secondary RAN node may also be included, if available.
- Path update signalling for E-RABs configured as "SCG bearers" and Serving GW relocation cannot occur at the same time.
- During handover with dual connectivity, the requirement of forwarding "end marker" packets to target node is also applicable to secondary RAN node if it is the source node for S1-U bearer.
- After handover with data forwarding, the E-UTRAN initiated E-RAB modification procedure of clause 5.4.7 should not be initiated by the target eNodeB before "end marker" packet is received at the target RAN node or a timer in target eNodeB expires.
- Relaying function is not supported.
- CSG function may be supported if the Secondary eNodeB is a hybrid access eNodeB (see more details in clause 5.4.7 and in TS 36.300 [5]).
NOTE 3: A HeNB cannot be the Master eNodeB, i.e. a HeNB cannot initiate the Secondary eNodeB Addition procedure.
NOTE 4: A HeNB is not allowed to be the Secondary eNodeB if the HeNB is a closed access eNodeB.
- When the Secondary eNodeB is a hybrid access eNodeB, the Master eNodeB may ask CSG membership verification to the MME using E-RAB Modification Indication message (for SCG bearers) or UE Context Modification Indication (for split bearers) message. The MME shall determine the CSG membership based on the CSG Membership Information as specified in TS 36.300 [5] and shall respond to the Master eNodeB using respectively a E-RAB Modification Confirm or a UE Context Modification Confirm, but shall not update the User CSG Information in the Core Network.
- The LIPA function may be supported for the SCG bearer alternative, in the case that the Secondary eNodeB is a HeNB with a collocated L-GW (see more details in TS 36.300 [5]).
- "SIPTO at the Local Network with L-GW function collocated with the (H)eNB" function may be supported (see more details in TS 36.300 [5]):
- For the MCG and split bearer alternatives, if the Master eNodeB is collocated with a L-GW; and/or
- For the SCG bearer alternative, if the Secondary eNodeB is a (H)eNB with a collocated L-GW.
NOTE 5: LIPA or SIPTO at the Local Network PDN connection can be established if the SeNodeB has already been added before the UE requests establishment of the LIPA or SIPTO at the Local Network PDN connection.
NOTE 6: LIPA or SIPTO at the Local Network PDN connection can be established if the UE is in the coverage of the candidate SeNodeB when the UE requests establishment of the LIPA or SIPTO at the Local Network PDN connection, but the SeNodeB has not yet been added. In this case, there is a time gap between the moment when the PDN connection establishment is completed and the moment when the SeNodeB Addition procedure is completed.
- "SIPTO at the Local Network with stand-alone GW" function may be supported for the MCG, SCG, and split bearer alternatives if the Master and Secondary eNodeBs belong to the same LHN (see more detail in TS 36.300 [5]).
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.3 Packet routing and transfer functions
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.3.1 General
|
A route is an ordered list of nodes used for the transfer of packets within and between the PLMN(s). Each route consists of the originating node, zero or more relay nodes and the destination node. Routing is the process of determining and using, in accordance with a set of rules, the route for transmission of a message within and between the PLMN(s).
The EPS is an IP network and uses the standard routing and transport mechanisms of the underlying IP network.
The Maximum Transfer Unit (MTU) size considerations in clause 9.3 of TS 23.060 [7] are also applicable to EPS.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.3.2 IP header compression function
|
The IP header compression function optimises use of radio capacity by IP header compression mechanisms.
When Control Plane CIoT EPS Optimisation is supported for PDN connections of IP PDN Type, if the IP header compression based on ROHC framework IETF RFC 5795 [77] is implemented in the MME and the UE, the ROHC profiles defined in TS 36.323 [78] may be supported.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.3.3 Packet screening function
|
The packet screening function provides the network with the capability to check that the UE is using the exact IPv4-Address and/or IPv6-Prefix that was assigned to the UE.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.3.4 IP Multicast Forwarding between a network accessed by LIPA and a UE
|
The Home eNodeB L-GW should support IP forwarding of packets to multicast groups between the UE and the network accessed by LIPA.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.4 Security functions
|
The security functions are described in clause 5.3.10.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5 Mobility management functions
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5.1 General
|
The mobility management functions are used to keep track of the current location of a UE.
Intra-RAT mobility for NB-IoT UEs is supported.
Inter-RAT idle mode mobility between NB-IoT and WB-EUTRAN/UTRAN/GERAN is supported. Tracking area list management as defined in clause 4.3.5.3 is required to ensure that at inter-RAT mobility, the UE performs a TAU or RAU procedure.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5.2 Reachability Management for UE in ECM-IDLE state
|
The location of a UE in ECM-IDLE state is known by the network on a Tracking Area List granularity. All cells of the Tracking Areas in which a UE in ECM-IDLE is currently registered needs to be taken into account for paging. The UE may be registered in multiple Tracking Areas. All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME.
An EMM-REGISTERED UE performs periodic Tracking Area Updates with the network after the expiry of the periodic TAU timer.
The MME may allocate long periodic TAU timer value to the UE according to clause 4.3.17.3.
If the UE is out of E-UTRAN coverage (including the cases when the UE is camped on GERAN/UTRAN cells) when its periodic TAU timer expires, the UE shall:
- if ISR is activated, start the E-UTRAN Deactivate ISR timer. After the E-UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "P-TMSI".
- if ISR is activated and the UE is camping on a GERAN/UTRAN cell (or returns to coverage in GERAN/UTRAN) and the UE is EPS/IMSI attached, perform a LAU procedure in NMO II or a combined RA/LA update procedure in NMO I.
- when EMM-REGISTERED, perform a Tracking Area Update when it next returns to E‑UTRAN coverage. For UE using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), if the UE knows how the E-UTRAN coverage varies with time based on information defined in TS 36.331 [37] (e.g. from the ephemeris data of a satellite access system that the UE is using) then the UE may deactivate its Access Stratum functions in order to optimise power consumption until coverage returns. Details are specified in TS 36.304 [34] and TS 24.301 [46].
If the UE is camped on an E‑UTRAN cell or is in ECM‑CONNECTED state when the UE's periodic RAU timer expires, the UE shall:
- if ISR is activated, start the GERAN/UTRAN Deactivate ISR timer. After the GERAN/UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "GUTI".
- perform a Routing Area Update when it next returns to GERAN/UTRAN coverage.
If the UE is EPS attached only and either camps on an E UTRAN cell or is in ECM CONNECTED state when the UE's periodic LAU timer expires, the UE shall perform a Location Area Update procedure in NMO II or combined RA/LA update in NMO I when it next returns to GERAN/UTRAN coverage.
The E-UTRAN Deactivate ISR timer is stopped when the UE performs a successful Tracking Area Update or combined TA/LA Update; and the GERAN/UTRAN Deactivate ISR timer is stopped when the UE performs a successful Routing Area Update or combined RA/LA Update.
Expiry of the periodic TAU timer, or, the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to change RAT.
The UE's periodic TAU timer is restarted from its initial value whenever the UE enters ECM‑IDLE mode and when the UE leaves the E‑UTRAN connection due to handover to GERAN/UTRAN. UTRAN RRC state transitions and GERAN GPRS STANDBY/READY state transitions shall have no other impact on the periodic TAU timer.
E‑UTRAN RRC state transitions shall have no impact on the periodic RAU timer or periodic LAU timer except that handover from GERAN/UTRAN to E‑UTRAN shall cause the periodic RAU timer to be started from its initial value.
Handover from E‑UTRAN to UTRAN/GERAN shall cause the periodic TAU timer to be started from its initial value.
Typically, the MME runs a mobile reachable timer. Whenever the UE enters ECM IDLE mode the timer is started with a value similar to the UE's periodic TAU timer. If this timer expires in the MME, the MME can deduce that the UE is not reachable. However, the MME does not know for how long the UE is not reachable, so, the MME shall not immediately delete the UE's bearers. Instead the MME should clear the PPF flag in the MME and start an Implicit Detach timer, with a relatively large value and if ISR is activated, at least slightly larger than the UE's E-UTRAN Deactivate ISR timer.
Tracking Area or RAT specific MME configuration can be used to support UEs using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage).
NOTE 1: For example, if a satellite system only provides coverage to a UE for 20 minutes when a satellite passes, and the maximum time before a satellite passes any point on the earth is 10 hours, the MME could configure the periodic TAU timer and mobile reachable timer to be just greater than 20 minutes and the Implicit Detach timer to be greater than 10 hours to avoid unintended implicit detach due to coverage gap. Such configuration does not require MME to be aware of detailed coverage times for each UE or for different locations.
Further enhancements to handle discontinuous coverage for satellite access is provided in clause 4.13.8.2.
If MME has allocated an Active Time to the UE, then the MME starts the Active timer with the value of Active Time whenever the UE enters ECM IDLE mode. If this timer expires in the MME, the MME can deduce that the UE is not reachable and should clear the PPF flag in the MME.
With the PPF clear, the MME does not page the UE in E‑UTRAN coverage and shall send a Downlink Data Notification Reject message to the Serving GW when receiving a Downlink Data Notification message from the Serving GW. If the Implicit Detach timer expires before the UE contacts the network, then the MME can deduce that the UE has been 'out of coverage' for a long period of time and implicitly detach the UE as described in clause 5.3.8.3 "MME-initiated Detach procedure".
If the MME is requested to monitor Reachability for Data and the UE enters ECM-CONNECTED, the MME sends a Monitoring Report message to the address that was indicated in the related Monitoring Request as described in TS 23.682 [74].
When the MME applies General NAS level Mobility Management Congestion Control to a UE, the MME may need to adjust the mobile reachable timer and/or Implicit Detach timer (as clause 4.3.7.4.2.4).
NOTE 2: The SGSN has similar functionality as the MME.
NOTE 3: Alternative MME implementations are permitted, however, the externally visible MME behaviour should conform to the above description.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5.3 Tracking Area list management
|
Tracking Area list management comprises the functions to allocate and reallocate a Tracking Area Identity list to the UE. All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME.
The "tracking area list concept" is used with E-UTRAN. With this concept, when the UE registers with the network, the MME allocates a set (a "list") of tracking areas to the UE. By making the centre of this set of tracking areas close to the UE's current location, the chance of a UE rapidly making another tracking area update can be reduced.
If SIPTO at local network with stand-alone GW, Serving GW relocation without mobility and ISR are supported in the core network the Tracking Area list should only contain either Tracking Areas inside one local network or inside the macro network. If the tracking area list covers both local network and macro network, the ISR shall not be activated if the UE is allowed to use SIPTO at local network.
The MME determines the RAT type the UE is camping on, i.e. NB-IoT or WB-E-UTRAN for terrestrial access and WB-E-UTRAN or NB-IoT RAT types for satellite access, based on the Tracking Area indicated in the INITIAL UE MESSAGE by the eNodeB.
To ensure a UE initiates tracking area updating procedure when performing inter-RAT mobility between NB-IoT and WB-E-UTRAN, the E-UTRAN shall be configured such that a Tracking Area does not contain both WB-E-UTRAN and NB-IoT cells, and, the MME shall not allocate a Tracking Area Identity list that contains both NB-IoT and WB-E-UTRAN Tracking Areas.
To ensure the UE initiates tracking area update procedure when it moves to and from an MME that supports 15 EPS bearers per UE as defined in clause 4.12 to an MME that does not support 15 EPS bearers per MME and vice versa, the MME shall allocate a Tracking Area Identity list that provides homogenous support for 15 EPS bearers per UE.
Other features (e.g. User Plane CIoT EPS Optimisation, Supporting up to 15 EPS bearers per UE, satellite access) may require the MME to adapt how it creates the "list" of TAIs.
NOTE: This TAI list functionality is different to the SGSN behaviour in GERAN and UTRAN systems. In GERAN/UTRAN the UE is only registered in one Routeing Area at a time.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5.4 Inter-eNodeB mobility anchor function
|
The Inter-eNodeB Mobility Anchor is the functional entity that anchors the user plane for E-UTRAN mobility.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
4.3.5.5 Inter-3GPP mobility anchor function
|
The Inter-3GPP Mobility Anchor is the functional entity that anchors the user plane for mobility between 3GPP 2G/3G access systems and the E-UTRA access system.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.