A method for generating a radio access network slice, a radio access network and a slice manager

Abstract

The patent application discloses a method for generating a radio access network slice, a radio access network and a slice manager. The method comprises: receiving, by the radio access network, a radio access network slice generation request message sent by the slice manager; and generating, by the radio access network, a radio access network slice. The radio access network slice generation request message comprises information of a service type, and the radio access network slice is configured with a protocol stack corresponding to the service type. According to the patent application, different radio access networks do not need to be repeatedly deployed to meet different service types, and operation costs are saved. The radio access network slice can be quickly generated, which is beneficial to the rapid deployment of new services.

Description

[0001] This application is a divisional application. The original application has the application number 201610257629.3 and the original application date is April 23, 2016. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This patent application relates to the field of communications, and more specifically, to a method for generating wireless access network slices, a wireless access network, and a slice manager. Background Technology

[0003] With the rapid development of wireless communication, future wireless communication networks will exhibit a variety of differentiated services coexisting. These services have significantly different performance requirements, with different service types requiring different networks in terms of speed, performance, security, reliability, and latency. For example, multi-party high-definition video services require high bandwidth to provide high service rates, while Narrow Band Internet of Things (NB-IoT) services have lower Quality of Service (QoS) requirements, meaning they do not need very high data rates and extremely low latency, but require high endurance and massive connectivity. Traditional cellular networks use a uniform data processing method to process service data, which cannot provide differentiated services. Future communication systems will need to provide customized services for different types of services. Currently, there is no suitable solution for quickly deploying wireless access networks for different types of services. Summary of the Invention

[0004] This patent application provides a method for generating wireless access network slices, a wireless access network, and a slice manager, thereby enabling rapid deployment of wireless access networks for different types of services.

[0005] Firstly, this patent application proposes a method for generating a radio access network (RAN) slice. The method includes: the RAN receiving a RAN slice generation request message sent by a slice manager; and the RAN generating the RAN slice. The RAN slice generation request message includes service type information, and the RAN slice is configured with a protocol stack corresponding to the service type.

[0006] In this patent application, the Radio Access Network (RAN) generates RAN slices after receiving a RAN slice generation request. The generation request includes the service type, and the RAN slice is configured with a protocol stack corresponding to that service type. Using this patent application, it is unnecessary to repeatedly deploy different RANs to meet different service types, thus saving operating costs. RAN slices can be generated quickly, facilitating the rapid deployment of new services.

[0007] In conjunction with the first aspect, in a first possible implementation of the first aspect, before the radio access network receives the radio access network slice generation request message sent by the slice manager, the method further includes: the radio access network receiving a trigger measurement control message sent by the slice manager, and the radio access network sending a measurement report message to the slice manager. The trigger measurement control message includes trigger conditions, and the measurement report message includes the service type, wherein the service type satisfies the trigger conditions. Through the above technical solution, the establishment of slices can be triggered automatically by the RAN, specifically by the RAN according to the trigger conditions. Due to its real-time nature, resource utilization is improved.

[0008] In a second possible implementation of the first aspect, in conjunction with the first aspect or the first possible implementation of the first aspect, the radio access network slice generation request message further includes: information on quality of service requirements. The generation of the radio access network slice by the radio access network includes: when the available resources of the radio access network are configured with the protocol stack in the radio access network slice and meet the quality of service requirements, the radio access network generates the radio access network slice. Through the above technical solution, the RAN can know the resources required to generate the corresponding RAN slice, and decide whether to generate the corresponding RAN slice based on the available resources, thereby reducing the risk that although the corresponding RAN slice is generated, insufficient resources may prevent the satisfaction of user quality of service.

[0009] In a third possible implementation of the first aspect, in conjunction with the first aspect or any of the above possible implementations of the first aspect, after the radio access network generates the radio access network slice, the method further includes: the radio access network sending system update information to the terminal device. The system update information includes the service type. Through the above technical solutions, the RAN informs the terminal device of the service types supported by the RAN, which helps the terminal device select the appropriate RAN access, thereby improving the throughput of the terminal device and reducing latency.

[0010] In a fourth possible implementation of the first aspect, in conjunction with the first aspect or any of the above possible implementations of the first aspect, before the radio access network generates the radio access network slice, the method further includes: the radio access network sending a radio access network slice access request message to the gateway; and the radio access network receiving a radio access network slice access feedback message sent by the gateway. The radio access network slice access request message includes the service type, and the radio access network slice access feedback message is used to instruct the gateway to allow the radio access network slice to access. Through the above technical solution, a suitable gateway can be selected for the RAN slice to be generated. It also avoids redundant processing caused by creating RAN slices in scenarios where no suitable gateway is available for access.

[0011] In conjunction with the first aspect or any of the above possible implementations of the first aspect, in the fifth possible implementation of the first aspect, the radio access network slice generation request message further includes: information on the radio access network slice generation and retention priority. By setting priorities, in resource-constrained scenarios, the performance of high-priority RAN slices can be guaranteed by releasing low-priority RAN slices, thereby ensuring the quality of service for high-priority users. When creating RAN slices, higher-priority RAN slices can also be created first.

[0012] In a sixth possible implementation of the first aspect, combining any of the first to fifth possible implementations of the first aspect, the RAN slice generation request message further includes: gateway identification information. Through the above technical solutions, if the RAN slice generation request message includes gateway identification information, then when sending the RAN slice access request message, the RAN can send it to a specific gateway, thereby reducing the amount of signaling sent.

[0013] In conjunction with the first aspect or any of the above possible implementations of the first aspect, in the seventh possible implementation of the first aspect, the radio access network slice generation request message further includes the protocol stack information. Through the above technical solution, by including protocol stack information in the RAN slice generation request message, it is possible to obtain the protocol stack corresponding to the service type without resorting to signaling, thereby reducing the amount of signaling sent.

[0014] In conjunction with the first aspect or any of the above possible implementations of the first aspect, in the eighth possible implementation of the first aspect, after the radio access network generates the radio access network slice, the method further includes: the radio access network sending a radio access network slice generation feedback message to the slice manager, the radio access network slice generation feedback message being used to indicate that the radio access network has generated a radio access network slice.

[0015] Secondly, this patent application proposes a method for generating a radio access network (RAN) slice. The method includes: a slice manager sending a RAN slice generation request message to the RAN; and the slice manager receiving a RAN slice generation feedback message sent by the RAN. The RAN slice generation request message contains service type information. The RAN slice generation feedback message indicates that the RAN has generated a RAN slice. The RAN slice is configured with a protocol stack corresponding to the service type.

