Communication method and device

Abstract

The embodiments of the present application provide a communication method and apparatus, relating to the field of communications. The method includes: receiving a first message from a second network device, the first message including network slice configuration information, the network slice configuration information being used to indicate a maximum data rate provided by each of n network slices for a terminal device, where n is an integer greater than or equal to 1; and sending a second message to the second network device, instructing the first network device to reject a configuration requirement for the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n. This effectively improves the quality of service of the terminal device.

Description

[0001] This application is a divisional application. The application number of the original application is 201910919493.1, and the original application date is September 26, 2019. The entire content of the original application is incorporated into this application by reference. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and in particular to a communication method and apparatus. Background Art

[0003] Currently, in existing communication systems, the method for limiting the aggregate bit rate that can be provided to terminal devices is usually that the core network sends the aggregate maximum bit rate of the terminal device to the base station to limit the aggregate bit rate that can be provided to all non-guaranteed bit rate quality of service (Non-GBR QoS) flows of the terminal device.

[0004] However, the current limiting methods in existing technologies are no longer sufficient to meet the current 5G application scenarios. Summary of the Invention

[0005] The present application provides a communication method and device that can provide a current limiting method that can be applied to 5G scenarios.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a communication method, which is applied to a first network device, and the method includes: the first network device receives a first message from a second network device, the first message including network slice configuration information, and the network slice configuration information is used to indicate the maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1; then, the first network device may send a second message to the second network device, to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0008] Through the above method, it is achieved to solve the data rate execution problem of terminal devices in network slices in a network environment that supports network slicing. That is, the setting of network slices in this application is based on the granularity of terminal devices, and the maximum data rate of each terminal device on the network slice is processed, thereby improving the service quality of the terminal device.

[0009] In one possible implementation, the step of the first network device sending a second message to the second network device may include: the first network device determines, based on local available resources and / or local policies, to reject the maximum data rate provided by m network slices for the terminal device, and then sends the second message to the second network device.

[0010] Through the above-mentioned method, it is achieved that the first network device can determine whether to accept the maximum data rate provided by n network slices for the terminal device based on locally available resources and / or local policies. In one example, the first network device can accept the maximum data rate provided by n network slices for the terminal device. In another example, the first network device can accept part of the maximum data rate provided by one or more network slices for the terminal device, and reject the maximum data rate provided by other network slices for the terminal device except for the one or more network slices mentioned above. In another example, the first network device may not accept the requirements of any network slice, that is, reject the maximum data rate provided by n network slices for the terminal device.

[0011] In a possible implementation, the method may further include: the first network device sends a rejection message to the second network device, indicating that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0012] Through the above method, the first network device can inform the second network device that the reason for rejecting m network slices is because the first network device does not support the demand for m network slices, thereby eliminating the reasons caused by the network or the second network device, so that when the second network device learns that the first network device has rejected m network slices, it does not need to detect its own reasons.

[0013] In one possible implementation, the method may further include: the first network device sends recommendation information to the second network device, indicating the maximum data rate provided by at least one network slice among the m network slices supported by the first network device for the terminal device.

[0014] Through the above method, the first network device can recommend to the second network device the actual maximum data rate provided by at least one of its m acceptable network slices for the terminal device based on available resources and / or local policies.

[0015] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the non-guaranteed bit rate service quality Non-GBRQoS flow and / or the guaranteed bit rate service quality GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0016] Through the above method, it is possible to limit the different data streams provided by the network slice to the terminal device, so as to provide a complete flow limiting method for different application scenarios and further improve the service quality of the terminal device.

[0017] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0018] Through the above method, the diversity of application scenarios can be improved, that is, the present application can be applied to switching scenarios, UE context setting scenarios, UE context modification scenarios, bearer context setting scenarios, bearer context modification scenarios, secondary node addition scenarios, secondary node modification scenarios, PDU session resource setting scenarios and / or initial context setting scenarios, etc.

[0019] In a second aspect, an embodiment of the present application provides a communication method, which can be applied to a second network device. The method may include: the second network device sends a first message to the first network device, the first message including network slice configuration information, the network slice configuration information being used to indicate the maximum data rate provided by each of the n network slices for the terminal device, where n is an integer greater than or equal to 1; then, the second network device may receive a second message from the first network device, the second message being used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0020] In one possible implementation, the second message is sent by the first network device to the second network device after the first network device determines to reject the maximum data rate provided by m network slices for the terminal device based on local available resources and / or local policies.

[0021] In one possible implementation, the method also includes: the second network device receives a rejection message sent by the first network device, wherein the rejection information is used to indicate that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0022] In one possible implementation, the method also includes: the second network device receives recommendation information sent by the first network device, wherein the recommendation information is used to indicate the maximum data rate provided by at least one network slice among the m network slices supported by the first network device for the terminal device.

[0023] In one possible implementation, the method further includes: based on the recommendation information, modifying the maximum data rate provided by at least one network slice for the terminal device, and indicating to the first network device the modified maximum data rate provided by the at least one network slice for the terminal device.

[0024] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0025] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0026] In a third aspect, an embodiment of the present application provides a communication method, which can be applied to a first network device, comprising: the first network device receives a first message from a second network device, the first message including network slice configuration information, wherein the network slice configuration information is used to indicate the maximum data rate provided by each of n network slices for the terminal device, and n is an integer greater than or equal to 1; then, the first network device can perform resource scheduling and / or admission control on the n network slices based on the network slice configuration information.

[0027] In one possible implementation, resource scheduling and / or admission control is performed on n network slices based on network slice configuration information, including: determining the maximum data rate supported by m network slices for terminal devices based on local available resources and / or local policies, where m is an integer greater than or equal to 0 and less than or equal to n; and allocating corresponding resources to the m network slices based on the network slice configuration information.

[0028] In a possible implementation, the first message is an obtain UE context response message. Before receiving the first message from the second network device, the method may further include: sending an obtain UE context request message to the second network device.

[0029] In a possible implementation, the first message is a downlink NAS transmission message.

[0030] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device E, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0031] In a fourth aspect, an embodiment of the present application provides a communication method, which includes: after a first network device receives a first message sent by a second network device, the first network device sends a second message to a third network device, where the second message includes network slice configuration information, wherein the network slice configuration information is used to indicate the maximum data rate provided by each of the n network slices for the terminal device, and n is an integer greater than or equal to 1; the first network device receives a third message sent by a third network device, wherein the third message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, wherein m is an integer greater than or equal to 0 and less than or equal to n; the first network device sends a fourth message to the second network device, wherein the fourth message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, wherein m is an integer greater than or equal to 0 and less than or equal to n.

[0032] In one possible implementation, the third message, or the third message and the fourth message include rejection information, and the rejection information is used to indicate that the reason why the third network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0033] In one possible implementation, the third message, or the third message and the fourth message include recommendation information for indicating the maximum data rate provided by at least one of the m network slices supported by the third network device to the terminal device.

[0034] In a possible implementation, the first message is a handover requirement message, and the second message is a handover request message.

[0035] In a fifth aspect, an embodiment of the present application provides a communication device, which is applied to a first network device, and the device includes: a memory and a processor, and the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: receiving a first message from a second network device, the first message includes network slice configuration information, and the network slice configuration information is used to indicate the maximum data rate provided by each of the n network slices for the terminal device, where n is an integer greater than or equal to 1; sending a second message to the second network device, used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0036] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: based on local available resources and / or local policies, determine to reject the maximum data rate provided by m network slices for the terminal device, and then send a second message to the second network device.

[0037] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: sending a rejection message to the second network device, indicating that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0038] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: sending recommendation information to the second network device to indicate the maximum data rate provided by at least one of the m network slices supported by the first network device to the terminal device.

[0039] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0040] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0041] In a sixth aspect, an embodiment of the present application provides a communication device, which is applied to a second network device, and the device includes: a memory and a processor, and the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: sending a first message to the first network device, the first message includes network slice configuration information, and the network slice configuration information is used to indicate the maximum data rate provided by each of the n network slices to the terminal device, where n is an integer greater than or equal to 1; receiving a second message from the first network device, the second message is used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices to the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0042] In one possible implementation, the second message is sent by the first network device to the second network device after the first network device determines to reject the maximum data rate provided by m network slices for the terminal device based on local available resources and / or local policies.

[0043] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: receiving a rejection message sent by the first network device, wherein the rejection message is used to indicate that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0044] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: receiving recommendation information sent by the first network device, wherein the recommendation information is used to indicate the maximum data rate provided by at least one of the m network slices supported by the first network device to the terminal device.

[0045] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: based on the recommendation information, modify the maximum data rate provided by at least one network slice for the terminal device, and indicate to the first network device the maximum data rate provided by the modified at least one network slice for the terminal device.

[0046] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0047] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0048] In the seventh aspect, an embodiment of the present application provides a communication device, which is applied to a first network device, including a memory and a processor, and the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: receiving a first message from a second network device, the first message including network slice configuration information, wherein the network slice configuration information is used to indicate the maximum data rate provided by each of n network slices to the terminal device, and n is an integer greater than or equal to 1; based on the network slice configuration information, performing resource scheduling and / or admission control on the n network slices.

[0049] In one possible implementation, when the program instructions are executed by the processor, the device performs the following steps: based on locally available resources and / or local policies, determine the maximum data rate provided by m network slices to the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n; based on the network slice configuration information, allocate corresponding resources to the m network slices.

[0050] In a possible implementation, the first message is a Get UE Context Response message. When the program instructions are executed by the processor, the apparatus performs the following steps: before receiving the first message from the second network device, sending a Get UE Context Request message to the second network device.

[0051] In a possible implementation, the first message is a downlink NAS transmission message.

[0052] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device E, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0053] In an eighth aspect, an embodiment of the present application provides a communication device, which is applied to a first network device, and includes a memory and a processor, and the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: after receiving a first message sent by the second network device, sending a second message to the third network device, the second message including network slice configuration information, wherein the network slice configuration information is used to indicate the maximum data rate provided by each of the n network slices for the terminal device, and n is an integer greater than or equal to 1; receiving a third message sent by the third network device, wherein the third message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, wherein m is an integer greater than or equal to 0 and less than or equal to n; sending a fourth message to the second network device, wherein the fourth message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, wherein m is an integer greater than or equal to 0 and less than or equal to n.

