WO2020042848A1

WO2020042848A1 - Network slice management method and apparatus

Info

Publication number: WO2020042848A1
Application number: PCT/CN2019/098153
Authority: WO
Inventors: 武绍芸; 苏偌宇
Original assignee: 华为技术有限公司
Priority date: 2018-08-31
Filing date: 2019-07-29
Publication date: 2020-03-05
Also published as: CN110875827A; CN110875827B

Abstract

A network slice management method and apparatus, for optimizing end-to-end network slice management. Said method comprises: a proxy node receiving a network slice creation request from an NSMF, the network slice creation request being used to request for the creation of a first end-to-end network slice sharing resources with a created end-to-end network slice, the first end-to-end network slice including a first core network slice and a first access network slice; creating the first core network slice according to the network slice creation request, the first core network slice sharing resources with a created second core network slice; and sending an access network slice creation request to an access network device supporting a network slice proxy, the access network slice creation request being used to request for the creation of the first access network slice, the access network slice creation request carrying first instruction information, the first instruction information being used to instruct the first core network slice and the second core network slice to share resources.

Description

Network slice management method and device

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China on August 31, 2018, with application number 201811010266.9, and the invention name is "A Method and Device for Network Slice Management", the entire contents of which are incorporated by reference In this application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a network slice management method and device.

Background technique

The 5th-generation (5G) mobile communication system introduces network slicing technology to cope with the difference in network performance requirements of different communication services. In the related art, a slice that can be implemented to provide a terminal with an end-to-end network service from an access network (AN) to a core network (CN) is called an end-to-end network slice. Hereinafter, AN and CN are collectively referred to as a subnet. The end-to-end network slice may include a subnet slice, such as a core network slice and an access network slice.

In the prior art, an end-to-end network slice is managed by a network slice management function (NSMF). For example, an end-to-end network slice can be created, updated, or destroyed through NSMF. Taking the creation of an end-to-end network slice as an example, NSMF can send network slice creation requests to the network slice subnet management function (NSSMF) deployed in the subnet. The NSSMF in each subnet is based on the network slice. The creation request creates a subnet slice, thereby realizing the creation of an end-to-end network slice.

Earlier research on network slicing mainly focused on the core network, and research on access network slicing was relatively scarce. For the NSSMF deployment in the AN was late, there may be scenarios where the NSSMF is not deployed in the AN. In this scenario, the NSMF cannot be connected. The network slice is managed, and the end-to-end network slice cannot be managed.

In addition, even if NSSMF has been deployed in the AN, because NSMF does not understand the implementation details of the control plane of each subnet, it may lead to inconsistent decisions made by NSSMF in each subnet when managing the subnet slicing.

Summary of the Invention

The embodiments of the present application provide a network slice management method and device, which are used to optimize the management of end-to-end network slices.

The specific technical solutions provided in the embodiments of the present application are as follows:

In a first aspect, a network slice management method is provided. The execution body of the method may be a proxy node. The proxy node may be a newly added node in the CN, or it may be integrated on the NSSMF in the CN. The steps of the specific method may be as follows: receiving a network slice creation request from NSMF, the network slice creation request is used to request the creation of a first end-to-end network slice that shares resources with the created end-to-end network slice, the The first end-to-end network slice includes a first core network slice and a first access network slice, and the first core network slice is created according to the network slice creation request, and the first core network slice and the created second The core network slice shares resources and sends an access network slice creation request to an access network device that supports a network slice proxy, where the access network slice creation request is used to request creation of the first access network slice, and the access network The slice creation request carries first indication information, and the first indication information is used to instruct the first core network slice and the second core network slice to share resources. In the scenario where NSSMF is not deployed in the AN, the NSMF can use this proxy node to send network slice management messages (such as network slice creation requests) to access network devices that support network slice agents in the AN to achieve end-to-end network slice management. . In the scenario where NSSMF is deployed in the AN, the NSMF no longer sends network slice management messages to the AN and CN separately as in the prior art. Instead, the network slice management message is first sent to the proxy node in the CN. The network slicing management message makes a decision, and then the proxy node sends a network slicing management message to the access network device supporting the network slicing proxy in the AN, and the proxy node notifies the decision made by the access network device CN side so that The access network equipment on the AN side can refer to the decision made by the CN side, and then make a decision consistent with the CN side.

Exemplarily, the network slice management method provided by the embodiment of the present application is exemplified by an example. Suppose the NSMF sends a network slice creation request to the proxy node, requesting to create an end-to-end network slice 3 that shares resources with the created end-to-end network slice. The end-to-end network slice 3 may include core network slice 3 and access network slice 3. Among them, the created end-to-end network slice includes end-to-end network slice 1 and end-to-end network slice 2, end-to-end network slice 1 includes core network slice 1 and access network slice 1, and end-to-end network slice 2 includes Core network slice 2 and access network slice 2. If the existing method is adopted, in the scenario where the NSSMF is deployed in the AN, the NSMF can send core network slice creation requests to the NSSMF in the CN, requesting to create a core network slice 3 that shares resources with the created core network slice. The NSSMF in the AN sends an access network slice creation request to request the creation of an access network slice 3 that shares resources with the created access network slice. The NSSMF in the CN can create and create the core network according to the core network slice creation request. Slice 1 or core network slice 2 shares the core network slice 3 of the resource. The NSSMF in the AN can create an access network that shares resources with the created access network slice 1 or access network slice 2 according to the access network slice creation request. Slice 3 may cause NSSMF in CN to create core network slice 3 that shares resources with the created core network slice 1, while NSSMF in AN creates access network slice 3 that shares resources with the created access network slice 2. In this way, the subnet slices created in AN and CN do not belong to the same end-to-end network slice, which may cause subsequent errors when using end-to-end network slice 3. If the existing method is adopted, in a scenario where NSSMF is not deployed in the AN, the NSMF cannot send an access network slice creation request to the AN, and thus cannot create an end-to-end network slice. By using the method provided in the embodiment of the present application, the NSMF can send a network slice creation request to a proxy node in the CN. The proxy node creates a core network slice 3 that shares resources with the created core network slice 1 according to the network slice creation request, and Send an access network slice creation request to an access network device in the AN that supports a network slice proxy, and the access network slice creation request carries instruction information to instruct core network slice 1 and core network slice 3 to share resources. In this way, the support The access network device of the network slice proxy can create an access network slice 3 that shares resources with the created access network slice 1 according to the access network slice creation request, so that the subnet slices created in the AN and CN belong to the same end End-to-end network slicing can avoid errors when using end-to-end network slicing 3.

In a possible design, the network slice creation request may carry the identity of the second end-to-end network slice. At this time, the network slice creation request may be used to request creation of a shared resource with the second end-to-end network slice. The first end-to-end network slice. That is, the network slice creation request can be used to request the creation of a first end-to-end network slice that shares resources with a particular end-to-end network slice.

In the embodiment of the present application, the following describes how a proxy node creates the first core network slice.

In a possible design, the proxy node receives a network slice creation request from NSMF, and the network slice creation request carries an identifier of a second end-to-end network slice and is used to request creation of the second end-to-end network slice. The first end-to-end network slice of the shared resource, the second end-to-end network slice includes the second core network slice, the proxy node creates the first core network slice, and the first core network slice and the The second core network slice included in the second end-to-end network slice shares resources.

In a possible design, after receiving the network slice creation request from the NSMF, the proxy node may create the first core according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs. For network slices, the resource sharing slice information of the core network to which the proxy node belongs includes information about core network slices that have been created in the core network and support resource sharing. In this way, the proxy node can learn the implementation details of the core network control plane according to the resource sharing slice information of the core network to which the proxy node belongs, and then can relatively accurately create the first core network slice in combination with the implementation details of the core network control plane.

In the embodiment of the present application, the following describes how a proxy node creates the first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs.

