WO2021056449A1

WO2021056449A1 - Session switching method, apparatus and related device

Info

Publication number: WO2021056449A1
Application number: PCT/CN2019/108655
Authority: WO
Inventors: 杨水根; 韩锋; 晋英豪; 谭巍
Original assignee: 华为技术有限公司
Priority date: 2019-09-27
Filing date: 2019-09-27
Publication date: 2021-04-01

Abstract

The embodiment of the present application provides a session switching method, apparatus and related device, wherein, a first access network device may receive a first message from a second access network device, and the first message is used to request to switch a session of protocol data unit from the second access network device to the first access network device. When the request of the switching is rejected by the first access network, a second message indicating the reason for the failure of session switching of protocol data unit is transmitted from the first access network device to the second access network device. The first access network device transmits the reason for the failure of the session switching of the protocol data unit to the second access network device. Thus, the second access network device may determine whether to initiate a session switching next time, referring to the reason for the failure of the session switching received from the first access network device. In this way, the probability of success of session switching of the protocol data unit is improved.

Description

Method, device and related equipment for session switching

Technical field

This application relates to the field of communications, and in particular to a session switching method, device and related equipment.

Background technique

As a key technology of the future 5th generation (5G) communication system, network slicing can meet the customization needs of operators for various industries, vertical markets, and various virtual operation services. Network slicing refers to the logical division of a physical network into multiple virtual networks, and each virtual network corresponds to a network slice. Among them, the network slicing can be divided according to the service requirements of different users, for example, according to indicators such as latency, bandwidth, and reliability, so as to cope with complex and changeable application scenarios. For an access network formed by a base station, a base station may include one or more cells, and each cell may support one or more network slices. When user equipment (UE) is handed over from the cell in the source base station (called the source cell) to the cell in the target base station (called the target cell), if the number of UEs served by the network slice in the target cell has reached or exceeded The maximum number of UEs that the network slice can support, and the number of protocol data unit (PDU) sessions served by the network slice in the target cell has reached or exceeded any one of the maximum number of PDU sessions that the network slice can support When this situation occurs, the target cell will reject the UE's access, resulting in UE handover failure. Then, how to improve the handover success rate of the UE in the next handover becomes a problem to be solved when the current handover fails.

Summary of the invention

The embodiments of the present application provide a session switching method, device, and related equipment, wherein a first access network device can receive a first message from a second access network device, and the first message is used to request the protocol data The unit session is switched from the second access network device to the first access network device, and if the first access network device rejects the switching of the protocol data unit session, it sends a second message to the second access network device to Indicates the reason for the switch failure of the protocol data unit session that failed to switch. The first access network device sends the switch failure reason of the protocol data unit session to the second access network device, so that the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. , Which is beneficial to increase the probability of successful session switching of the protocol data unit in the second access network device.

In the first aspect, an embodiment of the present application provides a session switching method, which can be executed by a first access network device, and the first access network device can receive a first message from a second access network device, so The first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device and the identifiers of the network slices corresponding to each protocol data unit session The N is an integer greater than 1 or equal to 1, and the first message is used to instruct to switch the N protocol data unit sessions from the second access network device to the first access network device. If the first access network device refuses to switch the protocol data unit session to the target cell under the first access network device, the first access network device may send a second message to the second access network device The second message is used to indicate a switch failure reason of a protocol data unit session that fails to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the network slice supports The number of protocol data unit sessions is greater than or equal to one or more of the second thresholds. The first access network device sends the switch failure reason of the protocol data unit session to the second access network device, so that the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. , Which is beneficial to increase the probability of successful session switching of the protocol data unit in the second access network device.

In a possible design, the first access network device may determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; If the first number is greater than or equal to the first threshold, refuse to switch the protocol data unit session to the target cell. The first access network device can determine whether to switch the protocol data unit session corresponding to the network slice by judging whether the number of terminal devices supported by the network slice in the target cell reaches the maximum value. If the first access network device rejects at least one The PDU session is switched to the target cell, and the first access network device may indicate to the second access network device that the reason for the handover failure is that the number of terminal devices supported by the network slice has reached the maximum value.

In a possible design, the first access network device may determine a second number according to the identifier of the network slice, and the second number is the number of protocol data unit sessions supported by the network slice in the target cell. Quantity; if the second quantity is greater than or equal to the second threshold, refuse to switch the protocol data unit session to the target cell. The first access network device can determine whether to switch the protocol data unit session corresponding to the network slice by judging whether the number of protocol data unit sessions supported by the network slice in the target cell reaches the maximum value. If the first access network device rejects At least one PDU session is handed over to the target cell, and the first access network device may indicate to the second access network device that the reason for the handover failure is that the number of protocol data unit sessions supported by the network slice has reached the maximum value.

In a possible design, the first access network device may determine the first number and the second number according to the identifier of the network slice; if the first number is greater than or equal to the first threshold, and the second number If it is greater than or equal to the second threshold, refuse to switch the protocol data unit session to the target cell. The first access network device determines whether the number of terminal devices supported by the network slice in the target cell reaches the maximum value, and at the same time determines whether the number of protocol data unit sessions supported by the network slice in the target cell reaches the maximum value, and can determine whether to switch For the protocol data unit session corresponding to the network slice, if the first access network device refuses to switch at least one PDU session to the target cell, the first access network device may indicate to the second access network device that the reason for the handover failure is the network The number of terminal devices supported by the slice has reached the maximum and the number of protocol data unit sessions supported by the network slice has reached the maximum.

In a possible design, if the first access network device refuses to switch the M protocol data unit sessions to the target cell, the M is less than the N, which means that the first access network device refuses a part of the protocol data unit sessions. The protocol data unit session is switched to the target cell. The first access network device sends a second message to the second access network device, where the second message is a handover request confirmation message, and the handover request confirmation message is used to indicate each protocol data in the M protocol data unit sessions The reason for the switchover failure corresponding to the unit session.

In a possible design, if the first access network device refuses to switch the N protocol data unit sessions to the target cell, it means that the first access network device refuses to switch all the protocol data unit sessions to Target cell. The first access network device sends a second message to the second access network device, where the second message is a handover preparation failure message, and the handover preparation failure message is used to indicate a handover failure corresponding to the N protocol data unit sessions the reason.

In the second aspect, the embodiments of the present application provide a session switching method, which may be executed by a first access network device, and the first access network device receives a first message from a core network device. The first message The first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device and the identifiers of the network slices corresponding to each protocol data unit session, where N is greater than 1 or an integer equal to 1, the first message is used to instruct to switch the N protocol data unit sessions from the second access network device to the first access network device. If the first access network device refuses to switch the protocol data unit session to the target cell under the first access network device, the first access network device may send a second message to the core network device, The second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the protocol supported by the network slice The number of data unit sessions is greater than or equal to one or more of the second thresholds. Compared with the session switching method described in the first aspect, in the session switching method described in this embodiment, the first access network device and the second access network device cannot directly communicate with each other, and can communicate through the core network device. For example, if the core network device sends the switch failure reason of the protocol data unit session to the second access network device, the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. It is beneficial to increase the probability of successful session switching of the protocol data unit in the second access network device.

In a possible design, if the first access network device refuses to switch the M protocol data unit sessions to the target cell, the M is less than the N, which means that the first access network device refuses a part of the protocol data unit sessions. The protocol data unit session is switched to the target cell. The first access network device sends a second message to the core network device, where the second message is a handover request confirmation message, and the handover request confirmation message is used to indicate that each of the M protocol data unit sessions corresponds to each protocol data unit session. The reason for the switchover failure.

In a possible design, if the first access network device refuses to switch the N protocol data unit sessions to the target cell, it means that the first access network device refuses to switch all the protocol data unit sessions to Target cell. The first access network device sends a second message to the core network device, where the second message is a handover failure message, and the handover failure message is used to indicate a switch failure reason corresponding to the N protocol data unit sessions.

In a third aspect, an embodiment of the present application provides a session switching method, which may be executed by a second access network device, and the second access network device may send a first message to the first access network device to request switching, The first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device and the network slice corresponding to each protocol data unit session The N is an integer greater than or equal to 1, and the first message is used to instruct to switch the N protocol data unit sessions from the second access network device to the first access network The target cell under the device. If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, the second access network device receives the data from the first access network device A second message, the second message is used to indicate a switch failure reason of a protocol data unit session switch that fails to switch, the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, the The number of protocol data unit sessions supported by the network slicing is greater than or equal to one or more of the second thresholds. By receiving the cause of the protocol data unit session switching failure, the second access network device can refer to the switching failure reason to determine whether to switch the next time, which is beneficial to improve the probability of the protocol data unit session switching success in the second access network device. .

In a possible design, the target cell rejects the handover of M protocol data unit sessions, and the M is less than the N, which means that the first access network device rejects a part of the protocol data unit sessions to switch to the target cell. . The second message is a handover request confirmation message, and the handover request confirmation message is used to indicate a switch failure reason corresponding to each protocol data unit session in the M protocol data unit sessions.

In a possible design, the target cell rejects the switching of the N protocol data unit sessions, which means that the first access network device rejects all the protocol data unit sessions to switch to the target cell. The second message is a handover preparation failure message, and the handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.

In a fourth aspect, an embodiment of the present application provides a session switching method, which may be executed by a second access network device, and the second access network device may send a third message to the core network device, and the third message includes Third information, the third information includes the identification of the N protocol data unit sessions to be handed over under the second access network device and the identification of the target cell, the target cell being a cell under the first access network device , The N is an integer greater than or equal to 1. If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, the second access network device receives the fourth message from the core network device The fourth message is used to indicate the switch failure reason of the protocol data unit session switch of the switch failure, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the network slice The number of protocol data unit sessions supported is greater than or equal to one or more of the second thresholds. Compared with the session switching method described in the third aspect, in the session switching method described in this embodiment, the first access network device and the second access network device cannot directly communicate with each other, and can communicate through the core network device. For example, if the core network device sends the switch failure reason of the protocol data unit session to the second access network device, the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. It is beneficial to increase the probability of successful session switching of the protocol data unit in the second access network device.

