CN108076471B - A method and apparatus for managing RAN slices - Google Patents

Abstract

The invention discloses a method and a device for managing RAN slices, which relate to the technical field of communications and are used to meet the differentiated performance requirements of different services. The method includes: the RAN slice manager obtains initial configuration information of the RAN slice; the RAN slice manager sends a creation instruction message to the infrastructure controller; wherein the creation instruction message includes initial configuration information for instructing the infrastructure controller according to the initial configuration information to create the RAN slice.

Description

A method and apparatus for managing RAN slices

technical field

The present patent application relates to the field of communication technologies, and in particular, to a method and apparatus for managing slices of a radio access network (residential access network, RAN).

Background technique

Wireless communication systems provide communication services for businesses in the fields of education, medical care, enterprises, government, Internet of Vehicles, and the Internet of Things. Traditional wireless communication systems use a unified pipeline architecture to provide services for different services, which cannot effectively meet the differentiated performance requirements of different services. To this end, the future 5G network plans to adopt a slice architecture to meet the differentiated performance requirements of different services.

The slicing architecture of a wireless communication system mainly includes core network slicing and RAN slicing. At present, the focus is on the related issues of core network slicing, and there is no technical solution for effectively managing RAN slicing.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method and apparatus for managing RAN slices to meet differentiated performance requirements of different services.

To achieve the above object, the embodiments of the present invention adopt the following technical solutions:

A first aspect provides a method for creating a RAN slice, the method may include: a RAN slice manager obtains initial configuration information of a RAN slice, and then sends a creation instruction message to an infrastructure controller, wherein the creation instruction message includes the initial configuration information , the creation instruction message is used to instruct the infrastructure controller to create a RAN slice according to the initial configuration information. This technical solution provides a way to create RAN slices, which can meet the differentiated performance requirements of different services. The initial configuration information included in the creation instruction message may be all or part of the configuration information required by the infrastructure controller to create the RAN slice.

In a possible design, the initial configuration information may include information of functional modules used by the RAN slice. Optionally, the initial configuration information of the RAN slice may further include at least one of the following information: functional configuration of the functional module used by the RAN slice, parameter configuration of the functional module used by the RAN slice, computing resources used by the RAN slice, Storage resources used by RAN slices, and radio spectrum resources used by RAN slices. Wherein, the parameter configuration of the function module includes any one or more parameter configurations of any one or more function modules.

In a possible design, the creating an instruction message is used to instruct the infrastructure controller to create a RAN slice according to the initial configuration information, which may include: creating an instruction message to instruct the infrastructure controller to create a RAN slice according to the initial configuration information and the default configuration information slice. The default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller when configuring the RAN slice.

In a possible design, after the RAN slice manager sends the creation instruction message to the infrastructure controller, the method may further include: the RAN slice manager receives a creation response message sent by the infrastructure controller, wherein the creation response message Used to indicate to the RAN slice manager that the RAN slice has been created by the infrastructure controller. Then, the RAN slice manager sends an update instruction message to the RAN slice, where the update instruction message is used to instruct the RAN slice to update the current configuration information of the RAN slice. In this possible implementation, the infrastructure controller may create a RAN slice according to the initial configuration information and the default configuration information, and then the RAN slice updates its own current configuration information, so that the RAN slice is first created according to the default configuration information , resources can be quickly preempted, so that the RAN slice can be created quickly; and the signaling overhead of creating an indication message can also be saved.

In a possible design, the RAN slice manager obtains the initial configuration information of the RAN slice, which may include any of the following methods:

Manner 1: The RAN slice manager receives a service creation request message including service information, and then acquires the initial configuration information of the RAN slice corresponding to the service.

Manner 2: The RAN slice manager receives a request message for creating a RAN slice including an identifier of the RAN slice, and then obtains the initial configuration information of the RAN slice according to the identifier of the RAN slice.

In a possible design, after the RAN slice manager sends the creation instruction message to the infrastructure controller, the method may further include: the RAN slice manager sends radio spectrum resource configuration information to the physical layer functional module. The wireless spectrum resource configuration information may include at least one set of configuration information, and a set of configuration information may include but not limited to at least one of the following information: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameters of the wireless spectrum resource. configuration. Optionally, the parameter configuration of the wireless spectrum resource may include at least one of a transmission time interval (transmission time interval, TTI), a subcarrier interval, and a resource block group (resource block group, RBG). For example, suppose that the spectrum of 1-21MHz (megahertz) is divided into the following two segments: 1-11MHZ and 11-21MHZ; and, the spectrum 1-11MHZ adopts 1ms (millisecond) TTI, and the subcarrier spacing is 15KHZ (kilohertz), The RBG is 12*8 subcarriers; the spectrum 11-21MHZ adopts 0.5msTTI, the subcarrier interval is 30KHZ, and the RBG is 12*4 subcarriers. Then, the first group of wireless spectrum resource configuration information may be: the center frequency is 6MHZ, the bandwidth is 10MHZ, the TTI is 1ms, the subcarrier interval is 15KHZ, and the RBG is 96 subcarriers; the second group of wireless spectrum resource configuration information is: the center frequency is 16MHZ, the bandwidth is 10MHZ, the TTI is 0.5ms, the subcarrier spacing is 30KHZ, and the RBG is 48 subcarriers.

In a possible design, after the RAN slice manager sends the radio spectrum resource configuration information to the physical layer functional module, the method may further include: the RAN slice manager sends at least one of the following information to the terminal device: radio spectrum Configuration information of resources, the identifier of each RAN slice that has been created but not deleted, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and each RAN slice that has been created but not deleted bandwidth information of wireless spectrum resources. During specific implementation, the RAN slice manager may send the broadcast information to the terminal device. Each RAN slice in this possible design includes the RAN slice created above.

Specifically, the sending of the RAN slice manager to the terminal device may include but is not limited to: the RAN slice manager sends directly to the terminal device, or the RAN slice manager sends the RAN slice manager to the terminal device through the physical layer function module, or the RAN slice manager sends the The RAN slice and the physical layer function module are sent, or the RAN slice manager sends the RAN slice and the physical layer function module to the terminal device through the common RAN slice and the physical layer function module. The common RAN slice refers to a RAN slice shared by multiple RAN slices in the system, for example, a common control channel of multiple RAN slices constitutes a shared RAN slice. In this possible design manner, the terminal device can obtain the wireless spectrum resource configuration information, and use the wireless spectrum resource according to the wireless spectrum resource configuration information.

In a possible design, the method may further include: the RAN slice manager updates a RAN slice database, where the RAN slice database contains the identifiers of the created RAN slices.

In a possible design, the method may further include: the RAN slice manager sends a second update instruction message to the infrastructure controller, where the second update instruction message is used to instruct the infrastructure controller to update the storage resource information and computing At least one of resource information. Optionally, the infrastructure controller updates at least one of storage resource information and computing resource information, which may include, but is not limited to: the infrastructure controller updates idle storage resources and computing resources, and/or, the infrastructure controller updates Information on which RAN slice is used by storage resources and computing resources.

In a possible design, the method may further include: the RAN slice manager updates the radio spectrum resource information. The RAN slice manager updates the radio spectrum resource information, which may include, but is not limited to: the RAN slice manager updates the center frequency and bandwidth information of the idle radio spectrum resources, and/or the RAN slice manager updates the used radio spectrum resources. configuration information.

In a second aspect, a method for creating a RAN slice is provided, which may include: an infrastructure controller receiving a creation instruction message; wherein the creation instruction message includes initial configuration information of the RAN slice. The infrastructure controller creates RAN slices based on the initial configuration information.

In a possible design, the initial configuration information includes information of functional modules used by the RAN slice.

In a possible design, the infrastructure controller creates a RAN slice according to the initial configuration information, which may include: the infrastructure controller creates a RAN slice according to the initial configuration information and the default configuration information; wherein the default configuration information includes the infrastructure controller Configuration information other than the initial configuration information required when configuring RAN slices.

In a possible design, the method may further include: the infrastructure controller receives an update indication message sent by the RAN slice manager; the infrastructure controller updates at least one of storage resource information and computing resource information.

In a third aspect, a method for creating a RAN slice is provided, comprising: a physical layer functional module receiving radio spectrum resource configuration information sent by a RAN slice manager; wherein the radio spectrum resource configuration information includes at least one set of configuration information, one set of configuration information It includes at least one of the following information: the center frequency of the radio spectrum resource, the bandwidth of the radio spectrum resource, and the parameter configuration of the radio spectrum resource; wherein the RAN slice manager sends the radio spectrum resource configuration to the physical layer function module after creating the RAN slice information. The physical layer functional module uses the wireless spectrum resources according to the configuration information of the wireless spectrum resources. The technical solution provides a method for configuring wireless spectrum resource configuration information of a physical layer functional module after creating a RAN slice. Optionally, the parameter configuration of the wireless spectrum resource includes at least one of TTI, subcarrier spacing and RBG.

A fourth aspect provides a method for creating a RAN slice, comprising: a terminal device sending a service creation request message to a RAN slice manager; wherein the service creation request message includes service information, and the service creation request message is used to request the creation of a service corresponding to the service RAN slice; or, the terminal device sends a RAN slice creation request message to the RAN slice manager; wherein the RAN slice creation request message includes an identifier of the RAN slice, and the RAN slice creation request message is used to request the creation of a RAN slice.

In a possible design, the method may further include: the terminal device receives at least one of the following information sent by the RAN slice manager: configuration information of radio spectrum resources, information about each RAN slice that has been created but not deleted Identification, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted; the terminal device uses the at least one kind of information wireless spectrum resources.

In a fifth aspect, a network device is provided, the network device may include the RAN slice manager described above. The network device may include a transceiver, a memory, and a processor. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instructions stored in the memory, so as to perform the following steps when executing the instructions: acquiring initial configuration information of the RAN slice; sending a creation instruction message to the infrastructure controller through the transceiver ; wherein the creation instruction message includes initial configuration information, and the creation instruction message is used to instruct the infrastructure controller to create a RAN slice according to the initial configuration information.

In a possible design, the initial configuration information includes information of functional modules used by the RAN slice.

In a possible design, creating an instruction message is used to instruct the infrastructure controller to create a RAN slice according to the initial configuration information, including: creating an instruction message to instruct the infrastructure controller to create a RAN slice according to the initial configuration information and the default configuration information; The default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: send wireless spectrum resource configuration information to the physical layer functional module through the transceiver; wherein the wireless spectrum resource configuration information includes at least one set of configuration information , a set of configuration information includes at least one of the following information: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameter configuration of the wireless spectrum resource.

In a possible design, the parameter configuration of the wireless spectrum resource includes at least one of a transmission time interval TTI, a subcarrier interval, and a resource block group RBG.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: send at least one of the following information to the terminal device through the transceiver: configuration information of wireless spectrum resources, created but not deleted The identifier of each RAN slice, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receive a service creation request message through the transceiver; wherein the service creation request message includes information of the service; then, obtain the RAN slice corresponding to the service initial configuration information.

In a possible design, when the processor executes the instruction, the processor is specifically configured to perform the following steps: receive a request message for creating a RAN slice through the transceiver; wherein the request message for creating a RAN slice includes an identifier of the RAN slice; then, according to the RAN slice The identifier of the slice obtains the initial configuration information of the RAN slice.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: receive a create response message sent by the infrastructure controller through the transceiver; send an update instruction message to the RAN slice through the transceiver; wherein the update The indication message is used to instruct the RAN slice to update the current configuration information of the RAN slice.

In a possible design, the processor is further configured to perform the following steps when executing the instruction: update the RAN slice database and the radio spectrum resource information; wherein the RAN slice database contains the identifier of the created RAN slice.

In a possible design, the processor is further configured to perform the following steps when executing the instruction: send a second update instruction message to the infrastructure controller through the transceiver; wherein the second update instruction message is used to instruct the infrastructure control The server updates at least one of storage resource information and computing resource information.

In a sixth aspect, a network device is provided, including: a transceiver, a memory, and a processor. The network device may include the infrastructure controller described above. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instruction stored in the memory, so as to perform the following steps when executing the instruction: receiving a creation instruction message through the transceiver; wherein, the creation instruction message includes the initial configuration information of the RAN slice; according to Initial configuration information creates RAN slices.

