hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.2 Description | The Architectural Assumptions in clause 4.1 include the assumption that a single active human user (identified by a user ID) and corresponding user profile is applied to determine restrictions and policies which apply to the UE and a specific PDU Session.
This solution proposes that the user profile data includes infor... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.3.1 Procedure for influencing the AM and UE policy by the user profile information | This procedure shows how the AM and UE policy is influenced by the user profile information.
Figure 6.26.3.1-1: AM and UE policy influence by the user profile information
0a. The upper layers in the UE indicate the user ID to the UE.
0b. The UDR stores one or more user profiles associated with User IDs (e.g. for User A... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.3.2 Procedure for influencing the SM policy by the user profile information | The procedure of SM policy influenced by the user profile information is shown in Solution #1, clause 6.1.3, steps 7a -7c. Especially the step 7b can be re-used and enhanced so that the PCF retrieves from the UDR the PDU Session policy control subscription information (by using the SUPI as reference key) and, in additi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.3.3 Procedure for exposure of user identity profile information | The user profile is stored in the UDR and there is a data structure containing the data to be exposed to an AF.
Editor's note: It is FFS which the data to be exposed and how this data is sent to the UDR. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.26.4 Impacts on services, entities and interfaces | Impacts to UDM:
- retrieve AM and/or SM related data sets from the user profile information by using authorised (or active) user ID.
- create AM subscription data to be sent to the AMF and SM subscription data to be sent to the SMF by using the UE subscription data and the corresponding AM and/or SM related data sets f... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.27 Solution #27: Configuration and Usage of User Identifiers | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.27.1 Key Issue mapping | The solution addresses Key Issue 2. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.27.2 Description | This solution addresses key issue #2 “Authentication and Authorization of Users and Restrictions on Users”. In the architectural assumptions, there is a restriction about the usage of user identify that when the user identifier applies to a human, only a single user identifier is active with a UE subscription at a give... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.27.3 Procedures | The figure 6.27.3-1 below shows a high-level flow of the actions needed for enhancement about PDU session modification procedure.
Figure 6.27.3-1: High-level flow of enhancement about PDU session modification procedure
The procedure includes the following steps:
0. The UE and user#1 have registered for network, and the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.27.4 Impacts on services, entities and interfaces | UE impacts:
- When determining that the user#1 would logout with application interaction, the UE triggers the PDU session modification procedure.
- When determining that the user#2 would login with application interaction, the UE may trigger the PDU session modification procedure.
SMF impacts:
- When SMF receives PDU s... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28 Solution #28: Handling and notifying the UE when the UE is associated with a User Identifier. | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28.1 Introduction | This solution addresses KI#2 related to WT. Below details more on notification building on top of Solution 6 and Solution 10 which mentions of UECM de-registration of the UE (father) for the SMS service when the User identity (child) is registered to the network.
NOTE: If the UECM de-registration should be done for the... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28.2 Description | If the User Identity is using the UE, the terminating services like SMS attempting to deliver a message to the UE Subscription will fail because UE is not available at that moment for the SMS, as UECM is deregistered for the SMS. However, UE is still used by user identity. So, it is required that.
- The terminating SMS... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28.3.1 Illustration for SMS | Figure 6.28.3-1: Procedure for send indication to UE when the terminating service is SMS
1. User Identifier 1 is registered with the UE and the UE may have indicated that is supports receiving an indication.
2. UE gets UECM deregistered for the SMS Service.
3. When SendRoutingInfoForSM reaches to the UDM for terminatin... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.28.4 Impacts on services, entities, and interfaces | UE:
- UE supports indicating UE capability of supporting receiving indications from the network for the UE.
- UE implements receiving of the indication.
UDM:
- Implements identification of terminating SMS to a UE and the state of the UE being in de-registered state.
- Carries out indication to the UE based on the local... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.29 Solution #29: User profile exposure check | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.29.1 Key Issue mapping | This solution addresses Key Issue #3, Exposure of User Identity Profile Information.
- What and how User Identity Profile information and functionality are exposed (e.g. exposure of the content of the User Identity Profile, exposure of authorization/authentication results, authenticating users, and linking a User Ident... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.29.2 Description | The following information and functionality of User Identity Profile Information may be exposed by NEF:
- Provisioning of User Identity Profile (UIP) Information by AF.
- Verification of Link between User Identifier and associated subscription.
- Exposure of Authentication Results (e.g. in the sol#15).
- User Identifie... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.29.3 Procedures | The procedure in clause 4.15.6.2 of TS 23.502 [5] (i.e. Parameter Provisioning information flow) is re-used with following additional handling.
- After step 1, the NEF retrieve the UIP Exposure Profile from UDM and perform the exposure check. Only this operation is allowed, the NEF perform the subsequent step. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.29.4 Impacts on existing services, entities and interfaces | UDM:
- There is a UIP Exposure Profile in the UDM for the subscriber.
NEF:
- Perform the UIP Exposure Profile check against the AF request. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30 Solution #30: Identifying non-3GPP devices behind a UE or 5G-RG via Server control | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.1 Key Issue mapping | This solution addresses KI#4. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2 Description | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2.0 General | This solution is based on storing the device information in a server via a client program that runs in the UE/5G-RG. Then, the subscriber/admin of UE/5G-RG can log into the server and select the desired QoS profiles for each device. The device information is provided to the PCF via NEF and PCF provides relevant policie... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2.1 Device Information Profile | The Device Information Profile (DIP) for each UE/5G-RG contain the following elements:
1. Device traffic descriptors: For each device behind UE/5G-RG this is used to detect its traffic for differentiated QoS provisioning and charging and may include:
a. Source IPv6 address allocated by UE/5G-RG: For IPv6 traffic.
b. So... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2.3 Architecture | Figure 6.30.2.3.1 and figure 6.30.2.3.2 describe the solution architecture for roaming and non-roaming cases.
Figure 6.30.2.3.1: High-level roaming architecture
Figure 6.30.2.3.2: High-level non-roaming architecture
NOTE: In the case of 5G-RG, the DIP client may reside in Auto-Configuration Server (ACS). |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2.4 Solution Description | The following, describes a high-level procedure for the solution:
NOTE 1: Whether to standardize the DIP client-server protocol in 3GPP e.g. in SA WG6 is to be determined during study conclusions.
1. The UE/5G-RG's subscriber connects to the DIP server to determine QoS descriptors for the devices behind UE/5G-RG. The l... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.2.5 Authentication and Authorization | Regarding Authentication and authorization, the following apply:
- The DIP server is responsible to authenticate the UE/5G-RG subscriber.
- It is the responsibility of the subscriber to ensure that the device descriptor corresponds to the correct device behind UE/5G-RG. There is a risk of using device hostname as devic... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.3 Procedures | Figure 6.30.3.1 describes the procedure for provisioning the device information profile to the DIP server, and that DIP server can provide guidance for URSP rules, and figure 6.30.3.2 describes how this information is used by the 5GC to enable differentiated QoS for each device behind 5G-RG/UE.
Figure 6.30.3.1: Provisi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.30.4 Impacts | DIP Server:
- A new server outside 5GC, which is deployed and operated by the operator.
NEF:
- Enhancement to Nnef_AFsessionWithQoS service to accept device port ranges and device descriptor as an input.
UE/5G-RG:
- Supporting a client program to update the device information profile in DIP server.
UE/PCF:
- Optionally... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31 Solution #31: UE/5G-RG-initiated PDU Modification to support differentiated QoS for device behind UE/5G-RG | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.1 Key Issue mapping | This solution addresses Key Issue #4 on how to provide policy control of individual non-3GPP device behind a UE or 5G-RG.
5GC may have information on a QoS policy applied to a non-3GPP device behind a 5G-RG or UE where a User Identifier is used between 5GC and the 5G-RG/UE to identify the QoS policy, and maps that poli... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.2 Description | Pre-Requisites:
- UE/5G-RG has an inbuilt authentication capability or is configured to access an external AAA server, which the UE/5G-RG could use to authenticate the device user identity. An EAP based device authentication can be carried out. This aspect is not discussed under this solution and not in the scope of th... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.3.1 Procedures for provisioning of non-3GPP device information | Figure 6.31.3.1-1: Provisioning of non-3GPP device information
Steps 1-4 follow Rel-18 WWC procedures for NAUN3 devices as specified in TS 23.316 [7] -
1. 5G-RG registers to 5GC as specified in clause 7.2.1.1 of TS 23.316 [7].
2. The non-3GPP device establishes an L2 connection (e.g., WLAN connection) with the 5G-RG.
3... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.3.2 Procedures for policy control for non-3GPP devices | Figure 6.31.3.2-1: Policy control for non-3GPP device
1-2. During Steps 1-2, 5G-RG detects the non-3GPP device with the User Identifier is connected. For example, 5G-RG can detect the User Identifier during the Wi-Fi association or authentication procedure. The 5G-RG/UE allocates the device with the IP address/port num... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.31.4 Impacts on services, entities and interfaces | NEF:
- Extensions to the NEF Service Parameter Service to allow an AF to provision non-3GPP device information.
- NEF receives non-3GPP Device User identifier as part of Policy Data from the AF and communicate the same to the UDR.
- NEF may support receiving of even notification subscription from the AF for UE User map... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32 Solution #32: Non-3GPP Devices Behind UE or 5G-RG support | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.1 Key Issue mapping | This is a solution for KI#4. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.2 Description | The proposed solution addresses how 5GC identifies individual non-3GPP devices connecting behind a UE or 5G-RG (as depicted in Figure 6.32.2-1) and how to provide policy control for the traffic associated with individual non-3GPP devices. The mention of UE in subsequent clauses needs to be considered as applicable for ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.3.1 Identification | Figure 6.32.3.1-1 depicts high level procedures to show how 5GC identifies individual non-3GPP devices connecting behind a UE or 5G-RG.
Figure 6.32.3.1-1: Identification of non-3GPP devices connecting behind a UE or 5G-RG
0. The 5GS operators provision a list of N3DBU IDs. In Steps 1a-1c, the UE or 5G-RG follows genera... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.3.2 Maximum Number of Simultaneously Active N3DBU ID | An operator may provision a maximum number of simultaneously active N3DBU IDs in the UE/5G-RG subscription data. As described in clause 6.32.2 and clause 6.32.3.1, the UE/5G-RG receives a list of subscribed N3DBU IDs and the allowed maximum number of simultaneously active N3DBU in the Registration Accept. UE/5G-RG shou... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.3.3 Policy Aspects | To send PDU of a non-3GPP device associated with an N3DBU ID, the 5G-RG/UE determines the association of a Non-3GPP device to a PDU session based on URSP evaluation, by means of matching a N3DBU ID to a TD of a URSP rule. One PDU session can be used by one or multiple non-3GPP devices. The mapping of local network reso... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.32.4 Impacts on services, entities and interfaces | UE or 5G-RG:
- Support Registration Request with indication of N3DBU support.
- Handle N3DBU ID related URSP rules.
AMF:
- UE Policy Association Establishment with UE context subscription information related to N3DBU IDs, optionally.
SMF:
- SM Policy Association Establishment or SMF initiated SM Policy Association Modi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.33 Solution #33: Number of the active non-3gpp devices restriction | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.33.1 Key Issue mapping | The solution applies to Key Issue #4: Identifying non-3GPP Devices Connecting behind a UE or 5G-RG. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.33.2 Description | Assumptions:
- It is assumed that a UE and the UE's subscription may be used by multiple users. Such an UE is provided with an User Profile in the UDM linked to the UE's subscription profile. One of the attributes of the User Profile is the max number of the active non-3gpp devices.
- The number of the simultaneously i... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.33.3 Procedures | Figure 6.33.3: Number of the active non-3gpp devices restriction
1. The User Profile is provided to the UDM and linked to the UE subscription information. One of the attributes of the User Profile is the max number of the active non-3gpp devices which is optional and configurable by the operator.
2. The UE registers wi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.33.4 Impacts on existing services, entities and interfaces | UDM:
- User Profile handling.
AMF:
- User Profile handling;
- Number of the active non-3gpp devices with non-3gpp device identity counting and control.
- New 'max number of active non-3gpp devices reached' reject cause.
UE:
- New parameter to indicate a service request from a new non-3gpp device with non-3gpp device id... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34 Solution #34: Identifying non-3GPP Devices based on non-3GPP Device Report from the UE/5G-RG | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.1 Key Issue mapping | This solution addresses Key Issue #4. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.2 Description | In this solution, it is assumed that a Device Identifier of a non-3GPP device is unique at least within the operator's network.
The Device Identity Profile contains following information:
- Linked 3GPP subscription (SUPI).
- List of Device Identifiers.
- Information that can identify the non-3GPP device (e.g. host name... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.3 Procedures | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.3.1 Procedures for provisioning of Device Identity Profile | Figure 6.34.3.1-1: Provisioning of Device Identity Profile
1. If the AF wants to create/update/delete Device Identity Profile, the AF provides Device Identity Profile information including GPSI of linked 3GPP subscription, Device Identifiers, information that can identify non-3GPP devices and Specific service settings ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.3.2 Procedures for authorization of UE/5G-RG supporting non-3GPP devices and non-3GPP device policy provisioning | Figure 6.34.3.2-1: Authorization of UE/5G-RG supporting non-3GPP devices and non-3GPP device policy provisioning
1. If the UE supports non-3GPP devices connecting behind a UE/5G-RG, the UE indicates its capability in the 5GMM capability of Registration Request message.
2. The AMF retrieves subscription data of the UE/5... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.3.3 Procedures for providing service to non-3GPP device | Figure 6.34.3.3-1: Providing service to non-3GPP device
1. A non-3GPP device connects to the UE/5G-RG.
2. Based on information that can identify the non-3GPP device (e.g. host name, MAC address, port, SSID, etc.) in the N3D Policy, the UE/5G-RG identifies non-3GPP device. Then the UE establishes PDU Session or selects ... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 6.34.4 Impacts on services, entities and interfaces | UE/5G-RG:
- provisioned with N3D Policy.
- identifies non-3GPP device connecting behind it and sends NAS SM message.
AMF:
- selects the PCF which supports N3D Policy provisioning and establishes a UE policy association with the PCF.
SMF:
- supports receiving NAS SM message containing Non-3GPP Device information.
- regi... |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 7 Overall Evaluation | Editor's note: This clause provides evaluations of different solutions. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 8 Conclusions | |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 8.1 Key Issue #1: Identifying the Human User of a Subscription | No normative work will take place for this key issue in this Release. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 8.2 Key Issue #2: Authentication and Authorization of Users and Restrictions on Users | No normative work will take place for this key issue in this Release. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 8.3 Key Issue #3: Exposure of User Identity Profile Information | No normative work will take place for this key issue in this Release. |
fb0c502ceb1833d179cc417229266866 | 23.700-32 | 8.4 Key Issue #4: Identifying non-3GPP Devices Connecting behind a UE or 5G-RG | The following bullets are the conclusion principles for KI#4: - Authentication for non-3GPP device is performed by UE or 5G-RG, which is not in the scope of 3GPP. - Device Identifier is a permanent identifier and will be a generic string, and the allocation of the Device Identifier is out of scope of 3GPP. - 5GC is abl... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 1 Scope
| The scope of Technical Report is to study on potential enhancements to Service Enabler Architecture Layer (SEAL). In particular, the study reviews the existing SEAL specifications and architecture to identify any gaps or potential enhancements necessary to enable usage of SEAL for 3rd party applications, including aspe... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 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.
-... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 3 Definitions of terms, symbols and abbreviations
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 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].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 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>
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4 SEAL services technical gap analysis
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.1 Technical gap#1: NRM service
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.1.1 Analysis
| XR is an emerging mobile media service expected to contribute more and more traffics to 5G network. 3GPP specifies several new capabilities to support this feature, including the enhancement of PCF/N33 APIs towards the AF/AS. There are some gaps from the easy-to-use perspective.
(1) Unnecessary parameters for XR, whic... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.2 Technical gap #2: SEALDD service
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.2.1 Analysis
| Currently, the services defined in SEALDD can be improved to expose a better service to the 3rd party. The improvement can contain following aspect:
The functions and values supported by services defined in SEALDD need to be further improved to make it easier for third parties to understand the functions and values of... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.2.2 Identified gaps
| Gap 4-2-2-1: The functions supported by services should be further improved for 3rd party to understand.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.3 Technical Gap#3: Direct and/or indirect interaction \with CN NFs per different deployments and requirements
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.3.1 Analysis
| According to 3GPP TS 23.501 [10] and 3GPP TS 23.502 [11], a MNO's AF(trusted AF) can invoke all the APIs exposed by NF(s) from SBA interface. Thus, SEAL server(s) deployed by an MNO within the MNO's domain may act as the trusted AF and is able to invoke network service APIs exposed by 3GPP core network functions direct... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.3.2 Gaps
| 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 changes if required.
Gap#4-3-2-2: Study how to enable GMS to use 5G VN group ... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.4 Technical gap #4: NRM service to support IoT
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.4.1 Analysis
| 1. The network API is not designed for dedicated application scenarios(e.g., power saving) in IoT service.
Several network APIs defined in 3GPP TS 29.122 [15] can be used by the IoT service. However, they are designed in a generic manner to cater to different varieties of consumers (e.g.Vertical applications). Based o... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.4.2 Identified gaps
| - Gap#4-4-2-1: How to use the SS_NetworkResourceAdaptation and monitoringEvent API to meet IoT application requirements e.g., power savingis not clear;
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.5 Technical gap #5: Security Credential
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.5.1 Analysis
| The term Security Credential was added in some SEAL service procedures and information flows, but without definition (e.g., in 3GPP TS 23.434 [3] clause 12.3.4, 3GPP TS 23.435 [4], 3GPP TS 23.436 [5], 3GPP TS 23.437 [6], 3GPP TS 23.438 [7], 3GPP TS 23.482 [13]). It's unclear about the mechanisms on how Security Credent... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.5.2 Identified gaps
| Gap 4.5.2-1: How to align the Security Credential in the SEAL information flows with the security mechanisms specified in 3GPP TS 33.434 [13] and clean application enablement specifications.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.6 Technical Gap#6: SEAL server API consumers
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.6.1 Analysis
| In existing SEAL specification, the API consumer of many SEAL server APIs are restricted to VAL server only. Such restriction is not aligned with the assumption of allowing UE type of consumer, or a third party's platform.
In addition, there are no technical support to distinguish API requests from UE side with API re... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.6.2 Identified gaps
| Gap 4.6.2-1: Solutions to guide the changes to existing SEAL specifications to cover other the SEAL server API consumers should be studied.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.7 Technical gap#7: Distinguishing stage 2 SEAL services design with stage 3 API definition
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.7.1 Analysis
| As 3GPP TS 23.502, Stage 2 API works should mainly focus on services (e.g., SEAL services) design. Services are more about what kind of resource/information are supposed to be provided to consumers and should be enabled by an API. It may also include the required input information and potiential operations for the serv... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.7.2 Identified gaps
| Gap# 4.7.2-1: The solutions about how to modifying stage 2 SEAL specifications to align them with 3GPP working splitting between SA2 WG (services design) and stage 3 WGs (API definition).
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.8 Technical gap #8: API design guidelines for SEAL services
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.8.1 Analysis
| The supporting of application ecosystem is very important for the commercialization of the SEAL technologies. So, make APIs easy-to- use is already a widely used API design principle.
There is no global unified standard/guidance about how to design easy-to-use API. However many organizations or API providers has setup... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 4.8.2 Identified gaps
| Gap# 4-8-2-1:How to design easy-to-use APIs o guide the API definition work and provide solution about how to enhance 3GPP TS 23.222 [9].
Gap# 4-8-2-2:Revisit the existed SEAL services/APIs and make improvement based on the API design guidelines.
|
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5 SEAL services adoption gap analysis
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.1 Generic gap #1: Representention of SEAL services within 3GPP system
| |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.1.1 Analysis
| In the existing SEAL service specification 3GPP TS 23.434 [3], the architecture mainly focuses on SEAL services layer. The holistic picture providing the role and responsibility of SEAL service layer within the complete 3GPP system perspective is missing.
As the SEAL service server is a new type of 3GPP network funct... |
d0ed7c76ec64333437bedc5ac6134b17 | 23.700-35 | 5.1.2 Identified gaps
| Gap# 5-1-2-1:The representation of SEAL services layer within 3GPP system needs to be added.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.