hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1 Use case #1: Enhancement of radio service delivering and assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation for delivering a radio service is described in clause 5.1.2. The RadioServiceExpectation is defined to represent MnS consumer's expectations for radio service delivering and assurance in the specified area. However, follo... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.2 Potential requirements
| REQ-IDMS_RadioServiceIntent-CON-1: The intent driven MnS producer for radio service should have capabilities enabling the MnS consumer to express service reliability requirements.
REQ-IDMS_RadioServiceIntent-CON-2: The intent driven MnS producer for radio service should have capabilities enabling the MnS consumer to e... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.3 Potential solutions
| This solution proposes to reuse and enhance the existing RadioServiceExpectation defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Add following attributes as the ExpectationTargets for the RadioServiceExpectation to enable the MnS consumer to express service reliability requirements.
- ReliabilityTarget, it repres... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.1.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2 Use case #2: Enhancement of radio network performance assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation on radio network performance to be assured and intent containing an expectation for RAN energy saving are described in clause 5.1.5 and clause 5.1.7. The RadioNetworkExpectation is defined in clause 6.2.2.1.1 to represent... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2.2 Potential requirements
| REQ-IDMS_RadioNetworkIntent-CON-1: The intent driven MnS producer for radio network should have capabilities enabling the MnS consumer to express radio network performance assurance for a specific RAN feature.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2.3 Potential solution
| This solution proposes to reuse and enhance the existing RadioNetworkExpectation defined in 3GPP TS 28.312 [1] to enable the MnS consumer to express radio network performance assurance for a specific RAN feature.
Enhancement Aspect1: Add following attributes as the ObjectContexts for the RadioNetworkExpectation:
rANF... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.2.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3 Use case #3: Assisting and reporting intent decomposition across intent handling functions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3.1 Description
| An intent-driven MnS producer can translate an intent and decompose it into one or more new intents. If these newly generated intent(s) cannot be handled by the intent-driven MnS producer, it can submit them to another intent-driven MnS producer(s). In this case, the former intent-driven MnS producer acts as the consum... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3.2 Potential requirements
| REQ-Intent_DCMP-1: The intent driven MnS producer should have the capability to allow an MnS consumer to specify a context to be able to assist the intent-driven MnS producer regarding the decomposition of an intent to other MnS producers.
REQ-Intent_DCMP-2: The intent driven MnS producer should have the capability to... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3.3.1 Potential solution #1
| This solution proposes to reuse and enhance the existing intent expectations and intent report information models defined in 3GPP TS 28.312 [1].
Intent expectations are enhanced with:
- A new expectation context that specifies the constraints applicable in the intent decomposition performed by the intent-driven MnS p... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.3.4 Evaluation of potential solutions
| Only one potential solution provided in clause 4.3.3.1 is identified. This potential solution proposes enhancing the existing intent expectations by adding a new expectation context that allows the MnS consumer to specify intent handling functions that are not recommended for intent decomposition. This allows an MnS co... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4 Use case #4: Intent traceability
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.1 Description
| An intent consumer (owner) submits an intent to a single intent handling function. In some cases, in order to fulfil the intent an intent handling function may need to submit additional intent(s) to other intent handling functions. Such handling can occur multiple times across intent handling functions across multiple ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.2 Potential requirements
| REQ-Intent_Trace-1: The intent driven MnS producer should provide information in the intent to identify that an intent has been handled by a particular intent handling function.
REQ-Intent_Trace-2: The intent driven MnS producer should provide information (as defined in REQ-Intent_Trace-1) to identify any subsequent i... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.3.1 Potential solution #1
| To address REQ-Intent_Trace-1, REQ-Intent_Trace-2 and REQ-Intent_Trace-3 this solution proposes adding a new data structure to the intent model definition to define the information to trace the decomposition of an intent into subsequent intents. The information is updated and propagated as new intent(s) are created as ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.3.1 Potential solution #2
| To address REQ-Intent_Trace-4, this solution proposes adding a new attribute to the intent model definition to allow the MnS consumer indicate its preference for the propagation of intent traceability information.
The content proposed for the intent model definition would include:
- an attribute to indicate intent de... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.4.4 Evaluation of potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.5 Use case #5: Invariant Guidance in Intent Contexts
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.5.1 Description
| 3GPP TS 28.312 [1] describes a scenario where for an instantiated intent, the intent handler may need to decompose the intent into multiple derivative intents, each to be fulfilled by a separate other intent handler. There may be contexts in the intent which the MnS consumer desires that the other intent handlers under... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.5.2 Potential requirements
| REQ-Intent_InvarGui-1: The intent driven MnS should include a capability enabling the MnS consumer to indicate the requirements, goals and contexts which the MnS consumer recommends be copied into decomposed intents and transmitted to other intent handlers without modification.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.5.3 Potential solutions
| The "context" dataType, as defined in 3GPP TS 28.312 [1], can be extended to include information about invariant guidance.
- Add a description for invariant guidance e.g. as: The Context can be used to indicate invariant guidance, e.g., which context is recommended to be propagated to all intent handler functions in t... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.5.4 Evaluation of potential solutions
| TBA
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.6 Use case #6: Intent Interpretation Assistance Information
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.6.1 Description
| A similar intent can be instantiated on several intent handlers, e.g., on several management systems each responsible for a for a different domain. 3GPP TS 28.312 [1] supports intent negotiation that enables interaction between the MnS producer and MnS consumer to clarify the ability to fulfill intent requirements that... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.6.2 Potential requirements
| REQ-Intent_Interpretation_Assistance_1: The intent driven MnS producer should have the capability enabling the MnS consumer to provide information containing prior intent negotiations to the handler that can then be used by the intent handler to support the interpretation of the intent.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.6.3 Potential solutions
| - Add to the Intent IOC a description of the information about intent interpretation e.g., as:
a) The intent IOC includes intentInterpretationAssistanceInfo which contains prior negotiation interactions from the MnS consumer that are provided to the intent handling function and can be used by the intent handling funct... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.6.4 Evaluation of potential solutions
| TBA
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.7 Use case #7: Enhancement of intent exploration
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.7.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent Exploration is defined in clause 5.3.5. The IntentExplorationReport is defined in clause 6.2.1.3.19 to represent the intent exploration result, which includes the list of expectation exploration results. However, following scenarios are not suppor... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.7.2 Potential requirements
| REQ-IDMS-IntentExploration-CON-1: The intent driven MnS producer should have the capability enabling the MnS consumer to request to periodically obtain the exploration report.
REQ-IDMS-IntentExploration-CON-2: The intent driven MnS producer should have the capability enabling the MnS consumer to obtain the best target... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.7.3 Potential solution
| This solution proposes to reuse and enhance the existing Intent and IntentReport IOC defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Extend the IntentReportControl <<dataType>> with following aspects:
- Extend the attribute "observationPeriod" in IntentReportControl <<dataType>> to indicate the time period for wh... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.7.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8 Use case #8: Support to express guarantee requirements in an intent
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.1 Description
| In today's highly dynamic and heterogeneous network environment, Intent-Driven Management Service (IDMS) is emerging as the foundational paradigm for advanced network operations and automation. Nevertheless, practical deployments reveal a critical capability gap: the absence of robust support for dynamic resource reser... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.2 Potential requirements
| REQ-IDMS_Guarantee-1: The intent driven MnS producer should have the capability to allow MnS consumer to express an intent to be guaranteed and which expectations requirement in an intent should be guaranteed.
REQ-IDMS_Guarantee-2: The intent driven MnS producer should have the capability to allow MnS consumer to spec... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.3.1 Potential solution #1
| To support to express guarantee requirements in an intent, the following enhancements are proposed:
- Add a new attribute guaranteeIndicator in the Intent IOC to allow the MnS Consumer to specify Guarantee Requirements in the intent. guaranteeIndicator attribute can be on intent expectation level.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.3.2 Potential solution #2
| Enhancement Aspect 1:
A new generic type of intentContext and expectationContext is proposed to be added to the Intent <<IOC>> and IntentExpectation <<dataType>>, respectively.
The presence of this new context indicates that the associated requirements should be guaranteed by the MnS producer. When the context is set... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.8.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9 Use case #9: Intent handling capability configuration, registration and discovery
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.1 Description
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.1.1 Intent handling capability description
| In 3GPP TS 28.312 [1], the existing use case, requirements and solution (including IntentHandlingCapability <<dataType>>) for intent handling capability obtaining are defined, which allows the MnS consumer to query the intent handling capabilities for a specific intent handling function. The use case also describes tha... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.1.2 Intent handling capability registration and discovery
| In 3GPP TS 28.537 [6], the existing use case, requirements and solution (including MnSInfo IOC) for MnS discovery are defined, which allows MnS consumer to retrieve the list of MnS instances which can provide the intent driven management capability from MnS Registry. In this case, MnS consumer needs to send the query r... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.1.3 Intent handling capability configuration
| As 3GPP TS 28.312 [1] described, multiple intent handling functions maybe deployed to support different expectation objects or to support different areas of the same intent expectation object domain. Operator may need to configuration the intent handling capability for each intent handling function with different respo... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.2 Potential requirements
| REQ-IDMS_IHCO-CON-1: The intent driven MnS producer should have capabilities enabling an MnS consumer to obtain intent handling capabilities of each intent handling function, including supported contexts.
NOTE: Examples of contexts to be included as part of the intent handling capabilities are the ObjectContexts and t... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.3 Potential solution
| This solution proposes to reuse and enhance the existing IntentHandlingFunction defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Add following attributes for IntentHandlingCapability <<dataType>>:
- supportedObjectContextInfoList, it represents the list of specific ObjectContexts supported by the intent handling f... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.9.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.10 Use Case#10: Radio network delivering in transient overload scenario
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.10.1 Description
| This use case describes a scenario where a MnS consumer express intent containing an expectation for ensuring a radio network in transient overload scenarios (e.g., high-speed rail or subway systems) to a MnS producer. In transient overload scenarios, the high load caused by massive user access and bursty traffic typic... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.10.2 Potential requirements
| REQ-IDMS_RadioServiceIntent-CON-1: The intent driven MnS producer for radio network should have capabilities enabling the MnS consumer to express transient load requirements.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.10.3 Potential solution
| This solution proposes to reuse and enhance the existing RadioNetworkExpectation defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Add following attributes as the ExpectationTargets for the RadioNetworkExpectation to support transient overload requirements:
- PrbHighLoadRatio, it represents the load target for the ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.10.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11 Use case #11: Enhancing intent feasibility check capability
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.1 Description
| This use case describes proposed enhancements for feasibility check, enabling intent-driven MnS consumer to receive information regarding how to make an infeasible intent feasible together with feasibility check in case the intent is deemed as infeasible. This will support MnS consumers to understand the changes needed... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.2 Potential requirements
| REQ-Intent_FEAS1: The intent driven MnS producer should have the capability to enable the authorized MnS consumer to receiverecommended values for infeasible targets.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.3.1 Potential solution #1 for a new procedure of feasibility check with exploration
| This solution proposes to reuse the existing generic intent exploration report and intent feasibility check report defined in 3GPP TS 28.312 [1] and to enhance the Intent <<IOC>>.
In order to enable an MnS consumer to request a feasibility check with corresponding recommendations, a procedure is proposed with ensuring... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.3.2 Potential solution #2 Extend inFeasibleTarget with recommended values
| This solution proposes to reuse and enhance the existing IntentFeasibilityCheckReport<<dataType>>defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Extend the type for attribute "inFeasibleTargets" from "String" to "inFeasibleTargetInfo <<dataType>>", which includes following attributes:
- targetName, represents the... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.11.4 Evaluation of potential solutions
| Two potential solutions are identified in clause 4.11.3. Both potential solution #1 and potential solution #2 support the capability to allow MnS consumer to receive recommended values for infeasible targets in an infeasible intent.
The implementation of both potential solutions is not complex. Therefore, both potenti... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.12 Use case #12: Documentation for the overview of intent driven management functionalities
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.12.1 Description
| In 3GPP TS 28.312 [1], several intent management functionalities (including but not limited to Intent handling capability obtaining, intent exploration, intent feasibility check, intent report management) are introduced in different releases. However, the overview of intent driven management functionalities and corresp... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.12.2 Potential requirements
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.12.3 Potential solution
| It proposes to introduce a new concept section in clause 4 in 3GPP TS 28.312 [1] as showed below to illustrate the overview of intent driven management functionalities.
4.X Overview of intent driven management functionalities for different phases
4.X.1 Introduction
The intent management functionalities for different... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.12.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
4.13 Use case #13: Investigation on the intent lifecycle management state transition
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.1 Description
| 3GPP TS 28.312 [1] studies the state transitions during fulfilment phase. However, the intent Lifecycle management states that describes the pre-evaluation phase (i.e. intent feasibility check and intent exploration) and negotiation in intent fulfilment phase is missing. The main difference between the pre-evaluation p... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.2 Potential requirements
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.3.1 Potential solution #1
| It proposes to add intent lifecycle management state transition diagram and intent lifecycle management state transition table to indicate the state transitions. Figure 4.13.2.1 shows the intent lifecycle management state diagram, where the number in the figure identify the changes to the intent lifecycle management st... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.3.2 Potential solution #2
| It proposes to add a new intent handling state diagram based on figure 4.13.3.2-1. New FULFILLING and EXPLORING states are defined to represent the full lifecycle of the intent and Figure 4.13.3.2-1 shows the intent handling state diagram, where the numbers identify the state changes. The explanations for the state cha... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.13.4 Evaluation of potential solutions
| Two solutions have been proposed concerning the lifecycle management state transitions. The evaluation considers how well each solution aligns with the intent states already defined in 3GPP TS 28.312 [1], the clarity and completeness of the state transitions, and the implementation complexity. 3GPP TS 28.312 [1] alread... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.14 Use case #14: Intent expectation satisfied information
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.14.1 Description
| In 3GPP TS 28.312 [1], the existing intentReport allows the IDMS consumer to obtain the values of KPI as indicated by the corresponding expectation targets. However, this information may not accurately reflect the actual situation. For example, considering an intent that includes a radio network expectation with the ta... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.14.2 Potential requirements
| REQ-Intent_IESI-1: The intent driven MnS producer should have a capability providing information besides average value in the intent report.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.14.3 Potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.14.4 Evaluation of potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.15 Use case #15: Relation and Interaction with MnS producers for AI/ML Management
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.15.1 Description
| This use case describes a scenario where an intent driven MnS producer interacts and coordinates with MnS producers for AI/ML management which is specified in 3GPP TS 28.105 [10]. Such coordination can enable the intent-driven MnS producer to both leverage AI/ML for its own internal intent handling tasks, as well as fo... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.15.2 Potential requirements
| REQ-Intent_AIML-1: The intent driven MnS producer should have the capability to interact with MnS producers for ML model lifecycle management in both intent pre-evaluation phase and intent fulfilment phase.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.15.3 Potential solutions
| This potential solution considers enabling an intent-driven MnS producer to interact with MnS producers for ML model lifecycle management. The solution does not require updating the NRM or already specified interfaces, and it only necessitates of updating the 3GPP TS 28.312 [1] to describe that the intent driven MnS pr... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.15.4 Evaluation of potential solutions
| The potential solution proposed in clause 4.15.3.1 satisfies the requirement identified in clause 4.15.2. The solution does not require updates to the NRM and/or interfaces, only describing the possible interactions between intent-driven MnS producer and MnS producer for ML model lifecycle management in 3GPP TS 28.312 ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.16 Use case #16: Investigation on the applicability and potential impacts to support natural language intents translation
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.16.1 Description
| In TR 28.914 [9], clause 5.6 described the use case for investigating potential impacts to support natural language intents translation. It also states that there are some use cases where the use of natural language for intent expression would be preferred. For example, on the human-machine interface presenting and exp... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.17 Use case #17: Enhancement of core network and service delivering and assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.17.1 Description
| This use case proposes to add the scenarios on core network and service delivering and assurance to support the SLA of core network services. In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation for 5GC network is described in clause 5.1.8, enabling MnS consumers to express... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.17.2 Potential requirements
| REQ-IDMS_CNServiceIntent-1: The intent driven MnS producer for core network service should have capabilities enabling the MnS consumer to express service latency requirements.
REQ-IDMS_CNServiceIntent-2: The intent driven MnS producer for core network service should have capabilities enabling the MnS consumer to expre... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.17.3 Potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.17.4 Evaluation of potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.18 Use case #18: The relation and the interactions between intent handling function and NDTFunction
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.18.1 Description
| This use case proposes a scenario where intent-driven management services (IDMS) are enabled through the Network Digital Twin (NDT). A Network Digital Twin, as referenced in 3GPP TS 28.561 [12], is used as a replica of a mobile network, in order to learn how an actual mobile network would behave in certain scenarios, w... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.18.2 Potential requirements
| REQ-Intent_NDT-1: The intent driven MnS producer should have the capability to interact with NDTFunction to validate the feasibility of intents or explore the best values of intent targets in intent pre-evaluation phase.
REQ-Intent_NDT-2: The intent driven MnS producer should have the capability to allow MnS consumer ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.18.3 Potential solutions
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.18.4 Evaluation of potential solutions
| TBD
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.19 Use case #19: Enhancement of radio service scenarios for service protection
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.19.1 Description
| In 3GPP TS 28.312 [1], the existing use case and requirements for intent containing an expectation for delivering a radio service is described in clause 5.1.2. The RadioServiceExpectation is defined to represent MnS consumer's expectations for radio service delivering and assurance in the specified area. However, curre... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.