A configuration method and corresponding device

Abstract

A configuration method and a corresponding device are used to provide a mechanism for configuring the network slices supported by the RAN. The configuration method includes: a first network management device sends network slice configuration information to a second network management device, the network slice configuration information includes information indicating the network slices supported by the access network RAN, and the second network management device has the function of configuring the RAN; the first network management device receives a message returned by the second network management device indicating that the configuration of the RAN is completed.

Description

[0001] This application is a divisional application submitted to the China Patent Office on September 4, 2017, with application number 201710786862.5 and application name “A configuration method and corresponding device”. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a configuration method and a corresponding device. Background Art

[0003] A network slice (NS) refers to a different logical network customized according to different service requirements on top of a physical or virtual network infrastructure. Different radio access network (RAN) devices in the network may support different network slices. In many scenarios, RAN devices need to obtain information about the network slices they support. For example, RAN devices need to send information about the network slices they support to the access and mobility management function (AMF) so that AMF can configure a tracking area identity (TAI) list for the RAN device. For another example, neighboring RAN devices may need to exchange information about the network slices supported by their own nodes so that RAN devices can perform slice-aware switching management. However, the prior art lacks a mechanism for configuring RAN devices with the network slices they support. Summary of the invention

[0004] The present application provides a configuration method and a corresponding device to provide a mechanism for configuring the RAN with the network slices it supports.

[0005] In a first aspect, the present application provides a configuration method, comprising: a first network management device sends network slice configuration information to a second network management device, so that the second network management device sends the network slice configuration information to a RAN, wherein the network slice configuration information includes information indicating network slices supported by the RAN, the first network management device may be a module for managing network slices, or a module for managing network slice subnets, or a module for managing the entire network, etc., and the second network management device has a function of configuring the RAN. Then, the first network management device receives a message returned by the second network management device indicating that the configuration of the RAN is completed.

[0006] In the above technical solution, the first network management device is responsible for forming network slice configuration information for configuring the network slice of the RAN device, but it may not directly send the network slice configuration information to the RAN device. Instead, the network slice configuration information of one or more RAN devices is sent to the second network management device, and the second network management device is responsible for sending its corresponding network slice configuration information to the RAN device. This not only enables the configuration of network slices supported by the RAN device, but also because the above-mentioned first network management device and the second network management device have clear division of labor, their respective burdens will not be too heavy, so that the system for configuring network slices can run efficiently.

[0007] In combination with the first aspect, in a first possible implementation of the first aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each TAI configured for each cell of the RAN. Based on this implementation, the network slice configuration information configures supported network slices for each TAI of each cell of the RAN. Since the traditional configuration method configures TAI for the cell, this implementation method makes fewer modifications to the traditional method and configuration content, and thus the implementation cost is relatively low.

[0008] In combination with the first aspect, in a second possible implementation of the first aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each tracking area identifier TAI configured by the RAN. Based on this implementation, the RAN can configure the network slices supported by each TAI according to the network slice configuration information, and only configure each TAI once, thereby avoiding repeated indication of the network slices supported by the same TAI in different cells, reducing the data volume of the network slice configuration information, reducing the transmission time and transmission resource consumption of the network slice configuration information, and improving the configuration efficiency.

[0009] In combination with the first aspect and any one of the first to second possible implementations of the first aspect, in a third possible implementation of the first aspect, the information of the network slice includes: single network slice selection auxiliary information S-NSSAI.

[0010] In combination with the first aspect and any one of the first to third possible implementations of the first aspect, in a fourth possible implementation of the first aspect, the network slice configuration information further includes: information indicating available frequencies of network slices supported by the RAN. This implementation enables the RAN to configure the supported network slices and the available frequencies of each network slice at the same time.

[0011] In combination with the first aspect and any one of the first to third possible implementations of the first aspect, in a fifth possible implementation of the first aspect, after the first network management device sends the network slice configuration information to the second network management device, the first network management device also sends spectrum configuration information to the second network management device, where the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN. In this implementation, it is possible to configure only the available frequencies of the network slices, and this configuration method is flexible and convenient for adjusting the available frequencies corresponding to part or all of the S-NSSAI of the RAN.

[0012] In combination with the first aspect and any one of the first to fifth possible implementations of the first aspect, in a sixth possible implementation of the first aspect, the network slice configuration information further includes: information indicating at least one TAI configured for each cell of the RAN. This implementation enables the RAN to configure the TAI of the cell and the supported network slices according to the network slice configuration information, which is more efficient.

[0013] In combination with the first aspect and any one of the first to fifth possible implementations of the first aspect, in a seventh possible implementation of the first aspect, before sending the network slice configuration information to the second network management device, the first network management device also sends tracking area configuration information to the second network management device, where the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN. This implementation facilitates adjustment of network slices supported by the RAN.

[0014] In combination with the first aspect and any one of the first to seventh possible implementations of the first aspect, in the eighth possible implementation of the first aspect, the first network management device is a network manager NM or a network slice management function NSMF module, and the second network management device is an equipment manager EM or a network function NF manager; or, the first network management device is an NSMF module, and the second network management device is a network slice subnet management function NSSMF module, and the NSSMF module is integrated with an EM or NF manager; or, the first network management device is an NSSMF module, and the second network management device is an EM or NF manager. In the embodiments of the present invention, the implementation methods of the first network management device and the second network management device are diverse and flexible, and can be applied to communication networks in various scenarios.

[0015] In combination with the first aspect and any one of the first to eighth possible implementations of the first aspect, in a ninth possible implementation of the first aspect, before the first network management device sends the network slice configuration information to the second network management device, the first network management device generates or receives the network slice configuration information. In this implementation, the first network management device obtains the network slice configuration information in a flexible manner, which facilitates implementation and improves the efficiency of configuring the network slice of the RAN device.

[0016] In a second aspect, the present application provides a configuration method, comprising: a second network management device sends network slice configuration information to a RAN, wherein the network slice configuration information includes information indicating network slices supported by the RAN; and the second network management device receives a message returned by the RAN indicating that the network slice configuration is complete. In this implementation, the second network management device sends the network slice configuration information to the RAN so that the RAN can configure the network slice based on the network slice configuration information.

[0017] In combination with the second aspect, in a first possible implementation of the second aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each TAI configured for each cell of the RAN. Based on this implementation, the network slice configuration information configures supported network slices for each TAI of each cell of the RAN. Since the RA is configured for the cell in the traditional configuration method, this implementation method has fewer modifications to the traditional method and configuration content, and thus the implementation cost is relatively low.