[0054] In one possible implementation, the third message, or the third message and the fourth message include rejection information, and the rejection information is used to indicate that the reason why the third network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0055] In one possible implementation, the third message, or the third message and the fourth message include recommendation information for indicating the maximum data rate provided by at least one of the m network slices supported by the third network device to the terminal device.

[0056] In a possible implementation, the first message is a handover requirement message, and the second message is a handover request message.

[0057] In a ninth aspect, an embodiment of the present application provides a communication device, applied to a first network device, the device including:

[0058] a receiving module, configured to receive a first message from a second network device, the first message including network slice configuration information, the network slice configuration information being used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1;

[0059] A sending module is used to send a second message to the second network device, where the second message is used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0060] In one possible implementation, the sending module is used to: based on local available resources and / or local policies, determine to reject the maximum data rate provided by m network slices for the terminal device, and then send a second message to the second network device.

[0061] In one possible implementation, the sending module is also used to: send a rejection message to the second network device, indicating that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0062] In one possible implementation, the sending module is also used to: send recommendation information to the second network device, indicating the maximum data rate provided by at least one of the m network slices supported by the first network device to the terminal device.

[0063] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the non-guaranteed bit rate service quality Non-GBRQoS flow and / or the guaranteed bit rate service quality GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0064] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0065] In a tenth aspect, an embodiment of the present application provides a communication device, applied to a second network device, the device including:

[0066] a sending module, configured to send a first message to a first network device, where the first message includes network slice configuration information, where the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1;

[0067] A receiving module is used to receive a second message from the first network device, where the second message is used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.

[0068] In one possible implementation, the second message is sent by the first network device to the second network device after the first network device determines to reject the maximum data rate provided by m network slices for the terminal device based on local available resources and / or local policies.

[0069] In one possible implementation, the receiving module is further used to: receive a rejection message sent by the first network device, wherein the rejection information is used to indicate that the reason why the first network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices for the terminal device.

[0070] In one possible implementation, the receiving module is further used to: receive recommendation information sent by the first network device, wherein the recommendation information is used to indicate the maximum data rate provided by at least one of the m network slices supported by the first network device to the terminal device.

[0071] In one possible implementation, the device also includes: a modification module, which is used to modify the maximum data rate provided by at least one network slice to the terminal device based on the recommendation information, and indicate to the first network device the modified maximum data rate provided by the at least one network slice to the terminal device.

[0072] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0073] In one possible implementation, the first message is a handover request message; or, the first message is a UE context setting request message or a UE context modification request message; or, the first message is a bearer context setting request message or a bearer context modification request message; or, the first message is a secondary node addition request message or a secondary node modification request message; or, the first message is a PDU session resource setting request message or an initial context setting request message.

[0074] In an eleventh aspect, an embodiment of the present application provides a communication device, applied to a first network device, the device including:

[0075] a receiving module, configured to receive a first message from a second network device, where the first message includes network slice configuration information, wherein the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1;

[0076] A processing module is used to perform resource scheduling and / or admission control on n network slices based on network slice configuration information.

[0077] In one possible implementation, the processing module is used to: determine the maximum data rate provided by m network slices to the terminal device based on local available resources and / or local policies, where m is an integer greater than or equal to 0 and less than or equal to n; and allocate corresponding resources to the m network slices based on the network slice configuration information.

[0078] In a possible implementation, the first message is an obtain UE context response message. Before receiving the first message from the second network device, the method may further include: sending an obtain UE context request message to the second network device.

[0079] In a possible implementation, the first message is a downlink NAS transmission message.

[0080] In a possible implementation, the network slice configuration information includes at least one of the following: first indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the Non-GBR QoS flow and / or GBR QoS flow of the terminal device; second indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the uplink data flow of the terminal device E, the uplink data flow is the uplink Non-GBR QoS flow and / or the uplink GBR QoS flow; third indication information, used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, the downlink data flow is the downlink Non-GBR QoS flow and / or the downlink GBR QoS flow.

[0081] In a twelfth aspect, an embodiment of the present application provides a communication device, applied to a first network device, the device including:

[0082] A receiving module, configured to receive a first message sent by a second network device;

[0083] a sending module, configured to send a second message to the third network device after the receiving module receives the first message, where the second message includes network slice configuration information, wherein the network slice configuration information is used to indicate a maximum data rate provided by each of the n network slices for the terminal device, where n is an integer greater than or equal to 1;

[0084] The receiving module is further used to receive a third message sent by a third network device, wherein the third message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n;

[0085] The sending module is also used to send a fourth message to the second network device after the receiving module receives the third message, wherein the fourth message is used to instruct the third network device to reject the configuration requirement of the maximum data rate provided by m network slices for the terminal device, wherein m is an integer greater than or equal to 0 and less than or equal to n.

[0086] In one possible implementation, the third message, or the third message and the fourth message include rejection information, and the rejection information is used to indicate that the reason why the third network device rejects m network slices is that the first network device does not support the maximum data rate provided by the m network slices to the terminal device.

[0087] In one possible implementation, the third message, or the third message and the fourth message include recommendation information for indicating the maximum data rate provided by at least one of the m network slices supported by the third network device to the terminal device.

[0088] In a possible implementation, the first message is a handover requirement message, and the second message is a handover request message.

[0089] In a thirteenth aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0090] In a fourteenth aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the second aspect or any possible implementation of the second aspect.

[0091] In a fifteenth aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, which includes instructions for executing the method in the third aspect or any possible implementation of the third aspect.

[0092] In a sixteenth aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, which includes instructions for executing the method in the fourth aspect or any possible implementation of the fourth aspect.

[0093] In a seventeenth aspect, an embodiment of the present application provides a computer program comprising instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0094] In an eighteenth aspect, an embodiment of the present application provides a computer program comprising instructions for executing the method in the second aspect or any possible implementation of the second aspect.

[0095] In a nineteenth aspect, an embodiment of the present application provides a computer program comprising instructions for executing the method in the third aspect or any possible implementation of the third aspect.

[0096] In the twentieth aspect, an embodiment of the present application provides a computer program comprising instructions for executing the method in the fourth aspect or any possible implementation of the fourth aspect.

[0097] In a twenty-first aspect, an embodiment of the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processor executes the method of the first aspect or any possible implementation of the first aspect to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0098] In aspect 22, embodiments of the present application provide a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processor executes the method of aspect 2 or any possible implementation of aspect 2 to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0099] In a twenty-third aspect, an embodiment of the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processor executes the method of the third aspect or any possible implementation of the third aspect to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0100] In a twenty-fourth aspect, an embodiment of the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processor executes the method of the fourth aspect or any possible implementation of the fourth aspect to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0101] In aspect 25, an embodiment of the present application provides a communication system, which includes the first network device, the second network device and the terminal device involved in the above-mentioned first aspect, second aspect, third aspect and fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0103] Figure 1A This is a schematic diagram of a possible communication system architecture provided by an embodiment of the present application;

[0104] Figure 1B This is a schematic diagram of the architecture of a CU-DU separated base station provided in an embodiment of the present application;

[0105] Figure 2 This is a schematic diagram of the base station structure provided by an embodiment of the present application;

[0106] Figure 3 This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0107] Figure 4 is one of the flowcharts of an exemplary communication method;

[0108] Figure 5 This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0109] Figure 6 is one of the flowcharts of an exemplary communication method;

[0110] Figure 7 This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0111] Figure 8 This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0112] Figure 9This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0113] Figure 10 is one of the flowcharts of an exemplary communication method;

[0114] Figure 11 This is one of the flow diagrams of a communication method provided in an embodiment of the present application;

[0115] Figure 12 is a structural diagram of a first network device provided in an embodiment of the present application;

[0116] Figure 13 is a schematic structural diagram of a second network device provided in an embodiment of the present application;

[0117] Figure 14 is a structural diagram of a first network device provided in an embodiment of the present application;

[0118] Figure 15 is a structural diagram of a first network device provided in an embodiment of the present application;

[0119] Figure 16 It is a structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0120] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0121] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0122] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0123] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0124] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0125] Next, descriptions of various network elements and professional terms that may be involved in the embodiments of this application are as follows:

[0126] Terminal device: It can be user equipment (UE). UE accesses the network side through the base station. For example, it can be a handheld terminal device, a laptop computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), a tablet computer, a wireless modem, a handheld device, a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal or other device that can access the network.

[0127] Base station: Mainly responsible for wireless resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side.

[0128] The core network device may be an access and mobility management function (AMF), which is mainly responsible for access control, mobility management (MM), attachment and detachment, and gateway selection. The core network device involved in the embodiments of the present application is not limited to the AMF.

[0129] Fifth-generation (5G) communication systems introduce the concept of network slicing, which allows a physical network to be divided into multiple virtual networks. Each virtual network is considered a "network slice," and each network slice is independent of the others. Different protocol data unit (PDU) sessions within a terminal device may require the network slice corresponding to each PDU session to provide services.

[0130] To help those skilled in the art better understand this application, the following briefly explains the concept of network slicing involved in this application:

[0131] As a key 5G technology, network slicing has received extensive attention and research within 3GPP and other international standardization organizations. It can meet operators' customized needs for various industries, vertical markets, and virtual operations. A network slice is a logical network that provides specific network capabilities and characteristics. It can be a logical network with different network capabilities and characteristics, customized based on different service requirements or tenants, on top of a physical or virtual network infrastructure. A network slice consists of a set of network functions and their required resources (e.g., computing resources, storage resources, and network resources).

[0132] The network slices supported by each cell are configured by the operation, administration and maintenance (OAM) system. A single network slice selection assistance information (S-NSSAI) identifies a network slice.

[0133] S-NSSAI includes at least one of the following: slice type, service type (SST) information, and optionally, slice differentiator (SD) information. SST information is used to indicate the behavior of the network slice, such as the characteristics of the network slice and the service type. SD information is complementary to SST. For example, if SST points to multiple network slices, SD can help correspond to a unique network slice.