In a possible design, the initial configuration information includes information of functional modules used by the RAN slice.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: create a RAN slice according to the initial configuration information and the default configuration information; wherein the default configuration information includes the information used when the infrastructure controller configures the RAN slice. Required configuration information other than the initial configuration information.

In a seventh aspect, a terminal device is provided, including: a transceiver, a memory, and a processor. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instructions stored in the memory, so as to perform the following steps when executing the instructions: sending a service creation request message to the RAN slice manager through the transceiver; wherein, the service creation request message includes the service information, and create a service request message for requesting to create a RAN slice corresponding to the service; or, send a RAN slice creation request message to the RAN slice manager through the transceiver; wherein, the RAN slice creation request message includes the identifier of the RAN slice, and the RAN slice is created. The request message is used to request the creation of a RAN slice.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: receive at least one of the following information sent by the RAN slice manager through the transceiver: configuration information of wireless spectrum resources, created and The identifier of each RAN slice that has not been deleted, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted; The terminal device uses the wireless spectrum resource according to the at least one kind of information.

In an eighth aspect, a method for deleting a RAN slice is provided, the method may include: the RAN slice manager obtains an identifier of the RAN slice, and then sends a RAN slice deletion indication message to the infrastructure controller, wherein the RAN slice deletion indication message includes The identifier of the RAN slice, used to instruct the infrastructure controller to delete the RAN slice.

In a possible design, the RAN slice manager obtains the identifier of the RAN slice, which may include any of the following methods:

Manner 1: The RAN slice manager receives a service deletion request message including service information, and then acquires the identifier of the RAN slice corresponding to the service.

Manner 2: The RAN slice manager receives a delete RAN slice request message including an identifier of the RAN slice.

Manner 3: The RAN slice manager receives a status report sent by the RAN slice and includes the identifier of the RAN slice, where the status report is used to describe the operation status of the RAN slice.

In a possible design, after the RAN slice manager sends the RAN slice deletion instruction message to the infrastructure controller, the method may further include: the RAN slice manager sends radio spectrum resource configuration information to the physical layer functional module. Optionally, after the RAN slice manager sends the radio spectrum resource configuration information to the physical layer functional module, the method may further include: the RAN slice manager sends at least one of the following information to the terminal device: configuration information of radio spectrum resources , the identifier of each RAN slice that has been created but not deleted, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the radio spectrum resource of each RAN slice that has been created and not deleted bandwidth information. During specific implementation, the RAN slice manager may send the broadcast information to the terminal device.

In a possible design, the method may further include: the RAN slice manager updating the RAN slice database.

In a possible design, the method may further include: the RAN slice manager sends an update instruction message to the infrastructure controller, where the update instruction message is used to instruct the infrastructure controller to update the resource information and the stored resource information in the physical resource database. At least one of computing resource information.

In a possible design, the method may further include: the RAN slice manager updates the radio spectrum resource information.

In a ninth aspect, a network device is provided, the network device may include the RAN slice manager described above. The network device may include a transceiver, a memory, and a processor. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instruction stored in the memory, so as to perform the following steps when executing the instruction: acquiring the identifier of the RAN slice, and then sending an instruction to delete the RAN slice to the infrastructure controller through the transceiver message, wherein the RAN slice deletion instruction message includes the identifier of the RAN slice, and is used to instruct the infrastructure controller to delete the RAN slice.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receive a delete service request message including service information through the transceiver, and then acquire the identifier of the RAN slice corresponding to the service.

In a possible design, when the processor executes the instruction, the processor is specifically configured to perform the following steps: receive a delete RAN slice request message including an identifier of the RAN slice through the transceiver.

In a possible design, when the processor executes the instruction, the processor is specifically configured to perform the following steps: receive, through the transceiver, a status report sent by receiving a RAN slice and including the identifier of the RAN slice, where the status report is used to describe the The health of the RAN slice.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following step: send the wireless spectrum resource configuration information to the physical layer functional module through the transceiver.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: send at least one of the following information to the terminal device through the transceiver: configuration information of wireless spectrum resources, created but not deleted The identifier of each RAN slice, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: update the RAN slice database.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following step: send an update instruction message to the infrastructure controller through the transceiver, wherein the update instruction message is used to instruct the infrastructure controller to update the physical At least one of resource information and computing resource information is stored in the resource database.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following step: update the wireless spectrum resource information.

A tenth aspect provides a method for reconfiguring a RAN slice, which may include: a RAN slice manager obtains reconfiguration information of a RAN slice, and then sends at least one of the RAN slice, an infrastructure controller, and a physical layer functional module to the RAN slice A reconfiguration indication message is sent, wherein the reconfiguration indication message is used to instruct to update the current configuration information to the reconfiguration information. The technical solution provides a way of reconfiguring RAN slices, which can meet the differentiated performance requirements of different services.

In a possible design, the RAN slice manager obtains the reconfiguration information of the RAN slice, which may include any of the following methods:

Manner 1: The RAN slice manager receives the reconfiguration service request message, wherein the reconfiguration service request message includes service information; then, the RAN slice manager obtains the reconfiguration information of the RAN slice corresponding to the service.

Manner 2: The RAN slice manager receives a RAN slice request message, where the reconfiguration slice request message includes reconfiguration information of the RAN slice; then, the RAN slice manager obtains the reconfiguration information of the RAN slice.

Manner 3: The RAN slice manager receives the status report sent by the RAN slice, wherein the status report is used to describe the operation status of the RAN slice, and then the RAN slice manager determines the reconfiguration information of the RAN slice according to the status report.

In a possible design, after the RAN slice manager sends the reconfiguration indication message to the physical layer functional module, the method may further include: the RAN slice manager sends at least one of the following information to the terminal device: radio spectrum resources configuration information, the identifier of each RAN slice that has been created but not deleted, the center frequency of the radio spectrum resources of each RAN slice that has been created but not deleted, and the Bandwidth information of wireless spectrum resources. During specific implementation, the RAN slice manager may send the broadcast information to the terminal device.

In a possible design, the method may further include: the RAN slice manager sends an update instruction message to the infrastructure controller, where the update instruction message is used to instruct the infrastructure controller to update the resource information and the stored resource information in the physical resource database. At least one of computing resource information.

In a possible design, the method may further include: the RAN slice manager updates the radio spectrum resource information.

In an eleventh aspect, a network device is provided, the network device may include the RAN slice manager described above. The network device may include a transceiver, a memory, and a processor. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instructions stored in the memory, so as to perform the following steps when executing the instructions: acquiring reconfiguration information of the RAN slice, and then sending the RAN slice, infrastructure to the RAN slice through the transceiver At least one of the controller and the physical layer function module sends a reconfiguration instruction message, wherein the reconfiguration instruction message is used to instruct to update the current configuration information to the reconfiguration information.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receive a reconfiguration service request message through the transceiver, wherein the reconfiguration service request message includes service information; then, obtain the service corresponding to the RAN slice reconfiguration information.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receive a RAN slice request message through the transceiver, where the reconfiguration slice request message includes reconfiguration information of the RAN slice; and then obtain the RAN slice request message. Reconfiguration information for RAN slices.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receive a status report sent by the RAN slice through the transceiver, where the status report is used to describe the operating status of the RAN slice, and then, according to The status report determines the reconfiguration information of the RAN slice.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following steps: send at least one of the following information to the terminal device through the transceiver: configuration information of wireless spectrum resources, created but not deleted The identifier of each RAN slice, the center frequency point of the radio spectrum resource of each RAN slice that has been created but not deleted, and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following step: send an update instruction message to the infrastructure controller through the transceiver, wherein the update instruction message is used to instruct the infrastructure controller to update the physical At least one of resource information and computing resource information is stored in the resource database.

In a possible design, when the processor executes the instruction, the processor is further configured to perform the following step: update the wireless spectrum resource information.

A twelfth aspect provides a method for querying a RAN slice, the method may include: the RAN slice manager obtains an identifier of the RAN slice, and if the RAN slice has been created in the query, replying information that the RAN slice exists; If it is found that the RAN slice has not been created, it will reply that the RAN slice does not exist.

In a possible design, the RAN slice manager obtains the identifier of the RAN slice, which may include any of the following methods:

Manner 1: The RAN slice manager receives a first query RAN slice request message including an identifier of the RAN slice.

Manner 2: The RAN slice manager receives a second query RAN slice request message containing service information, and then obtains the identifier of the RAN slice corresponding to the service.

A thirteenth aspect provides a network device that may include the RAN slice manager described above. The network device may include a transceiver, a memory, and a processor. Among them, the memory is used to store instructions. The processor is connected to the memory and the transceiver respectively, and is used for executing the instruction stored in the memory, so as to perform the following steps when executing the instruction: obtain the identifier of the RAN slice, and reply that the RAN slice exists if it is found that the RAN slice has been created. information about the slice; or, if it is found that the RAN slice has not been created, it will reply the information that the RAN slice does not exist.

In a possible design, when the processor executes the instruction, the processor is specifically configured to perform the following steps: receive, through the transceiver, a first query RAN slice request message including an identifier of the RAN slice.

In a possible design, the processor is specifically configured to perform the following steps when executing the instruction: receiving a second query RAN slice request message including service information through the transceiver, and then acquiring the identifier of the RAN slice corresponding to the service .

A fourteenth aspect provides a system for managing RAN slices, the system may include a RAN slice manager and an infrastructure controller. The RAN slice manager is configured to acquire initial configuration information of the RAN slice, and send a creation instruction message to the infrastructure controller, where the creation instruction message includes the initial configuration information. The infrastructure controller is configured to receive the creation instruction message and create the RAN slice according to the initial configuration information.

In a possible design, the initial configuration information may include information of functional modules used by the RAN slice.

In a possible design, the infrastructure controller may be specifically configured to: create the RAN slice according to the initial configuration information and the default configuration information, where the default configuration information includes the RAN slice except the initial configuration required by the infrastructure controller to configure the RAN slice. Configuration information other than configuration information.

In one possible design, the system may also include the RAN slice. The RAN slice manager is further configured to receive a creation response message sent by the infrastructure controller; and send a first update indication message to the RAN slice. The RAN slice is used for: updating the current configuration information of the RAN slice according to the first update indication message.

In a possible design, the RAN slice manager may be specifically configured to: receive a service creation request message including service information; and then acquire initial configuration information of the RAN slice corresponding to the service.

In a possible design, the RAN slice manager may be specifically configured to: receive a request message for creating a RAN slice that includes an identifier of the RAN slice; and then acquire initial configuration information of the RAN slice.

In one possible design, the system may also include physical layer function modules. The RAN slice manager may also be configured to send radio spectrum resource configuration information to the physical layer functional module; wherein the radio spectrum resource configuration information may include at least one group of configuration information, and one group of configuration information may include at least one of the following information: The central frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameter configuration of the wireless spectrum resource. The physical layer functional module is used to use the wireless spectrum resources according to the configuration information of the wireless spectrum resources.

In a possible design, the parameter configuration of the wireless spectrum resource includes at least one of a transmission time interval TTI, a subcarrier interval, and a resource block group RBG.

In a possible design, the RAN slice manager is further configured to send at least one of the following information to the terminal device: configuration information of radio spectrum resources, an identifier of each RAN slice that has been created and has not been deleted, The center frequency point of the radio spectrum resource of each RAN slice created but not deleted and the bandwidth information of the radio spectrum resource of each RAN slice created but not deleted.

In a possible design, the system may further include: a RAN slice database, where the RAN slice database contains the identifiers of the created RAN slices. The RAN slice manager can also be used to update the RAN slice database.

In a possible design, the RAN slice manager may also be used to update the radio spectrum resource information.

In a possible design, the RAN slice manager may be further configured to send a second update instruction message to the infrastructure controller; the infrastructure controller is further configured to update the storage resource information and computing resources according to the second update instruction message at least one of the information.

For the explanation of the relevant content in any of the methods provided in the above-mentioned second aspect to the fourteenth aspect, reference may be made to the above-mentioned first aspect.

It can be understood that any of the above-mentioned apparatuses or systems are used to execute the above-mentioned methods. Therefore, for the beneficial effects that can be achieved, reference may be made to the beneficial effects in the corresponding methods for managing RAN slices provided above. The effect will not be repeated here.

Description of drawings