[0018] In combination with the second aspect, in a second possible implementation of the second aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each tracking area identifier TAI configured by the RAN. Based on this implementation, the RAN can configure the network slices supported by each TAI according to the network slice configuration information, and only configure each TAI once, thereby avoiding repeated indication of the network slices supported by the same TAI in different cells, reducing the amount of data of the network slice configuration information, reducing the transmission time and transmission resource consumption of the network slice configuration information, and improving the configuration efficiency.

[0019] In combination with the second aspect and any one of the first to second possible implementations of the second aspect, in a third possible implementation of the second aspect, the information of the network slice includes: S-NSSAI.

[0020] In combination with the second aspect and any one of the first to third possible implementations of the second aspect, in a fourth possible implementation of the second aspect, the network slice configuration information further includes: information indicating available frequencies of network slices supported by the RAN. This implementation enables the RAN to configure the supported network slices and the available frequencies of each network slice at the same time.

[0021] In combination with the second aspect and any one of the first to third possible implementations of the second aspect, in a fifth possible implementation of the second aspect, after the second network management device sends the network slice configuration information to the RAN, it also sends spectrum configuration information to the RAN, where the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN. In this implementation, it is possible to configure only the available frequencies of the network slices, and this configuration method is flexible and convenient for adjusting the available frequencies corresponding to some or all of the S-NSSAI of the RAN.

[0022] In combination with the second aspect and any one of the first to fifth possible implementations of the second aspect, in a sixth possible implementation of the second aspect, the network slice configuration information further includes: information indicating at least one TAI configured for each cell of the RAN. This implementation enables the RAN to configure the TAI of the cell and the supported network slices at the same time according to the network slice configuration information, which is more efficient.

[0023] In combination with the second aspect and any one of the first to fifth possible implementations of the second aspect, in a seventh possible implementation of the second aspect, the second network management device sends tracking area configuration information to the RAN before sending the network slice configuration information to the RAN, where the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN. This implementation facilitates adjustment of network slices supported by the RAN.

[0024] In combination with the second aspect and any one of the first to seventh possible implementations of the second aspect, in the eighth possible implementation of the second aspect, before the second network management device sends the network slice configuration information to the RAN, it also receives the network slice configuration information sent by the first network management device. In this implementation, the first network management device can send network slice configuration information of multiple RAN devices to the second network management device, and the second network management device sends its network slice configuration information to the RAN devices one by one, so as to efficiently configure the network slices supported by the RAN through the upper two-layer architecture.

[0025] In combination with the second aspect and any one of the first to eighth possible implementations of the second aspect, in a ninth possible implementation of the second aspect, after the second network management device receives the message returned by the RAN indicating that the network slice configuration is complete, it also sends a message to the first network management device indicating that the RAN configuration is complete. In this implementation, the second network management device can feed back the network slice configuration result to the first network management device, so that the first network management device can learn the actual configuration status of the network slice configuration information issued by it.

[0026] In a third aspect, the present application provides a configuration method, including: a RAN receives network slice configuration information sent by a network management device, the network slice configuration information includes information indicating network slices supported by the RAN, and the network management device has a function of configuring the RAN; after the RAN configures the supported network slices according to the network slice configuration information, the RAN returns a message indicating that the network slice configuration is complete to the network management device. In this implementation, the RAN can implement the configuration of the network slice based on the received network slice configuration information.

[0027] In combination with the third aspect, in a first possible implementation of the third aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each TAI configured for each cell of the RAN. Based on this implementation, the RAN can configure the network slices supported by each TAI of each cell according to the network slice configuration information.

[0028] In combination with the third aspect, in a second possible implementation of the third aspect, the information indicating the network slices supported by the RAN is specifically: information indicating the network slices supported by each tracking area identifier TAI configured by the RAN. Based on this implementation, the RAN can configure the network slices supported by each TAI according to the network slice configuration information, and only configure each TAI once, thereby avoiding repeated indication of the network slices supported by the same TAI in different cells, reducing the data volume of the network slice configuration information, reducing the transmission time and transmission resource consumption of the network slice configuration information, and improving the configuration efficiency.

[0029] In combination with the third aspect and any one of the first to second possible implementations of the third aspect, in a third possible implementation of the third aspect, the information of the network slice includes: S-NSSAI.

[0030] In combination with the third aspect and any one of the first to third possible implementations of the third aspect, in a fourth possible implementation of the third aspect, the network slice configuration information also includes: information indicating the available frequencies of the network slices supported by the RAN.

[0031] In combination with the third aspect and any one of the first to third possible implementations of the third aspect, in a fifth possible implementation of the third aspect, after the RAN receives the network slice configuration information sent by the network management device, the RAN also receives spectrum configuration information sent by the network management device, and the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN.

[0032] In combination with the third aspect and any one of the first to fifth possible implementations of the third aspect, in a sixth possible implementation of the third aspect, the network slice configuration information further includes: information indicating at least one TAI configured for each cell of the RAN. This implementation enables the RAN to configure the TAI of the cell and the supported network slices according to the network slice configuration information, which is more efficient.

[0033] In combination with the third aspect and any one of the first to fifth possible implementations of the third aspect, in the seventh possible implementation of the third aspect, before receiving the network slice configuration information sent by the network management device, the RAN also receives tracking area configuration information sent by the network management device, and the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN.

[0034] In a fourth aspect, the present application provides a network management device, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the device includes a module for executing the method in the first aspect or any possible implementation of the first aspect.

[0035] In a fifth aspect, the present application provides a network management device, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the device includes a module for executing the method in the second aspect or any possible implementation of the second aspect.

[0036] In a sixth aspect, the present application provides a RAN, the device being used to execute the method in the third aspect or any possible implementation of the third aspect. Specifically, the device includes a module for executing the method in the third aspect or any possible implementation of the third aspect.

[0037] In a seventh aspect, the present application provides a communication device, which may be the first network management device in the first aspect or any possible implementation of the first aspect, or a chip of the first network management device. The communication device includes a processor, a memory, and a transceiver, wherein the processor is coupled to the memory and the transceiver, and the memory is used to store computer executable program code, and the computer executable program code includes instructions, and when the processor executes the instructions, the communication device executes the method in the first aspect or any possible implementation of the first aspect.

[0038] In an eighth aspect, the present application provides a communication device, which may be the second network management device in the second aspect or any possible implementation of the second aspect, or a chip of the second network management device. The communication device includes a processor, a memory, and a transceiver, wherein the processor is coupled to the memory and the transceiver, and the memory is used to store a computer executable program code, and the computer executable program code includes instructions, and when the processor executes the instructions, the communication device executes the method in the second aspect or any possible implementation of the second aspect.

[0039] In a ninth aspect, the present application provides a communication device, which may be the RAN in the third aspect or any possible implementation of the third aspect, or a chip of the RAN. The communication device includes a processor, a memory, and a transceiver, wherein the processor is coupled to the memory and the transceiver, and the memory is used to store computer executable program code, and the computer executable program code includes instructions, and when the processor executes the instructions, the communication device executes the method in the third aspect or any possible implementation of the third aspect.

