WO2021244078A1 - 一种切换方法及装置 - Google Patents

一种切换方法及装置 Download PDF

Info

Publication number
WO2021244078A1
WO2021244078A1 PCT/CN2021/078307 CN2021078307W WO2021244078A1 WO 2021244078 A1 WO2021244078 A1 WO 2021244078A1 CN 2021078307 W CN2021078307 W CN 2021078307W WO 2021244078 A1 WO2021244078 A1 WO 2021244078A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
source
pdu session
identifier
ran node
Prior art date
Application number
PCT/CN2021/078307
Other languages
English (en)
French (fr)
Inventor
孙飞
罗海燕
曾清海
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21817557.8A priority Critical patent/EP4152821A4/en
Publication of WO2021244078A1 publication Critical patent/WO2021244078A1/zh
Priority to US17/994,292 priority patent/US20230098982A1/en

Links

Images

Classifications

    • 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/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • 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/06—Reselecting a communication resource in the serving access point
    • 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/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength

Definitions

  • This application relates to the field of communication technology, and in particular to a handover method and device.
  • 5G Fifth Generation
  • 5G is a wireless communication technology has been a hot industry, when meet the above requirements, requires 5G equipped with flexible, scalability, to meet different business needs.
  • 5G provides users with customized network services through end-to-end network slices. Specifically, through flexible allocation of network resources and on-demand networking, 5G virtualizes multiple logical networks with different characteristics and isolated from each other on the same physical facility to provide targeted services to users.
  • a terminal device in a connected state moves from a source radio access network (RAN) node to a target RAN node, its communication services also need to be switched to the target RAN node.
  • RAN radio access network
  • 5G networks due to differences in the functions of RAN nodes of different equipment vendors, or operators’ regional strategies for network slicing deployment, different RAN nodes have different support capabilities for network slicing, so their coverage
  • the network slicing services supported within the scope will also be different.
  • the network slice supported by one RAN node may be different from the network slice supported by another RAN node.
  • the network slice connected to the source RAN node for communication may not be supported by the target RAN node.
  • the embodiments of the present application provide a handover method and device to solve the problem of high signaling overhead in the handover interaction process.
  • a handover method includes: a terminal device receives a second message from a source radio access network RAN node; wherein, the second message includes at least one source network slice identifier, and the at least The identifier of at least one protocol data unit PDU session of each source network slice in one source network slice, the identifier of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped; or at least one source network slice identifier, so An identifier of at least one PDU session of each source network slice in the at least one source network slice, and an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice.
  • the terminal device receives the identification of the network slice to which the session is remapped, or an indication of whether the session is rolled back to the default network slice, and can use the remapped network slice or the default network slice in the subsequent session establishment process. Data transmission is performed on the slice, which improves the reliability of communication.
  • the second message is a radio resource control RRC message
  • the second message further includes the at least one PDU session
  • the method further includes: the terminal device randomly accesses the target RAN node, and remaps to the target RAN node according to the at least one PDU session
  • the configuration parameters of the network slice of the network slice communicate with the target RAN node; or the terminal device randomly accesses the target RAN node, and communicates with the target RAN node according to the configuration parameter of the default network slice.
  • a handover method includes: a terminal device receives a second message from a source RAN node; wherein, the second message includes at least one source network slice identifier, and the at least one source network slice The identification of at least one QoS flow in each source network slice in the at least one source network slice, the identification of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped; or at least one source network slice identification, in the at least one source network slice An identifier of at least one QoS flow of each source network slice, and an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice.
  • the terminal device receives the identification of the network slice to which the QoS flow is remapped, or an indication of whether the QoS flow has fallen back to the default network slice, and can be used in the subsequent QoS flow establishment process in the remapped network slice or Data transmission is performed on the default network slice, which improves the reliability of communication.
  • the second message is an RRC message.
  • the second message further includes that the at least one QoS flow is remapped to The configuration parameters of the network slice of the network slice, or the configuration parameters of the default network slice; the method further includes: the terminal device randomly accesses the target RAN node, and remaps to the network slice according to the at least one QoS flow Or the terminal device randomly accesses the target RAN node, and communicates with the target RAN node according to the configuration parameters of the default network slice.
  • a handover method includes: a terminal device receives a second message from a source RAN node; wherein, the second message includes at least one source network slice identifier, which belongs to the at least one source network
  • the identifier of at least one DRB of each source network slice in the slice belongs to the identifier of the network slice to which some or all of the DRBs in the at least one DRB are remapped; or at least one source network slice identifier belongs to the at least one source network slice
  • the identifier of at least one DRB of each source network slice belongs to an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice.
  • the terminal device receives the identifier of the network slice to which the DRB is remapped, or an indication of whether the DRB is remapped to the default network slice, and can be used in the remapped network slice or the default network slice during the subsequent DRB establishment process. Data transmission is performed on the corresponding resource on the slice, which improves the reliability of communication.
  • the second message is an RRC message.
  • the second message further includes the network to which the at least one DRB is remapped.
  • the configuration parameters of the slice, or the configuration parameters of the default network slice; the method further includes: the terminal device randomly accesses the target RAN node according to the configuration parameters of the network slice to which the at least one DRB is remapped Communicate with the target RAN node; or the terminal device randomly accesses the target RAN node, and communicates with the target RAN node according to the configuration parameters of the default network slice.
  • a handover method includes: a source radio access network RAN node sends a first handover message to a first network node, and the first handover message includes: at least one source network slice identifier, and The first handover message further includes at least one of the following: an indication of whether at least one protocol data unit PDU session of each source network slice in the at least one source network slice supports network slice remapping, and each of the at least one source network slice An indication of whether at least one PDU session of the source network slice supports network slice fallback; and the source RAN node receives a first response message from the first network node; wherein, the first handover message includes the PDU In the case of an indication of whether the session supports network slice remapping, the first response message includes the at least one source network slice identifier, the identifier of at least one PDU session of each source network slice in the at least one source network slice, and The identification of the network slice to which part or all of the PDU sessions in the
  • an indication of whether the session supports network slice remapping is carried in the handover message, and/or an indication of whether the session supports network slice fallback, without the need to carry the entire network slice remapping information, and / Or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the method further includes: the source RAN node obtains network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier , And a remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • each RAN node obtains network slice remapping information in advance, and/or default network slice information, the source RAN node does not need to carry the entire network slice remapping information during the handover process of each terminal device, and / Or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the source RAN node acquiring network slice remapping information, and/or the default network slice information includes: the source RAN node receives a first message, the first message including all The network slice remapping information, and/or, the default network slice information.
  • the core network can notify the source access network node of the network slice remapping information in advance through a separate message before the handover, and / Or, the default network slice information.
  • the method before the source RAN node sends the first handover message to the first network node, the method further includes: the source RAN node receives the at least one PDU session establishment request from the core network node
  • the at least one PDU session establishment request includes an indication of whether the established at least one PDU session supports network slice remapping, and/or an indication of whether the established at least one PDU session supports network slice fallback.
  • the source access network node receives an indication of whether the established session supports network slice remapping, and/or an indication of whether the established session supports network slice fallback, thus, In the subsequent handover process, network slice remapping or fallback can be performed according to the above instructions.
  • the first handover message further includes the network slice remapping information, and/or, the default network slice information.
  • the first handover message may carry the aforementioned network slice remapping information or the default network slice information.
  • the first network node is a target RAN node
  • the source RAN node sending a first handover message to the first network node includes: the source RAN node sending to the target RAN node A handover request message
  • the source RAN node receiving a first response message from the first network node includes: the source RAN node receives a handover request response message from the target RAN node; or the first network node Is a core network node
  • the source RAN node sends a first handover message to a first network node, including: the source RAN node sends a handover request message to the core network node; the source RAN node receives a handover request message from the first network node;
  • the first response message of the network node includes: the source RAN node receives a handover command from the core network node.
  • the source access network node can complete the remapping or fallback of the network slice in the above-mentioned switching process through X
  • the method further includes: the source RAN node sends a second message to the terminal device; wherein, the second message includes at least one source network slice identifier, and the at least one source network slice The identifier of at least one PDU session of each source network slice in the at least one PDU session, the identifier of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped; or the second message includes at least one source network slice identifier, the An identifier of at least one PDU session of each source network slice in at least one source network slice, and an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice.
  • the source RAN node notifies the terminal device of the above information after receiving the identifier of the network slice to which the session is remapped from the target RAN node, or the indication of whether the session is remapped to the default network slice or not, so that the terminal device In the subsequent session establishment process, data transmission is performed on the remapped network slice or the default network slice, which improves the reliability of communication.
  • a handover method includes: a source RAN node sends a first handover message to a first network node, the first handover message includes: at least one source network slice identifier, and the first handover The message also includes at least one of the following: an indication of whether at least one QoS flow of each source network slice in the at least one source network slice supports network slice remapping, and at least one QoS of each source network slice in the at least one source network slice An indication of whether the flow supports network slice fallback; and the source RAN node receives a first response message from the first network node; wherein the first handover message includes whether the QoS flow supports network slice remapping
  • the first response message includes the at least one source network slice identifier, the at least one QoS flow identifier of each source network slice in the at least one source network slice, and a part of the at least one QoS flow Or the identifier of the network slice to which all
  • the handover message carries an indication of whether the QoS flow supports network slice remapping, and/or whether the QoS flow supports network slice fallback, without the need to carry the entire network slice remapping information , And/or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the method further includes: the source RAN node obtains network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier , And a remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • each RAN node obtains network slice remapping information in advance, and/or default network slice information, the source RAN node does not need to carry the entire network slice remapping information during the handover process of each terminal device, and / Or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the source RAN node acquiring network slice remapping information, and/or the default network slice information includes: the source RAN node receives a first message, the first message including all The network slice remapping information, and/or, the default network slice information.
  • the core network can notify the source access network node of the network slice remapping information in advance through a separate message before the handover, and / Or, the default network slice information.
  • the method before the source RAN node sends the first handover message to the first network node, the method further includes: the source RAN node receives the at least one QoS flow establishment request from a core network node
  • the at least one QoS flow establishment request includes an indication of whether the established at least one QoS flow supports network slice remapping, and/or an indication of whether the established at least one QoS flow supports network slice fallback.
  • the source access network node when a QoS flow is established, the source access network node receives an indication of whether the established QoS flow supports network slice remapping, and/or an indication of whether the established QoS flow supports network slice fallback Therefore, in the subsequent handover process, network slice remapping or fallback can be performed according to the above-mentioned instructions.
  • the first handover message further includes the network slice remapping information, and/or the default network slice information.
  • the first handover message may carry the aforementioned network slice remapping information or the default network slice information.
  • the first network node is a target RAN node
  • the source RAN node sending a first handover message to the first network node includes: the source RAN node sending to the target RAN node A handover request message
  • the source RAN node receiving a first response message from the first network node includes: the source RAN node receives a handover request response message from the target RAN node; or the first network node Is a core network node
  • the source RAN node sends a first handover message to a first network node, including: the source RAN node sends a handover request message to the core network node; the source RAN node receives a handover request message from the first network node;
  • the first response message of the network node includes: the source RAN node receives a handover command from the core network node.
  • the source access network node can complete the remapping or fallback of the network slice in the above-mentioned switching process through X
  • the method further includes: the source RAN node sends a second message to the terminal device; wherein, the second message includes at least one source network slice identifier, and the at least one source network slice The identification of at least one QoS flow in each source network slice in the at least one QoS flow, the identification of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped; or the second message includes at least one source network slice identification, the An identifier of at least one QoS flow of each source network slice in at least one source network slice, and an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice.
  • the source RAN node notifies the terminal device of the above information after receiving the identification of the network slice to which the QoS flow is remapped from the target RAN node, or the indication of whether the QoS flow has fallen back to the default network slice, and thereby In the subsequent session establishment process, the terminal device performs data transmission on the remapped network slice or the default network slice, which improves the reliability of communication.
  • a handover method includes: a source RAN node sends a first handover message to a first network node, the first handover message includes: at least one source network slice identifier, the first handover The message also includes at least one of the following: an indication of whether at least one DRB belonging to each source network slice in the at least one source network slice supports network slice remapping, and at least one of the source network slices belonging to each source network slice in the at least one source network slice An indication of whether the DRB supports network slice fallback; and the source RAN node receives a first response message from the first network node; wherein the first handover message includes whether the DRB supports network slice remapping If indicated, the first response message includes the at least one source network slice identifier, the identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and the identifier of at least one DRB belonging to the at least one DRB.
  • the first response message includes the at least one source network slice identifier , The identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice; or in the first handover
  • the first response message includes the at least one source network slice identifier, which belongs to the at least one source network slice identifier.
  • the identifier of at least one DRB of each source network slice in one source network slice, the identifier of the network slice to which some or all of the DRBs in the at least one DRB are remapped, or the at least one source network slice identifier belongs to the at least one An identifier of at least one DRB of each source network slice in one source network slice, and an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice.
  • the handover message carries an indication of whether the DRB supports network slice remapping, and/or whether the DRB supports network slice fallback, without having to carry the entire network slice remapping information, and / Or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the method further includes: the source RAN node obtains network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier , And a remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • each RAN node obtains network slice remapping information in advance, and/or default network slice information, the source RAN node does not need to carry the entire network slice remapping information during the handover process of each terminal device, and / Or the default network slice information, which saves the signaling overhead during the handover interaction process.
  • the source RAN node acquiring network slice remapping information, and/or the default network slice information includes: the source RAN node receives a first message, the first message including all The network slice remapping information, and/or, the default network slice information.
  • the core network can notify the source access network node of the network slice remapping information in advance through a separate message before the handover, and / Or, the default network slice information.
  • the first network node is a target RAN node
  • the source RAN node sending a first handover message to the first network node includes: the source RAN node sending to the target RAN node A handover request message
  • the source RAN node receiving a first response message from the first network node includes: the source RAN node receives a handover request response message from the target RAN node; or the first network node Is a core network node
  • the source RAN node sends a first handover message to a first network node, including: the source RAN node sends a handover request message to the core network node; the source RAN node receives a handover request message from the first network node;
  • the first response message of the network node includes: the source RAN node receives a handover command from the core network node.
  • the source access network node can complete the remapping or fallback of the network slice in the above-mentioned switching process through X
  • the method further includes: the source RAN node sends a second message to the terminal device; wherein, the second message includes at least one source network slice identifier, which belongs to the at least one source network The identifier of at least one DRB of each source network slice in the slice belongs to the identifier of the network slice to which some or all of the DRBs in the at least one DRB are remapped; or the second message includes at least one source network slice identifier, which belongs to the The identifier of at least one DRB of each source network slice in at least one source network slice belongs to an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice.
  • the source RAN node notifies the terminal device of the above information after receiving the identifier of the network slice to which the DRB is remapped from the target RAN node, or the indication of whether the DRB is remapped to the default network slice or not, so that the terminal device In the subsequent DRB establishment process, data transmission is performed on the remapped network slice or the default network slice, which improves the reliability of communication.
  • a handover method includes: a target radio access network RAN node receives a second handover message from a second network node, where the second handover message includes: at least one source network slice identifier, The second handover message further includes at least one of the following: an indication of whether at least one protocol data unit PDU session of each source network slice in the at least one source network slice supports network slice remapping, in the at least one source network slice An indication of whether at least one PDU session of each source network slice supports network slice fallback; the target RAN node performs admission control according to the second handover message, and the admission control is used to determine whether to control the at least one Perform network slice remapping for the PDU session, and determine the identity of the network slice to which it is remapped; or, the admission control is used to determine whether to roll back the at least one PDU session to the default network slice; and the target RAN The node sends a second response message to the second network node; wherein, in
  • the second response message includes at least one source network slice identifier, and at least one PDU of each source network slice in the at least one source network slice The identifier of the session, indicating whether part or all of the PDU sessions in the at least one PDU session fall back to the default network slice; or the second handover message includes an indication whether the PDU session supports network slice remapping ,
  • the second response message includes at least one source network slice identifier, and at least one PDU session of each source network slice in the at least one source network slice ID, the ID of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped, or, at least one source network slice ID, the ID of at least one PDU session of each source network slice in the at least one source network slice Identifier, an indication of whether part or all of the PDU sessions in the at least one P
  • the method further includes: the target RAN node obtains network slice remapping information, and/or, default network slice information, where the network slice remapping information includes at least one source network slice identifier , And a remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the target RAN node acquiring network slice remapping information, and/or the default network slice information includes: the target RAN node receives a first message, and the first message includes all The network slice remapping information, and/or, the default network slice information.
  • the second network node is a source RAN node
  • the target RAN node receives a second handover message from the second network node, including: the target RAN node receives the source RAN node A handover request message of a node; the target RAN node sending a second response message to the second network node includes: the target RAN node sends a handover request response message to the source RAN node; or the second network node Is a core network node, and the target RAN node receives a second handover message from a second network node, including: the target RAN node receives the handover request message from the core network node;
  • the sending of the second response message by the second network node includes: the target RAN node sending the handover request response message to the core network node.
  • the method further includes: the target RAN node sends a path switch request to the core network node, the path switch request including the network slice identifier to which each PDU session in the at least one PDU session belongs , Or, the path switch request includes an indication of whether each PDU session in the at least one PDU session performs network slicing rollback; the target RAN node receives a path switch response from the core network node, and the path switch response At least one of the following information is included: the PDU session identifier of the at least one PDU session for which the path switch succeeds, the PDU session identifier of the at least one PDU session for which the path switch fails, and the context of the modified at least one PDU session.
  • a handover method includes: a target RAN node receives a second handover message from a second network node, the second handover message includes: at least one source network slice identifier, the second The handover message further includes at least one of the following: an indication of whether at least one QoS flow of each source network slice in the at least one source network slice supports network slice remapping, and at least one of the source network slices in the at least one source network slice An indication of whether the QoS flow supports network slice fallback; the target RAN node performs admission control according to the second handover message, and the admission control is used to determine whether to perform network slice remapping on the at least one QoS flow , And determine the identity of the network slice to which it is remapped; or, the admission control is used to determine whether to fall back the at least one QoS flow to the default network slice; and the target RAN node reports to the second network The node sends a second response message; wherein, in the
  • the mapping information, and/or the default network slice information saves the signaling overhead during the handover interaction process.
  • the method further includes: the target RAN node obtains network slice remapping information, and/or, default network slice information, where the network slice remapping information includes at least one source network slice An identifier, and a remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the target RAN node acquiring network slice remapping information, and/or the default network slice information includes: the target RAN node receives a first message, and the first message includes all The network slice remapping information, and/or, the default network slice information.
  • the second network node is a source RAN node
  • the target RAN node receives a second handover message from the second network node, including: the target RAN node receives the source RAN node A handover request message of a node; the target RAN node sending a second response message to the second network node includes: the target RAN node sends a handover request response message to the source RAN node; or the second network node Is a core network node, and the target RAN node receives a second handover message from a second network node, including: the target RAN node receives the handover request message from the core network node;
  • the sending of the second response message by the second network node includes: the target RAN node sending the handover request response message to the core network node.
  • the method further includes: the target RAN node sends a path switch request to the core network node, the path switch request including the network slice identifier to which each QoS flow in the at least one QoS flow belongs Or, the path switching request includes an indication of whether each QoS flow in the at least one QoS flow performs network slicing fallback; the target RAN node receives a path switching response from the core network node, the path switching response At least one of the following information is included: the QoS flow identifier of the at least one QoS flow for which path switching is successful, the QoS flow identifier of the at least one QoS flow for which path switching fails, and the context of the modified at least one QoS flow.
  • a handover method comprising: a target RAN node receives a second handover message from a second network node, the second handover message including: at least one source network slice identifier, the first The second handover message also includes at least one of the following: an indication of whether at least one DRB belonging to each source network slice in the at least one source network slice supports network slice remapping, and the information belonging to each source network slice in the at least one source network slice An indication of whether at least one DRB supports network slice fallback; the target RAN node performs admission control according to the second handover message, and the admission control is used to determine whether to perform network slice remapping on the at least one DRB , And determine the identity of the network slice to be remapped; or, the admission control is used to determine whether to fall back the at least one DRB to the default network slice; and the target RAN node reports to the second network node Send a second response message; wherein, in the case that the second hand
  • the method further includes: the target RAN node obtains network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier , And a remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the target RAN node acquiring network slice remapping information, and/or the default network slice information includes: the target RAN node receives a first message, and the first message includes all The network slice remapping information, and/or, the default network slice information.
  • the second network node is a source RAN node
  • the target RAN node receives a second handover message from the second network node, including: the target RAN node receives the source RAN node A handover request message of a node; the target RAN node sending a second response message to the second network node includes: the target RAN node sends a handover request response message to the source RAN node; or the second network node Is a core network node, and the target RAN node receives a second handover message from a second network node, including: the target RAN node receives the handover request message from the core network node;
  • the sending of the second response message by the second network node includes: the target RAN node sending the handover request response message to the core network node.
  • this application provides a switching device, which may be a terminal device, or a chip or chipset in the terminal device.
  • the device may include a transceiver unit, and may also include a processing unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit The instructions stored in the storage module are executed, so that the terminal device executes the above-mentioned first aspect or the corresponding function in any implementation of the first aspect.
  • the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to The terminal device is caused to perform the corresponding function in the foregoing first aspect or any one of the first aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a switching device, which may be a terminal device, or a chip or chipset in the terminal device.
  • the device may include a transceiver unit, and may also include a processing unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit The instructions stored in the storage module are executed, so that the terminal device executes the above-mentioned second aspect or the corresponding function in any implementation of the second aspect.
  • the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to The terminal device is allowed to perform the corresponding function in the foregoing second aspect or any one of the second aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a switching device, which may be a terminal device, or a chip or chipset in the terminal device.
  • the device may include a transceiver unit, and may also include a processing unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit The instructions stored in the storage module are executed, so that the terminal device executes the above-mentioned third aspect or the corresponding function in any implementation of the third aspect.
  • the processing unit may be a processor, and the transceiving unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to The terminal device is allowed to perform the corresponding function in the foregoing third aspect or any one of the third aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a source RAN node, or a chip or chipset in a source access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiver unit may be a transceiver;
  • the device may also include a storage module, which may be a memory; the storage module is used to store instructions, The processing unit executes the instructions stored in the storage module, so that the source access network node executes the corresponding function in the fourth aspect or any design of the fourth aspect.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions to enable the source access network node to perform the corresponding function in the fourth aspect or any of the fourth aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a source RAN node, or a chip or chipset in a source access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor
  • the transceiver unit may be a transceiver;
  • the device may also include a storage module, which may be a memory; the storage module is used to store instructions, The processing unit executes the instructions stored in the storage module, so that the source access network node executes the corresponding function in the fifth aspect or any one of the fifth aspects.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions to enable the source access network node to perform the corresponding function in the fifth aspect or any of the fifth aspects.
  • the storage module may be a storage module (e.g., register, cache, etc.) in the chip or chipset, or a storage module (e.g., read-only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a source RAN node, or a chip or chipset in a source access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiver unit may be a transceiver;
  • the device may also include a storage module, which may be a memory; the storage module is used to store instructions, The processing unit executes the instructions stored in the storage module, so that the source access network node executes the corresponding function in the sixth aspect or any design of the sixth aspect.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions to enable the source access network node to perform the corresponding function in the sixth aspect or any design of the sixth aspect.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a target RAN node, or a chip or chipset in a target access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions,
  • the processing unit executes the instructions stored in the storage module, so that the target access network node executes the corresponding function in the seventh aspect or any one of the seventh aspects.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions to enable the target access network node to perform the corresponding function in the seventh aspect or any one of the seventh aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a target RAN node, or a chip or chipset in a target access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions,
  • the processing unit executes the instructions stored in the storage module, so that the target access network node executes the corresponding function in the eighth aspect or any one of the eighth aspects.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions to enable the target access network node to perform the corresponding function in the eighth aspect or any of the eighth aspects described above.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • this application provides a handover device, which may be a target RAN node, or a chip or chipset in a target access network node.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions,
  • the processing unit executes the instructions stored in the storage module, so that the target access network node executes the corresponding function in the ninth aspect or any one of the ninth aspects.
  • the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes what is stored in the storage module Instructions so that the target access network node executes the corresponding function in the ninth aspect or any of the ninth aspects.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read only memory, random access memory, etc.) located outside the chip or chipset.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the aforementioned first aspect or any one of the first aspects. Switch method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the aforementioned second aspect or any one of the second aspects. Switch method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the above-mentioned third aspect or any one of the third aspects. Switch method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in the fourth aspect or any one of the fourth aspects above. method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in the fifth aspect or any one of the fifth aspects above. method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in the sixth aspect or any one of the sixth aspects above. method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in the seventh aspect or any one of the seventh aspects above. method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in the eighth aspect or any one of the eighth aspects above. method.
  • a switching device which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes the switching as described in any one of the ninth aspect or the ninth aspect. method.
  • a computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute the first aspect to the ninth aspect or the first aspect.
  • the switching method described in any one of the aspect to the ninth aspect is designed.
  • a computer program product including instructions, which when run on a computer, causes the computer to execute the design described in any one of the first aspect to the ninth aspect or the first aspect to the ninth aspect.
  • the switching method when run on a computer, causes the computer to execute the design described in any one of the first aspect to the ninth aspect or the first aspect to the ninth aspect.
  • a chip is provided, which is coupled with a memory, and executes the switching method described in any one of the first aspect to the ninth aspect or the first aspect to the ninth aspect of the embodiments of the present application.
  • Coupled in the embodiments of the present application means that two components are directly or indirectly combined with each other.
  • a communication system including the above-mentioned switching device.
  • Figure 1 is a schematic diagram of the architecture of a communication system to which this application applies;
  • FIG. 2 is a schematic structural diagram of a switching device 200 provided by an embodiment of the application.
  • FIG. 3 is a schematic flowchart of a handover method provided by an embodiment of the application.
  • FIG. 4 is a schematic diagram of another flow of the handover method provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of another flow of the handover method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of another flow of the handover method provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of another flow of the handover method provided by an embodiment of the application.
  • FIG. 8 is a schematic flowchart of an exemplary method for switching between a centralized unit and a distributed unit in a target RAN node
  • FIG. 9 is a schematic flowchart of another handover method provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a switching device 300 provided by an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of a switching device 400 provided by an embodiment of the application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • e-LTE enhanced long term evolution
  • 5G fifth generation
  • NR new radio system
  • 6G sixth generation
  • the 5G mobile communication system involved in this application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system.
  • NSA non-standalone
  • SA standalone
  • the communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine to machine (M2M) communication system, and a device-to-device (D2D) communication system.
  • PLMN public land mobile network
  • D2D device-to-device
  • M2M machine to machine
  • D2D device-to-device
  • IoT Internet of Things
  • IoV communication system or other communication systems.
  • FIG. 1 is a schematic diagram of the architecture of a communication system to which this application applies.
  • the communication system 100 includes a terminal device 101, a source RAN node 102, and a target RAN node 103.
  • the terminal device 101, the source RAN node 102, and the target RAN node 103 may communicate directly, or communicate through the forwarding of other devices, which is not specifically limited in the embodiment of the present application.
  • the communication system may also include other network elements.
  • the terminal device 101 in the embodiment of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, and a user terminal.
  • terminal wireless communication equipment, user agent, user device, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop, WLL) stations, personal digital assistants (personal digital assistants, PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in the future 5G network or in the future
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs personal digital assistants
  • handheld devices with wireless communication functions computing devices or other processing devices connected to wireless modems
  • in-vehicle devices wearable devices
  • the terminal in the evolved PLMN or the terminal in the future Internet of Vehicles, etc. are not limited in the embodiment of the present application.
  • the terminal device 101 may be a mobile phone, a tablet computer, a computer with wireless transceiving function, a virtual reality terminal, an augmented reality terminal, a wireless terminal in industrial control, and a wireless terminal in unmanned driving.
  • wearable devices can also be referred to as wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which need to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device 101 can also be a terminal in an IoT system.
  • IoT is an important part of the development of information technology in the future. Interconnection, an intelligent network of interconnection of things.
  • the IoT technology can achieve massive connections, deep coverage, and power saving of the terminal through, for example, narrowband (NB) technology.
  • NB narrowband
  • the terminal device 101 may also include sensors such as smart printers, train detectors, gas stations, etc.
  • the main functions include collecting data (part of the terminal), receiving control information and downlink data from RAN nodes, and sending electromagnetic waves. , To transmit uplink data to the RAN node.
  • the source RAN node 102 or the target RAN node 103 in the embodiment of the present application may be any communication device with a wireless transceiving function for communicating with the terminal device 101.
  • the source RAN node 102 or the target RAN node 103 includes but is not limited to: evolved node B (evolved node B, eNB), baseband unit (BBU), wireless fidelity (wireless fidelity, WIFI) system access Point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP), or transmission reception point (transmission reception point, TRP), etc.
  • the RAN device may also be a gNB or TRP or TP in a 5G system, or one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system.
  • the access network device may also be a network node constituting a gNB or TP, such as a BBU, or a distributed unit (DU).
  • the gNB may include a central unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • CU realizes part of the functions of gNB
  • DU realizes part of the functions of gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and realizes the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical layer (PHY).
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas.
  • the source RAN node 102 or the target RAN node 103 may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the source RAN node 102 or the target RAN node 103 and the terminal device 101 in the embodiment of the present application can communicate through a licensed spectrum, or communicate through an unlicensed spectrum, or they can communicate through a licensed spectrum and an unlicensed spectrum at the same time. Spectrum to communicate.
  • the source RAN node 102 or the target RAN node 103 and the terminal device 101 can communicate through the frequency spectrum below 6 gigahertz (gigahertz, GHz), or through the frequency spectrum above 6 GHz, and can also use the frequency spectrum below 6 GHz and The frequency spectrum above 6GHz communicates.
  • the embodiment of the present application does not limit the spectrum resources used between the source RAN node 102 or the target RAN node 103 and the terminal device 101.
  • the terminal device 101, the source RAN node 102, or the target RAN node 103 in the embodiment of the present application can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water; it can also be deployed in the air Aircraft, balloons and satellites.
  • the embodiment of the present application does not limit the application scenarios of the terminal device 101, the source RAN node 102, or the target RAN node 103.
  • the terminal device 101, the source RAN node 102, or the target RAN node 103 includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of this application do not specifically limit the specific structure of the execution body of the methods provided in the embodiments of this application, as long as it can be provided according to the embodiments of this application by running a program that records the codes of the methods provided in the embodiments of this application.
  • the execution subject of the method provided in this embodiment of the present application may be the terminal device 101, the source RAN node 102 or the target RAN node 103, or the terminal device 101, the source RAN node 102 or the target RAN node 103 can call the program and execute the function module of the program.
  • the related functions of the terminal device 101, the source RAN node 102, or the target RAN node 103 in the embodiment of the present application can be implemented by one device, or by multiple devices, or by one or more devices in one device.
  • This function module is implemented, which is not specifically limited in the embodiment of the present application. It is understandable that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (for example, a cloud platform) Virtualization function.
  • FIG. 2 shows a schematic structural diagram of a switching device 200 provided by an embodiment of the application.
  • the switching device 200 includes one or more processors 201, a communication line 202, and at least one communication interface (in FIG. 2 it is only an example that includes a communication interface 204 and a processor 201 for illustration), optional
  • the memory 203 may also be included.
  • the processor 201 can be a central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of this application. Circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 202 may include a path for connecting different components.
  • the communication interface 204 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), and so on.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 204 may also be a transceiver circuit located in the processor 201 to implement signal input and signal output of the processor.
  • the memory 203 may be a device having a storage function.
  • it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage ( Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 202.
  • the memory can also be integrated with the processor.
  • the memory 203 is used to store computer execution instructions for executing the solution of the present application, and the processor 201 controls the execution.
  • the processor 201 is configured to execute computer-executable instructions stored in the memory 203, so as to implement the switching method provided in the embodiment of the present application.
  • the processor 201 may also perform processing-related functions in the switching method provided in the following embodiments of the present application, and the communication interface 204 is responsible for communicating with other devices or communication networks.
  • the communication interface 204 is responsible for communicating with other devices or communication networks.
  • the computer execution instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 2.
  • the switching apparatus 200 may include multiple processors, such as the processor 201 and the processor 206 in FIG. 2. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the switching apparatus 200 may further include an output device 205 and an input device 206.
  • the output device 205 communicates with the processor 201 and can display information in a variety of ways.
  • the aforementioned switching device 200 may be a general-purpose device or a special-purpose device.
  • the switching device 200 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal, an embedded device, or a device with a similar structure in FIG. 2.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the switching device 200.
  • Network slice remapping refers to the protocol data unit (PDU) session/quality of service flow (QoS flow)/data wireless performed on network slice #1 (slice#1)
  • the bearer data radio bearer, DRB
  • the bearer can be remapped to network slice #2 (slice#2). That is, the service of network slice #1 can be realized through network slice #2, which is equivalent to using the network resources of network slice #2 to realize the service of network slice #1.
  • the source RAN node supports network slice #1, however, the target RAN node may not support network slice #1, but supports network slice #2.
  • network slice remapping includes network slice remapping at PDU session granularity, network slice remapping at QoS flow granularity, and network slice remapping at DRB granularity.
  • the network slice remapping of the PDU session granularity means that the PDU session performed on the source network slice can be remapped to another network slice supported by the target RAN node, and the PDU session is continued by the remapped network slice
  • QoS flow Granular network slice remapping means that the QoS flow performed on the source network slice can be remapped to another network slice supported by the target RAN node, and the remapped network slice continues to execute the services in the QoS flow
  • DRB granularity Network slice remapping means that the DRB performed on the source network slice can be remapped to another network slice supported by the target RAN node, and the remapped network slice continues to execute the service carried on the DRB.
  • Network slicing rollback means that the terminal device, the source RAN node, and the target RAN node all support a specific network slice and know the identification and configuration of the specific network slice in advance.
  • the terminal device is handed over, it is in the source RAN node.
  • the PDU session/QoS flow/DRB on any network slice is transferred (also called fallback) to the specific network slice, that is, after the handover, the PDU session/QoS flow/DRB on any network slice of the terminal device passes through
  • the realization of the specific network slice of the target RAN node can also be considered as any network slice of the terminal device being remapped to the specific network slice.
  • the target RAN node can switch the PDU session/QoS on any network slice of the terminal device.
  • the flow/DRB is rolled back to the specific network slice, that is, the network resources of the specific network slice are used to realize the service of any network slice of the terminal device.
  • the specific network slice is called a default network slice, and the specific network slice may also have other names, which is not limited in this application. It should be understood that the default network slice may be determined by the network side and configured to the terminal device, may also be obtained through negotiation between the terminal device and the network side, or may be predefined by the standard.
  • network slice remapping is to map one network slice to another network slice
  • network slice fallback is to map one network slice to the default network slice. It is worth noting that when the other network slice is the same as the default network slice, network slice remapping is equivalent to network slice fallback.
  • the network slice identifier may be characterized by at least one of the following parameters:
  • Network slice type information can indicate enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine-type communications ( Network slicing types such as massive machine type communication, mMTC).
  • the network slice type information can also indicate the end-to-end network slice type, including the network slice type from the radio access network (RAN) to the core network (core network, CN), or it can refer to the RAN side Network slicing type, or CN-side network slicing type;
  • Service type information which is related to specific services, for example, the service type information can indicate service characteristics such as video service, car networking service, voice service, etc. or specific service information;
  • Tenant information which is used to instruct customer information for creating or renting the network slice
  • User group information which is used to indicate grouping information for grouping users according to a certain characteristic, such as user level
  • Slice group information used to indicate that according to a certain characteristic, for example, all network slices that can be accessed by the terminal device can be regarded as a slice group, or network slice groups can also be divided according to other standards;
  • Network slice instance information used to indicate the instance ID and characteristic information created for the network slice.
  • an ID can be assigned to the network slice instance to indicate the network slice instance, or it can be based on the network slice instance ID Map a new identifier to the network slice instance, and the receiver can identify the specific network slice instance indicated by the identifier according to the identifier;
  • a dedicated core network (DCN) identifier which is used to uniquely indicate a dedicated core network in an LTE system or an eLTE system, such as a dedicated core network for the Internet of Things.
  • the DCN identifier can be associated with the network
  • the slice identifier is mapped, and the network slice identifier can be mapped from the DCN identifier, and the DCN identifier can also be mapped through the network slice identifier.
  • FIG. 3 it is a schematic flowchart of a handover method provided by an embodiment of this application.
  • This process mainly involves network slice remapping or fallback based on the granularity of the PDU session switched by the Xn interface.
  • the method includes the following steps:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or, default network slice information.
  • the source RAN node and the target RAN node may obtain network slice remapping information, and/or default network slice information. In this way, during the terminal device handover process, the source RAN node does not need to re-send the network slice remapping information and/or the default network slice information to the target RAN node.
  • the target RAN node also does not need to re-receive network slice remapping information, and/or default network slice information.
  • the source RAN node receives a first message from a core network node or a network management system, where the first message includes network slice remapping information, and/or default network slice information.
  • the first message may include network slice remapping information corresponding to all source network slice identifiers in the coverage area of the RAN node, and/or default network slice information.
  • the network slice remapping information is the remapping information of the network slice supported by the source RAN node.
  • the network slice remapping information includes one or more source network slice identifiers, and a remappable network slice identifier corresponding to each source network slice identifier.
  • Network slice 1 Network slice 2
  • network slice 3 Network slice 4
  • Network slice 5 ... ...
  • Network slice N Network slice M1
  • network slice M2
  • the default network slice information includes the identifier of the default network slice.
  • the first message may be a next generation application protocol (NGAP) message.
  • NGAP next generation application protocol
  • the access and mobility management function (AMF) network element can inform the source RAN node and the target RAN node of the foregoing network slice remapping information and/or default network slice information through an NGAP message.
  • AMF access and mobility management function
  • the first message may also be an Xn interface application protocol (Xn application protocol, XnAP) message.
  • Xn application protocol XnAP
  • the RAN nodes exchange the foregoing network slice remapping information and/or default network slice information through XnAP messages.
  • the UE may also obtain network slice remapping information in advance, and/or default network slice information.
  • the AMF network element may inform the UE of the foregoing network slice remapping information and/or the default network slice information through a non-access straum (NAS) message.
  • NAS non-access straum
  • the source RAN node may also notify the UE of the above network slice remapping information through a broadcast message or a radio resource control (Radio Resource Control, RRC) message , And/or, the default network slice information.
  • RRC Radio Resource Control
  • the source RAN node sends a first handover message to the target RAN node, where the first handover message includes one or more source network slice identifiers, and whether one or more PDU sessions of each source network slice in the one or more source network slices An indication of supporting network slice remapping, and/or an indication of whether one or more PDU sessions of each source network slice in the one or more source network slices support network slice fallback.
  • the source RAN node determines the target RAN node among one or more RAN nodes according to the signal strength measurement report of one or more adjacent RAN nodes of the source RAN node reported by the UE.
  • the target RAN node receives the first handover message.
  • the first handover message may be a handover request (handover request) message.
  • the source RAN node Before the source RAN node sends the first handover message to the target RAN node, it may also receive a PDU session establishment request from the core network node.
  • the PDU session establishment request includes an indication of whether the established PDU session supports network slice remapping, and/or, An indication of whether the established PDU session supports network slice rollback. Therefore, the source RAN node can perform subsequent operations according to the foregoing instructions.
  • the PDU session performed on one or more source network slices of the source RAN node needs to continue on the side of the target RAN node.
  • the network slice supported by the target RAN node may be different from the source network slice.
  • the PDU session may not be performed on the source network slice, and needs to be remapped to a new network slice supported by the target RAN node or fall back to the default network slice.
  • the source RAN node needs to indicate whether the PDU session supports network slice remapping and/or whether it supports network slice fallback.
  • the first handover message includes one or more sources.
  • the slice identifier indicates whether the PDU session on the source network slice supports network slice fallback; or, the first handover message includes one or more source network slice identifiers, and PDUs of each network slice in the one or more source network slices The indication of whether the session supports network slice remapping and
  • the first handover message includes one or more source network slice identifiers and an indication that the PDU session of each source network slice in the one or more source network slices supports network slice remapping, that is, for Each source network slice identifier indicates that the PDU session on the source network slice supports network slice remapping; or, the first handover message includes one or more source network slice identifiers and each source network in the one or more source network slices
  • the sliced PDU session supports the indication of network slice fallback, that is, for each source network slice identifier, it indicates that the PDU session on the source network slice supports network slice fallback; or, the first handover message includes one or more source network slices Identifier, an indication that the PDU session of each source network slice in the one or more source network slices supports network slice remapping and an indication that the PDU session supports network slice fallback, that is, for each source network slice identifier, the source network slice is indicated The PDU session on the network supports network slice remapping and fallback.
  • the first handover message includes one Or multiple source network slice identifiers, the PDU session identifiers of multiple PDU sessions on each source network slice in the one or more source network slices, and whether the PDU sessions corresponding to some or all of the PDU session identifiers support network slice remapping Indication, that is, for each source network slice identifier, it indicates whether some or all of the multiple PDU sessions on the source network slice support network slice remapping; or, the first handover message includes one or more source network slice identifiers , The PDU session identifiers of multiple PDU sessions on each source network slice in the one or more source network slices and an indication of whether the PDU sessions corresponding to some or all of the PDU session identifiers support network slice fallback, that is, for each source network The
  • indicating whether a PDU session supports network slice remapping and/or network slice fallback usually includes the identification of the PDU session and whether the PDU session supports network slice remapping and/or network slice fallback Instructions.
  • indicating that a PDU session supports network slice remapping and/or supports network slice fallback usually includes the identifier of the PDU session and the indication information that the PDU session supports network slice remapping and/or supports network slice fallback. It should be understood that the indication information may be a 1-bit indication information.
  • the value of the bit when the value of the bit is 1, it indicates that network slice remapping and/or network slice fallback is supported, and when the value of the bit is 0 , Which means that network slice remapping and/or network slice fallback are not supported.
  • S103 The target RAN node performs admission control according to the first handover message.
  • the admission control uses To determine whether to perform network slice remapping for the one or more PDU sessions, and to determine the identifier of the network slice to which the remap is to be performed. Specifically, for any PDU session corresponding to the source network slice, if the first handover message includes an indication that the PDU session supports network slice remapping, the target RAN node corresponds to the source network slice identifier obtained in step S101.
  • the network slice remapping information determines to remap the PDU session on the source network slice to a new network slice. For example, a PDU session on the source network slice (slice#1) is switched to the target RAN node, however, the target RAN node does not support slice#1, and the network slice remapping information corresponding to slice#1 includes slice#2 and slice #3, the target RAN node can remap the PDU session to slice# according to the strategy (for example, based on the respective load conditions or performance indicators of slice#2 and slice#3 on the target RAN node, or the priority of the slice, etc.) 2 or slice#3; for another example, if the target RAN node supports slice#1, the target RAN node can use slice#1 to continue the PDU session.
  • the strategy for example, based on the respective load conditions or performance indicators of slice#2 and slice#3 on the target RAN node, or the priority of the slice, etc.
  • the target RAN node When the load of slice#1 of the target RAN node is too high, it can also set slice# 1 is remapped to slice#2 or slice#3. If the first handover message includes an indication that the PDU session does not support network slice remapping, and the target RAN node does not support slice#1, the target RAN node rejects the handover of the PDU session on the source network slice; or the first handover The message includes an indication that the PDU session does not support network slice remapping, and the target RAN node supports slice#1, then the target RAN node can use slice#1 to continue the PDU session.
  • the admission control is used To determine whether to roll back the one or more PDU sessions to the default network slice. Specifically, for any PDU session corresponding to the source network slice, if the first handover message includes an indication that the PDU session supports network slice fallback, the target RAN node determines to change the network slice according to the default network slice information obtained in step S101. The PDU session on the source network slice is rolled back to the default network slice. If the first handover message includes an indication that the PDU session does not support network slice rollback, the target RAN node rejects the handover of the PDU session on the source network slice.
  • the target RAN node can choose to remap the PDU session to a network slice included in the network slice remapping information in S101 according to the policy, or choose to remap the PDU session to a network slice included in the network slice remapping information in S101 The PDU session falls back to the default network slice.
  • the target RAN node sends a first response message to the source RAN node.
  • the source RAN node receives the first response message.
  • the first response message is a handover request acknowledgement (handover request acknowledgement) message.
  • the first handover message includes an indication that a PDU session of a source network slice supports network slice remapping, and the target RAN node determines through admission control to remap the PDU session, then the first response
  • the message includes the source network slice identifier, the PDU session identifier, and the network slice identifier to which the PDU session is remapped. That is, if the PDU session supports network slice remapping, the target RAN node determines the identity of the network slice to which the PDU session is remapped through the above admission control.
  • the target RAN node informs the source RAN node of the network slice to which the PDU session on the source network slice is remapped through the first response message.
  • the first handover message includes an indication of whether a PDU session of a source network slice supports network slice remapping. If the PDU session of the source network slice supports network slice remapping, and the target RAN node determines to remap the PDU session through admission control, the information included in the first response message is the same as the foregoing implementation. If the PDU session of the source network slice does not support network slice remapping, the target RAN node refuses to remap the PDU session, and the PDU session is interrupted, the first response message includes the source network slice identifier and the PDU session identifier The indication information that the target RAN node refuses to remap the PDU session.
  • the first handover message includes an indication that a PDU session of a source network slice supports network slice rollback, and the target RAN node determines that the PDU session is rolled back to the default through the above admission control.
  • Network slice the first response message includes the source network slice identifier, the PDU session identifier, and an indication of the PDU session to fall back to the default network slice, or the first response message includes the source network slice identifier, the PDU session identifier, and The default network slice ID.
  • the indication of the PDU session falling back to the default network slice may be 1-bit indication information.
  • the bit value is "1"
  • the source RAN node can know which network slice to fall back to; the bit value is When "0”, it means that the PDU session will not be rolled back, and the PDU session will end. That is, if the PDU session supports network slice rollback, the target RAN node determines through the above admission control that the PDU session is rolled back to the default network slice. If it is determined to roll back the PDU session to the default network slice, the target RAN node informs the source RAN node of the PDU session on the source network slice to roll back to the default network slice through a first response message.
  • the first handover message includes an indication whether a PDU session of a source network slice supports network slice fallback, if the PDU session of the source network slice supports network slice fallback, and the target RAN node It is determined through the above admission control that the PDU session is rolled back to the default network slice, and the first response message includes the same information as the above implementation; if the PDU session of the source network slice does not support network slice rollback, then The target RAN node refuses to roll back the PDU session, and the PDU session is interrupted, the first response message includes the source network slice identifier, the PDU session identifier, and indication information indicating that the target RAN node refuses to roll back the PDU session.
  • the first handover message includes an indication that a PDU session of a source network slice supports network slice remapping and an indication that network slice fallback is supported
  • the first response message includes the source network slice identifier, The PDU session identifier and the identifier of the network slice to which the PDU session is remapped, or, the first response message includes the source network slice identifier, the PDU session identifier, and an indication of the PDU session to fall back to the default network slice, or,
  • the first response message includes the source network slice identifier, the PDU session identifier, and the default network slice identifier.
  • the target RAN node determines through the above admission control whether to remap the PDU session to a new network slice or fall back to the default network slice .
  • the target RAN node informs the source RAN node of the identifier of the network slice to which the PDU session in the source network slice is remapped through the first response message, or instructs to roll back the PDU session to the default network slice.
  • the source RAN node After the source RAN node receives the identifier of the network slice to which the PDU session is remapped or the default network slice identifier, it compares the identifier of the source network slice to which the PDU session belongs with the identifier of the network slice to which the target RAN node is assigned to be remapped. , You can know that the PDU session needs to be remapped; or by comparing the source network slice ID to which the PDU session belongs to the default network slice ID indicated by the target RAN node, you can know that the PDU session needs to be rolled back.
  • the source RAN node may also receive an indication of whether the PDU session is rolled back to the default network slice. According to the indication, the source RAN node may know that the PDU session needs to be rolled back to the default network slice.
  • the source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the second message may be an RRC message.
  • the target RAN node may generate a container (container), and the container includes the content included in the foregoing first response message.
  • the target RAN node sends the container to the source RAN node.
  • the source RAN node does not parse the information in the container, but includes the container in the RRC message and forwards it to the terminal device.
  • the source RAN node after parsing the first response message, includes part or all of the information in the first response message in the RRC message generated by the source RAN node, and sends the RRC message to the terminal device .
  • the second message may also include the configuration parameters of the network slice to which at least one PDU session is remapped, or the configuration parameters of the default network slice, then the terminal device randomly accesses the target RAN node, Communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one PDU session is remapped, or communicate with the target RAN node according to the configuration parameters of the default network slice.
  • the target RAN node sends a path switching request to the core network node.
  • the path switching request includes the identifier of the network slice remapped by each PDU session in one or more PDU sessions, or an indication of whether each PDU session in the one or more PDU sessions performs network slice rollback.
  • the target RAN node indicates which PDU sessions need to be remapped or rolled back.
  • the core network node modifies the corresponding PDU session according to the path switching request. Specifically, the PDU session is modified to continue on the remapped network slice, or the PDU session is modified to continue on the default network slice. It should be understood that different network slices have different data transmission paths. Therefore, when the network slice is remapped or rolled back, the path of one or more PDU sessions in the network slice will change.
  • the core network node changes the path of a PDU session by modifying the context of the PDU session.
  • the core network node sends a path switching response to the target RAN node.
  • the path switching response includes one or more of the following information: PDU session identifiers of one or more PDU sessions that have succeeded in path switching, PDU session identifiers of one or more PDU sessions that have failed in path switching, and modified one or more The context of multiple PDU sessions.
  • the core network node sends the result of one or more PDU session path switching to the target RAN node.
  • the result of the one or more PDU session path switching includes one or more of the following information: PDU session identifiers of one or more PDU sessions that have succeeded in path switching, and PDU sessions of one or more PDU sessions that have failed in path switching Identify and modify the context of one or more PDU sessions.
  • the result of the PDU session modification is carried in the path switching response.
  • the source RAN node may support a separate architecture of CU and DU
  • the target RAN node may also support a separate architecture of CU and DU.
  • the CU of the source RAN node executes the foregoing acquisition of network slice remapping information, and /Or, the step of defaulting network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the information in the first response message to the DU of the source RAN node.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and remapping information according to the obtained network slice, and/or, Perform admission control by saving network slice information and some or all of the information in the received first handover message; and the step of sending a first response message to the CU of the source RAN node.
  • the source RAN node may not support the architecture of separating CU and DU, while the target RAN node supports the architecture of separating CU and DU.
  • the source RAN node performs the foregoing acquisition of network slice remapping information, and/or lacks The step of saving network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and remapping information according to the obtained network slice, and/or, The step of saving network slice information and some or all of the information in the received first handover message, performing admission control, and sending the first response message to the source RAN node.
  • the foregoing source RAN node may support a separate architecture of CU and DU, while the target RAN node may not support a separate architecture of CU and DU.
  • the CU of the source RAN node performs the foregoing acquisition of network slice remapping information, and/ Or, the step of defaulting network slice information, the step of sending the first handover message; the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the first response message to the DU of the source RAN node.
  • the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, and receiving the first handover message, according to the obtained network slice remapping information, and/or, the default network slice Information and the first handover message, perform admission control, and send the first response message to the CU of the source RAN node.
  • the handover message carries an indication of whether the PDU session supports network slice remapping, and/or whether the PDU session supports network slice fallback Indication, without the need to carry the entire network slice remapping information and/or default network slice information, which saves the signaling overhead in the handover interaction process.
  • the above switching method is based on Xn interface switching, and the switching method can also be based on NG interface switching.
  • FIG. 4 it is a schematic flowchart of another handover method provided by an embodiment of this application. This method mainly involves network slice remapping or fallback based on PDU session granularity of NG interface switching.
  • the method may include the following processes:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or, default network slice information.
  • the source RAN node sends a first handover message to the core network node, where the first handover message includes one or more source network slice identifiers, and whether one or more PDU sessions of each source network slice in the one or more source network slices An indication of supporting network slice remapping, and/or an indication of whether one or more PDU sessions of each source network slice in the one or more source network slices support network slice fallback.
  • the core network node receives the first handover message.
  • the first handover message may be a handover required (handover required) message.
  • the handover demand message is used to indicate that the source RAN node needs to perform handover.
  • the handover request message includes one or more source network slice identifiers, an indication of whether one or more PDU sessions of each source network slice in the one or more source network slices support network slice remapping, and/or the one or more source network slices An indication of whether one or more PDU sessions of each source network slice in each source network slice supports network slice rollback.
  • step S102 of the embodiment shown in FIG. 3.
  • the core network node sends a second handover message to the target RAN node.
  • the source RAN node determines the target RAN node among one or more RAN nodes according to the signal strength measurement report of one or more adjacent RAN nodes of the source RAN node reported by the UE.
  • the above-mentioned first handover message may also include the identification of the target RAN node.
  • the core network node sends a second handover message to the target RAN node.
  • the content of the second switching message includes part or all of the content of the first switching message.
  • the target RAN node receives the second handover message.
  • the second handover message may be a handover request (handover request) message.
  • the handover request message is used to indicate a request to switch the PDU session of the source RAN node to the target RAN node.
  • step S102 of the embodiment shown in FIG. 3.
  • S204 The target RAN node performs admission control according to the second handover message.
  • the admission control is used to determine whether to perform network slice remapping for one or more PDU sessions, and to determine the identity of the network slice to which the remap is to be performed; or, the admission control is used to determine whether to return one or more PDU sessions to Fall back to the default network slice.
  • S205 The target RAN node sends a second response message to the core network node.
  • the core network node receives the second response message.
  • the second response message is a response message to the second handover message.
  • the second response message may be a handover request acknowledgement (handover request acknowledge) message.
  • the handover request response message is a response to the aforementioned handover request message.
  • step S104 of the embodiment shown in FIG. 3.
  • the core network node sends a first response message to the source RAN node.
  • the content of the first response message may include part or all of the content of the second response message.
  • the second handover message may be a handover command (handover command).
  • the handover command is used to instruct the source RAN node to switch the PDU session to the target RAN node. Specifically, it is used to instruct the source RAN node to switch the PDU session to the remapped network slice or the default network slice.
  • step S104 for the specific implementation of this step, reference may be made to the related description of step S104 in the embodiment shown in FIG. 3.
  • S207 The source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the handover message carries an indication of whether the PDU session supports network slice remapping, and/or whether the PDU session supports network slice fallback Indication, without the need to carry the entire network slice remapping information and/or default network slice information, which saves the signaling overhead in the handover interaction process.
  • the foregoing embodiment describes the network slice remapping or fallback based on the granularity of the PDU session.
  • the network slice remapping or fallback based on the QoS flow granularity is described.
  • a QoS flow of the terminal device is also performed on a network slice. Therefore, when the terminal device performs RAN node handover, it may also involve network slice remapping or fallback with QoS flow granularity.
  • FIG. 5 it is a schematic flowchart of a handover method provided by an embodiment of this application.
  • This process mainly involves network slice remapping or fallback based on the QoS flow granularity of Xn interface switching.
  • the method includes the following steps:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or, default network slice information.
  • step S101 for the specific implementation of this step, reference may be made to the related description of step S101 in the embodiment shown in FIG. 3.
  • the source RAN node sends a first handover message to the target RAN node, where the first handover message includes one or more source network slice identifiers, and whether one or more QoS flows of each source network slice in the one or more source network slices An indication of supporting network slice remapping, and/or an indication of whether one or more QoS flows of each source network slice in the one or more source network slices support network slice fallback.
  • the target RAN node receives the first handover message.
  • the first switching message may be a switching request message.
  • the source RAN node Before the source RAN node sends the first handover message to the target RAN node, it may also receive a QoS flow establishment request from the core network node.
  • the QoS flow establishment request includes an indication of whether the established QoS flow supports network slice remapping, and/or, An indication of whether the established QoS flow supports network slicing rollback. Therefore, the source RAN node can perform subsequent operations according to the foregoing instructions.
  • the QoS flow performed on one or more source network slices of the source RAN node needs to continue on the side of the target RAN node.
  • the network slice supported by the target RAN node may be different from the source network slice.
  • the QoS flow may not be performed on the source network slice, and needs to be remapped to a new network slice supported by the target RAN node or fall back to the default network slice.
  • the source RAN node needs to indicate whether the QoS flow supports network slice remapping and/or whether it supports network slice fallback.
  • the first switching message includes one or more sources The network slice identifier and an indication of whether the QoS flow of each source network slice in the one or more source network slices supports network slice remapping, that is, for each source network slice identifier, it indicates whether the QoS flow on the source network slice supports network slice Remapping; or, the first handover message includes one or more source network slice identifiers and an indication of whether the QoS flow of each source network slice in the one or more source network slices supports network slice fallback, that is, for each source network The slice identifier indicates whether the QoS flow on the source network slice supports network slice fallback; or, the first handover message includes one or more source network slice identifiers, and the QoS of each network slice in the one or more source network slices An indication of whether the flow supports network slice re
  • the first handover message includes one or more source network slice identifiers and an indication that the QoS flow of each source network slice in the one or more source network slices supports network slice remapping, that is, for Each source network slice identifier indicates that the QoS flow on the source network slice supports network slice remapping; or, the first handover message includes one or more source network slice identifiers and each source network in the one or more source network slices
  • the sliced QoS flow supports the indication of network slice fallback, that is, for each source network slice identifier, it indicates that the QoS flow on the source network slice supports network slice fallback; or, the first handover message includes one or more source network slices Identifies, an indication that the QoS flow of each source network slice in the one or more source network slices supports network slice remapping and an indication that the QoS flow supports network slice fallback, that is, for each source network slice identifier, the source network slice is indicated
  • the above QoS flow supports network slicing re
  • the first handover message includes one Or multiple source network slice IDs, the QoS flow IDs of multiple QoS flows on each source network slice in the one or more source network slices, and whether the QoS flows corresponding to some or all of the QoS flow IDs support network slice remapping Indication, that is, for each source network slice identifier, indicate whether some or all of the QoS flows on the source network slice support network slice remapping; or, the first handover message includes one or more source network slice identifiers , The QoS flow identifiers of multiple QoS flows on each source network slice in the one or more source network slices and an indication of whether the QoS flows corresponding to some or all of the QoS flow identifiers support network slice fallback, that is, for each
  • indicating whether a QoS flow supports network slicing remapping and/or network slicing fallback usually including the identification of the QoS flow and whether the QoS flow supports network slicing remapping and/or network slicing fallback Instructions.
  • indicating that a QoS flow supports network slicing remapping and/or supporting network slicing fallback usually includes the identification of the QoS flow and the indication information that the QoS flow supports network slicing remapping and/or supporting network slicing fallback. It should be understood that the indication information may be a 1-bit indication information.
  • the value of the bit when the value of the bit is 1, it indicates that network slice remapping and/or network slice fallback is supported, and when the value of the bit is 0 , Which means that network slice remapping and/or network slice fallback are not supported.
  • the target RAN node performs admission control according to the first handover message.
  • the admission control is used To determine whether to perform network slice remapping for the one or more QoS flows, and to determine the identity of the network slice to which the remap is to be performed. Specifically, for any QoS flow corresponding to the source network slice, if the first handover message includes an indication that the QoS flow supports network slice remapping, the target RAN node corresponds to the source network slice identifier obtained in step S301.
  • the network slice remapping information determines to remap the QoS flow on the source network slice to a new network slice. For example, a QoS flow on the source network slice (slice#1) is switched to the target RAN node, however, the target RAN node does not support slice#1, and the network slice remapping information corresponding to slice#1 includes slice#2 and slice #3, the target RAN node can remap the QoS flow to slice# according to the strategy (for example, based on the respective load conditions or performance indicators of slice#2 and slice#3 on the target RAN node, or the priority of the slice, etc.) 2 or slice#3; for another example, if the target RAN node supports slice#1, the target RAN node can use slice#1 to continue the QoS flow.
  • the strategy for example, based on the respective load conditions or performance indicators of slice#2 and slice#3 on the target RAN node, or the priority of the slice, etc.
  • slice# 1 is remapped to slice#2 or slice#3. If the first handover message includes an indication that the QoS flow does not support network slice remapping, and the target RAN node does not support slice#1, the target RAN node rejects the handover of the QoS flow on the source network slice; or the first handover The message includes an indication that the QoS flow does not support network slice remapping, and the target RAN node supports slice#1, then the target RAN node can use slice#1 to continue the QoS flow.
  • the admission control is used To determine whether to fall back the one or more QoS flows to the default network slice. Specifically, for any QoS flow corresponding to the source network slice, if the first handover message includes an indication that the QoS flow supports network slicing fallback, the target RAN node determines to change the network slice according to the default network slice information obtained in step S301 The QoS flow on the source network slice falls back to the default network slice. If the first handover message includes an indication that the QoS flow does not support network slice fallback, the target RAN node rejects the handover of the QoS flow on the source network slice.
  • the target RAN node can choose to remap the QoS flow to a network slice included in the network slice remapping information in S301 according to the policy, or choose to remap The QoS flow falls back to the default network slice.
  • S304 The target RAN node sends a first response message to the source RAN node.
  • the source RAN node receives the first response message.
  • the first response message is a switching request response message.
  • the first handover message includes an indication that a QoS flow of a source network slice supports network slice remapping, and the target RAN node determines through admission control to remap the QoS flow, then the first response
  • the message includes the source network slice identification, the QoS flow identification, and the identification of the network slice to which the QoS flow is remapped. That is, if the QoS flow supports network slice remapping, the target RAN node determines the identity of the network slice to which the QoS flow is remapped through the foregoing admission control.
  • the target RAN node informs the source RAN node of the network slice to which the QoS flow on the source network slice is remapped through the first response message.
  • the first handover message includes an indication of whether a QoS flow of a source network slice supports network slice remapping. If the QoS flow of the source network slice supports network slice remapping, and the target RAN node determines to remap the QoS flow through admission control, the information included in the first response message is the same as the foregoing implementation. If the QoS flow of the source network slice does not support network slice remapping, the target RAN node refuses to remap the QoS flow, and the QoS flow is interrupted, the first response message includes the source network slice identification and the QoS flow identification And the indication information that the target RAN node refuses to remap the QoS flow.
  • the first handover message includes an indication that a QoS flow of a source network slice supports network slice fallback, and the target RAN node determines that the QoS flow falls back to the default through the above admission control.
  • Network slice the first response message includes the source network slice identifier, the QoS flow identifier, and an indication that the QoS flow falls back to the default network slice, or the first response message includes the source network slice identifier, the QoS flow identifier, and The default network slice ID.
  • the indication of the QoS flow falling back to the default network slice may be 1-bit indication information, for example, when the bit value is "1", it means that the QoS flow is falling back to the default network slice, because the source RAN node
  • the default network slice information is obtained in advance with the target RAN node. Therefore, when receiving the instruction of the QoS flow to fall back to the default network slice, the source RAN node can know which network slice to fall back to; the bit value is When "0", it means that the QoS flow will not be rolled back, and the QoS flow will end. That is, if the QoS flow supports network slice fallback, the target RAN node determines through the above admission control that the QoS flow falls back to the default network slice. If it is determined that the QoS flow falls back to the default network slice, the target RAN node informs the source RAN node of the QoS flow on the source network slice to fall back to the default network slice through a first response message.
  • the first handover message includes an indication of whether a QoS flow of a source network slice supports network slice fallback, if the QoS flow of the source network slice supports network slice fallback, and the target RAN node It is determined through the above admission control that the QoS flow is rolled back to the default network slice, and the first response message includes the same information as the above implementation; if the QoS flow of the source network slice does not support network slice rollback, then The target RAN node refuses to roll back the QoS flow, and the QoS flow is interrupted, then the first response message includes the source network slice identifier, the QoS flow identifier, and indication information indicating that the target RAN node refuses to roll back the QoS flow.
  • the first handover message includes an indication that a QoS flow of a source network slice supports network slice remapping and an indication that network slice fallback is supported
  • the first response message includes the source network slice identifier, The QoS flow identification and the identification of the network slice to which the QoS flow is remapped, or, the first response message includes the source network slice identification, the QoS flow identification, and an indication of the QoS flow to fall back to the default network slice, or,
  • the first response message includes the source network slice identifier, the QoS flow identifier, and the default network slice identifier.
  • the target RAN node determines through the above admission control whether to remap the QoS flow to a new network slice or fall back to the default network slice. .
  • the target RAN node informs the source RAN node of the identifier of the network slice to which the QoS flow in the source network slice is remapped through the first response message, or instructs the QoS flow to fall back to the default network slice.
  • the source RAN node After the source RAN node receives the identifier of the network slice to which the QoS flow is remapped or the default network slice identifier, it compares the identifier of the source network slice to which the QoS flow belongs with the identifier of the network slice to which the target RAN node is assigned to be remapped. , You can know that the QoS flow needs to be remapped; or by comparing the source network slice identifier to which the QoS flow belongs and the default network slice identifier indicated by the target RAN node, you can know that the QoS flow needs to be rolled back.
  • the source RAN node may also receive an indication of whether the QoS flow falls back to the default network slice. According to the indication, the source RAN node may know that the QoS flow needs to fall back to the default network slice.
  • S305 The source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the second message may be an RRC message.
  • a container may be generated by the target RAN node, and the container includes the content included in the foregoing first response message.
  • the target RAN node sends the container to the source RAN node.
  • the source RAN node does not parse the information in the container, but includes the container in the RRC message and forwards it to the terminal device.
  • the source RAN node after parsing the first response message, includes part or all of the information in the first response message in the RRC message generated by the source RAN node, and sends the RRC message to the terminal device .
  • the second message may also include the configuration parameters of the network slice to which at least one PDU session is remapped, or the configuration parameters of the default network slice, then the terminal device randomly accesses the target RAN node, Communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one PDU session is remapped, or communicate with the target RAN node according to the configuration parameters of the default network slice.
  • S306 The target RAN node sends a path switching request to the core network node.
  • the path switching request includes the identifier of the network slice to which each QoS flow in the one or more QoS flows is remapped, or an indication of whether each QoS flow in the one or more QoS flows performs network slicing rollback.
  • the target RAN node indicates which QoS flows need to be remapped or rolled back.
  • the core network node modifies the corresponding QoS flow according to the path switching request. Specifically, the QoS flow is modified to continue on the remapped network slice, or the QoS flow is modified to continue on the default network slice. It should be understood that different network slices have different data transmission paths. Therefore, when the network slice is remapped or rolled back, the path of one or more QoS flows in the network slice will change.
  • the core network node changes the path of a QoS flow by modifying the context of the QoS flow.
  • the core network node sends a path switching response to the target RAN node.
  • the path switching response includes one or more of the following information: the QoS flow identification of one or more QoS flows that have succeeded in path switching, the QoS flow identification of one or more QoS flows that have failed in path switching, and one or more modified QoS flow identifications.
  • the context of multiple QoS flows includes one or more of the following information: the QoS flow identification of one or more QoS flows that have succeeded in path switching, the QoS flow identification of one or more QoS flows that have failed in path switching, and one or more modified QoS flow identifications.
  • the core network node sends the result of one or more QoS flow path switching to the target RAN node.
  • the result of the one or more QoS flow path switching includes one or more of the following information: the QoS flow identification of one or more QoS flows that have succeeded in path switching, and the QoS flow of one or more QoS flows that have failed in path switching. Identify and modify the context of one or more QoS flows. The result of the QoS flow modification is carried in the path switching response.
  • the source RAN node may support a separate architecture of CU and DU
  • the target RAN node may also support a separate architecture of CU and DU.
  • the CU of the source RAN node executes the foregoing acquisition of network slice remapping information, and /Or, the step of defaulting network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the information in the first response message to the DU of the source RAN node.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and remapping information according to the obtained network slice, and/or, Perform admission control by saving network slice information and some or all of the information in the received first handover message; and the step of sending a first response message to the CU of the source RAN node.
  • the source RAN node may not support the architecture of separating CU and DU, while the target RAN node supports the architecture of separating CU and DU.
  • the source RAN node performs the foregoing acquisition of network slice remapping information, and/or lacks The step of saving network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and remapping information according to the obtained network slice, and/or, The step of saving network slice information and some or all of the information in the received first handover message, performing admission control, and sending the first response message to the source RAN node.
  • the foregoing source RAN node may support a separate architecture of CU and DU, while the target RAN node may not support a separate architecture of CU and DU.
  • the CU of the source RAN node performs the foregoing acquisition of network slice remapping information, and/ Or, the step of defaulting network slice information, the step of sending the first handover message; the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the first response message to the DU of the source RAN node.
  • the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, and receiving the first handover message, according to the obtained network slice remapping information, and/or, the default network slice Information and the first handover message, perform admission control, and send the first response message to the CU of the source RAN node.
  • the handover message carries an indication of whether the QoS flow supports network slice remapping, and/or whether the QoS flow supports network slice fallback Indication, without the need to carry the entire network slice remapping information and/or default network slice information, which saves the signaling overhead in the handover interaction process.
  • the above switching method is based on Xn interface switching, and the switching method can also be based on NG interface switching.
  • FIG. 6 a schematic flowchart of another handover method provided by an embodiment of this application.
  • the method mainly involves network slice remapping or fallback based on the QoS flow granularity of NG interface switching.
  • the method may include the following processes:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or default network slice information.
  • step S101 for the specific implementation of this step, reference may be made to the related description of step S101 in the embodiment shown in FIG. 3.
  • the source RAN node sends a first handover message to the core network node, where the first handover message includes one or more source network slice identifiers, and whether one or more QoS flows of each source network slice in the one or more source network slices An indication of supporting network slice remapping, and/or an indication of whether one or more QoS flows of each source network slice in the one or more source network slices support network slice fallback.
  • the core network node receives the first handover message.
  • the first handover message may be a handover demand message.
  • the handover demand message is used to indicate that the source RAN node needs to perform handover.
  • the handover request message includes one or more source network slice identifiers, an indication of whether one or more QoS flows of each source network slice in the one or more source network slices support network slice remapping, and/or the one or more source network slices An indication of whether one or more QoS flows of each source network slice in each source network slice support network slice fallback.
  • step S302 of the embodiment shown in FIG. 5 For the specific implementation of this step, reference may be made to the related description in step S302 of the embodiment shown in FIG. 5.
  • S403 The core network node sends a second handover message to the target RAN node.
  • the source RAN node determines the target RAN node among one or more RAN nodes according to the signal strength measurement report of one or more adjacent RAN nodes of the source RAN node reported by the UE.
  • the above-mentioned first handover message may also include the identification of the target RAN node.
  • the core network node sends a second handover message to the target RAN node.
  • the content of the second switching message includes part or all of the content of the first switching message.
  • the target RAN node receives the second handover message.
  • the second handover message may be a handover request message.
  • the handover request message is used to indicate a request to switch the QoS flow of the source RAN node to the target RAN node.
  • step S302 of the embodiment shown in FIG. 5 For the specific implementation of this step, reference may be made to the related description in step S302 of the embodiment shown in FIG. 5.
  • S404 The target RAN node performs admission control according to the second handover message.
  • the admission control is used for the QoS flow to determine whether to perform network slice remapping for one or more QoS flows, and to determine the identity of the network slice to which the QoS flow is remapped; or, the admission control is used for the QoS flow to determine whether to remap one or more QoS flows. Or multiple QoS flows fall back to the default network slice.
  • step S303 For the specific implementation of this step, reference may be made to the related description of step S303 in the embodiment shown in FIG. 5.
  • S405 The target RAN node sends a second response message to the core network node.
  • the core network node receives the second response message.
  • the second response message is a response message to the second handover message.
  • the second response message may be a handover request response message.
  • the handover request response message is a response to the aforementioned handover request message.
  • the core network node sends a first response message to the source RAN node.
  • the content of the first response message may include part or all of the content of the second response message.
  • the second handover message may be a handover command.
  • the handover command is used to instruct the source RAN node to switch the QoS flow to the target RAN node. Specifically, it is used to instruct the source RAN node to switch the QoS flow to the remapped network slice or the default network slice.
  • step S304 for the specific implementation of this step, reference may be made to the related description of step S304 in the embodiment shown in FIG. 5.
  • S407 The source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the handover message carries an indication of whether the QoS flow supports network slicing remapping, and/or whether the QoS flow supports network slicing fallback Indication, without the need to carry the entire network slice remapping information and/or default network slice information, which saves the signaling overhead in the handover interaction process.
  • the foregoing embodiments describe network slice remapping or fallback based on QoS flow granularity, and then the network slice remapping or fallback based on DRB granularity is described.
  • different DRBs are used on the air interface to carry the transmission of data with different QoS characteristics.
  • a DRB uses a certain air interface resource, and the air interface resource corresponding to a DRB of the terminal device also belongs to a network slice. Therefore, when the terminal device performs RAN node switching, it may also involve DRB granular network slice remapping or fallback, that is, after switching, the air interface resources corresponding to the DRB belong to the remapped network slice or the default network slice.
  • one or more QoS flows are mapped to one DRB, that is, one DRB carries the one or more QoS flows, and the mapping relationship between DRB and QoS flows remains unchanged during the handover process.
  • FIG. 7 it is a schematic flowchart of a handover method provided by an embodiment of this application.
  • This process mainly involves network slice remapping or fallback based on the DRB granularity of Xn interface switching.
  • the method includes the following steps:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or default network slice information.
  • step S101 in the embodiment shown in FIG. 3 or step S301 in the embodiment shown in FIG. 5.
  • the source RAN node sends a first handover message to the target RAN node, where the first handover message includes one or more source network slice identifiers, and whether one or more DRBs of each source network slice in the one or more source network slices support An indication of network slice remapping, and/or an indication of whether one or more DRBs of each source network slice in the one or more source network slices support network slice rollback.
  • the target RAN node receives the first handover message.
  • the first switching message may be a switching request message.
  • the DRB of one or more source network slices belonging to the source RAN node needs to be switched to the target RAN node side.
  • the network slice supported by the target RAN node may be different from the source network slice.
  • the air interface resources corresponding to the DRB may no longer belong to the source network slice, but belong to the new network slice or the default network slice supported by the remapped target RAN node.
  • the source RAN node For each DRB belonging to the source network slice, the source RAN node needs to indicate whether the DRB supports network slice remapping and/or whether it supports network slice fallback. It is worth noting that, in the application embodiment, the air interface resource corresponding to a DRB belongs to a network slice, and it can also be said that the DRB belongs to the network slice.
  • the first handover message includes one or more source network slices. Identifies and indicates whether the DRB belonging to each source network slice in the one or more source network slices supports network slice remapping, that is, for each source network slice identifier, indicates whether the DRB belonging to the source network slice supports network slice remapping
  • the first handover message includes one or more source network slice identifiers and an indication of whether the DRB belonging to each source network slice in the one or more source network slices supports network slice fallback, that is, for each source network slice identifier , Indicating whether the DRB belonging to the source network slice supports network slice fallback; or, the first handover message includes one or more source network slice identifiers, which belong to the DRB of each source network slice in the one or more source network slices The indication of whether network slice remapping is supported and
  • the first handover message includes one or more source network slice identifiers and an indication that the DRB belonging to each source network slice in the one or more source network slices supports network slice remapping, that is, for The identifier of each source network slice indicates that the DRB belonging to the source network slice supports network slice remapping; or, the first handover message includes one or more source network slice identifiers and each source belonging to the one or more source network slices
  • the DRB of the network slice supports the indication of network slice fallback, that is, for each source network slice identifier, it indicates that the DRB belonging to the source network slice supports network slice fallback; or, the first handover message includes one or more source network slices Identifier, an indication that the DRB belonging to each source network slice in the one or more source network slices supports network slice remapping and an indication that the DRB supports network slice fallback, that is, for each source network slice identifier, it indicates that it belongs to the source network slice
  • the DRB on the network supports network slicing re
  • the first handover message includes one or more A source network slice identifier, which belongs to the DRB identifiers of multiple DRBs on each source network slice in the one or more source network slices, and an indication of whether the DRB corresponding to some or all of the DRB identifiers supports network slice remapping, that is, for each The source network slice identifier indicates whether some or all of the DRBs belonging to the source network slice support network slice remapping; or, the first handover message includes one or more source network slice identifiers, which belong to the one or more DRBs.
  • DRB ID of a DRB and an indication of whether the DRB corresponding to some or all of the DRB ID supports network slice remapping and an indication of whether the DRB corresponding to some or all of the DRB ID supports network slice fallback, that is, for each source network slice ID , Indicating whether some or all of the DRBs belonging to each DRB on the source network slice support network slice remapping and fallback.
  • indicating whether a DRB supports network slice remapping and/or network slice fallback usually includes the identification of the DRB and whether the DRB supports network slice remapping and/or network slice fallback indication information.
  • instructing a DRB to support network slice remapping and/or support network slice fallback usually includes the identification of the DRB and the indication information that the DRB supports network slice remapping and/or supports network slice fallback.
  • the indication information may be a 1-bit indication information.
  • the value of the bit when the value of the bit is 1, it indicates that network slice remapping and/or network slice fallback is supported, and when the value of the bit is 0 , Which means that network slice remapping and/or network slice fallback are not supported.
  • S503 The target RAN node performs admission control according to the first handover message.
  • the admission control is used for It is determined whether to perform network slice remapping on the one or more DRBs, and the identifier of the network slice to which the remap is to be determined. Specifically, for any DRB belonging to the source network slice, if the first handover message includes an indication that the DRB supports network slice remapping, the target RAN node will remap the network slice according to the source network slice identifier obtained in step S501.
  • the mapping information is determined to remap the DRB belonging to the source network slice to a new network slice. For example, a DRB belonging to the source network slice (slice#1) is switched to the target RAN node, however, the target RAN node does not support slice#1, and the network slice remapping information corresponding to slice#1 includes slice#2 and slice# 3.
  • the target RAN node can remap the DRB to slice#2 or slice#2 according to the strategy (for example, based on the respective load conditions or performance indicators of slice#2 and slice#3 on the target RAN node, or the priority of the slice, etc.) slice#3; For another example, if the target RAN node supports slice#1, the DRB can belong to slice#1 of the target RAN node. When the load of slice#1 of the target RAN node is too high, slice#1 can also be remapped to slice#2 or slice#3.
  • the target RAN node rejects the handover of the DRB belonging to the source network slice; or the first handover message Including the indication that the DRB does not support network slice remapping and the target RAN node supports slice#1, then the DRB may belong to slice#1 of the target RAN node.
  • the admission control is used for Determine whether to fall back the one or more DRBs to the default network slice.
  • the target RAN node determines that it will belong to the source according to the default network slice information obtained in step S501. The DRB of the network slicing is rolled back to the default network slicing. If the first handover message includes an indication that the DRB does not support network slice fallback, the target RAN node rejects the handover of the DRB belonging to the source network slice.
  • the target RAN node can choose to remap the DRB to a network slice included in the network slice remapping information in S501 according to the policy, or choose to roll back the DRB To the default network slice.
  • the above admission control process also needs to consider whether the target RAN node accepts the lossless data forwarding requirement of the DRB, that is, the mapping relationship between the DRB and the QoS flow cannot be changed.
  • S504 The target RAN node sends a first response message to the source RAN node.
  • the source RAN node receives the first response message.
  • the first response message is a switching request response message.
  • the first handover message includes an indication that a DRB belonging to a source network slice supports network slice remapping, and the target RAN node determines to remap the DRB through admission control, then the first response message Including the source network slice identifier, the DRB identifier, and the identifier of the network slice to which the DRB is remapped. That is, if the DRB supports network slice remapping, the target RAN node determines the identity of the network slice to which the DRB is remapped through the foregoing admission control. The target RAN node informs the source RAN node of the network slice to which the DRB on the source network slice is remapped through the first response message.
  • the first handover message includes an indication whether a DRB belonging to a source network slice supports network slice remapping. If the DRB belonging to the source network slice supports network slice remapping, and the target RAN node determines to remap the DRB through admission control, the information included in the first response message is the same as the foregoing implementation. If the DRB belonging to the source network slice does not support network slice remapping, the target RAN node refuses to remap the DRB, and the DRB ends, and the first response message includes the source network slice identifier, the DRB identifier, and the target RAN The indication information that the node refuses to remap the DRB.
  • the first handover message includes an indication that a DRB belonging to a source network slice supports network slice fallback, and the target RAN node determines that the DRB falls back to the default network through the above admission control.
  • Slice the first response message includes the source network slice identifier, the DRB identifier, and the indication of the DRB to fall back to the default network slice, or the first response message includes the source network slice identifier, the DRB identifier, and the default network slice Logo.
  • the indication of the DRB falling back to the default network slice may be 1-bit indication information.
  • the bit value is "1"
  • the source RAN node can know which network slice to fall back to; the bit value is "0"
  • the target RAN node determines that the DRB is rolled back to the default network slice through the above admission control. If it is determined to fall back to the default network slice, the target RAN node informs the source RAN node of the DRB on the source network slice to fall back to the default network slice through a first response message.
  • the first handover message includes an indication whether a DRB belonging to a source network slice supports network slice fallback, if the DRB belonging to the source network slice supports network slice fallback, and the target RAN node It is determined through the above admission control that the DRB is rolled back to the default network slice, and the first response message includes the same information as the above implementation; if the DRB of the source network slice does not support network slice rollback, the target RAN If the node refuses to roll back the DRB, and the DRB is interrupted, the first response message includes the source network slice identifier, the DRB identifier, and the indication information indicating that the target RAN node refuses to roll back the DRB.
  • the first handover message includes an indication that a DRB belonging to a source network slice supports network slice remapping and an indication that network slice fallback is supported
  • the first response message includes the source network slice identifier, The DRB identifier and the identifier of the network slice to which the DRB is remapped, or, the first response message includes the source network slice identifier, the DRB identifier, and an indication of the DRB to fall back to the default network slice, or the first response message Including the source network slice identifier, the DRB identifier, and the default network slice identifier.
  • the target RAN node determines through the above admission control whether to remap the DRB to a new network slice or fall back to the default network slice.
  • the target RAN node informs the source RAN node of the identifier of the network slice to which the DRB in the source network slice is remapped through the first response message, or instructs the DRB to fall back to the default network slice.
  • the source RAN node After the source RAN node receives the identifier of the network slice to which the DRB is remapped or the default network slice identifier, it compares the identifier of the source network slice to which the DRB belongs with the identifier of the network slice to which the target RAN node is assigned to be remapped, that is, It can be known that the DRB needs to be remapped; or by comparing the source network slice identifier to which the DRB belongs to the default network slice identifier indicated by the target RAN node, it can be known that the DRB needs to be rolled back.
  • the source RAN node may also receive an indication of whether the DRB is to fall back to the default network slice. According to the indication, the source RAN node may know that the DRB needs to fall back to the default network slice.
  • S505 The source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the second message may be an RRC message.
  • a container may be generated by the target RAN node, and the container includes the content included in the foregoing first response message.
  • the target RAN node sends the container to the source RAN node.
  • the source RAN node does not parse the information in the container, but includes the container in the RRC message and forwards it to the terminal device.
  • the source RAN node after parsing the first response message, includes part or all of the information in the first response message in the RRC message generated by the source RAN node, and sends the RRC message to the terminal device .
  • the second message may also include the configuration parameters of the network slice to which at least one PDU session is remapped, or the configuration parameters of the default network slice, then the terminal device randomly accesses the target RAN node, Communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one PDU session is remapped, or communicate with the target RAN node according to the configuration parameters of the default network slice.
  • the source RAN node may support a separate architecture of CU and DU
  • the target RAN node may also support a separate architecture of CU and DU.
  • the CU of the source RAN node executes the foregoing acquisition of network slice remapping information, and /Or, the step of defaulting network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the information in the first response message to the DU of the source RAN node.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and remapping information according to the obtained network slice, and/or, Perform admission control by saving network slice information and some or all of the information in the received first handover message; and the step of sending a first response message to the CU of the source RAN node.
  • the source RAN node may not support the architecture of separating CU and DU, while the target RAN node supports the architecture of separating CU and DU.
  • the source RAN node performs the foregoing acquisition of network slice remapping information, and/or lacks The step of saving network slice information, the step of sending the first handover message, the step of receiving the first response message, and the step of sending the second message.
  • the CU of the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, receiving the first handover message, and DU remapping information according to the obtained network slice, and/or, The step of performing admission control on the default network slice information and some or all of the information in the received first handover message, and sending the first response message to the source RAN node.
  • the foregoing source RAN node may support a separate architecture of CU and DU, while the target RAN node may not support a separate architecture of CU and DU.
  • the CU of the source RAN node performs the foregoing acquisition of network slice remapping information, and/ Or, the step of defaulting network slice information, the step of sending the first handover message; the step of receiving the first response message, and the step of sending the second message through the DU. After receiving the first response message, the CU forwards part or all of the first response message to the DU of the source RAN node.
  • the target RAN node executes the steps of obtaining network slice remapping information, and/or the default network slice information, and receiving the first handover message, according to the obtained network slice remapping information, and/or, the default network slice Information and the first handover message, perform admission control, and send the first response message to the CU of the source RAN node.
  • step S601 after the CU obtains the network slice remapping information sent by the core network node or other RAN nodes, and/or the default network slice information, it sends the obtained network slice remapping information to the DU through an F1AP message, and / Or default network slice information. Then, in step S602, after receiving the first handover message sent by the source RAN node, the CU sends a UE context establishment request to the DU.
  • the context establishment request includes the source network slice identifier and an indication of whether the DRB supports network slice remapping. And/or an indication of whether the DRB supports network slicing rollback.
  • the DU performs admission control according to the foregoing instructions, as well as network slice remapping information and/or default network slice information.
  • the DU sends a UE context establishment response to the CU.
  • the UE context establishment response includes the identifier of the network slice to which the DRB is remapped, or an indication of whether the DRB has fallen back to the default network slice.
  • the handover message carries an indication whether the DRB supports network slice remapping, and/or whether the DRB supports network slice fallback, There is no need to carry the entire network slice remapping information and/or the default network slice information, which saves the signaling overhead in the handover interaction process.
  • the above switching method is based on Xn interface switching, and the switching method can also be based on NG interface switching.
  • FIG. 9 it is a schematic flowchart of another handover method provided by an embodiment of this application.
  • This method mainly involves network slice remapping or fallback based on DRB granularity of NG interface switching.
  • the method may include the following processes:
  • the source RAN node and the target RAN node obtain network slice remapping information, and/or default network slice information.
  • step S501 For the specific implementation of this step, reference may be made to the related description of step S501 in the embodiment shown in FIG. 7.
  • the source RAN node sends a first handover message to the core network node, where the first handover message includes one or more source network slice identifiers, and whether one or more DRBs of each source network slice in the one or more source network slices support An indication of network slice remapping, and/or an indication of whether one or more DRBs of each source network slice in the one or more source network slices support network slice fallback.
  • the core network node receives the first handover message.
  • the first handover message may be a handover demand message.
  • the handover demand message is used to indicate that the source RAN node needs to perform handover.
  • the handover request message includes one or more source network slice identifiers, an indication of whether one or more DRBs of each source network slice in the one or more source network slices support network slice remapping, and/or the one or more source network slices An indication of whether one or more DRBs of each source network slice in the source network slice support network slice fallback.
  • S703 The core network node sends a second handover message to the target RAN node.
  • the source RAN node determines the target RAN node among one or more RAN nodes according to the signal strength measurement report of one or more adjacent RAN nodes of the source RAN node reported by the UE.
  • the above-mentioned first handover message may also include the identification of the target RAN node.
  • the core network node sends a second handover message to the target RAN node.
  • the content of the second switching message includes part or all of the content of the first switching message.
  • the target RAN node receives the second handover message.
  • the second handover message may be a handover request message.
  • the handover request message is used to indicate a request to handover the DRB of the source RAN node to the target RAN node.
  • step S702 of the embodiment shown in FIG. 7.
  • S704 The target RAN node performs admission control according to the second handover message.
  • the admission control is used by the DRB to determine whether to perform network slice remapping on one or more DRBs, and to determine the identity of the network slice to which the DRB is remapped; or, the admission control is used for the DRB to determine whether to remap one or more DRBs Fall back to the default network slice.
  • step S703 For the specific implementation of this step, reference may be made to the related description of step S703 in the embodiment shown in FIG. 7.
  • S705 The target RAN node sends a second response message to the core network node.
  • the core network node receives the second response message.
  • the second response message is a response message to the second handover message.
  • the second response message may be a handover request response message.
  • the handover request response message is a response to the aforementioned handover request message.
  • S706 The core network node sends a first response message to the source RAN node.
  • the content of the first response message may include part or all of the content of the second response message.
  • the second handover message may be a handover command.
  • the handover command is used to instruct the source RAN node to switch the DRB to the target RAN node. Specifically, it is used to instruct the source RAN node to switch the DRB to the remapped network slice or the default network slice.
  • step S704 For the specific implementation of this step, reference may be made to the related description of step S704 in the embodiment shown in FIG. 7.
  • S707 The source RAN node sends a second message to the terminal device.
  • the terminal device receives the second message.
  • the handover message carries an indication of whether DRB supports network slice remapping, and/or an indication of whether DRB supports network slice fallback, There is no need to carry the entire network slice remapping information and/or the default network slice information, which saves the signaling overhead in the handover interaction process.
  • an embodiment of the present application also provides a switching device.
  • the device 300 includes a transceiving unit 301 and a processing unit 302, and the processing unit 302 is coupled to the transceiving unit 301.
  • the apparatus 300 may be the terminal device in the embodiment shown in FIG. 3 to FIG. 4. in:
  • the transceiver unit 301 is configured to receive the second message from the source RAN node
  • the second message includes at least one source network slice identifier, at least one protocol data unit PDU session identifier of each source network slice in the at least one source network slice, and some or all of the PDU sessions in the at least one PDU session
  • the second message is a radio resource control RRC message, and when the at least one PDU session is remapped or rolled back, the second message further includes the at least one PDU session The configuration parameters of the network slice to which the remap is to be remapped, or the configuration parameters of the default network slice;
  • the processing unit 302 is configured to randomly access the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one PDU session is remapped; or
  • the processing unit 302 is configured to randomly access the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the default network slice.
  • transceiver unit 301 For the specific implementation of the transceiver unit 301 and the processing unit 302, reference may be made to the relevant description of the terminal device in the embodiments shown in FIGS. 3 to 4.
  • the apparatus 300 may be the terminal device in the embodiment shown in FIG. 5 to FIG. 6. in:
  • the transceiver unit 301 is configured to receive the second message from the source RAN node
  • the second message includes at least one source network slice identifier, the identifier of at least one QoS flow of each source network slice in the at least one source network slice, and some or all of the QoS flows in the at least one QoS flow are remapped to Or at least one source network slice identifier, the identifier of at least one QoS flow of each source network slice in the at least one source network slice, whether some or all of the QoS flows in the at least one QoS flow fall back to An indication of the default network slicing.
  • the second message is a radio resource control RRC message.
  • the second message further includes the at least one QoS flow.
  • the processing unit 302 is configured to randomly access to the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one QoS flow is remapped; or
  • the processing unit 302 is configured to randomly access the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the default network slice.
  • transceiver unit 301 For the specific implementation of the transceiver unit 301 and the processing unit 302, reference may be made to the relevant description of the terminal device in the embodiments shown in FIG. 5 to FIG. 6.
  • the apparatus 300 may be the terminal device in the embodiments shown in FIGS. 7-9. in:
  • the transceiver unit 301 is configured to receive a second message from a source RAN node
  • the second message includes at least one source network slice identifier, the identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and the network to which some or all of the DRBs in the at least one DRB are remapped
  • the second message is a radio resource control RRC message.
  • the second message further includes the at least one DRB remap The configuration parameters of the obtained network slice, or the configuration parameters of the default network slice;
  • the processing unit 302 is configured to randomly access to the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the network slice to which the at least one DRB is remapped; or
  • the processing unit 302 is configured to randomly access the target RAN node through the transceiver unit 301, and communicate with the target RAN node according to the configuration parameters of the default network slice.
  • transceiver unit 301 For the specific implementation of the transceiver unit 301 and the processing unit 302, reference may be made to the relevant description of the terminal device in the embodiments shown in FIGS. 7-9.
  • the apparatus 300 may also be the source RAN node in the embodiments shown in FIGS. 3 to 4. in:
  • the processing unit 302 is configured to generate a first handover message, where the first handover message includes: at least one source network slice identifier, and the first handover message further includes at least one of the following: each source in the at least one source network slice An indication of whether at least one protocol data unit PDU session of a network slice supports network slice remapping, and an indication of whether at least one PDU session of each source network slice in the at least one source network slice supports network slice fallback;
  • the transceiver unit 301 is configured to send the first handover message to a first network node
  • the transceiver unit 301 is further configured to receive a first response message from the first network node;
  • the first response message includes at least one source network slice identifier, and each source in the at least one source network slice The identifier of at least one PDU session of the network slice, and the identifier of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped; or
  • the first response message includes at least one source network slice identifier, and each source network slice in the at least one source network slice An identifier of at least one PDU session in the at least one PDU session, an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice; or
  • the first response message includes at least one source network slice Identification, the identification of at least one PDU session of each source network slice in the at least one source network slice, the identification of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped, or at least one source network slice An identifier, an identifier of at least one PDU session of each source network slice in the at least one source network slice, and an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier, and A remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice;
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the transceiver unit 301 is further configured to receive a PDU session establishment request from a core network node, where the PDU session establishment request includes an indication of whether the established PDU session supports network slice remapping, and/ Or, an indication of whether the established PDU session supports network slice fallback.
  • the first network node is a target RAN node
  • the transceiver unit 301 is further configured to send a handover request message to the target RAN node
  • the transceiver unit 301 is further configured to receive a handover request response message from the target RAN node; or
  • the first network node is a core network node, and the transceiver unit 301 is further configured to send a handover request message to the core network node;
  • the transceiver unit 301 is further configured to receive a handover command from the core network node.
  • the transceiving unit 301 is further configured to send a second message to the terminal device;
  • the second message includes at least one source network slice identifier, the identifier of at least one PDU session of each source network slice in the at least one source network slice, and some or all of the PDU sessions in the at least one PDU session are remapped to The ID of the network slice; or
  • the second message includes at least one source network slice identifier, at least one PDU session identifier of each source network slice in the at least one source network slice, and whether some or all of the PDU sessions in the at least one PDU session are rolled back to all An indication of the default network slicing; or
  • the second message includes at least one source network slice identifier, the identifier of at least one PDU session of each source network slice in the at least one source network slice, and the network to which some or all of the PDU sessions in the at least one source network slice are remapped
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the source RAN node in the embodiments shown in FIGS. 3 to 4.
  • the apparatus 300 may also be the source RAN node in the embodiment shown in FIG. 5 to FIG. 6. in:
  • the processing unit 302 is configured to generate a first handover message, where the first handover message includes: at least one source network slice identifier, and the first handover message further includes at least one of the following: An indication of whether at least one QoS flow of each source network slice supports network slice remapping, and an indication of whether at least one QoS flow of each source network slice in the at least one source network slice supports network slice fallback;
  • the transceiver unit 301 is configured to send the first handover message to a first network node
  • the transceiver unit 301 is further configured to receive a first response message from the first network node;
  • the first response message includes at least one source network slice identifier, and each source in the at least one source network slice The identifier of at least one QoS flow of the network slice, and the identifier of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped; or
  • the first response message includes at least one source network slice identifier, and each source network slice in the at least one source network slice An identifier of at least one QoS flow in the at least one QoS flow, an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice; or
  • the first response message includes at least one source network slice Identification, the identification of at least one QoS flow of each source network slice in the at least one source network slice, the identification of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped, or at least one source network slice An identifier, an identifier of at least one QoS flow of each source network slice in the at least one source network slice, and an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or, default network slice information, where the network slice remapping information includes at least one source network slice identifier, and A remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice;
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the transceiver unit 301 is further configured to receive a QoS flow establishment request from a core network node, where the QoS flow establishment request includes an indication of whether the established QoS flow supports network slice remapping, and/ Or, an indication of whether the established QoS flow supports network slice fallback.
  • the first network node is a target RAN node
  • the transceiver unit 301 is further configured to send a handover request message to the target RAN node
  • the transceiver unit 301 is further configured to receive a handover request response message from the target RAN node; or
  • the first network node is a core network node, and the transceiver unit 301 is further configured to send a handover demand message to the core network node;
  • the transceiver unit 301 is further configured to receive a handover command from the core network node.
  • the transceiving unit 301 is further configured to send a second message to the terminal device;
  • the second message includes at least one source network slice identifier, the identifier of at least one QoS flow of each source network slice in the at least one source network slice, and some or all of the QoS flows in the at least one QoS flow are remapped to The ID of the network slice; or
  • the second message includes at least one source network slice identifier, the identifier of at least one QoS flow of each source network slice in the at least one source network slice, and whether some or all of the QoS flows in the at least one QoS flow fall back to all An indication of the default network slicing; or
  • the second message includes at least one source network slice identifier, the identifier of at least one QoS flow of each source network slice in the at least one source network slice, and the network to which some or all of the QoS flows in the at least one QoS flow are remapped
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the related description of the source RAN node in the embodiments shown in FIGS. 5-6.
  • the apparatus 300 may also be the source RAN node in the embodiments shown in FIGS. 7-9. in:
  • the processing unit 302 is configured to generate a first handover message, where the first handover message includes: at least one source network slice identifier, and the first handover message further includes at least one of the following: belonging to the at least one source network slice An indication of whether at least one DRB of each source network slice in the at least one source network slice supports network slice remapping, and an indication of whether at least one DRB of each source network slice in the at least one source network slice supports network slice fallback;
  • the transceiver unit 301 is configured to send the first handover message to a first network node
  • the transceiver unit 301 is further configured to receive a first response message from the first network node;
  • the first response message includes at least one source network slice identifier, which belongs to each source in the at least one source network slice.
  • the first response message includes at least one source network slice identifier, which belongs to each source network slice in the at least one source network slice An identifier of at least one DRB in the at least one DRB, an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice; or
  • the first response message includes at least one source network slice identifier, The identity of at least one DRB belonging to each source network slice in the at least one source network slice, the identity of the network slice to which some or all of the DRBs in the at least one DRB are remapped, or at least one source network slice identity belongs to all The identification of at least one DRB of each source network slice in the at least one source network slice, and an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier, and A remappable network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice;
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the first network node is a target RAN node
  • the transceiver unit 301 is further configured to send a handover request message to the target RAN node
  • the transceiver unit 301 is further configured to receive a handover request response message from the target RAN node; or
  • the first network node is a core network node, and the transceiver unit 301 is further configured to send a handover demand message to the core network node;
  • the transceiver unit 301 is further configured to receive a handover command from the core network node.
  • the transceiving unit 301 is further configured to send a second message to the terminal device;
  • the second message includes at least one source network slice identifier, the identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and the network to which some or all of the DRBs in the at least one DRB are remapped The identification of the slice; or
  • the second message includes at least one source network slice identifier, the identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and whether some or all of the DRBs in the at least one DRB fall back to the defect Independent network slicing instructions; or
  • the second message includes at least one source network slice identifier, the identifier of at least one DRB belonging to each source network slice in the at least one source network slice, and the identifier of the network slice to which some or all of the DRBs in the at least one DRB are remapped.
  • ID or, at least one source network slice ID, the ID of at least one DRB belonging to each source network slice in the at least one source network slice, whether some or all of the DRBs in the at least one DRB fall back to the default network Instructions for slicing.
  • transceiver unit 301 and processing unit 302 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the related description of the source RAN node in the embodiments shown in FIGS. 7-9.
  • the apparatus 300 may be the target RAN node in the embodiment shown in FIG. 3 to FIG. 4. in:
  • the transceiver unit 301 is configured to receive a second handover message from a second network node, where the second handover message includes: at least one source network slice identifier, and the second handover message further includes at least one of the following: the at least one An indication of whether at least one protocol data unit PDU session of each source network slice in the source network slice supports network slice remapping, and an indication of whether at least one PDU session of each source network slice in the at least one source network slice supports network slice fallback ;
  • the processing unit 302 is configured to perform admission control according to the second handover message, where the admission control is used to determine whether to perform network slice remapping on the at least one PDU session, and to determine the network slice to which the remap is Identification; or, the admission control is used to determine whether to roll back the at least one PDU session to the default network slice;
  • the transceiver unit 301 is further configured to send a second response message to the second network node;
  • the second response message when the second handover message includes an indication of whether the PDU session supports network slice remapping, includes at least one source network slice identifier, and each source in the at least one source network slice The identifier of at least one PDU session of the network slice, and the identifier of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped; or
  • the second response message includes at least one source network slice identifier, and each source network slice in the at least one source network slice An identifier of at least one PDU session in the at least one PDU session, an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice; or
  • the second response message includes at least one source network slice Identification, the identification of at least one PDU session of each source network slice in the at least one source network slice, the identification of the network slice to which part or all of the PDU sessions in the at least one PDU session are remapped, or at least one source network slice An identifier, an identifier of at least one PDU session of each source network slice in the at least one source network slice, and an indication of whether some or all of the PDU sessions in the at least one PDU session fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier, and The remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the second network node is a source RAN node
  • the transceiver unit 301 is further configured to receive a handover request message from the source RAN node
  • the transceiver unit 301 is further configured to send a handover request response message to the source RAN node; or
  • the second network node is a core network node, and the transceiver unit 301 is further configured to receive the handover request message from the core network node;
  • the transceiver unit 301 is further configured to send the handover request response message to the core network node.
  • the transceiver unit 301 is further configured to send a path switch request to the core network node, where the path switch request includes at least one PDU session in the network slice identifier to which each PDU session belongs, or ,
  • the path switching request includes an indication of whether each PDU session in the at least one PDU session performs network slicing rollback;
  • the transceiver unit 301 is further configured to receive a path switch response from the core network node, where the path switch response includes one or more of the following information: the PDU session identifier of at least one PDU session for which the path switch is successful, The PDU session identifier of the at least one PDU session for which path switching fails, and the modified context of the at least one PDU session.
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the target RAN node in the embodiments shown in FIGS. 3 to 4.
  • the apparatus 300 may be the target RAN node in the embodiment shown in FIG. 5 to FIG. 6. in:
  • the transceiver unit 301 is configured to receive a second handover message from a second network node, where the second handover message includes: at least one source network slice identifier, and the second handover message further includes at least one of the following: the at least one An indication of whether at least one QoS flow of each source network slice in the source network slice supports network slice remapping, and an indication of whether at least one QoS flow of each source network slice in the at least one source network slice supports network slice fallback;
  • the processing unit 302 is configured to perform admission control according to the second handover message, where the admission control is used to determine whether to perform network slice remapping on the at least one QoS flow, and determine the network slice to which the remap is Identification; or, the admission control is used to determine whether to roll back the at least one QoS flow to the default network slice;
  • the transceiver unit 301 is further configured to send a second response message to the second network node;
  • the second response message when the second handover message includes an indication of whether the QoS flow supports network slice remapping, the second response message includes at least one source network slice identifier, and each source in the at least one source network slice The identifier of at least one QoS flow of the network slice, and the identifier of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped; or
  • the second response message includes at least one source network slice identifier, and each source network slice in the at least one source network slice An identifier of at least one QoS flow in the at least one QoS flow, an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice; or
  • the second response message includes at least one source network slice Identification, the identification of at least one QoS flow of each source network slice in the at least one source network slice, the identification of the network slice to which part or all of the QoS flows in the at least one QoS flow are remapped, or at least one source network slice An identifier, an identifier of at least one QoS flow of each source network slice in the at least one source network slice, and an indication of whether some or all of the QoS flows in the at least one QoS flow fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier, and The remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the second network node is a source RAN node
  • the transceiver unit 301 is further configured to receive a handover request message from the source RAN node
  • the transceiver unit 301 is further configured to send a handover request response message to the source RAN node; or
  • the second network node is a core network node, and the transceiver unit 301 is further configured to receive the handover request message from the core network node;
  • the transceiver unit 301 is further configured to send the handover request response message to the core network node.
  • the transceiver unit 301 is further configured to send a path switch request to the core network node, where the path switch request includes the network slice identifier to which each QoS flow in at least one QoS flow belongs, or ,
  • the path switching request includes an indication of whether each QoS flow in the at least one QoS flow performs network slicing rollback;
  • the transceiving unit 301 is further configured to receive a path switching response from the core network node, the path switching response including one or more of the following information: the QoS flow identifier of at least one QoS flow for which the path switching is successful, The QoS flow identifier of the at least one QoS flow for which path switching fails, and the modified context of the at least one QoS flow.
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the target RAN node in the embodiments shown in FIG. 5 to FIG. 6.
  • the apparatus 300 may be the target RAN node in the embodiment shown in Figs. 7-9. in:
  • the transceiver unit 301 is configured to receive a second handover message from a second network node, where the second handover message includes: at least one source network slice identifier, and the second handover message further includes at least one of the following: belonging to the at least one An indication of whether at least one DRB of each source network slice in one source network slice supports network slice remapping, and an indication of whether at least one DRB of each source network slice in the at least one source network slice supports network slice fallback;
  • the processing unit 302 is configured to perform admission control according to the second handover message, where the admission control is used to determine whether to perform network slice remapping on the at least one DRB, and determine the identity of the network slice to which the remap is performed Or, the admission control is used to determine whether to roll back the at least one DRB to the default network slice;
  • the transceiver unit 301 is further configured to send a second response message to the second network node;
  • the second response message includes at least one source network slice identifier, which belongs to each source in the at least one source network slice.
  • the second response message includes at least one source network slice identifier, which belongs to each source network slice in the at least one source network slice An identifier of at least one DRB in the at least one DRB, an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice; or
  • the second response message includes at least one source network slice identifier, The identity of at least one DRB belonging to each source network slice in the at least one source network slice, the identity of the network slice to which some or all of the DRBs in the at least one DRB are remapped, or at least one source network slice identity belongs to all The identification of at least one DRB of each source network slice in the at least one source network slice, and an indication of whether some or all of the DRBs in the at least one DRB fall back to the default network slice.
  • the transceiver unit 301 is further configured to obtain network slice remapping information, and/or default network slice information, where the network slice remapping information includes at least one source network slice identifier, and The remapped network slice identifier corresponding to each source network slice identifier, and the default network slice information includes the identifier of the default network slice.
  • the transceiver unit 301 is further configured to receive a first message, where the first message includes the network slice remapping information, and/or the default network slice information.
  • the second network node is a source RAN node
  • the transceiver unit 301 is further configured to receive a handover request message from the source RAN node
  • the transceiver unit 301 is further configured to send a handover request response message to the source RAN node; or
  • the second network node is a core network node, and the transceiver unit 301 is further configured to receive the handover request message from the core network node;
  • the transceiver unit 301 is further configured to send the handover request response message to the core network node.
  • transceiver unit 301 and processing unit 302 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the target RAN node in the embodiments shown in FIGS. 7-9.
  • the device 300 may also be a core network node in the embodiments shown in FIGS. 3 to 4. in:
  • the transceiver unit 301 is configured to receive a path switch request from a target RAN node, where the path switch request includes the network slice identifier to which each PDU session in at least one PDU session belongs, or the path switch request includes the path switch request in the at least one PDU session. Indication of whether each PDU session performs network slicing rollback;
  • the processing unit 302 is configured to modify each PDU session in the at least one PDU session according to the path switching request;
  • the transceiver unit 301 is further configured to send a path switch response to the target RAN node, where the path switch response includes one or more of the following information: the PDU session identifier and path of at least one PDU session for which the path switch is successful The PDU session identifier of the at least one PDU session for which the handover fails, and the modified context of the at least one PDU session.
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the core network node in the embodiments shown in FIG. 3 to FIG. 4.
  • the device 300 may also be a core network node in the embodiments shown in FIG. 5 to FIG. 6. in:
  • the transceiver unit 301 is configured to receive a path switching request from a target RAN node, where the path switching request includes the network slice identifier to which each QoS flow in at least one QoS flow belongs, or the path switching request includes the at least one QoS flow Indication of whether each QoS flow performs network slicing rollback;
  • the processing unit 302 is configured to modify each QoS flow in the at least one QoS flow according to the path switching request;
  • the transceiving unit 301 is further configured to send a path switching response to the target RAN node, the path switching response including one or more of the following information: the QoS flow identifier and path of at least one QoS flow for which the path switching is successful The QoS flow identifier of the at least one QoS flow for which the handover fails, and the modified context of the at least one QoS flow.
  • transceiver unit 301 For the specific implementation of the foregoing transceiver unit 301 and processing unit 302, reference may be made to the relevant description of the core network node in the embodiments shown in FIG. 5 to FIG. 6.
  • FIG. 11 is a structural diagram of possible product forms of the switching device according to an embodiment of the application.
  • the switching device is a terminal device.
  • the switching device may be an information transmission device, and the information transmission device includes a transceiver 403; the transceiver 403 is used to support the information transmission device to perform step S105 of the embodiment shown in FIG. 3, or The transceiver 403 is used to support the information transmission device to perform step S207 of the embodiment shown in FIG. 4, or the transceiver 403 is used to support the information transmission device to perform step S305 of the embodiment shown in FIG. 5, or The transceiver 403 is used to support the information transmission device to perform step S407 in the embodiment shown in FIG. 6, or the transceiver 403 is used to support the information transmission device to perform step S505 in the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission device to perform step S707 of the embodiment shown in FIG. 9, or the transceiver 403 is also used to support the information transmission device to randomly access the target RAN node according to at least one PDU
  • the configuration parameters of the network slice to which the session is remapped or the configuration parameters of the default network slice communicate with the target RAN node.
  • the information transmission device may further include a memory 401 and a processor 402.
  • the switching device may be an information transmission single board.
  • the information transmission single board includes a transceiver 403; the transceiver 403 is used to support the information transmission single board to execute Step S105, or, the transceiver 403 is used to support the information transmission board to perform step S207 of the embodiment shown in FIG. 4, or the transceiver 403 is used to support the information transmission board to perform the implementation shown in FIG. 5
  • the transceiver 403 is used to support the information transmission single board to perform step S407 of the embodiment shown in FIG. 6, or the transceiver 403 is used to support the information transmission single board to perform the step S407 shown in FIG.
  • Step S505 of the illustrated embodiment, or, the transceiver 403 is used to support the information transmission board to perform step S707 of the embodiment shown in FIG. 9, or the transceiver 403 is also used to support the random connection of the information transmission board.
  • Enter the target RAN node and communicate with the target RAN node according to the configuration parameters of the network slice to which at least one PDU session is remapped or the configuration parameters of the default network slice.
  • the information transmission single board may further include a memory 401 and a processor 402.
  • the switching device is also implemented by a general-purpose processor, which is commonly known as a chip.
  • the general-purpose processor includes: a processing circuit 402 and a communication interface 403; optionally, the general-purpose processor may also include a storage medium 401.
  • the communication device can also be implemented using the following: one or more field programmable gate arrays (FPGA), programmable logic devices (programmable logic device, PLD), control Any combination of devices, state machines, gate logic, discrete hardware components, any other suitable circuits, or circuits capable of performing the various functions described throughout this application.
  • FPGA field programmable gate arrays
  • PLD programmable logic device
  • the switching device is a source RAN node.
  • the switching device may be an information transmission device, and the information transmission device includes a transceiver 403; the transceiver 403 is used to support the information transmission device to perform steps S101 and S101 in the embodiment shown in FIG. 3 S102, S104, and S105; or, the transceiver 403 is used to support the information transmission device to perform steps S201, S202, S206, and S207 of the embodiment shown in FIG. 4; or, the transceiver 403 is used to support information transmission
  • the device executes steps S301, S302, S304, and S305 in the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission device to execute steps S401, S402, S406, and S407 in the embodiment shown in FIG. 6; Or, the transceiver 403 is used to support the information transmission device to perform steps S501, S502, S504, and S505 in the embodiment shown in FIG. 7; or, the transceiver 403 is used to support the information transmission device to perform steps S501, S502, S504, and S505 in the embodiment shown in FIG. Steps S701, S702, S706, and S707 of the embodiment are shown.
  • the information transmission device may further include a memory 401 and a processor 402.
  • the switching device may be an information transmission single board, and the information transmission single board includes a transceiver 403; the transceiver 403 is used to support the information transmission single board to perform Steps S101, S102, S104 and S105 of; or, the transceiver 403 is used to support the information transmission single board to perform steps S201, S202, S206 and S207 of the embodiment shown in FIG. 4; or, the transceiver 403, It is used to support the information transmission single board to perform steps S301, S302, S304 and S305 in the embodiment shown in FIG. 5; or, the transceiver 403 is used to support the information transmission single board to perform step S401 in the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission single board to perform steps S501, S502, S504, and S505 in the embodiment shown in FIG. 7; or, the transceiver 403 is used to The support information transmission single board executes steps S701, S702, S706, and S707 of the embodiment shown in FIG. 9.
  • the information transmission single board may further include a memory 401 and a processor 402.
  • the switching device is also implemented by a general-purpose processor, which is commonly known as a chip.
  • the general-purpose processor includes: a processing circuit 402 and a communication interface 403; optionally, the general-purpose processor may also include a storage medium 401.
  • the communication device can also be implemented using the following: one or more FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or capable of executing this Any combination of circuits with various functions described throughout the application.
  • the handover device is a target RAN node.
  • the switching device may be an information transmission device, which includes a processor 402 and a transceiver 403; the processor 402 is used to control and manage the actions of the information transmission device, for example, Used to support the information transmission device to perform step S103 of the embodiment shown in FIG. 3, or to support the information transmission device to perform step S204 of the embodiment shown in FIG. 4, or to support the information transmission device to perform the implementation shown in FIG. 5
  • Step S303 of the example is used to support the information transmission device to perform step S404 of the embodiment shown in FIG. 6, or is used to support the information transmission device to perform step S503 of the embodiment shown in FIG. 7, or, to support information transmission
  • the device performs step S704 of the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission device to perform steps S101, S102, S104, S106, and S107 of the embodiment shown in FIG. 3, or, the transceiver 403 is used to support the information transmission device to perform steps S201, S203, and S205 of the embodiment shown in FIG. 4, or the transceiver 403 is used to support the information transmission device to perform steps S301, S301, and S301 of the embodiment shown in FIG. 5 S302, S304, S306, and S307, or, the transceiver 403 is used to support the information transmission device to perform steps S401, S403, S405 in the embodiment shown in FIG.
  • the transceiver 403 is used to support information
  • the transmission device executes steps S501, S502, and S504 of the embodiment shown in FIG. 7, or the transceiver 403 is used to support the information transmission device to execute steps S701, S703, and S705 of the embodiment shown in FIG. 9.
  • the information transmission device may further include a memory 401.
  • the switching device may be an information transmission board.
  • the information transmission board includes a processor 402 and a transceiver 403; the processor 402 is used to perform actions on the information transmission board.
  • Control management for example, for supporting the information transmission board to perform step S103 of the embodiment shown in FIG. 3, or for supporting the information transmission board to perform step S204 of the embodiment shown in FIG. 4, or for supporting information transmission
  • the single board executes step S303 of the embodiment shown in FIG. 5, or, is used to support the information transmission single board to execute step S404 of the embodiment shown in FIG. 6, or, is used to support the information transmission single board to execute the steps of the embodiment shown in FIG. Step S503, or, is used to support the information transmission single board to perform step S704 of the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission device to perform steps S101, S102, and S104 of the embodiment shown in FIG. 3 , S106 and S107, or, the transceiver 403 is used to support the information transmission device to perform steps S201, S203, S205 of the embodiment shown in FIG. 4, or the transceiver 403 is used to support the information transmission device to perform Perform steps S301, S302, S304, S306, and S307 of the embodiment shown in FIG. 5, or, the transceiver 403 is used to support the information transmission device to perform steps S401, S403, S405 of the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission device to perform steps S501, S502, and S504 of the embodiment shown in FIG. 7, or the transceiver 403 is used to support the information transmission device to perform the implementation shown in FIG. 9 Steps S701, S703, and S705 of the example.
  • the information transmission single board may further include a memory 401.
  • the switching device is also implemented by a general-purpose processor, which is commonly known as a chip.
  • the general-purpose processor includes: a processing circuit 402 and a communication interface 403; optionally, the general-purpose processor may also include a storage medium 401.
  • the communication device can also be implemented using the following: one or more FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or capable of executing this Any combination of circuits with various functions described throughout the application.
  • the switching device is a core network node.
  • the switching device may be an information transmission device, and the information transmission device includes a transceiver 403; the transceiver 403 is used to support the information transmission device to perform steps S106 and S107 of the embodiment shown in FIG. 3 , Or, the transceiver 403 is used to support the information transmission device to perform steps S202, S203, S205 and S206 of the embodiment shown in FIG. 4, or the transceiver 403 is used to support the information transmission device to perform the steps S202, S203, S205 and S206 in the Steps S306 and S307 of the illustrated embodiment, or, the transceiver 403 is used to support the information transmission device to perform steps S402, S403, S405, and S406 of the embodiment shown in FIG. 6, or, the transceiver 403 is used for The supporting information transmission device executes steps S702, S703, S705, and S706 of the embodiment shown in FIG. 9.
  • the information transmission device may further include a memory 401 and a processor 402.
  • the switching device may be an information transmission single board.
  • the information transmission single board includes a transceiver 403; the transceiver 403 is used to support the information transmission single board to execute Steps S106 and S107, or, the transceiver 403 is used to support the information transmission single board to perform steps S202, S203, S205 and S206 of the embodiment shown in FIG. 4, or, the transceiver 403 is used to support information transmission
  • the board executes steps S306 and S307 of the embodiment shown in FIG. 5, or, the transceiver 403 is used to support the information transmission board to execute steps S402, S403, S405, and S406 of the embodiment shown in FIG.
  • the transceiver 403 is used to support the information transmission single board to execute steps S702, S703, S705, and S706 of the embodiment shown in FIG. 9.
  • the information transmission single board may further include a memory 401 and a processor 402.
  • the switching device is also implemented by a general-purpose processor, which is commonly known as a chip.
  • the general-purpose processor includes: a processing circuit 402 and a communication interface 403; optionally, the general-purpose processor may also include a storage medium 401.
  • the communication device can also be implemented using one or more FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or capable of executing this Any combination of circuits with various functions described throughout the application.
  • the aforementioned processor 402 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the bus 404 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect standard
  • EISA extended industry standard architecture
  • an embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled with the memory through the interface, and when the at least one processor executes the computer program or instruction in the memory At this time, the method in any of the foregoing method embodiments is executed.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which are not specifically limited in the embodiment of the present application.
  • an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a switching device, the switching device executes the method in any of the foregoing method embodiments.
  • the embodiment of the present application further provides a computer program product containing instructions, which when executed by a computer, cause the switching device to execute the method in any of the foregoing method embodiments.
  • an embodiment of the present application further provides a communication system, and the communication system includes the above-mentioned switching device.
  • the methods and/or steps implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used for the terminal device; the methods and/or steps implemented by the source RAN node It can also be implemented by a component (such as a chip or circuit) that can be used in the source RAN node; the method and/or steps implemented by the target RAN node can also be implemented by a component (such as a chip or circuit) that can be used in the target RAN node.
  • an embodiment of the present application also provides a switching device, which is used to implement the above-mentioned various methods.
  • the switching apparatus may be the terminal equipment in the foregoing method embodiment, or an apparatus including the foregoing terminal equipment, or a component that can be used for terminal equipment; or, the switching apparatus may be the source RAN node in the foregoing method embodiment, or may include
  • the foregoing device of the source RAN node may be a component that can be used for the source RAN node; or, the switching device may be the target RAN node in the foregoing method embodiment, or a device including the foregoing target RAN node, or may be used for the target RAN node Parts.
  • the switching device includes hardware structures and/or software modules corresponding to each function.
  • 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 as going beyond the scope of this application.
  • the embodiments of the present application may divide the switching device into functional modules according to the foregoing method embodiments.
  • 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.
  • one or more of the above units or units can be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built in a system on chip (system on chip, SoC) or ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • the processor's internal processing is used to execute software instructions for calculations or processing, and may further include necessary hardware accelerators, such as field programmable gate arrays (FPGA) and programmable logic devices (programmable logic devices). device, PLD), or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate arrays
  • programmable logic devices programmable logic devices
  • device, PLD programmable logic circuit that implements dedicated logic operations.
  • the hardware can be a central processing unit (CPU), a microprocessor, a digital signal processing (DSP) chip, and a microcontroller unit (MCU) ), artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or any one or any combination of non-integrated discrete devices, which can run the necessary software or do not rely on software to perform the above Method flow.
  • CPU central processing unit
  • DSP digital signal processing
  • MCU microcontroller unit
  • artificial intelligence processor ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or any one or any combination of non-integrated discrete devices, which can run the necessary software or do not rely on software to perform the above Method flow.
  • words such as “first” and “second” are used to distinguish the same items or similar items with substantially the same function and effect.
  • the words “first”, “second” and the like do not limit the quantity and order of execution, and the words “first” and “second” do not limit the difference.
  • 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.
  • words such as “exemplary” or “for example” are used to present related concepts in a specific manner to facilitate understanding.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or include one or more data storage devices such as servers, data centers, etc. that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Abstract

本申请公开了一种切换方法及装置。在切换过程中，源RAN节点在切换消息中包括PDU会话是否支持网络切片重映射的指示，和/或，PDU会话是否支持网络切片回退的指示。目标RAN节点根据上述指示进行准入控制，并通知源RAN节点PDU会话重映射到的网络切片的标识，或，PDU会话是否回退到缺省网络切片的指示。源RAN节点向终端设备转发上述通知。由此，节省了切换交互过程中的信令开销。

Description

一种切换方法及装置
本申请要求于2020年05月30日提交中国国家知识产权局、申请号为202010480982.4、发明名称为“一种切换方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种切换方法及装置。
背景技术
随着移动通信技术的发展，各类新业务以及应用场景不断涌现，不同业务对网络功能、连接性能及安全性等方面的需求存在很大的差别。如果利用单一网络去承载这些业务，将很难同时满足高带宽、低时延、高可靠性等需求。而如果为每种业务单独新建网络又会带来巨大的成本。第五代(5 th generation，5G)无线通信技术已是目前业界的热点，在满足上述需求时，要求5G在具备灵活、可拓展性的同时，能够满足不同的业务需求。为此，5G通过端到端的网络切片(network slice)为用户提供定制化的网络服务。具体地，通过对网络资源的灵活分配、按需组网，5G在同一套物理设施上虚拟出多个具有不同特点且相互隔离的逻辑网络，来针对性地为用户提供服务。
在传统的蜂窝网络中，处于连接态的终端设备从源无线接入网(radio access network，RAN)节点移动到目标RAN节点时，其通信业务也需要切换到目标RAN节点。在5G网络中，由于不同设备商的RAN节点的功能可能存在差异性，或者运营商对网络切片的部署具有区域性的策略，使得不同RAN节点对于网络切片的支持能力是不同的，因此其覆盖范围内所支持的网络切片服务也会不相同。例如，一个RAN节点所支持的网络切片和另一个RAN节点所支持的网络切片可能不同。在这种情况下，当终端设备移动时，其在源RAN节点通信所连接的网络切片有可能在目标RAN节点并不支持。在终端设备的切换过程中，如何在保证业务连续性的同时，以较小的信令开销实现终端设备的切换，是本申请需要解决的问题。
发明内容
本申请实施例提供了一种切换方法及装置，以解决切换交互流程信令开销较大的问题。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种切换方法，所述方法包括：终端设备接收来自源无线接入网RAN节点的第二消息；其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。在该方面中，终端设备接收会话重映射到的网络切片的标识，或，会话是否回退到缺省网络切片的指示，可以在后续 会话建立过程中，在重映射的网络切片或缺省网络切片上进行数据传输，提高了通信的可靠性。
在一种可能的实现中，所述第二消息为无线资源控制RRC消息，在所述至少一个PDU会话进行重映射或回退的情况下，所述第二消息还包括所述至少一个PDU会话重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；所述方法还包括：所述终端设备随机接入到目标RAN节点，根据根据所述至少一个PDU会话重映射到的网络切片的配置参数与所述目标RAN节点进行通信；或所述终端设备随机接入到所述目标RAN节点，根据所述缺省网络切片的配置参数与所述目标RAN节点进行通信。
第二方面，提供了一种切换方法，所述方法包括：终端设备接收来自源RAN节点的第二消息；其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示。在该方面中，终端设备接收QoS流重映射到的网络切片的标识，或，QoS流是否回退到缺省网络切片的指示，可以在后续QoS流建立过程中，在重映射的网络切片或缺省网络切片上进行数据传输，提高了通信的可靠性。
在一种可能的实现中，所述第二消息为RRC消息，在所述至少一个QoS流进行重映射或回退的情况下，所述第二消息还包括所述至少一个QoS流重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；所述方法还包括：所述终端设备随机接入到目标RAN节点，根据根据所述至少一个QoS流重映射到的网络切片的配置参数与所述目标RAN节点进行通信；或所述终端设备随机接入到所述目标RAN节点，根据所述缺省网络切片的配置参数与所述目标RAN节点进行通信。
第三方面，提供了一种切换方法，所述方法包括：终端设备接收来自源RAN节点的第二消息；其中，所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示。在该方面中，终端设备接收DRB重映射到的网络切片的标识，或，DRB是否回退到缺省网络切片的指示，可以在后续DRB建立过程中，在重映射的网络切片或缺省网络切片上对应的资源上进行数据传输，提高了通信的可靠性。
在一种可能的实现中，所述第二消息为RRC消息，在所述至少一个DRB进行重映射或回退的情况下，所述第二消息还包括所述至少一个DRB重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；所述方法还包括：所述终端设备随机接入到目标RAN节点，根据根据所述至少一个DRB重映射到的网络切片的配置参数与所述目标RAN节点进行通信；或所述终端设备随机接入到所述目标RAN节点，根据所述缺省网络切片的配置参数与所述目标RAN节点进行通信。
第四方面，提供了一种切换方法，所述方法包括：源无线接入网RAN节点向第一网络节点发送第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切 换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；以及所述源RAN节点接收来自所述第一网络节点的第一响应消息；其中，在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或在所述第一切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示；或在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。在该方面中，在切换过程中，在切换消息中携带会话是否支持网络切片重映射的指示，和/或，会话是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在一种可能的实现中，所述方法还包括：所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。在该实现中，各个RAN节点预先获取网络切片重映射信息，和/或，缺省网络切片信息，源RAN节点无需在每个终端设备的切换过程中，再携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在又一种可能的实现中，所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述源RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。在该实现中，该网络切片重映射信息或缺省网络切片信息若是与终端设备无关的，则在切换前，核心网可以通过单独的消息预先告知源接入网节点网络切片重映射信息，和/或，缺省网络切片信息。
在一种可能的实现中，所述源RAN节点向第一网络节点发送第一切换消息之前，所述方法还包括：所述源RAN节点接收来自核心网节点的所述至少一个PDU会话建立请求，所述至少一PDU会话建立请求包括建立的所述至少一个PDU会话是否支持网络切片重映射的指示，和/或，所述建立的至少一个PDU会话是否支持网络切片回退的指示。在该实现中，在会话建立时，源接入网节点便接收到该建立的会话是否支持网络切片重映射的指示，和/或，该建立的会话是否支持网络切片回退的指示，从而，在后续切换过程中，可根据上述指示进行网络切片重映射或回退。
在又一种可能的实现中，所述第一切换消息还包括所述网络切片重映射信息，和/或， 所述缺省网络切片信息。在该实现中，该网络切片重映射信息或缺省网络切片信息若是与终端设备相关的，则在第一切换消息中可以携带上述网络切片重映射信息或缺省网络切片信息。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述目标RAN节点发送切换请求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述目标RAN节点的切换请求应答消息；或所述第一网络节点为核心网节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述核心网节点发送切换需求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述核心网节点的切换命令。在该实现中，源接入网节点可以通过Xn接口切换或NG接口切换完成上述切换流程中网络切片的重映射或回退。
在又一种可能的实现中，所述方法还包括：所述源RAN节点向终端设备发送第二消息；其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。在该实现中，源RAN节点在接收到目标RAN节点发送的会话重映射到的网络切片的标识，或，会话是否回退到缺省网络切片的指示后，通知终端设备上述信息，从而终端设备在后续会话建立过程中，在重映射的网络切片或缺省网络切片上进行数据传输，提高了通信的可靠性。
第五方面，提供了一种切换方法，所述方法包括：源RAN节点向第一网络节点发送第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片回退的指示；以及所述源RAN节点接收来自所述第一网络节点的第一响应消息；其中，在所述第一切换消息包括所述QoS流是否支持网络切片重映射的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或在所述第一切换消息包括所述QoS流是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示；或在所述第一切换消息包括所述QoS流是否支持网络切片重映射的指示，以及所述QoS流是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识，或，所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示。在该方面中，在切换过程中，在切换消息中携带QoS流是否支持 网络切片重映射的指示，和/或，QoS流是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在一种可能的实现中，所述方法还包括：所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。在该实现中，各个RAN节点预先获取网络切片重映射信息，和/或，缺省网络切片信息，源RAN节点无需在每个终端设备的切换过程中，再携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在又一种可能的实现中，所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述源RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。在该实现中，该网络切片重映射信息或缺省网络切片信息若是与终端设备无关的，则在切换前，核心网可以通过单独的消息预先告知源接入网节点网络切片重映射信息，和/或，缺省网络切片信息。
在一种可能的实现中，所述源RAN节点向第一网络节点发送第一切换消息之前，所述方法还包括：所述源RAN节点接收来自核心网节点的所述至少一个QoS流建立请求，所述至少一QoS流建立请求包括建立的所述至少一个QoS流是否支持网络切片重映射的指示，和/或，所述建立的至少一个QoS流是否支持网络切片回退的指示。在该实现中，在QoS流建立时，源接入网节点便接收到该建立的QoS流是否支持网络切片重映射的指示，和/或，该建立的QoS流是否支持网络切片回退的指示，从而，在后续切换过程中，可根据上述指示进行网络切片重映射或回退。
在又一种可能的实现中，所述第一切换消息还包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。在该实现中，该网络切片重映射信息或缺省网络切片信息若是与终端设备相关的，则在第一切换消息中可以携带上述网络切片重映射信息或缺省网络切片信息。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述目标RAN节点发送切换请求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述目标RAN节点的切换请求应答消息；或所述第一网络节点为核心网节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述核心网节点发送切换需求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述核心网节点的切换命令。在该实现中，源接入网节点可以通过Xn接口切换或NG接口切换完成上述切换流程中网络切片的重映射或回退。
在又一种可能的实现中，所述方法还包括：所述源RAN节点向终端设备发送第二消息；其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示。在该实现中，源RAN节点在接收到目标RAN节 点发送的QoS流重映射到的网络切片的标识，或，QoS流是否回退到缺省网络切片的指示后，通知终端设备上述信息，从而终端设备在后续会话建立过程中，在重映射的网络切片或缺省网络切片上进行数据传输，提高了通信的可靠性。
第六方面，提供了一种切换方法，所述方法包括：源RAN节点向第一网络节点发送第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片重映射的指示，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片回退的指示；以及所述源RAN节点接收来自所述第一网络节点的第一响应消息；其中，在所述第一切换消息包括所述DRB是否支持网络切片重映射的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或在所述第一切换消息包括所述DRB是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示；或在所述第一切换消息包括所述DRB是否支持网络切片重映射的指示，以及所述DRB是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识，或，所述至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示。在该方面中，在切换过程中，在切换消息中携带DRB是否支持网络切片重映射的指示，和/或，DRB是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在一种可能的实现中，所述方法还包括：所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。在该实现中，各个RAN节点预先获取网络切片重映射信息，和/或，缺省网络切片信息，源RAN节点无需在每个终端设备的切换过程中，再携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在又一种可能的实现中，所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述源RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。在该实现中，该网络切片重映射信息或缺省网络切片信息若是与终端设备无关的，则在切换前，核心网可以通过单独的消息预先告知源接入网节点网络切片重映射信息，和/或，缺省网络切片信息。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述目标RAN节点发送切换请求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述目标RAN节点的切换请求应答消息；或所述第一网络节点为核心网节 点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述核心网节点发送切换需求消息；所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述核心网节点的切换命令。在该实现中，源接入网节点可以通过Xn接口切换或NG接口切换完成上述切换流程中网络切片的重映射或回退。
在又一种可能的实现中，所述方法还包括：所述源RAN节点向终端设备发送第二消息；其中，所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，属于所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示。在该实现中，源RAN节点在接收到目标RAN节点发送的DRB重映射到的网络切片的标识，或，DRB是否回退到缺省网络切片的指示后，通知终端设备上述信息，从而终端设备在后续DRB建立过程中，在重映射的网络切片或缺省网络切片上进行数据传输，提高了通信的可靠性。
第七方面，提供了一种切换方法，所述方法包括：目标无线接入网RAN节点接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；所述目标RAN节点根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个PDU会话回退到缺省网络切片；以及所述目标RAN节点向所述第二网络节点发送第二响应消息；其中，在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或在所述第二切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。在该方面中，在切换过程中，只需在切换消息中接收会话是否支持网络切片重映射的指示，和/或，会话是否支持网络切片回退的指示，而无需接收整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在一种可能的实现中，所述方法还包括：所述目标RAN节点获取网络切片重映射信息， 和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
在又一种可能的实现中，所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述目标RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述源RAN节点的切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述源RAN节点发送切换请求应答消息；或所述第二网络节点为核心网节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述核心网节点的所述切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述核心网节点发送所述切换请求响应消息。
在又一种可能的实现中，所述方法还包括：所述目标RAN节点向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个PDU会话中各个PDU会话所属的网络切片标识，或，所述路径切换请求包括所述至少一个PDU会话中各个PDU会话是否进行网络切片回退的指示；所述目标RAN节点接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的至少一项：路径切换成功的至少一个PDU会话的PDU会话标识、路径切换失败的所述至少一个PDU会话的PDU会话标识、修改后的至少一个PDU会话的上下文。
第八方面，提供了一种切换方法，所述方法包括：目标RAN节点接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片回退的指示；所述目标RAN节点根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个QoS流进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个QoS流回退到缺省网络切片；以及所述目标RAN节点向所述第二网络节点发送第二响应消息；其中，在所述第二切换消息包括所述QoS流是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或在所述第二切换消息包括所述QoS流是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示；或在所述第二切换消息包括所述QoS流是否支持网络切片重映射的指示，以及所述QoS流是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的 标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示。在该方面中，在切换过程中，只需在切换消息中接收QoS流是否支持网络切片重映射的指示，和/或，QoS流是否支持网络切片回退的指示，而无需接收整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在又一种可能的实现中，所述方法还包括：所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
在又一种可能的实现中，所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述目标RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述源RAN节点的切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述源RAN节点发送切换请求应答消息；或所述第二网络节点为核心网节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述核心网节点的所述切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述核心网节点发送所述切换请求响应消息。
在又一种可能的实现中，所述方法还包括：所述目标RAN节点向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个QoS流中各个QoS流所属的网络切片标识，或，所述路径切换请求包括所述至少一个QoS流中各个QoS流是否进行网络切片回退的指示；所述目标RAN节点接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的至少一项：路径切换成功的至少一个QoS流的QoS流标识、路径切换失败的所述至少一个QoS流的QoS流标识、修改后的至少一个QoS流的上下文。
第九方面，提供了一种切换方法，所述方法还包括：目标RAN节点接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片重映射的指示，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片回退的指示；所述目标RAN节点根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个DRB进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个DRB回退到缺省网络切片；以及所述目标RAN节点向所述第二网络节点发送第二响应消息；其中，在所述第二切换消息包括所述DRB是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识； 或在所述第二切换消息包括所述DRB是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示；或在所述第二切换消息包括所述DRB是否支持网络切片重映射的指示，以及所述DRB是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识，或，至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示。在该方面中，在切换过程中，只需在切换消息中接收DRB是否支持网络切片重映射的指示，和/或，DRB是否支持网络切片回退的指示，而无需接收整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
在一种可能的实现中，所述方法还包括：所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
在又一种可能的实现中，所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：所述目标RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述源RAN节点的切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述源RAN节点发送切换请求应答消息；或所述第二网络节点为核心网节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述核心网节点的所述切换请求消息；所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述核心网节点发送所述切换请求响应消息。
第十方面，本申请提供一种切换装置，该装置可以是终端设备，也可以是终端设备内的芯片或芯片组。该装置可以包括收发单元，还可以包括处理单元。当该装置是终端设备时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第一方面或第一方面的任一种实现中相应的功能。当该装置是终端设备内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使终端设备执行上述第一方面或第一方面的任一种实现中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十一方面，本申请提供一种切换装置，该装置可以是终端设备，也可以是终端设备 内的芯片或芯片组。该装置可以包括收发单元，还可以包括处理单元。当该装置是终端设备时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第二方面或第二方面的任一种实现中相应的功能。当该装置是终端设备内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使终端设备执行上述第二方面或第二方面的任一种实现中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十二方面，本申请提供一种切换装置，该装置可以是终端设备，也可以是终端设备内的芯片或芯片组。该装置可以包括收发单元，还可以包括处理单元。当该装置是终端设备时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第三方面或第三方面的任一种实现中相应的功能。当该装置是终端设备内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使终端设备执行上述第三方面或第三方面的任一种实现中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十三方面，本申请提供一种切换装置，该装置可以是源RAN节点，也可以是源接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是源接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使源接入网节点执行上述第四方面或第四方面的任一设计中相应的功能。当该装置是源接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使源接入网节点执行上述第四方面或第四方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十四方面，本申请提供一种切换装置，该装置可以是源RAN节点，也可以是源接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是源接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使源接入网节点执行上述第五方面或第五方面的任一设计中相应的功能。当该装置是源接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使源接入网节点执行上述第五方面或第五方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模 块(例如，只读存储器、随机存取存储器等)。
第十五方面，本申请提供一种切换装置，该装置可以是源RAN节点，也可以是源接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是源接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使源接入网节点执行上述第六方面或第六方面的任一设计中相应的功能。当该装置是源接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使源接入网节点执行上述第六方面或第六方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十六方面，本申请提供一种切换装置，该装置可以是目标RAN节点，也可以是目标接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是目标接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使目标接入网节点执行上述第七方面或第七方面的任一设计中相应的功能。当该装置是目标接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使目标接入网节点执行上述第七方面或第七方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十七方面，本申请提供一种切换装置，该装置可以是目标RAN节点，也可以是目标接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是目标接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使目标接入网节点执行上述第八方面或第八方面的任一设计中相应的功能。当该装置是目标接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使目标接入网节点执行上述第八方面或第八方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十八方面，本申请提供一种切换装置，该装置可以是目标RAN节点，也可以是目标接入网节点内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是目标接入网节点时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使目标接入网节点执行上述第九方面或第九方面的任一设计中相应的功能。当该装置是目标接入网节点内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以 使目标接入网节点执行上述第九方面或第九方面的任一设计中相应的功能。该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十九方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面或第一方面的任一种实现所述的切换方法。
第二十方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第二方面或第二方面的任一种实现所述的切换方法。
第二十一方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第三方面或第三方面的任一种实现所述的切换方法。
第二十二方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第四方面或第四方面中任一设计所述的切换方法。
第二十三方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第五方面或第五方面中任一设计所述的切换方法。
第二十四方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第六方面或第六方面中任一设计所述的切换方法。
第二十五方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第七方面或第七方面中任一设计所述的切换方法。
第二十六方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第八方面或第八方面中任一设计所述的切换方法。
第二十七方面，提供了一种切换装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装 置执行如上述第九方面或第九方面中任一设计所述的切换方法。
第二十八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面～第九方面或第一方面～第九方面中任一设计所述的切换方法。
第二十九方面，提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面～第九方面或第一方面～第九方面中任一设计所述的切换方法。
第三十方面，提供了一种芯片，所述芯片与存储器耦合，执行本申请实施例第一方面～第九方面或第一方面～第九方面中任一设计所述的切换方法。
需要说明的是，本申请实施例中“耦合”是指两个部件彼此直接或间接地结合。
第三十一方面，提供了一种通信系统，包括上述切换装置。
附图说明
图1为本申请适用的一个通信系统的架构示意图；
图2为本申请实施例提供的切换装置200的结构示意图；
图3为本申请实施例提供的切换方法的流程示意图；
图4为本申请实施例提供的切换方法的又一流程示意图；
图5为本申请实施例提供的切换方法的又一流程示意图；
图6为本申请实施例提供的切换方法的又一流程示意图；
图7为本申请实施例提供的切换方法的又一流程示意图；
图8为示例的目标RAN节点内集中单元与分布式单元实现切换方法的流程示意图；
图9为本申请实施例提供的切换方法的又一流程示意图；
图10为本申请实施例提供的切换装置300的结构示意图；
图11为本申请实施例提供的切换装置400的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统、增强的长期演进(enhanced long term evolution，e-LTE)系统、第五代(5th generation，5G)系统或新无线(new radio，NR)、或者下一代通信系统，比如第六代(6 th generation，6G)系统等。本申请中涉及的5G移动通信系统包括非独立组网(non-standalone，NSA)的5G移动通信系统或独立组网(standalone，SA)的5G移动通信系统。通信系统还可以是陆上公用移动通信网(public land mobile network，PLMN)网络、设备到设备(device-to-device，D2D)通信系统、机器到机器(machine to machine，M2M)通信系统、物联网(internet of Things，IoT)、车联网通信系统或者其他通信系统。
图1为本申请适用的一个通信系统的架构示意图，该通信系统100包括终端设备101、源RAN节点102和目标RAN节点103。其中，终端设备101、源RAN节点102和目标RAN 节点103之间可以直接通信，也可以通过其它设备的转发进行通信，本申请实施例对此不作具体限定。虽然未示出，该通信系统还可以包括其它网元。
可选的，本申请实施例中的终端设备101可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、用户设备(user equipment，UE)、终端(terminal)、无线通信设备、用户代理、用户装置、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端或者未来演进的PLMN中的终端或者未来车联网中的终端等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，终端设备101可以是手机、平板电脑、带无线收发功能的电脑、虚拟现实终端、增强现实终端、工业控制中的无线终端、无人驾驶中的无线终端、远程手术中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市中的无线终端、智慧家庭中的无线终端等。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备101还可以是IoT系统中的终端，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IoT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，在本申请实施例中，终端设备101还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分终端)、接收RAN节点的控制信息与下行数据，并发送电磁波，向RAN节点传输上行数据。
可选的，本申请实施例中的源RAN节点102或目标RAN节点103可以是用于与终端设备101通信的任意一种具有无线收发功能的通信设备。该源RAN节点102或目标RAN节点103包括但不限于：演进型节点B(evolved node B,eNB)，基带单元(baseband unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者传输接收点(transmission reception point，TRP)等。该RAN设备还可以为5G系统中的gNB或TRP或TP，或者5G系统中的基站的一个或一组(包括多个天线面板)天线面板。此外，该接入网设备还可以为构成gNB或TP的网络节点，如BBU，或分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中单元(central unit，CU)和DU。此外，gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB 的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层(physical layer，PHY)的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU和AAU发送的。可以理解的是，源RAN节点102或目标RAN节点103可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。
可选的，本申请实施例中的源RAN节点102或目标RAN节点103与终端设备101之间可以通过授权频谱进行通信，也可以通过免授权频谱进行通信，也可以同时通过授权频谱和免授权频谱进行通信。源RAN节点102或目标RAN节点103与终端设备101之间可以通过6千兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对源RAN节点102或目标RAN节点103与终端设备101之间所使用的频谱资源不做限定。
可选的，本申请实施例中的终端设备101、源RAN节点102或目标RAN节点103可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对终端设备101、源RAN节点102或目标RAN节点103的应用场景不做限定。
可选的，在本申请实施例中，终端设备101、源RAN节点102或目标RAN节点103包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备101、源RAN节点102或目标RAN节点103，或者，是终端设备101、源RAN节点102或目标RAN节点103中能够调用程序并执行程序的功能模块。
换言之，本申请实施例中的终端设备101、源RAN节点102或目标RAN节点103的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的终端设备、源RAN节点或目标RAN节点的相关功能可以通过图2中的切换装置200来实现。图2所示为本申请实施例提供的切换装置200的结构示 意图。该切换装置200包括一个或多个处理器201，通信线路202，以及至少一个通信接口(图2中仅是示例性的以包括通信接口204，以及一个处理器201为例进行说明)，可选的还可以包括存储器203。
处理器201可以是一个中央处理单元(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路202可包括一通路，用于连接不同组件之间。
通信接口204，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口204也可以是位于处理器201内的收发电路，用以实现处理器的信号输入和信号输出。
存储器203可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路202与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器203用于存储执行本申请方案的计算机执行指令，并由处理器201来控制执行。处理器201用于执行存储器203中存储的计算机执行指令，从而实现本申请实施例中提供的切换方法。
或者，本申请实施例中，也可以是处理器201执行本申请下述实施例提供的切换方法中的处理相关的功能，通信接口204负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器201可以包括一个或多个CPU，例如图2中的CPU0和CPU1。
在具体实现中，作为一种实施例，切换装置200可以包括多个处理器，例如图2中的处理器201和处理器206。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，切换装置200还可以包括输出设备205和输入设备206。输出设备205和处理器201通信，可以以多种方式来显示信息。
上述的切换装置200可以是一个通用装置或者是一个专用装置。例如切换装置200可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动 手机、平板电脑、无线终端、嵌入式设备或具有图2中类似结构的设备。本申请实施例不限定切换装置200的类型。
下面将结合图1至图9对本申请实施例提供的切换方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不做具体限定。
本申请实施例中，涉及的网络切片重映射(slice re-mapping)和网络切片回退(slice fallback)的含义如下：
网络切片重映射，是指在网络切片#1(slice#1)上进行的协议数据单元(protocol data unit，PDU)会话(session)/服务质量流(quality of service flow，QoS flow)/数据无线承载(data radio bearer，DRB)可以重映射到网络切片#2(slice#2)。即网络切片#1的业务可以通过网络切片#2实现，相当于利用网络切片#2的网络资源实现了网络切片#1的业务。其中，源RAN节点支持网络切片#1，然而，目标RAN节点可能不支持网络切片#1，而支持网络切片#2。即网络切片重映射包括PDU会话粒度的网络切片重映射、QoS流粒度的网络切片重映射和DRB粒度的网络切片重映射。其中，PDU会话粒度的网络切片重映射，是指在源网络切片上进行的PDU会话可以重映射到目标RAN节点支持的另一网络切片，由重映射的网络切片继续进行该PDU会话；QoS流粒度的网络切片重映射，是指在源网络切片上进行的QoS流可以重映射到目标RAN节点支持的另一网络切片，由重映射的网络切片继续执行该QoS流中的业务；DRB粒度的网络切片重映射，是指在源网络切片上进行的DRB可以重映射到目标RAN节点支持的另一网络切片，由重映射的网络切片继续执行该DRB上承载的业务。
网络切片回退，是指终端设备、源RAN节点和目标RAN节点均支持一个特定的网络切片并预先获知该特定的网络切片的标识和配置，当终端设备发生切换时，其在源RAN节点的任意一个网络切片上的PDU会话/QoS流/DRB转移(也称为回退)到该特定的网络切片，即在切换后，终端设备的任意一个网络切片上的PDU会话/QoS流/DRB通过目标RAN节点的该特定的网络切片实现，也可认为是终端设备的任意一个网络切片重映射到该特定的网络切片。不管目标RAN节点是否支持其它的网络切片，也不管终端设备在源RAN节点上使用哪个网络切片，在终端设备发生切换时，目标RAN节点可以将终端设备的任意一个网络切片上的PDU会话/QoS流/DRB回退到该特定的网络切片上，即利用该特定的网络切片的网络资源来实现终端设备的任意一个网络切片的业务。在本文中，作为示例，该特定的网络切片称为缺省(default)网络切片，该特定的网络切片也可有其他的名称，本申请对此不做限定。应理解，该缺省网络切片可以是由网络侧确定并配置给终端设备的，也可以是终端设备与网络侧协商得到，还可以是标准预定义的。
换言之，网络切片重映射是将一个网络切片映射到另一个网络切片，而网络切片回退是将一个网络切片映射到缺省网络切片。值得说明的是，当该另一个网络切片与缺省网络切片相同时，网络切片重映射等同于网络切片回退。
本申请实施例中，网络切片标识可以采用以下参数中的至少一种表征：
1)网络切片类型信息，例如，网络切片类型信息可以指示增强的移动宽带业务(enhanced mobile broadBand，eMBB)，超可靠低时延通信(ultra-reliable low latency  communications,URLLC)，海量机器类通信(massive machine type communication,mMTC)等网络切片类型。可选地，该网络切片类型信息还可以指示端到端的网络切片类型，包含无线接入网(radio access network，RAN)到核心网(core network，CN)的网络切片类型，也可以指RAN侧网络切片类型，或者CN侧网络切片类型；
2)业务类型信息，与具体的业务相关，例如，该业务类型信息可以指示视频业务，车联网业务，语音业务等业务特征或者具体业务的信息；
3)租户(tenant)信息，用于指示创建或者租用该网络切片的客户信息；
4)用户组信息，用于指示按照某种特征，如用户的级别等将用户进行分组的分组信息；
5)切片组信息，用于指示按照某种特征，例如，可以将终端设备能够接入的所有网络切片作为一个切片组，或者也可以按照其他标准划分网络切片的分组；
6)网络切片实例信息，用于指示为该网络切片创建的实例标识以及特征信息，例如，可以为网络切片实例分配一个标识，用于指示该网络切片实例，也可以在网络切片实例标识的基础上映射一个新的标识，关联该网络切片实例，接收方可以根据该标识识别出该标识指示的具体网络切片实例；
专有核心网(dedicated core network，DCN)标识，该标识用于唯一指示LTE系统或者eLTE系统中的专有核心网，例如物联网专有的核心网，可选的，该DCN标识可以与网络切片标识做映射，由DCN标识可以映射出网络切片标识，通过网络切片标识也可以映射出DCN标识。
如图3所示，为本申请实施例提供的一种切换方法的流程示意图。该流程主要涉及基于Xn接口切换的PDU会话粒度的网络切片重映射或回退。示例性地，该方法包括以下步骤：
S101、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息。
在终端设备进行切换前，源RAN节点、目标RAN节点可以获取网络切片重映射信息，和/或，缺省网络切片信息。这样，在终端设备切换过程中，源RAN节点无需向目标RAN节点重新发送网络切片重映射信息，和/或，缺省网络切片信息。目标RAN节点也无需重新接收网络切片重映射信息，和/或，缺省网络切片信息。
示例性地，源RAN节点从核心网节点或网络管理系统接收第一消息，第一消息包括网络切片重映射信息，和/或，缺省网络切片信息。该第一消息可以包括RAN节点覆盖范围内所有源网络切片标识对应的网络切片重映射信息，和/或，缺省网络切片信息。其中，该网络切片重映射信息是源RAN节点支持的网络切片的重映射信息。具体地，该网络切片重映射信息包括一个或多个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识。应理解，一个源网络切片对应的可重映射的网络切片可以是一个或多个，该源网络切片最终重映射到哪一个网络切片可以是由目标RAN节点根据根据各网络切片优先级、各网络切片的负载情况、各网络切片的性能指标、或其他策略来确定。示例性地，源网络切片标识与重映射的网络切片标识的对应关系如下表1所示：
表1
源网络切片标识 可重映射的网络切片标识
网络切片1 网络切片2、网络切片3
网络切片4 网络切片5
… …
网络切片N 网络切片M1、网络切片M2
在发生切换时，源RAN节点支持的源网络切片上的PDU会话也可以回退到缺省网络切片上进行。该缺省网络切片信息包括缺省网络切片的标识。
该第一消息可以是下一代应用协议(next generation application protocol，NGAP)消息。接入和移动性管理功能(access and mobility management function，AMF)网元可以通过NGAP消息告知源RAN节点、目标RAN节点上述网络切片重映射信息，和/或，缺省网络切片信息。
该第一消息也可以是Xn接口应用协议(Xn application protocol，XnAP)消息。RAN节点之间通过XnAP消息交互上述网络切片重映射信息，和/或，缺省网络切片信息。
另外，UE也可以预先获取网络切片重映射信息，和/或，缺省网络切片信息。例如，AMF网元可以通过非接入层(non-access straum，NAS)消息告知UE上述网络切片重映射信息，和/或，缺省网络切片信息。又例如，源RAN节点在获取网络切片重映射信息，和/或，缺省网络切片信息后，也可以通过广播消息或无线资源控制(radio resource control，RRC)消息告知UE上述网络切片重映射信息，和/或，缺省网络切片信息。
S102、源RAN节点向目标RAN节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片回退的指示。
示例性地，源RAN节点根据UE上报的源RAN节点的相邻的一个或多个RAN节点的信号强度测量报告，在一个或多个RAN节点中确定目标RAN节点。目标RAN节点接收该第一切换消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一切换消息可以为切换请求(handover request)消息。
在源RAN节点向目标RAN节点发送第一切换消息之前，还可以接收来自核心网节点的PDU会话建立请求，PDU会话建立请求包括建立的PDU会话是否支持网络切片重映射的指示，和/或，建立的PDU会话是否支持网络切片回退的指示。从而，源RAN节点可以根据上述指示，进行后续操作。
在终端设备发生切换时，为了提高业务的连续性，源RAN节点的一个或多个源网络切片上进行的PDU会话需要在目标RAN节点侧继续进行。然而，目标RAN节点支持的网络切片可能与源网络切片不同。终端设备进行切换后，PDU会话可能不能在源网络切片上进行，需要重映射到目标RAN节点支持的新的网络切片或回退到缺省网络切片上进行。源RAN节点对于每个源网络切片上进行的PDU会话，需要指示该PDU会话是否支持网络切片重映射，和/或是否支持网络切片回退。
在源网络切片与PDU会话是一一对应的情况下，即一个源网络切片上当前只存在一个 待切换的PDU会话，在一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的PDU会话是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话是否支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的PDU会话是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话是否支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个网络切片的PDU会话是否支持网络切片重映射的指示和该PDU会话是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话是否支持网络切片重映射和回退。
在另一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的PDU会话支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的PDU会话支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的PDU会话支持网络切片重映射的指示和该PDU会话支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的PDU会话支持网络切片重映射和回退。
在源网络切片与PDU会话是一对多的关系的情况下，即一个源网络切片上存在多个待切换到目标RAN节点的PDU会话，在一种可能的实现中，第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个PDU会话的PDU会话标识以及其中部分或全部PDU会话标识对应的PDU会话是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的多个PDU会话中的部分或全部PDU会话是否支持网络切片重映射；或者，第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个PDU会话的PDU会话标识以及其中部分或全部PDU会话标识对应的PDU会话是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的多个PDU会话中的部分或全部PDU会话是否支持网络切片回退；或者第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个PDU会话的PDU会话标识，以及其中部分或全部PDU会话标识对应的PDU会话是否支持网络切片重映射的指示和部分或全部PDU会话标识对应的PDU会话是否支持网络切片回退的指示，即对于每个源网络切片标识，指示该源网络切片上的各个PDU会话中的部分或全部PDU会话是否支持网络切片重映射和回退。
值得说明的是，指示一个PDU会话是否支持网络切片重映射和/或支持网络切片回退，通常包含该PDU会话的标识以及该PDU会话是否支持网络切片重映射和/或支持网络切片回退的指示信息。同样地，指示一个PDU会话支持网络切片重映射和/或支持网络切片回退，通常包含该PDU会话的标识以及该PDU会话支持网络切片重映射和/或支持网络切片回退的指示信息。应理解，该指示信息可以是一个1比特的指示信息，例如当该比特位取值为1时，表示支持网络切片重映射和/或支持网络切片回退，当该比特位取值为0时，表 示不支持网络切片重映射和/或支持网络切片回退。
S103、目标RAN节点根据第一切换消息，进行准入控制。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个PDU会话是否支持网络切片重映射的指示，则该准入控制用于确定是否对该一个或多个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识。具体地，对于该源网络切片所对应的任意一个PDU会话，若第一切换消息包括该PDU会话支持网络切片重映射的指示，则目标RAN节点根据步骤S101中获取的该源网络切片标识对应的网络切片重映射信息，确定将该源网络切片上的该PDU会话重映射到新的网络切片。例如，源网络切片(slice#1)上的一个PDU会话切换到目标RAN节点，然而，目标RAN节点并不支持slice#1，与slice#1对应的网络切片重映射信息包括slice#2和slice#3，则目标RAN节点可以根据策略(例如，基于目标RAN节点上的slice#2和slice#3各自的负载情况或者性能指标、或者切片的优先级等)将该PDU会话重映射到slice#2或slice#3；又例如，目标RAN节点支持slice#1，则目标RAN节点可以使用slice#1继续进行该PDU会话，在目标RAN节点的slice#1负载过高时，也可以将slice#1重映射到slice#2或slice#3。若第一切换消息包括该PDU会话不支持网络切片重映射的指示，且目标RAN节点不支持slice#1，则目标RAN节点拒绝对该源网络切片上的该PDU会话的切换；或者第一切换消息包括该PDU会话不支持网络切片重映射的指示，且目标RAN节点支持slice#1，则目标RAN节点可以使用slice#1继续进行该PDU会话。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个PDU会话是否支持网络切片回退的指示，则该准入控制用于确定是否将该一个或多个PDU会话回退到缺省网络切片。具体地，对于该源网络切片所对应的任意一个PDU会话，若第一切换消息包括PDU会话支持网络切片回退的指示，则目标RAN节点根据步骤S101中获取的缺省网络切片信息，确定将该源网络切片上的该PDU会话回退到缺省网络切片进行。若第一切换消息包括PDU会话不支持网络切片回退的指示，则目标RAN节点拒绝对该源网络切片上的该PDU会话的切换。
类似地，对于第一切换消息中包含一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个PDU会话是否支持网络切片重映射的指示和是否支持网络切片回退的指示，则对于该源网络切片所对应的任意一个PDU会话，目标RAN节点可以根据策略选择将该PDU会话重映射到S101中网络切片重映射信息包括的一个网络切片上，或者选择将该PDU会话回退到缺省网络切片上。
S104、目标RAN节点向源RAN节点发送第一响应消息。
相应地，源RAN节点接收该第一响应消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一响应消息为切换请求应答(handover request acknowledgement)消息。
在一种可能的实现中，第一切换消息包括一个源网络切片的一个PDU会话支持网络切片重映射的指示，目标RAN节点通过准入控制确定了将该PDU会话进行重映射，则第一响应消息包括该源网络切片标识、该PDU会话标识和该PDU会话重映射到的网络切片的标识。即若该PDU会话支持网络切片重映射，目标RAN节点通过上述准入控制确定了该 PDU会话重映射到的网络切片的标识。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片上的该PDU会话重映射到哪个网络切片。
在另一种可能的实现中，第一切换消息包括一个源网络切片的一个PDU会话是否支持网络切片重映射的指示。若该源网络切片的该PDU会话支持网络切片重映射，且目标RAN节点通过准入控制确定了将该PDU会话进行重映射，则第一响应消息包括的信息与上述实现相同。若该源网络切片的该PDU会话不支持网络切片重映射，则目标RAN节点拒绝对该PDU会话进行重映射，该PDU会话中断，则第一响应消息包括该源网络切片标识、该PDU会话标识和目标RAN节点拒绝对该PDU会话进行重映射的指示信息。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个PDU会话支持网络切片回退的指示，且目标RAN节点通过上述准入控制确定了将该PDU会话回退到缺省网络切片，则第一响应消息包括该源网络切片标识、该PDU会话标识和该PDU会话回退到缺省网络切片的指示，或者第一响应消息包括该源网络切片标识、该PDU会话标识和缺省网络切片标识。其中，该PDU会话回退到缺省网络切片的指示可以是1个比特的指示信息，例如，该比特值为“1”时，表示该PDU会话回退到缺省网络切片，由于源RAN节点和目标RAN节点是预先获取了缺省网络切片信息的，所以，在接收到该PDU会话回退到缺省网络切片的指示时，源RAN节点能够知晓回退到哪个网络切片；该比特值为“0”时，表示该PDU会话不进行回退，该PDU会话结束。即若该PDU会话支持网络切片回退，目标RAN节点通过上述准入控制确定了将该PDU会话回退到缺省网络切片。若确定将该PDU会话回退到缺省网络切片，则目标RAN节点通过第一响应消息告知源RAN节点该源网络切片上的该PDU会话回退到缺省网络切片。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个PDU会话是否支持网络切片回退的指示，若该源网络切片的该PDU会话支持网络切片回退，且目标RAN节点通过上述准入控制确定了将该PDU会话回退到缺省网络切片，则第一响应消息包括的信息与上述实现方式相同；若该源网络切片的该PDU会话不支持网络切片回退，则目标RAN节点拒绝对该PDU会话进行回退，该PDU会话中断，则第一响应消息包括该源网络切片标识、该PDU会话标识和目标RAN节点拒绝对该PDU会话进行回退的指示信息。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个PDU会话支持网络切片重映射的指示和支持网络切片回退的指示，则第一响应消息包括该源网络切片标识、该PDU会话标识和该PDU会话重映射到的网络切片的标识，或，第一响应消息包括该源网络切片标识、该PDU会话标识和该PDU会话回退到缺省网络切片的指示，或，第一响应消息包括该源网络切片标识、该PDU会话标识和缺省网络切片标识。若该PDU会话支持网络切片重映射，且该PDU会话支持网络切片回退，目标RAN节点通过上述准入控制确定了是将该PDU会话重映射到新的网络切片或回退到缺省网络切片。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片中的该PDU会话重映射到的网络切片的标识，或指示将该PDU会话回退到缺省网络切片。
源RAN节点接收到该PDU会话重映射到的网络切片的标识或缺省网络切片标识后，通过比对该PDU会话所属的源网络切片标识与目标RAN节点分配的重映射到的网络切片的标识，即可知道该PDU会话需要进行重映射；或通过比对该PDU会话所属的源网络切 片标识与目标RAN节点指示的缺省网络切片标识，即可知道该PDU会话需要进行回退。源RAN节点也可以接收该PDU会话是否回退到缺省网络切片的指示，根据该指示，源RAN节点可以知道该PDU会话需要回退到缺省网络切片。
S105、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。该第二消息可以是RRC消息。
具体实现时，在一种可能的实现中，可以由目标RAN节点生成一个容器(container)，该容器内包括上述第一响应消息包括的内容。目标RAN节点将该容器发送给源RAN节点。源RAN节点不解析该容器里的信息，而是将该容器包含在RRC消息中转发给终端设备。
在另一种可能的实现中，源RAN节点解析第一响应消息后，将第一响应消息中的部分或全部信息包含在源RAN节点生成的RRC消息中，并将该RRC消息发送给终端设备。
终端设备接收到上述第二消息，该第二消息还可以包括至少一个PDU会话重映射到的网络切片的配置参数，或缺省网络切片的配置参数，则终端设备随机接入到目标RAN节点，根据该至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点进行通信，或，根据缺省网络切片的配置参数与目标RAN节点进行通信。
S106、目标RAN节点向核心网节点发送路径切换请求。
其中，该路径切换请求包括一个或多个PDU会话中各个PDU会话所重映射的网络切片的标识，或，该一个或多个PDU会话中各个PDU会话是否进行网络切片回退的指示。
目标RAN节点指示哪些PDU会话需要进行重映射或回退。核心网节点根据该路径切换请求，修改对应的PDU会话。具体地，修改该PDU会话以使其在重映射的网络切片中继续进行，或修改该PDU会话以使其在缺省网络切片上继续进行。应理解，不同的网络切片具有不同的数据传输路径，因此，在网络切片重映射或回退时，该网络切片中的一个或多个PDU会话的路径会发生变化。核心网节点通过修改一个PDU会话的上下文来实现对该PDU会话的路径改变。
S107、核心网节点向目标RAN节点发送路径切换响应。该路径切换响应包括以下信息中的一项或多项：路径切换成功的一个或多个PDU会话的PDU会话标识、路径切换失败的一个或多个PDU会话的PDU会话标识、修改后的一个或多个PDU会话的上下文。
核心网节点将一个或多个PDU会话路径切换的结果发送给目标RAN节点。该一个或多个PDU会话路径切换的结果包括以下信息中的一项或多项：路径切换成功的一个或多个PDU会话的PDU会话标识、路径切换失败的一个或多个PDU会话的PDU会话标识、修改后的一个或多个PDU会话的上下文。该PDU会话修改的结果携带在路径切换响应中。
从而，经过上述处理，完成了终端设备切换时的网络侧流程。
另外，上述源RAN节点可能支持CU和DU分离的架构，目标RAN节点也可能支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息中的部分或全部信息。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的 部分或全部信息，进行准入控制；以及向源RAN节点的CU发送第一响应消息的步骤。
上述源RAN节点可能不支持CU和DU分离的架构，而目标RAN节点支持CU和DU分离的架构，在这种情况下，由源RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及发送第二消息的步骤。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的部分或全部信息，进行准入控制，并向源RAN节点发送第一响应消息的步骤。
上述源RAN节点可能支持CU和DU分离的架构，而目标RAN节点可能不支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤；接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息的部分或全部信息。由目标RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及第一切换消息，进行准入控制，并向源RAN节点的CU发送第一响应消息的步骤。
根据本申请实施例提供的一种切换方法，在基于Xn接口的切换过程中，在切换消息中携带PDU会话是否支持网络切片重映射的指示，和/或，PDU会话是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
上述切换方法是基于Xn接口切换的，该切换方法还可以基于NG接口切换。如图4所示，为本申请实施例提供的又一种切换方法的流程示意图。该方法主要涉及基于NG接口切换的PDU会话粒度的网络切片重映射或回退。示例性地，该方法可以包括以下流程：
S201、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息。
该步骤的具体实现可参考图3所示实施例的步骤S101。
S202、源RAN节点向核心网节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片回退的指示。
相应地，核心网节点接收该第一切换消息。
具体地，该第一切换消息可以为切换需求(handover required)消息。该切换需求消息用于指示源RAN节点需要进行切换。该切换需求消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个PDU会话是否支持网络切片回退的指示。
该步骤的具体实现可参考图3所示实施例的步骤S102中的相关描述。
S203、核心网节点向目标RAN节点发送第二切换消息。
示例性地，源RAN节点根据UE上报的源RAN节点的相邻的一个或多个RAN节点的信号强度测量报告，在一个或多个RAN节点中确定目标RAN节点。上述第一切换消息还可以包括目标RAN节点的标识。核心网节点向目标RAN节点发送第二切换消息。
该第二切换消息的内容包含第一切换消息的部分或全部内容。
相应地，目标RAN节点接收该第二切换消息。
具体地，该第二切换消息可以为切换请求(handover request)消息。该切换请求消息用于指示请求将源RAN节点的PDU会话切换到目标RAN节点。
该步骤的具体实现可参考图3所示实施例的步骤S102中的相关描述。
S204、目标RAN节点根据第二切换消息，进行准入控制。
该准入控制用于确定是否对一个或多个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识；或，该准入控制用于确定是否将一个或多个PDU会话回退到缺省网络切片。
该步骤的具体实现可参考图3所示实施例的步骤S103。
S205、目标RAN节点向核心网节点发送第二响应消息。
相应地，核心网节点接收该第二响应消息。
该第二响应消息为对第二切换消息的响应消息。具体地，该第二响应消息可以为切换请求应答(handover request acknowledge)消息。该切换请求应答消息为对上述切换请求消息的响应。
该步骤的具体实现可参考图3所示实施例的步骤S104中的相关描述。
S206、核心网节点向源RAN节点发送第一响应消息。
第一响应消息的内容可以包含第二响应消息的部分或全部内容。
具体地，该第二切换消息可以为切换命令(handover command)。该切换命令用于指示源RAN节点将PDU会话切换到目标RAN节点。具体地，用于指示源RAN节点将PDU会话切换到重映射的网络切片或缺省网络切片。
该步骤的具体实现可参考图3所示实施例的步骤S104的相关描述。
S207、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。
该步骤的具体实现可参考图3所示实施例的步骤S105。
根据本申请实施例提供的一种切换方法，在基于NG接口的切换过程中，在切换消息中携带PDU会话是否支持网络切片重映射的指示，和/或，PDU会话是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
上述实施例描述了基于PDU会话粒度的网络切片重映射或回退，接下来描述基于QoS流粒度的网络切片重映射或回退。终端设备的一个QoS流也是在一个网络切片上进行的。因此，终端设备进行RAN节点切换时，还可能涉及QoS流粒度的网络切片重映射或回退。
如图5所示，为本申请实施例提供的一种切换方法的流程示意图。该流程主要涉及基于Xn接口切换的QoS流粒度的网络切片重映射或回退。示例性地，该方法包括以下步骤：
S301、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片 信息。
该步骤的具体实现可参考图3所示实施例的步骤S101的相关描述。
S302、源RAN节点向目标RAN节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片回退的指示。
相应地，目标RAN节点接收该第一切换消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一切换消息可以为切换请求消息。
在源RAN节点向目标RAN节点发送第一切换消息之前，还可以接收来自核心网节点的QoS流建立请求，QoS流建立请求包括建立的QoS流是否支持网络切片重映射的指示，和/或，建立的QoS流是否支持网络切片回退的指示。从而，源RAN节点可以根据上述指示，进行后续操作。
在终端设备发生切换时，为了提高业务的连续性，源RAN节点的一个或多个源网络切片上进行的QoS流需要在目标RAN节点侧继续进行。然而，目标RAN节点支持的网络切片可能与源网络切片不同。终端设备进行切换后，QoS流可能不能在源网络切片上进行，需要重映射到目标RAN节点支持的新的网络切片或回退到缺省网络切片上进行。源RAN节点对于每个源网络切片上进行的QoS流，需要指示该QoS流是否支持网络切片重映射，和/或是否支持网络切片回退。
在源网络切片与QoS流是一一对应的情况下，即一个源网络切片上当前只存在一个待切换的QoS流，在一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的QoS流是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流是否支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的QoS流是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流是否支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个网络切片的QoS流是否支持网络切片重映射的指示和该QoS流是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流是否支持网络切片重映射和回退。
在另一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的QoS流支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和该一个或多个源网络切片中各个源网络切片的QoS流支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的QoS流支持网络切片重映射的指示和该QoS流支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的QoS流支持网络切片重映射和回退。
在源网络切片与QoS流是一对多的关系的情况下，即一个源网络切片上存在多个待切换到目标RAN节点的QoS流，在一种可能的实现中，第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个QoS流的QoS流标识以及其中部分或全部QoS流标识对应的QoS流是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示该源网络切片上的多个QoS流中的部分或全部QoS流是否支持网络切片重映射；或者，第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个QoS流的QoS流标识以及其中部分或全部QoS流标识对应的QoS流是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的多个QoS流中的部分或全部QoS流是否支持网络切片回退；或者第一切换消息包括一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片上的多个QoS流的QoS流标识，以及其中部分或全部QoS流标识对应的QoS流是否支持网络切片重映射的指示和部分或全部QoS流标识对应的QoS流是否支持网络切片回退的指示，即对于每个源网络切片标识，指示该源网络切片上的各个QoS流中的部分或全部QoS流是否支持网络切片重映射和回退。
值得说明的是，指示一个QoS流是否支持网络切片重映射和/或支持网络切片回退，通常包含该QoS流的标识以及该QoS流是否支持网络切片重映射和/或支持网络切片回退的指示信息。同样地，指示一个QoS流支持网络切片重映射和/或支持网络切片回退，通常包含该QoS流的标识以及该QoS流支持网络切片重映射和/或支持网络切片回退的指示信息。应理解，该指示信息可以是一个1比特的指示信息，例如当该比特位取值为1时，表示支持网络切片重映射和/或支持网络切片回退，当该比特位取值为0时，表示不支持网络切片重映射和/或支持网络切片回退。
S303、目标RAN节点根据第一切换消息，进行准入控制。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个QoS流是否支持网络切片重映射的指示，则该准入控制用于确定是否对该一个或多个QoS流进行网络切片重映射，并确定重映射到的网络切片的标识。具体地，对于该源网络切片所对应的任意一个QoS流，若第一切换消息包括该QoS流支持网络切片重映射的指示，则目标RAN节点根据步骤S301中获取的该源网络切片标识对应的网络切片重映射信息，确定将该源网络切片上的该QoS流重映射到新的网络切片。例如，源网络切片(slice#1)上的一个QoS流切换到目标RAN节点，然而，目标RAN节点并不支持slice#1，与slice#1对应的网络切片重映射信息包括slice#2和slice#3，则目标RAN节点可以根据策略(例如，基于目标RAN节点上的slice#2和slice#3各自的负载情况或者性能指标、或者切片的优先级等)将该QoS流重映射到slice#2或slice#3；又例如，目标RAN节点支持slice#1，则目标RAN节点可以使用slice#1继续进行该QoS流，在目标RAN节点的slice#1负载过高时，也可以将slice#1重映射到slice#2或slice#3。若第一切换消息包括该QoS流不支持网络切片重映射的指示，且目标RAN节点不支持slice#1，则目标RAN节点拒绝对该源网络切片上的该QoS流的切换；或者第一切换消息包括该QoS流不支持网络切片重映射的指示，且目标RAN节点支持slice#1，则目标RAN节点可以使用slice#1继续进行该QoS流。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个QoS流是否支持网络切片回退的指示，则该准入控制用于确定是否将该一个或多个QoS流回退到缺省网络切片。具体地，对于该源网络切片所对应的任意一个QoS流，若第一切换消息包括QoS流支持网络切片回退的指示，则目标RAN节点根据步骤S301中获取的缺省网络切片信息，确定将该源网络切片上的该QoS流回退到缺省网络切片进行。若第一切换消息包括QoS流不支持网络切片回退的指示，则目标RAN节点拒绝对该源网络切片上的该QoS流的切换。
类似地，对于第一切换消息中包含一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个QoS流是否支持网络切片重映射的指示和是否支持网络切片回退的指示，则对于该源网络切片所对应的任意一个QoS流，目标RAN节点可以根据策略选择将该QoS流重映射到S301中网络切片重映射信息包括的一个网络切片上，或者选择将该QoS流回退到缺省网络切片上。
S304、目标RAN节点向源RAN节点发送第一响应消息。
相应地，源RAN节点接收该第一响应消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一响应消息为切换请求应答消息。
在一种可能的实现中，第一切换消息包括一个源网络切片的一个QoS流支持网络切片重映射的指示，目标RAN节点通过准入控制确定了将该QoS流进行重映射，则第一响应消息包括该源网络切片标识、该QoS流标识和该QoS流重映射到的网络切片的标识。即若该QoS流支持网络切片重映射，目标RAN节点通过上述准入控制确定了该QoS流重映射到的网络切片的标识。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片上的该QoS流重映射到哪个网络切片。
在另一种可能的实现中，第一切换消息包括一个源网络切片的一个QoS流是否支持网络切片重映射的指示。若该源网络切片的该QoS流支持网络切片重映射，且目标RAN节点通过准入控制确定了将该QoS流进行重映射，则第一响应消息包括的信息与上述实现相同。若该源网络切片的该QoS流不支持网络切片重映射，则目标RAN节点拒绝对该QoS流进行重映射，该QoS流中断，则第一响应消息包括该源网络切片标识、该QoS流标识和目标RAN节点拒绝对该QoS流进行重映射的指示信息。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个QoS流支持网络切片回退的指示，且目标RAN节点通过上述准入控制确定了将该QoS流回退到缺省网络切片，则第一响应消息包括该源网络切片标识、该QoS流标识和该QoS流回退到缺省网络切片的指示，或者第一响应消息包括该源网络切片标识、该QoS流标识和缺省网络切片标识。其中，该QoS流回退到缺省网络切片的指示可以是1个比特的指示信息，例如，该比特值为“1”时，表示该QoS流回退到缺省网络切片，由于源RAN节点和目标RAN节点是预先获取了缺省网络切片信息的，所以，在接收到该QoS流回退到缺省网络切片的指示时，源RAN节点能够知晓回退到哪个网络切片；该比特值为“0”时，表示该QoS流不进行回退，该QoS流结束。即若该QoS流支持网络切片回退，目标RAN节点通过上述准入控制确定了将该QoS流回退到缺省网络切片。若确定将该QoS流回退到缺省网络切片，则目标RAN 节点通过第一响应消息告知源RAN节点该源网络切片上的该QoS流回退到缺省网络切片。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个QoS流是否支持网络切片回退的指示，若该源网络切片的该QoS流支持网络切片回退，且目标RAN节点通过上述准入控制确定了将该QoS流回退到缺省网络切片，则第一响应消息包括的信息与上述实现方式相同；若该源网络切片的该QoS流不支持网络切片回退，则目标RAN节点拒绝对该QoS流进行回退，该QoS流中断，则第一响应消息包括该源网络切片标识、该QoS流标识和目标RAN节点拒绝对该QoS流进行回退的指示信息。
在又一种可能的实现中，第一切换消息包括一个源网络切片的一个QoS流支持网络切片重映射的指示和支持网络切片回退的指示，则第一响应消息包括该源网络切片标识、该QoS流标识和该QoS流重映射到的网络切片的标识，或，第一响应消息包括该源网络切片标识、该QoS流标识和该QoS流回退到缺省网络切片的指示，或，第一响应消息包括该源网络切片标识、该QoS流标识和缺省网络切片标识。若该QoS流支持网络切片重映射，且该QoS流支持网络切片回退，目标RAN节点通过上述准入控制确定了是将该QoS流重映射到新的网络切片或回退到缺省网络切片。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片中的该QoS流重映射到的网络切片的标识，或指示将该QoS流回退到缺省网络切片。
源RAN节点接收到该QoS流重映射到的网络切片的标识或缺省网络切片标识后，通过比对该QoS流所属的源网络切片标识与目标RAN节点分配的重映射到的网络切片的标识，即可知道该QoS流需要进行重映射；或通过比对该QoS流所属的源网络切片标识与目标RAN节点指示的缺省网络切片标识，即可知道该QoS流需要进行回退。源RAN节点也可以接收该QoS流是否回退到缺省网络切片的指示，根据该指示，源RAN节点可以知道该QoS流需要回退到缺省网络切片。
S305、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。该第二消息可以是RRC消息。
具体实现时，在一种可能的实现中，可以由目标RAN节点生成一个容器，该容器内包括上述第一响应消息包括的内容。目标RAN节点将该容器发送给源RAN节点。源RAN节点不解析该容器里的信息，而是将该容器包含在RRC消息中转发给终端设备。
在另一种可能的实现中，源RAN节点解析第一响应消息后，将第一响应消息中的部分或全部信息包含在源RAN节点生成的RRC消息中，并将该RRC消息发送给终端设备。
终端设备接收到上述第二消息，该第二消息还可以包括至少一个PDU会话重映射到的网络切片的配置参数，或缺省网络切片的配置参数，则终端设备随机接入到目标RAN节点，根据该至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点进行通信，或，根据缺省网络切片的配置参数与目标RAN节点进行通信。
S306、目标RAN节点向核心网节点发送路径切换请求。
其中，该路径切换请求包括一个或多个QoS流中各个QoS流所重映射的网络切片的标识，或，该一个或多个QoS流中各个QoS流是否进行网络切片回退的指示。
目标RAN节点指示哪些QoS流需要进行重映射或回退。核心网节点根据该路径切换请求，修改对应的QoS流。具体地，修改该QoS流以使其在重映射的网络切片中继续进行， 或修改该QoS流以使其在缺省网络切片上继续进行。应理解，不同的网络切片具有不同的数据传输路径，因此，在网络切片重映射或回退时，该网络切片中的一个或多个QoS流的路径会发生变化。核心网节点通过修改一个QoS流的上下文来实现对该QoS流的路径改变。
S307、核心网节点向目标RAN节点发送路径切换响应。该路径切换响应包括以下信息中的一项或多项：路径切换成功的一个或多个QoS流的QoS流标识、路径切换失败的一个或多个QoS流的QoS流标识、修改后的一个或多个QoS流的上下文。
核心网节点将一个或多个QoS流路径切换的结果发送给目标RAN节点。该一个或多个QoS流路径切换的结果包括以下信息中的一项或多项：路径切换成功的一个或多个QoS流的QoS流标识、路径切换失败的一个或多个QoS流的QoS流标识、修改后的一个或多个QoS流的上下文。该QoS流修改的结果携带在路径切换响应中。
从而，经过上述处理，完成了终端设备切换时的网络侧流程。
另外，上述源RAN节点可能支持CU和DU分离的架构，目标RAN节点也可能支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息中的部分或全部信息。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的部分或全部信息，进行准入控制；以及向源RAN节点的CU发送第一响应消息的步骤。
上述源RAN节点可能不支持CU和DU分离的架构，而目标RAN节点支持CU和DU分离的架构，在这种情况下，由源RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及发送第二消息的步骤。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的部分或全部信息，进行准入控制，并向源RAN节点发送第一响应消息的步骤。
上述源RAN节点可能支持CU和DU分离的架构，而目标RAN节点可能不支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤；接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息的部分或全部信息。由目标RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及第一切换消息，进行准入控制，并向源RAN节点的CU发送第一响应消息的步骤。
根据本申请实施例提供的一种切换方法，在基于Xn接口的切换过程中，在切换消息中携带QoS流是否支持网络切片重映射的指示，和/或，QoS流是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
上述切换方法是基于Xn接口切换的，该切换方法还可以基于NG接口切换。如图6所示，为本申请实施例提供的又一种切换方法的流程示意图。该方法主要涉及基于NG接口切换的QoS流粒度的网络切片重映射或回退。示例性地，该方法可以包括以下流程：
S401、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息。
该步骤的具体实现可参考图3所示实施例的步骤S101的相关描述。
S402、源RAN节点向核心网节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片回退的指示QoS流。
相应地，核心网节点接收该第一切换消息。
具体地，该第一切换消息可以为切换需求消息。该切换需求消息用于指示源RAN节点需要进行切换。该切换需求消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个QoS流是否支持网络切片回退的指示QoS流。
该步骤的具体实现可参考图5所示实施例的步骤S302中的相关描述。
S403、核心网节点向目标RAN节点发送第二切换消息。
示例性地，源RAN节点根据UE上报的源RAN节点的相邻的一个或多个RAN节点的信号强度测量报告，在一个或多个RAN节点中确定目标RAN节点。上述第一切换消息还可以包括目标RAN节点的标识。核心网节点向目标RAN节点发送第二切换消息。
该第二切换消息的内容包含第一切换消息的部分或全部内容。
相应地，目标RAN节点接收该第二切换消息。
具体地，该第二切换消息可以为切换请求消息。该切换请求消息用于指示请求将源RAN节点的QoS流切换到目标RAN节点。
该步骤的具体实现可参考图5所示实施例的步骤S302中的相关描述。
S404、目标RAN节点根据第二切换消息，进行准入控制。
该准入控制用于QoS流确定是否对一个或多个QoS流进行网络切片重映射，并确定QoS流重映射到的网络切片的标识；或，该准入控制用于QoS流确定是否将一个或多个QoS流回退到缺省网络切片。
该步骤的具体实现可参考图5所示实施例的步骤S303的相关描述。
S405、目标RAN节点向核心网节点发送第二响应消息。
相应地，核心网节点接收该第二响应消息。
该第二响应消息为对第二切换消息的响应消息。具体地，该第二响应消息可以为切换请求应答消息。该切换请求应答消息为对上述切换请求消息的响应。
该步骤的具体实现可参考图5所示实施例的步骤S304中的相关描述。
S406、核心网节点向源RAN节点发送第一响应消息。
第一响应消息的内容可以包含第二响应消息的部分或全部内容。
具体地，该第二切换消息可以为切换命令。该切换命令用于指示源RAN节点将QoS流切换到目标RAN节点。具体地，用于指示源RAN节点将QoS流切换到重映射的网络切片或缺省网络切片。
该步骤的具体实现可参考图5所示实施例的步骤S304的相关描述。
S407、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。
该步骤的具体实现可参考图5所示实施例的步骤S305。
根据本申请实施例提供的一种切换方法，在基于NG接口的切换过程中，在切换消息中携带QoS流是否支持网络切片重映射的指示，和/或，QoS流是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
上述实施例描述了基于QoS流粒度的网络切片重映射或回退，接下来描述基于DRB粒度的网络切片重映射或回退。终端设备在与RAN节点通信时在空口使用不同的DRB来承载具有不同QoS特性的数据的传输，一个DRB使用一定的空口资源，终端设备的一个DRB对应的空口资源也是属于一个网络切片。因此，终端设备进行RAN节点切换时，还可能涉及DRB粒度的网络切片重映射或回退，即进行切换后，DRB对应的空口资源属于重映射的网络切片或缺省网络切片。其中，一个或多个QoS流映射到一个DRB上，也即一个DRB承载该一个或多个QoS流，在切换过程中，DRB和QoS流的映射关系保持不变。
如图7所示，为本申请实施例提供的一种切换方法的流程示意图。该流程主要涉及基于Xn接口切换的DRB粒度的网络切片重映射或回退。示例性地，该方法包括以下步骤：
S501、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息。
该步骤的具体实现可参考图3所示实施例的步骤S101或图5所示实施例的步骤S301的相关描述。
S502、源RAN节点向目标RAN节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片回退的指示。
相应地，目标RAN节点接收该第一切换消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一切换消息可以为切换请求消息。
在终端设备发生切换时，为了提高业务的连续性，属于源RAN节点的一个或多个源网络切片的DRB需要切换到目标RAN节点侧。然而，目标RAN节点支持的网络切片可能与源网络切片不同。终端设备进行切换后，DRB对应的空口资源可能不再属于源网络切片，而属于重映射的目标RAN节点支持的新的网络切片或缺省网络切片。源RAN节点对于每个属于源网络切片的DRB，需要指示该DRB是否支持网络切片重映射，和/或是否支持网络切片回退。值得说明的是，在申请实施例中，一个DRB对应的空口资源属于一个网络切片，也可称为该DRB属于该网络切片。
在源网络切片与DRB是一一对应的情况下，即一个源网络切片上当前只存在一个待切换的DRB，在一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和属于该一个或多个源网络切片中各个源网络切片的DRB是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示属于该源网络切片上的DRB是否支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和属于该一个或多个源网络切片中各个源网络切片的DRB是否支持网络切片回退的指示，即对于各个源网络切片标识，指示属于该源网络切片上的DRB是否支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，属于该一个或多个源网络切片中各个源网络切片的DRB是否支持网络切片重映射的指示和该DRB是否支持网络切片回退的指示，即对于各个源网络切片标识，指示该源网络切片上的DRB是否支持网络切片重映射和回退。
在另一种可能的实现中，该第一切换消息包括一个或多个源网络切片标识和属于该一个或多个源网络切片中各个源网络切片的DRB支持网络切片重映射的指示，即对于各个源网络切片标识，指示属于该源网络切片上的DRB支持网络切片重映射；或者，该第一切换消息包括一个或多个源网络切片标识和属于该一个或多个源网络切片中各个源网络切片的DRB支持网络切片回退的指示，即对于各个源网络切片标识，指示属于该源网络切片上的DRB支持网络切片回退；或者，该第一切换消息包括一个或多个源网络切片标识，属于该一个或多个源网络切片中各个源网络切片的DRB支持网络切片重映射的指示和该DRB支持网络切片回退的指示，即对于各个源网络切片标识，指示属于该源网络切片上的DRB支持网络切片重映射和回退。
在源网络切片与DRB是一对多的关系的情况下，即一个源网络切片上存在多个待切换到目标RAN节点的DRB，在一种可能的实现中，第一切换消息包括一个或多个源网络切片标识，属于该一个或多个源网络切片中各个源网络切片上的多个DRB的DRB标识以及其中部分或全部DRB标识对应的DRB是否支持网络切片重映射的指示，即对于各个源网络切片标识，指示属于该源网络切片上的多个DRB中的部分或全部DRB是否支持网络切片重映射；或者，第一切换消息包括一个或多个源网络切片标识，属于该一个或多个源网络切片中各个源网络切片上的多个DRB的DRB标识以及其中部分或全部DRB标识对应的DRB是否支持网络切片回退的指示，即对于各个源网络切片标识，指示属于该源网络切片上的多个DRB中的部分或全部DRB是否支持网络切片回退；或者第一切换消息包括一个或多个源网络切片标识，属于该一个或多个源网络切片中各个源网络切片上的多个DRB的DRB标识，以及其中部分或全部DRB标识对应的DRB是否支持网络切片重映射的指示和部分或全部DRB标识对应的DRB是否支持网络切片回退的指示，即对于每个源网络切片标识，指示属于该源网络切片上的各个DRB中的部分或全部DRB是否支持网络切片重映射和回退。
值得说明的是，指示一个DRB是否支持网络切片重映射和/或支持网络切片回退，通常包含该DRB的标识以及该DRB是否支持网络切片重映射和/或支持网络切片回退的指示信息。同样地，指示一个DRB支持网络切片重映射和/或支持网络切片回退，通常包含该DRB的标识以及该DRB支持网络切片重映射和/或支持网络切片回退的指示信息。应理解，该指示信息可以是一个1比特的指示信息，例如当该比特位取值为1时，表示支持网络切 片重映射和/或支持网络切片回退，当该比特位取值为0时，表示不支持网络切片重映射和/或支持网络切片回退。
S503、目标RAN节点根据第一切换消息，进行准入控制。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个DRB是否支持网络切片重映射的指示，则该准入控制用于确定是否对该一个或多个DRB进行网络切片重映射，并确定重映射到的网络切片的标识。具体地，对于属于该源网络切片的任意一个DRB，若第一切换消息包括该DRB支持网络切片重映射的指示，则目标RAN节点根据步骤S501中获取的该源网络切片标识对应的网络切片重映射信息，确定将属于该源网络切片上的该DRB重映射到新的网络切片。例如，属于源网络切片(slice#1)的一个DRB切换到目标RAN节点，然而，目标RAN节点并不支持slice#1，与slice#1对应的网络切片重映射信息包括slice#2和slice#3，则目标RAN节点可以根据策略(例如，基于目标RAN节点上的slice#2和slice#3各自的负载情况或者性能指标、或者切片的优先级等)将该DRB重映射到slice#2或slice#3；又例如，目标RAN节点支持slice#1，则该DRB可以属于目标RAN节点的slice#1，在目标RAN节点的slice#1负载过高时，也可以将slice#1重映射到slice#2或slice#3。若第一切换消息包括该DRB不支持网络切片重映射的指示，且目标RAN节点不支持slice#1，则目标RAN节点拒绝对属于该源网络切片上的该DRB的切换；或者第一切换消息包括该DRB不支持网络切片重映射的指示，且目标RAN节点支持slice#1，则该DRB可以属于目标RAN节点的slice#1。
对于第一切换消息中包含的一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个DRB是否支持网络切片回退的指示，则该准入控制用于确定是否将该一个或多个DRB回退到缺省网络切片。具体地，对于属于该源网络切片的任意一个DRB，若第一切换消息包括DRB支持网络切片回退的指示，则目标RAN节点根据步骤S501中获取的缺省网络切片信息，确定将属于该源网络切片的该DRB回退到缺省网络切片进行。若第一切换消息包括DRB不支持网络切片回退的指示，则目标RAN节点拒绝对属于该源网络切片的该DRB的切换。
类似地，对于第一切换消息中包含一个源网络切片标识，若第一切换消息还包括该源网络切片标识所对应的一个或多个DRB是否支持网络切片重映射的指示和是否支持网络切片回退的指示，则对于属于该源网络切片的任意一个DRB，目标RAN节点可以根据策略选择将该DRB重映射到S501中网络切片重映射信息包括的一个网络切片上，或者选择将该DRB回退到缺省网络切片上。
上述准入控制过程还需考虑目标RAN节点是否接受该DRB的无损数据转发需求，即DRB和QoS流的映射关系不能改变。
S504、目标RAN节点向源RAN节点发送第一响应消息。
相应地，源RAN节点接收该第一响应消息。
具体地，在本实施例的基于Xn接口切换流程中，该第一响应消息为切换请求应答消息。
在一种可能的实现中，第一切换消息包括属于一个源网络切片的一个DRB支持网络切片重映射的指示，目标RAN节点通过准入控制确定了将该DRB进行重映射，则第一响应 消息包括该源网络切片标识、该DRB标识和该DRB重映射到的网络切片的标识。即若该DRB支持网络切片重映射，目标RAN节点通过上述准入控制确定了该DRB重映射到的网络切片的标识。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片上的该DRB重映射到哪个网络切片。
在另一种可能的实现中，第一切换消息包括属于一个源网络切片的一个DRB是否支持网络切片重映射的指示。若属于该源网络切片的该DRB支持网络切片重映射，且目标RAN节点通过准入控制确定了将该DRB进行重映射，则第一响应消息包括的信息与上述实现相同。若属于该源网络切片的该DRB不支持网络切片重映射，则目标RAN节点拒绝对该DRB进行重映射，该DRB结束，则第一响应消息包括该源网络切片标识、该DRB标识和目标RAN节点拒绝对该DRB进行重映射的指示信息。
在又一种可能的实现中，第一切换消息包括属于一个源网络切片的一个DRB支持网络切片回退的指示，且目标RAN节点通过上述准入控制确定了将该DRB回退到缺省网络切片，则第一响应消息包括该源网络切片标识、该DRB标识和该DRB回退到缺省网络切片的指示，或者第一响应消息包括该源网络切片标识、该DRB标识和缺省网络切片标识。其中，该DRB回退到缺省网络切片的指示可以是1个比特的指示信息，例如，该比特值为“1”时，表示该DRB回退到缺省网络切片，由于源RAN节点和目标RAN节点是预先获取了缺省网络切片信息的，所以，在接收到该DRB回退到缺省网络切片的指示时，源RAN节点能够知晓回退到哪个网络切片；该比特值为“0”时，表示该DRB不进行回退，该DRB结束。即若该DRB支持网络切片回退，目标RAN节点通过上述准入控制确定了将该DRB回退到缺省网络切片。若确定将该DRB回退到缺省网络切片，则目标RAN节点通过第一响应消息告知源RAN节点该源网络切片上的该DRB回退到缺省网络切片。
在又一种可能的实现中，第一切换消息包括属于一个源网络切片的一个DRB是否支持网络切片回退的指示，若属于该源网络切片的该DRB支持网络切片回退，且目标RAN节点通过上述准入控制确定了将该DRB回退到缺省网络切片，则第一响应消息包括的信息与上述实现方式相同；若该源网络切片的该DRB不支持网络切片回退，则目标RAN节点拒绝对该DRB进行回退，该DRB中断，则第一响应消息包括该源网络切片标识、该DRB标识和目标RAN节点拒绝对该DRB进行回退的指示信息。
在又一种可能的实现中，第一切换消息包括属于一个源网络切片的一个DRB支持网络切片重映射的指示和支持网络切片回退的指示，则第一响应消息包括该源网络切片标识、该DRB标识和该DRB重映射到的网络切片的标识，或，第一响应消息包括该源网络切片标识、该DRB标识和该DRB回退到缺省网络切片的指示，或，第一响应消息包括该源网络切片标识、该DRB标识和缺省网络切片标识。若该DRB支持网络切片重映射，且该DRB支持网络切片回退，目标RAN节点通过上述准入控制确定了是将该DRB重映射到新的网络切片或回退到缺省网络切片。目标RAN节点通过第一响应消息告知源RAN节点该源网络切片中的该DRB重映射到的网络切片的标识，或指示将该DRB回退到缺省网络切片。
源RAN节点接收到该DRB重映射到的网络切片的标识或缺省网络切片标识后，通过比对该DRB所属的源网络切片标识与目标RAN节点分配的重映射到的网络切片的标识，即可知道该DRB需要进行重映射；或通过比对该DRB所属的源网络切片标识与目标RAN 节点指示的缺省网络切片标识，即可知道该DRB需要进行回退。源RAN节点也可以接收该DRB是否回退到缺省网络切片的指示，根据该指示，源RAN节点可以知道该DRB需要回退到缺省网络切片。
S505、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。该第二消息可以是RRC消息。
具体实现时，在一种可能的实现中，可以由目标RAN节点生成一个容器，该容器内包括上述第一响应消息包括的内容。目标RAN节点将该容器发送给源RAN节点。源RAN节点不解析该容器里的信息，而是将该容器包含在RRC消息中转发给终端设备。
在另一种可能的实现中，源RAN节点解析第一响应消息后，将第一响应消息中的部分或全部信息包含在源RAN节点生成的RRC消息中，并将该RRC消息发送给终端设备。
终端设备接收到上述第二消息，该第二消息还可以包括至少一个PDU会话重映射到的网络切片的配置参数，或缺省网络切片的配置参数，则终端设备随机接入到目标RAN节点，根据该至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点进行通信，或，根据缺省网络切片的配置参数与目标RAN节点进行通信。
从而，经过上述处理，完成了终端设备切换时的网络侧流程。
另外，上述源RAN节点可能支持CU和DU分离的架构，目标RAN节点也可能支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息中的部分或全部信息。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的部分或全部信息，进行准入控制；以及向源RAN节点的CU发送第一响应消息的步骤。
上述源RAN节点可能不支持CU和DU分离的架构，而目标RAN节点支持CU和DU分离的架构，在这种情况下，由源RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤，接收第一响应消息的步骤，以及发送第二消息的步骤。由目标RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，并DU根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及接收到的第一切换消息中的部分或全部信息，进行准入控制，并向源RAN节点发送第一响应消息的步骤。
上述源RAN节点可能支持CU和DU分离的架构，而目标RAN节点可能不支持CU和DU分离的架构，在这种情况下，由源RAN节点的CU执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，发送第一切换消息的步骤；接收第一响应消息的步骤，以及通过DU发送第二消息的步骤。该CU接收到第一响应消息后，向源RAN节点的DU转发该第一响应消息的部分或全部信息。由目标RAN节点执行上述获取网络切片重映射信息，和/或，缺省网络切片信息的步骤，接收第一切换消息的步骤，根据获取的网络切片重映射信息，和/或，缺省网络切片信息以及第一切换消息，进行准入控制，并向源RAN节点的CU发送第一响应消息的步骤。
如图8所示，以DRB粒度的网络切片重映射/回退为例，示例了目标RAN节点内CU与DU实现上述切换方法的流程。在步骤S601中，该CU获取到核心网节点或其它RAN节点发送的网络切片重映射信息，和/或缺省网络切片信息后，通过F1AP消息向DU发送获取到的网络切片重映射信息，和/或缺省网络切片信息。然后，在步骤S602中，CU在接收到源RAN节点发送的第一切换消息后，向DU发送UE上下文建立请求，该上下文建立请求包括：源网络切片标识，DRB是否支持网络切片重映射的指示和/或DRB是否支持网络切片回退的指示。DU根据上述指示，以及网络切片重映射信息和/或缺省网络切片信息，进行准入控制。在步骤S603中，DU向CU发送UE上下文建立响应，该UE上下文建立响应包括DRB重映射到的网络切片的标识，或，DRB是否回退到缺省网络切片的指示。
根据本申请实施例提供的一种切换方法，在基于Xn接口的切换过程中，在切换消息中携带DRB是否支持网络切片重映射的指示，和/或，DRB是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
上述切换方法是基于Xn接口切换的，该切换方法还可以基于NG接口切换。如图9所示，为本申请实施例提供的又一种切换方法的流程示意图。该方法主要涉及基于NG接口切换的DRB粒度的网络切片重映射或回退。示例性地，该方法可以包括以下流程：
S701、源RAN节点、目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息。
该步骤的具体实现可参考图7所示实施例的步骤S501的相关描述。
S702、源RAN节点向核心网节点发送第一切换消息，第一切换消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片回退的指示DRB。
相应地，核心网节点接收该第一切换消息。
具体地，该第一切换消息可以为切换需求消息。该切换需求消息用于指示源RAN节点需要进行切换。该切换需求消息包含一个或多个源网络切片标识，该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片重映射的指示，和/或该一个或多个源网络切片中各个源网络切片的一个或多个DRB是否支持网络切片回退的指示DRB。
该步骤的具体实现可参考图7所示实施例的步骤S502中的相关描述。
S703、核心网节点向目标RAN节点发送第二切换消息。
示例性地，源RAN节点根据UE上报的源RAN节点的相邻的一个或多个RAN节点的信号强度测量报告，在一个或多个RAN节点中确定目标RAN节点。上述第一切换消息还可以包括目标RAN节点的标识。核心网节点向目标RAN节点发送第二切换消息。
该第二切换消息的内容包含第一切换消息的部分或全部内容。
相应地，目标RAN节点接收该第二切换消息。
具体地，该第二切换消息可以为切换请求消息。该切换请求消息用于指示请求将源RAN节点的DRB切换到目标RAN节点。
该步骤的具体实现可参考图7所示实施例的步骤S702中的相关描述。
S704、目标RAN节点根据第二切换消息，进行准入控制。
该准入控制用于DRB确定是否对一个或多个DRB进行网络切片重映射，并确定DRB重映射到的网络切片的标识；或，该准入控制用于DRB确定是否将一个或多个DRB回退到缺省网络切片。
该步骤的具体实现可参考图7所示实施例的步骤S703的相关描述。
S705、目标RAN节点向核心网节点发送第二响应消息。
相应地，核心网节点接收该第二响应消息。
该第二响应消息为对第二切换消息的响应消息。具体地，该第二响应消息可以为切换请求应答消息。该切换请求应答消息为对上述切换请求消息的响应。
该步骤的具体实现可参考图7所示实施例的步骤S704中的相关描述。
S706、核心网节点向源RAN节点发送第一响应消息。
第一响应消息的内容可以包含第二响应消息的部分或全部内容。
具体地，该第二切换消息可以为切换命令。该切换命令用于指示源RAN节点将DRB切换到目标RAN节点。具体地，用于指示源RAN节点将DRB切换到重映射的网络切片或缺省网络切片。
该步骤的具体实现可参考图7所示实施例的步骤S704的相关描述。
S707、源RAN节点向终端设备发送第二消息。
相应地，终端设备接收该第二消息。
该步骤的具体实现可参考图7所示实施例的步骤S705。
根据本申请实施例提供的一种切换方法，在基于NG接口的切换过程中，在切换消息中携带DRB是否支持网络切片重映射的指示，和/或，DRB是否支持网络切片回退的指示，而无需携带整个网络切片重映射信息，和/或缺省网络切片信息，节省了切换交互过程中的信令开销。
基于上述切换方法的同一构思，如图10所示，本申请实施例还提供一种切换装置。该装置300包括：收发单元301和处理单元302，该处理单元302与该收发单元301耦合。
在一个实施例中，该装置300可以是图3～图4所示实施例中的终端设备。其中：
收发单元301，用于接收来自源RAN节点的第二消息；
其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
在一种可能的实现中，所述第二消息为无线资源控制RRC消息，在所述至少一个PDU会话进行重映射或回退的情况下，所述第二消息还包括所述至少一个PDU会话重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；
所述处理单元302用于通过所述收发单元301随机接入到目标RAN节点，根据所述至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点进行通信；或
所述处理单元302用于通过所述收发单元301随机接入到所述目标RAN节点,根据所述缺省网络切片的配置参数与目标RAN节点进行通信。
有关收发单元301和处理单元302的具体实现可参考图3～图4所示实施例中的终端设备的相关描述。
在另一个实施例中，该装置300可以是图5～图6所示实施例中的终端设备。其中：
收发单元301，用于接收来自源RAN节点的第二消息；
其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示。
在又一种可能的实现中，所述第二消息为无线资源控制RRC消息，在所述至少一个QoS流进行重映射或回退的情况下，所述第二消息还包括所述至少一个QoS流重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；
所述处理单元302用于通过所述收发单元301随机接入到目标RAN节点，根据所述至少一个QoS流重映射到的网络切片的配置参数与目标RAN节点进行通信；或
所述处理单元302用于通过所述收发单元301随机接入到所述目标RAN节点,根据所述缺省网络切片的配置参数与目标RAN节点进行通信。
有关收发单元301和处理单元302的具体实现可参考图5～图6所示实施例中的终端设备的相关描述。
在又一个实施例中，该装置300可以是图7～图9所示实施例中的终端设备。其中：
所述收发单元301，用于接收来自源RAN节点的第二消息；
其中，所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示。
在一种可能的实现中，所述第二消息为无线资源控制RRC消息，在所述至少一个DRB进行重映射或回退的情况下，所述第二消息还包括所述至少一个DRB重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；
所述处理单元302用于通过所述收发单元301随机接入到目标RAN节点，根据所述至少一个DRB重映射到的网络切片的配置参数与目标RAN节点进行通信；或
所述处理单元302用于通过所述收发单元301随机接入到所述目标RAN节点,根据所述缺省网络切片的配置参数与目标RAN节点进行通信。
有关收发单元301和处理单元302的具体实现可参考图7～图9所示实施例中的终端设备的相关描述。
在又一个实施例中，该装置300也可以是图3～图4所示实施例中的源RAN节点。其中：
处理单元302，用于生成第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
收发单元301，用于向第一网络节点发送所述第一切换消息；
所述收发单元301，还用于接收来自所述第一网络节点的第一响应消息；
其中，在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
在所述第一切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或
在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识；
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在一种可能的实现中，所述收发单元301，还用于接收来自核心网节点的PDU会话建立请求，所述PDU会话建立请求包括建立的PDU会话是否支持网络切片重映射的指示，和/或，所述建立的PDU会话是否支持网络切片回退的指示。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述收发单元301，还用于向所述目标RAN节点发送切换请求消息；
所述收发单元301，还用于接收来自所述目标RAN节点的切换请求应答消息；或
所述第一网络节点为核心网节点，所述收发单元301，还用于向所述核心网节点发送切换需求消息；
所述收发单元301，还用于接收来自所述核心网节点的切换命令。
在又一种可能的实现中，所述收发单元301，还用于向终端设备发送第二消息；
其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或
所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。
有关上述收发单元301和处理单元302的具体实现可参考图3～图4所示实施例中的源RAN节点的相关描述。
在又一个实施例中，该装置300也可以是图5～图6所示实施例中的源RAN节点。其中：
所述处理单元302，用于生成第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片回退的指示；
所述收发单元301，用于向第一网络节点发送所述第一切换消息；
所述收发单元301，还用于接收来自所述第一网络节点的第一响应消息；
其中，在所述第一切换消息包括所述QoS流是否支持网络切片重映射的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或
在所述第一切换消息包括所述QoS流是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示；或
在所述第一切换消息包括所述QoS流是否支持网络切片重映射的指示，以及所述QoS流是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或， 缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识；
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在一种可能的实现中，所述收发单元301，还用于接收来自核心网节点的QoS流建立请求，所述QoS流建立请求包括建立的QoS流是否支持网络切片重映射的指示，和/或，所述建立的QoS流是否支持网络切片回退的指示。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述收发单元301，还用于向所述目标RAN节点发送切换请求消息；
所述收发单元301，还用于接收来自所述目标RAN节点的切换请求应答消息；或
所述第一网络节点为核心网节点，所述收发单元301，还用于向所述核心网节点发送切换需求消息；
所述收发单元301，还用于接收来自所述核心网节点的切换命令。
在又一种可能的实现中，所述收发单元301，还用于向终端设备发送第二消息；
其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或
所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示；或
所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示。
有关上述收发单元301和处理单元302的具体实现可参考图5～图6所示实施例中的源RAN节点的相关描述。
在又一个实施例中，该装置300也可以是图7～图9所示实施例中的源RAN节点。其中：
所述处理单元302，用于生成第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片重映射的指示，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片回退的指示；
所述收发单元301，用于向第一网络节点发送所述第一切换消息；
所述收发单元301，还用于接收来自所述第一网络节点的第一响应消息；
其中，在所述第一切换消息包括所述DRB是否支持网络切片重映射的指示的情况下， 所述第一响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或
在所述第一切换消息包括所述DRB是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示；或
在所述第一切换消息包括所述DRB是否支持网络切片重映射的指示，以及所述DRB是否支持网络切片回退的指示的情况下，所述第一响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识，或，至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识；
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第一网络节点为目标RAN节点，所述收发单元301，还用于向所述目标RAN节点发送切换请求消息；
所述收发单元301，还用于接收来自所述目标RAN节点的切换请求应答消息；或
所述第一网络节点为核心网节点，所述收发单元301，还用于向所述核心网节点发送切换需求消息；
所述收发单元301，还用于接收来自所述核心网节点的切换命令。
在又一种可能的实现中，所述收发单元301，还用于向终端设备发送第二消息；
其中，所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或
所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示；或
所述第二消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识，或，至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示。
有关上述收发单元301和处理单元302的具体实现可参考图7～图9所示实施例中的源 RAN节点的相关描述。
在又一个实施例中，该装置300可以是图3～图4所示实施例中的目标RAN节点。其中：
收发单元301，用于接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
处理单元302，用于根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个PDU会话回退到缺省网络切片；
所述收发单元301，还用于向所述第二网络节点发送第二响应消息；
其中，在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
在所述第二切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或
在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括缺省网络切片的标识。
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述收发单元301，还用于接收来自源RAN节点的切换请求消息；
所述收发单元301，还用于向所述源RAN节点发送切换请求应答消息；或
所述第二网络节点为核心网节点，所述收发单元301，还用于接收来自所述核心网节点的所述切换请求消息；
所述收发单元301，还用于向所述核心网节点发送所述切换请求响应消息。
在又一种可能的实现中，所述收发单元301，还用于向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个PDU会话中各个PDU会话所属的网络切片标识，或，所述路径切换请求包括所述至少一个PDU会话中各个PDU会话是否进行网络切片回退的指示；
所述收发单元301，还用于接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的一项或多项：路径切换成功的至少一个PDU会话的PDU会话标识、路径切换失败的所述至少一个PDU会话的PDU会话标识、修改后的至少一个PDU会话的上下文。
有关上述收发单元301和处理单元302的具体实现可参考图3～图4所示实施例中的目标RAN节点的相关描述。
在又一个实施例中，该装置300可以是图5～图6所示实施例中的目标RAN节点。其中：
收发单元301，用于接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个QoS流是否支持网络切片回退的指示；
处理单元302，用于根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个QoS流进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个QoS流回退到缺省网络切片；
所述收发单元301，还用于向所述第二网络节点发送第二响应消息；
其中，在所述第二切换消息包括所述QoS流是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识；或
在所述第二切换消息包括所述QoS流是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到所述缺省网络切片的指示；或
在所述第二切换消息包括所述QoS流是否支持网络切片重映射的指示，以及所述QoS流是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个QoS流的标识，所述至少一个QoS流中部分或全部QoS流是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源 网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括缺省网络切片的标识。
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述收发单元301，还用于接收来自源RAN节点的切换请求消息；
所述收发单元301，还用于向所述源RAN节点发送切换请求应答消息；或
所述第二网络节点为核心网节点，所述收发单元301，还用于接收来自所述核心网节点的所述切换请求消息；
所述收发单元301，还用于向所述核心网节点发送所述切换请求响应消息。
在又一种可能的实现中，所述收发单元301，还用于向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个QoS流中各个QoS流所属的网络切片标识，或，所述路径切换请求包括所述至少一个QoS流中各个QoS流是否进行网络切片回退的指示；
所述收发单元301，还用于接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的一项或多项：路径切换成功的至少一个QoS流的QoS流标识、路径切换失败的所述至少一个QoS流的QoS流标识、修改后的至少一个QoS流的上下文。
有关上述收发单元301和处理单元302的具体实现可参考图5～图6所示实施例中的目标RAN节点的相关描述。
在又一个实施例中，该装置300可以是图7～图9所示实施例中的目标RAN节点。其中：
收发单元301，用于接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片重映射的指示，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB是否支持网络切片回退的指示；
处理单元302，用于根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个DRB进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个DRB回退到缺省网络切片；
所述收发单元301，还用于向所述第二网络节点发送第二响应消息；
其中，在所述第二切换消息包括所述DRB是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识；或
在所述第二切换消息包括所述DRB是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到所述缺省网络切片的指示；或
在所述第二切换消息包括所述DRB是否支持网络切片重映射的指示，以及所述DRB 是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB重映射到的网络切片的标识，或，至少一个源网络切片标识，属于所述至少一个源网络切片中各个源网络切片的至少一个DRB的标识，所述至少一个DRB中部分或全部DRB是否回退到缺省网络切片的指示。
在一种可能的实现中，所述收发单元301，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括缺省网络切片的标识。
在又一种可能的实现中，所述收发单元301，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
在又一种可能的实现中，所述第二网络节点为源RAN节点，所述收发单元301，还用于接收来自源RAN节点的切换请求消息；
所述收发单元301，还用于向所述源RAN节点发送切换请求应答消息；或
所述第二网络节点为核心网节点，所述收发单元301，还用于接收来自所述核心网节点的所述切换请求消息；
所述收发单元301，还用于向所述核心网节点发送所述切换请求响应消息。
有关上述收发单元301和处理单元302的具体实现可参考图7～图9所示实施例中的目标RAN节点的相关描述。
在又一个实施例中，该装置300也可以是图3～图4所示实施例中的核心网节点。其中：
收发单元301，用于接收目标RAN节点的路径切换请求，所述路径切换请求包括至少一个PDU会话中各个PDU会话所属的网络切片标识，或，所述路径切换请求包括所述至少一个PDU会话中各个PDU会话是否进行网络切片回退的指示；
处理单元302，用于根据所述路径切换请求，修改所述至少一个PDU会话中各个PDU会话；
所述收发单元301，还用于向所述目标RAN节点发送路径切换响应，所述路径切换响应包括以下信息中的一项或多项：路径切换成功的至少一个PDU会话的PDU会话标识、路径切换失败的所述至少一个PDU会话的PDU会话标识、修改后的至少一个PDU会话的上下文。
有关上述收发单元301和处理单元302的具体实现可参考图3～图4所示实施例中的核心网节点的相关描述。
在又一个实施例中，该装置300也可以是图5～图6所示实施例中的核心网节点。其中：
收发单元301，用于接收目标RAN节点的路径切换请求，所述路径切换请求包括至少一个QoS流中各个QoS流所属的网络切片标识，或，所述路径切换请求包括所述至少一个QoS流中各个QoS流是否进行网络切片回退的指示；
处理单元302，用于根据所述路径切换请求，修改所述至少一个QoS流中各个QoS流；
所述收发单元301，还用于向所述目标RAN节点发送路径切换响应，所述路径切换响 应包括以下信息中的一项或多项：路径切换成功的至少一个QoS流的QoS流标识、路径切换失败的所述至少一个QoS流的QoS流标识、修改后的至少一个QoS流的上下文。
有关上述收发单元301和处理单元302的具体实现可参考图5～图6所示实施例中的核心网节点的相关描述。
图11为本申请实施例所述的切换装置可能的产品形态的结构图。
在一个实施例中，该切换装置为终端设备。
作为一种可能的产品形态，该切换装置可以为信息传输设备，该信息传输设备包括收发器403；所述收发器403，用于支持信息传输设备执行图3所示实施例的步骤S105，或，所述收发器403，用于支持信息传输设备执行图4所示实施例的步骤S207，或，所述收发器403，用于支持信息传输设备执行图5所示实施例的步骤S305，或，所述收发器403，用于支持信息传输设备执行图6所示实施例的步骤S407，或，所述收发器403，用于支持信息传输设备执行图3所示实施例的步骤S505，或，所述收发器403，用于支持信息传输设备执行图9所示实施例的步骤S707，或，所述收发器403还用于支持信息传输设备随机接入到目标RAN节点，根据至少一个PDU会话重映射到的网络切片的配置参数或缺省网络切片的配置参数与目标RAN节点通信。可选地，所述信息传输设备还可以包括存储器401和处理器402。
作为另一种可能的产品形态，该切换装置可以为信息传输单板，该信息传输单板包括收发器403；所述收发器403，用于支持信息传输单板执行图3所示实施例的步骤S105，或，所述收发器403，用于支持信息传输单板执行图4所示实施例的步骤S207，或，所述收发器403，用于支持信息传输单板执行图5所示实施例的步骤S305，或，所述收发器403，用于支持信息传输单板执行图6所示实施例的步骤S407，或，所述收发器403，用于支持信息传输单板执行图3所示实施例的步骤S505，或，所述收发器403，用于支持信息传输单板执行图9所示实施例的步骤S707，或，所述收发器403还用于支持信息传输单板随机接入到目标RAN节点，根据至少一个PDU会话重映射到的网络切片的配置参数或缺省网络切片的配置参数与目标RAN节点通信。可选地，所述信息传输单板还可以包括存储器401和处理器402。
作为又一种可能的产品形态，该切换装置也由通用处理器来实现，即俗称的芯片来实现。该通用处理器包括：处理电路402和通信接口403；可选地，该通用处理器还可以包括存储介质401。
作为另一种可能的产品形态，通信装置也可以使用下述来实现：一个或多个现场可编程门阵列(field programmable gate array，FPGA)、可编程逻辑器件(programmble logic device，PLD)、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
在另一个实施例中，该切换装置为源RAN节点。
作为一种可能的产品形态，该切换装置可以为信息传输设备，该信息传输设备包括收发器403；所述收发器403，用于支持信息传输设备执行图3所示实施例中的步骤S101、S102、S104和S105；或，所述收发器403，用于支持信息传输设备执行图4所示实施例的步骤S201、S202、S206和S207；或，所述收发器403，用于支持信息传输设备执行图5 所示实施例中的步骤S301、S302、S304和S305；或，所述收发器403，用于支持信息传输设备执行图6所示实施例的步骤S401、S402、S406和S407；或，所述收发器403，用于支持信息传输设备执行图7所示实施例中的步骤S501、S502、S504和S505；或，所述收发器403，用于支持信息传输设备执行图9所示实施例的步骤S701、S702、S706和S707。可选地，所述信息传输设备还可以包括存储器401和处理器402。
作为另一种可能的产品形态，该切换装置可以为信息传输单板，该信息传输单板包括收发器403；所述收发器403，用于支持信息传输单板执行图3所示实施例中的步骤S101、S102、S104和S105；或，所述收发器403，用于支持信息传输单板执行图4所示实施例的步骤S201、S202、S206和S207；或，所述收发器403，用于支持信息传输单板执行图5所示实施例中的步骤S301、S302、S304和S305；或，所述收发器403，用于支持信息传输单板执行图6所示实施例的步骤S401、S402、S406和S407；或，所述收发器403，用于支持信息传输单板执行图7所示实施例中的步骤S501、S502、S504和S505；或，所述收发器403，用于支持信息传输单板执行图9所示实施例的步骤S701、S702、S706和S707。可选地，所述信息传输单板还可以包括存储器401和处理器402。
作为又一种可能的产品形态，该切换装置也由通用处理器来实现，即俗称的芯片来实现。该通用处理器包括：处理电路402和通信接口403；可选地，该通用处理器还可以包括存储介质401。
作为另一种可能的产品形态，通信装置也可以使用下述来实现：一个或多个FPGA、PLD、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
在又一个实施例中，该切换装置为目标RAN节点。
作为一种可能的产品形态，该切换装置可以为信息传输设备，该信息传输设备包括处理器402和收发器403；所述处理器402，用于对信息传输设备的动作进行控制管理，例如，用于支持信息传输设备执行图3所示实施例的步骤S103，或，用于支持信息传输设备执行图4所示实施例的步骤S204，或，用于支持信息传输设备执行图5所示实施例的步骤S303，或，用于支持信息传输设备执行图6所示实施例的步骤S404，或，用于支持信息传输设备执行图7所示实施例的步骤S503，或，用于支持信息传输设备执行图9所示实施例的步骤S704；所述收发器403，用于支持信息传输设备执行执行图3所示实施例的步骤S101、S102、S104、S106和S107，或，所述收发器403，用于支持信息传输设备执行执行图4所示实施例的步骤S201、S203、S205，或，所述收发器403，用于支持信息传输设备执行执行图5所示实施例的步骤S301、S302、S304、S306和S307，或，所述收发器403，用于支持信息传输设备执行执行图6所示实施例的步骤S401、S403、S405，或，所述收发器403，用于支持信息传输设备执行执行图7所示实施例的步骤S501、S502、S504，或，所述收发器403，用于支持信息传输设备执行执行图9所示实施例的步骤S701、S703、S705。可选地，所述信息传输设备还可以包括存储器401。
作为另一种可能的产品形态，该切换装置可以为信息传输单板，该信息传输单板包括包括处理器402和收发器403；所述处理器402，用于对信息传输单板的动作进行控制管理，例如，用于支持信息传输单板执行图3所示实施例的步骤S103，或，用于支持信息传输单 板执行图4所示实施例的步骤S204，或，用于支持信息传输单板执行图5所示实施例的步骤S303，或，用于支持信息传输单板执行图6所示实施例的步骤S404，或，用于支持信息传输单板执行图7所示实施例的步骤S503，或，用于支持信息传输单板执行图9所示实施例的步骤S704；所述收发器403，用于支持信息传输设备执行执行图3所示实施例的步骤S101、S102、S104、S106和S107，或，所述收发器403，用于支持信息传输设备执行执行图4所示实施例的步骤S201、S203、S205，或，所述收发器403，用于支持信息传输设备执行执行图5所示实施例的步骤S301、S302、S304、S306和S307，或，所述收发器403，用于支持信息传输设备执行执行图6所示实施例的步骤S401、S403、S405，或，所述收发器403，用于支持信息传输设备执行执行图7所示实施例的步骤S501、S502、S504，或，所述收发器403，用于支持信息传输设备执行执行图9所示实施例的步骤S701、S703、S705。可选地，所述信息传输单板还可以包括存储器401。
作为又一种可能的产品形态，该切换装置也由通用处理器来实现，即俗称的芯片来实现。该通用处理器包括：处理电路402和通信接口403；可选地，该通用处理器还可以包括存储介质401。
作为另一种可能的产品形态，通信装置也可以使用下述来实现：一个或多个FPGA、PLD、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
在另一个实施例中，该切换装置为核心网节点。
作为一种可能的产品形态，该切换装置可以为信息传输设备，该信息传输设备包括收发器403；所述收发器403，用于支持信息传输设备执行图3所示实施例的步骤S106和S107，或，所述收发器403，用于支持信息传输设备执行图4所示实施例的步骤S202、S203、S205和S206，或，所述收发器403，用于支持信息传输设备执行图5所示实施例的步骤S306和S307，或，所述收发器403，用于支持信息传输设备执行图6所示实施例的步骤S402、S403、S405和S406，或，所述收发器403，用于支持信息传输设备执行图9所示实施例的步骤S702、S703、S705和S706。可选地，所述信息传输设备还可以包括存储器401和处理器402。
作为另一种可能的产品形态，该切换装置可以为信息传输单板，该信息传输单板包括收发器403；所述收发器403，用于支持信息传输单板执行图3所示实施例的步骤S106和S107，或，所述收发器403，用于支持信息传输单板执行图4所示实施例的步骤S202、S203、S205和S206，或，所述收发器403，用于支持信息传输单板执行图5所示实施例的步骤S306和S307，或，所述收发器403，用于支持信息传输单板执行图6所示实施例的步骤S402、S403、S405和S406，或，所述收发器403，用于支持信息传输单板执行图9所示实施例的步骤S702、S703、S705和S706。可选地，所述信息传输单板还可以包括存储器401和处理器402。
作为又一种可能的产品形态，该切换装置也由通用处理器来实现，即俗称的芯片来实现。该通用处理器包括：处理电路402和通信接口403；可选地，该通用处理器还可以包括存储介质401。
作为另一种可能的产品形态，通信装置也可以使用下述来实现：一个或多个FPGA、 PLD、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
上述处理器402可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。总线404可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可选的，本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
可选的，本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被切换装置执行时，使得该切换装置执行上述任一方法实施例中的方法。
可选的，本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得切换装置执行上述任一方法实施例中的方法。
可选的，本申请实施例还提供一种通信系统，该通信系统包括上述的切换装置。
可以理解的是，以上各个实施例中，由终端设备实现的方法和/或步骤，也可以由可用于终端设备的部件(例如芯片或者电路)实现；由源RAN节点实现的方法和/或步骤，也可以由可用于源RAN节点的部件(例如芯片或者电路)实现；由目标RAN节点实现的方法和/或步骤，也可以由可用于目标RAN节点的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应地，本申请实施例还提供了切换装置，该切换装置用于实现上述各种方法。该切换装置可以为上述方法实施例中的终端设备，或者包含上述终端设备的装置，或者为可用于终端设备的部件；或者，该切换装置可以为上述方法实施例中的源RAN节点，或者包含上述源RAN节点的装置，或者为可用于源RAN节点的部件；或者，该切换装置可以为上述方法实施例中的目标RAN节点，或者包含上述目标RAN节点的装置，或者为可用于目标RAN节点的部件。可以理解的是，该切换装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对切换装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。 需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
需要说明的是，以上单元或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一单元或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于片上系统(system on chip，SoC)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、可编程逻辑器件(programmable logic device，PLD)、或者实现专用逻辑运算的逻辑电路。
当以上单元或单元以硬件实现的时候，该硬件可以是中央处理单元(central processing unit，CPU)、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
应理解，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。

Claims (37)

  1. 一种切换方法，其特征在于，所述方法包括：
    终端设备接收来自源无线接入网RAN节点的第二消息；
    其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
  2. 根据权利要求1所述的方法，其特征在于，所述第二消息为无线资源控制RRC消息，在所述至少一个PDU会话进行重映射或回退的情况下，所述第二消息还包括所述至少一个PDU会话重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；
    所述方法还包括：
    所述终端设备随机接入到目标RAN节点，根据所述至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点通信；或
    所述终端设备随机接入到所述目标RAN节点，根据所述缺省网络切片的配置参数与所述目标RAN节点进行通信。
  3. 一种切换方法，其特征在于，所述方法包括：
    源无线接入网RAN节点向第一网络节点发送第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
    所述源RAN节点接收来自所述第一网络节点的第一响应消息；
    其中，在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    在所述第一切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示；或
    在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源 网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
  5. 根据权利要求4所述的方法，其特征在于，所述源RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：
    所述源RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
  6. 根据权利要求3～5中任一项所述的方法，其特征在于，所述源RAN节点向第一网络节点发送第一切换消息之前，所述方法还包括：
    所述源RAN节点接收来自核心网节点的所述至少一个PDU会话建立请求，所述至少一PDU会话建立请求包括建立的所述至少一个PDU会话是否支持网络切片重映射的指示，和/或，所述建立的至少一个PDU会话是否支持网络切片回退的指示。
  7. 根据权利要求3～6中任一项所述的方法，其特征在于：
    所述第一网络节点为目标RAN节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述目标RAN节点发送切换请求消息；
    所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述目标RAN节点的切换请求应答消息；或
    所述第一网络节点为核心网节点，所述源RAN节点向第一网络节点发送第一切换消息，包括：所述源RAN节点向所述核心网节点发送切换需求消息；
    所述源RAN节点接收来自所述第一网络节点的第一响应消息，包括：所述源RAN节点接收来自所述核心网节点的切换命令。
  8. 根据权利要求3～7中任一项所述的方法，其特征在于，所述方法还包括：
    所述源RAN节点向终端设备发送第二消息；
    其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络 切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。
  9. 一种切换方法，其特征在于，所述方法包括：
    目标无线接入网RAN节点接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
    所述目标RAN节点根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个PDU会话回退到缺省网络切片；
    所述目标RAN节点向所述第二网络节点发送第二响应消息；
    其中，在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    在所述第二切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或
    在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
  11. 根据权利要求10所述的方法，其特征在于，所述目标RAN节点获取网络切片重映射信息，和/或，缺省网络切片信息，包括：
    所述目标RAN节点接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
  12. 根据权利要求9～11中任一项所述的方法，其特征在于，
    所述第二网络节点为源RAN节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述源RAN节点的切换请求消息；
    所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述源RAN节点发送切换请求应答消息；或
    所述第二网络节点为核心网节点，所述目标RAN节点接收来自第二网络节点的第二切换消息，包括：所述目标RAN节点接收来自所述核心网节点的所述切换请求消息；
    所述目标RAN节点向所述第二网络节点发送第二响应消息，包括：所述目标RAN节点向所述核心网节点发送所述切换请求响应消息。
  13. 根据权利要求9～12中任一项所述的方法，其特征在于，所述方法还包括：
    所述目标RAN节点向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个PDU会话中各个PDU会话所属的网络切片的标识，或，所述路径切换请求包括所述至少一个PDU会话中各个PDU会话是否进行网络切片回退的指示；
    所述目标RAN节点接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的至少一项：路径切换成功的至少一个PDU会话的PDU会话标识、路径切换失败的所述至少一个PDU会话的PDU会话标识、修改后的至少一个PDU会话的上下文。
  14. 一种切换装置，其特征在于，所述装置包括：
    收发单元，用于接收来自源无线接入网RAN节点的第二消息；
    其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
  15. 根据权利要求14所述的装置，其特征在于，所述第二消息为无线资源控制RRC消息，在所述至少一个PDU会话进行重映射或回退的情况下，所述第二消息还包括所述至少一个PDU会话重映射到的网络切片的配置参数，或所述缺省网络切片的配置参数；
    所述装置还包括处理单元，所述处理单元与所述收发单元耦合；
    所述处理单元，用于通过所述收发单元随机接入到目标RAN节点，根据所述至少一个PDU会话重映射到的网络切片的配置参数与目标RAN节点进行通信；或
    所述处理单元，用于通过所述收发单元随机接入到所述目标RAN节点，根据所述缺省网络切片的配置参数与所述目标RAN节点进行通信。
  16. 一种切换装置，其特征在于，所述装置包括：处理单元和收发单元，所述收发单元与所述处理单元耦合；
    所述处理单元，用于生成第一切换消息，所述第一切换消息包括：至少一个源网络切片标识，所述第一切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
    所述收发单元，用于向第一网络节点发送所述第一切换消息；
    所述收发单元，还用于接收来自所述第一网络节点的第一响应消息；
    其中，在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    在所述第一切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示；或
    在所述第一切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第一响应消息包括所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，所述至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。
  17. 根据权利要求16所述的装置，其特征在于，所述收发单元，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的可重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
  18. 根据权利要求17所述的装置，其特征在于，所述收发单元，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
  19. 根据权利要求16～18中任一项所述的装置，其特征在于，所述收发单元，还用于接收来自核心网节点的所述至少一个PDU会话建立请求，所述至少一PDU会话建立请求包括建立的所述至少一个PDU会话是否支持网络切片重映射的指示，和/或，所述建立的至少一个PDU会话是否支持网络切片回退的指示。
  20. 根据权利要求16～19中任一项所述的装置，其特征在于：
    所述第一网络节点为目标RAN节点，所述收发单元，还用于向所述目标RAN节点发送切换请求消息；
    所述收发单元，还用于接收来自所述目标RAN节点的切换请求应答消息；或
    所述第一网络节点为核心网节点，所述收发单元，还用于向所述核心网节点发送切换需求消息；
    所述收发单元，还用于接收来自所述核心网节点的切换命令。
  21. 根据权利要求16～20中任一项所述的装置，其特征在于，所述收发单元，还用于向终端设备发送第二消息；
    其中，所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    所述第二消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示。
  22. 一种切换装置，其特征在于，所述装置包括：收发单元和处理单元，所述处理单元与所述收发单元耦合；
    所述收发单元，用于接收来自第二网络节点的第二切换消息，所述第二切换消息包括：至少一个源网络切片标识，所述第二切换消息还包括以下至少一项：所述至少一个源网络切片中各个源网络切片的至少一个协议数据单元PDU会话是否支持网络切片重映射的指示，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话是否支持网络切片回退的指示；
    所述处理单元，用于根据所述第二切换消息，进行准入控制，所述准入控制用于确定是否对所述至少一个PDU会话进行网络切片重映射，并确定重映射到的网络切片的标识；或，所述准入控制用于确定是否将所述至少一个PDU会话回退到缺省网络切片；
    所述收发单元，还用于向所述第二网络节点发送第二响应消息；
    其中，在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识；或
    在所述第二切换消息包括所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话是否回退到所述缺省网络切片的指示；或
    在所述第二切换消息包括所述PDU会话是否支持网络切片重映射的指示，以及所述PDU会话是否支持网络切片回退的指示的情况下，所述第二响应消息包括至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识，所述至少一个PDU会话中部分或全部PDU会话重映射到的网络切片的标识，或，至少一个源网络切片标识，所述至少一个源网络切片中各个源网络切片的至少一个PDU会话的标识， 所述至少一个PDU会话中部分或全部PDU会话是否回退到缺省网络切片的指示。
  23. 根据权利要求22所述的装置，其特征在于，所述收发单元，还用于获取网络切片重映射信息，和/或，缺省网络切片信息，所述网络切片重映射信息包括至少一个源网络切片标识，以及每个源网络切片标识对应的重映射的网络切片标识，所述缺省网络切片信息包括所述缺省网络切片的标识。
  24. 根据权利要求23所述的装置，其特征在于，所述收发单元，还用于接收第一消息，所述第一消息包括所述网络切片重映射信息，和/或，所述缺省网络切片信息。
  25. 根据权利要求22～24中任一项所述的装置，其特征在于，
    所述第二网络节点为源RAN节点，所述收发单元，还用于接收来自所述源RAN节点的切换请求消息；
    所述收发单元，还用于向所述源RAN节点发送切换请求应答消息；或
    所述第二网络节点为核心网节点，所述收发单元，还用于接收来自所述核心网节点的所述切换请求消息；
    所述收发单元，还用于向所述核心网节点发送所述切换请求响应消息。
  26. 根据权利要求22～25中任一项所述的装置，其特征在于：
    所述收发单元，还用于向所述核心网节点发送路径切换请求，所述路径切换请求包括至少一个PDU会话中各个PDU会话所属的网络切片标识，或，所述路径切换请求包括所述至少一个PDU会话中各个PDU会话是否进行网络切片回退的指示；
    所述收发单元，还用于接收来自所述核心网节点的路径切换响应，所述路径切换响应包括以下信息中的至少一项：路径切换成功的至少一个PDU会话的PDU会话标识、路径切换失败的所述至少一个PDU会话的PDU会话标识、修改后的至少一个PDU会话的上下文。
  27. 一种切换装置，其特征在于，包括：处理器，用于执行存储器中存储的程序，当所述程序被执行时，使得所述切换装置执行如权利要求1或2所述的方法。
  28. 根据权利要求27所述的切换装置，其特征在于，所述存储器位于所述切换装置之外。
  29. 一种切换装置，其特征在于，包括：处理器，用于执行存储器中存储的程序，当所述程序被执行时，使得所述切换装置执行如权利要求3～8中任一项所述的方法。
  30. 根据权利要求29所述的切换装置，其特征在于，所述存储器位于所述切换装置之外。
  31. 一种切换装置，其特征在于，包括：处理器，用于执行存储器中存储的程序，当所述程序被执行时，使得所述切换装置执行如权利要求9～13中任一项所述的方法。
  32. 根据权利要求31所述的切换装置，其特征在于，所述存储器位于所述切换装置之外。
  33. 一种切换装置，其特征在于，所述切换装置包括处理器、存储器以及存储在存储器上并可在处理器上运行的计算机程序(指令)，当所述计算机程序被运行时，执行如权利要求1或2所述的方法。
  34. 一种切换装置，其特征在于，所述切换装置包括处理器、存储器以及存储在存储器上并可在处理器上运行的计算机程序(指令)，当所述计算机程序被运行时，执行如权利要求3～8中任一项所述的方法。
  35. 一种切换装置，其特征在于，所述切换装置包括处理器、存储器以及存储在存储器上并可在处理器上运行的计算机程序(指令)，当所述计算机程序被运行时，执行如权利要求9～13中任一项所述的方法。
  36. 一种计算机可读存储介质，其特征在于，存储有计算机程序(指令)，当其在计算机上运行时，如权利要求1～13中任一项所述的方法。
  37. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得权利要求1～13中任一项所述的方法被执行。
PCT/CN2021/078307 2020-05-30 2021-02-27 一种切换方法及装置 WO2021244078A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21817557.8A EP4152821A4 (en) 2020-05-30 2021-02-27 CELLULAR TRANSFER METHOD AND APPARATUS
US17/994,292 US20230098982A1 (en) 2020-05-30 2022-11-26 Handover method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010480982.4A CN113747522A (zh) 2020-05-30 2020-05-30 一种切换方法及装置
CN202010480982.4 2020-05-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/994,292 Continuation US20230098982A1 (en) 2020-05-30 2022-11-26 Handover method and apparatus

Publications (1)

Publication Number Publication Date
WO2021244078A1 true WO2021244078A1 (zh) 2021-12-09

Family

ID=78727856

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/078307 WO2021244078A1 (zh) 2020-05-30 2021-02-27 一种切换方法及装置

Country Status (4)

Country Link
US (1) US20230098982A1 (zh)
EP (1) EP4152821A4 (zh)
CN (1) CN113747522A (zh)
WO (1) WO2021244078A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924884A (zh) * 2017-04-04 2018-11-30 华为技术有限公司 通信方法及通信设备
US20190037409A1 (en) * 2016-02-16 2019-01-31 Idac Holdings, Inc. Network slicing operation
CN110035461A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 通信方法、接入网设备和终端设备
CN110754114A (zh) * 2017-06-19 2020-02-04 夏普株式会社 终端装置以及核心网装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108024253B (zh) * 2016-11-04 2021-04-09 华为技术有限公司 一种通信方法以及终端、接入网设备、核心网设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190037409A1 (en) * 2016-02-16 2019-01-31 Idac Holdings, Inc. Network slicing operation
CN108924884A (zh) * 2017-04-04 2018-11-30 华为技术有限公司 通信方法及通信设备
CN110754114A (zh) * 2017-06-19 2020-02-04 夏普株式会社 终端装置以及核心网装置
CN110035461A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 通信方法、接入网设备和终端设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP4152821A4
ZTE: "Further Discussion and 38.300 TP on Slice Aware Mobility", 3GPP DRAFT; R3-181687 FURTHER DISCUSSION AND 38.300 TP ON SLICE AWARE MOBILITY V3, vol. RAN WG3, 5 April 2018 (2018-04-05), Sanya, China, pages 1 - 5, XP051416599 *

Also Published As

Publication number Publication date
CN113747522A (zh) 2021-12-03
EP4152821A4 (en) 2023-11-01
EP4152821A1 (en) 2023-03-22
US20230098982A1 (en) 2023-03-30

Similar Documents

Publication Publication Date Title
US11576080B2 (en) Radio access network node, core network node, radio terminal, and methods therefor
JP2020511892A (ja) 情報伝送方法およびネットワークデバイス
US20230156564A1 (en) Communication path switching method, apparatus, and system
US20230156848A1 (en) Communication method applied to integrated access and backhaul iab system and communication apparatus
KR20210055774A (ko) 통신 방법 및 장치
WO2020098747A1 (zh) 传输路径的配置方法及装置
US20230171651A1 (en) Logical channel lch configuration method, communication apparatus, and communication system
WO2021097858A1 (zh) 一种通信方法及装置
CN113709908A (zh) 数据传输的方法和装置
WO2021226967A1 (zh) 切换的方法和设备
EP2883372B1 (en) Methods and apparatuses of bearer grouping for data transmission in a broadband wireless network
US10944625B2 (en) Bearer configuration method and related products
WO2021244078A1 (zh) 一种切换方法及装置
WO2021208813A1 (zh) 一种通信方法及通信装置
EP3823387B1 (en) Information indicating method and apparatus
WO2021097678A1 (zh) 一种接入回传控制方法及装置
CN115804241A (zh) 无线通信方法、网络节点以及设备
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2023236224A1 (zh) 迁移方法和装置
WO2023142981A1 (zh) 通信方法及相关装置
WO2024007878A1 (zh) 通信方法及装置
US20240056926A1 (en) Communication method and apparatus for obtaining load information
WO2022165721A1 (zh) Ran域的模型共享方法及装置
WO2022016338A1 (zh) 一种通信方法及装置
WO2024027636A1 (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: 21817557

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021817557

Country of ref document: EP

Effective date: 20221212

NENP Non-entry into the national phase

Ref country code: DE