hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.1.3 Potential solutions
| This solution proposes following updates in TS 28 561 [3]:
1. In clause 4.3, add Intent Handling function as one additional example of network automation functions.
2. In clause 5.2.2.1, add the text below:
"NDT can support for Intent Handling Function enabling intent handling capability, e.g., feasibility check an... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.1.4 Evaluation of potential solutions
| Only one potential solution provided in clause 5.1.3 is identified. This potential solution proposes enhancing the existing text description in TS 28.561 [3] clause 4.3 and 5.2.2.1 respectively. It is a feasible solution.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.2 Use Case #2: Improvement of data generation
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.2.1 Description
| TS 28.561 clause 5.4.2.2 [3] introduces the data generation capability provided by NDT to enable ML training. For different ML models, the preferences of its training data are different, which can vary in the dimension of data source object, data type, data quantity. The data source object is used to specify the simula... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.2.2 Potential requirements
| REQ-NDTDG-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to express data generation preferences on data source object, data type, and data quantity.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.2.3 Potential solutions
| This solution aims to enhance NDT NRMs as shown below:
1. Enhancement for NDTJob IOC
- Add new attribute "nDTDataGenObject" which represents the data source object from which the synthetic data is collected. This attribute allows the MnS consumer to express data generation preferences on data source objects.
- Add ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.2.4 Evaluation of potential solutions
| Only one potential solution provided in clause 5.2.3 is identified. This potential solution proposes to enhance existing NDTJob IOC with two new attributes which allow the MnS consumer to express data generation preferences on data source objects and data quantity. It is a feasible solution to satisfy the requirement i... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.3 Use case #3: Collaborate with ML training Producer to generate data
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.3.1 Description
| In TS 28.561 [3], the existing use case and requirements for using NDT to generate ML training data is described in clause 5.4.2.2. However, using NDT alone to generate data may be insufficient to support the following scenarios:
- Due to the coverage limitations of the physical network simulated by NDT, some extreme... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.3.2 Potential requirements
| REQ-NDTDG-AI-1: The 3GPP management system should support a capability that enables an authorized MnS consumer to obtain the enabler information of the NDT data generation.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.3.3 Potential solutions
| This solution aims to enhance the NDTReport IOC in TS 28.561 [3] to support the reporting of enabler information of the NDT data generation. Details are as shown below:
Add a new attribute "NDTDataGenEnaInfo" representing the enabler information of the NDT data generation, specifying whether AIML is used or not, with ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.3.4 Evaluation of potential solutions
| There is only one solution for clause 5.3, which is feasible.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.4 Use Case #4: Enhancement for multiple NDT collaborations
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.4.1 Description
| In TS 28.561 [3], the existing use case and requirements for collaboration between NDTs are described in clause 5.5.2.1 and the requirement in clause 5.5.3. The 3GPP management system should support a capability enabling an authorized MnS consumer to configure the relationship between NDTs during simulation/emulation. ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.4.2 Potential requirements
| REQ-NDT-Colla-1: The 3GPP management system should support a capability that enables an authorized MnS consumer to request a report on the relationships between NDTs regarding the collaboration of multiple NDTs.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.4.3 Potential solutions
| This solution aims to enhance NDTReport IOC and NDTFunction IOC in TS 28.561 [3], to support the reporting of multiple NDT collaboration relationships and update the corresponding definition in clause 6.2.1.3. Details are as shown below:
1. Enhancement for NDTReport IOC:
- Add new attributes "NDTCollaborationInfoList... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.4.4 Evaluation of potential solutions
| There is only one solution for this use case, which proposes to enhance the existing NDT IOCs. This solution is feasible and can serve as the baseline for normative work.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.5 Use Case #5: Enhancement on NDT reporting method
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.5.1 Description
| In TS 28.561 [3], the reporting method of NDT output is notification based reporting. The NDT MnS consumer receives an NDT report from NDT producer by invoking generic provisioning management service operations and notifications in TS 28.532 [4]. However, different NDT job may have different requirement on reporting me... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.5.2 Potential requirements
| REQ-NDTRM-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to request NDT report to be provided by streaming data reporting service.
REQ-NDTRM-02: The 3GPP management system should support a capability for NDT MnS producer to support delivery of NDT report by streaming dat... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.5.3 Potential solutions
| It is proposed to make the following changes to TS 28.561 [3] clause 6.2.1.3.2:
- update the NDTJob IOC attribute to add a new optional attribute reportingMethod, which can be used to indicate the required reporting method of NDT report, the allowed values of reportingMethod can include streaming and notification. The... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.5.4 Evaluation of potential solutions
| Only potential solution #1 is proposed, the requirements are satisfied and this solution is feasible for normative work.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.6 Use Case #6: Capability Discovery of NDT in NDT Collaboration
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.6.1 Description
| NDT collaboration among different NDTFunctions located in different domain is critical to enable end to end use cases, In Rel-19 the supported domain of NDT is represented by NDTFunctionScope attribute. Then, the NDTFunction that triggers the collaboration can involve NDT(s) that supports modelling of different domain.... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.6.2 Potential requirements
| Table 5.6.2-1: REQ- NDTAUT-01
REQ- NDTAUT-01
The 3GPP management system should support a capability enabling authorized MnS Consumer to discover detailed capability of candidate NDT components for NDT collaboration.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.6.3 Potential solutions
| Add a new the GenericModellingCapabilites <<dataType>> with the following new attributes to support modelling capability discovery of NDT in NDT collaboration:
- EnviromentModelling, it represents the NDTFunction supports to model the network topology and network infrastructure.
- UETrafficModelling, an ENUM, which i... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.6.4 Evaluation of potential solutions
| Only one solution has been identified, which is feasible.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7 Use Case #7 Defining the Lifecycle and Runtime Behaviour of NDT Jobs
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.1 Description
| The NDTJob lifecycle is not clear, there are some items open to interpretation and some items missing which are described below.
The MnS Consumer should have a method to know which configuration of NDTJob has produced a given report. In the current specification NDTReport refer to the NDT job (i.e. NDTJobRef). In the ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.2 Potential requirements
| REQ-DTLCM-XX: The MnS Producer should provide a mechanism for the MnS Consumer to distinguish between different configurations of the same NDTJob instance that may exist over time as a result of modify operations.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.3 Potential solutions
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.3.1 Solution1: New attribute to the ndtJob and ndtReport to maintain the version information
| An NDTJob MOI represents the job request and configuration provided by the MnS Consumer, including the network scenario, synchronization scope, and execution requirements.
To enable unambiguous correlation between NDTReports and the configuration used during NDTJob execution:
- A new read-only attribute (e.g. ndtJobS... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.3.2 Solution2: MnS Consumer maintains the configuration change information as required.
| The MnS Consumer(s) of the ndtJob maintain the ndtJob configuration identity information.
They can do this by subscribing to the notification regarding modification of the ndtJob MOI. If it receives a notification that the simulation related attributes of the ndtJob MOI have been modified, then it can internally maint... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.7.4 Evaluation of potential solutions
| Both solutions are feasible, however, to keep aligned with common behaviour in 3GPP SA5, the recommendation is to move forward with solution 2 as in clause 5.7.3.2.
Solution 2 has no normative impacts.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.8 Use Case #8: Using external data for NDT modelling
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.8.1 Description
| As defined in TS 28.561 [3], Network Digital Twin (NDT) is used as a replica of a mobile network, in order to learn how an actual mobile network would behave in certain scenarios, without causing any changes to the actual mobile network. To provide meaningful results, an NDT needs to model the behaviour of the mobile n... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.8.2 Potential requirements
| REQ-NDTDG-01: The 3GPP management system should support a capability to allow an authorized MnS consumer to specify external data information used for NDT modelling.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.8.3 Potential solutions
| TS 28.622 defines the ExternalDataType IOC which specifies a type of external management data and the associated meta data. This solution aims to enhance NDTJob IOC and NDTFunction IOC by reusing ExternalDataType IOC to carry the NDT MnS consumer's external data preference for an NDT job and show the supported external... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.8.4 Evaluation of potential solutions
| Only one potential solution provided in clause 5.8.3 is identified. This potential solution proposes enhancing existing NDTJob IOC and NDTFunction IOC by reusing ExternalDataType IOC to carry the NDT MnS consumer's external data preference for an NDT job and show the supported external data of NDT Function used for NDT... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9 Use Case #9: NDT for Non-Terrestrial Network (NTN) Performance and Optimization Evaluation
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.1 Description
| According to 3GPP TS 38.300 [5] a Non-Terrestrial Network (NTN) is defined as an NG-RAN consisting of gNBs, which provide non-terrestrial NR access to UEs by means of an NTN payload embarked on an airborne or space-borne NTN vehicle and an NTN Gateway. NTN Gateway is an earth station located at the surface of the earth... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.2 Potential requirements
| No new requirements are identified.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.3 Potential solutions
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.3.1 Solution update NDTFunctionScope
| This solution proposes to update the NDTFunctionScope with a new attribute named nDtNTNScope. nDTNTNScope can be used to indicate that the NDT concerns to NTN and further indicate the scope of the NTN that can be modelled by the NDT MnS Producer.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.3.2 Solution update supported NDTCapabilities
| This solution proposes to update the allowed values of supportedNDTCapabilities which indicate the different types of scenario specific capability which the NDT MnS Producer is capable of undertaking, with a new value named "NTN_PERFORMANCE_PREEVALUATION".
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.9.4 Evaluation of potential solutions
| Solution 1 is feasible since it reuses the existing NDT framework specified in TS 28.561 and provides an NRM extension needed by the NDT MnS Producer to be aware of the NTN scope when considering NTN.
Solution 2 is feasible since it reuses the existing NDT framework specified in TS 28.561 and provides an NRM extension... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.10 Use Case #10: Clarification of NDTJob Modification Behaviour
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.10.1 Description
| The MnS Consumer requires clarity on the conditions and procedures for modifying an existing NDTJob instance. At the moment, the specification leaves this open to interpretation, even though there are clear limitations associated with different implementation techniques for NDTJobs. For instance, if an NDTJob is implem... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.10.2 Potential requirements
| REQ-DTLCM-XX: The MnS Producer should expose the execution status of each NDTJob instance.
REQ-DTLCM-XX: The MnS Producer should allow for modification of the NDTJob.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.10.3 Potential solutions
| To ensure predictable behaviour across different NDTJobs, the NDTJob IOC should be extended with an attribute to expose its current lifecycle status. The proposed statuses of an NDTJob are as follows:
ACKNOWLEDGED: The NDTJob is accepted and checked for its validity. The consumer sends "createMOI (NDTJob)" request to ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.10.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.11 Use Case #11: Create and Execute NDT Job
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.11.1 Description
| The MnS Consumer requires clarity on whether the creation and execution of an NDTJob are distinct phases or a single combined procedure.
By having creation of an NDTJob separate to the execution of the NDTJob, it means certain MnS Consumers can define the NDTJob, and other MnS Consumers could execute the NDT jobs. Thi... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.11.2 Potential requirements
| REQ-DTLCM-XX: The 3GPP management system should allow an authorized MnS consumer to create an NDTJob without immediate execution.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.11.3 Potential solutions
| This solution resolves the inconsistency across clauses by formalising that creation and execution of an NDTJob are two distinct phases, and by leveraging ndtJobAdminState to clearly indicate when an NDTJob is permitted to run.
Administrative state indicates whether a process is permitted by management to run.
- loc... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.11.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.12 Use Case #12: Clarification of Suspension and Resumption Capabilities for NDTJobs
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.12.1 Description
| The MnS Consumer requires clarity on whether an NDTJob can be suspended and subsequently resumed, when such capabilities are supported by the NDT MnS Producer.
The MnS Consumer should have the capability to suspend NDTJobs such as an optimization activity in order to free up resources to prioritize different NDTJobs s... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.12.2 Potential requirements
| REQ-DTLCM-XX: The MnS Producer should support a mechanism for the MnS Consumer to suspend and resume NDTJobs.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.12.3 Potential solutions
| Information model alignment
- The NDTJob IOC shall support using the ndtJobAdminState introduced in clause 5.11, for suspension and resumption of the NDTJob.
- The attribute shall be exposed by the MnS Producer only if suspension/resumption is supported for the corresponding NDTJob.
Suspension and resumption proced... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 5.12.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6 Conclusions and Recommendations
| |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.1 Use Case #1: NDT support intent pre-evaluation
| The use case of NDT support intent pre-evaluation is described in clause 5.1 and no new requirement is identified. The potential solution is to update text description for NDT supporting intent pre-evaluation in TS 28 561 [3]. It is recommended to use the solution in clause 5.1.3 as baseline for normative work.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.2 Use Case #2: Improvement of data generation
| The use case of data generation improvement is described in clause 5.2 and requires the management capability to allow MnS consumers to express data generation preferences on data source object, data type, and data quantity.
It is recommended to enhance information model of NDTJob IOC defined in TS 28.561, using the ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.3 Use case #3: Collaborate with ML training Producer to generate data
| The use case description, potential requirements and a potential solution for collaborating with the ML training Producer to generate data are introduced in clause 5.3. This use case clarifies the data generation where the AI-based data generation models generated by the ML training Producer are introduced into NDT, an... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.4 Use Case #4: Enhancement for multiple NDT collaborations
| The use case description, potential requirements and a potential solution for the multiple NDT collaborations are introduced in clause 5.4. This use case clarifies the collaborative scenario where a single NDTFunction may not independently fulfil a simulation/emulation task and needs to rely on the services or outputs ... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.5 Use case #5: Enhancement on NDT reporting method
| The use case, requirements and solution for Use case: Enhancement on NDT reporting method is described in clause 5.5. It is recommended to add new attribute in NDTJob IOC to support a choice of streaming or notification for the NDT reporting method in TS 28.561 [3]. The detailed solution is described in clause 5.5.3.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.6 Use case #6: Capability Discovery of NDT in NDT Collaboration
| It is recommended to enhance the information model of NDT as per the potential solution in the clause 5.6.3 to support above identified management capabilities.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.7 Use case #7: Defining the Lifecycle and Runtime Behaviour of NDT Jobs
| The use-case and solution as proposed in clause 5.7.3.2 explains how the MnS Consumer can achieve the use-case, by monitoring the modification of the ndtJob and tracking which version of the ndtJob has produced which ndtReport.
No new normative work is expected as a result of this solution.
|
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.8 Use Case #8: Using external data for NDT modelling
| The use case of using external data for NDT modelling is described in clause 5.8 and requires the management capability to allow MnS consumers to specify external data information used for NDT modelling.
It is recommended to enhance information models for NDT management defined in TS 28.561, using the solution in clau... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.9 Use Case #9: NDT for Non-Terrestrial Network (NTN) Performance and Optimization Evaluation
| The use case of NDT for Non-Terrestrial Network (NTN) Performance and Optimization Evaluation described in clause 5.9 is not introducing additional requirements. Solutions described in clauses 5.9.3.1 and 5.9.3.2 are used to enable support for NTN networks and are related to existing requirements in TS 28.561.
It is r... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.10 Use case #10: Clarification of NDTJob Modification Behaviour
| The use-case and solution as proposed in clause 5.10 provides for the MnS Consumer the capability to monitor the state of the ndtJob. This allows the MnS Producer of the ndtJob the capability to indicate when modification of a ndtJob is possible based on the state of the ndtJob using states "ACKNOWLEDGED" and "SUSPENDE... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.11 Use case #11: Create and Execute NDT Job
| The use-case and solution as proposed in clause 5.11 provides for the MnS Consumer the capability to create and then later execute the ndtJob (simulations). The main motivation was to allow different users with different levels of access to perform the individual actions (e.g. create, execute).
The recommendation will... |
05c56d19e9004109bb58601d28cb2cad | 28.883 | 6.12 Use case #12: Clarification of Suspension and Resumption Capabilities for NDTJobs
| The use-case and solution as proposed in clause 5.12 provides for the MnS Consumer, the capability to suspend and resume the ndtJob (simulations). The main motivation was to allow the temporary release of resources via suspension to prioritize the execution of critical ndtJobs (e.g. fault related).
The recommendation ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 1 Scope
| The present document describes use cases, potential requirements, and potential solutions aimed at enhancing the Service Based Management Architecture (SBMA) in the context of 5G Advanced (5GA). It also presents conclusions and recommendations regarding the next steps in the standardization process.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 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.
-... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3 Definitions of terms, symbols and abbreviations
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4 Concepts and background
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.1 Introduction
| SBMA adopts a modular, service-oriented approach that enables flexible, scalable, and interoperable management solutions.
The architecture for the present study builds upon the SBMA framework in TS 28.533 [2]. All potential enhancements and solutions are expected to comply with the principles outlined in TS 28.533 [2]... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.2 Management data streaming based on Message Bus technologies
| 3GPP TS 28.532 [3] defines Stage 2 and Stage 3 of the streaming data reporting service. Currently, the 3GPP management system supports WebSocket-based data streaming for PM, tracing, and analytics, establishing a point-to-point transport connection between the streaming data reporting MnS consumer and MnS producer. The... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 4.3 Message Bus principles integrated in SBMA
| Message Bus principles
A Message Bus is a middleware architecture that enables different systems or services to communicate through a shared messaging infrastructure in a decoupled way. Key principles include the following:
• Loose Coupling: Services interact without knowing each other’s internal details. Enhance... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5 Use cases and potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1 Use case #1: Integration of SBMA with 5GC and 5G Access Network architecture
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.1 Description
| In a 5G Advanced network deployment, a mobile operator adopts an SBMA that leverages a modular reference model as defined in annex A.11 of TS 28.533 [YY]. This model abstracts Management Functions (MnFs) as logical entities, independent of their physical implementation, and enables them to interact exclusively through ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.2 Potential requirements
| REQ-SBMA-ARM-1: SBMA should provide a consolidated view of management architecture.
|
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.1.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2 Use case #2: Management data streaming based on Message Bus
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.1 Description
| The 5G network employs a distributed, service-oriented architecture, leading to scenarios where multiple consumers request the same management data for multiple uses. In a typical network performance data reporting scenario, an MnS producer collects and transmits performance data to multiple MnS consumers within the ne... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.2 Potential requirements
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.3 Potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.3.1 Solution #1: Multipoint-to-Multipoint management data streaming based on message broking MnF
| This potential solution proposes introduction of a new MnF implementing the message broker(s) that mediates data with the help of new MnS services, namely, message bus data reporting MnS and message bus data retrieval MnS (for data subscribers) to enable multipoint-to-multipoint streaming data reporting. This solution ... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.2.4 Evaluation of potential solutions
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3 Use case #3: Historical alarms
| |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.1 Description
| The "AlarmList" defined in TS 28.111 [10] contains "AlarmRecords" that represent currently active alarms. Alarms, that are cleared and acknowledged (inactive alarms) are removed from the alarm list and cannot be retrieved any more by MnS consumers.
However, old inactive alarms (historical alarms) are a valuable source... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.2 Potential requirements
| REQ-1: The 3GPP Management system should have the capability allowing to retrieve alarms that were active in the past (historical alarms).
REQ-2: The 3GPP Management system should have the capability allowing to retrieve alarms that were active at a certain point in time in the past.
REQ-3: The 3GPP Management system... |
a783bfffabe0a6b1e88e24a2cc62e556 | 28.884 | 5.3.3 Potential solutions
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.