[0040] In a tenth aspect, the present application provides a computer-readable storage medium, which stores computer instructions. When the instructions are executed on a computer, the computer executes the methods in the first to third aspects and any possible implementations thereof.

[0041] In an eleventh aspect, the present application provides a computer program product, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the methods in the first to third aspects and any possible implementations thereof.

[0042] In the twelfth aspect, a chip is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, and the computer program is used to implement the methods in the above-mentioned first to third aspects and any possible implementation methods thereof.

[0043] Based on the implementations provided in the above aspects, the present application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 is a schematic diagram of a network slice management system;

[0045] Figure 2 A schematic diagram of a system for managing network elements;

[0046] Figure 3 A schematic diagram of a system for managing network functions;

[0047] Figure 4 is a schematic diagram of a communication system in an embodiment of the present invention;

[0048] Figure 5 is another schematic diagram of a communication system in an embodiment of the present invention;

[0049] Figure 6-Figure 7 A schematic diagram of a configuration method according to an embodiment of the present invention;

[0050] Figure 8-Figure 10 A schematic diagram of a network management device in an embodiment of the present invention;

[0051] Fig.11 FIG. 4 is a schematic diagram of a RAN in an embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the embodiments of the present invention more clear, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0053] The embodiment of the present invention provides a configuration method and a corresponding device, which are used to provide a mechanism for configuring the network slices supported by the RAN. The configuration method and the device (such as a network management device and a RAN) are based on the same inventive concept. Since the method and the device solve the problem in a similar way, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0054] It should be understood that the multiple involved in the embodiments of the present invention refers to two or more. In addition, in the description of the embodiments of the present invention, the words "first", "second", etc. are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. The term "and / or" in the embodiments of the present invention is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone.

[0055] The embodiments of the present invention can be applicable to the fifth-generation mobile communication (5G) system, and can also be applicable to other wireless communication systems, such as the Long Term Evolution (LTE) system, the Global System for Mobile Communication (GSM), the Universal Mobile Telecommunications System (UMTS), the Code Division Multiple Access (CDMA) system, and new network equipment systems.

[0056] Some concepts involved in the embodiments of the present invention are first introduced below.

[0057] Network slicing: refers to different logical networks customized according to different service requirements on top of physical or virtual network infrastructure. A network slice can be a complete end-to-end network including terminals, access networks, transmission networks, core networks and application servers, which can provide complete telecommunications services and have certain network capabilities; a network slice can also be any combination of the above terminals, access networks, transmission networks, core networks and application servers. Network slices may have one or more of the following characteristics: The access network may or may not be sliced. The access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that make them up may be different.

[0058] Network slice instance (NSI): a real running logical network that can meet certain network characteristics or service requirements. A network slice instance may provide one or more services. A network slice instance can be created by a network management system. A network management system may create multiple network slice instances and manage them at the same time, including performance monitoring and fault management during the operation of network slice instances. When multiple network slice instances coexist, some network resources and network functions may be shared between network slice instances. A network slice instance may or may not be created from a network slice template. A complete network slice instance is capable of providing complete end-to-end network services, and a network slice instance may be composed of a network slice subnet instance (NSSI) and / or a network function (NF). Network functions may include physical network functions and / or virtual network functions. The following collectively refers to physical network functions and / or virtual network functions as network functions.

[0059] Network slice subnet instance NSSI: A network slice subnet instance may not need to provide end-to-end complete network services. A network slice subnet instance may be a collection of network functions of the same equipment vendor in a network slice instance, or a collection of network functions divided by domains, such as a core network slice subnet instance, an access network slice subnet instance, or a collection composed of other methods such as deployment location. A network slice subnet instance may be shared by multiple network slice instances. Proposing a network slice subnet instance can facilitate the management of the network management system. A network slice instance may be composed of several network slice subnet instances, each of which is composed of several network functions and / or several network slice subnet instances; a network slice instance may be composed of several network slice subnet instances and network functions that are not divided into network slice subnet instances; a network slice instance may also be composed of only several network functions.

[0060] Network function NF: A processing function in the network that defines functional behaviors and interfaces. Network functions can be implemented through dedicated hardware, by running software on dedicated hardware, or as virtual functions on general-purpose hardware platforms. Therefore, from the perspective of implementation, network functions can be divided into physical network functions and virtual network functions. From the perspective of use, network functions can be divided into exclusive network functions and shared network functions. Specifically, for multiple (sub) network slice instances, different network functions can be used independently, which is called an exclusive network function, or the same network function can be shared, which is called a shared network function.

[0061] The access network includes one or more access network devices, which may be a base station, a base station (gNode B, gNB) in 5G communication, an evolved base station (evolutional eNodeB) in evolved LTE, or other devices that support network slicing.

[0062] Tracking area (TA): TA is a concept established for UE location management. It is defined as a free movement area where the UE does not need to update services. The TA function is to manage the terminal location, which can be divided into paging management and location update management. The UE informs the core network of its TA through a location update message.

[0063] Tracking area identification code TAI can include tracking area code (TA code, TAC) and public land mobile network (public land mobile network, PLMN), where a cell can only be configured with one TAC, but can be configured with one or more PLMNs, different cells belonging to the same base station can be configured with the same TAC, or different TACs, different cells belonging to the same base station can be configured with the same PLMN, or different PLMNs, therefore, a cell can be configured with one or more TAIs, different cells belonging to the same base station can be configured with different TAIs, or the same TAI. UE is assigned a TAI list. When the UE moves in a TA in the TAI list, it does not need to send a location update message to the core network (except for periodic location update). When the UE moves to a TA that is not in the TAI list, the UE needs to send a location update message to the core network. When the UE is in an idle state, the core network can know that the UE is in a TA in the TAI list. At the same time, when the UE in the idle state needs to be paged, it must be paged in all cells in the TAI list corresponding to the UE.

[0064] Single Network Slice Selection Assistance information (S-NSSAI) is used to distinguish different network slices (but it does not mean that S-NSSAI has a one-to-one correspondence with network slice instances). SST has several standardized types, including enhanced mobile broadband (EMBB) type, ultra reliable & low latency communication (URLLC) type, and massive internet of things (MIoT) type, and the corresponding SST values ​​are 1, 2, and 3 respectively. S-NSSAI includes a slice / service type SST (slice / service type). Optionally, S-NSSAI may also include a slice differentiator (SD). In an embodiment of the present invention, one or more S-NSSAIs may be supported for the same TAI, and multiple S-NSSAIs supported by the same TAI may be represented as S-NSSAIs.

