hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.20 Use case #20: New deployment scenario for Intent Handling Function at ManagedElement
| |
bbd9841f4f65b6569258419594b8dc01 | 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.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.20.2 Potential requirements
| FFS
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.20.3 Potential solutions
| FFS
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 4.20.4 Evaluation of potential solutions
| Not applicable.
|
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5 Conclusions and Recommendations
| |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.4 Use case #4: Intent traceability
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.5 Use case #5: Invariant Guidance in Intent Contexts
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.6 Use case #6: Intent Interpretation Assistance Information
| |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.8 Use case #8: Support to express guarantee requirements in an intent
| |
bbd9841f4f65b6569258419594b8dc01 | 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 ... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.10 Use Case#10: Radio network delivering in transient overload scenario
| |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 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 and ne... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.14 Use case #14: Intent expectation satisfied information
| |
bbd9841f4f65b6569258419594b8dc01 | 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 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 management in both intent pre-e... |
bbd9841f4f65b6569258419594b8dc01 | 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... |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.17 Use case #17: Enhancement of core network and service delivering and assurance scenarios
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.18 Use case #18: The relation and the interactions between intent handling function and NDTFunction
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.19 Use case #19: Enhancement of radio service scenarios for service protection
| |
bbd9841f4f65b6569258419594b8dc01 | 28.881 | 5.20 Use case #20: New deployment scenario for Intent Handling Function at ManagedElement
| Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA5#162
Initial version.
0.0.0
2025-09
SA5#162
S5-254121
draftTR
Draft TR v0.1.0
S5-254032 Add structure proposal
S5-254033 Add new issue for enhancement of radio service de... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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.
-... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 3 Definitions of terms, symbols and abbreviations
| |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 4 Overview of Frameworks
| |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 4.2 Common API Framework (CAPIF)
| This clause will provide the CAPIF role in secure API exposure, onboarding, and discovery.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 ho... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 4.3 Edge Application Enablement (EDGEAPP)
| This clause will provide the EDGEAPP role in application lifecycle and orchestration at the edge.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,... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 4.4 Service Enabler Architecture Layer (SEAL)
| This clause will provide the SEAL role in the provision of reusable service enablers for vertical applications.
|
2b5c82519cec48b309e29881d9c51555 | 23.947 | 4.4 Inter-framework Relationships Overview
| This clause will describe the role of each framework can provide in an overall framework.
|
2b5c82519cec48b309e29881d9c51555 | 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)
|
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.1 Crowd Counting Video Analytics
| |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.1.3 Use case Realisation over Application Enablement Frameworks
| |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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 ... |
2b5c82519cec48b309e29881d9c51555 | 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.
|
2b5c82519cec48b309e29881d9c51555 | 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-... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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 ... |
2b5c82519cec48b309e29881d9c51555 | 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... |
2b5c82519cec48b309e29881d9c51555 | 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 ... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.2.1 Introduction
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.2.2 Use case Description
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.2.3 Use case Realisation over Application Enablement Frameworks
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.2.4 Use case Flows
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 6 Developer Guidelines
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 6.1 Introduction
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 6.2 Cross-Framework Integration
| CAPIF roles definition for EDGEAPP and SEAL entities
|
2b5c82519cec48b309e29881d9c51555 | 23.947 | 6.3 Example Application Flows
| The following flows will be considered “CAPIF + EDGEAPP”, “CAPIF + SEAL” and “CAPIF + EDGEAPP + SEAL”
|
2b5c82519cec48b309e29881d9c51555 | 23.947 | 6.4 Multi-CAPIF Considerations
| Relevant information to consider when several CAPIF are deployed
|
2b5c82519cec48b309e29881d9c51555 | 23.947 | 7 Security Considerations
| Aspects such as identity management across frameworks, secure onboarding and trust models, framework-specific and integrated authorization will be considered
Annex A:
Infrastructure Topology Diagrams Examples
Will show CAPIF+ EDGEAPP, CAPIF+SEAL and CAPIF+EDGEAPP+SEAL
A.1 CAPIF plus +EDGEAPP Topology
Editor’s No... |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.1 Use case XCrowd Counting Video Analytics
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.1.32 Use case Realisation over Application EnablementSA6 Frameworks
| |
2b5c82519cec48b309e29881d9c51555 | 23.947 | 5.1.43 Use case Flows
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 1 Scope
| The present document …
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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.
-... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 3 Definitions of terms, symbols and abbreviations
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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].
Management Service (MnS): defined in TS 28.533 [2].
External MnS consumer: defined in TS 28.533 [2... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 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].
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4 Concepts and background
| Editor’s note: This clause provides a description of concepts and background.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.1 Overview
| The study builds upon the management services exposure scenarios defined in clause 5.6 of TS 28.533 [2], which serves as the primary reference for exposing management services to external consumers. In addition, the Management Exposure framework described in TS 28.579 [3] introduces an optional approach based on CAPIF.... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2 Authorization of external MnS consumers using CAPIF
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2.1 Introduction
| As noted in clause 5.6 of TS 28.533 [2], an operator can decide to expose 3GPP management system capabilities to external MnS consumers using existing MnS interfaces (e.g. external MnS consumer Y1), or using CAPIF (e.g. external MnS consumer Y2).
When CAPIF is not used, an external MnS consumer gets access to MnS API... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 4.2.2 Authorization in CAPIF Framework
| 3GPP TS 33.122 [7] specifies security aspects of the CAPIF Framework.
CAPIF has defined three possible formats for access token’s scope. These formats are specified in the “scope” attribute in AccessTokenReq (see clause 8.5.4.2.6 of TS 29.222 [8]) and AccessTokenRsp (see clause 8.5.4.2.7 of TS 29.222 [8]).
4.3 Acces... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5 Use cases and potential solutions
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1 Use case #1: Authorization of the service API invocation request from the external MnS consumer using CAPIF
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.1 Description
| Editor's note: This clause provides a description of use case.
For an external MnS consumer to be able to invoke service APIs at the MSED AEF, first they send the service API authorization request (over the CAPIF-1e interfaced) to the CCF to request for the authorization to access one or more service APIs. If the serv... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
PREQ-FS_EnExpo-AuthCCF-01: The exposure of management services using CAPIF shall provide the capability enabling the authorization of the service API invocation request(s) at the MSED AEF.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.1.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2 Use case #2: Access control on notifications
| |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.1 Description
| Editor's note: This clause provides a description of use case.
When an MnS consumer subscribes to receive notifications using the NtfSubscriptionControl IOC (see clause 4.3), the 3GPP management system needs to be able to determine whether a given MnS consumer is authorized to receive notifications on a set of managed... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
PREQ-FS_EnExpo-Ntf-01: The 3GPP Management System should provide the capability to configure, per role (as defined in clause 7.3.2 of TS 28.319[4]), the set of notification types that the MnS consumer is authorized to receive.
... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.2.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
5.X Use case #3: Transformation of MnS information for external MnS consumers
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.1 Description
| Editor's note: This clause provides a description of use case.
When an external MnS consumer which is located outside the PLMN trust domain requests access to network information, 3GPP management system needs to ensure that internal 5G information is not revealed. For instance, the relevant "S-NSSAI" need to be transf... |
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.2 Potential requirements
| Editor's note: This clause provides potential requirements for the corresponding use case.
REQ-EnExpo-Trans-01: The 3GPP management system should support a transformation to replace S‑NSSAI with AF‑Service‑Identifier before exposure to external MnS consumers.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.3 Potential solutions
| Editor's note: This clause provides one or more solutions. Further (sub-)clause(s) may be added to capture details.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 5.3.4 Evaluation of potential solutions
| Editor's note: This clause provides evaluation of potential solutions.
|
109aef2cbd7243013266d216a69f4ffd | 28.888 | 6 Conclusions and recommendations
| 6.X Use case #<X>: <use case title>
Editor's note: This clause provides conclusions and recommendations for the corresponding use case.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
202... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 1 Scope
| The present document studies the charging aspects of 6G system. This includes new charging business models and potential charging metrics, 6G charging architecture and charging mechanism, and the charging aspects of 6G services and frameworks.
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 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.
-... |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 3 Definitions of terms, symbols and abbreviations
| |
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 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.
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
96f8bdc68da73f6fda85234415019d6f | 32.801-02 | 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].
ABMF Account Balance Management Function
CDR Charging Data Record
CGF Ch... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.