In a possible design, the target cell rejects the handover of M protocol data unit sessions, and the M is less than the N, which means that the first access network device rejects a part of the protocol data unit sessions to switch to the target cell. . The fourth message is a handover command message, and the handover command message is used to indicate a switch failure reason corresponding to each protocol data unit session in the M protocol data unit sessions.

In a possible design, the target cell rejects the switching of the N protocol data unit sessions, which means that the first access network device rejects all the protocol data unit sessions to switch to the target cell. The fourth message is a handover preparation failure message, and the handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.

In a fifth aspect, the embodiments of the present application provide a session switching method, which may be executed by a core network device, and the core area device may receive a third message from a second access network device, where the third message includes the first Three information, the third information includes the identification of the N protocol data unit sessions to be handed over under the second access network device and the identification of the target cell, where the target cell is a cell under the first access network device, The N is an integer greater than or equal to 1. The core network device sends a first message to the first access network device, where the first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions and each of the protocol data The identifier of the network slice corresponding to the unit session, where the first message is used to indicate support for switching the N protocol data unit sessions from the second access network device to the first access network device. If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, the core network device receives the second message from the first access network device The second message is used to indicate a switch failure reason of a protocol data unit session that fails to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the network slice supports The number of protocol data unit sessions is greater than or equal to one or more of the second thresholds. The core network device then sends a fourth message to the second access network device, where the fourth message is used to indicate the switch failure reason of the protocol data unit session that failed to switch. When the first access network device and the second access network device cannot communicate directly, they can communicate through the core network device. For example, the reason for the switchover failure of the protocol data unit session can be sent to the second access network device, so that the second The access network device refers to the switch failure reason sent by the first access network device to determine whether to switch the next time, which is beneficial to improve the probability that the protocol data unit session switch succeeds in the second access network device.

In a possible design, the target cell rejects the handover of M protocol data unit sessions, and the M is less than the N, which means that the first access network device rejects a part of the protocol data unit sessions to switch to the target cell. . Correspondingly, the second message sent by the first access network device to the core network device is a handover request confirmation message, and the fourth message sent by the core network device to the second access network device is a handover command message, and the handover request confirmation message Or the handover command message is used to indicate the reason for the handover failure corresponding to each of the M protocol data unit sessions.

In a possible design, the target cell rejects the switching of N protocol data unit sessions, which means that the first access network device rejects all protocol data unit sessions to switch to the target cell. Correspondingly, the second message sent by the first access network device to the core network device is a handover failure message, and the fourth message sent by the core network device to the second access network device is a handover preparation failure message. The handover failure message or The handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.

In a sixth aspect, an embodiment of the present application provides a data transmission method. The method is executed by a first device. The first device sends a fifth message to a second device. The fifth message includes network slice information. The information is used to indicate one or more of the first threshold of the number of terminal devices supported by the network slice, and the second threshold of the number of protocol data unit sessions supported by the network slice. The first device sends the network slice information to the second device, so that the second device can perform one or more of the access control of the terminal device according to the network slice information, and the access control of the protocol data unit session is beneficial to Improve the service quality of terminal equipment.

In a possible design, the network slice information is network slice information in the first device, the first device is a first access network device, and the second device is a second access network device The fifth message includes one or more of an interface establishment request message, an interface establishment response message, a next-generation radio access network node configuration update message, and a next-generation radio access network node configuration update confirmation message.

In a possible design, the network slice information is network slice information in the first device, the first device is a first access network device or a second access network device, and the second device It is a core network device; the fifth message includes one or more of an interface establishment request message, a radio access network configuration update message, and an uplink radio access network configuration transfer message.

In a possible design, the network slice information is network slice information in the second device, the first device is a core network device, and the second device is a first access network device or a second device. Access network equipment; the fifth message also includes one or more of an interface establishment response message, a downlink radio access network configuration transfer message, and a core network equipment configuration update message.

In a seventh aspect, an embodiment of the present application provides a session switching device, which has a function of implementing the session switching method provided in the first aspect or the second aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In an eighth aspect, an embodiment of the present application provides a session switching device, which has a function of implementing the session switching method provided in the third aspect or the fourth aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a ninth aspect, an embodiment of the present application provides a session switching device, which has a function of implementing the session switching method provided in the fifth aspect. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a tenth aspect, an embodiment of the present application provides an access network device, the access network device includes a processor and a memory; the memory is used to store a computer program, and the processor executes the computer program stored in the memory to enable the access network The network access device executes the method in the first aspect or any one of the possible implementations of the first aspect, or executes the method in the second aspect or any of the second aspect, or executes the sixth or sixth aspect Any one of the possible implementation methods in the aspect.

In an eleventh aspect, an embodiment of the present application provides an access network device including a processor and a memory; the memory is used to store a computer program, and the processor executes the computer program stored in the memory to enable the The access network device executes the method in the third aspect or any one of the possible implementation manners of the third aspect, or executes the method in any one of the fourth aspect or the fourth aspect, or executes the sixth aspect or the first aspect. Any one of the six possible implementation methods.

In a twelfth aspect, an embodiment of the present application provides a core network device, the access network device includes a processor and a memory; the memory is used to store a computer program, and the processor executes the computer program stored in the memory to enable the network The device executes the method in the fifth aspect or any one of the possible implementation manners of the fifth aspect, or executes the method in the sixth aspect or any one of the possible implementation manners of the sixth aspect.

In a thirteenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the first aspect or the first aspect. Any one of the possible implementation methods.

In a fourteenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the second aspect or the second aspect. Any one of the possible implementation methods.

In a fifteenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the third aspect or the third aspect. Any one of the possible implementation methods.

In a sixteenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the fourth aspect or the fourth aspect. Any one of the possible implementation methods.

In a seventeenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the fifth aspect or the fifth aspect. Any one of the possible implementation methods.

In an eighteenth aspect, an embodiment of the present application provides a readable storage medium that includes a program or instruction. When the program or instruction runs on a computer, the computer executes the sixth aspect or the sixth aspect. Any one of the possible implementation methods.

In a nineteenth aspect, an embodiment of the present application also provides a communication device, the communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. . In a feasible implementation manner, the communication device further includes a memory, and the memory is used to store program instructions and data necessary to implement the functions of the method described in the first aspect.

In a twentieth aspect, an embodiment of the present application also provides a communication device, the communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. . In a feasible implementation manner, the communication device further includes a memory, and the memory is used to store program instructions and data necessary for implementing the functions of the method described in the second aspect.

In the twenty-first aspect, an embodiment of the present application further provides a communication device, the communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip. system. In a feasible implementation manner, the communication device further includes a memory, and the memory is used to store program instructions and data necessary to realize the functions of the method described in the third aspect.

In the twenty-second aspect, an embodiment of the present application also provides a communication device, the communication device includes a processor, and the processor is configured to implement the data transmission method described in any of the foregoing method embodiments. The communication device may be, for example, a chip. system. In a feasible implementation manner, the communication device further includes a memory, which is used to store program instructions and data necessary to implement the functions of the method described in the fourth aspect.

In the twenty-third aspect, an embodiment of the present application also provides a communication device, the communication device includes a processor, and the processor is configured to implement the data transmission method described in any of the foregoing method embodiments. The communication device may be, for example, a chip. system. In a feasible implementation manner, the communication device further includes a memory, which is used to store program instructions and data necessary to implement the functions of the method described in the fifth aspect.

In a twenty-fourth aspect, an embodiment of the present application also provides a communication device, the communication device includes a processor, and the processor is configured to implement the data transmission method described in any of the foregoing method embodiments. The communication device may be, for example, a chip. system. In a feasible implementation manner, the communication device further includes a memory, which is used to store program instructions and data necessary to implement the functions of the method described in the sixth aspect.

The chip system in the above aspect may be a system on chip (SOC), or a baseband chip, etc., where the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem, and an interface module.

Description of the drawings

In order to explain the technical solutions in the embodiments of the present invention more clearly, the following will briefly introduce the drawings that need to be used in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. A person of ordinary skill in the art can obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of this application;

2 is a schematic diagram of the architecture of a base station with CU-DU separation in a 5G communication system;

FIG. 3 is a schematic flowchart of a session switching method provided by an embodiment of this application;

4 is a schematic flowchart of another session switching method provided by an embodiment of this application;

FIG. 5 is a schematic flowchart of a data transmission method provided by an embodiment of this application;

FIG. 6 is a schematic structural diagram of a session switching apparatus provided by an embodiment of this application;

FIG. 7 is a schematic structural diagram of a session switching apparatus provided by an embodiment of the application;

FIG. 8 is a schematic structural diagram of a session switching apparatus provided by an embodiment of this application;

FIG. 9 is a schematic structural diagram of a session switching apparatus provided by an embodiment of this application;

FIG. 10 is a schematic structural diagram of a session switching apparatus provided by an embodiment of this application;

FIG. 11 is a schematic structural diagram of a data transmission device provided by an embodiment of this application;

FIG. 12 is a schematic structural diagram of a first access network device provided by an embodiment of this application;

FIG. 13 is a schematic structural diagram of another first access network device provided by an embodiment of this application;

FIG. 14 is a schematic structural diagram of a second access network device provided by an embodiment of this application;

15 is a schematic structural diagram of another second access network device provided by an embodiment of this application;

FIG. 16 is a schematic structural diagram of a core network device provided by an embodiment of this application;

FIG. 17 is a schematic structural diagram of a network device provided by an embodiment of this application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