[0016] In conjunction with the second aspect, in a first possible implementation of the second aspect, before the slice manager sends the radio access network slice generation request message to the radio access network, the method further includes: the slice manager sending a trigger measurement control message to the radio access network; and the slice manager receiving a measurement report message sent by the radio access network. The trigger measurement control message includes a trigger condition. The measurement report message includes the service type, and the service type satisfies the trigger condition.

[0017] In a second possible implementation of the second aspect, in conjunction with the second aspect or the first possible implementation of the second aspect, the radio access network slice generation request message further includes: information on quality of service requirements. The radio access network generating the radio access network slice includes: the radio access network generating the radio access network slice when the available resources of the radio access network are configured with the protocol stack and the quality of service requirements are met.

[0018] In conjunction with the second aspect or any of the above possible implementations of the second aspect, in the third possible implementation of the second aspect, the wireless access network slice generation request message further includes: gateway identification information.

[0019] In conjunction with the second aspect or any of the above possible implementations of the second aspect, in the fourth possible implementation of the second aspect, the radio access network slice generation request message further includes information about the protocol stack.

[0020] Thirdly, this patent application proposes a method for generating a radio access network (RAN) slice. The method includes: a gateway receiving a RAN slice access request message sent by a RAN; and the gateway sending a RAN slice access feedback message to the RAN. The RAN slice access request message contains service type information, and the RAN slice access feedback message is used to instruct the gateway to allow the RAN slice access.

[0021] In conjunction with the third aspect, in the first possible implementation of the third aspect, the wireless access network slice access feedback message includes the context information of the gateway.

[0022] Fourthly, this patent application discloses a wireless access network. The wireless access network includes a transceiver, a memory, and a processor. The memory stores instructions. The processor is connected to both the memory and the transceiver, and executes the instructions to perform the following steps: receiving a wireless access network slice generation request message sent by a slice manager via the transceiver; and generating a wireless access network slice. The wireless access network slice generation request message contains service type information, and the wireless access network slice is configured with a protocol stack corresponding to the service type.

[0023] In conjunction with the fourth aspect, in a first possible implementation of the fourth aspect, the processor, when executing the instructions, further performs the following steps: receiving a trigger measurement control message sent by the slice manager via the transceiver; and sending a measurement report message to the slice manager via the transceiver. The trigger measurement control message contains a trigger condition, and the measurement report message contains the service type, wherein the service type satisfies the trigger condition.

[0024] In conjunction with the fourth aspect or the first possible implementation of the fourth aspect, in the second possible implementation of the fourth aspect, the radio access network slice generation request message further includes: information on quality of service requirements. The processor executes the step of generating the radio access network slice, which includes: when the available resources of the radio access network are configured with the protocol stack in the radio access network slice and meet the quality of service requirements, the processor executes the step of generating the radio access network slice.

[0025] In conjunction with the fourth aspect or any of the above possible implementations of the fourth aspect, in the third possible implementation of the fourth aspect, the processor further performs the following steps when executing the instruction: sending system update information to the terminal device through the transceiver, wherein the system update information includes the service type.

[0026] In conjunction with the fourth aspect or any of the above possible implementations of the fourth aspect, in a fourth possible implementation of the fourth aspect, the processor, when executing the instructions, further performs the following steps: sending a radio access network slice access request message to the gateway via the transceiver; and receiving a radio access network slice access feedback message sent by the gateway via the transceiver. The radio access network slice access request message includes the service type. The radio access network slice access feedback message is used to indicate that the radio access network slice access is permitted.

[0027] In conjunction with the fourth aspect or any of the above possible implementations of the fourth aspect, in the fifth possible implementation of the fourth aspect, the radio access network slice generation request message further includes: information on radio access network slice generation and retention priorities.

[0028] In conjunction with any of the above possible implementations of the fourth aspect, in the sixth possible implementation of the fourth aspect, the wireless access network slice generation request message further includes: gateway identification information.

[0029] In combination with the fourth aspect or any of the above possible implementations of the fourth aspect, among the seven possible implementations of the fourth aspect, the radio access network slice generation request message further includes information about the protocol stack.

[0030] In conjunction with the fourth aspect or any of the above possible implementations of the fourth aspect, in the eighth possible implementation of the first aspect, the processor, when executing the instruction, further performs the following step: sending a radio access network slice generation feedback message to the slice manager through the transceiver.

[0031] Fifthly, this patent application discloses a slice manager. The slice manager includes a transceiver, a memory, and a processor. The memory stores instructions. The processor is connected to both the memory and the transceiver, and is used to execute the instructions to perform the following steps: sending a radio access network (RAN) slice generation request message to the RAN via the transceiver; and receiving a RAN slice generation feedback message sent by the RAN via the transceiver. The RAN slice generation request message contains service type information, and the RAN slice generation feedback message indicates that the RAN has generated a RAN slice. The RAN slice is configured with a protocol stack corresponding to the service type.

[0032] In conjunction with the fifth aspect, in a first possible implementation of the fifth aspect, the processor, when executing the instructions, further performs the following steps: sending a trigger measurement control message to the radio access network via the transceiver; and receiving a measurement report message sent by the radio access network. The trigger measurement control message contains a trigger condition. The measurement report message contains the service type, and the service type satisfies the trigger condition.

[0033] In conjunction with the fifth aspect or the first possible implementation of the fifth aspect, in the second possible implementation of the fifth aspect, the radio access network slice generation request message further includes: information on quality of service requirements.

[0034] In conjunction with the fifth aspect or any of the above possible implementations of the fifth aspect, in the third possible implementation of the fifth aspect, the wireless access network slice generation request message further includes: gateway identification information.

[0035] In combination with the fifth aspect or any of the above possible implementations of the fifth aspect, in the fourth possible implementation of the fifth aspect, the radio access network slice generation request message further includes information about the protocol stack.

[0036] Sixthly, this patent application provides a gateway. The gateway includes a transceiver, a memory, and a processor. The memory stores instructions. The processor is connected to both the memory and the transceiver and is used to execute the instructions to perform the following steps when executing the instructions: receiving a radio access network (RAN) slice access request message sent by a RAN via the transceiver; and sending a RAN slice access feedback message to the RAN via the transceiver. The RAN slice access request message contains service type information. The RAN slice access feedback message instructs the gateway to allow the RAN slice access.

[0037] In conjunction with the sixth aspect, in a first possible implementation of the sixth aspect, the wireless access network slice access feedback message includes the context information of the gateway.