In a possible design, the resource shared slice information of the core network to which the proxy node belongs may include information of a core network slice that has been created and supports resource sharing, and the information of the core network slice includes the core network slice. Identification and resource usage. In this design, the proxy node may create the first core network slice in the following manner: the proxy node determines the core network slice with the lowest resource occupation rate in the core network slice as the second core network slice, and The network slice creation request and the identity of the second core network slice create the first core network slice. In this method, the agent node creates and shares the first core network slice of the resource with the created core network slice with the lowest resource occupancy according to the resource consumption of the core network slice, so as to optimize the resource sharing effect. . However, in the prior art, the resource sharing of network slices can only be determined by NSMF. NSMF cannot accurately sense the resource consumption of subnet slices in the core network and the access network. Therefore, when creating a new network slice, NSMF cannot accurately Determine the network slice to be created and which network slice has been created to perform the best resource sharing. Obviously, the method of the present application can optimize the management of network slices.

In a possible design, the network slice creation request carries an identifier of a second end-to-end network slice, and resource sharing slice information of a core network to which the proxy node belongs includes the second end-to-end network slice. The information of the core network slice, and the information of the core network slice includes an identifier of the core network slice and a resource occupation rate. In this design, the proxy node may create the first core network slice in the following manner: When the resource occupation rate of the core network slice in the second end-to-end network slice is less than a preset value, the proxy node will The core network slice in the second end-to-end network slice is determined to be the second core network slice, and the first core network slice is created according to the network slice creation request and the identity of the second core network slice. . In this method, the proxy node creates the core network slice in the second end-to-end network slice only when the resource occupancy rate of the core network slice in the second end-to-end network slice is less than a preset value. The first core network slice of the resource is shared to optimize the resource sharing effect.

It should be noted that the preset value may be set according to an actual application scenario. The principle for setting the preset value may be that after a core network slice with a resource occupancy rate less than the preset value shares resources with the first core network slice, the two core network slices sharing the resource can be used normally.

In a possible design, the proxy node may send an access network slice creation request to an access network device supporting a network slice proxy through a default access and mobility management entity (AMF). In this design, after the proxy node sends an access network slice creation request to an access network device that supports a network slice proxy through the default AMF, the proxy node may further receive a first list from the default AMF. A creation result of the first access network slice by the access network device supporting the network slice proxy. For example, the creation result may be the creation success or failure.

It should be noted that, in other possible designs, the proxy node may also interact with the access network device supporting the network slice proxy through other AMF (different from the default AMF), which is not limited in this application.

In a possible design, after receiving the first list from the default AMF, the proxy node may further send the first list to the NSMF. Then, the NSMF can make subsequent decisions according to the first list. For example, if the creation results included in the first list are all created successfully, the NSMF need not perform other operations. If there is a creation failure in the creation result included in the first list, the NSMF may re-initiate the slice creation process for the slice that failed to be created.

In the embodiment of the present application, an access network device that supports a network slice proxy can be understood as that an access network slice in the access network device can be managed by the proxy node. The ability of the proxy node to manage the access network slice in the access network device may be predetermined by the proxy node, the NSMF, and the access network device, or it may be the proxy. It is determined in real time through negotiation among the node, the NSMF, and the access network device.

In a possible design, before the proxy node receives the network slice creation request from the NSMF, the capability of the proxy node to manage the access network slice in the access network device may be negotiated. In this design, the proxy node may negotiate in the following manner: the proxy node receives a slice management proxy request from a default AMF, and the slice management proxy request may carry the information of the access network to which the access network device belongs. It is identified that the slice management proxy request may be used to request the proxy node to perform a network slice proxy for an access network device in the access network. After receiving the slice management proxy request, the proxy node may further send the slice management proxy request to the NSMF. In this way, when NSSMF is not deployed in the access network, it can be determined through negotiation that the proxy node manages the access network slice in the access network to assist the NSMF to achieve the management of the end-to-end network slice. Optimize management of end-to-end network slices.

In a possible design, the proxy node sends an access network slice update request to the access network device supporting the network slice proxy, and the access network slice update request may carry second instruction information, where The second instruction information is used to indicate that the first core network slice and the created third core network slice share resources. In this way, the access network device can update the resource sharing relationship between the first access network slice and the created access network slice according to the second instruction information, and ensure that the AN side and the CN side make consistent decisions. For example, if the proxy node updates the shared resources of the first core network slice and the created second core network slice to the shared resources of the first core network slice and the created third core network slice, the update content can be passed through the update The second instruction information informs the AN side access network device. Correspondingly, the access network device may also update the resource sharing relationship of the first access network slice according to the decision of the CN side.

In a second aspect, a network slicing management method is provided. The method may be performed by an access network device that supports a network slicing agent. The steps of the specific method may be described as follows: receiving a connection from an agent node. A network slice creation request, the access network slice creation request is used to request the creation of a first access network slice, and the access network slice creation request may carry first instruction information, where the first instruction information is used to indicate The first core network slice and the second core network slice share resources, and create the first access network slice according to the access network slice creation request, the first access network slice and the created second access Network slice shared resources, wherein the first core network slice and the first access network slice belong to a first end-to-end network slice, and the second core network slice and the second access network slice belong to The second end-to-end network slice created. The access network device may learn the decision made by the CN side according to the first instruction information, and then may refer to the decision made by the CN side to make a decision consistent with the CN side. For example, the AN and the CN The created subnet slices belong to the same end-to-end network slice, which can prevent subsequent errors when using the end-to-end network slice.

In a possible design, the access network device may receive an access network slice creation request from a proxy node through a default AMF. In this design, before the access network device receives the access network slice creation request from the proxy node through the default AMF, it may further send a slice management proxy request to the default AMF, and the slice management proxy request carries a support slice. A proxy flag bit and an identification of the access network device, and the support slice proxy flag bit is used to indicate that the access network device supports a network slice proxy. In order to enable the default AMF to subscribe to a network slice proxy from a proxy node, if NSSMF is not deployed in the access network, the proxy node can manage the access network slice in the access network to assist the NSMF to implement the end Management of end-to-end network slices.

In a third aspect, a network slice management method is provided. The execution body of the method may be a default AMF. The steps of the specific method may be described as follows: receiving an access network slice creation request from a proxy node, and the access network slice creation The request is used to request the creation of an access network slice, and the access network slice creation request carries first instruction information, where the first instruction information is used to indicate that the first core network slice and the second core network slice share resources, and The default AMF and the proxy node belong to the same core network, and send the access network slice to the access network device supporting the network slice proxy in the access network according to a pre-stored identifier of the access network device supporting the network slice proxy. Create request.

In a possible design, after the default AMF sends the access network slice creation request to an access network device that supports a network slice proxy in the access network, it may further receive a response message from the access network device. The response message includes the creation result of the access network slice, and a first list is sent to the proxy node according to the response message, where the first list includes the response message received by the default AMF within a preset time and includes Result of the creation of the access network slice.

In a possible design, before the default AMF receives an access network slice creation request from a proxy node, it may further receive a first slice management proxy request from the access network device, the first slice The management proxy request carries a support slice proxy flag and an identification of the access network device, and the support slice proxy flag is used to indicate that the access network device supports a network slice proxy. When the first ratio is greater than a first threshold , The default AMF sends a second slice management agent request to the proxy node according to the first slice management agent request, wherein the first ratio is to the access network to the access point within a preset time. The ratio of the number of access network devices requested by the first slice management agent to the total number of all access network devices included in the access network by default, and the second slice management agent request carries the The identification of the access network. The second slice management proxy request is used to request the proxy node to perform a network slice proxy for the access network device in the access network.

According to a fourth aspect, a network slice management method is provided. The execution body of the method may be NSSF. The steps of the specific method may be as follows: receiving a slice management agent request from an agent node, and the slice management agent request carries access The network identification and the identity of the proxy node, the slice management proxy request is used to request the proxy node to perform a network slice proxy for the access network device in the access network, and send the proxy node to the proxy node to carry the proxy node The identified network slice creation request is used to request the creation of an end-to-end network slice that shares resources with the created end-to-end network slice. The end-to-end network slice includes a core network slice and an access. Net slice.

In a possible design, the NSMF receives a first list from the proxy node, and the first list includes a creation result of the access network slice.

In a fifth aspect, a network slicing management device is provided. The device has a function of implementing the behavior of a proxy node in any of the first aspect and the first possible design of the first aspect. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the device includes a memory and a processor. The memory stores a set of programs. The processor is configured to execute the programs stored in the memory. When the program is executed, the device may execute the first aspect and the first aspect. The method described in any of the possible designs.