As a key technology of the 5th generation (5G) system, network slicing has received extensive attention and research in the 3rd generation partnership project (3GPP) and various other international standardization organizations. Network slicing is a logical network that provides specific network capabilities and network features. A network slicing includes various resources that can meet business needs. Specifically, network slicing includes core network control functions, user plane network functions, and user plane related functions. Resources (such as computing resources, storage resources, network resources, etc.). The network slice may also include the resources of the radio access network. For the cells in the radio access network, the network slices supported by each cell are configured by an operation and maintenance management entity (operation administration and maintenance, OAM), and each network slice A single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) identification may be used. The S-NSSAI includes at least slice type/service type (SST) information, and may also include slice differentiation information (SD). Among them, the SST information is used to indicate the behavior of the network slicing, such as indicating the characteristics of the network slicing and the service type; the SD information is supplementary information of the SST, and when the SST indicates multiple network slicing, the SD is used to correspond to each network slicing.

There are many types of services in 5G networks, such as enhanced mobile broadband (eMBB) services, ultra-reliable low latency communications (URLLC) services, and massive machine communications (massive) Machine type communication, mMTC) services, etc., and protocol data unit (protocol data unit, PDU) sessions of different types of services may correspond to different network slices. Moreover, even the network slices corresponding to the PDU sessions of the same type of service may be different network slices due to different operators or service providers. Then, when the user equipment (UE) switches from the cell in the source base station (called the source cell) to the cell in the target base station (called the target cell), if the target cell does not support the UE to perform PDUs in the source cell The network slice corresponding to the session, the target cell will deny the UE access. However, in an actual network deployment environment, even if the target cell supports the network slicing corresponding to the UE's PDU session in the source cell, the target cell may refuse the UE to access. For example, limited by network resources or network operation strategies, a network slice can only support a certain number of UEs and a certain number of PDU sessions. When the number of UEs served by the network slice in the target cell exceeds the maximum number of UEs that the network slice can support, and the number of PDU sessions served by the network slice exceeds the maximum number of PDU sessions that the network slice can support, either situation occurs At this time, even if the target cell supports the network slice corresponding to the PDU session of the UE in the source cell, the target cell will refuse the UE to access. Therefore, when the UE switches from the source cell in the source base station to the target cell in the target base station, how to improve the probability of the source base station handover succeeding becomes a problem to be solved when the current handover fails.

In order to solve the above problem, the embodiment of the present application provides a session switching method, which can be executed by a first access network device, and the first access network device can receive a first message from a second access network device. , The first message is used to request to switch the protocol data unit session from the second access network device to the first access network device, if the first access network device refuses to switch to at least one protocol data unit session The target cell under the first access network device sends a second message to the second access network device to indicate the switch failure reason of the protocol data unit session that failed to switch, and the switch failure reason includes the network slicing support The number of terminal devices is greater than or equal to the first threshold, and the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds. The first access network device sends the switch failure reason of the protocol data unit session to the second access network device, so that the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. , Which is beneficial to increase the probability of successful session switching of the protocol data unit in the second access network device.

The embodiments of the present application will be described in detail below with reference to the drawings.

The session switching method, device, and related equipment provided by the embodiments of the present application can be applied to various communication systems. To facilitate the understanding of the embodiments of the present application, firstly, the communication system shown in FIG. 1 is taken as an example to introduce applicable to the present application. The communication system of the embodiment. As shown in Figure 1, the communication system includes core network equipment 110, access network equipment (access network equipment 121 and access network equipment 122 shown in Figure 1), terminal equipment (terminal equipment shown in Figure 1 131, terminal equipment 132 and terminal equipment 133). The access network device may be connected to at least one terminal device. For example, the access network device 121 is connected to the terminal device 131 and the terminal device 132 respectively, and the access network device 122 is connected to the terminal device 133. The core network device may be connected to at least one access network device. For example, the core network device 110 is connected to the access network device 121 and the access network device 122 respectively. The core network device and the access network device communicate through a communication interface. For example, the communication interface between the access network device and the core network device is an N2 interface or an NG interface, and the core network device 110 can communicate with each other through the aforementioned communication interface. The access network device 121 communicates with the access network device 122. Optionally, different access network devices can communicate through communication interfaces. For example, the communication interface between the access network device 121 and the second access network device 122 is an Xn interface. The first access network device 121 and the second access network device 122 can communicate directly, and there is no need to communicate through core network devices or other devices. If there is no communication interface between different access network devices, they can communicate through core network devices.

Wherein, the core network device is used to process functions such as access control, mobility management, session management, and data transmission of the terminal device, and is a core part of the communication system shown in FIG. 1. The core network equipment may include, but is not limited to, access and mobility management function entities (AMF), session management function entities (session management function, SMF), unified data management (unified data management, UDM) Entity, authentication server function (authentication server function, AUSF) entity, etc. Among them, AMF is mainly responsible for functions such as access control, mobility management, terminal equipment attachment and detachment, and gateway selection. SMF is mainly responsible for the management function of user sessions; UDM is mainly responsible for the unified processing of front-end data, including user identification, user subscription data, and authentication data. AUSF and UDM are specifically responsible for processing user authentication data.

