CN108076471B

CN108076471B - Method and device for managing RAN slices

Info

Publication number: CN108076471B
Application number: CN201611036444.6A
Authority: CN
Inventors: 李旭; 陈斯; 倪锐
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-11-14
Filing date: 2016-11-14
Publication date: 2020-09-04
Anticipated expiration: 2036-11-14
Also published as: CN108076471A; WO2018086448A1

Abstract

The invention discloses a method and a device for managing RAN slices, relates to the technical field of communication, and aims to meet the differentiated performance requirements of different services. The method comprises the following steps: the RAN slice manager acquires initial configuration information of the RAN slice; the RAN slice manager sends a creation indication message to the infrastructure controller; wherein the creation indication message includes initial configuration information for instructing the infrastructure controller to create the RAN slice according to the initial configuration information.

Description

Method and device for managing RAN slices

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for managing a Radio Access Network (RAN) slice.

Background

The wireless communication system provides communication services for businesses in the fields of education, medical treatment, enterprises, governments, internet of vehicles, internet of things and the like. The traditional wireless communication system provides services for different services by adopting a uniform pipeline architecture, and can not effectively meet the differentiated performance requirements of different services. For this reason, the future 5G network is supposed to adopt a slicing architecture to meet the differentiated performance requirements of different services.

The slice architecture of the wireless communication system mainly comprises a core network slice and a RAN slice. Currently, the focus is on the research of the related problems of the core network slice, and no technical solution for effectively managing the RAN slice is provided.

Disclosure of Invention

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

In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:

in a first aspect, a method for creating a RAN slice is provided, which may include: the RAN slice manager acquires initial configuration information of the RAN slice and then sends a creation indication message to the infrastructure controller, wherein the creation indication message comprises the initial configuration information, and the creation indication message is used for indicating the infrastructure controller to create the RAN slice according to the initial configuration information. The technical scheme provides a mode for creating the RAN slice, and the requirements of different services on differentiated performance can be met. Wherein, the initial configuration information included in the creation indication message may be all or part of configuration information required by the infrastructure controller to create the RAN slice.

In one 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 functional modules used by the RAN slice, parameter configuration of functional modules used by the RAN slice, computational resources used by the RAN slice, storage resources used by the RAN slice, and radio spectrum resources used by the RAN slice. The parameter configuration of the functional module comprises any one or more parameter configurations of any one or more functional modules.

In one possible design, the creating an indication message for instructing the infrastructure controller to create the RAN slice according to the initial configuration information may include: the create indication message is used to instruct the infrastructure controller to create the RAN slice according to the initial configuration information and the 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.

In one possible design, after the RAN slice manager sends the create indication message to the infrastructure controller, the method may further include: receiving, by the RAN slice manager, a create response message sent by the infrastructure controller, wherein the create response message is used to instruct the RAN slice manager to: the infrastructure controller has already created the RAN slice. Then, the RAN slice manager sends an update indication message to the RAN slice, wherein the update indication message is used to indicate that the RAN slice updates the current configuration information of the RAN slice. In the possible implementation manner, the infrastructure controller may create a RAN slice according to the initial configuration information and the default configuration information, and then update the current configuration information of the RAN slice by using the RAN slice, so that the RAN slice is created according to the default configuration information, resources can be quickly occupied, and the RAN slice is quickly created; and may also save the signaling overhead of creating the indication message.

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

mode 1: the RAN slice manager receives a service creation request message containing service information, and then obtains initial configuration information of a RAN slice corresponding to the service.

Mode 2: the RAN slice manager receives a create RAN slice request message containing an identification of a RAN slice, and then obtains initial configuration information of the RAN slice according to the identification of the RAN slice.

In one possible design, after the RAN slice manager sends the create indication message to the infrastructure controller, the method may further include: and the RAN slice manager sends the wireless spectrum resource configuration information to the physical layer functional module. Wherein, the radio spectrum resource configuration information may include at least one set of configuration information, and the set of configuration information may include, 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. Optionally, the parameter configuration of the radio spectrum resource may include at least one of a Transmission Time Interval (TTI), a subcarrier interval, and a Resource Block Group (RBG). For example, assume that the 1-21MHz (megahertz) spectrum is divided into the following two segments: 1-11MHZ and 11-21 MHZ; and, the spectrum 1-11MHZ employs 1ms (millisecond) TTI, the subcarrier spacing is 15KHZ, the RBG is 12 x 8 subcarriers; the frequency spectrum 11-21MHZ adopts 0.5msTTI, the subcarrier interval is 30KHZ, and the RBG is 12 x 4 subcarriers. Then, the first set of radio 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 set of radio spectrum resource configuration information is: the center frequency is 16MHZ, the bandwidth is 10MHZ, the TTI is 0.5ms, the subcarrier interval is 30KHZ, and the RBG is 48 subcarriers.

In one 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: configuration information of the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted. In a specific implementation, the RAN slice manager may send the broadcast information to the terminal device. Each RAN slice in the possible design includes the RAN slice created above.

Specifically, the RAN slice manager sends to the terminal device, and may include but is not limited to: the RAN slice manager directly sends the RAN slice manager to the terminal equipment, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the physical layer function module, or the RAN slice manager sends the RAN slice manager through the RAN slice and the physical layer function module, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the public 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, common control channels of multiple RAN slices constitute one shared RAN slice. The possible design manner enables 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.

In one possible design, the method may further include: the RAN slice manager updates a RAN slice database, which contains the identity of the RAN slice that has been created.

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

In one 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: and the RAN slice manager updates the center frequency point and bandwidth information of the idle wireless spectrum resources and/or updates the configuration information of the used wireless spectrum resources.

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

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

In one possible design, the infrastructure controller creating the RAN slice from the initial configuration information 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 configuration information other than the initial configuration information required by the infrastructure controller to configure the RAN slice.

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

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

In a fourth aspect, a method for creating a RAN slice is provided, including: the terminal equipment sends a service creating request message to the RAN slice manager; the service creating request message comprises service information and is used for requesting to create an RAN slice corresponding to the service; or the terminal equipment sends a RAN slice creation request message to the RAN slice manager; 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 RAN slice creation.

In one possible design, the method may further include: the terminal equipment receives at least one of the following information sent by the RAN slice manager: configuration information of radio spectrum resources, identification of each created and undeleted RAN slice, a center frequency point of the radio spectrum resources of each created and undeleted RAN slice, and bandwidth information of the radio spectrum resources of each created and undeleted RAN slice; the terminal device uses the wireless spectrum resource according to the at least one type of information.

In a fifth aspect, a network device is provided, which may comprise the RAN slice manager described above. The network device may include: a transceiver, a memory, and a processor. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: acquiring initial configuration information of an RAN slice; sending, by the transceiver, a create indication message to the infrastructure controller; wherein the creation indication message includes initial configuration information, the creation indication message for instructing the infrastructure controller to create the RAN slice according to the initial configuration information.

In one possible design, the create indication message for instructing the infrastructure controller to create the RAN slice according to the initial configuration information includes: creating an indication message for instructing the infrastructure controller to create a RAN slice according to the initial configuration information and the 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.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: transmitting wireless spectrum resource configuration information to a physical layer function module through a transceiver; wherein the radio spectrum resource configuration information comprises at least one group of configuration information, and the group of configuration information comprises 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 one possible design, the parameter configuration of the radio spectrum resources includes at least one of a transmission time interval TTI, a subcarrier spacing, and a resource block group RBG.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: transmitting, by the transceiver, to the terminal device at least one of: configuration information of the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: receiving, by a transceiver, a create service request message; wherein, the message for requesting service creation comprises information of service; then, initial configuration information of the RAN slice corresponding to the service is acquired.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: receiving, by a transceiver, a create RAN slice request message; wherein the RAN slice creation request message comprises an identifier of the RAN slice; then, initial configuration information of the RAN slice is obtained according to the identifier of the RAN slice.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: receiving, by a transceiver, a create response message sent by an infrastructure controller; sending an update indication message to the RAN slice through the transceiver; wherein, the update indication message is used for indicating the RAN slice to update the current configuration information of the RAN slice.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: updating an RAN slice database and radio spectrum resource information; wherein the RAN slice database contains the identity of the created RAN slice.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: transmitting, by the transceiver, a second update indication message to the infrastructure controller; wherein the second update indication message is for instructing the infrastructure controller to update at least one of the storage resource information and the computing resource information.

In a sixth aspect, a network device is provided, comprising: a transceiver, a memory, and a processor. The network device may include the infrastructure controller described above. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: receiving, by a transceiver, a creation indication message; wherein the creation indication message includes initial configuration information of the RAN slice; the RAN slice is created from the initial configuration information.

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

