hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.4.3 Naf_Inference_Unsubscribe service operation
| Service operation name: Naf_Inference_Unsubscribe
Description: Unsubscribe to VFL inference.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.4.4 Naf_Inference_Notify service operation
| Service operation name: Naf_Inference_Notify
Description: Notify VFL inference result.
Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
- Inference results:
- Set of the tuple (Analytics ID, Analytics specific parameters): this parameter shall be present if output analytics are reported... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.4.5 Naf_Inference_Request service operation
| Service operation name: Naf_Inference_Request
Description: The consumer requests the AF to perform a one-time VFL inference.
Inputs, Required:
- Analytics ID.
- Target of Analytics Reporting.
Inputs, Optional:
- Analytics Reporting Information (with parameters as defined in clause 6.1.3).
- Analytics Filter.
Ou... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.5 Naf_Training Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.5.1 General
| Service Description: This service is provided by an AF acting as VFL server and enables an NWDAF or an NEF acting on its behalf as consumer to request the AF to perform model training as defined in clause 6.2H.2.3 under the supervision of the consumer.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.5.2 Naf_Training_Subscribe service operation
| Service operation name: Naf_Training_Subscribe
Description: Subscribes to ML Model training with AF as VFL server.
Inputs, Required:
For new subscription:
- Analytics ID as defined in Table 7.1-2.
- Notification Target Address (+ Notification Correlation ID).
When updating a subscription:
- Subscription Correl... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.5.3 Naf_Training_Unsubscribe service operation
| Service operation name: Naf_Training_Unsubscribe
Description: Terminate AF ML Model training.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: Cause code.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 11.5.4 Naf_Training_Notify service operation
| Service operation name: Naf_Training_Notify
Description: AF notifies the consumer of training progress
Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12 NEF Services to support network data analytics
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.1 General
| Table 12.1-1 illustrates the NEF Services to support network data analytics.
Table 12.1-1: NF services provided by NEF to support network data analytics
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nnef_VFLTraining
Subscribe
Subscribe / Notify
NWDAF
Unsubscribe
NWDAF
Notify
... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2 Nnef_VFLTraining Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2.1 General
| Service Description: This service is provided by an NEF on behalf of either an NWDAF or AF acting as VFL client in training process as defined in clause 6.2H.2.3.
For VFL, this service may also be used by the consumer (i.e. FL Server) to prepare the VFL training as described in in clause 6.2H.2.2.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2.2 Nnef_VFLTraining_Subscribe service operation
| Service operation name: Nnef_VFLTraining_Subscribe
Description: Subscribes to VFL ML Model training with AF as VFL client.
Inputs, Required:
For new subscription:
- Analytics ID.
- VFL correlation ID.
- Notification Target Address (+ Notification Correlation ID).
When updating a subscription:
- Subscription C... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2.3 Nnef_VFLTraining_Unsubscribe service operation
| Service operation name: Nnef_VFLTraining_Unsubscribe
Description: Terminate AF VFL ML Model training.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: Cause code.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2.4 Nnef_VFLTraining_Notify service operation
| Service operation name: Nnef_VFLTraining_Notify
Description: NEF notifies the consumer of client intermediate training result of the local ML mode.
Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
- Client intermediate training result.
Outputs, Required: Operation execution result indic... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.2.5 Nnef_VFLTraining_Request service operation
| Service operation name: Nnef_VFLTraining_Request
Editor´s note: Name of this service operation and its necessity is FFS. It is also FFS whether it can be replaced by a subscription request for the preparation.
Description: In preparation of VFL training, requests NEF to check at untrusted AF acting as VFL client if i... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3 Nnef_VFLInference Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3.1 General
| Service Description: This service is provided by by an NEF on behalf of an AF acting as VFL client and enables an VFL server as consumer to request or subscribe/unsubscribe for a VFL inference.
When the subscription is accepted by the AF, the consumer receives from the NWDAF an identifier (Subscription Correlation ID)... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3.2 Nnef_VFLInference_Subscribe service operation
| Service operation name: Nnef_VFLInference_Subscribe
Description: Subscribe to VFL inference.
Inputs, Required:
For new subscription:
- Notification Target Address (+ Notification Correlation ID).
- VFL Correlation ID.
- Target of VFL inference.
When updating a subscription:
- Subscription Correlation ID.
- F... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3.3 Nnef_VFLInference_Unsubscribe service operation
| Service operation name: Nnef_VFLInference_Unsubscribe
Description: Unsubscribe to VFL inference.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3.4 Nnef_VFLInference_Notify service operation
| Service operation name: Nnef_VFLInference_Notify
Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
- Client intermediate results.
- Analytics Metadata Information.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.3.5 Nnef_VFLInference_Request service operation
| Service operation name: Nnef_VFLInference_Request
Description: The consumer requests the NWDAF to perform a one-time VFL inference.
Inputs, Required:
- Target of VFL inference.
- VFL Correlation ID.
- Analytics ID.
Inputs, Optional:
- VFL inference filter.
- Data time window.
- Time when intermediate local res... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.4 Nnef_VFLNFDiscovery Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.4.1 General
| Service Description: This service is provided by by an NEF towards an untrusted AF acting as VFL server to enable the AF to interact with NWDAFs acting as VFL client. It enables the AF to detect NWDAFs as VFL clients as described in in clause 6.2H.2.1.
Editor´s note: Parameters of the service operations are FFS.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.4.2 Nnef_VFLNFDiscovery_NwdafDiscovery service operation
| Service operation name: Nnef_VFLNFDiscovery_NwdafDiscovery
Description: The consumer requests the NEF to discover an NWDAF that is to act as VFL client.
Inputs, Required:
- Analytics ID.
- required NF type (i.e. NWDAF type).
- VFL capability type (i.e. VFL client).
Inputs, Optional:
- Required feature IDs.
- Ti... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.4.3 Nnef_VFLNFDiscovery_NwdafRelease service operation
| Service operation name: Nnef_VFLNFDiscovery_NwdafDiscovery
Description: The consumer informs the NEF that it mo longer wants .to use an assigned temporary NWDAF ID.
Inputs, Required:
- external NWDAF ID.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5 Nnef_Inference Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5.1 General
| Service Description: This service is provided by an NEF on behalf of an AF acting as VFL server and enables an NWDAF as consumer to request or subscribe/unsubscribe for a VFL inference.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5.2 Nnef_Inference_Subscribe service operation
| Service operation name: Nnef_Inference_Subscribe
Description: Subscribe to VFL inference.
Inputs, Required:
For new subscription:
- Notification Target Address (+ Notification Correlation ID).
- Analytics ID.
- Target of Analytics Reporting.
When updating a subscription:
- Subscription Correlation ID.
Inputs... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5.3 Nnef_Inference_Unsubscribe service operation
| Service operation name: Nnef_Inference_Unsubscribe
Description: Unsubscribe to VFL inference.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5.4 Nnef_Inference_Notify service operation
| Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
- Inference results:
- Set of the tuple (Analytics ID, Analytics specific parameters): this parameter shall be present if output analytics are reported.
- Validity period.
- Confidence.
- Analytics Metadata Information.
- Analytics Accu... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.5.5 Nnef_Inference_Request service operation
| Service operation name: Nnef_Inference_Request
Description: The consumer requests the VFL server to perform a one-time VFL inference.
Inputs, Required:
- Analytics ID.
- Target of Analytics Reporting.
Inputs, Optional:
- Analytics Reporting Information (with parameters as defined in clause 6.1.3).
- Analytics Fi... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.6 Nnef_Training Service
| |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.6.1 General
| Service Description: This service is provided by NEF AF acting on behalf of an untrusted AF as VFL server and enables an NWDAF as consumer to request the AF to perform model training as defined in clause 6.2H.2.3 under the supervision of the consumer.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.6.2 Nnef_Training_Subscribe service operation
| Service operation name: Nnef_Training_Subscribe
Description: Subscribes to ML Model training with AF as VFL server.
Inputs, Required:
For new subscription:
- Analytics ID as defined in Table 7.1-2.
- Notification Target Address (+ Notification Correlation ID).
When updating a subscription:
- Subscription Corre... |
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.6.3 Nnef_Training_Unsubscribe service operation
| Service operation name: Nnef_Training_Unsubscribe
Description: Terminate AF ML Model training.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: Cause code.
|
30701f0da928d70591b1088aae4273d2 | 23.288 | 12.6.4 Nnef_Training_Notify service operation
| Service operation name: Nnef_Training_Notify
Description: AF notifies the consumer of training progress.
Inputs, Required:
- Notification Correlation Information.
Inputs, Optional:
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
Annex A (informative):
Methods to handle NAT o... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 1 Scope
| The present document specifies the use of the 5G System (5GS) considering common functional architecture, procedures and information flows needed to support mission critical services encompassing the common services core architecture.
The corresponding service requirements applied in 3GPP TS 22.179 [11], 3GPP TS 22.28... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 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.
-... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 3 Definitions of terms, symbols and abbreviations
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 3.1 Terms
| For the purposes of the present document, the terms 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].
Indirect path information: Consists of the path information and root relay in the form of... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 3.2 Symbols
| Void.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 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].
ECN Explicit Congestion Notification
L4S Low Latency, Low Loss ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4 MC system resource requirements
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.1 Multiple Access
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.1.1 General
| 5GS provides simultaneous integration of different access types 3GPP and non-3GPP (wireline and wireless), defined in 3GPP TS 23.501 [7]. Accordingly, this enables the MC service UE to be used under both stationary and non-stationary conditions.
With the convergence of multiple access technologies in 5GS, service feat... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.1.2 Requirements
| With the use of 5GS, MC services shall be available via 3GPP access as well as via non-3GPP access. To enable access to the MC system, the use of the various access types shall be authorized by the 5GC. The simultaneous use of different access types (Access Traffic Steering, Switching and Splitting) is defined in 3GPP ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.2 Session connectivity
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.2.1 General
| The access from 5GS to the MC service environment takes place via the Data Network (DN) in accordance with 3GPP TS 23.501 [7]. A Data Network Name (DNN) as part of the 5GS user profile allows access to the Data Network with up to 8 connectivity sessions (PDU sessions) each with up to 64 communication flows (QoS flows).... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.2.2 Requirements
| For MC service UEs who only utilize 5GS, a single DNN may be used for:
- for the SIP-1 reference point;
- for the HTTP-1 reference point; and
- for the CSC-1 reference point.
The DNN shall be made available to the MC service UE either via UE (pre)configuration or via initial UE configuration on a per HPLMN and opt... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3 QoS characteristics
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.1 General
| In 5GS, quality of service is enforced at QoS flow level and corresponding packets are classified and marked with an identifier in accordance with 3GPP TS 23.501 [7]. Every QoS flow is characterized by a QoS profile provided by the 5GC, and can be used for all connectivity types (PDU sessions) in accordance with 3GPP T... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.2 QoS requirements for general purposes
| The selection, deployment, initiation, and termination of QoS signalling and resource allocation shall consider the QoS mechanisms described in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], 3GPP TS 23.503 [9] and 3GPP TS 23.247 [15] for MBS.
MC system as well as MC service UE may share one DNN using multiple QoS flows for ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.3 QoS requirements for Mission Critical Push to Talk
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.3.1 General
| The requirements listed here apply for the use of 5GS and replace the corresponding requirements in 3GPP TS 23.379 [6].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.3.2 5QI values for MCPTT
| The MCPTT system may use the N5 reference point or Rx reference point for direct interaction with 5GS PCF to determine the required QoS flow parameters. Alternatively, the MCPTT system may use the N33 reference point for indirect interaction with 5GS NEF.
For the use of MBS, the MCPTT system may interact with the PCF... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.3.3 Use of priorities
| The QoS flow (unicast or multicast/broadcast) for an MCPTT emergency call shall have highest priority level among MCPTT call types. The QoS flow (unicast or multicast/broadcast) for MCPTT imminent peril call shall have higher priority level than one for a MCPTT call.
Depending on operators' policy, the MCPTT system ma... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.4 QoS requirements for Mission Critical Video
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.4.1 General
| The requirements listed here apply for the use of 5GS and replace the corresponding requirements in 3GPP TS 23.281 [4].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.4.2 5QI values for MCVideo
| The MCVideo system may use the N5 reference point or Rx reference point for direct interaction with 5GS PCF to determine the required QoS flow parameters. Alternatively, the MCVideo system may use the N33 reference point for indirect interaction with 5GS NEF.
For the use of MBS, the MCVideo system may interact with th... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.4.3 Use of priorities
| The MCVideo audio media and video media may transmit over dedicated QoS flows (unicast or multicast/broadcast), in which case the priority for each QoS flow (unicast or multicast/broadcast) is determined by the operator policy.
MCVideo services shall be able to use ARP pre-emption capability and the pre-emption vulne... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.5 QoS requirements for Mission Critical Data
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.5.1 General
| The requirements listed here apply for the use of 5GS and replace the corresponding requirements in 3GPP TS 23.282 [5].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.5.2 5QI values for MCData
| The MCData system may use the N5 reference point or Rx reference point for direct interaction with 5GS PCF to determine the required QoS flow parameters. Alternatively, the MCData system may use the N33 reference point for indirect interaction with 5GS NEF.
For the use of MBS, the MCData system may interact with the ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.3.5.3 Use of priorities
| The QoS flows (unicast or multicast/broadcast) for MCData emergency communications shall have highest priority level among MCData communication types. The QoS flow (unicast or multicast/broadcast) for MCData imminent peril call shall have higher priority level than one for a MCData communication.
MCData services shall... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.4 Network Slicing
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.4.1 General
| Network slicing in accordance with 3GPP TS 23.501 [7] can be used for several purposes such as to separate MC service users, UEs as well as applications in accordance with the various QoS requirements independent from 3GPP or non-3GPP access.
The corresponding slice information identifies a network slice across the 5G... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.4.2 Requirements
| For the use of network slicing in the MC service context, the following minimum requirements in accordance with 3GPP TS 23.501 [7] shall be considered:
One network slice shall be assigned per PDU session and may benefit from a dedicated transmission resource allocation.
The network slicing for MC services follows the... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.5 Use of public and non-public networks
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.5.1 General
| MC services are service agnostic with respect to 5GS, i.e., the available service options are identical in both public networks (i.e. PLMN) and non-public networks (NPNs). A non-public network (NPN) can be deployed in organization defined premises and the 5G network services are provided to a defined set of users or or... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.5.2 Requirements
| An MC system shall be able to utilize connectivity from public 5GS networks and non-public 5GS networks in accordance with 3GPP TS 23.501 [7].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.6 Migration
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.6.1 General
| For the migration of an MC service user the general assumptions in 3GPP TS 23.280 [3] clause 5.2.9.1 are applied.
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.6.2 Public network utilization
| Migrated MC service users should utilize the home PLMN of the partner MC system to access MC services in the partner MC system, however, utilizing the home PLMN of the primary MC system is not precluded.
NOTE 1: The above recommendation ensures the security policy of the partner MC system and is not compromised, the e... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.6.3 Non-Public network utilization
| When the NPN is a PNI-NPN as described in 3GPP TS 23.501 [7], the requirements in clause 4.6.2 are applicable.
When the NPN is a SNPN as described in 3GPP TS 23.501 [7], the requirements may be different in the following options.
Option 1: The SNPN utilized by the primary MC system and the SNPN utilized by the partne... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7 Architectural aspects of MC services using MBS
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.1 General
| The main purpose of 5G Multicast-Broadcast Service (MBS) use by mission critical services is to provide efficient downlink delivery of user traffic in group calls and communications. The architectural figures in this clause are aligned with the 5GS architecture for MBS shown in Figure 5.1-2 of 3GPP TS 23.247 [15], whi... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.2 General on-network architecture for use of MBS by MC services
| Figure 4.7.2-1 presents a high-level architectural view of mission critical services when using MBS. The shown architecture is consistent with 3GPP TS 23.501 [7] and 3GPP TS 23.247 [15].
MC services use MBS control plane capabilities by initiating access via Nmb13, Nmb10 or N33. MBS user plane capabilities can be acce... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.3 Specific instantiations of on-network architecture for use of MBS by MC services
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.3.1 Instantiation without optional entities and associated interfaces
| Figure 4.7.3.1-1 presents a high-level architectural view of mission critical services when using MBS without the presence or use of the optional entities (MBSF, MBSTF and NEF) and their associated interfaces. The shown architecture is a particularization of the general architecture shown in figure 4.7.3.1-1.
MC servi... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.3.2 Instantiation without MBSF / MBSTF and associated interfaces
| Figure 4.7.3.2-1 presents a high-level architectural view of mission critical services when using MBS without the presence or use of the optional entities MBSF and MBSTF and their associated interfaces. The shown architecture is a particularization of the general architecture shown in figure 4.7.2-1.
MC services use M... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.3.3 Instantiation without NEF and associated interfaces
| Figure 4.7.3.3-1 presents a high-level architectural view of mission critical services when using MBS without the presence or use of the optional entity NEF and its associated interfaces. The shown architecture is a particularization of the general architecture shown in figure 4.7.2-1.
MC services use MBS control plan... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.4 Service layer‑based interworking between eMBMS and MBS
| Figure 4.7.4-1 presents a high-level architectural view of mission critical services interworking between eMBMS and MBS at the service layer. The shown architecture is consistent with 3GPP TS 23.247 [15], subclauses 5.2, 6.8 and configurations 2 and 3 in Annex A.
The interworking between eMBMS and MBS for mission crit... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.5 Application layer based interworking between eMBMS and MBS
| Figure 4.7.5-1 presents a high-level architectural view of mission critical services interworking between eMBMS and MBS at the application layer. The shown architecture does not use the MBSF/MBSTF entities defined in 3GPP TS 23.247 [15] and is inclusive of configuration 1 in Annex A of 3GPP TS 23.247 [15].
MC services... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.7.6 General architecture showcasing use of MBS by UE for MC services
| Figure 4.7.6-1 presents a high-level system architecture that shows how the MC service UEs support the delivery of mission critical services through MBS. Figure 4.7.6-2 shows the functional model used by the UE, highlighting the conceptual MC MBS API used for information transfer within the UE. The shown system archite... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.8 Use of 5G ProSe UE-to-network relay
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.8.1 General
| The MC service shall support the capabilities for 5G ProSe UE-to-network relay. For this matter, 5G ProSe Layer-2 and 5G ProSe Layer-3 UE-to-network relaying techniques can be utilized, as described in 3GPP TS 23.304 [17]. The 5G ProSe Layer-3 UE-to-Network relaying technique may be done with or without the support of ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.8.2 5G ProSe UE-to-network relay service requirements
| In order to enable 5G ProSe UE-to-network relaying capabilities – whether based on Layer-3 or Layer-2 UE-to-network relaying techniques, the MC system provides the appropriate parameters and configurations to the MC service UE(s).
As defined in 3GPP TS 23.304 [17], among these parameters are: Relay Service Code(s) (RS... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.8.3 5G ProSe multi-hop UE-to-network relay service requirements
| In order to enable 5G ProSe multi-hop UE-to-network relaying capabilities (either Layer-2 or Layer-3), the MC system provides the appropriate parameters and configurations to the MC service UE(s). As defined in 3GPP TS 23.304 [17], the parameters associated with 5G ProSe Layer-3 multi-hop UE-to-network relay are among ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.9 EPS interworking
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.9.1 General
| Network deployments of MC services over 5GS may support interworking with EPS. EPS interworking aspects in 5G systems are specified in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], and 3GPP TS 23.503 [9].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.9.2 Requirements
| For MC services over a 5G system with EPS interworking, inter-system mobility between 5GC and EPC/E-UTRAN of MC service UEs shall be supported by the network based on the capabilities and procedures defined in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10], and 3GPP TS 23.503 [9].
For the case that seamless session continui... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.10 Use of 5G ProSe UE-to-UE relay
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.10.1 General
| The MC service shall support the capabilities for 5G ProSe UE-to-UE relay. For this matter, 5G ProSe Layer-2 and 5G ProSe Layer-3 UE-to-UE relaying techniques can be utilized, as described in 3GPP TS 23.304 [17].
A 5G ProSe UE-to-UE relay supporting MC service UE provides means of connectivity and relaying of MC traff... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.10.2 5G ProSe UE-to-UE relay service requirements
| In order to enable 5G ProSe UE-to-UE relaying capabilities – whether based on Layer-3 or Layer-2 UE-to-UE relaying techniques, the MC system provides the appropriate parameters and configurations to the MC service UE(s).
As defined in 3GPP TS 23.304 [17], among these parameters are: Relay Service Code(s) (RSCs) which ... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.10.3 5G ProSe multi-hop UE-to-UE relay service requirements
| In order to enable 5G ProSe Layer-3 multi-hop UE-to-UE relaying capabilities, the MC system provides the appropriate parameters and configurations to the MC service UE(s). As defined in 3GPP TS 23.304 [17], among these parameters are: RSC(s) which can be associated to a certain MC service group, User Info ID, ProSe Lay... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.11 Support of the 5GS congestion information exposure using L4S
| Based on the request from the MC system, the 5G system can expose network congestion information on the media path between the MC service server and MC service UE to enable reacting accordingly, e.g., adjust the application layer bit rate at the media sender side.
The 5G System can support Explicit Congestion Notifica... |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.12 Support of MC services over NTN
| |
00c630369f4492b30b380be367f5dbf7 | 23.289 | 4.12.1 General
| The MC service UE should utilize satellite access to obtain MC services as specified in 3GPP TS 23.501 [7], 3GPP TS 23.502 [10] and 3GPP TS 23.503 [9].
|
00c630369f4492b30b380be367f5dbf7 | 23.289 | 5 MC system functional model
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.