The access network device may be any device with a wireless transceiver function, providing wireless communication services for terminal devices within the coverage area, and may include, but is not limited to, next generation NodeB (gNB), next generation evolution type Base station (next generation-evolved NodeB, ng-eNB), etc. Among them, gNB provides new radio (NR) user plane functions and control plane functions for terminal equipment, and ng-eNB provides terminal equipment with evolved universal terrestrial radio access (E-UTRA). User plane function and control plane function. It should be noted that gNB and ng-eNB are only a kind of names, used to indicate base stations that support a 5G network system, and do not have a restrictive meaning. The base station involved in each embodiment may also be a base transceiver station (BTS) in a GSM system or a CDMA system, a base station (nodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (evolutional node B, eNB or eNodeB). Alternatively, the base station involved in each embodiment may also be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network side device in a network after 5G or a network device in a future evolved PLMN network, and a roadside station unit ( road site unit, RSU), etc.

The terminal device may include, but is not limited to, a handheld terminal device, a notebook computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, and a personal digital assistant. PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones or wireless local loops (wireless local loop, WLL), machines Type communication (machine type communication, MTC) terminal or other terminal equipment that can access the network.

In an example, the 5G communication system can separate the centralized unit (CU) and distributed unit (DU) of the access network equipment according to the real-time requirements of different protocol layers, where: Figure 2 shows a schematic diagram of the architecture of a base station with CU-DU separation in a 5G communication system. As shown in Figure 2, the 5G communication system includes a next generation core network (next generation core, 5GC) and a next generation radio access network (NG-RAN) node connected to the 5GC. The NG-RAN node can be a gNB or an ng-eNB. The NG-RAN node can be connected to the 5GC through the NG-C (next generation control) interface and the NG-U (next generation user) interface. For ease of description, only one gNB and one ng-eNB are shown in FIG. 2.

Optionally, the connection between gNB and gNB, between gNB and ng-eNB, or between ng-eNB and ng-eNB may be connected through an Xn interface. One gNB or ng-eNB may include one CU and one or more DUs. For example, one gNB or ng-eNB shown in FIG. 2 includes one CU and two DUs. Among them, a CU may include a centralized unit control plane (CU-control plane function, CU-CP) and one or more centralized unit user planes (CU-user plane function, CU-UP). Among them, the CU and DU can be connected through the F1 interface, the CU-CP and CU-UP can be connected through the E1 interface, and the CU-CP and DU can be connected through the F1 control plane interface (F1-C) Connection, CU-UP and DU can be connected through the F1 user plane interface (F1-U).

As shown in Figure 2, each interface corresponds to multiple solid lines or dashed lines, where the solid lines represent control plane transmission, and the dashed lines represent user plane transmission. The function division of CU and DU can be divided according to the protocol stack. In a feasible implementation, the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer can be deployed In CU. The radio link layer control protocol (radio link control, RLC), media access control (media access control, MAC), and physical layer (physical layer, PHY) are deployed in the DU. Correspondingly, the CU has the processing capabilities of RRC, PDCP, and SDAP, and the DU has the processing capabilities of RLC, MAC, and PHY. It should be noted that the above function segmentation is just an example, and there may be other segmentation methods. For example, the CU has the processing capabilities of RRC, PDCP, RLC, and SDAP, and the DU has the processing capabilities of MAC and PHY. For another example, the CU has the processing capabilities of RRC, PDCP, RLC, SDAP, and part of the MAC (such as adding a MAC header), and the DU has the processing capabilities of PHY and part of the MAC (such as scheduling). The names of CU and DU may change, as long as the access network nodes that can realize the above-mentioned functions can be regarded as CU and DU in this application. The CU-CP has the control plane functions of the CU, for example, the processing capabilities of RRC and the control plane processing capabilities in PDCP. CU-UP has the user plane functions of the CU, for example, the processing capabilities of SDAP and the user plane processing capabilities of PDCP. It should be noted that the steps performed by the access network device (for example, the first access network device, the second access network device) involved in each embodiment of the present application may be a base station, CU, DU, CU-CP, or CU-UP is implemented, and this application does not limit it.

The embodiment of the present application provides a session switching method, which can be implemented by interaction between a first access network device and a second access network device. Referring to FIG. 3, the method may include the following steps:

S301. The second access network device sends a first message to the first access network device, where the first message is used to instruct to switch N protocol data unit sessions from the second access network device to the first access network device. Under the access network device; correspondingly, the first access network device receives the first message from the second access network device.

If there is a terminal device to be handed over in the second access network device, the second access network device may send a first message to the first access network device that has established a communication connection, and the first message is used to request the first Access network equipment prepares the resources required for handover. Wherein, the first message includes first information, and the first information may include, but is not limited to, the identification of the terminal device to be handed over, and the identities of the N protocol data unit sessions to be handed over to the second access network device And the identifier of the network slice corresponding to each protocol data unit session, where N is an integer greater than or equal to 1. For example, the identification of the terminal device included in the first information may be the UE XnAP ID, and the UE XnAP ID is used to uniquely identify a terminal device on the Xn interface in the second access network device. For another example, the first message is a handover request (handover request) message, and the handover request message includes N PDU session IDs (PDU session IDs) and a network slice ID (S-NSSAI) corresponding to each PDU session.

Correspondingly, the first access network device receives the first message from the second access network device, and can obtain the identifiers of the N PDU sessions to be switched under the second access network device contained in the first message And the network slice identifier corresponding to each PDU session. The first access network device may determine, according to the network slice identifier, whether a handover condition for switching the PDU session to a target cell is satisfied, and the target cell is a cell under the first access network device. In a feasible implementation manner, the first access network device determining whether the handover condition for handover of the PDU session to the target cell is satisfied according to the network slice identifier includes the following steps:

Determining a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell;

It is determined whether the first number is greater than or equal to the first threshold.

In another feasible implementation manner, the first access network device determining whether the handover condition for handover of the PDU session to the target cell is satisfied according to the network slice identifier includes the following steps:

Determining a second number according to the identifier of the network slice, where the second number is the number of protocol data unit sessions supported by the network slice in the target cell;

It is determined whether the second number is greater than or equal to the second threshold.

Determining the first quantity and the second quantity according to the identifier of the network slice;

It is determined whether the first number is greater than or equal to the first threshold, and at the same time, it is determined whether the second number is greater than or equal to the second threshold.

Wherein, the first threshold is a numerical value of the number of terminal devices supported by the network slice, and the second threshold is a numerical value of the number of protocol data unit sessions supported by the network slice. The first threshold and the second threshold are configured by OAM or configured by core network equipment. Optionally, the first threshold is the maximum number of terminal devices supported by the network slice, and the second threshold is the maximum number of protocol data unit sessions supported by the network slice. Optionally, the first threshold may be any other numerical value, and the second threshold may also be any other numerical value, for example, a numerical value given according to network resources, network operation policies, and the like. The embodiment of the present invention does not limit this.

In this embodiment, it is assumed that the maximum number of terminal devices that can be supported by one network slice is the first threshold, and the maximum number of PDU sessions that can be supported by one network slice is the second threshold. Specifically, the first terminal device may obtain the number of terminal devices that the network slice corresponding to the network slice identifier supports in the target cell, and the network slice corresponding to the network slice identifier is among the number of PDU sessions supported in the target cell. One or more, and then determine whether the number of terminal devices supported by the network slice in the target cell is greater than or equal to the maximum number of terminal devices that the network slice can support, and the network slice is in the target cell One or more of the cases where the number of supported PDU sessions is greater than or equal to the maximum number of PDU sessions that can be supported by the network slice. If the number of terminal devices supported by the network slice in the target cell is greater than or equal to the maximum number of terminal devices that the network slice can support, the number of PDU sessions supported by the network slice in the target cell is greater than or Equal to one or more of the maximum number of PDU sessions that the network slice can support, it means that there are not enough resources in the target cell to provide one or more of the new terminal equipment or new PDU sessions Service, the first access network device will reject the handover request of the second access network device, that is, the handover fails. For example, if the number of terminal devices supported by the network slice corresponding to S-NSSAI in the target cell has reached the maximum, even if the number of PDU sessions supported by the network slice corresponding to S-NSSAI in the target cell has not reached the maximum, the first The access network device will reject the handover request of the second access network device. It is understandable that as long as any one of the two parameters of the number of terminal devices supported by the network slice in the target cell and the number of PDU sessions supported by the network slice in the target cell does not meet the handover condition, first The access network device will reject the handover request of the second access network device.

S302: If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell, the first access network device sends a second message to the second access network, where the second message is used to instruct the handover The reason for the failure of the handover of the failed protocol data unit session; correspondingly, the second access network device receives the second message from the first access network device.

When the target cell under the first access network device rejects the handover of the PDU session, the first access network device may send a second message to the second access network device, and the second message is used to indicate the failure of the handover. The reason for the failure to switch the PDU session. The reason for the handover failure includes that the number of terminal devices supported by the network slice has reached a maximum value, and the number of PDU sessions has reached one or more of the maximum values. For example, if the number of terminal devices supported by the network slice corresponding to the S-NSSAI in the target cell has reached the maximum value, the reason for the handover failure indicated by the second message sent by the first access network device to the second access network device is The number of terminal devices supported by the network slicing has reached the maximum value. For another example, if the number of PDU sessions supported by the network slice corresponding to the S-NSSAI in the target cell has reached the maximum value, the reason for the handover failure indicated by the second message sent by the first access network device to the second access network device The number of PDU sessions supported for the network slice has reached the maximum. For another example, if the number of terminal device PDU sessions supported by the network slice corresponding to S-NSSAI in the target cell has reached the maximum, and the number of terminal devices supported by the network slice corresponding to S-NSSAI in the target cell has reached the maximum , The reason for the handover failure indicated by the second message sent by the first access network device to the second access network device is that the number of PDU sessions supported by the network slice has reached the maximum value and the number of terminal devices supported by the network slice has reached the maximum value. The number has reached the maximum. It should be understood that the handover failure reason is used to indicate that the number of terminal devices supported by the network slice is greater than or equal to the threshold of the terminal devices supported by the network slice, and the number of PDU sessions supported by the network slice is greater than or equal to the network slice. One or more of the thresholds of the PDU sessions that the slice can support. The reason for the handover failure can be expressed in multiple forms. For example, the reason for the handover failure includes one or more of the number of terminal devices supported by the network slice has reached the maximum value and the number of PDU sessions has reached the maximum value. . For another example, the reasons for the handover failure include one or more of the reasons for the protection of the maximum number of terminal devices in the network slice and the reasons for the protection of the maximum number of PDU sessions in the network slice. The embodiment of the present invention does not limit this.

It should be noted that in the embodiment of the present invention, the handover failure means that the target cell refuses to switch the PDU session from the second access network device to the first access network device. Therefore, the reason for the handover failure includes the network The number of terminal devices supported by the slice has reached the maximum, and the number of PDU sessions has reached one or more of the maximum. It can also be understood that the reason for the handover failure includes the number of terminal devices supported by the network slice. The target cell has reached the maximum value, and the number of PDU sessions has reached one or more of the maximum values in the target cell. Both have the same meaning.

Optionally, if the number of PDU sessions supported by the network slice in the target cell has not reached the maximum value, the first access network device may choose to accept the handover of some PDU sessions according to the resource margin of the network slice , Reject the switching of another part of the PDU session. For example, for N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of M PDU sessions, and M is less than N, which means The target cell rejects the handover of some PDU sessions. In the foregoing case, the message sent by the first access network device to the second access network device is a handover request acknowledgement (handover request acknowledgement) message, and the handover request acknowledgement message contains M PDU session switching failure reasons. For example, the second access network device includes 5 PDU sessions to be switched, and if the target cell under the first access network device refuses to switch 3 PDU sessions, they are PDU session 1, PDU session 2, and PDU session 3. , PDU session 1 corresponds to network slice 1, PDU session 2 corresponds to network slice 2, and PDU session 3 corresponds to network slice 3. Then the second message sent by the first access network device to the second access network device contains 3 PDU session switching The reasons for the failure include switching failure reason 1 corresponding to PDU session 1, switching failure reason 2 corresponding to PDU session 2, and switching failure reason 3 corresponding to PDU session 3. For example, switch failure reason 1 is that the number of PDU sessions supported by network slice 1 reaches the maximum, switch failure reason 2 is that the number of PDU sessions supported by network slice 2 reaches the maximum, and switch failure reason 3 is the network slice 3. The number of PDU sessions supported reached the maximum.

Optionally, if the number of PDU sessions supported by the network slice in the target cell has reached the maximum value, the target cell under the first access network device may reject the handover of all PDU sessions. For example, for the N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of all N PDU sessions. In the above case, the message sent by the first access network device to the second access network device is a handover preparation failure message, and the handover preparation failure message contains the reason for the failure of the PDU session switch The number of PDU sessions supported by network slicing has reached the maximum. It is understandable that the reasons for the switch failure of the rejected N PDU sessions are all the same, and the number of PDU sessions supported by the network slice has reached the maximum value. It should be noted that the first access network device and the second access network device described in this embodiment may also be a CU, a CU-CP, etc., which is not limited in this embodiment.

An embodiment of the present application provides a session switching method. A second access network device may send a first message to the first access network device, and the first message is used to request that a protocol data unit session be accessed from the second access network device. The network device switches to the first access network device, and if the first access network device rejects the switching of the protocol data unit session, it sends a second message to the second access network device to indicate that the switching of the protocol data unit session failed The reason for the handover failure, the reason for the handover failure includes one of the number of terminal devices supported by the network slice being greater than or equal to a first threshold, the number of protocol data unit sessions supported by the network slice being greater than or equal to the second threshold, or Many kinds. The first access network device sends the switch failure reason of the protocol data unit session to the second access network device, so that the second access network device can refer to the switch failure reason sent by the first access network device to determine whether to switch the next time. , Which is beneficial to improve the probability of successful PDU session switching in the second access network device.

The embodiment of the present application provides a session switching method, and the session switching method may be implemented by the interaction between the first access network device, the second access network device, and the core network device. Please refer to FIG. 4. Compared with the session switching method in the embodiment shown in FIG. 3, there is no Xn interface between the first access network device and the second access network device in the embodiment shown in FIG. The first access network device and the second access network device can communicate through the core network device. The method can include the following steps:

S401: The second access network device sends a third message to the core network device; correspondingly, the core network device receives the third message from the second access network device.

The second access network device may send a third message to the core network device, where the third message is used to request preparation of handover resources of the first access network device. Wherein, the third message includes third information, and the third information includes the identities of the N protocol data unit sessions to be handed over under the second access network device and the identities of the target cell. Correspondingly, the core network device receives the third message from the second access network device. It should be noted that the identification of the target cell contained in the third information is information that does not need to be directly processed by the core network device, but needs to be forwarded by the core network device to the first access network device. For example, the third message received by the core network device is a handover required message, and the handover required message includes the identifiers of N PDU sessions. It is understandable that, compared to the first message sent by the second access network device to the first access network device in the embodiment shown in FIG. 3, the first message sent by the second access network device to the core network device is The three messages do not include the identifier of the network slice corresponding to the PDU session to be switched.

S402: The core network device sends a first message to a first access network device, where the first message is used to instruct to switch N protocol data unit sessions from the second access network device to the first access network device. Device; correspondingly, the first access network device receives the first message from the core network device.

After receiving the third message from the second access network device, the core network device may send the first message to the first access network device to request the first access network device to prepare resources required for handover. Wherein, the first message includes first information, and the first information may include, but is not limited to, the identifiers of the N protocol data unit sessions to be switched under the second access network device and each protocol data unit The identifier of the network slice corresponding to the session, where N is an integer greater than or equal to 1. For example, the first message is a handover request (handover request) message, and the handover request message includes N PDU session IDs (PDU session IDs) and a network slice ID (S-NSSAI) corresponding to each PDU session.

Correspondingly, the first access network device receives the first message from the core network device, and can obtain the identifiers of the N PDU sessions to be switched under the second access network device contained in the first message and each The network slice identifier corresponding to the PDU session. The first access network device may determine, according to the network slice identifier, whether a handover condition for switching the PDU session to a target cell is satisfied, and the target cell is a cell under the first access network device. Specifically, the step of determining whether the first access network device satisfies the handover condition for handover of the PDU session to the target cell according to the network slice identifier may refer to the description in S301 in the embodiment shown in FIG. 3, where No longer.

S403: If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, the first access network device sends a second message to the core network device, so The second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch; correspondingly, the core network device receives the second message from the first access network device.

When the target cell under the first access network device rejects the handover of the PDU session, the first access network device may send a second message to the core network device. The second message is used to indicate the failure of the handover of the PDU session. The reason for the switch failure. The reason for the handover failure includes that the number of terminal devices supported by the network slice has reached a maximum value, and the number of PDU sessions has reached one or more of the maximum values. In an example, if the number of PDU sessions supported by the network slice in the target cell has not reached the maximum value, the first access network device may choose to accept a part of the PDU sessions according to the resource margin of the network slice The switching of the other part of the PDU session is rejected. For example, for N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of M PDU sessions, and M is less than N, which means The target cell rejects the handover of some PDU sessions. In the above case, the message sent by the first access network device to the core network device is a handover request acknowledgement (handover request acknowledgement) message, and the handover request acknowledgement message contains M PDU session switching failure reasons. The switch request confirmation message will respectively indicate the reason for the switch failure of each PDU session that failed to switch.

In an example, if the number of PDU sessions supported by the network slice in the target cell has reached the maximum value, the target cell under the first access network device may reject the handover of all PDU sessions. For example, for the N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of all N PDU sessions. In the above case, the message sent by the first access network device to the core network device is a handover failure message, and the handover failure message contains the reason for the failure of the PDU session switch to be a PDU session supported by the network slice. The number of has reached the maximum. It is understandable that the reasons for the switch failure of the rejected N PDU sessions are all the same, and the number of PDU sessions supported by the network slice has reached the maximum value.

S404: The core network device sends a fourth message to the second access network device, where the fourth message is used to indicate the reason for the switch failure of the protocol data unit session that failed to switch; correspondingly, the second access network device receives from the core The fourth message of the network equipment.

The core network device may send a fourth message to the second access network device to indicate the switch failure reason of the failed PDU session, and the switch failure reason includes that the number of terminal devices supported by the network slice has reached the maximum value, and the PDU session The number of has reached one or more of the maximum values. In an example, if the number of PDU sessions supported by the network slice in the target cell has not reached the maximum value, the first access network device may choose to accept a part of the PDU sessions according to the resource margin of the network slice The switching of the other part of the PDU session is rejected. For example, for N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of M PDU sessions, and M is less than N, which means The target cell rejects the handover of some PDU sessions. In the above case, the message sent by the core network device to the second access network device is a handover command message, and the handover command message is used to indicate the reason why the M PDU session switching fails. Wherein, the handover command message will respectively indicate the reason for the switch failure of each PDU session that failed to switch.

In an example, if the number of PDU sessions supported by the network slice in the target cell has reached the maximum value, the target cell under the first access network device may reject the handover of all PDU sessions. For example, for the N PDU sessions to be switched under the second access network device, the target cell under the first access network device rejects the switching of all N PDU sessions. In the above case, the message sent by the core network device to the second access network device is a handover preparation failure message, and the handover preparation failure message is used to indicate that the reason for the failure of the PDU session switch is that the network slice supports The number of PDU sessions has reached the maximum. It is understandable that the reasons for the switch failure of the rejected N PDU sessions are all the same, and the number of PDU sessions supported by the network slice has reached the maximum value. It should be noted that the first access network device and the second access network device described in this embodiment may also be a CU, a CU-CP, etc., which is not limited in this embodiment.

The embodiment of the present application provides a session switching method. When the first access network device and the second access network device cannot directly communicate, they can communicate through the core network device. The second access network device receives the switch failure reason of the protocol data unit session, and can refer to the switch failure reason to determine whether to switch next time, which is beneficial to improve the probability of the second access network device switching success.

In order to improve the service quality of the terminal equipment, network slicing information can be shared among the first access network equipment, the second access network equipment, and the core network equipment, so that the first access network equipment, the second access network equipment And the core network equipment can perform terminal equipment access control, protocol data unit session access control, etc. according to the network slice information. The embodiment of the present application provides a data transmission method, which is implemented by the interaction between the first device and the second device. Referring to FIG. 5, the method may include the following steps:

S501: The first device obtains network slice information, where the network slice information is used to indicate one or more of the maximum number of terminal devices supported by the network slice and the maximum number of protocol data unit sessions supported by the network slice.

The network slice information may include, but is not limited to, the maximum number of terminal devices supported by the network slice, the maximum number of PDU sessions supported by the network slice, and so on. Wherein, the first device may include, but is not limited to, access network equipment, core network equipment, CU, CU-CP, DU, and CU-UP, etc., and the second device may include, but is not limited to, access network equipment, core network equipment, etc. Network equipment, CU and CU-CP, etc. The network slice information can be configured by OAM. When the first device is an access network device, the network slice information may also be configured by the core network device.

S502: The first device sends a fifth message to the second device, where the fifth message includes network slice information, and correspondingly, the second device receives the fifth message from the first device.

The first device may send a message to the second device through the communication interface, and the message includes the network slice information of the first device, where the network slice information may include, but is not limited to, the maximum number of terminal devices that the network slice can support, The maximum number of PDU sessions that a network slice can support. When the first device is of different device types, the types of messages sent by the first device to the second device are also different.

In an example, when the first device and the second device are access network devices, CUs, or CU-CPs, the message may be an Xn setup request (Xn setup request) message or an Xn setup response (Xn setup response) message One or more of the next generation radio access network node configuration update (NG-RAN node configuration update) message, and the next generation radio access network node configuration update acknowledgement (NG-RAN node configuration update acknowledge) message. Correspondingly, the second device receives the above message.

In an example, when the first device is an access network device, CU, or CU-CP, and the second device is a core network device, the message may be an NG setup request message, a radio access network configuration One or more of an update (RAN configuration update) message and an uplink radio access network configuration transfer (uplink RAN configuration transfer) message. Correspondingly, the second device receives the above message.

In an example, when the first device is a core network device and the second device is an access network device, CU, or CU-CP, the message may be an NG setup response message (NG setup response), a downlink radio access network device One or more of a configuration transfer (downlink RAN configuration transfer) message and an AMF configuration update (AMF configuration update) message. Correspondingly, the second device receives the above message.

In an example, when the first device is a DU and the second device is a CU or CU-CP, the message may be an F1 setup request (F1 setup request) message, a next-generation base station distributed unit configuration update (gNB-DU configuration update) one or more of the messages. Correspondingly, the second device receives the above message.

In an example, when the first device is CU-UP and the second device is CU-CP, the message may be a next-generation base station centralized unit user plane E1 setup request (gNB-CU-UP E1 setup request) message One or more of the next-generation base station centralized unit control plane E1 setup response (gNB-CU-CP E1 setup response) message, and the next-generation base station centralized unit user plane configuration update (gNB-CU-UP configuration update) message Kind. Correspondingly, the second device receives the above message. It should be noted that the embodiment of the present application does not limit the name of the above-mentioned message.

The embodiment of the application provides a data transmission method. A first device can obtain network slice information and send the network slice information to a second device. The second device can connect to the terminal device according to the received network slice information. Access control, protocol data unit session access control, etc., so as to improve the quality of service of terminal equipment.

The following describes in detail the related devices of the embodiment of the present application with reference to FIG. 6 to FIG. 11.

An embodiment of the application provides a session switching device, as shown in FIG. 6. The session switching apparatus 600 may be used to execute the steps corresponding to the first access network device in the session switching method shown in FIG. 3, and the session switching apparatus includes:

The receiving module 601 is configured to receive a first message from a second access network device, where the first message includes first information, and the first information includes N pieces of information to be handed over to the second access network device The identifier of the protocol data unit session and the identifier of the network slice corresponding to each protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to transfer the N protocol data units The session is switched from the second access network device to the first access network device;

The sending module 602 is configured to notify the second access network device when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device A second message is sent, the second message is used to indicate a switch failure reason of a protocol data unit session that fails to switch, and the switch failure reason includes that the number of terminal devices supported by the network slicing is greater than or equal to a first threshold, the The number of protocol data unit sessions supported by the network slicing is greater than or equal to one or more of the second thresholds.

In an implementation manner, the device further includes a processing module 603, and the processing module 603 may be specifically used for:

Determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; if the first number is greater than or equal to the first threshold, Refuse to switch the protocol data unit session to the target cell; or,

Determine a second number according to the identifier of the network slice, where the second number is the number of protocol data unit sessions supported by the network slice in the target cell; if the second number is greater than or equal to the second Threshold, refuse to switch the protocol data unit session to the target cell; or,

Determine the first number and the second number according to the identifier of the network slice; if the first number is greater than or equal to the first threshold, and the second number is greater than or equal to the second threshold, refuse to transfer the agreement The data unit session is switched to the target cell.

In an implementation manner, the processing module 603 may be specifically used to:

Refuse to handover the M protocol data unit sessions to the target cell, the M is less than the N; the second message is a handover request confirmation message, and the handover request confirmation message is used to indicate the M protocols The reason for the switch failure corresponding to each protocol data unit session in the data unit session.

Refusing to switch the N protocol data unit sessions to the target cell; the second message is a handover preparation failure message, and the handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions .

An embodiment of the present application provides a session switching device, as shown in FIG. 7. The session switching apparatus 700 may be used to perform the steps corresponding to the first access network device in the session switching method shown in FIG. 4, and the session switching apparatus includes:

The receiving module 701 is configured to receive a first message from a core network device, where the first message includes first information, and the first information includes information about N protocol data unit sessions to be switched under the second access network device. ID and the ID of the network slice corresponding to each protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to transfer the N protocol data unit sessions from the first Second, the access network device switches to the first access network device;

The sending module 702 is configured to send the second access network device to the core network device when the first access network device refuses to switch at least one protocol data unit session to the target cell under the first access network device. Message, the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, the switch failure reason includes that the number of terminal devices supported by the network slicing is greater than or equal to the first threshold, and the network slicing supports The number of protocol data unit sessions is greater than or equal to one or more of the second thresholds.

In an implementation manner, the device further includes a processing module 703, and the processing module 703 may be specifically used for:

In an implementation manner, the processing module 703 may be specifically used to:

Refuse to switch the N protocol data unit sessions to the target cell; the second message is a handover failure message, and the handover failure message is used to indicate the switch failure reason corresponding to the N protocol data unit sessions.

An embodiment of the present application provides a session switching device, as shown in FIG. 8. The session switching apparatus 800 may be used to perform the steps corresponding to the second access network device in the session switching method shown in FIG. 3, and the session switching apparatus includes:

The sending module 801 is configured to send a first message to a first access network device, where the first message includes first information, and the first information includes N protocols to be switched under the second access network device The identifier of the data unit session and the identifier of the network slice corresponding to each of the protocol data unit sessions, where N is an integer greater than or equal to 1, and the first message is used to indicate that the N protocol data unit sessions Handover from the second access network device to the target cell under the first access network device;

The receiving module 802 is configured to receive from the first access network device when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device The second message of the network device, the second message is used to indicate the switch failure reason of the protocol data unit session switch that failed to switch, the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to the first threshold , The number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds.

In an implementation manner, the target cell rejects the handover of M sessions of the protocol data unit, and the M is less than the N; the second message is a handover request confirmation message, and the handover request confirmation message is used for Indicate the switch failure reason corresponding to each protocol data unit session in the M protocol data unit sessions.

In an implementation manner, the target cell rejects the handover of the N protocol data unit sessions; the second message is a handover preparation failure message, and the handover preparation failure message is used to indicate the N protocol data units The reason for the switchover failure corresponding to the session.

An embodiment of the present application provides a session switching device, as shown in FIG. 9. The session switching apparatus 900 may be used to execute the steps corresponding to the second access network device in the session switching method shown in FIG. 4, and the session switching apparatus includes:

The sending module 901 is configured to send a third message to a core network device, where the third message includes third information, and the third information includes information about the N protocol data unit sessions to be switched under the second access network device. An identifier and an identifier of a target cell, where the target cell is a cell under the first access network device, and the N is an integer greater than or equal to 1;

The receiving module 902 is configured to receive a message from the core network device when the first access network device refuses to switch at least one protocol data unit session to the target cell under the first access network device The fourth message, the fourth message is used to indicate the switch failure reason of the protocol data unit session switch of the switch failure, the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, the The number of protocol data unit sessions supported by the network slicing is greater than or equal to one or more of the second thresholds.

In an implementation manner, the target cell rejects the handover of M sessions of the protocol data unit, and the M is less than the N; the fourth message is a handover command message, and the handover command message is used to indicate all The reason for the switching failure corresponding to each protocol data unit session in the M protocol data unit sessions.

An embodiment of the present application provides a session switching device, as shown in FIG. 10. The session switching apparatus 1000 may be used to execute the steps corresponding to the core network equipment in the session switching method shown in FIG. 4, and the session switching apparatus includes:

The receiving module 1001 is configured to receive a third message from a second access network device, where the third message includes third information, and the third information includes N pieces of information to be handed over under the second access network device. An identifier of the protocol data unit session and an identifier of a target cell, where the target cell is a cell under the first access network device, and the N is an integer greater than or equal to 1;

The sending module 1002 is configured to send a first message to the first access network device, where the first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions and each The identifier of the network slice corresponding to the protocol data unit session, and the first message is used to indicate support for switching the N protocol data unit sessions from the second access network device to the first access network device ；

The receiving module 1001 is further configured to receive data from the first access network device when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device. The second message of the access network device, the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to the first Threshold, the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds.

The sending module 1002 is further configured to send a fourth message to the second access network device, where the fourth message is used to indicate the switch failure reason of the protocol data unit session that failed to switch.

In an implementation manner, the target cell rejects the handover of M sessions of the protocol data unit, and the M is less than the N; the second message is a handover request confirmation message, and the fourth message is a handover command Message, the handover request confirmation message or the handover command message is used to indicate the reason for the handover failure corresponding to each of the M protocol data unit sessions.

In an implementation manner, the target cell rejects the handover of the N protocol data unit sessions; the second message is a handover failure message, the fourth message is a handover preparation failure message, and the handover failure message or The handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.

An embodiment of the application provides a data transmission device, as shown in FIG. 11. The data transmission apparatus 1100 can be used to execute the steps corresponding to the first device in the data transmission method shown in FIG. 5, and the data transmission apparatus includes:

The processing module 1101 is configured to obtain network slice information, where the network slice information is used to indicate one or more of the maximum number of terminal devices supported by the network slice and the maximum number of protocol data unit sessions supported by the network slice.

The sending module 1102 is configured to send a fifth message to the second device, where the fifth message includes network slice information, and correspondingly, the second device receives the fifth message from the first device.

In an implementation manner, the network slice information is network slice information in the first device, the first device is a first access network device, and the second device is a second access network device; The fifth message includes one or more of an interface establishment request message, an interface establishment response message, a next generation radio access network node configuration update message, and a next generation radio access network node configuration update confirmation message.

In an implementation manner, the network slice information is network slice information in the first device, the first device is a first access network device or a second access network device, and the second device is Core network equipment; the fifth message includes one or more of an interface establishment request message, a radio access network configuration update message, and an uplink radio access network configuration transfer message.

In an implementation manner, the network slice information is network slice information in the second device, the first device is a core network device, and the second device is a first access network device or a second access network device. Network access device; the fifth message also includes one or more of an interface establishment response message, a downlink radio access network configuration transfer message, and a core network device configuration update message.

The following describes in detail the related equipment of the embodiment of the present application with reference to Figs.

FIG. 12 is a schematic structural diagram of a first access network device provided by an embodiment of the present application. As shown in FIG. 12, the first access network device can be applied to the system shown in FIG. The function of the first access network device in the embodiment. For ease of description, FIG. 12 only shows the main components of the first access network device. As shown in FIG. 12, the first access network device 1200 may include a receiver 1201 and a transmitter 1202, where the receiver 1201 may also be referred to as a receiver, an input port, a receiving circuit, etc., for example, the receiver shown in FIG. 6 The related functions implemented by the module 601 can be implemented by the receiver 1201. The transmitter 1202 may also be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. For example, related functions implemented by the transmitting module 602 shown in FIG. 6 may be implemented by the transmitter 1202. Optionally, the receiver 1201 and the transmitter 1202 shown in FIG. 12 may also be regarded as a transceiver. The transceiver may also be called a transceiver, a transceiver, etc., which can implement the receiving module 601 and the transmitter shown in FIG. 6 Relevant functions of module 602.

The first access network device 1200 may further include a processor 1203, configured to process data received by the receiver 1201, or process data to be sent by the transmitter 1202. The processor 1203 may include one or more processors. For example, the processor 1203 may be one or more central processing units (CPUs), network processors (NPs), hardware chips, or any combination thereof . In the case where the processor 1203 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The first access network device 1200 may further include a memory 1204, and the memory 1204 is used to store program codes and the like. The memory 1204 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 1204 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory). Only memory (ROM), flash memory (flash memory), hard disk drive (HDD), or solid-state drive (SSD); the memory 1204 may also include a combination of the foregoing types of memories.