In one possible design, the processor, when executing the instructions, is specifically configured to perform the steps of: establishing a RAN slice according to the initial configuration information and the 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.

In a seventh aspect, a terminal device is provided, including: a transceiver, a memory, and a processor. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: sending a create service request message to a RAN slice manager through a transceiver; the service creating request message comprises service information and is used for requesting to create an RAN slice corresponding to the service; or, sending a create RAN slice request message to the RAN slice manager through the transceiver; 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 RAN slice creation.

In one possible design, the processor, when executing the instructions, is further configured to: receiving, by the transceiver, at least one of the following information sent by the RAN slice manager: configuration information of radio spectrum resources, identification of each created and undeleted RAN slice, a center frequency point of the radio spectrum resources of each created and undeleted RAN slice, and bandwidth information of the radio spectrum resources of each created and undeleted RAN slice; the terminal device uses the wireless spectrum resource according to the at least one type of information.

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

In one possible design, the RAN slice manager obtaining the identity of the RAN slice may include any of the following:

mode 1: the RAN slice manager receives a service deletion request message containing service information, and then acquires an identifier of a RAN slice corresponding to the service.

Mode 2: the RAN slice manager receives a delete RAN slice request message containing an identification of the RAN slice.

Mode 3: the RAN slice manager receives a status report which is sent by the RAN slice and contains the identification of the RAN slice, wherein the status report is used for describing the operation condition of the RAN slice.

In one possible design, after the RAN slice manager sends the delete RAN slice indication message to the infrastructure controller, the method may further include: and the RAN slice manager sends the wireless 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 function 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 the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted. In a specific implementation, the RAN slice manager may send the broadcast information to the terminal device.

In one possible design, the method may further include: the RAN slice manager updates the RAN slice database.

In one possible design, the method may further include: the RAN slice manager sends an update indication message to the infrastructure controller, wherein the update indication message is used for indicating the infrastructure controller to update at least one of the storage resource information and the computing resource information in the physical resource database.

In one 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 that may include the RAN slice manager described above. The network device may include: a transceiver, a memory, and a processor. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: an identity of a RAN slice is obtained and a delete RAN slice indication message is sent to the infrastructure controller via the transceiver, wherein the delete RAN slice indication message includes the identity of the RAN slice for instructing the infrastructure controller to delete the RAN slice.

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

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: a delete RAN slice request message containing an identification of the RAN slice is received by the transceiver.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: and receiving, by a transceiver, a status report containing an identification of the RAN slice sent by a RAN slice, wherein the status report is used for describing an operating condition of the RAN slice.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: and sending the wireless spectrum resource configuration information to the physical layer functional module through the transceiver.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: the RAN slice database is updated.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: sending, by the transceiver, an update indication message to the infrastructure controller, wherein the update indication message is used to instruct the infrastructure controller to update at least one of the storage resource information and the computing resource information in the physical resource database.

In one possible design, the processor, when executing the instructions, is further configured to perform the steps of: the radio spectrum resource information is updated.

In a tenth aspect, a method of reconfiguring a RAN slice is provided, which may include: the RAN slice manager acquires reconfiguration information of the RAN slice, and then sends a reconfiguration indication message to at least one of the RAN slice, the infrastructure controller and the physical layer functional module, wherein the reconfiguration indication message is used for indicating that current configuration information is updated into reconfiguration information. The technical scheme provides a mode for reconfiguring RAN slices, and the requirements of different services on differentiated performance can be met.

In one possible design, the RAN slice manager acquiring the reconfiguration information of the RAN slice may include any one of the following manners:

mode 1: receiving a reconfiguration service request message by a RAN slice manager, wherein the reconfiguration service request message comprises service information; then, the RAN slice manager acquires reconfiguration information of the RAN slice corresponding to the service.

Mode 2: receiving a RAN slice request message by a RAN slice manager, wherein the reconfiguration slice request message comprises reconfiguration information of a RAN slice; the RAN slice manager then obtains reconfiguration information for the RAN slice.

Mode 3: the RAN slice manager receives a status report sent by the RAN slice, wherein the status report is used for describing the operation condition of the RAN slice, and then the RAN slice manager determines the reconfiguration information of the RAN slice according to the status report.

In one 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: configuration information of the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted. In a specific implementation, the RAN slice manager may send the broadcast information to the terminal device.

In an eleventh aspect, a network device is provided that may include the RAN slice manager described above. The network device may include: a transceiver, a memory, and a processor. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: obtaining reconfiguration information of a RAN slice, and then sending a reconfiguration indication message to at least one of the RAN slice, an infrastructure controller and a physical layer function module through a transceiver, wherein the reconfiguration indication message is used for indicating that current configuration information is updated to reconfiguration information.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: receiving a reconfiguration service request message through a transceiver, wherein the reconfiguration service request message comprises information of a service; then, obtaining the reconfiguration information of the RAN slice corresponding to the service.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: receiving, by a transceiver, a RAN slice request message, wherein the reconfiguration slice request message includes reconfiguration information of a RAN slice; then, reconfiguration information of the RAN slice is acquired.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: receiving, by a transceiver, a status report sent by a RAN slice, wherein the status report is used for describing an operating condition of the RAN slice, and then determining reconfiguration information of the RAN slice according to the status report.

In a twelfth aspect, a method of querying a RAN slice is provided, which may include: the RAN slice manager acquires the identifier of the RAN slice, and if the RAN slice is found through inquiry, the RAN slice manager replies the information of the RAN slice; or if the RAN slice is not created, replying that the information of the RAN slice does not exist.

mode 1: the RAN slice manager receives a first query RAN slice request message containing an identification of a RAN slice.

Mode 2: the RAN slice manager receives a second query RAN slice request message containing information of the service, and then acquires an identifier of a RAN slice corresponding to the service.

In a thirteenth aspect, a network device is provided, which may comprise the RAN slice manager described above. The network device may include: a transceiver, a memory, and a processor. Wherein the memory is used for storing instructions. The processor is connected with the memory and the transceiver respectively and is used for executing the instructions stored in the memory so as to execute the following steps when the instructions are executed: acquiring an identifier of a RAN slice, and if the RAN slice is found, replying information of the RAN slice; or if the RAN slice is not created, replying that the information of the RAN slice does not exist.

In one possible design, the processor is specifically configured to perform the following steps when executing the instructions: a first query RAN slice request message containing an identification of a RAN slice is received by a transceiver.

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

In a fourteenth aspect, a system for managing RAN slices is provided that may include a RAN slice manager and an infrastructure controller. The RAN slice manager is used for acquiring initial configuration information of a RAN slice and sending a creation indication message to the infrastructure controller, wherein the creation indication message comprises the initial configuration information. And an infrastructure controller for receiving the creation indication message and creating the RAN slice according to the initial configuration information.

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

In one possible design, the infrastructure controller may be specifically configured to: the RAN slice is created according to initial configuration information and default configuration information, wherein the default configuration information includes configuration information other than the initial configuration information required by an infrastructure controller to configure the RAN slice.

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

In one possible design, the RAN slice manager may be specifically configured to: receiving a service creation request message containing service information; then, the initial configuration information of the RAN slice corresponding to the service is acquired.

In one possible design, the RAN slice manager may be specifically configured to: receiving a create RAN slice request message containing an identifier of a RAN slice; then, initial configuration information of the RAN slice is acquired.

In one possible design, the system may also include a physical layer functional module. The RAN slice manager may also be configured to send radio spectrum resource configuration information to the physical layer function module; wherein the radio spectrum resource configuration information may include at least one set of configuration information, and the set of configuration information may include 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. And the physical layer functional module is used for using the wireless spectrum resources according to the wireless spectrum resource configuration information.

In one 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 the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted.

In one possible design, the system may further include: a RAN slice database, which contains an identification of the created RAN slice. The RAN slice manager may also be configured to update the RAN slice database.

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

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

For explanation of relevant matters in any one of the methods provided by the second to fourteenth aspects, reference may be made to the first aspect described above.

It is to be understood that any one of the above-mentioned apparatuses or systems is configured to perform the above-mentioned method, and therefore, the beneficial effects achieved by the above-mentioned apparatus or system can refer to the beneficial effects in the above-mentioned corresponding method for managing RAN slices, which are not described herein again.

Drawings

Fig. 1 is a logic architecture diagram applicable to the technical solution provided by the embodiment of the present invention;

FIG. 2 is a diagram illustrating a physical architecture according to an embodiment of the present invention;

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

FIG. 4 is a diagram illustrating another physical architecture according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating another physical architecture according to an embodiment of the present invention;

FIG. 6 is a diagram illustrating another physical architecture according to an embodiment of the present invention;

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

fig. 8a is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention;

fig. 8b is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention;

