WO2021057549A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2021057549A1
WO2021057549A1 PCT/CN2020/115328 CN2020115328W WO2021057549A1 WO 2021057549 A1 WO2021057549 A1 WO 2021057549A1 CN 2020115328 W CN2020115328 W CN 2020115328W WO 2021057549 A1 WO2021057549 A1 WO 2021057549A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
message
data rate
terminal device
maximum data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/115328
Other languages
English (en)
French (fr)
Inventor
杨水根
韩锋
晋英豪
谭巍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20869389.5A priority Critical patent/EP4030820B1/en
Priority to KR1020227013975A priority patent/KR20220086584A/ko
Publication of WO2021057549A1 publication Critical patent/WO2021057549A1/zh
Priority to US17/704,362 priority patent/US12363601B2/en
Anticipated expiration legal-status Critical
Priority to US19/242,485 priority patent/US20250380194A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0257—Traffic management, e.g. flow control or congestion control per individual bearer or channel the individual bearer or channel having a maximum bit rate or a bit rate guarantee
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists

Definitions

  • the embodiments of the present application relate to the field of communication, and in particular to a communication method and device.
  • the method of limiting the aggregate bit rate that the terminal device can provide is usually that the core network sends the aggregate maximum bit rate of the terminal device to the base station to limit all non-guaranteed bit rate services of the terminal device.
  • the present application provides a communication method and device, which can provide a current limiting method applicable to 5G scenarios.
  • 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 includes a network slice Configuration information.
  • 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, and n is an integer greater than or equal to 1; then, the first network device can send the message to the second network device Sending a 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.
  • the data rate execution problem of terminal equipment in network slicing is solved in a network environment that supports network slicing.
  • the maximum data rate on the network slice is processed, thereby improving the quality of service of the terminal device.
  • the step of the first network device sending the second message to the second network device may include: the first network device determines to reject m network slices as terminals based on locally available resources and/or local policies The maximum data rate provided by the device sends a second message to the second network device.
  • the first network device can determine whether to accept the maximum data rate provided by the n network slices for the terminal device based on locally available resources and/or local policies.
  • the first network device may accept the maximum data rate provided by n network slices for the terminal device.
  • the first network device may accept part of the maximum data rate provided by one or more network slices for the terminal device, while rejecting the maximum data rate provided for the terminal device by other network slices other than the one or more network slices mentioned above. rate.
  • the first network device may not accept any network slicing requirements, that is, rejecting the maximum data rate provided by n network slices for the terminal device.
  • the method may further include: the first network device sends rejection information to the second network device, which is used to instruct the first network device to reject m network slices because the first network device does not support m network slices.
  • 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 requirement of m network slices, thereby eliminating the cause of the network or the second network device.
  • the second network device knows that the first network device has rejected the m network slices, it does not need to detect its own reasons.
  • the method may further include: the first network device sends suggestion information to the second network device, which is used to indicate that at least one of the m network slices that the first network device can support is a terminal device The maximum data rate provided.
  • the first network device can recommend to the second network device the actual maximum data rate provided by at least one of the m network slices acceptable to the second network device based on available resources and/or local policies.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a non-guaranteed bit rate quality of service of the terminal device Non-GBR QoS flow and/or guaranteed bit rate quality of service GBR-the aggregate bit rate provided by the QoS flow; the second indication information is 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 upstream data flow is the upstream Non-GBR QoS flow and/or the upstream 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, and the downstream The data flow is a downstream Non-GBR QoS flow and/or a downstream GBR QoS flow.
  • first indication information used to indicate that each of the n network slices is a non-guaranteed bit rate quality of service of the terminal device Non-GBR QoS flow and/or guaranteed bit rate quality of service
  • 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.
  • 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.
  • this application can be applied to handover scenarios, UE context setting scenarios, UE context modification scenarios, bearer context setting scenarios, bearer context modification scenarios, secondary node addition scenarios, and secondary Node modification scenario, PDU session resource setting scenario, and/or initial context setting scenario, etc.
  • embodiments of the present application provide a communication method, which can be applied to a second network device, and the method may include: the second network device sends a first message to the first network device, and the first message includes the network Slice configuration information.
  • 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; then, the second network device can receive data from the first The second message of the 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 for the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n.
  • the second message is sent by the first network device to the second network device after determining to reject the maximum data rate provided by the terminal device for m network slices based on locally available resources and/or local policies.
  • the method further includes: the second network device receives rejection information sent by the first network device, where the rejection information is used to indicate that the first network device rejects the m network slices because the first network device The maximum data rate provided by m network slices for the terminal device is not supported.
  • the method further includes: the second network device receives suggestion information sent by the first network device, where the suggestion information is used to indicate at least one network among the m network slices that the first network device can support The slice is the maximum data rate provided by the terminal device.
  • the method further includes: based on the suggestion information, modifying the maximum data rate provided by the at least one network slice for the terminal device, and indicating to the first network device that the modified at least one network slice is provided by the terminal device Maximum data rate.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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 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, the downlink data flow is the downlink Non-GBR QoS flow and/ Or downstream GBR QoS flow.
  • 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.
  • 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.
  • an embodiment of the present application provides a communication method, which can be applied to a first network device, and includes: the first network device receives a first message from a second network device, the first message includes network slice configuration information , Where the network slice configuration information is used to indicate the maximum data rate provided by each network slice of the n network slices to the terminal device, and n is an integer greater than or equal to 1; then, the first network device may be based on the network slice configuration information , Perform resource scheduling and/or admission control on n network slices.
  • resource scheduling and/or admission control on n network slices based on network slice configuration information includes: determining to support m network slices as terminal devices based on locally available resources and/or local policies The maximum data rate provided, where m is an integer greater than or equal to 0 and less than or equal to n; corresponding resources are allocated to m resources based on the network slice configuration information.
  • the first message is a UE context acquisition response message.
  • the method may further include: sending a UE context acquisition request message to the second network device.
  • the first message is a downlink NAS transmission message.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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, and the uplink data flow is an uplink Non-GBR QoS flow And/or 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, and the downlink data flow is the downlink Non-GBR QoS flow and / Or downstream GBR QoS flow.
  • first indication information used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow
  • the second indication information is used to indicate the aggregate bit rate provided by each of the n network
  • an embodiment of the present application provides a communication method.
  • the method includes: after a first network device receives a first message sent by a second network device, sending a second message to a third network device, where the second message includes Network slice configuration information, where 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, and n is an integer greater than or equal to 1; the first network device receives the third A third message sent by a network device, where 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 greater than or equal to 0 and less than or An integer equal to n; the first network device sends a fourth message to the second network device, where 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.
  • 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 m The maximum data rate provided by each network slice for the terminal device.
  • the third message, or the third message and the fourth message include suggestion information, which is used to indicate that at least one of the m network slices supported by the third network device is provided for the terminal device The maximum data rate.
  • the first message is a handover request message
  • the second message is a handover request message
  • an embodiment of the present application provides a communication device applied to a first network device.
  • 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, Make the apparatus perform the following steps: receive 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 provided by each network slice of the n network slices for the terminal device Rate, n is an integer greater than or equal to 1; a second message is sent 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 greater than Or an integer equal to 0 and less than or equal to n.
  • the device executes the following steps: based on locally available resources and/or local policies, it is determined to reject the maximum data rate provided by m network slices for the terminal device, then The second network device sends a second message.
  • the device executes the following steps: sending rejection information to the second network device, which is used to instruct the first network device to reject m network slices because the reason is the first network
  • the device does not support the maximum data rate provided by m network slices for the terminal device.
  • the device executes the following steps: sending suggestion information to the second network device for indicating at least one of the m network slices that the first network device can support The maximum data rate provided by the network slice for the terminal device.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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 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, the downlink data flow is the downlink Non-GBR QoS flow and/ Or downstream GBR QoS flow.
  • 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.
  • 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.
  • an embodiment of the present application provides a communication device applied to a second network device.
  • 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 apparatus is caused to perform the following steps: send 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 for the terminal device by each of the n network slices , 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 for the terminal device, where, m is an integer greater than or equal to 0 and less than or equal to n.
  • the second message is sent by the first network device to the second network device after determining to reject the maximum data rate provided by the terminal device for m network slices based on locally available resources and/or local policies.
  • the device executes the following steps: receiving rejection information sent by the first network device, where the rejection information is used to instruct the first network device to reject m network slices The reason is that the first network device does not support the maximum data rate provided by the m network slices for the terminal device.
  • the device executes the following steps: receiving suggestion information sent by the first network device, where the suggestion information is used to indicate the m number of suggestions that the first network device can support At least one network slice in the network slice provides the maximum data rate for the terminal device.
  • the device executes the following steps: based on the suggestion information, modify the maximum data rate provided by at least one network slice for the terminal device, and instruct the first network device after the modification At least one of the network slices provides the maximum data rate for the terminal device.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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 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, the downlink data flow is the downlink Non-GBR QoS flow and/ Or downstream GBR QoS flow.
  • 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.
  • 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.
  • 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 Perform 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 the maximum data provided by each network slice of the n network slices to the terminal device Rate, n is an integer greater than or equal to 1; based on network slice configuration information, resource scheduling and/or admission control are performed on n network slices.
  • the device executes the following steps: based on locally available resources and/or local policies, determine the maximum data rate provided by the terminal device for supporting m network slices, where: m is an integer greater than or equal to 0 and less than or equal to n; corresponding resources are allocated to m resources based on the network slice configuration information.
  • the first message is a UE context acquisition response message.
  • the method may further include: sending a UE context acquisition request message to the second network device.
  • the first message is a downlink NAS transmission message.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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, and the uplink data flow is an uplink Non-GBR QoS flow And/or 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.
  • the downlink data flow is the downlink Non-GBR QoS flow and / Or downstream GBR QoS flow.
  • 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 Perform the following steps: After receiving the first message sent by the second network device, send a second message to the third network device.
  • the second message includes network slice configuration information, where the network slice configuration information is used to indicate the number of network slices Each network slice of is the maximum data rate provided by the terminal device, n is an integer greater than or equal to 1; a third message sent by a third network device is received, where the third message is used to instruct the third network device to reject m network slices are the configuration requirements for the maximum data rate provided by the terminal device, where m is an integer greater than or equal to 0 and less than or equal to n; a fourth message is sent to the second network device, where the fourth message is 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.
  • 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 m The maximum data rate provided by each network slice for the terminal device.
  • the third message, or the third message and the fourth message include suggestion information, which is used to indicate that at least one of the m network slices supported by the third network device is provided for the terminal device The maximum data rate.
  • the first message is a handover request message
  • the second message is a handover request message
  • an embodiment of the present application provides a communication device, which is applied to a first network device, and the device includes:
  • the receiving module is configured to receive 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 to the terminal device , N is an integer greater than or equal to 1;
  • the sending module is used to send a second message to the second 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 for the terminal device, where m is greater than or equal to 0 And an integer less than or equal to n.
  • the sending module is configured to: based on locally 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 the second message to the second network device.
  • the sending module is further configured to: send rejection information to the second network device, which is used to instruct the first network device to reject m network slices because the first network device does not support m network slices.
  • the maximum data rate provided by the terminal device is further configured to: send rejection information to the second network device, which is used to instruct the first network device to reject m network slices because the first network device does not support m network slices. The maximum data rate provided by the terminal device.
  • the sending module is further used for: sending suggestion information to the second network device, which is used to indicate that at least one of the m network slices that the first network device can support provides the maximum value for the terminal device. Data rate.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a non-guaranteed bit rate quality of service of the terminal device Non-GBR QoS flow and/or guaranteed bit rate quality of service GBR-the aggregate bit rate provided by the QoS flow; the second indication information is 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 upstream data flow is the upstream Non-GBR QoS flow and/or the upstream 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, and the downstream The data flow is a downstream Non-GBR QoS flow and/or a downstream GBR QoS flow.
  • first indication information used to indicate that each of the n network slices is a non-guaranteed bit rate quality of service of the terminal device Non-GBR QoS flow and/or guaranteed bit rate quality of service
  • 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.
  • 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.
  • an embodiment of the present application provides a communication device, which is applied to a second network device, and the device includes:
  • the sending module is configured to send a first message to the first network device, where 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, n is an integer greater than or equal to 1;
  • the receiving module is configured to receive 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 for the terminal device, where m is greater than or equal to An integer of 0 and less than or equal to n.
  • the second message is sent by the first network device to the second network device after determining to reject the maximum data rate provided by the terminal device for m network slices based on locally available resources and/or local policies.
  • the receiving module is further configured to: receive rejection information sent by the first network device, where the rejection information is used to indicate that the first network device rejects the m network slices because the first network device does not support it.
  • the maximum data rate provided by m network slices for the terminal device is further configured to: receive rejection information sent by the first network device, where the rejection information is used to indicate that the first network device rejects the m network slices because the first network device does not support it. The maximum data rate provided by m network slices for the terminal device.
  • the receiving module is further configured to: receive suggestion information sent by the first network device, where the suggestion information is used to indicate that at least one of the m network slices that the first network device can support is The maximum data rate provided by the terminal device.
  • the apparatus further includes: a modification module, configured to modify the maximum data rate provided by the at least one network slice for the terminal device based on the suggestion information, and indicate the modified at least one network slice to the first network device The maximum data rate provided for the terminal device.
  • a modification module configured to modify the maximum data rate provided by the at least one network slice for the terminal device based on the suggestion information, and indicate the modified at least one network slice to the first network device The maximum data rate provided for the terminal device.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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 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, the downlink data flow is the downlink Non-GBR QoS flow and/ Or downstream GBR QoS flow.
  • 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.
  • 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.
  • an embodiment of the present application provides a communication device, which is applied to a first network device, and the device includes:
  • the receiving module is configured to 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 the maximum value provided by each network slice of the n network slices for the terminal device Data rate, n is an integer greater than or equal to 1;
  • the processing module is used to perform resource scheduling and/or admission control on n network slices based on network slice configuration information.
  • the processing module is used to determine the maximum data rate provided by the terminal device for supporting m network slices based on locally available resources and/or local policies, where m is greater than or equal to 0 and less than or An integer equal to n; based on the network slice configuration information, corresponding resources are allocated to m resources.
  • the first message is a UE context acquisition response message.
  • the method may further include: sending a UE context acquisition request message to the second network device.
  • the first message is a downlink NAS transmission message.
  • the network slice configuration information includes at least one of the following: first indication information, used to indicate that each of the n network slices is a Non-GBR QoS flow and/or GBR of the terminal device The aggregate bit rate provided by the QoS flow; the second indication information is 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, and the uplink data flow is an uplink Non-GBR QoS flow And/or 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.
  • the downlink data flow is the downlink Non-GBR QoS flow and / Or downstream GBR QoS flow.
  • an embodiment of the present application provides a communication device, which is applied to a first network device, and the device includes:
  • a receiving module configured to receive the first message sent by the second network device
  • the sending module is configured to send a second message to the third network device after the receiving module receives the first message.
  • the second message includes network slice configuration information, where the network slice configuration information is used to indicate each of the n network slices
  • the network slice is the maximum data rate provided by the terminal device, and n is an integer greater than or equal to 1;
  • the receiving module is further configured to receive a third message sent by a third network device, where 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;
  • the sending module is further configured to send a fourth message to the second network device after the receiving module receives the third message, where the fourth message is used to instruct the third network device to reject the maximum value provided by the m network slices for the terminal device.
  • Data rate configuration requirements where m is an integer greater than or equal to 0 and less than or equal to n.
  • 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 m The maximum data rate provided by each network slice for the terminal device.
  • the third message, or the third message and the fourth message include suggestion information, which is used to indicate that at least one of the m network slices supported by the third network device is provided for the terminal device The maximum data rate.
  • the first message is a handover request message
  • the second message is a handover request message
  • an embodiment of the present application provides a computer-readable medium for storing a computer program, the computer program including instructions for executing the first aspect or any possible implementation of the first aspect.
  • the embodiments of the present application provide a computer-readable medium for storing a computer program, and the computer program includes instructions for executing the second aspect or any possible implementation of the second aspect.
  • the embodiments of the present application provide a computer-readable medium for storing a computer program, and the computer program includes instructions for executing the third aspect or any possible implementation of the third aspect.
  • the embodiments of the present application provide a computer-readable medium for storing a computer program, and the computer program includes instructions for executing the fourth aspect or any possible implementation of the fourth aspect.
  • an embodiment of the present application provides a computer program, the computer program including instructions for executing the first aspect or any possible implementation of the first aspect.
  • embodiments of the present application provide a computer program, which includes instructions for executing the second aspect or any possible implementation of the second aspect.
  • embodiments of the present application provide a computer program, the computer program including instructions for executing the third aspect or any possible implementation of the third aspect.
  • an embodiment of the present application provides a computer program, the computer program including instructions for executing the fourth aspect or any possible implementation of the fourth aspect.
  • an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processor executes the method in the first aspect or any one of the possible implementations of the first aspect to control the receiving pin to receive the signal, and Control the sending pin to send signals.
  • an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processor executes the method in the second aspect or any one of the possible implementations of the second aspect to control the receiving pin to receive signals, and Control the sending pin to send signals.
  • an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processor executes the method in the third aspect or any one of the possible implementations of the third aspect to control the receiving pin to receive the signal, and Control the sending pin to send signals.
  • an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processor executes the method in the fourth aspect or any one of the possible implementation manners of the fourth aspect to control the receiving pin to receive the signal, and Control the sending pin to send signals.
  • 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 first, second, third, and fourth aspects described above.
  • FIG. 1A is a schematic diagram of a possible communication system architecture provided by an embodiment of the present application.
  • FIG. 1B is a schematic diagram of the architecture of a base station with CU-DU separation provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of the structure of a base station provided by an embodiment of the present application.
  • FIG. 3 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • Fig. 4 is one of the schematic flowcharts of an exemplary communication method
  • FIG. 5 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • Fig. 6 is one of the schematic flowcharts of an exemplary communication method
  • FIG. 7 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • FIG. 8 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • FIG. 9 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • FIG. 10 is one of the schematic flowcharts of an exemplary communication method
  • FIG. 11 is one of the schematic flowcharts of a communication method provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a first network device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a second network device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a first network device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a first network device provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • first and second in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of objects.
  • first target object and the second target object are used to distinguish different target objects, rather than to describe the specific order of the target objects.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.
  • Terminal equipment It can be a user equipment (UE).
  • the UE is connected to the network side through a base station.
  • a base station For example, it can be a handheld terminal device, a notebook computer, a subscriber unit, a cellular phone, Smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer (laptop computer), cordless phone (cordless phone) or wireless local loop (WLL) station, machine type communication (MTC) terminal or other devices that can access the network.
  • PDA personal digital assistant
  • modem handheld device
  • handheld handheld device
  • laptop computer laptop computer
  • cordless phone cordless phone
  • WLL wireless local loop
  • MTC machine type communication
  • Base station Mainly responsible for radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the core network equipment may be an access and mobility management function (AMF), which is mainly responsible for functions such as access control, mobility management (MM), attachment and detachment, and gateway selection.
  • AMF access and mobility management function
  • MM mobility management
  • attachment and detachment and gateway selection.
  • gateway selection The core network equipment involved in the embodiments of the present application is not limited to AMF.
  • the 5th Generation (5G) communication system introduces the concept of network slicing.
  • the network slicing technology can divide a physical network into multiple virtual networks.
  • a virtual network is treated as a "network slice", and each network slice is independent of each other.
  • Different protocol data unit (PDU) sessions in a terminal device may require network slices corresponding to each PDU session to provide services.
  • PDU protocol data unit
  • Network slice is a logical network that provides specific network capabilities and network characteristics (Network Slice: A logical network that provides specific network capabilities and network characteristics). It can be a logical network with different network capabilities and network characteristics customized according to different service requirements or tenants based on physical or virtual network infrastructure.
  • a network slice is composed of a set of network functions and the required resources (for example, computing resources, storage resources, and network resources).
  • the network slices supported by each cell are configured by the operation, administration and maintenance (OAM) system.
  • OAM operation, administration and maintenance
  • a single network slice selection assistance information (S-NSSAI) identifies a network slice.
  • the S-NSSAI includes at least one of the following: slice type and service type (slice/service type, SST) information.
  • the S-NSSAI may also include slice differentiator (SD).
  • SST information is used to indicate the behavior of network slicing, such as the characteristics of network slicing and service type.
  • SD information is supplementary information of SST. For example, if SST points to multiple network slices, SD can assist in corresponding to only one network slice. .
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency communications
  • MMTC massive machine type communications
  • the UE includes 3 PDU sessions, and each PDU session can correspond to a network slice.
  • multiple PDU sessions can correspond to the same network slice.
  • the network slicing can provide network resources for at least one PDU session of the terminal device.
  • FIG. 1A is a schematic diagram of a communication system provided by an embodiment of this application.
  • the communication system includes core network equipment 101, base stations (including base station 102 and base station 103), and terminal equipment (including terminal equipment 104, terminal equipment 105, and terminal equipment 106).
  • base stations including base station 102 and base station 103
  • terminal equipment including terminal equipment 104, terminal equipment 105, and terminal equipment 106.
  • the number of base stations and terminal devices can be one or more.
  • the number of base stations and terminal devices in the communication system shown in FIG. 1A is only an example of adaptability, and this application does not limit it. .
  • a terminal device can access at least one base station.
  • the terminal device 104 is connected to the base station 102
  • the terminal device 106 is connected to the base station 103
  • the terminal device 105 is connected to the base station 102 and the base station 103.
  • the scene is called dual connection).
  • the base station may be connected to at least one core network device, for example, the base station 102 and the base station 103 are connected to the core network device 101 respectively.
  • the core network device 101 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 respectively.
  • the communication interface is called N2 interface or NG interface in this application.
  • the two can communicate directly.
  • the direct communication means that the two base stations may not need to communicate through core network equipment or other equipment.
  • the communication interface between the base station 102 and the base station 103 may be called an Xn interface.
  • the two base stations without a communication interface can communicate through core network equipment.
  • 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.
  • 4G fourth generation
  • 5G fifth generation
  • ) Access technology such as new radio (NR) access technology
  • the communication system can also be used to support third generation (3G) access technology, such as universal mobile telecommunications system, UMTS) access technology
  • 3G such as universal mobile telecommunications system, UMTS
  • the communication system can also be used to support the second generation (2G) access technology, such as the global system for mobile communications (GSM) access technology
  • the communication system can also be used in a communication system supporting multiple wireless technologies, for example, supporting LTE technology and NR technology.
  • the communication system can also be applied to narrowband-internet of things (NB-IoT), enhanced data rate for GSM evolution (EDGE), and broadband code division multiple access systems (wideband code division multiple access, WCDMA), code division multiple access 2000 system (code division multiple access, CDMA2000), time division synchronization code division multiple access system (time division-synchronization code division multiple access, TD-SCDMA), long-term evolution system (long term evolution, LTE) and future-oriented communication technology.
  • NB-IoT narrowband-internet of things
  • EDGE enhanced data rate for GSM evolution
  • WCDMA wideband code division multiple access
  • CDMA2000 code division multiple access 2000 system
  • time division synchronization code division multiple access system time division-synchronization code division multiple access
  • LTE long term evolution
  • future-oriented communication technology future-oriented communication technology
  • the base stations (such as the first base station, the second base station, the source base station, or the target base station) involved in the embodiments of the present application may be the next generation NodeB (gNB) or the next generation base station (gNB). generation-evolved NodeB, ng-eNB).
  • gNB provides UE with new radio (NR) user plane functions and control plane functions
  • ng-eNB provides UE with evolved universal terrestrial radio access (E-UTRA) user plane Functions and control plane functions.
  • NR new radio
  • E-UTRA evolved universal terrestrial radio access
  • gNB and ng-eNB are only a name used to indicate a base station supporting a 5G network system and do not have a restrictive meaning.
  • the base station involved in each embodiment may also be a base transceiver station (BTS) in a GSM system or a CDMA system, a base station (nodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (evolutional node B, eNB or eNodeB).
  • BTS base transceiver station
  • nodeB, NB base station
  • LTE Long Term Evolution
  • the base station involved in each embodiment may also be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network side device in a network after 5G or a network device in a future evolved PLMN network, and a roadside station unit ( road site unit, RSU), etc.
  • RSU roadside station unit
  • Figure 2 is a schematic diagram of the structure of a base station.
  • Figure 2 is a schematic diagram of the structure of a base station.
  • 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, the memory 202, the transceiver 203 and the network interface 204 are connected, for example, by a bus.
  • the antenna 205 is connected to the transceiver 203.
  • the network interface 204 is used to connect the base station with other communication devices through a communication link. In the embodiment of the present application, the connection may include various interfaces, transmission lines, or buses, etc., which is not limited in this embodiment.
  • the processor in the embodiment of the present application may include at least one of the following types: a general central processing unit (CPU), a digital signal processor (DSP), a microprocessor, Application-specific integrated circuit (application-specific integrated circuit, ASIC), microcontroller (microcontroller unit, MCU), field programmable gate array (field programmable gate array, FPGA), or integrated circuit used to implement logic operations .
  • the processor 201 may be a single-CPU processor or a multi-CPU processor.
  • the at least one processor 201 may be integrated in one chip or located on multiple different chips.
  • the memory in the embodiment of the present application 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 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).
  • ROM read-only memory
  • RAM random access memory Random access memory
  • EEPROM electrically erasable programmable read-only memory
  • the memory can also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.) , A magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • CD-ROM compact disc read-only memory
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • a magnetic disk storage medium or other magnetic storage device or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 202 may exist independently and is connected to the processor 201.
  • the memory 202 may also be integrated with the processor 201, for example, integrated in one chip.
  • the memory 202 can store program codes for executing the technical solutions of the embodiments of the present application, and is controlled by the processor 201 to execute.
  • Various types of computer program codes executed can also be regarded as drivers of the processor 201.
  • the processor 201 is configured to execute computer program codes stored in the memory 202, so as to implement the technical solutions in the embodiments of the present application.
  • the memory 202 may also be outside the chip and connected to the processor 201 through an interface.
  • the transceiver 203 may be used to support the reception or transmission of radio frequency signals between the access network device and the terminal device, and the transceiver 203 may 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, and 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 convert the digital
  • the baseband signal or digital intermediate frequency signal is provided to the processor 201, so that the processor 201 performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver 203 is also used to receive a modulated digital baseband signal or digital intermediate frequency signal from the processor 201, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass it through a Or multiple antennas 205 transmit the radio frequency signal.
  • the receiver Rx can selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of precedence is adjustable.
  • the transmitter Tx can selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal, the up-mixing processing and the digital-to-analog conversion processing
  • the order of precedence is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • the base station is composed of two parts: a centralized unit (CU) and a distributed unit (DU).
  • CU Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • RRC Radio Resource Control
  • RLC Radio link control
  • MAC media access control
  • PHY physical layer
  • the CU has the processing capabilities of RRC, PDCP and SDAP.
  • DU has RLC, MAC, and PHY processing capabilities.
  • the CU includes the processing capabilities of RRC, PDCP, RLC, and SDAP, and the DU has the processing capabilities of MAC and PHY.
  • the CU includes the processing capabilities of RRC, PDCP, RLC, SDAP, and part of the MAC (for example, adding a MAC packet header), and the DU has the processing capability of PHY and part of the MAC (for example, scheduling).
  • the names of CU and DU may change, as long as the access network node that can realize the above functions can be regarded as CU and DU in this application.
  • the CU-CP has the control plane functions of the CU, for example, the processing capabilities of RRC and the control plane processing capabilities in PDCP.
  • CU-UP has the user plane functions of the CU, for example, the processing capabilities of SDAP and the user plane processing capabilities of PDCP.
  • CU and DU can be connected through F1 interface
  • CU-CP and CU-UP can be connected through E1 interface
  • CU-CP and DU can be connected through F1 control plane interface (F1-C)
  • the CU-UP and the DU can be connected through the F1 user plane interface (F1-U), which is not limited in this application.
  • the steps performed by the base station may be performed by the base station, CU, or CU-CP. This application does not limit this.
  • the second network device may send a first message to the first network device, where the first message may include network slice configuration information, and the configuration information is used to indicate each network in the n network slices.
  • the slice is the maximum data rate provided by the user equipment UE, and n is an integer greater than or equal to 1.
  • 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.
  • the first network device sends a second message to the second network device.
  • the second message may 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 greater than or equal to An integer of 0 and less than or equal to n.
  • the first network device and the second network device may be base stations.
  • the first network device may be a target base station, and the second network device may be a source base station.
  • This application can be applied to a scenario where a terminal device switches from a source base station to a target base station.
  • the second network device may be a primary node (master node, MN) in a dual connection scenario, and the first network device may be a secondary node (secondary node, SN).
  • scenario two refer to scenario two.
  • 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.
  • scenario three refer to scenario three.
  • the first network device may be CU-UP, and the second network device may be CU-CP.
  • the second network device may be an AMF
  • the first network device may be a base station.
  • scenario five refer to scenario five.
  • FIG. 3 is a schematic flowchart of a communication method in an embodiment of the application, and in FIG. 3:
  • Step 101 The source base station sends a first message to the target base station, where the first message includes network slice configuration information.
  • the source base station may receive the measurement result of the UE, and based on the measurement result, determines 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 parts related to network slicing current limiting. Others, such as the steps of obtaining measurement results, determining whether to switch, and subsequent switching steps, can be referred to in the prior art. , This application is not limited.
  • the source base station may send a handover request message to the target base station, which is used to indicate that the target base station is ready for the resources required for the UE to handover to the target base station.
  • the handover request message may be the first message in this application.
  • the handover request message may include network slice configuration information, which is used to indicate the maximum data rate provided for the UE by each of the n network slices.
  • the maximum data rate includes at least one of the following:
  • the maximum data rate can be the aggregate maximum bit rate, which is used to limit the network slice to the UE’s non-guaranteed bit rate quality of service Non-GBR QoS flow and/or guaranteed bit rate quality of service (GBR QoS) flow provision The aggregate bit rate.
  • the maximum data rate can be the uplink aggregate maximum bit rate, which is used to limit the aggregate bit rate provided by the network slice for the UE's uplink data flow.
  • the uplink data flow is an uplink Non-GBR QoS flow and/or an uplink GBR QoS flow;
  • the maximum data rate may be the downlink aggregate maximum bit rate, which is used to limit the aggregate bit rate provided by the network slice for the UE's downlink data flow.
  • the downlink data flow is a downlink Non-GBR QoS flow and/or a downlink GBR QoS flow.
  • the sum of the rates of the specified data flow of the UE in the network slice for example: it can be the sum of the data rates of the Non-GBR QoS flow and the GBR QoS flow, and does not exceed the limited maximum data rate (that is, the network slice is the UE The maximum data rate provided).
  • the setting of the maximum data rate may be set by the core network device or the control device, and the specific setting method may refer to the prior art, which will not be repeated in this application.
  • the control device may be an operation administration and maintenance (OAM) system or a network management system.
  • OAM operation administration and maintenance
  • the naming method of the control device is not limited in this application.
  • 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.
  • 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.
  • 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.
  • Step 102 The target base station sends a second message to the source base station.
  • the target base station can determine whether it can support the maximum data rate provided by n network slices for the UE based on locally available resources and/or local policies.
  • the locally available resources may be network resources such as bandwidth currently available to the target base station. This application is not limited.
  • the local policy includes but is not limited to at least one of the following: access and mobility management related policies, operator policies, access network discovery and selection policies (access network discovery&selection policy), UE route selection policy (UE route selection policy), session management related policy (session management related policy), etc.
  • the operator's strategy may be the current speed limit strategy of the target base station.
  • 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.
  • the target base station may determine to accept the maximum data rate provided by the n network slices for the UE based on locally available resources and/or local policies, and prepare the UE with resources required for handover.
  • the target base station may send a second message to the source base station to instruct the target base station to accept the maximum data rate provided by the n network slices for the UE.
  • the second message is a handover request acknowledgement (handover request acknowledge) 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 each of the n network slices to provide the UE with The maximum data rate.
  • handover request acknowledge handover request acknowledge
  • the target base station may determine to reject the maximum data rate provided by m (m greater than 0 and less than n) network slices for the UE based on locally available resources and/or local policies, and the target base station is ready for handover.
  • the target base station may send a second message to the source base station to indicate that the target base station is ready to part of the resources required for handover and instruct the target base station to reject the maximum data rate provided by the m network slices for the UE.
  • the second message is a handover request acknowledgement (handover request acknowledge) message.
  • the second message may further include rejection information, which is used to indicate that each of the m network slices is rejected because the target base station does not support the maximum data rate provided by the m network slices for the UE.
  • the target base station may determine to reject the maximum data rate provided for the UE by n network slices 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 that the handover preparation fails, that is, the target base station rejects the UE to switch to the target base station, and instructs the target base station to reject the maximum data rate provided by the n network slices for the UE.
  • the second message may be a handover preparation failure (handover preparation failure) message.
  • the second message may also include rejection information, which is used to indicate that the target base station refuses the UE to switch to the target base station because the target base station does not support the maximum data rate provided by the n network slices for the UE.
  • the target base station may send advice information to the source base station in the second message, which is used to indicate that at least one network slice that the target base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • the suggestion information can be carried in the second message, or the suggestion information can be carried in a newly defined message. This application is not limited.
  • the target base station can 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 network slice.
  • the maximum data rate provided by the UE can be performed.
  • the "rejection of network slicing", “rejection of the requirement for network slicing” and “rejection of the maximum data rate provided by the network slicing for the UE” in this application have the same meaning, and all refer to network equipment (such as target The base station) rejects the maximum data rate provided by the network slice for at least one PDU session on it. Therefore, in this application, "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.” It may be that the reason for the rejection of the PDU session is that the target base station does not support the network slice for the UE.
  • the maximum data rate provided has the same meaning.
  • the rejection information may also include multiple rejection reasons, which are used to indicate 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 PDU session.
  • each rejected PDU session can correspond to a rejection reason.
  • the source base station sends a handover request message to the target base station.
  • the source base station Take the source base station as the base station 102 in FIG. 1A, the target base station as the base station 103, and the UE as the terminal device 104 as an example. 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 identity of the UE, the identity of the k PDU sessions of the UE, and the corresponding information of the k PDU sessions.
  • the S-NSSAI of each network slice of n network slices, n network slices are the maximum data rate provided by the corresponding PDU session, among which, the maximum data rate provided by the n network slices for the corresponding PDU session can also be understood as PDU
  • the maximum data rate of the session on the corresponding network slice can also be understood as the maximum data rate of the PDU session supported or allowed by the source base station on the corresponding network slice.
  • the UE includes 4 PDU sessions, namely, PDU session 1, PDU session 2, PDU session 3, and PDU session 4.
  • PDU session 1 corresponds to network slice 1
  • PDU session 2 corresponds to network slice 2
  • PDU session 3 corresponds to network slice 3
  • PDU session 4 corresponds to network slice 3. That is, PDU session 3 and PDU session 4 both correspond to network slice 3.
  • a maximum data rate provided by each network slice for the UE is set.
  • the maximum data rate provided by network slice 1 for PDU session 1 of the UE 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 The rate is 10Mbps
  • the maximum data rate provided by network slice 3 for PDU session 4 is 8Mbps.
  • the maximum data rate can be used to limit the aggregate bit rate provided by the network slice for the UE's GBR QoS flow and Non-GBR QoS flow.
  • the PDU session 1 of the UE corresponds to network slice 1.
  • the PDU session 1 includes 3 GBR QoS flows and 3 Non-GBR QoS flows.
  • the maximum data rate provided by the network slice 1 for the UE can be used to limit the maximum data rate of the GBR QoS flow and the Non-GBR QoS flow of the PDU session 1 in the network slice 1.
  • the sum of the data rates of the three GBR QoS flows and the three Non-GBR QoS flows of PDU session 1 cannot exceed the maximum data rate provided by network slice 1.
  • the target base station determines the acceptance of n network slices based on locally available resources.
  • the target base station may determine whether to support the requirement of network slicing one by one based on the size order of the maximum data rate provided by the n network slices for the UE, where the requirement of network slicing refers to the maximum data rate required by the network slicing for the UE.
  • the target base station arranges the requirements of network slicing from large to small, for example: 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, and network slice 3
  • the maximum data rate provided for PDU session 3 is 10 Mbps, and the maximum data rate provided by network slice 3 for PDU session 4 is 8 Mbps.
  • the target base station sequentially detects based on available resources.
  • the target base station determines that it can provide corresponding resources for PDU session 1 based on the available resources. It is also understandable Therefore, the target base station can support the resources required for the maximum data rate provided by the network slice 1 for the PDU session 1, and correspondingly, the remaining available resources are 20 Mbps. Then, based on the available resources (20Mbps), the target base station determines that the corresponding resources (15Mbps) can be provided for the PDU session 2, and the remaining available resources are 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 also cannot support network slice 3.
  • the resource (8 Mbps) required for the maximum data rate provided by the PDU session 4 the target base station rejects the demand of the network slice 3. It can also be understood that the target base station rejects the PDU session 3 and the PDU session 4 corresponding to the network slice 3.
  • the target base station may also rank the requirements of network slicing 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 determines the requirements for n network slices can be set based on actual requirements, which is not limited in this application.
  • the target base station can accept the requirement of n network slices, and enter part 13.
  • the target base station may reject the request for m network slices and enter part 14.
  • m is greater than or equal to 0 and less than n.
  • the target base station may reject the demand for n network slices and enter the 15 part.
  • the target base station determines the acceptance of n network slices based on locally available resources as an example.
  • the target base station determines the acceptance of n network slices based on locally available resources and local policies, and the target base station determines the acceptance of n network slices based on local policies.
  • the process is similar to this embodiment, and will not be repeated here.
  • the target base station sends a handover request confirmation message to the source base station.
  • the target base station 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 handover of the UE and accepts the maximum data rate provided by the n network slices for the UE.
  • the target base station sends a handover request confirmation message to the source base station, and the message includes rejection information.
  • 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 handover of the UE and is also used to indicate the target
  • the base station rejects the maximum data rate provided by m network slices for the UE. That is, in this case, the UE can be handed over to the target base station, but at least one PDU session on the m network slices cannot be handed over to the target base station, and the target base station discards the at least one PDU session.
  • the target base station determines that it can provide corresponding resources for PDU Session 1 and PDU Session 2 based on the available resources (20 Mbps), and the remaining available resources are 5 Mbps. And, 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 maximum data rate required by network slice 3 for PDU session 4 , The target base station rejects the demand of network slice 3, that is, rejects PDU session 3 and PDU session 4 corresponding to network slice 3. In other words, the target base station rejected 1 network slice (that is, network slice 3), but in fact, it rejected two PDU sessions on network slice 3 (PDU session 3 and PDU session 4).
  • the message carries rejection information, which is used to indicate that the target base station rejects the network slice 3 because the target base station does not support the maximum data rate provided by the network slice 3 for the UE.
  • the rejection information includes rejection reason 1 and rejection reason 2.
  • Rejection reason 1 is used to indicate that the target base station rejects network slice 3 (or can be understood as rejecting PDU session 3) because the target base station does not support network slice 3 to provide the UE The maximum data rate.
  • Rejection reason 2 is used to indicate that the target base station rejects network slice 3 (or can be understood as rejecting PDU session 4) because the target base station does not support the maximum data rate provided by network slice 3 for the UE.
  • the handover request confirmation message may also carry the maximum data rate provided for the UE by at least one of the m network slices (that is, the rejected network slices) that the target base station can support.
  • the target base station determines the resources required for the maximum data rate that can be provided for the PDU session on network slice 1 and network slice 2 based on the available resources (40Mbps), and the available resources remain 5Mbps.
  • the target base station determines that it cannot support the resources required for the maximum data rate provided by network slice 3 for its PDU session 3 and PDU session 4, then the target base station rejects the demand for network slice 3, and at the same time Based on the available remaining network resources (5Mbps), the target base station can suggest to the source base station that the target base station can support network slice 3.
  • the maximum data rate provided by the target base station for PDU session 3 and/or PDU session 4 is 5Mbps (or less than 5Mbps, this data is only Illustrative example).
  • the source base station can determine whether to update the maximum data rate provided by the network slice for the UE based on the suggested value.
  • the specific determination method may be based on the local settings of the source base station, or based on the strategy formulated by the AMF, 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 sends the updated maximum data rate provided by the network slice for the UE to the target base station, and the target base station then according to the updated maximum data rate, It is determined that the maximum data rate provided by the network slice for the UE is acceptable, and the PDU session corresponding to the network slice is accepted.
  • the target base station sends a handover preparation failure message to the source base station.
  • the target base station determines to reject the maximum data rate provided by the n network slices for the UE, that is, determines not to accept the handover request of the UE.
  • the target base station sends a handover preparation failure message to the source base station, which is used to indicate the UE handover failure, that is, the target base station has not prepared resources for the UE handover.
  • the handover preparation failure message may carry rejection information, which is used to indicate that the target base station rejects the n network slices because the target base station does not support the maximum data rate provided by the n network slices for the UE.
  • rejection information is used to indicate that the target base station rejects the n network slices because the target base station does not support the maximum data rate provided by the n network slices for the UE.
  • the reason for the handover failure is that the target base station rejects the demand for n network slices, that is, it cannot provide corresponding resources for k PDU sessions.
  • the handover preparation failure message may carry suggestion information, which is used to indicate that the target base station can support the maximum data rate provided for the UE by at least one of the n network slices.
  • suggestion information is used to indicate that the target base station can support the maximum data rate provided for the UE by at least one of the n network slices.
  • FIG. 5 is a schematic flowchart of a communication method in an embodiment of the application.
  • FIG. 5 :
  • Step 201 The primary node sends a first message to the secondary node, where the first message includes network slice configuration information.
  • the primary node may provide a control plane connection to the core network for the UE
  • the secondary node may provide additional resources for the UE (for example, a user plane connection between the UE and 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.
  • the core network sets the maximum data rate provided by network slice 1 for the UE to 20Mbps, then the main node can set the maximum data rate of the UE on network slice 1 to 15Mbps, and set the maximum data rate of the UE on network slice 1 It is 5Mbps. That is, the sum of the maximum data rate of the network slice of the UE on the primary node and the secondary node is less than or equal to the maximum data rate set by the core network for it.
  • the primary node may increase or modify the maximum data rate of at least one network slice of the UE on the secondary node.
  • 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).
  • the message may include network slice configuration information, which is used to indicate the maximum data rate provided for the UE by each of the n network slices.
  • 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.
  • the primary node instructs the secondary node to perform processing such as admission and scheduling on n network slices based on the network slice configuration information.
  • 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),
  • the message may include network slice configuration information, which is used to indicate the maximum data rate provided for the UE by each of the n network slices.
  • the request can be used to instruct the secondary node to modify the maximum data rate provided by n network slices for the UE based on the network slice configuration information.
  • Step 202 The secondary node sends a second message to the primary node.
  • the secondary node may determine whether it can support 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 determine the maximum data rate provided for the UE by accepting n network slices based on locally available resources and/or local policies.
  • the secondary node may send a second message to the primary node for instructing the secondary node to accept the maximum data rate provided by the n network slices for the UE.
  • 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 original The second message in the embodiment.
  • the second message may be an SN modification request acknowledgement (S-Node modification request acknowledge, or SeNB modification request acknowledgement, or SgNB modification request)
  • S-Node modification request acknowledge or SeNB modification request acknowledgement, or SgNB modification request
  • the acknowledge message (this message is the second message in this embodiment) is used to instruct the secondary node to accept the maximum data rate provided by the n network slices for the UE, and to complete the modification of the resources of the secondary node.
  • the secondary node may determine to reject the maximum data rate provided for the UE by m (m greater than 0 and less than n) network slices based on locally available resources and/or local policies.
  • the secondary node may send a second message to the primary node for instructing the secondary node to reject the maximum data rate provided by the m network slices for the UE.
  • the second message may be an SN addition request confirmation message.
  • the first message is an SN modification request message
  • the second message may be an SN modification request confirmation message.
  • the secondary node may determine to reject the maximum data rate provided by the 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 the n network slices for the UE.
  • the second message may be an SN addition request reject (S-Node addition request reject, or SeNB addition request reject, or SgNB addition request reject) 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 original The second message in the embodiment).
  • S-Node modification request reject or SeNB modification request reject, or SgNB modification request reject
  • the second message may also include rejection information, which is used to indicate the reason for the failure of the secondary node 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 m Or the maximum data rate provided by n network slices for the UE.
  • rejection information is used to indicate the reason for the failure of the secondary node 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 m Or the maximum data rate provided by n network slices for the UE.
  • the second message may also include suggestion information, which is used to indicate that at least one network slice that can be supported by the secondary node is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice. The specific details will be described in the following embodiments.
  • the secondary node can 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 network slice.
  • the maximum data rate provided for the UE can be performed.
  • rejecting the network slice means rejecting the PDU session corresponding to the network slice. Therefore, in this application, "the reason for the rejection of network slicing is that the secondary node does not support the maximum data rate provided by the network slicing for the UE". It may be that the reason for the rejection of the PDU session is that the secondary node does not support network slicing.
  • the maximum data rate provided to the UE has the same meaning.
  • FIG. 6 it exemplarily shows a schematic flowchart of a communication method.
  • FIG. 6 shows a schematic flowchart of a communication method.
  • the primary node sends an SN increase request message to the secondary node.
  • the main node obtains the maximum data rate provided for the UE by each of the N network slices set by the core network.
  • the settings are as follows: network slice 1 provides a maximum data rate of 20 Mbps for UE PDU session 1, network slice 2 provides a maximum data rate of 15 Mbps for PDU session 2, and network slice 3 provides a maximum data rate of 10 Mbps for PDU session 3.
  • the maximum data rate provided by network slice 3 for PDU session 4 is 5 Mbps.
  • the primary node may set the maximum data rate of the UE on the network slice on the primary node and the maximum data rate of the UE on the network slice on the secondary node based on the above configuration.
  • the primary node can set the maximum data rate of network slice 1 of PDU session 1 on the primary node to 10Mbps, and the maximum data rate of network slice 1 of PDU session 1 on the secondary node to 10Mbps;
  • PDU session 2 on the primary node The maximum data rate of network slice 2 on the PDU is 10Mbps, the maximum data rate of network slice 2 on the secondary node of PDU session 2 is 5Mbps;
  • the maximum data rate of network slice 3 on the primary node of PDU session 3 is 10Mbps, PDU The maximum data rate of network slice 3 of session 4 on the secondary node is 5 Mbps.
  • the primary node can send an SN addition request message to the secondary node, which includes but is not limited to at least one of the following: the UE's identity, the identity of the k PDU sessions that need to be added to the secondary node, and the k PDU session correspondence S-NSSAI of n network slices, network slice configuration information, etc.
  • 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 by k PDU sessions.
  • the primary node may instruct the secondary node to increase the required resources for PDU session 1 and PDU session 2.
  • 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, it is expected that the secondary node will increase resources on the secondary node to meet the maximum data rate provided by network slice 1 for PDU session 1. Data rate.
  • the secondary node determines the acceptance of n network slices based on locally available resources.
  • 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 status of n network slices. For specific details, refer to Scenario 1, which will not be repeated here.
  • the secondary node can accept the requirement of n network slices, and enter part 23.
  • the secondary node may reject the demand for m network slices and enter the 24 part.
  • m is greater than or equal to 0 and less than n.
  • the secondary node may reject the demand for n network slices and enter part 25.
  • the secondary node sends an SN increase request confirmation message to the primary node.
  • the secondary node sends an SN increase request confirmation message to the primary node to indicate that the secondary node has prepared resources for the dual link operation of PDU session 1, PDU session 2 and PDU session 4, that is, the secondary node accepts the primary node.
  • the network slice 1 indicated by the node is the maximum data rate provided by the PDU session 1
  • the network slice 2 is the maximum data rate provided by the PDU session 2
  • the network slice 3 is the maximum data rate provided by the PDU session 4.
  • the secondary node sends an SN increase request confirmation message to the primary node, and the message includes rejection information.
  • the secondary node sends an SN increase request confirmation message to the primary node, where the message includes rejection information, which is used to indicate that the secondary node fails to add resources to the PDU session because the secondary node does not support and corresponds to the PDU session.
  • the network slice is the maximum data rate provided by the UE.
  • the rejection information includes multiple rejection reasons, that is, each rejected PDU session corresponds to one rejection reason.
  • the secondary node determines to reject the maximum data rate provided by network slice 2 for PDU session 2, and when it rejects the maximum data rate provided by network slice 3 for PDU session 4, the secondary node sends to the primary node Send an SN increase request confirmation message, 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 resources corresponding to the maximum data rate (5Mbps) required for network slice 2 (ie, network The increase in the maximum data rate provided by slice 2 for PDU session 2 on the secondary node), and the secondary node’s refusal of the resources corresponding to the maximum data rate (5Mbps) required for network slice 3 (ie, network slice 3 on the secondary The maximum data rate provided for PDU session 4 on the node) increases, that is, the secondary node cannot provide the resources required for dual connection operation for PDU session 2 and PDU session 4.
  • the secondary node sends an SN increase request failure message to the primary node.
  • the secondary node sends an SN increase request failure message to the primary node.
  • the message includes rejection information to indicate that the secondary node fails to add resources for k PDU sessions, that is, the secondary node rejects n network slices as k The maximum data rate provided by each PDU.
  • the scenario where the primary node instructs the secondary node to modify the corresponding resource based on the network slice configuration information is similar to the above steps, and will not be repeated in this application.
  • FIG. 7 is a schematic flowchart of a communication method in an embodiment of the application, and in FIG. 7:
  • Step 301 The CU sends a first message to the DU, where the first message includes network slice configuration information.
  • the first message may be a UE context setup request (UE context setup request) message, which is used to request the DU to set the context of the UE.
  • UE context setup request UE context setup request
  • the first message may be a UE context modification request (UE context modification request) message, which is used to provide the DU with a change in UE context information.
  • UE context modification request UE context modification request
  • the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices for the UE.
  • the network slice configuration information may include the maximum data rate provided for the UE by each of the n network slices corresponding to k data resource bearers (DRB).
  • DRB data resource bearers
  • Step 302 The DU sends a second message to the CU.
  • the DU may determine whether it can support the maximum data rate provided by the n network slices for the UE based on locally available resources and/or local policies.
  • the DU may determine the maximum data rate provided for the UE by accepting n network slices based on locally available resources and/or local policies.
  • the DU may send a second message to the CU to instruct the DU to accept the maximum data rate provided by the n network slices for the UE.
  • the second message may be a UE context setup response (UE context setup response) message.
  • the first message is a UE context modification request message
  • the second message may be a UE context modification response (UE context modification response) message.
  • the DU may determine to reject the maximum data rate provided for the UE by m (m greater than 0 and less than n) network slices 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 the m network slices for the UE.
  • the second message may be a UE context setup response (UE context setup response) message.
  • the first message is a UE context modification request message
  • the second message may be a UE context modification response (UE context modification response) message.
  • the DU may determine to reject the maximum data rate provided by the 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 the n network slices for the UE.
  • the second message may be a UE context setup failure (UE context setup failure) message.
  • the first message is a UE context modification request message
  • the second message may be a UE context modification failure (UE context modification failure) message.
  • the second message may also include rejection information to indicate that the DU fails to set or modify the DRB, that is, the reason for rejecting m or n network slices is that the DU does not support m or n network slices for the UE.
  • rejection information to indicate that the DU fails to set or modify the DRB, that is, the reason for rejecting m or n network slices is that the DU does not support m or n network slices for the UE.
  • the maximum data rate is not be included in the UE.
  • rejecting the network slice means rejecting the DRB corresponding to the network slice. Therefore, the reason for the rejection of the network slice in this application is that the DU does not support the maximum data rate provided by the network slice for the UE. It may be that the reason for the rejection of the DRB is that the DU does not support the maximum data rate provided by the network slice for the UE. Data rate, both have the same meaning.
  • the second message may also include suggestion information, which is used to indicate that at least one network slice that the DU can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • FIG. 8 is a schematic flowchart of a communication method in an embodiment of the application, and in FIG. 8:
  • Step 401 The CU-CP sends a first message to the CU-UP, where the first message includes network slice configuration information.
  • the first message may be a bearer context setup request message, which is used to request the CU-UP to set the bearer context.
  • the first message may be a bearer context modification request (bearer context modification request) message, which is used to request the CU-UP to modify the bearer context.
  • bearer context modification request bearer context modification request
  • the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices for the UE.
  • the network slice configuration information may include the maximum data rate provided by each of the n network slices for the corresponding PDU session.
  • scene one, scene two, and scene three please refer to scene one, scene two, and scene three, which will not be repeated here.
  • Step 402 CU-UP sends a second message to CU-CP.
  • the CU-UP may determine whether it can support the maximum data rate provided by the n network slices for the UE based on locally available resources and/or local policies.
  • 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 the n network slices for the UE.
  • the second message may be a bearer context setup response (bearer context setup response) message.
  • the second message may be a bearer context modification response (bearer context modification response) message.
  • the CU-UP may determine to reject the maximum data rate provided by the UE for m (m greater than 0 and less than n) network slices 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 the m network slices for the UE.
  • the second message may be a bearer context setup response (bearer context setup response) message.
  • the second message may be a bearer context modification response (bearer context modification response) message.
  • the CU-UP may determine to reject the maximum data rate provided by the 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 the n network slices for the UE.
  • the second message may be a bearer context setup failure message.
  • the first message is a bearer context modification request message
  • the second message may be a bearer context modification failure message.
  • the second message may also include rejection information, which is used to indicate that the CU-UP fails to set or modify the bearer context, that is, the reason for rejecting m or n network slices is that CU-UP does not support m or n The maximum data rate provided by each network slice for the UE.
  • rejection information which is used to indicate that the CU-UP fails to set or modify the bearer context, that is, the reason for rejecting m or n network slices is that CU-UP does not support m or n The maximum data rate provided by each network slice for the UE.
  • rejecting the network slice means rejecting the PDU session corresponding to the network slice. Therefore, in this application, "the reason for the rejection of network slicing is that CU-UP does not support the maximum data rate provided by the network slicing for the UE". It may be that the reason for the rejection of the PDU session is that CU-UP does not support network slicing.
  • the maximum data rate provided to the UE has the same meaning.
  • the second message may also include suggestion information, which is used to indicate that at least one network slice that can be supported by the CU-UP is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • FIG. 9 is a schematic flowchart of a communication method in an embodiment of the application.
  • FIG. 9 :
  • Step 501 The AMF sends a first message to the base station, where the first message includes network slice configuration information.
  • the first message may be a PDU session resource setup request (PDU session resource setup request) message, which is used by the base station to allocate resources for at least one PDU session.
  • PDU session resource setup request PDU session resource setup request
  • the first message may be an initial context setup request (initial context setup request) message, which is used to request to set the context of the UE.
  • initial context setup request initial context setup request
  • the first message may be a UE context modification request (UE context modification request) message, which is used to provide the base station with a change in UE context information.
  • UE context modification request UE context modification request
  • the first message may be a downlink non-access stratum (NAS) transport (downlink NAS transport) message, which is used to carry NAS information on the NG interface, so as to send the NAS information to the UE.
  • NAS downlink non-access stratum
  • the first message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices for the UE.
  • the network slice configuration information may include the maximum data rate provided by each of the n network slices for the corresponding PDU session.
  • scene one, scene two, scene three, and scene four please refer to scene one, scene two, scene three, and scene four, which will not be repeated here.
  • Step 502 The base station sends a second message to the AMF.
  • the base station may determine whether it can support the maximum data rate provided by the n network slices for the UE based on locally available resources and/or local policies.
  • the base station 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 base station may send a second message to the AMF, which is used to instruct the base station to accept the maximum data rate provided by the n network slices for the UE.
  • the second message may be a PDU session resource setup response (PDU session resource setup response) message.
  • 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.
  • the first message is a UE context modification request, refer to Scenario 3, which will not be repeated here.
  • the base station may determine, based on locally available resources and/or local policies, to reject the maximum data rate provided for the UE by m (m greater than 0 and less than n) network slices.
  • the base station may send a second message to the AMF, which is used to instruct the base station to reject the maximum data rate provided by the m network slices for the UE.
  • the first message is a PDU session resource setting request message
  • the second message may be a PDU session resource setting response message.
  • 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.
  • the first message is a UE context modification request, refer to Scenario 3, which will not be repeated here.
  • the base station may determine to reject the maximum data rate provided by the 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, which is used to instruct the base station to reject the maximum data rate provided by the n network slices for the UE.
  • the first message is a PDU session resource setting request message
  • the second message may be a PDU session resource setting response message.
  • the first message is an initial context setup request message
  • the second message may be an initial context setup failure (initial context setup failure) message.
  • the first message is a UE context modification request, refer to Scenario 3, which will not be repeated here.
  • the second message may also include rejection information, which is used to indicate that the base station rejects the m or n network slices because the base station does not support the maximum data rate provided by the m or n network slices for the UE.
  • rejection information is used to indicate that the base station rejects the m or n network slices because the base station does not support the maximum data rate provided by the m or n network slices for the UE.
  • the base station may perform admission control and/or resource scheduling on the network slice based on the acceptance status of n network slices and network slice configuration information, without sending the second message to the AMF .
  • the second message may also include suggestion information, which is used to indicate that at least one network slice that the base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • rejecting the network slice means rejecting the PDU session corresponding to the network slice. Therefore, in this application, "the reason for the rejection of network slicing is that the base station does not support the maximum data rate provided by the network slicing for the UE" may be that the reason for the rejection of the PDU session is that the base station does not support the network slicing provided for the UE. Maximum data rate, both have the same meaning.
  • FIG. 10 On the basis of the embodiments shown in Fig. 9 and Fig. 3, as shown in Fig. 10, it exemplarily shows a schematic flow diagram of a communication method.
  • Fig. 10 In Fig. 10:
  • the source base station sends a handover required (handover required) message to the AMF.
  • the AMF sends a handover request (handover request) message to the target base station, where the message includes network configuration information.
  • the handover request message sent by the AMF to the target base station includes but is not limited to: the identifiers of the k PDU sessions that need to be handed over from the source base station to the target base station, and the n network slices corresponding to the k PDU sessions. S-NSSAI of each network slice, and network slice configuration information.
  • the AMF caches all the configuration of the network slice on the active base station. Therefore, the handover request message sent by the source base station to the AMF may not carry network slice configuration information.
  • the target base station determines the acceptance of n network slices based on locally available resources and/or local policies.
  • the target base station can accept the requirement of n network slices, and enter part 34.
  • the target base station may reject the demand for m network slices and enter the 36 part.
  • m is greater than or equal to 0 and less than n.
  • the target base station may reject the demand for n network slices and enter the 38 section.
  • the target base station sends a handover request acknowledgement (handover request acknowledge) message to the AMF.
  • handover request acknowledge handover request acknowledge
  • the AMF sends a handover command message to the source base station.
  • the AMF after receiving the handover request confirmation message, the AMF sends a handover command message to the source base station.
  • the target base station sends a handover request confirmation message to the AMF.
  • the message includes rejection information, which is used to instruct the target base station to reject the maximum data rate provided by the m network slices for the UE.
  • the message includes suggestion information used to indicate that at least one network slice that the target base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • the AMF sends a handover command message to the source base station.
  • the AMF after receiving the handover request confirmation message, the AMF sends a handover command message to the source base station.
  • the message includes rejection information, which is used to instruct the target base station to reject the maximum data rate provided by the m network slices for the UE.
  • the message includes suggestion information used to indicate that at least one network slice that the target base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • the target base station sends a handover failure message to the AMF.
  • the message includes rejection information, which is used to instruct the target base station to reject the maximum data rate provided by the n network slices for the UE.
  • the message includes suggestion information used to indicate that at least one network slice that the target base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • the AMF sends a handover preparation failure message to the source base station.
  • the AMF after receiving the handover failure message, the AMF sends a handover preparation failure message to the source base station.
  • the message includes rejection information, which is used to instruct the target base station to reject the maximum data rate provided by the n network slices for the UE.
  • the message includes suggestion information used to indicate that at least one network slice that the target base station can support is the maximum data rate that the UE can provide. Among them, at least one network slice belongs to the rejected network slice.
  • rejecting the network slice means rejecting the PDU session corresponding to the network slice. Therefore, in this application, "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.” It may be that the reason for the rejection of the PDU session is that the target base station does not support the network slice for the UE.
  • the maximum data rate provided has the same meaning.
  • the first network device may also be a new base station
  • the second network device may be an old base station, as shown in FIG. 11.
  • the UE moves from the old base station to the new base station when it is in the inactive state, and the UE requests to switch from the inactive state to the active state.
  • the new base station needs to obtain information from the old base station.
  • the context of the UE, and in the process of acquiring the context of the UE, the new base station can obtain the maximum data rate provided by the network slice for the UE from the old base station.
  • the new base station after the new base station receives the RRC resume request message sent by the UE, it can send a retrieve UE context request message to the old base station to request the old base station to change the UE context. Transfer to the new base station.
  • the old base station sends a retrieve UE context response message to the new base station, where the message includes network slice configuration information, which is used to indicate the maximum data rate provided by the n network slices for the UE.
  • the new base station can determine whether to accept the maximum data rate provided by n network slices for the UE based on locally available resources and/or local policies, and perform RRC connection reconfiguration for the UE based on the maximum data rate provided for the UE by the accepted network slices And so on. It should be noted that in this embodiment, the new base station does not need to send the second message to the old base station.
  • the network device includes a hardware structure and/or software module corresponding to each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the network device into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 12 shows a type of the first network device 300 involved in the above-mentioned embodiment.
  • the first network device may include: a receiving module 301 and a sending module 302.
  • the receiving module 301 can be used for the step of "receiving the first message from the second network device".
  • this module can be used for supporting the first network device to perform step 101, step 201, step 301, and step 301 in the above method embodiment.
  • the sending module 302 can be used for the step of "sending the second message to the second network device".
  • this module can be used to support the first network device to perform step 102, step 202, step 302, and step 302 in the above method embodiment.
  • FIG. 13 shows a schematic diagram of a possible structure of the second network device 400 involved in the foregoing embodiment.
  • the second network device may include: a sending module 401 and a receiving module 402.
  • the sending module 401 can be used for the step of "sending the first message to the first network device".
  • this module can be used for supporting the second network device to perform step 101, step 201, step 301, and step in the above method embodiment.
  • Step 501 The receiving module 402 can be used for the step of "receiving the second message from the first network device".
  • this module can be used for supporting the second network device to perform step 102, step 202, and step 302 in the above method embodiment.
  • Step 402 Step 502.
  • FIG. 14 shows a schematic diagram of a possible structure of the first network device 500 involved in the foregoing embodiment.
  • the first network device 500 may include: a receiving module 501 and a processing module. Module 502.
  • the receiving module 501 may be used for the step of "receiving the first message from the second network device".
  • the processing module 502 may be used for the step of "performing resource scheduling and/or admission control on n network slices based on network slice configuration information".
  • the first network device 500 can perform the relevant steps of the embodiment shown in FIG. 11, which will not be repeated here.
  • FIG. 15 shows a schematic diagram of a possible structure of the first network device 600 involved in the foregoing embodiment.
  • 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 the first message sent by the second network device".
  • this module may be used for supporting the first network device to execute part 31 in the foregoing method embodiment.
  • the sending module 602 can be used for the step of "after the receiving module receives the first message, it sends the second message to the third network device".
  • this module can be used to support the first network device to execute part 32 in the above method embodiment. .
  • the receiving module 601 is also used for the step of "receiving the third message sent by the third network device". For example, this module can be used for supporting the first network device to execute part 34, part 36, and part 38 in the foregoing method embodiment.
  • the sending module 602 is also used for the step of "after the receiving module receives the third message, it sends the fourth message to the second network device". For example, this module can be used to support the first network device to execute part 35 in the above method embodiment. , 37 parts, 39 parts. That is, the first network device 600 can perform the relevant steps of the embodiment shown in FIG. 10.
  • the device includes a processing module 701 and a communication module 702.
  • the device further includes a storage module 703.
  • the processing module 701, the communication module 702, and the storage module 703 are connected by a communication bus.
  • the communication module 702 may be a device with a transceiver function, and is used to communicate with other network equipment or a communication network.
  • the storage module 703 may include one or more memories, and the memories may be devices for storing programs or data in one or more devices or circuits.
  • the storage module 703 can exist independently and is connected to the processing module 701 through a communication bus.
  • the storage module may also be integrated with the processing module 701.
  • the apparatus 700 may be used in a network device, a circuit, a hardware component, or a chip.
  • 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 shown in FIG. 2.
  • the communication module 702 of the apparatus 700 may include an antenna and a transceiver of a base station, for example, the antenna 105 and the transceiver 103 in FIG. 2.
  • the communication module 702 may also include a network interface of the base station, such as the network interface 104 in FIG. 2.
  • the apparatus 700 may be a chip in a network device (for example: a source base station, AMF, etc.) in the embodiment of the present application.
  • the communication module 702 may be an input or output interface, pin or circuit, or the like.
  • the storage module may store computer execution 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 foregoing embodiment.
  • the storage module 703 can be a register, a cache or RAM, etc.
  • the storage module 703 can be integrated with the processing module 701; the storage module 703 can be a ROM or other types of static storage devices that can store static information and instructions, and the storage module 703 can be integrated with the processing module 701.
  • the processing module 701 is independent.
  • the transceiver may be integrated on the device 700.
  • the communication module 702 integrates the transceiver 103 and the network interface 104.
  • 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 foregoing embodiment can be implemented.
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the methods described in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or transmitted on a computer-readable medium as one or more instructions or codes.
  • Computer-readable media may include computer storage media and communication media, and may also include any media that can transfer a computer program from one place to another.
  • a storage medium may be any available medium that can be accessed by a computer.
  • 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 for carrying or with instructions or data structures
  • the required program code is stored in the form of and can be accessed by the computer.
  • any connection is properly termed a computer-readable medium.
  • coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave
  • coaxial cable, fiber optic cable , Twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of the medium.
  • Magnetic 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, in which disks usually reproduce data magnetically, while optical disks use lasers to optically reproduce data. Combinations of the above should also be included in the scope of computer-readable media.
  • the embodiment of the present application also provides a computer program product.
  • the methods described in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If it is implemented in software, it can be fully or partially implemented in the form of a computer program product.
  • the 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-mentioned computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供了一种通信方法及装置，涉及通信领域，该方法包括：接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；向第二网络设备发送第二消息，用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。从而有效提升终端设备的服务质量。