[0065] The network slice management system is the part of the communication network that manages network slices. Figure 1The network slice management system may include a communication service management function (CSMF) module, a network slice management function (NSMF) module, and a network slice subnet management function (NSSMF) module.

[0066] Among them, the CSMF module can be responsible for converting the communication service needs of operators and / or third-party customers into needs for networks (slices), and sending needs for network slices (such as creation, termination, modification of network slice instance requests, etc.) to NSMF through the interface between NSMF and NSMF, obtaining management data of network slices (such as performance, fault data, etc.) from NSMF, generating management data of communication services running on network slice instances, receiving subscription needs of operators and / or third-party customers for network slice management data and / or communication service management data, etc.

[0067] The NSMF module can be responsible for receiving network slicing requirements sent by CSMF, managing the life cycle, performance, faults, etc. of network slice instances (hereinafter referred to as life cycle, performance, and fault management), orchestrating the composition of network slice instances, decomposing the requirements of network slice instances into the requirements of each network slice subnet instance and / or network function, and sending network slice subnet instance management requests to each NSSMF.

[0068] The NSSMF module can be responsible for receiving the network slice subnet requirements sent by NSMF, managing the network slice subnet instances, orchestrating the composition of the network slice subnet instances, decomposing the requirements of the network slice subnet instances into the requirements of each network function and / or nested network slice subnet instances, and may send nested network slice subnet instance management requests to other NSSMFs.

[0069] The above three modules are modules used for network slice management in the management system. The embodiments of the present invention do not limit the locations of these three modules and whether they exist independently.

[0070] Optionally, the management system in the communication network may further include:

[0071] The network manager (NM) is used to manage the entire communication network and send instructions to other modules in the network management system.

[0072] The element manager (EM) is responsible for configuring a network element. Figure 2EM can be an independent device, or it can be directly located on a network element, or it can be integrated on a domain manager (DM).

[0073] The network function NF manager is used to configure the network function. Figure 3 The NF manager can be an independent device or directly located on the NF. It may also be integrated with a domain manager or NSSMF module, or there may be a NF manager under the management of the NSSMF module.

[0074] Figure 4 This is a schematic diagram of a communication system in an embodiment of the present invention, wherein the management system of the communication network includes a first network management device and a second network management device, the first network management device sends a configuration message of the RAN to the second network management device, and the second network management device specifically implements the configuration of the RAN.

[0075] The first network management device and the second network management device may be implemented in a variety of ways, including but not limited to the following scenarios:

[0076] (1) The first network management device includes a network manager NM or a network slice management function NSMF module, and the second network management device includes an equipment manager EM or a network function NF manager.

[0077] (2) The first network management device includes an NSMF module, and the second network management device includes an NSSMF module. The NSSMF module is integrated with an EM or NF manager. The EM or NF manager integrated with the NSSMF module sends the network slice configuration information to the RAN device, which can simplify the architecture of the network management system and reduce costs.

[0078] (3) The first network management device includes a NSSMF module, and the second network management device includes an EM or a NF manager.

[0079] (4) The first network management device includes an NM / NSMF module, and the second network management device includes a domain manager (DM).

[0080] It should be noted that the above NM is not limited to the traditional network manager for managing the 4th generation mobile communication (4G) network, or the network manager for managing the 5th generation mobile communication (5G) network in the future. EM is not limited to the device manager for managing the traditional 4G network equipment, or the device manager for managing the 5G network equipment in the future. DM is responsible for managing a management domain in the 4G network, and it is not limited whether there is DM in the future 5G network, or whether the functions of DM and NSSMF are integrated together.

[0081] In addition, the first network management device and the second network management device can be implemented by different physical devices, or integrated into the same physical device. Figure 5 The second network management device may also be integrated into the RAN device. For example, when the second network management device is an EM or a NF manager, it may be integrated into the RAN device.

[0082] Figure 6 A schematic diagram of a configuration method according to an embodiment of the present invention, the method comprising:

[0083] Step 11, the first network management device sends network slice configuration information to the second network management device, and the second network management device receives the network slice configuration information. The network slice configuration information includes information indicating the network slices supported by the RAN. In an embodiment of the present invention, the first network management device can send the network slice configuration information of one RAN device to the second network management device, and can also send the network slice configuration information of multiple RAN devices to the second network management device at the same time.

[0084] Step 12: The second network management device sends the network slice configuration information to the RAN, and the RAN receives the network slice configuration information. If the first network management device sends the network slice configuration information of multiple RAN devices to the second network management device, the second network management device sends the network slice configuration information of the RAN device to each RAN device respectively.

[0085] Step 13, the RAN device configures the network slices it supports according to the received network slice configuration information. For example, after receiving the network slice configuration information, the RAN device can create a list that stores information about the network slices it supports. In some embodiments, the RAN device has already stored the list before receiving the network slice configuration information, and can update the list according to the network slice configuration information.

[0086] Step 14: The RAN device returns a message indicating that the network slice configuration is completed to the second network management device, and the second network management device receives the message indicating that the network slice configuration is completed.

[0087] Step 15: The second network management device returns a message indicating that the RAN configuration is completed to the first network management device, and the first network management device receives the message indicating that the RAN configuration is completed. In an embodiment in which the first network management device sends network slice configuration information of multiple RAN devices to the second network management device at the same time, step 15 can be implemented in two ways. First, after receiving the message indicating that the network slice configuration is completed returned by each RAN device, the second network management device returns a message indicating that the configuration of the RAN device is completed to the first network management device; second, after receiving the message indicating that the network slice configuration is completed returned by all RAN devices, the second network management device returns a message indicating that the configuration of all RAN devices is completed to the first network management device.

[0088] It should be noted that the above steps 14-15 are introduced for the completeness of the scheme, and are not necessary steps for implementing the embodiments of the present invention. For example, the second network management device may return the message indicating that the RAN configuration is completed to the first network management device after sending the network slice configuration information to the RAN device, without waiting for the RAN device to return the message indicating that the network slice configuration is completed, and there is no need to return the message indicating that the network slice configuration is completed to the first network management device after receiving the message indicating that the network slice configuration is completed. For another example, the RAN device may not send the message indicating that the network slice configuration is completed to the second network management device after the network slice configuration is completed, but only send the message indicating that the network slice configuration fails to the second network management device after the network slice configuration is unsuccessful. For another example, the second network management device may not return the message indicating that the RAN configuration is completed to the first network management device after the RAN configuration is completed, but only return the message indicating that the RAN configuration fails to the first network management device after the RAN configuration fails.