FIG. 1 is a logical architecture diagram to which the technical solution provided by an embodiment of the present invention is applicable;

2 is a schematic diagram of a physical architecture provided by an embodiment of the present invention;

3 is a schematic diagram of another physical architecture provided by an embodiment of the present invention;

4 is a schematic diagram of another physical architecture provided by an embodiment of the present invention;

5 is a schematic diagram of another physical architecture provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of another physical architecture provided by an embodiment of the present invention;

FIG. 7 is a schematic diagram of another physical architecture provided by an embodiment of the present invention;

8a is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention;

8b is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention;

FIG. 9 is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

10 is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

FIG. 11a is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

FIG. 11b is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

FIG. 12a is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

FIG. 12b is an interaction diagram of another method for creating a RAN slice provided by an embodiment of the present invention;

13 is an interaction diagram of a method for deleting a RAN slice provided by an embodiment of the present invention;

14 is an interaction diagram of another method for deleting a RAN slice provided by an embodiment of the present invention;

FIG. 15 is an interaction diagram of another method for deleting a RAN slice provided by an embodiment of the present invention;

16 is an interaction diagram of a method for reconfiguring RAN slices according to an embodiment of the present invention;

FIG. 17 is an interaction diagram of another method for reconfiguring RAN slices provided by an embodiment of the present invention;

18 is an interaction diagram of another method for reconfiguring RAN slices provided by an embodiment of the present invention;

FIG. 19 is an interaction diagram of a method for querying RAN slices according to an embodiment of the present invention;

FIG. 20 is an interaction diagram of another method for querying RAN slices provided by an embodiment of the present invention;

FIG. 21a is a schematic structural diagram of a network device according to an embodiment of the present invention;

FIG. 21b is a schematic structural diagram of another network device provided by an embodiment of the present invention;

FIG. 22 is a schematic structural diagram of another network device according to an embodiment of the present invention;

FIG. 23 is a schematic structural diagram of another network device according to an embodiment of the present invention;

FIG. 24 is a schematic structural diagram of another network device according to an embodiment of the present invention;

FIG. 25 is a schematic structural diagram of another terminal device according to an embodiment of the present invention;

FIG. 26 is a schematic structural diagram of another terminal device according to an embodiment of the present invention.

Detailed ways

RAN slice refers to a combination of access network functional modules that provide required communication services and network performance, and resources required to run these access network functional modules. Wherein, the access network functional module may include, but is not limited to, at least one of the following information: a packet buffering function module, a packet disassembly function module, a reordering function module, an encryption and decryption function module, a multi-user multiplexing function module, Power distribution function module, multi-antenna management function module, priority management function module, mixer function (ie center frequency shift) module, filter function module, etc. Resources mainly refer to physical resources, and physical resources may include, but are not limited to, at least one of the following information: computing resources, storage resources, and wireless spectrum resources. The wireless spectrum resource may include at least one of the following information: center frequency of the wireless spectrum resource, wireless spectrum bandwidth of the wireless spectrum resource, TTI, subcarrier spacing, RBG, and the like. Optionally, when using the RAN slice, the functional modules of the RAN slice may be configured, which may specifically include at least one of the following configurations: the function configuration of the functional module, and the parameter configuration of the functional module. The functional configuration of the functional module may include, but is not limited to, enabling or disabling the functional module. For example, the functional configuration of the encryption/decryption function module may include enabling the encryption/decryption function. Regarding the parameter configuration of the function module, for example, the parameter configuration of the encryption/decryption function module may include configuring which encryption/decryption algorithm to use.

In order to meet the differentiated performance requirements of different services, RAN slices that provide services for different services (hereinafter referred to as "RAN slices corresponding to services") have differentiated representations. For example, assuming that there are service 1 and service 2, the functional module of the RAN slice corresponding to service 1 may include an encryption and decryption function module, and the TTI is 1ms, and the function module of the RAN slice corresponding to service 2 may not include an encryption and decryption function module. And TTI is 0.5ms.

As shown in FIG. 1 , it is a logical architecture diagram to which the technical solution provided by the embodiment of the present invention is applicable. The logical architecture diagram shown in FIG. 1 includes a RAN slice manager 11 , an infrastructure controller 12 and a RAN slice set 13 . The RAN slice manager 11 is a decision-making unit for managing RAN slices, and managing RAN slices may include, but is not limited to, at least one of the following: creating, deleting, reconfiguring, or querying RAN slices. The infrastructure controller 12 is an execution unit that manages RAN slices. The RAN slice set 13 is a set composed of RAN slices that have been created but not deleted. RAN slice set 13 may include one or more RAN slices.

Optionally, the logical architecture diagram shown in FIG. 1 may further include at least one of the following: a physical resource database 14 , a RAN slice database 15 and a physical layer functional module 16 . The physical resource database 14 is used to store the usage of physical resources; for example, the physical resource database 14 may be used to store information of idle physical resources. The information on physical resources may include, but is not limited to, information on resources such as computing resources, storage resources, and wireless spectrum resources. The wireless spectrum resources may include, but are not limited to, center frequency, wireless spectrum bandwidth, and parameter configuration of the wireless spectrum resources. The parameter configuration of the wireless spectrum resource may include, but is not limited to, at least one of the following information: TTI, subcarrier spacing, and RBG. The RAN slice database 15 is used to store the information of RAN slices; for example, the RAN slice database 15 can be used to store the information of the created RAN slices; optionally, it can also store the information of the uncreated RAN slices, for details, please refer to the following .

The physical resource database 14 can be a public database, or a private database of the RAN slice manager 11 or a private database of the infrastructure controller 12 . The physical resource database 14, as a public database, can be understood as: multiple RAN slice managers 11, or multiple infrastructure controllers 12, or one RAN slice manager 11 and one or more infrastructure controllers 12, or One or more RAN slice managers 11 share the database with one infrastructure controller 12, or multiple RAN slice managers 11 and multiple infrastructure controllers 12. The private database of the RAN slice manager 11 can be understood as: only the RAN slice manager 11 can use the database. The private database of the infrastructure controller 12 can be understood as: only the infrastructure controller 12 can use the database.

The RAN slice database 15 can be used as a public database or as a private database of the RAN slice manager 11 . The RAN slice database 15 is a common database, which can be understood as: multiple RAN slice managers 11 can share the database. The RAN slice database 15 is a private database of the RAN slice manager 11, and it can be understood that only the RAN slice database 11 can use the database.

In addition, the physical resource database 14 and the RAN slice database 15 may exist at the same time, only one may exist, or neither may exist. When it does not exist, the corresponding RAN slice or physical resource information can be stored inside the RAN slice manager 11 or the infrastructure controller 12, and the RAN slice manager 11 or the infrastructure controller 12 can use and update the RAN slice or RAN slice stored by itself. Physical resource information.

The logical architecture shown in Figure 1 can be applied to various physical architectures. A few examples are given below.

FIG. 2 shows a schematic diagram of a physical architecture, and the physical architecture is specifically the physical architecture of an independent base station. The physical architecture shown in FIG. 2 may include multiple base stations 21, and a RAN slice manager 11 may be deployed on each base station 21 to serve as a decision unit for managing RAN slices in the base station. An infrastructure controller 12 may be deployed on each base station 21 to serve as an execution unit for managing RAN slices in the base station. A RAN slice set 13 may be deployed on each base station 21, and the RAN slice set 13 is a set composed of RAN slices that have been created and have not been deleted in the base station. Optionally, a physical resource database 14 may be deployed on each base station 21 for storing the usage of the physical resources of the base station. Optionally, a RAN slice database 15 may be deployed on each base station 21 to store information on RAN slices of the base station. Physical layer functional modules 16 may be deployed on each base station 21 .

FIG. 3 shows a schematic diagram of another physical architecture, and the physical architecture is specifically a clustered base station physical architecture. The physical architecture shown in FIG. 3 may include one or more clusters, and each cluster may include a cluster head base station 31 and one or more non-cluster head base stations 32 . In the physical architecture shown in FIG. 3 : a RAN slice manager 11 may be deployed on any base station in a cluster to serve as a decision unit for managing RAN slices in the cluster. For example, the RAN slice manager 11 may be deployed on the cluster head base station 31 or the non-cluster head base station 32 . Wherein, FIG. 3 illustrates the deployment of the RAN slice manager 11 on the cluster head base station 31 as an example. An infrastructure controller 12 may be deployed on each base station in a cluster to serve as an execution unit for managing RAN slices in the base station. A RAN slice set 13 may be deployed on each base station in a cluster, and the RAN slice set 13 is a set composed of RAN slices that have been created but not deleted in the base station. Optionally, a physical resource database 14 may be deployed on each base station for storing information on the use of physical resources of the base station. Alternatively, the physical resource database 14 may be deployed on any base station to store the usage of the cluster, for example, the physical resource database 14 may be deployed on the cluster head base station 31 . Optionally, a RAN slice database 15 may be deployed on each base station to store information about RAN slices of the base station; or, a RAN slice database 15 may be deployed on any base station to store information about RAN slices of this cluster, For example, the RAN slice database 15 is deployed on the cluster head base station 31 . A physical layer functional module 16 may be deployed on each base station.

FIG. 4 shows a schematic diagram of another physical architecture, which is specifically a centralized physical architecture. The physical architecture shown in FIG. 4 may include a centralized control unit 41 and one or more base stations 42 connected thereto. Wherein, the centralized control unit 41 may be, but not limited to, a traditional core network. In the physical architecture shown in FIG. 4 : a RAN slice manager 11 may be deployed on each base station 42 to serve as a decision-making unit for managing RAN slices in the base station. Alternatively, the RAN slice manager 11 may be deployed on the centralized control unit 41 or each base station 42 to serve as the decision unit for managing RAN slices in the centralized control unit. For example, the RAN slice manager 11 is deployed on the centralized control unit 41 . Wherein, FIG. 4 takes the deployment of the RAN slice manager 11 on the centralized control unit 41 as an example to illustrate. An infrastructure controller 12 may be deployed on each base station 42 to serve as an execution unit for managing RAN slices in the base station. A RAN slice set 13 may be deployed on each base station 42 , and the RAN slice set 13 is a set composed of RAN slices that have been created and have not been deleted in the base station. Optionally, a physical resource database 14 may be deployed on each base station 42 for storing information on the usage of physical resources of the base station. Alternatively, the physical resource database 14 may be deployed on the centralized control unit 41 or any one of the base stations 42 to store information on the usage of physical resources of all base stations managed by the centralized control unit, for example, the physical resources are deployed on the centralized control unit 41 Database 14. Optionally, the RAN slice database 15 may be deployed on each base station 42 to store the information of the RAN slice of the base station; or, the RAN slice database 15 may be deployed on the centralized control unit 41 or any base station 42 to store this For the information of the RAN slice of the base station, for example, the RAN slice database 15 is deployed on the centralized control unit 41 . A physical layer functional module 16 may be deployed on each base station.

FIG. 5 shows a schematic diagram of another physical architecture, which is specifically an independent BBU physical architecture in a C-RAN, where the C-RAN is a cloud radio access network or centralized radio access network. The English abbreviation of BBU is the English abbreviation of indoor baseband processing unit (building base bandunit). The physical architecture shown in FIG. 5 may include: one or more BBUs 51 and one or more remote radio units (radio remote units, RRU) 52 connected to each BBU 51 . A RAN slice manager 11 may be deployed on each BBU 51 to serve as a decision unit for managing RAN slices in the BBU and the RRU connected to the BBU. If all the functions of the RAN slice are on the BBU 51, the infrastructure controller 12 may be deployed on each BBU 51 having the function of the RAN slice to serve as an execution unit for managing the RAN slice in the BBU. Alternatively, if part of the functions of the RAN slice are on the BBU 51 and part of the functions are on the RRU 52, the infrastructure controller 12 may be deployed on both the BBU 51 and the RRU 52 with the functions of the RAN slice to serve as the execution unit for managing the RAN slice. A RAN slice set 13 may be deployed on each BBU 51 , and the RAN slice set 13 is a set composed of RAN slices that have been created but not deleted in the BBU. Alternatively, a RAN slice set 13 may be deployed on each RRU 52, and the RAN slice set is a set composed of RAN slices that have been created and have not been deleted in this RRU. Alternatively, a part of the set of RAN slices may be deployed on each BBU 51 and another part of the set of RAN slices may be deployed on each RRU 52 . Optionally, a physical resource database 14 may be deployed on each BBU 51 for storing the usage status of the physical resource information of the BBU and the RRU connected to the BBU. Optionally, a RAN slice database 15 may be deployed on each BBU 51 to store information about the RAN slice of the BBU and the RRU connected to the BBU. Physical layer functional modules 16 may be deployed on each RRU 52 .