In a possible design, the device further includes a transceiver for communication between the device and other network elements.

In a possible design, the device is a proxy node, and the proxy node may be a newly added node in the CN or may be integrated on the NSSMF in the CN.

According to a sixth aspect, a network slicing management device is provided, and the device has a function of implementing the behavior of an access network device in any one of the second aspect and the second possible design of the second aspect. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the device includes a memory and a processor. The memory stores a set of programs. The processor is configured to execute the programs stored in the memory. When the program is executed, the device may execute the second aspect and the second aspect. The method described in any of the possible designs.

In a possible design, the device is an access network device.

According to a seventh aspect, a network slicing management device is provided. The device has a function of implementing the default AMF behavior in any of the foregoing third aspect and the third possible design. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the device includes a memory and a processor. The memory stores a set of programs. The processor is configured to execute the programs stored in the memory. When the program is executed, the device may execute the third aspect and the third aspect. The method described in any of the possible designs.

In one possible design, the device is the default AMF.

According to an eighth aspect, a network slicing management device is provided. The device has a function of realizing the NSMF behavior in any one of the foregoing fourth aspect and the fourth possible design. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the device includes a memory and a processor. The memory stores a set of programs. The processor is configured to execute the programs stored in the memory. When the program is executed, the device may execute the fourth aspect and the fourth aspect. The method described in any of the possible designs.

In one possible design, the device is NSMF.

In a ninth aspect, a chip is provided, the chip is connected to a memory or the chip includes a memory for reading and executing a software program stored in the memory, so as to implement the first, second, and third aspects as described above. , The fourth aspect, any possible design of the first aspect, any possible design of the second aspect, any possible design of the third aspect, and any possible design of the fourth aspect Methods.

According to a tenth aspect, a communication system is provided, and the communication system includes the devices described in any two aspects or any two or more of the first to fourth aspects.

According to an eleventh aspect, a computer storage medium is provided, storing a computer program, the computer program including instructions for performing the foregoing aspects and any possible design method in each aspect.

According to a twelfth aspect, a computer program product is provided. When the computer reads and executes the computer program product, the computer is caused to execute the method described in the foregoing aspects and any possible design of each aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present application; FIG.

FIG. 2 is a second schematic diagram of a system architecture according to an embodiment of the present application; FIG.

3a is a third schematic diagram of a system architecture provided by an embodiment of the present application;

3b is a fourth schematic diagram of a system architecture according to an embodiment of the present application;

4 is a flowchart of a network slice management method according to an embodiment of the present application;

5 is a flowchart of another network slice management method according to an embodiment of the present application;

6a is a fifth schematic diagram of a system architecture according to an embodiment of the present application;

6b is a sixth schematic diagram of a system architecture according to an embodiment of the present application;

7 is a flowchart of another network slice management method according to an embodiment of the present application;

8 is a flowchart of another network slice management method according to an embodiment of the present application;

9 is a flowchart of still another network slice management method according to an embodiment of the present application;

10 is a flowchart of still another network slice management method according to an embodiment of the present application;

11 is a flowchart of another network slice management method according to an embodiment of the present application;

FIG. 12 is one of the schematic structural diagrams of a network slice management apparatus according to an embodiment of the present application; FIG.

13 is a second schematic structural diagram of a network slice management device according to an embodiment of the present application;

14 is a third schematic structural diagram of a network slice management device according to an embodiment of the present application;

FIG. 15 is a fourth schematic structural diagram of a network slice management apparatus according to an embodiment of the present application; FIG.

FIG. 16 is a fifth schematic structural diagram of a network slice management apparatus according to an embodiment of the present application.

detailed description

The present application provides a network slice management method and device, which are used to assist NSMF to optimize end-to-end network slice management through a proxy node. Among them, the method and device are based on the same or similar concept of the same invention. Since the principle of the method and the device to solve the problem is similar, the implementation of the device and the method can be referred to each other, and the duplicates will not be repeated. In the description of the embodiments of the present application, "and / or" describes the association relationship of the associated objects, and indicates that there can be three kinds of relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and There are three cases of B. The character "/" generally indicates that the related objects are an "or" relationship. At least one involved in this application means one or more; multiple means two or more. In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor as indicating Or imply order. "At least one" means one or more; "at least one" means one or more; multiple means two or more.

The embodiments of the present application will be described in detail below with reference to the drawings.

The network slice management method provided in the embodiment of the present application may be applicable to a 5G communication system, and may also be applicable to a new communication system in the future (such as the 6th-generation (6G) mobile communication system, etc.). .

FIG. 1 exemplarily shows a schematic diagram of a system architecture applicable to the embodiment of the present application, and the embodiment of the present application is not limited to be applied to the system architecture shown in FIG. 1. Each network element shown in FIG. 1 may be hardware, software divided in function, or a combination of the two. As shown in FIG. 1, the system architecture provided in the embodiment of the present application includes a terminal, an access network (AN) device, and an access and mobility management network element (also referred to as: access and mobility management functions). / Access and mobility management function entity), user plane network element (also referred to as: user plane function / user plane function entity), network slice management network element (or network slice management function / network slice management function entity) , Network slice subnet management network element (or network slice subnet management function / network slice subnet management function entity) and data network (DN). The terminal establishes communication with the DN through the access network equipment and the user plane network element.

It should be noted that the network elements involved in the embodiments of the present application may also be referred to as functions or functional entities. For example, the network slice management network element may also be referred to as a network slice management function or a network slice management function entity, access and mobility. The mobility management network element may be referred to as an access and mobility management function or an access and mobility management function entity.

The names of the various network elements are not limited in this application. Those skilled in the art may change the names of the above network elements to other names and perform the same functions, which all fall within the protection scope of this application.

Exemplarily, the system architecture shown in FIG. 1 may be the 5G system architecture shown in FIG. 2. The functions of each network element or device are described below.

Terminals, also known as user equipment (UE), mobile stations (MS), mobile terminals (MT), terminal equipment, etc., are a means of providing voice and / or data connectivity to users device of. For example, the terminal includes a handheld device having a wireless connection function, a vehicle-mounted device, and the like. At present, the terminals can be: mobile phones, tablet computers, laptops, palmtop computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented) Reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless in smart grid Terminals, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes.

The access network equipment (also called AN equipment) is responsible for the wireless side access of the terminal. Possible deployment forms include: a centralized unit (CU) and distributed unit (DU) separation scenario; and Single-site scenario. Single site includes gNB / NR-NB, transmission receiving point (TRP), evolved Node B (eNB), radio network controller (RNC), and node B (Node B) NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home NodeB, or home NodeB, HNB), baseband unit (base band unit, BBU), or wireless fidelity (Wifi) access point (AP). In a 5G communication system, a single site is gNB / NR-NB. Among them, the CU supports radio resource control (radio resource control, RRC), packet data convergence protocol (PDCP), service data adaptation protocol (service data adaptation protocol, SDAP) and other protocols. CUs are generally deployed at central offices and have relatively abundant computing resources. DU mainly supports radio link control layer (radio link control, RLC), media access control layer (media access control, MAC) and physical layer (PHY) protocols. DUs are generally deployed in a distributed manner. In general, more than one DU is connected to a CU. The gNB has the functions of CU and DU, and is usually deployed as a single site.

The access and mobility management network element may be an access and mobility management function (AMF) in 5G. The access and mobility management network element is responsible for terminal access and mobility management in the mobile network.

The user plane network element may be a user plane function (UPF) in a 5G architecture, as shown in FIG. 2. The UPF is responsible for message processing and forwarding.

DN, which provides data transmission services for terminals, can be a PDN network, such as the Internet (Internet), IP Multi-media Service (IMS), and so on.

The network slice management network element may be a network slice management function (NSMF) in the 5G architecture, which is used to manage the network slice of the entire network.