[0134] There are many types of services in terminal devices, such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communication (mMTC), etc., and the network slices corresponding to the PDU sessions of different types of services may be different.

[0135] For example, a UE includes three PDU sessions, each of which corresponds to a network slice. Multiple PDU sessions can correspond to the same network slice. Even for the same service type, different operators or service providers may provide different network slices. In other words, a network slice can provide network resources for at least one PDU session of the terminal device.

[0136] Before describing the technical solution of the embodiment of the present application, the communication system of the embodiment of the present application will be described with reference to the accompanying drawings. Figure 1A , is a schematic diagram of a communication system provided in an embodiment of the present application. The communication system includes a core network device 101, a base station (including a base station 102 and a base station 103), and a terminal device (including a terminal device 104, a terminal device 105, and a terminal device 106). It should be noted that in actual applications, the number of base stations and terminal devices can be one or more. Figure 1A The number of base stations and terminal devices in the communication system shown is only an adaptive example and is not limited in this application.

[0137] like Figure 1A As shown, a terminal device can access at least one base station. For example, terminal device 104 is connected to base station 102, terminal device 106 is connected to base station 103, and terminal device 105 is connected to base station 102 and base station 103 (this scenario is called dual connectivity). A base station can be connected to at least one core network device. For example, base station 102 and base station 103 are respectively connected to core network device 101.

[0138] There are communication interfaces between the core network device 101 and the base station 102 and the base station 103, respectively, so that the core network device 101 can communicate with the base station 102 and the base station 103. For example, the communication interface is referred to as N2 interface or NG interface in this application.

[0139] If there is a communication interface between base station 102 and base station 103, the two can communicate directly. Direct communication here means that the two base stations can communicate without going through core network equipment or other equipment. For example, the communication interface between base station 102 and base station 103 can be called an Xn interface.

[0140] If there is no communication interface between base station 102 and base station 103, the two cannot communicate directly. In one possible embodiment, the two base stations without a communication interface can communicate through core network equipment.

[0141] The above-mentioned communication system can be used to support fourth generation (4G) access technology, such as long term evolution (LTE) access technology; or, the communication system can also support fifth generation (5G) access technology, such as new radio (NR) access technology; or, the communication system can also be used to support third generation (3G) access technology, such as universal mobile telecommunications system (UMTS) access technology; or the communication system can also be used to support second generation (2G) access technology, such as global system for mobile communications (GSM) access technology; or, the communication system can also be used to support a communication system of multiple wireless technologies, such as supporting LTE technology and NR technology. In addition, the communication system can also be applied to narrowband Internet of Things (NB-IoT), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronous code division multiple access (TD-SCDMA), long term evolution (LTE) and future-oriented communication systems.

[0142] It should be noted that the base stations involved in each embodiment of the present application (such as the first base station, the second base station, the source base station or the target base station) can be a next generation NodeB (gNB) or a next generation evolved NodeB (ng-eNB). Among them, the gNB provides the user plane function and control plane function of the new radio (NR) for the UE, and the ng-eNB provides the user plane function and control plane function of the evolved universal terrestrial radio access (E-UTRA) for the UE. It should be noted that gNB and ng-eNB are only names used to indicate base stations that support the 5G network system and are not restrictive. The base stations involved in each embodiment can also be base stations (base transceiver station, BTS) in a GSM system or a CDMA system, or base stations (nodeB, NB) in a WCDMA system, or evolved base stations (evolutional node B, eNB or eNodeB) in an LTE system. Alternatively, the base station involved in each embodiment can also be a relay station, an access point, a vehicle-mounted device, a wearable device, a network-side device in a network after 5G, or a network device in a future evolved PLMN network, a roadside site unit (RSU), etc.

[0143] Figure 2 This is a schematic diagram of the structure of a base station. Figure 2 middle:

[0144] The base station includes at least one processor 201, at least one memory 202, at least one transceiver 203, at least one network interface 204, and one or more antennas 205. The processor 201, memory 202, transceiver 203, and network interface 204 are connected, for example, via a bus. Antenna 205 is connected to transceiver 203. Network interface 204 is used to connect the base station to other communication devices via a communication link. In the embodiments of the present application, the connection may include various interfaces, transmission lines, or buses, etc., which are not limited in this embodiment.

[0145] The processor in the embodiment of the present application, such as the processor 201, may include at least one of the following types: a general-purpose central processing unit (CPU), a digital signal processor (DSP), a microprocessor, an application-specific integrated circuit (ASIC), a microcontroller unit (MCU), a field programmable gate array (FPGA), or an integrated circuit for implementing logical operations. For example, the processor 201 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. At least one processor 201 may be integrated in one chip or located on multiple different chips.

[0146] The memory in the embodiments of the present application, such as memory 202, may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.

[0147] The memory 202 can be independent and connected to the processor 201. Optionally, the memory 202 can also be integrated with the processor 201, for example, integrated into a chip. Among them, the memory 202 can store program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 201. The various types of computer program codes executed can also be regarded as drivers for the processor 201. For example, the processor 201 is used to execute the computer program codes stored in the memory 202, thereby realizing the technical solutions in the embodiments of the present application. Optionally, the memory 202 can also be outside the chip and connected to the processor 201 through an interface.

[0148] The transceiver 203 can be used to support the reception or transmission of radio frequency signals between the access network device and the terminal device. The transceiver 203 can be connected to the antenna 205. The transceiver 203 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 205 can receive radio frequency signals. The receiver Rx of the transceiver 203 is used to receive the radio frequency signals from the antennas, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 201 so that the processor 201 can further process the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in the transceiver 203 is also used to receive modulated digital baseband signals or digital intermediate frequency signals from the processor 201, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 205. Specifically, the receiver Rx can selectively perform one or more stages of down-mixing and analog-to-digital conversion on the RF signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of the down-mixing and analog-to-digital conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of up-mixing and digital-to-analog conversion on the modulated digital baseband signal or digital intermediate frequency signal to obtain a RF signal. The order of the up-mixing and digital-to-analog conversion processes is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as digital signals.

[0149] like Figure 1BAs shown, it should be noted that under the CU-DU separation architecture, the base station consists of two parts: a centralized unit (CU) and a distributed unit (DU). Among them, one possible way is to deploy the radio resource control (RRC) and packet data convergence protocol (PDCP) layer and service data adaptation protocol (SDAP) layer in the CU. The radio link layer control protocol (RLC), media access control (MAC), and physical layer (PHY) are deployed in the DU. Accordingly, the CU has the processing capabilities of RRC, PDCP, and SDAP. The DU has the processing capabilities of RLC, MAC, and PHY. It is worth noting that the above functional division is only an example, and there may be other ways of division. For example, the CU includes the processing capabilities of RRC, PDCP, RLC, and SDAP, and the DU has the processing capabilities of MAC and PHY. For another example, CU includes the processing capabilities of RRC, PDCP, RLC, SDAP and part of MAC (such as adding MAC header), and DU has the processing capabilities of PHY and part of MAC (such as scheduling). The names of CU and DU may change, and any access network node that can implement the above functions can be regarded as the CU and DU in this application. CU-CP has the control plane functions of CU, such as the processing capabilities of RRC and the control plane processing capabilities in PDCP. CU-UP has the user plane functions of CU, such as the processing capabilities of SDAP and the user plane processing capabilities in PDCP. The CU and DU can be connected through the F1 interface, the CU-CP and CU-UP can be connected through the E1 interface, the CU-CP and DU can be connected through the control plane interface (F1-C) of F1, and the CU-UP and DU can be connected through the user plane interface (F1-U) of F1. This application does not limit this.

[0150] It should also be noted that the steps performed by the base stations (such as the first base station, the second base station, the source base station or the target base station) involved in each embodiment of the present application can be performed by the base station, the CU, or the CU-CP, and this application does not limit this.

[0151] Combined with the above Figure 1A The following is a schematic diagram of the application scenario, and the specific implementation plan of this application is introduced below:

[0152] Specifically, in the present application, the second network device may send a first message to the first network device, wherein the first message may include network slice configuration information, and the configuration information is used to indicate the maximum data rate provided by each of the n network slices for the user equipment UE, where n is an integer greater than or equal to 1. After receiving the first message, the first network device determines whether to accept the maximum data rate provided by the n network slices for the terminal device, and returns the result to the second network device. Specifically, the first network device sends a second message to the second network device, and the second message can be used to instruct the first network device to reject the configuration requirement of the maximum data rate provided by m network slices for the UE, where m is an integer greater than or equal to 0 and less than or equal to n.

[0153] Optionally, the first network device and the second network device may be base stations. In one example, the first network device may be a target base station, and the second network device may be a source base station. The present application may be applied to a scenario in which a terminal device switches from a source base station to a target base station. The specific implementation method may refer to scenario one. In another example, the second network device may be a master node (MN) in a dual-connection scenario, and the first network device may be a secondary node (SN). The specific implementation method may refer to scenario two. In another example, the second network device may be a CU in a base station, and the first network device may be a DU in a base station. The specific implementation method may refer to scenario three. In another example, the first network device may be a CU-UP, and the second network device may be a CU-CP. The specific implementation method may refer to scenario four. In another embodiment, the second network device may be an AMF, and the first network device may be a base station. The specific implementation method may refer to scenario five.

[0154] Scene 1

[0155] Combine Figure 1A ,like Figure 3 The figure shows a flow chart of the communication method in the embodiment of the present application. Figure 3 middle:

[0156] Step 101: The source base station sends a first message to the target base station, where the first message includes network slice configuration information.

[0157] Specifically, in this application, the source base station may receive the measurement results of the UE and, based on the measurement results, determine that the UE needs to be handed over to the target base station. It should be noted that the solution described in this application only involves the part related to network slicing current limiting. Other steps, such as the steps of obtaining measurement results, determining whether to switch, and subsequent switching steps, can all be referred to in the existing technology and are not limited in this application.

[0158] Specifically, after the source base station determines that the UE needs to be handed over to the target base station, it can send a handover request message to the target base station to instruct the target base station to prepare the resources required for the UE to be handed over to the target base station. The handover request message can be the first message in this application.

