hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.12.2 Potential requirements
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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
|
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.13.2 Potential requirements
| None
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.13.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 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.3.1-1 shows the intent lifecycle management state diagram, where the number in the figure identify the changes to the intent lifecycle management ... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.14 Use case #14: Intent expectation satisfied information
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.14.3 Potential solutions
| This solution proposes to enhance the expectation fulfilment results included in intent fulfilment report defined in clause 6.2.1.3.6, and intentReportControl defined in clause 6.2.1.3.16.
Enhancement Aspect #1: In order to enable the MnS consumer to receive more fulfilment information besides the binary fulfilment re... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.14.4 Evaluation of potential solutions
| Enhancement Aspect #1, i.e., adding one new attribute to cover satisfied information in ExpectationFulfilmentResult is feasible and independently to address the requirement REQ-Intent_IESI-1It is recommended to proceed to normative phase.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.15 Use case #15: Relation and Interaction with MnS producers for AI/ML Management and Closed-control-loops.
| |
455bf99ab6b77dabddd5d86956ce31ea | 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] or for closed control loops. Such coordination can enable the intent-driven MnS producer to both leverage AI/ML for its own internal intent h... |
455bf99ab6b77dabddd5d86956ce31ea | 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 and CCLs in both intent pre-evaluation phase and intent fulfilment phase.
|
455bf99ab6b77dabddd5d86956ce31ea | 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 and CCLs. The solution requires:
- updating the 3GPP TS 28.312 [1] to describe that the intent driven MnS producer, if necessary, can interact with MnS producers for ML model lifecy... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.15.4 Evaluation of potential solutions
| The potential solution proposed in clause 4.15.3 satisfies the requirement identified in clause 4.15.2. The solution requires updates describing the possible interactions between intent-driven MnS producer and MnS producer for ML model lifecycle management and CCLs in 3GPP TS 28.312 [1], ]. It also proposes to add in i... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.16 Use case #16: Investigation on the applicability and potential impacts to support natural language intents translation
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.17 Use case #17: Enhancement of core network and service delivering and assurance scenarios
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.17.3 Potential solutions
| This solution proposes to reuse and enhance the existing 5GCNetworkExpectation defined in 3GPP TS 28.312 [1].
Enhancement Aspect1: Add following attributes as the ExpectationTargets for the 5GCNetworkExpectation to enable the MnS consumer to express service latency requirements.
- LatencyTarget, it represents the lat... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.17.4 Evaluation of potential solutions
| Only one potential solution has been identified, which is feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.18 Use case #18: The relation and the interactions between intent handling function and NDTFunction
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 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 ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.18.3 Potential solutions
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.18.3.1 Potential solution #1
| This potential solution considers enabling an intent-driven MnS producer to interact with NDTFunction MnS producers. The solution proposes to reuse the NRM and interfaces defined in 3GPP TS 28.312 [1], and update the use cases to describe that the intent driven MnS producer, if necessary, can interact with NDTFunction ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.18.3.2 Potential solution #2
| This potential solution considers enabling an intent-driven MnS producer to interact with NDTFunction MnS producers. 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 producer, if necessary, ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.18.4 Evaluation of potential solutions
| Two potential solutions provided in clause 4.18.3 are identified, both feasible.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.19 Use case #19: Enhancement of radio service scenarios for service protection
| |
455bf99ab6b77dabddd5d86956ce31ea | 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... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.19.2 Potential requirements
| No potential requirements were identified in this study.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.19.3 Potential solutions
| No potential solutions were identified in this study.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.19.4 Evaluation of potential solutions
| Not applicable.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.20 Use case #20: New deployment scenario for Intent Handling Function at ManagedElement
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.20.1 Description
| This task investigates the need for a new deployment scenario for IHF at ManagedElement layer.
Discussion to date has not identified the need for such a scenario in 5GA. As such, the topic concludes with no potential requirements nor potential solutions proposed in this study.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.20.2 Potential requirements
| No requirement identified in the present document.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.20.3 Potential solutions
| No solution identified in the present document.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 4.20.4 Evaluation of potential solutions
| Not applicable.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5 Conclusions and Recommendations
| |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.1 Use case #1: Enhancement of radio service delivering and assurance scenarios
| The use case of enhancement of radio service delivering and assurance scenarios is introduced in clause 4.1 and following management capabilities are identified:
- MnS consumer expresses the radio service delivering and assurance intent expectation with service reliability information.
- MnS consumer expresses the ra... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.2 Use case #2: Enhancement of radio network performance assurance scenarios
| The use case of enhancement of radio network performance assurance scenarios is introduced in clause 4.2 and following management capabilities are identified:
- MnS consumer expresses radio network performance assurance expectation for a specific RAN feature.
It is recommended to enhance the RadiNetworkExpectation an... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.3 Use case #3: Assisting and reporting intent decomposition across intent handling functions
| The use case description, requirements and a potential solution for assisting and reporting intent decomposition across intent handling functions are described in clause 4.3. This use case enables an MnS consumer to specify the intent handling functions that are not recommended for intent decomposition as an expectatio... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.4 Use case #4: Intent traceability
| The use case description, requirements and potential solutions for Intent traceability are described in clause 4.4.
The use case proposes updates to support the control and reporting for intent traceability.
Both use cases defined in clause 4.4.3 are proposed to proceed to normative phase.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.5 Use case #5: Invariant Guidance in Intent Contexts
| The use case description, requirements and a potential solution for Invariant Guidance in Intent Contexts are described in clause 4.5. This use case enables an MnS consumer to indicate context which the MnS consumer desires to be invariant when decomposing the intent.
The potential solution described in clause 4.5.3, ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.6 Use case #6: Intent Interpretation Assistance Information
| The use case description, requirements and a potential solution for Intent Interpretation Assistance Information are described in clause 4.6. This use case enables an MnS consumer to provide information containing prior interactions that can then be used by the intent handler to support the interpretation of the intent... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.7 Use case #7: Enhancement of intent exploration
| The use case of enhancement of intent exploration is introduced in clause 4.7 and following management capabilities are identified:
- The capability enabling the MnS consumer to request to periodically obtain the exploration report.
- The capability enabling the MnS consumer to obtain the best target values for indiv... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.8 Use case #8: Support to express guarantee requirements in an intent
| The use case of Support to express guarantee requirements in an intent is described in clause 4.8 and following management capabilities are identified:
- The capability enabling an MnS consumer to express an intent to be guaranteed and which expectations requirement in an intent should be guaranteed.
- The capability... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.9 Use case #9: Intent handling capability configuration, registration and discovery
| The use case of Intent handling capability configuration, registration and discovery is described in clause 4.11 and following management capabilities are identified:
- The capability enabling an MnS consumer to obtain intent handling capabilities of each intent handling function, including supported contexts.
- The ... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.10 Use Case#10: Radio network delivering in transient overload scenario
| The use case of radio network delivering in transient overload scenario in clause 4.10 and following management capabilities are identified:
- The capability enabling the MnS consumer to express performance assurance requirement for the scenario with specific load condition (e.g. transient overload scenarios)
It is r... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.11 Use case #11: Enhancing intent feasibility check capability
| The use case of enhancement of intent feasibility check capability is introduced in clause 4.11 and following management capabilities are identified:
- The capability enabling the MnS consumer to receive recommended values for infeasible targets.
The potential solution described in clause 4.11.3.1 proposes a new allo... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.12 Use case #12: Documentation for the overview of intent driven management functionalities
| The overview of intent driven management functionalities and corresponding usage for different phases is introduced in 4.12.3, including intent investigation and pre-evaluation phase and intent fulfilment.
It is recommended to add a new concept section in clause 4 in 3GPP TS 28.312 [1] to illustrate the overview of in... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.13 Use case #13: Improve intent life cycle documentation
| The evaluation shows that potential solution #2 (clause 4.13.3.2) aligns most closely with the intent state definitions and behaviours described in 3GPP TS 28.312 [1]. States like FULFILLED, DEGRADED and SUSPENDED are already defined. By introducing only two new transient states - EXPLORING for feasibility check, explo... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.14 Use case #14: Intent expectation satisfied information
| The description, requirements and potential solutions for intent expectation satisfied information are described in clause 4.14. This use case proposes to update intent report to support satisfied information. It is recommended to enhance the ExpectationFulfilmentResult defined in 3GPP TS 28.312 [1] to support above ma... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.15 Use case #15: Relation and Interaction with MnS producers for AI/ML Management
| The use case description, requirements and a potential solution for relation and interaction with MnS producers for AI/ML Management and Closed-control-loops are described in clause 4.15. This use case clarifies the relation and interaction of intent-driven MnS producers with MnS producers for ML model lifecycle manage... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.16 Use case #16: Investigation on the applicability and potential impacts to support natural language intents translation
| Regarding the Deployment scnenario#1(Intent Interpreter as a separate function outside the intent handling function), the Intent Interpreter is MnS consumer's internal implementation and the existing intent driven management service can be used to satisfy the interaction between intent handling function and MnS consume... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.17 Use case #17: Enhancement of core network and service delivering and assurance scenarios
| The use case of enhancement of core network service delivering and assurance scenarios is introduced in clause 4.17 and following management capabilities are identified:
- MnS consumer expresses core network SLA-level latency assurance expectation for specific service flows.
- MnS consumer expresses the preference on... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.18 Use case #18: The relation and the interactions between intent handling function and NDTFunction
| The use case description, requirements and a potential solution for the relation and the interactions between intent handling function and NDTFunction is introduced in clause 4.18. This use case clarifies the relation and interaction of intent-driven MnS producers with NDTFunction MnS producers in the intent pre-evalua... |
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.19 Use case #19: Enhancement of radio service scenarios for service protection
| See clause 4.19.
|
455bf99ab6b77dabddd5d86956ce31ea | 28.881 | 5.20 Use case #20: New deployment scenario for Intent Handling Function at ManagedElement
| See clause 4.20.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
S5-253452
Initial version.
0.0.0
2025-09
SA5#162
S5-254121
Draft TR v0.1.0
S5-254032 Add structure proposal
S5-254033 Add new issue for enhancement of radi... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 1 Scope
| This Technical Report (TR) explains how application (App) developers can leverage the services from enablement frameworks, namely Common API Framework (CAPIF), Edge Application Enablement (EDGEAPP), and the Service Enabler Architecture Layer (SEAL) to create their software.
To facilitate understanding, this study pre... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 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.
-... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 3 Definitions of terms, symbols and abbreviations
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 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].
Application Client (AC): An application component, typically hosted on User Equipment (UE... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 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].
AC Application Client
AEF API Exposing Function
AMF API Managi... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4 Overview of Frameworks
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.1 Introduction
| Emerging 5G vertical services have requirements that can include low-latency, high-bandwidth, and context-aware processing at the network edge. To address these needs, 3GPP has developed several application enablement frameworks, each targeting a specific aspect of the application layer architecture:
- Common API Fram... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.2 Common API Framework (CAPIF)
| The Common API Framework (CAPIF) is a 3GPP framework that provides common functions for secure API exposure, discovery, onboarding, and authorization across multiple domains, 3GPP TS 23.222 [2]. Its primary role is to harmonize how service APIs are published and consumed, offering a single point of entry for applicatio... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.3 Edge Application Enablement (EDGEAPP)
| Edge Application Enablement (EDGEAPP) has been specified by 3GPP to enable applications to be deployed and managed at the edge of the network (closer to end users) to achieve ultra-low latency and high bandwidth efficiency, 3GPP TS 23.558 [4]. By offloading computation and services from centralized cloud to edge nodes ... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.4 Service Enabler Architecture Layer (SEAL)
| The Service Enabler Architecture Layer (SEAL), specified in 3GPP TS 23.434 [6], defines a common service framework designed to support vertical and mission-critical applications operating over 3GPP networks. SEAL provides a standardized set of service capabilitiesenablers, such as group management, configuration manage... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 4.5 Inter-framework Relationships Overview
| The integration of CAPIF, EDGEAPP, and SEAL within the 3GPP system enables a unified service enablement environment for vertical applications. Each framework addresses a specific functional domain (API exposure, edge application management, and service enabler support) while remaining interoperable under a consistent t... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5 Use Cases
| Each use case is expected to include end-to-end service flow and infrastructure details (e.g., number and placement of edge nodes, optional use of SEAL services for a single PLMN domain)
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1 Crowd Counting Video Analytics
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.1 Introduction
| This section describes a Crowd Counting Video Analytics use case. The use case has been selected to illustrate how application developers can leverage the EDGEAPP framework to discover and utilize Edge infrastructure that supports low-latency video analytics. Specifically, it demonstrates the benefits of deploying comp... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.2 Use case Description
| “Acme” company is developing a crowd counting video analytics application that leverages edge computing to process video in real time. The application consists of an Application Client (AC) running on a User Equipment (UE), which captures live video and streams it for analytics, and a video analytics application runnin... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.3 Use case Realisation over Application Enablement Frameworks
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.3.1 General
| From the developer’s point of view, it is essential to understand which entity handles which tasks in the EDGEAPP system. The AC is deliberately kept simple: it talks only to the EEC, and all network complexity is abstracted away. When the AC is designed, only the calls to the EEC’s APIs need to be implemented to lever... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.3.2 AC Discovering the Serving EES
| The EEC running in the UE, needs to discover its EES. The EEC can learn which EES to register with through multiple mechanisms:
- Pre-provisioned in the UE/application profile.
- DNS-based discovery, using operator domain naming conventions.
- Network-provisioned, delivered at onboarding or during mobile attachment.... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.3.3 CAPIF roles of EDGEAPP entities
| While AC does not interact directly with CCF, it is important to understand the roles that each EDGEAPP entity plays in relation to CAPIF to consume APIs. In this use case, the EEC behaves as a CAPIF API Invoker. The EEC needs to discover EAS APIs and obtain OAuth tokens to consume them. In particular, the EEC queries ... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4 Use case Flows
| Editor's note: Appropriate “Focus for Application developer” highlighting, if any, in the figures in this clause is FFS.
|
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.1 General
| From a developer’s perspective, the use case flows describe how an Application Client (AC) interacts with its local Edge Enabler Client (EEC) to request services, discover the right Edge Application Server (EAS), and sustain service continuity when the UE moves between edge zones. The AC is abstracted from all network-... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.2 Step 1: AC Registration & Provisioning
| The first step is for the AC to register with the EEC so that it can start consuming services. The developer must ensure the AC calls the Eeec_ACRegistration API. If the EEC already aware of its serving EES (through provisioning, DNS discovery, or cached state), it registers directly as depicted in Figure 5.1.4.2-1. Ot... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.3 Step 2: EAS Discovery
| Once registered, the AC needs to know which EAS can provide the video analytics service. The developer calls Eeec_EASDiscovery, and the EEC queries the EES to find suitable EAS instances in the serving zone. The response includes candidate EAS endpoints, which the EEC returns to the AC via callback. The flow is shown i... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.4 Step 3: CAPIF API Discovery
| The AC now requires the actual API contract to interact with the selected EAS. The developer does not handle CAPIF directly; instead, the EEC calls CAPIF_Discover_Service_API towards the CCF. CAPIF responds with the API base URI, supported operations, and authorization details. The EEC then informs the AC via a respons... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.5 Step 4: Service Invocation
| With the endpoint and API details, the AC begins sending its video stream directly to the EAS. From the developer’s perspective, this involves implementing the client logic that captures frames and invokes the Video Analytics service API as specified by CAPIF. The EAS processes the video in real time and returns crowd ... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.6 Step 5: Mobility with Application Context Relocation
| The EEC does not detect mobility itself. Mobility/zone-change is determined in the network and conveyed to the EES (e.g., via operator control-plane and exposure functions). The EES then informs the EEC over EDGE-1 using the service continuity/mobility procedures. The EEC translates that into the local EDGE-5 notificat... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.1.4.7 Step 6: API Update & Resume Streaming
| After relocation, the EEC refreshes API discovery with CAPIF to retrieve the new endpoint for EAS 2. The AC receives this updated endpoint via notification callback. The developer must handle this event by re-establishing the video stream to EAS 2 using the new service API. From the AC’s perspective, this looks like a ... |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.2.1 Introduction
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.2.2 Use case Description
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.2.3 Use case Realisation over Application Enablement Frameworks
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 5.2.4 Use case Flows
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6 Developer Guidelines
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.1 Introduction
| |
6c05d55bd5d8f1ec8fa6cbf3d03ca420 | 23.947 | 6.2 Cross-Framework Integration
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.