Apparatus for network slicing and slice management to support multi-slice service

Abstract

The invention provides a device for network slicing and a device for network slicing management, which can be used for supporting and optimizing multi-slice service. The apparatus provides functionality enhancements within different layers of a network architecture. The device applied to the network slicing is used for determining at least two related communication service flows for a service and binding the at least two related communication service flows. Furthermore, the apparatus is used to generate and preferably reveal binding information. The device for network slice management is used for converting service requirements of tenants / applications into joint performance parameters in related network slice instances. Further, it is used to determine a resource allocation for the at least one network slice instance based on the joint performance parameter.

Description

[0001] This application is a divisional application of a Chinese patent application with application number CN201880089730.X filed on February 19, 2018, and application name “Device for network slicing and slice management to support multi-slice services”. The entire contents are incorporated into this application by reference. Technical Field

[0002] The present invention relates to an apparatus and method for network slicing, in particular an apparatus and method for identifying and utilizing correlations between communication service flows applied to network slice instances. In addition, the present invention relates to an apparatus for network slice management, in particular an apparatus for joint performance management of related network slice instances. Background Art

[0003] The concept of network slicing is introduced in 5G to address various different requirements from multiple vertical industries that assume a shared network infrastructure (i.e. resources, devices, physical links, etc.). Network services can be customized according to the needs of different use cases, thereby improving network operation efficiency. In 5G networks, services are implemented through network slicing. Network slices are instantiated and managed by the network management system.

[0004] The 5GPPP Architecture WG summarized the overall 5G slicing architecture determined by the 5GPPP Phase 1 project as follows Figure 7 As shown: "At the service level, the slice provider provides a Northbound Interface (NBI) to the tenant, where the tenant can request / modify / monitor / control the slice based on the service level agreement (SLA) with the slice provider. At the network level, this means that such on-demand NFs can be customized for different devices based on the required support level. The network operating system maps logical network slices to the "resource and function" level, for example, using various (programmable) controllers, as well as virtualization technologies."

[0005] 3GPP defines some basic network slice types, such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra-reliable low latency communication (URLLC), where each network slice type is designed for a group of services with similar service requirements. However, some applications / services may require network functions implemented by multiple network slice types at the same time. For example, in the case of remote driving, Figure 8As shown, high-definition (HD) video data requires high throughput, which can be supported by eMBB slices. At the same time, on-board sensor data and vehicle control signaling require low latency and high reliability, which can be supported by URLLC slices. Similarly, virtual reality (VR) / augmented reality (AR) applications may require eMBB slices to transmit HD video content, while URLLC slices may be required to transmit key sensor data (such as header direction), which determines the actual video content to be transmitted to the user.

[0006] In this case of using multiple slices, different slices can be completely isolated and their performance can be independent of each other. However, the actual performance of each individual independent slice will affect the same service. This inevitably leads to the correlation between the requirements of different network slices for the same service / application. More specifically:

[0007] 1. The performance of one slice affects the key performance indicators (KPIs) required by another slice. For example, in remote driving / AR / VR, the long latency of the video control (viewing direction) signal makes HD streaming video transmission from the vehicle scene useless.

[0008] 2. In practice, the KPI (e.g., latency) budget is shared across slices. The user experience is affected by the total latency from multiple slices (e.g., in the above use case, the latency of control signaling to the vehicle and the latency of video / sensor reporting from the vehicle).

[0009] The current 3GPP architecture does not support any cross-slice optimization / intra-slice coordination aspects.

[0010] The current 3GPP SA5 specifies Fig. 9 The telecommunication management architecture shown in Figure 1. The Communication Service Management Function (CSMF) is responsible for converting communication service-related requirements into network slice-related requirements. The Network Slice Management Function (NSMF) is responsible for the management and orchestration of the Network Slice Instance (NSI) and obtains the network slice subnet-related requirements from the network slice-related requirements. The Network Slice Subnet Management Function (NSSMF) is responsible for the management and orchestration of the Network Slice Subnet Instance (NSSI).

[0011] The current specification focuses on service management of each slice (through NSMF and NSSMF). However, cross-slice optimization based on service relevance of different slices is not considered.

[0012] The 5GPPP Phase I project 5G-NORMA only provides partial cross-slice management and orchestration capabilities by introducing the Inter-Slice Resource Broker (ISRB). "ISRB handles resource allocation, dynamic provisioning, and management of shared resources for different slices within the management domain it controls." However, this approach only focuses on cross-slice resource management and does not explain how cross-slice management is accomplished across different subnets. In addition, the 5GPP Phase II project 5G-MoNArch began work on mapping the 5G-NORMA architecture to the 3GPP SA5 architecture and proposed cross-slice orchestration management capabilities. However, a detailed design and system framework are missing. Summary of the invention