[0089] In the above technical solution, the first network management device is responsible for forming network slice configuration information for configuring the network slice of the RAN device, but it may not directly send the network slice configuration information to the RAN device, but instead send the network slice configuration information of one or more RAN devices to the second network management device, and the second network management device is responsible for sending its corresponding network slice configuration information to the RAN device. This not only enables the configuration of network slices supported by the RAN device, but also because the above-mentioned first network management device and the second network management device have clear division of labor, the first network device mainly undertakes higher-level management functions, such as network management functions and network slice instance management functions, and the second network device mainly undertakes specific, lower-level management functions, such as managing network slice subnet instances, network devices, and network functions. The management hierarchy is clear, and each burden will not be too heavy, so that the system for configuring network slices can run efficiently.

[0090] Optionally, the source of the network slice configuration information sent by the first network management device in step 11 may include but is not limited to the following:

[0091] First, the first network management device generates the network slice configuration information itself. For example, the first network management device generates the network slice configuration information when the network slice is created. For another example, the first network management device generates the network slice configuration information when the network slice is running and changes the network slice supported by the RAN device.

[0092] Second, the first network management device receives the network slice configuration information from other network management devices. For example, NSMF and NM are not integrated together, but implemented separately, and there is an interface between the two. NSMF can provide slice information to NM, and the slice information may include one or more of the following: S-NSSAIs corresponding to the network slice instance, RAN network slice subnet instance information contained in the network slice instance, and the geographical scope covered by the network slice instance, so that NM can generate network slice configuration information, and NM further sends specific network slice configuration information to the second network management device. In the above example, NM is the first network management device, and NSMF is the other network management device.

[0093] In the above technical solution, the way in which the first network management device obtains network slice configuration information is flexible, which facilitates implementation and improves the efficiency of configuring the network slice of the RAN device.

[0094] Optionally, the information indicating the network slices supported by the RAN device included in the above-mentioned network slice configuration information may indicate information about the network slices supported by each TAI configured in each cell of the RAN device, and the network slices supported by each TAI of each cell may be configured according to the network slice configuration information.

[0095] Optionally, the information indicating the network slices supported by the RAN device included in the above-mentioned network slice configuration information may be information indicating the network slices supported by each TAI configured by the RAN device. According to the network slice configuration information, supported network slices can be configured for all TAIs configured for the RAN device, and each TAI is configured only once, thereby avoiding repeated indication of network slices supported by the same TAI in different cells, reducing the data amount of the network slice configuration information, reducing the transmission time and transmission resource consumption of the network slice configuration information, and improving configuration efficiency.

[0096] Optionally, the network slice information may be S-NSSAI, that is, the network slice configuration information includes the S-NSSAIs supported by each TAI configured by each cell of the RAN device, or the network slice configuration information includes the S-NSSAIs supported by each TAI configured by the RAN device. The following content of the embodiment of the present invention is explained by taking the network slice information as S-NSSAI as an example.

[0097] In an embodiment of the present invention, the above-mentioned network slice configuration information may be implemented in a variety of ways. Based on different implementations of the network slice configuration information, the configuration process of the RAN device may also be implemented in different ways. Some implementations are introduced below.

[0098] Implementation method 1, the above network slice configuration information includes information indicating at least one TAI configured for each cell of the RAN device and the S-NSSAI supported by each TAI configured for each cell of the RAN device. Table 1 is a possible example of the above network slice configuration information.

[0099]

[0100] Table 1

[0101] In the table, gNB_x is used to indicate a RAN device. For example, gNB_x is the identifier of a base station. A RAN device may include one to multiple cells. A cell is configured with one TAC and one or more PLMNs. Since a TAI includes a TAC and a PLMN, a cell may be configured with one or more TAIs. The number of TAIs in a cell depends on the number of PLMNs in the cell. Different TAIs in a cell may support different S-NSSAIs, while the same TAI in different cells supports the same S-NSSAIs. For example, in Table 1, the TAC allocated to Cell_1 is TAC_1, but two PLMNs are allocated, namely PLMN 1 and PLMN 2, that is, Cell_1 is allocated two TAIs, namely TAI=(TAC_1+PLMN 1) and TAI=(TAC_1+PLMN 2), and the S-NSSAIs supported by the two TAIs are different. The S-NSSAIs supported by TAI=(TAC_1+PLMN 1) include S-NSSAI 1~3, and the S-NSSAIs supported by TAI=(TAC_1+PLMN 2) include S-NSSAI 2~4. Cell_2 is also allocated TAI=(TAC_1+PLMN 1), and the S-NSSAI supported by TAI=(TAC_1+PLMN 1) allocated by Cell_2 is the same as the S-NSSAI supported by TAI=(TAC_1+PLMN 1) allocated by Cell_1.

[0102] The above implementation method 1 can configure the TAI of each cell for the RAN device, and configure the S-NSSAIs supported by each TAI of each cell at the same time, which is highly efficient.

[0103] Implementation method 2, the above network slice configuration information includes information indicating at least one TAI configured for each cell of the RAN device and the S-NSSAI supported by each TAI configured by the RAN device. Table 2 is a possible example of the above network slice configuration information.

[0104]

[0105] Table 2

[0106] The difference between Implementation Method 2 and Implementation Method 1 is that the network slices supported by the TAI are based on the configuration of the RAN device, rather than the TAI configuration of the cell. In different cells of a RAN device, the network slice information supported by the same TAI is the same. In other words, the network slice configuration information is used to indicate the S-NSSAI supported by each TAI of the RAN device, and does not focus on which cell's TAI supports the above S-NSSAI. In the technical solution of Implementation Method 2, it is possible to avoid configuring multiple S-NSSAIs for the same TAI (such as TAI = (TAC_1 + PLMN 1) in Table 1 is configured with S-NSSAI twice), reduce the amount of data of the network slice configuration information, reduce the transmission time and transmission resource consumption of the network slice configuration information, and improve the configuration efficiency.

[0107] In implementation method 3, the above-mentioned network slice configuration information does not include the above-mentioned information indicating at least one TAI configured for each cell of the RAN device. The network management system may first send tracking area configuration information to the RAN device, where the tracking area configuration information includes information indicating at least one TAI configured for each cell of the RAN device, to configure the TAI of the cell of the RAN device, and then send the network slice configuration information to the RAN device.

[0108] Table 3 is a possible example of tracking area configuration information.

[0109]

[0110] Table 3

[0111] Table 4 is a possible example of network slice configuration information. The network slice configuration information includes a mapping of each TAI of the RAN to the S-NSSAIs supported by the TAI.

[0112]

[0113] Table 4

[0114] Table 5 is another possible example of the network slice configuration information, which includes a mapping of each TAI of each cell of the RAN to the S-NSSAIs supported by the TAI. Although Tables 4 and 5 contain the TAI for each cell, unlike Tables 1 and 2 in Implementation 1, the network slice configuration information described in Tables 4 and 5 does not configure the TAI for each cell, but only configures the S-NSSAIs corresponding to each TAI supported by the cell, and the TAIs supported by the cell are configured by Table 3.