fig. 9 is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 10 is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 11a is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 11b is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 12a is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 12b is an interaction diagram of another method for creating a RAN slice according to an embodiment of the present invention;

fig. 13 is an interaction diagram of a method for deleting a RAN slice according to an embodiment of the present invention;

fig. 14 is an interaction diagram of another method for deleting a RAN slice according to an embodiment of the present invention;

fig. 15 is an interaction diagram of another method for deleting a RAN slice according to an embodiment of the present invention;

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

fig. 17 is an interaction diagram of another method for reconfiguring a RAN slice according to an embodiment of the present invention;

fig. 18 is an interaction diagram of another method for reconfiguring a RAN slice according to an embodiment of the present invention;

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

fig. 20 is an interaction diagram of another method for querying a RAN slice according to 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 according to 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 Description

A RAN slice refers to a combination of access network functional modules that provide the required communication services and network capabilities, and the resources required to operate these access network functional modules. The access network functional module may include, but is not limited to, at least one of the following information: the device comprises a message caching function module, a packet unpacking function module, a reordering function module, an encryption and decryption function module, a multi-user multiplexing function module, a power distribution function module, a multi-antenna management function module, a priority management function module, a mixer function (namely, center frequency shifting) module, a filter function module and the like. Resources refer primarily to physical resources, which may include, but are not limited to, at least one of the following: computing resources, storage resources, wireless spectrum resources. Wherein the wireless-spectrum resources may include at least one of the following information: a center frequency of the radio spectrum resource, a radio spectrum bandwidth of the radio spectrum resource, a TTI, a subcarrier spacing, an RBG, and the like. Optionally, when the RAN slice is used, the functional module of the RAN slice may be configured, and specifically, the configuration may include at least one of the following configurations: and function configuration of the function module and parameter configuration of the function module. The functional configuration of the functional module may include, but is not limited to, turning on or turning off the functional module, and the like, for example, the functional configuration of the encryption/decryption functional module may include turning on 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 which encryption/decryption algorithm is configured to be used.

In order to meet the differentiated performance requirements of different services, RAN slices (hereinafter referred to as "service-corresponding RAN slices") that provide services for different 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/decryption functional module, and the TTI is 1ms, and the functional module of the RAN slice corresponding to service 2 may not include an encryption/decryption functional module, and the TTI is 0.5 ms.

Fig. 1 is a schematic diagram of a logic architecture to which the technical solution provided by the embodiment of the present invention is applied. The logical architecture diagram shown in fig. 1 includes a RAN slice manager 11, an infrastructure controller 12, and a RAN slice collection 13. The RAN slice manager 11 is a decision unit for managing RAN slices, and managing RAN slices may include, but is not limited to, at least one of the following: create, delete, reconfigure, or query RAN slices, etc. Infrastructure controller 12 is an execution unit that manages RAN slices. RAN slice set 13 is a set of RAN slices that have been created and not deleted. RAN slice set 13 may include one or more RAN slices.

Optionally, the logic 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 function module 16. The physical resource database 14 is used for storing the use condition of the physical resource; for example, the physical resource database 14 may be used to store information of free physical resources. The information of the physical resources may include, but is not limited to, information of resources such as computing resources, storage resources, and wireless spectrum resources. The wireless spectrum resources may include, but are not limited to, a center frequency, a wireless spectrum bandwidth, and a parameter configuration of the wireless spectrum resources. The parameter configuration of the wireless spectrum resources may include, but is not limited to, at least one of the following information: TTI, subcarrier spacing, RBG, etc. The RAN slice database 15 is used to store information of RAN slices; for example, the RAN slice database 15 may be used to store information of RAN slices that have been created; optionally, information of the non-created RAN slice may also be stored, which may be referred to below.

The physical resource database 14 may be a public database or may be a private database of the RAN slice manager 11 or a private database of the infrastructure controller 12. The physical resource database 14 is a public database, and can be understood as: the database is shared by a plurality of RAN slice managers 11, or a plurality of infrastructure controllers 12, or one RAN slice manager 11 and one or more infrastructure controllers 12, or one or more RAN slice managers 11 and one infrastructure controller 12, or a plurality of RAN slice managers 11 and a plurality of 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 may be a public database or may be a private database of the RAN slice manager 11. Among these, the RAN slice database 15 is used as a common database, and can be understood as: multiple RAN slice managers 11 may share the database. The RAN slice database 15 serves as a private database of the RAN slice manager 11, and can be understood as: 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, or may exist only one, or may not exist at all. When not present, the corresponding RAN slice or physical resource information may be stored inside the RAN slice manager 11 or the infrastructure controller 12, and the RAN slice manager 11 or the infrastructure controller 12 may use and update the RAN slice or physical resource information stored therein.

The logical architecture shown in fig. 1 may be applied in a variety of physical architectures. This is illustrated below by means of several examples.

Fig. 2 shows a schematic diagram of a physical architecture, in particular an independent base station physical architecture. The physical architecture shown in fig. 2 may include a plurality of base stations 21, and a RAN slice manager 11 may be disposed 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 at each base station 21 as an execution unit in the base station that manages RAN slices. A RAN slice set 13 may be deployed on each base station 21, where the RAN slice set 13 is a set of RAN slices that have been created and not deleted in the base station. Optionally, a physical resource database 14 may be deployed on each base station 21, and is used to store the usage condition of the physical resource of the base station. Optionally, a RAN slice database 15 may be disposed on each base station 21 for storing information of RAN slices of the base station. A physical layer function module 16 may be deployed at each base station 21.

Fig. 3 shows a schematic diagram of another physical architecture, in particular a clustered base station physical architecture. The physical architecture shown in fig. 3 may include one or more clusters, each of which may include one clusterhead base station 31, and one or more non-clusterhead base stations 32. In the physical architecture shown in fig. 3: a RAN slice manager 11 may be deployed at any base station in a cluster, and is used 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. Fig. 3 illustrates an example of deploying the RAN slice manager 11 on the cluster head base station 31. An infrastructure controller 12 may be deployed at each base station in a cluster as an execution unit in the base station that manages RAN slices. A RAN slice set 13 may be deployed on each base station in a cluster, where the RAN slice set 13 is a set of RAN slices that have been created and not deleted in the base station. Optionally, a physical resource database 14 may be deployed on each base station, and is used to store the use condition of the information of the physical resources of the base station. Alternatively, the physical resource database 14 may be deployed on any one of the base stations for storing the usage of the cluster, for example, the physical resource database 14 is deployed on the cluster head base station 31. Optionally, a RAN slice database 15 may be deployed on each base station, and is used to store information of RAN slices of the base station; alternatively, a RAN slice database 15 may be deployed at any one of the base stations for storing information of RAN slices of the cluster, for example, the RAN slice database 15 is deployed at the cluster head base station 31. A physical layer function module 16 may be deployed at each base station.

Fig. 4 shows a schematic diagram of another physical architecture, which is embodied as 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. The centralized control unit 41 may be, but is not limited to, a conventional core network. In the physical architecture shown in fig. 4: a RAN slice manager 11 may be disposed on each base station 42 to serve as a decision 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 for managing the RAN slice as a decision unit of the present centralized control unit, for example, the RAN slice manager 11 is deployed on the centralized control unit 41. Fig. 4 illustrates an example of deploying the RAN slice manager 11 on the centralized control unit 41. An infrastructure controller 12 may be deployed at each base station 42 as an execution unit in the base station that manages RAN slices. A RAN slice set 13 may be deployed on each base station 42, where the RAN slice set 13 is a set of RAN slices that have been created and not deleted in the base station. Optionally, a physical resource database 14 may be disposed on each base station 42 for storing the usage condition of the information of the physical resources of the base station. Alternatively, the centralized control unit 41 or any one of the base stations 42 may be deployed with a physical resource database 14 for storing the usage of the physical resources of all the base stations managed by the centralized control unit, for example, the physical resource database 14 is deployed on the centralized control unit 41. Optionally, a RAN slice database 15 may be disposed on each base station 42, and is used for storing information of RAN slices of the base station; alternatively, the RAN slice database 15 may be deployed on the centralized control unit 41 or any one of the base stations 42 for storing information of RAN slices of the own base station, e.g., the RAN slice database 15 is deployed on the centralized control unit 41. A physical layer function module 16 may be deployed at each base station.

