Patent Description:
In fifth-generation mobile communication technology (<NUM>th Generation, <NUM>), one typical business mode is that an operator splits a physical wireless network into a plurality of logical networks by using slicing technology and leases them to vertical industries and enterprises, where each logical network may have different functional characteristics and service resources, to meet different service needs. A concept diagram of slices in a next-generation mobile communications network (next generation mobile networks, NGMN) is shown in <FIG>.

In an existing solution, in service logic of a current slice, a tenant needs to specify a service level agreement (service level agreement, SLA) index and a related service scenario in advance, and rents a network from an operator. The operator designs and deploys the slice based on requirements of the tenant, and a terminal to which the tenant belongs cannot really use the slice until the slice is completely deployed in a wireless network. A specific process is shown in <FIG>.

In the existing solution, the slice needs to be first deployed and then used. On the one hand, to carry a service of the tenant, the slice needs to enable some unique functional characteristics, and enabling of the functional characteristics consumes resources; on the other hand, to enable access of the service of the tenant at any time, the slice needs to reserve some resources. When there are a temporal gap and a geographic gap between deployment and use of a slice, where the temporal gap specifically means that the slice is deployed in advance, but used later, and the geographic gap specifically means that deployment is performed in a relatively large area, but the service actually occurs only in a relatively small area, network resources are wasted, and costs are increased.

<CIT> discloses systems and methods for network slice management.

<CIT> discloses a method for service provision at a network element in a radio access network associated with a core network.

<CIT> discloses a mobile communication network system and a network configuring method.

<CIT> discloses a method in a user equipment for attaching the user equipment to a mobile communications network.

<CIT> discloses systems and methods for operating network slices in a communication network such as a 5th generation wireless communication network. HUAWEI: "Key principles for support of Network Slicing in RAN" describes a support for user equipment associating with multiple network slices simultaneously.

ZTE: "Network Slice Selection Procedure" describes a procedure for Network slice selection.

The present invention is defined by the features disclosed in the independent claims. Additional embodiments are defined in the dependent claims.

Embodiments of this application provide a network slice deployment method, to reduce a gap between deployment and use of a slice, thereby saving network resources and reducing costs.

To make a person skilled in the art understand the technical solutions in this application better, the following describes the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application.

In the specification, claims, and accompanying drawings of this application, the terms "first", "second", "third", "fourth", and so on (if existent) are intended to distinguish between similar objects but do not necessarily indicate a specific order or sequence. It should be understood that the data termed in such a way are interchangeable in proper circumstances so that the embodiments of the present invention described herein can be implemented in other orders than the order illustrated or described herein.

This embodiment of this application may be applied to a network architecture shown in <FIG>. In the embodiments of this application, a first request message is specifically a network slice service request message, a second request message is specifically a network slice deployment request message, a first response message is specifically a network slice service response message, and a second response message is specifically a network slice deployment response message. The embodiments of this application are specifically described by using the names defined above, and the first request message and the like may alternatively have other names. This is not specifically limited herein. In the network architecture, a subscriber subscribes to a slice from an operator, and the operator designs the slice, generates slice information on a management function entity, but does not actually deploy the slice. Optionally, the operator defines a slice identification for the subscriber. When the terminal device initiates a service to the network device, the network device sends a message for requesting a slice to a management function entity, the management function entity actually deploys the slice, and the network device sends a message to the terminal device, so that the terminal device can complete a service in the corresponding slice. The embodiments of this application are described by using an example in which a terminal device initiates an automated driving service and a drone patrol and inspection service to the network device. A tenant completes an operation of subscribing to the slice. When the terminal device initiates an automated driving service to the network device, the network device deploys the slice that has been subscribed to, and completes the automated driving service. When the terminal device initiates a drone patrol and inspection service to the network device, the network device deploys the slice that has been subscribed to, and completes the drone patrol and inspection service.

For ease of understanding, a specific process of this embodiment of this application is described below. Referring to <FIG>, an embodiment of a network slice deployment method according to the embodiments of this application includes the following steps. A terminal device subscribes to a target network slice.

A subscriber subscribes to the target network slice from an operator by using the terminal device, and the target network slice is configured to meet a requirement of a target service to be initiated by the subscriber. When the subscriber subscribes to the target network slice, the target network slice is displayed as a dynamic network slice, and when the operator identifies that the target network slice is a dynamic network slice, the operator only records the network slice, but does not actually deploy the target network slice.