The network slice subnet management network element can be a network slice subnet management function (NSSMF) in the 5G architecture. It can be deployed in each subnet, for example, it can be deployed in the CN and AN for management. Network slices within a subnet. The NSSMF deployed in the CN may be referred to as the NSSMF in the CN or the NSSMF in the CN domain. Similarly, the NSSMF deployed in the AN may be referred to as the NSSMF in the AN or the NSSMF in the AN domain. The name of the NSSMF deployed in the subnet is not limited in this application.

Exemplarily, the system architecture shown in FIG. 1 may also be a 5G system architecture shown in FIG. 3a. Figure 3a illustrates the deployment of NSSMF in AN and CN respectively as an example. In the system architecture shown in FIG. 3a, end-to-end network slices can be managed through NSMF. For example, end-to-end network slices can be created, updated, or destroyed through NSMF. Taking the creation of an end-to-end network slice as an example, the NSMF can send network slice creation requests to the NSSMF in the AN and the NSSMF in the CN, respectively. The NSSMF in the AN creates the access network slice according to the network slice creation request, and the NSSMF in the CN according to the network. The slice creation request creates a core network slice, thereby completing the creation of an end-to-end network slice. However, because the NSMF does not understand the implementation details of the core and access network control planes, the NSMF may not be able to make accurate decisions.

In addition, the early research on network slicing mainly focused on the core network, and the research on access network slicing was scarce. For the NSSMF deployment in the AN was late, there may be scenarios where the NSSMF is not deployed in the AN, as shown in Figure 3b In this scenario, because NSSMF is not deployed in the AN, NSMF decisions cannot be sent to the AN. As a result, the NSMF cannot manage access network slices, and thus it cannot implement end-to-end network slice management.

Based on the aforementioned problems, an embodiment of the present application provides a network slice management method for optimizing management of an end-to-end network slice.

As shown in FIG. 4, it is a flowchart of a network slice management method according to an embodiment of the present application. The method includes the following processing flow.

S401: The proxy node receives a network slice creation request from the NSMF.

The network slice creation request may be used to request to create a first end-to-end network slice that shares resources with the created end-to-end network slice. The first end-to-end network slice may include a first core network slice and a first Access network slicing.

In this application, shared resources may refer to sharing virtual machines or containers.

In this application, the proxy node may be a newly added node in the CN, or it may be integrated on the NSSMF in the CN. In the embodiment of the present application, the proxy node is a newly added node in the CN.

In this application, the network slice creation request may also be referred to as an end-to-end network slice creation request or a slice creation request. The end-to-end network slice can be a slice that provides end-to-end network services from AN to CN for the terminal, and can also be called a network slice or slice. The end-to-end network slice may include a network slice in a core network and a network slice in an access network. The network slice in the core network can also be referred to as the network slice in the CN domain or the core network slice, and the network slice in the access network can also be called the network slice or access network slice in the AN domain.

In this application, AN and CN may be collectively referred to as a subnet, and may also be referred to as a subnetwork or a subdomain. Correspondingly, the network slices in the core network and the network slices in the access network may be collectively referred to as a sub-network slice, a sub-network slice, or a sub-domain slice.

S402: The proxy node creates a first core network slice according to the network slice creation request. The first core network slice shares resources with the created second core network slice.

Optionally, the network slice creation request may carry the identity of the second end-to-end network slice. When the network slice creation request carries the identity of the second end-to-end network slice, the network slice creation request may be used to request the creation of a first end-to-end network slice that shares resources with the second end-to-end network slice. That is, the NSMF can request the creation of a first end-to-end network slice that shares resources with a particular end-to-end network slice.

In one example, if the identification of the end-to-end network slice is not carried in the network slice request, that is, the NSMF does not specify which end-to-end network slice the first end-to-end network slice to be created shares resources with, The proxy node itself can determine that the first end-to-end network slice to be created shares resources with a particular created end-to-end network slice. The following section describes how the agent node creates the first core network slice in detail.

In another example, if the network slice request carries the identity of the second end-to-end network slice, that is, the NSMF specifies that the first end-to-end network slice to be created is shared with the second end-to-end network slice that has been created In this example, the proxy node can create a first end-to-end network slice that shares the resource with a second end-to-end network slice specified by NSMF, or it can create an The end-to-end network slice shares the first end-to-end network slice of the resource. Detailed examples are given below for different situations.

S403: The proxy node sends an access network slice creation request to an access network device that supports a network slice proxy. The access network slice creation request may be used to request creation of a first access network slice, and the access network slice creation request may carry first indication information, where the first indication information is used to indicate the first core network slice and the second core network slice. Core network slices share resources.

In this application, the proxy node may send an access network slice creation request to the access network device through control plane signaling.

The following describes in detail how the proxy node creates the first end-to-end network slice.

In a possible implementation manner, the network slice creation request carries an identifier of a second end-to-end network slice, and the second end-to-end network slice includes a second core network slice, and the proxy node may carry the identifier in the network slice creation request. Identification of the second end-to-end network slice, to determine the second core network slice included in the second end-to-end network slice corresponding to the identification, and then to create a second core network slice included in the second end-to-end network slice The first core network slice of the shared resource. That is, the proxy node may create a first core network slice that shares resources with the core network slice included in the second end-to-end network slice according to the identity of the second end-to-end network slice.

The second end-to-end network slice includes a second core network slice. It can also be understood that the second core network slice belongs to the second end-to-end network slice.

In another possible implementation manner, the proxy node may create a first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs.

The resource sharing slice information of the core network to which the proxy node belongs may include information of a core network slice that has been created in the core network to which the proxy node belongs and supports resource sharing. For example, the information of the core network slice may include an identifier of the core network slice, a resource occupation rate, and the like. The resource occupation rate of the core network slice in this application may include the resource occupation rate of a virtual machine or a container in which the core network slice is deployed.

In the embodiment of the present application, the following uses core network slice information including the identifier of the core network slice or the identifier of the core network slice and the resource occupancy rate as an example to the proxy node according to the network slice creation request and the resources of the core network to which the proxy node belongs. Share slice information and create a first core network slice for illustration.

There may be one or more core network slices that have been created in the core network to which the proxy node belongs and support resource sharing.

In one example, when there is one core network slice that has been created in the core network to which the proxy node belongs and supports resource sharing, the resource sharing slice information of the core network to which the proxy node belongs may include the one that has been created, Moreover, the identifier of the core network slice supporting resource sharing is supported, and the proxy node may create a first core network slice of the core network slice shared resource corresponding to the identifier according to the identifier.

In another example, when there are at least two core network slices that have been created in the core network to which the proxy node belongs and support resource sharing, the resource sharing slice information of the core network to which the proxy node belongs may include at least two The identifier of the core network slice that has been created and supports resource sharing and the resource occupancy rate. In this example, the proxy node may determine the core network slice with the lowest resource occupancy among at least two core network slices included in the core network to which the proxy node belongs, and create a second core network slice according to the network slice creation request and the first The identification of the two core network slices creates a first core network slice that shares resources with the second core network slice. For example, assuming that the core network to which the proxy node belongs includes three core network slices that have been created, namely core network slice A, core network slice B, and core network slice C, the resource sharing slice of the core network to which the proxy node belongs The information may include the identification and resource occupancy of core network slice A, core network slice B, and core network slice C. It is further assumed that the identification of core network slice A is identification A, the resource occupancy rate is 30%, and the identification of core network slice B is Identity B, resource occupancy rate is 70%, core network slice C is identity C, and resource occupancy rate is 50%. After receiving the network slice creation request from NSMF, the proxy node can determine the need to create and The first end-to-end network slice of the created end-to-end network slice sharing resources can be further determined to create a first core network slice that shares resources with the created core network slice. In order to ensure that the created first core network slice has With sufficient resources, the proxy node can root to create a first core network slice that shares resources with the core network slice A that has the lowest resource usage. With the method provided by this example, the proxy node can create a first core network slice that shares resources with the core network slice that has been created and has the lowest resource usage according to the resource consumption of the core network slice in the core network to which the proxy node belongs. In order to optimize the effect of resource sharing. It solves the problem of low resource utilization caused by NSMF in the prior art because it cannot sense the resource consumption of subnet slices in the core network and access network. Obviously, the method of the present application can optimize the management of network slices.