[0013] In view of the above problems and shortcomings, the present invention aims to improve the implementation methods and methods of traditional multi-slice services. The purpose of the present invention is to provide a complete framework that supports the optimization of multi-slice services. A specific purpose of the present invention is to identify and use the correlation between slice instances provided for the same service. In addition, the present invention aims to support inter-slice optimization taking into account multiple subnets. Another purpose of the present invention is to map service requirements into relevant KPIs of multiple associated network slice instances.

[0014] The objects of the invention are achieved by means of the solutions provided in the attached independent claim. The dependent claims further define advantageous embodiments of the invention.

[0015] Specifically, the present invention provides some functional enhancements, which support multi-slice services in different layers (levels) of the network architecture to provide a complete framework optimized in view of multi-slice services. Specifically, functional enhancements are provided in the network layer, management coordination (MANO) layer and service layer of the network architecture respectively.

[0016] Service correlation using network slicing can help improve network efficiency and enhance user experience.

[0017] A first aspect of the present invention provides a device for network slicing, which is used to determine at least two related communication service flows for a service; and to bind at least two related communication service flows and generate binding information.

[0018] For the purposes of this document, a communication traffic flow may be, or may include, a packet data unit (PDU) session, a GPRS tunneling protocol (GTP) data flow, and / or a quality of service (QoS) flow. A communication traffic flow is particularly used for a network slice instance, i.e., is related to a network slice instance or is part of a network slice instance.

[0019] Correlated communication network flows are communication network flows that are dependent on each other with respect to one or more performance parameters. Performance parameters, such as KPIs, are parameters that provide requirements for communication network flows, such as delay requirements, bandwidth requirements, reliability requirements. It can also be a function based on at least one of the above examples. For example, if two communication network flows are correlated with respect to delay requirements, this may mean that the two communication network flows share a delay budget defined by the delay requirements. The correlation between the two different slice instances is inherent to the two correlated communication network flows of the two different slice instances.

[0020] The binding information includes at least an identifier (ID) of the communication service flow.

[0021] For the purposes of this document, services include communication services, such as requests to establish one or more communication traffic flows, in particular PDU sessions, requests to establish one or more logical communication networks. For the first aspect, services may specifically refer to services requested from a terminal device (e.g., from a single user of the network).

[0022] The device of the first aspect presents an important part of a complete framework that can support multi-slice service optimization. The device can particularly identify and expose the correlation between slice instances and / or communication service flows for the same service. By generating binding information based on the identified correlation, the device can perform cross-slice management and optimization, and even consider multiple subnets for inter-slice optimization. The generated binding information helps to significantly improve network efficiency and improve user experience.

[0023] In one embodiment of the first aspect, the apparatus is used to receive a service request, in particular a request from a terminal device, wherein the determination is based on the request; and / or wherein the determination is based on preconfigured information, in particular information from a tenant and / or an application and / or a network.

[0024] Accordingly, various alternatives are provided for efficiently determining a correlation between at least two communication flows.

[0025] In another embodiment of the first aspect, the request and / or preset information for the service includes information about at least two related communication service flows. Such information can be any one / any combination of the following: PDU session ID, flow ID, source / destination IP address, source / destination port, application ID, etc.

[0026] Accordingly, the device may be directly informed which communication service flows are considered to be related, thereby binding these service flows.

[0027] In another embodiment of the first aspect, the service request includes information of a session for each communication service flow, and wherein the request also includes network slice selection assistance information for each session and / or the identity of each session.

[0028] In this embodiment, the terminal device can determine different network slices to be used for the service. Different network slices are based on different communication service flows. The session can be, for example, a PDU session. The request can also include information about multiple sessions of one or more communication service flows belonging to the same network slice instance. The network slice selection assistance information can be single network slice selection assistance information (S-NSSAI) specified by 3GPP, for example, as a slice identifier, and indicates performance correlation between corresponding communication service flows.

[0029] In another embodiment of the first aspect, the device is used to store a session list associated with slice selection assistance information and / or a list of session identifiers applied to at least two related communication service flows.

[0030] Thus, the correlation between at least two related communication service flows can be maintained and adapted according to the device requirements. Any changes to the list can be revealed. The above-mentioned embodiments are particularly used in the binding of at least two communication service flows.

[0031] In another implementation of the first aspect, the service request includes one or more service requirements, and the apparatus is configured to determine at least two related communication traffic flows based on the one or more service requirements.

[0032] In this embodiment, the device maps services to different network slices based on different communication flows according to overall business needs.

[0033] In another embodiment of the first aspect, the device is used to expose the binding information in at least one network layer and / or to at least one other network entity, in particular an access network function, a core network function, a management function, one or more applications, and / or to one or more network functions of the device.

