hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.1.1 General | As per KI#6 description, according to clause 4.17.1 in 3GPP TS 23.222 [2], the scope of an API invoker on a UE in Resource owner-aware northbound API access (RNAA) is limited to accessing its own resources only. This is also acknowledged by SA3 in clause 6.5.3 in 3GPP TS 33.122 [3], in which "only a UE accessing its ow... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.1.2 UE-deployed API invoker accessing resources not owned by that UE | Figure 6.25.1.2-1 presents the procedure for enabling a UE-hosted API invoker accessing network-hosted resources owned by other UEs.
Pre-condition:
1. CCF Authorization Function has connectivity and can interact with ROF via CAPIF-8.
2. The API invoker in UE2 knows the identifier for UE1.
3. The API invoker knows the A... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.2 Architecture Impacts | This solution is based on the existing architecture of CAPIF as described in 3GPP TS 23.222 [2] and relates to the CAPIF-8 reference point. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.3 Corresponding APIs | Whether new or enhanced APIs are required to support this solution is in scope of SA3. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.25.4 Solution evaluation | This solution addresses the following open issue in KI#6:
1. Whether (and how) RNAA can support the scenario where API invoker(s) which are deployed on the UE can access resources (hosted in the network) of other resource owners (users) (e.g., application client on UE is fetching location of another UE or setting QoS f... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26 Solution #25: Discovery without onboarding service operation for enhanced API Invoker | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.1 Solution description | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.1.1 General | This solution is related to Key issue #5: Enhancing support to API Invoker on-boarding.
Currently, 3GPP TS 23.222 [2] clause 8.1 On-boarding of API Invoker to the CAPIF procedure, assumes that the API Invoker has appropriate API information to make a decision of sending an on-boarding request to CCF, however, the API P... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.1.2 Enhancing Onboarding the API invoker API to CAPIF | The CAPIF_API_invoker_management API, i.e. the Onboarding API invoker API described in TS 23.222 clause 8.1, is enhanced with the definition of a new service operation, Discovery_without_Onboarding service operation, that enables to query the availability of the features the API Invoker is looking to consume.
The Disco... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.1.2.1 Information flows, Discovery without Onboarding of the API Invoker to the CAPIF | 6.26.1.2.1.1 Discovery without Onboarding request
Table 6.26.1.2.1.1-1 describes the information flow for the Discovery without Onboarding request from the API invoker to the CAPIF core function.
Table 6.26.1.2.1.1-1: Discovery without Onboarding API invoker request
Information element
Status
Description
Invoker inform... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.1.2.2 Procedure, Discovery without Onboarding of the API Invoker to the CAPIF | Figure 6.26.1.2.2-1 illustrates the procedure for the Discovery without Onboarding of the API invoker to the CAPIF. The security aspects of this procedure are specified by SA3 in subclause 6.1 of 3GPP TS 33.122 [3].
Pre-conditions:
1. The API invoker is not a recognized user of the CAPIF. The API invoker is authorized ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.2 Architecture Impacts | This solution is based on architecture of CAPIF as described in 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.3 Corresponding APIs | This solution impacts the CAPIF Onboard API specified in clause 8.1 of 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 6.26.4 Solution evaluation | This solution addresses the open issue of enhancing the support to API Invoker on-boarding in KI #5. The impacted CAPIF procedure is the procedure of Onboarding the API invoker to CAPIF, by adding a new service operation that can be invoked by the API Invoker prior to on-boarding to retrieve AEF(s) service APIs informa... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 7 Deployment scenarios | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 7.1 General | This clause provides the additional or enhanced deployment scenarios for CAPIF as specified in clause 7 of 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 7.2 Deployment model #1: Updates to RNAA deployments | The following updates (in bold) are proposed to the RNAA deployments specified in clause 7.5 of 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 7.5 RNAA deployments | CAPIF supports RNAA and has enabled API invoker(s) to have authorized access to resources of a resource owner provided by service APIs offered by the AEF. The CCF acts as the Authorization Function and supports the authentication and authorization of the resource owner. Based on resource owner's authorization, the CCF ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 8 Business Relationships | The following updates (in bold) are proposed to the RNAA business relationships specified in clause 5.2 of 3GPP TS 23.222 [2]. |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 5.2 CAPIF business relationships for RNAA | Figure 5.2-1 shows the CAPIF business relationships for the resource owner-aware northbound API access (RNAA).
Figure 5.2-1: CAPIF business relationships for RNAA
The business relationships the API invoker, the CAPIF provider, and the API provider follow the description in the clause 5.1. In addition to them, the resou... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9 Overall evaluation | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.1 Evaluation of key issue#1 | Clause 5.1 captures the key issue on managing resource owner consent. The following open issues are listed:
1. How consent of the resource owner can be managed through communication between the resource owner and authorization function in the CAPIF core function
2. Whether (and how) “purpose of data processing” will be... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.2 Evaluation of key issue#2 | Clause 5.2 captures the key issue on supporting single sign-on. The following open issues are listed:
1. Whether and how to enhance CAPIF architecture and procedures considering Single sign-on (SSO)?
SSO is a technical mechanism to be applied for Authenticating multiple API invokers of the same Resource Owner. This key... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.3 Evaluation of key issue#3 | Clause 5.3 captures the key issue on RNAA architecture enhancements. The following open issues are listed:
1. Further enhancements to CAPIF architecture considering Resource Owner Function functionalities and its interactions with CAPIF entities (e.g., CAPIF-8 related interactions).
Solution#1 specified in clause 6.1 a... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.4 Evaluation of key issue#4 | Clause 5.4 captures the key issue on CAPIF interconnection. The following open issues are listed:
1. How to authenticate and authorize service API access for the AEF service API(s) exposed via CAPIF-6/6e.
2. Investigate applicable events and new events (if any) for CAPIF-6/6e.
Solution#4 specified in clause 6.5 provide... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.5 Evaluation of key issue#5 | Clause 5.5 captures the key issue on Enhancing support to API Invoker on-boarding. The following open issues are listed:
1. How to enhance the support of API Invoker on-boarding to reduce unnecessary on-boarding and wastage of resources?
2. Any enhancements required to other CAPIF procedures e.g. Registering the API pr... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.6 Evaluation of key issue#6 | Clause 5.6 captures the key issue on UE-deployed API invoker accessing resources not owned by that UE. The following open issues are listed:
1. Whether (and how) RNAA can support the scenario where API invoker(s) which are deployed on the UE can access resources (hosted in the network) of other resource owners (users) ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 9.7 Evaluation of key issue#7 | Clause 5.7 captures the key issue on CAPIF enhancement for AEF status and service API status. The following open issues are listed:
1. Whether and what kinds of AEF availability status and service API status should be considered for service discovery?
2. Whether and how to enhance the current CAPIF mechnisms considerin... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10 Conclusions | |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.1 General conclusions | This technical report fulfills the objectives of the CAPIF Phase 3 study based on the CAPIF specified in 3GPP TS 23.222 [2], including the following:
1) Identification of key issues (clause 5) and corresponding architecture requirements (clause 4) for enhancements to common API framework towards northbound APIs.
2) Cla... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.2 Conclusions of key issue #1 | Solution#3 and Solution#9 can be considered as candidate for normative work for addressing the aspects of granular access and granular API invoker information.
Solution#11, Solution#16, Solution#12 and Solution#13 can be considered as candidate for normative work for addressing the communication between resource owner ... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.3 Conclusions of key issue #2 | SSO is a technical mechanism to be applied for Authenticating multiple API invokers of the same Resource Owner. This key issue should be considered for developing security solution. Any stage 2 impact due to the security solution(s) developed for this key issue will be considered during normative work.
NOTE: The securi... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.4 Conclusions of key issue #3 | The stage 2 aspects related to solution#1 are to be further evaluated for security aspects considering the overall evaluation specified in clause 9.3. Based on feedback received related to security aspects, any stage 2 impact can be considered during the normative stage.
NOTE: The evaluation of security aspects is in t... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.5 Conclusions of key issue #4 | Solution#4 can be considered as candidate for normative work for addressing the CAPIF interconnection aspects for obtaining authorization for an API invoker accessing service APIs of 3rd party CAPIF provider as specified in clause 6.5.1.3.1, for revoking authorization involving a 3rd party CAPIF provider as specified i... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.6 Conclusions of key issue #5 | Solution#5 and Solution#17 can be considered as candidate for normative work for addressing the CAPIF event notifications for API invoker onboarding. The events related to security are to be coordinated with SA3.
Solution#5 can be considered as candidate for normative work for enhancements related to API invoker onboar... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.7 Conclusions of key issue #6 | Solution#19 can be considered as candidate for normative work to address how API invoker on UE can access resources of group of UEs.
Solution#24 can be considered as candidate for normative work to address how API invoker on UE can access resources for other UEs, without the limitation of all the UEs belonging to the s... |
fa8188fb9b6d6c250efd0a463cee5d86 | 23.700-22 | 10.8 Conclusions of key issue #7 | Solution#6 and Solution#7 can be considered as candidates for normative work for the aspect of CAPIF's AMF being utilized by CCF to enable AEF level or service API level instantiation. It is to be further ascertained during normative work if service API discovery is only used as trigger or should be enhanced to support... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 1 Scope | The present document studies application enabling layer architecture requirements, key issues, and solution recommendations to support XR services.
The study is based on the requirements defined in 3GPP TS 22.261 [2] and is dependent on the 5GC architecture supporting XRM services as specified in 3GPP TS 23.501 [3], 23... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 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... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 3 Definitions of terms, symbols and abbreviations | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 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. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 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].
<ABBREVIATION> <Expansion> |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4 Key issues | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.1 Key issue #1: KPI measurement and exposure | According to clause 6.43 of 3GPP TS 22.261 [2], synchronization between different media components is crucial for immersive multi-modal VR applications. This becomes particularly important when the synchronization threshold between two or more modalities is lower than the latency Key Performance Indicator (KPI) for the... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.2 Key issue #2: E2E Multi-Modal Communication Flows | Many XR use cases will require E2E multi-modal communication flows between application clients and application servers. SA1 has defined requirements for tactile and multi-modal communication service in 3GPP TS 22.261 clause 6.43, including the support to provide policy(ies) for E2E multi-modal communication flows assoc... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.3 Key Issue #3: Coordination between direct UE connection and network based connection for AR/VR services | In clause 7.6.1 of 3GPP TS 22.261 [2], the gaming or training service data can be exchanged between two 5G connected AR/VR devices. Communication over a direct link between the UEs can improve performance and service experience. Communication over 5G network and direct wireless connection can be used in parallel betwee... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.4 Key issue #4: Application enablement layer capabilities usage to supporting the XR services | The XRApp aims to help XR service providers in delivering immersive experience which is enabled by communicating and synchronizing data streams such that multiple participants have a consistent immersive impression.
From SA6 perspective, in addition to the SEALDD, which could provide the data delivery services, more ap... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.5 Key issue #5: Support the tethered UE | Different from other types of AR UE, the end-to-end path for the tethered UE includes one more wireless/wireline tethering link between AR Glasses and the tethering 5G Phone. In order to fulfill the end-to-end QoS requirements for the AR glass session, the consumer needs to acquire the tethering link status via measure... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.6 Key issue #6: XR application server selection enhancement | As for XR service, current XR application server selection mechanism using EDGEAPP may not be able to satisfy the strict latency requirement. And considering that XR application server may involve multi-model communication flow, to support multi-model communication flow synchronization, it is better to improve service ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.7 Key issue #7: E2E KPI optimization for XR service | In real-time XR service, E2E KPI (e.g. low latency) is critical to provide immersive experience for XR users. Typically, the overall processing of XR service consists of several parts, such as media rendering, media transmission over 5G network, etc. The XR application servers may have different capabilities to perform... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 4.8 Key issue #8: PDU set handling for XR traffic | SA2 and SA4 introduced PDU set based handling to support XR traffic. As mentioned in 3GPP TS 23.501 [3] and 3GPP TS 26.522 [9], for multi-modal flows transported in different QoS flow, the importance of PDU set can be used to help RAN to discard PDUs belonging to the same PDU set across flows, when needed. The PDU set ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5 Application enablement architecture requirements | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.1 General requirements | The general architecture requirements specified in clause 6.1 to 6.4 of 3GPP TS 23.433 [6] are applicable for XRApp service. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.2 Support for direct UE connection | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.2.1 Description | This clause specifies the requirements related to support for coordination between direct UE connection and network based connection. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.2.2 Requirements | [AR-5.2.2-a] The architecture shall support a mechanism to authorize specific UEs to transmit XR data via direct device connection.
[AR-5.2.2-b] The architecture shall support a mechanism for monitoring the availability and QoS of direct link between UEs for XR service data transmission.
[AR-5.2.2-c] The architecture s... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.3 Multi-modal flows alignment and monitoring requirements | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.3.1 Description | This subclause specifies the requirements for multi-modal flows alignment and monitoring service. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.3.2 Requirements | [AR-5.3.2-a] The XRApp shall provide a mechanism to enable multi-modal flows alignment by the authorized VAL server.
[AR-5.3.2-b] The XRApp shall provide a mechanism to enable multi-modal flows alignment monitoring by the authorized users or VAL server. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.4 Tethered device discovery and monitoring requirements | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.4.1 Description | This subclause specifies the requirements to support the tethered device. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 5.4.2 Requirements | [AR-5.4.2-a] The XRApp shall provide a mechanism to discover the tethered device for the XR service.
[AR-5.4.2-b] The XRApp shall provide a mechanism to monitor the tethered device by measuring the tethering link for the XR service. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6 Application enablement architecture for XR services | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6.1 Application enablement architecture | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6.1.1 General | This clause provides the overall architecture description. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6.1.2 Option1: Application enablement architecture for XRAPP function | When the XRApp function is a SEAL layer function, it could be deployment implementation by integrating the related enabler function (e.g. SEALDD server, NSCE server) to support XR application.
The XRApp function provides the service to VAL server over XRApp-S. The XRApp function interact with XRApp client over XRApp-UU... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6.1.3 Option2: Application enablement architecture based on existing application enablement capabilities | Instead of defining an additional independent architecture, XR related services could be supported by enhancing relevant existing functions(e.g., SEALDD).
6.1.3.1 Application enablement architecture based on SEALDD
To facilitate the specific optimization for XR application provided by 5G network, the application enable... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 6.1.4 Option3: CAPIF architecture to support the service discovery and invocation for XR application | The border AEF in existing CAPIF architecture in 3GPP TS 23.222 [18] can be utilized to support the XR service by invoking the northbound API exposed by the application enablement (e.g. SEAL, EDGEAPP) or the northbound API exposed by 5GS, as described in Figure 6.1.4-1.
Figure 6.1.4-1: Reuse CAPIF architecture to suppo... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7 Solutions | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.0 Mapping of solutions to key issues | Table 7.0-1 Mapping of solutions to key issues
KI #1
KI #2
KI #3
KI #4
KI #5
KI #6
KI #7
KI #8
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
X
X
Sol #5
X
Sol #6
X
Sol #7
X
Sol #8
X
Sol #9
X
Sol #10
X
Sol #11
X
Sol #12
X
Sol #13
X
Sol #14
X
Sol #15
X
Sol #16
X
Sol #17
X |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.1 Solution #1: SEALDD Policy Configuration for multi-modal flows | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.1.1 Architecture Impacts | This solution adds support for multi-modal SEALDD policy configuration functionality by enhancing the existing SEALDD policy configuration functionality supported in clause 9.10 of 3GPP TS 23.433[6]. There are no impacts to the SEALDD architecture. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.1.2 Solution description | This solution is targeting KI #2: E2E Multi-Modal Communication Flows and specifies enhancements to the SEALDD policy configuration information flows. In this procedure, the VAL server is a specific server for configuring multi-modal SEALDD policies and is different from VAL servers used for VAL application processing.... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.1.3 Information flows | 7.1.3.1 SEALDD policy configuration request for multi-modal flows
Table 7.1.3.1-1 describes the new information elements to be added to the SEALDD policy configuration request in 3GPP TS 23.434[6] Table 9.10.3.1-1 in order to support multi-modal flows.
Table 7.1.3.1-1: SEALDD policy configuration request IEs for multi-... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.1.4 Solution evaluation | This solution addresses KI #2: E2E Multi-Modal Communication Flows by proposing enhancements to the SEALDD policy configuration information elements. There are no impacts to the SEALDD architecture. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.2 Solution #2: Policy based Multi-modal SEALDD flow establishment | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.2.1 Architecture Impacts | This solution describes policy-based multi-modal SEALDD flow establishment functionality. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.2.2 Solution description | This solution is targeting KI #2: E2E Multi-Modal Communication Flows and specifies a policy based multi-modal SEALDD flow establishment procedure.
NOTE 1: In the normative phase, this solution is to be harmonized with the corresponding solution for multi-modal application data delivery initiated by VAL server, as well... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.2.3 Solution evaluation | This solution enables end-to-end multi-modal connection between VAL client and VAL server for application data delivery, with the connection initiation being based on policy, and it is well-aligned with the existing functionality in clause 9.2.2.3 of 3GPP TS 23.433. The solution has minimal architectural impacts. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.3 Solution #3: Support of Multi-Modal traffic indication in SEALDD layer | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.3.1 Architecture Impacts | This solution is based on architecture of SEALDD as described in 3GPP TS 23.433 [6]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.3.2 Solution description | 7.3.2.1 General
This solution addresses the improvement of the SEALDD layer to support Multi-Modal service.
The solution improves the SEALDD layer defined in 3GPP TS 23.433, i.e.:
1. The multiple flows can be requested in one SEALDD enabled regular data transmission connection establishment.
2. The SEALDD server uses 5... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.3.3 Solution evaluation | This solution addresses KI#2 for the following aspects:
- Whether and how to support the interaction between the application enablement layer and 5G CN to manage E2E multi-modal communication flows between application clients and application servers?
- Whether and how SEALDD may be enhanced to assist in managing E2E mu... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.4 Solution #4: Support of QoS measurement for Multi-Modal traffic in SEALDD layer | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.4.1 Architecture Impacts | This solution is based on architecture of SEALDD as described in 3GPP TS 23.433 [6]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.4.2 Solution description | The current QoS measurement in SEALDD layer supports the QoS measurements with VAL UE, VAL Group, or VAL UE identity list. These three options of the monitoring granularity are not able to fulfil the XR application scenario due to the XR application scenario requires the QoS measurement granularity per Multi-Modal flow... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.4.3 Solution evaluation | This solution addresses KI#1 to support:
- what KPI the application enabling layer could provide that impact the QoS of the XR services.
- how the KPI could be measured at the application enabling layer, and the enhancement of the SEALDD services.
This solution also addresses KI#8 to support:
- QoS measurement for PDU ... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.5 Solution #5: Multi-flow synchronization for multi-modal XR application | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.5.1 Architecture Impacts | This solution is presented based on the existing SEALDD architecture in 3GPP TS 23.433 [6]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.5.2 Solution description | 7.5.2.1 General
This solution addresses key issue #2 on E2E multi-modal communication flow, to solve how the SEALDD layer to manage the multiple association flows for multi-modal XR service to satisfy the multi-flow synchronization.
By performing the transmission quality measurements for multi-modal application, the SE... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.5.3 Solution evaluation | This solution focuses on the muti-flow synchronization for multi-modal XR application, where the SEALDD layer is enhanced to establish the SEALDD connection, and further determine the required QoS information for multi-modal flow(s), it can solve the three open issues in key issue #2. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.6 Solution #6: Multi-modal flows alignment and monitoring | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.6.1 Architecture Impacts | This solution requires a mechanism for data storage to cache the traffic flows. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.6.2 Solution description | 7.6.2.1 General
Synchronization between different multi-modal XR application components is crucial. In other words, the delay difference among the associated flows should be small. Otherwise, the arrived flows need to wait for other associated flows that do not arrived yet.
To avoid the downlink traffic flow delay diff... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.6.3 Solution evaluation | This solution addresses Key issue #1and key issue #2: KPI measurement and exposure, and multi-modal communication. It proposes multi-modal flows alignment and monitoring to optimize the delay difference of multi-modal flows.
For multi-modal flows alignment, VAL server sends multi-modal flows alignment request to SEALDD... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.7 Solution #7: Support multi-modal service in SEALDD | |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.7.1 Architecture Impacts | This solution is based on architecture of SEALDD as described in 3GPP TS 23.433 [6]. |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.7.2 Solution description | 7.7.2.1 General
This solution addresses the improvement of the SEALDD layer to support Multi-Modal service.
In order to simplify VAL handling, the SEALDD layer can perform packetilization. Figure 7.7.2.1-2 illustrates packetilization in SEALDD layer and information flows:
Figure 7.7.2.1-2: SEALDD packetilization for VA... |
2be37cf6cf0917b31218ef2ae24cece0 | 23.700-23 | 7.7.3 Solution evaluation | This solution addresses KI#8 to support:
- using SEALDD to facilitate XR traffic between application clients and application servers regarding XR traffic transmission with PDU set inclusion. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.