It should be noted that the subscriber may subscribe to the target network slice from the operator in another manner. For example, the subscriber may reserve the network slice from the operator by using another terminal device, or may reserve the network slice through a call or by using related software. The another terminal device and the terminal device that initiates the service do not need to be a same device. The terminal device that initiates the service may be a device, such as a vehicle mounted station or a drone, that can use a wireless network, and the terminal device that subscribes to the network slice may be a communications device such as a smartphone.

It may be understood that, during the entire subscription process, the subscriber needs to specify a service scenario, so that the operator may properly design the network slice based on the specific service scenario. A description of the service scenario usually includes: a geographic distribution of the terminal device to which the subscriber belongs, an access frequency of the terminal device, a traffic feature of the terminal device, mobility of the terminal device, and the like. The operator usually designs the slice with reference to the service scenario of the subscriber, to convert an SLA of the subscriber to functional characteristics and resource requirements of the network device. There are a variety of forms of the SLA. For example, the subscriber may directly rent an air interface frequency spectrum of <NUM>, or the subscriber may rent a service at a rate of <NUM> Gbps, or the subscriber requires each terminal to guarantee an end-to-end latency of <NUM> at a probability of <NUM>%, or may be in another form. This is not specifically limited herein.

A management function entity generates target network slice information.

The management function entity generates the target network slice information according to an instruction of the operator, and the target network slice information corresponds to a target service to which the subscriber subscribes. The management function entity includes a network management (network management, NM) entity and a domain management (domain management, DM) entity. Specifically, the management function entity generates target network slice deployment information and a target network slice identification by using the network management entity NM, where the target network slice identification is used to uniquely identify the target network slice; and the management function entity generates a target network slice management instance by using the domain management entity DM, where the target network slice management instance is used to deploy the target network slice. The management instance includes subnet demand information of the subscriber, a functional characteristic and a resource policy of a subnet for meeting a demand, and the like. The DM checks an attribute of the slice, and if the slice is a dynamic slice, the slice is not deployed to the network device, and related information is kept only in the DM. The network slice deployment information may be at least one of the following information: a network slice template identification, a network slice configuration parameter, a network component required by the network slice (for example, a subnet and a network function), a virtual resource required by the network slice, and the like.

It should be noted that the network management entity includes one or all of end-to-end network management functions or end-to-end network orchestration functions, and may have some or all of the following functions: end-to-end network management (for example, lifecycle management of a network, network template management, fault management of a network, performance management of a network, and configuration management of a network); mapping between an end-to-end network and a subnet and mapping between an end-to-end network and a network function; coordination of network resources or child domain SLAs provided by different domains (for example, an access network domain, a core network domain, or a transport network domain); splitting network demand information into subnet demand information; and centralized orchestration of subnets and network functions that are provided by child domains, to enable the subnets or the network functions that are provided by the child domains to satisfy a requirement (for example, an SLA requirement, a key performance indicator (key performance indicator, KPI) requirement, or a quality of service (quality of service, QoS) requirement) of a target service or a network. The NM in this embodiment of this application mainly indicates an entity having the functions described above, this embodiment does not impose any limitation on the name of the NM, and the NM may be a cross-domain management unit, a cross-domain network slice management unit, or the like. This is not specifically limited herein. The NM may be an independent management unit, or may be a specific function of any management unit: a network orchestration unit, a network management and orchestration unit, a service management unit, a service orchestration unit, a service management and orchestration unit, or a network function virtualization orchestrator (network function virtualization orchestrator, NFVO). The NM may be included in the operation support system (Operation support system, OSS), or may be not included in the OSS.

It should be noted that the domain management entity includes one or all of a subnet management function or an orchestration function, and may have some or all of the following functions: domain management (including lifecycle management (creation, update, and deletion) of a subnet, fault management of a subnet, performance management of a subnet, and configuration management of a subnet, and the like); management of a service (including lifecycle management of a service, fault management of a service, performance management of a service, and configuration management of a service, and the like); coordination of network resources (for example, a network function (network function, NF) and a network element (network element, NE)), for centralized orchestration. The DM in this embodiment of this application mainly indicates an entity having the functions described above, this embodiment does not impose any limitation on the name of the DM, and the DM may be a domain slice management unit, a network slice subnet management unit, or the like. This is not specifically limited herein. The DM may be an independent management unit, or may be a specific function of any management unit: a network management unit, a network orchestration unit, a network management and orchestration unit, a network element functional unit, a service management unit, a service orchestration unit, a domain management unit, a service management and orchestration unit, or an NFVO. The DM may be included in the OSS, or may be not included in the OSS.