Description

通信方法及装置
本申请要求在2019年9月26日提交中国专利局、申请号为201910919493.1、发明名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种通信方法及装置。
背景技术
目前，已有的通信系统中限制为终端设备所能提供的聚合比特速率的方式，通常是由核心网向基站发送终端设备的聚合最大比特速率，以限制为终端设备的所有非保证比特速率服务质量(non-guaranteed bit rate quality of service，Non-GBR QoS)流所能提供的聚合比特速率。
但是，已有技术中的限流方式已不足以满足当前的5G应用场景。
发明内容
本申请提供一种通信方法及装置，能够提供一种可应用于5G场景的限流方式。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请实施例提供一种通信方法，其该方法应用于第一网络设备，所述方法包括：第一网络设备接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；接着，第一网络设备可向第二网络设备发送第二消息，用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
通过上述方式，实现了在支持网络切片的网络环境下，解决终端设备在网络切片中的数据速率执行问题，即，本申请对网络切片的设置是以终端设备为粒度，针对每个终端设备在网络切片上的最大数据速率进行处理，从而提高终端设备的服务质量。
在一种可能的实现方式中，第一网络设备向第二网络设备发送第二消息的步骤，可以包括：第一网络设备基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，则向第二网络设备发送第二消息。
通过上述方式，实现了第一网络设备可基于本地可用资源和/或本地策略，判定是否接受n个网络切片为终端设备提供的最大数据速率。一个示例中，第一网络设备可以接受n个网络切片为终端设备提供的最大数据速率。另一个示例中，第一网络设备可以接受部分，一个或一个以上网络切片为终端设备提供的最大数据速率，而拒绝除上述一个或一个以上网络切片以外的其它网络切片为终端设备提供的最大数据速率。又一个示例 中，第一网络设备可以不接受任何网络切片的需求，即，拒绝n个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，方法还可以包括：第一网络设备向第二网络设备发送拒绝信息，用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
通过上述方式，实现了第一网络设备可告知第二网络设备拒绝m个网络切片的原因是由于第一网络设备不支持m个网络切片的需求，从而排除因网络或第二网络设备的原因，使第二网络设备在获知第一网络设备拒绝了m个网络切片的情况下，不用再对自身的原因进行检测。
在一种可能的实现方式中，方法还可以包括：第一网络设备向第二网络设备发送建议信息，用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
通过上述方式，实现了第一网络设备可基于可用资源和/或本地策略，向第二网络设备建议其可接受的m个网络切片中的至少一个网络切片为终端设备提供的实际最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的非保证比特速率服务质量Non-GBR QoS流和/或保证比特速率服务质量GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
通过上述方式，实现了可对网络切片为终端设备提供的不同数据流进行限流，以对不同应用场景，提供完善的限流方式，进一步提升终端设备的服务质量。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
通过上述方式，可提升应用场景的多样性，即，本申请可应用于切换场景、UE上下文设置场景、UE上下文修改场景、承载上下文设置场景、承载上下文修改场景、次要节点增加场景、次要节点修改场景、PDU会话资源设置场景和/或初始上下文设置场景等。
第二方面，本申请实施例提供了一种通信方法，该方法可应用于第二网络设备，所 述方法可以包括：第二网络设备向第一网络设备发送第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；接着，第二网络设备可接收来自第一网络设备的第二消息，第二消息用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第二消息为第一网络设备基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，向第二网络设备发送的。
在一种可能的实现方式中，方法还包括：第二网络设备接收第一网络设备发送的拒绝信息，其中，拒绝信息用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，方法还包括：第二网络设备接收第一网络设备发送的建议信息，其中，建议信息用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，方法还包括：基于建议信息，修改至少一个网络切片为终端设备提供的最大数据速率，并向第一网络设备指示修改后的至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
第三方面，本申请实施例提供了一种通信方法，该方法可应用于第一网络设备，包括：第一网络设备接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最 大数据速率，n为大于或等于1的整数；接着，第一网络设备可基于网络切片配置信息，对n个网络切片进行资源调度和/或接纳控制。
在一种可能的实现方式中，基于网络切片配置信息，对n个网络切片进行资源调度和/或接纳控制，包括：基于本地可用资源和/或本地策略，确定支持m个网络切片为终端设备提供的最大数据速率，其中，m为大于或等于0且小于或等于n的整数；基于网络切片配置信息，为m个资源分配相应的资源。
在一种可能的实现方式中，第一消息为获取UE上下文响应消息，接收来自第二网络设备的第一消息之前，方法还可以包括：向第二网络设备发送获取UE上下文请求消息。
在一种可能的实现方式中，第一消息为下行NAS传输消息。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备E的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
第四方面，本申请实施例提供了一种通信方法，该方法包括：第一网络设备接收到第二网络设备发送的第一消息后，向第三网络设备发送第二消息，第二消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；第一网络设备接收到第三网络设备发送的第三消息，其中，所述第三消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数；第一网络设备向第二网络设备发送第四消息，其中，所述第四消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括拒绝信息，拒绝信息用于指示第三网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括建议信息，用于指示第三网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的 最大数据速率。
在一种可能的实现方式中，第一消息为切换要求消息，第二消息为切换请求消息。
第五方面，本申请实施例提供了一种通信装置，应用于第一网络设备，装置包括：存储器和处理器，存储器和处理器耦合；存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；向第二网络设备发送第二消息，用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，则向第二网络设备发送第二消息。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：向第二网络设备发送拒绝信息，用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：向第二网络设备发送建议信息，用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
第六方面，本申请实施例提供了一种通信装置，应用于第二网络设备，装置包括：存储器和处理器，存储器和处理器耦合；存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：向第一网络设备发送第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；接收来自第一网络设备的第二消息，第二消息用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第二消息为第一网络设备基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，向第二网络设备发送的。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：接收第一网络设备发送的拒绝信息，其中，拒绝信息用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：接收第一网络设备发送的建议信息，其中，建议信息用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：基于建议信息，修改至少一个网络切片为终端设备提供的最大数据速率，并向第一网络设备指示修改后的至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
第七方面，本申请实施例提供了一种通信装置，应用于第一网络设备，包括存储器 和处理器，存储器和处理器耦合；存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；基于网络切片配置信息，对n个网络切片进行资源调度和/或接纳控制。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：基于本地可用资源和/或本地策略，确定支持m个网络切片为终端设备提供的最大数据速率，其中，m为大于或等于0且小于或等于n的整数；基于网络切片配置信息，为m个资源分配相应的资源。
在一种可能的实现方式中，第一消息为获取UE上下文响应消息，接收来自第二网络设备的第一消息之前，方法还可以包括：向第二网络设备发送获取UE上下文请求消息。
在一种可能的实现方式中，第一消息为下行NAS传输消息。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备E的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
第八方面，本申请实施例提供了一种通信装置，应用于第一网络设备，包括存储器和处理器，存储器和处理器耦合；存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收到第二网络设备发送的第一消息后，向第三网络设备发送第二消息，第二消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；接收到第三网络设备发送的第三消息，其中，所述第三消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数；向第二网络设备发送第四消息，其中，所述第四消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括拒绝信息，拒绝信息用于指示第三网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网 络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括建议信息，用于指示第三网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，第一消息为切换要求消息，第二消息为切换请求消息。
第九方面，本申请实施例提供了一种通信装置，应用于第一网络设备，装置包括：
接收模块，用于接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
发送模块，用于向第二网络设备发送第二消息，第二消息用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，发送模块用于：基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，则向第二网络设备发送第二消息。
在一种可能的实现方式中，发送模块还用于：向第二网络设备发送拒绝信息，用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，发送模块还用于：向第二网络设备发送建议信息，用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的非保证比特速率服务质量Non-GBR QoS流和/或保证比特速率服务质量GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要 节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
第十方面，本申请实施例提供了一种通信装置，应用于第二网络设备，装置包括：
发送模块，用于向第一网络设备发送第一消息，第一消息包括网络切片配置信息，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
接收模块，用于接收来自第一网络设备的第二消息，第二消息用于指示第一网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第二消息为第一网络设备基于本地可用资源和/或本地策略，确定拒绝m个网络切片为终端设备提供的最大数据速率，向第二网络设备发送的。
在一种可能的实现方式中，接收模块还用于：接收第一网络设备发送的拒绝信息，其中，拒绝信息用于指示第一网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，接收模块还用于：接收第一网络设备发送的建议信息，其中，建议信息用于指示第一网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，装置还包括：修改模块，用于基于建议信息，修改至少一个网络切片为终端设备提供的最大数据速率，并向第一网络设备指示修改后的至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
在一种可能的实现方式中，第一消息为切换请求消息；或者，第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；或者，第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；或者，第一消息为次要节点增加请求消息或者次要节点修改请求消息；或者，第一消息为PDU会话资源设置请求消息，或者初始上下文设 置请求消息。
第十一方面，本申请实施例提供了一种通信装置，应用于第一网络设备，装置包括：
接收模块，用于接收来自第二网络设备的第一消息，第一消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
处理模块，用于基于网络切片配置信息，对n个网络切片进行资源调度和/或接纳控制。
在一种可能的实现方式中，处理模块用于：基于本地可用资源和/或本地策略，确定支持m个网络切片为终端设备提供的最大数据速率，其中，m为大于或等于0且小于或等于n的整数；基于网络切片配置信息，为m个资源分配相应的资源。
在一种可能的实现方式中，第一消息为获取UE上下文响应消息，接收来自第二网络设备的第一消息之前，方法还可以包括：向第二网络设备发送获取UE上下文请求消息。
在一种可能的实现方式中，第一消息为下行NAS传输消息。
在一种可能的实现方式中，网络切片配置信息包括以下至少之一：第一指示信息，用于指示n个网络切片中的每个网络切片为终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；第二指示信息，用于指示n个网络切片中的每个网络切片为终端设备E的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；第三指示信息，用于指示n个网络切片中的每个网络切片为终端设备的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
第十二方面，本申请实施例提供了一种通信装置，应用于第一网络设备，装置包括：
接收模块，用于接收第二网络设备发送的第一消息；
发送模块，用于接收模块接收到第一消息后，向第三网络设备发送第二消息，第二消息包括网络切片配置信息，其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
接收模块，还用于接收第三网络设备发送的第三消息，其中，所述第三消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数；
发送模块，还用于接收模块接收到第三消息后，向第二网络设备发送第四消息，其中，所述第四消息用于指示第三网络设备拒绝m个网络切片为终端设备提供的最大数据 速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括拒绝信息，拒绝信息用于指示第三网络设备拒绝m个网络切片的原因为第一网络设备不支持m个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，第三消息，或者，第三消息和第四消息包括建议信息，用于指示第三网络设备所能支持的m个网络切片中至少一个网络切片为终端设备提供的最大数据速率。
在一种可能的实现方式中，第一消息为切换要求消息，第二消息为切换请求消息。
第十三方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十四方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十五方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。
第十六方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第四方面或第四方面的任意可能的实现方式中的方法的指令。
第十七方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十八方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十九方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。
第二十方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第四方面或第四方面的任意可能的实现方式中的方法的指令。
第二十一方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理器执行第一方面或第一方面的任一种可能的实现方式中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第二十二方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理器执行第二方面或第二方面的任一种可能的实现方式中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第二十三方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理器执行第三方面或第三方面的任一种可能的实现方式中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第二十四方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理器执行第四方面或第四方面的任一种可能的实现方式中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
第二十五方面，本申请实施例提供一种通信系统，该系统包括上述第一方面、第二方面、第三方面和第四方面涉及的第一网络设备、第二网络设备以及终端设备。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1A是本申请实施例提供的一种可能的通信系统架构示意图；
图1B是本申请实施例提供的一种CU-DU分离的基站的架构示意图；
图2是本申请实施例提供的基站结构示意图；
图3是本申请实施例提供的一种通信方法的流程示意图之一；
图4是示例性的一种通信方法的流程示意图之一；
图5是本申请实施例提供的一种通信方法的流程示意图之一；
图6是示例性的一种通信方法的流程示意图之一；
图7是本申请实施例提供的一种通信方法的流程示意图之一；
图8是本申请实施例提供的一种通信方法的流程示意图之一；
图9是本申请实施例提供的一种通信方法的流程示意图之一；
图10是示例性的一种通信方法的流程示意图之一；
图11是本申请实施例提供的一种通信方法的流程示意图之一；
图12是本申请实施例提供的第一网络设备的结构示意图；
图13是本申请实施例提供的第二网络设备的结构示意图；
图14是本申请实施例提供的第一网络设备的结构示意图；
图15是本申请实施例提供的第一网络设备的结构示意图；
图16是本申请实施例提供的一种装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整 地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请实施例的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一目标对象和第二目标对象等是用于区别不同的目标对象，而不是用于描述目标对象的特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。例如，多个处理单元是指两个或两个以上的处理单元；多个系统是指两个或两个以上的系统。
接下来，本申请实施例中可能涉及的各网元、各专业词的描述如下：
终端设备：可以为用户设备(user equipment，UE)，UE是通过基站来实现接入网络侧的，例如可以是手持终端设备、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。
基站：主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。
核心网设备可以是接入和移动性管理功能(access and mobility management function，AMF)，主要负责接入控制、移动性管理(mobility management，MM)、附着与去附着以及网关选择等功能。本申请实施例所涉及的核心网设备不限于AMF。
第五代(5th Generation，5G)通信系统引入了网络切片的概念，网络切片技术能够实现将一个物理网络划分为多个虚拟网络。一个虚拟网络当作一个“网络切片”，每个网络切片之间是相互独立的。一个终端设备中的不同协议数据单元(protocol data unit，PDU)会话可能需要与各个PDU会话相对应的网络切片来提供服务。
为使本领域技术人员更好的理解本申请，下面对本申请涉及到的网络切片的概念进行简单说明：
网络切片作为5G的一项关键技术，在3GPP和其他各种国际标准化组织得到了广泛的重视和研究。其可以满足运营商对于各种工业、垂直市场和各种虚拟运营业务的定制化需求。网络切片是一个提供特定网络能力和网络特征的逻辑网络(Network Slice:A  logical network that provides specific network capabilities and network characteristics)。它可以是在物理或者虚拟的网络基础设施之上，根据不同的服务需求或者租户等定制化的有不同网络能力和网络特性的逻辑网络。网络切片由一组网络功能及其所需的资源(例如，计算资源、存储资源、网络资源)构成。
每个小区所支持的网络切片由操作、管理和维护系统(operation，administration and maintenance，OAM)配置。一个单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)标识一个网络切片。
S-NSSAI包括以下至少之一：切片类型、服务类型(slice/service type，SST)信息，可选地，S-NSSAI还可以包括切片区分信息(slice differentiator，SD)。其中，SST信息用于指示网络切片的行为，例如网络切片的特征以及服务类型，SD信息是SST的补足信息，例如：若SST指向多个网络切片，那么SD可以辅助对应到唯一的一个网络切片。
终端设备中存在多种类型的业务，例如增强的移动宽带业务(enhanced mobile broadband，eMBB)，超可靠低时延通信(ultra-reliable low latency communications，URLLC)，海量机器类通信(massive machine type communication，mMTC)等，而不同类型业务的PDU会话对应的网络切片可能不同。
举例说明：UE包括3个PDU会话，每个PDU会话可对应一个网络切片，其中，多个PDU会话之间可对应相同的网络切片，其中，即使是相同的业务类型，由于提供的运营商或者业务提供商不同，也可能对应不同的网络切片。也就是说，网络切片可以给终端设备的至少一个PDU会话提供网络资源。
在对本申请实施例的技术方案说明之前，首先结合附图对本申请实施例的通信系统进行说明。参见图1A，为本申请实施例提供的一种通信系统示意图。该通信系统中包括核心网设备101、基站(包括基站102和基站103)、终端设备(包括终端设备104、终端设备105和终端设备106)。需要说明的是，在实际应用中，基站与终端设备的数量均可以为一个或多个，图1A所示通信系统的基站与终端设备的数量仅为适应性举例，本申请对此不做限定。
如图1A所示，一个终端设备可以接入至少一个基站，例如，终端设备104与基站102相连接，终端设备106与基站103相连接，终端设备105与基站102和基站103相连接(这种场景称之为双连接)。基站可以与至少一个核心网设备相连接，例如，基站102和基站103分别与核心网设备101相连接。
其中，核心网设备101分别与基站102和基站103之间存在通信接口，这样核心网设备101可以分别与基站102和基站103进行通信。例如该通信接口在本申请中称为N2接口或者NG接口。
若基站102和基站103之间有通信接口，则两者可以直接通信，这里的直接通信是指两个基站可以不需要通过核心网设备或者其他设备进行通信。例如，基站102和基站103之间的通信接口可以称为Xn接口。
若基站102和基站103之间没有通信接口，则两者不可以直接通信，在一种可能的方式中，没有通信接口的两个基站可以通过核心网设备进行通信。
上述通信系统可以用于支持第四代(fourth generation，4G)接入技术，例如长期演 进(long term evolution，LTE)接入技术；或者，该通信系统也可以支持第五代(fifth generation，5G)接入技术，例如新无线(new radio，NR)接入技术；或者，该通信系统也可以用于支持第三代(third generation，3G)接入技术，例如通用移动通信系统(universal mobile telecommunications system，UMTS)接入技术；或者通信系统也可以用于支持第二代(second generation，2G)接入技术，例如全球移动通讯系统(global system for mobile communications，GSM)接入技术；或者，该通信系统还可以用于支持多种无线技术的通信系统，例如支持LTE技术和NR技术。另外，该通信系统也可以适用于窄带物联网系统(narrow band-internet of things，NB-IoT)、增强型数据速率GSM演进系统(enhanced data rate for GSM evolution，EDGE)、宽带码分多址系统(wideband code division multiple access，WCDMA)、码分多址2000系统(code division multiple access，CDMA2000)、时分同步码分多址系统(time division-synchronization code division multiple access，TD-SCDMA)，长期演进系统(long term evolution，LTE)以及面向未来的通信技术。
需要说明的是，本申请各实施例中涉及的基站(例如第一基站、第二基站、源基站或者目标基站)可以是下一代基站(next generation NodeB，gNB)或者下一代演进型基站(next generation-evolved NodeB，ng-eNB)。其中，gNB为UE提供新空口(new radio，NR)的用户面功能和控制面功能，ng-eNB为UE提供演进型通用陆地无线接入(evolved universal terrestrial radio access，E-UTRA)的用户面功能和控制面功能，需要说明的是，gNB和ng-eNB仅是一种名称，用于表示支持5G网络系统的基站，并不具有限制意义。各实施例中涉及的基站还可以为GSM系统或CDMA系统中的基站(base transceiver station，BTS)，也可以是WCDMA系统中的基站(nodeB，NB)，还可以是LTE系统中的演进型基站(evolutional node B，eNB或eNodeB)。或者，各实施例中涉及的基站还可以为中继站、接入点、车载设备、可穿戴设备以及5G之后的网络中的网络侧设备或未来演进的PLMN网络中的网络设备、路边站点单元(road site unit，RSU)等。
图2是一种基站的结构示意图。在图2中：
基站中包括至少一个处理器201、至少一个存储器202、至少一个收发器203、至少一个网络接口204和一个或多个天线205。处理器201、存储器202、收发器203和网络接口204相连，例如通过总线相连。天线205与收发器203相连。网络接口204用于使得基站通过通信链路，与其它通信设备相连。在本申请实施例中，所述连接可包括各类接口、传输线或总线等，本实施例对此不做限定。
本申请实施例中的处理器，例如处理器201，可以包括如下至少一种类型：通用中央处理器(central processing unit，CPU)、数字信号处理器(digital signal processor，DSP)、微处理器、特定应用集成电路专用集成电路(application-specific integrated circuit，ASIC)、微控制器(microcontroller unit，MCU)、现场可编程门阵列(field programmable gate array，FPGA)、或者用于实现逻辑运算的集成电路。例如，处理器201可以是一个单核(single-CPU)处理器或多核(multi-CPU)处理器。至少一个处理器201可以是集成在一个芯片中或位于多个不同的芯片上。
本申请实施例中的存储器，例如存储器202，可以包括如下至少一种类型：只读存储 器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmabler-only memory，EEPROM)。在某些场景下，存储器还可以是只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
存储器202可以是独立存在，与处理器201相连。可选的，存储器202也可以和处理器201集成在一起，例如集成在一个芯片之内。其中，存储器202能够存储执行本申请实施例的技术方案的程序代码，并由处理器201来控制执行，被执行的各类计算机程序代码也可被视为是处理器201的驱动程序。例如，处理器201用于执行存储器202中存储的计算机程序代码，从而实现本申请实施例中的技术方案。可选的，存储器202还可以在芯片之外，通过接口与处理器201相连。
收发器203可以用于支持接入网设备与终端设备之间射频信号的接收或者发送，收发器203可以与天线205相连。收发器203包括发射机Tx和接收机Rx。具体地，一个或多个天线205可以接收射频信号，该收发器203的接收机Rx用于从天线接收所述射频信号，并将射频信号转换为数字基带信号或数字中频信号，并将该数字基带信号或数字中频信号提供给所述处理器201，以便处理器201对该数字基带信号或数字中频信号做进一步的处理，例如解调处理和译码处理。此外，收发器203中的发射机Tx还用于从处理器201接收经过调制的数字基带信号或数字中频信号，并将该经过调制的数字基带信号或数字中频信号转换为射频信号，并通过一个或多个天线205发送所述射频信号。具体地，接收机Rx可以选择性地对射频信号进行一级或多级下混频处理和模数转换处理以得到数字基带信号或数字中频信号，所述下混频处理和模数转换处理的先后顺序是可调整的。发射机Tx可以选择性地对经过调制的数字基带信号或数字中频信号时进行一级或多级上混频处理和数模转换处理以得到射频信号，所述上混频处理和数模转换处理的先后顺序是可调整的。数字基带信号和数字中频信号可以统称为数字信号。
如图1B所示，需要说明的是，在CU-DU分离架构下，基站由集中式单元(central unit，CU)和分布式单元(distributed unit，DU)两部分组成。其中，一种可能的方式是将无线资源控制(radio resource control，RRC)以及分组数据汇聚协议(packet data convergence protocol，PDCP)层和业务数据适应(service data adaptation protocol，SDAP)层部署在CU。无线链路层控制协议(radio link control，RLC)、媒体接入控制(media access control，MAC)、物理层(physical layer，PHY)部署在DU。相应地，CU具有RRC、PDCP和SDAP的处理能力。DU具有RLC、MAC、和PHY的处理能力。值得注意的是，上述功能切分只是一个例子，还有可能有其他切分的方式。例如，CU包括RRC、PDCP、RLC和SDAP的处理能力，DU具有MAC、和PHY的处理能力。又例如CU包括RRC、PDCP、RLC、SDAP和部分MAC(例如加MAC包头)的处理能力，DU具有PHY和部分MAC(例如调度)的处理能力。CU、DU的名字可能会发生变化，只要能实现上述功能的接入网节点都可以看 做是本申请中的CU、DU。CU-CP具有CU的控制面功能，例如，RRC的处理能力，和PDCP中的控制面处理能力。CU-UP具有CU的用户面功能，例如，SDAP的处理能力，和PDCP中的用户面处理能力。CU和DU之间可以通过F1接口进行连接，CU-CP和CU-UP之间可以通过E1接口进行连接，CU-CP和DU之间可以通过F1的控制面接口(F1-C)进行连接，CU-UP和DU之间可以通过F1的用户面接口(F1-U)进行连接，本申请不作限定。
又一需要说明的是，本申请各实施例中涉及的基站(例如第一基站、第二基站、源基站或者目标基站)所执行的步骤，可以是基站、CU、或者CU-CP来执行，本申请对此不做限定。
结合上述如图1A所示的应用场景示意图，下面介绍本申请的具体实施方案：
具体的，在本申请中，第二网络设备可向第一网络设备发送第一消息，其中，第一消息可包括网络切片配置信息，该配置信息用于指示n个网络切片中的每个网络切片为用户设备UE提供的最大数据速率，n为大于或等于1的整数。第一网络设备接收到第一消息后，判定是否接受n个网络切片为终端设备提供的最大数据速率，并将结果返回给第二网络设备。具体的，第一网络设备向第二网络设备发送第二消息，第二消息可用于指示第一网络设备拒绝m个网络切片为UE提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
可选地，第一网络设备与第二网络设备可以为基站。一个示例中，第一网络设备可以为目标基站，第二网络设备可以为源基站，本申请可应用于终端设备从源基站切换到目标基站的场景中，具体实施例可参照场景一。另一个示例中，第二网络设备可以为双连接场景下的主要节点(master node，MN)，第一网络设备可以为次要节点(secondary node，SN)，具体实施例可参照场景二。又一个示例中，第二网络设备可以为基站中的CU，第一网络设备可以为基站中的DU，具体实施例可参照场景三。又一个示例中，第一网络设备可以为CU-UP，第二网络设备可以为CU-CP，具体实施例可参照场景四。又一个实施例中，第二网络设备可以为AMF，第一网络设备可以为基站，具体实施例可参照场景五。
场景一
结合图1A，如图3所示为本申请实施例中的通信方法的流程示意图，在图3中：
步骤101，源基站向目标基站发送第一消息，其中，第一消息包括网络切片配置信息。
具体的，在本申请中，源基站可接收到UE的测量结果，并基于测量结果，确定需要将UE切换到目标基站。需要说明的是，本申请所述的方案仅涉及与网络切片限流相关的部分，其它例如测量结果的获取步骤、判定是否切换的步骤、以及后续的切换步骤等，均可参照已有技术中，本申请不做限定。
具体的，源基站确定需要将UE切换到目标基站后，可向目标基站发送切换请求消息(handover request)，用于指示目标基站准备好UE切换到目标基站所需的资源。其中，切换请求消息可以为本申请中的第一消息。
可选地，切换请求消息中可包括网络切片配置信息，该信息用于指示n个网络切片 中的每个网络切片为UE提供的最大数据速率。
可选地，最大数据速率包括以下至少之一：
最大数据速率可以是聚合最大比特速率，用于限制网络切片为UE的非保证比特速率服务质量Non-GBR QoS流和/或保证比特速率服务质量(guaranteed bit rate quality of service，GBR QoS)流提供的聚合比特速率。
最大数据速率可以是上行聚合最大比特速率，用于限制网络切片为UE的上行数据流提供的聚合比特速率，上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；
最大数据速率可以是下行聚合最大比特速率，用于限制网络切片为UE的下行数据流提供的聚合比特速率，下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
也就是说，UE的指定数据流在网络切片中的速率之和，例如：可以是Non-GBR QoS流和GBR QoS流的数据速率之和，不超过限定的最大数据速率(即网络切片为UE提供的最大数据速率)。
可选地，最大数据速率的设置可以由核心网设备进行设置，也可以由控制设备进行设置，具体设置方式可参照已有技术，本申请不再赘述。这里控制设备可以为操作管理维护(operation administration and maintenance，OAM)系统，或者为网络管理系统，本申请对控制设备的命名方式不做限定。
可选地，切换请求消息中还包括UE的标识信息、UE的k个PDU会话的标识、k个PDU会话对应的n个网络切片的S-NSSAI。需要说明的是，UE包括k个PDU会话，其中，k个PDU会话对应n个网络切片，n个网络切片中的每个网络切片为对应的PDU会话提供最大数据速率。如上文所述，k个PDU会话中的每个PDU会话可对应一个网络切片，多个PDU会话可对应同一个网络切片，其中，k为大于或等于n的整数。
步骤102，目标基站向源基站发送第二消息。
具体的，目标基站接收到切换请求消息后，可基于本地可用资源和/或本地策略，判定是否可支持n个网络切片为UE提供的最大数据速率。
可选地，本地可用资源可以为目标基站当前可用的带宽等网络资源。本申请不做限定。
可选地，本地策略包括但不限于以下至少之一：接入和移动性管理相关策略(access and mobility management related policy)、运营商策略(operator policy)、接入网络发现和选择策略(access network discovery&selection policy)、UE路由选择策略(UE route selection policy)、会话管理相关策略(session management related policy)等。例如，运营商策略可以为当前目标基站的限速策略。
目标基站可基于本地可用资源、或者，基于本地策略，或者基于本地可用资源和本地策略，确定可接受的网络切片的数量。
一个示例中，目标基站可基于本地可用资源和/或本地策略，确定接受n个网络切片为UE提供的最大数据速率，并且为UE准备好切换所需的资源。目标基站可向源基站发送第二消息，用于指示目标基站接受n个网络切片为UE提供的最大数据速率。可选地，第二消息为切换请求确认(handover request acknowledge)消息，用于指示目标基站已经准备好切换所需的资源，即，目标基站接受n个网络切片中的每个网络切片为UE提供 的最大数据速率。
另一个示例中，目标基站可基于本地可用资源和/或本地策略，确定拒绝m(m大于0且小于n)个网络切片为UE提供的最大数据速率，并且，目标基站已经准备好切换所需的资源。目标基站可向源基站发送第二消息，用于指示目标基站已准备好切换所需的部分资源，并指示目标基站拒绝m个网络切片为UE提供的最大数据速率。可选地，第二消息为切换请求确认(handover request acknowledge)消息。可选地，第二消息还可以包括拒绝信息，用于指示m个网络切片中的每个网络切片被拒绝的原因为目标基站不支持m个网络切片为UE提供的最大数据速率。
又一个示例中，目标基站可基于本地可用资源和/或本地策略，确定拒绝n个网络切片为UE提供的最大数据速率。目标基站可向源基站发送第二消息，用于指示切换准备失败，即，目标基站拒绝UE切换到目标基站，并指示目标基站拒绝n个网络切片为UE提供的最大数据速率。可选地，第二消息可以为切换准备失败(handover preparation failure)消息。可选地，第二消息还可以包括拒绝信息，用于指示目标基站拒绝UE切换到目标基站的原因为目标基站不支持n个网络切片为UE提供的最大数据速率。
在一种可能的实现方式中，目标基站可向源基站第二消息发送建议信息，用于指示目标基站可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。可选地，建议信息可承载于第二消息中，或者，建议信息可承载新定义的消息中。本申请不做限定。
在一种可能的实现方式中，目标基站可基于网络配置信息等，对已接受的网络切片进行接纳控制、资源调度等操作，以保证UE在网络切片上的实际数据速率不超过该网络切片为UE提供的最大数据速率。
需要说明的是，在本申请中所涉及的“拒绝网络切片”、“拒绝网络切片的需求”以及“拒绝网络切片为UE提供的最大数据速率”的意思相同，均是指网络设备(例如目标基站)拒绝网络切片为其上的至少一个PDU会话提供的最大数据速率。因此，在本申请中所涉及的“网络切片被拒绝的原因为目标基站不支持网络切片为UE提供的最大数据速率”，可以是，PDU会话被拒绝的原因为目标基站不支持网络切片为UE提供的最大数据速率，二者意思相同。
在一种可能的实现方式中，拒绝信息中还可以包括多个拒绝原因，用于指示PDU会话被拒绝的原因为目标基站不支持网络切片为该PDU会话提供的最大数据速率。其中，每个被拒绝的PDU会话可对应一个拒绝原因。具体细节可参照下面实施例中的说明。
在图3所示实施例的基础上，如图4所示，其示例性示出了一种通信方法的流程示意图，在图4中：
11部分，源基站向目标基站发送切换请求消息。
以源基站为图1A中的基站102、目标基站为基站103、UE为终端设备104为例。具体的，源基站确定需要将UE切换到目标基站，向目标基站发送切换请求消息，切换请求消息中包括但不限于：UE的标识、UE的k个PDU会话的标识、k个PDU会话对应的n个网络切片的每个网络切片的S-NSSAI，n个网络切片为对应的PDU会话提供的 最大数据速率，其中，n个网络切片为对应的PDU会话提供的最大数据速率也可以理解为PDU会话在对应的网络切片上的最大数据速率，还可以理解为，源基站支持或允许PDU会话在对应的网络切片上的最大数据速率。
举例说明，在源基站上，UE包括4个PDU会话，分别为PDU会话1、PDU会话2和PDU会话3、PDU会话4。其中，PDU会话1对应网络切片1、PDU会话2对应网络切片2、PDU会话3对应网络切片3、PDU会话4对应网络切片3，即，PDU会话3和PDU会话4均对应网络切片3。
可选地，在源基站上，设置有每个网络切片为UE提供的最大数据速率。例如：在源基站上，网络切片1为UE的PDU会话1提供的最大数据速率为20Mbps，网络切片2为PDU会话2提供的最大数据速率为15Mbps，网络切片3为PDU会话3提供的最大数据速率为10Mbps，网络切片3为PDU会话4提供的最大数据速率为8Mbps。
可选地，最大数据速率可用于限制网络切片为UE的GBR QoS流和Non-GBR QoS流提供的聚合比特速率。举例说明：UE的PDU会话1对应网络切片1，其中，PDU会话1包括3个GBR QoS流和3个Non-GBR QoS流。其中，网络切片1为UE提供的最大数据速率可以用于限制PDU会话1在网络切片1的GBR QoS流和Non-GBR QoS流的最大数据速率。也就是说，PDU会话1的3个GBR QoS流和3个Non-GBR QoS流的数据速率之和，不能超过网络切片1为其所提供的最大数据速率。
12部分，目标基站基于本地可用资源，确定n个网络切片的接受情况。
可选地，目标基站可基于n个网络切片为UE提供的最大数据速率的大小顺序，逐一判定是否支持网络切片的需求，其中网络切片的需求是指网络切片为UE提供的最大数据速率所需的资源。例如：目标基站将网络切片的需求从大到小排列，例如：网络切片1为PDU会话1提供的最大数据速率为20Mbps、网络切片2为PDU会话2提供的最大数据速率为15Mbps、网络切片3为PDU会话3提供的最大数据速率为10Mbps、网络切片3为PDU会话4提供的最大数据速率为8Mbps。目标基站基于可用资源依次检测，举例说明：若目标基站当前可为网络切片提供的数据速率之和为40Mbps，则，目标基站基于可用资源，确定可为PDU会话1提供相应的资源，也可以理解为，目标基站可支持网络切片1为PDU会话1提供的最大数据速率所需的资源，相应的，可用资源剩余20Mbps。接着，目标基站基于可用资源(20Mbps)，确定可为PDU会话2提供相应的资源(15Mbps)，可用资源剩余5Mbps。以及，目标基站基于剩余网络资源(5Mbps)，确定无法支持网络切片3为PDU会话3提供的最大数据速率所需的资源(10Mbps)，并且，目标基站进一步确定目标基站同样无法支持网络切片3为PDU会话4提供的最大数据速率所需的资源(8Mbps)，则目标基站拒绝网络切片3的需求，也可以理解为，目标基站拒绝网络切片3对应的PDU会话3和PDU会话4。
可选地，目标基站还可以基于UE的PDU会话业务的重要性等因素，将网络切片的需求进行排序，并逐一进行判断。目标基站对n个网络切片的需求的判断顺序可基于实际需求进行设置，本申请不做限定。
一个示例中，目标基站可接受n个网络切片的需求，进入13部分。
另一个示例中，目标基站可拒绝m个网络切片的需求，进入14部分。m大于或等 于0且小于n。
又一个示例中，目标基站可拒绝n个网路切片的需求，进入15部分。
确定是否接受n个网络切片的需求的其它具体细节可参照上述实施例，此处不赘述。
在本实施例中，以目标基站基于本地可用资源，确定n个网络切片的接受情况为例，目标基站基于本地可用资源和本地策略，以及目标基站基于本地策略，确定n个网络切片的接受情况的过程与本实施例类似，不再赘述。
13部分，目标基站向源基站发送切换请求确认消息。
具体的，目标基站向源基站发送切换请求确认消息，用于指示目标基站已为UE的切换做好准备，并接受n个网络切片为UE提供的最大数据速率。
14部分，目标基站向源基站发送切换请求确认消息，该消息包括拒绝信息。
具体的，目标基站确定拒绝m个网络切片为UE提供的最大数据速率的情况下，向源基站发送切换请求确认消息，用于指示目标基站已为UE的切换做好准备，还用于指示目标基站拒绝了m个网络切片为UE提供的最大数据速率。也就是说，在该情况下，UE可切换到目标基站上，但是m个网络切片上的至少一个PDU会话无法切换到目标基站，目标基站丢弃所述至少一个PDU会话。仍以12部分中的数据为例进行说明，目标基站基于可用资源(20Mbps)，确定可为PDU会话1和PDU会话2提供相应的资源，可用资源剩余5Mbps。以及，目标基站基于剩余网络资源(5Mbps)，确定无法支持网络切片3为PDU会话3提供的最大数据速率所需的资源，并确定无法支持网络切片3为PDU会话4提供的最大数据速率所需的资源，则目标基站拒绝网络切片3的需求，即拒绝网络切片3对应的PDU会话3和PDU会话4。也就是说，目标基站拒绝了1个网络切片(即网络切片3)，而实际上，是拒绝了网络切片3上的两个PDU会话(PDU会话3和PDU会话4)
可选地，消息中携带拒绝信息，用于指示目标基站拒绝网络切片3的原因为目标基站不支持网络切片3为UE提供的最大数据速率。示例性的，拒绝信息包括拒绝原因1和拒绝原因2，拒绝原因1用于指示目标基站拒绝网络切片3(或可理解为拒绝PDU会话3)的原因为目标基站不支持网络切片3为UE提供的最大数据速率。拒绝原因2用于指示目标基站拒绝网络切片3(或可理解为拒绝PDU会话4)的原因为目标基站不支持网络切片3为UE提供的最大数据速率。
可选地，切换请求确认消息中还可以携带目标基站可支持的m个网络切片(即被拒绝的网络切片)中的至少一个网络切片为UE提供的最大数据速率。仍以12部分中的数据为例进行说明，目标基站基于可用资源(40Mbps)，确定可为网络切片1和网络切片2为其上的PDU会话提供的最大数据速率所需的资源，可用资源剩余5Mbps。以及，目标基站基于剩余网络资源(5Mbps)，确定无法支持网络切片3为其上的PDU会话3和PDU会话4提供的最大数据速率所需的资源，则目标基站拒绝网络切片3的需求，同时，目标基站可基于可用剩余网络资源(5Mbps)，向源基站建议目标基站可支持网络切片3为PDU会话3和/或PDU会话4提供的最大数据速率为5Mbps(或小于5Mbps，本数据仅为示意性举例)。相应的，源基站可基于该建议值，判定是否更新网络切片为UE提供的最大数据速率。具体判定方式可基于源基站的本地设置，或者基于AMF的制定的策略等， 本申请不做限定。若网络切片为UE提供的最大数据速率可根据建议值进行更新，则源基站将更新后的网络切片为UE提供的最大数据速率发送给目标基站，目标基站再根据该更新后的最大数据速率，确定可接受该网络切片为UE提供的最大数据速率，并接受网络切片对应的PDU会话。
15部分，目标基站向源基站发送切换准备失败消息。
具体的，目标基站确定拒绝n个网络切片为UE提供的最大数据速率，即，确定不接受UE的切换请求。目标基站向源基站发送切换准备失败消息，用于指示UE切换失败，即，目标基站未为UE的切换做好资源准备。
可选地，切换准备失败消息可携带拒绝信息，用于指示目标基站拒绝n个网络切片的原因为目标基站不支持n个网络切片为UE提供的最大数据速率。也就是说，切换失败的原因为目标基站拒绝n个网络切片的需求，即，无法为k个PDU会话提供相应的资源。
可选地，切换准备失败消息可携带建议信息，用于指示目标基站可支持n个网络切片中的至少一个切片为UE提供的最大数据速率。具体细节可参照上文，此处不赘述。
场景二
结合图1A，如图5所示为本申请实施例中的通信方法的流程示意图，在图5中：
步骤201，主要节点向次要节点发送第一消息，其中，第一消息包括网络切片配置信息。
具体的，主要节点可为UE提供到核心网的控制面连接，次要节点可为UE提供额外的资源(例如UE到核心网的用户面连接)，但不提供到核心网的控制面连接。也就是说，主要节点和次要节点对应相同的网络切片，并且，网络切片在主要节点上的资源与网络切片在次要节点上的资源之和等于核心网为该网络切片分配的资源。举例说明：核心网设置网络切片1为UE提供的最大数据速率为20Mbps，则，主要节点可设置UE在网络切片1上的最大数据速率为15Mbps，并设置UE在网络切片1上的最大数据速率为5Mbps。即，UE在主要节点和次要节点上的网络切片的最大数据速率之和，小于或等于核心网为其设置的最大数据速率。
可选地，在本申请中，主要节点可增加或修改UE在次要节点上的至少一个网络切片的最大数据速率。
一个示例中，主要节点可向次要节点发送SN增加请求(S-Node addition request，或SeNB addition request，或SgNB addition request)消息(SN增加请求消息可以为本申请中的第一消息)，该消息中可包括网络切片配置信息，用于指示n个网络切片中的每个网络切片为UE提供的最大数据速率。需要说明的是，该请求可以是在双链接建立的过程中发送的，即，该消息用于指示次要节点为UE的双链接操作准备所需的资源。也就是说，主要节点指示次要节点基于网络切片配置信息，对n个网络切片进行接纳和调度等处理。
另一个示例中，主要节点可向次要节点发送SN修改请求(S-Node modification request，或SeNB modification request，或SgNB modification request)消息(SN修改请求消息可 以为本申请中的第一消息)，该消息中可包括网络切片配置信息，用于指示n个网络切片中的每个网络切片为UE提供的最大数据速率。该请求可用于指示次要节点基于网络切片配置信息，修改n个网络切片为UE提供的最大数据速率。
其它细节可参照场景一，此处不赘述。
步骤202，次要节点向主要节点发送第二消息。
具体的，次要节点接收到第一消息后，可基于本地可用资源和/或本地策略，判定是否可支持n个网络切片为UE提供的最大数据速率。
一个示例中，次要节点可基于本地可用资源和/或本地策略，确定接受n个网络切片为UE提供的最大数据速率。次要节点可向主要节点发送第二消息，用于指示次要节点接受n个网络切片为UE提供的最大数据速率。可选地，若第一消息为SN增加请求消息，则第二消息可以为SN增加请求确认(S-Node addition request acknowledge，或SeNB addition request acknowledge，或SgNB addition request acknowledge)消息(该消息为本实施例中的第二消息。可选地，若第一消息为SN修改请求消息，则第二消息可以为SN修改请求确认(S-Node modification request acknowledge，或SeNB modification request acknowledge，或SgNB modification request acknowledge)消息(该消息为本实施例中的第二消息)，用于指示次要节点接受n个网络切片为UE提供的最大数据速率，并已完成对次要节点的资源的修改。
另一个示例中，次要节点可基于本地可用资源和/或本地策略，确定拒绝m(m大于0且小于n)个网络切片为UE提供的最大数据速率。次要节点可向主要节点发送第二消息，用于指示次要节点拒绝m个网络切片为UE提供的最大数据速率。可选地，若第一消息为SN增加请求消息，则第二消息可以为SN增加请求确认消息。可选地，若第一消息为SN修改请求消息，则第二消息可以为SN修改请求确认消息。
又一个示例中，次要节点可基于本地可用资源和/或本地策略，确定拒绝n个网络切片为UE提供的最大数据速率。次要节点可向主要节点发送第二消息，用于指示次要节点拒绝n个网络切片为UE提供的最大数据速率。可选地，若第一消息为SN增加请求消息，则第二消息可以为SN增加请求拒绝(S-Node addition request reject，或SeNB addition request reject，或SgNB addition request reject)消息。可选地，若第一消息为SN修改请求消息，则第二消息可以为SN修改请求拒绝(S-Node modification request reject，或SeNB modification request reject，或SgNB modification request reject)消息(该消息为本实施例中的第二消息)。
可选地，第二消息中还可以包括拒绝信息，用于指示次要节点为UE增加或修改资源失败的原因，即，拒绝m个或n个网络切片的原因为次要节点不支持m个或n个网络切片为UE提供的最大数据速率。
在一种可能的实现方式中，第二消息中还可以包括建议信息，用于指示次要节点可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。具体细节将在下面的实施例中进行说明。
在一种可能的实现方式中，次要节点可基于网络配置信息等，对已接受的网络切片进行接纳控制、资源调度等操作，以保证UE在网络切片上的实际数据速率不超过该网 络切片为UE提供的最大数据速率。
需要说明的是，拒绝网络切片，也就是拒绝了和该网络切片对应的PDU会话。因此，在本申请中所涉及的“网络切片被拒绝的原因为次要节点不支持网络切片为UE提供的最大数据速率”，可以是，PDU会话被拒绝的原因为次要节点不支持网络切片为UE提供的最大数据速率，二者意思相同。
在图5所示实施例的基础上，如图6所示，其示例性示出了一种通信方法的流程示意图，在图6中：
21部分，主要节点向次要节点发送SN增加请求消息。
具体的，主要节点获取核心网设置的N个网络切片中的每个网络切片为UE提供的最大数据速率。例如设置如下：网络切片1为UE的PDU会话1提供的最大数据速率为20Mbps，网络切片2为PDU会话2提供的最大数据速率为15Mbps，网络切片3为PDU会话3提供的最大数据速率为10Mbps、网络切片3为PDU会话4提供的最大数据速率为5Mbps。主要节点可基于上述配置，设置UE在主要节点上的网络切片上的最大数据速率和UE在次要节点上的网络切片上的最大数据速率。举例说明：主要节点可设置PDU会话1在主要节点上的网络切片1的最大数据速率为10Mbps，PDU会话1在次要节点上的网络切片1的最大数据速率为10Mbps；PDU会话2在主要节点上的网络切片2的最大数据速率为10Mbps，PDU会话2在次要节点上的网络切片2的最大数据速率为5Mbps；PDU会话3在主要节点上的网络切片3的最大数据速率为10Mbps、PDU会话4在次要节点上的网络切片3的最大数据速率为5Mbps。
主要节点可向次要节点发送SN增加请求消息，该消息中包括但不限于一下至少之一：UE的标识、需要在次要节点中增加的k个PDU会话的标识、以及k个PDU会话对应的n个网络切片的S-NSSAI、网络切片配置信息等。其中，网络切片配置信息用于指示n个网络切片中的每个网络切片为对应的PDU会话提供的最大数据速率。该消息可用于指示次要节点增加k个PDU会话所需的双链接资源。在本实施例中，基于上述主要节点的配置，主要节点可指示次要节点为PDU会话1和PDU会话2增加所需资源。例如：网络切片配置信息用于指示网络切片1为PDU会话1提供的最大数据速率为10Mbps，即，期望次要节点在次要节点上增加资源，以满足网络切片1为PDU会话1提供的最大数据速率。
22部分，次要节点基于本地可用资源，确定n个网络切片的接受情况。
可选地，次要节点可基于本地可用资源，确定是否接受PDU会话的双连接请求，即，确定n个网络切片的接受情况，具体细节可参照场景一，此处不赘述。
一个示例中，次要节点可接受n个网络切片的需求，进入23部分。
另一个示例中，次要节点可拒绝m个网络切片的需求，进入24部分。m大于或等于0且小于n。
又一个示例中，次要节点可拒绝n个网路切片的需求，进入25部分。
23部分，次要节点向主要节点发送SN增加请求确认消息。
具体的，次要节点向主要节点发送SN增加请求确认消息，用于指示次要节点已为 PDU会话1、PDU会话2和PDU会话4的双链接操作准备好资源，即，次要节点接受主要节点指示的网络切片1为PDU会话1提供的最大数据速率、网络切片2为PDU会话2提供的最大数据速率、网络切片3为PDU会话4提供的最大数据速率。
24部分，次要节点向主要节点发送SN增加请求确认消息，该消息包括拒绝信息。
具体的，次要节点向主要节点发送SN增加请求确认消息，其中，该消息中包括拒绝信息，用于指示次要节点为PDU会话增加资源失败的原因为次要节点不支持和该PDU会话对应的网络切片为UE提供的最大数据速率。可选地，拒绝信息包括多个拒绝原因，即，每个被拒绝的PDU会话对应一个拒绝原因。举例说明：次要节点基于本地可用资源，确定拒绝网络切片2为PDU会话2提供的最大数据速率，以及拒绝网络切片3为PDU会话4提供的最大数据速率的情况下，次要节点向主要节点发送SN增加请求确认消息，该消息用于指示次要节点为UE的双链接操作准备好资源，并且，次要节点拒绝对网络切片2所需的最大数据速率(5Mbps)对应资源(即，网络切片2在次要节点上为PDU会话2提供的最大数据速率)的增加，以及次要节点拒绝对网络切片3所需的最大数据速率(5Mbps)对应的资源(即，网络切片3在次要节点上为PDU会话4提供的最大数据速率)的增加，也就是说，次要节点无法为PDU会话2和PDU会话4提供双连接操作所需的资源。
25部分，次要节点向主要节点发送SN增加请求失败消息。
具体的，次要节点向主要节点发送SN增加请求失败消息，该消息中包括拒绝信息，用于指示次要节点为k个PDU会话增加资源失败，即，次要节点拒绝n个网络切片为k个PDU提供的最大数据速率。
主要节点指示次要节点基于网络切片配置信息，修改对应的资源的场景与上述步骤类似，本申请不再赘述。
场景三
结合图1B，如图7所示为本申请实施例中的通信方法的流程示意图，在图7中：
步骤301，CU向DU发送第一消息，其中，第一消息包括网络切片配置信息。
一个示例中，第一消息可以为UE上下文设置请求(UE context setup request)消息，用于请求DU设置UE的上下文。
另一个示例中，第一消息可以为UE上下文修改请求(UE context modification request)消息，用于向DU提供UE上下文信息的变化。
可选地，第一消息中包括网络切片配置信息，用于指示n个网络切片为UE提供的最大数据速率。示例性的，在本实施例中，网络切片配置信息可包括k个数据资源承载(data resource bearer，DRB)对应的n个网络切片中的每个网络切片为UE提供的最大数据速率。
其他细节可参照场景一、场景二，此处不赘述。
步骤302，DU向CU发送第二消息。
具体的，DU接收到第一消息后，可基于本地可用资源和/或本地策略，判定是否可支持n个网络切片为UE提供的最大数据速率。
一个示例中，DU可基于本地可用资源和/或本地策略，确定接受n个网络切片为UE提供的最大数据速率。DU可向CU发送第二消息，用于指示DU接受n个网络切片为UE提供的最大数据速率。可选地，若第一消息为UE上下文设置请求消息，则第二消息可以为UE上下文设置响应(UE context setup response)消息。可选地，若第一消息为UE上下文修改请求消息，则第二消息可以为UE上下文修改响应(UE context modification response)消息。
另一个示例中，DU可基于本地可用资源和/或本地策略，确定拒绝m(m大于0且小于n)个网络切片为UE提供的最大数据速率。DU可向CU发送第二消息，用于指示DU拒绝m个网络切片为UE提供的最大数据速率。可选地，若第一消息为UE上下文设置请求消息，则第二消息可以为UE上下文设置响应(UE context setup response)消息。可选地，若第一消息为UE上下文修改请求消息，则第二消息可以为UE上下文修改响应(UE context modification response)消息。
又一个示例中，DU可基于本地可用资源和/或本地策略，确定拒绝n个网络切片为UE提供的最大数据速率。DU可向CU发送第二消息，用于指示DU拒绝n个网络切片为UE提供的最大数据速率。可选地，若第一消息为UE上下文设置请求消息，则第二消息可以为UE上下文设置失败(UE context setup failure)消息。可选地，若第一消息为UE上下文修改请求消息，则第二消息可以为UE上下文修改失败(UE context modification failure)消息。
可选地，第二消息中还可以包括拒绝信息，用于指示DU设置或修改DRB失败，即，拒绝m个或n个网络切片的原因为DU不支持m个或n个网络切片为UE提供的最大数据速率。
需要说明的是，拒绝网络切片，也就是拒绝了和该网络切片对应的DRB。因此，在本申请中所涉及的“网络切片被拒绝的原因为DU不支持网络切片为UE提供的最大数据速率”，可以是，DRB被拒绝的原因为DU不支持网络切片为UE提供的最大数据速率，二者意思相同。
在一种可能的实现方式中，第二消息中还可以包括建议信息，用于指示DU可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
场景四
结合图1B，如图8所示为本申请实施例中的通信方法的流程示意图，在图8中：
步骤401，CU-CP向CU-UP发送第一消息，其中，第一消息包括网络切片配置信息。
一个示例中，第一消息可以为承载上下文设置请求(bearer context setup request)消息，用于请求CU-UP设置承载上下文。
另一个示例中，第一消息可以为承载上下文修改请求(bearer context modification request)消息，用于请求CU-UP修改承载上下文。
可选地，第一消息中包括网络切片配置信息，用于指示n个网络切片为UE提供的最大数据速率。示例性的，在本实施例中，网络切片配置信息可包括n个网络切片中的 每个网络切片为对应的PDU会话提供的最大数据速率。
其他细节可参照场景一、场景二、场景三，此处不赘述。
步骤402，CU-UP向CU-CP发送第二消息。
具体的，CU-UP接收到第一消息后，可基于本地可用资源和/或本地策略，判定是否可支持n个网络切片为UE提供的最大数据速率。
一个示例中，CU-UP可基于本地可用资源和/或本地策略，确定接受n个网络切片为UE提供的最大数据速率。CU-UP可向CU-CP发送第二消息，用于指示CU-UP接受n个网络切片为UE提供的最大数据速率。可选地，若第一消息为承载上下文设置请求消息，则第二消息可以为承载上下文设置响应(bearer context setup response)消息。可选地，若第一消息为承载上下文修改请求消息，则第二消息可以为承载上下文修改响应(bearer context modification response)消息。
另一个示例中，CU-UP可基于本地可用资源和/或本地策略，确定拒绝m(m大于0且小于n)个网络切片为UE提供的最大数据速率。CU-UP可向CU-CP发送第二消息，用于指示CU-UP拒绝m个网络切片为UE提供的最大数据速率。可选地，若第一消息为承载上下文设置请求消息，则第二消息可以为承载上下文设置响应(bearer context setup response)消息。可选地，若第一消息为承载上下文修改请求消息，则第二消息可以为承载上下文修改响应(bearer context modification response)消息。
又一个示例中，CU-UP可基于本地可用资源和/或本地策略，确定拒绝n个网络切片为UE提供的最大数据速率。CU-UP可向CU-CP发送第二消息，用于指示CU-UP拒绝n个网络切片为UE提供的最大数据速率。可选地，若第一消息为承载上下文设置请求消息，则第二消息可以为承载上下文设置失败bearer context setup failure)消息。可选地，若第一消息为承载上下文修改请求消息，则第二消息可以为承载上下文修改失败(bearer context modification failure)消息。
可选地，第二消息中还可以包括拒绝信息，用于指示CU-UP设置或修改承载的上下文失败，即，拒绝m个或n个网络切片的原因为CU-UP不支持m个或n个网络切片为UE提供的最大数据速率。
需要说明的是，拒绝网络切片，也就是拒绝了和该网络切片对应的PDU会话。因此，在本申请中所涉及的“网络切片被拒绝的原因为CU-UP不支持网络切片为UE提供的最大数据速率”，可以是，PDU会话被拒绝的原因为CU-UP不支持网络切片为UE提供的最大数据速率，二者意思相同。
在一种可能的实现方式中，第二消息中还可以包括建议信息，用于指示CU-UP可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
场景五
结合图1A，如图9所示为本申请实施例中的通信方法的流程示意图，在图9中：
步骤501，AMF向基站发送第一消息，其中，第一消息包括网络切片配置信息。
一个示例中，第一消息可以为PDU会话资源设置请求(PDU session resource setup  request)消息，用于基站为至少一个PDU会话分配资源。
另一个示例中，第一消息可以为初始上下文设置请求(initial context setup request)消息，用于请求设置UE的上下文。
又一个示例中，第一消息可以为UE上下文修改请求(UE context modification request)消息，用于向基站提供UE上下文的信息变化。
又一个示例中，第一消息可以为下行非接入层(non-access stratum，NAS)传输(downlink NAS transport)消息，用于在NG接口上承载NAS信息，从而向UE发送NAS信息。
可选地，第一消息中包括网络切片配置信息，用于指示n个网络切片为UE提供的最大数据速率。示例性的，在本实施例中，网络切片配置信息可包括n个网络切片中的每个网络切片为对应的PDU会话提供的最大数据速率。
其他细节可参照场景一、场景二、场景三、场景四，此处不赘述。
步骤502，基站向AMF发送第二消息。
具体的，基站接收到第一消息后，可基于本地可用资源和/或本地策略，判定是否可支持n个网络切片为UE提供的最大数据速率。
一个示例中，基站可基于本地可用资源和/或本地策略，确定接受n个网络切片为UE提供的最大数据速率。基站可向AMF发送第二消息，用于指示基站接受n个网络切片为UE提供的最大数据速率。可选地，若第一消息为PDU会话资源设置请求消息，则第二消息可以为PDU会话资源设置响应(PDU session resource setup response)消息。可选地，若第一消息为初始上下文设置请求消息，则第二消息可以为初始上下文设置响应(initial context setup response)消息。可选地，若第一消息为UE上下文修改请求，可参照场景三，此处不赘述。
另一个示例中，基站可基于本地可用资源和/或本地策略，确定拒绝m(m大于0且小于n)个网络切片为UE提供的最大数据速率。基站可向AMF发送第二消息，用于指示基站拒绝m个网络切片为UE提供的最大数据速率。可选地，若第一消息为PDU会话资源设置请求消息，则第二消息可以为PDU会话资源设置响应消息。可选地，若第一消息为初始上下文设置请求消息，则第二消息可以为初始上下文设置响应(initial context setup response)消息。可选地，若第一消息为UE上下文修改请求，可参照场景三，此处不赘述。
又一个示例中，基站可基于本地可用资源和/或本地策略，确定拒绝n个网络切片为UE提供的最大数据速率。基站可向AMF发送第二消息，用于指示基站拒绝n个网络切片为UE提供的最大数据速率。可选地，若第一消息为PDU会话资源设置请求消息，则第二消息可以为PDU会话资源设置响应消息。可选地，若第一消息为初始上下文设置请求消息，则第二消息可以为初始上下文设置失败(initial context setup failure)消息。可选地，若第一消息为UE上下文修改请求，可参照场景三，此处不赘述。
可选地，第二消息中还可以包括拒绝信息，用于指示基站拒绝m个或n个网络切片的原因为基站不支持m个或n个网络切片为UE提供的最大数据速率。
可选地，若第一消息为下行NAS传输消息，则基站可基于n个网络切片的接受情况 及网络切片配置信息，对网络切片进行接纳控制和/或资源调度，无需向AMF发送第二消息。
在一种可能的实现方式中，第二消息中还可以包括建议信息，用于指示基站可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
需要说明的是，拒绝网络切片，也就是拒绝了和该网络切片对应的PDU会话。因此，在本申请中所涉及的“网络切片被拒绝的原因为基站不支持网络切片为UE提供的最大数据速率”，可以是，PDU会话被拒绝的原因为基站不支持网络切片为UE提供的最大数据速率，二者意思相同。
在图9和图3所示实施例的基础上，如图10所示，其示例性示出了一种通信方法的流程示意图，在图10中：
31部分，源基站向AMF发送切换要求(handover required)消息。
32部分，AMF向目标基站发送切换请求(handover request)消息，其中，该消息中包括网络配置信息。
可选地，AMF向目标基站发送的切换请求消息中包括但不限于：需要从源基站切换到目标基站中的k个PDU会话的标识，以及k个PDU会话所对应的n个网络切片中的每个网络切片的S-NSSAI，以及网络切片配置信息。
需要说明的是，在本实施例中，AMF缓存有源基站上的网络切片的所有配置，因此，源基站向AMF发送的切换要求消息可不携带网络切片配置信息。
33部分，目标基站基于本地可用资源和/或本地策略，确定n个网络切片的接受情况。
一个示例中，目标基站可接受n个网络切片的需求，进入34部分。
另一个示例中，目标基站可拒绝m个网络切片的需求，进入36部分。m大于或等于0且小于n。
又一个示例中，目标基站可拒绝n个网路切片的需求，进入38部分。
34部分，目标基站向AMF发送切换请求确认(handover request acknowledge)消息。
35部分，AMF向源基站发送切换命令(handover command)消息。
具体的，AMF接收到切换请求确认消息后，向源基站发送切换命令消息。
36部分，目标基站向AMF发送切换请求确认消息。
可选的，该消息包括拒绝信息，用于指示目标基站拒绝m个网络切片为UE提供的最大数据速率。
可选的，该消息包括建议信息，用于指示目标基站可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
37部分，AMF向源基站发送切换命令消息。
具体的，AMF接收到切换请求确认消息后，向源基站发送切换命令消息。
可选的，该消息包括拒绝信息，用于指示目标基站拒绝m个网络切片为UE提供的最大数据速率。
可选的，该消息包括建议信息，用于指示目标基站可支持的至少一个网络切片为UE 所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
38部分，目标基站向AMF发送切换失败(handover failure)消息。
可选的，该消息包括拒绝信息，用于指示目标基站拒绝n个网络切片为UE提供的最大数据速率。
可选的，该消息包括建议信息，用于指示目标基站可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
39部分，AMF向源基站发送切换准备失败(handover preparation failure)消息。
具体的，AMF接收到切换失败消息后，向源基站发送切换准备失败消息。
可选的，该消息包括拒绝信息，用于指示目标基站拒绝n个网络切片为UE提供的最大数据速率。
可选的，该消息包括建议信息，用于指示目标基站可支持的至少一个网络切片为UE所能提供的最大数据速率。其中，至少一个网络切片属于被拒绝的网络切片。
需要说明的是，拒绝网络切片，也就是拒绝了和该网络切片对应的PDU会话。因此，在本申请中所涉及的“网络切片被拒绝的原因为目标基站不支持网络切片为UE提供的最大数据速率”，可以是，PDU会话被拒绝的原因为目标基站不支持网络切片为UE提供的最大数据速率，二者意思相同。
可选地，在本申请中，第一网络设备还可以为新基站，第二网络设备可以为旧基站，如图11所示。在该场景中，UE处于处于非激活态(inactive)的情况下，从旧基站移动到新基站，并且，UE请求从非激活态转换为激活态，相应的，新基站需要从旧基站上获取UE的上下文，并且在获取UE的上下文的过程中，新基站可从旧基站端获取到网络切片为UE提供的最大数据速率。具体的，参照图11，新基站接收到UE发送的RRC恢复请求(RRC resume request)消息后，可向旧基站发送获取UE上下文请求(retrieve UE context request)消息，用于请求旧基站把UE上下文转移到新基站。接着，旧基站向新基站发送获取UE上下文响应(retrieve UE context response)消息，其中，该消息中包括网络切片配置信息，用于指示n个网络切片为UE提供的最大数据速率。新基站可基于本地可用资源和/或本地策略，确定是否接受n个网络切片为UE提供的最大数据速率，并基于已接受的网络切片为UE提供的最大数据速率，对UE进行RRC连接重配置等操作。需要说明的是，在本实施例中，新基站无需向旧基站发送第二消息。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，网络设备(包括第一网络设备和第二网络设备)为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，在采用对应各个功能划分各个功能模块的情况下，一个示例中，图12示出了上述实施例中所涉及的第一网络设备300的一种可能的结构示意图，如图12所示，第一网络设备可以包括：接收模块301、发送模块302。其中，接收模块301可用于“接收来自第二网络设备的第一消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的步骤101、步骤201、步骤301、步骤401、步骤501。发送模块302，可用于“向所述第二网络设备发送第二消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的步骤102、步骤202、步骤302、步骤402、步骤502。
一个示例中，图13示出了上述实施例中所涉及的第二网络设备400的一种可能的结构示意图，如图13所示，第二网络设备可以包括：发送模块401、接收模块402。其中，发送模块401可用于“向第一网络设备发送第一消息”的步骤，例如，该模块可以用于支持第二网络设备执行上述方法实施例中的步骤101、步骤201、步骤301、步骤401、步骤501。接收模块402，可用于“接收来自所述第一网络设备的第二消息”的步骤，例如，该模块可以用于支持第二网络设备执行上述方法实施例中的步骤102、步骤202、步骤302、步骤402、步骤502。
另一个实施例中，图14示出了上述实施例中所涉及的第一网络设备500的一种可能的结构示意图，如图14所示，第一网络设备500可以包括：接收模块501和处理模块502。其中，接收模块501可以用于“接收来自第二网络设备的第一消息”的步骤。处理模块502可以用于“基于网络切片配置信息，对n个网络切片进行资源调度和/或接纳控制”的步骤。第一网络设备500可执行如图11所示的实施例的相关步骤，此处不再赘述。
又一个实施例中，图15示出了上述实施例涉及的第一网络设备600的一种可能的结构示意图，如图15所示，第一网络设备600可以包括：接收模块601和发送模块602。其中，接收模块601可以用于“接收第二网络设备发送的第一消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的31部分。发送模块602可以用于“接收模块接收到第一消息后，向第三网络设备发送第二消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的32部分。接收模块601还用于“接收第三网络设备发送的第三消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的34部分、36部分、38部分。发送模块602还用于“接收模块接收到第三消息后，向第二网络设备发送第四消息”的步骤，例如，该模块可以用于支持第一网络设备执行上述方法实施例中的35部分、37部分、39部分。即，第一网络设备600可执行如图10所示的实施例的相关步骤。
下面介绍本申请实施例提供的一种装置。如图16所示：
该装置包括处理模块701和通信模块702。可选的，该装置还包括存储模块703。处理模块701、通信模块702和存储模块703通过通信总线相连。
通信模块702可以是具有收发功能的装置，用于与其他网络设备或者通信网络进行通信。
存储模块703可以包括一个或者多个存储器，存储器可以是一个或者多个设备、电路中用于存储程序或者数据的器件。
存储模块703可以独立存在，通过通信总线与处理模块701相连。存储模块也可以与处理模块701集成在一起。
装置700可以用于网络设备、电路、硬件组件或者芯片中。
装置700可以是本申请实施例中的网络设备，例如：基站102或基站103。基站的示意图可以如图2所示。可选的，装置700的通信模块702可以包括基站的天线和收发机，例如图2中的天线105和收发机103。通信模块702还可以包括基站的网络接口，例如图2中的网络接口104。
装置700可以是本申请实施例中的网络设备(例如：源基站、AMF等)中的芯片。通信模块702可以是输入或者输出接口、管脚或者电路等。可选的，存储模块可以存储基站侧的方法的计算机执行指令，以使处理模块701执行上述实施例中基站侧的方法。存储模块703可以是寄存器、缓存或者RAM等，存储模块703可以和处理模块701集成在一起；存储模块703可以是ROM或者可存储静态信息和指令的其他类型的静态存储设备，存储模块703可以与处理模块701相独立。可选的，随着无线通信技术的发展，收发机可以被集成在装置700上，例如通信模块702集成了收发机103，网络接口104。
当装置700是本申请实施例中的网络设备或者网络设备中的芯片时，可以实现上述实施例中网络设备执行的方法。
本申请实施例还提供了一种计算机可读存储介质。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，则功能可以作为一个或多个指令或代码存储在计算机可读介质上或者在计算机可读介质上传输。计算机可读介质可以包括计算机存储介质和通信介质，还可以包括任何可以将计算机程序从一个地方传送到另一个地方的介质。存储介质可以是可由计算机访问的任何可用介质。
作为一种可选的设计，计算机可读介质可以包括RAM，ROM，EEPROM，CD-ROM或其它光盘存储器，磁盘存储器或其它磁存储设备，或可用于承载的任何其它介质或以指令或数据结构的形式存储所需的程序代码，并且可由计算机访问。而且，任何连接被适当地称为计算机可读介质。例如，如果使用同轴电缆，光纤电缆，双绞线，数字用户线(DSL)或无线技术(如红外，无线电和微波)从网站，服务器或其它远程源传输软件，则同轴电缆，光纤电缆，双绞线，DSL或诸如红外，无线电和微波之类的无线技术包括在介质的定义中。如本文所使用的磁盘和光盘包括光盘(CD)，激光盘，光盘，数字通用光盘(DVD)，软盘和蓝光盘，其中磁盘通 常以磁性方式再现数据，而光盘利用激光光学地再现数据。上述的组合也应包括在计算机可读介质的范围内。
本申请实施例还提供了一种计算机程序产品。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，可以全部或者部分得通过计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行上述计算机程序指令时，全部或部分地产生按照上述方法实施例中描述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (28)

  1. 一种通信方法，其特征在于，应用于第一网络设备，所述方法包括：
    接收来自第二网络设备的第一消息，所述第一消息包括网络切片配置信息，所述网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
    向所述第二网络设备发送第二消息，所述第二消息用于指示所述第一网络设备拒绝m个网络切片为所述终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
  2. 根据权利要求1所述的方法，其特征在于，所述向所述第二网络设备发送第二消息，包括：
    基于本地可用资源和/或本地策略，确定拒绝所述m个网络切片为所述终端设备提供的最大数据速率，则向所述第二网络设备发送所述第二消息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    向所述第二网络设备发送拒绝信息，用于指示所述第一网络设备拒绝m个网络切片的原因为所述第一网络设备不支持所述m个网络切片为所述终端设备提供的最大数据速率。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    向所述第二网络设备发送建议信息，用于指示所述第一网络设备所能支持的所述m个网络切片中至少一个网络切片为所述终端设备提供的最大数据速率。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述网络切片配置信息包括以下至少之一：
    第一指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的非保证比特速率服务质量Non-GBR QoS流和/或保证比特速率服务质量GBR QoS流提供的聚合比特速率；
    第二指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的上行数据流提供的聚合比特速率，所述上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；
    第三指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的下行数据流提供的聚合比特速率，所述下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，
    所述第一消息为切换请求消息；
    或者，
    所述第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；
    或者，
    所述第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；
    或者，
    所述第一消息为次要节点增加请求消息或者次要节点修改请求消息；
    或者，
    所述第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
  7. 一种通信方法，其特征在于，应用于第二网络设备，所述方法包括：
    向第一网络设备发送第一消息，所述第一消息包括网络切片配置信息，所述网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
    接收来自所述第一网络设备的第二消息，所述第二消息用于指示所述第一网络设备拒绝m个网络切片为所述终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
  8. 根据权利要求7所述的方法，其特征在于，所述第二消息为所述第一网络设备基于本地可用资源和/或本地策略，确定拒绝所述m个网络切片为所述终端设备提供的最大数据速率，向所述第二网络设备发送的。
  9. 根据权利要求7或8所述的方法，其特征在于，所述方法还包括：
    接收所述第一网络设备发送的拒绝信息，其中，所述拒绝信息用于指示所述第一网络设备拒绝m个网络切片的原因为所述第一网络设备不支持所述m个网络切片为所述终端设备提供的最大数据速率。
  10. 根据权利要求7至9任一项所述的方法，其特征在于，所述方法还包括：
    接收所述第一网络设备发送的建议信息，其中，所述建议信息用于指示所述第一网络设备所能支持的所述m个网络切片中至少一个网络切片为所述终端设备提供的最大数据速率。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    基于所述建议信息，修改所述至少一个网络切片为所述终端设备提供的最大数据速率，并向所述第一网络设备指示修改后的所述至少一个网络切片为所述终端设备提供的最大数据速率。
  12. 根据权利要求7至11任一项所述的方法，其特征在于，所述网络切片配置信息包括以下至少之一：
    第一指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；
    第二指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的上行数据流提供的聚合比特速率，所述上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；
    第三指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的下行数据流提供的聚合比特速率，所述下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
  13. 根据权利要求7至12任一项所述的方法，其特征在于，
    所述第一消息为切换请求消息；
    或者，
    所述第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；
    或者，
    所述第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；
    或者，
    所述第一消息为次要节点增加请求消息或者次要节点修改请求消息；
    或者，
    所述第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
  14. 一种通信装置，其特征在于，应用于第一网络设备，所述装置包括：
    存储器和处理器，所述存储器和所述处理器耦合；
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收来自第二网络设备的第一消息，所述第一消息包括网络切片配置信息，所述网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
    向所述第二网络设备发送第二消息，用于指示所述第一网络设备拒绝m个网络切片为所述终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
  15. 根据权利要求14所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    基于本地可用资源和/或本地策略，确定拒绝所述m个网络切片为所述终端设备提供的最大数据速率，则向所述第二网络设备发送所述第二消息。
  16. 根据权利要求14或15所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    向所述第二网络设备发送拒绝信息，用于指示所述第一网络设备拒绝m个网络切片的原因为所述第一网络设备不支持所述m个网络切片为所述终端设备提供的最大数据速率。
  17. 根据权利要求14至16任一项所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    向所述第二网络设备发送建议信息，用于指示所述第一网络设备所能支持的所述m个网络切片中至少一个网络切片为所述终端设备提供的最大数据速率。
  18. 根据权利要求14至17任一项所述的装置，其特征在于，所述网络切片配置信息包括以下至少之一：
    第一指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；
    第二指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的上行数据流提供的聚合比特速率，所述上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；
    第三指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的下行数据流提供的聚合比特速率，所述下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
  19. 根据权利要求14至18任一项所述的装置，其特征在于，
    所述第一消息为切换请求消息；
    或者，
    所述第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；
    或者，
    所述第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；
    或者，
    所述第一消息为次要节点增加请求消息或者次要节点修改请求消息；
    或者，
    所述第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
  20. 一种通信装置，其特征在于，应用于第二网络设备，所述装置包括：
    存储器和处理器，所述存储器和所述处理器耦合；
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    向第一网络设备发送第一消息，所述第一消息包括网络切片配置信息，所述网络切片配置信息用于指示n个网络切片中的每个网络切片为终端设备提供的最大数据速率，n为大于或等于1的整数；
    接收来自所述第一网络设备的第二消息，所述第二消息用于指示所述第一网络设备拒绝m个网络切片为所述终端设备提供的最大数据速率的配置需求，其中，m为大于或等于0且小于或等于n的整数。
  21. 根据权利要求20所述的装置，其特征在于，所述第二消息为所述第一网络设备基于本地可用资源和/或本地策略，确定拒绝所述m个网络切片为所述终端设备提供的最大数据速率，向所述第二网络设备发送的。
  22. 根据权利要求20或21所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收所述第一网络设备发送的拒绝信息，其中，所述拒绝信息用于指示所述第一网络设备拒绝m个网络切片的原因为所述第一网络设备不支持所述m个网络切片为所述终端设备提供的最大数据速率。
  23. 根据权利要求20至22任一项所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收所述第一网络设备发送的建议信息，其中，所述建议信息用于指示所述第一网络设备所能支持的所述m个网络切片中至少一个网络切片为所述终端设备提供的最大数据速率。
  24. 根据权利要求23所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    基于所述建议信息，修改所述至少一个网络切片为所述终端设备提供的最大数据速率，并向所述第一网络设备指示修改后的所述至少一个网络切片为所述终端设备提供的最大数速率。
  25. 根据权利要求20至24任一项所述的装置，其特征在于，所述网络切片配置信息包括以下至少之一：
    第一指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的Non-GBR QoS流和/或GBR QoS流提供的聚合比特速率；
    第二指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的上行数据流提供的聚合比特速率，所述上行数据流为上行Non-GBR QoS流和/或上行GBR QoS流；
    第三指示信息，用于指示所述n个网络切片中的每个网络切片为所述终端设备的下行数据流提供的聚合比特速率，所述下行数据流为下行Non-GBR QoS流和/或下行GBR QoS流。
  26. 根据权利要求20至25任一项所述的装置，其特征在于，
    所述第一消息为切换请求消息；
    或者，
    所述第一消息为UE上下文设置请求消息或者UE上下文修改请求消息；
    或者，
    所述第一消息为承载上下文设置请求消息或者承载上下文修改请求消息；
    或者，
    所述第一消息为次要节点增加请求消息或者次要节点修改请求消息；
    或者，
    所述第一消息为PDU会话资源设置请求消息，或者初始上下文设置请求消息。
  27. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序包含至少一段代码，该至少一段代码可由计算机执行，以控制所述计算机执行权利要求1-6所述的方法。
  28. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，该计算机程序包含至少一段代码，该至少一段代码可由计算机执行，以控制所述计算机执行权利要求7-13所述的方法。