Fig. 5 shows a schematic diagram of another physical architecture, which is specifically a physical architecture of an independent BBU in a C-RAN, where the C-RAN is an english abbreviation of a cloud/centralized radio access network (cloud radio access network or centralized radio access network), and the BBU is an english abbreviation of an indoor baseband processing unit (building base unit). The physical architecture shown in fig. 5 may include: one or more BBUs 51 and one or more Radio Remote Units (RRUs) 52 connected to each BBU 51. A RAN slice manager 11 may be disposed on each BBU51, and is used as a decision unit for managing RAN slices in the present BBU and the RRUs connected to the present BBU. If the full functionality of the RAN slice is on the BBU51, then an infrastructure controller 12 may be deployed on each BBU51 that has the functionality of the RAN slice, for use as an execution unit in the present BBU to manage the RAN slices. Alternatively, if part of the functionality of the RAN slice is on the BBU51 and part of the functionality is on the RRU52, then the infrastructure controller 12 may be deployed on both the BBU51 and the RRU52 that have the functionality of the RAN slice as an execution unit to manage the RAN slice. A RAN slice set 13 may be disposed on each BBU51, where the RAN slice set 13 is a set of RAN slices that have been created and have not been deleted in the BBU. Alternatively, a RAN slice set 13 may be deployed on each RRU52, where the RAN slice set is a set of RAN slices that have been created and have not been deleted in the RRU. Alternatively, one portion of the RAN slice set can be deployed on each BBU51 and another portion of the RAN slice set can be deployed on each RRU 52. Optionally, a physical resource database 14 may be disposed on each BBU51, and is used to store the use condition of the BBU and the information of the RRU physical resources connected to the BBU. Optionally, a RAN slice database 15 may be disposed on each BBU51, and is used to store information of the BBU and the RAN slices of the RRUs connected to the BBU. A physical layer function module 16 may be deployed on each RRU 52.

Fig. 6 shows a schematic diagram of another physical architecture, in particular a clustered BBU in C-RAN physical architecture. The physical architecture shown in fig. 6 may include one or more clusters, each cluster may include one clusterhead BBU61 and one or more RRUs 62 connected to the clusterhead BBU61, as well as one or more non-clusterhead BBUs 63 and one or more RRUs 62 connected to the non-clusterhead BBU 63. In the physical architecture shown in fig. 6: any BBU in a cluster, including the cluster head BBU61 or the non-cluster head BBU63, may have a RAN slice manager 11 deployed thereon, for use as a decision unit for managing RAN slices in the cluster, for example, the RAN slice manager 11 is deployed on the cluster head BBU61, where fig. 6 illustrates an example in which the RAN slice manager 11 is deployed on the cluster head BBU 61. For the deployment 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 of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in fig. 5, which is not described herein again.

Optionally, a physical resource database 14 may be disposed on each BBU, and is used to store the use condition of the information of the physical resources of the BBU; alternatively, the physical resource database 14 may be deployed on any BBU, and is used to store the use condition of the BBU in the cluster and the information of the physical resources in the RRUs to which the BBU in the cluster is connected, for example, the physical resource database 14 is deployed on the cluster head BBU 61. Optionally, a RAN slice database 15 may be disposed on each BBU, and is configured to store information of a RAN slice of the BBU; alternatively, a RAN slice database 15 may be disposed on any BBU, and is used to store information of the cluster BBU and the RAN slices in the RRUs connected to the cluster BBU, for example, the RAN slice database is disposed on the cluster head BBU 61. A physical layer function module 16 may be deployed on each RRU 62.

Fig. 7 shows a schematic diagram of another physical architecture, in particular a centralized physical architecture in the C-RAN. The physical architecture shown in fig. 7 can include a centralized control unit 71, one or more BBUs 72 connected thereto, and one or more RRUs 73 connected to each BBU 72; the centralized control unit 71 may be, but is not limited to, a conventional core network. In the physical architecture shown in fig. 7: a RAN slice manager 11 may be disposed on each BBU72, and is used as a decision unit for managing RAN slices in the BBU; alternatively, a RAN slice manager 11 may be deployed on the centralized control unit 71 or any of the BBUs 72 as a decision unit for the centralized control unit to manage RAN slices, for example, the RAN slice manager 11 is deployed on the centralized control unit 71, where fig. 7 illustrates an example of deploying the RAN slice manager 11 on the centralized control unit 71. For the deployment 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 of the infrastructure controller 12 and the RAN slice set 13 in the architecture shown in fig. 5, which is not described herein again. Optionally, a physical resource database 14 may be disposed on each BBU72, and is used to store the use condition of the information of the physical resources of the BBU; alternatively, the physical resource database 14 may be disposed on the centralized control unit 71 or any of the BBUs 72, for storing the usage of information of physical resources in all BBUs managed by the centralized control unit 71 and RRUs connected to the BBUs, for example, the physical resource database 14 is disposed on the centralized control unit 71. Optionally, a RAN slice database 15 may be disposed on each BBU72, and is used to store information of RAN slices of the BBU; alternatively, the RAN slice database 15 may be deployed on the centralized control unit 71 or any of the BBUs 72 for storing information of RAN slices in all BBUs and RRUs connected to BBUs managed by the centralized control unit, e.g., the RAN slice database 15 is deployed on the centralized control unit 71. A physical layer function module 16 may be deployed on each RRU 73.

RAN slices are briefly introduced below:

1. RAN slice and configuration information of RAN slice

The configuration information of different RAN slices is different and the identity of a RAN slice may be used to label one RAN slice. The same RAN slice may have one or more kinds of configuration information, but one RAN slice has only one kind of configuration information at the same time. It should be noted that the reason for having multiple configuration information for one RAN slice may include, but is not limited to, reconfiguring one RAN slice; that is, before and after reconfiguration of one RAN slice, configuration information of the RAN slice is different. For example, the correspondence between the RAN slice and the 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 configuration information of RAN slice 1 is similarly explained, and is not described in detail here.

2. Configuration information for RAN slices

The configuration information of the RAN slice may include: functional module information, physical resource information, and the like. The different configuration information may include configuration information of different RAN slices and different configuration information of the same RAN slice. Specifically, but not limited to, at least one of information of the differentiated functional module and the differentiated radio spectrum resource may be included. The information of the differentiated functional module may include, but is not limited to, at least one of the following information: the composition information of the differentiated functional module, if yes, whether the functional module has an encryption and decryption functional module; the function configuration of the differentiated function module, if yes, the encryption and decryption functions are started; and configuring parameters of the differentiated functional modules, such as which encryption and decryption algorithm is used by the encryption and decryption function. The differentiated physical resource information may include, but is not limited to, at least one of the following: differentiated computing resources, differentiated storage resources, differentiated radio spectrum resources, and the like.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship. The terms "first" and "second" are used herein for the purpose of distinguishing different objects more clearly, and are not limited to any other. "plurality" herein means two or more. As used herein, a "device" may be understood as an access network device that may include, but is not limited to, the physical architecture shown in any of the above-described figures 2-7.

It should be noted that, all the following description is given by taking the application of the technical solution provided by the embodiment of the present invention to the logical architecture diagram shown in fig. 1 as an example, and a person skilled in the art should be able to map the technical solution provided by the embodiment of the present invention to a corresponding physical architecture according to the content described below, which is not described below.

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

s801 a: the RAN slice manager obtains initial configuration information of the RAN slice.

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

Optionally, the initial configuration information of the RAN slice may include information of a functional module used by the RAN slice. Further optionally, at least one of the following information may be included: a functional configuration of a functional module used by the RAN slice, a parameter configuration of a functional module used by the RAN slice, information of computational resources used by the RAN slice, information of storage resources used by the RAN slice, and information of radio spectrum resources used by the RAN slice. The parameter configuration of the functional module comprises any one or more parameter configurations of any one or more functional modules in the functional module. The wireless spectrum resources include, but are 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. Wherein the parameter configuration of the radio spectrum resource comprises at least one of TTI, subcarrier spacing and RBG.

S802 a: the RAN slice manager sends a create indication message to the infrastructure controller, which receives the create indication message. Wherein the creation indication message may include initial configuration information, the creation indication message for instructing the infrastructure controller to create the 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 acquired in S801 a.

S803 a: the infrastructure controller creates the RAN slice according to the initial configuration information in the create indication message.

Create a RAN slice, which can be understood as: and distributing physical resources for the RAN slice and starting a functional module according to the configuration information. These functional modules are run using the allocated physical resources.

In particular implementations, the RAN slice may be created by any of the following:

mode 1: all configuration information required for the infrastructure controller to create the RAN slice may be included in the creation indication message, in which case the infrastructure controller creates the RAN slice according to the all configuration information. Wherein the entire configuration information may be the initial configuration information. This approach can be understood as: the required RAN slice is created directly. Specifically, the following example 1 or example 2 may be referred to.