FIG. 6 shows a schematic diagram of another physical architecture, and the physical architecture is specifically a clustered BBU physical architecture in a C-RAN. The physical architecture shown in FIG. 6 may include one or more clusters, and each cluster may include a cluster head BBU61 and one or more RRUs 62 connected to the cluster head BBU61, and one or more non-cluster head BBU63 and the cluster head BBU63 One or more RRUs 62 connected to the non-cluster head BBU63. In the physical architecture shown in FIG. 6 , the RAN slice manager 11 can be deployed on any BBU in a cluster, including the cluster head BBU61 or the non-cluster head BBU63, to serve as the decision-making unit for managing RAN slices in the cluster, for example , the RAN slice manager 11 is deployed on the cluster head BBU61, wherein FIG. 6 is an example of the deployment of the RAN slice manager 11 on the cluster head BBU61. For the deployment situation of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in FIG. 6 , reference may be made to the deployment situation of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in FIG. 5 , which will not be repeated here.

Optionally, a physical resource database 14 can be deployed on each BBU to store the usage of the physical resource information of the BBU; or, a physical resource database 14 can be deployed on any BBU to store the BBUs of this cluster and this BBU. The usage situation of the physical resource information in the RRUs connected to the cluster BBU, for example, the physical resource database 14 is deployed on the cluster head BBU61. Optionally, a RAN slice database 15 may be deployed on each BBU to store information about RAN slices of this BBU; or, a RAN slice database 15 may be deployed on any BBU to store the connection between the BBU of the cluster and the BBU of the cluster. The information of the RAN slice in the RRU, for example, the RAN slice database is deployed on the cluster head BBU61. Physical layer functional modules 16 may be deployed on each RRU 62 .

FIG. 7 shows a schematic diagram of another physical architecture, which is specifically a centralized physical architecture in C-RAN. The physical architecture shown in FIG. 7 may include a centralized control unit 71, one or more BBUs 72 connected thereto, and one or more RRUs 73 connected with each BBU 72; wherein, the centralized control unit 71 may be, but is not limited to, a traditional core network. In the physical architecture shown in FIG. 7 : the RAN slice manager 11 can be deployed on each BBU 72 to serve as the decision unit for managing RAN slices in the BBU; or, the RAN slice can be deployed on the centralized control unit 71 or any BBU 72 The manager 11 is used as the decision-making unit for managing RAN slices in the centralized control unit. For example, the RAN slice manager 11 is deployed on the centralized control unit 71, and FIG. 7 shows the deployment of the RAN slice manager on the centralized control unit 71. 11 as an example. For the deployment situation of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in FIG. 7 , reference may be made to the deployment situation of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in FIG. 5 , which will not be repeated here. Optionally, a physical resource database 14 can be deployed on each BBU 72 to store the usage information of the physical resources of the BBU; or, a physical resource database 14 can be deployed on the centralized control unit 71 or any BBU 72 to store The usage of information of physical resources in all BBUs and RRUs connected to the BBUs managed by the centralized control unit 71 , for example, the physical resource database 14 is deployed on the centralized control unit 71 . Optionally, the RAN slice database 15 may be deployed on each BBU 72 to store the information of the RAN slice of the BBU; or, the RAN slice database 15 may be deployed on the centralized control unit 71 or any BBU 72 to store the centralized control unit. Information of RAN slices in all managed BBUs and RRUs connected to the BBUs, for example, the RAN slice database 15 is deployed on the centralized control unit 71 . Physical layer functional modules 16 may be deployed on each RRU 73 .

The following is a brief introduction to RAN slices:

1. RAN slice and RAN slice configuration information

The configuration information of different RAN slices is different, and the identifier of the RAN slice can be used to mark a RAN slice. The same RAN slice may have one or more kinds of configuration information, but at the same time, one RAN slice has only one kind of configuration information. It should be noted that the reasons for a RAN slice having multiple configuration information may include, but are not limited to, reconfiguration of a RAN slice; that is, before and after reconfiguration of a RAN slice, the configuration information of the RAN slice is different. Exemplarily, the correspondence between RAN slices and configuration information is shown in Table 1:

Table 1

The configuration information of RAN slice 2 in Table 1 can be understood as: at time t1, the configuration information of RAN slice 2 is configuration information 21; at time t2, the configuration information of RAN slice 2 is configuration information 22. The explanation of the configuration information of RAN slice 1 is similar, and details are not repeated here.

2. RAN slice configuration information

The configuration information of the RAN slice may include: functional module information and physical resource information. The different configuration information may include configuration information of different RAN slices and different configuration information of the same RAN slice. Specifically, it may include, but is not limited to, at least one of differentiated functional module information and differentiated wireless spectrum resources. Wherein, the information of the differentiated functional modules may include, but is not limited to, at least one of the following information: composition information of the differentiated functional modules, such as whether there is an encryption and decryption functional module; functional configuration of the differentiated functional modules, such as whether Enable encryption and decryption function; parameter configuration of differentiated function modules, such as which encryption and decryption algorithm to use for encryption and decryption functions. The differentiated physical resource information may include, but is not limited to, at least one of the following information: differentiated computing resources, differentiated storage resources, differentiated wireless spectrum resources, and the like.

The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship. The "first" and "second" and the like in this document are for the purpose of distinguishing different objects more clearly, and do not make any other limitation. As used herein, "plurality" refers to two or more. The "device" described herein may be understood as an access network device, and the device may include, but is not limited to, the physical architecture shown in any of the foregoing Figures 2 to 7 .

It should be noted that, in the following description, the technical solution provided by the embodiment of the present invention is applied to the logical architecture diagram shown in FIG. 1 as an example for description. Those skilled in the art should be able to The technical solutions provided in the embodiments of the present invention are mapped to corresponding physical architectures, which will not be described hereinafter.

As shown in FIG. 8a, it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 8a may include the following steps S801a-S803a:

S801a: The RAN slice manager obtains the initial configuration information of the RAN slice.

Optionally, S801a may include: the RAN slice manager obtains the initial configuration information of the RAN slice through the RAN slice database. The initial configuration information of different RAN slices may be the same or different.

Optionally, the initial configuration information of the RAN slice may include information of functional modules used by the RAN slice. Further optionally, it may also include at least one of the following information: the functional configuration of the functional module used by the RAN slice, the parameter configuration of the functional module used by the RAN slice, the computing resource information used by the RAN slice, the The storage resource information used by the RAN slice and the wireless spectrum resource information used by the RAN slice. Wherein, the parameter configuration of the functional module includes any one or more parameter configurations of any one or more functional modules in the functional module. The wireless spectrum resource includes, but is not limited to, at least one of the following information: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameter configuration of the wireless spectrum resource. The parameter configuration of the wireless spectrum resource includes at least one of TTI, subcarrier spacing and RBG.

S802a: The RAN slice manager sends a creation instruction message to the infrastructure controller, and the infrastructure controller receives the creation instruction message. The creation instruction message may include initial configuration information, and the creation instruction message is used to instruct the infrastructure controller to create a RAN slice according to the initial configuration information.

Specifically, the initial configuration information included in the creation instruction message may be part or all of the initial configuration information obtained in S801a.

S803a: The infrastructure controller creates a RAN slice according to the initial configuration information in the creation instruction message.

Creating a RAN slice can be understood as: according to the configuration information, allocate physical resources to the RAN slice and start functional modules. These functional modules run using the allocated physical resources.

During specific implementation, RAN slices can be created in any of the following ways:

Manner 1: The creation instruction message may contain all the configuration information required by the infrastructure controller to create the RAN slice. In this case, the infrastructure controller creates the RAN slice according to the entire configuration information. Wherein, the whole configuration information may be the above-mentioned initial configuration information. This method can be understood as: directly create the required RAN slice. For details, refer to Example 1 or Example 2 below.

Manner 2: The creation instruction message may include part of the configuration information required by the infrastructure controller to create the RAN slice. In this case, the infrastructure controller may create the RAN slice according to the part of the configuration information and the default configuration information. The part of the configuration information may be a part of the above-mentioned initial configuration information. The default configuration information here may include configuration information other than the part of the configuration information required by the infrastructure controller to create the RAN slice. This possible design can be understood as: creating a semi-universal RAN slice. Subsequently, the current configuration information of the semi-universal RAN slice can be reconfigured, so as to provide differentiated performance requirements for different services. For details, refer to the following Example 3 or Example 4.

The embodiment of the present invention provides a method for creating a RAN slice. By setting the initial configuration information of different RAN slices, the created RAN slices are different. In this way, during specific implementation, the different services can be mapped according to the performance requirements of different services. to different RAN slices to meet the differentiated performance requirements of different services.

As shown in FIG. 8b, it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 8b may include the following steps S801b-S802b:

S801b: The RAN slice manager sends a creation instruction message to the infrastructure controller, and the infrastructure controller receives the creation instruction message.

S802b: The infrastructure controller creates a RAN slice according to the default configuration information.

In this embodiment, the creation instruction message may not contain any configuration information required for creating a RAN slice. In this case, the infrastructure controller may create a RAN slice according to the default configuration information. The default configuration information here may include all configuration information required by the infrastructure controller to create the RAN slice. This optional design can be understood as: creating a common RAN slice. Subsequently, the current configuration information of the general RAN slice can be reconfigured, so as to provide differentiated performance requirements for different services. For details, refer to the following Examples 3 to 6.

Example 1

As shown in FIG. 9 , it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 9 may include the following steps S901 to S915:

S901: The RAN slice manager receives a service creation request message, wherein the service creation request message includes service information.

Specifically: the RAN slice manager receives a service creation request message sent by the network side device or the terminal side device. Among them, the network side device is also called the northbound device, and the terminal side device is also called the southbound device. The network side device may include, but is not limited to, any of the following: a service provider server, a network operator server, a core network network element, and the like. For example, the service provider server may include, but is not limited to, any of the following: a Baidu server, a Tencent server, and the like. The network operator server may include, but is not limited to, any of the following: a mobile server, a China Unicom server, and the like. The core network elements may include but are not limited to any of the following: a home subscriber server (home subscriber server, HSS), a mobility management entity (mobility management entity, MME), a gateway (gateway, GW), policies and charging rules Network elements such as a functional unit (policy and charging rules function, PCRF), and other network elements that may appear in the future. The terminal-side device may include, but is not limited to, any of the following: a mobile phone, a computer, a virtual reality (virtual reality, VR) helmet, an Internet of Things device, a camera, and the like.

If services are distinguished according to service types, the information of the service may include: the ID of the service

(identity) or the service quality (quality of service, QoS) requirements of the business. The QoS requirement may include, but is not limited to, at least one of the following information: delay, throughput, packet loss rate, and the like. If the service is distinguished according to the service type and the operator/service provider, the information of the service may include: the ID of the service and the ID of the operator/service provider.

S902: The RAN slice manager determines whether a RAN slice corresponding to the service needs to be created according to the service information.

If not, end. If yes, execute S903.

During specific implementation, if the judgment result in S902 is "No", it means that the RAN slice has been created, and the RAN slice manager maps the service to the RAN slice corresponding to the service, and then uses the RAN slice to provide the service for the service. Serve.

S902 may include but not be limited to the following two implementation manners:

Manner 1: The RAN slice manager determines whether the RAN slice corresponding to the service has been created by accessing the RAN slice database. If so, it is determined that the RAN slice does not need to be created, and if not, it is determined that the RAN slice needs to be created.

Manner 2: The RAN slice manager accesses the RAN slice database to determine whether the initiator (for example, the operator/service provider) that creates the RAN slice has the right to create the RAN slice corresponding to the service. If and the RAN slice corresponding to the service has not been created, it is determined that the RAN slice needs to be created; otherwise, the RAN slice does not need to be created. It is worth noting that it is also possible to first determine whether the RAN slice corresponding to the service has been created, and if not, then determine whether the initiator of the RAN slice creation has the right to create the RAN slice corresponding to the service. RAN slice, otherwise the RAN slice does not need to be created.