In yet another example, the network slice creation request carries the identity of the second end-to-end network slice, and the resource sharing slice information of the core network to which the proxy node belongs includes the identity of the core network slice in the second end-to-end network slice. And resource usage. In this example, when the proxy node determines that the resource occupation rate of the core network slice in the second end-to-end network slice is less than a preset value, the proxy node determines the core network slice in the second end-to-end network slice as the second core Network slice, and create a first core network slice according to the network slice creation request and the identity of the second core network slice. For example, according to the requirements of the end-to-end network slice carried in the network slice creation request, a first core network slice that shares resources with the created core network slice may be created. The requirements of the end-to-end network slicing may include delay requirements, isolation requirements, and the like.

Exemplarily, assuming that the network slice creation request carries the identity 2 of the second end-to-end network slice, the resource sharing slice information of the core network to which the proxy node belongs includes the identity 22 of the core network slice in the second end-to-end network slice. And the resource occupancy rate is 40%, assuming the preset value is 50%, after receiving the network slice creation request from NSMF, the proxy node can determine the need to create a share with the created second end-to-end network slice according to the request The first end-to-end network slice of the resource can further determine the need to create a first core network slice that shares the resource with the core network slice in the second end-to-end network slice, and the proxy node can further determine the second end-to-end network slice The resource occupancy rate of the core network slice of 40% is less than a preset value of 50%, so that a first core network slice that shares resources with the core network slice in the second end-to-end network slice can be created. With the method provided by this example, the proxy node creates a first shared resource with the core network slice in the second end-to-end network slice when the resource occupation rate of the core network slice in the second end-to-end network slice is less than a preset value. A core network slice to optimize resource sharing.

It should be noted that the preset value can be set according to the actual application scenario. The principle for setting the preset value may be that after the core network slice with the resource occupancy rate less than the preset value shares resources with the first core network slice, the two core network slices sharing the resource can be used normally.

The network slicing management method provided by the embodiment of the present application is described in more detail below with reference to the flow shown in FIG. 4. As shown in FIG. 5, the flow of the network slice management method is as follows. The description of the new node in the CN is based on the proxy node.

Among them, S501-S503 can refer to the descriptions of S401-S403, which will not be repeated here.

In a possible implementation manner, the proxy node may receive the network slice creation request from the NSMF through the NSSMF in the CN, see S501a and S501b in FIG. 5.

In a possible implementation manner, the proxy node sends an access network slice creation request to an access network device supporting a network slice proxy through a default AMF, as shown in S503a-S503c in FIG. 5. After receiving the access network slice creation request from the proxy node by default, the AMF sends the access to the access network device supporting the network slice proxy in the access network according to the pre-stored identification of the access network device supporting the network slice proxy. Net slice creation request.

It should be noted that the access network device in FIG. 5 refers to an access network device that supports a network slicing agent.

In other possible designs, the proxy node may also interact with the access network device supporting the network slice proxy through another AMF (different from the default AMF), which is not limited in this application.

Among them, when the terminal is not sure to access a specific AMF after registering to the network, it chooses to access the default AMF.

It should be noted that the steps marked with a solid line in FIG. 5 are all steps that must be performed, such as S501, S502, and S503, and the steps marked with a dotted line are optional steps, such as S503a, S503c, S501a and S501b. In addition, steps marked with a solid line in the drawings involved in this application are all steps that must be performed, and steps marked with a dotted line are optional steps.

After the access network device supporting the network slice proxy in the access network receives the access network slice creation request sent by the proxy node, it may execute S504.

S504: The access network device supporting the network slice proxy in the access network creates a first access network slice according to the access network slice creation request.

For example, an access network device that supports a network slice proxy in the access network may create a first access network slice according to a delay requirement, an isolation requirement, etc. carried in the access network slice creation request.

The first access network slice and the created second access network slice share resources. The second core network slice and the second access network slice belong to the created second end-to-end network slice.

S505: The access network device supporting the network slice proxy in the access network sends a response message to the default AMF.

The response message may include the creation result of the access network slice. For example, the creation result may be the creation success or failure.

S506: The default AMF sends the first list to the proxy node according to the response message.

The first list may include the creation result of the access network slice included in the response message received by the default AMF within a preset time. For example, suppose that there are 500 access network devices in the access network that support network slicing agents. Each access network device that supports the network slicing agent can create the first access network slice according to the access network slice creation request. Send a response message including the creation result of the access network slice to the default AMF, but each access network device that supports the network slice agent may not send a response message to the default AMF at the same time, the default AMF can receive each support within a preset time The response message sent by the access network device of the network slicing agent. Assuming that the default AMF receives the response message sent by 450 access network devices that support the network slicing agent within a preset time, the 450 response messages can be included in the response message. The creation result of the access network slice forms a first list, and sends the first list to the proxy node.

S507: The proxy node receives the first list from the default AMF.

After the proxy node receives the first list sent by the default AMF, it can be processed by the proxy node in the CN domain. For example, if the creation result included in the first list does not include the creation failure, the first list is ignored. If the included creation result includes a creation failure, the creation process can be re-initiated for the access network slice that failed to be created.

Of course, instead of being processed by the agent node in the CN domain, S508 may be executed.

S508: The proxy node sends the first list to the NSMF.

Specifically, the NSMF performs subsequent processing after receiving the first list. For example, if the creation result included in the first list does not include the creation failure, the first list is ignored, and if the creation result included in the first list includes the creation failure, the creation process may be re-initiated for the slice that failed to be created.

In a possible implementation manner, the proxy node may send the first list to the NSMF through the NSSMF in the CN in step S508, see S508a and S508b in FIG. 5.

In the embodiment of the present application, an access network device supporting a network slice proxy can be understood as that an access network slice in the access network device can be managed by a proxy node. Among them, the ability of the proxy node to manage the access network slice in the access network device may be predetermined by the proxy node, NSMF, and access network device, or it may be real-time negotiation between the proxy node, NSMF, and access network device. definite.

In a possible implementation manner, before the proxy node receives the network slice creation request from the NSMF, the capability of the proxy node to manage the access network slice in the access network device is negotiated, see S500a-S500f in FIG. 5.

S500a: The access network device sends a first slice management proxy request to the default AMF.

The first slice management proxy request is used to request a network slice proxy for the access network device. The first slice management agent request may carry the identifier of the access network device.

Optionally, the first slice management agent request may further carry a slice agent support flag. The support slice proxy flag bit is used to indicate that the access network device supports a network slice proxy. The support slice proxy flag can be one or more bits.

Optionally, after receiving the first slice management agent request by default, the AMF may further confirm the first slice management agent request, and may further send an acknowledgement to the access network device to receive the first slice management agent. Requested confirmation message.

It should be noted that the number of the access network devices may be one or more. When the number of access network devices is one, the default AMF forwards the first slice management agent request to the proxy node after receiving the first slice management agent request sent by the access network device. When the number of access network devices is multiple, the default AMF may execute S500b after receiving the first slice management agent request sent by the access network device.

S500b: When the first ratio is greater than the first threshold, the default AMF sends a second slice management agent request to the proxy node according to the first slice management agent request.

The first ratio is a ratio of the number of access network devices in the access network that sends the first slice management agent request to the default AMF to the number of all access network devices included in the access network within a preset time. For example, assuming that there are 500 access network devices in the access network, and the number of access network devices that sends the first slice management agent request to the default AMF within the preset time is 450, the first ratio is 450 /500=0.9.

The second slice management agent request may carry the identifier of the access network to which the access network device supporting the network slice agent belongs. The second slice management proxy request is used to request the proxy node to perform a network slice proxy for an access network device in the access network. Optionally, the second slice management proxy request may also carry the identity of the proxy node.

Optionally, after receiving the second slice management agent request, the proxy node may further confirm the second slice management agent request, and may further send a confirmation message to the default AMF to confirm receipt of the second slice management agent request .

It should be noted that the first threshold may be an empirical value, and may be preset in a default AMF. For different application scenarios, the first threshold may be different.

S500d: The proxy node sends the third slice management proxy request to the NSMF according to the received second slice management proxy request.