[0115]

[0116] Table 5

[0117] A variation of Table 5 is: the network slice configuration information includes a mapping of each PLMN of each cell of the RAN and the S-NSSAIs supported by the PLMN, because for each cell, the PLMN of the cell corresponds to the TAI of the cell one by one. This variation can reduce the amount of data in the network slice configuration information and reduce resource consumption during RAN configuration.

[0118] It should be noted that in implementation method 3, the configuration process of the tracking area of ​​each cell of the RAN can adopt a mechanism similar to the configuration process of the aforementioned network slice, that is, the third network management device sends the tracking area configuration information to the fourth network management device, and the fourth network management device specifically sends the tracking area configuration information to the RAN device. Among them, the third network management device can be the same device as the aforementioned first network management device, and the fourth network management device can be the same device as the second network management device, that is, the first network management device can send tracking area configuration information to the second network management device, and can also send network slice configuration information to the second network management device, and the second network management device can send tracking area configuration information to the RAN device, and can also send network slice configuration information to the RAN device. In another possible implementation, the third network management device in the tracking area configuration scheme is different from the aforementioned first network management device, and / or the fourth network management device is different from the aforementioned second network management device. For example, the aforementioned first network management device is an NSMF module, and the second network management device is an NSSMF module integrated with an EM or NF manager; and the third network management device in the tracking area configuration scheme is an NM, and the fourth network management device is an NF manager.

[0119] Implementation method 4, in combination with the above-mentioned implementation method 1, implementation method 2 or implementation method 3, the above-mentioned network slice configuration information also includes information indicating the available frequencies corresponding to the S-NSSAI. The RAN device can also configure the frequencies supported by each S-NSSAI according to the network slice configuration information, thereby improving the efficiency of RAN configuration.

[0120] Table 6 is a possible example of network slice configuration information in combination with implementation method 1, where the network slice configuration information includes the TAI of each cell of the RAN device, the S-NSSAIs supported by each TAI of each cell, and the available frequency band information of each S-NSSAI supported by each TAI of each cell.

[0121]

[0122] Table 6

[0123] Table 7 is another possible example of network slice configuration information when combined with implementation method 1. The difference from the network slice configuration information described in Table 6 is that for each S-NSSAI supported by the RAN device, the supported frequency is configured only once to reduce the data volume of the network slice configuration information and reduce resource consumption during network slice configuration.

[0124]

[0125] Table 7

[0126] Table 8 is a possible example of network slice configuration information when combined with implementation method 2, where the network slice configuration information includes the S-NSSAIs supported by each TAI of the RAN device, information on the available frequency bands of each S-NSSAI, and the TAI of each cell of the RAN device.

[0127]

[0128] Table 8

[0129] When combined with implementation method 3, the network slice configuration information includes the mapping of each TAI of the RAN to the S-NSSAIs supported by the TAI (see Table 4 or Table 5) and the mapping of each S-NSSAI to its available frequency. Table 9 is a possible example of the mapping of the S-NSSAI to its available frequency. Among them, in addition to being the identifier of the frequency band, the frequency band information can also be a frequency range, or a parameter indicating a frequency characteristic, such as a parameter indicating a high frequency or a low frequency. The present invention does not limit the specific form of the frequency information.

[0130] Slice information Frequency information S-NSSAI 1 Band 1 S-NSSAI 2,3 Frequency band 1~5 S-NSSAI 4,5 Band 2 to 4

[0131] Table 9

[0132] In other possible implementations in combination with implementation mode 3, the network slice configuration information may configure the available frequency for each network slice supported by each TAI of each cell of the RAN device, and Table 10 is an example of the network slice configuration information in this possible implementation. Although Table 10 contains the TAI configured for each cell, the network slice configuration information described in Table 10 does not configure the TAI of each cell, but configures the network slices supported by the TAI configured in the cell, and configures the available frequencies of the network slices supported by the TAI of the cell, that is, configures the S-NSSAIs corresponding to the TAI and the frequencies that the S-NSSAI can use.

[0133]

[0134] Table 10

[0135] In the technical solution of implementation method 4, the network management system can configure the S-NSSAIs supported by TAI and the available frequency band corresponding to each S-NSSAI for the RAN device at the same time, which is more efficient.

[0136] Implementation method 5, in combination with the above-mentioned implementation method 1, implementation method 2 or implementation method 3, the above-mentioned network slice configuration information does not include the information indicating the available frequency corresponding to the S-NSSAI described in implementation method 3. However, after sending the network slice configuration information to the RAN device, the network management system may send spectrum configuration information to the RAN device, and the spectrum configuration information includes information indicating the available frequency corresponding to the S-NSSAI. The implementation of the spectrum configuration information can refer to Table 9.

[0137] Figure 7 A schematic diagram of a process for configuring available frequencies of a network slice of a RAN in implementation mode 5, including:

[0138] Step 16: The first network management device sends spectrum configuration information to the second network management device, and the second network management device receives the spectrum configuration information.

[0139] Step 17: The second network management device sends the spectrum configuration information to the RAN device, and the RAN device receives the spectrum configuration information.

[0140] Step 18: The RAN device configures the available frequencies of the network slices it supports according to the received spectrum configuration information.

[0141] Step 19. The RAN device returns a message indicating that the frequency configuration of the network slice is completed to the second network management device, and the second network management device receives the message indicating that the frequency configuration of the network slice is completed.

[0142] Step 20: The second network management device returns a message indicating that the frequency configuration of the network slice of the RAN is completed to the first network management device, and the first network management device receives the message indicating that the frequency configuration of the network slice of the RAN is completed.

[0143] In an embodiment of the present invention, the above-mentioned step 16 can be performed after any one of the above-mentioned steps 11 to 15, for example, step 16 is performed after step 15, or, the above-mentioned step 11 can be performed after any one of steps 16 to 20, or, there is no sequence restriction between the process of the above-mentioned steps 11 to 15 and the process of steps 16 to 20.

[0144] In the scheme of steps 16 to 20 above, the first network management device and the second network management device configure the available frequencies of the network slices of the RAN device, but the embodiment of the present invention does not limit the available frequencies of the network slices of the RAN device to be configured by the first network management device and the second network management device. For example, when the first network management device is an NSMF module and the second network management device is an NF manager, the NSMF module sends the network slice configuration information to the NF manager, and the NF manager specifically sends the network slice configuration information to the RAN device; and when configuring the available frequencies of the network slices supported by the RAN device, the NM module can send the spectrum configuration information to the NF manager, and the NF manager specifically sends the spectrum configuration information to the RAN device.