[0038] In a seventh aspect, this patent application also provides a network system comprising the wireless access network of the fourth aspect and the slice manager of the fifth aspect. The network system may also include the gateway of the sixth aspect.

[0039] Eighthly, this patent application discloses a wireless access network. The wireless access network includes a receiving unit and a processing unit. The receiving unit is used to receive a wireless access network slice generation request message sent by a slice manager. The processing unit is used to generate the wireless access network slice. The wireless access network slice generation request message contains service type information. The wireless access network slice is configured with a protocol stack corresponding to the service type.

[0040] In conjunction with the eighth aspect, in a first possible implementation of the eighth aspect, the radio access network further includes: a transmitting unit. The receiving unit is further configured to: receive a trigger measurement control message sent by the slice manager before receiving the radio access network slice generation request message sent by the slice manager. The transmitting unit is further configured to send a measurement report message to the slice manager. The trigger measurement control message includes a trigger condition. The measurement report message includes the service type, and the service type satisfies the trigger condition.

[0041] In conjunction with the first possible implementation of the eighth aspect, in the second possible implementation of the eighth aspect, the radio access network slice generation request message further includes: information on quality of service requirements. The processing unit is further configured to: generate the radio access network slice when the available resources of the radio access network are configured with the protocol stack in the radio access network slice and meet the quality of service requirements.

[0042] In a third possible implementation of the eighth aspect, in conjunction with the eighth aspect or any of the above possible implementations, the sending unit is further configured to send system update information to the terminal device. The system update information includes the service type.

[0043] In conjunction with the eighth aspect or any of the above possible implementations of the eighth aspect, in the fourth possible implementation of the eighth aspect, the sending unit is further configured to: send a radio access network slice access request message to the gateway before the processing unit generates the radio access network slice. The receiving unit is further configured to: receive a radio access network slice access feedback message sent by the gateway. The radio access network slice access request message includes the service type, and the radio access network slice access feedback message is used to instruct the gateway to allow the radio access network slice access.

[0044] In conjunction with the eighth aspect or any of the above possible implementations of the eighth aspect, in the fifth possible implementation of the eighth aspect, the radio access network slice generation request message further includes: information on radio access network slice generation and retention priorities.

[0045] In conjunction with any of the first to fifth possible implementations of the eighth aspect, in the sixth possible implementation of the eighth aspect, the radio access network slice generation request message further includes: gateway identification information.

[0046] In conjunction with the eighth aspect or any of the above possible implementations of the eighth aspect, in the seventh possible implementation of the eighth aspect, the radio access network slice generation request message further includes information about the protocol stack.

[0047] In conjunction with the eighth aspect or any of the above possible implementations of the eighth aspect, in the eighth possible implementation of the eighth aspect, the sending unit is further configured to: after generating the radio access network slice, send a radio access network slice generation feedback message to the slice manager. The radio access network slice generation feedback message is used to indicate that a radio access network slice has been generated.

[0048] Ninthly, this patent application discloses a slice manager. The slice manager includes a sending unit and a receiving unit. The sending unit is configured to send a Radio Access Network (RAN) slice generation request message to a Radio Access Network (RAN). The receiving unit is configured to receive a RAN slice generation feedback message sent by the RAN. The RAN slice generation request message contains service type information. The RAN slice generation feedback message indicates that the RAN has generated a RAN slice. The RAN slice is configured with a protocol stack corresponding to the service type.

[0049] In conjunction with the ninth aspect, in a first possible implementation of the ninth aspect, the sending unit is further configured to: send a trigger measurement control message to the radio access network before sending the radio access network slice generation request message to the radio access network. The receiving unit is further configured to: receive a measurement report message sent by the radio access network. The trigger measurement control message includes a trigger condition. The measurement report message includes the service type, and the service type satisfies the trigger condition.

[0050] In conjunction with the ninth aspect or the first possible implementation of the ninth aspect, in the second possible implementation of the ninth aspect, the radio access network slice generation request message further includes: information on quality of service requirements. The generation of the radio access network slice by the radio access network includes: the radio access network generating the radio access network slice when the available resources of the radio access network configure the protocol stack in the radio access network slice and meet the quality of service requirements.

[0051] In conjunction with the ninth aspect or any of the above possible implementations of the ninth aspect, in the third possible implementation of the ninth aspect, the wireless access network slice generation request message further includes: gateway identification information.

[0052] In conjunction with the ninth aspect or any of the above possible implementations of the ninth aspect, in the fourth possible implementation of the ninth aspect, the radio access network slice generation request message further includes information about the protocol stack.

[0053] Tenthly, this patent application discloses a gateway. The gateway includes a receiving unit and a sending unit. The receiving unit is used to receive a Radio Access Network (RAN) slice access request message sent by a Radio Access Network (RAN). The sending unit is used to send a RNA slice access feedback message to the RNA. The RNA slice access request message contains service type information, and the RNA slice access feedback message is used to instruct the gateway to allow the RNA slice access.

[0054] In conjunction with the tenth aspect, in a first possible implementation of the tenth aspect, the wireless access network slice access feedback message includes the context information of the gateway.

[0055] In its eleventh aspect, this patent application also provides a network system comprising the wireless access network of the eighth aspect and the slice manager of the ninth aspect. The network system may also include the gateway of the tenth aspect.

[0056] The wireless access network slice generation method, wireless access network, and slice manager disclosed in this patent application can enable rapid deployment of wireless access networks for different types of services. Attached Figure Description

[0057] To more clearly illustrate the technical solutions of the embodiments of this patent application, the drawings used in the embodiments of this patent application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this patent application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 This is a schematic diagram of the architecture of a network system according to one embodiment of this patent application.

[0059] Figure 2 This is a schematic diagram of the architecture of a network system according to another embodiment of this patent application.

[0060] Figure 3 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application.

[0061] Figure 4 This is a schematic diagram of a wireless access network slice generation decision process according to another embodiment of this patent application.

[0062] Figure 5 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application.

[0063] Figure 6 This is a schematic diagram of a network architecture according to another embodiment of this patent application.

[0064] Figure 7 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application.

[0065] Figure 8 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application.

[0066] Figure 9 This is a schematic diagram of a wireless access network according to another embodiment of this patent application.

[0067] Figure 10 This is a processing schematic diagram of a processor for a wireless access network according to another embodiment of this patent application.

[0068] Figure 11 This is a schematic diagram of a slice manager according to another embodiment of this patent application.