It may be understood that, the subnet described above may include one or more of the following: an access network (access network, AN) part (for example, an AN NF), a core network (core network, CN) part (for example, a CN NF), and a transport network (transport network, TN) part. When the subnet managed by the DM includes only the AN part, it may be considered that the subnet management unit is an AN DM. When the subnet managed by the DM includes only the CN part, it may be considered that the subnet management unit is a CN DM. When the subnet managed by the DM includes the AN part and the CN part, it may be considered that the subnet management unit is a Mix DM.

The management function entity sends the target network slice information to the terminal device.

After the management function entity generates the target network slice deployment information and the target network slice identification, the management function entity sends the target network slice information to the terminal device, where the target network slice includes the target network slice deployment information and the target network slice identification, and the target network slice identification is used to: identify the target network slice, and split demand information (for example, an end-to-end (end to end, E2E) SLA) of a subscriber into subnet demand information (for example, a CN SLA, an AN SLA, and a TN SLA).

The terminal device sends a network slice service request message to a network device.

The terminal device sends the network slice service request message to the network device, where the network slice service request message is used to instruct to deploy a target network slice for providing a target service to the terminal device, a corresponding management function entity has allocated target network slice information for the target network slice corresponding to the target service, and the target service is a service that subscribes to the target network slice. The target service may be a temporary slice service or a low-traffic slice service. Specifically, the temporary slice service may be an automated driving service, and the low-traffic slice service may be a drone patrol and inspection service.

The network device sends a network slice deployment request message to the management function entity.

After the network device receives the network slice service request message sent by the terminal device, and identifies the target network slice information carried in the network slice service request message, the network device sends the network slice deployment request message to the management function entity, where the network slice deployment request message includes the target network slice information, and the network slice deployment request message is used to instruct the management function entity to deploy the target network slice corresponding to the target network slice information. Specifically, the network device sends the network slice deployment request message to the domain management entity DM.

It should be noted that the network slice service request message further includes an international mobile subscriber identity (international mobile subscriber identification, IMSI), or a mobile station integrated services digital network number (mobile station integrated services digital network number, MSISDN), or may include other information. This is not specifically specified herein.

The management function entity deploys the target network slice based on the network slice deployment request message.

The management function entity obtains corresponding target network slice deployment information based on the target network slice information, and deploys the target network slice based on the target network slice deployment information, where the target network slice is a network slice to which the target service subscribes. Specifically, the DM deploys the target network slice on the network device based on the generated management instance and the network slice deployment request message. It may be understood that, after receiving the target network slice information that is forwarded by the network device and that is sent by the mobile terminal, the management function entity may perform authentication on the target network slice information. Specifically, based on a parameter of the network slice information that is generated and saved by the management function entity, the received target network slice information is verified whether to meet the requirement. If the requirement is met, the target network slice deployment information is obtained based on the received target network slice information.

It should be noted that the management function entity obtains, based on the target network slice information added by the terminal device when the terminal device initiates a service request, the target network slice deployment information that has been generated by the operator, and actually deploys the target network slice to the network device based on the target network slice deployment information. Because a location of the terminal device that initiates the service is specific, the management function entity may deploy the network slice in an area of a preset size in which the terminal device is located, and in this case, the initiated target service is in a temporarily suspended state. The management function entity sends a network slice deployment response message to the network device.

When the management function entity completes the deployment of the network slice, the management function entity sends the network slice deployment response message to the network device, where the network slice deployment response message is used to indicate that the target network slice has been completely deployed.

It may be understood that, the network device may send a network slice service response message to the terminal device, where the network slice service response message is used to indicate that the terminal device can provide a service by using the deployed target network slice.

It should be noted that, after the network device receives the network slice deployment response message sent by the management function entity, the network device may further separately send a notification message to the terminal device, where the notification message is used to indicate that the target network slice has been completely deployed.

The terminal device uses the deployed target network slice to perform a service.