The following is an exemplary description of the correspondence between services and RAN slices according to different methods of differentiating services:

If different services are distinguished according to service types, the RAN slices corresponding to different types of services may be the same or different, and the RAN slices corresponding to the same type of services are the same. An example is shown in Table 2:

Table 2

business information RAN slice identification ID of the video service RAN slice 1 ID of the voice service RAN slice 1 SMS service ID RAN slice 2 ID of the game business RAN slice 3

If different services are distinguished according to service types and operators/service providers, then: the RAN slices corresponding to services provided by different operators/service providers of the same type may be the same or different; The RAN slices corresponding to the services are the same. The RAN slices corresponding to the services provided by different operators/service providers of different types may be the same or different, and the services provided by the same operator/service providers of different types may be the same or different. An example is shown in Table 3:

table 3

The RAN slice database may store the identifiers of the created RAN slices, and optionally, may also store the identifiers of the uncreated RAN slices. The two cases are exemplified below:

Case 1: The RAN slice database stores the identifiers of the created RAN slices and the identifiers of the uncreated RAN slices. In this case, the RAN slice database may store the correspondence between the following information: service information, ID of the RAN slice, initial configuration information of the RAN slice, and information on whether the RAN slice has been created.

If different services are distinguished according to service types, a RAN slice database can be shown in Table 4:

Table 4

If different services are distinguished according to service types and operators/service providers, a RAN slice database can be shown in Table 5:

table 5

Wherein, "1" in Table 4 and Table 5 indicates that the RAN slice has been created, and "0" indicates that the RAN slice has not been created. During specific implementation, information about whether a RAN slice has been created may also be indicated in other manners, which is not limited in this embodiment of the present invention. The initial configuration information 1 and 2 in Table 4 may be the same or different. Any two pieces of initial configuration information in Table 5 may be the same or different.

Case 2: The RAN slice database stores the identifiers of the created RAN slices, and does not store the identifiers of the uncreated RAN slices. This situation is generally applicable to distinguish different services according to service types and operators/service providers. In this case, the correspondence between the following information can be stored in the RAN slice database: service information (including service ID and operator/service provider identifier), RAN slice ID, and RAN slice initial configuration information. Here are two examples of this situation:

Example 1: Before the RAN slice is created, the ID of the operator/service provider corresponding to the RAN slice is not saved. In this example, if no RAN slice has been created in the system, a RAN slice database can be shown in Table 6:

Table 6

Based on Table 6, if some RAN slices have been created in the system, a RAN slice database can be shown in Table 7:

Table 7

Example 2: Before creating a RAN slice, save the ID of the operator/service provider corresponding to the RAN slice. In this example, if no RAN slice has been created in the system, a RAN slice database can be shown in Table 8:

Table 8

It should be noted that, in the scenario where the operator/service provider needs to pay for the RAN slice to have the right to use the RAN slice, optionally, the RAN slice database can store the ID of the operator/service provider is the paid operator /The ID of the service provider, does not store the ID of the operator/service provider without payment. The paid operator/service provider refers to the operator/service provider that has purchased the right to use the RAN slice; the non-paid operator/service provider refers to the operator/service provider that has not purchased the usage right of the RAN slice. For example, the IDs of the operators/service providers in Table 8 are the IDs of the operators/service providers who have purchased the corresponding RAN slice usage rights. For example, Tencent and Alibaba have purchased the RAN slice usage rights corresponding to the video service.

Based on Table 8, if some RAN slices have been created in the system, a RAN slice database can be shown in Table 9:

Table 9

It should be noted that, in the scenario where the operator/service provider needs to pay for the RAN slice to have the right to use the RAN slice, S902 can be specifically implemented through the second method above.

S903: The RAN slice manager obtains the initial configuration information of the RAN slice by accessing the RAN slice database.

Among them, S901-S903 may be considered as a specific implementation manner of the above-mentioned S801a.

S904: The RAN slice manager decides whether to create the RAN slice according to the initial configuration information.

If yes, execute S905; if not, end.

Specifically, the RAN slice manager accesses the physical resource database to obtain the usage of the physical resources. If the usage of physical resources satisfies the physical resources required for configuring the RAN slice, the RAN slice can be created; if the usage of the physical resources does not satisfy the physical resource information required for configuring the RAN slice, the RAN slice cannot be created . The usage of physical resources may include information about idle physical resources, etc. The idle physical resources may include but not limited to information about at least one of the following resources: computing resources, storage resources, and wireless spectrum resources. It can be understood that when the physical resources required for configuring a RAN slice include multiple physical resources, if all the free physical resources meet the corresponding physical resources required for configuring the RAN slice, the RAN slice can be created; If a physical resource does not satisfy the corresponding physical resource information required for configuring the RAN slice, the RAN slice cannot be created.

Exemplarily, if the physical resources required for configuring the RAN slice include computing resources and storage resources, in this case, if both the idle computing resources and the idle storage resources meet the corresponding resources required for configuring the RAN slice, then the RAN slice can be created. The RAN slice; if at least one of the idle computing resources and idle storage resources does not meet the corresponding resources required for configuring the RAN slice, the RAN slice cannot be created. For example, assuming that the idle computing resources are 1 CPU, the idle storage resources are 10G bytes, the computing resources required to configure the RAN slice are 1 CPU, and the storage resources required to configure the RAN slice are 5G bytes , then the RAN slice can be created. As another example, assuming that the idle computing resources are 1 CPU, the idle storage resources are 10G bytes, the computing resources required to configure the RAN slice are 1 CPU, and the storage resources are 20G bytes, then, although the idle resources are The computing resources are the same as the computing resources required to configure the RAN slice, but the free storage resources are smaller than the storage resources required to configure the RAN slice, so the RAN slice cannot be created.

S905: The RAN slice manager sends a creation instruction message to the infrastructure controller, and the infrastructure controller receives the creation instruction message sent by the RAN slice manager. The creation instruction message includes initial configuration information.

S906: The infrastructure controller creates the RAN slice according to the initial configuration information included in the creation instruction message.

In this embodiment, it is considered that the initial configuration information included in the creation instruction message is all the information required by the infrastructure controller to create the RAN slice.

S907: The infrastructure controller replies a creation response message to the RAN slice manager; the RAN slice manager receives the creation response message replied by the infrastructure controller.

S908: The RAN slice manager determines whether radio spectrum resources need to be configured.

Since different RAN slices can share wireless spectrum resources, the RAN slice manager may, according to the configuration information of the RAN slice, comprehensively consider the configuration information of other RAN slices, and decide whether to configure the wireless spectrum resources. The embodiment of the present invention does not limit the specific implementation manner.

If yes, execute S909; if not, execute S911.

S909: The RAN slice manager sends radio spectrum resource configuration information to the physical layer function module; the physical layer function module receives the radio spectrum resource configuration information sent by the RAN slice manager.

Specifically, the RAN slice manager directly sends the radio spectrum resource configuration information to the physical layer functional module, or sends the radio spectrum resource configuration information to the physical layer functional module via other functional modules.

The wireless spectrum resource configuration information may include at least one set of configuration information, and a set of configuration information may include but not limited to at least one of the following information: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameters of the wireless spectrum resource. configuration. Optionally, the parameter configuration of the wireless spectrum resource may include at least one of TTI, subcarrier spacing and RBG.

S910: The physical layer functional module uses the wireless spectrum resource according to the wireless spectrum resource configuration information.

S911: The RAN slice manager sends at least one of the following information to the terminal device: configuration information of radio spectrum resources, an identifier of each RAN slice that has been created but not deleted, and each RAN slice that has been created but not deleted The center frequency point of the radio spectrum resource and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

Specifically, the sending of the RAN slice manager to the terminal device may include but is not limited to: the RAN slice manager sends directly to the terminal device, or the RAN slice manager sends the RAN slice manager to the terminal device through the physical layer function module, or the RAN slice manager sends the The RAN slice and the physical layer function module are sent, or the RAN slice manager sends the RAN slice and the physical layer function module to the terminal device through the common RAN slice and the physical layer function module. A common RAN slice refers to a RAN slice shared by multiple RAN slices in the system, for example, a common control channel of multiple RAN slices constitutes a shared RAN slice.

The purpose of executing S911 is to enable the terminal device to obtain the wireless spectrum resource configuration information, and use the wireless spectrum resource according to the wireless spectrum resource configuration information.

S912: The RAN slice manager updates the RAN slice database.

Based on the above situation 1, S912 may include: the RAN slice manager updates the information on whether the RAN slice has been created in the RAN slice database. Based on Example 1 in the above case 2, S912 may include: the RAN slice manager adds the ID of the RAN slice and the ID of the operator/service provider corresponding to the RAN slice in the RAN slice database. Based on example 2 in the above case 2, S912 may include: the RAN slice manager adds the ID of the RAN slice in the RAN slice database.

S913: The RAN slice manager sends an update indication message to the infrastructure controller, and the infrastructure controller receives the update indication message sent by the RAN slice manager.

S914: The RAN slice manager updates at least one of storage resource information and computing resource information in the physical resource database according to the update instruction message.

The storage resource information may include, but is not limited to, at least one of the following information: information on idle storage resources, information on which RAN slices the used storage resources are used by, and the like. The computing resource information may include, but is not limited to, at least one of the following information: information on idle computing resources, information on which RAN slice is used by the used computing resources, and the like.

For example, assuming that before the RAN slice is created, the free storage resources in the physical resource database are 20G bytes, if the storage resources required for configuring the RAN slice are 5G bytes, after the RAN slice is created, The infrastructure controller updates the free storage resources in the physical resource database to 15G bytes.

S915: The RAN slice manager updates the radio spectrum resources in the physical resource database.

The wireless spectrum resource information includes, but is not limited to, at least one of the following information: center frequency and bandwidth information of idle wireless spectrum resources, and configuration information of used wireless spectrum resources. The configuration information of the wireless spectrum resource is at least one of TTI, subcarrier spacing, and RBG of the specified center frequency point and/or the specified spectrum bandwidth of the wireless spectrum resource.

Exemplarily, before executing S910, there are two types of idle wireless spectrum resources in the physical resource database, namely 1-10 Hz and 21-30 Hz, and in S909, the physical layer function module starts to use the 21-30 Hz wireless spectrum resources. , then in S915, the RAN slice manager updates the idle radio spectrum resources in the physical resource database to 1-10 Hz.

It should be noted that, the embodiment of the present invention does not limit the execution order of S912, S913-S914, and S915.

Example 2

As shown in FIG. 10 , it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 10 may include the following steps S1001 to S1015:

S1001: The RAN slice manager receives a request message for creating a RAN slice, wherein the request message for creating a RAN slice includes an identifier of the RAN slice.

Specifically, the RAN slice manager receives a request message for creating a RAN slice sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1002: The RAN slice manager determines whether the RAN slice needs to be created.

If yes, execute S1003; if not, end.

Specifically, the RAN slice manager can determine whether the RAN slice has been created by accessing the RAN slice database. If so, it is determined that the RAN slice does not need to be created, and if not, it is determined that the RAN slice needs to be created.

In this embodiment, the RAN slice database may store the identifiers of the created RAN slices and the identifiers of the uncreated RAN slices. In this case, the RAN slice database may be as shown in Table 4 or Table 5. Based on Table 4 or Table 5, the RAN slice manager determines whether a RAN slice has been created by looking up "information on whether a RAN slice has been created" in the RAN slice database.

S1003 to S1015: the same as the above S903 to S915.

Example 3a

As shown in FIG. 11a , it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 11a may include the following steps S1101a to S1117a:

S1101a to S1104a: the same as the above-mentioned S901 to S904.

S1105a: The RAN slice manager sends a creation instruction message to the infrastructure controller; the infrastructure controller receives the creation instruction message sent by the RAN slice manager. The creation instruction message is used to instruct the infrastructure controller to create the RAN slice according to the initial configuration information and the default configuration information.

The initial configuration information included in the creation instruction message is part of the configuration information required by the infrastructure controller to create the RAN slice.

S1106a: The infrastructure controller creates the RAN slice according to the initial configuration information and the default configuration information.

S1107a: The infrastructure controller replies a creation response message to the RAN slice manager; the RAN slice manager receives the creation response message sent by the infrastructure controller.