Mode 2: part of configuration information required by the infrastructure controller to create the RAN slice may be included in the creation indication message, and in this case, the infrastructure controller may create the RAN slice according to the part of configuration information and the default configuration information. The part of the configuration information may be a part of the initial configuration information. The default configuration information herein may include configuration information other than the portion of configuration information required by the infrastructure controller to create the RAN slice. This possible design can be understood as: a semi-generic RAN slice is created. Subsequently, the current configuration information of the semi-generic RAN slice can be reconfigured, so as to provide differentiated performance requirements for different services. Specifically, the following example 3 or example 4 may be referred to.

The embodiment of the invention provides a method for creating RAN slices, which is characterized in that the created RAN slices are different by setting initial configuration information of different RAN slices, so that different services can be mapped onto different RAN slices according to the performance requirements of the different services during specific implementation, and the differentiated performance requirements of the different services are met.

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

s801 b: the RAN slice manager sends a create indication message to the infrastructure controller, which receives the create indication message.

S802 b: the infrastructure controller creates the RAN slice according to the default configuration information.

In this embodiment, the creation indication message may not contain any configuration information required to create the RAN slice, in which case the infrastructure controller may create the RAN slice according to default configuration information. The default configuration information here may include all configuration information required by the infrastructure controller to create the RAN slice. This alternative design can be understood as: a generic RAN slice is created. Subsequently, the current configuration information of the general RAN slice can be reconfigured, so as to provide differentiated performance requirements for different services. Specifically, the following examples 3 to 6 can be referred to.

Example 1

Fig. 9 is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention. The method shown in fig. 9 may include the following steps S901 to S915:

s901: receiving a service creation request message by the RAN slice manager; wherein the create service request message includes information of the service.

Specifically, the method comprises the following steps: and the RAN slice manager receives a service creation request message sent by network side equipment or terminal side equipment. The network side device is also called a northbound device, and the terminal side device is also called a 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 element, etc. By way of example, the service provider server may include, but is not limited to, any of the following: hundredth server, Tencent server, etc. The network operator server may include, but is not limited to, any of the following: mobile server, unicom server, etc. The core network elements may include, but are not limited to, any of the following: home Subscriber Server (HSS), Mobility Management Entity (MME), Gateway (GW), Policy and Charging Rules Function (PCRF), and other network elements that may appear in the future. The terminal side devices may include, but are not limited to, any of the following: mobile phones, computers, Virtual Reality (VR) helmets, internet of things devices, cameras, and the like.

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

(identity) or quality of service (QoS) requirements of the service. The QoS requirement may include, but is not limited to, at least one of the following information: time delay, throughput, packet loss rate, etc. If the services are differentiated according to the service types and the operators/service providers, the information of the services may include: the ID of the service and the ID of the operator/service provider.

S902: and the RAN slice manager judges whether the RAN slice corresponding to the service needs to be created or not according to the service information.

If not, the process is ended. If yes, go to S903.

In a specific implementation, if the determination result in S902 is "no", which indicates that the RAN slice has been created, the RAN slice manager maps the service to the RAN slice corresponding to the service, and subsequently, the RAN slice is used to provide a service for the service.

S902 may include, but is not limited to, the following two implementations:

the first method is as follows: the RAN slice manager determines whether a RAN slice corresponding to the service has been created by accessing the RAN slice database. If so, determining that the RAN slice does not need to be created, and if not, determining that the RAN slice needs to be created.

The second method comprises the following steps: the RAN slice manager accesses the RAN slice database to determine whether the originator (e.g., operator/service provider) that created the RAN slice has the right to create the RAN slice corresponding to the service. And if the RAN slice corresponding to the service is not created, determining that the RAN slice needs to be created, otherwise, not creating the RAN slice. It is noted that, it may also be determined whether the RAN slice corresponding to the service is already created, and if not, then it is determined whether an initiator that creates the RAN slice has an authority to create the RAN slice corresponding to the service, and if so, it is determined that the RAN slice needs to be created, otherwise, the RAN slice does not need to be created.

The following describes an exemplary correspondence between a service and a RAN slice according to different service differentiation methods:

if different services are distinguished according to the service types, the following steps are carried out: 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

Information of a service	Identification of RAN slices
		ID of video service	RAN slice	1
ID of voice service	RAN slice				1
		ID of short message service	RAN slice 2
ID of game service	RAN slice 3

If different services are distinguished according to the service types and operators/service providers, then: 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 services provided by the same operator/service provider of the same type are the same. The RAN slices corresponding to services provided by different types of different operators/providers may be the same or different, and the services provided by the same operator/provider of different types may be the same or different. An example is shown in table 3:

TABLE 3

The RAN slice database may store therein an identification of a RAN slice that has been created, and optionally, an identification of a RAN slice that has not been created. These two cases are exemplified below:

case 1: the RAN slice database stores the identities of the RAN slices that have been created and the identities of the RAN slices that have not been created. In this case, the RAN slice database may store a correspondence between: information of a service, an ID of a RAN slice, slice initial configuration information of a RAN, information whether a RAN slice has been created.

If different services are differentiated according to service types, a RAN slice database may be as shown in table 4:

TABLE 4

If different services are differentiated according to service type and operator/service provider, a RAN slice database may be as shown in table 5:

TABLE 5

Where "1" in table 4 and table 5 indicates that a RAN slice has been created, and "0" indicates that a RAN slice has not been created. In a specific implementation, the information indicating whether the RAN slice has been created may also be represented 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 therein the identities of RAN slices that have been created and does not store the identities of RAN slices that have not been created. This situation applies generally to differentiating different services by service type and operator/service provider. In this case, the RAN slice database may store a correspondence between: information of the service (including the ID of the service and the identity of the operator/facilitator), the ID of the RAN slice, the initial configuration confidence of the RAN slice. Two examples of this are listed below:

example 1: the ID of the operator/facilitator to which the RAN slice corresponds is not saved until the RAN slice is not created. In this example, if no RAN slice has been created in the system, a RAN slice database may be as shown in table 6:

TABLE 6

Based on table 6, if a partial RAN slice has been created in the system, a RAN slice database may be as shown in table 7:

TABLE 7

Example 2: before the RAN slice is not created, the ID of the operator/service provider corresponding to the RAN slice is saved. In this example, if no RAN slice has been created in the system, a RAN slice database may be as shown in table 8:

TABLE 8

It should be noted that in a scenario where an operator/service provider needs to pay for a RAN slice to have a right to use the RAN slice, optionally, the RAN slice database may store an ID of the operator/service provider that is paid for, and not store an ID of an operator/service provider that is not paid for. Wherein, the operator/service provider who pays refers to the operator/service provider who purchases the usage right of the RAN slice; an operator/facilitator who does not pay a fee refers to an operator/facilitator who does not purchase usage rights for the RAN slice. For example, the ID of each operator/service provider in table 8 is the ID of the operator/service provider who purchased the usage right of the corresponding RAN slice, such as Tencent and Ali who purchased the usage right of the RAN slice corresponding to the video service.

Based on table 8, if a partial RAN slice has been created in the system, a RAN slice database may be as shown in table 9:

TABLE 9

It should be noted that, in a scenario where the operator/service provider needs to pay for the RAN slice to have the right to use the RAN slice, S902 may be implemented in the above-mentioned manner two specifically.

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

Among them, S901 to S903 may be regarded as a specific implementation of S801a described above.

S904: the RAN slice manager decides whether the RAN slice can be created according to the initial configuration information.

If yes, executing S905; if not, the process is ended.

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

For example, if the physical resources required for configuring the RAN slice include computing resources and storage resources, in this case, if the idle computing resources and the idle storage resources both satisfy the corresponding resources required for configuring the RAN slice, the RAN slice can be created; the RAN slice cannot be created if at least one of the free computing resources and the free storage resources does not satisfy the corresponding resources required to configure the RAN slice. For example, assuming that the idle computing resources are 1 CPU, the idle storage resources are 10 gbytes, the computing resources required to configure the RAN slice are 1 CPU, and the storage resources required to configure the RAN slice are 5 gbytes, 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 computing resources are the same as the computing resources required to configure the RAN slice, the idle storage resources are less than the storage resources required to configure the RAN slice, and thus the RAN slice cannot be created.

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

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

In the present embodiment, it is considered that: the initial configuration information included in the creation indication 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 a create response message in reply to the infrastructure controller.

S908: the RAN slice manager decides whether radio spectrum resources need to be configured.

Since different RAN slices may share radio spectrum resources, the RAN slice manager may determine whether radio spectrum resources need to be configured according to configuration information of the RAN slice, taking configuration information of other RAN slices into consideration comprehensively. The embodiment of the present invention does not limit the specific implementation manner.

If yes, go to S909; if not, S911 is executed.

S909: the RAN slice manager sends wireless spectrum resource configuration information to the physical layer function module; and the physical layer functional 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 function module, or sends the radio spectrum resource configuration information to the physical layer function module through another function module.

