# US 12,113,667 B2 · Network slice configuration method, apparatus, and system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,113,667 B2
- Document ID: US12113667B2
- Status: Granted
- Kind: B2
- Application number: 18/228,116
- Filed: 2023-07-31
- Published: 2023-11-23
- Granted: 2024-10-08
- Earliest claimed: 2017-03-24
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Ruiyue Xu; Kai Zhang; Xiaoqian Jia
- Web page: https://patentgrep.com/patent/US12113667B2

## CPC

- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 41/342: between virtual entities, e.g. orchestrators, SDN or NFV entities
- H04W 48/18: Selecting a network or a communication service
- H04W 68/005: {Transmission of information for alerting of incoming communication}
- H04W 72/04: Wireless resource allocation
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

This application provides a network slice configuration method, apparatus, and system, and pertains to the field of wireless communications technologies. The method includes: after receiving a management request of a network slice, obtaining or determining, by a network slice manager, network resource information corresponding to a subnet included in the network slice, and then sending, in a form of a subnet management request to a subnet manager, the network resource information corresponding to the subnet, so that the subnet manager configures the corresponding subnet based on the network resource information corresponding to the subnet. In this application, network slice configuration efficiency can be improved.

## Claims

### Claim 1

A network slice manager, comprising at least one processor, and one or more memories coupled to the at least one processor, wherein the one or more memories are configured to store non-transitory computer-readable instructions, and wherein the at least one processor is configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
determine or obtain transport resource information corresponding to a first subnet comprised in a network slice, wherein the first subnet is an access network (AN) subnet or a core network (CN) subnet, wherein the transport resource information is for configuring a communication connection between the first subnet and a second subnet comprised in the network slice; and
send the transport resource information to a subnet manager, wherein the subnet manager is to configure the first subnet based on the transport resource information.

### Claim 2 (depends on 1)

The network slice manager according to claim 1, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
determine the transport resource information based on requirement information of the network slice.

### Claim 3 (depends on 1)

The network slice manager according to claim 1, wherein the transport resource information comprises at least one of a transport resource type or a transport resource identifier (ID).

### Claim 4 (depends on 3)

The network slice manager according to claim 3,
wherein the transport resource type comprises at least one of a local area network (LAN) type, a virtual LAN (VLAN) type, a virtual extensible LAN (VXLAN) type, a generic routing encapsulation (GRE) type, or a layer-3 virtual private network (L3-VPN) type; or
wherein the transport resource ID comprises at least one of a LAN ID, a VLAN ID, a VXLAN ID, a GRE key, or an L3-VPN ID.

### Claim 5 (depends on 3)

The network slice manager according to claim 3, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
determine the transport resource type based on requirement information of the network slice; or
determine the transport resource identifier.

### Claim 6 (depends on 1)

The network slice manager according to claim 1, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
receive a management request, wherein the management request comprises requirement information of the network slice.

### Claim 7 (depends on 1)

The network slice manager according to claim 1, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
receive a subnet notification message from the subnet manager, wherein the subnet notification message indicates that the first subnet has been configured.

### Claim 8 (depends on 1)

The network slice manager according to claim 1, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
receive the transport resource information; and
configure the communication connection based on the transport resource information.

### Claim 9 (depends on 8)

The network slice manager according to claim 8, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the network slice manager to:
send, after configuring the communication connection, a subnet notification message to the network slice manager, wherein the subnet notification message indicates that the first subnet has been configured.

### Claim 10

A subnet manager, comprising at least one processor, and one or more memories coupled to the at least one processor, wherein the one or more memories are configured to store non-transitory computer-readable instructions, and wherein the at least one processor is configured to execute the non-transitory computer-readable instructions to cause the subnet manager to:
receive transport resource information corresponding to a first subnet comprised in a network slice, wherein the first subnet is an access network (AN) subnet, or a core network (CN) subnet, and the transport resource information corresponding to the first subnet is sent by a network slice manager; and
configure a communication connection between the first subnet and a second subnet comprised in the network slice based on the transport resource information.

### Claim 11 (depends on 10)

The subnet manager according to claim 10, wherein the transport resource information comprises at least one of a transport resource type or a transport resource identifier (ID).

### Claim 12 (depends on 11)

The subnet manager according to claim 11,
wherein the transport resource type comprises at least one of a local area network (LAN) type, a virtual LAN (VLAN) type, a virtual extensible LAN (VXLAN) type, a generic routing encapsulation (GRE) type, or a layer-3 virtual private network (L3-VPN) type; or
wherein the transport resource ID comprises at least one of a LAN ID, a VLAN ID, a VXLAN ID, a GRE key, or an L3-VPN ID.

### Claim 13 (depends on 10)

The subnet manager according to claim 10, wherein the at least one processor is further configured to execute the non-transitory computer-readable instructions to cause the subnet manager to:
send a subnet notification message to the network slice manager to inform that the first subnet has been configured.

### Claim 14

A network slice configuration method, comprising:
determining or obtaining, by a network slice manager, transport resource information corresponding to a first subnet comprised in a network slice, wherein the first subnet is an access network (AN) subnet or a core network (CN) subnet, wherein the transport resource information is for configuring a communication connection between the first subnet and a second subnet comprised in the network slice;
sending, by the network slice manager, the transport resource information to a subnet manager, wherein the subnet manager is to configure the first subnet based on the transport resource information;
receiving, by the subnet manager, the transport resource information; and
configuring, by the subnet manager, the communication connection.

### Claim 15 (depends on 14)

The method according to claim 14, wherein the transport resource information comprises at least one of a transport resource type or a transport resource identifier (ID).

### Claim 16 (depends on 14)

The method according to claim 14, wherein the determining or obtaining of the transport resource information comprises:
determining the transport resource information based on requirement information of the network slice.

### Claim 17 (depends on 15)

The method according to claim 15, wherein the determining or obtaining of the transport resource information comprises at least one of:
determining, by the network slice manager, the transport resource type based on requirement information of the network slice; or
determining, by the network slice manager, the transport resource identifier.

### Claim 18 (depends on 14)

The method according to claim 14, further comprising:
receiving, by the network slice manager, a management request, wherein the management request comprises requirement information of the network slice.

### Claim 19 (depends on 14)

The method according to claim 14, further comprising:
receiving, by the network slice manager, a subnet notification message from the subnet manager, wherein the subnet notification message indicates that the first subnet has been configured.

### Claim 20 (depends on 15)

The method according to claim 15, wherein after the configuring the communication connection, the method further comprises:
sending, by the subnet manager, a subnet notification message to the network slice manager to inform that the first subnet has been configured.