[0069] Figure 12 This is a schematic diagram of a gateway according to another embodiment of this patent application.

[0070] Figure 13 This is a schematic diagram of a wireless access network according to another embodiment of this patent application.

[0071] Figure 14 This is a schematic diagram of a slice manager according to another embodiment of this patent application.

[0072] Figure 15 This is a schematic diagram of a gateway according to another embodiment of this patent application. Detailed Implementation

[0073] The technical solutions of the embodiments of this patent application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this patent application, not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this patent application without inventive effort should fall within the scope of protection of this patent application.

[0074] In this patent application, the terminal device may also be referred to as a user unit, user station, mobile station, mobile station, remote station, remote terminal device, mobile device, user terminal device, wireless communication device, user agent, user apparatus, or user equipment (UE). The terminal device may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device, or other processing device connected to a wireless modem.

[0075] In this patent application, the Radio Access Network (RAN) can be used to communicate with mobile terminal devices, and the RAN may include base stations. The base station may be a Base Transceiver Station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an Evolutionary Node B (eNB) in Long Term Evolution (LTE), a relay station or access point, or base station equipment in future communication networks, etc.

[0076] Figure 1 This is a schematic diagram of the architecture of a network system according to one embodiment of this patent application. Figure 1 As shown, the network system includes a first core network 103, a first RAN 101, a first interface 102, a second core network 105, a second interface 106, and a second RAN 107. The first core network 103 and the first RAN 101 are connected through the first interface 102 and jointly serve a first service. The second core network 105 and the second RAN 107 are connected through the second interface 106 and jointly serve a second service.

[0077] For example, the first service could be an MBB service, with the first interface 102 corresponding to the S1 interface, and the first RAN 101 potentially including existing LTE base stations. The second service could be an NB-IoT service, with the second interface 106 corresponding to the S1-lite interface, and the second RAN 107 potentially including new NB-IoT base stations. The S1-lite interface is simplified compared to the S1 interface. For instance, in the control plane, the S1-lite interface only needs to support simplified control procedures, and in the user plane, the S1-lite interface does not need to support the establishment of dedicated data bearers.

[0078] use Figure 1 The architecture shown requires redundant hardware deployment to accommodate different service types, including redundant RAN and core network deployments. Extensive hardware deployment increases equipment and operational costs. Furthermore, it is time-consuming and hinders the rapid deployment of new services.

[0079] Figure 2 This is a schematic diagram of the architecture of a network system according to another embodiment of this patent application. Figure 2 As shown, the network system includes RAN201 and core network 211. Terminal device 209 connects to RAN201 via wireless access. Core network 211 includes a first gateway 203, a second gateway 205, and a slice manager 207. Slice manager 207 is connected to the first gateway 203 and the second gateway 205 respectively. The core network can provide authentication, routing, and billing functions for terminal devices connected to RAN201.

[0080] In one scenario, core network 211 may include a first core network slice and a second core network slice. The first core network slice serves a first service. The second core network slice serves a second service. The first service may be Mobile Broadband (MBB) service. The second service may be NB-IoT service. These service types are merely illustrative and not intended to be limiting. A core network slice includes a series of network functions and the resources required to operate these functions. These network functions can provide the necessary core network functions such as security authentication and authorization for the corresponding services. First gateway 203 corresponds to the first core network slice, and second gateway 205 corresponds to the second core network slice. RAN 201 and first gateway 203 can be connected via first interface 202, which may be an S1 interface. RAN 201 and second gateway 207 are connected via second interface 206, which may be an S1-lite interface.

[0081] The slice manager 207 is connected to RAN 201 and controls the generation of slices in RAN 201. For example, slice manager 207 can control RAN 201 to generate a first RAN slice to provide a first service to the terminal device. The generated first RAN slice is connected to the first gateway 203 through the first interface 202. If the first service is an MBB service, the first interface 202 is an S1 interface. Slice manager 207 can also control RAN 201 to generate a second RAN slice to provide a second service to the terminal device. The generated second RAN slice is connected to the second gateway 205 through the second interface 206. If the second service is an NB-IoT service, the second interface 206 is an S1-lite interface. Each RAN slice can contain at least one shareable processing unit, which can be assigned corresponding protocol stack functions to provide customized services.

[0082] The slice manager 207 can also have other names, such as network manager. Any network device used to control the generation of slices in RAN201 can be considered a slice manager. The slice manager 207 is connected to the first gateway 203 and the second gateway 205 respectively, and can exchange information. Through the first gateway 203, the slice manager 207 can obtain information about the core network slice corresponding to the first gateway 203. Through the second gateway 205, the slice manager 207 can obtain information about the core network slice corresponding to the second gateway 205.

[0083] Figure 3 This is an interactive schematic diagram of a method for generating a Radio Access Network (RAN) slice, according to another embodiment of this patent application. The method of this embodiment can be applied in scenarios where the network needs to generate a new RAN slice, or in scenarios where RAN slice generation is periodically triggered. Figure 3 As shown, the method includes the following steps:

[0084] 301. The slice manager sends a RAN slice generation request message to the Radio Access Network (RAN). The RAN receives the RAN slice generation request message. This message contains service type information. The RAN slice generation request message indicates that a RAN slice corresponding to the service type needs to be generated. In this embodiment, the message may also contain protocol stack information, which corresponds to the service type. Step 301 can be triggered during RAN initialization configuration or triggered periodically.

[0085] 302. The RAN makes a RAN slice generation decision. The specific decision-making process will be explained in more detail below. If the RAN decides to generate a new slice, then continue with the following steps.

[0086] 303. The RAN sends a RAN slice access request message to the gateway. The gateway receives the RAN slice access request message. This message contains service type information, which the gateway uses to determine whether to accept RAN slice access. This message may also contain RAN context information, such as the E-UTRAN CellGlobal Identifier (ECGI) and tracking area code.

[0087] 304. After receiving the RAN slice access request message, the gateway determines whether to allow RAN slice access. For example, it can determine whether to allow RAN slice access based on the service type contained in the RAN slice access request message. If the service type is not supported by the core network slice corresponding to the gateway, RAN access is rejected. Conversely, if the service type is supported by the core network corresponding to the gateway, RAN access is allowed. The gateway sends RAN slice access feedback information to the RAN, and the RAN receives the RAN slice access feedback information. The slice access feedback information may contain the gateway's context information. The gateway's context information may contain access capability information, which is used by the RAN to select a gateway. The RAN prioritizes gateways with strong access capabilities for access. The gateway's context information may also contain gateway identification information, such as the gateway ID.