[0034] Exposing binding information means making it available. Specifically, the binding information may be exposed directly to an entity, function, or application, or may be exposed indirectly through another network function. Any changes to the binding information may be exposed immediately, or the binding information may be exposed periodically. Exposing the binding information allows other network entities to exploit correlations between communication traffic flows to improve support for multi-chip services.

[0035] In another implementation of the first aspect, the apparatus is configured to authenticate a received service request and map the service to at least two related communication traffic flows.

[0036] In this way, the device can determine the different network slices to be used for the service. As described above, this can be triggered by the terminal device or the device respectively.

[0037] In another embodiment of the first aspect, the bundling of at least two related communication service flows is performed at the network layer, in particular by means of an inter-slice coordination function ISCF of the device.

[0038] For the above implementation, there may be different implementation options at the network layer: As a first option, a new network function may be implemented and connected to a service-based architecture (SBA). As a second option, sub-functions of existing network functions may be implemented, where the network functions are connected to the SBA (e.g., access and mobility management function (AMF), policy control function (PCF), or SMF). In particular, these functions may be as defined in '3GPP TS23.501 System Architecture for 5G System Stage 2 (Rel.15)'.

[0039] A second aspect of the present invention provides a device for network slice management, which is used to convert the service requirements of tenants / applications into joint performance parameters in relevant network slice instances; based on the joint performance parameters, determine resource allocation for at least one of the network slice instances.