Correspondingly, after receiving the third slice management agent request, the NSMF can learn that the above-mentioned proxy node can manage the access network slice in the access network, and will no longer manage the access network slice in the access network through NSMF. . For example, subsequent messages that the NSMF needs to send to the access network device in the access network may be sent by the proxy node.

The third slice management agent request may carry the identifier of the access network to which the access network device supporting the network slice agent belongs and the identifier of the proxy node. The third slice management proxy request is used to request the proxy node to perform a network slice proxy for an access network device in the access network.

In a possible implementation manner, the proxy node may send the third slice management proxy request to the NSMF through the NSSMF in the CN, refer to S500e and S500f in FIG. 5.

S500e: The proxy node sends the third slice management proxy request to the NSSMF in the CN.

S500f: The NSSMF in the CN sends the third slice management agent request to the NSMF.

Correspondingly, after receiving the third slice management agent request, the NSMF can learn that the above-mentioned proxy node can manage the access network slice in the access network, and will no longer manage the access network slice in the access network through NSMF. .

Optionally, after receiving the third slice management agent request, the NSMF may further confirm the third slice management agent request, and may further send a confirmation message to the proxy node to confirm receipt of the third slice management agent request.

The following uses the proxy node and NSMF to interact with the NSSMF in the CN, the proxy node and the access network device to interact with the default AMF, the network slice creation request to carry the identity of the second end-to-end network slice, and the proxy node is receiving the network from the NSMF Before the slice creation request, the ability of the proxy node to manage the access network slice in the access network device is taken as an example. For the above process of creating a network slice in FIG. 5, the message names involved, the network elements involved, and the main messages The types of cells, interfaces, and protocols carried are described in Table 1.

Table 1

In the scenario where NSSMF is deployed in the AN, referring to FIG. 3a, a proxy node can be added in the CN through the method of the above embodiment of the application. Referring to FIG. 6a, the NSMF can send a network slice creation request to the proxy node in the CN first. After the agent node creates the core network slice according to the network slice creation request, the agent node sends an access network slice creation request to the access network device supporting the network slice agent in the AN, and the agent node notifies the access network device CN The decision made by the side is to make the AN side refer to the decision made by the CN side, and then make a decision consistent with the CN side.

In the scenario where NSSMF is not deployed in the AN, referring to FIG. 3b, a proxy node can be added in the CN through the method of the above embodiment of the application. Referring to FIG. 6b, the NSMF can support the network slice proxy in the AN through the proxy node The access network device sends a network slice creation request to implement the creation of an end-to-end network slice. In addition, the AN side can also refer to the decision made by the CN side, and then make a decision consistent with the CN side.

Refer to FIG. 7, which is a flowchart of another network slice management method according to an embodiment of the present application. Figure 7 illustrates the integration of a proxy node on the NSSMF in the CN. In the implementation manner of FIG. 7, the operations performed by the proxy node can be understood as being performed by the NSSMF in the CN. Referring to FIG. 7, the operations performed by S700a-S700d in FIG. 7 can be referred to S500a-S500d in FIG. 5. For operations performed by S701-S708 in FIG. 7, refer to S501-S508 in FIG. 5, and details are not described herein again. The difference is that the operations performed by the proxy node in FIG. 5 are all performed by the NSSMF in the CN in FIG. 7.

It should be noted that the third slice management agent request in FIG. 7 may carry the identifier of the NSSMF in the CN.

It can be understood that, in the foregoing embodiment of the present application, network slice creation is used as an example for description. Similarly, the network slice update may also use the foregoing method embodiments, as shown in FIG. 8 and FIG. 9.

In the implementations shown in FIGS. 8 and 9, the operations performed by S800a-S800f can be referred to S500a-S500f in FIG. 5, and the operations performed by S900a-S900d can be referred to S500a-S500d in FIG. 5, and the proxy node in FIG. 8 In Figure 9, the NSSMF in the CN can also send an access network slice update request to an access network device that supports a network slice agent. The access network slice update request carries second instruction information, and the second instruction information is used to indicate the first core. The network slice and the created third core network slice share resources. In this way, the access network device may update the sharing relationship between the first access network slice and the created access network slice according to the second instruction information. For example, suppose the proxy node shares resources with the first core network slice and the second core network slice. , Updating to share resources between the first core network slice and the third core network slice, and the third core network slice and the third access network slice belong to the third end-to-end network slice, and the proxy node sends the second to the access network device Instruction information to enable the access network device to share resources of the first access network slice and the second access network slice to update the first access network slice and the third access network slice to share resources, so that after updating the network slice The AN and CN subnet slices belong to the same end-to-end network slice. In this implementation manner, the response message in S805 in FIG. 8 and the response message in S905 in FIG. 9 may carry the update result of the access network slice, such as the update success or failure. The second lists in FIG. 8 and FIG. 9 may include the update results of the access network slices fed back by multiple access network devices.

In the following, the proxy node and NSMF interact through the NSSMF in the CN, the proxy node and the access network device interact through the default AMF, and the ability of the proxy node to manage the access network slice in the access network device is the proxy node, NSMF, and access network device. Pre-agreed and the identification of the third end-to-end network slice carried in the network slice update request is taken as an example. For the above process of updating the network slice in FIG. 8, the message names involved, the network elements involved, and the messages that are mainly carried in the message Cells, interfaces / protocol types are described in Table 2.

Table 2

It can be understood that the network slice destruction may also use the foregoing method embodiments, as shown in FIG. 10 and FIG. 11.

In the implementation shown in FIG. 10 and FIG. 11, the operations performed by S1000a-S1000f can be referred to S500a-S500f in FIG. 5, and the operations performed by S1100a-S1100d can be referred to S500a-S500d in FIG. 5, and the proxy node in FIG. 10 In FIG. 11, the NSSMF in the CN may also send an access network slice destruction request to an access network device that supports a network slice agent, and the access network slice destruction request may carry the identifier of the first access network slice. For example, assuming that the proxy node destroys the first core network slice, the proxy node sends the identification of the first access network slice to the access network device, so that the access network device destroys the first access network slice. In this implementation manner, the response message in S1005 in FIG. 10 and the response message in S1105 in FIG. 11 may carry the destruction result of the access network slice, such as the destruction success or failure. The third list in FIG. 10 and FIG. 11 may include the destruction result of the access network slice fed back by multiple access network devices.

In the following, the proxy node and NSMF interact through the NSSMF in the CN, the proxy node and the access network device interact through the default AMF, and the ability of the proxy node to manage the access network slice in the access network device is the proxy node, NSMF, and access network device. Pre-agreed, and the identification of the first end-to-end network slice carried in the network slice destruction request is taken as an example. For the process of destroying the network slice shown in FIG. 10, the message names involved, the network elements involved, and the messages that are mainly carried in the message Cells, interfaces / protocol types are described in Table 3.

table 3

Based on the same inventive concept of the foregoing method embodiments, as shown in FIG. 12, an embodiment of the present application further provides a network slice management device 1200, which is configured to perform an operation performed by a proxy node in the foregoing network slice management method. The device 1200 may include a receiving unit 1201, a processing unit 1202, and a sending unit 1203.

A receiving unit 1201 is configured to receive a network slice creation request from the NSMF, where the network slice creation request is used to request the creation of a first end-to-end network slice that shares resources with the created end-to-end network slice, the first end The end-to-end network slice includes a first core network slice and a first access network slice;

A processing unit 1202, configured to create the first core network slice according to the network slice creation request, and the first core network slice and the created second core network slice share resources;

A sending unit 1203 is configured to send an access network slice creation request to an access network device supporting a network slice proxy, where the access network slice creation request is used to request creation of the first access network slice, and the access network The slice creation request carries first indication information, and the first indication information is used to instruct the first core network slice and the second core network slice to share resources.

In a possible implementation manner, the network slice creation request carries an identifier of a second end-to-end network slice, and the network slice creation request is used to request creation of a resource that is shared with the second end-to-end network slice. The first end-to-end network slice.

In a possible implementation manner, the second end-to-end network slice includes the second core network slice.

In a possible implementation manner, the processing unit 1202 is configured to create the first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs, and the proxy The resource sharing slice information of the core network to which the node belongs includes information of a core network slice that has been created in the core network and supports resource sharing.