[0159] Optionally, the handover request message may include network slice configuration information, which is used to indicate the maximum data rate provided by each of the n network slices to the UE.

[0160] Optionally, the maximum data rate includes at least one of the following:

[0161] The maximum data rate may be an aggregate maximum bit rate, which is used to limit the aggregate bit rate provided by the network slice for the UE's non-GBR QoS flow and / or guaranteed bit rate quality of service (GBR QoS) flow.

[0162] The maximum data rate may be an uplink aggregate maximum bit rate, used to limit the aggregate bit rate provided by the network slice for an uplink data flow of the UE, where the uplink data flow is an uplink Non-GBR QoS flow and / or an uplink GBR QoS flow;

[0163] The maximum data rate can be the downlink aggregate maximum bit rate, which is used to limit the aggregate bit rate provided by the network slice for the downlink data flow of the UE, where the downlink data flow is a downlink Non-GBR QoS flow and / or a downlink GBR QoS flow.

[0164] That is to say, the sum of the rates of the UE's designated data flows in the network slice, for example, the sum of the data rates of the Non-GBR QoS flow and the GBR QoS flow, does not exceed the specified maximum data rate (that is, the maximum data rate provided by the network slice for the UE).

[0165] Optionally, the maximum data rate can be set by the core network device or by the control device. The specific setting method can refer to the existing technology and will not be described in detail in this application. The control device here can be an operation administration and maintenance (OAM) system or a network management system. This application does not limit the naming method of the control device.

[0166] Optionally, the handover request message also includes the identification information of the UE, the identification of the k PDU sessions of the UE, and the S-NSSAI of the n network slices corresponding to the k PDU sessions. It should be noted that the UE includes k PDU sessions, where the k PDU sessions correspond to n network slices, and each of the n network slices provides the maximum data rate for the corresponding PDU session. As described above, each of the k PDU sessions can correspond to one network slice, and multiple PDU sessions can correspond to the same network slice, where k is an integer greater than or equal to n.

[0167] Step 102: The target base station sends a second message to the source base station.

[0168] Specifically, after receiving the switching request message, the target base station can determine whether it can support the maximum data rate provided by n network slices for the UE based on local available resources and / or local policies.

[0169] Optionally, the locally available resources may be network resources such as bandwidth currently available to the target base station, which is not limited in this application.

[0170] Optionally, the local policy includes, but is not limited to, at least one of the following: an access and mobility management related policy, an operator policy, an access network discovery and selection policy, a UE route selection policy, a session management related policy, etc. For example, the operator policy may be a rate limit policy of the current target base station.

[0171] The target base station may determine the number of acceptable network slices based on locally available resources, or based on local policies, or based on locally available resources and local policies.

[0172] In one example, the target base station may determine, based on locally available resources and / or local policies, to accept the maximum data rate provided by n network slices for the UE, and prepare the resources required for handover for the UE. The target base station may send a second message to the source base station, indicating that the target base station accepts the maximum data rate provided by n network slices for the UE. Optionally, the second message is a handover request acknowledgement message, which is used to indicate that the target base station has prepared the resources required for handover, that is, the target base station accepts the maximum data rate provided by each of the n network slices for the UE.

[0173] In another example, the target base station may determine to reject the maximum data rate provided by m (m is greater than 0 and less than n) network slices for the UE based on local available resources and / or local policies, and the target base station is ready to switch the resources required. The target base station may send a second message to the source base station to indicate that the target base station is ready to switch part of the resources required, and to instruct the target base station to reject the maximum data rate provided by m network slices for the UE. Optionally, the second message is a handover request acknowledgement message. Optionally, the second message may also include rejection information to indicate that the reason why each of the m network slices is rejected is that the target base station does not support the maximum data rate provided by the m network slices for the UE.

[0174] In another example, the target base station may determine to reject the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The target base station may send a second message to the source base station to indicate a handover preparation failure, that is, the target base station rejects the UE from switching to the target base station, and instructs the target base station to reject the maximum data rate provided by n network slices for the UE. Optionally, the second message may be a handover preparation failure message. Optionally, the second message may also include rejection information, indicating that the reason why the target base station rejects the UE from switching to the target base station is that the target base station does not support the maximum data rate provided by n network slices for the UE.

[0175] In one possible implementation, the target base station may send a second message to the source base station, indicating that at least one network slice supported by the target base station is the maximum data rate that the UE can provide. At least one network slice belongs to a rejected network slice. Optionally, the recommendation information may be carried in the second message, or the recommendation information may be carried in a newly defined message. This application is not limited thereto.

[0176] In one possible implementation, the target base station may perform admission control, resource scheduling and other operations on the accepted network slice based on network configuration information, etc., to ensure that the actual data rate of the UE on the network slice does not exceed the maximum data rate provided by the network slice for the UE.

[0177] It should be noted that the “rejection of network slicing”, “rejection of the demand for network slicing” and “rejection of the maximum data rate provided by the network slicing for the UE” involved in this application have the same meaning, which all refer to the network device (such as the target base station) rejecting the maximum data rate provided by the network slicing for at least one PDU session thereon. Therefore, the “reason for the rejection of the network slicing is that the target base station does not support the maximum data rate provided by the network slicing for the UE” involved in this application may be that the reason for the rejection of the PDU session is that the target base station does not support the maximum data rate provided by the network slicing for the UE, and the two have the same meaning.

[0178] In one possible implementation, the rejection information may further include multiple rejection reasons, indicating that the reason the PDU session was rejected was that the target base station did not support the maximum data rate provided by the network slice for the PDU session. Each rejected PDU session may correspond to one rejection reason. For details, please refer to the description in the following embodiments.

[0179] exist Figure 3 Based on the embodiment shown, Figure 4 As shown, it exemplarily shows a flow chart of a communication method, in Figure 4 middle:

[0180] In part 11, the source base station sends a handover request message to the target base station.

[0181] The source base station Figure 1A Take the base station 102 in the example, the target base station is the base station 103, and the UE is the terminal device 104. Specifically, the source base station determines that the UE needs to be handed over to the target base station, and sends a handover request message to the target base station. The handover request message includes but is not limited to: the identifier of the UE, the identifiers of the k PDU sessions of the UE, the S-NSSAI of each network slice of the n network slices corresponding to the k PDU sessions, and the maximum data rate provided by the n network slices for the corresponding PDU session. The maximum data rate provided by the n network slices for the corresponding PDU session can also be understood as the maximum data rate of the PDU session on the corresponding network slice, and can also be understood as the maximum data rate supported or allowed by the source base station for the PDU session on the corresponding network slice.

[0182] For example, on the source base station, the UE includes 4 PDU sessions, namely PDU session 1, PDU session 2, PDU session 3, and PDU session 4. Among them, PDU session 1 corresponds to network slice 1, PDU session 2 corresponds to network slice 2, PDU session 3 corresponds to network slice 3, and PDU session 4 corresponds to network slice 3, that is, PDU session 3 and PDU session 4 both correspond to network slice 3.

[0183] Optionally, the source base station is configured with a maximum data rate provided by each network slice to the UE. For example, on the source base station, the maximum data rate provided by network slice 1 for the UE's PDU session 1 is 20 Mbps, the maximum data rate provided by network slice 2 for PDU session 2 is 15 Mbps, the maximum data rate provided by network slice 3 for PDU session 3 is 10 Mbps, and the maximum data rate provided by network slice 3 for PDU session 4 is 8 Mbps.

[0184] Optionally, the maximum data rate can be used to limit the aggregate bit rate provided by the network slice for the GBR QoS flows and Non-GBR QoS flows of the UE. For example: the UE's PDU session 1 corresponds to network slice 1, where PDU session 1 includes 3 GBR QoS flows and 3 Non-GBR QoS flows. The maximum data rate provided by network slice 1 to the UE can be used to limit the maximum data rate of the GBR QoS flows and Non-GBR QoS flows of PDU session 1 in network slice 1. That is to say, the sum of the data rates of the 3 GBR QoS flows and 3 Non-GBR QoS flows of PDU session 1 cannot exceed the maximum data rate provided by network slice 1 for it.

[0185] In part 12, the target base station determines the acceptance of n network slices based on the local available resources.

[0186] Optionally, the target base station may determine whether to support the network slice requirements one by one based on the order of the maximum data rates provided by the n network slices for the UE. A network slice requirement refers to the resources required for the maximum data rate provided by the network slice for the UE. For example, the target base station arranges the network slice requirements from highest to lowest, such as: Network slice 1 provides a maximum data rate of 20 Mbps for PDU Session 1, Network slice 2 provides a maximum data rate of 15 Mbps for PDU Session 2, Network slice 3 provides a maximum data rate of 10 Mbps for PDU Session 3, and Network slice 3 provides a maximum data rate of 8 Mbps for PDU Session 4. The target base station then checks the requirements sequentially based on available resources. For example, if the total data rate currently provided by the target base station for the network slices is 40 Mbps, then based on the available resources, the target base station determines that it can provide the corresponding resources for PDU Session 1. This can also be understood as the target base station can support the resources required for the maximum data rate provided by network slice 1 for PDU Session 1, resulting in a remaining available resource of 20 Mbps. Next, based on the available resources (20 Mbps), the target base station determines that it can provide the corresponding resources (15 Mbps) for PDU Session 2, resulting in a remaining available resource of 5 Mbps. In addition, based on the remaining network resources (5Mbps), the target base station determines that it cannot support the resources (10Mbps) required for the maximum data rate provided by network slice 3 for PDU session 3, and the target base station further determines that the target base station cannot support the resources (8Mbps) required for the maximum data rate provided by network slice 3 for PDU session 4. The target base station then rejects the demand for network slice 3. It can also be understood that the target base station rejects PDU session 3 and PDU session 4 corresponding to network slice 3.

[0187] Optionally, the target base station can also sort the network slice requirements based on factors such as the importance of the UE's PDU session service and make judgments one by one. The order in which the target base station judges the requirements for n network slices can be set based on actual needs, and this application does not limit it.

[0188] In one example, the target base station can accept the demand for n network slices, entering part 13.