PCT/CN2020/115328 2019-09-26 2020-09-15 通信方法及装置 Ceased WO2021057549A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20869389.5A EP4030820B1 (en) 2019-09-26 2020-09-15 Communication method and device
KR1020227013975A KR20220086584A (ko) 2019-09-26 2020-09-15 통신 방법 및 장치
US17/704,362 US12363601B2 (en) 2019-09-26 2022-03-25 Communication method and apparatus
US19/242,485 US20250380194A1 (en) 2019-09-26 2025-06-18 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910919493.1 2019-09-26
CN201910919493.1A CN112566186B (zh) 2019-09-26 2019-09-26 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/704,362 Continuation US12363601B2 (en) 2019-09-26 2022-03-25 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2021057549A1 true WO2021057549A1 (zh) 2021-04-01

Family

ID=75029983

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/115328 Ceased WO2021057549A1 (zh) 2019-09-26 2020-09-15 通信方法及装置

Country Status (5)

Country Link
US (2) US12363601B2 (zh)
EP (1) EP4030820B1 (zh)
KR (1) KR20220086584A (zh)
CN (2) CN112566186B (zh)
WO (1) WO2021057549A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116347529A (zh) * 2021-12-22 2023-06-27 中国电信股份有限公司 辅节点预留资源的方法、基站、辅节点和通信系统
WO2023117559A1 (en) * 2021-12-22 2023-06-29 Nokia Technologies Oy Bit rate management in cellular communication networks

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20210088268A (ko) * 2020-01-06 2021-07-14 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스 데이터 속도를 제어하기 위한 장치 및 방법
CN114071565B (zh) * 2020-08-06 2024-07-12 中国电信股份有限公司 网络切片用户数据速率限制方法、装置和系统、存储介质
CN120642441A (zh) * 2023-02-13 2025-09-12 三星电子株式会社 用于在多rat双连接中处理辅节点操作的方法及装置
CN120021289A (zh) * 2023-11-17 2025-05-20 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770794A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种网络切片配置方法及装置
WO2019007486A1 (en) * 2017-07-04 2019-01-10 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND APPARATUS FOR SUPPORTING THE INSTANCATION OF A NETWORK WAFER IN A COMMUNICATION NETWORK
CN109792657A (zh) * 2017-10-26 2019-05-21 Oppo广东移动通信有限公司 无线通信方法和设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019096918A (ja) * 2016-04-05 2019-06-20 シャープ株式会社 端末装置、基地局装置、ＭＭＥ（Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｅｎｔｉｔｙ）および通信制御方法
CN109257827B (zh) * 2016-09-30 2020-09-18 华为技术有限公司 通信方法、装置、系统、终端和接入网设备
CN108366365B (zh) * 2017-01-26 2021-03-23 华为技术有限公司 一种接入目标小区的方法以及设备
AU2018255075B2 (en) * 2017-04-19 2020-02-06 Lg Electronics Inc. Method for processing PDU session establishment procedure and AMF node
US11122470B2 (en) * 2017-05-04 2021-09-14 Ofinno, Llc Network slice information for handover procedure
CN108964961A (zh) * 2017-05-27 2018-12-07 华为技术有限公司 一种管理传输网切片的方法、装置及系统
CN109151924B (zh) * 2017-06-16 2024-03-01 华为技术有限公司 通信方法及接入网设备、核心网设备
CN109151940B (zh) * 2017-06-16 2021-12-03 华为技术有限公司 一种基于dc的切换方法及设备
CN111491345B (zh) * 2017-08-11 2021-04-20 华为技术有限公司 通信方法、接入网设备及计算机可读存储介质
CN109842955B (zh) * 2017-09-23 2023-11-21 华为技术有限公司 通信方法及装置
KR20250136936A (ko) * 2019-07-03 2025-09-16 지티이 코포레이션 네트워크 슬라이싱을 위한 인가 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770794A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种网络切片配置方法及装置
WO2019007486A1 (en) * 2017-07-04 2019-01-10 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND APPARATUS FOR SUPPORTING THE INSTANCATION OF A NETWORK WAFER IN A COMMUNICATION NETWORK
CN109792657A (zh) * 2017-10-26 2019-05-21 Oppo广东移动通信有限公司 无线通信方法和设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA ET AL.: ""RDI handling for data forwarding at handover"", "3GPP TSG-RAN WG2 MEETING #104 R2-1816412", 2 November 2018 (2018-11-02), XP051480375 *
See also references of EP4030820A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116347529A (zh) * 2021-12-22 2023-06-27 中国电信股份有限公司 辅节点预留资源的方法、基站、辅节点和通信系统
WO2023117559A1 (en) * 2021-12-22 2023-06-29 Nokia Technologies Oy Bit rate management in cellular communication networks