The terminal device uses the deployed target network slice to perform a service. In one feasible implementation, the terminal device receives the notification message sent by the network device, and confirms that the target network slice that is subscribed to for a to-be-initiated target service has been deployed, and the terminal device uses the deployed network slice to perform the target service. The terminal device may further initiate a service based on the network slice service response message.

It should be noted that, after the terminal device completes the target service, the terminal device may send a prompt message to the network device, and the prompt message is used to indicate that use of the target network slice has been completed, and the target network slice is no longer needed, so that the network device may delete the deployed target network slice, to release the occupied resources.

In this embodiment of this application, the network device deploys, based on a received service request, the network slice in real time in a service initiation phase, to reduce a gap between deployment and use of the network slice, thereby saving network resources and reducing costs.

This embodiment of this application is described below by using an example with reference to an application scenario of an automated driving service.

For example, it is assumed that five cars are traveling, and on the halfway, it is temporarily decided to group the five cars into an automated driving vehicle fleet. A subscriber A in the vehicle fleet subscribes to a slice from an operator in any available manner, including, but not limited to, making a call to a customer service of a wireless operator or using a web page or an application program provided by a wireless operator. It needs be clarified herein that the related five cars all have an automated driving function. After receiving a subscription request from the subscriber A, the operator generates target network slice information for the subscriber A by using an NM, including generating a target network slice identification and target network slice deployment information for a target network slice, splits demand information (for example, an E2E SLA) of the tenant into subnet demand information (such as a CN SLA, an AN SLA, or a TN SLA), and marks the target network slice as a dynamic slice, where the target network slice provides a service for the automated driving service. The NM may return one target network slice identification to the operator, the operator may inform the vehicle fleet of the identification, and the vehicle fleet may use the identification to activate the network slice. The NM deploys the target network slice to the DM, and the DM generates a management instance for the target network slice, where the management instance includes subnet demand information of the subscriber, a functional characteristic and a resource policy of a subnet for meeting a demand, and the like. The DM checks an attribute of the target network slice, and if the slice is a dynamic slice, the slice is not deployed to the network device, and related information is kept only in the DM. A vehicle terminal in the vehicle fleet initiates a call to access the network device, where the vehicle terminal carries a specific identification specified by the operator in the call. When dealing with the call from the vehicle terminal, the network device finds that the UE carries a particular identification (target network slice identification), and after the particular identification is successfully authenticated, the network device requests the management function entity to deploy the slice. The management function entity indexes, based on the particular identification carried by the vehicle terminal when the vehicle terminal initiates the call, the target network slice deployment information that has been generated by the operator, and actually deploys the network slice for the network device based on the corresponding target network slice deployment information. Because a location of the terminal that initiates the service is specific, the deployment occurs only in a relatively small area in which the terminal device is located, and in this case, the service of the vehicle mounted station is in a temporarily suspended state. After the target network slice is completely deployed, the service of the vehicle mounted station is activated, and the vehicle mounted station may continue to perform the automated driving service. In this embodiment of this application, based on the foregoing process, the network device may deploy the slice in advance on a traveling route of the vehicle fleet, so that large-scale deployment is not needed, thereby saving network resources.

Referring to <FIG>, another embodiment of a network slice deployment method according to the embodiments of this application includes the following steps.

A terminal device subscribes to a target network slice.

The management function entity generates the target network slice information according to an instruction of the operator, and the target network slice information corresponds to a target service to which the subscriber subscribes. The management function entity includes a network management entity (network management, NM) and a domain management entity (domain management, DM). Specifically, the management function entity generates target network slice deployment information and a target network slice identification by using the network management entity NM, where the target network slice identification is used to uniquely identify the target network slice; and the management function entity generates a target network slice management instance by using the domain management entity DM, where the target network slice management instance is used to deploy the target network slice. The management instance includes subnet demand information of the subscriber, a functional characteristic, a resource policy, and the like of a subnet for meeting a demand. The DM checks an attribute of the slice, and if the slice is a dynamic slice, the slice is not deployed to the network device, and related information is kept only in the DM.

The management function entity sends target network slice identification information to the network device.