Wherein, the radio spectrum resource configuration information may include at least one set of configuration information, and the set of configuration information may include, 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. Optionally, the parameter configuration of the radio spectrum resource may include at least one of TTI, subcarrier spacing, and RBG.

S910: and the physical layer functional module uses the wireless spectrum resources 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 the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted.

Specifically, the RAN slice manager sends to the terminal device, and may include but is not limited to: the RAN slice manager directly sends the RAN slice manager to the terminal equipment, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the physical layer function module, or the RAN slice manager sends the RAN slice manager through the RAN slice and the physical layer function module, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the public 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, e.g., common control channels of multiple RAN slices constitute one shared RAN slice.

S911 is performed to enable the terminal device to obtain the radio spectrum resource allocation information and use the radio spectrum resources according to the radio spectrum resource allocation information.

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

Based on the above case 1, S912 may include: the RAN slice manager updates information in the RAN slice database whether the RAN slice has been created. Based on example 1 in case 2 above, 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 to a RAN slice database. Based on example 2 in case 2 above, 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: and the RAN slice manager updates at least one of the storage resource information and the calculation resource information in the physical resource database according to the update indication message.

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

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

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

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

For example, if the free radio spectrum resources in the physical resource database include two types, 1-10HZ and 21-30HZ respectively, and the physical layer function module starts to use the radio spectrum resources of 21-30HZ in S909 before performing S910, the RAN slice manager updates the free radio spectrum resources in the physical resource database to 1-10HZ in S915.

In the embodiment of the present invention, the execution order of S912, S913 to S914, and S915 is not limited.

Example 2

Fig. 10 is an interaction diagram of a method for creating a RAN slice according to 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 RAN slice creation request message, wherein the RAN slice creation request message comprises an identifier of a RAN slice.

Specifically, the RAN slice manager receives a request message for creating a RAN slice, which is sent by a network side device or a terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device.

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

If yes, executing S1003; if not, the process is ended.

Specifically, the RAN slice manager may determine whether the RAN slice has been created by accessing a RAN slice database. If so, determining that the RAN slice does not need to be created, and if not, determining that the RAN slice needs to be created.

In this embodiment, the RAN slice database may have stored therein an identification of the RAN slice that has been created and an identification of the RAN slice that has not been created. 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 is created by looking up "information whether a RAN slice has been created" in the RAN slice database.

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

Example 3a

Fig. 11a is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention. The method shown in FIG. 11a may include the following steps S1101 a-S1117 a:

s1101 a-S1104 a: the same as S901 to S904 described above.

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

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

S1106 a: the infrastructure controller creates the RAN slice based on the initial configuration information and the default configuration information.

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

S1108 a: 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.

S1109 a: the RAN slice manager updates the current configuration information of the RAN slice according to the reconfiguration information of the RAN slice.

S1110 a-S1117 a: the same as in S908 to S915 described above.

In addition, the execution order of S1109a and S1107a to S1108a is not limited in the embodiment of the present invention. In the embodiment, the RAN slice is established according to the default configuration information and the initial configuration information, so that resources can be quickly occupied, and the RAN slice is quickly established; and may also save the signaling overhead of creating the indication message.

Example 3b

Fig. 11b is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention. The method shown in FIG. 11b may include the following steps S1101 b-S1117 b:

s1101 b-S1102 b: the same as S901 to S902 described above.

S1103 b: the RAN slice manager sends a creation indication message to the infrastructure controller; the infrastructure controller receives a create indication message sent by the RAN slice manager. Wherein the creation indication message does not include the initial configuration information, and the creation indication message is used for indicating the infrastructure controller to create the RAN slice according to the default configuration information.

S1104 b: the infrastructure controller creates the RAN slice according to default configuration information.

S1105 b-S1115 b: the same as in S1107a to S1117 a.

In the embodiment, the RAN slice is established according to the default configuration information, so that resources can be occupied quickly, and the RAN slice is established quickly; and may also save the signaling overhead of creating the indication message.

Example 4a

Fig. 12a is an interaction diagram of a method for creating a RAN slice according to an embodiment of the present invention. The method shown in FIG. 12a may include the following steps S1201 a-S1217 a:

s1201 a: the RAN slice manager receives a create RAN slice request message, wherein the create RAN slice request message includes an identification of a RAN slice.

S1202 a-S1204 a: the same as in S1002 to S1004 described above.

S1205a to S1217 a: the same as in S1105a to S1117 a.

Example 4b

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

s1201 b-S1202 b: the same as S1201a to S1202 a.

S1203 b-S1215 b: the same as S1103b to S1115 b.

The following describes a method for deleting a RAN slice according to an embodiment of the present invention.

Example 5

Fig. 13 is an interaction diagram of a method for deleting a RAN slice according to an embodiment of the present invention. The method shown in fig. 13 may include the following steps S1301 to S1318:

s1301: receiving a service deletion request message by the RAN slice manager; wherein the delete service request message includes information of the service.

Specifically, the RAN slice manager receives a delete service request message sent by a network side device or a terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device.

S1302: and the RAN slice manager acquires the identifier of the RAN slice corresponding to the service.

The method for acquiring the identifier of the RAN slice corresponding to the service by the RAN slice manager may refer to the first implementation manner in S902.

S1303: and the RAN slice manager acquires the service corresponding to the RAN slice and judges whether the service corresponding to the RAN slice also comprises other services.

If yes, go to S1304; if not, S1307 is performed.

Based on table 2, if the service in S1301 is a short message service, the service corresponding to the RAN slice (i.e., RAN slice 2) is only a short message service; if the service in S1301 is a video service, the service corresponding to the RAN slice includes a voice service in addition to the video service.

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

S1305: and the RAN slice deletes the service according to the service deletion indication message.

S1306: the RAN slice replies a delete service response message to the RAN slice manager; the RAN slice manager receives a delete service response message in reply to the RAN slice.

After S1306 is executed, the process ends.

S1307: the RAN slice manager sends a RAN slice deleting indication message to the infrastructure controller; the infrastructure controller receives a delete RAN slice indication message sent by the RAN slice manager. Wherein the delete RAN slice indication message includes an identification of the RAN slice.

S1308: the infrastructure controller deletes the RAN slice according to the delete RAN slice indication message.

S1309: the infrastructure controller replies a RAN slice deleting response message to the RAN slice manager; the RAN slice manager receives a delete RAN slice response message in reply to the infrastructure controller.

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

If yes, executing S1311; if not, go to S1314.

If the radio spectrum resources used by the RAN slice are shared by other RAN slices, the radio spectrum resources used by the RAN slice do not need to be placed in an idle state; if the radio spectrum resource used by the RAN slice is only used by the RAN slice at the current time, the radio spectrum resource used by the RAN slice may be placed in an idle state.

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

Wherein the radio spectrum resource configuration information comprises at least one group of configuration information, and the group of configuration information comprises 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: and the physical layer functional module places the radio spectrum resources used by the RAN slice in an idle state according to the radio spectrum resource configuration information.

S1313: and the physical layer function module replies 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 function module.

S1314: the RAN slice manager sends at least one of the following information to the terminal device: configuration information of the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted.

Wherein, the RAN slice manager sends to the terminal device may include but is not limited to: the RAN slice manager directly sends the RAN slice manager to the terminal equipment, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the physical layer function module, or the RAN slice manager sends the RAN slice manager through the RAN slice and the physical layer function module, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the public RAN slice and the physical layer function module.

S1314 is performed to enable the terminal device to obtain information of the RAN slice and transmit a corresponding service using an appropriate RAN slice.

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

Based on the above case 1, S1315 may include: the RAN slice manager updates information in the RAN slice database whether the RAN slice has been created. Based on example 1 in case 2 above, 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 case 2 above, 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 in S913 to S915 described above.

Example 6

Fig. 14 is an interaction diagram of a method for deleting a RAN slice according to an embodiment of the present invention. The method shown in fig. 14 may include the following steps S1401 to S1413:

s1401: the RAN slice manager receives a delete RAN slice request message, wherein the delete RAN slice request message includes an identification of the RAN slice.

Specifically, the RAN slice manager receives a request message for deleting a RAN slice, which is sent by a network side device or a terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device.

S1402-S1413: the same as the above-described S1307 to S1318.

Example 7

Fig. 15 is an interaction diagram of a method for deleting a RAN slice according to 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 the RAN slice, wherein the status report comprises an identification of the RAN slice.

Wherein the status report is used for describing the operation condition of the RAN slice. The status report may include, but is not limited to, at least one of an idle duration of the RAN slice and a number of users scheduled by the RAN slice.