[0189] In another example, the target base station may reject the request for m network slices, as shown in part 14. m is greater than or equal to 0 and less than n.

[0190] In another example, the target base station may reject the request for n network slices and enter the 15 part.

[0191] Other specific details of determining whether to accept the demand for n network slices can be referred to the above embodiments and will not be repeated here.

[0192] In this embodiment, taking the target base station determining the acceptance status of n network slices based on local available resources as an example, the process of the target base station determining the acceptance status of n network slices based on local available resources and local policies, and the target base station determining the acceptance status of n network slices based on local policies are similar to those in this embodiment and will not be repeated here.

[0193] In part 13, the target base station sends a handover request confirmation message to the source base station.

[0194] Specifically, the target base station sends a switching request confirmation message to the source base station, indicating that the target base station is ready for the UE's switching and accepts the maximum data rate provided by n network slices for the UE.

[0195] In part 14, the target base station sends a handover request confirmation message to the source base station, where the message includes rejection information.

[0196] Specifically, when the target base station determines to reject the maximum data rate provided by m network slices for the UE, it sends a handover request confirmation message to the source base station, which is used to indicate that the target base station is ready for the UE's handover, and is also used to indicate that the target base station has rejected the maximum data rate provided by m network slices for the UE. That is to say, in this case, the UE can be switched to the target base station, but at least one PDU session on the m network slices cannot be switched to the target base station, and the target base station discards the at least one PDU session. Still taking the data in part 12 as an example, the target base station determines that it can provide corresponding resources for PDU session 1 and PDU session 2 based on the available resources (40Mbps), and the available resources remain at 5Mbps. In addition, based on the remaining network resources (5Mbps), the target base station determines that it cannot support the resources required for the maximum data rate provided by network slice 3 for PDU session 3, and determines that it cannot support the resources required for the maximum data rate provided by network slice 3 for PDU session 4. The target base station then rejects the requirements of network slice 3, that is, rejects PDU session 3 and PDU session 4 corresponding to network slice 3. That is to say, the target base station rejected one network slice (i.e., network slice 3), but in fact, it rejected two PDU sessions on network slice 3 (PDU session 3 and PDU session 4).

[0197] Optionally, the message carries rejection information, which is used to indicate that the reason why the target base station rejects network slice 3 is that the target base station does not support the maximum data rate provided by network slice 3 to the UE. Exemplarily, the rejection information includes rejection reason 1 and rejection reason 2, and rejection reason 1 is used to indicate that the reason why the target base station rejects network slice 3 (or can be understood as rejecting PDU session 3) is that the target base station does not support the maximum data rate provided by network slice 3 to the UE. Rejection reason 2 is used to indicate that the reason why the target base station rejects network slice 3 (or can be understood as rejecting PDU session 4) is that the target base station does not support the maximum data rate provided by network slice 3 to the UE.

[0198] Optionally, the handover request confirmation message may also carry the maximum data rate provided by at least one of the m network slices (i.e., the rejected network slices) supported by the target base station for the UE. Still taking the data in part 12 as an example, the target base station determines, based on the available resources (40 Mbps), the resources required for the maximum data rate provided for network slice 1 and network slice 2 for the PDU sessions thereon, and the available resources remain at 5 Mbps. In addition, based on the remaining network resources (5 Mbps), the target base station determines that it cannot support the resources required for the maximum data rate provided by network slice 3 for PDU session 3 and PDU session 4 thereon. The target base station then rejects the requirements of network slice 3. At the same time, the target base station may, based on the available remaining network resources (5 Mbps), recommend to the source base station that the target base station can support a maximum data rate of 5 Mbps (or less than 5 Mbps, this data is only an illustrative example) provided by network slice 3 for PDU session 3 and / or PDU session 4. Accordingly, the source base station may determine whether to update the maximum data rate provided by the network slice for the UE based on the recommended value. The specific determination method may be based on the local settings of the source base station, or based on the policy formulated by the AMF, etc., which is not limited in this application. If the maximum data rate provided by the network slice for the UE can be updated according to the recommended value, the source base station will send the updated maximum data rate provided by the network slice for the UE to the target base station. The target base station will then determine the acceptable maximum data rate provided by the network slice for the UE based on the updated maximum data rate, and accept the PDU session corresponding to the network slice.

[0199] In part 15, the target base station sends a handover preparation failure message to the source base station.

[0200] Specifically, the target base station determines to reject the maximum data rate provided by n network slices for the UE, that is, determines not to accept the UE's handover request. The target base station sends a handover preparation failure message to the source base station to indicate that the UE handover has failed, that is, the target base station has not prepared resources for the UE's handover.

[0201] Optionally, the handover preparation failure message may carry rejection information, indicating that the reason why the target base station rejected n network slices is that the target base station does not support the maximum data rate provided by n network slices for the UE. In other words, the reason for the handover failure is that the target base station rejected the demand for n network slices, that is, it is unable to provide corresponding resources for k PDU sessions.

[0202] Optionally, the handover preparation failure message may carry recommendation information to indicate that the target base station can support the maximum data rate provided to the UE by at least one slice among the n network slices. Specific details can be found above and are not repeated here.

[0203] Scene 2

[0204] Combine Figure 1A ,like Figure 5 The figure shows a flow chart of the communication method in the embodiment of the present application. Figure 5 middle:

[0205] Step 201: The primary node sends a first message to the secondary node, wherein the first message includes network slice configuration information.

[0206] Specifically, the primary node can provide the UE with a control plane connection to the core network, and the secondary node can provide the UE with additional resources (such as a user plane connection from the UE to the core network), but does not provide a control plane connection to the core network. That is, the primary node and the secondary node correspond to the same network slice, and the sum of the resources of the network slice on the primary node and the resources of the network slice on the secondary node is equal to the resources allocated by the core network for the network slice. For example: the core network sets the maximum data rate provided by network slice 1 to 20Mbps for the UE. Then, the primary node can set the maximum data rate of the UE on network slice 1 to 15Mbps, and the secondary node sets the maximum data rate of the UE on network slice 1 to 5Mbps. That is, the sum of the maximum data rates of the UE on the network slices on the primary node and the secondary node is less than or equal to the maximum data rate set for it by the core network.

[0207] Optionally, in the present application, the primary node may increase or modify the maximum data rate of the UE in at least one network slice on the secondary node.

[0208] In one example, the primary node may send an SN addition request (S-Node addition request, or SeNB addition request, or SgNB addition request) message to the secondary node (the SN addition request message may be the first message in this application), which may include network slice configuration information to indicate the maximum data rate provided by each of the n network slices to the UE. It should be noted that the request may be sent during the dual link establishment process, that is, the message is used to instruct the secondary node to prepare the required resources for the dual link operation of the UE. In other words, the primary node instructs the secondary node to perform processing such as acceptance and scheduling on the n network slices based on the network slice configuration information.

[0209] In another example, the primary node may send an SN modification request (S-Node modification request, or SeNB modification request, or SgNB modification request) message to the secondary node (the SN modification request message may be the first message in this application), which may include network slice configuration information for indicating the maximum data rate provided by each of the n network slices for the UE. The request may be used to instruct the secondary node to modify the maximum data rate provided by the n network slices for the UE based on the network slice configuration information.

[0210] For other details, please refer to Scenario 1 and will not be repeated here.

[0211] Step 202: The secondary node sends a second message to the primary node.

[0212] Specifically, after receiving the first message, the secondary node can determine whether it can support the maximum data rate provided by n network slices to the UE based on local available resources and / or local policies.