After the management function entity generates the target network slice deployment information and the target network slice identification, the management function entity sends the target network slice identification information to the network device, where the target network slice includes the target network slice deployment information and the target network slice identification, and the target network slice identification is used to: identify the target network slice, and split subscriber demand information (such as an E2E SLA) into subnet demand information (such as a CN SLA, an AN SLA, and a TN SLA). Specifically, the network device may write the target network slice identification through the NM into a home subscriber server (home subscriber server, HSS) by using the IMSI or MSISDN of the terminal device as an index.

After the network device receives the network slice service request message sent by the terminal device, the HSS is triggered by the network slice service request message of the terminal device, and the network device sends, based on the target network slice information stored in the HSS, the network slice deployment request message to the management function entity, where the network slice deployment request message includes the target network slice identification, the target network slice identification is used to identify a target network slice, and the network slice deployment request message is used to instruct the management function entity to deploy the target network slice corresponding to the target network slice information. Specifically, the network device sends the network slice deployment request message to the domain management entity DM.

It should be noted that, the network slice service request message further includes the IMSI or the MSISDN, or may further include other information. This is not specifically limited herein.

The management function entity obtains corresponding target network slice deployment information based on the target network slice information, and deploys the target network slice based on the target network slice deployment information, where the target network slice is a network slice to which the target service subscribes. Specifically, the DM deploys the target network slice on the network device based on the generated management instance and the network slice deployment request message. It should be noted that the management function entity indexes, based on the target network slice information added by the terminal device when the terminal device initiates a service request, the target network slice deployment information that has been generated by the operator, and actually deploys the target network slice to the network device based on the target network slice deployment information. Because a location of the terminal device that initiates the service is specific, the management function entity may deploy the network slice in an area of a preset size in which the terminal device is located, and in this case, the initiated target service is in a temporarily suspended state. The management function entity sends a network slice deployment response message to the network device.

This embodiment of this application is described below by using an example with reference to an application scenario of a drone patrol and inspection service.

For example, a specific electric power company needs to perform a half-yearly patrol and inspection service for transmission lines by using a drone, and the electric power company may subscribe to a slice from an operator in any manner at any time. After receiving a subscription request from the electric power company, the operator generates target network slice information for the electric power company by using an NM, including generating a target network slice identification and target network slice deployment information for a target network slice, splits demand information (such as an E2E SLA) of the tenant into subnet demand information (such as a CN SLA, an AN SLA, or a TN SLA), and marks the target network slice as a dynamic slice, where the target network slice provides a service for the drone patrol and inspection service. The NM may write the target network slice identification into an HSS by using an IMSI or an MSISDN of the UE provided by a subscriber when the subscriber subscribes to the slice as an index. The NM deploys the target network slice to the DM, and the DM generates a management instance for the target network slice, where the management instance includes subnet demand information of the subscriber, a functional characteristic and a resource policy of a subnet for meeting a demand, and the like. The DM checks an attribute of the target network slice, and if the slice is a dynamic slice, the slice is not deployed to the network device, and related information is kept only in the DM. When the drone actually conducts the patrol and inspection service, the drone terminal initiates a call to access the network device. When dealing with the call from the drone terminal, the network device finds a particular identification (target network slice identification) of the UE in the HSS, and requests the management function entity to deploy the slice. The management function entity indexes, based on the particular identification of the drone terminal, the target network slice deployment information that has been generated by the operator, and actually deploys the network slice for the network device based on the corresponding target network slice deployment information. Because a location of the terminal that initiates the service is specific, the deployment occurs only in a relatively small area in which the drone terminal is located, and in this case, the service of the drone terminal is in a temporarily suspended state. After the target network slice is completely deployed, the service of the drone patrol and inspection is activated, and the drone terminal may continue to perform the patrol and inspection service. In this embodiment of this application, based on the foregoing process, the network device may deploy the slice only when the drone actually performs the service, so that long time deployment is not needed, thereby saving network resources.

The network slice deployment method in the embodiments of this application is described above. The network device, the terminal device, and the management function entity in the embodiments of this application are described below. Referring to <FIG>, an embodiment of a network device according to the embodiments of this application includes:.

In an example, the network device may further include:
a third receiving unit <NUM>, configured to receive the target network slice information sent by the management function entity, where the target network slice information includes a target network slice identification.

In an example, the network device may further include:
a second sending unit <NUM>, configured to send a first response message to the terminal device, where the first response message is used to indicate that the terminal device can provide a service by using the deployed target network slice.