In an example, the above-mentioned receiver 1201, transmitter 1202, and processor 1203 may be used to implement the session switching method performed by the first access network device as shown in FIG. 3, where the receiver 1201 is used to receive data from the first access network device. 2. A first message of an access network device, where the first message includes first information, and the first information includes the identification of the N protocol data unit sessions to be switched under the second access network device and each The identifier of the network slice corresponding to the protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to transfer the N protocol data unit sessions from the second access network device Handover to the first access network device; the transmitter 1202 is used for when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device , Sending a second message to the second access network device, where the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, and the switch failure reason includes the terminal device supported by the network slicing The number is greater than or equal to the first threshold, and the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds.

In an implementation manner, the processor 1203 may be specifically configured to determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; if If the first number is greater than or equal to the first threshold, refuse to switch the protocol data unit session to the target cell; or,

In an implementation manner, the processor 1203 may be specifically configured to refuse to handover the M protocol data unit sessions to the target cell, and the M is less than the N; the second message is a handover request confirmation message, The handover request confirmation message is used to indicate the reason for the handover failure corresponding to each protocol data unit session in the M protocol data unit sessions.

In an implementation manner, the processor 1203 may be specifically configured to refuse to switch the N protocol data unit sessions to the target cell; the second message is a handover preparation failure message, and the handover preparation failure message is used for Indicate the switch failure reasons corresponding to the N protocol data unit sessions.

