WO2022170514A1

WO2022170514A1 - Dynamic network slices management

Info

Publication number: WO2022170514A1
Application number: PCT/CN2021/076357
Authority: WO
Inventors: Zhi Wang; Yigang Cai
Original assignee: Nokia Technologies Oy; Nokia Solutions And Networks Investment (China) Co., Ltd.
Priority date: 2021-02-09
Filing date: 2021-02-09
Publication date: 2022-08-18
Also published as: EP4292335A1; CN117121560A

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses and computer readable storage media of dynamic network slices management. The method comprises receiving, at a first network slices management device, a request for a target network slice; in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device. In this solution, a new Network slices management Function (NSMF) is introduced to leverage network slicing service provided by different network slices providers to serve network slicing service request from different applications with the best network slice according to the requirements. In this way, the service cost to both network slices provider and customer can be minimized and moreover the efficiency on network slicing management can be increased.

Description

DYNAMIC NETWORK SLICES MANAGEMENT

FIELD

Embodiments of the present disclosure generally relate to the field of telecommunication and in particular to a method, device, apparatus and computer readable storage medium of dynamic network slices management.

BACKGROUND

One of key commercial objectives of the future fifth generation (5G) is to enable network to support multiple service types on a common physical network infrastructure. In this way, 5G will act as a key enabler to growth markets in the future, such as Internet of Things (IoT) , Industry 4.0, Smart City, Public Safety and the new 5G applications such as Virtual Reality/Augmented Reality (VR/AR) , Machine Learning/Artificial Intelligence (ML/AI) and connected car.

Network slicing is the key technology to address above demands, which supports very diverse ranges of services with very different performance requirements on a common physical infrastructure. It allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then customized to meet the specific needs of applications, services, devices, customers or operators. Network slices may differ for supported features and network functions optimizations.

SUMMARY

In general, example embodiments of the present disclosure provide a solution of dynamic network slices management.

In a first aspect, there is provided a method. The method comprises receiving, at a first network slices management device, a request for a target network slice; in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device.

In a second aspect, there is provided a method. The method comprises receiving, at a central network slices management device and from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and in accordance with a determination that the target network slice is able to be provided by the second network slices management device, providing the target network slice from the second network slices management device to the first network slices management device.

In a third aspect, there is provided a first network slices management device. The first network slices management device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first network slices management device at least to receive a request for a target network slice; in the lack of the target network slice from the first network slices management device, send a message for detecting an availability of the target network slice from a second network slices management device; and in accordance with a determination that the target network slice is available, provide the target network slice from the second network slices management device.

In a fourth aspect, there is provided a central network slices management device. The central network slices management device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the central network slices management device at least to receive, from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and in accordance with a determination that the target network slice is able to be provided by the second network slices management device, provide the target network slice from the second network slices management device to the first network slices management device.

In a fifth aspect, there is provided an apparatus comprising means for receiving a request for a target network slice; means for in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and means for in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device.

In a sixth aspect, there is provided an apparatus comprising means for receiving, from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and means for in accordance with a determination that the target network slice is able to be provided by the second network slices management device, providing the target network slice from the second network slices management device to the first network slices management device.

In a seventh aspect, there is provided a computer readable medium having a computer program stored thereon which, when executed by at least one processor of a device, causes the device to carry out the method according to the first aspect.

In an eighth aspect, there is provided a computer readable medium having a computer program stored thereon which, when executed by at least one processor of a device, causes the device to carry out the method according to the second aspect.

Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure are presented in the sense of examples and their advantages are explained in greater detail below, with reference to the accompanying drawings, where

FIG. 1 illustrates an example system environment in which example embodiments of the present disclosure can be implemented;

FIG. 2 shows a signaling chart illustrating a process of dynamic network slices management according to some example embodiments of the present disclosure;

FIG. 3 shows a signaling chart illustrating a process of dynamic network slices management according to some example embodiments of the present disclosure;

FIG. 4 shows a flowchart of an example method of dynamic network slices management according to some example embodiments of the present disclosure;

FIG. 5 shows a flowchart of an example method of dynamic network slices management according to some example embodiments of the present disclosure;

FIG. 6 shows a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