[0213] In one example, the secondary node may determine to accept the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The secondary node may send a second message to the primary node to indicate that the secondary node accepts the maximum data rate provided by n network slices for the UE. Optionally, if the first message is an SN addition request message, the second message may be an SN addition request acknowledgement (S-Node addition request acknowledge, or SeNB addition request acknowledge, or SgNB addition request acknowledge) message (this message is the second message in this embodiment. Optionally, if the first message is an SN modification request message, the second message may be an SN modification request acknowledgement (S-Node modification request acknowledge, or SeNB modification request acknowledge, or SgNB modification request acknowledge) message (this message is the second message in this embodiment), indicating that the secondary node accepts the maximum data rate provided by n network slices for the UE and has completed the modification of the resources of the secondary node.

[0214] In another example, the secondary node may determine, based on locally available resources and / or local policies, to reject the maximum data rate provided by m (m is greater than 0 and less than n) network slices for the UE. The secondary node may send a second message to the primary node, instructing the secondary node to reject the maximum data rate provided by m network slices for the UE. Optionally, if the first message is an SN add request message, the second message may be an SN add request confirmation message. Optionally, if the first message is an SN modify request message, the second message may be an SN modify request confirmation message.

[0215] In another example, the secondary node may determine to reject the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The secondary node may send a second message to the primary node to instruct the secondary node to reject the maximum data rate provided by n network slices for the UE. Optionally, if the first message is an SN addition request message, the second message may be an SN addition request reject (S-Node addition request reject, or SeNB additionrequest reject, or SgNB addition request reject) message. Optionally, if the first message is an SN modification request message, the second message may be an SN modification request reject (S-Node modification request reject, or SeNB modification request reject, or SgNB modification request reject) message (this message is the second message in this embodiment).

[0216] Optionally, the second message may also include rejection information to indicate the reason why the secondary node failed to add or modify resources for the UE, that is, the reason for rejecting m or n network slices is that the secondary node does not support the maximum data rate provided by m or n network slices for the UE.

[0217] In one possible implementation, the second message may further include recommendation information indicating that at least one network slice supported by the secondary node represents the maximum data rate that the UE can provide. The at least one network slice is a rejected network slice. The details will be described in the following embodiments.

[0218] In one possible implementation, the secondary node may perform admission control, resource scheduling, and other operations on the accepted network slice based on network configuration information, etc., to ensure that the actual data rate of the UE on the network slice does not exceed the maximum data rate provided by the network slice for the UE.

[0219] It should be noted that rejecting a network slice means rejecting the PDU session corresponding to the network slice. Therefore, the "reason for the rejection of the network slice is that the secondary node does not support the maximum data rate provided by the network slice for the UE" involved in this application may be that the reason for the rejection of the PDU session is that the secondary node does not support the maximum data rate provided by the network slice for the UE, and the two have the same meaning.

[0220] exist Figure 5 Based on the embodiment shown, Figure 6 As shown, it exemplarily shows a flow chart of a communication method, in Figure 6 middle:

[0221] In part 21, the primary node sends an SN add request message to the secondary node.

[0222] Specifically, the primary node obtains the maximum data rate provided by each network slice of the n network slices configured in the core network for the UE. For example, the configuration is as follows: the maximum data rate provided by network slice 1 for the UE's PDU session 1 is 20 Mbps, the maximum data rate provided by network slice 2 for PDU session 2 is 15 Mbps, the maximum data rate provided by network slice 3 for PDU session 3 is 10 Mbps, and the maximum data rate provided by network slice 3 for PDU session 4 is 5 Mbps. Based on the above configuration, the primary node can set the maximum data rate for the UE on the network slice on the primary node and the maximum data rate for the UE on the network slice on the secondary node. For example: the primary node can set the maximum data rate of PDU session 1 in network slice 1 on the primary node to 10Mbps, and the maximum data rate of PDU session 1 in network slice 1 on the secondary node to 10Mbps; the maximum data rate of PDU session 2 in network slice 2 on the primary node is 10Mbps, and the maximum data rate of PDU session 2 in network slice 2 on the secondary node is 5Mbps; the maximum data rate of PDU session 3 in network slice 3 on the primary node is 10Mbps, and the maximum data rate of PDU session 4 in network slice 3 on the secondary node is 5Mbps.

[0223] The primary node may send an SN add request message to the secondary node, which includes but is not limited to at least one of the following: the identifier of the UE, the identifiers of the k PDU sessions that need to be added in the secondary node, and the S-NSSAI of the n network slices corresponding to the k PDU sessions, network slice configuration information, etc. Among them, the network slice configuration information is used to indicate the maximum data rate provided by each of the n network slices for the corresponding PDU session. This message can be used to instruct the secondary node to increase the dual-link resources required for k PDU sessions. In this embodiment, based on the above-mentioned configuration of the primary node, the primary node may instruct the secondary node to increase the required resources for PDU session 1 and PDU session 2. For example: the network slice configuration information is used to indicate that the maximum data rate provided by network slice 1 for PDU session 1 is 10Mbps, that is, the secondary node is expected to increase resources on the secondary node to meet the maximum data rate provided by network slice 1 for PDU session 1.

[0224] In part 22, the secondary node determines the acceptance of n network slices based on the locally available resources.

[0225] Optionally, the secondary node may determine whether to accept the dual connection request of the PDU session based on locally available resources, that is, determine the acceptance of n network slices. For specific details, please refer to Scenario 1 and will not be repeated here.

[0226] In one example, a secondary node may accept a request for n network slices, entering the 23 part.

[0227] In another example, the secondary node may reject the request for m network slices and enter the 24-part. m is greater than or equal to 0 and less than n.

[0228] In another example, a secondary node may reject the request for n network slices and enter the 25 part.

[0229] In part 23, the secondary node sends an SN addition request confirmation message to the primary node.

[0230] Specifically, the secondary node sends an SN increase request confirmation message to the primary node, indicating that the secondary node has prepared resources for the dual-link operations of PDU session 1, PDU session 2 and PDU session 4, that is, the secondary node accepts the maximum data rate provided by network slice 1 for PDU session 1, the maximum data rate provided by network slice 2 for PDU session 2, and the maximum data rate provided by network slice 3 for PDU session 4 indicated by the primary node.

[0231] In part 24, the secondary node sends an SN addition request confirmation message to the primary node, which includes rejection information.

[0232] Specifically, the secondary node sends an SN addition request confirmation message to the primary node, wherein the message includes rejection information, which is used to indicate that the reason why the secondary node failed to add resources for the PDU session is that the secondary node does not support the maximum data rate provided by the network slice corresponding to the PDU session for the UE. Optionally, the rejection information includes multiple rejection reasons, that is, each rejected PDU session corresponds to one rejection reason. For example: When the secondary node determines to reject the maximum data rate provided by network slice 2 for PDU session 2 and the maximum data rate provided by network slice 3 for PDU session 4 based on local available resources, the secondary node sends an SN increase request confirmation message to the primary node, which is used to instruct the secondary node to prepare resources for the dual-link operation of the UE, and the secondary node rejects the increase of resources corresponding to the maximum data rate (5Mbps) required by network slice 2 (that is, the maximum data rate provided by network slice 2 for PDU session 2 on the secondary node), and the secondary node rejects the increase of resources corresponding to the maximum data rate (5Mbps) required by network slice 3 (that is, the maximum data rate provided by network slice 3 for PDU session 4 on the secondary node). In other words, the secondary node cannot provide the resources required for dual-connection operations for PDU session 2 and PDU session 4.

[0233] In part 25, the secondary node sends an SN addition request failure message to the primary node.

[0234] Specifically, the secondary node sends an SN increase request failure message to the primary node, which includes rejection information, indicating that the secondary node failed to increase resources for k PDU sessions, that is, the secondary node rejects the maximum data rate provided by n network slices for k PDUs.

[0235] The scenario in which the primary node instructs the secondary node to modify the corresponding resources based on the network slice configuration information is similar to the above steps and will not be repeated in this application.

[0236] Scene 3

[0237] Combine Figure 1B ,like Figure 7 The figure shows a flow chart of the communication method in the embodiment of the present application. Figure 7 middle:

[0238] Step 301: CU sends a first message to DU, where the first message includes network slice configuration information.

[0239] In an example, the first message may be a UE context setup request message, which is used to request the DU to set the context of the UE.

[0240] In another example, the first message may be a UE context modification request message, which is used to provide the DU with changes in UE context information.

[0241] Optionally, the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by n network slices to the UE. Exemplarily, in this embodiment, the network slice configuration information may include the maximum data rate provided by each of the n network slices corresponding to k data resource bearers (DRBs) to the UE.

[0242] For other details, please refer to Scenario 1 and Scenario 2, which will not be repeated here.

[0243] Step 302: The DU sends a second message to the CU.

[0244] Specifically, after receiving the first message, the DU can determine whether it can support the maximum data rate provided by n network slices to the UE based on local available resources and / or local policies.

[0245] In one example, the DU may determine to accept the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The DU may send a second message to the CU to indicate that the DU accepts the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a UE context setup request message, the second message may be a UE context setup response message. Optionally, if the first message is a UE context modification request message, the second message may be a UE context modification response message.

[0246] In another example, the DU may determine to reject the maximum data rate provided by m (m is greater than 0 and less than n) network slices for the UE based on local available resources and / or local policies. The DU may send a second message to the CU to indicate that the DU rejects the maximum data rate provided by m network slices for the UE. Optionally, if the first message is a UE context setup request message, the second message may be a UE context setup response message. Optionally, if the first message is a UE context modification request message, the second message may be a UE context modification response message.

[0247] In another example, the DU may determine to reject the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The DU may send a second message to the CU to instruct the DU to reject the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a UE context setup request message, the second message may be a UE context setup failure message. Optionally, if the first message is a UE context modification request message, the second message may be a UE context modification failure message.

[0248] Optionally, the second message may also include rejection information, which is used to indicate that the DU failed to set or modify the DRB, that is, the reason for rejecting m or n network slices is that the DU does not support the maximum data rate provided by m or n network slices for the UE.

[0249] It should be noted that rejecting a network slice means rejecting the DRB corresponding to the network slice. Therefore, the "reason for rejecting the network slice is that the DU does not support the maximum data rate provided by the network slice for the UE" involved in this application may be that the reason for rejecting the DRB is that the DU does not support the maximum data rate provided by the network slice for the UE, and the two have the same meaning.

[0250] In one possible implementation, the second message may further include recommendation information for indicating that at least one network slice supported by the DU is a maximum data rate that can be provided by the UE, wherein at least one network slice belongs to a rejected network slice.

[0251] Scene 4

[0252] Combine Figure 1B ,like Figure 8 The figure shows a flow chart of the communication method in the embodiment of the present application. Figure 8 middle:

[0253] Step 401: CU-CP sends a first message to CU-UP, where the first message includes network slice configuration information.

[0254] In an example, the first message may be a bearer context setup request message, which is used to request the CU-UP to set a bearer context.

[0255] In another example, the first message may be a bearer context modification request message, which is used to request the CU-UP to modify the bearer context.

[0256] Optionally, the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices to the UE. Exemplarily, in this embodiment, the network slice configuration information may include the maximum data rate provided by each of the n network slices for the corresponding PDU session.

[0257] For other details, please refer to Scenario 1, Scenario 2, and Scenario 3, which will not be repeated here.

[0258] Step 402: The CU-UP sends a second message to the CU-CP.

[0259] Specifically, after receiving the first message, CU-UP can determine whether it can support the maximum data rate provided by n network slices to the UE based on local available resources and / or local policies.

[0260] In one example, the CU-UP may determine the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The CU-UP may send a second message to the CU-CP to instruct the CU-UP to accept the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a bearer context setup request message, the second message may be a bearer context setup response message. Optionally, if the first message is a bearer context modification request message, the second message may be a bearer context modification response message.

[0261] In another example, the CU-UP may determine to reject the maximum data rate provided by m (m is greater than 0 and less than n) network slices for the UE based on local available resources and / or local policies. The CU-UP may send a second message to the CU-CP to instruct the CU-UP to reject the maximum data rate provided by m network slices for the UE. Optionally, if the first message is a bearer context setup request message, the second message may be a bearer context setup response message. Optionally, if the first message is a bearer context modification request message, the second message may be a bearer context modification response message.

[0262] In another example, the CU-UP may determine to reject the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The CU-UP may send a second message to the CU-CP to instruct the CU-UP to reject the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a bearer context setup request message, the second message may be a bearer context setup failure (bearer context setup failure) message. Optionally, if the first message is a bearer context modification request message, the second message may be a bearer context modification failure (bearer context modification failure) message.

[0263] Optionally, the second message may also include rejection information, which is used to indicate that the CU-UP failed to set or modify the bearer context, that is, the reason for rejecting m or n network slices is that the CU-UP does not support the maximum data rate provided by m or n network slices to the UE.

[0264] It should be noted that rejecting a network slice means rejecting the PDU session corresponding to the network slice. Therefore, the "reason for the rejection of the network slice is that the CU-UP does not support the maximum data rate provided by the network slice for the UE" involved in this application may be that the reason for the rejection of the PDU session is that the CU-UP does not support the maximum data rate provided by the network slice for the UE, and the two have the same meaning.

[0265] In one possible implementation, the second message may further include recommendation information, which is used to indicate that at least one network slice supported by the CU-UP is a maximum data rate that can be provided by the UE, wherein the at least one network slice is a rejected network slice.

[0266] Scene 5

[0267] Combine Figure 1A ,like Figure 9 The figure shows a flow chart of the communication method in the embodiment of the present application. Figure 9 middle:

[0268] Step 501: AMF sends a first message to the base station, where the first message includes network slice configuration information.

[0269] In one example, the first message may be a PDU session resource setup request message, which is used by the base station to allocate resources for at least one PDU session.

[0270] In another example, the first message may be an initial context setup request (initial context setup request) message, used to request setting of a UE context.

[0271] In another example, the first message may be a UE context modification request (UE context modification request) message, which is used to provide the base station with information changes of the UE context.

[0272] In another example, the first message may be a downlink non-access stratum (NAS) transport message, which is used to carry NAS information on the NG interface, thereby sending the NAS information to the UE.

[0273] Optionally, the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices to the UE. Exemplarily, in this embodiment, the network slice configuration information may include the maximum data rate provided by each of the n network slices for the corresponding PDU session.

[0274] For other details, please refer to Scenario 1, Scenario 2, Scenario 3, and Scenario 4, which will not be repeated here.

[0275] Step 502: The base station sends a second message to the AMF.

[0276] Specifically, after receiving the first message, the base station can determine whether it can support the maximum data rate provided by n network slices to the UE based on local available resources and / or local policies.

[0277] In one example, the base station may determine to accept the maximum data rate provided by n network slices for the UE based on local available resources and / or local policies. The base station may send a second message to the AMF to indicate that the base station accepts the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a PDU session resource setup request message, the second message may be a PDU session resource setup response (PDU session resource setup response) message. Optionally, if the first message is an initial context setup request message, the second message may be an initial context setup response (initialcontext setup response) message. Optionally, if the first message is a UE context modification request, please refer to scenario three, which will not be described here.

[0278] In another example, the base station may determine to reject the maximum data rate provided by m (m is greater than 0 and less than n) network slices for the UE based on local available resources and / or local policies. The base station may send a second message to the AMF to instruct the base station to reject the maximum data rate provided by m network slices for the UE. Optionally, if the first message is a PDU session resource setup request message, the second message may be a PDU session resource setup response message. Optionally, if the first message is an initial context setup request message, the second message may be an initial context setup response (initial context setup response) message. Optionally, if the first message is a UE context modification request, please refer to scenario three, which will not be described here.

[0279] In another example, the base station may determine to reject the maximum data rate provided by n network slices for the UE based on locally available resources and / or local policies. The base station may send a second message to the AMF to instruct the base station to reject the maximum data rate provided by n network slices for the UE. Optionally, if the first message is a PDU session resource setting request message, the second message may be a PDU session resource setting response message. Optionally, if the first message is an initial context setup request message, the second message may be an initial context setup failure message. Optionally, if the first message is a UE context modification request, please refer to scenario three, which will not be described here.

[0280] Optionally, the second message may also include rejection information, used to indicate that the reason why the base station rejects m or n network slices is that the base station does not support the maximum data rate provided by m or n network slices to the UE.

[0281] Optionally, if the first message is a downlink NAS transmission message, the base station can perform admission control and / or resource scheduling on the network slice based on the acceptance status of n network slices and the network slice configuration information, without sending a second message to the AMF.

[0282] In one possible implementation, the second message may further include recommendation information for indicating that at least one network slice supported by the base station is a maximum data rate that can be provided by the UE, wherein the at least one network slice is a rejected network slice.

[0283] It should be noted that rejecting a network slice means rejecting the PDU session corresponding to the network slice. Therefore, the "reason for the rejection of the network slice is that the base station does not support the maximum data rate provided by the network slice for the UE" involved in this application can be that the reason for the rejection of the PDU session is that the base station does not support the maximum data rate provided by the network slice for the UE, and the two have the same meaning.

[0284] exist Figure 9 and Figure 3 Based on the embodiment shown, Figure 10 As shown, it exemplarily shows a flow chart of a communication method, in Figure 10 middle:

[0285] In part 31, the source base station sends a handover required message to the AMF.

[0286] In part 32, the AMF sends a handover request message to the target base station, where the message includes network configuration information.

[0287] Optionally, the switching request message sent by the AMF to the target base station includes but is not limited to: the identifiers of k PDU sessions that need to be switched from the source base station to the target base station, the S-NSSAI of each of the n network slices corresponding to the k PDU sessions, and the network slice configuration information.

[0288] It should be noted that in this embodiment, the AMF caches all configurations of the network slice on the active base station. Therefore, the switching request message sent by the source base station to the AMF may not carry the network slice configuration information.

[0289] In part 33, the target base station determines the acceptance of n network slices based on local available resources and / or local policies.

[0290] In one example, the target base station can accept the demand for n network slices, entering the 34 part.

[0291] In another example, the target base station may reject the request for m network slices, entering part 36. m is greater than or equal to 0 and less than n.

[0292] In another example, the target base station may reject the request for n network slices and enter part 38.

[0293] In part 34, the target base station sends a handover request acknowledgement message to the AMF.

[0294] In part 35, the AMF sends a handover command message to the source base station.

[0295] Specifically, after receiving the handover request confirmation message, the AMF sends a handover command message to the source base station.

[0296] In part 36, the target base station sends a handover request confirmation message to the AMF.

[0297] Optionally, the message includes rejection information, used to instruct the target base station to reject the maximum data rate provided by m network slices to the UE.

[0298] Optionally, the message includes recommendation information for indicating that at least one network slice supported by the target base station is a maximum data rate that can be provided by the UE, wherein at least one network slice belongs to a rejected network slice.

[0299] In part 37, the AMF sends a handover command message to the source base station.

[0300] Specifically, after receiving the handover request confirmation message, the AMF sends a handover command message to the source base station.

[0301] Optionally, the message includes rejection information, used to instruct the target base station to reject the maximum data rate provided by m network slices to the UE.

[0302] Optionally, the message includes recommendation information for indicating that at least one network slice supported by the target base station is a maximum data rate that can be provided by the UE, wherein at least one network slice belongs to a rejected network slice.

[0303] In part 38, the target base station sends a handover failure message to the AMF.

[0304] Optionally, the message includes rejection information, used to instruct the target base station to reject the maximum data rate provided by n network slices to the UE.

[0305] Optionally, the message includes recommendation information for indicating that at least one network slice supported by the target base station is a maximum data rate that can be provided by the UE, wherein at least one network slice belongs to a rejected network slice.

[0306] In part 39, the AMF sends a handover preparation failure message to the source base station.

[0307] Specifically, after receiving the handover failure message, the AMF sends a handover preparation failure message to the source base station.

[0308] Optionally, the message includes rejection information, used to instruct the target base station to reject the maximum data rate provided by n network slices to the UE.

[0309] Optionally, the message includes recommendation information for indicating that at least one network slice supported by the target base station is a maximum data rate that can be provided by the UE, wherein at least one network slice belongs to a rejected network slice.

[0310] It should be noted that rejecting a network slice means rejecting the PDU session corresponding to the network slice. Therefore, the "reason for the rejection of the network slice is that the target base station does not support the maximum data rate provided by the network slice for the UE" involved in this application may be that the reason for the rejection of the PDU session is that the target base station does not support the maximum data rate provided by the network slice for the UE, and the two have the same meaning.

[0311] Optionally, in this application, the first network device may also be a new base station, and the second network device may be an old base station, such as Figure 11 In this scenario, the UE is in an inactive state and moves from the old base station to the new base station. The UE requests to be converted from the inactive state to the active state. Accordingly, the new base station needs to obtain the UE context from the old base station. In the process of obtaining the UE context, the new base station can obtain the maximum data rate provided by the network slice for the UE from the old base station. For details, refer to Figure 11 , after the new base station receives the RRC resume request (RRC resumerequest) message sent by the UE, it may send a retrieve UE context request (retrieve UE context request) message to the old base station to request the old base station to transfer the UE context to the new base station. Then, the old base station sends a retrieve UE context response (retrieve UE context response) message to the new base station, wherein the message includes network slice configuration information, which is used to indicate the maximum data rate provided by n network slices for the UE. The new base station may determine whether to accept the maximum data rate provided by n network slices for the UE based on local available resources and / or local policies, and perform RRC connection reconfiguration and other operations on the UE based on the maximum data rate provided by the accepted network slices for the UE. It should be noted that in this embodiment, the new base station does not need to send a second message to the old base station.

[0312] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that in order to implement the above functions, the network device (including the first network device and the second network device) includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0313] The embodiments of the present application can divide the functional modules of the network device according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0314] In the case where each functional module is divided into each functional module, in the case where each functional module is divided into each functional module, in one example, Figure 12 A possible structural diagram of the first network device 300 involved in the above embodiment is shown. Figure 12 As shown, the first network device may include: a receiving module 301 and a sending module 302. The receiving module 301 may be used to perform the step of "receiving a first message from a second network device." For example, the module may be used to support the first network device in executing steps 101, 201, 301, 401, and 501 in the above-described method embodiment. The sending module 302 may be used to perform the step of "sending a second message to the second network device." For example, the module may be used to support the first network device in executing steps 102, 202, 302, 402, and 502 in the above-described method embodiment.