[0088] 305. After receiving RAN slice access feedback information, the RAN generates RAN slices. There are several specific implementation methods. For example, the RAN may contain multiple sub-functional modules. Based on the protocol stack type corresponding to the RAN slice, the RAN combines these sub-functional modules in different ways to form a protocol stack processing module corresponding to that protocol stack, thus logically generating different RAN slices. The generated RAN slice is configured with the protocol stack corresponding to the service type.

[0089] 306. After generating a RAN slice, the RAN sends a RAN slice generation feedback message to the slice manager. The RAN slice generation feedback message indicates that the RAN has generated a RAN slice corresponding to the service type. This message may also contain gateway ID information, allowing the slice manager to understand the gateways currently connected to the RAN slice and the service types supported by the core network slice corresponding to that gateway.

[0090] 307. The RAN sends system update information to the terminal equipment, and the terminal equipment receives the system update information. This information includes the service type, which indicates the types of services supported by the RAN.

[0091] There is no requirement for the order of steps 306 and 307. You can perform step 306 first and then step 307, or step 307 first and then step 306, or perform steps 306 and 307 simultaneously, as needed.

[0092] In section 301, the RAN slice generation request message can also include gateway identification information (e.g., ID information). If the RAN slice generation request message includes gateway ID information, the RAN can send the request to that gateway when sending the RAN slice access request message in section 303. If it does not include gateway ID information, the RAN needs to send the request information to all gateways except the currently connected gateway. Including gateway information reduces the amount of signaling sent.

[0093] In Section 301, the RAN slice generation request message can also include Quality of Service (QoS) information. QoS information indicates the QoS requirements corresponding to a service type, enabling the RAN to calculate the resources needed to configure a protocol stack within the RAN slice and meet the QoS requirements. The RAN can decide whether to create a RAN slice based on its own resource usage. The RAN only generates a RAN slice if a protocol stack is configured within the RAN slice and the QoS requirements are met. Available RAN resources can include idle RAN resources.

[0094] In Section 301, the RAN slice creation request message can also include RAN Slice Establish and Retention Priority (RERP) information. RERP serves several purposes: First, it determines which specific RAN slice creation request the RAN should accept or reject under resource constraints, accepting requests in the order of highest priority. For example, if the RAN receives multiple RAN slice creation requests simultaneously, it will accept the highest priority request first and allocate resources to it. Second, RERP determines which specific RAN slice the RAN should release under resource constraints, releasing slices in the order of lowest priority. For example, if RAN resources are limited, it will release the lowest priority RAN slice. RERP prioritizes the quality of service (QoS) of high-priority services and high-value users under resource constraints, maximizing network benefits.

[0095] Figure 4 This is a schematic diagram of the RAN slice generation decision process according to another embodiment of this patent application. Figure 4As shown, the specific process can be as follows: The RAN first calculates the resource quantity A required to generate the first RAN slice based on the QoS information and protocol stack type information in the RAN slice generation request. If the amount of idle resources B in the RAN is not less than the resource quantity A, the RAN decides to generate a new first RAN slice. If the resource quantity B is less than the resource quantity A, it further determines whether there is at least one second RAN slice with a lower RERP than the first RAN slice. If such a second RAN slice exists and the sum of the resource quantity C obtained by releasing the second RAN slice and the idle resource quantity B is not less than the resource quantity A, the RAN decides to generate a new first RAN slice. If no second RAN slice exists or the sum of the resource quantity C obtained by releasing the second RAN slice and the idle resource quantity B is less than the resource quantity A, the RAN decides not to generate a new first RAN slice. The criterion used for the above RAN slice generation decision is the resource quantity. In this case, the available resources of the RAN can include idle resources and resources that can be released on the RAN.

[0096] It is worth noting that RAN slice generation decisions can also employ other criteria, such as energy consumption. For example, the RAN calculates the additional energy consumption X required to generate the first RAN slice based on the QoS information and protocol stack type in the RAN slice generation request. If the additional energy consumption X is less than the specified upper limit energy consumption Y (where energy consumption Y can be set by the slice manager), the RAN decides to generate the first RAN slice; otherwise, it rejects the generation of the first RAN slice. RAN slice generation decisions can also use operating expenses (OPEX) as a criterion.

[0097] In this patent application, the service type can include service types, such as MBB services, NB-IoT services, and other services. The service type can also include operator type and service type. Within different service types, if the service types are different, the corresponding RAN slices will use different protocol stack types. The operator type can reflect isolation; in this case, the service types can be different or the same. The operator can be a virtual operator (MVNO). For example, Tencent might require a dedicated RAN slice to provide services for QQ Video, while Apple might require a dedicated RAN slice to provide services for FaceTime; their service types are the same, but their operator types are different.

[0098] RAN slicing enables the functionality of a radio access network, providing communication services for specific purposes. One or more RAN slices can be generated on a single RAN. Each RAN slice is configured with a protocol stack corresponding to its service type. Different RAN slices can have different protocol stack processing flows. The RAN is a physical entity, while RAN slices can be logical concepts. RAN slices configured with a specific protocol stack can use specific resources. Resources can include processing resources and / or transmission resources. Processing resources can be represented in the form of processors, and transmission resources can be represented in the form of air interface time-frequency resources.

[0099] A protocol stack refers to the sum of all protocols at each layer in a network. For a RAN slice, its configured protocol stack can include at least one of the following layers: Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, and Packet Data Convergence Protocol (PDCP) layer.

[0100] For example, for Mobile Broadband (MBB) services, the corresponding first RAN slice can be configured with a first protocol stack. Accordingly, the first RAN slice can include a first protocol stack processing module, which includes a PDCP sub-functional module, an RLC sub-functional module, a MAC sub-functional module, and a PHY sub-functional module. The PDCP sub-functional module can be used for data header compression and decompression, and security control, etc. The RLC sub-functional module can be used for data segmentation and concatenation. The MAC sub-functional module can be used for scheduling, multiplexing / demultiplexing, and supporting multicast services. The PHY sub-functional module can be used for channel encoding / decoding and modulation / demodulation.

[0101] For NB-IoT services, the corresponding second RAN slice can be configured with a second protocol stack. Accordingly, the second RAN slice may include a second protocol stack processing module, which includes a MAC sub-function module and a PHY sub-function module. The MAC and PHY sub-function modules in the second protocol stack processing module may differ from those in the first protocol stack processing module. For example, the MAC sub-function module in the second protocol stack processing module may not include multicast functionality.