In a possible implementation manner, the resource sharing slice information of the core network to which the proxy node belongs includes information of a core network slice that has been created and supports resource sharing, and the information of the core network slice includes information of the core network slice. Identification and resource usage. In this implementation manner, the processing unit 1202 is configured to determine a core network slice with the lowest resource occupancy rate among the core network slices as the second core network slice; and create the request according to the network slice and the network slice. The identification of the second core network slice creates the first core network slice.

In a possible implementation manner, the network slice creation request carries an identifier of a second end-to-end network slice, and resource sharing slice information of a core network to which the proxy node belongs includes the second end-to-end network slice. Information of the core network slice, and the information of the core network slice includes an identifier of the core network slice and a resource occupation rate. In this implementation manner, the processing unit 1202 is configured to, when the resource occupation rate of the core network slice in the second end-to-end network slice is less than a preset value, change the core in the second end-to-end network slice. The network slice is determined as the second core network slice; and the first core network slice is created according to the network slice creation request and the identity of the second core network slice.

In a possible implementation manner, the sending unit 1203 sends an access network slice creation request to an access network device that supports a network slice proxy through a default AMF. After the sending unit 1203 sends an access network slice creation request to an access network device supporting a network slice proxy through the default AMF, the receiving unit 1201 is further configured to receive a first list from the default AMF, and the first A list includes the creation result of the first access network slice by the access network device supporting the network slice proxy.

In a possible implementation manner, the sending unit 1203 is further configured to send the first list to the NSMF.

In a possible implementation manner, before receiving the network slice creation request from NSMF, the receiving unit 1201 is further configured to receive a slice management agent request from a default AMF, where the slice management agent request carries the access network. The identifier of the access network to which the device belongs is used to request the proxy node to perform a network slice proxy for the access network device in the access network; the sending unit 1203 is further configured to send the slice management to the NSMF Proxy request.

In a possible implementation manner, the sending unit 1203 is further configured to send an access network slice update request to the access network device supporting the network slice proxy, and the access network slice update request carries a second instruction. Information, and the second indication information is used to indicate that the first core network slice and the created third core network slice share resources.

Based on the same inventive concept of the foregoing method embodiments, as shown in FIG. 13, an embodiment of the present application further provides a network slice management apparatus 1300 for performing operations performed by an access network device in the foregoing network slice management method. The apparatus 1300 may include a receiving unit 1301 and a processing unit 1302. Optionally, it may further include a sending unit 1303.

A receiving unit 1301 is configured to receive an access network slice creation request from a proxy node. The access network slice creation request is used to request creation of a first access network slice, and the access network slice creation request carries a first instruction. Information, the first indication information is used to indicate that the first core network slice and the second core network slice share resources, and the access network device supports a network slice agent;

A processing unit 1302 is configured to create the first access network slice according to the access network slice creation request, and the first access network slice and the created second access network slice share resources; The first core network slice and the first access network slice belong to a first end-to-end network slice, and the second core network slice and the second access network slice belong to a created second end-to-end network slice.

In a possible implementation manner, the receiving unit 1301 receives an access network slice creation request from a proxy node through a default AMF. Before the receiving unit 1301 receives an access network slice creation request from a proxy node through a default AMF, the sending unit 1303 is configured to send a slice management proxy request to the default AMF, and the slice management proxy request carries a support for a slice proxy flag Bit and the identifier of the access network device, and the support slice proxy flag bit is used to indicate that the access network device supports a network slice proxy.

Based on the same inventive concept of the foregoing method embodiments, as shown in FIG. 14, an embodiment of the present application further provides a network slice management device 1400, which is configured to perform an operation performed by a default AMF in the foregoing network slice management method. The apparatus 1400 may include a receiving unit 1401 and a sending unit 1402. Optionally, it may further include a processing unit 1403.

The receiving unit 1401 is configured to receive an access network slice creation request from a proxy node, where the access network slice creation request is used to request creation of an access network slice, and the access network slice creation request carries first indication information, The first indication information is used to indicate that the first core network slice and the second core network slice share resources, and the default AMF and the proxy node belong to the same core network;

The sending unit 1402 is configured to send the access network slice creation request to an access network device that supports the network slice proxy in the access network according to a pre-stored identifier of the access network device that supports the network slice proxy.

In a possible implementation manner, after the sending unit 1402 sends the access network slice creation request to an access network device that supports a network slice proxy in an access network, the receiving unit 1401 is further configured to receive a request from the receiving unit 1401. A response message of the access network device, where the response message includes a creation result of the access network slice; the sending unit 1402 is configured to send a first list to the proxy node according to the received response message, and the first list The creation result of the access network slice included in the response message received by the default AMF within a preset time is included.

In a possible implementation manner, before the receiving unit 1401 is configured to receive an access network slice creation request from a proxy node, it may also be configured to receive a first slice management proxy request from the access network device. The first slice management agent request carries a support slice agent flag bit and an identifier of the access network device, and the support slice agent flag bit is used to indicate that the access network device supports a network slice agent; the sending unit 1402 is further configured to send a second slice management agent request to the proxy node according to the first slice management agent request when the first ratio is greater than a first threshold, where the first ratio is within a preset time A ratio of the number of access network devices in the access network that sends the first slice management agent request to the default AMF to the number of all access network devices included in the access network, the first The two-slice management agent request carries the identifier of the access network, and is used to request the proxy node to perform a network slice proxy for the access network device in the access network.

Based on the same inventive concept of the foregoing method embodiments, as shown in FIG. 15, an embodiment of the present application further provides a network slice management device 1500 for performing operations performed by the NSMF in the foregoing network slice management method. The apparatus 1500 may include a receiving unit 1501 and a sending unit 1502.

A receiving unit 1501 is configured to receive a slice management proxy request from an agent node, where the slice management proxy request carries an identifier of an access network and the identity of the proxy node, and the slice management proxy request is used to request the proxy node Performing a network slice proxy for an access network device in the access network;

A sending unit 1502 is configured to send a network slice creation request carrying the identifier of the proxy node to the proxy node, where the network slice creation request is used to request the creation of an end-to-end shared resource with the created end-to-end network slice A network slice, which includes a core network slice and an access network slice.

In a possible implementation manner, the receiving unit 1501 is further configured to receive a first list from the proxy node, where the first list includes a creation result of the access network slice.

Based on the same inventive concept as the above method embodiment, as shown in FIG. 16, an embodiment of the present application further provides a network slice management device 1600, which is used to implement the proxy node and access in the method provided by the above embodiment. The operations performed by network equipment, default AMF, or NSMF are for brief description. The schematic diagram of the possible physical devices of each network element is illustrated by referring to FIG. 16. It can be understood that FIG. 16 is only a schematic diagram and can be applied to each of the foregoing. Different network elements. The network slice management device 1600 includes a transceiver 1601, a processor 1602, and a memory 1603. The processor 1602 is configured to call a group of programs, and when the programs are executed, cause the processor 1602 to perform operations performed by the proxy node, the access network device, the default AMF, or the NSMF in one of the methods provided by the foregoing embodiments. The memory 1603 is configured to store a program executed by the processor 1602. The above-mentioned sending unit and receiving unit in FIG. 11 to FIG. 14 may be implemented by the transceiver 1601, and the processing unit may be implemented by the processor 1602.

The processor 1602 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.

The processor 1602 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

The memory 1603 may include volatile memory (for example, random-access memory (RAM); the memory 1603 may also include non-volatile memory (for example, flash memory) memory), hard disk (HDD) or solid-state drive (SSD); the memory 1603 may also include a combination of the above types of memory.

In the method provided by the foregoing embodiments of the present application, some or all of the operations and functions performed by the described network element or device may be completed by a chip or an integrated circuit.

In order to implement the functions of the device described in FIG. 12 to FIG. 16, an embodiment of the present application further provides a chip, including a processor, for supporting the device to implement functions related to the method provided in the foregoing embodiment. In a possible design, the chip is connected to a memory or the chip includes a memory, and the memory is used to store program instructions and data necessary for the device.

An embodiment of the present application provides a computer storage medium storing a computer program, where the computer program includes instructions for executing the method provided by the foregoing embodiment.