FIG. 13 is a schematic structural diagram of another first access network device provided by an embodiment of the present application. As shown in FIG. 13, the first access network device can be applied to the system shown in FIG. The function of the first access network device in the illustrated embodiment. For ease of description, FIG. 13 only shows the main components of the first access network device. As shown in FIG. 13, the first access network device 1300 may include a receiver 1301, a transmitter 1302, a processor 1303, and a memory 1304. For the description of the foregoing devices, refer to the corresponding description in the embodiment shown in FIG. This will not be repeated here. The above-mentioned receiver 1301, transmitter 1302, and processor 1303 may be used to implement the session switching method performed by the first access network device as shown in FIG. 4, where the receiver 1301 is used to receive the first message from the core network device , The first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device and the identifiers of the network slices corresponding to each protocol data unit session The N is an integer greater than 1 or equal to 1, and the first message is used to instruct to switch the N protocol data unit sessions from the second access network device to the first access network device; The transmitter 1302 is configured to send a second message to the core network device when the first access network device refuses to switch at least one protocol data unit session to the target cell under the first access network device The second message is used to indicate a switch failure reason of a protocol data unit session that fails to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the network slice supports The number of protocol data unit sessions is greater than or equal to one or more of the second thresholds.

In an implementation manner, the processor 1303 may be specifically configured to determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; if If the first number is greater than or equal to the first threshold, refuse to switch the protocol data unit session to the target cell; or,