Referring to <FIG>, an embodiment of a management function entity according to the embodiments of this application includes:.

In an example, the management function entity may further include:
a processing unit <NUM>, configured to generate the target network slice information.

In an example, the processing unit <NUM> includes:
a generation module <NUM>, configured to generate a target network slice identification and the corresponding target network slice deployment information by using a network management entity, where the target network slice deployment information is used to deploy the target network slice.

In an example, the processing unit <NUM> includes:
a sending module <NUM>, configured to send the target network slice information to the network device, or send the target network slice information to the terminal device.

In an example, the management function entity may further include:
an authentication unit <NUM>, configured to perform authentication on the received target network slice information.

Referring to <FIG>, an embodiment of a terminal device according to the embodiments of this application includes:.

In an example, the terminal device may further include:.

In an example, the terminal device may further include:
a second receiving unit <NUM>, configured to receive a first response message sent by the network device, where the first response message is used to indicate that the terminal device can provide a service by using the deployed target network slice.

<FIG> above separately describe the network device, the management function entity, and the terminal device in the embodiments of this application in detail from a perspective of a modularized function entity, and the network device, the management function entity, and the terminal device in the embodiments of this application are described below in detail from a perspective of hardware processing. <FIG> is a schematic structural diagram of a network device according to an embodiment of this application. The network device <NUM> may vary greatly due to different configurations or performance, and may include one or more processors (central processing units, CPU) <NUM> (for example, one or more processors) and a memory <NUM>, and one or more storage media <NUM> (for example, one or more massive storage devices) that store an application program <NUM> or data <NUM>. The memory <NUM> and the storage medium <NUM> may be transient or persistent storages. The program stored in the storage medium <NUM> may include one or more modules (not shown in the figure), and each module may include a series of instructions and operations for the network device. Still further, the processor <NUM> may be configured to: communicate with the storage medium <NUM>, and perform, on the network device <NUM>, the series of instruction and operations in the storage medium <NUM>.

The network device <NUM> may further include one or more power supplies <NUM>, one or more wired or wireless network interfaces <NUM>, one or more input/output interfaces <NUM>, and/or one or more operating systems <NUM>, for example, Windows Server, Mac OS X, Unix, Linux, or FreeBSD. A person skilled in the art may understand that the structure of the network device shown in <FIG> does not constitute a limitation to the network device, and the network device may include more components or fewer components than those shown in the figure, or a combination of some components, or a different component arrangement.

The components of the network device are described in detail below with reference to <FIG>.

The processor <NUM> is a control center of the network device, and may perform processing based on a set network slice deployment method. The processor <NUM> connects all parts of the entire network device by using various interfaces and lines, performs various functions of the network device and processes data by running or executing the software program and/or module stored in the memory <NUM> and by invoking the data stored in the memory <NUM>, to implement the deployment of the network slice.

The memory <NUM> may be configured to store a software program and a module, and the processor <NUM> runs the software program and the module that are stored in the memory <NUM>, to perform various functional applications of the network device <NUM> and data processing. The memory <NUM> may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required by at least one function (for example, a function of deploying a slice), and the like. The data storage area may store data (for example, a network slice deployment request message) created based on use of the network device, and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may also include a non-volatile memory such as at least one magnetic disk storage component, a flash memory, or another volatile solid-state storage device. The program and the received data flow of the network slice deployment method according to the embodiments of this application are stored in the memory, and when the program and the received data flow need to be used, the processor <NUM> invokes them from the memory <NUM>.

<FIG> is a schematic structural diagram of a management function entity according to an embodiment of this application. When an integrated unit is used, <FIG> is a possible schematic structural diagram of the management function entity included in the foregoing embodiment. The management function entity <NUM> includes: a processing unit <NUM> and a communications unit <NUM>. The processing unit <NUM> is configured to control and manage an action of the management function entity. For example, the processing unit <NUM> is configured to support the management function entity in performing step <NUM>, step <NUM>, step <NUM>, and step <NUM> in the <FIG>, and/or another process of the technology described in this specification. The communications unit <NUM> is configured to support the management function entity in communicating with another network entity. The management function entity may further include a storage unit <NUM>, configured to store program code and data of the management function entity.