[0102] Figure 5 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application. Figure 5 As shown, the method includes the following steps:

[0103] 501. The slice manager sends a triggered measurement control message to the radio access network (RAN), which receives the message. The triggered measurement control message carries trigger conditions. These conditions instruct the RAN to send a measurement report to the slice manager if the trigger conditions are met.

[0104] 502. After receiving the trigger measurement control message, if the triggering conditions are met, the RAN sends a RAN slice measurement report message to the slice manager. This message contains the service type. The service type meets the triggering conditions.

[0105] 503-509 are basically the same as 301-307.

[0106] In trigger measurement control messages, the triggering conditions can differ for different service types. For example, for MBB services, the triggering condition could be that the performance of MBB services connected to the default slice falls below a certain threshold. This performance could be throughput and / or latency. For NB-IoT services, the triggering condition could be that the number of machine-type communication (MTC) terminal devices connected to the default slice reaches a certain threshold.

[0107] In this embodiment, a default RAN slice may exist pre-existing on the RAN. The default RAN slice can provide services for multiple service types to a certain extent. When a terminal device accesses the network, if its service type does not have a corresponding dedicated RAN slice, and the default slice supports that service type, the terminal device will first be served in the default slice until a dedicated RAN slice corresponding to its service type is generated, at which point it will be transferred to the dedicated RAN slice. There may be multiple default slices, which can be specifically configured... Figure 3 The illustrated embodiment was established. (By...) Figure 3 When establishing the example shown, the service type in the RAN slice generation request message can be set to the service type of the default slice.

[0108] In this embodiment, the RAN slice establishment is for an event-triggered scenario. Through steps 501 and 502, the RAN can automatically trigger slice establishment, for example, based on its own resource usage and real-time load conditions. This real-time nature improves resource utilization.

[0109] Figure 6 This is a schematic diagram of a network system according to another embodiment of this patent application. Figure 6As shown, a network system includes a RAN 601 and a core network 611. Terminal devices 609 are connected to the RAN 601 via wireless access. The core network 611 includes a first gateway 603, a second gateway 605, a slice manager 607, and a software-defined protocol controller (SDPC) 609. The slice manager 607 is connected to the first gateway 603 and the second gateway 605, respectively. The core network can provide authentication, routing, and billing functions for terminal devices connected to the RAN 601.

[0110] In one scenario, the core network 611 may include a first core network slice and a second core network slice. The first core network slice provides a first service. The second core network slice provides a second service. A first gateway 603 corresponds to the first core network slice, and a second gateway 605 corresponds to the second core network slice. RAN 601 and the first gateway 603 can be connected via a first interface 602. RAN 601 and the second gateway 607 are connected via a second interface 606.

[0111] The slice manager 607 is connected to RAN 601 and is used to control the generation of slices for RAN 601. SDPC 609 is used to configure the protocol stacks of different RAN slices. SDPC 609 stores the mapping between service types and RAN slice protocol stacks. Based on the received service type information, SDPC 609 can feed back the corresponding protocol stack type to the RAN. Figure 6 Zhongyu Figure 2 For similarities, please refer to the information about Figure 2 The details of that will not be repeated here.

[0112] Figure 7 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application. Figure 7 As shown, the method includes the following steps:

[0113] 701. The slice manager sends a RAN slice generation request message to the RAN. The RAN receives the RAN slice generation request message. This message contains service type information. The service type information indicates that a RAN slice corresponding to the service type needs to be generated.

[0114] 702. After receiving the RAN slice generation request message, the RAN sends a protocol request message to the SDPC. The SDPC receives the protocol request message. The protocol request message contains information about the service type.

[0115] 703. After receiving a protocol request message, the SDPC determines the protocol stack type corresponding to the service type based on the service type information in the message. The SDPC can determine the protocol stack type based on the correspondence between service types and RAN slice protocol stacks. The SDPC sends a protocol stack request feedback message to the RAN. The RAN receives the protocol stack request feedback message. This message contains: the protocol stack type.

[0116] 704-709 are basically the same as 302-307.

[0117] In this embodiment, the RAN slice generation request message does not need to carry the protocol stack type. Instead, the protocol stack type corresponding to the service type is obtained through steps 702 and 703.

[0118] Figure 8 This is an interactive schematic diagram of a method for generating wireless access network slices according to another embodiment of this patent application. Figure 8 As shown, the method includes the following steps:

[0119] 801 is basically the same as 501.

[0120] 802 is basically the same as 502.

[0121] 803-811 are basically the same as 701-709.

[0122] The foregoing mainly describes the solutions provided by the embodiments of the present invention from the perspective of interaction between various network elements. It is understood that each network element, in order to achieve the above functions, includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the embodiments disclosed herein, this patent application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this patent application.

[0123] This patent application further provides apparatus embodiments for implementing the steps and methods in the above-described method embodiments. It is worth noting that the apparatus embodiments can be used in conjunction with the above-described methods, or they can be used independently.

[0124] Figure 9 A schematic diagram of a possible structure of the wireless access network involved in the above embodiments is shown. For example... Figure 9As shown, the radio access network 900 includes a transceiver 901, a memory 902, and a processor 903. The memory 902 stores instructions. The processor 903 is connected to both the memory 902 and the transceiver 901, and is used to execute instructions, performing the following steps during instruction execution: receiving a radio access network slice generation request message sent by the slice manager via the transceiver 901; and generating a radio access network slice. The radio access network slice generation request message contains service type information, and the radio access network slice is configured with the protocol stack corresponding to the service type.

[0125] Optionally, the processor 903, when executing instructions, also performs the following steps: receiving a trigger measurement control message sent by the slice manager via transceiver 901; and sending a measurement report message to the slice manager via transceiver 901. The trigger measurement control message contains trigger conditions, and the measurement report message contains service types, wherein the service type satisfies the trigger conditions.

[0126] Optionally, the radio access network slice generation request message also includes: information on quality of service requirements. Processor 903 executes the step: generating a radio access network slice, including: available resources of the radio access network. If the radio access network slice is configured with a protocol stack and meets the quality of service requirements, processor 903 executes the step: generating a radio access network slice.

[0127] Optionally, when executing instructions, the processor 903 also performs the following steps: sending system update information to the terminal device via transceiver 901, the system update information including the service type.

[0128] Optionally, the processor 903, when executing instructions, further performs the following steps: sending a Radio Access Network (RAN) slice access request message to the gateway via transceiver 901; and receiving a RAN slice access feedback message sent by the gateway via transceiver 901. The RAN slice access request message contains the service type. The RAN slice access feedback message is used to indicate that RAN slice access is permitted.