In an implementation manner, the processor 1303 may be specifically configured to refuse to handover the M protocol data unit sessions to the target cell, and the M is less than the N; the second message is a handover request confirmation message, The handover request confirmation message is used to indicate the reason for the handover failure corresponding to each protocol data unit session in the M protocol data unit sessions.

In an implementation manner, the processor 1303 may be specifically configured to refuse to handover the N protocol data unit sessions to the target cell; the second message is a handover failure message, and the handover failure message is used to indicate N A switch failure reason corresponding to each of the protocol data unit sessions.

FIG. 14 is a schematic structural diagram of a second access network device provided by an embodiment of the present application. As shown in FIG. 14, the second access network device can be applied to the system shown in FIG. The function of the second access network device in the embodiment. For ease of description, FIG. 14 only shows the main components of the second access network device. As shown in FIG. 14, the second access network device 1400 may include a transmitter 1401 and a receiver 1402, where the transmitter 1401 may also be referred to as a transmitter, a transmitter, or a transmitting circuit, etc., for example, the transmitter shown in FIG. 9 The related functions implemented by the module 901 can be implemented by the transmitter 1401. The receiver 1402 may also be referred to as a receiver, an input port, a receiving circuit, etc., for example, related functions implemented by the receiving module 902 shown in FIG. 9 may be implemented by the receiver 1402. Optionally, the transmitter 1401 and the receiver 1402 shown in FIG. 14 may also be regarded as a transceiver. The transceiver may also be called a transceiver, a transceiver, etc., which can implement the sending module 901 and the receiver shown in FIG. 9 Related functions of module 902.

The second access network device 1400 may further include a processor 1403, configured to process data to be sent by the transmitter 1401, or process data received by the receiver 1402. The processor 1403 may include one or more processors. For example, the processor 1403 may be one or more central processing units (CPU), network processors (NP), hardware chips, or any combination thereof . In the case where the processor 1403 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The first access network device 1400 may further include a memory 1404, where the memory 1404 is used to store program codes and the like. The memory 1404 may include volatile memory (volatile memory), such as random access memory (random access memory, RAM); the memory 1404 may also include non-volatile memory (non-volatile memory), such as read-only memory (read-only memory). Only memory (ROM), flash memory (flash memory), hard disk drive (HDD), or solid-state drive (SSD); the memory 1404 may also include a combination of the foregoing types of memories.

In an example, the above-mentioned transmitter 1401, receiver 1402, and processor 1403 may be used to implement the session switching method performed by the second access network device as shown in FIG. 3, where the transmitter 1401 is used to communicate with the first access network device. The network access device sends a first message, the first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device and each of the The identifier of the network slice corresponding to the protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to switch the N protocol data unit sessions from the second access network device To the target cell under the first access network device; the receiver 1402 is configured to switch at least one protocol data unit session to the target cell under the first access network device when the first access network device refuses In the target cell, a second message from the first access network device is received, where the second message is used to indicate the reason for the handover failure of the protocol data unit session handover of the handover failure, and the reason for the handover failure includes the network The number of terminal devices supported by the slice is greater than or equal to the first threshold, and the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds.

FIG. 15 is a schematic structural diagram of another second access network device provided by an embodiment of the present application. As shown in FIG. 15, the second access network device can be applied to the system shown in FIG. The function of the second access network device in the illustrated embodiment. For ease of description, FIG. 15 only shows the main components of the second access network device. As shown in FIG. 15, the second access network device 1500 may include a transmitter 1501, a receiver 1502, a processor 1503, and a memory 1504. For the description of the foregoing devices, refer to the corresponding description in the embodiment shown in FIG. 14. This will not be repeated here. The above-mentioned transmitter 1501, receiver 1502, and processor 1503 may be used to implement the session switching method performed by the second access network device in FIG. 4, where the transmitter 1501 is used to send the third message to the core network device, so The third message includes third information, and the third information includes the identity of the N protocol data unit sessions to be handed over under the second access network device and the identity of the target cell, and the target cell is the first access In the cell under the network device, the N is an integer greater than 1 or equal to 1. The receiver 1502 is configured to switch at least one protocol data unit session to the first access when the first access network device refuses When the target cell under the network device is received, a fourth message from the core network device is received, where the fourth message is used to indicate the reason for the handover failure of the protocol data unit session handover of the handover failure, and the reason for the handover failure includes all the reasons for the handover failure. The number of terminal devices supported by the network slice is greater than or equal to a first threshold, and the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second threshold.

In an implementation manner, the target cell rejects the handover of the N protocol data unit sessions; the fourth message is a handover preparation failure message, and the handover preparation failure message is used to indicate the N protocol data units The reason for the switchover failure corresponding to the session.

FIG. 16 is a schematic structural diagram of a core network device provided by an embodiment of the present application. As shown in FIG. 16, the core network device can be applied to the system shown in FIG. 1 to implement the core network in the embodiment shown in FIG. The function of the device. For ease of description, FIG. 16 only shows the main components of the core network device. As shown in FIG. 16, the core network device 1600 may include a receiver 1601 and a transmitter 1602. The receiver 1601 may also be called a receiver, an input port, a receiving circuit, etc., for example, the receiving module 1001 shown in FIG. The implemented related functions can be implemented by the receiver 1601. The transmitter 1602 may also be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. For example, related functions implemented by the transmitting module 1002 shown in FIG. 10 may be implemented by the transmitter 1602. Optionally, the receiver 1601 and the transmitter 1602 shown in FIG. 16 may also be regarded as a transceiver. The transceiver may also be called a transceiver, a transceiver, etc., which can implement the receiving module 1001 and the transmitter shown in FIG. Related functions of module 1002.

The core network device 1600 may further include a processor 1603, configured to process data received by the receiver 1601, or process data to be sent by the transmitter 1602. The processor 1603 may include one or more processors. For example, the processor 1603 may be one or more central processing units (CPU), network processors (NP), hardware chips, or any combination thereof . In the case where the processor 1603 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The core network device 1600 may further include a memory 1604, and the memory 1604 is used to store program codes and the like. The memory 1604 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 1604 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory). Only memory (ROM), flash memory (flash memory), hard disk drive (HDD), or solid-state drive (SSD); the memory 1604 may also include a combination of the foregoing types of memories.

The above-mentioned receiver 1601, transmitter 1602, and processor 1603 may be used to implement the session switching method performed by the core network device in FIG. 4, where the receiver 1601 is used to receive the third message from the second access network device , The third message includes third information, and the third information includes the identifiers of the N protocol data unit sessions to be handed over under the second access network device and the identifier of the target cell, and the target cell is the first In the cell under the access network device, the N is an integer greater than 1 or equal to 1. The transmitter 1602 is configured to send a first message to the first access network device, where the first message includes first information, so The first information includes the identifier of the N protocol data unit sessions and the identifier of the network slice corresponding to each protocol data unit session, and the first message is used to indicate that the N protocol data unit sessions are supported from The second access network device is switched to the first access network device; the receiver 1601 is further configured to switch at least one of the protocol data unit sessions to the first access network device when the first access network device refuses When a target cell under an access network device receives a second message from the first access network device, the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, and the switch Reasons for failure include that the number of terminal devices supported by the network slice is greater than or equal to the first threshold, and the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second threshold; the sender 1602 also It is used to send a fourth message to the second access network device, where the fourth message is used to indicate the switch failure reason of the protocol data unit session that failed to switch.

FIG. 17 is a schematic structural diagram of a network device provided by an embodiment of the present application. As shown in FIG. 17, the network device is used to perform the function of the first device in the embodiment shown in FIG. 5. It is understandable that the network device 1700 may be the first access network device shown in FIG. 12 and FIG. 13, or the second access network device shown in FIG. 14 and FIG. 15, or may be the second access network device shown in FIG. The core network equipment is not limited in this embodiment. For ease of description, FIG. 17 only shows the main components of the network device. As shown in FIG. 17, the network device 1700 may include a processor 1701 and a transmitter 1702, where the processor 1603 is configured to process data to be sent by the transmitter 1702. The processor 1701 may include one or more processors. For example, the processor 1701 may be one or more central processing units (CPU), network processors (NP), hardware chips, or any combination thereof . In the case where the processor 1701 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The transmitter 1702 may also be referred to as a transmitter, a transmitter, or a transmitting circuit, etc. For example, related functions implemented by the transmitting module 1102 shown in FIG. 11 may be implemented by the transmitter 1702.