[0040] Service requirements may relate to one or more services. For the second aspect, services may specifically refer to communication services requested by tenants (e.g., vertical industries using an operator's network) and / or applications, in particular applications provided by customers, such as vertical industries. Performance parameters (similar to the above definition) are parameters that provide requirements for one or more network slice instances. Specifically, a parameter may be a KPI. For example, a performance requirement may be the average latency of all communication service flows in a single network slice instance. KPIs may include latency, reliability, bandwidth, etc. As described above, the relevance of related network slice instances may be derived from the relevance of communication service flows for these network slice instances. The service requirements (e.g., KPIs) of related network slice instances are inherent to the communication service flows of the related network slice instances.

[0041] Accordingly, the device of the second aspect realizes mapping of service requirements to relevant KPIs of multiple associated network slice instances, thereby supporting a framework for optimizing multi-slice services. Specifically, by utilizing the correlation of network slice instances for resource allocation, network efficiency is improved and user experience is improved.

[0042] In one embodiment of the second aspect, the device is used to expose joint performance parameters to one or more functions in the network layer, in particular the radio access network RAN ​​function, PCF, SMF, AMF.

[0043] Therefore, these functions can consider joint performance parameters, for example, applying cross-slice policies (SMMF / PCF), applying inter-slice optimization (RAN) or adjusting QoS parameters (PCF). Accordingly, support for multi-slice services can be improved.

[0044] In another embodiment of the second aspect, the device is used to instantiate at least two related network slice instances for a service based on resource allocation.

[0045] Slice instances can serve the same service with optimized performance (especially in terms of network efficiency). Therefore, a better user experience can be provided.

[0046] In another embodiment of the second aspect, the device is used to instantiate at least two sub-slices in at least one related network slice instance based on resource allocation.

[0047] Accordingly, the device supports slice instantiation and optimization, even taking subnets into account.

[0048] In another implementation of the second aspect, the device is used to receive communication service flow binding information from a network layer.

[0049] For example, the apparatus of the second aspect may obtain binding information from the apparatus of the first aspect. The apparatus of the second aspect may use the binding information to identify related communication service flows.

[0050] In another embodiment of the second aspect, the device is used to monitor joint performance parameters and / or resource allocation across at least two related network slice instances and / or across two related communication service flows.

[0051] Monitoring performance parameters and / or performance parameters of each communication service flow across different slice instances is a prerequisite for improving cross-slice optimization.

[0052] In another embodiment of the second aspect, the device is used to expose joint performance parameters and / or resource allocation to tenants / applications across at least two related network slice instances and / or across at least two related communication service flows.

[0053] This can be done, for example, via a Northbound Interface (NBI). Thus, tenants / applications can utilize joint performance parameters.

[0054] In another embodiment of the second aspect, the device is used to apply joint QoS processing to at least two related network slice instances and / or at least two communication service flows based on joint performance parameters and / or binding information.

[0055] QoS processing may include resource allocation and network configuration based on KPI monitoring results. Accordingly, an optimized QoS for the service may be provided.

[0056] In another embodiment of the second aspect, the device is used to manage at least two related network slice instances and / or at least two sub-slices based on joint performance parameters and / or resource allocation, in particular by applying joint resource management across at least two related network slice instances and / or at least two sub-slices; and / or perform service optimization across at least two related network slice instances and / or at least two sub-slices in at least two related network slice instances.

[0057] Accordingly, optimized support for multi-slice services can be provided, improving user experience accordingly. One sub-slice can belong to one network slice instance, while another can belong to another network slice instance.

[0058] A third aspect of the present invention provides a method for network slicing, comprising determining at least two related communication service flows for a service; and binding at least two related communication service flows and generating binding information.

[0059] In an embodiment of the third aspect, the method comprises receiving a service request, in particular a request from a terminal device, wherein the determination is based on the request; and / or wherein the determination is based on preconfigured information, in particular information from a tenant and / or an application.

[0060] In another implementation of the third aspect, the request and / or pre-configuration information for the service includes information about at least two related communication traffic flows.

[0061] In another embodiment of the third aspect, the service request includes information about a session for each communication service flow, and wherein the request also includes network slice selection assistance information for each session and / or the identity of each session.

[0062] In another embodiment of the third aspect, the method includes storing a list of sessions associated with slice selection assistance information and / or session identifiers for at least two related communication service flows.

[0063] In another implementation of the third aspect, the service request includes one or more service requirements, and the apparatus is configured to determine at least two related communication traffic flows based on the one or more service requirements.

[0064] In another embodiment of the third aspect, the method includes exposing the binding information in at least one network layer and / or to at least one other network entity, in particular an access network function, a core network function, a management function, one or more applications, and / or to one or more network functions.

[0065] In another embodiment of the third aspect, the method includes authenticating a received service request; and mapping the service to at least two related communication traffic flows.

[0066] In another embodiment of the third aspect, the binding of at least two related communication service flows is performed at the network layer, in particular through the inter-slice coordination function ISCF.

[0067] The method of the third aspect and its embodiments respectively achieve the same advantages and effects as the apparatus of the first aspect and its embodiments, and the same definitions and examples also apply.

[0068] A fourth aspect of the present invention provides a method for network slice management, which includes converting the service requirements of tenants / applications into joint performance parameters in relevant network slice instances; and determining resource allocation for at least one of the network slice instances based on the joint performance parameters.

[0069] In one embodiment of the fourth aspect, the method includes exposing joint performance parameters to one or more functions in the network layer, in particular RAN functions, PCF, SMF, AMF.

[0070] In another embodiment of the fourth aspect, the method includes instantiating at least two related network slice instances for a service based on resource allocation.

[0071] In another embodiment of the fourth aspect, the method includes instantiating at least two sub-slices in at least one related network slice instance based on resource allocation.

[0072] In another embodiment of the fourth aspect, the method includes receiving communication service flow binding information from a network layer.

[0073] In another embodiment of the fourth aspect, the method includes monitoring joint performance parameters and / or resource allocation across at least two related network slice instances and / or across two related communication service flows.

[0074] In another embodiment of the fourth aspect, the method includes exposing joint performance parameters and / or resource allocation to the tenant / application across at least two related network slice instances and / or across at least two related communication service flows.

[0075] In another embodiment of the fourth aspect, the method includes applying joint QoS processing to at least two related network slice instances and / or at least two communication service flows based on joint performance parameters and / or binding information.

[0076] In another embodiment of the fourth aspect, the method includes managing at least two related network slice instances and / or at least two sub-slices based on joint performance parameters and / or resource allocation, in particular by applying joint resource management across at least two related network slice instances and / or at least two sub-slices; and / or performing service optimization across at least two related network slice instances and / or at least two sub-slices in at least two related network slice instances.

[0077] The method of the fourth aspect and its embodiments respectively achieve the same advantages and effects as the apparatus of the second aspect and its embodiments, and the same definitions and examples also apply.

[0078] It should be noted that all devices, elements, units and devices described in this application can be implemented with software or hardware elements or any type of combination thereof. All steps performed by various entities described in this application and functions performed by various entities are intended to represent that the corresponding entity is suitable for or used to perform the corresponding steps and functions. Even if in the description of the following specific embodiments, a specific function or step fully performed by an external entity is not reflected in the description of the specific detailed elements of the entity that performs the specific step or function, it should be clear to those skilled in the art that these methods and functions can be implemented in the corresponding software or hardware elements or any type of combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] The above aspects and implementations of the present invention will be explained in the following description of specific embodiments in conjunction with the accompanying drawings, wherein

[0080] Figure 1 A device for network slicing according to an embodiment of the present invention is shown.

[0081] Figure 2 A method for network slicing according to an embodiment of the present invention is shown.

[0082] Figure 3 A device for network slice management according to an embodiment of the present invention is shown.

[0083] Figure 4 The functional enhancements provided by the framework of the present invention at different network layers and interfaces of the network architecture are shown.

[0084] Figure 5 PDU session establishment requested by a non-roaming and roaming UE is shown.

