hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.3 SEALDD (service enabler architecture layer) server/client
| SEALDD server provides application layer data(content) storage and forwarding services utilizing 3GPP network capabilities. By caching content closer to end users and co-operating with 3GPP network for improving transmission performance, it will reduce latency and improve user experience of applications.
SEALDD client... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.4 NSCE (Network Slice Capability Exposure) server/client
| NSCE server provides the value-added services by utilizing slice related capabilities of 3GPP core network and OAM. It enables third party’s application (application server or application client) to request 3GPP system to provide slice services to meet with the third party’s requirement in an easy-to-use way.
NOTE: Th... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.5 LM (location management) server/client
| LM server provides the value-added services by utilizing UE position related capabilities of 3GPP core network by combining the information from CN and location client (e., g if the CN cannot retrieve non-3GPP location information from UE modem, or UE using non-3GPP connection). It enables third party’s application (ap... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.6 AIMLE (AIML enabler) server/client
| Editor's Note: This clause will provide introduction of AIMLE server and client.
|
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.7 Spatial Anchor server/client
| The entities offering the spatial anchor services are Spatial Anchor server and Spatial Anchor client. These entities provides the capabilities to efficiently manage the spatial anchors belonging to the vertical application layer (VAL) entities that are offering metaverse services (e.g. VAL Server , VAL Client). Functi... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.8 Spatial Map server/client
| The Spatial map service offers the capabilities to the vertical application layer entities (VAL server, VAL client) for managing the spatial maps. The main functional entities are Spatial Map server and client that provides client and server-side functionalities respectively for managing spatial map for the vertical ap... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 4.2.9 Digital Assets server/client
| The Digital assets service provides functionalities to manage the digital assets related to metaverse services particularly Digital Avatars. The core entities of the Digital Service enabler are Digital Asset server and Digital Asset client. The digital asset service supports management of digital assets profile, digita... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5 The use cases and advantages to applications
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.1 Summary of SEAL services
| Editor's Note: Brief summary of the value of each the SEAL services.
This clause is to address the overall summary of the values and beneficial use case(s) of each SEAL service.
The supporting of the following are the key services that make SEAL layer distinct with other non-3GPP basis developer API Platform:
- NSCE... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.2 Use cases and advantages for SEAL Service provided by SEALDD
| Editor's Note: Details about the value of each SEAL services and how it brings advantages to applications
|
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.2.1 Use case
| CDN is known as a content distribution network. CDN is a global network server system that works together to provide super-fast delivery of Internet content such as website webpages, HTML pages, JavaScript files, stylesheets, images, and videos. When people try to access a website if using a CDN, then visitors will see... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.2.2 Advantages and values of SEALDD Services
| As it shows in figure 5.2.2-1, the application data information will be provided by SEAL DD in the way 3GPP system can read. So that 3GPP network layer can apply some enhancement transmission on SEALDD data.
Figure 5.2.2-1: SEALDD data transmission using differentiating-processing capability by 3GPP network
In addi... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.3 Use cases and advantages for SEAL Services provided by NRM
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.3.1 Use case
| Below list specifies the needs of the various applications utilizing the 3GPP network capabilities:
- URLLC as mentioned in clause 7.2 of 3GPP TS 22.261 [15].
- High data rate and low latency as mentioned in clause 7.6 of 3GPP TS 22.261 [15].
- Low latency e.g IMS/MCX Voice call/video call.
- Background data transf... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.4 Use cases and advantages for SEAL Services provided by NSCE
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.4.1 Use case
| Some of the vertical industry players could rent dedicated network slice(s) for their vertical applications. They can self-manage the network slice related operation themselves, including determining the services required, network slice SLA, ordering a network slice product with the determined SLA from MNO, triggering ... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.4.2 Advantages and values of NSCE
| To enable the self-management of network slice(s) by vertical industry players, NSCE needs to utilize the network slice related APIs exposed by OAM, core network and UE client to offer the NSCE services as illustrated in figure 5.4.2-1. When the NSCE is deployed within operator's trusted domain, it can access the 5GC d... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.5 Use cases and advantages for SEAL Services provided by metaverse service
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.5.1 Use case
| Spatial anchor, Spatial mapping, and digital asset are typical Metaverse Services for support Metaverse application.
A spatial anchor is an association between space and service information. The Spatial anchors SEAL service offers spatial anchors related capabilities (i.e., CRUDS) to one or more vertical applications.... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.5.2 Advantages and values of spatial anchor Services
| A spatial anchor is an association between space and service information. The Spatial anchors SEAL service offers spatial anchors related capabilities (i.e., CRUDS) to one or more vertical applications. Spatial anchors enable the authorized users to place digital information at specific locations.
Spatial anchors can ... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.5.3 Advantages and values of Digital asset Service
| The SEAL digital assets service enables management and usage of digital assets in a secure and controllable way. Examples of digital assets include digital representation (avatar), software licenses, gift certificates, tokens and files (e.g., music files) that have been purchased.
Digital asset service can be used in ... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 5.5.4 Advantages and values of Spatial Map Service
| For spatial map service, sensing data gathered transparently is processed in order to identify the static and transient forms.
Spatial map service can be used in many ways (as described in clause 5.5 of 3GPP TR 22.856 [24]):
- A government conducting a digital city project can build a 3D spatial map of outdoor envir... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 6 Deployment of SEAL entities and business relationship among stakeholders
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 6.1 Ecosystem stakeholders
|
Figure 6.1-1: Ecosystem stakeholders for the exposure of MNO’s service
Figure 6.1-1 shows the Ecosystem stakeholders for the exposure of MNO’s service. The following ecosystem stakeholders are covered:
- The stakeholders who develop different parts of MNO system, including Network vendors for network equipment, ... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 6.2 Deployment alternatives
| |
f58e9a2477fb0608752170605ec26488 | 23.949 | 6.2.1 Common exposure entities
| In the deployment alternative as figure 6.2.1-1, it assumes that one MNO would like to deploy the common exposure framework entities to expose all the APIs from difference domain to third party.
Within each domain (e.g. OAM and CN), domain API gateway(NEF or EGMF) for some reasons (e.g., inter-domain security isolat... |
f58e9a2477fb0608752170605ec26488 | 23.949 | 6.2.2 Separated exposure entities for different domain API
|
Figure 6.2.2-1: Separated exposure framework among different domains
In the deployment alternative as figure 6.2.1-1, it assumes that one MNO would like to deploy the separated exposure entitles to expose the APIs from difference domain to third party.
The O&M and CN domain API are managed and discovered by Comm... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 1 Scope
| The present document studies a number of potential enhancements to the intent driven management services for 5G Advanced network. These include the definition of new targets and contexts for existing scenarios, negotiation enhancements, and utility function enhancements.
New functionality includes the introduction of ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 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.
-... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 3 Definitions of terms, symbols and abbreviations
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [11] 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 [11].
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 3.2 Symbols
| Void.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [11] 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 [11].
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4 Use cases and potential solutions for new areas
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.1 Use case #1: Enhancement of radio service delivering and assurance scenarios
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.1.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.2 Use case #2: Enhancement of radio network performance assurance scenarios
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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.
|
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.2.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.3 Use case #3: Assisting and reporting intent decomposition across intent handling functions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.3.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.4 Use case #4: Intent traceability
| |
455bf99ab6b77dabddd5d86956ce31ea | 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 ... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.4.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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 ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.4.3.2 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.4.4 Evaluation of potential solutions
| Potential solution #1 is feasible and addresses requirements REQ-Intent_Trace-1, REQ-Intent_Trace-2, and REQ-Intent_Trace-3. It is recommended to proceed to normative phase.
Potential solution #2 is feasible and addresses requirement REQ-Intent_Trace-4. It is recommended to proceed to normative phase.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.5 Use case #5: Invariant Guidance in Intent Contexts
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.5.1 Description
| 3GPP TS 28.312 [1] describes a scenario where for an instantiated intent, the intent handling function may need to decompose the intent into multiple derivative intents, each to be fulfilled by a separate other intent handling function. There may be contexts in the intent which the MnS consumer desires that the other i... |
455bf99ab6b77dabddd5d86956ce31ea | 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 handling functions without modification.
|
455bf99ab6b77dabddd5d86956ce31ea | 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 handling functions in ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.5.4 Evaluation of potential solutions
| Only one potential solution provided in clause 4.5.3 is identified. This potential solution proposes enhancing the context datatype to add a Boolean indication whether the context is preferred to be invariant. The implementation of this potential solution is not complex as it proposes enhancements to an existing datat... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.6 Use case #6: Intent Interpretation Assistance Information
| |
455bf99ab6b77dabddd5d86956ce31ea | 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 fulfil intent requirements that ... |
455bf99ab6b77dabddd5d86956ce31ea | 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.
|
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.6.4 Evaluation of potential solutions
| Only one potential solution provided in clause 4.6.3 is identified. This potential solution proposes enhancing the existing intent IOC by adding an attribute that captures the previous MnS-producer to MnS consumer interactions. The implementation of this potential solution is not complex as it proposes enhancements to ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.7 Use case #7: Enhancement of intent exploration
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.7.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.8 Use case #8: Support to express guarantee requirements in an intent
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.8.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.8.3.2 Potential solution #2
| Enhancement Aspect 1:
A new attribute whose type is Context <<datatype>> 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 at the ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.8.4 Evaluation of potential solutions
| For UC#8, two potential solutions have been identified. Both the present solutions are feasible, but potential solution #2 can cover potential solution #1 with some future enhancements.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.9 Use case #9: Intent handling capability configuration, registration and discovery
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.9.1 Description
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.9.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.10 Use Case#10: Radio network delivering in transient overload scenario
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.10.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 performance assurance expectations for the scenario with specific load condition (e.g. transient overload scenarios).
|
455bf99ab6b77dabddd5d86956ce31ea | 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 ExpectationContexts for the RadioNetworkExpectation to support transient overload scenarios:
- PrbHighLoadRatioContext, it represents the load condition ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.10.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.11 Use case #11: Enhancing intent feasibility check capability
| |
455bf99ab6b77dabddd5d86956ce31ea | 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 when the intent is deemed infeasible. This will support MnS consumers to understand the changes needed to make an intent feasible.
In 3GPP ... |
455bf99ab6b77dabddd5d86956ce31ea | 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 receive recommended values for infeasible targets.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.11.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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 allowed values for intentMgmtPurpose attribute of Intent <<IOC>> which is specified in 3GPP TS 28.312 [1], clause 6.2.1.4, with the value of "FEASIBILITYCHECK_... |
455bf99ab6b77dabddd5d86956ce31ea | 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 potential solution#2 is a simplified solution (All necessary inf... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.12 Use case #12: Documentation for the overview of intent driven management functionalities
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.