hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.2 Void
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.3 Adoption gap #2: Representation of SEAL services within the whole 3GPP network exposure system
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.3.1 Analysis
| The important role of SEAL services is to re-expose the 3GPP system capabilities by combining multiple capabilities of 3GPP system, across different domain including core network, OAM and terminal client.
In the existed SEAL service specification, the architecture mainly focuses on SEAL services layer. The informatio... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.3.2 Identified gaps
| Gap# 5-3-2-1:How to represent the SEAL service layer in the whole 3GPP network exposure system needs to be added
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.4 Adoption gap #3: Linking SEAL services to target application use cases
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.4.1 Analysis
| Many third-party application providers lack a comprehensive understanding of the mechanisms provided by 3GPP. A more detailed knowledge of SEAL could be highly beneficial for application layer developers, enabling them to make more effective use of its capabilities. Additionally, identifying and analyzing relevant use ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.4.2 Identified gaps
| Gap#5-4-2-1: It is essential to study how SEAL services benefit application developers (e.g., streamlined development time, enhanced robustness and reliability, abstraction of complicated APIs, etc.) and explore what new use cases can be enabled by these advantages.
Editor's Note: Solutions for this key issue should b... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.5 Adoption Gap#5: Incomplete business relationship for SEAL service
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.5.1 Analysis
| In 3GPP TS 23.434 [3] clause 5 describes the business relationship between different stakeholders. In clause 5 the SEAL service provider is quite not clear and complete (e.g., the role of seal service provider, seal clients/server provider). For example, the existing business relationship in the specification does not ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.5.2 Identified gaps
| Gap#5-5-2-1: Identify the further enhancements (like role of seal client provider) for the seal service provider described in clause 5 based on the different seal service deployment options in the context of the overall SEAL business relationship.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.6 Adoption Gap#6: Deployment options involving SEAL Client
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.6.1 Analysis
| Existing deployment defined in clause 8 of 3GPP TS 23.434 [3] does not cover the SEAL Client.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.6.2 Identified gaps
| Gap#5-6-2-1: Study how to cover SEAL client in the deployment mode.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.7 Generic gap#7: The adoption of SEAL layer by External Organizations
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.7.1 Analysis
| Both SEAL and the Network Transformation functions of the GSMA Open Gateway Platform are defined to provide abstraction layer services to enable third parties to use 5G/5GA capabilities. The current GSMA Open Gateway Platform Network Transformation functions are providing the mapping between CAMARA APIs (adopted by GSM... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.7.2 Identified gaps
| Gap#5-7-2-1: Study the different alternatives of using the SEAL layer in external organizations(e.g., GSMA Open Gateway Platform,5GAA/5GACIA etc), using the GSMA OPG architecture as base, and potential advantages/dis-advantages of each alternative.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 6 Void
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 7 Architecture requirements
| Editor's Note: requirements can be based on the idetified gaps
7.1 < API design guidance> requirements
Editor's Note: This clause will describe the architectural requirements for the studied application layer capabilities.
[Requirement 5.X.1] All the SEAL services and APIs should be defined in the principle of simpl... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8 Solutions
| <<for the idetified gaps and architecture requirements>>
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.0 Solutions and gaps mapping
| This clause provides the mapping of solutions to key issues.
Table 8.0-1: Mapping of solutions to technical gaps
Gap#1
Gap#2
Gap#3
Gap#4
Gap#5
Gap#6
Gap#7
Gap#8
Technical Sol #1
X
Technical Sol #2
X
Technical Sol #3
X
Technical Sol #4
X
Technic... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1 Solutions for SEAL services technical gaps
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1 Technical solution#1 SEALDD APIs improvement
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1 Solution description
| This solution is corresponding to Gap#4.2.2-1.
According to SA1 identified 5G applications/Use cases, the application needs from different application includes the following:
a) Application layer signalling between AC and AS for different applications with different data transmission QoS requirements:
a.1) Best effo... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.2.1 SEALDD regular connection management.
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.2.1.1 General
| The following clauses specify procedures, information flow and APIs for establishing an SEALDD enabled end-to-end connection between VAL client and VAL server. The end-to-end connection is uniquely identified in the SEALDD layer by the SEALDD-UU flow ID. The specific procedures detailed in the subsequent clauses are fo... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.2.2 Procedure
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.2.2.1 SEALDD enabled best effort signalling transmission connection establishment procedure
| Figure 8.1.1.2.2.1-1 illustrates the procedure for best effort signalling transmission connection establishment. In this clause, considering VAL server's requirement on signalling transmission is not strict, then the VAL server can invoke best effort signalling transmission connection establishment API to enable the co... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.3 Signalling flow
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.3.1 SEALDD enabled best effort signalling transmission connection establishment request
| Table 8.3.1.1.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the best effort application signalling traffic transmission service.
Table 8.3.1.1.3.1-1: SEALDD enabled best effort signalling transmission connection establishment request
Information element
Status
Descript... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.3.2 SEALDD enabled best effort signalling transmission connection establishment response
| Table 8.3.1.1.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the best effort application signalling traffic transmission.
Table 8.1.1.1.3.2-1: SEALDD enabled best effort signalling transmission connection establishment response
Information element
Status
Description
... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.3.3 SEALDD signalling transmission connection establishment initiated by SEALDD client request
| Table 8.3.1.1.3.3-1 describes the information flow from the SEALDD client to the SEALDD server for requesting the SEALDD signalling transmission connection establishment.
Table 8.1.1.1.3.3-1: SEALDD signalling transmission connection establishment initiated by SEALDD client request
Information element
Status
Descri... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.3.4 SEALDD signalling transmission connection establishment initiated by SEALDD client response
| Table 8.3.1.1.3.4-1 describes the information flow from the SEALDD server to the SEALDD client for responding to the SEALDD signalling transmission connection establishment initiated by SEALDD client.
Table 8.1.1.1.3.4-1: SEALDD signalling transmission connection establishment initiated by SEALDD client response
Info... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.2.2 SEALDD enabled High data rate & low latency (HRLC)
| The SEALDD enabled regular data transmission defined in clause 9.2.2.2 of 3GPP TS 23.433[2] can be used with the following changes:
- The term Sdd_RegularTransmission is changed to Sdd_HRLCTransmission.
- The QoS information for the application traffic in step 1 of 9.2.3.1 and 9.3.3.3 should restricted to indicate re... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.1.2.3 SEALDD enabled application data transmission for Low latency (LC)
| The SEALDD enabled regular data transmission defined in clause 9.2.2.2 of 3GPP TS 23.433[2] can be used with the following changes:
- The term Sdd_RegularTransmission is changed to Sdd_LCTransmission.
- The QoS information for the application traffic in step 1 of 9.2.3.1 and 9.3.3.3 should restricted to indicate requ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.1.2 Solution evaluation
| This solution provides new SEALDD services, which are designed according to application needs on performance. Different SEALDD services also requires different resource cost.
Therefore, it is easily for SEALDD services consumer to understand what benefits their applications can get, and why they are charged differentl... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.2 Technical solution #2: < SEAL services and SEAL API design guidelines>
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.2.1 Solution description
| This solution addresses the technical gaps#8in clause 4.8. This solution is about how to establishing common evaluation criteria to support easy-to-use SEAL service and associated APIs.
The difference and relationship between SEAL service design (about what information/resource can be exposed to third party) and API d... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.2.2 Solution evaluation
| The guidelines defined in this solution are aligned with the principle of defining easy-to-use service(s).
NOTE: The API service design guidelines will only impact the newly added services and will not impact the existing architecture or API services.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3 Technical solution#3: SEAL service design guidance framework
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1 Description
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.1 Aspects related to Guidance Framework
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.1.1 General
| This guidance framework addresses technical gap#8 by providing a systematic approach to help application developers understand and utilize SEAL services effectively. The guidance explains service applicability through detailed scenario analysis, presents comparative advantages over existing solutions, and offers practi... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.1.2 Service Applicability Analysis
| The first aspect of this guidance is to enumerate potential application scenarios and industries for each SEAL service, enabling developers from relevant domains to quickly understand the applicability of these services.
For example, when describing the location management service, we identify its applicability in sc... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.1.3 Comparative Advantages
| The second aspect of this guidance is to describe the advantages of SEAL services by comparing them with similar solutions (such as 3GPP core network services and OTT services).
When compared with 3GPP core network services, SEAL services demonstrate advantages in API simplification, enhanced reliability, and unified ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.1.4 Development Guidance
| The third aspect of this guidance is to provide best practice examples for some specific scenarios.
For each SEAL service, we select specific scenarios and provide best practice examples to ensure efficient integration and optimal usage. These guidelines include detailed workflows that outline API interactions step by... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.1.2 Implementation of guidance framework
| Editor's Note: This clause is FFS
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.3.2 Solution evaluation
| This solution addresses technical gap#8by proposing a guidance framework for SEAL service design, which helps application developers understand and utilize SEAL services effectively.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.4 Technical solution 4: The specification changes for direct interaction between LMS and GMLC/LMF
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.4.1 Solution description
| This solution is to address LMS related content for Gap#4-3-2-1. The solution is descibed in the way to tell how to change the 3GPP TS 23.434 [3] with highlight content.
8.1.4.1.1 Changes to clause 9.2.2 of 3GPP TS 23.434 [3]
The changes to Clause 9.2.5 of 3GPP TS 23.434 [3] should be changed as the following (new ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.2 On-network functional model description
| Figure 9.2.2-1 illustrates the generic on-network functional model for location management.
Editor's Note 1: The above figure should be deleted by the normative CR to 3GPP TS 23.434 [3].
Figure 9.2.2-1: On-network functional model for location management
The location management client communicates with the locat... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5 Reference points description
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.1 General
| The reference points for the functional model for location management are described in the following subclauses.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.2 LM-UU
| The interactions related to location management functions between the location management client and the location management server are supported by LM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
LM-UU reference point provides a means... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.3 LM-PC5
| The interactions related to location management functions between the location management clients located in different VAL UEs are supported by LM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.4 LM-C
| The interactions related to location management functions between the VAL client(s) and the location management client within a VAL UE are supported by LM-C reference point.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.5 LM-S
| The interactions related to location management functions between the VAL server(s) and the location management server are supported by LM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
LM-S reference point is used by the VAL server to request and ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.6 LM-E
| The interactions related to location management functions between the location management servers in a distributed deployment are supported by LM-E reference point.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.7 T8
| The reference point T8 supports the interactions between the location management server and the SCEF and is specified in 3GPP TS 23.682 [13]. The functions related to location management of T8 are supported by the location management server.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.8 Le
| The reference point Le supports the interactions between the location management server and the GMLC and is specified in 3GPP TS 23.273 [50].
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.9 LM-3P
| The reference point LM-3P is used for location retrieval of the target UE from a third-party location server.
NOTE: Further definition of LM-3P is out of scope of this specification.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.10 N33
| The reference point N33 supports the interactions between the location management server and the NEF and is specified in 3GPP TS 23.501 [10] and 3GPP TS 23.502 [11]. The functions related to location management of N33 are supported by the location management server.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5.11 Ngmlc
| The reference point N33 supports the interactions between the location management server and the GMLC and is specified in 3GPP TS 23.273 [8].
******************************End of Changes***************************************************
8.1.4.1.3 Changes to clause 9.3.7 of 3GPP TS 23.434 [3]
The changes to Clause... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.3.7 Location information subscription procedure
| Figure 9.3.7-1 illustrates the high-level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to VAL user or VAL UE location information. This procedure is also used for initiating tracking a UE's locati... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.3.11.2 Monitoring Location Deviation procedure
| Figure 9.3.11.2-1 describes the procedure for monitoring the VAL UE's location in a given area of interest.
Pre-condition:
- The location management server authorized to consume the 3GPP core network service (Monitoring events provided by NEF as specified in 3GPP TS 23.502 [11] or by GMLC as specified in 3GPP TS 23.2... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.3.26.3 Confirm location verification
| The location management client (LMC)/application in the UE gets from non-3GPP positioning (e.g. GNSS) in the UE its location. The application in the UE wants to check if this is really the correct location.
Pre-conditions:
1. The LMC is authorized to discover and to use Confirm Location API provided by the LMS;
2. L... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.4.2 Solution evaluation
| This solution well addresses the solution about how to address LMS related content for Gap#4-3-2-1. It makes an aligned description for the case where LMS is deployed with trusted domain of MNO.
8.1.5 Technical Solution#5: Align Security Credential with 3GPP TS 33.434 [13] and Clean Application Enablement Specificatio... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.5.1 Solution description
| This solution maps to Gaps in clause 4.5. This solution is about how to align Security Credential with 3GPP TS 33.434[13] and clean application enablement specifications.
Security credential(s) for authorization and verification as well as security mechanisms for SEAL services in general are specified in 3GPP TS 33.43... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.5.2 Solution evaluation
| The solution provides a method to avoid using undefined parameter in SEAL specifications and avoid misalignment across different WGs.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6 Technical Solution #6: Multiple NRM services for network service QoS control
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.1 Solution description
| This solution proposes to address the gaps identified in clause 4.1 regarding the support various application requirements at NRM.
It is proposed to introduce a new set of NRM services to support the various applications per their requirements to the network resource and handling based on the following principles:
- ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.1.1 Procedures
| 8.1.6.1.1.1 QoS control service for network transport with additional indication of SLA on QoS service type
The figure 8.1.6.1.1.1-1 illustrates the high-level procedures of creating the QoS control service for network transport with high data rate and low latency service.
Pre-conditions:
SLA on QoS service type (... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.1.1.2 Information flow
| 8.1.6.1.1.2.1 Network resource adaptation request
Table 8.1.6.1.1.2-1 describes the information flow network resource adaptation request from the VAL/SEALDD server to the NRM server for request the different QoS services.
Table 8.1.6.1.1.2.1-1: Network resource adaptation request
Information element
Status
Descri... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.1.1.2.2 Network resource adaptation response
| Table 8.1.6.1.1.2.2-1 describes the information flow network resource adaptation response from the NRM server to the VAL server.
Table 8.1.6.1.2.2.2-1: Network resource adaptation response
Information element
Status
Description
Result
M
Result includes success or failure of the network resource adaptation with t... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.2 NRM services
| The following new NRM service listed in table 8.1.6.2-1 are introduced:
Table 8.1.6.2-1: List of new QoS SLA service names for network resource control
Service Name
Known Consumer(s)
Communication Type
NOTE
Nrm_QoSCtrlLowLatencyHighBW
VAL
Request/response
No special reliable requirement comparing to network av... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.3 NRM services API
| NRM services defined in 8.1.6.2 is to label the addition resource type (comparing to the average QoS performance based best effort) what API invoker can request for different application traffic. It is possible that specifying one NRM service API to support SLA on multiple QoS services type (listed in 8.1.6.1) which ar... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.6.4 Solution evaluation
| This solution provides several new NRM services for network service QoS control to the application service providers/developers. Each of the new NRM service represents a different QoS service catalog and allow the application stakeholders to choose a proper QoS control service corresponding to their application require... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.7 Solution#7: Enhancements of NRM network resource adaptation service
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.7.1 Solution Description
| This solution addresses technical gap#1 in clause 4.1.
It is important for the NRM services to provide sufficient input parameters to support latest network capabilities such as multi-modal application traffic. The existing NRM network resource adaptation service can be enhanced for multi-modal traffic by providing ad... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.7.2.1 Impact to existing NRM information flows
| The information flows of NRM network resource adaptation service in 3GPP TS 23.434 [3] can be enhanced (highlighted in bold italics) as follows.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.3.3.1 Network resource adaptation
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.3.3.1.1 General
| This subclause describes the procedure for network resource adaptation using PCC procedures. This procedure satisfies the requirements for requesting unicast resources and modification to already allocated unicast resources to VAL communications.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.3.3.1.2 Procedure
| Figure 14.3.3.3.1.2-1 illustrates the procedure for the network resource adaptation.
Figure 14.3.3.3.1.2-1: Network resource adaptation
1. The VAL server (or SEALDD server) sends a network resource adaptation request to the NRM server for one or more users belonging to one or more VAL services, and may comprise... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.2 Information flows
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.2.1 Network resource adaptation request
| Table 14.3.2.1-1 describes the information flow network resource adaptation request from the VAL/SEALDD server to the NRM server.
Table 14.3.2.1-1: Network resource adaptation request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
List of VAL ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 14.3.2.2 Network resource adaptation response
| Table 14.3.2.2-1 describes the information flow network resource adaptation response from the NRM server to the VAL server.
Table 14.3.2.2-1: Network resource adaptation response
Information element
Status
Description
Result
M
Result includes success or failure of the network resource adaptation with the underly... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.7.2 Solution evaluation
| This solution provide mechanism to enable NRM to support network resource adaptation service for multi-modal applications. There are two some open issues for UE IP address and multi-modal service ID in solution.
It has no architecture impact.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.8 Technical solution #8: Representation of SEAL service consumer
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.8.1 Solution description
| This solution addresses technical gap#6 in clause 4.6.
The following sentences for clarification should be added into 3GPP TS 23.434[3], 3GPP TS23.435[4], 3GPP TS23.436[5], 3GPP TS23.437[6], 3GPP TS23.438[7], 3GPP TS23.482[12]:
In present document, there is no general restriction on the type of potential consumers o... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.8.2 Solution evaluation
| This solution removes unnecessary restriction on the consumers of SEAL services. It makes SEAL service specification aligned with application implementation mechanisms, and improves the value of SEAL by allowing more customers.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9 Technical solution #9: New NRM service for IoT power saving
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9.1 Solution description
| This solution proposes to address the gaps identified in clause 4.4 regarding the support power saving requirements at NRM. based on the following principles:
• The new NRM services are designed per application layer requirements as described in clause 8.4.A single service API serves a single service;
• The i... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9.1.1 Procedures
| The figure 8.9.1.1-1 illustrates the high-level procedure for the application layer consumer (e.g., VAL server) to use the power saving service.
Figure 8.9.1.1-1: IoT Power saving invocation procedure
1. The application layer consumer (e.g., VAL server) invokes the IoT power saving service. The input parameters e.g... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9.1.2 NRM service for IoT power saving
| The following new NRM service listed in table 8.1.b.1.2 are introduced:
Table 8.1.b.1.2-1: List of new NRM services for IoT power saving
Service Name
Known Consumer(s)
Communication Type
IoT Power saving service
Application layer entity
Request/response and subscribe/notify
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9.2 Impacts on architecture, services, entities
| This solution has no architecture impacts.
This solution creates new NRM service at NRM for IoT power saving.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.9.3 Solution evaluation
| This solution provides a single IoT power saving service to the IoT service provider/developer to achieve the power saving. It aggregates multiple network northbound service and expose a single service API to the ASP which simplifies the interactions between the IoT service provider/developer and the 3GPP network to ut... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10 Technical Solution # 10: Single NRM service for network service QoS control for applications
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1 Solution description
| This solution proposes to address the technical gaps identified in clause 4.1 regarding the support for various application requirements at NRM.
To achieve an API design involving different use cases/application with different QoS characteristics, the proposed solution is to consider a single API and with inputs – de... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.1 Procedures
| This subclause describes the procedure for QoS control service creation/updating/deletion based on VAL server application QoS requirements.
Figure 8.1.10.1.1-1 illustrates the procedure for the QoS control service.
Figure 8.1.10.1.1-1: QoS control service procedure
1. The VAL server triggers SS_ NRM_QoS_Servi... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2 Information flows
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.1 SS_NRM_QoS_Service_Create request
| Table 8.1.10.1.2.1-1 describes the information flow for QoS service create request from the VAL server to the NRM server.
Table 8.1.10.1.2.1-1: SS_NRM_QoS_Service_Create request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Application Server... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.