hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.2.2.1 Overview
| Three types of Command service operations are supported: Read, Write and Disable.
An AF uses the Command service Read operation to retrieve information from AIoT Device(s), and the AIOTF uses the commands described in clause 5.2.2.2 towards the AIoT Device for the operation.
An AF uses the Command service Write operation to write information to AIoT Device(s), and the AIOTF uses the commands described in clause 5.2.2.2 towards the AIoT Device for the operation.
An AF uses the Command service Disable operation to permanently disable the capability of AIoT Device(s) to transmit RF signals, and the AIOTF uses the commands described in clause 5.2.2.3 towards the AIoT Device for the operation.
If the AIoT Device receives a NAS Command Request that the AIoT Device does not support or has not implemented, the AIoT Device shall return an AIOT STATUS message with an appropriate cause code as defined in TS 24.369 [13]. Otherwise, the AIoT Device performs the Command service operation according to the received NAS Command Request.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.2.2.2 Read and Write Commands
| It is optional for an AIoT Device to support of Read and Write Commands. If supported, an AIoT Device contains User Memory that can be used to store application specific data and is accessed using AIoT NAS commands from an AIOTF. An AIoT Device implementation may have other storage outside of the User Memory that is used to store e.g. AIoT Device Permanent Identifier, etc.
The User Memory is accessed by the following commands and responses between the AIOTF and AIoT Device:
- Read Request: used to read application data from User Memory.
- Read Response: Response from the AIoT Device to Read Request, providing a status and the application data read from the User Memory.
- Write Request: used to write application data to User Memory.
- Write Response: Response from the AIoT Device to Write Request, providing a status for the Write Request.
The Read Request and Response, and Write Request and Response commands are used to access the User Memory when an authorized AF uses the Read or Write command service operations, as described in clause 5.2.2.1. The Read or Write Request is sent in the Command Request step and the Read or Write Response is sent in the Command Response step of the Command procedure described in clause 6.2.3.
The physical memory map of an AIoT Device and where the User Memory is within it is implementation specific.
The commands to access the User Memory include an offset from the start of the User Memory to indicate where to read application data from and where to write application data to. The offset and the application data transferred in the Read Request, Write Request, and Read Response has no special meaning to the network, and the AIOTF or other NFs do not attempt to interpret them.
Figure 5.2.2.2-1: Logical AIoT Device User Memory
The Write Request command is used to write application data into the User Memory and includes:
- the application data to write and its length; and
- the offset where to write the application data.
The AIoT Device responds with a Write Response indicating whether the Write Request was successful.
The Read command is used to read from the User Memory and includes:
- the offset to read application data from; and
- the length of the application data to read.
The application data is from the User Memory in the place indicated by the offset and the length.
The AIoT Device responds with a Read Response including whether the read was successful and the application data read from the User Memory.
If an AIoT Device does not support Read Request or Write Request commands, or the parameters in the commands are invalid the AIoT Device shall reject the command.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.2.2.3 Permanent Disable Command
| An AIoT Device may be permanently disabled. A permanently disabled AIoT Device does not respond to the Inventory Procedure, as described in clause 6.2.2.
An AIoT Device is permanently disabled by the Permanent Disable command sent by an AIOTF to the AIoT Device.
The Permanent Disable command is sent to an AIoT Device when an authorized AF uses the Permanent Disable command service operations as described in clause 5.2.2.1, or if the network determines to disable the AIoT Device. The Permanent Disable command is sent in the Command Request step and a response is sent in the Command Response step of the Command procedure described in clause 6.2.3. The AIoT Device responds indicating whether the Permanent Disable command was successful.
NOTE: The trigger conditions when a network determines to disable the AIoT Device depends on operator and implementation policy.
When the AIoT Device has received and verified a Permanent Disable command, it shall no longer respond to the inventory procedure.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.3 Discovery and Selection of AIoT node(s)
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.3.1 AIOTF Discovery and Selection
| The AIOTF discovery and selection functionality is to determine an AIOTF(s) to handle an AIoT service operation request.
The NEF determines AIOTF instances(s) by providing the NRF with Target Area information and the NRF returning AIOTF instance(s) that match the provided Target Area information, or by using local configuration.
A service operation request received by the NEF from an AF may include External Target Area information and the NEF uses it to determine the Target Area information that is provided to the AIOTF and NRF, if used. The External Target Area information is a pre-configured External Area Identifier or geographic area (e.g., a civic address or GAD shapes). The Target Area information is a list of AIoT Areas.
NOTE: The mapping between AIoT Areas and External Area Identifiers information provided by an AF is configured in the NEF.
When an AIoT service operation request indicates individual AIoT Device(s), the AIOTF instance(s) may be selected by taking into account the last known AIOTF instance(s) (e.g. AIOTF ID/address) for those AIoT Device(s) obtained from the ADM.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.3.2 ADM Discovery and Selection
| The ADM discovery and selection function is supported by the AIOTF to select an ADM instance to retrieve the device profile data or update the last known AIOTF for the AIoT device. The AIOTF may also discover and select an ADM to retrieve AF authorization data. Similarly, the NEF uses the ADM discovery and selection function to select an ADM to obtain the last known AIOTF for the AIoT device.
When the ADM discovery is performed, the AIOTF or the NEF utilizes the NRF to discover the ADM instance(s) unless the ADM information is available by other means, e.g., locally configured. The AIOTF or the NEF selects an ADM instance based on the available ADM instances (obtained from the NRF or locally configured).
The following factors may be considered for the ADM discovery and selection for AIoT device profile retrieval or update:
- The domain information or the AIoT device permanent ID.
NOTE 1: Based on local configuration, the AIOTF or the NEF can determine whether to use the domain information or the AIoT device permanent ID.
NOTE 2: In case the domain information is empty, the AIOTF or the NEF uses AIoT device permanent ID for ADM discovery and selection.
The following factors may be considered for the ADM discovery and selection for AF authorization data retrieval:
- The AF ID.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.3.3 NG-RAN Node and RAN Reader Selection
| The AIOTF selects NG-RAN node(s) and optionally RAN Readers based on the configured NG-RAN configuration information and the received AIoT service operation request. The AIOTF may also select a RAN Reader based on the stored last known RAN Reader information.
The AIOTF obtains the NG-RAN configuration information (NG-RAN node ID, AIoT Area ID list, optionally RAN Reader(s) associated with each AIoT area and, optionally, the location served by each RAN Reader) via OAM or local configuration.
When the AIOTF receives an AIoT service operation request, based on the received Target Area information in the AIoT service operation request and the NG-RAN configuration information, the AIOTF selects the NG-RAN node(s) and optionally RAN Reader(s) to handle the request and the AIOTF determines a Requested Service Area Information for each selected NG-RAN node. The Requested Service Area Information provided by the AIOTF to each selected NG-RAN node can be empty, or includes a list of AIoT Area IDs, a list of RAN Reader IDs, or both a list of AIoT Area IDs and a list of RAN Reader IDs. How the NG-RAN node determines RAN Readers based on the Requested Service Area Information is specified in TS 38.300 [5].
NOTE 1: The Target Area information in a received AIoT service operation request can span multiple NG-RAN node(s) or can be a subset of the supported AIoT areas of a single NG-RAN node.
The AIOTF sends the AIoT service operation request to each selected NG-RAN node, either directly or through the selected AMF, including the Requested Service Area Information for the NG-RAN node.
If an AIoT service operation request received by the AIOTF includes individual target AIoT Device Perminant ID(s), the AIOTF may consider the last known serving RAN Reader, if available from the AIoT Device context to determine the NG-RAN node and RAN Reader(s) for the request. In this case the last known serving RAN Reader ID is sent as the Requested Service Area to the selected NG-RAN node.
NOTE 2: The RAN Reader ID is not exposed to the AF.
NOTE 3: An AIOTF receives the Inventory Report from an NG-RAN node includes a RAN Reader ID that represents the AIoT Device’s location at Reader granularity.
NOTE 4: The AIOTF uses the RAN Reader ID and the NG-RAN node to update the last known serving RAN Reader information in the local AIoT Device context.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.3.4 AMF Discovery and Selection
| For indirect Connectivity via AMF (see clause 4.2), AMF discovery and selection functionality is implemented in AIOTF.
In this case, the AIOTF is locally configured with the information of the AMF corresponding NG-RAN node(s).
The AIOTF selects the AMF that is corresponding to the selected NG-RAN nodes based on the local configuration in order to forward the AIoT service operation messages towards the selected NG-RAN node(s) (see NG-RAN Node and RAN Reader Selection in clause 5.3.3) via the selected AMF.
NOTE: It is left to stage3 to handle the case that the AMF fails to forward the inventory or command request to the selected NG-RAN. It is up to the operator to ensure local configured AMF corresponding to the NG-RAN do have the NG connection with the AMF during the deployment phase.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.4 Assistance information provided to NG-RAN node
| The AIOTF provides the following assistance information to the NG-RAN together with the service operation requests.
For Inventory or Command service operation, following Inventory Assistance Information is included in the Inventory Request from AIOTF to NG-RAN:
a) Optionally, approximate number of AIoT devices based on AF request.
b) Size of the Inventory Response message from the AIoT Device.
c) Optionally, time interval for AIoT Device response aggregation used by the NG-RAN as specified in clause 5.9.
For Command service operation, following Command Assistance Information is included in the Command Request from AIOTF to NG-RAN:
d) Size of the Command Response message from the AIoT Device.
Bullet b) is determined by AIOTF based on the length of device specific authentication information as specified in TS 33.369 [9] and if AIoT Device ID Permanent ID is included, its length is considered.
If not provided by the AF, bullet c) in the above assistance information provided by the AIOTF may be based on local configuration based on SLA between the AIoT service provider represented by an AF and the operator.
The assistance information is used by the NG-RAN for performing service operations, e.g. radio resource allocation by using bullets a), b) and d), AIoT Device responses aggregation by using bullet c).
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.5 AIoT Device Profile Management
| The ADM may hold AIoT Device Profile Data for the AIoT Device used in the network. If the AIoT Device is managed by the network, then the profile data for an AIoT Device is managed in the ADM, otherwise the corresponding profile data is stored external to the network.
The AIoT Device Permanent ID is used by the AIOTF together with local configuration, 3rd party related context to locate the entity which stores the profile data of an AIoT Device.
In case the AIoT Device is managed by the network, the AIOTF checks whether the AIoT Device Permanent ID from AIoT Device has the profile data in the network and retrieves the profile data. The profile data for AIoT Device is different from the UE subscription data as defined in clause 5.2.3 of TS 23.502 [4], it is stored in the ADM network entity that exclusively supports management of AIoT Device’s profile data. The AIoT Device Permanent ID is the primary key for AIoT Device profile data in the ADM.
Optionally, the ADM stores AIoT Device Temporary Identifier(s) as described in TS 33.369 [9].
The table 5.5-1 below describes information storage structures for AIoT device profile data.
Table 5.5-1: AIoT Device Profile Data
Field
Description
AIoT Device Permanent ID
Uniquely identifies the AIoT Device.
Last known AIOTF information
Indicate the last known AIOTF that serves the AIoT device, or unknown
AIoT Device Temporary Identifier(s)
Temporary ID(s) may be stored as described in TS 33.369 [9].
NOTE: In addition to the AIoT device profile data, the ADM also manages AIoT device security data including device credentials as specified in TS 33.369 [9].
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.6 AF authorization for the AIoT Services
| The information needed to support the authorization of the AF for performing the AIoT service is stored as the authorization data for 3rd party AF in the ADM, or locally configured in the AIOTF.
Table 5.6-1 below describes items stored as AF authorization data for the AIoT.
Table 5.6-1: AF Authorization Data for AIoT
AF Authorization Data
Description
AF ID
Identifier used to identify the AF.
Allowed area
Indicate the allowed area for the indicated AF to perform the AIoT services operations.
Allowed service operations
Indicate the allowed service operation (s) for the indicated AF, e.g. inventory, read, write, permanent disable.
Allowed target AIoT Devices
Indicate the allowed AIoT Device(s) for the indicated AF.
The information indicating the allowed target AIoT Devices is a list of the permanent AIoT Device ID (see clause 5.7) or the filtering information (see clause 5.8).
The authorization of the AF for the AIoT includes two parts:
- NEF performs AIoT AF request authorization based on the service level agreement (SLA) between the 3rd party AF and the 5GS of the mobile network operator, the operator policy and local configuration as in TS 33.501 [8].
- AIOTF may perform authorization of AIoT service requested by the AF, using the AF authorization data retrieved from n the ADM or configured locally as described in above Table 5.6-1. When ADM is used, the AIOTF also subscribes to changes of AF authorization data in the ADM for synchronization.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.7 Identifiers
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.7.1 General
| The following clauses define the identifiers used within the AIoT system to support identification of AIoT Device and AIoT Session.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.7.2 AIoT Device Permanent Identifier
| In order to support the AIoT feature in 5G System, a globally unique AIoT Device Permanent Identifier shall be allocated to each AIoT Device. An AIoT Device Permanent Identifier is assigned either by an operator or by a third party. The AIoT Device Permanent Identifier is used to identify an AIoT Device and locate the entity where the AIoT Device related information is stored.
NOTE 1: How to configure an AIoT Device with the AIoT Device Permanent Identifier is out of scope of this specification.
The AIoT Device Permanent Identifier includes the following components:
- The ID Type, including:
- Information indicating whether a PLMN ID is included.
- Information indicating whether a NID is included.
- Information indicating whether a third party identifier is included.
- Identification Information Type, indicating whether the Identification Information contains an EPC or unstructured information.
- The Domain Information includes none, one or more of the following:
- A PLMN Identifier (i.e., MCC and MNC) as specified in TS 23.003 [6] when the information in the ID type indicates it is included
- A Network Identifier (NID) as specified in TS 23.003 [6] when the information in the ID type indicates it is included.
- A third party identifier used to identify a third party when the information in the ID type indicates it is included.
- The Identification Information is used to distinguish different AIoT Devices within the scope identified by Domain Information (if available) and can contain either:
- An EPC, as defined in clause 14 of GS1 TDS Release 2.1 [7].
- Unstructured information, where the contents is defined by the allocator.
Figure 5.7.2-1: AIoT Device Permanent Identifier Structure
An operator allocated AIoT Device Permanent Identifier should include the identifier of the network for the operator. The identifier of the network is present as either a PLMN Identifier, NID or both in the AIoT Device Permanent Identifier.
A third party allocated AIoT Device Permanent Identifier may include none of the following information or include any combination of at least one kind of the following information: a PLMN Identifier, NID or the third party identifier.
NOTE 3: The length of ID Type, PLMN Identifier (if present), NID (if present) and the third party identifier (if present) components is fixed. The length of the Identification Information is variable. The details are specified in TS 23.003 [6].
NOTE 4: When the Domain Information is empty, the AIOTF uses, e.g., Identification Information (i.e EPC) to discover and select the ADM instance or the external server for the AIoT Device Profile Data.
The following lengths are supported for the Identification Information in an AIoT Device Permanent Identifier: 32 bits, 64 bits, 96 bits, 128 bits, 256 bits and 496 bits.
NOTE 5: The encoding for the length of the Identification Information enables additional shorter or longer fixed lengths to be supported in the future.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.7.3 Correlation ID
| Correlation ID is generated by AIOTF corresponding to an AF service operation request. It is used together with AIOTF ID to uniquely identify an AIoT Session between the NG-RAN and AIOTF which is corresponding to an AF service operation request. Correlation ID shall be unique within an AIOTF.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.7.4 AIoT Device Temporary Identifier
| A Device Temporary ID may be used as AIoT Identification Information in Inventory procedure if privacy protection is used. The details of how Device Temporary ID is generated, managed and used are specified in TS 33.369 [9].
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.8 Filtering Information
| The Filtering Information is used to identify or filter one or multiple AIoT Device(s). The Filtering Information is constructed by one or multiple filtering elements and each filtering element corresponds to a component (i.e. ID Type, PLMN Identifier, NID, Third Party Identifier or Identification Information) of the AIoT Device Permanent Identifier as defined in clause 5.7.
Each filtering element shall include:
- Component Type Information indicating a component of the AIoT Device Permanent Identifier that is used to match the bitstring.
- A bitstring which is used to compare with the component.
- An Offset from the beginning of the indicated component of the AIoT Device Permanent Identifier, which indicates the start location in the indicated component to be used to compare with the corresponding bitstring.
- A Length indicating the length of the bitstring.
When the Component Type Information of a filtering element indicates a PLMN ID, NID or Third-Party Identifier component, then the Offset and Length are not included in the filtering element, i.e. the whole component is compared with the bitstring.
When the Component Type Information of the filtering element indicates an Identification Information or ID Type component, the Offset and Length are always included and the indicated component is compared from the start location indicated by the Offset with the bitstring for its entire indicated Length. The AIOTF includes at most one filtering element within the Filtering Information for the ID Type, PLMN ID, NID and Third Party Identifier components of the AIoT Device Permanent Identifier.
There may be multiple filtering elements corresponding to the component Identification Information of the AIoT Device Permanent Identifier.
NOTE 1: It is assumed that the AIoT Device does not validate the number of filtering element(s) for any indicated component within the Filtering Information.
NOTE 2: The format of the Filtering Information is specified in clause 31.3 of TS 23.003 [6].
Figure 5.8-1: The example of the comparing the bitstring to the component
To determine whether an AIoT Device Permanent Identifier matches the Filtering Information, the bitstring of every filtering element within the Filtering Information is compared with the indicated component of the AIoT Device Permanent Identifier. If all the compared bitstrings match the corresponding component of the AIoT Device Permanent Identifier, then an AIoT Device Permanent Identifier matches the Filtering Information. If an AIoT Device Permanent Identifier does not contain an indicated component then it does not match the Filtering Information.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.9 AIoT Service Operation Result Aggregation
| An AIoT service operation may involve many AIoT Devices. The NG-RAN may perform AIoT service operation result aggregation with a specific Correlation ID based on the aggregation assistance information received from the AIOTF for a service operation request as specified in clause 5.4.
The AIOTF determines the aggregation assistance information based on the request from the AF or local configuration, which includes:
- Time interval: the fixed time interval for which NG-RAN collects multiple AIoT Devices’ operation responses before reporting the aggregated AIoT response to the AIOTF. The reporting based on time interval may potentially happen multiple times until the NG-RAN completes the request operation.
If the AF has provided a time interval, then the AIOTF should signal a time interval to the NG-RAN that is equal or shorter than the time interval received from the AF.
NOTE: Based on local configuration, the AIOTF can reject the AF request, e.g. if the AF provided time interval is shorter than a locally configured minimum interval.
If the AIOTF does not provide aggregation assistance information, the aggregation process in the NG-RAN may be determined by implementation.
The AIOTF may also aggregate the results of a requested service operation before sending them to the NEF or trusted AF.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.10 AIoT Device Location
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.10.1 Overview
| During inventory procedure (see clause 6.2.2) or command procedure (see clause 6.2.3), the AIOTF may be requested to report AIoT Device Locations. Based on operator policy, the AIOTF determines whether to provide the AIoT Device Location to the AF.
The Inventory Report(s) sent by NG-RAN include a RAN Reader ID for each reported AIoT Device. The location of each RAN Reader may be configured in the AIOTF. If configured, the AIOTF uses the location of RAN Reader to determine the location of the AIoT Device.
NOTE: The location format is defined based on the SLA between the operator and the AF, which is out the scope of 3GPP.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 5.11 AIoT Device Context in AIOTF
| The AIOTF supports management of the AIoT Device context information locally. The AIoT Device context includes e.g. the AIoT Device Permanent ID, the last known RAN reader information, RAN AIoT Device NGAP ID, etc. The last known RAN Reader information can be used to support the AIOTF to perform RAN Reader selection as defined in clause 5.3.3.
Table 5.11-1 below describes information storage structures for AIoT device context.
Table 5.11-1: AIoT Device Context in AIOTF
Field
Description
AIoT Device Permanent ID
Uniquely identifies the AIoT Device.
Last known RAN reader information
Indicate the last known RAN reader that serves the AIoT device.
RAN AIoT Device NGAP ID
Indicate the RAN AIoT Device NGAP ID used to transfer the NGAP AIoT Command messages towards the AIoT Device between AIOTF and NG-RAN.
NOTE: When to erase the stored AIoT Device context is up to implementation and local configuration.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6 AIoT Procedures
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.1 General
| Clause 6.2 describes the AIoT procedures and Network Function services for the 5GS by end-to-end information flows and making use of the NF service operations defined in clause 7, in those information flows.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2 AIoT Service Procedures
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.1 General
| Clause 6.2.2 provides the procedure for AIoT Inventory. Clause 6.2.3 provides the procedure for AIoT Command. Clause 6.2.5 provides the AIoT Session release procedure for AIoT Inventory and AIoT Command.
The AIOTF may perform the procedure in Clause 6.2.2 or Clause 6.2.3 for the resynchronization of T-ID as specified in clause 5.4.4 of TS 33.369 [9].
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.2 Inventory Procedure
| Figure 6.2.2-1 describes the inventory procedure.
The procedure focuses on the messages and parameters used for the communication between AIOTF and NG-RAN regardless of the path to access NG-RAN, see clause 4.2.2.1. The handling of the different communication paths is described in clause 6.2.4.
Figure 6.2.2-1: Inventory Procedure
1. The AF invokes Nnef_AIoT_Inventory Request (AF ID, [External Target Area information], [information about the target AIoT Device(s)], [Approximate number of AIoT Devices], [time interval], [location information requested]) service operation request to the NEF.
Information about the target AIoT Device(s) may include Filtering Information, as described in clause 5.8, or include complete AIoT Device Identifier(s). If Information about the target AIoT Device(s) is not included, the Inventory Request is for all AIoT Devices.
The approximate number of AIoT Devices, if provided, is used to determine the number of AIoT Devices expected to respond to this inventory AIoT service operation request, which is sent by AIOTF to the NG-RAN in the assistance information for NG-RAN in step 7 for proper radio resource allocation.
The time interval, if provided, is described in clause 5.9.
The location information requested parameter indicates whether the AF expects the network to provide the device location information.
2. The NEF may further authorize the AF request as specified in clause 5.6.
The NEF determines the Target Area information from the External Target Area information, and selects one or multiple AIOTF(s) to handle the request as specified in clause 5.3.1. If no AIOTF can be selected, the NEF rejects the Nnef_AIoT_Inventory request with an appropriate cause code and step 6 is performed before ending the procedure
3. The NEF invokes the Naiotf_AIoT_Inventory(AF ID, [Target Area information], [information about the target AIoT Device(s)], [Approximate number of AIoT Devices], [time interval], [location information requested]) service operation towards each of the selected AIOTF(s).
4. The AIOTF receives the Naiotf_AIoT_Inventory request and checks the parameters included in the request. The AIOTF may perform authorization as specified in clause 5.6. If the AIoT service operation request cannot be processed, the AIOTF rejects the AIoT service operation request with an appropriate cause code, and step 7 onwards are skipped.
The AIOTF generates a Correlation ID corresponding to this AIoT service operation request and the Correlation ID is used for the AIOTF to correlate the service operation responses received from NG-RAN to the AIOTF request. The AIOTF creates the AIoT Session for the AF service operation request, which is identified by the Correlation ID.
The AIOTF obtains security parameters from the ADM, as described in TS 33.369 [9].
The AIoT Identification Information to be provided to NG-RAN contains either Filtering Information as defined in clause 5.8, an AIoT Device Permanent Identifier as defined in clause 5.7.2 or an AIoT Device Temporary Identifier as defined in clause 5.7.4.
When the AIoT Identification Information includes an AIoT Device Temporary Identifier, the AIoT Device Temporary Identifier and related information is determined as specified in TS 33.369 [9].
If no AIoT Identification Information is provided to NG-RAN, then the NG-RAN inventories all AIoT Devices.
NOTE 1: The concerns of paging all or paging a large group of AIoT devices are described in TS 33.369 [9].
The AIoT Identification Information and security parameters are provided to NG-RAN in step 7.
The AIOTF performs Reader Selection, see clause 5.3.3. If no NG-RAN or RAN Reader can be selected, the AIOTF rejects the AIoT service operation request with an appropriate cause code.
The AIOTF determines assistance information as described in clause 5.4, taking into account the parameters provided in the AIoT service operation request.
The AIOTF may perform AMF selection as described in clause 5.3.4.
5. AIOTF sends the AIoT Inventory Service Response to the NEF containing the accept or reject result for the AIoT service operation request based on step 4.
6. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT service operation request as specified in clause 8.3.
7. The AIOTF sends the Inventory Request message including AIoT Identification Information and security parameters determined in step 4 to be included in the paging message, Correlation ID, Requested Service Area Information and assistance information to the selected NG-RAN as specified in TS 38.413 [10].
8. The NG-RAN sends an Inventory Response to the AIOTF with the Correlation ID indicating that the Inventory Request is received successfully and will perform the AIoT service operation accordingly as specified in TS 38.413 [10]. If the Inventory Request is not rejected, then an AIoT Session is created in the NG-RAN. After this step, the AIoT Session between the NG-RAN and AIOTF identified by correlation ID is established.
9. Upon reception of the Inventory Request message from the AIOTF, the RAN Reader(s) will execute the inventory operation as specified in TS 38.300 [5] and TS 38.391 [11]. The RAN Reader(s) broadcast the paging message that includes the AIoT Identification Information and the security parameters.
If the received AIoT Identification Information contains:
- Filtering Information, the AIoT Device determines whether it matches the AIoT Identification Information, as described in clause 5.8.
- AIoT Device Temporary Identifier, the AIoT Device determines whether it matches the AIoT Identification Information, as described TS 33.369 [9].
- AIoT Device Permanent Identifier, the AIoT Device determines whether it matches the AIoT Identification Information by comparing it with the stored AIoT Device Permanent Identifier.
The AIoT Device determines whether it matches the AIoT Identification Information, as described in clause 5.8.
If an AIoT device matches the AIoT Identification Information in the paging message, the AIoT Device responds to the paging message and sends an AIOT NAS message that includes its device specific authentication information as specified in TS 33.369 [9] and optionally the AIoT Device Permanent Identifier if privacy protection is not used.
10. NG-RAN sends one or more Inventory Report messages to the AIOTF including the Correlation ID, Reader ID and the AIOT NAS message(s) from the AIoT Device(s) as specified in TS 38.413 [10]. The NG-RAN may aggregate multiple Inventory Report messages based on the assistance information before reporting the response to the AIOTF as described in clause 5.9. The AIOTF stores the mapping between the Reader ID and AIoT Device ID(s) as part of the AIoT Device context.
When the NG-RAN detects that no more AIoT Devices will respond to the inventory procedure, the NG-RAN informs the AIOTF by including the Inventory Complete Indication in the last Inventory Report message.
11. The AIOTF authenticates the AIoT Device and retrieves the AIoT Device Permanent Identifier as specified in TS 33.369 [9]. The AIOTF may aggregate the results.
12. If the NG-RAN has sent an inventory complete indication in step 10, the AIOTF triggers the AIoT Session Release procedure defined in clause 6.2.5 to release the AIoT Session between the NG-RAN and the AIOTF.
13. The AIOTF reports the progress of the Naiotf_AIoT_Inventory request to the NEF by sending the Naiotf_AIoT_Notify message including a list of AIoT Device Permanent Identifier (s) and optionally location of each AIoT Device. The AIOTF may send multiple reports.
Based on operator policy, if the location information is requested by the AF and if the location of the reader is configured, the AIOTF uses the Reader ID reported from NG-RAN in step 10 to determine the AIoT Device Location.
The AIOTF in the final Naiotf_AIoT_Notify message indicates it is the last report for this operation. When the last report is sent, the AIOTF ends the AIoT Session. If multiple AIOTFs are involved in the procedure, the NEF may receive Naiotf_AIoT_Notify's from multiple AIOTFs.
14. When receiving the Naiotf_AIoT_Notify message from AIOTF, the NEF informs the AF of the outcome of the Nnef_AIoT_Inventory request by sending the Nnef_AIoT_Notify message(s) including the AIoT Device Permanent Identifier(s) and optionally location of each AIoT Device. The NEF in the final Nnef_AIoT_Notify message indicates that it is the last report for this operation.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.3 Command Procedure
| Figure 6.2.3-1 depicts the command procedure.
The procedure focuses on the messages and parameters used for the communication between AIOTF and NG-RAN regardless of the path to access NG-RAN, see clause 4.2.2.1. The handling of the different communication paths is described in clause 6.2.4.
Figure 6.2.3-1: Command Procedure
1. The AF sends the Nnef_AIoT_Command Request (AF ID, Command Type, information about the target AIoT Device(s), [External Target Area information], [Approximate number of AIoT Devices], [Approximate D2R message size], [Command type specific parameters], [location information requested]) message to NEF.
Information about the target AIoT Device(s) may include Filtering Information, as described in clause 5.8, or include complete AIoT Device Identifier(s).
The approximate number of AIoT Devices (see clause 5.4), if provided, is used to indicate the number of AIoT Devices expected to respond to this AIoT service operation request, which is sent by AIOTF to the NG-RAN in the assistance information as specified in clause 5.4.
Command Type provides the operation to be performed and the Command type specific parameters provides the required parameters for the operation. The service operations are described in clause 5.2.2.
2. Step 2 of the Inventory Procedure specified in clause 6.2.2 is performed for External Target Area information processing and AIOTF selection with the following clarifications:
- If AIOTF selection fails, the NEF rejects the Nnef_AIoT_Command request and step 6 of this procedure is performed instead.
3. The NEF sends Naiotf_AIoT_Command Request message (AF ID, Command Type, information about the target AIoT Device(s), [Target area information], [Approximate number of AIoT Devices], [Approximate D2R message size], [Command type specific parameters], [location information requested]) message to the selected AIOTF(s).
4. The AIOTF receives the Naiotf_AIoT_Command Request and checks the parameters included in the request. The AIOTF performs Reader Selection as specified in clause 5.3.3. If no NG-RAN or RAN Reader can be selected, the AIOTF rejects the AIoT Command request with an appropriate cause code.
The AIOTF generates a Correlation ID corresponding to this AIoT service operation request and the Correlation ID is used for the AIOTF to correlate the service operation responses received from NG-RAN to the request. The AIOTF creates the AIoT Session for the AF service operation request, which is identified by the Correlation ID.
The AIOTF performs Reader Selection, see clause 5.3.3. If no NG-RAN or RAN Reader can be selected, the AIOTF rejects the AIoT service operation request with an appropriate cause code.
The AIOTF determines assistance information as described in clause 5.4, taking into account the parameters provided in the AIoT service operation request.
The AIOTF performs AF authorization for AIoT service operation request as described in clause 5.6.
The AIOTF may perform AMF selection as described in clause 5.3.4.
5. AIOTF sends the Naiotf_AIoT_Command Response message (accept or reject, [cause code]) to the NEF.
6. NEF sends the Nnef_AIoT_Command Response message (accept or reject, [cause code]) to the AF. If the response was a reject the procedure stops here.
7. Step 7 to step11 of procedure for Inventory specified in clause 6.2.2 are performed with the following clarifications:
- In step 7, the AIOTF also includes follow on command indication in the Inventory Request message to inform the NG-RAN command delivery occurs after the inventory.
- In step 10, the NG-RAN also includes the RAN AIoT Device NGAP ID for each AIoT Device in the Inventory Report as specified in TS 38.413 [10].
- In step 11, the AIOTF authenticates the AIoT Devices as specified in TS 33.369 [9], and determines whether the command should be sent to an AIoT Device, e.g., by checking the Target AIoT device information. The AIOTF updates the corresponding AIoT device context in the AIOTF to include the RAN AIoT Device NGAP ID.
If none of successful Inventory response is received, Step 8 -11 is not performed and the AIOTF sends a failure report to the NEF in step 12.
8. For each successful Inventory response received, the AIOTF sends Command Request message (Correlation ID, [Reader ID], NAS Command Request, [Approximate D2R message size], RAN AIoT Device NGAP ID for each AIoT Device) to the NG-RAN directly or as a NGAP AIoT information via an AMF as specified in clause 6.2.4. The NAS Command Request message includes the AIoT data. The Correlation ID is as the same as the Correlation ID generated in step 4. The RAN AIoT Device NGAP ID for each AIoT Device is used by the NG-RAN to determine the AIoT device context in NG-RAN as specified in TS 38.413 [10].
The AIOTF uses the Command Type and Command type specific parameters received in Step 3 to determine the NAS Command Request to send to the AIoT Device, as described in clause 5.2.2.
The protection of the NAS Command Request message is specified in clause 5.3 of TS 33.369 [9].
NOTE 1: Command Request(s) can be sent to NG-RAN when inventory procedure is ongoing.
9. The NG-RAN sends the AS R2D message (NAS Command Request) to the AIoT Device as defined in TS 38.391 [11].
10. The AIoT Device performs security check of the received NAS Command Request and sends the AS D2R message (including NAS Command Response) to the NG-RAN as defined in TS 38.391 [11]. The NAS Command Response message may include the AIoT data.
The protection of the NAS Command Response message is specified in clause 5.3 of TS 33.369 [9].
11. The NG-RAN responds with a Command Response message (Correlation ID, Reader ID, NAS Command Response, RAN AIoT Device NGAP ID) to the AIOTF directly or as a NGAP AIoT information via an AMF as specified in clause 6.2.4. The AIOTF determines the AIoT device context by the RAN AIoT Device NGAP ID received.
If the NAS Command Response indicates the NAS Command type is not supported by the AIoT Device, the AIOTF reports the error result in step 13 and step 14.
NOTE 2: The AIOTF can take this into account to avoid initiating further command procedures of the same command type towards the AIoT Device by implementation.
12. After receiving the inventory complete indication in the last inventory report from the NG-RAN, when the AIOTF has completed sending Command Requests and all the Command Response have been received, the AIOTF initiates the AIoT Session Release Procedure in clause 6.2.5 to release the AIoT Session created during the Inventory Procedure.
13. The AIOTF reports the result of the Naiotf_AIoT_Command request to the NEF by sending the Naiotf_AIoT_Command Notify message (a list of AIoT Device(s) response information (AIoT Device ID(s), AIoT data and optionally location of each AIoT Device), AF ID, [Last Report Indication]). If multiple AIOTFs are involved in the procedure, the NEF may receive Naiotf_AIoT_Command Notify messages from multiple AIOTFs.
Based on operator policy, if the location information is requested by the AF and if the location of the reader is configured, the AIOTF uses the Reader ID reported from NG-RAN during inventory in step 7 to determine the AIoT Device Location.
When the last report is sent, the AIOTF ends the AIoT Session.
14. The NEF informs the AF of the result of the Nnef_AIoT_Command request by sending the Nnef_AIoT_Command Notify message (a list of AIoT Device(s) response information (AIoT Device ID(s), AIoT data and optionally location of each AIoT Device), AF ID, [Last Report Indication]).
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.4 Procedures between AIOTF and NG-RAN for Indirect Connectivity
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.4.1 Overview
| An AIOTF and NG-RAN can use an indirect interface via an AMF as described in clause 4.2.2.4. The procedure for NGAP message delivery to NG-RAN is defined in clause 6.2.4.2 and the procedure for message delivery from NG-RAN is defined in clause 6.2.4.3.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.4.2 Message delivery to NG-RAN
| When the AIOTF sends commands the AMF receives an Namf_AIoT_MessageDelivery request and sends the corresponding NGAP command to NG-RAN. The additional steps used for indirect interface between AIOTF and NG-RAN are shown in Figure 6.2.4.2-1.
Figure 6.2.4.2-1: Procedure for NGAP message delivery to NG-RAN using indirect connectivity via an AMF
1. The AIOTF sends Namf_AIoT_MessageDelivery Request message (NGAP AIoT information, NG-RAN ID, AIOTF ID, Correlation ID, AIoT NGAP Message Type, Notification endpoint, [RAN AIoT Device NGAP ID]) to the AMF.
The AIoT NGAP Message Type identifies the NGAP message to send to NG-RAN and NGAP AIoT information is provided to NG-RAN in the NGAP message.
If the AMF receives a Notification endpoint, the AMF creates a context for the transaction and stores the NG-RAN ID, AIOTF ID, Correlation ID and Notification endpoint. The AIOTF is implicitly subscribed to Namf_AIoT_Notify events.
2. The AMF responds to the AIOTF with a result indicating whether the AMF will handle the request. If a failure is indicated by the result indication, then the procedure stops and the remaining steps are skipped.
3. The AMF sends an NGAP message (AIOTF ID, Correlation ID, NGAP AIoT information, [RAN AIoT Device NGAP ID]) to the target NG-RAN.
4. The procedure for handling NGAP messages from NG-RAN is used for route NGAP messages from NG-RAN to the AIOTF, see clause 6.2.4.3.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.4.3 Message delivery to AIOTF
| When the AMF receives an NGAP message from NG-RAN, for example, responses to a procedure or events like Inventory Reports, the AMF determines which AIOTF to send a Namf_AIoT_Notify to and sends the information from NG-RAN to that AIOTF. The additional steps used for indirect interface from NGAP towards AIOTF is shown in Figure 6.2.4.3-1.
Figure 6.2.4.3-1: Procedure for NG-RAN event handling using indirect connectivity via an AMF
1. Before any NGAP message can be routed from NG-RAN to the AIOTF, the AMF needs routing information to be able to route the messages from NG-RAN to the AIOTF, see clause 6.2.4.2. The same context can be used route multiple NGAP messages from NG-RAN.
2. NG-RAN sends an NGAP message (AIOTF ID, Correlation ID, NGAP AIoT information, [RAN AIoT Device NGAP ID]) to an AMF. NGAP AIoT information is determine by NG-RAN depending upon the operation the NGAP message relates to.
3. AMF determines the Notification endpoint using the AIOTF ID and Correlation ID received in step 1 from NG-RAN, and then sends the Namf_AIoT_Notify message (AIoT NGAP Message Type, NGAP AIoT information) to the AIOTF.
Step 2 and step 3 are repeated for each NGAP message received from NG-RAN.
If the message received from NG-RAN is an Inventory Failure indicating an error or an AIOT Session Release Complete, then the AMF releases the context which is associated with the AIOTF ID and Correlation ID, after sending the Namf_AIoT_Notify message to the AIOTF.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 6.2.5 AIoT Session Release Procedure
| This procedure is used to release the AIoT Session between the NG-RAN and the AIOTF. The AIoT Session release procedure can be triggered by the AIOTF or the NG-RAN node and is specified in TS 38.413 [10].
The initiation of AIoT Session release may be:
- NG-RAN-initiated e.g. if the NG-RAN detects no AIoT Devices responds to the inventory procedure or the command procedure; or
- AIOTF-initiated, e.g. if the AIOTF fails validating the results of AIOT NAS Inventory Response as specified in TS 33.369 [9]in the command procedure.
Both NG-RAN-initiated and AIOTF-initiated AIoT Session Release procedures are shown in Figure 6.2.5-1.
Figure 6.2.5-1: AIoT Session Release Procedure
1. NG-RAN may decide to initiate the AIoT Session release procedure. NG-RAN sends AIoT Session Release request message (Correlation ID, Cause) to the AIOTF directly or as a NGAP AIoT information via an AMF as specified in clause 6.2.4.
2. If the AIOTF receives the AIoT Session Release request message or the AIOTF decides to terminate all activities related to the AIoT Session, the AIOTF sends an AIoT Session Release Command message (Correlation ID, Cause) to the NG-RAN directly or as a NGAP AIoT information via an AMF as specified in clause 6.2.4.
3. The NG-RAN node releases the AIoT Session and radio resources related to the AIoT session identified by the Correlation ID provided by the AIOTF, as specified in TS 38.300 [5]. And the NG-RAN confirms the AIoT Session Release by returning an AIoT Session Release Complete message (Correlation ID) to the AIOTF directly or as a NGAP AIoT information via an AMF as specified in clause 6.2.4. The AIOTF releases AIoT Session.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7 Network Functions Services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.1 General
| The following clauses provide for each involved NF the NF services it exposes through its service-based interfaces for AIoT Services.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.2 AIOTF services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.2.1 General
| The AIOTF supports to expose AIoT services towards the AF or the NEF as described in Table 7.2.1-1.
Table 7.2.1-1: NF services provided by the AIOTF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Naiotf_AIoT
Inventory
Request/Response
NEF, AF
Command
Request/Response
NEF, AF
Notify
Subscribe/Notify
NEF, AF
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.2.2 Naiotf_AIoT_Inventory service operation
| Service operation name: Naiotf_AIoT_Inventory.
Description: The NF consumer requests an inventory operation for one or multiple AIoT Device(s).
Inputs, Required:
1) AF ID.
2) At least one of the following parameters are included:
- Target Area information for the inventory operation.
- Information about the target AIoT Device(s):
- either the AIoT Device ID(s) or the filtering information(see clause 5.8) for multiple target AIoT Devices.
3) Notification Endpoint.
Inputs, Optional:
1) Information to be used for resource allocation:
- Approximate number of AIoT Devices.
2) Time Interval for result aggregation.
3) Location information requested.
Outputs, Required: Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.2.3 Naiotf_AIoT_Command service operation
| Service operation name: Naiotf_AIoT_Command.
Description: The NF consumer requests a command operation for one or multiple AIoT Device(s).
Inputs, Required:
1) AF ID.
2) At least one of the following parameters are included:
- Target Area information for the command operation.
- Information about the target AIoT Device(s):
- either the AIoT Device ID(s) or the filtering information(see clause 5.8) for multiple AIoT Devices.
3) Notification Endpoint.
4) Command Type: Read, Write or Permanent Disable.
Inputs, Optional:
Information to be used for resource allocation:
- Approximate number of AIoT Devices.
- Approximate message size from the AIoT Device for Read Operation.
- If the Command Type is Read, the offset to read application data from and the length of application data to read shall be included.
- If the Command Type is Write, the offset where to write the application data, the application data to write and its length shall be included.
- Location information requested.
Outputs, Required: Transaction ID, Result indication (Success or Failure), Failure Cause in case of Failure.
Outputs, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.2.4 Naiotf_AIoT_Notify service operation
| Service operation name: Naiotf_AIoT_Notify
Description: The AIOTF uses this service operation to notify the results or status of the service operation towards the NF consumers. If the NF consumer invokes the Naiotf_AIoT_Inventory, or Naiotf_AIoT_Command service operation, the NF consumer implicitly subscribes to the results of the requested service operation.
Inputs, Required:
1) Common report information: Transaction ID.
Inputs, Optional:
1) List of AIoT Device ID or Failure Cause in case of Failure.
2) Read command specific report information: Information obtained from each target AIoT Device corresponding to each reported AIoT Device ID.
3) The Last Report Indication, indicating the notify is the last notify for an AIoT service operation.
4) Location information of each AIoT Device.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.3 AMF services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.3.1 General
| AMF supports to expose AIoT services towards the AIOTF as described in Table 7.3.1-1. The Namf_AIoT AMF service is used when the NG-RAN and the AIoTF communicate indirectly via an AMF.
Table 7.3.1-1: NF services provided by the AMF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Namf_AIoT
MessageDelivery
Request/Response
AIOTF
Notify
Subscribe/Notify
AIOTF
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.3.2 Namf_AIoT_MessageDelivery service operation
| Service operation name: Namf_AIoT_MessageDelivery
Description: The NF consumer requests to send AIoT data towards NG-RAN or AIoT devices.
Inputs, Required:
1) NGAP AIoT Information to deliver to NG-RAN.
2) NG-RAN ID.
3) AIoT NGAP Message Type ("Inventory" or "Command").
4) AIOTF Identifier and Correlation Identifier, this is to allow identifying the association between NG-RAN and AMF.
Outputs, Required: Result indication (Success or Failure), Failure Cause in case of Failure.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.3.3 Namf_AIoT_Notify service operation
| Service operation name: Namf_AIoT_Notify
Description: The NF consumer requests to receive AIoT data from NG-RAN or AIoT devices. If the NF consumer invokes the Namf_AIoT_MessageDelivery, the NF consumer implicitly subscribes to receive the AIoT data from NG-RAN or AIoT devices.
Inputs, Required:
1) NGAP Information received from NG-RAN.
Input, Optional: None.
Outputs, Required: Operation execution result indication.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.4 NEF services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.4.1 General
| In addition to those defined in clause 7.2.8 of TS 23.501 [3] and clause 5.2.6 of TS 23.502 [4], table 7.4.1-1 illustrates additional NEF services to support AIoT.
Table 7.4.1-1: NF Services provided by NEF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnef_AIoT
Inventory
Request/Response
AF
Command
Request/Response
AF
Notify
Subscribe/Notify
AF
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.4.2 Nnef_AIoT_Inventory service operation
| Service operation name: Nnef_AIoT_Inventory
Description: The consumer requests to perform an inventory operation for an AIoT Device or multiple AIoT Devices.
Input, Required:
1) AF ID.
2) At least one of the following parameters are included:
- External Target Area information.
- Either AIoT Device ID(s) or AIoT Device ID filter information for the inventory operation.
3) Notification Endpoint.
Input, Optional: Approximate number of AIoT Devices, time interval, location information requested.
Output, Required: AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.4.3 Nnef_AIoT_Command service operation
| Service operation name: Nnef_AIoT_Command
Description: The consumer requests to perform a command operation for an AIoT Device or multiple AIoT Devices.
Input, Required:
1) AF ID.
2) At least one of the following parameters are included:
- External Target Area information.
- Either AIoT Device ID(s) or AIoT Device ID filter information for the command operation.
3) Notification Endpoint.
4) Command type (Read, Write, or Permanent Disable).
Input, Optional: Approximate number of AIoT Devices, if the Command Type is Read, the offset to read application data from and the length of application data to read shall be included, if the Command Type is Write the offset where to write the application data, the application data to write and its length shall be included, Approximate message size from the AIoT Device for Read command type, location information requested.
Output, Required: AF Transaction ID, Result indication, Failure cause in case of Failure.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.4.4 Nnef_AIoT_Notify service operation
| Service operation name: Nnef_AIoT_Notify
Description: The consumer receives notification of the status or results of the requested service operation. If the consumer invokes the Nnef_AIoT_Inventory, or Nnef_AIoT_Command service operation, the consumer implicitly subscribes to the results of the requested service operation.
Input, Required:
1) AF Transaction ID.
Input, Optional:
1) a list of AIoT Device ID(s), Failure Cause in case of Failure.
2) Read command specific report information: Information obtained from each target AIoT Device.
3) The Last Report Indication, indicating the notify is the last notify for an AIoT service operation.
4) Location information of each target AIoT Device.
Output, Required: Result indication.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.5 ADM services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.5.1 General
| The following table shows the Nadm_DM Service and Service Operations.
Table 7.5.1-1: NF services provided by ADM
NF service name
Service Operations
Operation Semantics
Example Consumer(s)
Nadm_DM
Query
Request/Response
AIOTF, NEF
Update
Request/Response
AIOTF
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.5.2 Nadm_DM_Query service operation
| Service operation name: Nadm_DM_Query
Description: NF service consumer may request the AIoT device profile data or the AF authorization data from the ADM.
Inputs, Required: AIoT Device Permanent ID or AF ID.
Input, Optional: None.
Outputs, Required: the AIoT device profile data or the AF authorization data.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.5.3 Nadm_DM_Update service operation
| Service operation name: Nadm_DM_Update
Description: NF service consumer may update the AIoT device profile data in the ADM.
Inputs, Required: AIoT Device Permanent ID, updated AIoT device profile data.
Input, Optional: None.
Outputs, Required: Result indication (Success or Failure), Failure Cause in case of Failure.
Output, Optional: None.
|
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.6 UDR Services
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.6.1 Nudr_DataManagement (DM) Service
| |
b2d353929edcfdfba7b1da5c3ee436ab | 23.369 | 7.6.1.1 General
| The ADM makes use of the Nudr_DM service for Ambient IoT Data, as described in clause 5.2.12 of TS 23.502 [4].
The Ambient IoT Data includes AIoT Device Profile Data and AF Authorization Data. The AIoT Device Permanent ID is the Data Key of AIoT Device Profile Data, while the AF ID is the Data Key of AF Authorization Data, as illustrated in Table 7.6.1.1-1.
Table 7.6.1.1-1: Data keys
Data Set
Data Subset
Data Key
Data Sub Key
Ambient IoT Data
AIoT Device Profile Data
AIoT Device Permanent ID
-
AF Authorization Data
AF ID
-
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-01
SA2#166 AH-e
S2-2501256
-
-
-
Proposed skeleton agreed at SA2#166AH-e
0.0.0
2025-06
SP#108
SP-250489
-
-
-
MCC editorial update for presentation to TSG SA for approval
1.0.0
2025-06
SP#108
-
-
-
-
MCC editorial update for publication after TSG SA approval
19.0.0
2025-09
SP#109
SP-250948
0001
1
F
Removal of AIoT service type provided to NG-RAN
19.1.0
2025-09
SP#109
SP-250948
0005
2
B
Session release procedure and correlation ID
19.1.0
2025-09
SP#109
SP-250948
0007
2
B
Support of Device Location in Ambient IoT
19.1.0
2025-09
SP#109
SP-250948
0010
2
F
Nudr Service for Accessing AIoT Data
19.1.0
2025-09
SP#109
SP-250948
0043
1
F
Removal of EN for Device ID
19.1.0
2025-09
SP#109
SP-250948
0050
2
F
Term alignment and clarifications on AIOTF and Reader Selection
19.1.0
2025-09
SP#109
SP-250948
0054
2
F
Update of Procedures between AIOTF and NG-RAN for Indirect Connectivity
19.1.0
2025-09
SP#109
SP-250948
0063
2
F
Corrections to the Filtering Information
19.1.0
2025-09
SP#109
SP-250948
0065
3
F
Update to AIoT Area related
19.1.0
2025-09
SP#109
SP-251277
0068
1
F
Private Network Deployment Alignment
19.1.0
2025-12
SP#110
SP-251328
0029
5
F
Resolve Security Related ENs
19.2.0
2025-12
SP#110
SP-251328
0072
2
F
Update on Filtering Information
19.2.0
2025-12
SP#110
SP-251328
0078
1
F
Filtering Information security guidance
19.2.0
2025-12
SP#110
SP-251328
0084
1
F
Alignment for the security aspects
19.2.0
2025-12
SP#110
SP-251328
0085
2
F
Alignment related to completion and Session Release
19.2.0
2025-12
SP#110
SP-251328
0091
3
F
Security Alignment and Resolve ENs
19.2.0
2025-12
SP#110
SP-251328
0092
3
F
Handling of Unsupported Command
19.2.0
2025-12
SP#110
SP-251328
0096
2
F
Clarification on AmbientIoT Device
19.2.0
2025-12
SP#110
SP-251328
0101
7
B
Updates to AIOTF and ADM to support temporary ID
19.2.0
2025-12
SP#110
SP-251328
0103
2
F
Temporary Device ID description
19.2.0
2025-12
SP#110
SP-251328
0106
8
F
Update to Inventory procedure for use of Temporary Device ID
19.2.0
2025-12
SP#110
SP-251328
0109
2
F
Support of AIoT device context management
19.2.0
2025-12
SP#110
SP-251328
0123
2
F
Clarification on AIOT Device Profile Data and AIoT Security Data
19.2.0
2025-12
SP#110
SP-251328
0134
1
F
Update on AIoT Permanent ID Length
19.2.0
|
85bf19f2724bd70687927dc10941722c | 23.379 | 1 Scope
| This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service. The MCPTT service utilizes the common functional architecture to support MC services over LTE including the common services core defined in 3GPP TS 23.280 [16].Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.179 [2] and 3GPP TS 22.280 [17].
The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [8]. Certain application functions of the MCPTT service such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats.
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 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 22.179: "Mission Critical Push to Talk (MCPTT)"; Stage 1.
[3] 3GPP TS 23.002: "Network Architecture".
[4] 3GPP TS 23.203: "Policy and charging control architecture".
[5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[6] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
[8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[10] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[11] Void
[12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[13] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[14] void
[15] void
[16] 3GPP TS 23.280: "Common functional architecture to support mission critical services".
[17] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1".
[18] 3GPP TS 29.283: "Diameter data management applications".
[19] 3GPP TS 33.180: "Security of the mission critical service".
[20] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
|
85bf19f2724bd70687927dc10941722c | 23.379 | 3 Definitions, symbols and abbreviations
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR 21.905 [1].
Automatic commencement mode: A mode in which the initiation of the private call does not require any action on the part of the receiving MCPTT user.
First-to-answer call: A call that is started when the first MCPTT user among multiple potential target recipients' answers. This call requires the answering MCPTT user to answer manually; automatic answer is not allowed
Group call: A mechanism by which an MCPTT user can make a one-to-many MCPTT transmission to other users that are members of MCPTT group(s).
Group home MCPTT system: The MCPTT system where the MCPTT group is defined.
Group host MCPTT server: The MCPTT server within an MCPTT system that provides centralised support for MCPTT services of an MCPTT group defined in a group home MCPTT system.
Manual commencement mode: A mode in which the initiation of the private call requires the receiving MCPTT user to perform some action to accept or reject the call setup.
MCPTT client: An instance of an MC service client that provides the client application function for the MCPTT service.
MCPTT group: An MC service group configured for MCPTT service.
MCPTT group affiliation: An MC service group affiliation for MCPTT.
MCPTT group de-affiliation: An MC service group de-affiliation for MCPTT.
MCPTT ID: An instance of an MC service ID within the MCPTT service.
MCPTT server: An instance of an MC service server that provides the server application function for the MCPTT service.
On-network MCPTT service: The collection of functions and capabilities required to provide MCPTT via EPS bearers using E-UTRAN to provide the last hop radio bearers.
Preconfigured MCPTT group: an MCPTT group used only for regrouping that has been configured in advance of a group or user regrouping operation to serve as the source of regroup group configuration.
Pre-selected MCPTT user profile: An instance of the pre-selected MC service user profile for MCPTT.
UE-to-network relay MCPTT service: The collection of functions and capabilities required to provide MCPTT via a ProSe UE-to-network relay using ProSe direct communication paths to provide the last hop radio bearer(s).
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 [2] apply:
Dispatcher
Floor control
Group-broadcast group
MCPTT administrator
MCPTT service
MCPTT system
MCPTT UE
MCPTT user
MCPTT User Profile
Mission Critical Organization
Mission Critical Push To Talk
Off-network MCPTT service
Partner MCPTT system
Primary MCPTT system
Private call
Multi-talker control
User-broadcast group
For the purposes of the present document, the following terms and definitions given in IETF RFC 5245 [13] apply:
Candidate
Candidate pair
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [16] apply:
Ad hoc Group Communication
Active MC service user profile
Chat group
MC service client
MC service group
MC service group affiliation
MC service group de-affiliation
MC service ID
MC service server
Pre-arranged group
Pre‑selected MC service user profile
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [17] apply:
Functional alias
|
85bf19f2724bd70687927dc10941722c | 23.379 | 3.2 Symbols
| For the purposes of the present document, the following symbols given in 3GPP TS 22.179 [2] apply:
B1
B2
N2
N3
N4
N5
N6
N7
N10
N11
|
85bf19f2724bd70687927dc10941722c | 23.379 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 [1].
APN Access Point Name
ARP Allocation and Retention Priority
BM-SC Broadcast Multicast Service Centre
CHAP Challenge-Handshake Authentication Protocol
CSCF Call Server Control Function
DL Downlink
DPF Direct Provisioning Function
E-UTRAN Evolved Universal Terrestrial Radio Access Network
E2EE End to End Encryption
ECGI E-UTRAN Cell Global Identifier
EPC Evolved Packet Core
EPS Evolved Packet System
GBR Guaranteed Bit Rate
GCS AS Group Communication Service Application Server
GCSE_LTE Group Communication Service Enabler over LTE
GRUU Globally Routable User agent URI
HLR Home Location Register
HSS Home Subscriber Server
HTTP Hyper Text Transfer Protocol
I-CSCF Interrogating CSCF
ICE Interactive Connectivity Establishment
IM CN IP Multimedia Core Network
IMPI IP Multimedia Private Identity
IMPU IP Multimedia PUblic identity
IMS IP Multimedia Subsystem
ITSI Individual TETRA Subscriber Identity
LMR Land Mobile Radio
MBMS Multimedia Broadcast and Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MC Mission Critical
MC ID Mission Critical user identity
MCPTT Mission Critical Push To Talk
MCPTT AS MCPTT Application Server
MCPTT group ID MCPTT group identity
MCPTT ID MCPTT user identity
NAT Network Address Translation
PAP Password Authentication Protocol
P-CSCF Proxy CSCF
PCC Policy and Charging Control
PCRF Policy and Charging Rules Function
PLMN Public Land Mobile Network
ProSe Proximity-based Services
PSI Public Service Identity
PTT Push To Talk
QCI QoS Class Identifier
QoS Quality of Service
RAN Radio Access Network
RF Radio Frequency
RSI Radio Set Identity
S-CSCF Serving CSCF
SAI Service Area Identifier
SDF Service Data Flow
SIP Session Initiated Protocol
SSL Secure Sockets Layer
TLS Transport Layer Security
TMGI Temporary Mobile Group Identity
UM Unacknowledged Mode
URI Uniform Resource Identifier
USB Universal Serial Bus
WLAN Wireless Local Area Network
|
85bf19f2724bd70687927dc10941722c | 23.379 | 4 Introduction
| The MCPTT service supports communication between several users (i.e. group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users.
The MCPTT architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [16] and aspects of the IMS architecture defined in 3GPP TS 23.228 [5], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE_LTE) architecture defined in 3GPP TS 23.468 [9] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [6] to enable support of the MCPTT service.
The MCPTT UE primarily obtains access to the MCPTT service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [8]. Certain application functions of MCPTT service such as dispatch and administrative functions can be supported using either MCPTT UEs in E-UTRAN or using MCPTT UEs via non-3GPP access networks.
NOTE: Dispatch consoles and devices used by MCPTT service administrators are considered MCPTT UEs in the MCPTT architecture.
MCPTT UEs that use non-3GPP access can only support a subset of the functionality specified in this specification that is supported by the non-3GPP access network.
The MCPTT system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [20].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5 Architectural requirements
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 5.1 Media routing requirements
| The voice media flow for a private call shall be routed according to one of the following two options:
a) Option 1:
1) Through the primary MCPTT system if both users in the call belong to the same organisation; or
2) Through the primary MCPTT system of both users, if the users in the call do not belong to the same organisation.
b) Option 2: The voice media flow may be routed locally, under the control of the primary MCPTT system, through an entity allowing the duplication of the media flow to the primary MCPTT system of each user.
The voice media flow for a group call shall be routed to the group home MCPTT system.
The routing of media flow shall be end-to-end from transmitter to receiver(s), except for the MCPTT control function.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.2 Requirements for user identity management
| To allow for confidentiality of user identities in various cases of business relationship as defined in clause 6, the MCPTT application may provide public user identities to the MCPTT UE, to be used by MCPTT UE for MCPTT services.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.3 MCPTT group affiliation and MCPTT group de-affiliation
| MCPTT group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [16]. In addition, the following requirements shall be fulfilled by the MCPTT service for MCPTT users affiliated to MCPTT groups:
- MCPTT users receive notifications for MCPTT group call setup and invitations for their affiliated MCPTT group(s).
- MCPTT users receive media and events from their affiliated MCPTT group(s).
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.4 MCPTT call requirements
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 5.4.1 General
| The on-network MCPTT service shall support the use of pre-established sessions.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.4.2 Group call requirements
| The MCPTT service shall support the chat group (restricted) call model for MCPTT group call.
The MCPTT service shall support the pre-arranged group call model for MCPTT group call.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.5 GCS AS requirements for the MCPTT service
| The GCS AS architecture requirements for MC services are specified in 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.6 Group selection
| The following functionalities shall be supported by the MCPTT service.
a. The MCPTT user shall select an affiliated group to initiate a new group call or transmit media in an existing group call.
b. An authorized MCPTT user (e.g., dispatcher) may remotely force or request to change other on-network MCPTT users' selected MCPTT group to a particular affiliated group.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7 Bearer management
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.1 General
| The MCPTT UE shall use the APNs as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.2 EPS bearer considerations
| The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [16] shall apply.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.2.1 Void
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.2.2 Void
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.3 EPS unicast bearer considerations for MCPTT
| For an MCPTT call session request, resources shall be requested utilising interaction with dynamic PCC. The MCPTT system shall request resources over Rx to a PCRF. The dedicated bearer for voice shall utilise the QCI value of 65 (as specified in 3GPP TS 23.203 [4]) and the bearer for MCPTT-4 reference point messaging shall utilise the QCI value of 65 or the QCI value of 69 (as specified in 3GPP TS 23.203 [4]). The request of resources over Rx shall include an application identifier for MCPTT in order for the PCRF to evaluate the correct QCI.
The UE is required to support at minimum one UM bearer which is used for MCPTT voice (see annex A in 3GPP TS 36.331 [12]).
Depending on operator policy:
- the MCPTT system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or
- the EPS bearers for MCPTT call may enable pre-emption of lower priority EPS bearers if the maximum number of UM bearers has been reached in favour of MCPTT initiated EPS bearer, if the EPS bearer used for MCPTT call has higher priority level (ARP) than the UM bearer(s) used for other application(s) and if the bearers for non MCPTT application are pre-emptable. In this case, the EPS bearer for MCPTT call pre-empts one of the existing EPS bearers when the maximum number of bearers is established for other applications.
NOTE 1: Operator policy takes into account regional/national requirements.
The EPS bearer for MCPTT emergency call shall have highest priority level among MCPTT call types. The EPS bearer for MCPTT imminent peril call shall have higher priority level than one for MCPTT call.
To ensure that the MCPTT service always has access to a dedicated bearer for MCPTT media, a pre-established session may be setup that includes a request for resources at the first MCPTT group affiliation.
This means that the PCC may multiplex MCPTT media streams from multiple concurrent MCPTT calls into one EPS bearer on one shared network priority regardless of MCPTT call priority.
NOTE 2: A single UM bearer is used to multiplex the media streams from multiple concurrent MCPTT calls.
NOTE 3: The sharing of a single GBR bearer for voice means that different QCI and/or ARP values are not possible for different voice media streams.
NOTE 4: Multi-talker control may require additional bearer resources if multiple audio streams are sent to the UE when the floor is granted to additional participants during an established MCPTT group session.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.7.4 MBMS bearer management
| The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 5.8 MCPTT system interconnect requirements
| The architecture for interconnect between MCPTT systems is specified, allowing the affiliation of MCPTT users from an MCPTT system with MCPTT groups defined in another MCPTT system. When both MCPTT systems are served by different networks, interconnect of signalling and media is achieved using the interfaces defined for interconnect between PLMNs.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 6 Involved business relationships
| The description of the involved business relationships for the MCPTT service is contained in clause 6 of 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7 Functional model
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 7.1 General
| The functional model for the support of MCPTT is defined as a series of planes to allow for the breakdown of the architectural description.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.2 Description of the planes
| The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.3 Functional model description
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 7.3.1 On-network functional model
| Figure 7.3.1-1 shows the functional model for the application plane of the MCPTT service.
Figure 7.3.1-1: Functional model for application plane of the MCPTT service
In the model shown in figure 7.3.1-1, the following apply:
- The MCPTT server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [16].
- The MCPTT server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [9].
- MCPTT-9 carries multicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE.
- MCPTT-4 carries unicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE.
- MCPTT-7 carries unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT UE.
- MCPTT-8 carries multicast media from the media distribution function of the MCPTT server to the media mixer of the MCPTT UE.
Figure 7.3.1-2 shows the relationships between the reference points of the application plane and the signalling plane.
Figure 7.3.1-2: Relationships between reference points of MCPTT application and signalling control planes
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.3.2 Off-network functional model
| Figure 7.3.2-1 shows the functional model for off-network operation of MCPTT service.
Figure 7.3.2-1: Functional model for off-network operation of MCPTT service
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4 Functional entities description
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2 Application plane of MCPTT service
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.1 General
| Entities within the application plane of MCPTT service provide application control, media control and distribution functions.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.2 Common services core
| The description of the common services core entities are contained in common functional architecture to support MC services in 3GPP TS 23.280 [16].
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3 MCPTT application service
| |
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.1 MCPTT client
| The MCPTT client functional entity acts as the user agent for all MCPTT application transactions. The client reports the information of where the client is currently located.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.2 MCPTT server
| The MCPTT server functional entity provides centralised support for MCPTT services.
All the MCPTT clients supporting users belonging to a single group are required to use the same MCPTT server for that group. An MCPTT client supporting a user involved in multiple groups can have relationships with multiple MCPTT servers.
NOTE 1: Possible requirements for handling multiple distinct media on different MCPTT servers are not covered in this version of the document.
The MCPTT server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [9] to control multicast and unicast operations for group communications.
The MCPTT server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane.
By assuming the role of a GCS AS, the MCPTT server functional entity is responsible for:
- requesting the allocation of multicast resources utilizing the media distribution function;
- announcing the association of multicast resources to calls to MCPTT UEs;
- determining for each MCPTT UE involved in a given call whether to use unicast or multicast transport;
- announcing the assignment of multicast transport for specific calls to MCPTT UEs; and
- informing the media distribution function of the media streams requiring support for a given call.
The MCPTT server shall support the controlling role and the participating role. The MCPTT server may perform the controlling role for private calls and group calls. The MCPTT server performing the controlling role for a private call or group call may also perform a participating role for the same private call or group call. For each private call and group call, there shall be only one MCPTT server assuming the controlling role, while one or more MCPTT servers in participating role may be involved.
The MCPTT server performing the controlling roles is responsible for:
- call control (e.g. policy enforcement for participation in the MCPTT group calls) towards all the MCPTT users of the group call and private call;
- interfacing with the group management server for group policy and affiliation status information of this MCPTT server's served affiliated users;
- enforcing functional alias priority handling;
- managing floor control entity in a group call and private call;
- managing media handling entity in call i.e. conferencing, transcoding ; and
- interfacing with the recording server for the management of the recording processes.
The MCPTT server performing the functional alias controlling role is responsible for:
- interfacing with the functional alias management server for functional alias policy from the functional alias configuration;
- functional alias activation, deactivation, take over and interrogation support for MCPTT user.
The controlling roles for group call, private call and functional alias are independent with each other.
The MCPTT server performing the participating roles is responsible for:
- call control (e.g. authorization for participation in the MCPTT group calls) to its MCPTT users for group call and private call;
- group affiliation support for MCPTT user, including enforcement of maximum N2 number of simultaneous group affiliations by a user;
- enforcing functional alias priority handling;
- relaying the call control and floor control messages between the MCPTT client and the MCPTT server performing the controlling role; and
- media handling in call for its MCPTT users, i.e. transcoding, lawful interception for both unicast and multicast media.
NOTE 2: The MCPTT server in the controlling role and the MCPTT server in the participating role can belong to the same MCPTT system or to different MCPTT systems.
For group regrouping involving multiple groups from primary and partner MCPTT systems,
- the group host MCPTT server of the temporary group performs the controlling role and is responsible for the centralized floor control, and for arbitration according to the temporary group or user policies (e.g., priority);
- the group host MCPTT server of the constituent MCPTT group is responsible for providing call invitations to their group members, and for filtering between constituent group members' floor control requests according to the constituent group or user policies (e.g., priority); and
- the MCPTT server responsible for the constituent MCPTT group members performs the participating role.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.3 Floor participant
| The floor participant functional entity is responsible for floor requests. This functional entity is located in the UE for both on-network and off-network operations.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.4 Floor control server
| This functional entity provides support for centralised floor control for on-network and distributed floor control for off-network operation. It may provide arbitration between floor control requests between different users, grant the floor in response to successful requests, and provide queuing in cases of contention. For on-network operation, this functional entity is located with the MCPTT server, however, the floor control server may use different IP addresses. For off-network operation, this functional entity is located in the UE.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.5 Media distribution function
| The media distribution function is responsible for the distribution of media to call participants. The media distribution function may use different IP addresses than the MCPTT server. By means of information provided by the MCPTT server (e.g. IP addresses, transport layer ports), it will provide the following functionality:
- provide for the reception of uplink MCPTT UE media transmission by means of the MCPTT-7 reference point;
- replicate the media as needed for distribution to those participants using unicast transport;
- distribute downlink media to MCPTT UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCPTT-7 reference point;
- distribute downlink media to MCPTT UEs using multicast downlink transport of media for the call by means of the MCPTT-8 reference point; and
- provide a media mixing function where multiple media streams are combined (e.g. multi-talker control) into a single media stream for transmission to the MCPTT UE.
NOTE 1: If media mixing function occurs within the media distribution function, it operates independently of the media mixer in the UE.
NOTE 2: A media mixing function within the media distribution function is not possible where the media is end to end encrypted.
Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the MCPTT server.
NOTE 3: If media mixing in the network is utilized, care should be taken to minimize the feedback of the user's own voice from the mixed audio in order to avoid echoes.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.6 Media mixer
| This functional entity exists on the UE and provides support for combining multiple media streams (e.g. multi-talker control) into one media stream through the enforcement of media policy information. Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the UE.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.7 MCPTT user database
| This functional entity contains information of the MCPTT user profile associated with an MCPTT ID that is held by the MCPTT service provider at the application plane. The MCPTT user profile is determined by the mission critical organization, the MCPTT service provider, and potentially the MCPTT user.
|
85bf19f2724bd70687927dc10941722c | 23.379 | 7.4.2.3.8 MC gateway server
| The MC gateway server provides support for MCPTT interconnection services with a partner MCPTT system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCPTT servers in the partner MCPTT system without needing to expose the MCPTT servers in the primary MCPTT system outside the trusted domain of the primary MCPTT system. It may be a role of the MCPTT server described in subclause 7.4.2.3.2 of the present document.
The MC gateway server is responsible for relaying call control and floor control signalling messages, and media between MCPTT servers within the MCPTT system and the interconnected MCPTT system.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.