hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28.2.1 PS Data Off activation with existing IMS Session with DCs | Figure 6.28.2.1-1 provides the procedures of PS Data Off activation when an IMS Session with DCs has been established for the UE.
Figure 6.28.2.1-1: Activation of PS Data Off when IMS Session with DCs has been established
0. An IMS session with data channels has been established between UE-1 and UE-2.
1. When the user ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28.2.2 PS Data Off activation without existing IMS session with DCs | Figure 6.28.2.2-1 provides the procedure of active PS Data Off when the bootstrap DC and application DC is not established.
Figure 6.28.2.2-1: Active PS Data Off when the bootstrap DC and application DC is not established
1. When the user of UE-1 active the PS Data Off, the UE-1 sends the (re)Register message contains ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.28.3 Impacts on services, entities and interfaces | DCSF:
- Receive notification from IMS AS for the indication of PS Data Off status.
- Determine the UE is in roaming state by the received roaming indication
- Choose specific DC application list for PS Data Off which contains only allowed applications.
- Trigger the release of application DCs that not associated with t... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.29 Solution #29: Handling of PS data off exemption for services over IMS DC | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.29.1 Description | This clause proposes a solution for handling PS data off exemption for services over IMS DC.
This proposal is to enhance the existing PS data off exemption procedure defined in Annex X of TS 23.228 [5]. There is a list of services which have been defined for PS data off exemption and IMS data channel can be provisioned... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.29.2 Procedures | The procedure for UE and network enforcement is based upon the existing Annex X, clauses X.2 and X.3 TS 23.228 [5] with following enhancement:
1. If the services over IMS DC is not in the 3GPP PS Data Off Exempt, UE shall immediately stop sending any media packets for IMS DC services and shall terminate application DC ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.29.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to existing entities and interfaces:
UE:
- As part of UE enforcement, instead of releasing the whole IMS Session, UE shall send Re-INVITE to keep audio and video media when ISM DC is not marked for PS data off exemption. If the services over IMS DC is not in the 3GPP PS Data... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.30 Solution #30: DC interworking with DC service data provision to MTSI UE | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.30.1 Description | In some DC application service, it can serve the MTSI UE which only support conventional media (such as video, audio, text) with the same or similar user experience comparing to DC MTSI UE. For example, when a conference call with screen sharing, some users who join via data channel can control the screen or make some ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.30.2 Procedures | The procedure for provision of DC service data for MTSI UE to access to the DC AS is described in Figure 6.30.2.1-1.
Figure 6.30.2.1-1: Procedure for DC interworking with MTSI UE with DC service data provision over SMS
1. DC AS subscribes IMS AS via NEF to notify when IMS session is requested for the UE(s) as a called ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.30.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to exiting entities and interfaces:
DC AS:
- DC AS subscribes to IMS AS for notification of the event that a IMS session is requested for certain UE(s) as a called UE.
- DC AS triggers IMS AS to request the bootstrap data channel establishment initiation by terminating UE. D... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31 Solution #31: Support of IMS DC based avatar communication | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.1 Description | This solution proposes how to support Avatar communication with the avatar data repository in the IMS DC network. The avatar data stored in the network can be accessed by the IMS network only for the authorized UE. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.1.1 General | Figure 6.31.1.1: Example of enhanced IMS DC Architecture to support avatar store and access
To support of IMS avatar communications, the architecture is enhanced as below:
Avatar Data Repository (ADR):
- The Avatar Data Repository is used by the UE and the DCSF/MF to store and access to the list of Avatar IDs and its c... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.2.1 Authorization of the UE to access avatar data stored in the network | Based on Figure 5.1 in clause 5.2.2 of TS 23.228 [5], Authorize the UE for using the avatar data stored in Avatar Data Repository accessed by the IMS network for avatar communication with following differences:
- The UE includes a media feature tag in the Contact header field in REGISTER request that indicating UE supp... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.2.2 Bootstrap data channel establishment for retrieval of identities of avatar data stored in the network | Based on the Figure AC.7.1-1 of TS 23.228 [5], the bootstrap data channel establishment for retrial of Avatar ID List can be performed as described in Figure 6.31.2.2-1.
Figure 6.31.2.2-1: Bootstrap Data Channel set up Signalling Procedure for avatar communication
1. UE sends the INVITE with the SDP offer for audio/vid... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.31.3 Impacts on Existing Nodes and Functionality | This solution may have the following impacts to exiting entities and interfaces:
S-CSCF:
- S-CSCF checks whether the UE is subscribed to the avatar communication service which means the network can access to the Avatar Data Repository and the network is allowed to transfer the list of Avatar ID, and the Avatar data for... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32 Solution #32: Solution for support of IMS avatar communication without using data channel | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.1 Description | Figure 6.32.1-1: Architecture to support IMS avatar communication without DC
To support of IMS avatar communication, the architecture is enhanced as follows:
Editor's note: Whether existing DC2 can be re-used (e.g. by adding a new service) or a new DC2' is needed is FFS.
Digital Asset Container (DAC):
- The Digital Ass... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.2 Procedures | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.2.1 Scenario 1: Network centric IMS avatar call flow using SIP/SDP | Figure 6.32.2.1-1: Network centric IMS avatar call flow using SIP/SDP
The Avatar ID is transmitted as part of SIP/SDP negotiation.
NOTE 1: The following flow relates only to UE-A's avatar. Whether UE-B also wants to use an avatar in the same session is not considered.
1. UE A decides to request an avatar session with n... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.2.2 Scenario 2: UE-A centric IMS avatar call flow using SIP/SDP | Figure 6.32.2.2-1: UE A centric IMS avatar call flow using SIP/SDP
The Avatar ID is exchanged with the IMS network for getting the avatar representation. The Avatar ID is negotiated within SIP/SDP.
1. UE A decides to request an avatar session with local avatar rendering, e.g. based on its internal capabilities, and can... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.2.3 Scenario 3: UE-B centric IMS avatar call flow using SIP/SDP | Figure 6.32.2.3-1: UE B centric IMS avatar call flow using SIP/SDP
The Avatar ID is exchanged with UE-B for getting the avatar representation. The Avatar ID is negotiated within SIP/SDP.
1. UE A decides to request an avatar session with remote UE based avatar rendering, e.g. based on its internal capabilities, and can ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 6.32.3 Impacts on existing nodes and functionality | Impacted nodes and functionality are listed as follows:
UE:
- Support indicating avatar-id when establishing IMS sessions. Can support local avatar download from DAC, and rendering. Can support avatar media to allow remote rendering. Can support receiving feedback media including avatar from MF in case of network-based... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 7 Overall Evaluation | Editor's note: This clause will provide evaluation of different solutions. |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8 Conclusions | |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.1 Conclusions of KI #1 | For KI#1 on "Extensible IMS mechanism supporting IMS events in the context of DC communication" the following solution principles are proposed:
1. A new NEF service, based on SUBSCRIBE/NOTIFY requests, is defined for the IMS events in the context of DC communication.
2. The NEF service must be extensible and shall supp... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.2 Conclusions of KI #2 | The following conclusions are agreed for KI#2:
1. IMS network exposes its capabilities through the NEF, which can be provided by a specific NEF instance serving the IMS network exposure only or by the NEF instance serving the 5GC network exposure simultaneously.
2. The following capabilities need to be exposed by the I... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.3 Conclusions of KI #3 | For KI#3 on "IMS data channel interworking with MTSI UE" the following interim conclusions are agreed:
1. When the originating DCMTSI UE initiates an IMS DC session to the terminating MTSI UE, the originating DCSF is aware that the target UE does not support IMS DC based on the SDP answer from the terminating side and ... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.4 Conclusions of KI #4 | For KI#4 on "Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions" the following solution principles are agreed:
1. Support authorization check in IMS AS or S-CSCF whether the calling party (PBX / user) is authorized to use Third Party specific identity informat... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.5 Conclusions of KI #5 | For KI#5 on " Handling of PS data off exemption for services over IMS DC " the following conclusions are agreed:
1. "Services over IMS Data Channel" is configured as a whole service in the list of 3GPP PS Data Off Exempted Services.
2. When the user activates/de-activates PS Data Off in the UE, existing procedures shal... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.6 Conclusions of KI #6 | The following interim conclusions for KI#6 "Support of Standalone IMS Data Channel Sessions" are agreed:
1. The following scenarios for IMS session with standalone bootstrap DC, or a combination of standalone bootstrap DC and application DC shall be supported in this Release.
a. An IMS session with only standalone boot... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.7 Conclusions of KI #7 | The following conclusions for KI#7 "Support multiplexing multiple DC applications over single SCTP connection" are agreed:
The solution #22 in TR 23.700-77 is taken as the basis to form the solution principle.
The following multiplexing scenarios are supported in this release:
- Multiplexing using a single SDP m line S... |
ec4eaba43deb25dda94995d9f2935479 | 23.700-77 | 8.8 Conclusions of KI #8 | The following conclusions are agreed for supporting IMS Avatar communication: 1. In release 19, avatar communication is only supported based on the data channel architecture. 2. In release 19, network based rendering and UE based rendering is supported, which means: 2a. In network based rendering case the rendering of ... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 1 Scope | The present document is a technical report which identifies the application enabling layer architecture, capabilities, and services to support AI/ML services at the application layer.
The aspects of the study include the investigation of application enablement impacts, the application enablement layer architecture enha... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 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.
- Fo... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 3 Definitions of terms, symbols and abbreviations | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 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].
ML model: According to 3GPP TS 28.105 [9], mathematical algorithm that can be "trained" by... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
a968fed150b6156e01512b97375c462a | 23.700-82 | 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].
ADAES Application Data Analytics Enablement Server
A-ADRF Applica... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4 Analysis of AI/ML support in 3GPP | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.1 AI/ML related use cases and requirements in 3GPP | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.1.1 Description | 3GPP SA1 has identified use cases (3GPP TR 22.874 [12]) and requirements (in 3GPP TS 22.261 [10]) for the support of AI/ML model distribution, transfer, training for various applications (e.g., video/speech recognition, robot control, automotive), also covering the support for Distributed AI training/inference based on... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.1.2 Analysis | Table 4.1.2-1 lists the 3GPP specifed AI/ML service requirements which may have impact on application enablement layer. The requirements are grouped by functional areas.
Table 4.1.2-1: 3GPP AI/ML related requirements from 3GPP TS 22.261 [10] which may have impact on application enablement layer
Sl.
Requirements
Applica... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.2 AI/ML related stage 2 work in 3GPP | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.2.1 Description | 4.2.1.1 3GPP SA2
3GPP SA2 started from Rel-16 to investigate the AI/ML support focusing on the main two aspects.
1) AI-ML support in NWDAF
Network analytics and AI/ML is deployed in the 5G core network via the introducing of NWDAF consider the support of various analytics types that can be distinguished using different... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 4.2.2 Analysis | Both 3GPP SA2 and 3GPP SA5 have investigated the use of AI/ML for either enhancing core and management domain operations, or for providing assistance for 3rd party AI/ML services. Current solutions from other WGs do not cover:
- Support application layer aspects on top of 5GC/OAM, where the ML models and the ML/FL memb... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5 Key issues | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.1 Key issue #1: Support of Architecture Enhancement and Functions for Application Layer AI/ML Services | SA2 Rel-18 AIMLsys (in 3GPP TS 23.501 [5] and 3GPP TS 23.502 [6]) studied 5G System support for AI/ML-based services in application layer with the assumptions, for example:
- Application AI/ML operation logic is controlled by an Application Function (AF).
- AF request to the 5G System in the context of 5GS assistance t... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.3 Key issue #3: Support for federated learning | Federated Learning (FL) is a machine learning technique that enables multiple FL clients to train a model by exchanging the parameters instead of exchanging/sharing local data set. FL servers perform management of FL operations by maintaining and updating a global ML model, selecting and managing FL clients, performing... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.4 Key issue #4: Key issue on supporting Vertical FL at enablement layer | There are two types of federated learning defined, horizontal and vertical federated learning. Horizontal federated learning, or sample-based federated learning, is introduced in the scenarios that data sets share the same feature space but have different samples. Vertical federated learning or feature-based federated ... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.5 Key Issue #5: Support for of AI/ML operation splitting between AI/ML endpoints and in-time transfer of AI/ML models | KI #5 focuses on AI/ML operation splitting between AI/ML endpoints, and in-time transfer of AI/ML models as described in 3GPP TS 22.261 [10].
Split AI/ML inference is depicted in Figure 5.5-1. The AI/ML model inference is distributed into multiple parts according to the current task and environment (such as communicati... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.6 Key issue #6: Support for transfer learning | In 3GPP TS 22.261 [10] clause 6.40 it is stated that the 5G system needs to support at least three types of AI/ML operations:
- AI/ML operation splitting between AI/ML endpoints,
- Distributed/Federated Learning over 5G system, and
- AI/ML model/data distribution and sharing over 5G system.
With the latter kind of oper... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 5.7 Key issue #7: Discovery or Support of Member Selection and Maintenance for Application Layer AIML Service | AI/ML Services enable the Distributed/Federative Learning over 5G system. The Application layer AI/ML entities have heterogeneous nature, e.g., different models, OS, capabilities, that require creation of AIML criteria specific for application layer AIML enabler service. The AI/ML Services need have information about c... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 6 Application enablement architecture requirements | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 6.1 General requirements | [AR-6.1-a] The AI/ML enablement layer shall be able to support one or more VAL applications.
[AR-6.1-b] Supported AI/ML enablement capabilities may be offered as APIs to the VAL applications.
[AR-6.1-c] The AIML enablement layer shall support interaction with 3GPP network system to consume network and management data a... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 6.2 ADAE capability related requirements | [AR-6.2-a] The ADAE server shall be capable of providing data analytics for the DN energy efficiency.
[AR-6.2-b] The ADAE server shall be capable of providing data analytics for supporting ML/FL member selection.
[AR-6.2-c] The ADAE server shall be capable of providing AI/ML enabled data analytics. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 6.3 AIMLE capability related requirements | [AR-6.3-a] The AIMLE server shall be capable of provisioning and exposing ML client information.
[AR-6.3-b] The AIMLE server shall be capable of supporting the registration, discovery and selection of AIMLE clients which participate as ML/FL members in AIML service lifecycle.
[AR-6.3-c] The AIMLE server shall be capabl... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7 Application architecture for enabling AI/ML services | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.1 General | The functional architecture enhancements for the AIML enablement service are based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [7]. The architecture enhancements are organized into functional entities to describe a functional architecture enhancement which addresses the support for AIML en... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2 Application enablement architecture | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.1 On-Network AIML Enablement (AIMLE) Functional Architecture | Figure 7.2.1-1: On-network AIMLE functional model
Figure 7.2.1-1 illustrates the on-network functional model of AIML enablement. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes. The AIML enablement ... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.1.1 Service-based AIMLE architecture representation | Figure 7.2.1.1-1 exhibits the service-based interfaces for providing and consuming AIML enablement services. The AIMLE server could provide service to VAL server and AIML enablement client through interface SAiml.
Figure 7.2.1.1-1: Architecture for AIML enablement – Service based representation.
Figure 7.2.1.1-2 illust... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.2 Off-Network AIML Enablement Functional Architecture | Figure 7.2.2-1: Off-network AIML enablement functional model
Figure 7.2.2-1 illustrates the off-network (UE-to-UE) functional model of AIML enablement. In the vertical application layer, the VAL client communicates with a further VAL client over VAL-PC5 reference point. VAL-PC5 supports both unicast and multicast deliv... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.3 Architecture representation for supporting ADAE analytics | Figure 7.2.3-1: Architecture representation for supporting ADAE analytics.
Figure 7.2.3-1 illustrates the architecture representation of AIMLE when the AIML support capabilities serve ADAES to enhance its analytics services. Based on the VAL request to provide ML-enabled analytics, ADAES may consume AIMLE services (e.g... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.4 Functional Entities Description | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.4.1 General | The AIMLE functional entities are described in the following subclauses. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.4.2 AIMLE client | The AIMLE client functional entity acts as the application client supporting AIML Enablement services. It interacts with the AIML Enablement server. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.4.3 AIMLE server | The AIMLE server functional entity provides AIML Enablement services (like ML model related assistance operations) supported within the vertical application layer. It interacts with the AIML Enablement client. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.4.4 ML repository | The ML repository is a logical entity which can serve as registry for the ML / FL members as well as a repository for the application layer ML models and ML model information. The ML repository can be accessed by other entities via the AIMLE server. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5 Reference Points Description | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.1 General | The reference points for the functional model related to AIML enablement are described in the following subclauses. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.2 AIML-UU | The interactions related to AIML enablement functions between the AIML enablement client and AIML enablement server are supported by AIML-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [8] and 3GPP TS 23.501 [5]. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.3 AIML-S | The interactions related to AIML enablement functions between the VAL server(s) and the AIML enablement server are supported by AIML-S reference point. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.4 AIML-C | The interactions related to AIML enablement functions between the VAL client(s) and the AIML enablement client within a VAL UE are supported by AIML-C reference point. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.5 AIML-R | The interactions related to AIML enablement functions between the AIML enablement server, and the ML repository are supported by AIML-R reference point. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.6 AIML-E | The interactions related to AIML enablement functions between AIML enablement servers (e.g., central and edge AIMLE servers). |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.7 ADAE-S | The interactions related to application data analytics enablement functions between the VAL server(s) and the application data analytics enablement server are supported by the ADAE-S reference point. The specific ADAE server interactions corresponding to ADAE-S are described in 3GPP TS 23.436 [4]. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 7.2.5.8 SEAL-X | The interactions between the AIMLE servers and other SEAL servers are generically referred to as SEAL‑X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in 3GPP TS 23.434 [7]. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8 Solutions | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.0 Mapping of solutions to key issues | Table 8.0-1: Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI #5
KI #6
KI #7
Sol #1
X
Sol #2
X
X
Sol #3
X
X
Sol #4
X
Sol #5
X
Sol #6
X
X
Sol #7
X
X
Sol #8
X
Sol #9
X
Sol #10
X
X
Sol #11
X
Sol #12
X
X
Sol #13
X
X
X
Sol #14
X
X
Sol #15
X
Sol #16
X
Sol #17
X
X
Sol #18
X
Sol #19
X
Sol #20
X
Sol #21
X
Sol #22
X... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1 Solution #1: ADAE Functional Architecture Enhancement to Support Application Layer AI/ML Services | The following clauses specify the functional model of the ADAE with the ML Model Training and Management Enablement (MTME) function and the functional model of the AIML enablement service for supporting application layer AI/ML services. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.2 Functional Architecture | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.2.1 General | The functional architecture enhancements for the ADAE with ML model training and management enablement function and AIML enablement service are based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [7]. The architecture enhancements are organized into functional entities to describe a function... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.2.2 On-Network MTME-enhanced ADAE Functional Architecture | Figure 8.1.2.2-1: On-network MTME-enhanced ADAE functional model
Figure 8.1.2.2-1 illustrates the on-network functional model of ADAE with ML Model Training and Management Enablement (MTME) function. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU s... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.2.3 On-Network AIML Enablement Layer Functional Architecture | Figure 8.1.2.3-1: On-network AIML enablement layer functional model
Figure 8.1.2.3-1 illustrates the on-network functional model of AIML enablement layer. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery m... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.2.4 Coexistence of MTME-enhanced ADAE and AIML enabler | MTME-enhanced ADAES function supports ML capabilities (i.e. model training and management) to the ADAE service so that enhanced ADAE server/client are enabled to generate analytics results for supported analytics IDs using ML-enhanced methods.
For supporting MTME capabilities, the MTME-enhanced ADAE service assumes co-... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3 Functional Entities Description | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3.1 General | The ADAE functional entities with ML model training and management enablement function and AIML enablement layer function are described in the following subclauses. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3.2 ADAE client | The ADAE client functional entity acts as the application client supporting ML model training and may supporting management of ML model training. It interacts with the ADAE server. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3.3 ADAE server | The ADAE server functional entity provides for management and execution of ML model training supported within the vertical application layer. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3.4 AIML Enablement client | The AIML enablement client functional entity acts as the application client supporting AIML services and performs client-side operations. It interacts with the AIML enablement server. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.3.5 AIML Enablement server | The AIML enablement server functional entity provides services for comprehensive enablement of AIML functionality (e.g., federated and distributed learning). |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.4 Reference Points Description | |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.4.1 General | The reference points for the functional model for management and execution of ML model training and AIML enablement layer functions are described in the following subclauses. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.4.2 ADAE-UU | The interactions related to ML model training and management functions between the ADAE client and ADAE server are supported by ADAE-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [8] and 3GPP TS 23.501 [5].
ADAE-UU reference point is used for VAL service signalling ... |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.4.3 ADAE-S | The interactions related to ML model training and management functions between the VAL server(s) and the ADAE server are supported by ADAE-S reference point. |
a968fed150b6156e01512b97375c462a | 23.700-82 | 8.1.4.4 ADAE-C | The interactions related to ML model training and management functions between the VAL client(s) and the ADAE client within a VAL UE are supported by ADAE-C reference point. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.