S1502: the RAN slice manager sends a delete RAN slice indication message to the infrastructure controller according to the status report, wherein the delete RAN slice indication message comprises an identification of the RAN slice and is used for indicating the infrastructure controller to delete the RAN slice.

Specifically, the method comprises the following steps: and if the RAN slice manager decides that the RAN slice needs to be deleted according to the status report, the RAN slice manager sends a RAN slice deleting indication message to the infrastructure controller.

For example, if the idle duration of the RAN slice is greater than or equal to a 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 a duration that the RAN slice does not schedule any UE or provide service for any service. For example, if the number of users scheduled by the RAN slice is less than or equal to a 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: the same as S1308-S1318 described above.

The following describes a method for reconfiguring a RAN slice according to an embodiment of the present invention.

Example 8

Fig. 16 is an interaction diagram of a method for reconfiguring a RAN slice according to an embodiment of the present invention. The method shown in fig. 16 may include the following steps S1601 to S1612:

s1601: and the RAN slice manager receives a reconfiguration service request message, wherein the reconfiguration service request message comprises information of the service.

Specifically, the RAN slice manager receives a reconfiguration service request message sent by a network side device or a terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device. In addition, the description about the information on the service can also refer to embodiment 1.

S1602: and the RAN slice manager acquires the reconfiguration information of the RAN slice corresponding to the service according to the service information.

For the information about the service and the description about the correspondence between the service and the RAN slice, reference may be made to embodiment 1 above. For example, the information of the service may include QoS of the service, and 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: and the RAN slice manager decides whether the RAN slice needs to be reconfigured or not according to the reconfiguration information.

If yes, go to S1604; if not, the process is ended.

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, then there is no need to reconfigure the RAN slice.

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

If yes, executing S1605; if not, the process is ended.

Specifically, the RAN slice manager accesses the physical resource database to obtain the usage of the physical resources. If the use condition of the physical resource meets the physical resource needed by the reconfiguration of the RAN slice, the RAN slice can be created; if the usage of the physical resources does not satisfy the information of the physical resources required for reconfiguring the RAN slice, the RAN slice cannot be created. Specific examples thereof can refer to the above embodiment 1.

S1605: the RAN slice manager respectively sends reconfiguration instruction messages to the RAN slice, the infrastructure controller and the physical layer functional module; the RAN slice, the infrastructure controller and the physical layer functional module respectively receive reconfiguration indication messages sent by a RAN slice manager.

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

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

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

S1607: and the infrastructure controller updates the current configuration information of the RAN slice into the reconfiguration information according to the reconfiguration instruction message.

S1608: and the physical layer functional module updates the current configuration information of the wireless spectrum resources into reconfiguration information according to the reconfiguration indication message. It should be noted that steps S1606, S1607, and S1608 have no sequence, and the execution sequence of these steps can be arbitrarily adjusted.

S1609: the RAN slice, the infrastructure controller and the physical layer function module respectively send reconfiguration response messages to the RAN slice manager; the RAN slice manager receives reconfiguration response messages sent by the RAN slice, the infrastructure controller and the physical layer function module.

S1610: the RAN slice manager sends at least one of the following information to the terminal device: configuration information of the radio spectrum resources, identification of each RAN slice which is created and not deleted, a center frequency point of the radio spectrum resources of each RAN slice which is created and not deleted, and bandwidth information of the radio spectrum resources of each RAN slice which is created and not deleted.

Wherein, the RAN slice manager sends to the terminal device may include but is not limited to: the RAN slice manager directly sends the RAN slice manager to the terminal equipment, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the physical layer function module, or the RAN slice manager sends the RAN slice manager through the RAN slice and the physical layer function module, or the RAN slice manager sends the RAN slice manager to the terminal equipment through the public RAN slice and the physical layer function module. S1610 is performed to enable the terminal device to obtain information of the RAN slice and transmit a corresponding service using an appropriate RAN slice.

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

Example 9

Fig. 17 is an interaction diagram of a method for reconfiguring a RAN slice according to an embodiment of the present invention. The method shown in fig. 17 includes the following steps S1701 to S1712:

s1701: the RAN slice manager receives a reconfiguration RAN slice request message, wherein the reconfiguration slice request message includes reconfiguration information of the RAN slice.

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

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

Example 10

Fig. 18 is an interaction diagram of a method for reconfiguring a RAN slice according to 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 status reports sent by the RAN slice. Wherein the status report includes an identification of the RAN slice, and the status report describes an operating condition of the RAN slice. The status report may include, but is not limited to, slice feedback latency or throughput information, etc.

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

S1803: the RAN slice manager sends reconfiguration instruction information to the RAN slice, the infrastructure controller and the physical layer functional module, wherein the reconfiguration instruction information is used for instructing to update the current configuration information into reconfiguration information; the RAN slice, the infrastructure controller and the physical layer function module receive a reconfiguration indication message sent by the RAN slice manager.

Specifically, the method comprises the following steps: and if the RAN slice manager determines that the RAN slice needs to be reconfigured according to the status report decision, the RAN slice manager sends a reconfiguration instruction message to the RAN slice. The method may further comprise: and if the RAN slice manager determines that the RAN slice does not need to be reconfigured according to the status report decision, the RAN slice manager is ended.

For example, if the actual throughput is greater than or equal to the third preset threshold, which indicates that the resources are not enough, some more resources need to be allocated. If the designed RAN slice maximum throughput is 100M, the throughput of all current users has reached 95M, and the number of users is increasing; to prevent the RAN slice from crashing, 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, which indicates that the resources are excessive, some resources may be withdrawn or the RAN slice may be adjusted; if the designed RAN slice maximum throughput is 100M, and the current throughput of all users is 1M and is maintained for a long time, the scaling is required, and in this case, the maximum throughput that can be supported is 10M, and it is determined to reconfigure the RAN slice.

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

The following describes a method for querying a RAN slice according to an embodiment of the present invention.

Example 11

Fig. 19 is an interaction diagram of a method for querying a RAN slice according to 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, wherein the first query RAN slice request message includes an identification of a RAN slice.

Specifically, the RAN slice manager may receive a first query RAN slice request message sent by a network side device or a terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device.

S1902: and the RAN slice manager judges whether the RAN slice is created according to the identification of the RAN slice.

If yes, go to S1903; if not, go to S1904.

Specifically, S1902 may include: the RAN slice manager accesses a RAN slice database and acquires information of the RAN slice according to the identifier of the RAN slice, or the RAN slice manager accesses a storage unit of a node where the RAN slice manager is located and acquires the information of the RAN slice according to the identifier of the RAN slice; wherein, the storage unit stores therein information of RAN slices in a 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 no information for the RAN slice exists.

Example 12

Fig. 20 is an interaction diagram of a method for querying a RAN slice according to 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, wherein the second query RAN slice request message includes information of the service.

Specifically, the RAN slice manager receives a second RAN slice query request message sent by the network side device or the terminal side device. Please refer to embodiment 1 for a description of a network side device and a terminal side device. Fig. 20 illustrates this specific embodiment as an example.

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

The method for the RAN slice manager to obtain the identifier of the RAN slice corresponding to the service may be referred to as S902.

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

The above description mainly introduces the scheme provided by the embodiment of the present invention from the perspective of the RAN slice manager. It is understood that, in order to implement the above functions, the device for managing RAN slices includes a hardware structure and/or a software module for performing the functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary modules and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Fig. 21a shows a network device 210 a. Network device 210a may be a network device that includes the RAN slice manager provided above. Network device 210a may include: an acquisition module 2101a and a sending module 2102 a. Optionally, the network device 210a may further include: a receiving module 2103a and an updating module 2104 a.

1) When network device 210a is configured to perform the method of creating RAN slices provided above:

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

In an alternative implementation, the sending module 2102a may perform S801b in fig. 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, S913, etc., in fig. 9, and/or other processes for the techniques described herein. The receiving module 2103a may perform S901 and S907 of fig. 9, and/or the like, and/or other processes for the techniques described herein. The update module 2104a can perform S912 and S915 of fig. 9, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the obtaining module 2101a may perform S1003 in fig. 10. The transmitting module 2102a may perform S1005, S1009, S1011, S1013, etc. in fig. 10, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1001 and S1007 in fig. 10, and/or the like, and/or other processes for the techniques described herein. The update module 2104a can perform S1012 and S1015, etc. in fig. 10, and/or other processes for the techniques described herein.

In an alternative implementation, the obtaining module 2101a may perform S1103a in fig. 11 a. The sending module 2102a may perform S1108a, S1111a, S1113a, S1115a, etc., in fig. 11a, and/or other processes for the techniques described herein. The receiving module 2103a may perform S1101a and S1107a in fig. 11a, and/or the like, 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 alternative implementation, the obtaining module 2101a may perform S1203a in fig. 12 a. The sending module 2102a may perform S1205a, S1208a, S1211a, S1213a, 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, among other things, S1214a and S1217a in FIG. 12a, and/or other processes for the techniques described herein.

