hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 1 Scope | The present document specifies the procedures and information flows necessary for Network Slice Capability Exposure for Application Layer Enablement on the basis of SEAL. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 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... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 3 Definitions of terms, symbols and abbreviations | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 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].
VAL server policy: Network slice management Policy which can be seen as application functi... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
ASP Application Service Provider
Auto-NS-LCM Automatic Applicatio... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4 Overview | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.1 Registration | This functionality enables the VAL server to become a recognized user of CAPIF. VAL server registration procedures are specified in clause 9.2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.2 Slice API configuration and translation | This functionality is provided to the vertical application specific layer and configures the exposure of APIs in a slice-tailored manner. It is assumed that the VAL server is not initially aware of the all the API exposure capabilities and information which will be needed for the given slice based on the SLA, and NSCE ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.3 Application layer network slice lifecycle management | Application layer network slice lifecycle management is provided to the VAL to better meet consumer's requirement without having to interact with 5GS frequently, based on network slice status collected from 5GS and QoE collected from application layer. Application layer network slice lifecycle management procedures are... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.4 Network slice optimization based on VAL server policy | Network slice optimization based on VAL server policy optimizes the network slice for the vertical applications by triggering the network slice modification exposed by EGMF defined in SA5. Network slice optimization based on VAL server policy procedures are specified in clause 9.5. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.5 Discovery of management service exposure | This network slice capability enablement feature supports the initial discovery of MnS for a given slice based on VAL server request, and the discovery of new/modified MnS with the required exposure (for example the permissions of the VAL server over the target MnS, e.g. read, write operations). This feature consists o... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.6 Network slice performance and analytics monitoring | This functionality is provided to the VAL to get end to end network slice related performance and analytic monitoring. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the 5GC Network, etc.), performs data processing and abstraction, exposes the proc... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.7 Information collection from NSCE server(s) | The network slice status collected by the NSCE server could be exposed to other NSCE server(s) if some agreement has been made. Information collection from NSCE server(s) procedures are specified in clause 9.8. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.8 Predictive slice modification in edge based NSCE deployments | This feature addresses scenarios where the NSCE server is deployed at the edge and the migration to different Data Network will require that the ongoing slice is supported at the target area to ensure meeting the application session requirements. The slice parameters monitoring at the target area (e.g. for per NSI/NSSI... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.9 Multiple slices coordinated resource optimization | This functionality is provided to the VAL to monitor the slice usage status of multiple slices (PNI-NPN slice(s) and its private slice in the PLMN) of the PNI-NPN owner in a combined manner. It makes resource adjustment between different slices in one PLMN to realize optimized and efficient resource usage among multipl... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.10 Network slice adaptation for VAL application | This functionality is provided to the VAL to adapt the network slice for the VAL application. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS. The network slice adaptation request can be triggered by VAL server or VAL UE. ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.11 Slice related communication service lifecycle management | This functionality is provided to the VAL server to make slice related communication service lifecycle management. The NSCE server can acquire the application services related requirements for a specific VAL service from the vertical industry perspective, evaluate these requirements and then determines the network slic... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.12 Predictive slice modification in Inter-PLMN based slice service continuity | This functionality is provided to the VAL to make predictive slice modification where NSCE service provider provides its services when connected to two PLMNs and has SLA with them. The NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target PLMN and... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.13 Network slice diagnostics | Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service – either reported from a mobile user or service or detected by a... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.14 Network slice fault management capability exposure | Network slice fault management capability exposure gathers data from different sources (e.g., OAM, VAL server, NSCE client) and provides fault data that characterize the quality of the network connections and services to ensure a quick reaction to identify network connectivity, performance related problems. The Network... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.15 Slice requirements verification and alignment capability exposure | Slice requirements verification and alignment capability exposure provides the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client by checking whether the existing QoS/Slice related data is able to satisfy t... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.16 Network Slice Information delivery | The Network Slice information delivery sends the Network Slice information to VAL server and NSCE client. With that information, the VAL server is able to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice. The Network Slice Information deli... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 4.17 Network Slice Allocation | The NSCE server performs the Network Slice allocation operation on behalf of the VAL server if non-trusted 3rd party application (i.e., VAL server) cannot access to the 5GS management system directly. The specific service is specified in clause 9.18. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 5 Business models and relationships for NSCE | NSCE layer provides value added services to VAL customers, based on consuming 5GS services related to slicing (from OAM, 5GC) and based on interacting with the VAL UE side. The variety of services and the deployment aspects depend on the different assumptions for the slice owner / provider, the slice customer and the S... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6 Architectural requirements | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.1 General Description | The following clauses specify the requirements for network slice capability enablement services for application layers. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.2 General requirements | [AR-6.2-1] The NSCE architecture shall support the NSCE server to communicate with the VAL server with one or more applications.
[AR-6.2-2] The NSCE architecture shall support the NSCE server to communicate with one or more VAL servers.
[AR-6.2-3] The NSCE architecture shall support the NSCE server to interact with 3GP... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.3 Network slice Lifecycle management requirements | [AR-6.3-1] The NSCE architecture shall enable lifecycle management capability exposure of network slice by authorized VAL server.
[AR-6.3-2] The NSCE architecture shall enable lifecycle management capability exposure of network slice communication service to authorized VAL server.
[AR-6.3-3] The NSCE architecture shall... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.4 Performance data retrieval requirement | [AR-6.4-1] The NSCE architecture shall support the end-to-end network slice performance and analytics monitoring capability exposure to authorized VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.5 Network slice adaption requirement | [AR-6.5-1] The NSCE architecture shall support the network slice adaption capability exposure to authorized VAL server.
[AR-6.5-2] The NSCE architecture shall support the network slice adaption capability exposure to authorized NSCE client. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.6 Network slice configuration and translation requirement | [AR-6.6-1] The NSCE architecture shall support the network slice configuration capability exposure to authorized VAL server.
[AR-6.6-2] The NSCE architecture shall support the network slice translation capability to enable the translation of slice API invocated by VAL server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.7 Multiple slices combined management requirement | [AR-6.7-1] The NSCE architecture shall support the interactions with OAM or 5GC of 3GPP PLMN to provide multiple slices combined management service of that PLMN.
[AR-6.7-2] The NSCE architecture shall provide multiple slices combined performance monitoring service of the PLMN and its PNI-NPNs to authorized VAL server.
... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 6.8 Security requirements | [AR-6.8-1] The NSCE architecture shall provide mechanisms to authorize the usage of network slicing related services by the VAL servers and NSCE clients, conform to CAPIF as specified in 3GPP TS 23.222 [3].
[AR-6.8-2] The NSCE architecture shall support mutual authentication and authorization check between clients and ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7 Application architecture for NSCE | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.1 General | The architecture for the network slice capability enablement is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe a functional architecture which addresses the support for network slice capability enablement aspects for vertical app... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.2 Architecture description | Figure 7.2-1 depicts the network slice capability enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other.
Figure 7.2-1: Architecture for network slice capability enablement – reference points representation
The network slice capabi... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.3 Functional entities description | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.3.1 General | The functional entities for network slice capability enablement SEAL service are described in the following subclauses. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.3.2 Network slice capability enablement server | The network slice capability enablement server functional entity provides the application layer enablement of the network slicing aspects to support the VAL applications. The network slice capability enablement server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [3]. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.3.3 Network slice capability enablement client | The network slice capability enablement client functional entity acts as the application client for the slice enablement. The network slice capability enablement client interacts with the network slice capability enablement server to trigger network slice related operations such as adaptation due to an application requ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4 Reference points description | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.1 General | The reference points for the functional model for network slice capability enablement are described in the following subclauses. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.2 NSCE-UU | The interactions related to network slice capability enablement functions between the network slice capability enablement server and the network slice capability enablement client are supported by NSCE-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.501 [14]. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.3 NSCE-C | The interactions related to network slice capability enablement functions between the VAL client(s) and the network slice capability enablement client within a VAL UE are supported by the NSCE-C reference point. The NSCE client may receive application requirement change, application client information (such as its KQI)... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.4 NSCE-S | The interactions related to network slice capability enablement functions between the VAL server(s) and the network slice capability enablement server are supported by the NSCE-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [3]. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.5 N33 | The reference point N33 supports the interactions between the network slice capability enablement server and the NEF and is specified in 3GPP TS 23.501 [14]. N33 is used for the network-based mechanism for slice re-mapping, where NSCE server acting as AF influences the URSP rules for the application traffic per UE by p... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.6 NSCE-E | The interactions between the NSCE servers are generically referred to as NSCE-E reference point. This reference point supports information collection from other NSCE servers as defined in clause 9.8, Service continuity negotiation as defined in clause 9.9.2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.7 NSCE-OAM | The interface between the NSCE server and the OAM system are generically referred to as NSCE-OAM reference point. This reference point supports provisioning of management service as defined in clause 6.1, 3GPP TS 28.531 [8].
NOTE: The NSCE-OAM reference point is out of scope of this specification, and is defined by SA5... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 7.4.8 SEAL-X | The interactions between the NSCE servers and other SEAL servers are generically referred to as SEAL‑X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in 3GPP TS 23.434 [2]. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8 Identities and commonly used values | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.1 General | The common identities for SEAL refer to TS 23.434[2]. The following clauses list the additional identities and commonly used values for Network Slice Capability Enablement. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.2 NSCE server ID | The NSCE server ID uniquely identifies the Network Slice Capability enablement server. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.3 NSCE client ID | The Network Slice Capability enablement client ID identifies a particular NSCE client. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.4 Network Slice related Identifier | The network slice related identifier identifies the network slice, which is mapped to the VAL application.
The identifier of the network slice is either S-NSSAI defined in 5.15.2.1 TS 23.501[16], or External Network Slice Information (ENSI) defined in TS 33.501[14].
Based on the operator’s policy, if the service applie... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.5 Slice coverage area | The slice coverage area is the area where the network slice is available in the whole PLMN or in one or more Tracking Areas of the PLMN. The slice coverage area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geographical coordinates) or both. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 8.6 NSCE service area | The NSCE service area is the area where the Network Slice Capability Enablement server owner provides its services. It is equal to the collection of coverage area of slices it can enable.
The NSCE service area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geograph... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9 Procedures and information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.1 General | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.1.1 Common Information Elements | 9.1.1.1 General
This clause provides descriptions for Information Elements which are commonly used in several procedures. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.1.1.2 Service requirement | The service requirement indicates the VAL application requirements pertaining to the slice(s).
Table 9.1.1.2-1: Service requirement
Information element
Status
Description
VAL service ID
M
The identification of the application ID related with the service requirement.
VAL service KPIs
O
KPIs including application QoS req... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.2 Registration | For registration of the VAL server to be a recognized user of the CAPIF, the VAL server triggers the CAPIF Onboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.1. The NSCE server could be deployed with CAPIF core function.
NOTE: What additional information is needed, and if needed, whether it is s... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3 Slice API configuration and translation | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.1 General | This functionality is a service related to the translation of the service API as invoked by the end applications to slice APIs based on the API configuration and application to slice mapping. Slice APIs can be defined as customized/tailored sets of service APIs (which can be either NEF northbound APIs or OAM provided A... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2.1 Procedures on slice API configuration | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2.1.1 General | In the Initial Configuration procedure, the VAL server initially provides an application requirement to enabler server including the service KPIs and the subscribed/preferred slices. Then, the slice enabler configures the mapping of the VAL application to a slice API which is a combination/bundling of northbound APIs (... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2.1.2 Initial Configuration | Figure 9.3.2.1.2-1 illustrates the procedure of the initial slice API configuration.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
Figure 9.3.2.1.2-1: Initial Slice API configuration
1. The VAL server sends a VAL application requirement request to the NSCE server. If CAPIF is used, the NSCE... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2.1.3 VAL server-initiated Configuration Update | Figure 9.3.2.1.3-1 illustrates the procedure of the slice API configuration updated based on a trigger event.
Pre-conditions:
1. Initial configuration of the slice API has been completed successfully.
2. A trigger event, which may result the need of a slice configuration change, is captured by the VAL server (applicati... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.2.2 Procedure on slice API translation | This procedure follows the 9.3.2.1 and aims to describe how the slice API invocation request is translated to service API invocations after the slice API configuration mapping. In this procedure, the NSCE server initially receives a slice API invocation request from the vertical application. Then, the NSCE server fetch... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.1 General | The following information elements are specified for slice API translation and configuration specified in clause 9.3.2.1 and 9.3.2.2. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.2 VAL application requirement request | Table 9.3.3.2-1 describes information elements for the VAL application requirement request from the VAL server to the NSCE server.
This request provides the service requirements / KPIs, the capability exposure requirements and a preferred/subscribed slice identification (e.g., S-NSSAI or ENSI).
Table 9.3.3.2-1: VAL app... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.3 VAL application requirement response | Table 9.3.3.3-1 describes information elements for the VAL application requirement response from the NSCE server to the VAL server.
Table 9.3.3.3-1: VAL application requirement response
Information element
Status
Description
Result
M
Indicates the success or failure of the VAL application requirements request.
>Cause
O... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.4 Slice API information notify | Table 9.3.3.4-1 describes information elements for the Slice API information notification from the NSCE server to the VAL server. The Slice API information notification is used by NSCE server to send Slice API information to VAL server in the Initial Configuration and Configuration Update procedures.
Table 9.3.3.4-1: S... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.5 VAL server-initiated configuration update request | Table 9.3.3.5-1 describes information elements of the VAL server-initiated configuration update request sent by the VAL server to the NSCE server.
Table 9.3.3.5-1: VAL server-initiated configuration update request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
Network slice ID
O... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.6 VAL server-initiated configuration update response | Table 9.3.3.6-1 describes information elements of the VAL server-initiated configuration update response sent by the NSCE server to the VAL server.
Table 9.3.3.6-1: VAL server-initiated configuration update response
Information element
Status
Description
Configuration changed
O
(see NOTE)
Indicates that the slice confi... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.7 slice API invocation request | Table 9.3.3.7-1 describes information elements for the slice API invocation request from the VAL server to the NSCE server.
Table 9.3.3.7-1: slice API invocation request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
Authorization information
O
The authorization information obta... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.3.8 slice API invocation response | Table 9.3.3.8-1 describes information elements for the slice API invocation response from the NSCE server to the VAL server.
Table 9.3.3.8-1: slice API invocation response
Information element
Status
Description
Result
M
Indicates the success or failure of slice API invocation request.
>Cause
O
(see NOTE)
Indicates the ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4 APIs | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.1 General | Table 9.3.4.1-1 illustrates the NSCE APIs for the slice API configuration and translation feature.
Table 9.3.4.1-1: List of APIs for slice API configuration and translation feature
API Name
API Operations
Known Consumer(s)
Communication Type
SS_NSCE_SliceApiConfiguration
Slice_API_configuration
VAL server
Request /Resp... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.2 SS_NSCE_SliceApiConfiguration API | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.2.1 General | API description: This API enables the VAL server to communicate with the NSCE server for the initial configuration of the slice API and possible subsequent slice API configuration update(s). |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.2.2 SS_NSCE_Slice_API_configuration | API operation name: Slice_API_configuration
Description: Providing for VAL_Application_requirement to the NSCE server.
Known Consumers: VAL server
Inputs: See subclause 9.3.3.2
Outputs: See subclause 9.3.3.3 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.2.3 SS_NSCE_Slice_API_configuration_update | API operation name: Slice_API_configuration_update
Description: VAL server providing trigger event information to the NSCE server that may potentially invoke slice API configuration change(s).
Known Consumers: VAL server
Inputs: See subclause 9.3.3.5
Outputs: See subclause 9.3.3.6 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.2.4 SS_NSCE_Slice_API_information_notify | API operation name: Slice_API_information_notify
Description: Notifying the slice API information
Known Consumers: VAL server
Inputs: See subclause 9.3.3.4
Outputs: None |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.3 SS_NSCE_Slice_ApiInvocation API | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.3.1 General | API description: This API enables the VAL server to communicate with the NSCE server for invoking the slice API over NSCE-S. |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.3.4.3.2 SS_NSCE_Slice_API_invocation | API operation name: Slice_API_invocation
Description: Requesting slice API invocation from NSCE server.
Known Consumers: VAL server
Inputs: See subclause 9.3.3.7
Outputs: See subclause 9.3.3.8 |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4 Application layer network slice lifecycle management | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.1 General | When NSCE receives a request for application layer network slice lifecycle management (AppLayer_NS_LCM) from VAL server, the NSCE server performs the service operations including subscribing the event which may trigger the management system to do the network slice lifecycle management, making the network slice lifecycl... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.2 Procedure | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.2.1 Procedures on slice lifecycle management | Figure 9.4.2.1-1 illustrates a procedure of application layer network slice lifecycle management based on network slice related data and QoE collected from application layer.
Pre-conditions:
1. The NSCE server has authenticated and authorized to the capabilities to collect current network slice from 5GS.
2. The NSCE se... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3 Information flows | |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.1 General | The following information flows are specified for AppLayer_NS_LCM:
- AppLayer_NS_LCM subscribe, response and notification;
- QoE metrics subscribe, response and notification;
- Network slice LCM recommendation request and response; |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.2 Application layer network slice lifecycle management subscribe request | Table 9.4.3.2-1 describes information elements for the application layer network slice lifecycle management subscribe request from the VAL server to the NSCE server.
Table 9.4.3.2-1: AppLayer-NS-LCM Subscribe
Information element
Status
Description
Requestor Identifier
M
Unique identifier of the requestor (i.e. VAL serv... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.3 Application layer network slice lifecycle management response | The information elements specified in the Table 9.4.3.3-1 is used for the application layer network slice lifecycle management response sent from the NSCE server to the VAL server.
Table 9.4.3.3-1: AppLayer-NS-LCM Response
Information element
Status
Description
Result
M
Indicates that the success or failure.
> Cause
O
... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.4 Application layer network slice lifecycle management notification | The information elements specified in the Table 9.4.3.4-1 is used for the application layer network slice lifecycle management notification sent from the NSCE server to the VAL server.
Table 9.4.3.4-1: AppLayer-NS-LCM Notification
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that th... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.5 QoE metrics subscribe | Table 9.4.3.5-1 describes information elements for the QoE metrics subscribe from the NSCE server to the VAL server.
Table 9.4.3.5-1: QoE metrics Subscribe
Information element
Status
Description
Requestor Identifier
M
Unique identifier of the requestor (i.e. NSCE server ID).
Security credentials
M
Security credentials ... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.6 QoE metrics response | Table 9.4.3.6-1 describes the information elements for the QoE metrics response from the VAL server to the NSCE server.
Table 9.4.3.6-1: QoE metrics Response
Information element
Status
Description
Result
M
Indicates the success or failure of the QoE metrics request.
> Subscription ID
O
(see NOTE1)
Subscription identifi... |
a89a0ce5789287ec186d94e36b976f2e | 23.435 | 9.4.3.7 QoE metrics notification | Table 9.4.3.7-1 describes the information elements for the QoE metrics notification from the VAL server to the NSCE server.
Table 9.4.3.7-1: QoE metrics Notify
Information element
Status
Description
Subscription ID
M
Indicates that the QoE metrics request was successful.
QoE metrics report
M
List of result values for t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.