Also Published As

Publication number Publication date
EP4030820B1 (en) 2026-04-29
EP4030820A1 (en) 2022-07-20
KR20220086584A (ko) 2022-06-23
US20250380194A1 (en) 2025-12-11
CN114828101B (zh) 2025-08-08
CN112566186B (zh) 2022-04-05
EP4030820A4 (en) 2022-11-09
US12363601B2 (en) 2025-07-15
CN112566186A (zh) 2021-03-26
CN114828101A (zh) 2022-07-29
US20220217593A1 (en) 2022-07-07

Similar Documents

Publication Publication Date Title
US11039361B2 (en) Enhanced 5GSM state mapping when interworking
US11240699B2 (en) Insufficient resources in the UE during PDU session establishment procedure
US10893459B2 (en) Wireless base station, first wireless control apparatus, second wireless control apparatus, and wireless apparatus
US12363601B2 (en) Communication method and apparatus
CN110999520B (zh) 无线接入网节点、核心网节点和无线终端及其方法
CN112788680B (zh) 一种数据传输的方法及相关设备
CN105874877B (zh) 控制无线接入技术(rat)通信管理器的装置、系统和方法
JP2022553672A (ja) 無線通信システムにおけるエンドツーエンドのスライシング
CN108696910B (zh) 一种选择目标基站的方法、装置和存储介质
WO2021217672A1 (zh) 网络切片的负载控制方法及相关产品
WO2020103807A1 (zh) 一种通信方法及装置
CN112839332A (zh) 多频段通信、接口参数更新方法、ap设备和ml设备
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
WO2018027988A1 (zh) 网络切片的选择方法、无线接入设备和终端
CN111866905B (zh) 通信方法及相关设备
CN105379353B (zh) 一种切换方法及源接入网节点、目标接入网节点
US20250212093A1 (en) Network node, communication method, and storage medium
WO2022001738A1 (zh) 一种移动边缘计算处理方法以及相关设备
CN107005904A (zh) 一种用户设备切换方法和装置
CN115250511A (zh) 通信方法及通信装置
US12568549B2 (en) MA PDU reactivation requested handling
WO2024011462A1 (zh) 一种通信方法及装置、通信设备、接入网架构
WO2021056449A1 (zh) 一种会话切换方法、装置及相关设备
RU2642836C1 (ru) Устройство и способы отсоединения расширенного выделенного канала восходящей линии связи и высокоскоростного совместно используемого канала нисходящей линии связи
CN104521300A (zh) 一种控制服务质量的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20869389

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227013975

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020869389

Country of ref document: EP

Effective date: 20220412

WWR Wipo information: refused in national office

Ref document number: 1020227013975

Country of ref document: KR

WWR Wipo information: refused in national office

Ref document number: 1020227013975

Country of ref document: KR

WWC Wipo information: continuation of processing after refusal or withdrawal

Ref document number: 1020227013975

Country of ref document: KR