[0315] In one example, Figure 13 A possible structural diagram of the second network device 400 involved in the above embodiment is shown. Figure 13 As shown, the second network device may include: a sending module 401 and a receiving module 402. The sending module 401 may be used to perform the step of "sending a first message to the first network device." For example, the module may be used to support the second network device in executing steps 101, 201, 301, 401, and 501 in the above-described method embodiment. The receiving module 402 may be used to perform the step of "receiving a second message from the first network device." For example, the module may be used to support the second network device in executing steps 102, 202, 302, 402, and 502 in the above-described method embodiment.

[0316] In another embodiment, Figure 14 A possible structural diagram of the first network device 500 involved in the above embodiment is shown. Figure 14As shown, the first network device 500 may include: a receiving module 501 and a processing module 502. The receiving module 501 may be used for the step of "receiving a first message from a second network device". The processing module 502 may be used for the step of "performing resource scheduling and / or admission control for n network slices based on network slice configuration information". The first network device 500 may perform the following steps: Figure 11 The relevant steps of the illustrated embodiment will not be repeated here.

[0317] In yet another embodiment, Figure 15 A possible structural diagram of the first network device 600 involved in the above embodiment is shown. Figure 15 As shown, the first network device 600 may include: a receiving module 601 and a sending module 602. The receiving module 601 may be used for the step of "receiving a first message sent by the second network device". For example, the module may be used to support the first network device to execute part 31 of the above method embodiment. The sending module 602 may be used for the step of "after the receiving module receives the first message, the second message is sent to the third network device". For example, the module may be used to support the first network device to execute part 32 of the above method embodiment. The receiving module 601 is also used for the step of "receiving a third message sent by the third network device". For example, the module may be used to support the first network device to execute parts 34, 36, and 38 of the above method embodiment. The sending module 602 is also used for the step of "after the receiving module receives the third message, the fourth message is sent to the second network device". For example, the module may be used to support the first network device to execute parts 35, 37, and 39 of the above method embodiment. That is, the first network device 600 may execute as follows Figure 10 Relevant steps of the embodiment shown.