[0085] Figure 6 A reference network architecture suitable for use with the present invention is shown.

[0086] Figure 7 The overall 5G architecture determined by the 5G-PPP Phase 1 project is shown.

[0087] Figure 8 A remote driving use case is shown that includes communication of HD video data and vehicle sensor data.

[0088] Fig. 9 The 3SA5 telecommunications management architecture including CSMF, NSMF and NSSMF is shown. DETAILED DESCRIPTION

[0089] Figure 1 1 shows an apparatus 100 according to an embodiment of the present invention. The apparatus 100 is used for network slicing. The apparatus 100 may be located at least partially in a network layer 401 of a network architecture 400 (see Figure 4 ).

[0090] Specifically, the apparatus 100 is used to determine at least two related communication service flows 101 for a service. In addition, the apparatus 100 is used to bind 102 at least two related communication service flows 101 and generate binding information 103. The binding information 103 is specifically generated according to the binding of the communication service flows 101.

[0091] Advantageously, the apparatus 100 may make the generated binding information 103 available, for example, available in at least one network layer and / or available to at least one other network entity, in particular an access network function, a core network function, a management function, one or more applications, and / or one or more network functions available to the apparatus 100. Thus, the correlation between communication traffic flows 101 (and the correlation of the corresponding network slice instances) may be exploited in the network architecture 400 for optimizing multi-slice service support.

[0092] Figure 2 A method 200 according to an embodiment of the present invention, in particular a method for network slicing, is shown. The method 200 may be Figure 1 The device 100 shown is executed. Specifically, the method comprises a step 201 of determining at least two related communication service flows 101 for a service. The method further comprises a step 202 of binding 202 at least two related communication service flows 101 and generating binding information 102.

[0093] Figure 3 4 shows an apparatus 300 according to an embodiment of the present invention. The apparatus 300 is used for network slice management. The apparatus 300 may be at least partially located in the service layer 403 and / or the MANO layer 402 of the network architecture 400 (see Figure 4 ). Figure 3 The device 300 and Figure 1The devices 100 can be interconnected in the network architecture 400, particularly for transmitting information (e.g., binding information 102) across different layers 401, 402, 403 of the network architecture 400, or can even form a single device or system across different layers 401, 402, 403 of the network architecture 400.

[0094] The apparatus 300 is particularly configured to convert a service requirement 301 of a tenant / application (related to a service) into a joint performance parameter 302 in a related network slice instance 304. Each network slice instance may include at least one communication service flow. In addition, the apparatus 300 is configured to determine a resource allocation 303 for at least one of the network slice instances 304 (e.g., a resource allocation 303 for at least one communication service flow 101 in at least one network slice instance 304) based on the joint performance parameter 302. Thus, the apparatus 300 supports optimization of multi-slice services.

[0095] Figure 4 The functional enhancements achieved by implementing the apparatus 100 and the apparatus 300 as a network architecture 400 are generally shown. Specifically, functional enhancements are made to multi-slice service support in different layers 401, 402, and 403 of the network architecture 400. These enhancements include:

[0096] In the service layer 403, service management functions and service level agreements (SLA) for multi-slice service support are enhanced. Specifically, by implementing the device 300 (here exemplarily including the CSMF), the service requirements 301 of the tenant / application can be converted into at least one related (joint) performance parameter (here KPI) in the related network slice instance 304.

[0097] The service layer 403 specifically enhances the service level agreement (SLA) around the specification of service requirements 301. For example, service requirements 301 may be defined at a finer granularity than conventional granularity, including: if the service is to be implemented by multiple slices, joint KPIs 302 for each associated slice instance 304; service dependencies between associated slice instances 304; and overall service KPIs.

[0098] In the MANO layer 402, additional management orchestration (MANO) functions are implemented by the device 300 (here exemplarily including NSMF and NSSMF) to provide management support for inter-slice optimization (e.g., monitoring / configuring cross-slice (x-slice) instances, etc.). Specifically, the cross-slice MANO function can be defined at both the end-to-end (E2E) level (i.e., E2E x-slice MANO function) and the subnet level (i.e., domain x-slice MANO function). In addition, the x-slice functions at the above two levels can be enhanced to support resource management across associated slice instances 304, KPI monitoring across associated slice instances 304, and / or inter-slice service optimization across slice instances 304. For this purpose, the following can also be defined: Figure 4 New interfaces are shown (eg, for themselves and / or for slice-specific MANO functions).