S1108a: The RAN slice manager sends an update indication message to the RAN slice; the RAN slice receives the update indication message sent by the RAN slice manager. Wherein, the update indication message may include reconfiguration information of the RAN slice.

S1109a: The RAN slice manager updates the current configuration information of the RAN slice according to the reconfiguration information of the RAN slice.

S1110a to S1117a: The same as the above-mentioned S908 to S915.

It should be noted that, the embodiment of the present invention does not limit the execution order of S1109a and S1107a to S1108a. In this embodiment, the RAN slice is first created according to the default configuration information and the initial configuration information, which can quickly preempt resources, so that the RAN slice can be created quickly; and the signaling overhead of creating an indication message can also be saved.

Example 3b

As shown in FIG. 11b, it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 11b may include the following steps S1101b to S1117b:

S1101b to S1102b: the same as the above-mentioned S901 to S902.

S1103b: The RAN slice manager sends a creation instruction message to the infrastructure controller; the infrastructure controller receives the creation instruction message sent by the RAN slice manager. Wherein, the creation instruction message does not include initial configuration information, and the creation instruction message is used to instruct the infrastructure controller to create a RAN slice according to the default configuration information.

S1104b: The infrastructure controller creates the RAN slice according to the default configuration information.

S1105b to S1115b: the same as the above-mentioned S1107a to S1117a.

In this embodiment, the RAN slice is first created according to the default configuration information, which can quickly preempt resources, so that the RAN slice can be created quickly; and the signaling overhead of creating an indication message can also be saved.

Example 4a

As shown in FIG. 12a, it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 12a may include the following steps S1201a-S1217a:

S1201a: The RAN slice manager receives a request message for creating a RAN slice, where the request message for creating a RAN slice includes an identifier of the RAN slice.

Specifically, the RAN slice manager receives a request message for creating a RAN slice sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1202a to S1204a: the same as the above-mentioned S1002 to S1004.

S1205a to S1217a: the same as the above-mentioned S1105a to S1117a.

In this embodiment, the RAN slice is first created according to the default configuration information, which can quickly preempt resources, so that the RAN slice can be created quickly; and the signaling overhead of creating an indication message can also be saved.

Example 4b

As shown in FIG. 12b, it is an interaction diagram of a method for creating a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 12b may include the following steps S1201b to S1215b:

S1201b to S1202b: the same as the above-mentioned S1201a to S1202a.

S1203b to S1215b: the same as the above-mentioned S1103b to S1115b.

The following describes the method for deleting a RAN slice provided by the embodiment of the present invention.

Example 5

As shown in FIG. 13 , it is an interaction diagram of a method for deleting a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 13 may include the following steps S1301-S1318:

S1301: The RAN slice manager receives a service deletion request message, wherein the service deletion request message includes service information.

Specifically, the RAN slice manager receives the delete service request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1302: The RAN slice manager obtains the identifier of the RAN slice corresponding to the service.

For the method for the RAN slice manager to obtain the identifier of the RAN slice corresponding to the service, reference may be made to the first implementation in S902 above.

S1303: The RAN slice manager acquires the service corresponding to the RAN slice, and determines whether the service corresponding to the RAN slice also includes other services.

If yes, execute S1304; if not, execute S1307.

Based on Table 2, if the service in S1301 is the SMS service, the service corresponding to the RAN slice (ie, RAN slice 2) is only the SMS service; if the service in S1301 is the video service, the service corresponding to the RAN slice is the video service. It also includes voice services.

S1304: The RAN slice manager sends a service deletion indication message to the RAN slice, and the RAN slice receives the service deletion indication message sent by the RAN slice manager. Wherein, the service deletion instruction message carries the information of the service.

S1305: The RAN slice deletes the service according to the service deletion instruction message.

S1306: The RAN slice replies to the RAN slice manager with a service deletion response message; the RAN slice manager receives the service deletion response message returned by the RAN slice.

After executing S1306, the process ends.

S1307: The RAN slice manager sends a RAN slice deletion instruction message to the infrastructure controller; the infrastructure controller receives the RAN slice deletion instruction message sent by the RAN slice manager. Wherein, the delete RAN slice indication message includes the identifier of the RAN slice.

S1308: The infrastructure controller deletes the RAN slice according to the RAN slice deletion instruction message.

S1309: The infrastructure controller replies a delete RAN slice response message to the RAN slice manager; the RAN slice manager receives the delete RAN slice response message replied by the infrastructure controller.

S1310: The RAN slice manager decides whether the radio spectrum resources used by the RAN slice need to be placed in an idle state.

If yes, execute S1311; if not, execute S1314.

If the radio spectrum resources used by this RAN slice are shared by other RAN slices, it is not necessary to put the radio spectrum resources used by this RAN slice in an idle state; if the radio spectrum resources used by this RAN slice, at the current moment, only this RAN slice is available If it is used, the radio spectrum resources used by the RAN slice can be placed in an idle state.

S1311: The RAN slice manager sends radio spectrum resource configuration information to the physical layer function module; the physical layer function module receives the radio spectrum resource configuration information sent by the RAN slice manager.

The wireless spectrum resource configuration information includes at least one group of configuration information, and a group of configuration information includes at least one of the following information: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource, and the parameter configuration of the wireless spectrum resource.

S1312: The physical layer function module places the radio spectrum resources used by the RAN slice in an idle state according to the radio spectrum resource configuration information.

S1313: The physical layer functional module replies with a radio spectrum resource configuration response message to the RAN slice manager, and the RAN slice manager receives the radio spectrum resource configuration response message replied by the physical layer functional module.

S1314: The RAN slice manager sends at least one of the following information to the terminal device: configuration information of radio spectrum resources, an identifier of each RAN slice that has been created but not deleted, and each RAN slice that has been created but not deleted The center frequency point of the radio spectrum resource and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

The sending of the RAN slice manager to the terminal device may include, but is not limited to: the RAN slice manager sends directly to the terminal device, or the RAN slice manager sends to the terminal device through the physical layer functional module, or the RAN slice manager passes through the RAN The slice and the physical layer function module are sent, or the RAN slice manager sends it to the terminal device through the common RAN slice and the physical layer function module.

The purpose of executing S1314 is to enable the terminal device to obtain the information of the RAN slice, and to use the appropriate RAN slice to transmit the corresponding service.

S1315: The RAN slice manager updates the RAN slice database.

Based on the above situation 1, S1315 may include: the RAN slice manager updates the information on whether the RAN slice has been created in the RAN slice database. Based on Example 1 in the above case 2, S1315 may include: the RAN slice manager deletes the ID of the RAN slice and the ID of the operator/service provider corresponding to the RAN slice in the RAN slice database. Based on example 2 in the above case 2, S1315 may include: the RAN slice manager deletes the ID of the RAN slice in the RAN slice database.

S1316 to S1318: the same as the above S913 to S915.

Example 6

As shown in FIG. 14 , it is an interaction diagram of a method for deleting a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 14 may include the following steps S1401-S1413:

S1401: The RAN slice manager receives a RAN slice deletion request message, where the RAN slice deletion request message includes an identifier of the RAN slice.

Specifically, the RAN slice manager receives a delete RAN slice request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1402-S1413: Same as S1307-S1318 above.

Example 7

As shown in FIG. 15 , it is an interaction diagram of a method for deleting a RAN slice provided by an embodiment of the present invention. The method shown in FIG. 13 may include the following steps S1501 to S1513:

S1501: The RAN slice manager receives a status report sent by a RAN slice, where the status report includes an identifier of the RAN slice.

The status report is used to describe the running status of the RAN slice. The status report may include, but is not limited to, at least one of the idle duration of the RAN slice and information on the number of users scheduled for the RAN slice.

S1502: The RAN slice manager sends a RAN slice deletion instruction message to the infrastructure controller according to the status report, where the RAN slice deletion instruction message includes an identifier of the RAN slice and is used to instruct the infrastructure controller to delete the RAN slice.

Specifically: if the RAN slice manager decides to delete the RAN slice according to the status report, it sends a RAN slice deletion instruction message to the infrastructure controller.

For example, if the idle duration of the RAN slice is greater than or equal to the first preset threshold, it is determined that the RAN slice needs to be deleted; otherwise, it is determined that the RAN slice does not need to be deleted. The idle duration of the RAN slice refers to the duration during which the RAN slice does not schedule any UE or provides services for any service. For example, if the information on the number of users scheduled by the RAN slice is less than or equal to the second preset threshold, it is determined that the RAN slice needs to be deleted; otherwise, it is determined that the RAN slice does not need to be deleted.

S1503-S1513: Same as S1308-S1318 above.

The following describes the method for reconfiguring RAN slices provided by the embodiments of the present invention.

Example 8

As shown in FIG. 16 , it is an interaction diagram of a method for reconfiguring RAN slices provided by an embodiment of the present invention. The method shown in FIG. 16 may include the following steps S1601-S1612:

S1601: The RAN slice manager receives a reconfiguration service request message, where the reconfiguration service request message includes service information.

Specifically, the RAN slice manager receives the reconfiguration service request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device. In addition, reference may also be made to Embodiment 1 for the related description of the information about the service.

S1602: The RAN slice manager obtains the reconfiguration information of the RAN slice corresponding to the service according to the service information.

Wherein, reference may be made to Embodiment 1 above for the relevant description of the information about the service and the correspondence between the service and the RAN slice. For example, the information of the service may include the QoS of the service, etc. When the QoS of the service changes, the configuration information of the RAN slice serving the service needs to be changed accordingly, so as to satisfy the new QoS of the service.

S1603: The RAN slice manager decides whether to reconfigure the RAN slice according to the reconfiguration information.

If yes, execute S1604; if not, end.

Specifically, if the reconfiguration information is different from the current configuration information of the RAN slice, the RAN slice needs to be reconfigured; if the reconfiguration information is the same as the current configuration information of the RAN slice, the RAN slice does not need to be reconfigured.

S1604: The RAN slice manager decides whether the RAN slice can be reconfigured according to the reconfiguration information.

If yes, execute S1605; if not, end.

Specifically, the RAN slice manager accesses the physical resource database to obtain the usage of the physical resources. If the usage of physical resources satisfies the physical resources required to reconfigure the RAN slice, the RAN slice can be created; if the usage of physical resources does not satisfy the physical resource information required to reconfigure the RAN slice, the RAN slice cannot be created. RAN slice. For a specific example, refer to the above-mentioned Embodiment 1.

S1605: The RAN slice manager sends a reconfiguration indication message to the RAN slice, the infrastructure controller and the physical layer function module respectively; the RAN slice, the infrastructure controller and the physical layer function module respectively receive the reconfiguration message sent by the RAN slice manager Indication message.

Specifically, the RAN slice manager determines to send a reconfiguration instruction message to the RAN slice, the infrastructure controller and the physical layer functional module according to the reconfiguration information of the RAN slice. The current configuration information of the RAN slice refers to the configuration information of the RAN slice when the RAN slice receives the reconfiguration instruction message.

If the reconfiguration information includes at least one of the functional configuration of the functional module used by the RAN slice and the parameter configuration of the functional module used by the RAN slice, the RAN slice manager sends a reconfiguration indication message to the RAN slice. If the reconfiguration information includes at least one of computing resources used by the RAN slice and storage resources used by the RAN slice, the RAN slice manager sends a reconfiguration indication message to the infrastructure controller. If the reconfiguration information includes radio spectrum resources, the RAN slice manager sends a reconfiguration indication message to the physical layer function module.

S1606: The RAN slice updates the current configuration information of the RAN slice to reconfiguration information according to the reconfiguration indication message.

S1607: The infrastructure controller updates the current configuration information of the RAN slice to reconfiguration information according to the reconfiguration indication message.

S1608: The physical layer function module updates the current configuration information of the wireless spectrum resource to the reconfiguration information according to the reconfiguration instruction message. It is worth noting that steps S1606, S1607 and S1608 are not in order, and the execution order of these steps can be adjusted arbitrarily.

S1609: The RAN slice, the infrastructure controller and the physical layer functional module respectively send a reconfiguration response message to the RAN slice manager; the RAN slice manager receives the reconfiguration response message sent by the RAN slice, the infrastructure controller and the physical layer functional module.

