hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.2 SS_NRM_QoS_Service_Create response
| Table 8.1.10.1.2.2-1 describes the information flow for QoS service create response from the NRM server to the VAL server.
Table 8.1.10.1.2.2-1: SS_NRM_QoS_Service_Create response
Information element
Status
Description
Result
M
Result includes success or failure of the creation of the network resource with the u... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.3 SS_NRM_QoS_Service_Update request
| Table 8.1.10.1.2.3-1 describes the information flow for QoS service update request from the VAL server to the NRM server.
Table 8.1.10.1.2.3-1: SS_NRM_QoS_Service_Update request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Application Server... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.4 SS_NRM_QoS_Service_Update response
| Table 8.1.10.1.2.4-1 describes the information flow for QoS service update response from the NRM server to the VAL server.
Table 8.1.10.1.2.4-1: SS_NRM_QoS_Service_Update response
Information element
Status
Description
Result
M
Result includes success or failure of the update of network resource with the underly... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.5 SS_NRM_QoS_Service_Delete request
| Table 8.1.10.1.2.5-1 describes the information flow for QoS service delete request from the VAL server to the NRM server.
Table 8.1.10.1.2.5-1: SS_NRM_QoS_Service_Delete request
Information element
Status
Description
Requester Identity
M
The identity of the VAL server performing the request.
Application Server... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.2.6 SS_NRM_QoS_Service_Delete response
| Table 8.1.10.1.2.6-1 describes the information flow for QoS service delete response from the NRM server to the VAL server.
Table 8.1.10.1.2.6-1: SS_NRM_QoS_Service_Delete response
Information element
Status
Description
Result
M
Result includes success or failure of the deletion of network resource with the under... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.1.3 NRM service
| The proposal is to use a single NRM service for QoS control.
The following table 8.1.1.3-1 provides example of QoS requirements and the corresponding applications:
Table 8.1.1.3-1: List of examples QoS requirements and the corresponding applications
Max Data rate
Delay Characteristics
Max Packet loss rate
Applic... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.10.2 Solution evaluation
| This solution addresses the technical gap 4-1-2-1 on how to enhance NRM services API for various services and applications, ensuring ease of API usage and at same time ability to support services with commonly used QoS parameters for an API.
The key differentiating aspect of this solution (when compared with other pr... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.11 Solution #11: New SEAL service for power saving in IoT devices
| This solution corresponds to the technical gap described in clause 4.4, where the use of SS_NetworkResourceAdaptation and MonitoringEvent APIs to meet IoT application requirement, e.g., power saving, is not clear.
For the case of IoT devices, the NRM may be configured with DRX and eDRX parameters value that is mapped... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.11.1 Solution description
| The solution presents two procedures which correspond to two cases:
- Clause 8.1.11.3 describes the procedure related to the case when VAL server triggers power saving assist service for power saving in IoT devices. In this scenario, the VAL server requires a desired power saving mode for the target devices.
- Claus... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.11.2 Information elements
| Table 8.1.11.2-1: Power saving assist request
Information element
Status
Description
VAL User or VAL UE(s) ID(s) (NOTE)
M
The identity of the VAL user whose UE(s) are target for power savings configuration. Alternatively, is the UE ID on which the NRM client resided
VAL Service ID
M
The identity of the VAL se... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.11.3 Procedure case 1
| Figure 8.1.11.3-1 describes the procedure when the VAL server triggers power saving assist service for power saving in IoT devices.
Figure 8.1.11.3-1: Procedure for VAL server triggers power saving assist service
1. VAL server requests the NRM Server to assist power saving of the VAL user(s) that are part of VAL S... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.11.5 Solution evaluation
| The solution addresses the existing technical gap#4 in clause 4.4.2 related to IoT power saving scenarios. The solution describes two scenarios based on the entity that triggers power saving assist service for power saving in the VAL UE: scenario 1 is when the VAL server triggers the required power saving mode. Scenari... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.12 Technical solution 12: Solution for stage 2 services design in SEAL specifications
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.12.1 Solution description
| This solution addresses technical gap#7.
The API definition in 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] should be changes to SEAL services (list API The following way:
• List of SEAL API should be reverted to List of SEAL service
• API descr... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.4.4 SS_LocationInfoRetrieval API service
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.4.4.1 General
| API Service description: This API enables the VAL server to obtain UEs location information from the location management server over LM-S.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.4.4.2 Obtain_Location_Info operation
| Service API operation name: Obtain_Location_Info
Description : Request UEs location information.
Known Consumers: VAL server.
Inputs: Refer subclause 9.3.2.3
Outputs: Refer subclause 9.3.2.2
See subclause 9.3.9 for the details of usage of this API operation.
**************************************Third change***... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.3.9 On-demand usage of location information procedure
| The VAL server can request UE location information at any time by sending a location information request to the location management server, which may trigger location management server to immediately send the location report.
Figure 9.3.9-1 illustrates the high level procedure of on demand usage of location informati... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.3.2.3 Location information request for SS_LocationInfoRetrieval
| Table 9.3.2.3-1 describes the information flow from the VAL server to the location management server and/or from the location management server to the location management client for requesting an immediate location information report.
Table 9.3.2.3-1: Location information request
Information element
Status
Descript... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.12.5 Solution evaluation
| The solution addresses the existing technical gap in clause Gap# 4.7.2-1. It provides an example about how to modify stage 2 SEAL specifications according to stage 2's scope.
**************************************The end of changes************************************
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.13 Technical solution#13: Service design guidelines for common functionalities
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.13.1 Solution Description
| This paper proposes service design guidelines for common functionalities related to technical gap#8. In alignment with SEAL approach for common services for application enablement, this paper recommends that the common requirements and functionalities for different scenarios/applications shall be compiled into common e... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.1.13.2 Solution evaluation
| This solution addresses technical gap#8 and improvement of existing SEAL services based on the guidelines.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2 Solutions for SEAL services adoption gaps
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.1 Adoption Solution#1: Service based Architecture of 3GPP system supporting SEAL services
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.1.1 Solution description
| This solution is to solve GAP# 5-1-2-1.
Figure 8.2.1-1 Service based Architecture of 3GPP system supporting SEAL services
In the figure 8.1.1-1, SEAL services layer represents the SEAL server(s) supporting SEAL services and the SEAL client(s) (if applicable) defined in the SEAL specification 3GPP TS 23.434 [... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.1.2 Functional Elements
| NOTE: No new function elements are added to the existing 3GPP system.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.1.3 Reference Points
| NOTE: No new reference points added to the existing 3GPP system.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.1.4 Solution evaluation
| This solution provides the holistic picture providing the role and responsibility of SEAL service layer within the complete 3GPP system perspective. It clarifies the SEAL services can be implemented as part of 3GPP system and can well avoid some misleading.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2 Adoption Solution#2: Layered representation of 3GPP network exposure system
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.1 Solution description
| This solution is to solve adoption gap#3.
Figure8.2.2.1-1: Layered representation of SEAL service layer in 3GPP network exposure system
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2 Functional Elements
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.1 3GPP Exposure layer
| 3GPP Exposure layer acts entry points for exposing services APIs supported by 3GPP system, to a services APIs customer (the customer can be Application layer/or a third party's re-exposure system). The APIs exposed by exposure layer contains both service APIs and framework APIs.
the framework APIs and function entiti... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.2 3GPP service layer
| 3GPP service layer includes the legacy MNO services like IMS, SMS, and 3GPP application enabler layer services.
3GPP application enabler layer provides value added service based on network layer capabilities (including capabilities supported by Core network and OAM). it provides the following services based on genera... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.2.1 Edge application enabler layer
| The services and APIs provided by EEC/EES/ECS as defined in 3GPP TS 23.558[20] at this layer, enable an application on mobile UE to discover and select an edge application server (EAS) deployed at Edge site (at or close to 3GPP network border), and application server rediscovery and reselection due to UE mobility or ov... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.2.2 SEAL service layer
| The services at this layer defined in 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] provide the value-added services to enable application layer to utilize 3GPP network and UE capabilities in an easy-to-use way. SEAL services and APIs are generic to any app... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.2.3 Vertical specific services layer
| A service at this layer provides certain application layer service functions, which is specific for certain vertical application.
In 3GPP, the application specific service includes 3GPP TS 23.255 [22] for UAV, or 3GPP TS 23.286 [21] for V2X.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.4 3GPP user communication service layer
| It provides another type of service layer services, which mainly refers to the legacy user-orient operator applications, like IMS voice, SMS. These applications can also be exposed as the services to a third-party application.
The APIs specified in 3GPP includes 3GPP TS 23.228 [24], or 3GPP TS 23.239 [23]
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2.4 3GPP network connection layer
| The smallest granularity services that a 3GPP network layer function entity or OAM function entity, or a 3GPP UE is able to support e.g., 3GPP network connectivity services, QoS control, 3GPP position, slice creation/updating/deletion.
Network functions and capabilities defined at this layer are designed generally to ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.3 Relationship between different layer
| APIs from 3GPP network connection layer and APIs from SEAL service server of application enabler layer can be provided by MNO and offered certain services towards application layer via CAPIF.
3GPP service layer consumes the API services from 3GPP network connection layer and also terminal side APIs services.
APIs fro... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.2.2 Solution evaluation
| This solution clarifies the role and responsibility of SEAL service layer from the whole 3GPP system perspective, which are missing from 3GPP official document. Such layered representation of whole 3GPP network exposure system in the network exposure language will be helpful for customers to understand SEAL services be... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.3 Adoption solution#3: business relationship involving SEAL Client provider
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.3.1 Solution description
| This solution addresses adoption gap#5.
VAL service provider may get SEAL services by establishing the service agreement with SEAL server service provider directly as figure 8.2.3.1-1, or indirectly based on the service agreement between VAL service provider and SEAL client service provider, and SEAL client service pr... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.3.2 Evaluation
| This solution addresses adoption Gap#5. It provides more completed business relationship information which cover all the potential business parties related with SEAL layer.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4 Adoption Solution # 4: SEAL deployment involving SEAL Client(s)
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4.1 Solution description
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4.1.1 General description
| This solution addresses adoption gap#6.
3GPP TS 23.434 [3] only specifies the deployment alternatives of SEAL server. This solution provides additionally the description of potential SEAL Client(s) deployment alternatives.
SEAL server service provider may provide SEAL Client(s) as terminal SDK on top of terminal OS. ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4.1.2 Deployment of SEAL Client(s) in the same provider domain of SEAL server(s)
| Figure 8.2.1.2-1 illustrates deployment of the SEAL client(s) in the same domain of SEAL server(s). In this case, SEAL server(s) can be deployed in any of the domain described in clause 8.2.1 or 8.2.2, or 8.2.3 of 3GPP TS 23.434 [3].
Figure 8.2.1.2-1: SEAL client(s) deployed in the same domain of SEAL server
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4.1.3 Deployment of SEAL Client(s) in UE vendor domain
| Figure 8.2.1.3-1 and Figure 8.2.1.3-2 illustrates deployment of the SEAL client(s) in UE Vendor domain, which is different with the domain of SEAL server. In this case, SEAL server(s) can be deployed in any of the domain described in clause 8.2.1 or 8.2.2, or 8.2.3 of 3GPP TS 23.434 [3].
Figure 8.2.1.3-1: SEAL cli... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.4.2 Evaluation
| This solution addresses adoption gap#6. It provides the information about the SEAL client deployment which is currently lacking from 3GPP TS 23.434 [3].
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5 Adoption Solution#5: Target application use case of SEAL services
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1 Description
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.1 General description
| This solution is to address the adoption gap #4. It provides the content about the value and beneficial use case and advantages of SEAL services.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.2 Overall introduction of SEAL services
| This solution is to address the overall summary of the values and beneficial use case(s) of each SEAL service.
The supporting of the following are the key services that make SEAL layer distinct with other non-3GPP basis developer API Platform:
- NSCE/NRM/SEAL-DD which are specific to the usage of 5G/4G network capabi... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.3 SEALDD service to target application use case
| This solution provide clarification on SEALDD service linked to target application use case, and provide analysis on SEALDD mechanism and CDN mechanism.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.3.1 Use case
| CDN is known as a content distribution network. CDN is a global network server system that works together to provide super-fast delivery of Internet content such as website webpages, HTML pages, JavaScript files, stylesheets, images, and videos. When people try to access a website if using a CDN, then visitors will see... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.4.2 Advantages and values of SEALDD Services
| As it shows in figure 8.2.5.1.3-2, the application data information will be provided by SEAL DD in the way 3GPP system can read. So that 3GPP network layer can apply some enhancement transmission on SEALDD data.
Figure 8.2.5.1.3-1: SEALDD data transmission using differentiating-processing by 3GPP network
In additio... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.4 NRM services to target application use case
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.4.1 Use case
| Below list specifies the needs of the various applications utilizing the 3GPP network capabilities :
- URLLC as mentioned in clause 7.2 of 3GPP TS 22.261 [17]
- High data rate and low latency as mentioned in clause 7.6 of 3GPP TS 22.261 [17]
- Low latency e.g IMS/MCX Voice call/video call
- Background data transfer... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.4.2 Advantages and values of NRM Services
|
Figure 8.2.5.1.4.2-1: Capabilities of 5G system transformed by NRM service
The NRM service transforms 3GPP network capabilities and UE capabilities into the following types of service, enabling third party application providers to select and use network layer connection with different QoS services based on applica... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.5 NSCE to target application use case
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.5.1 Use case
| Some of the vertical industry players may rent dedicate slice(s) for their vertical applications. They may intent to have some slice self-management operation by themselves, including determining by themselves the services required slice SLA, ordering a slice product with the determined SLA from MNO, triggering the act... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.5.2 Advantages and values of NSCE
| To enable the slice self-management operation by vertical industry players, NSCE needs to use OAM APIs associated with slices. and core network slice APIs, UE client APIs to produce the NSCE services as Figure 8.2.5.1.5-1. When the NSCE is deployed within operator's trusted domain, it can access the 5GC directly, other... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.6 Spatial anchors
| A spatial anchor is an association between space and service information. The Spatial anchors SEAL service offers spatial anchors related capabilities (i.e., CRUDS) to one or more vertical applications. Spatial anchors enable the authorized users to place digital information at specific locations.
Spatial anchors can ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.6.1 Spatial map
| The Spatial map SEAL service offers spatial mapping and localization capabilities.
- Spatial mapping is constructing or updating a map of an unknown location.
- Localization is tracking an object to identify its location and orientation over time.
For spatial mapping service, sensing data gathered transparently is p... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.1.6.2 Digital asset
| The SEAL digital assets service enables management and usage of digital assets in a secure and controllable way. Examples of digital assets include digital representation (avatar), software licenses, gift certificates, tokens and files (e.g., music files) that have been purchased.
Digital asset service can be used in ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.5.2 Solution Evaluation
| This solution provides the overall summary of functions and values of each SEAL service. It also provides detailed description about the target use case and advantages of several SEAL services. It will be helpful for both system providers and customers to know more about SEAL services.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6 Adoption Solution #6: Alternative solutions for the SEAL mapping to an external SDO's system
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6.1 Description
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6.1.1 General description
| This solution is to address the adoption gap#5-7-2-1. It provides different alternatives about how to map the SEAL layer services to external API platform e.g., GSMA Open gateway, and how external SDO's application can use SEAL.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6.1.2 Alternative 1: SEAL layer services as the SBI of external platform
| 1) SEAL layer service as the SBI capabilities.
Figure 8.2.6.1.1-1 SEAL layer APIs are selected by external SDO as SBI In this solution, it is assumed external platform selects the3GPP API(s) as southbound. Based on their customer's requirement, it may select to the network layer services by adopting network API. O... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6.1.2 Alternative 2: Standard alternatives for market
|
Figure 8.2.6.1.2-2 Standard alternatives of exposure platform for market
External SDO platform only consume network layer services and defined their enabler layer services and Non-3GPP NBI for third party.
The non-3GPP NBI may expose the same services or different services with what are exposed by 3GPP NBI (pos... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 8.2.6.1.2 Solution evaluation
| SEAL layer services provides 3GPP enabler layer services, which are produced based on 3GPP system's capabilities. 3GPP SEAL layer services can be directly exposed to any applications, for example vertical applications of 5GAA,5GACIA.
From 3GPP perspective, 3GPP API consumers can also be a third-party platform. There a... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9 Overall evaluation
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1 Solution evaluations for technical gaps
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.1 Overall evaluation on technical gap #1
| Technical gap #1 focuses on NRM service to support the latest network capabilities, such as multi-modal traffic. Technical solutions 6, 7, and 10 in clause 8.1.6, 8.1.7, and 8.1.10 respectively address this gap.
Solution 6 focuses on application layer requirements by introducing a new set of NRM services to support re... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.2 Overall evaluation on technical gap #2
| Technical Solution #1 is the only one solution for technical gap #2.
The following texts described in gap#2:” The functions supported by services need to be further simplified and clarified. That is, it is recommended that the service exposed by an API should be Interpretable-value-to- application (e.g., no/less int... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.3 Overall evaluation on technical gap #3
| Technical gap #3 contains Gap#4-3-2-1 and Gap#4-3-2-2 as the following:”
Gap#4-3-2-1: Identify the procedures from the SEAL specification to provide the direct interaction (not via NEF/SCEF) with CN NFs (e.g., PCF, SMF) and/or indirect interaction (via NEF/SCEF) per different deployments and requirements and make chan... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.4 Overall evaluation on technical gap #4
| Technical gap #4 focuses on NRM services supporting IoT devices for dedicated scenarios such as power saving. Both solution 9 in clause 8.1.9 and solution 11 in clause 8.1.11 address this gap.
Solution 9 focuses on the interaction between the NRM server and the 3GPP network to address the gap under consideration. The... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.6 Overall evaluation on technical gap #6
| Technical solution#8 is the only solution for technical gap#6. It provides the solution to allow more API consumers, and aligned with existing application development domain implementation method.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.7 Overall evaluation on technical gap #7
| Technical solution#12 is the only solution for technical gap#7. It provides the solution about how to change the stage 2 TS to align with the stage 2 description style for SEAL services.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.1.8 Overall evaluation on technical gap #8
| Technical solution#2 and #3 and #13 are 3 solutions for the gap#8. Solution#2 and Solution#3 provide guidelines for API and SEAL service design from different aspects, and are complementary to each other as the following:
- Technical Solution#2 is about the criterial on what kind of SEAL services and APIs are easy-to-... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2 Gap evaluation for adoption gaps
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.1 Overall evaluation on adoption gap#1
| The adoption solution#1 is the only solutions for the adoption gap#1.
The following gap is mentioned in adoption gap#1:
• The representation of SEAL services layer within 3GPP system needs to be added.
The adoption solution#1 provides the architectures which includes SEAL services and other part of 3GPP system.... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.2 Overall evaluation on adoption gap#2
| The adoption solution#2 is the only solution for the adoption gap#2. It provides the solution to show where SEAL layer locates in the whole layered 3GPP exposure architecture. It is the necessary information to align the understanding within and outside 3GPP.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.3 Overall evaluation on adoption gap#3
| The adoption solution#5 is the only solution for the adoption gap#3.
It provides the summary of SEAL services and benefits of each. It also describes target use case, advantages of several SEAL services. Therefore, the solution can be used to tell how SEAL services benefit application developers.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.5 Overall evaluation on adoption gap#5
| The adoption solution#3 is the only solution for the adoption gap#5. It provides the solution about how to modify the existing SEAL specification, to show the complete business relationship involving SEAL client providers.
Therefore, adoption solution#3 should be selected as the baseline solution for adoption gap#5.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.6 Overall evaluation on adoption gap#6
| The adoption solution #4 is the only solution for the adoption gap#6. It provides the solution about how to modify the existing SEAL specification, to show how to deploy SEAL clients.
Therefore, adoption solution#4 should be selected as the baseline solution for adoption gap#6.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 9.2.7 Overall evaluation on adoption gap#7
| The adoption solution# 6 is the only solution for the adoption gap#7. It provides the two alternatives for the potential relationship between SEAL services and external SDOs. It is the advice from 3GPP perspectives, and leaves the flexible of external SDO to determine whether to use SEAL services and how to use SEAL se... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 10 Conclusions
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 10.1 General conclusions
| The results from the study will be considered for follow-up normative work in Release 20 as follows:
- SEAL services usage guideline toward 3GPP external ecosystem partners/organizations will be captured during normative phase by utilizing the content of final selected solutions for gaps as the input during normative ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 10.2 Conclusions of SEAL services technical gap #x
| This clause provides the final conclusion for each technical gap.
Technical Gap#1:
Technical Gap#2: Technical solution#1 is recommended as basis for normative work.
Technical Gap#3: Technical solution#4 is recommended as basis for normative work.
Technical Gap#4:
- Solution 11, which is a generalized solution wit... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 10.3 Conclusions of SEAL services adoption gaps
| This clause provides the final conclusion for each adoption gap.
Adoption Gap#1: Adoption solution#1 is recommended as basis for normative work.
Adoption Gap#2: Adoption solution#2 is recommended as basis for normative work.
Adoption Gap#3: Adoption solution#5 is recommended as basis for normative work
Adoption Gap... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 1 Scope | The present document will study and identify potential enhancements for supporting 5G NR Femto deployment. The study will investigate potential enhancements in the following areas:
- How to enable interworking between CAG and CSG cells.
- Study whether and how to support enabling the provisioning of subscribers allowed... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 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... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 3 Definitions of terms and abbreviations | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 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. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 3.2 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> |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 4 Architectural Assumptions and Requirements | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 4.1 Architectural Assumptions | The architecture for support of 5G NR Femto shall be based on the following architectural assumptions:
- the 5GS defined as part of Rel-18 is used as basis for further potential enhancements;
- the need for potential architecture enhancements for supporting 5G NR Femto deployments depends on the outcome of RAN WG3 stud... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.