hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6 Analysis on AI/ML across 3GPP
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.1 General
| This clause identifies any potential misalignments and inconsistencies for AI/ML across 3GPP, based on clause 5.
NOTE: Any RAN related aspects are subject to early coordination and feedback from TSG RAN.
|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2 AI/ML related terminology
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1 Analysis on AI/ML model related terminology consistency
| This clause identifies any potential misalignments and inconsistencies for AI/ML terminology across 3GPP, based on clause 5.
|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.1 Analysis on ML model
| The term 'ML model' has been defined differently by SA WG5, SA WG6 and RAN WG1, as illustrated in Table 6.2.1.1-1.
Table 6.2.1.1-1: Definition of ML model as defined across 3GPP WGs
TSG (TS/TR)
ML model
SA WG5 TS 28.105 [9]
A manageable representation of an ML model algorithm.
(NOTE 1, NOTE 2, NOTE 3)
SA WG6 TS ... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.2 Analysis on ML model training
| The term 'ML model training' has been defined differently by SA WG5, SA WG6 and RAN WG1, as illustrated in Table 6.2.1.2-1. RAN WG3 follows the definition of SA WG5.
Table 6.2.1.2-1: Definition of ML model training as defined across 3GPP WGs
TSG (TS/TR)
ML model training
SA WG5 TS 28.105 [9]
A process performed by... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.3 Analysis on ML model re-training
| The term 'ML model re-training' has been defined differently by SA WG5 and RAN WG1, as illustrated in Table 6.2.1.3-1. RAN WG1 introduces two new terms, i.e. ML model parameter update and ML model update, which is nothing but ML model re-training.
Table 6.2.1.3-1: Definition of ML model re-training / ML model paramete... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.4 Analysis on ML model testing
| The term 'ML model testing' has been defined differently by SA WG5 and RAN WG1, as illustrated in Table 6.2.1.4-1.
Table 6.2.1.4-1: Definition of ML model testing as defined across 3GPP WGs
TSG (TS/TR)
ML model testing
SA WG5 TS 28.105 [9]
A process of evaluating the performance of an ML model using testing data d... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.5 Analysis on ML model inference
| The term 'ML model inference' has been defined differently by SA WG5, SA WG6 and RAN WG1, as illustrated in Table 6.2.1.5-1. RAN WG3 follows the definition of SA WG5.
Table 6.2.1.5-1: Definition of ML model inference as defined across 3GPP WGs
TSG (TS/TR)
ML model inference
SA WG5 TS 28.105 [9]
A process of runnin... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.6 Analysis on ML model activation & ML model de-activation
| The term 'ML model activation' and 'ML model deactivation' have been defined by RAN WG1, as illustrated in Table 6.2.1.6-1. SA WG5 mentions the terms ML activation and ML deactivation several times in TS 28.105 [9] but does not provide a definition. It defines instead AI/ML activation/deactivation of the scope of an in... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.7 Analysis on ML model lifecycle
| The term 'ML model lifecycle' has been defined by SA WG6, as illustrated in Table 6.2.1.7-1. However, SA WG2 TS 23.288 [8], SA WG2 TR 23.700-84 [7], SA WG4 TR 26.927 [12], SA WG5 TS 28.105 [9], SA WG6 TR 23.700-82 [4], RAN WG1 TR 38.843 [3] and RAN WG3 also mentions one or more phases of ML model life cycle without pro... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.8 Analysis on ML model lifecycle management
| SA WG5 describes the ML model lifecycle in clause 4a.0 of TS 28.105 [9] and ML model lifecycle management capabilities for ML model training, ML model testing, ML inference emulation as optional, ML model deployment and AI/ML inference in clause 6.1 of TS 28.105 [9]. The terms 'ML model-based lifecycle management', 'ML... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9 Analysis on usage of ML Model identifier in each Working Group
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9.1 RAN WG 1
| As part of the RAN1 lead work " Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface AI/ML" work in RAN WGs in TR 38.843 [3], RAN is studying two flavours of LCM; Functionality-based and ML model-based (details in clause 4.2.1 of TR 38.843 [3] and clause 6.2.1.8.
- Study on the usage of ML ... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9.2 RAN WG 3
| As part of the RAN WG3 work in TS 38.300 [11]. The following scenarios are supported:
- AI/ML Model Training is located in the OAM and AI/ML Model Inference is located in the NG-RAN node.
- AI/ML Model Training and AI/ML model inference are both located in the NG-RAN node.
Analysis on usage of ML Model identifier:
... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9.3 SA WG 2
| As part of the work defined in TS 23.288 [8].
- An ML model is trained by the NWDAF MTLF.
Figure 6.2.1.9.3-1: ML model training/identification in AIML related work in SA WG2
- The training may be triggered by request(s) from one more ML model consumer(s) (i.e. NWDAF AnLF). The NWDAF AnLF indicates the purpose of t... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9.4 SA WG5
| As part of the work defined in TS 28.105 [9]:
- An ML model is trained by the ML training MnS producer.
Figure 6.2.1.9.4-1: ML model training/identification in AIML related work in SA WG5
- The training may be triggered by request(s) from one or more ML training MnS consumer(s). The consumer may be for example a n... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.9.5 SA WG6
| As part of the work defined in TS 23.482 [34]
- The ML model ID uniquely identifies the application-layer ML model.
Figure 6.2.1.9.5-1: ML model training/identification in AIML related work in SA WG6
- A VAL server may offload training of an ML model to an AIMLE server.
- An AIML server may train an ML model base... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.10 Analysis on ML model pre-specialized training and ML model fine-tuning
| The terms 'ML model pre-specialized training' has been defined by SA WG5 as illustrated in Table 6.2.1.10-1. No other 3GPP WG has yet adopted these terms in their activities.
Table 6.2.1.10-1: Definition of ML model pre-specialized training and ML model fine-tuning
TSG (TS/TR)
ML model pre-specialized training and M... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.1.11 Analysis on ML model distributed training
| The terms 'ML model distributed training' has been defined by SA WG5 as illustrated in Table 6.2.1.11-1. No other 3GPP WG has yet adopted these terms in their activities.
Table 6.2.1.11-1: Definition of ML model distributed training
TSG (TS/TR)
ML model distributed training
SA WG5 TS 28.105 [9]
Distributed trainin... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.2 Analysis on Federated Learning
| The term 'Horizontal Federated Learning' and 'Vertical Federated Learning' have been defined in SA WG2 and RAN WG1 as well as SA WG5 defines 'Federated Learning', as illustrated in Table 6.2.2-1.
Table 6.2.2-1: Definition of Federated Learning as defined across 3GPP WGs
TSG (TS/TR)
Federated Learning
SA WG2 TR 23.7... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.4 Analysis on Decision vs Prediction vs Output
| RAN WG1 and RAN WG3 only uses "prediction" in all corresponding ML related TRs/TSs. SA WG2 uses "output" in all corresponding TRs/TSs where output may include both statistics and predictions. SA WG5 uses "decision" in all corresponding TRs/TSs with few occurrences of "prediction".
The term "output" is proposed as unif... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.5 Analysis on ML vs AI vs AI/ML
| Across 3GPP WGs, different terminology is currently used to refer to Artificial Intelligence (AI) and Machine Learning (ML) functions:
- RAN WG1, RAN WG2, RAN WG3 and SA WG1 only uses "AI/ML" in all corresponding AI/ML related TRs/TSs.
- SA WG2 uses a mix of "ML" and "AI/ML" in all corresponding AI/ML related TRs/TSs... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.2.6 Analysis on Transfer Learning
| The term 'ML Knowledge-based Transfer Learning' has been defined by SA WG5 in TR 28.858 [19], as illustrated in Table 6.2.6-1. However, the term "Transfer learning" has not been defined in the study or normative phase for SA WG5 Release 19. SA WG6 mentions the term Transfer Learning' in TS 23.482 [34], but definition o... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.3 AI/ML related features
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.3.1 Analysis on ML model training services
| The analysis focuses on the specifications from SA WG2, SA WG5 and SA WG6, considering these are the working groups defining services and operations related to ML model training in 3GPP Release 18. SA WG1, SA WG3, SA WG4, RAN WG1, RAN WG2 and RAN WG3 have not defined any services or operations related to ML model train... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.3.2 Analysis on analytics related services
| This clause focuses on the specifications from SA WG2, SA WG5 and SA WG6, considering these are the working groups defining services and operations related to ML model inference in 3GPP Release 18. SA WG1, SA WG3, SA WG4, RAN WG1, RAN WG2 and RAN WG3 have not defined any services or operations related to ML model infer... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.3.3 Analysis on ML performance evaluation and monitoring
| The analysis focuses on the specifications from SA WG2, SA WG5 and SA WG6, considering these are the working groups defining services and operations related to ML performance evaluation in 3GPP Release 18 / Release 19. SA WG1, SA WG3, SA WG4, RAN WG1, RAN WG2 and RAN WG3 have not defined any services or operations rela... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 6.3.4 Analysis on data collection and management for AI/ML
| The analysis focuses on the specifications from SA WG2, SA WG6 and RAN WG3, considering these are the working groups defining services and operations related to data collection for AI/ML in 3GPP Release 18. SA WG1, SA WG3, SA WG4, SA WG5, RAN WG1 and RAN WG2 have not defined any services or operations related to data c... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 7 Overall Evaluation
| |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 7.1 General evaluation on AI/ML related terminology
| The study reviewed AI/ML-related activities across TSG SA, TSG RAN, and TSG CT Working Groups, to identify potential misalignment in AI/ML terminology and AI/ML feature descriptions across Working Groups.
The study confirms that AI/ML-related terminology across 3GPP WGs is broadly aligned at the conceptual level but s... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 7.2 Detailed evaluation on AI/ML-related terminology
| The evaluation below examines AI/ML-related terminology across working groups and proposes unified definitions where appropriate.
- ML model: Defined with differences across SA WG5, SA WG6, and RAN WG1 but all converge on a mathematical construct producing outputs from inputs.
- ML model training: Consistently descri... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 7.3 Evaluation summary on AI/ML-related terminology
| The evaluation of AIML-related terminology yielded the following observation:
- No critical inconsistencies in terminology have been identified that would block cross-domain AI/ML lifecycle management.
- Differences mainly reflect WG scope and perspective, not fundamental conflicts.
|
fba61181a0f9993b18933fec82e25a47 | 22.850 | 7.4 Evaluation summary on AI/ML-related features
| The analysis of AI/ML related features has identified services for AI/ML model training, AI/ML model inference and AI/ML performance are specified across the SA WG2, SA WG5 and SA WG6 Working Groups.
Additionally, analysis of AI/ML related features has also identified that services for data collection for AI/ML are sp... |
fba61181a0f9993b18933fec82e25a47 | 22.850 | 8 Conclusions
| The study documented in this technical report has identified a wide range of AI/ML-related activities across 3GPP working groups, including lifecycle management (LCM) functionalities, data handling mechanisms and terminology usage. These variations largely reflect justified functional scopes, architectural focuses and ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 1 Scope | The present document investigates use cases and potential new requirements related to 3GPP system enhanced support of specific 5G network sharing deployment scenarios, in particular where there is no direct interconnection between the shared NG-RAN and participating operators’ core networks. It includes the following a... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 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.
- Fo... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 3 Definitions of terms, symbols and abbreviations | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 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 Network Sharing: describes the communication between the shared access NG-RAN and... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 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].
HTA High Traffic Areas
LTA Low Traffic Areas
MOCN Multi-Operator ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 4 Overview | The present document introduces the newly supported network sharing scenario, where a NG-RAN is shared among multiple operators without necessarily assuming a direct connection between the shared radio access network and the participating operator’s core network. Use cases including service continuity and QoS, access c... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5 Use Cases | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1 Use Case on Network Sharing without Direct Connections between the Shared Access and the Core Networks of the Participating Operators | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.1 Description | As stated in TS 22.261 [3] the increased density of access nodes needed to meet future performance objectives pose considerable challenges in deployment and acquiring spectrum and antenna locations. RAN sharing is seen as a technical solution to these issues.
Sharing access networks and network infrastructure has becom... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.2 Pre-conditions | Two (or more) operators provide coverage with their respective radio access networks in different parts of a country but together cover the entire country.
There is an agreement between all the operators to work together and to build a shared network, but utilizing the different operator’s allocated spectrum appropriat... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.3 Service Flows | 1) UE1 can successfully attach to NG-RAN, and the display of the network operator name is the name of OP1.
2) UE2 can successfully attach to NG-RAN, and the display of the network operator name is the name of OP2.
3) UE3 can successfully attach to NG-RAN, and the display of the network operator name is the name of OP3.... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.4 Post-conditions | The hosting network will be able to provide accessing to all participating operators' users. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.5 Existing Features partly or fully covering Use Case Functionality | Network sharing has been studied in previous releases, where related normative stage 1 requirements are introduced in 3GPP TS 22.101 [2] and TS 22.261[3].
3GPP TS 22.101 [2] introduces general requirements of network sharing, stated as follows:
Network sharing shall be transparent to the user.
The specifications shall ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.1.6 Potential New Requirements needed to support the Use Case | [PR 5.1.6-001] The 5G system shall be able to support network sharing with indirect connection between the Shared NG-RAN and one or more Participating NG-RAN Operators’ core networks.
[PR 5.1.6-002] The 5G system shall be able to support means for Participating Operators to provide their operator’s name to a registered... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.1 Description | In Indirect Network Sharing scenario, the requirements to the services provided by the participating operator and the hosting operator for a UE moving between their service areas needs to be clearly defined. These service considerations are based on their user subscriptions and charging requirements from the participat... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.2 Pre-conditions | Assumptions,
1. OP 1 is a Hosting NG-RAN Operator.
2. The core network of OP 2 does not have direct connection with OP1’s Shared NG-RAN.
3. There is connection between the OP1’s CN and OP2’s CN.
4. UE 1 belongs to OP 1. UE 2 and UE N belong to OP 2. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.3 Service Flows | Figure 5.2.3-1: Basic service scenario without direct connections between the Shared NG-RAN and the core networks of the participating operators
1. UE 2 successfully registers to OP 2’s PLMN via the Shared NG-RAN.
2. UE 1 successfully registers to OP 1's PLMN.
3. UE N successfully registers to OP 2's PLMN, via OP2’s wi... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.4 Post-conditions | The service of UE 2 succeeds, when UE 2 moves between shared access network and participating operator’s network. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.5 Existing Features partly or fully covering Use Case Functionality | SA1 has performed various studies on services aspects in previous releases. For the definition of service continuity and the description of user experience see 3GPP TS 22.261 [3]. Requirements to service capabilities are described in 3GPP TS 22.101 [2] as follows:
The provision of services and service capabilities that... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.2.6 Potential New Requirements needed to support the Use Case | [PR 5.2.6-001] The 5G core network shall be able to support collection of charging information associated with a UE accessing a Shared NG-RAN using Indirect Network Sharing.
[PR 5.2.6-002] In case of Indirect Network Sharing and subject to Hosting and Participating Operators’ policies, the 3GPP system shall support ser... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3 Use Case on Network Access Control and Mobility between Sharing Parties | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.1 Description | It is worth mentioning that 5G networks have been designed to be able to provide shared facilities from the beginning. This means that in the case that the 4G network has both non-shared and shared E-UTRAN at the same time, there could be a number of different types of coverage in the same region:
- Non-shared E-UTRA c... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.2 Pre-conditions | 1. It is assumed that OP1, OP2 and OP3 has deployed 4G and 5G networks.
NOTE: The home 4G and 5G network of OP1, OP2 and OP3 may be deployed with non-shared and shared wireless access technology.
- Both OP1 and OP3 are Hosting NG-RAN Operators, which shared NG-RAN with participating OP2.
- UEs subscribe to OP2’s home P... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.3 Service Flows | Mobility and access control scenarios in shared network are illustrated in the following:
• Scenario 1 (Figure 5.3.3-1a): a UE with a subscription from OP2 moves between OP2’s own 4G access networks and either OP1’s or OP3’s shared 5G networks.
• Scenario 2 (Figure 5.3.3-1b): a UE with a subscription from OP2 moves bet... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.4 Post-conditions | All forms of mobility (i.e., between participating operators RAN and shared RAN for both CONNECTED mode and IDLE mode UE, see the clause 3.1 of TS 23.122 [5]) are successfully processed in a sharing scenario without direct connections between the shared access and the core networks of the participating operator. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.5 Existing Features partly or fully covering Use Case Functionality | SA1 has performed various studies on mobility and network sharing in previous releases, where related normative stage 1 requirements are introduced in 3GPP TS 22.101 [2] and 22.261 [3].
3GPP TS 22.261 [3] introduces requirements of Diverse mobility management, stated as follows:
The 5G system shall support inter- and/o... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.3.6 Potential New Requirements needed to support the Use Case | [PR 5.3.6-001] In case of indirect network sharing, the 3GPP system shall support mechanisms to minimize service interruptions for UEs that are moving between different Shared RANs or between a Shared RAN and a non-shared RAN (managed by Hosting and Participating Operators).
[PR 5.3.6-002] In case of Indirect Network S... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4 Use Case on International Roaming Users in a Shared Network | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.1 Description | There are network sharing scenarios in the process of 5G deployment due to different operators’ business consideration, such as network planning, operation and other factors, which introduce demand for 5G network sharing with indirect connection between the shared access network and a participating operator’s core netw... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.2 Pre-conditions | In the 5G scenario, an operator may deploy its network as an applicable shared network to other operators.
As illustrated in Figure 5.4.2-1, three operators (OP1, OP2, OP3) are involved:
- OP1, as a Hosting NG-RAN Operator, owns an applicable Shared NG-RAN which can be shared to other operators (e.g., OP2).
- OP2, as a... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.3 Service Flows | When a UE of OP3 travels to the coverage of OP2’s NG-RAN, it can enjoy services provided by their home environment in another country via OP2’s network.
When a UE of OP3 travels to the coverage of OP1’s shared NG-RAN, it can enjoy services provided by their home environment in another country via OP1’s shared access ne... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.4 Post-conditions | It is the same for the service experience and treatment of OP2’s UE and OP3’s UE in the coverage of OP1’s Shared NG-RAN, based on the agreement between operators. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.5 Existing Features partly or fully covering Use Case Functionality | 3GPP TS 22.011 [6] introduces requirements on roaming in shared networks, as described below:
The following requirements are applicable to GERAN, UTRAN, E-UTRAN and NG-RAN sharing scenarios:
- When network sharing exists between different operators and a user roams into the shared network it shall be possible for that ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.4.6 Potential New Requirements needed to support the Use Case | [PR 5.4.6-001] The 5G system shall enable Shared NG-RAN of a Hosting Operator with the indirect connection between Shared NG-RAN and a Participating NG-RAN Operator’s core network to provide services for inbound roaming users.
NOTE: Inbound roaming users mentioned above refer to the subscribers of a foreign operator ha... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.1 Description | Subscribers have the opportunity to visit the Hosted Services via its own operator's network, specified in TS 22.261[3]. These Hosted Services contain applications provided by operators and/or trusted 3rd parties. Usually, operators use some technologies to optimize the path of the user plane to reduce latency and band... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.2 Pre-conditions | Assumptions,
1. OP1 is a Hosting NG-RAN Operator.
2. The core network of OP2, as the participating operator, does not have direct connection with OP1’s shared NG-RAN.
3. There is connection between the OP1’s CN and OP2’s CN.
4. OP2 provides Hosted Services for subscribers in the local area 1 and 2. OP2 wishes to provid... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.3 Service Flows | Figure 5.5.3-1: Scenario of visiting Hosted Services via shared network
1. UE is the subscriber of OP2, and enjoy the Hosted Services of OP2 in the local area 2.
2. UE is ready to move to the shared network of OP1. During this process, the Service Hosting Environment hosting the service may or may not change.
3. Availa... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.4 Post-conditions | The visiting hosted service via shared network succeeds, when UE moves between shared access network and participating operator’s network. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.5 Existing Features partly or fully covering Use Case Functionality | Session 6.5 of TS 22.261 mainly introduces the relevant terms and related requirements of Hosted Services. Some typical requirements for service in network sharing are:
5G is designed to meet diverse services with different and enhanced performances (e.g. high throughput, low latency and massive connections) and data t... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.5.6 Potential New Requirements needed to support the Use Case | [PR 5.5.6-001] In case of Indirect Network Sharing, the 5G system shall support a mechanism to enable a UE subscribed to the participating operator to access the participating operator’s Hosted Services.
5.6 Use Case on Emergency Call |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.1 Description | The network is allowed to route the emergency call to the emergency response centre in the area where the operator provides services, as specified in TS 22.101[2], in accordance with national regulations and where the subscriber is located.
In order to route emergency calls to the correct emergency response centre, ope... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.2 Pre-conditions | Assumptions:
1. OP-1 is a Hosting NG-RAN Operator. There is a connection between the OP-1’s CN and OP-2’s CN, while OP-2 as a participating operator indirectly sharing the network.
2. OP-2, as the participating operator, is an emergency call service provider. The network of OP-2 is connected to the emergency response c... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.3 Service Flows | Figure 5.6.3-1: Emergency call routing in network sharing scenarios
1. UE is registered to OP-2. UE accesses the shared network of OP-1, and registered with the OP-2’s IMS. The nearest emergency response centre to UE's current geographic location is in Area 1, shown as Fig. 5.6.3-1.
2. UE initiates an emergency call in... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.4 Post-conditions | The emergency call can be correctly routed to the appropriate PSAP to serve the UE according to its location information. |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.5 Existing Features partly or fully covering Use Case Functionality | Chapter 10 of TS 22.101[2] defines the emergency call service. According to National regulations, the requirement of UE’s location of emergency call service is different in deployment scenarios, examples are:
National regulations may require wireless networks to provide the emergency caller's location. This requirement... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.6.6 Potential New Requirements needed to support the Use Case | [PR 5.6.6-001] Subject to national or regional regulatory and operator policies, the 5G system shall support emergency call from a UE accessing a Shared NG-RAN via Indirect Network Sharing.
[PR 5.6.6-002] Subject to national or regional regulatory and operator policies, the 5G system shall provide to the Participating ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7 Use Case on Long-distance Mobility in and across Shared Networks | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.1 Description | Despite the aircraft and rail have been developed to serve more and more regions, road transport remains the most important way to deliver goods. As the logistics industry is booming, the total length of long-distance road transport has increased every year in the last ten years. How to provide communication service du... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.2 Pre-conditions | It is assumed that network operators OP1, OP2, and OP3 have deployed 5G networks respectively in a country. Their radio access network can provide coverage to different regions of the country, and together cover the entire country with overlapping in certain regions.
OP1 and OP3 are agreed with OP2 to share radio acces... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.3 Service Flows | 1. UE on the vehicle connects to OP2’s network via OP1 shared access nodes and is authorized to initiate a communication service (e.g., data transfer, IMS voice call) during the movement.
2. In geographic Area #A, UE connects to OP2’s network only through the access nodes like 5G BS #A based on the agreement and the po... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.4 Post-conditions | UE can get services with the displayed serving network as OP2’s network when move in OP1’s Shared NG-RAN, across OP1’s and OP3’s shared RANs, and across OP3’s shared RAN and OP2’s non-shared RAN.
OP2 ensures service continuity with proper mobility and access control to the shared access nodes of the same or different H... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.5 Existing Features partly or fully covering Use Case Functionality | The normative stage1 requirements of network sharing has been introduced to TS22.101 [2] and TS 22.261 [3] in previous releases. TS 22.101[2] specifies the service principle about Network Sharing that
It shall be possible to support different mobility management rules, service capabilities and access rights as a functi... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.7.6 Potential New Requirements needed to support the use case | [PR 5.7.6-001] Subject to the agreement between Hosting Operators and Participating Operator, the 5G system shall support a mechanism to authorize a UE with the subscription to the Participating Operator to obtain services in a Shared NG-RAN of Hosting Operators using Indirect Network Sharing.
[PR 5.7.6-002] In case of... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8 Use Case on Support of PWS in Shared NG-RAN in Indirect Interconnection with the Participating Operators | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.1 Description | Operators 1 and 2, both licensed to operate a 4G network and a 5G network share the 5G part of the radio access network in some areas of the country.
The Public Safety Agency sends the PWS message in a certain area covered by NG-RAN1 and RAN2 of Operator 1 and Operator 2 respectively and by the shared NG-RAN area of Op... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.2 Pre-conditions | • Operator 1 owns NG-RAN 1 which is not shared.
• Operator 2 owns RAN 2 which is not shared.
• NG-RAN is a shared NG-RAN between Operator 1 and Operator 2.
• Operator 1 is the hosting operator.
• Operator 2 is a participating operator. Operator 1 and Operator 2 share NG-RAN in an indirect sharing method.
• Operator 1 h... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.3 Service flows | 1) The Public Safety Agency (PSA) sends the PWS message in a certain Shared NG-RAN radio coverage area designated by the PSA where Operator 1 and Operator 2 share the RAN access.
2) Operator 1 and Operator 2 both broadcast the PWS message in the area covered by their respective not shared RAN they have regulatory oblig... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.4 Post-conditions | For UEs subscribed to unshared accesses NG-RAN 1 and RAN 2, the public warning message can only be received by UEs subscribed to these operators owning the access.
UEs served by Shared NG-RAN receive the public warning message issued by the PSA in the radio coverage area of the Shared NG-RAN designated for the warning ... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.5 Existing requirements to PWS Support in Shared Networks | See TS 22.101 [2].
28.2.5 PWS support of Shared E-UTRAN/NG-RAN
A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of E-UTRAN/NG-RAN sharing.
The following requirements apply:
The shared E-UTRAN/NG-RAN shall be able to broadcast PWS messages originated fr... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 5.8.6 Potential New Requirements needed to support the Use Case | [PR 5.8.6-001] Subject to regulatory requirements and mutual agreement between the Participating Operators and the Hosting Operator, the 5G system shall be able to support PWS when connectivity is provided via Indirect Network Sharing.
[PR 5.8.6-002] Subject to regulatory requirements and mutual agreement between the P... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 6 Other considerations | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 6.1 Considerations on security | Different from MOCN configuration, which routes UE to the core network of a participating operator directly through Shared RAN of hosting operator, Indirect Network Sharing needs to involve the core network of the Hosting NG-RAN Operator in the signaling exchange. The interoperability between the core networks of Hosti... |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 7 Consolidated requirements | |
c3de68f0eebb105002ecbb9ed169af5e | 22.851 | 7.1 Introduction | Potential requirements on Indirect Network Sharing have been identified in Section 5 out of the use cases under the following aspects:
- General
- Mobility
- Network access control
- Regulatory services
- Charging
These requirements have been especially introduced to support the newly defined network sharing scenario, ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.