S1610: The RAN slice manager sends at least one of the following information to the terminal device: configuration information of radio spectrum resources, an identifier of each RAN slice that has been created but not deleted, and each RAN slice that has been created but not deleted The center frequency point of the radio spectrum resource and the bandwidth information of the radio spectrum resource of each RAN slice that has been created but not deleted.

The sending of the RAN slice manager to the terminal device may include, but is not limited to: the RAN slice manager sends directly to the terminal device, or the RAN slice manager sends to the terminal device through the physical layer functional module, or the RAN slice manager passes through the RAN The slice and the physical layer function module are sent, or the RAN slice manager sends it to the terminal device through the common RAN slice and the physical layer function module. The purpose of executing S1610 is to enable the terminal device to obtain the information of the RAN slice, and use the appropriate RAN slice to transmit the corresponding service.

S1611-S1613: the same as the above steps S913-S915.

Example 9

As shown in FIG. 17 , it is an interaction diagram of a method for reconfiguring RAN slices provided by an embodiment of the present invention. The method shown in FIG. 17 includes the following steps S1701-S1712:

S1701: The RAN slice manager receives a reconfiguration RAN slice request message, where the reconfiguration slice request message includes reconfiguration information of the RAN slice.

Specifically, the RAN slice manager receives a RAN slice reconfiguration request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1702-S1712: the same as the above steps S1603-S1613.

Example 10

As shown in FIG. 18 , it is an interaction diagram of a method for reconfiguring RAN slices provided by an embodiment of the present invention. The method shown in FIG. 18 includes the following steps S1801 to S1811:

S1801: The RAN slice manager receives the status report sent by the RAN slice. Wherein, the status report includes the identifier of the RAN slice, and the status report is used to describe the operation status of the RAN slice. The status report may include, but is not limited to, slice feedback delay or throughput information.

S1802: The RAN slice manager determines the reconfiguration information of the RAN slice according to the status report.

S1803: The RAN slice manager sends a reconfiguration instruction message to the RAN slice, the infrastructure controller, and the physical layer function module, where the reconfiguration instruction message is used to instruct the current configuration information to be updated to the reconfiguration information; RAN slice, infrastructure control The RAN Slice Manager and the physical layer function module receive the reconfiguration indication message sent by the RAN slice manager.

Specifically: if the RAN slice manager determines that the RAN slice needs to be reconfigured according to the status report decision, it sends a reconfiguration indication message to the RAN slice. The method may further include: if the RAN slice manager determines according to the status report decision that the RAN slice does not need to be reconfigured, ending.

For example, if the actual throughput is greater than or equal to the third preset threshold, it indicates that the resources are insufficient, and more resources need to be allocated. For example, the maximum throughput of the designed RAN slice is 100M, the current throughput of all users has reached 95M, and the number of users is increasing; in order to prevent the collapse of the RAN slice, the RAN slice is expanded to support a maximum throughput of 200M . Or, if the actual throughput is less than or equal to the fourth preset threshold, indicating that there are too many resources, some resources can be recovered or the RAN slice can be adjusted; for example, the designed maximum throughput of the RAN slice is 100M, the current throughput of all users is 1M and If it is maintained for a long time, it needs to be scaled down. In this case, the maximum throughput that can be supported is 10M, so it is decided to reconfigure the RAN slice.

S1804-S1811: the same as the above steps S1606-S1613.

The following describes the method for querying RAN slices provided by the embodiments of the present invention.

Example 11

As shown in FIG. 19 , it is an interaction diagram of a method for querying RAN slices provided by an embodiment of the present invention. The method shown in FIG. 19 includes the following steps S1901 to S1904:

S1901: The RAN slice manager receives a first query RAN slice request message, where the first query RAN slice request message includes an identifier of a RAN slice.

Specifically, the RAN slice manager may receive the first query RAN slice request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device.

S1902: The RAN slice manager determines information whether the RAN slice has been created according to the identifier of the RAN slice.

If yes, execute S1903; if not, execute S1904.

Specifically, S1902 may include: the RAN slice manager accesses the RAN slice database, and obtains the information of the RAN slice according to the identifier of the RAN slice, or the RAN slice manager accesses the storage unit of the node where it is located, and obtains the information of the RAN slice according to the identifier of the RAN slice , to obtain the information of the RAN slice; wherein, the storage unit stores the information of the RAN slice in the node where the RAN slice manager is located.

S1903: The RAN slice manager replies with information that the RAN slice exists.

S1904: The RAN slice manager replies that the RAN slice does not exist.

Example 12

As shown in FIG. 20 , it is an interaction diagram of a method for querying RAN slices provided by an embodiment of the present invention. The method shown in FIG. 20 includes the following steps S2001 to S2005:

S2001: The RAN slice manager receives a second query RAN slice request message, where the second query RAN slice request message includes service information.

Specifically, the RAN slice manager receives the second query RAN slice request message sent by the network side device or the terminal side device. Wherein, please refer to Embodiment 1 for the relevant description of the network side device and the terminal side device. The specific implementation is taken as an example for description in FIG. 20 .

S2002: The RAN slice manager acquires the identifier of the RAN slice corresponding to the service.

For the method for the RAN slice manager to obtain the identifier of the RAN slice corresponding to the service, reference may be made to the above S902.

S2003-S2005: the same as the above steps S1902-S1904.

The foregoing mainly introduces the solutions provided by the embodiments of the present invention from the perspective of the RAN slice manager. It can be understood that, in order to implement the above functions, the apparatus for managing RAN slices includes hardware structures and/or software modules corresponding to executing the functions. Those skilled in the art should easily realize that the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the modules and algorithm steps of each example described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

Figure 21a shows a network device 210a. The network device 210a may be a network device including the RAN slice manager provided above. The network device 210a may include: an obtaining module 2101a and a sending module 2102a. Optionally, the network device 210a may further include: a receiving module 2103a and an updating module 2104a.

1), when the network device 210a is used to perform the method for creating a RAN slice provided above:

In an alternative implementation, the acquisition module 2101a may perform S801a in Figure 8a and/or other processes for the techniques described herein. The sending module 2102a may perform S802a in Figure 8a and/or other processes for the techniques described herein.

In an alternative implementation, the sending module 2102a may perform S801b in Figure 8b and/or other processes for the techniques described herein.

In an alternative implementation, the acquisition module 2101a may perform S903 in FIG. 9 and/or other processes for the techniques described herein. The sending module 2102a may perform S905, S909, S911, and S913, etc. in FIG. 9, and/or other processes for the techniques described herein. The receiving module 2103a may perform S901 and S907, etc. in FIG. 9, and/or other processes for the techniques described herein. The update module 2104a may perform S912 and S915, etc. in FIG. 9, and/or other processes for the techniques described herein.

In an optional implementation manner, the obtaining module 2101a may execute S1003 in FIG. 10 . The sending module 2102a may perform S1005, S1009, S1011, and S1013, etc. in FIG. 10, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1001 and S1007, etc. in FIG. 10, and/or other processes for the techniques described herein. The update module 2104a may perform S1012 and S1015, etc. in FIG. 10, and/or other processes for the techniques described herein.

In an optional implementation manner, the obtaining module 2101a may execute S1103a in FIG. 11a. The sending module 2102a may perform S1108a, S1111a, S1113a, and S1115a, etc. in FIG. 11a, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1101a and S1107a, etc. in FIG. 11a, and/or other processes for the techniques described herein. The update module 2104a may perform S1114a and S1117a, etc. in FIG. 11a, and/or other processes for the techniques described herein.

In an optional implementation manner, the obtaining module 2101a may execute S1203a in FIG. 12a. The sending module 2102a may perform S1205a, S1208a, S1211a, S1213a, and S1215a, etc. in FIG. 12a, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1201a and S1207a, etc. in FIG. 12a, and/or other processes for the techniques described herein. The update module 2104a may perform S1214a and S1217a in Figure 12a, etc., and/or other processes for the techniques described herein.

2) When the network device 210a is used to execute the method for deleting a RAN slice provided above:

In an optional implementation, the acquisition module 2101a may perform S1302 and S1303, etc. in FIG. 13, and/or other processes for the techniques described herein. The sending module 2102a may perform S1304, S1307, S1311, S1314, and S1316, etc. in FIG. 13, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1301, S1306, S1309, and S1313, etc. in FIG. 13, and/or other processes for the techniques described herein. The update module 2104a may perform S1315 and S1318, etc. in FIG. 13, and/or other processes for the techniques described herein.

In an alternative implementation, the sending module 2102a may perform S1402, S1406, and S1409, etc. in FIG. 14, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1401, S1404, and S1408, etc. in FIG. 14, and/or other processes for the techniques described herein. The update module 2104a may perform S1410 and S1413, etc. in FIG. 14, and/or other processes for the techniques described herein.

In an optional implementation, the sending module 2102a may perform S1502, S1506, S1509, and S1511, etc. in FIG. 15, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1501, S1504, and S1508, etc. in FIG. 15, and/or other processes for the techniques described herein. The update module 2104a may execute S1510 and S1513 and the like in FIG. 15 .

3) When the network device 210a is used to perform the method for reconfiguring RAN slices provided above:

In an optional implementation manner, the obtaining module 2101a may execute S1602 in FIG. 16 . The sending module 2102a may perform S1605 and S1610-S1611, etc. in FIG. 16, and/or other processes for the techniques described herein. The update module 2104a may execute S1613 in FIG. 16 .

In an optional implementation, the sending module 2102a may perform S1704, S1709-S1710, etc. in FIG. 17, and/or other processes for the techniques described herein. The update module 2104a may perform S1712 in FIG. 17 .

In an optional implementation, the sending module 2102a may perform S1803, S1808-S1809, etc. in FIG. 18, and/or other processes for the techniques described herein. The update module 2104a may execute S1811 in FIG. 18 .

Figure 21b shows a network device 210b. The network device 210b may be a network device including the RAN slice manager provided above. The network device 210b may include: a sending module 2101b and a judging module 2102b. Optionally, the network device 210b may further include: an obtaining module 2103b. The network device 210b is configured to perform the method of querying RAN slices provided above.

In an optional implementation, the sending module 2101b may perform S1901, S1903-S1904, etc. in FIG. 19, and/or other processes for the techniques described herein. The determination module 2102b may perform S1902 in FIG. 19, etc., and/or other processes for the techniques described herein.

In an optional implementation manner, the sending module 2101b may perform S2001, S2004-S2005, etc. in FIG. 20, and/or other processes for the techniques described herein. The determination module 2102b may perform S2003 in FIG. 20, etc., and/or other processes for the techniques described herein. The acquisition module 2103b may perform S2002 in FIG. 20, etc., and/or other processes for the techniques described herein.

FIG. 22 shows a network device 220 . The network device 220 may include: a processor 2201 , a transceiver 2202 , and a memory 2203 . The network device 220 may also include a bus 2204, wherein the processor 2201, the transceiver 2202 and the memory 2203 are connected to each other through the bus 2204. Of course, the processor 2201, the transceiver 2202 and the memory 2203 may also be connected to each other through other connection manners. The memory 2203 is used to store program codes, the program codes are used to cause the processor 2201 to perform the actions performed by the RAN slice manager in any of the methods for managing RAN slices provided above, wherein the method for managing RAN slices may include At least one of methods of creating, deleting, reconfiguring and querying RAN slices. For the explanation of the relevant content in this embodiment, reference may be made to the above.

FIG. 23 shows a network device 230 . Network device 230 may be a network device that includes the infrastructure controller provided above. The network device 230 may include: a receiving module 2301 and a creating module 2302 . Optionally, the network device 230 may further include: a sending module 2303 , a deleting module 2304 and an updating module 2305 . The function of each functional module in the functional modules can be inferred according to the steps in the method embodiments provided above, and the content provided in the content of the invention above can be referred to, which is not repeated here. Repeat.

1), when the network device 230 is used to perform the method for creating a RAN slice provided above:

In an alternative implementation, the receiving module 2301 may perform S801a in FIG. 8a, etc., and/or other processes for the techniques described herein. The creation module 2302 may perform S802a in Figure 8a, etc., and/or other processes for the techniques described herein.

In an optional implementation, the receiving module 2301 may perform S801b in FIG. 8b, etc., and/or other processes for the techniques described herein. The creation module 2302 may perform S802b in Figure 8b, etc., and/or other processes for the techniques described herein.