[0129] Optionally, the processor 903 also performs the following steps when executing instructions: sending a radio access network slice generation feedback message to the slice manager via transceiver 901.

[0130] Alternatively, the transceiver 901 and memory 902 can be directly connected to the processor 903. Or as... Figure 9 As shown, transceiver 901, memory 902 are connected to bus 904, and processor 903 is also connected to bus 904.

[0131] In one embodiment, transceiver 901 may include a first communication interface, a second communication interface, a third communication interface, and a fourth communication interface (not fully shown in the figure). The first communication interface is used for communication with a terminal device, specifically receiving and / or sending information to the terminal device. Communication between the first communication interface and the terminal device is wireless. The second communication interface is used for communication with a gateway, specifically receiving and / or sending information to the gateway. Communication between the second communication interface and the gateway can be wired or wireless. The third communication interface is used for communication with a slice manager, specifically receiving and / or sending information to the slice manager. Communication between the third communication interface and the slice manager can be wired or wireless. The fourth communication interface is used for communication with an SDPC, specifically receiving and / or sending information to the SDPC. Communication between the fourth communication interface and the SDPC can be wired or wireless. The first, second, third, and fourth communication interfaces may be physically independent, or they may be partially or completely integrated physically. The second communication interface may include multiple independent communication interfaces, each of which can enable communication between different RAN slices and their corresponding gateways.

[0132] Different RAN slices can use isolated and orthogonal time-frequency resources for transmission over the air interface. For example, the first RAN slice can use the 10-20 MHz frequency domain for transmission, while the second RAN slice can use the 30-40 MHz frequency domain resources. Alternatively, different RAN slices can share the same frequency domain resources but be distinguished through scheduling.

[0133] like Figure 10 As shown, processor 903 may include a slice generation decision module, a protocol stack configuration module, a first sub-functional module, a second sub-functional module, a third sub-functional module, and a fourth sub-functional module. The number of the first, second, third, and fourth sub-functional modules can be one or more. The above example illustrates the case with four sub-functional modules. The number of each sub-functional module can also vary; for example, there may be one or more first sub-functional modules.

[0134] The slice generation decision module is used to execute slice generation decisions. When it determines that a RAN slice needs to be generated, it notifies the protocol stack configuration module. After receiving the notification, the protocol stack configuration module combines the sub-functional modules within the RAN according to the protocol stack corresponding to the RAN slice to generate the RAN slice corresponding to that protocol stack.

[0135] For example, such as Figure 10 As shown, when the RAN needs to generate a first RAN slice with a first protocol stack configured, the protocol stack configuration module selects and combines the corresponding first, second, third, and fourth sub-functional modules based on the first protocol stack to obtain the first protocol stack functional module. When the RAN needs to generate a second RAN slice with a second protocol stack configured, the protocol stack configuration module selects and combines the corresponding second and third sub-functional modules based on the second protocol stack to obtain the second protocol stack functional module. When the RAN needs to generate a third RAN slice with a third protocol stack configured, the protocol stack configuration module selects and combines the corresponding third and fourth sub-functional modules based on the first protocol stack to obtain the third protocol stack functional module. Multiple protocol stack functional modules may exist on a single RAN. In one embodiment, the first, second, third, and fourth sub-functional modules can be a PDCP sub-functional module, an RLC sub-functional module, a MAC sub-functional module, and a PHY sub-functional module, respectively.

[0136] Figure 11 A schematic diagram of a possible structure of the slice manager involved in the above embodiments is shown. For example... Figure 11 As shown, the slice manager 1100 includes a transceiver 1101, a memory 1102, and a processor 1103. The memory 1102 stores instructions. The processor 1103 is connected to both the memory 1102 and the transceiver 1101, and is used to execute the instructions to perform the following steps: sending a radio access network (RAN) slice generation request message to the RAN via the transceiver 1101; and receiving a RAN slice generation feedback message sent by the RAN via the transceiver 1101. The RAN slice generation request message contains service type information, and the RAN slice generation feedback message indicates that the RAN has generated a RAN slice. The RAN slice configures the protocol stack corresponding to the service type.

[0137] Optionally, the processor 1103, when executing instructions, also performs the following steps: sending a trigger measurement control message to the radio access network via transceiver 1101; and receiving a measurement report message sent by the radio access network. The trigger measurement control message contains trigger conditions. The measurement report message contains a service type, and the service type satisfies the trigger conditions.

[0138] Alternatively, the transceiver 1101 and memory 1102 can be directly connected to the processor 1103. Or as... Figure 11 As shown, transceiver 1101, memory 1102 are connected to bus 1104, and processor 1103 is also connected to bus 1104.

[0139] Figure 12 A possible structural diagram of the gateway involved in the above embodiments is shown. For example... Figure 12 As shown, the gateway 1200 includes a transceiver 1201, a memory 1202, and a processor 1203. The memory 1202 stores instructions. The processor 1203 is connected to both the memory 1202 and the transceiver 1201, and is used to execute instructions to perform the following steps: receiving a Radio Access Network (RAN) slice access request message from the RAN via the transceiver 1201; and sending a RAN slice access feedback message to the RAN via the transceiver 1201. The RAN slice access request message contains service type information. The RAN slice access feedback message instructs the gateway to allow RAN slice access.

[0140] Alternatively, the transceiver 1201 and memory 1202 can be directly connected to the processor 1203. Or as... Figure 12 As shown, transceiver 1201, memory 1202 are connected to bus 1204, and processor 1203 is also connected to bus 1204.

[0141] Figure 13 A schematic diagram of a possible structure of the wireless access network involved in the above embodiments is shown. For example... Figure 13 As shown, the radio access network 1300 includes a receiving unit 1320 and a processing unit 1330. The receiving unit 1320 and the processing unit 1330 are connected. The receiving unit 1320 receives a radio access network slice generation request message sent by the slice manager. The processing unit 1330 generates a radio access network slice. The radio access network slice generation request message contains service type information. The radio access network slice is configured with the protocol stack corresponding to the service type.

[0142] Optionally, the radio access network further includes a transmitting unit 1310. The receiving unit 1320 is further configured to receive a trigger measurement control message sent by the slice manager before receiving the radio access network slice generation request message sent by the slice manager. The transmitting unit 1310 is also configured to send a measurement report message to the slice manager. The trigger measurement control message contains trigger conditions. The measurement report message contains a service type, and the service type satisfies the trigger conditions.