[0099] For example, the apparatus 300 located within the MANO layer 402 may monitor a joint performance parameter 302 and / or a resource allocation 303 across at least two related network slice instances 304 and / or across two related communication traffic flows 101. In addition, the apparatus 300 may expose the joint performance parameter 302 and / or the resource allocation 303 to the tenant / application across at least two related network slice instances 304 and / or at least two related communication traffic flows 101. The apparatus 300 may also apply a joint QoS treatment to the at least two related network slice instances 304 and / or the at least two communication traffic flows 101 based on the joint performance parameter 302 and / or the binding information 102 exposed by the apparatus 100. The apparatus 300 may also be used to manage the at least two related network slice instances 304 and / or the at least two sub-slices by applying a joint resource management across the at least two related network slice instances and / or the at least two sub-slices based on the joint performance parameter 302 and / or the resource allocation 303. The device 300 can also perform service optimization across at least two related network slice instances 304 and / or at least two sub-slices in at least two related network slice instances 304.

[0100] In the network layer 401, the device 100 (here exemplarily including ISCF) implements additional network functions to provide association / binding of at least two related communication service flows 101 with related requirements, and a mechanism for distributing binding information 102. The device 100 performs association / binding of communication service flows 101, as well as generation and exposure of binding information 102 (e.g., exposure to different network entities / layers). Specifically, the device 100 can provide the binding information 102 from the network layer 401 to the device 300 located in the slice management (MANO) layer 402. Other potential enhancements include cross-slice policies (e.g., PCF) and cross-slice context sharing / monitoring data sharing (e.g., NWDAF) by UE / service / tenant.

[0101] In addition, interface enhancements between and within different network layers 401, 402, 403 of the network architecture 400 are provided for support / optimization of multi-slice services. The interface enhancements may include the exchange of binding information 102 between the network layer 401 and the MANO layer 402 (i.e., slice association information), and / or the exchange of extended service requirements / performance reports (i.e., service requirement monitoring data) between the service layer 403 and the MANO layer 402, such as Figure 4 shown.

[0102] In the following, a more detailed example will be described Figure 1 The binding of the relevant communication service flow 101 in the device 100 (specifically in Figure 4 ISCF execution shown).

[0103] Identification of relevant communication service flows 101 (such as PDU sessions) of different network slice instances 304 is an important condition for performing services based on cross-slice instance 304 optimization. Therefore, the device 100 is advantageously configured to identify relevant communication service flows 101 and provide this information as binding information 102 to other network functions / management planes for service / network performance optimization. It is assumed here that the PCF receives application / service requirements 301 from the AF. The PCF can then determine one or more cross-slice policies at the flow level / PDU session level, for example, a QoS profile can be determined for associated QoS flows (e.g., ARP, 5QI), and / or a policy can be determined for associated PDU sessions (e.g., UPF selection, etc.).

[0104] Figure 5 As an example, a PDU session establishment requested by a user equipment (UE) for non-roaming and roaming with local breakout as defined in 3GPP TS23.502 V15.0.0 (2017-12) is shown. It usually includes:

[0105] 1. "From UE to AMF: NAS message (S-NSSAI, DNN, PDU Session ID, Request Type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request))."

[0106] 2. "The AMF selects the SMF as described in clause 4.3.2.2.3. If the request type indicates "initial request" or the request is due to a handover from EPS, the AMF stores the association of the S-NSSAI, PDU Session ID and SMF ID."

[0107] In order to support the binding of relevant communication service flows 101 related to the network slice instance 304, according to the present invention, Figure 5 The UE session management procedures provide the following enhancements:

[0108] UE 501 may send a PDU session establishment request to AMF 503 with multiple PDU sessions, and each PDU session may be associated with a respective S-NSSAI. For example, an application may have multiple IP addresses, and each IP address may be used for a PDU session with a different NSSAI. UE 501 may also use NSSP (Network Slice Selection Policy) to map an application to multiple slices.

[0109] Accordingly, an example modification for a legacy UE requested PDU session establishment could be (comments underlined):

[0110] 1. "From UE to AMF: NAS message ((S-NSSAI, DNN, PDU session ID, request type, old PDU session ID, N1SM container (PDU session establishment request)) List )”.

[0111] In a further embodiment, the UE 501 may send a PDU session establishment request to the AMF 502,

[0112] And can indicate the ID of the associated PDU session.

[0113] Accordingly, an example modification for a legacy UE requested PDU session establishment could be (comments underlined):

[0114] 1. "From UE to AMF: NAS message (S-NSSAI, DNN, PDU session ID, request type, old PDU session ID, Relationship PDU Session ID, N1 SM container (PDU session establishment request))”

[0115] AMF (ISCF) 503 optionally stores a list of related PDU Session ID, S-NSSAI, SMF ID associations.

[0116] Accordingly, an example modification for a legacy UE requested PDU session establishment could be (comments underlined):

[0117] 2. "The AMF selects the SMF as described in clause 4.3.2.2.3. If the request type indicates "initial request" or the request is due to a handover from EPS, the AMF stores the association of the S-NSSAI, PDU Session ID and SMF ID. In multiple related In case of PDU session, AMF stores a list of the above associations. ”