The embodiment of the present application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the method provided by the foregoing embodiment.

Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

This application is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, so that the instructions generated by the processor of the computer or other programmable data processing device are used to generate Means for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions The device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Although the preferred embodiments of the present application have been described, those skilled in the art can make other changes and modifications to these embodiments once they know the basic inventive concepts. Therefore, the following claims are intended to be construed to include the preferred embodiments and all changes and modifications that fall within the scope of this application.

Obviously, those skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application also intends to include these changes and variations.

Claims

A network slice management method is characterized in that it includes:

The proxy node receives a network slice creation request from the network slice management function NSMF. The network slice creation request is used to request the creation of a first end-to-end network slice that shares resources with the created end-to-end network slice. The first end The end-to-end network slice includes a first core network slice and a first access network slice;

The proxy node creates the first core network slice according to the network slice creation request, and the first core network slice and the created second core network slice share resources;

The proxy node sends an access network slice creation request to an access network device supporting a network slice proxy, where the access network slice creation request is used to request creation of the first access network slice, and the access network slice creation The request carries first indication information, and the first indication information is used to instruct the first core network slice and the second core network slice to share resources.
The method according to claim 1, wherein the network slice creation request carries an identifier of a second end-to-end network slice, and the network slice creation request is used to request creation of a connection with the second end-to-end network Slicing the first end-to-end network slice of a shared resource.
The method of claim 2, wherein the second end-to-end network slice includes the second core network slice.
The method according to claim 1 or 2, wherein the creating, by the proxy node, the first core network slice according to the network slice creation request comprises:

The proxy node creates the first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs, and the resource sharing slice information of the core network to which the proxy node belongs includes This section describes information about core network slices that have been created in the core network and support resource sharing.
The method according to claim 4, wherein the resource sharing slice information of the core network to which the proxy node belongs includes information of a core network slice that has been created and supports resource sharing, and the information of the core network slice includes Identification and resource occupancy of core network slices;

The creating, by the proxy node, the first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs, includes:

Determining, by the proxy node, the core network slice with the lowest resource occupancy rate among the core network slices as the second core network slice;

The proxy node creates the first core network slice according to the network slice creation request and the identity of the second core network slice.
The method according to claim 4, wherein the network slice creation request carries an identifier of a second end-to-end network slice, and resource sharing slice information of a core network to which the proxy node belongs includes the second end Information of the core network slice in the end-to-end network slice, and the information of the core network slice includes an identifier of the core network slice and a resource occupation rate;

The creating, by the proxy node, the first core network slice according to the network slice creation request and resource sharing slice information of a core network to which the proxy node belongs, includes:

When the resource occupation rate of the core network slice in the second end-to-end network slice is less than a preset value, the proxy node determines the core network slice in the second end-to-end network slice as the second core network slice;

The proxy node creates the first core network slice according to the network slice creation request and the identity of the second core network slice.
The method according to any one of claims 1 to 6, wherein the sending, by the proxy node, an access network slice creation request to an access network device supporting a network slice proxy comprises:

The proxy node sends an access network slice creation request to an access network device supporting a network slice proxy through a default access and mobility management function AMF;

After the proxy node sends the access network slice creation request to the access network device supporting the network slice proxy through the default AMF, the method further includes:

The proxy node receives a first list from the default AMF, where the first list includes a creation result of the first access network slice by the access network device supporting the network slice proxy.
The method according to claim 7, further comprising:

The proxy node sends the first list to the NSMF.
The method according to any one of claims 1 to 8, wherein before the proxy node receives a network slice creation request from NSMF, further comprising:

The proxy node receives a slice management proxy request from a default AMF, and the slice management proxy request carries an identifier of an access network to which the access network device belongs, and is used to request the proxy node to be in the access network. Access network equipment for network slicing proxy;

The proxy node sends the slice management proxy request to the NSMF.
The method according to any one of claims 1 to 9, further comprising:

Sending, by the proxy node, an access network slice update request to an access network device that supports a network slice proxy, where the access network slice update request carries second instruction information, and the second instruction information is used to indicate the The first core network slice and the created third core network slice share resources.
A network slice management method is characterized in that it includes:

The access network device receives an access network slice creation request from a proxy node, where the access network slice creation request is used to request creation of a first access network slice, and the access network slice creation request carries first instruction information, The first indication information is used to indicate that the first core network slice and the second core network slice share resources, and the access network device supports a network slice agent;

The access network device creates the first access network slice according to the access network slice creation request, and the first access network slice and the created second access network slice share resources;

The first core network slice and the first access network slice belong to a first end-to-end network slice, and the second core network slice and the second access network slice belong to a created second end. End-to-end network slicing.
The method according to claim 11, wherein the access network device receiving an access network slice creation request from a proxy node comprises:

The access network device receives an access network slice creation request from a proxy node through a default access and mobility management function AMF;

Before the access network device receives an access network slice creation request from a proxy node, the method further includes:

The access network device sends a slice management proxy request to the default AMF. The slice management proxy request carries a support slice proxy flag and an identifier of the access network device, and the support slice proxy flag is used to indicate The access network device supports a network slicing agent.
A network slice management method is characterized in that it includes:

The default access and mobility management function AMF receives an access network slice creation request from a proxy node, the access network slice creation request is used to request the creation of an access network slice, and the access network slice creation request carries a first Instruction information, where the first instruction information is used to indicate that the first core network slice and the second core network slice share resources, and the default AMF and the proxy node belong to the same core network;

The default AMF sends the access network slice creation request to the access network device supporting the network slice proxy in the access network according to a pre-stored identifier of the access network device supporting the network slice proxy.
The method according to claim 13, wherein after the default AMF sends the access network slice creation request to an access network device that supports a network slice proxy in the access network, further comprising:

Receiving, by the default AMF, a response message from the access network device, where the response message includes a creation result of the access network slice;

The default AMF sends a first list to the proxy node according to the response message, where the first list includes a creation result of an access network slice included in a response message received by the default AMF within a preset time. .
The method according to claim 13 or 14, before the default AMF receiving an access network slice creation request from a proxy node, further comprising:

The default AMF receives a first slice management proxy request from the access network device, and the first slice management proxy request carries a support for a slice proxy flag and an identifier of the access network device, and the support The slice proxy flag bit is used to indicate that the access network device supports a network slice proxy;

When the first ratio is greater than the first threshold, the default AMF sends a second slice management proxy request to the proxy node according to the first slice management proxy request;

The first ratio is the number of access network devices in the access network that sends the first slice management agent request to the default AMF within a preset time and the number of access network devices included in the access network. Ratio of the number of all access network devices, the second slice management agent request carries the identity of the access network, and the second slice management agent request is used to request the proxy node to be in the access network Access network device performs network slicing proxy.
A network slice management method is characterized in that it includes:

The network slice management function NSMF receives a slice management proxy request from a proxy node, and the slice management proxy request carries an identification of the access network and the identity of the proxy node, and is used to request the proxy node to be in the access network Access network equipment for network slicing proxy;

Sending, by the NSMF to the proxy node, a network slice creation request carrying the identity of the proxy node, the network slice creation request is used to request creation of an end-to-end network slice that shares resources with the created end-to-end network slice, The end-to-end network slice includes a core network slice and an access network slice.
The method according to claim 16, further comprising:

The NSMF receives a first list from the proxy node, and the first list includes a creation result of the access network slice.
A network slice management device, comprising: a processor, the processor being coupled to a memory;

Memory for storing computer programs;

A processor for executing a computer program stored in the memory, so that the apparatus executes the method according to any one of claims 1-10.
A network slice management device, comprising: a processor, the processor being coupled to a memory;

Memory for storing computer programs;

A processor for executing a computer program stored in the memory, so that the apparatus executes the method according to any one of claims 11-12.
A network slice management device, comprising: a processor, the processor being coupled to a memory;

Memory for storing computer programs;

A processor for executing a computer program stored in the memory, so that the apparatus executes the method according to any one of claims 13-15.
A network slice management device, comprising: a processor, the processor being coupled to a memory;

Memory for storing computer programs;

A processor for executing a computer program stored in the memory, so that the apparatus executes the method according to any one of claims 16-17.