hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.2.1 AIoT Inventory service
| AIoT Inventory service is used to discover the AIoT Devices.
|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.2.2 AIoT Command service
| |
86def9d910bbdd3d62d143eb5eeb440e | 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 opera... |
86def9d910bbdd3d62d143eb5eeb440e | 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 us... |
86def9d910bbdd3d62d143eb5eeb440e | 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... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.3 Discovery and Selection of AIoT node(s)
| |
86def9d910bbdd3d62d143eb5eeb440e | 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 con... |
86def9d910bbdd3d62d143eb5eeb440e | 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 fu... |
86def9d910bbdd3d62d143eb5eeb440e | 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 that... |
86def9d910bbdd3d62d143eb5eeb440e | 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 l... |
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
86def9d910bbdd3d62d143eb5eeb440e | 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 Identifier is used by th... |
86def9d910bbdd3d62d143eb5eeb440e | 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... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.7 Identifiers
| |
86def9d910bbdd3d62d143eb5eeb440e | 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.
|
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
86def9d910bbdd3d62d143eb5eeb440e | 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.
|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.7.4 AIoT Device Temporary Identifier
| A Device Temporary Identifier may be used as AIoT Identification Information in Inventory procedure if privacy protection is used. The details of how Device Temporary Identifier is generated, managed and used are specified in TS 33.369 [9].
|
86def9d910bbdd3d62d143eb5eeb440e | 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 A... |
86def9d910bbdd3d62d143eb5eeb440e | 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 aggregati... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 5.10 AIoT Device Location
| |
86def9d910bbdd3d62d143eb5eeb440e | 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 eac... |
86def9d910bbdd3d62d143eb5eeb440e | 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 Identifier, 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 sele... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 6 AIoT Procedures
| |
86def9d910bbdd3d62d143eb5eeb440e | 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.
|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 6.2 AIoT Service Procedures
| |
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
86def9d910bbdd3d62d143eb5eeb440e | 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: Inve... |
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 6.2.4 Procedures between AIOTF and NG-RAN for Indirect Connectivity
| |
86def9d910bbdd3d62d143eb5eeb440e | 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.
|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 6.2.4.2 Message delivery to NG-RAN
| When the AIOTF sends NGAP message, the AMF receives an Namf_AIoT_MessageDelivery request and sends the corresponding NGAP message 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 i... |
86def9d910bbdd3d62d143eb5eeb440e | 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 i... |
86def9d910bbdd3d62d143eb5eeb440e | 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 resp... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7 Network Functions Services
| |
86def9d910bbdd3d62d143eb5eeb440e | 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.
|
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.2 AIOTF services
| |
86def9d910bbdd3d62d143eb5eeb440e | 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
N... |
86def9d910bbdd3d62d143eb5eeb440e | 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 targe... |
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
86def9d910bbdd3d62d143eb5eeb440e | 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 r... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.3 AMF services
| |
86def9d910bbdd3d62d143eb5eeb440e | 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... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.3.2 Namf_AIoT_MessageDelivery service operation
| Service operation name: Namf_AIoT_MessageDelivery
Description: The NF consumer requests to send AIoT NGAP Messages towards NG-RAN.
Inputs, Required:
1) NGAP AIoT Information to deliver to NG-RAN.
2) NG-RAN ID.
3) AIoT NGAP Message Type ("Inventory Request" or "Command Request" or "Session Release Command").
4) AI... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.3.3 Namf_AIoT_Notify service operation
| Service operation name: Namf_AIoT_Notify
Description: The NF consumer requests to receive notifications for AIoT NGAP messages from NG-RAN. If the NF consumer invokes the Namf_AIoT_MessageDelivery, the NF consumer implicitly subscribes to receive the Namf_AIoT_Notify.
Inputs, Required:
1) AIoT Information received f... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.4 NEF services
| |
86def9d910bbdd3d62d143eb5eeb440e | 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/Resp... |
86def9d910bbdd3d62d143eb5eeb440e | 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... |
86def9d910bbdd3d62d143eb5eeb440e | 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 Devi... |
86def9d910bbdd3d62d143eb5eeb440e | 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 opera... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.5 ADM services
| |
86def9d910bbdd3d62d143eb5eeb440e | 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
Subscribe
Subscribe/Notify
AIOTF
Unsub... |
86def9d910bbdd3d62d143eb5eeb440e | 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 Identifier (if retrieving AIoT Device profile data), AF ID (if retrieving a specific AF's authorization data; if not provid... |
86def9d910bbdd3d62d143eb5eeb440e | 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 Identifier, updated AIoT Device profile data.
Input, Optional: None.
Outputs, Required: Result indication (Success or Failure), Failure Cause in case of... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.5.4 Nadm_DM_Subscribe service operation
| Service operation name: Nadm_DM_Subscribe
Description: NF service consumer performs the subscription to notifications to data modified in the ADM. The events can be changes on existing data, addition of data. Specifically, this service operation together with the corresponding Unsubscribe and Notify service operations... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.5.5 Nadm_DM_Unsubscribe service operation
| Service operation name: Nadm_DM_Unsubscribe
Description: NF service consumer unsubscribes from the notifications about data modified in the ADM. The events can be changes on existing data, addition of data.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, O... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.5.6 Nadm_DM_Notify service operation
| Service operation name: Nadm_DM_Notify
Description: ADM notifies NF service consumer(s) about modification of data, when data in the ADM is added, modified or deleted and an NF needs to be informed about this, due to a previous subscription to notifications procedure with the ADM.
Inputs, Required: Notification Corre... |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.6 UDR Services
| |
86def9d910bbdd3d62d143eb5eeb440e | 23.369 | 7.6.1 Nudr_DataManagement (DM) Service
| |
86def9d910bbdd3d62d143eb5eeb440e | 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 ... |
654ce7f815f094ec84428f386a012c76 | 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].Suppo... |
654ce7f815f094ec84428f386a012c76 | 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.
-... |
654ce7f815f094ec84428f386a012c76 | 23.379 | 3 Definitions, symbols and abbreviations
| |
654ce7f815f094ec84428f386a012c76 | 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 privat... |
654ce7f815f094ec84428f386a012c76 | 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
|
654ce7f815f094ec84428f386a012c76 | 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... |
654ce7f815f094ec84428f386a012c76 | 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 sup... |
654ce7f815f094ec84428f386a012c76 | 23.379 | 5 Architectural requirements
| |
654ce7f815f094ec84428f386a012c76 | 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 o... |
654ce7f815f094ec84428f386a012c76 | 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.
|
654ce7f815f094ec84428f386a012c76 | 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 gro... |
654ce7f815f094ec84428f386a012c76 | 23.379 | 5.4 MCPTT call requirements
| |
654ce7f815f094ec84428f386a012c76 | 23.379 | 5.4.1 General
| The on-network MCPTT service shall support the use of pre-established sessions.
|
654ce7f815f094ec84428f386a012c76 | 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.
|
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 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' selec... |
654ce7f815f094ec84428f386a012c76 | 23.379 | 5.7 Bearer management
| |
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 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.
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 5.7.2.1 Void
| |
654ce7f815f094ec84428f386a012c76 | 23.379 | 5.7.2.2 Void
| |
654ce7f815f094ec84428f386a012c76 | 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 s... |
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 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 fo... |
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 7 Functional model
| |
654ce7f815f094ec84428f386a012c76 | 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.
|
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.3 Functional model description
| |
654ce7f815f094ec84428f386a012c76 | 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 2... |
654ce7f815f094ec84428f386a012c76 | 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
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.4 Functional entities description
| |
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.4.1 General
| Each subclause is a description of a functional entity and does not imply a physical entity.
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.4.2 Application plane of MCPTT service
| |
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.4.2.1 General
| Entities within the application plane of MCPTT service provide application control, media control and distribution functions.
|
654ce7f815f094ec84428f386a012c76 | 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].
|
654ce7f815f094ec84428f386a012c76 | 23.379 | 7.4.2.3 MCPTT application service
| |
654ce7f815f094ec84428f386a012c76 | 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.
|
654ce7f815f094ec84428f386a012c76 | 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 serve... |
654ce7f815f094ec84428f386a012c76 | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.