FIG. 7 shows a block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish functionalities of various elements. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital reference signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as fifth generation (5G) systems, Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) new radio (NR) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR Next Generation NodeB (gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology. A RAN split architecture comprises a gNB-CU (Centralized unit, hosting RRC, SDAP and PDCP) controlling a plurality of gNB-DUs (Distributed unit, hosting RLC, MAC and PHY) . A relay node may correspond to DU part of the IAB node.

The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a subscriber station (SS) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. The terminal device may also correspond to Mobile Termination (MT) part of the integrated access and backhaul (IAB) node (a.k.a. a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

Although functionalities described herein can be performed, in various example embodiments, in a fixed and/or a wireless network node, in other example embodiments, functionalities may be implemented in a user equipment apparatus (such as a cell phone or tablet computer or laptop computer or desktop computer or mobile IoT device or fixed IoT device) . This user equipment apparatus can, for example, be furnished with corresponding capabilities as described in connection with the fixed and/or the wireless network node (s) , as appropriate. The user equipment apparatus may be the user equipment and/or or a control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functionalities include the bootstrapping server function and/or the home subscriber server, which may be implemented in the user equipment apparatus by providing the user equipment apparatus with software configured to cause the user equipment apparatus to perform from the point of view of these functions/nodes.

FIG. 1 shows an example system environment 100 in which embodiments of the present disclosure can be implemented. As shown in FIG. 1, the system environment 100 comprises network slices management devices 110-1, 110-2 and 110-3 (hereinafter may also be referred to as a first network slices management device 110-1, a second network slices management device 110-2 and a third network slices management device 110-3, respectively, or a first network slices management function 110-1, a second network slices management function 110-2 and a third network slices management function 110-3, respectively) . The network slices management devices 110-1, 110-2 and 110-3 can communication with each other. Each of network slices management devices 110-1, 110-2 and 110-3 may manage multiple network slices. For example, the network slices management device 110-1 manages network slices 121-1 to 121-N, the network slices management device 110-2 manages network slices 122-1 to 123-N and the network slices management device 110-3 manages network slices 123-1 to 123-N.

In the system environment 100, the network slices management devices 110-1, 110-2 and 110-3 may be implemented as a management entity. For example, each of network slices management devices 110-1, 110-2 and 110-3 may be implemented to be integrated with different network slices providers respectively. Alternatively, the network slices management devices 110-1, 110-2 and 110-3 can be implemented individually. As another option, the network slices management devices 110-1, 110-2 and 110-3 may also be implemented as software which can perform a network slices management function.

The system environment 100 may also comprise a central network slices management device 120-1 (hereinafter may also be referred to as a central network slices management function 120-1) , which can communication with the network slices management devices 110-1, 110-2 and 110-3 respectively. The central network slices management device 120-1 may manage the network slices in each of network slices management devices 110-1, 110-2 and 110-3.

In the system environment 100, an application 130 can request a certain network slice from a network slices management device 110-1, 110-2 or 110-3. The application 130 can also request a certain network slice from the central network slices management device 120-1. The application 130 can be considered as/implemented at a terminal device. The application 130 can be supported by a user, a customer or an enterprise.

Furthermore, the system environment 100 may further comprise a further central network slices management device 120-2 (hereinafter may also be referred to as a central network slices management function 120-2) . The further central network slices management device 120-2 may communication with a network slices management device 110-4 (hereinafter may also be referred to as a fourth network slices management function 110-4) and manage network slices in the network slices management device 110-4. The further central network slices management device 120-2 and the central network slices management device 120-1 may communication with each other.

Depending on the communication technologies, the system environment 100 may be a Code Division Multiple Access (CDMA) network, a Time Division Multiple Address (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency-Division Multiple Access (OFDMA) network, a Single Carrier-Frequency Division Multiple Access (SC-FDMA) network or any others. Communications discussed in the network 100 may conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like. Furthermore, the communications may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols. The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

As mentioned above, one of key commercial objectives of the future fifth generation (5G) is to enable network to support multiple service types on a common physical network infrastructure. In this way, 5G will act as a key enabler to growth markets in the future, such as Internet of Things (IoT) , Industry 4.0, Smart City, Public Safety and the new 5G applications such as Virtual Reality/Augmented Reality (VR/AR) , Machine Learning/Artificial Intelligence (ML/AI) and connected car.

The End-to End (E2E) network slice can be defined by enterprises by means of the support of network slicing technology. The E2E Enterprise network slices can be considered as a separate independent logical network E2E in a common infrastructure and may have the functionality and performance to support a specific industry sector and/or service. The E2E concept may span multiple network domains (e.g. radio, transport, core, service, etc…) , and in some cases more than one administrative domain.

For example, a customized network slice may require certain 5G network capability and requirements such as broadband, URLLC, accuracy, security, or any other specially required QoS to meet the needs of the network slice customer. The network slice may also support multiple service scenarios, such as IoT, Industry 4.0, smart city, V2V/V2X, entertainment, e-health, public security, e-education, etc.

An E2E network slice may consist of multitude of RAN-slice, Core-slice, Transport-slices and Service-slices and span multiple network domains. However, providing E2E network slice by single network slices provider may have the following issues. For example, a single network slices provider may not be able to provide all network capabilities required by the network slices customer. Furthermore, current solution of E2E network slice provided by a single network slices provider could not meet the demands on cost saving. Even if a network slices provider is very competitive on some domains, the network slices provider may still not have opportunity to provide the corresponding network slices to the customers without an efficient management of network slices.

Therefore, the present disclosure provides solutions of dynamic network slices management. In this solution, if a network slices management device receives a request of a network slice and fails to provide the network slice, the network slices management may transmit a message for detecting an availability of the network slice from another network slices management devices. If the network slices management device determines that the network slice from another network slices management devices is available, the network slices management device may provide the network slice from another network slices management devices. In this solution, a new Network slices management Function (NSMF) is introduced to leverage network slicing service provided by different network slices providers to serve network slicing service request from different applications with the best network slice according to the requirements. In this way, the service cost to both network slices provider and customer can be minimized and moreover the efficiency on network slicing management can be increased.

Principle and implementations of the present disclosure will be described in detail below with reference to FIG. 2, which shows a signaling chart illustrating a process 200 of dynamic network slices management according to some example embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the first network slices management device 110-1, the second network slices management device 110-2 and the third network slices management device 110-3 and the application 130 as illustrated in FIG. 1.

As shown in FIG. 2, the application 130 may transmit 205 a request for a target network slice to the first network slices management device 110-1. As described above, the first network slices management device 110-1 may manage multiple network slices. The first network slices management device 110-1, which may also be considered as a Network Slice Management Function (NSMF) , may maintain the network slicing service status in its own network by communicating with a network slice controller deployed in its network. The NSMF can be integrated with the network slice controller or arranged separately from the network slice controller.

After receiving the request, the first network slices management device 110-1 may calculate 210 the requirements of the application 130 based on the request. For example, first network slices management device 110-1 may obtain, from the request a description of the service provided by the target network slice and the corresponding capability associated with target network slice that the application 130 can supply.

If the first network slices management device 110-1 fails to provide the target network slice, the first network slices management device 110-1 may probe whether the target network slice can be provided by other network slices management devices.

In some example embodiments, the first network slices management device 110-1 may transmit 215, to the second network slices management device 110-2, a message for detecting an availability of the target network slice from the second network slices management device 110-2. If the second network slices management device 110-2 determines that the target network slice (for example, the network slice 122-1 as shown in FIG. 1) is able to be provided by the second network slices management device 110-2, the second network slices management device 110-2 may transmit 225, to the first network slices management device 110-1, a response indicating the target network slice is able to be provided by the second network slices management device 110-2.

In some example embodiments, the message may comprise property information associated with the target network slice. For example, the property information may comprise a description about a service provided by the target network slice. The description can indicate, for example, which capabilities the application can obtain from the service. The property information may also comprise a capability associated with the target network slice that the application 130 can supply. Hereinafter the capability can at least comprise network resources available for the service provided by the target network slice and cost afforded by the application 130 for the target network slice.

Similarly, the first network slices management device 110-1 may also transmit 220, to the third network slices management device 110-3, a message for detecting an availability of the target network slice from the third network slices management device 110-3. If the third network slices management device 110-3 determines that the target network slice (for example, the network slice 123-2 as shown in FIG. 1) is able to be provided by the third network slices management device 110-3, the third network slices management device 110-3 may transmit 235, to the first network slices management device 110-1, a response indicating the target network slice is able to be provided by the third network slices management device 110-3.

If the first network slices management device 110-1 receives the response indicating the target network slice is able to be provided by the second network slices management device 110-2, the first network slices management device 110-1 may determine that the target network slice is available. If the first network slices management device 110-1 also receives the response indicating the target network slice is able to be provided by the third network slices management device 110-3, the first network slices management device 110-1 may determine that from which network slices management device the target network slice is to be provided to the application 130.

For example, the first network slices management device 110-1 may determine a target network slices management device to be provide the target network slice based on the capability level required by the candidate network slices management devices. For example, if the second network slices management device 110-2 requires a capability level lower than that of the third network slices management device 110-3, the first network slices management device 110-1 may determine that the target network slice is to be provided from the second network slices management device 110-2. That is, the network slice 122-1 managed by the second network slices management device 110-2 is to be provided to the application 130. Cost is another example of target network slice selection.

In some example embodiments, a negotiation procedure may be performed between the first network slices management device 110-1 and second network slices management device 110-2 or between the first network slices management device 110-1 and third network slices management device 110-3, to determine whether the capability supplied by the application 130 is acceptable by the second network slices management device 110-2 or the third network slices management device 110-3.

For example, after receiving the response indicating the target network slice is able to be provided by the second network slices management device 110-2, the capability required by the second network slices management device 110-2 may be known by the first network slices management device 110-1. Furthermore, the first network slices management device 110-1 may also know the actual capability that the application 130 can supply. If the first network slices management device 110-1 determines that the actual capability that the application 130 can supply cannot match the capability required by the second network slices management device 110-2, the negotiation procedure between the first network slices management device 110-1 and second network slices management device 110-2 can be initiated. The first network slices management device 110-1 may transmit 240, to the second network slices management device 110-2, for example, an indication to inquire whether the capability required by the second network slices management device 110-2 can be adjusted to be matched with the actual capability that the application 130 can supply. If the second network slices management device 110-2 determines that the actual capability is acceptable, the second network slices management device 110-2 may transmit 245 a response indicating the actual capability is acceptable by the second network slices management device 110-2 to the first network slices management device 110-1. The first network slices management device 110-1 may determine 250 that the target network slice is to be provided from the second network slices management device 110-2.

Then the first network slices management device 110-1 may provide 255 the target network slice from the second network slices management device 110-2 to the application 130. For example, the first network slices management device 110-1 may obtain the identifier of the target network slice, such as a network address of the target network slice. Then the first network slices management device 110-1 may bind the target network slice to a set of network slices original managed by the first network slices management device 110-1 based on the identifier of the target network slice.

In some example embodiments, the first network slices management device 110-1 can subscribe the service status of another network slices management devices. For example, the first network slices management device 110-1 may subscribe the service status of the second network slices management device 110-2. Once the status change occurs at the second network slices management device 110-2, the second network slices management device 110-2 may transmit 260, to the first network slices management device 110-1, an indication of the service status event occurred at the second network slices management device 110-2. The first network slices management device 110-1 may determine 265 whether the target network slice is still available from the second network slices management device 110-2 based on the indication. For example, if the indication indicates a failure of the target network slice, the first network slices management device 110-1 may determine the target network slice is unavailable from the second network slices management device 110-2. In this case, the first network slices management device 110-1 may initiate a new probing procedure to inquire a network slices management device that can provide the target network slice.

In some example embodiments, the first network slices management device 110-1 can, for example, subscribe the service status of third network slices management device 110-3. The first network slices management device 110-1 may monitor the service status of the network slices management devices that the first network slices management device 110-1 subscribes. If a dynamic network slice management criteria are met, the first network slices management device 110-1 may adjust the provider of the target network slice.

For example, if the first network slices management device 110-1 receives, from the third network slices management device 110-3, a notification indicating that the target network slice can be provided from the third network slices management device 110-3 (for example, the network slice 123-2 as shown in FIG. 1) and the target network slice provided from the third network slices management device 110-3 requires a capability lower than the current capability required by the second network slices management device 110-2, the first network slices management device 110-1 may replace the current network slices provided from the second network slices management device 110-2 with the new network slice provided from the third network slices management device 110-3. Once the replacement completes, the set of network slices managed by the network slices management device 110-1 can be updated, i.e. the network slice 123-2 can be bund to the set of network slices managed by the network slices management device 110-1.

For example, a dynamic network slice management provisioning may be set from the application 130 to NSMF (for example, first network slices management device 110-1) in their network slice service request as below.

Table 1: dynamic network slice management provisioning

Now referring to the FIG. 3, which shows a signaling chart illustrating a process 300 of dynamic network slices management according to some example embodiments of the present disclosure. For the purpose of discussion, the process 300 will be described with reference to FIG. 1. The process 300 may involve the first network slices management device 110-1, the second network slices management device 110-2, the central network slices management device 120-1 and the application 130 as illustrated in FIG. 1.

As shown in FIG. 3, the application 130 may transmit 305 a request for a target network slice to the first network slices management device 110-1. As described above, the first network slices management device 110-1 may manage multiple network slices. The first network slices management device 110-1, which may also be considered as a NSMF, may maintain the network slicing service status in its own network by communicating with a network slice controller deployed in its network.

After receiving the request, the first network slices management device 110-1 may calculate 310 the requirements of the application 130 based on the request. For example, first network slices management device 110-1 may obtain, from the request a description of the service provided by the target network slice and the corresponding capability associated with target network slice that the application 130 can supply. If the first network slices management device 110-1 fails to provide the target network slice, the first network slices management device 110-1 may probe whether the target network slice can be provided by other network slices management devices.

In some example embodiments, the first network slices management device 110-1 may transmit 315, to a central network slices management device 120-1, a message for detecting an availability of the target network slice from the second network slices management device 110-2.

In some example embodiments, the message may comprise property information associated with the target network slice. For example, the property information may comprise a description about a service provided by the target network slice and/or a capability associated with the target network slice that the application 130 can supply. Hereinafter the capability can at least comprise network resources available for the service provided by the target network slice and cost afforded by the application 130 for the target network slice.

The second network slices management device 110-2 can be registered at the central network slices management device 120-1. Thus, the network slices supported by the second network slices management device 110-2 can be known by the central network slices management device 120-1. After receiving the message from the first network slices management device 110-1, if the central network slices management device 120-1 determines 320 that the target network slice (for example, the network slice 122-1 as shown in FIG. 1) is able to be provided by the second network slices management device 110-2, the central network slices management device 120-1 may transmit 325, to the first network slices management device 110-1, a response indicating the target network slice is able to be provided by the second network slices management device 110-2.

When the first network slices management device 110-1 receives the response from the central network slices management device 120-1. The first network slices management device 110-1 may determine that the target network slice is available.

The first network slices management device 110-1 may transmit 330, to the second network slices management device 110-2, a request for the allocation of the target network slice. If the second network slices management device 110-2 determines that the target network slice is able to be provided to the application 130, the second network slices management device 110-2 may transmit 335, to the first network slices management device 110-1, a response indicating the target network slice is able to be provided by the second network slices management device 110-2.

Similarly, the first network slices management device 110-1 can also subscribe the service status of other network slices management devices via the central network slices management device 120-1 and adjust the strategy for providing the target network slice based on the notification of the status changes from the central network slices management device 120-1.

In some example embodiments, if the central network slices management device 120-1 determines that the target network slice fails to be provided by any network slices management devices managed by the central network slices management device 120-1, the central network slices management device 120-1 may also request the target network slice from other central network slices management device. For example, as shown in FIG. 3, the central network slices management device 120-1 may send 340 a request for the target network slice to a further central network slices management device 120-2. After receiving the request from the central network slices management device 120-1, if the further central network slices management device 120-2 determines 345 that the target network slice is able to be provided by a network slices management device managed by the further central network slices management device 120-2 (for example, the fourth network slices management device 110-4 as shown in FIG. 4) , the further central network slices management device 120-1 may transmit 350, to the central network slices management device 120-1, a response indicating the target network slice is able to be provided by the fourth network slices management device 110-4.

In this way, a new NSMF is introduced to leverage network slicing service provided by different network slices providers to serve network slicing service request from different applications with the best network slice according to the requirements. By providing the new NSMF, the service cost to both network slices provider and customer can be minimized and moreover the efficiency on network slicing management can be increased.

FIG. 4 shows a flowchart of an example method 400 of dynamic network slices management according to some example embodiments of the present disclosure. The method 400 can be implemented at a first network slices management device 110-1 as shown in FIG. 1. For the purpose of discussion, the method 400 will be described with reference to FIG. 1.

At 410, the first network slices management device 110-1 receives a request for a target network slice.

At 420, in the lack of the target network slice from the first network slice management device 110-1, the first network slices management device 110-1 sends a message for detecting an availability of the target network slice from a second network slice management device.

In some example embodiments, the first network slices management device 110-1 may send the message to the second network slice management device. If the first network slices management device 110-1 determines that a response is received from the second network slice management indicating the target network slice is able to be provided by the second network slice management device, the first network slices management device 110-1 may determine that the target network slice is available.

In some example embodiments, the first network slices management device 110-1 may send the message to a central network slice management device, the central network slice management device managing the first network slice management device and the second network slice management device. If the first network slices management device 110-1 determines that a response is received from the central network slice management device indicating the target network slice is able to be provided by the second network slice management device, the first network slices management device 110-1 may determine that the target network slice is available.

In some example embodiments, the message comprises property information associated with the target network slice comprises at least one of a description about a service provided by the target network slice or a capability associated with the target network slice.

At 430, if the first network slices management device 110-1 determines that the target network slice is available, the first network slices management device 110-1 provides the target network slice from the second network slice management device.

In some example embodiments, the first network slices management device 110-1 may send, to the second network slice management device in a negotiation procedure for the target network slice, an indication of a capability associated with the target network slice. If the first network slices management device 110-1 determines that a response is received from the second network slice management indicating the capability is acceptable by the second network slice management device, the first network slices management device 110-1 may provide the target network slice from the second network slice management device.

In some example embodiments, the first network slices management device 110-1 may receive, from the second network slice management device, a notification of a service status event associated with the target network slice and determine the availability of the target network slice based on the notification.

In some example embodiments, if the first network slices management device 110-1 determines that target network slice is available from a third network slice management device different from the second network slice management device, the first network slices management device 110-1 may determine a reference capability associated with the target network slice required by the third network slice management device. If the first network slices management device 110-1 determines that the reference capability is lower than a current capability associated with the target network slice required by the second network slice management device, the first network slices management device 110-1 may provide the target network slice from the third network slice management device.

FIG. 5 shows a flowchart of an example method 500 of dynamic network slices management according to some example embodiments of the present disclosure. The method 500 can be implemented at the central network slices management device 120-1 as shown in FIG. 1. For the purpose of discussion, the method 500 will be described with reference to FIG. 1.

At 510, the central network slices management device 120-1 receive, from a first network slice management device, a message for detecting an availability of a target network slice from a second network slice management device, the central network slice management device managing the first network slice management device and the second network slice management device.

At 520, if the central network slices management device 120-1 determines that the target network slice is able to be provided by the second network slice management device, the central network slices management device 120-1 provides the target network slice from the second network slice management device to the first network slice management device.

In some example embodiments, an apparatus capable of performing the method 400 (for example, implemented at first network slices management device 110-1) may comprise means for performing the respective steps of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the apparatus comprises means for receiving a request for a target network slice; means for in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and means for in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device.

In some example embodiments, an apparatus capable of performing the method 500 (for example, implemented at the central network slices management device 120-1) may comprise means for performing the respective steps of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the apparatus comprises means for receiving, from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and means for in accordance with a determination that the target network slice is able to be provided by the second network slices management device, providing the target network slice from the second network slices management device to the first network slices management device.

FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure. The device 600 may be provided to implement the communication device, for example the first network slices management device 110-1 or the central network slices management device 120-1 as shown in FIG. 1. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more transmitters and receivers (TX/RX) 640 coupled to the processor 610.

The TX/RX 640 is for bidirectional communications. The TX/RX 640 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.

The processor 610 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.

A computer program 630 includes computer executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 620. The processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 620.

The embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to FIGs. 2-5. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

In some embodiments, the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600. The device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. FIG. 7 shows an example of the computer readable medium 700 in form of CD or DVD. The computer readable medium has the program 630 stored thereon.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, device, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the

methods

400 and 500 as described above with reference to FIGs. 4-5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing device, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, device or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A method for network slices management comprising:

receiving, at a first network slices management device, a request for a target network slice;

in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and

in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device.
The method of Claim 1, further comprising:

sending the message to the second network slices management device; and

in accordance with a determination that a response is received from the second network slices management indicating the target network slice is able to be provided by the second network slices management device, determining that the target network slice is available.
The method of Claim 1, further comprising:

sending the message to a central network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and

in accordance with a determination that a response is received from the central network slices management device indicating that the target network slice is able to be provided by the second network slices management device, determining that the target network slice is available.
The method of any of Claims 1-3, wherein the message comprises property information associated with the target network slice comprises at least one of the following:

a description about a service provided by the target network slice, or

a capability associated with the target network slice.
The method of Claim 1, wherein providing the target network slice from the second network slices management device comprises:

sending, to the second network slices management device in a negotiation procedure for the target network slice, an indication of a capability associated with the target network slice;

in accordance with a determination that a response is received from the second network slices management indicating the capability is acceptable by the second network slices management device, providing the target network slice from the second network slices management device.
The method of Claim 1, further comprising:

receiving, from the second network slices management device, a notification of a service status event occurred at the second network slices management device; and

determining the availability of the target network slice based on the notification.
The method of Claim 1, further comprising:

in accordance with a determination that target network slice is available from a third network slices management device different from the second network slices management device, determining a reference capability associated with the target network slice required by the third network slices management device; and

in accordance with a determination that the reference capability is lower than a current capability associated with the target network slice required by the second network slices management device, providing the target network slice from the third network slices management device.
A method comprising:

receiving, at a central network slices management device and from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and

in accordance with a determination that the target network slice is able to be provided by the second network slices management device, providing the target network slice from the second network slices management device to the first network slices management device.
A first network slices management device comprising:

at least one processor; and

at least one memory including computer program codes;

the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first network slices management device at least to:

receive a request for a target network slice;

in the lack of the target network slice from the first network slices management device, send a message for detecting an availability of the target network slice from a second network slices management device; and

in accordance with a determination that the target network slice is available, provide the target network slice from the second network slices management device.
The first network slices management device of Claim 9, wherein the first network slices management device is further caused to:

send the message to the second network slices management device; and

in accordance with a determination that a response is received from the second network slices management indicating the target network slice is able to be provided by the second network slices management device, determine that the target network slice is available.
The first network slices management device of Claim 9, wherein the first network slices management device is further caused to:

send the message to a central network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and

in accordance with a determination that a response is received from the central network slices management device indicating that the target network slice is able to be provided by the second network slices management device, determine that the target network slice is available.
The first network slices management device of any of Claims 9-11, wherein the message comprises property information associated with the target network slice comprises at least one of the following:

a description about a service provided by the target network slice, or

a capability associated with the target network slice.
The first network slices management device of Claim 9, wherein the first network slices management device is caused to provide the target network slice from the second network slices management device by:

sending, to the second network slices management device in a negotiation procedure for the target network slice, an indication of a capability associated with the target network slice;

in accordance with a determination that a response is received from the second network slices management indicating the capability is acceptable by the second network slices management device, providing the target network slice from the second network slices management device.
The first network slices management device of Claim 9, wherein the first network slices management device is further caused to:

receive, from the second network slices management device, a notification of a service status event occurred at the second network slices management device; and

determine the availability of the target network slice based on the notification.
The first network slices management device of Claim 9, wherein the first network slices management device is further caused to:

in accordance with a determination that target network slice is available from a third network slices management device different from the second network slices management device, determine a reference capability associated with the target network slice required by the third network slices management device; and

in accordance with a determination that the reference capability is lower than a current capability associated with the target network slice required by the second network slices management device, provide the target network slice from the third network slices management device.
A central network slices management device comprising:

at least one processor; and

at least one memory including computer program codes;

the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first network slices management device at least to:

receive, from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and

in accordance with a determination that the target network slice is able to be provided by the second network slices management device, provide the target network slice from the second network slices management device to the first network slices management device.
An apparatus comprising:

means for receiving a request for a target network slice;

means for in the lack of the target network slice from the first network slices management device, sending a message for detecting an availability of the target network slice from a second network slices management device; and

means for in accordance with a determination that the target network slice is available, providing the target network slice from the second network slices management device.
An apparatus comprising:

means for receiving, from a first network slices management device, a message for detecting an availability of a target network slice from a second network slices management device, the central network slices management device managing the first network slices management device and the second network slices management device; and

means for in accordance with a determination that the target network slice is able to be provided by the second network slices management device, providing the target network slice from the second network slices management device to the first network slices management device.
A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of any of claims 1-7.
A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 8.