The processing unit <NUM> may be a processor or a controller, for example, may be a central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA), or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in this application. Alternatively, the processor may be a combination implementing a computing function, for example, including a combination of one or more microprocessors, or a combination of the DSP and a microprocessor, or the like. The communications unit <NUM> may be a communications interface, a transceiver, a transceiver circuit, or the like. The communications interface is a general term and may include one or more interfaces, for example, a transceiver interface. The storage unit <NUM> may be a memory.

When the processing unit <NUM> is a processor, the communications unit <NUM> is a communications interface, and the storage unit <NUM> is a memory, the management function entity included in this embodiment of this application may be a management function entity shown in <FIG>.

Referring to <FIG>, the management function entity <NUM> includes: a processor <NUM>, a communications interface <NUM>, and a memory <NUM>. Optionally, the management function entity <NUM> may further include a bus <NUM>. The communications interface <NUM>, the processor <NUM>, and the memory <NUM> are interconnected through the bus <NUM>. The bus <NUM> may be a peripheral component interconnect (peripheral component interconnect, PCI) bus, an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The bus <NUM> may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in <FIG>, but this does not mean that there is only one bus or only one type of bus.

The components of the terminal device are described in detail below with reference to <FIG>.

<FIG> is a block diagram of a partial structure of a terminal device according to an embodiment of this application. Referring to <FIG>, the terminal device includes components such as a radio frequency (radio frequency, RF) circuit <NUM>, a memory <NUM>, an input unit <NUM>, a display unit <NUM>, a sensor <NUM>, an audio circuit <NUM>, a wireless fidelity (wireless fidelity, Wi-Fi) module <NUM>, and a processor <NUM>. A person skilled in the art may understand that the structure of the terminal device shown in <FIG> does not constitute a limitation to the terminal device, and the terminal device may include more components or fewer components than those shown in the figure, or a combination of some components, or a different component arrangement.

The processor <NUM> is a control center of the terminal device. In the embodiments of this application, a network slice may be subscribed to in advance from the operators, and after a network device deploys the network slice for the terminal device to perform an initiated service, the deployed network slice is used to perform the service.

The RF circuit <NUM> is connected to the processor <NUM> through a bus, is responsible for sending data to the Internet or receiving data from the Internet, and may be configured to: receive and send a message or receive and send a signal during a call process, and in particular, send a network slice service request message to a network device. In addition, after receiving a network slice service response message sent by the network device, the RF circuit sends the network slice service response message to the processor <NUM> for processing. Usually, the RF circuit <NUM> includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (low noise amplifier, LNA), a duplexer, and the like. In addition, the RF circuit <NUM> may also communicate with a network and another device through wireless communication. The wireless communication may use any communications standard or protocol, including, but not limited to, a global system for mobile communications (global system of mobile communication, GSM), a general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), long-term evolution (long term evolution, LTE), an email, a short message service (short message service, SMS), and the like.

The memory <NUM> may be configured to store a software program and a module. The processor <NUM> runs the software program and the module that are stored in the memory <NUM>, to perform various functional applications of the terminal device and data processing. The memory <NUM> may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required by at least one function (for example, a function of sending a network slice service request message, or a function of using the network slice to perform a service), and the like. The data storage area may store data (for example, an international mobile subscriber identity, a mobile station integrated services digital network number) created based on use of a mobile terminal, and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may also include a non-volatile memory such as at least one magnetic disk storage component, a flash memory, or another volatile solid-state storage device.

The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedures or functions according to the embodiments of this application are all or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible to the computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive (solid state disk, SSD)), or the like.

Claim 1:
A network slice deployment method, comprising:
receiving (<NUM>, <NUM>), by a network device, a first request message sent by a terminal device, wherein the first request message is used to instruct to deploy a target network slice for providing a target service to the terminal device, and a corresponding management function entity has allocated target network slice information for the target network slice corresponding to the target service, wherein the target network slice is recorded by the management function entity but not deployed to the network device, and wherein the target network slice information is provided to the terminal device;
sending (<NUM>, <NUM>), by the network device, a second request message to the management function entity, wherein the second request message carries the target network slice information, and the second request message is used to instruct the management function entity to deploy the target network slice corresponding to the target network slice information; and
receiving (<NUM>, <NUM>), by the network device, a second response message sent by the management function entity, wherein the second response message is used to indicate that the target network slice has been completely deployed.