[0118] Next, we will compare Figure 5 A more detailed example describes Figure 1The device 100 provides binding information 102 of at least two related communication service flows 101 of the slice instance 304. In this embodiment, ISCF is implemented as a sub-function of AMF.

[0119] The AMF 503 provides binding information 102, such as related PDU sessions, to other network entities (e.g., to the PCF 506, SMF 505, Network Data Analysis Function (NWDAF), RAN 502, management plane, etc.).

[0120] In an example implementation, the AMF 503 provides the binding information 102 to other network functions using a service-based interface (SBI), as shown in the following table in 3GPP format (underlined comments).

[0121]

[0122] In another example implementation, the AMF 503 provides this information to the SMF 505 using the N11 interface. Accordingly, an example modification may be (comments underlined):

[0123] 3. From AMF to SMF: Nsmf_PDUSession_CreateSMContext request (SUPI, DNN, S-NSSAI, PDU session ID, Associate PDU Session ID , AMF ID, request type, N1 SM container (PDU session establishment request), user location information, access type, PEI, GPSI, subscription for PDU session status notification) or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN, S-NSSAI, PDU session ID, Associate PDU Session ID , AMF ID, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI).”

[0124] In another example implementation, the AMF 503 provides this information to the RAN 502 using the N2 interface. Accordingly, an example modification may be (comments underlined):

[0125] 12. AMF to (R)AN: N2 PDU session request (N2 SM information, Associate PDU Session ID , NAS message (PDU session ID, N1 SM container (PDU session establishment accept))).

[0126] An example usage of the exposed binding information 102 at different network functions may be as follows:

[0127] The SMF 505 may identify the instances 304 of the relevant QoS flows / PDU sessions (based on the binding information 102 received from the ISCF, and based on the mapping of local QoS flows to PDU sessions), and may apply the cross-slice policies from the PCF 506.

[0128] RAN 502 may receive relevant PDU session binding information 102 from AMF (ISCF) 503, may receive mapping from PDU sessions to QoS flows from SMF 505, and may apply inter-chip optimization from the RAN perspective.

[0129] Based on the monitored performance from one of the associated (related) slice instances 304 , the PCF 506 may adjust one or more QoS parameters for another slice instance 304 .

[0130] Next, the mapping of services to logical network slices will be described with a more detailed example. The mapping can be done by the tenant / customer himself or by the network (particularly the device 100 and / or 300 provided in the network).

[0131] If the mapping is done by the tenant / customer, the process can be as follows:

[0132] 1. Operators expose network functions based on different types of network slices (i.e. network slices as a service). Tenants / customers require multiple network slices for their services.

[0133] 2. The tenant / customer defines one or more service requirements for each slice.

[0134] 3. The tenant / customer asks the network to report the performance of all slices.

[0135] 4. In case the performance of a single network slice changes, the tenant / customer can adjust the requirements of each associated slice taking into account the E2E service requirements.

[0136] If the mapping is done by the network (particularly the device 100 and / or 300 provided in the network), the process may be as follows:

[0137] 1. The tenant / customer defines one or more overall service requirements.

[0138] 2. The network maps tenants / customer services to multiple slices (e.g., via CSMF)

[0139] 3. The network reports the overall performance of the service to the tenant / customer.

[0140] 4. In case the performance of a single network slice changes, the network adjusts the requirements of each associated slice.

[0141] Next, the method and process for instantiating and managing related slices considering multiple subnets will be described in detail. Figure 6 The reference architecture shown is used as an example to describe the details. However, similar processes can be derived for other architectures (such as 3GPP SA5, 5G-MoNArch architecture, 5GPPP architecture WG, etc.).

[0142] Step 1: Design a slice template (e.g., finer-grained service KPIs for multiple slices) and enable it.

[0143] Step 2: BSS sends the order (one or more associated services) to the communication service layer.

[0144] Step 3: The communication service layer converts the order into a slice initialization request (including multiple slices and correlation (binding) information 102)

[0145] Step 4: For each slice, SSS initializes E2E slice instance 304:

[0146] 4.1 Negotiate and confirm latency quotas with each DSM.

[0147] 4.2 Obtain launch parameters from the request, plan pool, and inventory, and generate an E2E slice launch plan.

[0148] 4.3 Divide the plan into several domain slice initialization requests (including slice correlation information) and send them to the DSM.

[0149] Step 5: DSM initializes the subslice instance:

[0150] 5.1 Generate a sub-slice initialization plan that takes into account slice dependencies and implement the plan.

[0151] 5.2 Report the initialization process to SSS.

[0152] Step 6: SSS subscribes to the KPI from DSM after the instance is initialized.