[0145] The solution of the above-mentioned implementation method 5 can realize the configuration of only the available frequencies of the network slice. This configuration method is flexible and convenient for adjusting the available frequencies corresponding to part or all of the S-NSSAI of the RAN device.

[0146] It should be noted that the above Tables 1 to 10 are examples of possible implementation methods of the above configuration information. The above configuration information can be organized in a form different from the above table, and the embodiments of the present invention do not limit the specific organization form of the above configuration information. In addition, in the above embodiments and tables, the network slice configuration information may include the S-NSSAIs supported by each TAI in the TAI list supported by the base station or cell, the frequency information supported by each S-NSSAI (optional), and each TAI of each cell (optional). Other content is not necessarily included in the network slice configuration information, such as the cell identifier, the base station identifier, etc.

[0147] Figure 8 A network management device provided by an embodiment of the present invention is shown. The network management device can be used as the first network management device in the aforementioned configuration method provided by an embodiment of the present invention. The network management device includes:

[0148] The first sending module 301 is used to send network slice configuration information to the second network management device, where the network slice configuration information includes information indicating the network slices supported by the access network RAN, and the second network management device has a function of configuring the RAN;

[0149] The first receiving module 302 is configured to receive a message returned by the second network management device indicating that the RAN configuration is completed.

[0150] Optionally, in an embodiment of the present invention, the information indicating the network slices supported by the RAN is specifically:

[0151] Information indicating the network slices supported by each tracking area identity TAI configured by the RAN; or

[0152] Indicates information about the network slices supported by each TAI configured for each cell of the RAN.

[0153] Optionally, in an embodiment of the present invention, the network slice information includes: S-NSSAI.

[0154] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating the available frequencies of the network slices supported by the RAN.

[0155] Optionally, in an embodiment of the present invention, the first sending module 301 is also used to: after sending the network slice configuration information to the second network management device, send spectrum configuration information to the second network management device, wherein the spectrum configuration information is used to indicate the available frequency of the network slice supported by the RAN.

[0156] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating at least one TAI configured for each cell of the RAN.

[0157] Optionally, in an embodiment of the present invention, the first sending module 301 is also used to: before sending the network slice configuration information to the second network management device, send tracking area configuration information to the second network management device, and the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN.

[0158] Optionally, in an embodiment of the present invention, the network management device is a network manager NM or a network slice management function NSMF module, and the second network management device is a device manager EM or a network function NF manager; or

[0159] The network management device is an NSMF module, the second network management device is a network slice subnet management function NSSMF module, and the NSSMF module is integrated with an EM or NF manager; or

[0160] The network management device is a NSSMF module, and the second network management device is an EM or a NF manager.

[0161] Optionally, in an embodiment of the present invention, the first receiving module 302 is also used to: receive the network slice configuration information before the first sending module 301 sends the network slice configuration information to the second network management device.

[0162] Optionally, in the embodiment of the present invention, the network management device further includes:

[0163] The first generation module 303 is used to generate the network slice configuration information before the first sending module 301 sends the network slice configuration information to the second network management device.

[0164] The division of modules in the embodiments of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present invention may be integrated into one processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0165] Among them, when the integrated module is implemented in the form of hardware, such as Fig. 9 As shown, the network management device may include a processor 401. The hardware of the entity corresponding to the above-mentioned first generation module may be a processor 401. The processor 401 may be a central processing unit (CPU), or a digital processing module, etc. The network management device may also include a transceiver 402, and the processor 401 sends network slice configuration information to the second network management device through the transceiver 402 and receives a message returned by the second network management device indicating that the RAN configuration is completed. The network management device also includes: a memory 403 for storing the program executed by the processor 401. The memory 403 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory), such as a random-access memory (RAM). The memory 403 is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0166] The implementation of each module of the above network management device can refer to the implementation of the steps executed by the first network management device in the aforementioned configuration method.

[0167] Fig.10 Another network management device provided by an embodiment of the present invention is shown. The network management device can be used as the second network management device in the aforementioned configuration method provided by an embodiment of the present invention. The network management device includes:

[0168] A second sending module 501 is used to send network slice configuration information to the RAN, where the network slice configuration information includes information indicating the network slices supported by the RAN;

[0169] The second receiving module 502 is used to receive a message returned by the RAN indicating that the network slice configuration is completed.

[0170] Optionally, in an embodiment of the present invention, the information indicating the network slices supported by the RAN is specifically:

[0171] Information indicating the network slices supported by each tracking area identity TAI configured by the RAN; or

[0172] Indicates information about the network slices supported by each TAI configured for each cell of the RAN.

[0173] Optionally, in an embodiment of the present invention, the network slice information includes: S-NSSAI.

[0174] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating the available frequencies of the network slices supported by the RAN.

[0175] Optionally, in an embodiment of the present invention, the second sending module 501 is further used to: after sending the network slice configuration information to the RAN, send spectrum configuration information to the RAN, wherein the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN.

[0176] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating at least one TAI configured for each cell of the RAN.

[0177] Optionally, in an embodiment of the present invention, the second sending module 501 is further used to: send tracking area configuration information to the RAN before sending the network slice configuration information to the RAN, wherein the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN.

[0178] Optionally, in an embodiment of the present invention, the second receiving module 502 is further used to: receive the network slice configuration information sent by the first network management device before the second sending module 501 sends the network slice configuration information to the RAN.

[0179] Optionally, in the embodiment of the present invention, the second sending module 501 is further used to:

[0180] After the second receiving module 502 receives the message returned by the RAN indicating that the network slice configuration is completed, it sends a message indicating that the RAN configuration is completed to the first network management device.

[0181] Optionally, in an embodiment of the present invention, the network management device is a network manager NM or a network slice management function NSMF module, and the second network management device is a device manager EM or a network function NF manager; or

[0182] The network management device is an NSMF module, the second network management device is a network slice subnet management function NSSMF module, and the NSSMF module is integrated with an EM or NF manager; or

[0183] The network management device is a NSSMF module, and the second network management device is an EM or a NF manager.

[0184] The division of modules in the embodiments of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present invention may be integrated into one processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0185] When the integrated module is implemented in the form of hardware, the network management device may include a transceiver (refer to Fig. 9 ), the hardware entities corresponding to the above-mentioned second receiving module and the second sending module may be transceivers. The network management device may also include a processor, which may be a central processing module, or a digital processing module, etc., for instructing the transceiver to send the above-mentioned network slice configuration information, receive a message indicating that the network slice configuration is completed, etc. The network management device also includes: a memory for storing programs executed by the processor. The memory may be a non-volatile memory, such as a hard disk or a solid-state drive, or a volatile memory, such as a random access memory. The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0186] The implementation of each module of the above network management device can refer to the implementation of the steps executed by the second network management device in the aforementioned configuration method.