[0143] Optionally, the radio access network slice generation request message also includes information on quality of service requirements. Processing unit 1330 is further configured to generate a radio access network slice when the available resources of the radio access network are configured with a protocol stack in the radio access network slice and meet the quality of service requirements.

[0144] Optionally, the sending unit 1310 is also used to send system update information to the terminal device. The system update information includes the service type.

[0145] Optionally, the sending unit 1310 is further configured to: send a radio access network slice access request message to the gateway before the processing unit 1330 generates a radio access network slice. The receiving unit 1320 is further configured to: receive a radio access network slice access feedback message sent by the gateway. The radio access network slice access request message contains a service type, and the radio access network slice access feedback message is used to instruct the gateway to allow radio access network slice access.

[0146] Optionally, the sending unit 1310 is further configured to: send a radio access network (RAN) slice generation feedback message to the slice manager after generating a RAN slice. The RAN slice generation feedback message is used to indicate that a RAN slice has been generated.

[0147] Figure 14 A schematic diagram of a possible structure of the slice manager involved in the above embodiments is shown. For example... Figure 14 As shown, the slice manager 1400 includes a sending unit 1410 and a receiving unit 1420. The sending unit 1410 is used to send a Radio Access Network (RAN) slice generation request message to the RANTO (Radio Access Network). The receiving unit 1420 is used to receive a RANTO slice generation feedback message sent by the RANTO. The RANTO slice generation request message contains service type information. The RANTO slice generation feedback message indicates that the RANTO has generated a RANTO slice. The RANTO slice configures the protocol stack corresponding to the service type.

[0148] Optionally, the sending unit 1410 is further configured to: send a trigger measurement control message to the radio access network before sending the radio access network slice generation request message to the radio access network. The receiving unit 1420 is further configured to: receive a measurement report message sent by the radio access network. The trigger measurement control message contains trigger conditions. The measurement report message contains a service type, and the service type meets the trigger conditions.

[0149] Optionally, the Radio Access Network (RAN) slice generation request message also includes: information on Quality of Service (QoS) requirements. The RAVN generates a RAVN slice, provided that the available resources of the RAVN are configured with a protocol stack that meets the QoS requirements.

[0150] Optionally, the slice processor 1400 may further include a processing unit 1430, which is connected to the transmitting unit 1410 and the receiving unit 1420 respectively. The processing unit 1430 is used to process signals and control the transmitting unit 1410 and the receiving unit 1420.

[0151] Figure 15 A possible structural diagram of the gateway involved in the above embodiments is shown. For example... Figure 15As shown, the gateway 1500 includes a receiving unit 1520 and a sending unit 1510. The receiving unit 1520 receives a Radio Access Network (RAN) slice access request message sent by the RANTO (Radio Access Network). The sending unit 1510 sends a RANTO slice access feedback message to the RANTO. The RANTO slice access request message contains service type information, and the RANTO slice access feedback message instructs the gateway to allow RANTO slice access.

[0152] Optionally, the gateway 1500 may further include a processing unit 1530, which is connected to the transmitting unit 1510 and the receiving unit 1520 respectively. The processing unit 1530 is used to process signals and control the transmitting unit 1510 and the receiving unit 1520.

[0153] In this patent application, multiple RAN slices can be generated within a single RAN based on service type, enabling customized services for different service types. This avoids the high costs and lengthy hardware and software upgrades associated with deploying different RANs for different service types. This effectively reduces operating and equipment costs and shortens service deployment cycles. Furthermore, this patent application allows for real-time adjustments to the resource deployment of RAN slices based on changes in different service loads within the RAN, specifically meeting diverse service needs. Flexible resource allocation improves network performance.

[0154] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0155] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] In addition, the functional units in the various embodiments of this patent application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0157] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this patent application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and contains several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this patent application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0158] The above are merely specific embodiments of this patent application, but the scope of protection of this patent application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this patent application should be included within the scope of protection of this patent application. Therefore, the scope of protection of this patent application shall be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Include: The wireless access network receives a wireless access network slice generation request message from the slice manager. The wireless access network slice generation request message contains information about the service type and protocol stack information. The wireless access network sends a wireless access network slice access request message to the gateway, and the wireless access network slice access request message includes the service type; The wireless access network receives a wireless access network slice access feedback message from the gateway, the wireless access network slice access feedback message being used to instruct the gateway to allow the wireless access network slice access; The wireless access network generates a wireless access network slice, and the wireless access network slice is configured with the protocol stack corresponding to the service type; The wireless access network sends a wireless access network slice generation feedback message to the slice manager, the wireless access network slice generation feedback message being used to indicate that the wireless access network has generated a wireless access network slice corresponding to the service type; the wireless access network sends system update information to the terminal device, the system update information including service types supported by the wireless access network.

2. The communication method as described in claim 1, characterized in that, The method further includes: The wireless access network receives a trigger measurement control message from the slice manager, the trigger measurement control message containing trigger conditions; and The wireless access network sends a measurement report message to the slice manager. The measurement report message contains the service type, and the service type satisfies the triggering condition.

3. The communication method as described in claim 1 or 2, characterized in that, The wireless access network slice generation request message also includes information on quality of service requirements.

4. A wireless access network, characterized in that... Include: transceiver; Memory, used to store instructions; and A processor, connected to both the memory and the transceiver, is configured to execute the instructions, and in executing the instructions, perform the following steps: Receive a radio access network slice generation request message from the slice manager, the radio access network slice generation request message containing service type information and protocol stack information; Send a radio access network slice access request message to the gateway, wherein the radio access network slice access request message includes the service type; Receive a radio access network slice access feedback message from the gateway, the radio access network slice access feedback message being used to instruct the gateway to allow the radio access network slice access; Generate a wireless access network slice, wherein the wireless access network slice is configured with the protocol stack corresponding to the service type; Send a radio access network slice generation feedback message to the slice manager. The radio access network slice generation feedback message is used to indicate that the radio access network has generated a radio access network slice corresponding to the service type. Send system update information, which includes information indicating the types of services supported by the radio access network.

5. The wireless access network as described in claim 4, characterized in that: The processor also performs the following steps when executing the instruction: Receive a trigger measurement control message sent by the slice manager, the trigger measurement control message containing trigger conditions; and Send a measurement report message, the measurement report message containing the service type, the service type satisfying the triggering condition.

6. The wireless access network as described in claim 4 or 5, characterized in that: The wireless access network slice generation request message also includes information on quality of service requirements.

Images