[0318] The following describes a device 700 provided in an embodiment of the present application. Figure 16 As shown:

[0319] The device includes a processing module 701 and a communication module 702. Optionally, the device also includes a storage module 703. The processing module 701, the communication module 702 and the storage module 703 are connected via a communication bus.

[0320] The communication module 702 may be a device with transceiver functions, used to communicate with other network devices or communication networks.

[0321] The storage module 703 may include one or more memories, and the memory may be a device in one or more devices or circuits for storing programs or data.

[0322] The storage module 703 can exist independently and be connected to the processing module 701 via a communication bus. The storage module can also be integrated with the processing module 701.

[0323] The apparatus 700 may be used in a network device, a circuit, a hardware component, or a chip.

[0324] The apparatus 700 may be a network device in the embodiment of the present application, for example, the base station 102 or the base station 103. The schematic diagram of the base station may be as follows: Figure 2 Optionally, the communication module 702 of the apparatus 700 may include an antenna and a transceiver of a base station, for example Figure 2 The communication module 702 may also include a network interface of a base station, such as Figure 2 The network interface 204 in.

[0325] The device 700 may be a chip in a network device (e.g., a source base station, an AMF, etc.) in an embodiment of the present application. The communication module 702 may be an input or output interface, a pin, or a circuit, etc. Optionally, the storage module may store computer-executable instructions of the method on the base station side, so that the processing module 701 executes the method on the base station side in the above embodiment. The storage module 703 may be a register, a cache, or a RAM, etc. The storage module 703 may be integrated with the processing module 701; the storage module 703 may be a ROM or other type of static storage device that can store static information and instructions, and the storage module 703 may be independent of the processing module 701. Optionally, with the development of wireless communication technology, a transceiver may be integrated into the device 700, for example, the communication module 702 integrates the transceiver 103 and the network interface 104.

[0326] When the apparatus 700 is a network device or a chip in a network device in an embodiment of the present application, the method executed by the network device in the above embodiment can be implemented.

[0327] The embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. If implemented in software, the functions can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any available medium that can be accessed by a computer.

[0328] As an optional design, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the required program code in the form of instructions or data structures and can be accessed by the computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) is used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and Blu-ray disks, where disks generally reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0329] The present application also provides a computer program product. The methods described in the above embodiments can be implemented in whole or in part through software, hardware, firmware, or any combination thereof. If implemented in software, they can be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on a computer, the processes or functions described in the above method embodiments are generated in whole or in part. The above computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device.

[0330] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A communication method, characterized in that: Applied to a first network device, the method includes: Receive a first message from a second network device, where the first message includes network slice configuration information, where the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1; In response to receiving the first message, sending a second message to the second network device; The network slice configuration information includes at least one of the following: The second indication information is used to indicate an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, where the uplink data flow is an uplink Non-GBR QoS flow and / or an uplink GBR QoS flow; The third indication information is used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, where the downlink data flow is a downlink Non-GBR QoS flow and / or a downlink GBR QoS flow.

2. The method according to claim 1, characterized in that The first message is a handover request message; or, The first message is a UE context setting request message or a UE context modification request message; or, The first message is a bearer context setting request message or a bearer context modification request message; or, The first message is a secondary node addition request message or a secondary node modification request message; or, The first message is a PDU session resource setting request message or an initial context setting request message.

3. The method according to claim 1 or 2, characterized in that The second message is a handover request response message; or, The second message is a UE context setting request response message or a UE context modification response message; or, The second message is a bearer context setting request response message or a bearer context modification response message; or, The second message is a secondary node addition request response message or a secondary node modification request response message; or, The second message is a PDU session resource setting request response message or an initial context setting request response message.

4. A communication method, characterized in that: Applied to the second network device, the method includes: Sending a first message to a first network device, where the first message includes network slice configuration information, where the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1; receiving a second message sent by the first network device in response to the first message; The network slice configuration information includes at least one of the following: The second indication information is used to indicate an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, where the uplink data flow is an uplink Non-GBR QoS flow and / or an uplink GBR QoS flow; The third indication information is used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, where the downlink data flow is a downlink Non-GBR QoS flow and / or a downlink GBR QoS flow.

5. The method according to claim 4, characterized in that The first message is a handover request message; or, The first message is a UE context setting request message or a UE context modification request message; or, The first message is a bearer context setting request message or a bearer context modification request message; or, The first message is a secondary node addition request message or a secondary node modification request message; or, The first message is a PDU session resource setting request message or an initial context setting request message.

6. The method according to claim 4 or 5, characterized in that The second message is a handover request response message; or, The second message is a UE context setting request response message or a UE context modification response message; or, The second message is a bearer context setting request response message or a bearer context modification response message; or, The second message is a secondary node addition request response message or a secondary node modification request response message; or, The second message is a PDU session resource setting request response message or an initial context setting request response message.

7. A communication device, characterized in that: Applied to a first network device, the apparatus includes: a memory and a processor, the memory and the processor being coupled; The memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: Receive a first message from a second network device, where the first message includes network slice configuration information, where the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1; In response to receiving the first message, sending a second message to the second network device; The network slice configuration information includes at least one of the following: The second indication information is used to indicate an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, where the uplink data flow is an uplink Non-GBR QoS flow and / or an uplink GBR QoS flow; The third indication information is used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, where the downlink data flow is a downlink Non-GBR QoS flow and / or a downlink GBR QoS flow.

8. The device according to claim 7, characterized in that The first message is a handover request message; or, The first message is a UE context setting request message or a UE context modification request message; or, The first message is a bearer context setting request message or a bearer context modification request message; or, The first message is a secondary node addition request message or a secondary node modification request message; or, The first message is a PDU session resource setting request message or an initial context setting request message.

9. The device according to claim 7 or 8, characterized in that The second message is a handover request response message; or, The second message is a UE context setting request response message or a UE context modification response message; or, The second message is a bearer context setting request response message or a bearer context modification response message; or, The second message is a secondary node addition request response message or a secondary node modification request response message; or, The second message is a PDU session resource setting request response message or an initial context setting request response message.

10. A communication device, characterized in that: Applied to a second network device, the apparatus includes: a memory and a processor, the memory and the processor being coupled; The memory stores program instructions, and when the program instructions are executed by the processor, the device performs the following steps: Sending a first message to a first network device, where the first message includes network slice configuration information, where the network slice configuration information is used to indicate a maximum data rate provided by each of n network slices for the terminal device, where n is an integer greater than or equal to 1; receiving a second message sent by the first network device in response to the first message; The network slice configuration information includes at least one of the following: The second indication information is used to indicate an aggregate bit rate provided by each of the n network slices for an uplink data flow of the terminal device, where the uplink data flow is an uplink Non-GBR QoS flow and / or an uplink GBR QoS flow; The third indication information is used to indicate the aggregate bit rate provided by each of the n network slices for the downlink data flow of the terminal device, where the downlink data flow is a downlink Non-GBR QoS flow and / or a downlink GBR QoS flow.

11. The device according to claim 10, characterized in that The first message is a handover request message; or, The first message is a UE context setting request message or a UE context modification request message; or, The first message is a bearer context setting request message or a bearer context modification request message; or, The first message is a secondary node addition request message or a secondary node modification request message; or, The first message is a PDU session resource setting request message or an initial context setting request message.

12. The device according to claim 10 or 11, characterized in that The second message is a handover request response message; or, The second message is a UE context setting request response message or a UE context modification response message; or, The second message is a bearer context setting request response message or a bearer context modification response message; or, The second message is a secondary node addition request response message or a secondary node modification request response message; or, The second message is a PDU session resource setting request response message or an initial context setting request response message.

13. A computer-readable storage medium storing a computer program, wherein the computer program comprises at least one code segment, and the at least one code segment can be executed by a computer to control the computer to execute the method according to any one of claims 1 to 3.

14. A computer-readable storage medium storing a computer program, wherein the computer program comprises at least one code segment, and the at least one code segment can be executed by a computer to control the computer to execute the method according to any one of claims 4 to 6.

15. A computer program product, characterized in that The method comprises computer instructions, which, when executed on a computer, enable the method according to any one of claims 1 to 3 to be executed.

16. A computer program product, characterized in that The method comprises computer instructions, which, when executed on a computer, enable the method according to any one of claims 4 to 6 to be executed.

Images