The network device 1700 may further include a memory 1703, where the memory 1703 is used to store program codes and the like. The memory 1703 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 1703 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory). Only memory (ROM), flash memory (flash memory), hard disk drive (HDD), or solid-state drive (SSD); the memory 1703 may also include a combination of the foregoing types of memories.

The processor 1701 is configured to obtain network slice information, where the network slice information is used to indicate one or more of the maximum number of terminal devices supported by the network slice and the maximum number of protocol data unit sessions supported by the network slice; and The device 1702 is configured to send a fifth message to the second device, where the fifth message includes network slice information.

The embodiment of the present application also provides a readable storage medium, which includes a program or instruction, when the program or instruction runs on a computer, the computer executes the first access network device in the above method embodiment. The session switching method performed.

The embodiment of the present application also provides a readable storage medium, the readable storage medium includes a program or instruction, when the program or instruction runs on a computer, the computer is caused to execute the second access network device in the above method embodiment. The session switching method performed.

The embodiment of the present application also provides a readable storage medium, the readable storage medium includes a program or instruction, when the program or instruction runs on a computer, the computer executes the session executed by the core network device in the above method embodiment. Switch method.

The embodiment of the present application also provides a readable storage medium, the readable storage medium includes a program or instruction, when the program or instruction runs on a computer, the computer executes the data transmission performed by the network device in the above method embodiment method.

An embodiment of the present application also provides a communication device. The communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. In a feasible implementation manner, the communication device further includes a memory, which is used to store program instructions and data necessary for realizing the function of the first access network device.

An embodiment of the present application also provides a communication device. The communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. In a feasible implementation manner, the communication device further includes a memory, and the memory is used to store program instructions and data necessary for realizing the function of the second access network device.

An embodiment of the present application also provides a communication device. The communication device includes a processor, and the processor is configured to implement the session switching method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. In a feasible implementation manner, the communication device further includes a memory, and the memory is used to store program instructions and data necessary for realizing the functions of the core network device.

An embodiment of the present application also provides a communication device. The communication device includes a processor configured to implement the data transmission method described in any of the foregoing method embodiments. The communication device may be, for example, a chip system. In a feasible implementation manner, the communication device further includes a memory, which is used to store program instructions and data necessary for realizing the functions of the network device.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one 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. Transmission to another website, computer, server, or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) etc.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both, in order to clearly illustrate the hardware and software Interchangeability, in the above description, the composition and steps of each example have been generally described in accordance with the function. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application. The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. It should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

A session switching method, characterized in that it is applied to a first access network device, and includes:

Receive a first message from a second access network device, where the first message includes first information, and the first information includes the identifiers of N protocol data unit sessions to be switched under the second access network device And the identifier of the network slice corresponding to each protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to transfer the N protocol data unit sessions from the second The access network device switches to the first access network device;

If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, a second message is sent to the second access network device, and the first The second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, the switch failure reason includes the number of terminal devices supported by the network slice is greater than or equal to the first threshold, and the protocol data unit session supported by the network slice The number of is greater than or equal to one or more of the second thresholds.
The method according to claim 1, wherein the first access network device refusing at least one of the protocol data unit sessions to be handed over to the target cell under the first access network device comprises:

Determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; if the first number is greater than or equal to the first threshold, Refuse to switch the protocol data unit session to the target cell; or,

Determine a second number according to the identifier of the network slice, where the second number is the number of protocol data unit sessions supported by the network slice in the target cell; if the second number is greater than or equal to the second Threshold, refuse to switch the protocol data unit session to the target cell; or,

Determine the first number and the second number according to the identifier of the network slice; if the first number is greater than or equal to the first threshold, and the second number is greater than or equal to the second threshold, Then refuse to switch the protocol data unit session to the target cell.
The method according to claim 1 or 2, wherein the refusal of the first access network device to switch at least one of the protocol data unit sessions to the target cell under the first access network device comprises:

Refuse to handover the M protocol data unit sessions to the target cell, the M is less than the N; the second message is a handover request confirmation message, and the handover request confirmation message is used to indicate the M protocols The reason for the switch failure corresponding to each protocol data unit session in the data unit session.
The method according to claim 1 or 2, wherein the refusal of the first access network device to switch at least one of the protocol data unit sessions to the target cell under the first access network device comprises:

Refusing to switch the N protocol data unit sessions to the target cell; the second message is a handover preparation failure message, and the handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions .
A session switching method, characterized in that it is applied to a second access network device, and includes:

A first message is sent to the first access network device, the first message includes first information, and the first information includes the identifiers of the N protocol data unit sessions to be switched under the second access network device, and The identifier of the network slice corresponding to each protocol data unit session, where N is an integer greater than 1 or equal to 1, and the first message is used to instruct to connect the N protocol data unit sessions from the second The network access device switches to the target cell under the first access network device;

If the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device, receive the second data from the first access network device Message, the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, the switch failure reason includes that the number of terminal devices supported by the network slicing is greater than or equal to the first threshold, and the network slicing supports The number of protocol data unit sessions is greater than or equal to one or more of the second thresholds.
The method according to claim 5, wherein the target cell under the first access network device rejects the handover of M sessions of the protocol data unit, and the M is less than the N; The second message is a handover request confirmation message, and the handover request confirmation message is used to indicate a switch failure reason corresponding to each protocol data unit session in the M protocol data unit sessions.
The method according to claim 5, wherein the target cell under the first access network device rejects the handover of N protocol data unit sessions; the second message is a handover preparation failure message, The handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.
A session switching device, characterized in that it comprises:

The receiving module is configured to receive a first message from a second access network device, where the first message includes first information, and the first information includes N protocols to be switched under the second access network device The identifier of the data unit session and the identifier of the network slice corresponding to each of the protocol data unit sessions, where N is an integer greater than or equal to 1, and the first message is used to indicate that the N protocol data unit sessions Handover from the second access network device to the first access network device;

A sending module, configured to send to the second access network device when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device The second message, the second message is used to indicate the switch failure reason of the protocol data unit session that failed to switch, the switch failure reason includes that the number of terminal devices supported by the network slicing is greater than or equal to the first threshold, and the network The number of protocol data unit sessions supported by the slice is greater than or equal to one or more of the second thresholds.
The apparatus according to claim 8, wherein the apparatus further comprises a processing module, the processing module refuses to switch at least one of the protocol data unit sessions to the first access network when the first access network equipment When the target cell under the network equipment, it is specifically used for:

Determine a first number according to the identifier of the network slice, where the first number is the number of terminal devices supported by the network slice in the target cell; if the first number is greater than or equal to the first threshold, Refuse to switch the protocol data unit session to the target cell; or,

Determine a second number according to the identifier of the network slice, where the second number is the number of protocol data unit sessions supported by the network slice in the target cell; if the second number is greater than or equal to the second Threshold, refuse to switch the protocol data unit session to the target cell; or,

Determine the first number and the second number according to the identifier of the network slice; if the first number is greater than or equal to the first threshold, and the second number is greater than or equal to the second threshold, refuse to transfer the agreement The data unit session is switched to the target cell.
The apparatus according to claim 8 or 9, wherein the processing module refuses to switch at least one protocol data unit session to a target cell under the first access network device when the first access network device refuses When, specifically used for:

Refuse to handover the M protocol data unit sessions to the target cell, the M is less than the N; the second message is a handover request confirmation message, and the handover request confirmation message is used to indicate the M protocols The reason for the switch failure corresponding to each protocol data unit session in the data unit session.
The apparatus according to claim 8 or 9, wherein the processing module refuses to switch at least one protocol data unit session to a target cell under the first access network device when the first access network device refuses When, specifically used for:

Refusing to switch the N protocol data unit sessions to the target cell; the second message is a handover preparation failure message, and the handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions .
A session switching device, characterized in that it comprises:

A sending module, configured to send a first message to a first access network device, where the first message includes first information, and the first information includes N protocol data to be switched under the second access network device The identifier of the unit session and the identifier of the network slice corresponding to each of the protocol data unit sessions, where N is an integer greater than or equal to 1, and the first message is used to instruct to transfer the N protocol data unit sessions from Switching the second access network device to the target cell under the first access network device;

The receiving module is configured to receive from the first access network device when the first access network device refuses to switch at least one of the protocol data unit sessions to the target cell under the first access network device The second message of the network access device, the second message is used to indicate the switch failure reason of the protocol data unit session switch that failed to switch, and the switch failure reason includes that the number of terminal devices supported by the network slice is greater than or equal to the first Threshold, the number of protocol data unit sessions supported by the network slice is greater than or equal to one or more of the second thresholds.
The apparatus according to claim 12, wherein the target cell under the first access network device rejects the handover of M sessions of the protocol data unit, and the M is less than the N; The second message is a handover request confirmation message, and the handover request confirmation message is used to indicate a switch failure reason corresponding to each protocol data unit session in the M protocol data unit sessions.
The apparatus according to claim 12, wherein the target cell under the first access network device rejects the handover of N protocol data unit sessions; the second message is a handover preparation failure message, The handover preparation failure message is used to indicate the reason for the handover failure corresponding to the N protocol data unit sessions.
A readable storage medium, characterized by comprising a program or instruction, and when the program or instruction runs on a computer, the method according to any one of claims 1 to 4 is executed.
A readable storage medium, characterized by comprising a program or instruction, when the program or instruction runs on a computer, the method according to any one of claims 5 to 7 is executed.