[0187] Fig.11 The figure shows a RAN provided by an embodiment of the present invention, which can be used as the RAN device in the aforementioned configuration method provided by an embodiment of the present invention. The RAN includes:

[0188] The third receiving module 601 is used to receive network slice configuration information sent by the network management device, where the network slice configuration information includes information indicating the network slices supported by the RAN;

[0189] A third configuration module 602 is used to configure supported network slices according to the network slice configuration information;

[0190] The third sending module 603 is used to return a message indicating that the network slice configuration is completed to the network management device after the third configuration module configures the supported network slice according to the network slice configuration information.

[0191] Optionally, in an embodiment of the present invention, the information indicating the network slices supported by the RAN is specifically:

[0192] Information indicating the network slices supported by each tracking area identity TAI configured by the RAN; or

[0193] Indicates information about the network slices supported by each TAI configured for each cell of the RAN.

[0194] Optionally, in an embodiment of the present invention, the network slice information includes: S-NSSAI.

[0195] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating the available frequencies of the network slices supported by the RAN.

[0196] Optionally, in an embodiment of the present invention, the third receiving module 601 is also used to: after receiving the network slice configuration information sent by the network management device, receive spectrum configuration information sent by the network management device, wherein the spectrum configuration information is used to indicate the available frequency of the network slice supported by the RAN.

[0197] Optionally, in an embodiment of the present invention, the network slice configuration information also includes: information indicating at least one TAI configured for each cell of the RAN.

[0198] Optionally, in an embodiment of the present invention, the third receiving module 601 is also used to: before receiving the network slice configuration information sent by the network management device, receive tracking area configuration information sent by the network management device, and the tracking area configuration information is used to indicate information of at least one TAI configured for each cell of the RAN.

[0199] The division of modules in the embodiments of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present invention may be integrated into one processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0200] When the integrated module is implemented in the form of hardware, the RAN may include a processor (refer to Fig. 9 ). The hardware of the entity corresponding to the above configuration module may be a processor. The processor may be a central processing module, or a digital processing module, etc. The RAN may also include a transceiver, which receives network slice configuration information sent by the network management device through the transceiver, and sends a message indicating that the network slice configuration is completed to the network management device. The network management device also includes: a memory for storing programs executed by the processor. The memory may be a non-volatile memory, such as a hard disk or a solid-state drive, or a volatile memory, such as a random access memory. The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0201] The implementation of each module of the above RAN may refer to the implementation of the steps executed by the RAN device in the aforementioned configuration method.

[0202] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed on a computer, the computer executes the steps executed by the first network management device in the aforementioned configuration method.

[0203] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed on a computer, the computer executes the steps executed by the second network management device in the aforementioned configuration method.

[0204] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed on a computer, the computer executes the steps executed by the RAN device in the aforementioned configuration method.

[0205] The present application provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the method in the first aspect or any possible implementation of the first aspect.

[0206] An embodiment of the present invention further provides a computer program product. When the computer program product is run on a computer, the computer executes the steps executed by the first network management device in the aforementioned configuration method.

[0207] An embodiment of the present invention further provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the steps executed by the second network management device in the aforementioned configuration method.

[0208] An embodiment of the present invention further provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the steps executed by the RAN device in the aforementioned configuration method.

[0209] The embodiments of the present invention are described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0210] The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A network management device, It is characterized in that comprising a processor and a transceiver, the processor being coupled to the transceiver; The processor is used to instruct the transceiver to send network slice configuration information to the second network management device, where the network slice configuration information includes information indicating network slices supported by the access network RAN, and the second network management device has the function of configuring the RAN. The information on network slices supported by the RAN is information indicating network slices supported by each tracking area identifier TAI configured by each cell of the RAN, or information indicating network slices supported by each TAI configured by the RAN.

2. The network management device according to claim 1, It is characterized in that The processor is also used to instruct the transceiver to send spectrum configuration information to the second network management device, where the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN.

3. The network management device according to claim 1 or 2, It is characterized in that The processor is further used to instruct the transceiver to receive the network slice configuration information; Alternatively, the processor is also used to: generate the network slice configuration information.

4. A network management device, It is characterized in that a processor and a transceiver, the processor being coupled to the transceiver; The processor is used to instruct the transceiver to receive network slice configuration information sent by the first network management device; and to send network slice configuration information to the RAN, wherein the network slice configuration information includes information indicating network slices supported by the RAN, and the information on network slices supported by the RAN is information indicating network slices supported by each tracking area identifier TAI configured for each cell of the RAN, or information indicating network slices supported by each TAI configured by the RAN.

5. The network management device according to claim 4, It is characterized in that The processor is also used to instruct the transceiver to send spectrum configuration information to the RAN, where the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN.

6. A RAN, It is characterized in that a processor and a transceiver, the processor being coupled to the transceiver; The processor is used to instruct the transceiver to receive network slice configuration information from the second network management device, the network slice configuration information includes information indicating network slices supported by the RAN, the network slice configuration information is received or generated by the first network management device and sent to the second network management device, and the information of the network slices supported by the RAN is information indicating network slices supported by each tracking area identifier TAI configured by each cell of the RAN, or is information indicating network slices supported by each TAI configured by the RAN; The processor is also used to: configure supported network slices according to the network slice configuration information.

7. The RAN according to claim 6, It is characterized in that The processor is also used to instruct the transceiver to receive spectrum configuration information sent by the second network management device, where the spectrum configuration information is used to indicate the available frequencies of the network slices supported by the RAN.

8. A configuration method, It is characterized in that include: The first network management device sends network slice configuration information to the second network management device, where the network slice configuration information includes information indicating network slices supported by the access network RAN, and the information on network slices supported by the RAN is information indicating network slices supported by each tracking area identifier TAI configured for each cell of the RAN, or information indicating network slices supported by each TAI configured for the RAN. The second network management device has the function of configuring the RAN.

9. A configuration method, It is characterized in that include: The second network management device receives the network slice configuration information from the first network management device; The second network management device sends network slice configuration information to the RAN, and the network slice configuration information includes information indicating network slices supported by the RAN, and the information on network slices supported by the RAN is information indicating network slices supported by each tracking area identifier TAI configured by each cell of the RAN, or information indicating network slices supported by each TAI configured by the RAN.

10. A configuration method, It is characterized in that include: The RAN receives network slice configuration information from the second network management device, where the network slice configuration information includes information indicating network slices supported by the RAN, where the network slice configuration information is generated or received by the first network management device and sent to the second network management device, and the information on network slices supported by the RAN is information indicating network slices supported by each tracking area identity TAI configured by each cell of the RAN, or information indicating network slices supported by each TAI configured by the RAN; The RAN configures the supported network slices according to the network slice configuration information.

Images