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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[4] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[5] GSMA NG.116 - Generic Network Slice Template.
[6] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[7] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[8] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[9] 3GPP TS 28.537: "Management and orchestration; Management capabilities".
[10] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[11] 3GPP TS 28.535: "Management and orchestration; Management services for communication service assurance; Requirements".
[12] 3GPP TS 23.502: "Procedures for the 5G System (5GS)".
[13] 3GPP TS 29.536: "5G System; Network Slice Admission Control Service; Stage 3".
[14] 3GPP TS 33.501: "Security architecture and procedures for 5G System"
[15] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements"
[16] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[17] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[18] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[19] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[20] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[21] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".[22] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[22] 3GPP TS 33.434: "Service Enabler Architecture Layer (SEAL); Security aspects for Verticals".
[23] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS) "
[24] 3GPP TS 32.111-1: "Management and orchestration; Fault management, Part 1: 3G fault management requirements".
[25] 3GPP TS 28.533: "Management and orchestration; Architecture framework".
[26] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service"
[27] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction ".
[28] 3GPP TS 28.202: "Charging management; Network slice management charging in the 5G System (5GS); Stage 2"。
… |
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 function policy from VAL Provider/ slice customer/ASP, abstracted based on the slice usage pattern of application, consisting of trigger event and expected action. When provided to NSCE server, the NSCE server will trigger the expected action based on the policy.
MNO policy: The network slice management policy between the VAL and MNO pertaining to a specific service and slice, including ranges of network slice capabilities which can be adapted, i.e. Network slice Service level agreement.
NSCE service provider policy (NSPP): The network slice capability enablement service policy between the VAL and NSCE service provider pertaining to a specific service and slice, including ranges of network slice capability enablement service which can be adapted, i.e. NSCE service level agreement.
Policy harmonization: The NSCE service that harmonizing the VAL server policy parameter, to make sure the VAL server policy is compatible with the policies of the MNO and NSCE service provider policy for the same service or slice.
Requirement alignment: The NSCE service that aligning the network slice performance and the VAL service requirement in the request. |
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 Application Layer Network Slice Lifecycle Management
EDN Edge Data Network
EGMF Exposure Governance Management Function
GST Generic Network Slice Template
KPI Key Performance Indicator
KQI Key Quality Indicator
MnS Management Service
MNO Mobile Network Operator
NEF Network Exposure Function
NEST Network Slice Template
NOP Network Operator
NSCE Network Slice Capability Enablement
NSaaS Network Slice as a Service
NSI Network Slice Instance
NSSI Network Slice Subnet Instance
NWDAF Network Data Analytics Function
NSACF Network Slice Admission Control Function
NSC Network Slice consumer
NSP Network Slice Provider
NSMF Network Slice Management Function
OAM Operation, administration and maintenance
QoE Quality of Experience
S-NSSAI Single Network Slice Selection Assistance Information
SLA Service Level agreement
VAL Vertical Application Layer |
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 plays a vital role in configuring and translating the slice API based on the per slice requirements to service APIs. Slice API configuration and translation procedures are specified in clause 9.3. |
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 specified in clause 9.4. |
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 of two procedures, which are specified in clause 9.6:
- Discovery of management service capabilities and related permissions (e.g. permitted CRUD operations) based on VAL server request;
- Discovery and exposure of new or modified management service capabilities based on changes at OAM. |
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 processed data to VAL servers. Network slice performance and analytics monitoring procedures are specified in clause 9.7. |
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 resource situation) need to be known at the server NSCE server to allow for pro-active slice (or slice subnet) modification trigger to avoid degradation of the application service performance. Predictive slice modification procedures are specified in clause 9.9. |
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 multiple slices sharing common network resources. Coordinated PLMN and PNI-NPN slice resource optimization procedures are specified in clause 9.10. |
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. Network slice adaptation for VAL application procedures are specified in clause 9.11. |
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 slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined, the NSCE server allocates proper network slice resources to support the application services. Slice related communication service lifecycle management exposure procedures are specified in clause 9.12. |
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 make slice modification decision if needed. Predictive slice modification in Inter-PLMN based slice service continuity procedures are specified in clause 9.13. |
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 application, can initiate a check with NSCE. The NSCE server can provide Network slice diagnostics details related to the identified event as specified in clause 9.14. |
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 slice fault management capability exposure is specified in clause 9.15. |
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 the VAL clients. Periodically alignment notifications are sent to VAL server for the slice requirements alignment. The Slice requirements verification and alignment capability exposure is specified in clause 9.16. |
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 delivery is specified in clause 9.17. |
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 SEAL service provider. With respect to NSCE, the NSCE server belongs to the SEAL provider (as stated in TS 23.434 [2] clause 5) who can be either the MNO itself, or the vertical customer (e.g. factory owner, automaker X) or the edge/cloud provider (e.g. hyperscaler) who provides such platform services related to slice capability exposure to the vertical customer on top of the MNO. Thus, NSCE can play different roles based on the business models. For example, NSCE server can be:
- deployed by NOP / MNO.
- deployed by an Edge / Cloud Provider. In this case, it is assumed that the NSCE server is acting as an authorized AF/AS.
- deployed by a vertical industry, which can be the end slice customer.
From business perspective, the following business model applies. In Figure 5-1, the different interactions among all the involved entities are provided. More specifically, in this model the end user is the consumer of the applications provided by the vertical/ASP and can have app-level service agreement with vertical/ASP(s).
The end user/UE also has a PLMN subscription arrangement with the MNO. The UE used by the end user is allowed to be registered on the MNO's network. MNO (via OAM) can have a slice SLA with the vertical / ASP, which is optional when vertical customer is the NSC. In addition, due to the involvement of a NSCE service provider, additional agreements can be possible between the NSCE server and VAL/ASP layer and the NOP/MNO(s):
- the enablement service agreement between VAL/ASP layer and the NSCE service provider include the agreement on the value-added services, which in case on NSaaS these are services related to the consumed slice from NOP. So, the end customer (VAL) subscribes to NSCE server for receiving additional services for optimizing the slice utilization. In case that the NSCE server is a NSP towards VAL customer, then such agreement can relate to slice SLA (for the slice provided by the NSCE server). When the NSCE server is part of the vertical, the service agreement between VAL/ASP layer and the NSCE service provider is internal to a single organization.
- the service agreement between MNO and NSCE service provider is for consuming 5GS services (and being also authorized to provide additional services on top). Such agreement could be also a slice SLA for the scenarios when NSCE server is the NSC of the MNO (in NSaaS model).
Figure 5-1: Business relationships
In case of shared RAN between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL) using the shared RAN via one or both operators.
In case of national roaming between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL). |
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 3GPP network management system(s) to consume network slice management services provided by MNO(s). The network management system(s) can belong to the same PLMN or different PLMNs on which the NSCE service provider offers its services.
[AR-6.2-4] The APIs interactions between the vertical application server(s) and NSCE server(s) shall conform to CAPIF as specified in 3GPP TS 23.222 [3].
[AR-6.2-5] The NSCE architecture shall support the NSCE server to communicate with one or more other NSCE server(s). |
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 support the interactions with 3GPP network management system to consume network slice lifecycle management service provided by MNO. |
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.
[AR-6.7-3] The NSCE architecture shall provide multiple slices coordinated resource optimization service between 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 servers, servers and servers that interact, conform to CAPIF as specified in 3GPP TS 23.222 [3].
NOTE: The authentication and authorization aspects related to VAL servers and NSCE enablers are out scope of this study and to be addressed by SA3, in TS 33.434[21]. |
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 applications. Since the slicing is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause. |
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 capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE-C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. It is assumed that the network slice capability enablement server is deployed at the 5G system domain. The network slice capability enablement server, acting as AF, may communicate with the 5G Core Network functions via NEF (N33) reference point (for interactions with PCF, NSACF, etc.). The network slice capability enablement server may interact with OAM system over NSCE-OAM reference point, as consumer in both NSaaS and NoP model defined in the clause 4.1.6 and clause 4.1.7 of 3GPP TS 28.530 [15] (for Network Slice Provisioning capabilities, Performance Assurance, Fault Supervision etc.).
NOTE: OAM interfaces and/or network slice information can be exposed to an authorized (trusted) third-party (NSCE) only after a contract has been signed between the MNO and this third-party. Whether and how CAPIF/EGMF can be used to expose management services (MnS) is up to SA5 decision.
Figure 7.2-2 illustrates the architecture for interconnection between NSCE servers.
Figure 7.2-2: Interconnection between NSCE servers
The NSCE server could interact with another NSCE server over NSCE-E reference point.
Figure 7.2-3 illustrates the architecture for inter-service communication between NSCE servers and other SEAL server.
Figure 7.2-3: Inter-service communication between NSCE server and other SEAL server
The NSCE server interacts with another SEAL server for inter-service communication over SEAL-X reference point. |
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 requirement change. This trigger may be due to an application QoS requirement change, a service operation change. The NSCE client may receive a network slice / DNN re-mapping notification from the NSCE server. The NSCE client may optionally notify the VAL client on the network slice / DNN re-mapping. |
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) over NSCE-C. Further, the NSCE client may provide a notification on the network slice adaptation upon successful adaptation of the slice to application mapping. |
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 providing a guidance on the route selection parameters (including the S-NSSAI and DNN mapping), as specified in 3GPP TS 23.502 [12] clause 4.15.6.10, 3GPP TS 23.503 [17] clause 6.6.2.2, 3GPP TS 23.548 [18] clause 6.2.4. |
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 applies for a certain network slice instance, the identifier of Network Slice instance is used, i.e. NSI ID as defined in TS 23.501 or ENSI. If used, the NSI ID is associated with S-NSSAI. |
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. geographical coordinates) or both.
NOTE: The NSCE server service area shall not smaller than the collection of slice(s) coverage area(s) the NSCE server can enable. |
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 requirements (latency, error rates, throughput, jitter,..)
Network slice related identifier(s)
M
Identifier of network slice for which the request applies
Application layer Service Profile
O
The properties of network slice related requirement. If Service Profile is known by the VAL server, it can be provided to the NSCE server. The GST defined by GSMA (see clause 2.2 in [5]) and the performance requirements defined in clause 7 TS 22.261 [6] are all considered as input for it.
Area of interest
O
The service area for which the requirement applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA). |
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 specific for NSCE service or generally applicable for CAPIF is not specified in this release.
For de-registration of the VAL server, the VAL server triggers the CAPIF Offboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.2. |
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 APIs or enabler layer/SEAL provided APIs) and can be mapped to particular slice instances. The slice APIs can be a bundled or combined API comprising of different types of APIs, which will be used to expose the telco (5GS/SEAL)-provided services as needed by the applications of the slice customer. Each slice API may be configured per network slice instance. |
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 (from both management and control plane). In particular, a slice API consists of telco-provided/platform dependent service APIs (e.g., NEF, OAM, SEAL, etc), and provides an abstraction/simplification on top of them. The VAL server-initiated Configuration Update procedure covers the scenario where a trigger event occurs (e.g., QoS degradation, slice load) and the mapping configuration or the slice API configuration needed to be changed. In this scenario, the slice enabler updates the configuration of the API and provides a notification to the VAL server.
These two procedures for the initial configuration and the configuration update are covered in 9.3.2.1 and 9.3.2.2 respectively. |
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 server acts as AEF, and the authorization is obtained from CCF.
NOTE: The NSCE server provided service can serve any slice.
2. The NSCE server maps the VAL application requirement to a slice API which includes a list of APIs which is needed to be consumed as part of this service capability exposure.
The NSCE server may also store the mapping of the slice API to the service API list and per service API information (e.g. data encoding, transport technology, API protocol and versions)
3. The NSCE server registers to consume the corresponding APIs from the 5GS (NEF and OAM) and SEAL service producers. The NSCE server registers to the following:
- to consume NEF monitoring events as specified in 3GPP TS 29.522 clause 5 e.g., network monitoring, slice status, analytics exposure, etc
- to consume PM services and KPI monitoring from OAM
- to consume SEAL services based on 3GPP TS 23.434
If CAPIF is used, the subscription/registration requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. The preferred network slice related identifier received in step 1 is used by the NSCE server in requesting CCF authorization to consume the service provided by 5GS/SEAL.
4. The NSCE server sends a VAL application requirement response to notify on the result of the request and indicate whether the configuration of slice API is possible or not.
5. The NSCE server sends the slice API information notification to the VAL server. |
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 (application server relocation to different EDN/DN, UE mobility to different EDN, application change of behaviour).
Figure 9.3.2.1.3-1: Slice API configuration update
1. The VAL server sends a VAL server-initiated configuration update request to the NSCE server.
2. The NSCE server processes the trigger event and checks the feasibility of such change and updates the mapping of service APIs to the slice APIs. One criterion for the update of the mapping is, if possible, to avoid changing the slice API configuration, which can be achieved by the re-mapping of the underlying service APIs
3. The NSCE server updates the subscription/registration to the underlying 5GS and SEAL service producers, if an update on the service APIs (e.g., NEF APIs, SEAL APIs, OAM provided APIs) is needed.
4. The NSCE server sends a VAL server-initiated configuration update response, containing the new slice API information, if an update has been carried out by the NSCE server. |
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 fetches the service APIs to be invoked based on the slice API configuration and performs invocation requests to the corresponding service API providers.
Figure 9.3.2.2-1 illustrates the procedure of the slice API translation based on the initial configuration.
Pre-conditions:
1. The VAL server has registered to receive NSCE services.
2. The slice API mapping to the VAL server has been performed based on 9.3.2.1.2 step 2 and the slice API information is provided to the VAL server based on 9.3.2.1.2 step 5.
Figure 9.3.2.2-1: Slice API translation
1. The VAL server sends a slice API invocation request to the NSCE server
2. The NSCE server checks that the user is authenticated and authorized to perform the slice API invocation and maps the requested slice API to a service APIs. If CAPIF is used, the NSCE server acts as AEF, and the authorization is obtained from CCF.
NOTE: The NSCE server provided service can serve any slice.
3. The NSCE server generates a trigger for service API invocation requests to all the service APIs within the slice API.
4. The NSCE server performs the corresponding service API invocation procedures based on CAPIF or via performing requests to the corresponding service API providers, which are mapped to the slice API.
If CAPIF is used, the requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. The requested network slice related identifier received in step 1 is used by the NSCE server in requesting CCF authorization to consume the service provided by 5GS/SEAL.
5. The NSCE server sends a slice API invocation response to the VAL server, based on the result of the service API invocation response(s) of step 4.
9.3. 3 Information flows |
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 application requirement request
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server
List of service requirement(s)
M
The VAL application requirements pertaining to the slice(s) as defined in table 9.1.1.1-1
Time validity
O
The time validity of the request
NOTE: One of this shall be present |
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
(see NOTE)
Indicates the cause of failure
NOTE : May only be present if the result is failure. |
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: Slice API information notify
Information element
Status
Description
Slice API info
M
The information for the configured slice API |
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
Identifier of the network slice for which the API configuration update is requested
Trigger Event Details
M
The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be:
• the UE mobility to a different service area (outside the original area of interest),
• application server migration to different edge/cloud platform,
• service API unavailability,
• VAL application QoS requirements change |
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 configuration has been changed.
> Updated slice API information
M
The information for the updated slice API
Configuration not changed
O
(see NOTE)
The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be
> Cause
M
Indicates the reason for not changing the slice configuration. The reason may be that no change was needed, failure of changing in 5GS/SEAL or other (e.g. server internal error).
NOTE: Only one of these IEs is present in the message. |
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 obtained before initiating the slice API invocation request
Slice API identification
M
The identification information of the slice API for which invocation is requested. The slice API identification is part of the specific slice API invocation request. |
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 cause of failure
NOTE: May only be present if the result is failure. |
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 /Response
Slice_API_configuration_update
VAL server
Request /Response
Slice_API_information_notify
VAL server
Notify
SS_NSCE_Slice_ApiInvocation
Slice_API_invocation
VAL server
Request /Response |
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 lifecycle management recommendation/decision, triggering the network slice lifecycle management operations, notifying the consumer about the network slice information. |
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 server has authenticated and authorized to the capabilities trigger the network slice LCM operations.
3. There is signed contract for LCM between the entities using VAL server and entities using NSCE.
Figure 9.4.2.1-1: Application layer network slice lifecycle management
1. The VAL server sends the application layer network slice lifecycle management (AppLayer-NS-LCM) subscribe request to NSCE server, with network slice requirements from VAL server/consumer (e.g. delay, throughput, load, the maximum number of users supported, etc.). The request can indicate whether the notification is needed before performing the AppLayer-NS-LCM. The request can also indicate the trigger conditions, such as by providing the monitored parameters and the corresponding thresholds as described in clause 9.4.3.2.
2. After receiving the request, the NSCE server checks that the user is authenticated and authorized to perform the corresponding AppLayer-NS-LCM operations, and filters the unauthorized requests, if any.
3. According to network slice requirements and/or the trigger conditions, NSCE server triggers the provision of network slice status and QoE metrics. If the trigger conditions are not indicated in the subscription, the NSCE server can help to configure an appropriate trigger condition, such as report period or thresholds.
3a. The network slice status could be collected through subscribing or requesting to 5GS. List of network slice status parameters to be collected are:
- Network Slice load statistics information, and/or Network Slice load predictions information from NWDAF/NEF as defined in TS 23.288 Table 6.3.3A.
- Performance metric in the performance data file from OAM as defined in clause 11.3 of TS 28.532 [7].
3b. Also, the NSCE server could get the information of QoE metrics from the application layer domain by QoE metric subscribe as described in clause 9.4.3.5.
4. Once authenticated and authorized, the NSCE server sends the AppLayer-NS-LCM response to the VAL server.
5. The NSCE server may process and combine the collected network slice status and QoE metrics, if needed. The NSCE server may process and combine the parameters in the trigger conditions, if multiple trigger conditions were provided. Once the trigger condition or the combination of trigger conditions are met which indicating the network slice requirements from VAL server is not satisfied, the NSCE server determines whether and what network slice LCM operations should be taken based on requirements from VAL server/consumer and network slice status and QoE metrics, and makes the decision(s)/recommendation(s), such as modifyNsi/AllocateNsi/DeallocateNsi request as specified in TS 28.531 [8].
6. Optionally, if it is indicated in the request to notify the VAL server/consumer before performing the AppLayer-NS-LCM, the NSCE sends the network slice LCM recommendation(s) with network slice information to VAL server, to see whether takes the recommendation(s) or not.
7. Optionally, the VAL server sends the response to NSCE server.
8. Based on decision made by VAL server or NSCE server, the NSCE server sends the network slice LCM request to the OAM.
9. According to the corresponding operation(s) result, the NSCE server sends the response to the VAL server. |
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 server ID).
Security credentials
M
Security credentials resulting from a successful authorization for the NSCE service.
Service requirement
M
The VAL application requirements pertaining to the slice as defined in table 9.1.1.1-1
AppLayer-NS-LCM notification indication
M
Indicates whether to notify the VAL server/consumer about the AppLayer-NS-LCM
>AppLayer-NS-LCM notification address (see NOTE)
O
The address (e.g. URL) of the consumer that can receive the AppLayer-NS-LCM notification
Trigger condition
O
Indicates the monitored parameters and the corresponding thresholds which could trigger the AppLayer-NS-LCM.
The supported trigger conditions are:
- The Network Slice load exceeds the threshold.
- The collected Network Slice performance exceeds the threshold;
- The collected QoE exceeds the threshold.
Proposed expiration time
O
Proposed expiration time for the subscription
NOTE: When the AppLayer-NS-LCM recommendation notification is needed, AppLayer-NS-LCM notification indication should be provided. |
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
(see NOTE)
Indicates the cause of AppLayer-NS-LCM request failure
NOTE: May only be present if the result is failure. |
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 the AppLayer-NS-LCM request was successful.
>network slice information
M
Network slice information (i.e. NEST) with network slice identifier(i.e. S-NSSAI)
Failure response (see NOTE)
O
Indicates that the AppLayer-NS-LCM request failed.
> Cause
O
Indicates the cause of AppLayer-NS-LCM request failure
NOTE: One of these IEs shall be present in the message. |
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 resulting from a successful authorization.
Notification Target Address
O
The Notification Target Address (e.g. URL) where the notifications destined for the requestor should be sent to.
Subscription ID
M
Identifier of the subscription.
Event Filter
M
The associated filter on a network slice to be notified
> Network slice related Identifier(s)
M
Identifier of the interested network slice
> VAL service ID
O
Indicator of the interested application (i.e. App ID)
>QoE type indicator
M
QoE metric type including latency, throughput, jitter, etc.
Event Reporting information
M
Information indicates how the notification is supposed to be sent, threshold based or the notification is periodical or the Immediate reporting is requested
>Threshold
O
Threshold of QoE metrics
>Reporting period
O
Indicating the metrics reporting period
>Immediate reporting flag
O
Indicating the request needs immediate reporting or not
Proposed expiration time
O
Proposed expiration time for the subscribe |
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 identifier corresponding to the subscription.
>QoE metrics report
O
(see NOTE2)
List of result values for the observed or computed QoE metrics value if the immediate reporting is needed.
> Cause
O
(see NOTE3)
Indicates the cause of QoE metrics request failure
NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: May only be present if the result is success.
NOTE 3: May only be present if the result is failure. |
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 the observed or computed QoE metrics value. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.