2) When network device 210a is configured to perform the method for deleting RAN slices provided above:

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

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

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

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

in an alternative implementation, the obtaining module 2101a may perform 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 can perform S1613 in fig. 16.

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

In an alternative 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 can perform S1811 in fig. 18.

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

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

In an alternative implementation, the transmit module 2101b may perform S2001 and S2004-S2005, etc. in FIG. 20, and/or other processes for the techniques described herein. The decision module 2102b may perform S2003, etc., in fig. 20, and/or other processes for the techniques described herein. The acquisition module 2103b may perform S2002, etc. in fig. 20, 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 interconnected by the bus 2204. Of course, the processor 2201, the transceiver 2202 and the memory 2203 may be connected to each other by other connection means. Wherein the memory 2203 is configured to store program code for causing the processor 2201 to perform the actions performed by the RAN slice manager in any of the methods of managing RAN slices provided above, wherein the methods of managing RAN slices may include at least one of creating, deleting, reconfiguring, and querying RAN slices. For explanation of relevant contents 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 an infrastructure device controller as 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 send module 2303, a delete module 2304, and an update module 2305. The functions of each of the functional modules may be deduced according to the steps in the embodiments of the method provided above, and refer to the contents provided in the above contents of the present invention, which are not described herein again.

1) When the network device 230 is configured to perform the method of creating RAN slices provided above:

in an alternative implementation, the receiving module 2301 may perform S801a in fig. 8a, and/or the like, and/or other processes for the techniques described herein. Creation module 2302 can perform S802a, etc. in fig. 8a, and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S801b in fig. 8b, and/or the like, and/or other processes for the techniques described herein. Creation module 2302 may perform S802b, etc. in fig. 8b, and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S905 and S913, etc. in fig. 9, and/or other processes for the techniques described herein. Creation module 2302 can perform S906, etc. in fig. 9, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S907, etc. in fig. 9, 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 alternative implementation, the receiving module 2301 may perform S1005, S1013, etc. in fig. 10, and/or other processes for the techniques described herein. Creation module 2302 can perform S1006, etc. in fig. 10, and/or other processes for the techniques described herein. Transmitting 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 and S1115a in fig. 11a, and/or the like, and/or other processes for the techniques described herein. Creation module 2302 can perform S1106a in fig. 11a, etc., and/or other processes for the techniques described herein. The sending module 2303 may perform S1107a in fig. 11a, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1106a in fig. 11a, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform, among other things, S1205a and S1215a in fig. 12a, and/or other processes for the techniques described herein. Creation module 2302 can perform S1206a, etc., in fig. 12a, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S1207a in fig. 12a, etc., and/or other processes for the techniques described herein. The update module 2305 may perform S1216a in fig. 12a, etc., and/or other processes for the techniques described herein.

2) When the network device 230 is configured to perform the method for deleting RAN slices provided above:

in an alternative implementation, the receiving module 2301 may perform, among other things, S1307 and S1316 in fig. 13, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S1309, etc. in fig. 13, and/or other processes for the techniques described herein. Deletion module 2304 may perform S1308 in fig. 13, etc., and/or other processes for the techniques described herein. Update module 2305 may perform S1317, etc. in fig. 13, and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S1402 and S1411, etc. in fig. 14, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S1404, etc. in fig. 14, and/or other processes for the techniques described herein. Deletion module 2304 may perform S1403 at 14, etc., and/or other processes for the techniques described herein. Update module 2305 may perform S1412, etc. in fig. 14, and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform, among other things, S1502 and S1511 in fig. 15, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S1504, etc. in fig. 15, and/or other processes for the techniques described herein. The delete module 2304 may perform S1503 or the like in fig. 15, and/or other processes for the techniques described herein. Update module 2305 may perform S1512, etc. in fig. 15, and/or other processes for the techniques described herein.

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

in an alternative 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. Update module 2305 may perform S1607 in fig. 16, etc., and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform S1704, etc. in fig. 17, and/or other processes for the techniques described herein. The transmitting module 2303 may perform S1708 in fig. 17, etc., and/or other processes for the techniques described herein. Update module 2305 may perform S1706 in fig. 17, and/or the like, and/or other processes for the techniques described herein.

In an alternative implementation, the receiving module 2301 may perform the operations of fig. 18 and S1803, etc., 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. 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. Network device 240 may include: a processor 2401, a transceiver 2402, and a memory 2403. The network device 220 may also include a bus 2404; the processor 2401, the transceiver 2402 and the memory 2403 are connected to each other via a bus 2404. Of course, the processor 2401, the transceiver 2402 and the memory 2403 may be interconnected by other connection means. Memory 2403 is used to store, among other things, program code for causing processor 2401 to perform the actions performed by the infrastructure controller in any of the methods of managing RAN slices provided above. The method for managing the RAN slice may include at least one of a method for creating, deleting, reconfiguring, and querying the RAN slice. For explanation of relevant contents in this embodiment, reference may be made to the above.

Fig. 25 shows a terminal device 250. The terminal device 250 may include: a transmitting module 2501. Optionally, the terminal device 250 may further include: a receiving module 2502 and a using module 2503. The functions of each of the functional modules may be deduced according to the steps in the embodiments of the methods provided above, or refer to the contents provided in the above contents of the present invention, and are not described herein again.

1) When the terminal device 250 is configured to perform the method for creating a RAN slice provided above:

in one possible implementation, the transmitting module 2501 may perform S901 in fig. 9, and/or the like, and/or other processes for the techniques described herein. Receiving module 2502 may perform S911 or the like in fig. 9, and/or other processes for the techniques described herein.

In one possible implementation, the transmitting module 2501 may perform S1001, etc. in fig. 10, and/or other processes for the techniques described herein. Receiving module 2502 may perform S1011, etc. in fig. 10, and/or other processes for the techniques described herein.

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

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

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

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

In one possible implementation, transmitting module 2501 may perform S1401, etc. in fig. 14, and/or other processes for the techniques described herein. Receiving module 2502 may perform S1409, etc. in fig. 14, and/or other processes for the techniques described herein.

In one possible implementation, the transmitting module 2501 may perform S1501, etc. in fig. 15, and/or other processes for the techniques described herein. Receiving module 2502 may be S1509, etc. in fig. 15, and/or other processes for the techniques described herein.

3) When the terminal device 250 is configured to perform the method of reconfiguring a RAN slice provided above:

in one possible implementation, the transmitting module 2501 may perform S1601 or the like in fig. 16, and/or other processes for the techniques described herein. Receiving module 2502 may perform S1610, etc. in fig. 16, and/or other processes for the techniques described herein.

In one possible implementation, the transmitting module 2501 may perform S1701 in fig. 17, and/or the like, and/or other processes for the techniques described herein. Receiving module 2502 may perform S1709, etc. in fig. 17, and/or other processes for the techniques described herein.

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

4) When the terminal device 250 is configured to perform the method for querying a RAN slice provided above:

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

In one possible implementation, 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; the processor 2601, the transceiver 2602, and the memory 2603 are connected to each other via a bus 2604. Of course, the processor 2601, the transceiver 2602, and the memory 2603 may be connected to each other by other connections. Memory 2603 is configured to store program code for causing processor 2601 to perform, among other things, the actions performed by the terminal device in any of the methods of managing RAN slices provided above. The method for managing the RAN slice may include at least one of a method for creating, deleting, reconfiguring, and querying the RAN slice. For explanation of relevant contents in this embodiment, reference may be made to the above.

It is noted that processor 2201, processor 2401, and processor 2601 may be a CPU, a general purpose processor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. Processor 2201, processor 2401, and processor 2601 may also be a combination that performs computing functions, e.g., comprising one or more microprocessors, a combination of DSPs and microprocessors, or the like.

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

Bus 2203, bus 2403, and bus 2603 may be Peripheral Component Interconnect (PCI) buses or Extended Industry Standard Architecture (EISA) buses, or the like. The bus 2203, bus 2403 and bus 2603 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 22, 24 and 26, but this does not mean only one bus or one type of bus.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processing module. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a compact disc read only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC.

It will be clear to those skilled in the art that, for convenience and simplicity of description, the above-described apparatus is only illustrated by the division of the above functional modules, and in practical applications, the above-described function distribution may be performed by different functional modules according to needs, that is, the internal structure of the apparatus is divided into different functional modules to perform all or part of the above-described functions. For the specific working processes of the above-described apparatus, and module, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the modules or the division of modules are merely one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of modules or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

Claims

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,

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;

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.