[0153] Step 7: DSM periodically reports KPIs to SSS, and considering slice dependencies, DSM performs local inter-slice optimization.

[0154] Step 8: SSS aggregates the KPIs into E2E KPIs and displays them on the KPI dashboard. Considering the slice dependencies, SSS performs cross-slice optimization.

[0155] The invention has been described in conjunction with various embodiments as examples and implementations. However, by studying the drawings, the present disclosure and the independent claims, a person skilled in the art can understand and implement other variations and implement the claimed invention. In the claims and in the specification, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. A single element or other unit may perform the functions of several entities or items recited in the claims. The fact that certain means are recited in mutually different dependent claims does not indicate that a combination of these means cannot be used in an advantageous implementation.

[0156] This application-related project has received funding from the European Union's 5G-MoNArch program under grant number 761445.

Claims

1. A device (100) for network slicing, for - determining at least two relevant communication traffic flows (101) for the service; and - Binding (102) the at least two related communication service flows (101) and generating binding information (103), the binding information comprising identifiers of the at least two related communication service flows, the at least two related communication service flows being bound at a network layer.

2. The device (100) according to claim 1, wherein The apparatus (100) is used to receive a service request, in particular a request from a terminal device, wherein the determination is based on the request; and / or wherein the determination is based on preconfigured information, in particular information from a tenant and / or an application and / or a network.

3. The device (100) according to claim 2, wherein The service request and / or the pre-configuration information comprises information about the at least two related communication traffic flows (101).

4. The device (100) according to claim 3, wherein The service request includes information about each session of the communication service flow (101), and wherein the request also includes network slice selection assistance information for each session and / or an identifier of each session.

5. The device (100) according to claim 4, used for -Storing a list of sessions associated with the slice selection assistance information and / or a list of session identifiers applied to the at least two related communication service flows (101).

6. The device (100) according to claim 1, wherein The service request includes one or more service requirements, and The device (100) is used to determine the at least two related communication traffic flows (101) based on the one or more service requirements.

7. The device (100) according to any one of claims 1 to 6, used for - exposing the binding information (103) in at least one network layer and / or to at least one other network entity, in particular an access network function, a core network function, a management function, one or more applications, and / or to one or more network functions of the device (100).

8. The device (100) according to any one of claims 1 to 7, used for - authenticating the received service request; and - Mapping said service to said at least two related communication traffic flows (101).

9. The device (100) according to claim 1 or 8, wherein The binding (102) of the at least two related communication traffic flows (101) is performed at the network layer, in particular by an inter-slice coordination function ISCF of the device (100).

10. An apparatus (300) for network slice management, Converting tenant / application service requirements (301) into joint performance parameters (302) in the relevant network slice instance (304); -Based on the joint performance parameter (302), determining a resource allocation (303) for at least one of the network slice instances (304).

11. The device (300) according to claim 10, used for - Exposing joint performance parameters (302) to one or more functions in the network layer, in particular RAN functions, PCF, SMF, AMF.

12. The device (300) according to claim 10 or 11, used for -Based on the resource allocation (303), instantiate at least two related network slice instances (304) for the service.

13. The device (300) according to any one of claims 10 to 12, used for -Based on the resource allocation (303), instantiate at least two sub-slices of at least one of the related network slice instances (304).

14. The device (300) according to any one of claims 10 to 13, used for - receiving communication service flow binding information (103) from the network layer.

15. The device (300) according to any one of claims 10 to 14, used for -Monitoring the joint performance parameter (302) and / or the resource allocation (303) across the at least two related network slice instances (304) and / or across the two related communication service flows (101).

16. The device (300) according to any one of claims 10 to 15, used for - Exposing the joint performance parameters (302) and / or resource allocation (303) to the tenant / application across the at least two related network slice instances (304) and / or across the at least two related communication service flows (101).

17. The device (300) according to claim 15 or 16, used for -Based on the joint performance parameters (302) and / or binding information (102), applying joint QoS processing to the at least two related network slice instances (304) and / or at least two communication service flows (101).

18. The device (300) according to any one of claims 13 to 17, used for - based on the joint performance parameter (302) and / or the resource allocation (303), managing the at least two related network slice instances (304) and / or the at least two sub-slices, in particular by applying joint resource management across the at least two related network slice instances (304) and / or the at least two sub-slices; and / or -Perform service optimization across the at least two related network slice instances (304) and / or at least two sub-slices of the at least two related network slice instances (304).

19. A method (200) for network slicing, comprising: - determining (201) at least two relevant communication traffic flows (101) for the service; and -Binding (202) the at least two related communication service flows (101) and generating binding information (102), the binding information comprising identifiers of the at least two related communication service flows, the at least two related communication service flows being bound at a network layer.

Images