In an optional implementation, the receiving module 2301 may perform S905, S913, etc. in FIG. 9, and/or other processes for the techniques described herein. The creation module 2302 may perform S906 in FIG. 9, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S907 in FIG. 9, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S914 in FIG. 9, etc., and/or other processes for the techniques described herein.

In an optional implementation, the receiving module 2301 may perform S1005 and S1013 in FIG. 10, etc., and/or other processes for the techniques described herein. The creation module 2302 may perform S1006 in FIG. 10, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1007 in FIG. 10, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1014 in FIG. 10 .

In an alternative implementation, the receiving module 2301 may perform S1105a, S1115a, etc. in FIG. 11a, and/or other processes for the techniques described herein. The creation module 2302 may perform S1106a in FIG. 11a, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1107a in Figure 11a, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1106a in Figure 11a, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S1205a, S1215a, etc. in FIG. 12a, and/or other processes for the techniques described herein. The creation module 2302 may perform S1206a in Figure 12a, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1207a in Figure 12a, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1216a in Figure 12a, etc., and/or other processes for the techniques described herein.

2), when the network device 230 is used to execute the method for deleting a RAN slice provided above:

In an optional implementation, the receiving module 2301 may perform S1307 and S1316, etc. in FIG. 13, and/or other processes for the techniques described herein. The sending module 2303 may perform S1309 in FIG. 13, etc., and/or other processes for the techniques described herein. The deletion module 2304 may perform S1308 in FIG. 13, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1317 in FIG. 13, etc., and/or other processes for the techniques described herein.

In an optional implementation, the receiving module 2301 may perform S1402 and S1411, etc. in FIG. 14, and/or other processes for the techniques described herein. The sending module 2303 may perform S1404 in FIG. 14, etc., and/or other processes for the techniques described herein. The deletion module 2304 may perform S1403 in 14, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1412 in FIG. 14, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S1502 and S1511, etc. in FIG. 15, and/or other processes for the techniques described herein. The sending module 2303 may perform S1504 in FIG. 15, etc., and/or other processes for the techniques described herein. The deletion module 2304 may perform S1503 in FIG. 15, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1512 in FIG. 15, etc., and/or other processes for the techniques described herein.

3) When the network device 230 is used to perform the method for reconfiguring RAN slices provided above:

In an optional implementation, the receiving module 2301 may perform S1605 in FIG. 16, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1609 in FIG. 16, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1607 in FIG. 16, etc., and/or other processes for the techniques described herein.

In an optional implementation, the receiving module 2301 may perform S1704 in FIG. 17, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1708 in FIG. 17, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1706 in FIG. 17, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S1803 and the like in FIG. 18 , and/or other processes for the techniques described herein. The sending module 2303 may perform S1807 in FIG. 18, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1805 in FIG. 18, etc., and/or other processes for the techniques described herein.

FIG. 24 shows a network device 240 . The network device 240 may include: a processor 2401 , a transceiver 2402 and a memory 2403 . The network device 220 may further include a bus 2404 ; wherein the processor 2401 , the transceiver 2402 and the memory 2403 are connected to each other through the bus 2404 . Of course, the processor 2401, the transceiver 2402 and the memory 2403 may also be connected to each other through other connection manners. The memory 2403 is used for storing program codes, and the program codes are used to cause the processor 2401 to perform the actions performed by the infrastructure controller in any of the methods for managing RAN slices provided above. The method for managing RAN slices may include at least one of the methods for creating, deleting, reconfiguring and querying RAN slices. For the explanation of the relevant content in this embodiment, reference may be made to the above.

FIG. 25 shows a terminal device 250 . The terminal device 250 may include: a sending module 2501 . Optionally, the terminal device 250 may further include: a receiving module 2502 and a using module 2503 . The function possessed by each of the functional modules can be inferred according to the steps in the method embodiments provided above, or can refer to the content provided in the content of the invention above, which will not be repeated here. .

1), when the terminal device 250 is used to execute the method for creating a RAN slice provided above:

In one possible implementation, the sending module 2501 may perform S901 in FIG. 9, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S911 in FIG. 9, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1001 in FIG. 10, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1011 in FIG. 10, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1101a in FIG. 11a, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1113a in FIG. 11a, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1201a in FIG. 12a, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1213a in Figure 12a, etc., and/or other processes for the techniques described herein.

2) When the terminal device 250 is used to execute the method for deleting a RAN slice provided above:

In one possible implementation, the sending module 2501 may perform S1301 and S1501, etc. in FIG. 13, and/or other processes for the techniques described herein. The receiving module 2502 may perform S1314 in FIG. 13, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1401 in FIG. 14, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1409 in FIG. 14, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1501 in FIG. 15, etc., and/or other processes for the techniques described herein. The receiving module 2502 may be S1509 in FIG. 15, etc., and/or other processes for the techniques described herein.

3) When the terminal device 250 is used to execute the method for reconfiguring RAN slices provided above:

In one possible implementation, the sending module 2501 may perform S1601 in FIG. 16, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1610 in FIG. 16, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1701 in FIG. 17, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1709 in FIG. 17, etc., and/or other processes for the techniques described herein.

In one possible implementation, the sending module 2501 may perform S1801 in FIG. 18, etc., and/or other processes for the techniques described herein. The receiving module 2502 may perform S1808 in 18, etc., and/or other processes for the techniques described herein.

4) When the terminal device 250 is used to execute the method for querying RAN slices provided above:

In one possible implementation, the receiving module 2502 may perform S1903-S1904, etc. in FIG. 19, and/or other processes for the techniques described herein.

In one possible implementation, the receiving module 2502 may perform S2004-S2005, etc. in FIG. 20, and/or other processes for the techniques described herein.

FIG. 26 shows a terminal device 260 . The terminal device 260 may include: a processor 2601 , a transceiver 2602 and a memory 2603 . The terminal device 260 may also include a bus 2404 ; wherein the processor 2601 , the transceiver 2602 and the memory 2603 are connected to each other through the bus 2604 . Of course, the processor 2601, the transceiver 2602 and the memory 2603 may also be connected to each other through other connection manners. The memory 2603 is used for storing program codes, and the program codes are used for causing the processor 2601 to perform the actions performed by the terminal device in any of the methods for managing RAN slices provided above. The method for managing RAN slices may include at least one of the methods for creating, deleting, reconfiguring and querying RAN slices. For the explanation of the relevant content in this embodiment, reference may be made to the above.

It should be noted that the processor 2201, the processor 2401 and the processor 2601 may be a CPU, a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or a field-based processor. A field programmable gate array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor 2201, the processor 2401 and the processor 2601 may also be a combination that realizes computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

Memory 2203, memory 2403 and memory 2603 are used to store program code for causing processor 2201, processor 2401 and processor 2601 to perform any of the methods for managing RAN slices provided above, wherein managing RAN slices The method may include at least one of the methods of creating, deleting, reconfiguring and querying RAN slices. For the explanation of the relevant content in this embodiment, reference may be made to the above.

The bus 2203, the bus 2403 and the bus 2603 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus or the like. The bus 2203, the bus 2403 and the bus 2603 can be divided into an address bus, a data bus, a control bus and the like. 22, 24 and 26 are shown with only one thick line for ease of presentation, but do not mean that there is only one bus or one type of bus.

The steps of the method or algorithm described in conjunction with the disclosure of the present invention may be implemented in a hardware manner, or may be implemented in a manner in which a processing module executes software instructions. Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read only memory (erasable). programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may reside in an ASIC.

Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the above-described device is only illustrated by the division of the above-mentioned functional modules. The function module is completed, that is, the internal structure of the device is divided into different function modules, so as to complete all or part of the functions described above. For the specific working processes of the above-described devices, devices, and modules, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus, apparatus and method may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the modules or modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically alone, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.

Claims (16)

1. A method of managing radio access network, RAN, slices, comprising:

the RAN slice manager acquires initial configuration information of the RAN slice;

the RAN slice manager sends a creation indication message to an infrastructure controller; wherein the creation indication message includes the initial configuration information, the creation indication message instructing the infrastructure controller to create the RAN slice according to the initial configuration information and default configuration information; wherein the default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

2. The method of claim 1, wherein the initial configuration information comprises information of functional modules used by the RAN slice.

3. The method in claim 1, wherein after the RAN slice manager sends a create indication message to an infrastructure controller, the method further comprises:

the RAN slice manager sends wireless spectrum resource configuration information to a physical layer function module; wherein the radio spectrum resource configuration information comprises at least one set of configuration information, the set of configuration information comprising at least one of: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource and the parameter configuration of the wireless spectrum resource.

4. The method of any of claims 1 to 3, wherein the RAN slice manager obtains initial configuration information of a RAN slice, and wherein the obtaining comprises:

the RAN slice manager receives a service creation request message; wherein the create service request message includes information of a service;

and the RAN slice manager acquires initial configuration information of the RAN slice corresponding to the service.

5. The method of any of claims 1 to 3, wherein the RAN slice manager obtains initial configuration information of a RAN slice, and wherein the obtaining comprises:

the RAN slice manager receives a request message for establishing the RAN slice; wherein the create RAN slice request message includes an identification of a RAN slice;

and the RAN slice manager acquires the initial configuration information of the RAN slice according to the identifier of the RAN slice.

6. The method according to any of claims 1 to 3, wherein after the RAN slice manager sends a create indication message to an infrastructure controller, the method further comprises:

the RAN slice manager receives a creation response message sent by the infrastructure controller;

the RAN slice manager sends an update indication message to the RAN slice; wherein the update indication message is used to indicate the RAN slice to update the current configuration information of the RAN slice.

7. A method of managing radio access network, RAN, slices, comprising:

the infrastructure controller receiving a creation indication message; wherein the creation indication message includes initial configuration information of the RAN slice;

the infrastructure controller creating the RAN slice according to the initial configuration information and default configuration information; wherein the default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

8. The method of claim 7, wherein the initial configuration information comprises information of functional modules used by the RAN slice.

9. A network device, wherein the network device is applied to a radio access network RAN slice manager, comprising:

a transceiver;

a memory to store instructions;

a processor, coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:

acquiring initial configuration information of an RAN slice;

sending, by the transceiver, a create indication message to an infrastructure controller; wherein the creation indication message includes the initial configuration information, the creation indication message instructing the infrastructure controller to create the RAN slice according to the initial configuration information and default configuration information; wherein the default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

10. The network device of claim 9, wherein the initial configuration information comprises information of functional modules used by the RAN slice.

11. The network device of claim 9, wherein the processor, when executing the instructions, further performs the steps of:

transmitting wireless spectrum resource configuration information to a physical layer function module through the transceiver; wherein the radio spectrum resource configuration information comprises at least one set of configuration information, the set of configuration information comprising at least one of: the center frequency of the wireless spectrum resource, the bandwidth of the wireless spectrum resource and the parameter configuration of the wireless spectrum resource.

12. The network device of any of claims 9 to 11,

the processor, when executing the instructions, is specifically configured to perform the steps of:

receiving, by the transceiver, a create service request message; wherein the create service request message includes information of a service;

and acquiring initial configuration information of the RAN slice corresponding to the service.

13. The network device of any of claims 9 to 11,

the processor, when executing the instructions, is specifically configured to perform the steps of:

receiving, by the transceiver, a create RAN slice request message; wherein the create RAN slice request message includes an identification of a RAN slice;

and acquiring initial configuration information of the RAN slice according to the identifier of the RAN slice.

14. The network device of any of claims 9 to 11,

the processor, when executing the instructions, is further configured to perform the steps of:

receiving, by the transceiver, a create response message sent by the infrastructure controller;

sending, by the transceiver, an update indication message to the RAN slice; wherein the update indication message is used to indicate the RAN slice to update the current configuration information of the RAN slice.

15. A network device, wherein the network device is applied to an infrastructure controller, comprising:

a transceiver;

a memory to store instructions;

a processor, coupled to the memory and the transceiver, respectively, for executing the instructions stored by the memory to perform the following steps when executing the instructions:

receiving, by the transceiver, a create indication message; wherein the creation indication message includes initial configuration information of the RAN slice;

creating the RAN slice according to the initial configuration information and default configuration information; wherein the default configuration information includes configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

16. The network device of claim 15, wherein the initial configuration information comprises information of a functional module used by the RAN slice.

Images