WO2019029674A1 - 通信方法及源基站、目标基站、核心网设备、终端设备 - Google Patents

通信方法及源基站、目标基站、核心网设备、终端设备 Download PDF

Info

Publication number
WO2019029674A1
WO2019029674A1 PCT/CN2018/099875 CN2018099875W WO2019029674A1 WO 2019029674 A1 WO2019029674 A1 WO 2019029674A1 CN 2018099875 W CN2018099875 W CN 2018099875W WO 2019029674 A1 WO2019029674 A1 WO 2019029674A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
session
handover
target base
network slice
Prior art date
Application number
PCT/CN2018/099875
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
Priority to EP21189454.8A priority Critical patent/EP4007367B1/en
Priority to RU2019132118A priority patent/RU2772653C2/ru
Priority to BR112019019985A priority patent/BR112019019985A2/pt
Priority to KR1020197026830A priority patent/KR102311745B1/ko
Priority to AU2018315286A priority patent/AU2018315286B2/en
Priority to EP18842877.5A priority patent/EP3576458B1/en
Priority to IL269926A priority patent/IL269926B2/en
Priority to KR1020217031973A priority patent/KR102498517B1/ko
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2019544921A priority patent/JP7031944B2/ja
Priority to EP24177020.5A priority patent/EP4444025A2/en
Publication of WO2019029674A1 publication Critical patent/WO2019029674A1/zh
Priority to US16/443,304 priority patent/US10952105B2/en
Priority to US17/199,928 priority patent/US11758441B2/en
Priority to US18/364,932 priority patent/US20240040443A1/en

Links

Images

Classifications

    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • 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/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a communication method, a source base station, a target base station, a core network device, and a terminal device.
  • 5G introduces the concept of network slicing, where a terminal device currently has multiple sessions, and different sessions may require network slices corresponding to the session to provide services.
  • the terminal device needs to access the network and establish multiple sessions, the connected base station needs to support all the sessions in the terminal device or the network slice corresponding to the partial session.
  • the technical problem to be solved by the embodiments of the present invention is to provide a communication method, a source base station, a target base station, a core network device, and a terminal device, so as to improve the probability of successful handover.
  • a first aspect of the present invention provides a communication method, including:
  • the source base station sends a handover request to the target base station, where the handover request is used to request to switch the session of the terminal device from the source base station to the target base station, where the handover request includes the identifier of the session requesting the handover and the indication information of the network slice corresponding to the session;
  • the handover response message of the target base station, the handover response message includes the rejection indication information, and the rejection indication information is used to indicate the reason information corresponding to the session in the session that is rejected by the target base station due to the network slice.
  • the source base station can learn the cause information of the rejection due to the network slice of the target base station corresponding to the session that is rejected by the target base station, so that information assistance is provided for other sessions that need to request handover to the target base station.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can be switched to the target base station, which improves the probability of successful handover.
  • the source base station sends a handover command to the terminal device, where the handover command includes a weight corresponding to the session rejected by the target base station.
  • the retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station.
  • the retransmission indication information may not indicate a specific network slice to which the specific route is routed. This improves the flexibility of session switching so that the terminal device can know which sessions can be re-established in the target base station after the rejection.
  • the method further includes: when the handover response message is a handover failure message, the source base station sends a radio resource control RRC connection release message to the terminal device.
  • the RRC connection release message includes the indication information of the network slice supported by the neighboring cell of the source cell; or the indication information of the network slice supported by the TA/RA of the neighboring cell of the source cell; or the neighboring base station including the source base station Supported network slice information.
  • a second aspect of the present invention provides a communication method, including:
  • the target base station receives a handover request from the source base station, and the handover request is used to request to switch the session of the terminal device from the source base station to the target base station, where the handover request includes the identifier of the session requesting the handover and the indication information of the network slice corresponding to the session;
  • the source base station sends a handover response message, where the handover response message includes a rejection indication information, and the rejection indication information is used to indicate cause information corresponding to the session in the session that is rejected by the target base station due to the network slice.
  • the target base station can notify the source base station of the reason information of the rejection of the network slice of the target base station corresponding to the session that is rejected, so that other sessions in the source base station that need to request handover to the target base station are provided.
  • the information helps that when the source base station needs to switch the session of the same network slice, it can directly determine whether it can be switched to the target base station, which improves the probability of successful handover.
  • the target base station receives a handover confirmation message from the terminal device; the target base station sends a path transfer request to the core network device, where the path transfer request includes the identifier of the session that the target base station confirms to switch.
  • the target base station rejects the identifier of the session to be handed over; the target base station receives a path transfer request response message from the core network device, and the path transfer request response message includes an identifier of the session of the successfully transferred path.
  • the core network device In order for the core network device to perform path transfer processing on the session confirming the handover.
  • a third aspect of the present invention provides a communication method, including:
  • the core network device receives a path transfer request from the target base station, where the path transfer request includes an identifier of the session in which the target base station confirms the handover and an identifier of the session in which the target base station rejects the handover; the core network device performs a path transfer process on the session confirming the handover, and rejects the handover
  • the session performs deactivation or deletion processing; the core network device sends a path transfer request response message to the target base station, and the path transfer request response message includes an identifier of the session of the successful transfer path.
  • the core network device can determine the session that has been deactivated from all the sessions of the stored terminal device by carrying the session confirming the handover and the identifier of the session rejecting the handover in the path transfer request. In this way, the core network device does not need to process this type of session, and only needs to process the session for confirming the handover and the session for rejecting the handover, thereby improving the processing efficiency.
  • the session requesting the handover includes the first session, and the network slice corresponding to the first session is supported by the target base station.
  • the target base station does not need to target The second session performs access control, which saves processing time for access control for the second session.
  • the session requesting the handover includes the first session and the second session; the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station, so that the target base station can directly determine that it is not Supported sessions improve the efficiency of determining handover response messages.
  • the cause information includes: a network slice corresponding to the session in which the target base station does not support the rejection of the handover, or a session correspondence supported by the target base station to reject the handover.
  • the network slicing resources are limited.
  • the handover response message in a case that the handover response message is a handover request acknowledgement message, the handover response message further includes retransmission indication information corresponding to the session that the target base station rejects the handover,
  • the retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station. This improves the flexibility of session switching so that the terminal device can know which sessions can be re-established in the target base station after the rejection.
  • the handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or The identification of the rejected data stream enables the source base station to acknowledge the rejected bearer or rejected data stream.
  • the handover request response message further includes information that carries a network slice supported by the target base station. This facilitates the target base station to notify the source base station of the network slice information currently supported by the target base station, and reduces the interaction between the source base station and the target base station.
  • the path transfer request further includes indication information of the network slice corresponding to the session that the target base station rejects the handover.
  • the core network device can compare the network slice corresponding to the rejected session with the network slice supported by the target cell that is saved by itself, so as to know whether the rejected session is caused by the network slice of the target base station is not supported, if Yes, the core network device subsequently triggers the process of deleting the session, which can reduce the storage space occupied by such a session in the core network device. If not, the core network device can subsequently trigger the process of deactivating the session, so that the core network device can quickly resume the session if activation is required.
  • the path transfer request further includes reason information corresponding to the session that the target base station rejects the handover.
  • reason information corresponding to the session that the target base station rejects the handover.
  • a fourth aspect of the present invention provides a communication method, including:
  • Radio resource control RRC connection release message from the source base station; releasing the RRC connection; wherein the RRC connection release message includes indication information of the network slice supported by the neighboring cell of the source cell; or the TA/including the neighboring cell of the source cell The indication information of the network slice supported by the RA; or the information of the network slice supported by the neighbor base station of the source base station.
  • the terminal device can release the RRC connection as early as possible, avoiding a subsequent radio link failure process, and reducing signaling overhead.
  • a fifth aspect of the present invention provides a communication method, including:
  • the source base station sends a first handover request to the core network device, where the first handover request is used to request to switch the session of the terminal device from the source base station to the target base station, where the first handover request includes information of the target base station and an identifier of the session requesting the handover;
  • the base station receives the first handover response message from the core network device, where the first handover response message includes the rejection indication information, and the rejection indication information is used to indicate the reason information corresponding to the session in the session that is rejected by the target base station due to the network slice.
  • the source base station can learn, by the core network device, the reason information that the rejected handover session is rejected by the network slice of the target base station, so that information assistance is provided for other sessions that need to request handover to the target base station.
  • the base station needs to switch the session of the same network slice, it can directly determine whether it can switch to the target base station, thereby improving the probability of successful handover.
  • the method further includes: when the first handover response message is the first handover request acknowledgement message, the source base station sends a handover command to the terminal device, where the handover command includes the target
  • the retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station.
  • the retransmission indication information may not indicate a specific network slice to which the specific route is routed. This improves the flexibility of session switching so that the terminal device can know which sessions can be re-established in the target base station after the rejection.
  • the method further includes: when the first handover response message is the first handover failure message, the source base station sends an RRC connection release message to the terminal device.
  • the RRC connection release message includes indication information of the network slice supported by the neighboring cell of the source base station; or indication information of the network slice supported by the TA/RA of the neighboring cell of the source base station; or the neighboring base station including the source base station Supported network slice information.
  • a sixth aspect of the present invention provides a communication method, including:
  • the core network device Receiving, by the core network device, a first handover request from the source base station, where the first handover request is used to request to switch the session of the terminal device from the source base station to the target base station, where the first handover request includes information of the target base station and an identifier of the session requesting the handover;
  • the core network device sends a first handover response message to the source base station, where the first handover response message includes the rejection indication information, and the rejection indication information is used to indicate the reason information corresponding to the session in the session that is rejected by the target base station due to the network slice.
  • the core network device can notify the source base station of the reason information of the rejection of the network slice of the target base station corresponding to the session that is rejected, so that the other source in the source base station needs to request to switch to the target base station.
  • the information helps that when the source base station needs to switch the session of the same network slice, it can directly determine whether it can be switched to the target base station, which improves the probability of successful handover.
  • the method before the core network device sends the first handover response message to the source base station, the method further includes: the core network device sends a second handover request to the target base station, where the second handover request includes The identifier of the session and the indication information of the network slice corresponding to the session; the core network device receives the second handover response message from the target base station, and the second handover response message includes the rejection indication information. The core network device is notified to the source base station of the rejection indication information.
  • a seventh aspect of the present invention provides a communication method, including:
  • the target base station receives the second handover request from the core network device, where the second handover request includes the identifier of the session and the indication information of the network slice corresponding to the session; the target base station sends a second handover response message to the source base station, where the second handover response message includes the rejection
  • the indication information is used to indicate the reason information corresponding to the session in the session that is rejected by the target base station due to the network slice.
  • the target base station may notify the core network device of the reason for the rejection of the network slice of the target base station corresponding to the session that is rejected by the handover, so that the core network device notifies the source base station of the information, so that the source base station is in the source base station.
  • Other information that needs to be requested to switch to the target base station provides information assistance.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can be switched to the target base station, which improves the probability of successful handover.
  • the cause information includes: a network slice corresponding to the session that the target base station does not support the handover rejection, or a session correspondence supported by the target base station to reject the handover.
  • the network slicing resources are limited.
  • the first handover request further includes first indication information, where the indication information indicates that the source base station is unsure or does not know the network slice supported by the target base station, so that the core
  • the network device learns that the source base station does not know the network slice information supported by the target base station, so that the information of the network slice supported by the target base station can be carried in the first handover response message. This reduces the interaction between the source base station and the target base station, and improves the information acquisition efficiency of the network slice.
  • the target base station may be a base station having a communication interface with the source base station; or may be a base station having no communication interface with the source base station.
  • the first handover request may include second indication information that does not have a communication interface between the source base station and the target base station, so that the core network device feeds back information about the network slice supported by the target base station.
  • the first handover response message in a case that the first handover response message is the first handover request acknowledgement message, the first handover response message further includes a session corresponding to the handover rejected by the target base station
  • the retransmission indication information is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station. This improves the flexibility of session switching so that the terminal device can know which sessions can be re-established in the target base station after the rejection.
  • the first handover request acknowledgement message further includes a rejection of the session requesting the handover The identity of the bearer or the identity of the rejected data stream.
  • the source base station can be made to acknowledge the rejected bearer or the rejected data stream.
  • the first handover request acknowledgement message further includes a network slice supported by the target base station. information. For example, if the first handover request includes the first indication information that the source base station does not determine the network slice supported by the target base station, or the second indication that the core network device does not have a communication interface between the source base station and the target base station carried in the first handover request.
  • the information may carry the information of the network slice supported by the target base station, thereby reducing the interaction between the source base station and the target base station, and improving the information acquisition efficiency of the network slice.
  • the first handover request further includes indication information of the network slice corresponding to the session requesting the handover.
  • the core network device can directly determine the indication information of the network slice corresponding to the session requesting the handover. It is to be understood that the first handover request may not include the indication information of the network slice corresponding to the session requesting the handover, which is not limited in this embodiment of the present invention.
  • the first handover request further includes an identifier of the data flow that the session requesting the handover needs to establish and QoS information corresponding to the data flow. This can save search time, reduce switching delay, and improve switching efficiency.
  • the first handover request further includes an aggregate maximum bit rate AMBR information corresponding to the session.
  • the search time can be saved, the handover delay is reduced, and the handover efficiency is improved.
  • the session included in the second handover request is a first session, and the network slice corresponding to the first session is supported by the target base station, in this case, The target base station does not need to perform access control for the second session, which saves processing time for performing access control for the second session.
  • the session included in the second handover request is the first session and the second session; the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is The target base station does not support, so that the target base station can directly determine the session that it does not support, and improve the determining efficiency of the handover response message.
  • the second handover response message in a case that the second handover response message is a second handover request acknowledgement message, the second handover response message further includes the target Retransmitting indication information corresponding to the session that the base station refuses to switch, and the retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session that refuses to switch to the network supported by the target base station. slice.
  • the core network device can re-establish in the target base station through the source base station which sessions can be re-established after the rejection, which improves the flexibility of session switching.
  • the second handover request acknowledgement message further includes the The identifier of the rejected bearer of the session included in the handover request or the identifier of the rejected data stream, so that the core network device can confirm the rejected bearer or the rejected data stream.
  • An eighth aspect of the present invention provides a communication method, where the first base station sends a first message to a core network device, where the first message is used to obtain information about a network slice supported by the core network device for the PLMN; The base station receives a second message from the core network device, the second message including information of the network slice supported by the PLMN served by the core network device.
  • the first base station may obtain the indication information of the network slice supported by the core network device in the case of the serving PLMN by using the core network device, and improve the first by using the network slice supported by the core network device in the PLMN granularity feedback.
  • the base station selects the accuracy of the core network device for the session of the terminal device.
  • a communication method where the core network device receives a first message from a first base station, where the first message is used to obtain information about a network slice supported by the core network device for the PLMN; The network device sends a second message to the first base station, where the second message includes information of a network slice supported by the PLMN served by the core network device.
  • the core network device may send the indication information of the network slice supported by the core network device in the case of the serving PLMN to the first base station, and improve the first base station by feeding back the network slice supported by the core network device with the PLMN granularity. Select the accuracy of the core network device for the session of the terminal device.
  • the embodiment of the present invention provides a base station, where the base station is a source base station, and the source base station includes: a sending unit, configured to send a handover request to the target base station, where the handover request is used to request a session of the terminal device
  • the source base station switches to the target base station, where the handover request includes an identifier of a session requesting handover and indication information of a network slice corresponding to the session; and a receiving unit, configured to receive a handover response message from the target base station, where
  • the handover response message includes a reject indication information, where the reject indication information is used to indicate cause information corresponding to a session in the session that is rejected by the target base station due to network slice.
  • the source base station may also implement some or all of the optional implementations of the first aspect.
  • an embodiment of the present invention provides a base station, where the base station is a target base station, where the target base station includes: a receiving unit, configured to receive a handover request from a source base station, where the handover request is used to request a session of the terminal device from The source base station switches to the target base station, where the handover request includes an identifier of a session requesting handover and indication information of a network slice corresponding to the session; and a sending unit, configured to send a handover response message to the source base station, where The handover response message includes rejection indication information, and the rejection indication information is used to indicate cause information corresponding to the session in the session that is rejected by the target base station due to network slice.
  • the source base station may also implement some or all optional implementations of the second aspect.
  • an embodiment of the present invention provides a core network device, where the core network device includes: a receiving unit 1001, configured to receive a path transfer request from a target base station, where the path transfer request includes the target base station confirming a handover The identifier of the session and the identifier of the session that the target base station refuses to switch; the processing unit 1002 is configured to perform a path transfer process on the session that confirms the handover, and perform a deactivation or deletion process on the session that rejects the handover; the sending unit 1003 is configured to: Sending a path transfer request response message to the target base station, the path transfer request response message including an identifier of a session of the successful transfer path.
  • the source base station may also implement some or all optional implementations of the third aspect.
  • the embodiment of the present invention provides a terminal device, where the terminal device includes: a receiving unit, configured to receive a radio resource control RRC connection release message from a source base station; and a processing unit, configured to release an RRC connection;
  • the RRC connection release message includes indication information of a network slice supported by a neighboring cell of the source cell; or indication information including a network slice supported by the TA/RA of the neighboring cell of the source cell; or a neighboring base station including the source base station Supported network slice information.
  • the terminal device can also implement the communication method of the fourth aspect.
  • the embodiment of the present invention provides a base station, where the base station is a source base station, and the source base station includes: a sending unit, configured to send a first handover request to the core network device, where the first handover request is used for the request And the first handover request includes: information about the target base station and an identifier of a session requesting handover; and a receiving unit, configured to receive, by the core network device, a session of the terminal device A handover response message, the first handover response message includes a rejection indication information, where the rejection indication information is used to indicate cause information corresponding to a session in the session that is rejected by the target base station due to network slice.
  • the source base station may also implement some or all optional implementation manners of the fifth aspect.
  • an embodiment of the present invention provides a core network device, where the core network device includes: a receiving unit, configured to receive a first handover request from a source base station, where the first handover request is used to request a terminal device Switching from the source base station to the target base station, the first handover request includes information of the target base station and an identifier of a session requesting handover; and a sending unit, configured to send a first handover response message to the source base station,
  • the first handover response message includes a reject indication information, where the reject indication information is used to indicate cause information corresponding to a session in the session that is rejected by the target base station due to network slice.
  • the core network device may also implement some or all of the optional implementation manners of the sixth aspect.
  • the embodiment of the present invention provides a base station, where the base station is a target base station, and the target base station includes: a receiving unit, configured to receive a second handover request from a core network device, where the second handover request includes a session And the sending unit is configured to send a handover response message to the source base station, where the handover response message includes a reject indication information, where the reject indication information is used to indicate that the network slice is caused The reason information corresponding to the session in which the target base station rejects the handover in the session.
  • the target base station may also implement some or all optional implementations of the seventh aspect.
  • the embodiment of the present invention provides a base station, where the base station is a first base station, and includes: a sending unit 1101, configured to send a first message to a core network device, where the first message is used to obtain the core
  • the network device is configured to receive information about the network slice supported by the PLMN.
  • the receiving unit 1102 is configured to receive a second message from the core network device, where the second message includes information about a network slice supported by the PLMN served by the core network device.
  • the source base station may also implement some or all optional implementations of the seventh aspect.
  • an embodiment of the present invention provides a core network device, where the core network device includes: a receiving unit, configured to receive a first message from a first base station, where the first message is used to obtain the core network The information about the network slice supported by the PLMN; the sending unit, configured to send the second message to the first base station, where the second message includes information about a network slice supported by the PLMN served by the core network device.
  • the source base station may also implement some or all of the optional implementation manners of the ninth aspect.
  • a communication device may be a base station in the above method design, or a chip disposed in the base station.
  • the communication device includes a memory for storing computer executable program code, a transceiver, and a processor coupled to the memory and the transceiver.
  • the program code stored in the memory comprises instructions which, when executed by the processor, cause the communication device to perform any one of the possible aspects of the first aspect, the second aspect, the fifth aspect, the seventh aspect or the eighth aspect The method performed by the terminal device.
  • a communication device may be a core network device in the above method design, or a chip disposed in the core network device.
  • the communication device includes a memory for storing computer executable program code, a transceiver, and a processor coupled to the memory and the transceiver.
  • the program code stored in the memory includes instructions that, when executed by the processor, cause the communication device to perform the method performed by the network device in any of the possible aspects of the third aspect, the sixth aspect, and the ninth aspect.
  • a communication device may be a terminal device in the above method design, or a chip disposed in the terminal device.
  • the communication device includes a memory for storing computer executable program code, a transceiver, and a processor coupled to the memory and the transceiver.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the terminal device in any of the possible designs of the fourth aspect above.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform the first to ninth aspects and The method in any possible implementation.
  • a twenty-third aspect a computer readable medium storing program code, when the computer program code is run on a computer, causing the computer to perform the first to ninth aspects and A method in any of its possible implementations.
  • a twenty-fourth aspect a chip comprising a processor and a memory for storing a computer program, the processor for calling and running the computer program from the memory, the computer program for implementing the first aspect to The method of the ninth aspect and any possible implementation thereof.
  • FIG. 1 is a schematic structural diagram of a possible communication system according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a possible core network device according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart diagram of a communication method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart diagram of another communication method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of another communication method according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart diagram of another communication method according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart diagram of another communication method according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another base station according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of another core network device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of another base station according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of another base station according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of another core network device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another base station according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of another core network device according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of another terminal device according to an embodiment of the present invention.
  • the terminal device may be a user equipment (UE), and the UE is accessed by the access network device, for example, a handheld terminal device, a notebook computer, a subscriber unit, and a cellular phone.
  • the access network device for example, a handheld terminal device, a notebook computer, a subscriber unit, and a cellular phone.
  • Phone smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handheld, laptop computer , cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal or other device that can access the network.
  • PDA personal digital assistant
  • WLL wireless local loop
  • MTC machine type communication
  • the terminal device and the access network device communicate with each other by using some air interface technology.
  • Radio access network (RAN) equipment mainly responsible for radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • the access network device may include various forms of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • base stations such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • the name of a device having a base station function may be different, for example, in a 5th generation (5th generation, 5G) system, called gNB; in an LTE system, It is an evolved Node B (eNB or eNodeB); in a 3rd generation (3G) system, it is called a Node B or the like.
  • 5G 5th generation
  • gNB 5th generation
  • LTE Long Term Evolution
  • eNB evolved Node B
  • 3G 3rd
  • the core network device is used to provide user connections, management of users, and completion of services.
  • the establishment of user connections includes functions such as mobile management (MM), paging, and the like.
  • User management includes user description, QoS, and security (the security measures provided by the authentication center include security management for mobile services and security for external network access).
  • the bearer connection includes an external public switched telephone network (PSTN), an external circuit data network and a packet data network, the Internet, and the like.
  • PSTN public switched telephone network
  • the core network device may include an access and mobility management function (AMF) network element, which is mainly responsible for the signaling processing part, that is, the control plane function, including access control, mobility management, attaching and going. Attachment and other functions.
  • AMF access and mobility management function
  • the core network device may further include a session management function (SMF) network element: responsible for session management functions, such as session establishment, modification, and release.
  • SMF session management function
  • the core network device may further include a user plane function (UPF) network element: responsible for forwarding and receiving user data in the terminal device.
  • the user data may be received from the data network and transmitted to the terminal device through the access network device.
  • the UPF network element may also receive user data from the terminal device through the access network device and forward the data to the data network.
  • the transmission resources and scheduling functions for the terminal devices in the UPF network element are managed and managed by the SMF network element.
  • the core network device in the embodiment of the present invention is not limited to the AMF network element, the SMF network element, and the UPF network element.
  • the access network device can be connected to at least one terminal device.
  • the access network device 101 is respectively connected to the terminal device 104 and the terminal device 105, and the access network device 102 and the terminal respectively.
  • Device 106 is coupled to terminal device 106.
  • the access network device can be connected to at least one core network device 103.
  • the access network device 101 and the access network device 102 are respectively connected to the core network device 103.
  • control plane interface between the core network device and the access network device.
  • an interface exists between the core network device and the access network. This is referred to as an N2 interface or an NG interface.
  • the two can communicate with each other; if the access network device 101 and the access network in FIG. There is no communication interface between devices 102, so the two cannot communicate with each other. Therefore, the access network device 101 and the access network device 102 can only transmit the information of the network slices supported by them when there is a communication interface, and cannot communicate in the absence of the communication interface, thereby failing to transmit the respective supported Network slice information.
  • the core network device 103 may include at least one AMF network element, and optionally may also include an SMF and a UPF network element.
  • the access network device 102 can be connected to one or more AMF network elements.
  • An AMF network element can support one or more different types of network slices, and different AMF network elements can support different types of network slices.
  • Each SMF can support one or more different types of network slices.
  • the types of network slices supported by different SMF network elements can be different.
  • One AMF network element can establish a communication connection with multiple SMF network elements.
  • one SMF network element can be connected to multiple AMF network elements.
  • one SMF network element can be connected to multiple UPF network elements, and one UPF network element can be connected to one SMF network element.
  • one SMF network element can manage and control multiple UPF network elements, one UPF.
  • the network element is controlled by an SMF management.
  • the UPF network element can establish a connection with the access network device to implement data transmission with respect to the terminal device.
  • FIG. 2 is a schematic diagram of a possible core network device according to an embodiment of the present invention.
  • An AMF network element 201 is connected to two SMF network elements, and the two SMF network elements are an SMF network element 202 and an SMF network element 203, respectively.
  • the network slice type supported by the AMF network element 201 includes the network slice type 1 and the network slice type 2, the network slice type 1 is the type of the network slice 1, and the network slice type 2 is the type of the network slice 2.
  • the SMF network element 202 is an SMF network element corresponding to the network slice 1, and the SMF network element 203 is an SMF network element corresponding to the network slice 2.
  • An SMF network element can manage and control a plurality of UPF network elements.
  • the SMF network element 202 manages the UPF network element 204, the UPF network element 205, and the UPF network element 206.
  • the SMF network element 203 manages the UPF network element 204 and the UPF network element 208.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-atency communications
  • massive machine-like communication massive machine-like communication
  • mMTC massive machine-like communication
  • Different access network devices can support different network slices. In this case, when the terminal device needs to access the network and establish multiple sessions, the connected access network device needs to support all the sessions in the terminal device or the network slice corresponding to the partial session.
  • the session of the terminal device 104 needs to be switched from one access network device 101 to another.
  • the network device 102 is accessed, but the success or failure of the handover is related to the network slice corresponding to whether the access network device 102 supports the session of the terminal device 104.
  • the access network device 101 sends a handover request to the access network device 102, and sometimes some sessions cannot be handed over to the access network device 102.
  • the access network device 101 cannot determine the reason that the session cannot be switched to the access network device 102. If the first network slice resource corresponding to the requested session in the access network device 102 is limited, When the session needs to be switched to the first network slice, the access network device 101 still sends a handover request to the access network device 102, and the situation that the session cannot be switched to the access network device 102 still occurs, and the handover is successfully reduced. The probability.
  • the access network device 101 can learn the reason that the rejected handover session is rejected by the network slice of the access network device 102. Information, which provides information assistance for other sessions that require a handover to the access network device 102.
  • the access network device 101 needs to switch sessions of the same network slice, it can directly determine whether it can be switched to the access network device 102. The probability of successful handover is improved, and a better target base station can be selected for handover for other terminal devices to be switched.
  • the access network device in the embodiment of the present application is described by using a base station as an example.
  • the information about the network slice supported by the base station involved in any embodiment of the present application may be included in an optional manner.
  • the base station includes at least one cell identifier and indication information of at least one network slice corresponding to each cell identifier.
  • One base station may include one or more cells, each cell is represented by a cell identifier, and each cell may support one or more network slices, and each cell supports different network slices, such that one cell identifier may correspond to at least one Indicates the network slice.
  • the specific manifestation is as follows (the name is only indicated, and the name is not limited in the embodiment of the present application), wherein the Cell ID indicates the cell identifier, the S-NSSAI list indicates the indication information of a network slice, and one Cell ID can be associated with at least one S. -NSSAI list corresponds.
  • the information about the network slice supported by the base station may include the information of the base station and the indication information of the at least one network slice corresponding to the base station.
  • Each base station can support one or more network slices, such that information of one base station can correspond to indication information of at least one network slice.
  • the specific manifestation is as follows (the name is only indicated, and the name is not limited in the embodiment of the present application), wherein the gNB ID indicates information of the base station, and the S-NSSAI list indicates indication information of a network slice, and one gNB ID may be associated with at least one The S-NSSAI list corresponds.
  • the information about the network slice supported by the base station may include at least one network slice corresponding to a tracking area (TA) or a registration area (RA) to which the cell included in the base station belongs.
  • TA tracking area
  • RA registration area
  • Each TA/RA can support one or more network slices, such that the information of one TA/RA can correspond to the indication information of at least one network slice.
  • the specific manifestation is as follows (the name is only indicated, and the name is not limited in the embodiment of the present application), wherein the tracking area identity/identifier (TAI) and the registration area identity/identifier (RAI) ), tracking area code (TAC) or registration area identity/identifier (RAC) is used to indicate TA/RA information, and S-NSSAI list indicates indication information of a network slice, a TAI/RAI /TAC/RAC can correspond to at least one S-NSSAI list.
  • the information about the base station involved in any embodiment of the present application may include a base station identifier of the base station, a central unit ID of the base station, a distributed unit ID included in the base station, and a base station included. At least one of a Physical Cell Identifier (PCI) and a Cell Global ID (CGI) included in the base station.
  • PCI Physical Cell Identifier
  • CGI Cell Global ID
  • the indication information of each network slice involved in any embodiment of the present application may include a network slice identification assistance information (S-NSSAI). And at least one of RAN network slice selection assistance information (R-NSSAI).
  • S-NSSAI network slice identification assistance information
  • R-NSSAI RAN network slice selection assistance information
  • the network slice identifier may be represented by at least one of the following (1) to (7).
  • Network slice type information may indicate enhanced mobile broadband (eMBB), Ultra-Reliable Low Latency Communications (URLLC), massive machine type communication Network slice type, such as massive machine type communication (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC Ultra-Reliable Low Latency Communications
  • mMTC massive machine type communication
  • the network slice type information may also indicate an end-to-end network slice type, including a network slice type of the RAN to the core network (Core Network, CN), or Refers to the RAN side network slice type, or the CN side network slice type.
  • the service type information is related to a specific service.
  • the service type information may indicate a service feature such as a video service, a car network service, a voice service, or a specific service.
  • Tenant information used to indicate the customer information for creating or renting the network slice, such as Tencent, State Grid, etc.
  • User group information for indicating grouping information for grouping users according to a certain characteristic, such as the level of the user.
  • Slice group information which is used to indicate that according to a certain feature, for example, all network slices that the terminal device can access can be regarded as one slice group, or packets of network slices can also be divided according to other standards.
  • Network snippet instance information which is used to indicate an instance identifier and feature information created for the network slice.
  • the network slice instance may be assigned an identifier for indicating the network slice instance, or may be identified by the network slice instance.
  • a new identifier is mapped on the basis of 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 proprietary core network in a Long Term Evolution (LTE) system or an Enhanced LTE (eLTE) system, for example
  • LTE Long Term Evolution
  • eLTE Enhanced LTE
  • the core network of the Internet of Things is optional.
  • the DCN identifier can be mapped to the network slice identifier.
  • the DCN identifier can be used to map the network slice identifier.
  • the DCN identifier can also be mapped through the network slice identifier.
  • the S-NSSAI includes at least slice type/service type (SST) information, and optionally may include slice distinguishing information (Slice Differentiator, SD).
  • SST information is used to indicate the behavior of the network slice, such as the characteristics of the network slice and the service type.
  • the SD information is the complement information of the SST. If the SST is directed to multiple network slice implementations, the SD may correspond to a unique network slice instance.
  • R-NSSAI represents a specific set of S-NSSAIs, that is, the identifiers of a set of specific S-NSSAIs.
  • the network slice may use at least one of the foregoing parameters to represent the indication information of the network slice.
  • the indication information of the network slice may be characterized by a network slice type, or may also be sliced by using a network.
  • the characterization of the type and the service type, or the characterization of the service type plus the tenant information, etc., is not limited in this embodiment of the present application.
  • the specific coding format of the indication information of the network slice is not limited, and different fields of the interface message that can be carried between different devices respectively represent indication information of different network slices, or may be replaced by an abstracted index value.
  • the index values correspond to different network slices.
  • the indication information of the network slice supported by the terminal device, the access network device, or the core network device may be represented by the list of at least one identifier. .
  • “having a communication interface” or “having an interface” in the embodiment of the present invention means that a communication interface is established and the communication interface is available; the “no communication interface” or “no interface” is involved. The communication interface is not established or the established communication interface is unavailable.
  • the communication interface herein is not limited to the communication interface between the access network device and the access network device, the communication interface between the access network device and the core network device.
  • Embodiments of the present invention are applicable to other communication systems that support network slicing.
  • the term "system” can be replaced with "network”.
  • the system architecture described in the embodiments of the present invention is for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and does not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • the access network device is described by taking a base station as an example.
  • the communication method involves a terminal device, a source base station, a target base station, and a core network device.
  • the communication method corresponds to a communication method in a case where the target base station determines that the handover is successful, the source base station is a base station currently establishing a communication connection with the terminal device, and the target base station is a base station requesting to switch the session of the terminal device to.
  • the communication method includes steps 301 to 307, which are described in detail below.
  • the source base station sends a handover request to the target base station.
  • the handover request is used to request to handover the session of the terminal device from the source base station to the target base station, and the handover request includes an identifier of the session requesting the handover and indication information of the network slice corresponding to the session. For example, if the number of sessions requesting the handover is multiple, the handover request carries the indication information of the network slice corresponding to each session.
  • the target base station receives the handover request.
  • the session requesting the handover may be an active session of the terminal device, which may be understood as a session currently in progress in the terminal device.
  • the session of the terminal device includes session A1, session A2, session A3, session A4, and session A5, wherein session A1, session A2, and session A3 are in an active state; session A4 and session A5 are in a deactivated state.
  • the session requesting the handover includes the identifiers of the session A1, the session A2, and the session A3, and the indication information of the network slice corresponding to the session A1, the session A2, and the session A3, respectively. For a deactivated session, there is no need to switch to the target base station, which can reduce signaling transmission.
  • the source base station may further determine, according to the information about the network slice supported by the target base station and the indication information of the network slice corresponding to the session that requests the handover: which network segments corresponding to the session in the session to be switched The target base station is supported, and the network slice target base stations corresponding to which sessions are not supported. Further, if all the network slice target base stations corresponding to the session requesting the handover are not supported, the source base station may not send the handover request information to the target base station.
  • the session requesting the handover may be the first session and the second session of the terminal device, where the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station.
  • the source base station and the target base station have a communication interface, the source base station can determine the network slice supported by the target base station by interacting with the target base station, by interacting with other base stations, or by interacting with the core network side, and then the source base station.
  • the session requesting the handover may be classified according to the indication information of the network slice corresponding to each session that is requested to be switched and the network slice supported by the target base station, to obtain the first session and the second session.
  • the session requesting the handover includes the session B1, the session B2, and the session B3.
  • the target base station supports the network slice corresponding to the session B1 and the session B2, and the target base station does not support the network slice corresponding to the session B3.
  • the session requesting the handover is performed.
  • the identifiers are sent to the target base station in two types, one is the identifier of the first session, and the other is the identifier of the second session, so that the target base station can directly determine the session that it does not support, and improve the determination efficiency of the handover response message.
  • the session requesting the handover may be the first session of the terminal device, where the network slice corresponding to the first session is supported by the target base station.
  • the target base station does not need to determine whether to support the network slice corresponding to the request handover session for the part of the session corresponding to the unsupported network slice, and can determine whether to switch the first session according to the resource usage of the network slice in the target base station.
  • the target base station does not need to perform access control for the second session, which saves processing time for performing access control for the second session.
  • the source base station selects one of the base stations that have a communication interface with the source base station to determine the target base station. Further, the determined target base station supports the network slice corresponding to all or part of the session requesting the handover, so as to avoid the handover failure caused by the target base station not supporting the network slice of all the sessions requesting the handover, thereby reducing the number of handover failures. To increase the probability of successful handover.
  • the source base station may, when receiving the measurement report sent by the terminal device, select the target base station according to the measurement report, and perform step 301 to send a handover request to the target base station.
  • the measurement report includes measurement report values for at least one of the cell and the base station.
  • the included cell may be a cell included in the source base station, or may be a cell included in another base station. If the measurement report includes the measurement report value of the base station, the included base station may be the source base station or other base stations.
  • the embodiment of the present invention does not limit the number of cells and the number of base stations included in the measurement report.
  • the target base station performs access control according to factors such as network slice support, resource usage, and handover request.
  • the target base station when the target base station receives the handover request sent by the source base station, the target base station performs admission control.
  • the target base station determines the handover response message according to the indication information of the network slice corresponding to each session in the handover request, the support status of the network slice, and the resource usage.
  • the session B4 if the information of the network slice supported by the target base station includes the indication information of the network slice corresponding to the session B4, it indicates that the target base station supports the network slice corresponding to the session B4. If the information of the network slice supported by the target base station does not include the indication information of the network slice corresponding to the session B4, it indicates that the target base station does not support the network slice corresponding to the session B4. In this case, the session B4 is the session that rejects the handover. Further, if the target base station supports the network slice corresponding to the session B4, if the target base station can also allocate the resource of the corresponding network slice to the session B4, the target base station determines that the session B4 is the session for confirming the handover. If the target base station cannot allocate resources of the corresponding network slice to the session B4, the target base station determines that the session B4 is a session that refuses to be exchanged. In this way, the target base station can determine the handover response message by using the access control.
  • the target base station may check the indication information of the network slice corresponding to the first session (one session or multiple sessions) to determine whether the first session is currently supported. Network slice.
  • the handover response message may be a handover request acknowledgement message; or the handover response message is a handover failure message.
  • the handover response message is introduced as a handover request acknowledgement message.
  • the session that is rejected by the target base station may be caused by the target base station not supporting the network slice corresponding to the rejected session, or may be caused by the resource limitation of the network slice corresponding to the rejected session in the target base station.
  • the handover request acknowledgement message includes reject indication information, which is used to indicate cause information corresponding to the session in the session that is rejected by the target base station due to network slice.
  • the reason information includes that the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that the target base station supports to reject the handover is limited.
  • the cause information in the embodiment of the present invention may be indicated by an information element (IE), a flag, a cause, or the like, which is not limited by the embodiment of the present invention.
  • IE information element
  • the reason information of the session that is rejected for the handover may be a network slice corresponding to the session in which the target base station does not support the rejection of the handover, or the rejection handover supported by the target base station.
  • the network slice resources corresponding to the session are limited. If the session requesting the handover includes the first session, the reason information of the session that is rejected for handover is that the network slice resource corresponding to the session of the target base station that refuses to switch is limited.
  • the data flow is a traffic flow or a QoS flow
  • the first session part of the data stream is received by the target base station, and part of the data stream is rejected by the target base station
  • For the first session carrying indication information indicating the reason for the data flow that the first session part is rejected, for example, the resource is limited or the network slice corresponding to the first session is limited in the target base station resource.
  • the target base station sends a handover request acknowledgement message to the source base station.
  • the handover request acknowledgement message includes an identifier of the session confirming the handover, an identifier of the session rejecting the handover, and a reason information corresponding to the session rejecting the handover.
  • the handover request acknowledgement message may be a handover acknowledgement, or a handover request acknowledgement.
  • Table 1 is a PDU session release list or a PDU session rejection list.
  • the identifier of the session rejecting the handover included in the handover request acknowledgement message and the reason information corresponding to the session rejecting the handover may be expressed in the form of Table 1.
  • the handover request acknowledgement message further includes retransmission indication information corresponding to the session that rejects the handover.
  • the retransmission indication information is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station.
  • the case where the rejected session is the session B1 and the session B1 corresponding to the network slice 1 is used as an example.
  • the reason information that the session B1 is refused to be switched may be that the target base station does not support the network slice 1 corresponding to the session B1, or may be the target base station.
  • the target base station determines that the retransmission indication information corresponding to the session B1 is: allowing the terminal device to route the data flow included in the session B1 to the network slice 2 supported by the target base station. It can be understood that the retransmission indication information may not indicate a specific network slice to which a specific route is routed.
  • the target base station determines that the retransmission indication information corresponding to the session B1 is:
  • the terminal device is not allowed to route the data stream contained in the session B1 to the network slice supported by the target base station.
  • the retransmission indication information and the cause information can be identified by using an IE/Flag/Cause value, that is, the IE/Flag/Cause value indicates the reason for the session rejection and indicates that the data flow corresponding to the rejected session can be routed.
  • the session can be re-established on the network slice supported by other target base stations for transmitting the data stream.
  • the retransmission indication information and the cause information may also be identified by two different IE/Flag/Cause values, respectively.
  • the handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • one session includes multiple data flows, and one bearer may correspond to multiple data flows.
  • the rejected bearer may be a bearer included in the session confirming the handover, or may be a bearer included in the session rejected by the handover;
  • the data stream may be the data stream included in the session confirming the handover, or may be the data stream included in the session rejected by the handover.
  • the part of the session included in the switched session is a rejected bearer
  • the part of the data stream included in the session of the handover is confirmed to be the rejected data stream
  • the handover request determination message is sent to the source base station, so that the source base station can confirm the A rejected or rejected data stream.
  • the handover request acknowledgement message further includes the identifier of the rejected data flow, refer to Table 2, which includes the identifier of the session confirming the handover, the reason information of the data flow rejected by the handover, and the The ID of the rejected data stream.
  • the convinced session list may be represented as a PDU Session Admitted List, or may be represented as a PDU Sessions Subject to Forwarding List.
  • the handover request acknowledgement message may feed back the information included in the form of a list, the session requesting handover by the source base station includes the first session and the second session, and determining that the handover response message is a handover request acknowledgement message, to One session includes session C1, session C2, and session C3, and the second session includes session D1 and session D2 as an example.
  • the session in which the target base station confirms the handover is the session C1 and the session C2; the session in which the target base station rejects the handover includes the session C3, the session D1, and the session D2, and the target base station supports the network slice corresponding to the session C3, but the handover is limited due to the limitation of the network slice resource. Failure, confirming that part of the bearer or part of the data stream in the switched session C1 is rejected.
  • the session C1 with the rejected bearer/data flow may also correspond to the cause information in the handover request acknowledgement message.
  • the reason information is used to indicate the reason information of the partially rejected or rejected partial data stream.
  • the reason information R3 of the rejected part of the carried or rejected partial data stream may be resource limited, the data stream corresponding to the QoS combination corresponding to the QoS combination, the data stream identifier repetition, and the like.
  • the session C1 that has the rejected bearer/data flow may also correspond to the retransmission indication information in the handover request acknowledgement message.
  • the redirection indication information indicates the same meaning as the foregoing content, and the retransmission indication information is Y indicating that the terminal device is allowed to
  • the rejected data stream contained in session C1 is routed to the network slice supported by the target base station. Thereby, it is possible to provide more accurate information for the next handover and improve the success rate of the handover.
  • the rejected bearer/data flow identifier, the retransmission indication information, and the cause information may be optionally carried in the handover request acknowledgement message.
  • the confirmed session list may be represented as a PDU Session Admitted List, or may be represented as a PDU Sessions Subject to Forwarding List.
  • Table 4 is a list form of a session for rejecting handover according to an embodiment of the present invention, where the rejected bearer/data flow identifier and retransmission indication information are optionally carried in the handover request acknowledgement message.
  • the reason information of the session C3 is R1, indicating that the target base station supports the network slice corresponding to the session C3 but the resource of the network slice is limited; the cause information of the session D1 and the session D2 is R2, indicating that the target base station does not support the network corresponding to the session D1. Slices and network slices corresponding to session D2 are not supported.
  • the Y in the retransmission indication information indicates that the terminal device is allowed to route the data stream included in the session C3 to the network slice supported by the target base station; the N in the retransmission indication information indicates that the terminal device is not allowed to include the data included in the session D1 and the session D2.
  • the flow is routed to a network slice supported by the target base station.
  • the list of sessions that are refused to be switched may be represented as a PDU Sessions to Release List, or may be represented as a PDU Session Not Admitted List.
  • Table 4 generates a list according to each session identifier.
  • the list can be generated according to the reason information.
  • Table 5 another embodiment of the present invention is provided.
  • Such a reason information corresponds to multiple session identifiers, which can save signaling transmission.
  • the rejected bearer/data flow identifier and the retransmission indication information are optionally carried in the handover request acknowledgement message.
  • the list of sessions that are refused to be switched may be represented as a PDU Sessions to Release List, or may be represented as a PDU Session Not Admitted List.
  • the handover request acknowledgement message further carries the bearer configuration information determined by the target base station, where the bearer configuration information is used to indicate that the terminal device performs bearer configuration according to the configuration information.
  • the handover request acknowledgement message further includes full configuration handover indication information, where the full configuration handover indication information is used to indicate that the terminal device does not need to modify the original bearer one by one, and may perform full configuration by using the bearer configuration information determined by the target base station. The handover is performed by deleting all the original bearer configurations and storing the bearer configuration information determined by the target base station to improve the configuration efficiency of the bearer.
  • the handover request acknowledgement message further includes full configuration handover indication information.
  • the handover request acknowledgement message further includes information that carries the network slice supported by the target base station. This facilitates the target base station to notify the source base station of the network slice information currently supported by the target base station, and reduces the interaction between the source base station and the target base station.
  • the source base station receives the handover request acknowledgement message sent by the target base station.
  • the source base station sends a handover command to the terminal device.
  • the source base station After the source base station receives the handover request acknowledgement message sent by the target base station, the source base station sends a handover command to the terminal device.
  • the handover command may be an RRC connection reconfiguration message (RRC Connection Reconfiguration) or a handover command message (handover command).
  • the handover command includes at least one of an identifier of the session confirming the handover, an identifier of the data stream included in the session in which the handover is confirmed, and an identifier of the bearer corresponding to the session confirming the handover, to notify the terminal device that the session and the data flow can be switched to the target base station. Or bear.
  • the handover command further includes retransmission indication information corresponding to the session that the target base station rejects the handover and the session that rejects the handover, so that the terminal device determines whether to reject the target base station according to the retransmission indication information corresponding to the reject handover session. Switch the session establishment request for the session.
  • the handover command may include retransmission indication information corresponding to each session, or the handover command may allow retransmission and two types of retransmission not allowed to be indicated, the present invention The embodiment does not limit this.
  • the handover command further includes bearer configuration information determined by the target base station, to indicate that the terminal device performs bearer configuration according to the configuration information.
  • the handover request acknowledgement message further includes full configuration handover indication information
  • the handover command further includes full configuration handover indication information to improve the configuration efficiency of the bearer.
  • the terminal device receives the handover command sent by the source base station.
  • the terminal device sends a handover confirmation message to the target base station.
  • the handover confirmation message may be a handover complete message (handover complete) or an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete).
  • the terminal device performs random access with the target base station to feed back a handover confirmation message to the target base station, where the terminal device has completed the handover.
  • the target base station sends a path transfer request to the core network device.
  • the path transfer request is sent to the core network device.
  • the path transfer request is a Path switch request.
  • the path transfer request includes an identifier of the session in which the target base station confirms the handover, so that the core network device performs path transfer processing on the session confirming the handover.
  • the path transfer request may further include an identifier of the session that the target base station refuses to switch, so that the core network device deletes or deactivates the session that rejects the handover.
  • the terminal device has a service in an activated state and a service in a deactivated state, and the core network device stores all sessions of the terminal device. Since the session confirming the handover and the session rejecting the handover belong to the activated service, the core network device can determine from all the sessions of the stored terminal device by carrying the identifiers of the two types of sessions in the path transfer request. The session is in the deactivated state, so that the core network device does not need to process this type of session, and only needs to process the session for confirming the handover and the session for rejecting the handover, thereby improving the processing efficiency.
  • the path transfer request further includes the indication information of the network slice corresponding to the session that the target base station refuses to switch, so that the core network device can perform the network slice supported by the target cell and the network slice supported by the target cell that is saved by the core network device.
  • the core network device subsequently triggers the process of deleting the session, which can reduce such session in the core network. The storage space occupied by the device. If not, the core network device can subsequently trigger the process of deactivating the session, so that the core network device can quickly resume the session if activation is required.
  • the path transfer request includes reason information corresponding to the session that the target base station rejects the handover.
  • reason information corresponding to the session that the target base station rejects the handover.
  • the core network device receives the path transfer request sent by the target base station.
  • the core network device performs a path transfer process on the session that confirms the handover, and performs a deactivation or deletion process on the session that rejects the handover.
  • the process performed by the core network device to confirm the handover of the session execution path is specifically:
  • the core network device performs the deactivation process for the session that refuses to switch, specifically suspending the session that refuses to switch, and the context corresponding to the session may also be saved in the core network device, so that the core network device may be activated if the session needs to be activated. Quickly resume the session.
  • the core network device performs a deletion process on the session that refuses to switch. Specifically, the core network device deletes the context corresponding to the session. For example, the AMF network element notifies the SMF network element to delete the context corresponding to the session, so that the session can be reduced in the core network device.
  • the core network device may perform a deactivation process on the session that is rejected because the network slice resource of the target base station is restricted, so that the network slice may be restored in the target base station if the network slice is not limited. data transmission.
  • the time required for the activation process is shorter by re-establishing the session, so that the data transmission of the deactivation session can be resumed.
  • the core network device may perform a deletion process on the session that is rejected because the target base station does not support the network slice. Since the network slice supported by the target base station does not change in a short time, the session cannot be restored in a short time. Data transmission, so that if the session is deactivated, it will occupy more storage space on the core network device, resulting in waste of storage space.
  • the core network device sends a path transfer request response message to the target base station.
  • the core network device sends a path transfer request response message to the target base station, where the path transfer request response message includes an identifier of the session of the successfully transferred path. For example, the path transfer request response message Path switch request ack or Path switch request response.
  • the path transfer request response message further includes an identifier of the session that fails for the transfer path, so that the target base station determines a path transfer result of the core network device.
  • the source base station after the source base station sends the handover request to the target base station, the source base station can learn the reason information that the rejected handover session is rejected by the network slice of the target base station, so that the other needs to request to switch to the target base station.
  • the session provides information assistance.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can switch to the target base station, which improves the probability of successful handover.
  • the access network device is described by taking a base station as an example.
  • the communication method involves a terminal device, a source base station, and a target base station. 4 corresponds to a communication method in the case where the target base station determines that the handover fails, the source base station is a base station currently establishing a communication connection with the terminal device, and the target base station is a base station requesting to switch the session of the terminal device to.
  • the communication method includes steps 401 to 404, which are described in detail below.
  • the source base station sends a handover request to the target base station.
  • step 401 reference may be made to the detailed description of the corresponding step 301 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the target base station performs access control according to factors such as network slice support, resource usage, and handover request.
  • the target base station when the target base station receives the handover request sent by the source base station, the target base station performs admission control.
  • the target base station determines the handover response message according to the indication information of the network slice corresponding to each session in the handover request, the support status of the network slice, and the resource usage.
  • the handover response message may be a handover request acknowledgement message; or the handover response message is a handover failure message.
  • the handover response message is described as a handover failure message.
  • the session that is rejected by the target base station may be caused by the target base station not supporting the network slice corresponding to the rejected session, or may be caused by the resource limitation of the network slice corresponding to the rejected session in the target base station.
  • the handover request acknowledgement message includes reject indication information, which is used to indicate cause information corresponding to the session in the session that is rejected by the target base station due to network slice.
  • the reason information includes that the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that the target base station supports to reject the handover is limited.
  • the cause information in the embodiment of the present invention may be indicated by an IE, a flag, a cause, or the like, which is not limited by the embodiment of the present invention.
  • the reason information of the session that is rejected for the handover may be a network slice corresponding to the session in which the target base station does not support the rejection of the handover, or the rejection handover supported by the target base station.
  • the network slice resources corresponding to the session are limited. If the session requesting the handover includes the first session, the reason information of the session that is rejected for handover is that the network slice resource corresponding to the session of the target base station that refuses to switch is limited.
  • the target base station sends a handover failure message to the source base station.
  • the handover failure message includes reason information corresponding to the session that rejects the handover.
  • the handover failure message is a handover preparation failure message.
  • the handover failure message further includes an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • one session includes multiple data flows, one bearer corresponds to at least one data flow, the rejected bearer may be a bearer included in the session rejected by the handover; the rejected data flow may be rejected by the data flow included in the switched session .
  • all the bearers included in the session that is refused to be switched are rejected bearers, and all the data streams included in the session that is refused to be switched are rejected data flows, and are sent to the source base station through a handover failure message, so that the source base station The rejected bearer or rejected data stream can be acknowledged.
  • the handover failure message may also be represented by a list of sessions that reject the handover, and the list may refer to Table 4 and Table 5 to remove all contents of the retransmission indication information, where the rejected bearer
  • the identifier of the data stream is an optional content of the handover failure message, which is not limited by the embodiment of the present invention.
  • the rejection indication information may be used to indicate that the target base station does not support the network slice corresponding to any session currently performed by the terminal device.
  • the handover failure message includes the rejection indication information as indicated by IE, flag, cause, etc., and the identifier of the session that refuses to switch, for example, in this case, Referring to Table 6, the PDU session release list includes an indication value for rejecting the handover.
  • the handover failure message includes the rejection indication information (as indicated by IE, flag, cause, etc.). In this case, it is not necessary to carry the PDU session release list in Table 6, but only the handover failure indication value. So that the source base station determines a network slice that is not supported by the target base station.
  • the refusal indication information may be used to indicate that the target base station supports a network slice corresponding to any session included in the handover request, and refuses to switch all sessions included in the handover request.
  • the handover failure message includes the rejection indication information. (Indicated by IE, flag, cause, etc.); in another optional scheme, the handover failure message includes the rejection indication information as indicated by IE, flag, cause, etc.) and the identifier of the session that refuses to switch, The source base station determines the resource usage of the network slice corresponding to the request handover session in the target base station.
  • the refusal indication information may be used to indicate that the target base station supports the network slice corresponding to the third session and refuses to switch the third session, and the target base station does not support the network slice corresponding to the fourth session, where the session for requesting handover includes The third session and the fourth session. For example, if the source base station is not sure of the supported network slice that is updated by the target base station, the session for which the source base station requests the handover includes the first session and the second session, or the session for the source base station to request the handover includes the first In the case of a session, the target base station may reclassify the session requesting handover according to the support situation of the network slice and the resource usage situation.
  • the source base station determines the first session supported by the target base station, and may change to the session that the target base station does not support. If the source base station determines the second session that the target base station does not support, it may change to the session supported by the target base station. Therefore, the third session in the reject indication information fed back by the target base station may be the same or may not be the same in the first session in the handover request; and the fourth session in the rejection indication information fed back by the target base station may be in the handover request.
  • the second session is the same or it may not be the same.
  • the target base station may classify the session corresponding to the reason for rejecting the same handover into one class to correspond to one reject indication information (as indicated by IE, flag, cause, etc.), that is, the handover failure message includes Two rejection indication information and an identifier of a session respectively corresponding to the two rejection indication information; or, the target base station may respectively correspond to one rejection indication information (indicated by IE, flag, cause, etc.) for each of the rejection handover sessions, That is, the handover failure message includes at least one identifier of the session that rejects the handover and the refusal indication information corresponding to each session that rejects the handover; or the handover failure message includes two rejection indication information, which is not limited by the embodiment of the present invention.
  • the handover failure message may include the identifier of the session including the network that rejects the handover and the indication information of the network slice corresponding to the session that rejects the handover.
  • the content is used to indicate that the resource of the network slice in the target base station of the source base station is limited, and no additional indication information is needed, so that the source base station can determine the resource usage of the class to the sliced target base station.
  • the rejection indication information may be used to indicate that the target base station rejects the handover session.
  • the handover failure message includes a rejection indication information to indicate that the target base station not only rejects the requested handover session, but also rejects the handover for the other network slice corresponding to the supported network, so that the source base station can also know the target base station in time.
  • the resource usage of all network slices provides information assistance for the switching of other sessions in the source base station, and improves the handover success rate.
  • the handover failure message further includes information that carries a network slice supported by the target base station. This facilitates the target base station to notify the source base station of the network slice information currently supported by the target base station, and reduces the interaction between the source base station and the target base station.
  • the source base station sends an RRC connection release message to the terminal device.
  • the RRC connection release message is sent to the terminal device, so that the terminal device releases the RRC connection as soon as possible, avoiding the subsequent radio link failure process, and reducing the signaling overhead.
  • the RRC connection release message includes indication information of a network slice supported by a neighboring cell of the source cell; or indication information of a network slice supported by the TA/RA of the neighboring cell of the source cell; or includes the source Information about the network slice supported by the neighbor base station of the base station.
  • the source cell is a cell that the source base station serves the terminal device when requesting handover from the target base station. In order to enable the source base station to obtain more network slices supported by other cells or other base stations, it provides information for subsequent assistance, thereby reducing the mutual signaling of acquiring the network slice information between the second base station and the neighboring base station of the first base station, and improving The convenience and speed of obtaining the information of the network slice supported by the base station.
  • the terminal device receives the RRC connection release message and performs RRC connection release.
  • the source base station after the source base station sends the handover request to the target base station, the source base station can learn the reason information that the rejected handover session is rejected by the network slice of the target base station, so that the other needs to request to switch to the target base station.
  • the session provides information assistance.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can switch to the target base station, which improves the probability of successful handover.
  • FIG. 5 another communication method is provided according to an embodiment of the present invention.
  • the access network device involved in the communication method is described by taking a base station as an example.
  • the communication method involves a first base station and a core network device. Please see the specifics below.
  • the first base station sends a first message to the core network device, where the first message is used to obtain indication information of the core network device for the network slice supported by the PLMN.
  • the core network equipment can serve multiple Public Land Mobile Networks (PLMNs).
  • PLMNs Public Land Mobile Networks
  • the network slice supported by the core network device may be different.
  • the network slices supported by different core network devices may be different.
  • the embodiment of the present invention does not limit this.
  • the first core network device may provide services for the first PLMN and the second PLMN. In the case of serving the first PLMN, the first core network device supports the network slice 1, the network slice 2, and the network slice 3; In the case of the second PLMN, the first core network device supports the network slice 1 and the network slice 4.
  • the second core network device may provide services for the first PLMN, and in the case of serving the first PLMN, the second core network device supports the network slice 1, the network slice 4, and the network slice 5.
  • the first message carries the identifier of the PLMN, so that the core network device feeds back the indication information of the network slice supported by the PLMN indicated by the identifier of the serving PLMN.
  • the identifier of the carried PLMN may be part or all of the identifiers of the PLMNs supported by the cell included in the first base station.
  • the first message does not carry the identifier of any PLMN, so that the core network device can feed back the indication information of the network slice respectively supported in the case of providing services for each PLMN.
  • the core network device sends indication information of the network slice supported by the first base station for each PLMN.
  • the core network device receives the first message from the first base station.
  • the core network device sends a second message to the first base station, where the second message includes indication information of a network slice supported by the PLMN served by the core network device.
  • the network slice supported by the core network device for different PLMNs may be pre-configured by the network management device.
  • the network management device is Operation Administration and Maintenance (OAM), and the supported network slice may also be The updated network slice (for example, the OAM is updated for the core network, or is updated for other reasons), which is not limited by the embodiment of the present invention.
  • OAM Operation Administration and Maintenance
  • the first base station can provide information help when the first base station selects the core network device for the terminal device by receiving the indication information of the network slice supported by the core network device in the case of the serving PLMN, and can more accurately serve the terminal device.
  • the session selects the core network device.
  • the terminal device accesses the first PLMN, and the network slice corresponding to the session that needs to be served by the core network device is the network slice 4.
  • the first core network device supports network slice 1, network slice 2, network slice 3; in the case of serving the second PLMN, the first core network device supports network slice 1, network slice 4
  • the second core network device supports network slice 1, network slice 4 and network slice 5. If the network slice supported by the first core network device is not fed back in the PLMN granularity, it can be seen that the first core network device supports the network slice 1, the network slice 2, the network slice 3, and the network slice 4; the second core network device supports the network slice. 1.
  • Network slice 4 and network slice 5 such that the first base station is likely to select the core network device serving the session of the terminal device as the first core network device, but since the first core network device is serving the first PLMN In the case that the network slice 4 is not supported, the selection of the core network device is incorrect.
  • the first base station can be prevented from selecting the first core network device for the session of the terminal device, and the accuracy of selecting the core network device for the session of the terminal device is improved.
  • the first base station receives the second message sent by the core network device.
  • the core network device may send, to the first base station, indication information of the network slice supported by the core network device in the case of serving the PLMN indicated by the PLMN identifier; or The core network device sends indication information of the network slice supported by all served PLMNs to the first base station.
  • the core network device may feed back indication information of the network slice respectively supported in the case of providing services for each PLMN.
  • the communication interface between the first base station and the core network device is represented by N2 or NG.
  • the first message sent by the first base station to the core network device may be an N2 interface setup request or a base station configuration update (eg, gNB configuration update) message, and the first base station receives the core from the core.
  • the N2 interface setup failure or the base station configuration update failure (for example, gNB configuration updatefailure) message may be sent by the core network device through the N2 interface establishment failure message or the update failure message to send the core in the case of the serving PLMN.
  • the indication information of the network slice supported by the network device may also obtain the indication information of the network slice supported by the core network device in the case of the serving PLMN, so as to reduce the supported network slice for obtaining. Another interaction, speeding up the acquisition of instructions for network slicing.
  • the first message sent by the first base station to the core network device is also an N2 interface setup request or a base station configuration update message, and the first base station receives an N2 interface setup response message or a base station configuration update from the core network device.
  • the core network device may send an indication message of the network slice supported by the core network device in the case of the serving PLMN by using the N2 interface setup response message or the core network device configuration update acknowledgement message, such that A base station can obtain the indication information of the network slice supported by the core network device in the case of the serving PLMN, which helps to improve the convenience of obtaining the indication information of the network slice.
  • a communication interface exists between the first base station and the core network device.
  • the first message is an acquisition request
  • the core network device may send, by using a response message, indication information of a network slice supported by the core network device in the case of the serving PLMN.
  • the first message sent by the first base station to the core network device may be a base station configuration update (eg, gNB configuration update) message, and the first base station receives a base station configuration update failure (eg, gNB configuration update failure) from the core network device.
  • the message the core network device may send the indication information of the network slice supported by the core network device in the case of the serving PLMN by the update failure message.
  • the first message sent by the first base station to the core network device is also a base station configuration update message
  • the first base station receives a base station configuration update acknowledgement (eg, gNB configuration update ACK) message from the core network device
  • the core network device can pass
  • the core network device configuration update confirmation message is used to send the indication information of the network slice supported by the core network device in the case of the serving PLMN, so that the first base station can obtain the indication information of the network slice supported by the core network device in the case of the serving PLMN, Helps improve the convenience of obtaining indications of network slices.
  • step 502 can be implemented independently, as long as step 502, the core network device determines an indication of the network slice supported by the core network device in the case of the serving PLMN. Information can be. For example, after the core network device determines that the network slice supported by the core network device is updated in the case of the serving PLMN, step 502 may be actively implemented. In this case, the second message is an AMF configuration update message (for example, AMF configuration update). Instructing the first base station to update the indication information of the network slice supported by the core network device in the case of the serving PLMN.
  • AMF configuration update message for example, AMF configuration update
  • the description of the PLMN in the embodiment of the present invention is also applicable to the PLMN supported by the core network device, which is not limited in this embodiment of the present invention.
  • the first base station may obtain, by using the core network device, the indication information of the network slice supported by the core network device in the case of the serving PLMN, and improve the network slice supported by the core network device by using the PLMN granularity feedback.
  • a base station selects the accuracy of the core network device for the session of the terminal device.
  • the access network device is described by taking a base station as an example.
  • the communication method relates to a terminal device, a source base station, a target base station, and a core network device. 6 corresponds to a communication method in a case where the core network device determines that the handover preparation fails, the source base station is a base station currently establishing a communication connection with the terminal device, and the target base station is a base station requesting to switch the session of the terminal device to.
  • the communication method includes steps 601 to 606, which are described in detail below.
  • the source base station sends a first handover request to the core network device.
  • the source base station and the core network device have a communication interface, for example, an N2 interface or an NG interface. Thus, the source base station and the core network device can communicate with each other.
  • the first handover request is used to request that the session of the terminal device be handed over from the source base station to the target base station, for example, the first handover request is handover required.
  • the first handover request includes information of the target base station and an identifier of a session requesting handover.
  • the information of the target base station may enable the core network device to determine the base station/cell to which the terminal device's session is to be handed over; the identity of the session requesting the handover may cause the core network device to determine the session to be handed over.
  • the session requesting the handover may be one or more, and different sessions may correspond to different network slices. The indication information of the network slice corresponding to different network slices is different.
  • the target base station information includes a base station identifier of the target base station, an identifier of a central unit included in the target base station, an identifier of a distributed unit included in the target base station, and a physical cell identifier included in the target base station. And at least one of a cell global identifier included in the target base station.
  • the first handover request further includes indication information of the network slice corresponding to the session requesting the handover.
  • the core network device can directly determine the network slice corresponding to the session to be switched, saves the time for searching the network slice corresponding to the session, reduces the handover delay, and improves the handover success rate.
  • the first handover request may not include the indication information of the network slice corresponding to the session requesting the handover, which is not limited in this embodiment of the present invention.
  • the core network device is used as the AMF network element as an example. If the AMF network element cannot save the network slice indication information corresponding to the session, the network switch indication information corresponding to each session needs to be carried in the first handover request.
  • the first session includes multiple data flows, for example, the data flow is a traffic flow or a QoS flow, and the first handover request further includes an identifier of the data flow that needs to be established corresponding to the session (for example, a data flow).
  • the identifier includes a QoS flow ID), and further includes QoS information (for example, priority information) corresponding to each of the plurality of data streams included in the session.
  • the AMF network element first receives the first handover request message sent by the source base station, and the AMF network element sends the second handover request message to the target base station, where
  • the second handover request message needs to include the identifier of the data flow included in the session to be switched and the QoS information of the data flow, but the information is not saved in the AMF network element, so if the information is carried in the first handover request, In this way, the AMF network element does not need to go to the SMF network element to obtain the information, thereby saving the search time, reducing the handover delay, and improving the switching efficiency.
  • the first handover request further includes aggregate maximum bit rate (AMBR) information corresponding to the session, such as subscribed AMBR information.
  • AMBR aggregate maximum bit rate
  • the target base station can perform flow control of the data flow according to the information, but the information needs to be sent by the core network device to the target base station, so that the core network device includes the AMF network element and the SMF network element on the core network side, because the AMF network element does not store the For information, in order to reduce the time for the AMF network element to find the information to the SMF network element, by including the information in the first handover request, the search time can be saved, the handover delay is reduced, and the handover efficiency is improved.
  • AMBR aggregate maximum bit rate
  • the first handover request further includes first indication information, where the indication information indicates that the source base station is uncertain or does not know the network slice supported by the target base station, so that the core network device knows that the source base station does not know the network slice supported by the target base station.
  • Information so that the information of the network slice supported by the target base station can be carried in the first handover response message. This reduces the interaction between the source base station and the target base station, and improves the information acquisition efficiency of the network slice.
  • the target base station may be a base station having a communication interface with the source base station; or may be a base station having no communication interface with the source base station.
  • the first handover request may include second indication information that does not have a communication interface between the source base station and the target base station, so that the core network device feeds back information about the network slice supported by the target base station.
  • the source base station selects one of the base stations that have a communication interface with the source base station to determine the target base station. Further, the determined target base station supports the network slice corresponding to all or part of the session requesting the handover, so as to avoid the handover failure caused by the target base station not supporting the network slice of all the sessions requesting the handover, thereby reducing the number of handover failures. To increase the probability of successful handover.
  • the source base station may, when receiving the measurement report sent by the terminal device, select the target base station according to the measurement report, and perform step 601 to send a handover request to the target base station.
  • the measurement report includes measurement report values for at least one of the cell and the base station.
  • the included cell may be a cell included in the source base station, or may be a cell included in another base station. If the measurement report includes the measurement report value of the base station, the included base station may be the source base station or other base stations.
  • the embodiment of the present invention does not limit the number of cells and the number of base stations included in the measurement report.
  • the core network device determines indication information of a network slice corresponding to the session requesting the handover.
  • step 602 is an optional step. If the first handover request does not include the indication information of the network slice corresponding to the session, the core network device may search and request the handover according to the identifier of the session that is requested to be switched, and the correspondence between the identifier of the stored session and the indication information of the network slice.
  • the correspondence stored by the core network device may include an identifier of one or more sessions of the terminal device and indication information of the corresponding network slice.
  • the core network device may directly determine the indication information of the network slice corresponding to the session requesting the handover, so that the core network device lookup request switching may be reduced.
  • the time of the indication of the network slice corresponding to the session may be reduced.
  • the first handover request may include information of the target base station, and the core network device determines information of the network slice supported by the target base station according to the information of the target base station.
  • the information of the network slice includes indication information of the supported network slice.
  • the session requesting the handover is set to the session E1. If there is a communication interface between the target base station and the core network device, if the core network device has acquired the information of the first network slice supported by the target base station.
  • the indication information of the first network slice supported by the target base station may be directly determined. If the information of the first network slice supported by the target base station is not obtained by the core network device, the first network slice supported by the target base station may be obtained from the target base station. Instructions.
  • the core network device may determine whether the indication information of the first network slice supported by the target base station includes the indication information of the second network slice corresponding to the session E1, and if yes, the target base station supports the network slice corresponding to the session E1; If it is included, it indicates that the target base station does not support the network slice corresponding to the session E1.
  • the core network device may determine that the target base station does not support the network slice corresponding to the session requesting the handover.
  • the core network device may perform step 605 in FIG. 6, and the core network device sends a first handover response message to the source base station.
  • the first handover response message may be a first handover failure message
  • the first handover failure message includes a rejection indication information, which is used to indicate that the target base station does not support the network slice corresponding to all the sessions requesting the handover.
  • the refusal indication information may be indicated by an IE, a flag, a cause, or the like, which is not limited by the embodiment of the present invention.
  • the core network device performs step 603 in FIG. 6, and the core network device sends a second handover request to the target base station.
  • the core network device sends a second handover request to the target base station.
  • the second handover request is a Handover Request.
  • the second handover request includes an identifier of the session corresponding to the session requesting the handover and indication information of the network slice corresponding to the session requesting the handover.
  • the second handover request includes a session identifier of all sessions that the source base station requests to switch, and indication information of a network slice corresponding to each session.
  • the core network device may divide the session that the source base station requests to switch into the first session and the second session, where the network slice corresponding to the first session is supported by the target base station, and second.
  • the network slice corresponding to the session is not supported by the target base station.
  • the second handover request may include only the identifier of the first session and the indication information of the network slice corresponding to the first session, or the second handover request includes the identifier of the first session, the identifier of the second session, and the first session.
  • the indication information of the corresponding network slice and the indication information of the network slice corresponding to the second session does not limit this.
  • the target base station receives the second handover request.
  • the target base station sends a second handover failure message to the core network device.
  • the target base station receives the second handover request from the core network device, and determines whether the service can be provided for the included session. If the target base station cannot provide service for any of the sessions, step 604 in FIG. 6 sends the message to the core network device.
  • the second handover response message may be a second handover failure message, for example, handover request failure or handover failure; or the second handover failure message is a handover preparation failure message.
  • the second handover failure message includes reason information corresponding to the session rejecting the handover.
  • the reason information of the session that is refused to be switched may be a network slice corresponding to the session in which the target base station does not support the handover, or the network slice resource corresponding to the session that the target base station supports to reject the handover is limited.
  • the core network device receives the second handover failure message sent by the target base station.
  • the core network device sends a first handover response message to the source base station.
  • the core network device sends a first handover response message to the source base station.
  • the first handover response message is a first handover failure message, for example, the first handover failure message is a handover preparation failure message.
  • the first handover response message includes a reject indication information, where the reject indication information is used to indicate cause information corresponding to a session in the session that is rejected by the target base station due to network slice.
  • the first handover failure message includes an identifier of the rejected session, and a reason information that the session corresponding to the identifier is rejected.
  • the identifier of the session that the source network device requests to switch to the target base station is sent to the target base station
  • the identifier of the session that rejects the handover included in the first handover failure message rejects the reason information corresponding to the session.
  • the reason information corresponding to the session rejecting the handover included in the second handover failure message and the session information rejecting the handover are the same.
  • the target network station supports the corresponding network slice.
  • the first handover failure message includes the identifier of the first rejection session, the reason information corresponding to the first rejection session, the identifier of the second rejection session, and the reason information corresponding to the second rejection session.
  • the first reject session is a session that is rejected in the second handover failure message
  • the second reject session is a session in the session requesting handover that the target base station does not support its corresponding network slice.
  • the identifier of the second reject session and the cause information corresponding to the second reject session are determined by the core network device.
  • the core network device carries information about the network slice supported by the target base station in the first handover response message.
  • the first handover request includes the first indication information that the source base station does not determine the network slice supported by the target base station, or the core network device determines the source according to the indication that the source base station and the target base station carried in the first handover request do not have a communication interface.
  • the base station does not know the network slice supported by the target base station. This reduces the interaction between the source base station and the target base station, and improves the information acquisition efficiency of the network slice.
  • the source base station sends an RRC connection release message to the terminal device.
  • step 606 reference may be made to the detailed description of the step 404 in the embodiment shown in FIG. 4, and details are not described herein again.
  • the source base station after the source base station sends the handover request to the core network device, the source base station can learn the reason information that the rejected handover session is rejected by the network slice of the target base station, so that the other needs to request to switch to the target base station.
  • the session provides information assistance.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can switch to the target base station, which improves the probability of successful handover.
  • FIG. 7 another communication method is provided according to an embodiment of the present invention.
  • the access network device is described by taking a base station as an example.
  • the communication method involves a terminal device, a source base station, a target base station, and a core network device.
  • FIG. 7 corresponds to a communication method in which the core network device determines that the handover is successful.
  • the source base station is a base station that currently establishes a communication connection with the terminal device
  • the target base station is a base station that requests to switch the session of the terminal device to.
  • the communication method includes steps 701 to 707, which are described in detail below.
  • the source base station sends a first handover request to the core network device.
  • the core network device determines indication information of a network slice corresponding to the session requesting the handover.
  • the core network device sends a second handover request to the target base station.
  • the target base station sends a second handover request acknowledgement message to the core network device.
  • the second handover request acknowledgement message includes an identifier of the session that confirms the handover.
  • the second handover request acknowledgement message is handover request acknowledge.
  • the first handover response message may further include an identifier of the session that rejects the handover and a reason information corresponding to the session that rejects the handover.
  • the second handover request acknowledgement message further includes retransmission indication information corresponding to the session that rejects the handover.
  • the retransmission indication information is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to the network slice supported by the target base station.
  • the case where the rejected session is the session B1 and the session B1 corresponding to the network slice 1 is used as an example.
  • the reason information that the session B1 is refused to be switched may be that the target base station does not support the network slice 1 corresponding to the session B1, or may be the target base station.
  • the target base station determines that the retransmission indication information corresponding to the session B1 is: allowing the terminal device to route the data flow included in the session B1 to the network slice 2 supported by the target base station.
  • the target base station determines that the retransmission indication information corresponding to the session B1 is: the terminal device is not allowed to route the data flow included in the session B1 to the target base station. Supported network slices.
  • the handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • the second handover request acknowledgement message in the embodiment of the present invention and the identifier of the session, the identifier of the session that rejects the handover, and the reason information corresponding to the session that refuses to switch are referred to in the embodiment shown in FIG.
  • the second handover request acknowledgement message is sent to the core network device. I will not repeat them here.
  • the core network device sends a first handover request acknowledgement message to the source base station.
  • the core network device sends a first handover response message to the source base station.
  • the first handover response message is a first handover request acknowledgement message.
  • the first handover request acknowledgement message is a handover command.
  • the first handover request acknowledgement message includes an identification of the session confirming the handover.
  • the first handover corresponding message may further include an identifier of the session that rejects the handover and a reason information corresponding to the session that rejects the handover.
  • the core network device sends the identifiers of all the sessions that the source base station requests to switch to the target base station, the identifier of the session that rejects the handover included in the first handover request acknowledgement message and the reason corresponding to the session that rejects the handover
  • the information is the same as the identifier of the session rejecting the handover included in the second handover request acknowledgement message and the reason information corresponding to the session rejecting the handover.
  • the target network station supports the corresponding network slice.
  • the first handover request acknowledgement message includes the identifier of the first reject session, the cause information corresponding to the first reject session, the identifier of the second reject session, and the cause information corresponding to the second reject session.
  • the first reject session is a session that is rejected in the second handover request acknowledgement message
  • the second reject session is a session in the session requesting handover that the target base station does not support its corresponding network slice.
  • the identifier of the second reject session and the cause information corresponding to the second reject session are determined by the core network device.
  • the core network device carries information about the network slice supported by the target base station in the first handover response message.
  • the first handover request includes the first indication information that the source base station does not determine the network slice supported by the target base station, or the core network device determines the source according to the indication that the source base station and the target base station carried in the first handover request do not have a communication interface.
  • the base station does not know the network slice supported by the target base station. This reduces the interaction between the source base station and the target base station, and improves the acquisition efficiency of the indication information of the network slice.
  • the source base station sends a handover command to the terminal device.
  • the terminal device sends a handover confirmation message to the target base station.
  • the source base station after the source base station sends the handover request to the core network device, the source base station can learn the reason information that the rejected handover session is rejected by the network slice of the target base station, so that the other needs to request to switch to the target base station.
  • the session provides information assistance.
  • the source base station needs to switch the session of the same network slice, it can directly determine whether it can switch to the target base station, which improves the probability of successful handover.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station can be a source base station for implementing the embodiment of FIG. 3 or FIG.
  • the source base station includes:
  • the sending unit 801 is configured to send a handover request to the target base station, where the handover request is used to request to switch a session of the terminal device from the source base station to the target base station, where the handover request includes an identifier and a session of the session requesting the handover The indication information of the network slice corresponding to the session;
  • the receiving unit 802 is configured to receive a handover response message from the target base station, where the handover response message includes a reject indication information, where the reject indication information is used to indicate that the target base station rejects the handover in the session due to network slicing The reason information for the session.
  • the requesting handover session includes a first session; or the requesting handover session includes the first session and the second session;
  • the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the handover response message is a handover request acknowledgement message
  • the handover response message further includes retransmission indication information corresponding to the session that the target base station rejects the handover, and the retransmission indication corresponding to the session The information is used to indicate whether the terminal device is allowed to route the data flow included in the session rejecting the handover to a network slice supported by the target base station.
  • the source base station sends a handover command to the terminal device, where the handover command includes retransmission corresponding to the session that the target base station rejects the handover.
  • the handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • the sending unit 801 is further configured to: when the handover response message is a handover failure message, send a radio resource control RRC connection release message to the terminal device.
  • the RRC connection release message includes indication information of a network slice supported by a neighboring cell of the source cell; or indication information of a network slice supported by the TA/RA of the neighboring cell of the source cell; or includes the source Information about the network slice supported by the neighbor base station of the base station.
  • the transmitting unit may be a transmitter and the receiving unit may be a receiver.
  • FIG. 9 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station can be a target base station for implementing the embodiment of FIG. 3 or FIG.
  • the target base station includes:
  • the receiving unit 901 receives a handover request from a source base station, where the handover request is used to request to switch a session of the terminal device from the source base station to the target base station, where the handover request includes an identifier of the session requesting the handover and the The indication information of the network slice corresponding to the session;
  • the sending unit 902 is configured to send a handover response message to the source base station, where the handover response message includes a reject indication information, where the reject indication information is used to indicate that the target base station rejects the handover in the session due to network slicing.
  • the reason information corresponding to the session is configured to send a handover response message to the source base station, where the handover response message includes a reject indication information, where the reject indication information is used to indicate that the target base station rejects the handover in the session due to network slicing.
  • the reason information corresponding to the session.
  • the requesting handover session includes a first session; or the requesting handover session includes the first session and the second session;
  • the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the handover response message further includes retransmission indication information corresponding to the session that is rejected by the target base station, and the retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to switch the rejection.
  • the data stream contained in the session is routed to the network slice supported by the target base station.
  • the handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or an identifier of the rejected data flow.
  • the receiving unit 901 is further configured to receive a handover confirmation message from the terminal device;
  • the sending unit 902 is further configured to send a path transfer request to the core network device, where the path transfer request includes an identifier of the session that the target base station confirms to switch and an identifier of the session that the target base station refuses to switch;
  • the receiving unit 901 is further configured to receive a path transfer request response message from the core network device, where the path transfer request response message includes an identifier of a session that successfully transfers the path.
  • the path transfer request further includes indication information of a network slice corresponding to the session that the target base station rejects the handover.
  • the path transfer request further includes reason information corresponding to the session that the target base station rejects the handover.
  • FIG. 10 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • the core network device is used to implement the embodiment of FIG. As shown in FIG. 10, the core network device includes:
  • the receiving unit 1001 is configured to receive a path transfer request from the target base station, where the path transfer request includes an identifier of the session that the target base station confirms to switch, and an identifier of the session that the target base station rejects the handover;
  • the processing unit 1002 is configured to perform a path transfer process on the session that confirms the handover, and perform a deactivation or deletion process on the session that rejects the handover;
  • the sending unit 1003 is configured to send a path transfer request response message to the target base station, where the path transfer request response message includes an identifier of the session of the successful transfer path.
  • the path transfer request further includes indication information of a network slice corresponding to the session that the target base station rejects the handover.
  • the path transfer request includes reason information corresponding to the session that the target base station rejects the handover.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the processing unit can be implemented in the form of a processor.
  • FIG. 11 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station can be a first base station for implementing the embodiment of FIG.
  • the base station includes:
  • the sending unit 1101 is configured to send, to the core network device, a first message, where the first message is used to obtain information about a network slice supported by the core network device for the PLMN;
  • the receiving unit 1102 is configured to receive a second message from the core network device, where the second message includes information about a network slice supported by the PLMN served by the core network device.
  • FIG. 12 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • the core network device is used to implement the embodiment of FIG. As shown in FIG. 12, the core network device includes:
  • the receiving unit 1201 is configured to receive a first message from the first base station, where the first message is used to obtain information about a network slice supported by the core network device for the PLMN;
  • the sending unit 1202 is configured to send, to the first base station, a second message, where the second message includes information about a network slice supported by the PLMN served by the core network device.
  • FIG. 13 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station can be a source base station for implementing the embodiment of FIG. 6 or FIG.
  • the source base station includes:
  • the sending unit 1301 is configured to send, to the core network device, a first handover request, where the first handover request is used to request to switch a session of the terminal device from the source base station to the target base station, where the first handover request includes the target The information of the base station and the identifier of the session requesting the handover;
  • the receiving unit 1302 is configured to receive a first handover response message from the core network device, where the first handover response message includes a reject indication information, where the reject indication information is used to indicate that the session is caused by the network slice The reason information corresponding to the session that the target base station rejects the handover.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the first handover response message is a first handover request acknowledgement message
  • the first handover response message further includes retransmission indication information corresponding to the session that the target base station rejects the handover, where The retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session that rejects the handover to the network slice supported by the target base station.
  • the sending unit 1301 is further configured to: when the first handover response message is a first handover request acknowledgement message, send a handover command to the terminal device, where the handover command includes the target The retransmission indication information corresponding to the session that the base station rejects the handover.
  • the first handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or is rejected. The identity of the data stream.
  • the sending unit 1301 is further configured to send an RRC connection release message to the terminal device if the first handover response message is a first handover failure message.
  • the RRC connection release message includes the indication information of the network slice supported by the neighboring cell of the source base station; or the indication information of the network slice supported by the TA/RA of the neighboring cell of the source base station; or Information including network slices supported by neighboring base stations of the source base station.
  • the first handover request acknowledgement message further includes information about a network slice supported by the target base station.
  • the first handover request further includes indication information of the network slice corresponding to the session requesting the handover.
  • the first handover request further includes an identifier of the data flow that the session requesting the handover needs to establish and QoS information corresponding to the data flow.
  • the first handover request further includes an aggregate maximum bit rate AMBR information corresponding to the session.
  • FIG. 14 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • the base station can be a target base station for implementing the embodiment of FIG. 6 or FIG.
  • the target base station includes:
  • the receiving unit 1401 is configured to receive a second handover request from the core network device, where the second handover request includes an identifier of the session and indication information of the network slice corresponding to the session;
  • the sending unit 1402 is configured to send, to the source base station, a second handover response message, where the second handover response message includes rejection indication information, where the rejection indication information is used to indicate that the target is in the session due to network slicing The reason information corresponding to the session that the base station refuses to switch.
  • the session included in the second handover request is a first session; or the session included in the second handover request is the first session and the second session;
  • the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the second handover response message is a second handover request acknowledgement message
  • the second handover response message further includes retransmission indication information corresponding to the session that is rejected by the target base station, where The retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session that rejects the handover to the network slice supported by the target base station.
  • the second handover request acknowledgement message further includes an identifier of the rejected bearer of the session included in the second handover request or The identity of the rejected data stream.
  • FIG. 15 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • the core network device is used to implement the embodiment of Figure 6 or Figure 7.
  • the core network device includes:
  • the receiving unit 1501 is configured to receive a first handover request from a source base station, where the first handover request is used to request to switch a session of the terminal device from the source base station to the target base station, where the first handover request includes the target The information of the base station and the identifier of the session requesting the handover;
  • the sending unit 1502 is configured to send, to the source base station, a first handover response message, where the first handover response message includes rejection indication information, where the rejection indication information is used to indicate that the target is in the session due to network slicing The reason information corresponding to the session that the base station refuses to switch.
  • the reason information includes: the target base station does not support the network slice corresponding to the session that rejects the handover, or the network slice resource corresponding to the session that is rejected by the target base station is limited.
  • the first handover response message is a first handover request acknowledgement message
  • the first handover response message further includes retransmission indication information corresponding to the session that the target base station rejects the handover, where The retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session that rejects the handover to the network slice supported by the target base station.
  • the first handover request acknowledgement message further includes an identifier of the rejected bearer of the session requesting the handover or is rejected. The identity of the data stream.
  • the first handover request acknowledgement message further includes information about a network slice supported by the target base station; or, the target base station includes The indication information of the network slice supported by the TA/RA to which the cell belongs.
  • the first handover request further includes indication information of the network slice corresponding to the session requesting the handover.
  • the first handover request further includes an identifier of the data flow that the session requesting the handover needs to establish and QoS information corresponding to the data flow.
  • the first handover request further includes an aggregate maximum bit rate AMBR information corresponding to the session.
  • the sending unit 1502 is further configured to send a second handover request to the target base station, where the second handover request includes an identifier of the session and indication information of a network slice corresponding to the session;
  • the receiving unit 1501 is further configured to receive a second handover response message from the target base station, where the second handover response message includes the rejection indication information.
  • the session included in the second handover request is a first session; or the session included in the second handover request is the first session and the second session;
  • the network slice corresponding to the first session is supported by the target base station, and the network slice corresponding to the second session is not supported by the target base station.
  • the second handover response message is a second handover request acknowledgement message
  • the second handover response message further includes retransmission indication information corresponding to the session that is rejected by the target base station, where The retransmission indication information corresponding to the session is used to indicate whether the terminal device is allowed to route the data flow included in the session that rejects the handover to the network slice supported by the target base station.
  • the second handover request acknowledgement message further includes an identifier of the rejected bearer of the session included in the second handover request or The identity of the rejected data stream.
  • each determining unit can be implemented in the form of a processor.
  • FIG. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • the terminal device may be a terminal device for implementing the embodiment of FIG. 4 or FIG. 6.
  • the terminal device includes:
  • the receiving unit 1601 is configured to receive a radio resource control RRC connection release message from the source base station;
  • the processing unit 1602 is configured to release an RRC connection, where the RRC connection release message includes indication information of a network slice supported by a neighboring cell of the source cell, or an indication of a network slice supported by the TA/RA of the neighboring cell of the source cell. Information; or, information including network slices supported by neighboring base stations of the source base station.
  • FIG. 17 is a schematic structural diagram of another base station according to an embodiment of the present invention.
  • the base station 1700 shown in FIG. 17 includes: a processor 1701 and a transceiver 1702.
  • the transceiver 1702 is configured to support the base station 1700 and the foregoing. Information transmission between core network devices or other base stations involved in the embodiments.
  • the processor 1701 and the transceiver 1702 are communicatively coupled, such as by a bus.
  • the base station 1700 can also include a memory 1703.
  • the memory 1703 is used to store program codes and data for execution by the base station 1700, and the processor 1701 is configured to execute application code stored in the memory 1703 to implement the actions of the base station provided by any of the embodiments shown in FIG. 3 to FIG.
  • the base station may include one or more processors, and the structure of the base station 1700 does not constitute a limitation on the embodiments of the present application.
  • the processor 1701 may be a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 1703 may include a volatile memory such as a random access memory (RAM); the memory 1703 may also include a non-volatile memory such as a read-only memory (read- Only memory, ROM), flash memory, hard disk drive (HDD) or solid-state drive (SSD); the memory 1703 may also include a combination of the above types of memories.
  • RAM random access memory
  • ROM read- Only memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 1703 may also include a combination of the above types of memories.
  • a computer storage medium which can be used to store computer software instructions used by the base station in the embodiments shown in FIG. 8, FIG. 9, FIG. 11, FIG. 13, and FIG.
  • the program designed for the base station in the above embodiment is executed.
  • the storage medium includes, but is not limited to, a flash memory, a hard disk, a solid state disk.
  • a computer program product is also provided.
  • the computer product is operated by the computing device, the communication designed for the base station in the foregoing embodiments of FIG. 8, FIG. 9, FIG. 11, FIG. 13, and FIG. method.
  • FIG. 18 is a schematic structural diagram of another core network device according to an embodiment of the present invention.
  • the core network device 1800 shown in FIG. 18 includes: a processor 1801 and a transceiver 1802.
  • the transceiver 1802 is configured to support Information transmission between the core network device 1800 and the base stations involved in the above embodiments.
  • the processor 1801 and the transceiver 1802 are communicatively coupled, such as by a bus.
  • the core network device 1800 can also include a memory 1803.
  • the memory 1803 is configured to store program code and data for execution by the core network device 1800, and the processor 1801 is configured to execute the application code stored in the memory 1803 to implement any of the implementations shown in FIG. 4, FIG. 5, FIG. 6, or FIG. The action of the core network device provided by the example.
  • the core network device may include one or more processors, and the structure of the core network device 1800 does not constitute a limitation on the embodiments of the present application.
  • the processor 1801 can be a CPU, an NP, a hardware chip, or any combination thereof.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the memory 1803 may include a volatile memory such as a RAM; the memory 1803 may also include a non-volatile memory such as a ROM, a flash memory, a hard disk or a solid state hard disk; the memory 1803 may also include a combination of the above-described types of memory.
  • a volatile memory such as a RAM
  • the memory 1803 may also include a non-volatile memory such as a ROM, a flash memory, a hard disk or a solid state hard disk
  • the memory 1803 may also include a combination of the above-described types of memory.
  • a computer storage medium which can be used to store computer software instructions used by the core network device in the embodiments shown in FIG. 10, FIG. 12, and FIG. 15, which are included to perform the foregoing implementation.
  • the program is designed for the core network device.
  • the storage medium includes, but is not limited to, a flash memory, a hard disk, a solid state disk.
  • a computer program product is also provided.
  • the communication method designed for the core network device in the embodiment shown in FIG. 10, FIG. 12 and FIG. 15 may be executed.
  • the terminal device in the above-described embodiment shown in FIG. 16 can be implemented by the terminal device 1900 shown in FIG.
  • FIG. 19 is a schematic structural diagram of another terminal device according to an embodiment of the present invention.
  • the terminal device 1900 shown in FIG. 19 includes: a processor 1901 and a transceiver 1902, where the transceiver 1902 is configured to support a terminal device. Information transmission between 1900 and the base stations involved in the above embodiments.
  • the processor 1901 and the transceiver 1902 are communicatively coupled, such as by a bus.
  • the terminal device 1900 can also include a memory 1903.
  • the memory 1903 is configured to store program code and data for execution by the terminal device 1900, and the processor 1901 is configured to execute the application code stored in the memory 1903 to implement the action of the terminal device provided by any of the embodiments shown in FIG. 4 and FIG. .
  • the terminal device may include one or more processors, and the structure of the terminal device 1900 does not constitute a limitation on the embodiments of the present application.
  • the processor 1901 can be a CPU, an NP, a hardware chip, or any combination thereof.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the memory 1903 may include volatile memory such as RAM; the memory 1903 may also include non-volatile memory such as a ROM, a flash memory, a hard disk or a solid state hard disk; the memory 1903 may also include a combination of the above-described types of memory.
  • a computer storage medium which can be used to store computer software instructions used by the terminal device in the embodiment shown in FIG. 16, which is configured to perform the design of the terminal device in the foregoing embodiment. program of.
  • the storage medium includes, but is not limited to, a flash memory, a hard disk, a solid state disk.
  • a computer program product is also provided.
  • the communication method designed for the terminal device in the foregoing embodiment of FIG. 16 can be executed.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开了一种通信方法及源基站、目标基站、核心网设备、终端设备，其中方法包括：源基站向目标基站发送切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；所述源基站接收来自所述目标基站的切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。采用本申请，可以提高切换成功的概率。

Description

通信方法及源基站、目标基站、核心网设备、终端设备 技术领域
本发明涉及通信技术领域，尤其涉及一种通信方法及源基站、目标基站、核心网设备、终端设备。
背景技术
5G引入了网络切片的概念，一个终端设备当前进行的会话存在多种，而不同的会话可能需要与会话相对应的网络切片来提供服务。这样在终端设备需要接入网络并建立多个会话的情况下，所连接的基站需要支持终端设备中的全部会话或者部分会话对应的网络切片。
在这种情形下，怎么提高切换成功的概率，是一个值得考虑的问题。
发明内容
本发明实施例所要解决的技术问题在于，提供一种通信方法及源基站、目标基站、核心网设备、终端设备，以期提高切换成功的概率。
第一方面，为本发明实施例提供了一种通信方法，包括：
源基站向目标基站发送切换请求，切换请求用于请求将终端设备的会话从源基站切换至目标基站，切换请求包括请求切换的会话的标识和会话对应的网络切片的指示信息；源基站接收来自目标基站的切换响应消息，切换响应消息包括拒绝指示信息，拒绝指示信息用于指示由于网络切片导致会话中被目标基站拒绝切换的会话对应的原因信息。
在第一方面中，源基站能够通过目标基站获知被拒绝切换的会话对应的因目标基站的网络切片而导致拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
结合第一方面，在一种可选的实现方式中，在切换响应消息为切换请求确认消息的情况下，源基站向终端设备发送切换命令，切换命令包括被目标基站拒绝切换的会话对应的重发指示信息。会话对应的重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。可选的，重发指示信息可以不指明具体路由到的具体的网络切片。这样以便于终端设备获知哪些会话可以在拒绝之后仍旧可以在目标基站中重新建立，提高了会话切换的灵活性。
结合第一方面，在一种可选的实现方式中，该方法还包括：在切换响应消息为切换失败消息的情况下，源基站向终端设备发送无线资源控制RRC连接释放消息。可选的，RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括源基站的邻基站支持的网络切片的信息。以使终端设备尽早的释放RRC连接，避免后续的无线链路失败过程，减少了信令开销。
第二方面，为本发明实施例提供了一种通信方法，包括：
目标基站接收来自源基站的切换请求，切换请求用于请求将终端设备的会话从源基站切换至目标基站，切换请求包括请求切换的会话的标识和会话对应的网络切片的指示信息；目标基站向源基站发送切换响应消息，切换响应消息包括拒绝指示信息，拒绝指示信息用于指示由于网络切片导致会话中被目标基站拒绝切换的会话对应的原因信息。
在第二方面中，目标基站能够向源基站通知被拒绝切换的会话对应的因目标基站的网络切片而导致拒绝的原因信息，这样为源基站中其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
结合第二方面，在一种可选的实现方式中，目标基站接收来自终端设备的切换确认消息；目标基站向核心网设备发送路径转移请求，路径转移请求包括目标基站确认切换的会话的标识和目标基站拒绝切换的会话的标识；目标基站接收来自核心网设备的路径转移请求响应消息，路径转移请求响应消息包括成功转移路径的会话的标识。以使核心网设备对确认切换的会话进行路径转移处理。
第三方面，为本发明实施例提供了一种通信方法，包括：
核心网设备接收来自目标基站的路径转移请求，路径转移请求包括目标基站确认切换的会话的标识和目标基站拒绝切换的会话的标识；核心网设备对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理；核心网设备向目标基站发送路径转移请求响应消息，路径转移请求响应消息包括成功转移路径的会话的标识。
在第三方面中，通过在路径转移请求中携带这确认切换的会话和拒绝切换的会话的标识，核心网设备能够从所存储的终端设备的全部会话中确定出已处于去激活状态的会话，这样核心网设备将无需对这一类会话进行处理，只需要对确认切换的会话和拒绝切换的会话进行处理，提高了处理效率。
结合第一方面或第二方面，在一种可能的实现方式中，请求切换的会话包括第一会话，第一会话对应的网络切片是目标基站支持的，这一情况下，目标基站不需要针对第二会话进行接入控制，节省了针对第二会话进行接入控制的处理时间。或者，请求切换的会话包括第一会话和第二会话；第一会话对应的网络切片是目标基站支持的，第二会话对应的网络切片是目标基站不支持的，这样目标基站可以直接确定自身不支持的会话，提高切换响应消息的确定效率。当然，也可以针对所有的需要进行切换的会话不做特别的归类处理。
结合第一方面、第二方面或第三方面，在一种可能的实现方式中，原因信息包括：目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。
结合第一方面或第二方面，在一种可能的实现方式中，在切换响应消息为切换请求确认消息的情况下，切换响应消息还包括被目标基站拒绝切换的会话对应的重发指示信息，会话对应的重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。这样以便于终端设备获知哪些会话可以在拒绝之后仍旧可以在目标基站中重新建立，提高了会话切换的灵活性。
结合第一方面或第二方面，在一种可选的实现方式中，在切换响应消息为切换请求确认消息的情况下，切换请求确认消息还包括请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识，使得源基站可以确认被拒绝的承载或被拒绝的数据流。
结合第一方面或第二方面，在一种可选的实现方式中，切换请求响应消息还包括携带目标基站支持的网络切片的信息。这样便于目标基站通知源基站目标基站当前支持的网络切片的信息，减少了源基站和目标基站之间的交互。
结合第二方面或第三方面，在一种可选的实现方式中，路径转移请求还包括被目标基站拒绝切换的会话对应的网络切片的指示信息。这样核心网设备就可以根据被拒绝的会话对应 的网络切片与自己保存的目标小区支持的网络切片进行对比，从而可以获知被拒绝的会话是否是由于目标基站网络切片不支持的原因造成的，如果是，则核心网设备后续会触发删除(remove)会话的过程，这样可以减少这类会话在核心网设备中所占用的存储空间。如果否，那么核心网设备后续可以触发去激活(deactivate)该会话的流程，这样可以在需要激活的情况下核心网设备可以快速恢复该会话。
结合第二方面或第三方面，在一种可选的实现方式中，路径转移请求还包括被目标基站拒绝切换的会话对应的原因信息。这样通过携带原因信息，核心网设备可以针对因不同原因导致被拒绝会话执行不同的处理。
第四方面，为本发明实施例提供了一种通信方法，包括：
终端设备接收来自源基站的无线资源控制RRC连接释放消息；释放RRC连接；其中，RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括源基站的邻基站支持的网络切片的信息。
在第四方面中，终端设备可以尽早地释放RRC连接，避免后续的无线链路失败过程，减少了信令开销。
第五方面，为本发明实施例提供了一种通信方法，包括：
源基站向核心网设备发送第一切换请求，第一切换请求用于请求将终端设备的会话从源基站切换到目标基站，第一切换请求包括目标基站的信息和请求切换的会话的标识；源基站接收来自核心网设备的第一切换响应消息，第一切换响应消息包括拒绝指示信息，拒绝指示信息用于指示由于网络切片导致会话中被目标基站拒绝切换的会话对应的原因信息。
在第五方面中，源基站能够通过核心网设备获知被拒绝切换的会话由目标基站的网络切片而拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率
结合第五方面，在一种可能的实现方式中，该方法还包括：在第一切换响应消息为第一切换请求确认消息的情况下，源基站向终端设备发送切换命令，切换命令包括被目标基站拒绝切换的会话对应的重发指示信息。会话对应的重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。可选的，重发指示信息可以不指明具体路由到的具体的网络切片。这样以便于终端设备获知哪些会话可以在拒绝之后仍旧可以在目标基站中重新建立，提高了会话切换的灵活性。
结合第五方面，在一种可能的实现方式中，该方法还包括：在第一切换响应消息为第一切换失败消息的情况下，源基站向终端设备发送RRC连接释放消息。可选的，RRC连接释放消息包括源基站的邻小区支持的网络切片的指示信息；或者，包括源基站的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括源基站的邻基站支持的网络切片的信息。以使终端设备尽早的释放RRC连接，避免后续的无线链路失败过程，减少了信令开销。
第六方面，为本发明实施例提供了一种通信方法，包括：
核心网设备接收来自源基站的第一切换请求，第一切换请求用于请求将终端设备的会话从源基站切换到目标基站，第一切换请求包括目标基站的信息和请求切换的会话的标识；核心网设备向源基站发送第一切换响应消息，第一切换响应消息包括拒绝指示信息，拒绝指示信息用于指示由于网络切片导致会话中被目标基站拒绝切换的会话对应的原因信息。
在第六方面中，核心网设备能够向源基站通知被拒绝切换的会话对应的因目标基站的网 络切片而导致拒绝的原因信息，这样为源基站中其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
结合第六方面，在一种可能的实现方式中，核心网设备向源基站发送第一切换响应消息之前，该方法还包括：核心网设备向目标基站发送第二切换请求，第二切换请求包括会话的标识和会话对应的网络切片的指示信息；核心网设备接收来自目标基站的第二切换响应消息，第二切换响应消息包括拒绝指示信息。以使核心网设备向源基站通知该拒绝指示信息。
第七方面，为本发明实施例提供了一种通信方法，包括：
目标基站接收来自核心网设备的第二切换请求，第二切换请求包括会话的标识和会话对应的网络切片的指示信息；目标基站向源基站发送第二切换响应消息，第二切换响应消息包括拒绝指示信息，拒绝指示信息用于指示由于网络切片导致会话中被目标基站拒绝切换的会话对应的原因信息。
在第七方面中，目标基站可以通知核心网设备被拒绝切换的会话对应的因目标基站的网络切片而导致拒绝的原因信息，以使核心网设备将该信息通知源基站，这样为源基站中其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
结合第五方面、第六方面或第七方面，在一种可能的实现方式中，原因信息包括：目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。
结合第五方面或第六方面，在一种可能的实现方式中，第一切换请求还包括第一指示信息，该指示信息指示源基站不确定或者不知道目标基站支持的网络切片，以使核心网设备得知源基站不知道目标基站支持的网络切片信息，从而可以在第一切换响应消息携带目标基站支持的网络切片的信息。这样减少了源基站和目标基站之间的交互，提高了网络切片的信息的获取效率。
结合第五方面或第六方面，在一种可能的实现方式中，目标基站可以是与源基站之间有通信接口的基站；或者，也可以是与源基站之间没有通信接口的基站。可选的，所述第一切换请求可以包括源基站和目标基站之间没有通信接口的第二指示信息，这样以便于核心网设备反馈目标基站支持的网络切片的信息。
结合第五方面或第六方面，在一种可能的实现方式中，在第一切换响应消息为第一切换请求确认消息的情况下，第一切换响应消息还包括被目标基站拒绝切换的会话对应的重发指示信息，会话对应的重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。这样以便于终端设备获知哪些会话可以在拒绝之后仍旧可以在目标基站中重新建立，提高了会话切换的灵活性。
结合第五方面或第六方面，在一种可能的实现方式中，在第一切换响应消息为第一切换请求确认消息的情况下，第一切换请求确认消息还包括请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。使得源基站可以确认被拒绝的承载或被拒绝的数据流。
结合第五方面或第六方面，在一种可能的实现方式中，在第一切换响应消息为第一切换请求确认消息的情况下，第一切换请求确认消息还包括目标基站支持的网络切片的信息。例如在第一切换请求包括源基站不确定目标基站支持的网络切片的第一指示信息的情况下，或者核心网设备根据第一切换请求中携带的源基站与目标基站没有通信接口的第二指示信息判 断源基站不知道目标基站支持的网络切片的情况下，可以携带目标基站支持的网络切片的信息，这样减少了源基站和目标基站之间的交互，提高了网络切片的信息的获取效率。
结合第五方面或第六方面，在一种可能的实现方式中，第一切换请求还包括请求切换的会话对应的网络切片的指示信息。这样核心网设备可以直接确定请求切换的会话对应的网络切片的指示信息。可以理解的是，第一切换请求也可以不包括请求切换的会话对应的网络切片的指示信息，本发明实施例对此不做限定。
结合第五方面或第六方面，在一种可能的实现方式中，第一切换请求还包括请求切换的会话需要建立的数据流的标识和数据流对应的QoS信息。这样可以节省查找时间，降低切换时延，提高切换效率。
结合第五方面或第六方面，在一种可能的实现方式中，第一切换请求还包括会话对应的聚合最大比特速率AMBR信息。通过在第一切换请求中包括该信息可以节省了查找时间，降低了切换时延，提高了切换效率。
结合第六方面或第七方面，在一种可能的实现方式中，所述第二切换请求所包括的会话为第一会话，第一会话对应的网络切片是目标基站支持的，这一情况下，目标基站不需要针对第二会话进行接入控制，节省了针对第二会话进行接入控制的处理时间。或者，所述第二切换请求所包括的会话为所述第一会话和第二会话；所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的，这样目标基站可以直接确定自身不支持的会话，提高切换响应消息的确定效率。当然，也可以针对所有的需要进行切换的会话不做特别的归类处理。
结合第六方面或第七方面，在一种可能的实现方式中，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。这样以便于核心网设备通过源基站哪些会话可以在拒绝之后仍旧可以在目标基站中重新建立，提高了会话切换的灵活性。
结合第六方面或第七方面，在一种可能的实现方式中，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换请求确认消息还包括所述第二切换请求包括的会话的被拒绝的承载的标识或被拒绝的数据流的标识，使得核心网设备可以确认被拒绝的承载或被拒绝的数据流。
第八方面，为本发明实施例提供了一种通信方法，包括：第一基站向核心网设备发送第一消息，第一消息用于获取核心网设备针对PLMN支持的网络切片的信息；第一基站接收来自核心网设备的第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
在第八方面中，第一基站可以通过核心网设备获取到在服务PLMN的情况下核心网设备支持的网络切片的指示信息，通过以PLMN粒度反馈核心网设备支持的网络切片，能够提高第一基站为终端设备的会话选择核心网设备的准确性。
第九方面，为本发明实施例提供了一种通信方法，包括：核心网设备接收来自第一基站的第一消息，第一消息用于获取核心网设备针对PLMN支持的网络切片的信息；核心网设备向第一基站发送第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
在第九方面中，核心网设备可以向第一基站发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息，通过以PLMN粒度反馈核心网设备支持的网络切片，能够提高第一基 站为终端设备的会话选择核心网设备的准确性。
第十方面，本发明实施例提供了一种基站，该基站为源基站，该源基站包括：发送单元，用于向目标基站发送切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；接收单元，用于接收来自所述目标基站的切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，该源基站还可以实现第一方面的部分或全部的可选的实现方式。
第十一方面，本发明实施例提供了一种基站，该基站为目标基站，该目标基站包括：接收单元，接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；发送单元，用于向所述源基站发送切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，该源基站还可以实现第二方面的部分或全部的可选的实现方式。
第十二方面，本发明实施例提供了一种核心网设备，该核心网设备包括：接收单元1001，用于接收来自目标基站的路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；处理单元1002，用于对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理；发送单元1003，用于向所述目标基站发送路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
可选的，该源基站还可以实现第三方面的部分或全部的可选的实现方式。
第十三方面，本发明实施例提供了一种终端设备，该终端设备包括：接收单元，用于接收来自源基站的无线资源控制RRC连接释放消息；处理单元，用于释放RRC连接；所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括所述源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
可选的，该终端设备还可以实现第四方面的通信方法。
第十四方面，本发明实施例提供了一种基站，该基站为源基站，该源基站包括：发送单元，用于向核心网设备发送第一切换请求，所述第一切换请求用于请求将终端设备的会话从所述源基站切换到目标基站，所述第一切换请求包括所述目标基站的信息和请求切换的会话的标识；接收单元，用于接收来自所述核心网设备的第一切换响应消息，所述第一切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，该源基站还可以实现第五方面的部分或全部的可选的实现方式。
第十五方面，本发明实施例提供了一种核心网设备，该核心网设备包括：接收单元，用于接收来自源基站的第一切换请求，所述第一切换请求用于请求将终端设备的会话从所述源基站切换到目标基站，所述第一切换请求包括所述目标基站的信息和请求切换的会话的标识；发送单元，用于向所述源基站发送第一切换响应消息，所述第一切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的 会话对应的原因信息。
可选的，该核心网设备还可以实现第六方面的部分或全部的可选的实现方式。
第十六方面，本发明实施例提供了一种基站，该基站为目标基站，目标基站包括：接收单元，用于接收来自核心网设备的第二切换请求，所述第二切换请求包括会话的标识和所述会话对应的网络切片的指示信息；发送单元，用于向所述源基站发送切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，该目标基站还可以实现第七方面的部分或全部的可选的实现方式。
第十七方面，本发明实施例提供了一种基站，该基站为第一基站，包括：发送单元1101，用于向核心网设备发送第一消息，所述第一消息用于获取所述核心网设备针对PLMN支持的网络切片的信息；接收单元1102，用于接收来自所述核心网设备的第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
可选的，该源基站还可以实现第七方面的部分或全部的可选的实现方式。
第十八方面，本发明实施例提供了一种核心网设备，该核心网设备包括：接收单元，用于接收来自第一基站的第一消息，所述第一消息用于获取所述核心网设备针对PLMN支持的网络切片的信息；发送单元，用于向所述第一基站发送第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
可选的，该源基站还可以实现第九方面的部分或全部的可选的实现方式。
第十九方面，提供一种通信装置。该通信装置可以为上述方法设计中的基站，或者为设置在基站中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；收发器，以及处理器，处理器与存储器、收发器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第一方面、第二方面、第五方面、第七方面或第八方面的任意一种可能的设计中终端设备所执行的方法。
第二十方面，提供一种通信装置。该通信装置可以为上述方法设计中的核心网设备，或者为设置在核心网设备中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；收发器，以及处理器，处理器与存储器、收发器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第三方面、第六方面、第九方面的任意一种可能的设计中网络设备所执行的方法。
第二十一方面，提供一种通信装置。该通信装置可以为上述方法设计中的终端设备，或者为设置在终端设备中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；收发器，以及处理器，处理器与存储器、收发器耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第四方面的任意一种可能的设计中终端设备所执行的方法。
第二十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第九方面及其任意可能的实现方式中的方法。
第二十三方面，提供了一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第九方面及其任意可能的实现方式中的方法。
第二十四方面，提供一种芯片，包括处理器和存储器，该存储器用于存储计算机程序， 该处理器用于从存储器中调用并运行该计算机程序，该计算机程序用于实现上述第一方面至第九方面及其任意可能的实现方式中的方法。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1为本发明实施例提供了一种可能的通信系统架构示意图；
图2为本发明实施例提供了一种可能的核心网设备的示意图；
图3为本发明实施例提供了一种通信方法的流程示意图；
图4为本发明实施例提供了另一种通信方法的流程示意图；
图5为本发明实施例提供了另一种通信方法的流程示意图；
图6为本发明实施例提供了另一种通信方法的流程示意图；
图7为本发明实施例提供了另一种通信方法的流程示意图；
图8是本发明实施例提供的一种基站的结构示意图；
图9是本发明实施例提供的一种基站的结构示意图；
图10是本发明实施例提供的一种核心网设备的结构示意图；
图11是本发明实施例提供的另一种基站的结构示意图；
图12是本发明实施例提供的另一种核心网设备的结构示意图；
图13是本发明实施例提供的另一种基站的结构示意图；
图14是本发明实施例提供的另一种基站的结构示意图；
图15是本发明实施例提供的另一种核心网设备的结构示意图；
图16是本发明实施例提供的一种终端设备的结构示意图；
图17是本发明实施例提供的另一种基站的结构示意图；
图18是本发明实施例提供的另一种核心网设备的结构示意图；
图19是本发明实施例提供的另一种终端设备的结构示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
本发明实施例中所涉及的各网元的描述如下：
终端设备：可以为用户设备(user equipment，UE)，UE是通过接入网设备来实现接入网络侧的，例如可以是手持终端设备、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端或是其他可以接入网络的设备。终端设备与接入网设备之间采用某种空口技术相互通信。
接入网(radio access network，RAN)设备：主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。接入网设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在第五代(5th  generation，5G)系统中，称为gNB；在LTE系统中，称为演进的节点B(evolved nodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(node B)等。
核心网设备用于提供用户连接、对用户的管理以及对业务完成承载。例如，用户连接的建立包括移动性管理(mobile management，MM)、寻呼(paging)等功能。用户管理包括用户的描述、Qos、安全性(由鉴权中心提供相应的安全性措施包含了对移动业务的安全性管理和对外部网络访问的安全性处理)。承载连接包括到外部的公共交换电话网络(public switched telephone network，PSTN)、外部电路数据网和分组数据网、因特网(Internet)等等。
例如，核心网设备可以包括接入和移动性管理功能(access and mobility management function，AMF)网元，主要负责信令处理部分，即控制面功能，包括接入控制、移动性管理、附着与去附着等功能。
可选的，核心网设备还可以包括会话管理功能(session management function，SMF)网元：负责会话管理功能，例如会话的建立、修改和释放等。
可选的，核心网设备还可以包括用户面功能(user plane function，UPF)网元：负责终端设备中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端设备；UPF网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。本发明实施例所涉及的核心网设备不限于AMF网元、SMF网元、UPF网元。
参见图1，是本发明实施例使用的一种可能的通信系统架构示意图。如图1所示，可以看出，接入网设备可以与至少一个终端设备相连接，例如，接入网设备101分别与终端设备104和终端设备105相连接，接入网设备102分别与终端设备106和终端设备106相连接。接入网设备可以与至少一个核心网设备103相连接，例如，接入网设备101和接入网设备102分别与核心网设备103相连接。
其中，核心网设备与接入网设备之间存在控制面接口，例如核心网设备与接入网之间存在接口，在本申请中称之为N2接口或NG接口。
例如，若图1中的接入网设备101和接入网设备102之间有通信接口，例如，Xn接口，则两者可以相互通信；若图1中的接入网设备101和接入网设备102之间没有通信接口，则两者不可以相互通信。因此，接入网设备101和接入网设备102仅能在有通信接口的情况下传输各自所支持的网络切片的信息，在没有通信接口的情况下，无法通信，进而无法发送各自所支持的网络切片的信息。
核心网设备103可以包括至少一个AMF网元，可选的还可以包括SMF和UPF网元。其中，接入网设备102可以与一个或多个AMF网元相连接。一个AMF网元可以支持一个或者多个不同类型的网络切片，不同的AMF网元支持的网络切片的类型可以不同。每个SMF可以支持一个或者多个不同类型的网络切片，不同的SMF网元支持的网络切片的类型可以不同，一个AMF网元可以与多个SMF网元建立通信连接。可选的，一个SMF网元可以与多个AMF网元相连接。另外，一个SMF网元可以与多个UPF网元相连接，一个UPF网元可以与一个SMF网元相连接，在这一情况下，一个SMF网元可以管理控制多个UPF网元，一个UPF网元被一个SMF管理控制。UPF网元可以与接入网设备建立连接，以实现关于终端设备的数据传输。
举例来说，请参见图2，为本发明实施例提供了一种可能的核心网设备的示意图。一个AMF网元201与两个SMF网元建立了连接，两个SMF网元分别为SMF网元202和SMF网元203。 AMF网元201支持的网络切片类型包括网络切片类型1和网络切片类型2，网络切片类型1为网络切片1的类型，网络切片类型2为网络切片2的类型。SMF网元202为与网络切片1对应的SMF网元，SMF网元203为与网络切片2对应的SMF网元。一个SMF网元可以管理控制多个UPF网元，例如，SMF网元202管理UPF网元204、UPF网元205、UPF网元206；SMF网元203管理UPF网元204和UPF网元208。
由于终端设备中存在多种类型的业务，例如增强的移动宽带业务(enhanced mobile broadband,eMBB)，超可靠低时延通信(ultra-reliable low l atency communications,URLLC)，海量机器类通信(massive machine type communication,mMTC)等，而不同类型的业务会话对应的网络切片可能会存在不同，即使相同的业务类型，由于提供的运营商或者业务提供商不同，也可能对应不同的网络切片。不同接入网设备可以支持不同的网络切片。这样在终端设备需要接入网络并建立多个会话的情况下，所连接的接入网设备需要支持终端设备中的全部会话或者部分会话对应的网络切片。
在由于终端设备的位置移动或者负载均衡等原因而需要为终端设备切换接入网设备的情况下，例如，结合图1，需要将终端设备104的会话从一个接入网设备101切换到另一个接入网设备102，但切换成功与否与接入网设备102是否支持终端设备104的会话对应的网络切片息息相关。实际中，接入网设备101会向接入网设备102发送切换请求，往往存在部分会话无法切换至接入网设备102。然而，会话无法切换至接入网设备102有多种原因，例如，接入网设备102中的无线资源受限(radio resource not available)、不支持所请求的网络切片等。但是现有的方案中，接入网设备101无法确定该会话无法切换至接入网设备102的原因，若接入网设备102中该请求的会话对应的第一网络切片资源受限，对于其他会话需要请求切换至第一网络切片的时候，接入网设备101依旧会向接入网设备102发送切换请求，依旧会存在该会话无法切换至接入网设备102的情况发生，降低了切换成功的概率。
而在本发明实施例中，接入网设备101在向接入网设备102发送切换请求之后，接入网设备101能够获知被拒绝切换的会话由接入网设备102的网络切片而拒绝的原因信息，这样为其他需要请求切换到该接入网设备102的会话提供了信息帮助，在接入网设备101需要切换相同网络切片的会话时，可以直接确定是否能够切换到接入网设备102中，提高了切换成功的概率，也可以为其他待切换的终端设备选择更好的目标基站进行切换。
需要指出的是，本申请的实施例接入网设备以基站为例进行说明，本申请中任一实施例中所涉及的基站支持的网络切片的信息，在一种可选的方式中可以包括该基站包含的至少一个小区标识和每个小区标识对应的至少一个网络切片的指示信息。其中，一个基站可以包含一个或者多个小区，每个小区通过小区标识来表示，每个小区可以支持一个或者多个网络切片，每个小区支持的网络切片不同，这样一个小区标识可以对应至少一个网络切片的指示信息。例如，具体表现形式如下(名称只是示意，本申请实施例对名称不做限定)，其中，Cell ID表示小区标识，S-NSSAI list表示一个网络切片的指示信息，一个Cell ID可以与至少一个S-NSSAI list相对应。
>>>Cell ID
>>>S-NSSAI list
或者，在另一种可选的方式中基站支持的网络切片的信息可以包括该基站的信息和基站对应的至少一个网络切片的指示信息。其中，每个基站可以支持一个或者多个网络切片，这样一个基站的信息可以对应至少一个网络切片的指示信息。例如，具体表现形式如下(名称只 是示意，本申请实施例对名称不做限定)，其中，gNB ID表示基站的信息，S-NSSAI list表示一个网络切片的指示信息，一个gNB ID可以与至少一个S-NSSAI list相对应。
>>>gNB ID
>>>S-NSSAI list
或者，在另一种可选的方式中基站支持的网络切片的信息可以包括该基站包含的小区所属的跟踪区(tracking area，TA)或注册区域(registration area，RA)对应的至少一个网络切片的指示信息。其中，每个TA/RA可以支持一个或者多个网络切片，这样一个TA/RA的信息可以对应至少一个网络切片的指示信息。例如，具体表现形式如下(名称只是示意，本申请实施例对名称不做限定)，其中，跟踪区识别码(tracking area identity/identifier，TAI)、注册区域识别码(registration area identity/identifier，RAI)、跟踪区编码(tracking area Code，TAC)或注册区域编码(registration area identity/identifier，RAC)用于表示TA/RA的信息，S-NSSAI list表示一个网络切片的指示信息，一个TAI/RAI/TAC/RAC可以与至少一个S-NSSAI list相对应。
>>>TAI/RAI/TAC/RAC
>>>S-NSSAI list
本申请中任一实施例所涉及的基站的信息可以包括基站的基站标识、基站包含的中心单元的标识(central unit ID)、基站包含的分布式单元的标识(distributed unit ID)、基站包含的物理小区标识(Physical Cell Identifier，PCI)和基站包含的小区全球标识(Cell Global ID，CGI)中的至少一个。
又一需要指出的是，在本申请的任一实施例中所涉及到的每个网络切片的指示信息可以包括网络切片标识、单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)和接入网网络切片选择辅助信息(RAN network slice selection assistance information，R-NSSAI)中的至少一个。
其中，网络切片标识可以通过以下(1)至(7)中的至少一项来表示。
(1)网络切片类型信息，例如，网络切片类型信息可以指示增强的移动宽带业务(enhanced mobile broadband，eMBB)，超可靠低时延通信(Ultra-Reliable Low Latency Communications，URLLC)，海量机器类通信(massive Machine Type Communication，mMTC)等网络切片类型，可选的，该网络切片类型信息还可以指示端到端的网络切片类型，包含RAN到核心网(Core Network，CN)的网络切片类型，也可以指RAN侧网络切片类型，或者CN侧网络切片类型。
(2)业务类型信息，与具体的业务相关，例如，该业务类型信息可以指示视频业务，车联网业务，语音业务等业务特征或者具体业务的信息。
(3)租户(Tenant)信息，用于指示创建或者租用该网络切片的客户信息，如腾讯，国家电网等。
(4)用户组信息，用于指示按照某种特征，如用户的级别等将用户进行分组的分组信息。
(5)切片组信息，用于指示按照某种特征，例如，可以将终端设备能够接入的所有网络切片作为一个切片组，或者也可以按照其他标准划分网络切片的分组。
(6)网络切片实例信息，用于指示为该网络切片创建的实例标识以及特征信息，例如，可以为网络切片实例分配一个标识，用于指示该网络切片实例，也可以在网络切片实例标识的基础上映射一个新的标识，关联该网络切片实例，接收方可以根据该标识识别出该标识指 示的具体网络切片实例。
(7)专有核心网(Dedicated Core Network，DCN)标识，该标识用于唯一指示长期演进(Long Term Evolution，LTE)系统或者增强LTE(enhanced LTE，eLTE)系统中的专有核心网，例如物联网专有的核心网，可选的，该DCN标识可以与网络切片标识做映射，由DCN标识可以映射出网络切片标识，通过网络切片标识也可以映射出DCN标识。
其中，S-NSSAI至少包含切片类型/服务类型(Slice/Service type，SST)信息，可选的还可以包含切片区分信息(Slice Differentiator，SD)。SST信息用于指示网络切片的行为，例如网络切片的特征以及服务类型，SD信息是SST的补足信息，若SST指向多个网络切片实施，那么SD可以对应到唯一的一个网络切片实例。
其中，R-NSSAI表示一组特定的S-NSSAI，即一组特定的S-NSSAI的集合的标识。
应理解，在本申请实施例中，网络切片都可以采用上述参数中的至少一种表征该网络切片的指示信息，例如，网络切片的指示信息可以用网络切片类型表征，或者也可以用网络切片类型和业务类型表征，或者也可以用业务类型加租户信息表征等，本申请实施例对此不作限定，以下对于网络切片的指示信息如何表征不再赘述。可选的，网络切片的指示信息的具体编码形式不限，可以承载在不同设备之间的接口消息的不同字段分别代表不同的网络切片的指示信息，或者可以通过抽象后的索引值代替，不同的索引值分别对应不同的网络切片。当然，除了上述的标识外，还可以是其他的标识，在此不作限定。应理解，若终端设备、接入网设备或者核心网设备支持多个网络切片，则终端设备、接入网设备或者核心网设备支持的网络切片的指示信息可以以上述至少一个标识的列表形式体现。
需要说明的是，在本发明实施例中涉及的“有通信接口”或“有接口”表示建立了通信接口并且该通信接口可用(available)；涉及的“没有通信接口”或“没有接口”表示未建立通信接口或建立的通信接口不可用(unavailable)。这里的通信接口不限于接入网设备和接入网设备之间的通信接口、接入网设备和核心网设备之间的通信接口。
本发明实施例可应用于其它支持网络切片的通信系统中。术语“系统”可以和“网络”相互替换。本发明实施例描述的系统架构是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
请参见图3，为本发明实施例提供了一种通信方法。在该实施例中，接入网设备以基站为例进行说明，如图3所示，该通信方法涉及到终端设备、源基站、目标基站以及核心网设备。图3对应于目标基站确定切换成功的情况下的通信方法，源基站是当前与终端设备建立通信连接的基站，目标基站是请求将终端设备的会话切换到的基站。
如图3所示，该通信方法包括步骤301至步骤307，请参见以下具体介绍。
301，源基站向目标基站发送切换请求。
其中，源基站和目标基站之间存在通信接口，例如Xn接口。这样源基站和目标基站可以相互通信。该切换请求用于请求将终端设备的会话从源基站切换至目标基站，该切换请求包括请求切换的会话的标识和该会话对应的网络切片的指示信息。例如，若请求切换的会话为多个，则切换请求中携带每个会话对应的网络切片的指示信息。相应的，目标基站接收该切换请求。
可选的，请求切换的会话可以为终端设备的处于激活状态的会话，可以理解为终端设备 中当前正在进行的会话。例如，终端设备的会话包括会话A1、会话A2、会话A3、会话A4和会话A5，其中，会话A1、会话A2和会话A3处于激活状态；会话A4和会话A5处于去激活状态。这一情况下，请求切换的会话包括会话A1、会话A2和会话A3的标识，以及会话A1、会话A2和会话A3分别对应的网络切片的指示信息。对于去激活状态的会话，无需切换至目标基站，能够减少信令传输。
可选的，源基站在发送切换请求前，还可以根据获知的目标基站支持的网络切片的信息与请求切换的会话对应的网络切片的指示信息判断：请求切换的会话中哪些会话对应的网络切片目标基站是支持的，哪些会话对应的网络切片目标基站是不支持的。更进一步，若所有请求切换的会话对应的网络切片目标基站都是不支持的，则源基站可以不向该目标基站发送切换请求信息。
可选的，请求切换的会话可以为终端设备的第一会话和第二会话，其中，第一会话对应的网络切片是目标基站支持的，第二会话对应的网络切片是目标基站不支持的。由于源基站和目标基站之间是有通信接口的，因此源基站可以通过与目标基站交互、通过与其他基站交互或通过与核心网侧交互等方式来确定目标基站支持的网络切片，进而源基站可以根据请求切换的各个会话对应的网络切片的指示信息和目标基站支持的网络切片，对请求切换的会话进行分类，得到第一会话和第二会话。例如，请求切换的会话包括会话B1、会话B2和会话B3，目标基站支持会话B1和会话B2所对应的网络切片，目标基站不支持会话B3对应的网络切片，这一情况下，请求切换的会话的标识分为两类发送至目标基站，一类为第一会话的标识，另一类为第二会话的标识，这样目标基站可以直接确定自身不支持的会话，提高切换响应消息的确定效率。当然，也可以针对所有的需要进行切换的会话不做特别的归类处理。
可选的，请求切换的会话可以为终端设备的第一会话，其中，第一会话对应的网络切片是目标基站支持的。这样无需目标基站针对不支持的网络切片所对应的那部分会话判断是否支持请求切换会话对应的网络切片，可以直接根据目标基站中网络切片的资源使用情况，确定是否切换该第一会话。这一情况下，目标基站不需要针对第二会话进行接入控制，节省了针对第二会话进行接入控制的处理时间。
可选的，源基站从多个与源基站有通信接口的基站中，选择一个基站确定为目标基站。进一步的，所确定的目标基站支持请求切换的全部或者部分会话对应的网络切片，这样能够避免由于目标基站不支持全部请求切换的会话的网络切片而导致的切换失败，进而减少了切换失败的次数，以提高切换成功概率。
可选的，源基站可以在接收到终端设备发送的测量报告的情况下，源基站根据测量报告来选择目标基站，并执行步骤301，向目标基站发送切换请求。该测量报告包含小区和基站中至少一个的测量报告值。可选的，若测量报告中包含小区的测量报告值，则所包含的小区可以是源基站包含的小区，也可以是其他基站包含的小区。若测量报告中包含基站的测量报告值，则所包含的基站可以是源基站，也可以是其他基站。可选的，本发明实施例对测量报告中包含的小区的数量和基站的数量不做限定。
302，目标基站根据网络切片的支持情况和资源使用情况以及切换请求等因素进行接入控制。
其中，在目标基站接收到源基站发送的切换请求的情况下，目标基站执行接入控制(admission control)。可选的，目标基站根据切换请求中各个会话对应的网络切片的指示信息、自身网络切片的支持情况和资源使用情况等因素，以确定切换响应消息。
举例来说，对于会话B4，若目标基站支持的网络切片的信息包含会话B4对应的网络切片的指示信息，则表示目标基站支持该会话B4对应的网络切片。若目标基站支持的网络切片的信息不包含会话B4对应的网络切片的指示信息，则表示目标基站不支持该会话B4对应的网络切片，则这一情况下会话B4为拒绝切换的会话。进一步的，对于目标基站支持会话B4对应的网络切片，若目标基站还可以为该会话B4分配相对应的网络切片的资源，则目标基站确定该会话B4为确认切换的会话。若目标基站不可以为该会话B4分配相对应的网络切片的资源，则目标基站确定该会话B4为拒绝换的会话。这样目标基站通过接入控制即可确定切换响应消息。
可选的，即使在步骤301中只携带第一会话，目标基站也可以针对第一会话(一个会话或者多个会话)对应的网络切片的指示信息进行检查，以确定当前是否支持第一会话对应的网络切片。
进一步的，该切换响应消息可以为切换请求确认消息；或者切换响应消息为切换失败消息。在图3所示实施例中介绍切换响应消息为切换请求确认消息的情况，这一情况下，请求切换的会话中存在可以切换至目标基站的；且还存在被目标基站拒绝切换的会话。其中，被目标基站拒绝切换的会话可能是由于目标基站不支持该被拒绝会话对应的网络切片导致的，也可能是由于目标基站中被拒绝会话对应的网络切片的资源受限导致的。因此，该切换请求确认消息包括拒绝指示信息，该拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。原因信息包括：目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。
可选的，本发明实施例中的原因信息可以是以信元(information element，IE)、标志(flag)、原因值(cause)等来指示，本发明实施例对此不做限定。
举例来说，若请求切换的会话包括第一会话和第二会话，则被拒绝切换的会话的原因信息可以是目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。若请求切换的会话包括第一会话，则被拒绝切换的会话的原因信息为目标基站的拒绝切换的会话对应的网络切片资源受限。若第一会话包含多个数据流，例如数据流为traffic flow或QoS流(QoS flow)，且第一会话部分数据流被目标基站接收(admitted)，部分数据流被目标基站拒绝，则也可以针对第一会话携带指示信息，指示第一会话部分被拒绝的数据流的原因，例如资源受限或者第一会话对应的网络切片在目标基站资源受限。
303，目标基站向源基站发送切换请求确认消息。
其中，切换请求确认消息包括确认切换的会话的标识、拒绝切换的会话的标识和拒绝切换的会话对应的原因信息。例如，该切换请求确认消息可以是handover acknowledgement，或者handover request acknowledgement。
举例来说，请参见表1，为PDU会话释放列表或PDU会话拒绝列表，切换请求确认消息包括的拒绝切换的会话的标识和拒绝切换的会话对应的原因信息可以以表1的形式来表示。
表1
Figure PCTCN2018099875-appb-000001
Figure PCTCN2018099875-appb-000002
可选的，切换请求确认消息还包括拒绝切换的会话对应的重发指示信息。该重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。举例来说，以拒绝的会话为会话B1、会话B1对应网络切片1为例来说明，会话B1被拒绝切换的原因信息可以为目标基站不支持会话B1对应的网络切片1，也可为目标基站指示网络切片1但网络切片1资源受限，不论是什么原因导致会话B1被拒绝切换，若目标基站支持网络切片2，且会话B1包含的数据流在路由至网络切片2的情况下也可以实现数据传输，则目标基站确定会话B1对应的重发指示信息为：允许终端设备将会话B1包含的数据流路由到目标基站支持的网络切片2。可以理解，重发指示信息可以不指明具体路由到的具体的网络切片。另外，若目标基站中不存在会话B1包含的数据流可以路由至的网络切片，或者目标基站不能满足会话B1包含的数据流的QoS需求，则目标基站确定会话B1对应的重发指示信息为：不允许终端设备将会话B1包含的数据流路由到目标基站支持的网络切片。可以理解，重发指示信息和原因信息可以采用一个IE/Flag/Cause value进行标识，即该IE/Flag/Cause value指示了会话拒绝的原因并且同时指示该被拒绝的会话对应的数据流可以路由到其他的网络切片，即可以在其他目标基站支持的网络切片上重新建立会话用于传输该数据流。重发指示信息和原因信息也可以采用两个不同的IE/Flag/Cause value分别进行标识。
可选的，切换请求确认消息还包括请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。其中，一个会话包含多个数据流，一个承载可以对应多个数据流，被拒绝的承载可以是确认切换的会话所包含的承载，也可以是被拒绝切换的会话所包含的承载；被拒绝的数据流可以是确认切换的会话所包含的数据流，也可以是被拒绝切换的会话所包含的数据流。例如，确认切换的会话所包含的部分承载为被拒绝的承载，确认切换的会话所包含的部分数据流为被拒绝的数据流，通过切换请求确定消息发送给源基站，使得源基站可以确认被拒绝的承载或被拒绝的数据流。
举例来说，在切换请求确认消息还包括被拒绝的数据流的标识的情况下，请参见表2，表2中包含了确认切换的会话的标识、被拒绝切换的数据流的原因信息以及被拒绝的数据流的标识。其中，确认切换的会话列表可以表示为PDU会话允许列表(PDU Session Admitted List)，也可以表示为PDU会话转移的列表(PDU Sessions Subject to Forwarding List)
表2
确认切换的会话列表
>PDU会话标识(PDU Session ID)
>原因值(Cause)
>被拒绝切换的数据流标识/标识列表(traffic/QoS flow ID(list))
举例来说，切换请求确认消息可以通过列表的形式来反馈以上所包含的信息，对于源基站请求切换的会话包括第一会话和第二会话，且确定切换响应消息为切换请求确认消息，以第一会话包括会话C1、会话C2和会话C3，第二会话包括会话D1和会话D2为例来说明。在目标基站确认切换的会话为会话C1和会话C2；目标基站拒绝切换的会话包括会话C3、会话D1和会话D2，目标基站支持会话C3对应的网络切片，但由于该网络切片资源受限导致切换失败，确认切换的会话C1中的部分承载或部分数据流被拒绝。
这一情况下，请参见表3，为本发明实施例提供了确认切换的会话的列表形式，其中，对于存在被拒绝的承载/数据流的会话C1还可以在切换请求确认消息中对应原因信息，该原因信息用于指示被拒绝的部分承载或被拒绝部分数据流的原因信息。例如，被拒绝的部分承载或被拒绝部分数据流的原因信息R3可以是资源受限、该会话包含的数据流对应QoS组合无效(Invalid QoS combination)、数据流标识重复等。对于存在被拒绝的承载/数据流的会话C1还可以在切换请求确认消息中对应重发指示信息，重发指示信息所表示的含义与前述内容相同，重发指示信息为Y表示允许终端设备将会话C1包含的被拒绝的数据流路由到目标基站支持的网络切片。从而可以为下次的切换提供更准确的信息，提高切换的成功率。其中，被拒绝的承载/数据流标识、重发指示信息、原因信息为切换请求确认消息中可选择携带的。其中，确认的会话列表可以表示为PDU会话允许列表(PDU Session Admitted List)，也可以表示为PDU会话转移的列表(PDU Sessions Subject to Forwarding List)。
表3
Figure PCTCN2018099875-appb-000003
进一步，请参见表4，为本发明实施例提供了拒绝切换的会话的列表形式，其中，被拒绝的承载/数据流标识、重发指示信息为切换请求确认消息中可选择携带的。其中，会话C3的原因信息为R1，表示目标基站支持会话C3对应的网络切片但该网络切片的资源受限；会话D1和会话D2的原因信息为R2，表示目标基站不支持会话D1对应的网络切片和不支持会话D2对应的网络切片。重发指示信息中的Y，表示允许终端设备将会话C3包含的数据流路由到目标基站支持的网络切片；重发指示信息中的N，表示不允许终端设备将会话D1、会话D2包含的数据流路由到目标基站支持的网络切片。其中，拒绝切换的会话的列表可以表示为PDU会话释放列表(PDU Sessions to Release List)，也可以表示为PDU会话拒绝列表(PDU sessions Not Admitted List)。
表4
Figure PCTCN2018099875-appb-000004
另外可以看出，表4是按照各个会话标识来生成列表的，在另一种可选的方式中，可以按照原因信息来生成列表，如表5所示，为本发明实施例提供了另一种拒绝切换的会话的列表形式。这样一个原因信息对应多个会话标识，能够节省信令的传输。其中，被拒绝的承载/ 数据流标识、重发指示信息为切换请求确认消息中可选择携带的。其中，拒绝切换的会话的列表可以表示为PDU会话释放列表(PDU Sessions to Release List)，也可以表示为PDU会话拒绝列表(PDU sessions Not Admitted List)。
表5
Figure PCTCN2018099875-appb-000005
可选的，切换请求确认消息还携带目标基站确定的承载配置信息，该承载配置信息用于指示终端设备按照该配置信息进行承载配置。
进一步可选的，切换请求确认消息还包括满配置切换指示信息，该满配置切换指示信息用于指示终端设备无需对原有承载进行逐个对应修改，可以采用目标基站确定的承载配置信息执行满配置切换，即通过删除全部原有承载配置并存储目标基站确定的承载配置信息，以提高承载的配置效率。可选的，在切换请求包括满配置切换指示信息的情况下，切换请求确认消息还包括满配置切换指示信息。
可选的，切换请求确认消息还包括携带目标基站支持的网络切片的信息。这样便于目标基站通知源基站目标基站当前支持的网络切片的信息，减少了源基站和目标基站之间的交互。
相应的，源基站接收目标基站发送的切换请求确认消息。
304，源基站向终端设备发送切换命令。
在源基站接收到目标基站发送的切换请求确认消息之后，源基站向终端设备发送切换命令。例如，该切换命令可以是RRC连接重配置消息(RRC Connection Reconfiguration)，也可以是切换命令消息(handover Command)。该切换命令包括确认切换的会话的标识、确认切换的会话包含的数据流的标识和确认切换的会话对应的承载的标识中的至少一个，以通知终端设备能够切换至目标基站的会话、数据流或承载。
可选的，该切换命令还包括被目标基站拒绝切换的会话和拒绝切换的会话对应的重发指示信息，以使终端设备根据拒绝切换会话对应的重发指示信息来确定是否向目标基站发起拒绝切换会话的会话建立请求。可选的，对于有多个被拒切换的会话，切换命令可以包括每个会话对应的重发指示信息，或者，切换命令可以允许重发和不允许重发的分两类来指示，本发明实施例对此不做限定。
可选的，在切换请求确认消息包括目标基站确定的承载配置信息的情况下，该切换命令还包括目标基站确定的承载配置信息，以指示终端设备按照该配置信息进行承载配置。在切换请求确认消息还包括满配置切换指示信息的情况下，切换命令还包括满配置切换指示信息，以提高承载的配置效率。
相应的，终端设备接收源基站发送的切换命令。
305，终端设备向目标基站发送切换确认消息。
例如，该切换确认消息可以是切换命令完成消息(handover Complete)，也可以是RRC 连接重配置完成消息(RRC Connection Reconfiguration Complete)。
可选的，在终端设备接收到切换命令之后，终端设备与目标基站之间进行随机接入，以向目标基站反馈切换确认消息，用于表示终端设备已完成切换。
306，目标基站向核心网设备发送路径转移请求。
其中，在目标基站接收到切换确认消息的情况下，向核心网设备发送路径转移请求。例如，路径转移请求为Path switch request。该路径转移请求包括目标基站确认切换的会话的标识，以使核心网设备对确认切换的会话进行路径转移处理。
可选的，路径转移请求还可以包括目标基站拒绝切换的会话的标识，以使核心网设备为拒绝切换的会话进行删除或去激活处理。
进一步的，终端设备中存在处于激活状态的业务和处于去激活状态的业务，而核心网设备中存储有终端设备的全部会话。由于确认切换的会话和拒绝切换的会话均属于处于激活状态的业务，这样通过在路径转移请求中携带这两类会话的标识，核心网设备能够从所存储的终端设备的全部会话中确定出已处于去激活状态的会话，这样核心网设备将无需对这一类会话进行处理，只需要对确认切换的会话和拒绝切换的会话进行处理，提高了处理效率。
可选的，路径转移请求还包括被目标基站拒绝切换的会话对应的网络切片的指示信息，这样核心网设备就可以根据被拒绝的会话对应的网络切片与自己保存的目标小区支持的网络切片进行对比，从而可以获知被拒绝的会话是否是由于目标基站网络切片不支持的原因造成的，如果是，则核心网设备后续会触发删除(remove)会话的过程，这样可以减少这类会话在核心网设备中所占用的存储空间。如果否，那么核心网设备后续可以触发去激活(deactivate)该会话的流程，这样可以在需要激活的情况下核心网设备可以快速恢复该会话。
可选的，路径转移请求包括被目标基站拒绝切换的会话对应的原因信息。通过携带原因信息，核心网设备可以针对因不同原因导致被拒绝会话执行不同的处理。
相应的，核心网设备接收目标基站发送的路径转移请求。
307，核心网设备对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理。
其中，核心网设备对确认切换的会话执行路径转移处理具体是：
核心网设备对拒绝切换的会话执行去激活处理具体是将拒绝切换的会话进行挂起，该会话对应的上下文还可以保存在核心网设备中，这样在需要激活该会话的情况下核心网设备可以快速恢复该会话。
核心网设备对拒绝切换的会话执行删除处理，具体是核心网设备删除该会话对应的上下文，例如AMF网元通知SMF网元删除该会话对应的上下文，这样可以减少这类会话在核心网设备中所占用的存储空间。
可选的，核心网设备可以对因目标基站的网络切片资源受限而被拒绝的会话执行去激活处理，这样在目标基站中该网络切片不受限的情况下，还可以恢复对该会话的数据传输。相比于对该会话执行删除处理，在目标基站中该网络切片不受限的情况下通过重新建立该会话的方式，激活处理所需时间更短，因此能加快恢复去激活会话的数据传输。
可选的，核心网设备可以对因目标基站不支持网络切片而被拒绝的会话执行删除处理，由于目标基站所支持的网络切片在短时间内不会变化，因此该会话无法在短时间内恢复数据传输，这样若对该会话执行去激活处理，则会占用核心网设备较多存储空间，造成存储空间 的浪费。
308，核心网设备向目标基站发送路径转移请求响应消息。
其中，核心网设备向目标基站发送路径转移请求响应消息，该路径转移请求响应消息包括成功转移路径的会话的标识。例如，路径转移请求响应消息Path switch request ack或者Path switch request response。
可选的，该路径转移请求响应消息还包括为转移路径失败的会话的标识，以使目标基站确定核心网设备的路径转移结果。
在本发明实施例中，源基站在向目标基站发送切换请求之后，源基站能够获知被拒绝切换的会话由目标基站的网络切片而拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
请参见图4，为本发明实施例提供了一种通信方法。在该实施例中，接入网设备以基站为例进行说明，如图4所示，该通信方法涉及到终端设备、源基站以及目标基站。图4对应于目标基站确定切换失败的情况下的通信方法，源基站是当前与终端设备建立通信连接的基站，目标基站是请求将终端设备的会话切换到的基站。
如图4所示，该通信方法包括步骤401至步骤404，请参见以下具体介绍。
401，源基站向目标基站发送切换请求。
其中，步骤401可以参考图3所示实施例中对应步骤301的详细描述，在此不再赘述。
402，目标基站根据网络切片的支持情况和资源使用情况以及切换请求等因素进行接入控制。
其中，在目标基站接收到源基站发送的切换请求的情况下，目标基站执行接入控制(admission control)。可选的，目标基站根据切换请求中各个会话对应的网络切片的指示信息、自身网络切片的支持情况和资源使用情况等因素，以确定切换响应消息。
进一步的，该切换响应消息可以为切换请求确认消息；或者切换响应消息为切换失败消息。在图4所示实施例中介绍切换响应消息为切换失败消息的情况，这一情况下，请求切换的会话中不存在可以切换至目标基站的，即所请求切换的会话均为被目标基站拒绝的会话。其中，被目标基站拒绝切换的会话可能是由于目标基站不支持该被拒绝会话对应的网络切片导致的，也可能是由于目标基站中被拒绝会话对应的网络切片的资源受限导致的。因此，该切换请求确认消息包括拒绝指示信息，该拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。原因信息包括：目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。
可选的，本发明实施例中的原因信息可以是以IE、flag、cause等来指示，本发明实施例对此不做限定。
举例来说，若请求切换的会话包括第一会话和第二会话，则被拒绝切换的会话的原因信息可以是目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。若请求切换的会话包括第一会话，则被拒绝切换的会话的原因信息为标基站的拒绝切换的会话对应的网络切片资源受限。
403，目标基站向源基站发送切换失败消息。
其中，切换失败消息包括拒绝切换的会话对应的原因信息。例如切换失败消息为切换准 备失败(handover preparation failure)消息。
可选的，切换失败消息还包括请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。其中，一个会话包含多个数据流，一个承载对应至少一个数据流，被拒绝的承载可以是被拒绝切换的会话所包含的承载；被拒绝的数据流可以被拒绝切换的会话所包含的数据流。例如，被拒绝切换的会话所包含的全部承载均为被拒绝的承载，被拒绝切换的会话所包含的全部数据流均为被拒绝的数据流，通过切换失败消息发送给源基站，使得源基站可以确认被拒绝的承载或被拒绝的数据流。
进一步的，在本发明实施例中，切换失败消息中也可以以拒绝切换的会话的列表来表示，该列表可以参考表4和表5中除去重发指示信息的全部内容，其中被拒绝的承载/数据流的标识是切换失败消息的可选内容，本发明实施例对此不做限定。
可选的，在切换响应消息为切换失败消息的情况下，拒绝指示信息可以用于表示所述目标基站不支持所述终端设备当前进行的任一会话对应的网络切片。例如，在请求切换的会话包括第一会话和第二会话的情况下，若源基站不确定目标基站最新更新的所支持的网络切片的情况下，可能出现所请求的会话目标基站均不支持的情况。这一情况下，一种可选的方案中，切换失败消息包括该拒绝指示信息如以IE、flag、cause等来指示)和拒绝切换的会话的标识，举例来说，这一情况下，可以参见表6，该PDU会话释放列表包含了拒绝切换的指示值；另一种可选的方案中，切换失败消息包括该拒绝指示信息(如以IE、flag、cause等来指示)，在这种情况下，不需要携带表6中的PDU会话释放列表，而只携带切换失败指示值。以使源基站确定目标基站所不支持的网络切片。
表6
Figure PCTCN2018099875-appb-000006
或者，拒绝指示信息可以用于表示所述目标基站支持所述切换请求包括的任一会话对应的网络切片，且拒绝切换所述切换请求中包括的全部会话。例如，在请求切换的会话包括第一会话，且目标基站对请求切换的每个会话对应的网络切片均资源受限的情况下，一种可选的方案中，切换失败消息包括该拒绝指示信息(如以IE、flag、cause等来指示)；另一种可选的方案中，切换失败消息包括该拒绝指示信息如以IE、flag、cause等来指示)和拒绝切换的会话的标识，以使源基站确定目标基站中请求切换会话对应的网络切片的资源使用情况。
或者，拒绝指示信息可以用于表示所述目标基站支持第三会话对应的网络切片且拒绝切换第三会话，且所述目标基站不支持第四会话对应的网络切片，所述请求切换的会话包括所述第三会话和第四会话。例如，在源基站不确定目标基站最新更新的所支持的网络切片的前提下，对于源基站请求切换的会话包括第一会话和第二会话的情况，或者，对于源基站请求切换的会话包括第一会话的情况，目标基站根据自身网络切片的支持情况和资源使用情况，可能对请求切换的会话重新分类，即源基站确定目标基站支持的第一会话，则可能变更为目标基站不支持的会话，源基站确定目标基站不支持的第二会话，则可能变更为目标基站支持的会话。因此在目标基站反馈的拒绝指示信息中的第三会话可能于切换请求中的第一会话相同，也可能不相同；以及在目标基站反馈的拒绝指示信息中的第四会话可能于切换请求中的第二会话相同，也可能不相同。进一步的，在这一情况下，目标基站可以对对应于相同拒绝切换的原因的会话分为一类来对应一个拒绝指示信息(如以IE、flag、cause等来指示)，即 切换失败消息包括两个拒绝指示信息和分别对应于这两个拒绝指示信息的会话的标识；或者，目标基站可以对每个拒绝切换会话分别对应一个拒绝指示信息(如以IE、flag、cause等来指示)，即切换失败消息包括至少一个拒绝切换的会话的标识和每个拒绝切换的会话对应的拒绝指示信息；或者，切换失败消息包括两个拒绝指示信息，本发明实施例对此不做限定。可选的，对于由于目标基站的网络切片资源受限而拒绝切换的会话，可以在切换失败消息中可以通过包括拒绝切换的会话的标识和拒绝切换的会话对应的网络切片的指示信息这两项内容，来指示源基站目标基站中该类网络切片的资源受限，而无需采用额外的指示信息，这样源基站可以确定目标基站该类往了切片的资源使用情况。
或者，拒绝指示信息可以用于表示所述目标基站拒绝切换会话。例如，在源基站请求切换的会话包括第一会话和第二会话的情况下，由于目标基站支持的每个网络切片的资源均受限。这一情况下，切换失败消息包括一个拒绝指示信息，以表示目标基站不仅拒绝所请求切换的会话，对于所支持的其他网络切片对应的会话也拒绝切换，这样源基站也能够及时获知目标基站中全部网络切片的资源使用情况，为源基站中其他会话的切换提供了信息帮助，提高了切换成功率。
可选的，切换失败消息还包括携带目标基站支持的网络切片的信息。这样便于目标基站通知源基站目标基站当前支持的网络切片的信息，减少了源基站和目标基站之间的交互。
404，源基站向终端设备发送RRC连接释放消息。
其中，在源基站确定切换失败的情况下，向终端设备发送RRC连接释放消息，以使终端设备尽早的释放RRC连接，避免后续的无线链路失败过程，减少了信令开销。
可选的，所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。其中，源小区(sourcecell)是源基站向目标基站请求切换时为终端设备服务的小区。以使源基站获得更多其他小区或者其他基站所支持的网络切片，为后续提供信息帮助，这样减少了第二基站与第一基站的邻基站之间获取网络切片的信息的交互信令，提高了获取基站支持的网络切片的信息的便利性和快捷性。
相应的，终端设备接收该RRC连接释放消息，并执行RRC连接释放。
在本发明实施例中，源基站在向目标基站发送切换请求之后，源基站能够获知被拒绝切换的会话由目标基站的网络切片而拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
请参见图5，为本发明实施例提供了另一种通信方法。该通信方法中涉及的接入网设备以基站为例进行说明。如图5所示，该通信方法涉及第一基站、核心网设备。请参见以下具体介绍。
501，第一基站向核心网设备发送第一消息，第一消息用于获取核心网设备针对PLMN支持的网络切片的指示信息。
其中，核心网设备可以服务多个公共陆地移动网络(Public Land Mobile Network，PLMN)。对于同一个核心网设备在服务不同的PLMN的情况下，核心网设备支持的网络切片可能是不同的，对于不同核心网设备服务相同PLMN的情况下，不同核心网设备支持的网络切片可能是不同的，本发明实施例对此不做限定。举例来说，第一核心网设备可以为第一PLMN、第二PLMN 提供服务，在服务第一PLMN的情况下，第一核心网设备支持网络切片1、网络切片2、网络切片3；在服务第二PLMN的情况下，第一核心网设备支持网络切片1、网络切片4。第二核心网设备可以为第一PLMN提供服务，在服务第一PLMN的情况下，第二核心网设备支持网络切片1、网络切片4和网络切片5。
可选的，第一消息携带PLMN的标识，以使核心网设备反馈在服务PLMN的标识指示的PLMN支持的网络切片的指示信息。可选的，所携带的PLMN的标识可以是第一基站包含的小区所支持的PLMN的标识中的部分或者全部。
可选的，第一消息未携带任何PLMN的标识，这样核心网设备可以反馈在为各个PLMN提供服务的情况下分别支持的网络切片的指示信息。例如，若核心网设备为3个PLMN提供服务，则核心网设备向第一基站发送服务每个PLMN的情况下所支持的网络切片的指示信息。
相应的，核心网设备接收来自第一基站的第一消息。
502，核心网设备向第一基站发送第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的指示信息。
其中，核心网设备针对服务不同PLMN所支持的网络切片可以是由网络管理设备预先配置的，例如，网络管理设备为操作维护管理(Operation Administration and Maintenance，OAM)，所支持的网络切片也可能是更新后的网络切片(例如OAM为核心网进行了更新，或者由于其他的原因进行了更新)，本发明实施例对此不做限定。
第一基站通过接收在服务PLMN的情况下核心网设备支持的网络切片的指示信息，能够在第一基站为终端设备选择核心网设备的情况下，提供信息帮助，能够更加准确的为终端设备的会话选择核心网设备。
例如，终端设备接入第一PLMN，需要核心网设备提供服务的会话对应的网络切片为网络切片4。对于在服务第一PLMN的情况下，第一核心网设备支持网络切片1、网络切片2、网络切片3；在服务第二PLMN的情况下，第一核心网设备支持网络切片1、网络切片4；在服务第一PLMN的情况下，第二核心网设备支持网络切片1、网络切片4和网络切片5。若不以PLMN粒度反馈第一核心网设备支持的网络切片，可以看出，第一核心网设备支持网络切片1、网络切片2、网络切片3和网络切片4；第二核心网设备支持网络切片1、网络切片4和网络切片5，这样第一基站很有可能选择为终端设备的会话提供服务的核心网设备为第一核心网设备，但由于第一核心网设备在为第一PLMN服务的情况下是不支持网络切片4的，导致了核心网设备的选择错误。而通过以PLMN粒度反馈核心网设备支持的网络切片，能够避免第一基站为终端设备的会话选择第一核心网设备的情况发生，提高了为终端设备的会话选择核心网设备的准确性。
相应的，第一基站接收核心网设备发送的第二消息。
可选的，在第一消息携带PLMN的标识的情况下，核心网设备可以向第一基站发送在服务该PLMN标识指示的PLMN的情况下核心网设备所支持的网络切片的指示信息；或者，核心网设备向第一基站发送所服务的全部PLMN所支持的网络切片的指示信息。
可选的，在第一消息未携带PLMN标识的情况下，核心网设备可以反馈在为各个PLMN提供服务的情况下分别支持的网络切片的指示信息。
可选的，第一基站和核心网设备之间没有通信接口。例如，第一基站和核心网设备之间的通信接口用N2或NG表示。例如，以N2接口为例，第一基站向核心网设备发送的第一消息可以是N2接口建立请求(N2interface setup request)或基站配置更新(例如，gNB  configuration update)消息，第一基站接收来自核心网设备的N2接口建立请求失败(N2interface setup failure)或基站配置更新失败(例如，gNB configuration updatefailure)消息，核心网设备可以通过N2接口建立失败消息或更新失败消息来发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息，这样在建立的过程中，第一基站也可以获取到在服务PLMN的情况下核心网设备支持的网络切片的指示信息，以减少为获取所支持的网络切片的又一次交互，加快了获取网络切片的指示信息的速度。又如，第一基站向核心网设备发送的第一消息同样是N2接口建立请求或基站配置更新消息，第一基站接收来自核心网设备的N2接口建立响应(N2interface setup response)消息或基站配置更新确认(例如，gNB configuration update ACK)消息，核心网设备可以通过N2接口建立响应消息或核心网设备配置更新确认消息来发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息，这样第一基站可以获取到在服务PLMN的情况下核心网设备支持的网络切片的指示信息，有助于提高获取网络切片的指示信息的便利性。
可选的，第一基站和核心网设备之间有通信接口。例如，第一消息为获取请求，核心网设备可以通过响应消息来发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息。又例如，第一基站向核心网设备发送的第一消息可以是基站配置更新(例如，gNB configuration update)消息，第一基站接收来自核心网设备的基站配置更新失败(例如，gNB configuration update failure)消息，核心网设备可以通过更新失败消息来发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息。又如，第一基站向核心网设备发送的第一消息同样是基站配置更新消息，第一基站接收来自核心网设备的基站配置更新确认(例如，gNB configuration update ACK)消息，核心网设备可以通过核心网设备配置更新确认消息来发送在服务PLMN的情况下核心网设备支持的网络切片的指示信息，这样第一基站可以获取到在服务PLMN的情况下核心网设备支持的网络切片的指示信息，有助于提高获取网络切片的指示信息的便利性。
应理解，步骤501和步骤502之间没有必然的因果关系以及前后顺序，例如步骤502可以独立实施，只要步骤502前，核心网设备确定在服务PLMN的情况下核心网设备支持的网络切片的指示信息即可。例如核心网设备确定在服务PLMN的情况下核心网设备支持的网络切片进行了更新以后，可以主动的实施步骤502，这一情况下第二消息为AMF配置更新消息(例如，AMF configuration update)，以告知第一基站更新后的在服务PLMN的情况下核心网设备支持的网络切片的指示信息。
需要说明的是，本发明实施例中采用核心网设备服务的PLMN的描述方式也可以理解为：核心网设备支持的PLMN，本发明实施例对此不做限定。
在本发明实施例中，第一基站可以通过核心网设备获取到在服务PLMN的情况下核心网设备支持的网络切片的指示信息，通过以PLMN粒度反馈核心网设备支持的网络切片，能够提高第一基站为终端设备的会话选择核心网设备的准确性。
请参见图6，为本发明实施例提供了另一种通信方法。在该实施例中，接入网设备以基站为例进行说明，如图6所示，该通信方法涉及到终端设备、源基站、目标基站以及核心网设备。图6对应于核心网设备确定切换准备失败的情况下的通信方法，源基站是当前与终端设备建立通信连接的基站，目标基站是请求将终端设备的会话切换到的基站。
如图6所示，该通信方法包括步骤601至步骤606，请参见以下具体介绍。
601，源基站向核心网设备发送第一切换请求。
其中，源基站和核心网设备之间有通信接口，例如，N2接口或者NG接口。这样源基站和核心网设备之间可以相互通信。所述第一切换请求用于请求将终端设备的会话从所述源基站切换到目标基站，例如，第一切换请求为handover required。所述第一切换请求包括所述目标基站的信息和请求切换的会话的标识。通过目标基站的信息可以使核心网设备确定终端设备的会话所要切换至的基站/小区；通过请求切换的会话的标识可以使核心网设备确定所要切换的会话。请求切换的会话可以为一个或者多个，不同会话可以对应不同的网络切片。不同网络切片对应的网络切片的指示信息不同。
可选的，所述目标基站信息包括所述目标基站的基站标识、所述目标基站包含的中心单元的标识、所述目标基站包含的分布式单元的标识、所述目标基站包含的物理小区标识和所述目标基站包含的小区全球标识中的至少一个。
可选的，第一切换请求还包括请求切换的会话对应的网络切片的指示信息。这样能够让核心网设备直接确定所要切换的会话对应的网络切片，节省了查找会话对应的网络切片的时间，降低了切换时延，提高了切换成功率。可以理解的是，第一切换请求可以不包括请求切换的会话对应的网络切片的指示信息，本发明实施例对此不做限定。
举例来说，以核心网设备为AMF网元为例来说明，如果AMF网元不能保存会话对应的网络切片指示信息，那么在第一切换请求中需要携带每个会话对应的网络切片指示信息。
可选的，第一会话包含多个数据流，例如数据流为traffic flow或QoS流(QoS flow)，第一切换请求还包括所述会话对应的需要建立的数据流的标识(例如，数据流的标识包括QoS流ID)，以及还包括会话包含的多个数据流中每个数据流对应的QoS信息(例如，优先级信息)。因为在核心网侧，核心网设备包括AMF网元和SMF网元，首先由AMF网元接收源基站发送的第一切换请求消息，并且由AMF网元向目标基站发送第二切换请求消息，其中第二切换请求消息中需要包含需要切换的会话所包含的数据流的标识以及数据流的QoS信息，但是在AMF网元这些信息是不保存的，因此如果在第一切换请求中携带这些信息，这样AMF网元就不需要去SMF网元获得这些信息，从而节省了查找时间，降低了切换时延，提高了切换效率。
可选的，第一切换请求还包括所述会话对应的聚合最大比特速率(aggregate maximum bit rate，AMBR)信息，例如订阅的AMBR信息。目标基站可以根据这个信息进行数据流的流量控制，但该信息需要核心网设备发送至目标基站，这样在核心网侧，核心网设备包括AMF网元和SMF网元，由于AMF网元不存储这一信息，为了减少AMF网元向SMF网元查找该信息的时间，通过在第一切换请求中包括该信息可以节省了查找时间，降低了切换时延，提高了切换效率。
可选的，第一切换请求还包括第一指示信息，该指示信息指示源基站不确定或者不知道目标基站支持的网络切片，以使核心网设备得知源基站不知道目标基站支持的网络切片信息，从而可以在第一切换响应消息携带目标基站支持的网络切片的信息。这样减少了源基站和目标基站之间的交互，提高了网络切片的信息的获取效率。
可选的，目标基站可以是与源基站之间有通信接口的基站；或者，也可以是与源基站之间没有通信接口的基站。可选的，所述第一切换请求可以包括源基站和目标基站之间没有通信接口的第二指示信息，这样以便于核心网设备反馈目标基站支持的网络切片的信息。
可选的，源基站从多个与源基站有通信接口的基站中，选择一个基站确定为目标基站。进一步的，所确定的目标基站支持请求切换的全部或者部分会话对应的网络切片，这样能够 避免由于目标基站不支持全部请求切换的会话的网络切片而导致的切换失败，进而减少了切换失败的次数，以提高切换成功概率。
可选的，源基站可以在接收到终端设备发送的测量报告的情况下，源基站根据测量报告来选择目标基站，并执行步骤601，向目标基站发送切换请求。该测量报告包含小区和基站中至少一个的测量报告值。可选的，若测量报告中包含小区的测量报告值，则所包含的小区可以是源基站包含的小区，也可以是其他基站包含的小区。若测量报告中包含基站的测量报告值，则所包含的基站可以是源基站，也可以是其他基站。可选的，本发明实施例对测量报告中包含的小区的数量和基站的数量不做限定。
602，核心网设备确定请求切换的会话对应的网络切片的指示信息。
其中，该步骤602为可选步骤。若第一切换请求未包括会话对应的网络切片的指示信息，则核心网设备可以根据请求切换的会话的标识，从存储的会话的标识与网络切片的指示信息的对应关系中，查找与请求切换的会话对应的网络切片的指示信息。其中，核心网设备所存储的对应关系可以包含终端设备的一个或多个会话的标识以及对应的网络切片的指示信息。
若第一切换请求包括了请求切换的会话的标识对应的网络切片的指示信息，则核心网设备可以直接确定请求切换的会话对应的网络切片的指示信息，这样可以减少核心网设备查找请求切换的会话对应的网络切片的指示信息的时间。
进一步，第一切换请求可以包括目标基站的信息，核心网设备根据目标基站的信息，确定目标基站所支持的网络切片的信息。其中，网络切片的信息中包含所支持的网络切片的指示信息。在一个具体的例子中，请求切换的会话设定为会话E1，在目标基站与核心网设备之间有通信接口的情况下，若核心网设备已获取到目标基站支持的第一网络切片的信息，则可以直接确定目标基站支持的第一网络切片的指示信息，若核心网设备未获取到目标基站支持的第一网络切片的信息，则可以向目标基站获取目标基站支持的第一网络切片的指示信息。进一步的，核心网设备可以判断目标基站支持的第一网络切片的指示信息是否包含会话E1对应的第二网络切片的指示信息，若包含，则表示目标基站支持会话E1对应的网络切片；若不包含，则表示目标基站不支持会话E1对应的网络切片。
接着，若目标基站支持的第一网络切片的指示信息不包含请求切换的全部会话对应的第二网络切片的指示信息，则核心网设备可以确定目标基站不支持请求切换的会话对应的网络切片，核心网设备可以执行图6中的步骤605，核心网设备向源基站发送第一切换响应消息。这一情况下，第一切换响应消息可以是第一切换失败消息，第一切换失败消息包括拒绝指示信息，用于表示目标基站不支持请求切换的全部会话对应的网络切片。可选的，拒绝指示信息可以是以IE、flag、cause等来指示，本发明实施例对此不做限定。
或者，若目标基站支持请求切换的全部或者部分会话对应的网络切片，则核心网设备执行图6中的步骤603，核心网设备向目标基站发送第二切换请求。
603，核心网设备向目标基站发送第二切换请求。
其中，例如，第二切换请求为Handover Request。第二切换请求包括请求切换的会话对应的会话的标识和与请求切换的会话对应的网络切片的指示信息。
可选的，所述第二切换请求包括源基站请求切换的全部会话的会话标识以及与各个会话对应的网络切片的指示信息。
可选的，在核心网设备执行步骤602之后，核心网设备可以将源基站请求切换的会话划分为第一会话和第二会话，其中第一会话对应的网络切片是目标基站支持的，第二会话对应 的网络切片是目标基站不支持的。进一步的，第二切换请求可以包括仅包括第一会话的标识和第一会话对应的网络切片的指示信息，或者，第二切换请求包括第一会话的标识、第二会话的标识、第一会话对应的网络切片的指示信息和第二会话对应的网络切片的指示信息。本发明实施例对此不做限定。
相应的，目标基站接收第二切换请求。
604，目标基站向核心网设备发送第二切换失败消息。
其中，目标基站接收来自核心网设备的第二切换请求，并确定是否能够为所包括的会话提供服务，若目标基站不能够为任一个会话提供服务，则图6中步骤604向核心网设备发送的第二切换响应消息可以是第二切换失败消息，例如，handover request failure或者handover failure；或者第二切换失败消息为切换准备失败(handover preparation failure)消息。该第二切换失败消息包括拒绝切换的会话对应的原因信息。
进一步的，被拒绝切换的会话的原因信息可以是目标基站不支持拒绝切换的会话对应的网络切片，或者，目标基站支持的拒绝切换的会话对应的网络切片资源受限。
其中，本发明实施例中第二切换失败消息的具体实现可以参考图4所示实施例中步骤403中的切换失败消息的具体描述，在此不再赘述。
相应的，核心网设备接收目标基站发送的第二切换失败消息。
605，核心网设备向源基站发送第一切换响应消息。
其中，核心网设备向源基站发送第一切换响应消息，在该实施例中第一切换响应消息为第一切换失败消息，例如第一切换失败消息为切换准备失败(handover preparation failure)消息。所述第一切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，第一切换失败消息包括拒绝的会话的标识，以及该标识对应的会话被拒绝的原因信息。
可选的，对于核心网设备将源基站请求切换的全部会话的标识均发送至目标基站的情况下，则第一切换失败消息包含的拒绝切换的会话的标识拒绝切换的会话对应的原因信息，与第二切换失败消息中包含的拒绝切换的会话的标识和拒绝切换的会话对应的原因信息是相同的。
可选的，对于核心网设备将源基站请求切换的全部会话中第一会话的标识发送至目标基站的情况下，其中，第一会话是请求切换的会话中被目标基站支持其对应的网络切片的会话，则第一切换失败消息包含第一拒绝会话的标识、第一拒绝会话对应的原因信息、第二拒绝会话的标识和第二拒绝会话对应的原因信息。其中，第一拒绝会话是包含在第二切换失败消息中的被拒绝切换的会话，第二拒绝会话是请求切换的会话中目标基站不支持其对应的网络切片的会话。其中，第二拒绝会话的标识和第二拒绝会话对应的原因信息是由核心网设备确定的。
可选的，核心网设备在第一切换响应消息携带目标基站支持的网络切片的信息。例如在第一切换请求包括源基站不确定目标基站支持的网络切片的第一指示信息的情况下，或者核心网设备根据第一切换请求中携带的源基站与目标基站没有通信接口的指示判断源基站不知道目标基站支持的网络切片。这样减少了源基站和目标基站之间的交互，提高了网络切片的信息的获取效率。
606，可选的，源基站向终端设备发送RRC连接释放消息。
其中，步骤606可以参考图4所示实施例中步骤404的详细介绍，在此不再赘述。
在本发明实施例中，源基站在向核心网设备发送切换请求之后，源基站能够获知被拒绝切换的会话由目标基站的网络切片而拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
请参见图7，为本发明实施例提供了另一种通信方法。在该实施例中，接入网设备以基站为例进行说明，如图7所示，该通信方法涉及到终端设备、源基站、目标基站以及核心网设备。图7对应于核心网设备确定切换成功的情况的通信方法，源基站是当前与终端设备建立通信连接的基站，目标基站是请求将终端设备的会话切换到的基站。
如图7所示，该通信方法包括步骤701至步骤707，请参见以下具体介绍。
701，源基站向核心网设备发送第一切换请求。
702，核心网设备确定请求切换的会话对应的网络切片的指示信息。
703，核心网设备向目标基站发送第二切换请求。
其中，步骤701至步骤703可以参考图6所示实施例中对应步骤601-603的详细描述，在此不再赘述。
704，目标基站向核心网设备发送第二切换请求确认消息。
其中，第二切换请求确认消息包括确认切换的会话的标识。例如，第二切换请求确认消息为handover request acknowledge。
可选的，第一切换响应消息还可以包括拒绝切换的会话的标识和拒绝切换的会话对应的原因信息。
可选的，第二切换请求确认消息还包括拒绝切换的会话对应的重发指示信息。该重发指示信息用于指示是否允许终端设备将拒绝切换的会话包含的数据流路由到目标基站支持的网络切片。举例来说，以拒绝的会话为会话B1、会话B1对应网络切片1为例来说明，会话B1被拒绝切换的原因信息可以为目标基站不支持会话B1对应的网络切片1，也可为目标基站指示网络切片1但网络切片1资源受限，不论是什么原因导致会话B1被拒绝切换，若目标基站支持网络切片2，且会话B1包含的数据流在路由至网络切片2的情况下也可以实现数据传输，则目标基站确定会话B1对应的重发指示信息为：允许终端设备将会话B1包含的数据流路由到目标基站支持的网络切片2。另外，若目标基站中不存在会话B1包含的数据流可以路由至的网络切片，则目标基站确定会话B1对应的重发指示信息为：不允许终端设备将会话B1包含的数据流路由到目标基站支持的网络切片。
可选的，切换请求确认消息还包括请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。具体介绍可以参考图3所示实施例中步骤303中的详细描述，在此不再赘述。
其中，本发明实施例中的第二切换请求确认消息和参考图3所示实施例中切换请求确认消息反馈确认切换的会话的标识、拒绝切换的标识和拒绝切换的会话对应的原因信息的形式来向核心网设备发送第二切换请求确认消息。在此不再赘述。
705，核心网设备向源基站发送第一切换请求确认消息。
其中，核心网设备向源基站发送第一切换响应消息，在该实施例中第一切换响应消息为第一切换请求确认消息，例如，第一切换请求确认消息为切换命令(Handover command)。第一切换请求确认消息包括确认切换的会话的标识。
可选的，第一切换相应消息还可以包括拒绝切换的会话的标识和拒绝切换的会话对应的原因信息。
可选的，对于核心网设备将源基站请求切换的全部会话的标识均发送至目标基站的情况下，则第一切换请求确认消息包含的拒绝切换的会话的标识和拒绝切换的会话对应的原因信息，与第二切换请求确认消息中包含的拒绝切换的会话的标识和拒绝切换的会话对应的原因信息是相同的。
可选的，对于核心网设备将源基站请求切换的全部会话中第一会话的标识发送至目标基站的情况下，其中，第一会话是请求切换的会话中被目标基站支持其对应的网络切片的会话，则第一切换请求确认消息包含第一拒绝会话的标识、第一拒绝会话对应的原因信息、第二拒绝会话的标识和第二拒绝会话对应的原因信息。其中，第一拒绝会话是包含在第二切换请求确认消息中的被拒绝切换的会话，第二拒绝会话是请求切换的会话中目标基站不支持其对应的网络切片的会话。其中，第二拒绝会话的标识和第二拒绝会话对应的原因信息是由核心网设备确定的。
可选的，核心网设备在第一切换响应消息携带目标基站支持的网络切片的信息。例如在第一切换请求包括源基站不确定目标基站支持的网络切片的第一指示信息的情况下，或者核心网设备根据第一切换请求中携带的源基站与目标基站没有通信接口的指示判断源基站不知道目标基站支持的网络切片。这样减少了源基站和目标基站之间的交互，提高了网络切片的指示信息的获取效率。
706，源基站向终端设备发送切换命令。
707，终端设备向目标基站发送切换确认消息。
其中，步骤706和步骤707可以参考图3所示实施例中步骤304和步骤305的详细描述，在此不再赘述。
在本发明实施例中，源基站在向核心网设备发送切换请求之后，源基站能够获知被拒绝切换的会话由目标基站的网络切片而拒绝的原因信息，这样为其他需要请求切换到该目标基站的会话提供了信息帮助，在源基站需要切换相同网络切片的会话时，可以直接确定是否能够切换到目标基站中，提高了切换成功的概率。
请参见图8，图8是本申请实施例提供的一种基站的结构示意图。该基站可以为源基站，用于实现图3或图4的实施例。如图8所示，该源基站包括：
发送单元801，用于向目标基站发送切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
接收单元802，用于接收来自所述目标基站的切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述请求切换的会话包括第一会话；或者，所述请求切换的会话包括所述第一会话和第二会话；
所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片， 或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可选的，在所述切换响应消息为切换请求确认消息的情况下，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，在所述切换响应消息为切换请求确认消息的情况下，所述源基站向所述终端设备发送切换命令，所述切换命令包括被所述目标基站拒绝切换的会话对应的重发指示信息。
可选的，在所述切换响应消息为切换请求确认消息的情况下，所述切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可选的，所述发送单元801，还用于在所述切换响应消息为切换失败消息的情况下，向所述终端设备发送无线资源控制RRC连接释放消息。
可选的，所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
可以理解的，关于图8的基站包括的功能块的具体实现方式及相应的有益效果，可参考前述图3或图4的实施例的具体介绍，这里不赘述。
在本专利申请中，发送单元可以是发送器，接收单元可以是接收器。
请参见图9，图9是本申请实施例提供的一种基站的结构示意图。该基站可以为目标基站，用于实现图3或图4的实施例。如图9所示，该目标基站包括：
接收单元901，接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
发送单元902，用于向所述源基站发送切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述请求切换的会话包括第一会话；或者，所述请求切换的会话包括所述第一会话和第二会话；
所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可选的，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，在所述切换响应消息为切换请求确认消息的情况下，所述切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可选的，所述接收单元901，还用于接收来自所述终端设备的切换确认消息；
所述发送单元902，还用于向核心网设备发送路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
所述接收单元901，还用于接收来自所述核心网设备的路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
可选的，所述路径转移请求还包括被所述目标基站拒绝切换的会话对应的网络切片的指示信息。
可选的，所述路径转移请求还包括被所述目标基站拒绝切换的会话对应的原因信息。
可以理解的，关于图9的基站包括的功能块的具体实现方式及相应的有益效果，可参考前述图3或图4的实施例的具体介绍，这里不赘述。
请参见图10，图10是本申请实施例提供的一种核心网设备的结构示意图。该核心网设备用于实现图4的实施例。如图10所示，该核心网设备包括：
接收单元1001，用于接收来自目标基站的路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
处理单元1002，用于对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理；
发送单元1003，用于向所述目标基站发送路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
可选的，所述路径转移请求还包括被所述目标基站拒绝切换的会话对应的网络切片的指示信息。
可选的，所述路径转移请求包括被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可以理解的，关于图10的核心网设备包括的功能块的具体实现方式及相应的有益效果，可参考前述图4的实施例的具体介绍，这里不赘述。
本专利申请中，处理单元可以通过处理器的形式实现。
请参见图11，图11是本申请实施例提供的一种基站的结构示意图。该基站可以为第一基站，用于实现图5的实施例。如图11所示，该基站包括：
发送单元1101，用于向核心网设备发送第一消息，所述第一消息用于获取所述核心网设备针对PLMN支持的网络切片的信息；
接收单元1102，用于接收来自所述核心网设备的第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
可以理解的，关于图11的基站包括的功能块的具体实现方式及相应的有益效果，可参考前述图5的实施例的具体介绍，这里不赘述。
请参见图12，图12是本申请实施例提供的一种核心网设备的结构示意图。该核心网设备用于实现图5的实施例。如图12所示，该核心网设备包括：
接收单元1201，用于接收来自第一基站的第一消息，所述第一消息用于获取所述核心网设备针对PLMN支持的网络切片的信息；
发送单元1202，用于向所述第一基站发送第二消息，第二消息包括在核心网设备服务的PLMN支持的网络切片的信息。
可以理解的，关于图12的核心网设备包括的功能块的具体实现方式及相应的有益效果，可参考前述图5的实施例的具体介绍，这里不赘述。
请参见图13，图13是本申请实施例提供的一种基站的结构示意图。该基站可以为源基站，用于实现图6或图7的实施例。如图13所示，该源基站包括：
发送单元1301，用于向核心网设备发送第一切换请求，所述第一切换请求用于请求将终端设备的会话从所述源基站切换到目标基站，所述第一切换请求包括所述目标基站的信息和请求切换的会话的标识；
接收单元1302，用于接收来自所述核心网设备的第一切换响应消息，所述第一切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，所述发送单元1301，还用于在所述第一切换响应消息为第一切换请求确认消息的情况下，向所述终端设备发送切换命令，所述切换命令包括被所述目标基站拒绝切换的会话对应的重发指示信息。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可选的，所述发送单元1301，还用于在所述第一切换响应消息为第一切换失败消息的情况下，向所述终端设备发送RRC连接释放消息。
可选的，所述RRC连接释放消息包括所述源基站的邻小区支持的网络切片的指示信息；或者，包括所述源基站的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换请求确认消息还包括所述目标基站支持的网络切片的信息。
可选的，所述第一切换请求还包括所述请求切换的会话对应的网络切片的指示信息。
可选的，所述第一切换请求还包括所述请求切换的会话需要建立的数据流的标识和所述数据流对应的QoS信息。
可选的，所述第一切换请求还包括所述会话对应的聚合最大比特速率AMBR信息。
可以理解的，关于图13的基站包括的功能块的具体实现方式及相应的有益效果，可参考前述图6或图7的实施例的具体介绍，这里不赘述。
请参见图14，图14是本申请实施例提供的一种基站的结构示意图。该基站可以为目标基站，用于实现图6或图7的实施例。如图14所示，该目标基站包括：
接收单元1401，用于接收来自核心网设备的第二切换请求，所述第二切换请求包括会话的标识和所述会话对应的网络切片的指示信息；
发送单元1402，用于向所述源基站发送第二切换响应消息，所述第二切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述第二切换请求所包括的会话为第一会话；或者，所述第二切换请求所包括的会话为所述第一会话和第二会话；
所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可选的，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换请求确认消息还包括所述第二切换请求包括的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可以理解的，关于图14的基站包括的功能块的具体实现方式及相应的有益效果，可参考前述图6或图7的实施例的具体介绍，这里不赘述。
请参见图15，图15是本申请实施例提供的一种核心网设备的结构示意图。该核心网设备用于实现图6或图7的实施例。如图15所示，该核心网设备包括：
接收单元1501，用于接收来自源基站的第一切换请求，所述第一切换请求用于请求将终端设备的会话从所述源基站切换到目标基站，所述第一切换请求包括所述目标基站的信息和请求切换的会话的标识；
发送单元1502，用于向所述源基站发送第一切换响应消息，所述第一切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
可选的，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可选的，在所述第一切换响应消息为第一切换请求确认消息的情况下，所述第一切换请求确认消息还包括所述目标基站支持的网络切片的信息；或者，目标基站包含的小区所属TA/RA支持的网络切片的指示信息。
可选的，所述第一切换请求还包括所述请求切换的会话对应的网络切片的指示信息。
可选的，所述第一切换请求还包括所述请求切换的会话需要建立的数据流的标识和所述 数据流对应的QoS信息。
可选的，所述第一切换请求还包括所述会话对应的聚合最大比特速率AMBR信息。
可选的，所述发送单元1502，还用于向所述目标基站发送第二切换请求，所述第二切换请求包括会话的标识和所述会话对应的网络切片的指示信息；
所述接收单元1501，还用于接收来自所述目标基站的第二切换响应消息，所述第二切换响应消息包括所述拒绝指示信息。
可选的，所述第二切换请求所包括的会话为第一会话；或者，所述第二切换请求所包括的会话为所述第一会话和第二会话；
所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
可选的，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
可选的，在所述第二切换响应消息为第二切换请求确认消息的情况下，所述第二切换请求确认消息还包括所述第二切换请求包括的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
可以理解的，关于图15的核心网设备包括的功能块的具体实现方式及相应的有益效果，可参考前述图6或图7的实施例的具体介绍，这里不赘述。
本专利申请中，各个确定单元可以通过处理器的形式实现。
请参见图16，图16是本申请实施例提供的一种终端设备的结构示意图。该终端设备可以为终端设备，用于实现图4或图6的实施例。如图16所示，该终端设备包括：
接收单元1601，用于接收来自源基站的无线资源控制RRC连接释放消息；
处理单元1602，用于释放RRC连接；所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括所述源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
可以理解的，关于图16的终端设备包括的功能块的具体实现方式及相应的有益效果，可参考前述图4或图6的实施例的具体介绍，这里不赘述。
上述图8、图9、图11、图13、图14所示实施例中的基站可以以图17所示的基站1700实现。如图17所示，为本发明实施例提供了另一种基站的结构示意图，图17所示的基站1700包括：处理器1701和收发器1702，所述收发器1702用于支持基站1700与上述实施例中涉及的核心网设备或其他基站之间的信息传输。处理器1701和收发器1702通信连接，例如通过总线相连。所述基站1700还可以包括存储器1703。存储器1703用于存储供基站1700执行的程序代码和数据，处理器1701用于执行存储器1703中存储的应用程序代码，以实现图3至图7所示任一实施例提供的基站的动作。
需要说明的是，实际应用中基站可以包括一个或者多个处理器，该基站1700的结构并不构成对本申请实施例的限定。
处理器1701可以是中央处理器(central processing unit，CPU)，网络处理器(network  processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
存储器1703可以包括易失性存储器(volatile memory)，例如随机存取存储器(random access memory，RAM)；存储器1703也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器1703还可以包括上述种类的存储器的组合。
在本发明实施例中还提供了一种计算机存储介质，可以用于存储图8、图9、图11、图13、图14所示实施例中所述基站所用的计算机软件指令，其包含用于执行上述实施例中为基站所设计的程序。该存储介质包括但不限于快闪存储器、硬盘、固态硬盘。
在本发明实施例中还提供了一种计算机程序产品，该计算机产品被计算设备运行时，可以执行上述图8、图9、图11、图13、图14实施例中为基站所设计的通信方法。
上述图10、图12、图15所示的核心网设备可以以图18所示的核心网设备1800实现。如图18所示，为本发明实施例提供了另一种核心网设备的结构示意图，图18所示的核心网设备1800包括：处理器1801和收发器1802，所述收发器1802用于支持核心网设备1800与上述实施例中涉及的基站之间的信息传输。处理器1801和收发器1802通信连接，例如通过总线相连。所述核心网设备1800还可以包括存储器1803。存储器1803用于存储供核心网设备1800执行的程序代码和数据，处理器1801用于执行存储器1803中存储的应用程序代码，以实现图4、图5、图6或图7所示任一实施例提供的核心网设备的动作。
需要说明的是，实际应用中核心网设备可以包括一个或者多个处理器，该核心网设备1800的结构并不构成对本申请实施例的限定。
处理器1801可以是CPU，NP，硬件芯片或者其任意组合。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
存储器1803可以包括易失性存储器，例如RAM；存储器1803也可以包括非易失性存储器，例如ROM，快闪存储器，硬盘或固态硬盘；存储器1803还可以包括上述种类的存储器的组合。
在本发明实施例中还提供了一种计算机存储介质，可以用于存储图10、图12、图15所示实施例中所述核心网设备所用的计算机软件指令，其包含用于执行上述实施例中为核心网设备所设计的程序。该存储介质包括但不限于快闪存储器、硬盘、固态硬盘。
在本发明实施例中还提供了一种计算机程序产品，该计算机产品被计算设备运行时，可以执行上述图10、图12、图15所示实施例中为核心网设备所设计的通信方法。
上述图16所示实施例中的终端设备可以以图19所示的终端设备1900实现。如图19所示，为本发明实施例提供了另一种终端设备的结构示意图，图19所示的终端设备1900包括：处理器1901和收发器1902，所述收发器1902用于支持终端设备1900与上述实施例中涉及的基站之间的信息传输。处理器1901和收发器1902通信连接，例如通过总线相连。所述终 端设备1900还可以包括存储器1903。存储器1903用于存储供终端设备1900执行的程序代码和数据，处理器1901用于执行存储器1903中存储的应用程序代码，以实现图4、图6所示任一实施例提供的终端设备的动作。
需要说明的是，实际应用中终端设备可以包括一个或者多个处理器，该终端设备1900的结构并不构成对本申请实施例的限定。
处理器1901可以是CPU，NP，硬件芯片或者其任意组合。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
存储器1903可以包括易失性存储器，例如RAM；存储器1903也可以包括非易失性存储器，例如ROM，快闪存储器，硬盘或固态硬盘；存储器1903还可以包括上述种类的存储器的组合。
在本发明实施例中还提供了一种计算机存储介质，可以用于存储图16所示实施例中所述终端设备所用的计算机软件指令，其包含用于执行上述实施例中为终端设备所设计的程序。该存储介质包括但不限于快闪存储器、硬盘、固态硬盘。
在本发明实施例中还提供了一种计算机程序产品，该计算机产品被计算设备运行时，可以执行上述图16实施例中为终端设备所设计的通信方法。
本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选的还包括没有列出的步骤或单元，或可选的还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
本领域普通技术人员可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本发明较佳实施例而已，当然不能以此来限定本发明之权利范围，因此依本发明权利要求所作的等同变化，仍属本发明所涵盖的范围。

Claims (80)

  1. 一种通信方法，其特征在于，包括：
    源基站向目标基站发送切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    所述源基站接收来自所述目标基站的切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
  2. 根据权利要求1所述的方法，其特征在于，所述请求切换的会话包括第一会话；或者，所述请求切换的会话包括所述第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  3. 根据权利要求1或2所述的方法，其特征在于，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，在所述切换响应消息为切换请求确认消息的情况下，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
  5. 根据权利要求4所述的方法，其特征在于，还包括：
    在所述切换响应消息为切换请求确认消息的情况下，所述源基站向所述终端设备发送切换命令，所述切换命令包括被所述目标基站拒绝切换的会话对应的重发指示信息。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述切换响应消息为切换请求确认消息的情况下，所述切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
  7. 根据权利要求1-3任一项所述的方法，其特征在于，还包括：
    在所述切换响应消息为切换失败消息的情况下，所述源基站向所述终端设备发送无线资源控制RRC连接释放消息。
  8. 根据权利要求7所述的方法，其特征在于，所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
  9. 一种通信方法，其特征在于，包括：
    目标基站接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    所述目标基站向所述源基站发送切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
  10. 根据权利要求9所述的方法，其特征在于，所述请求切换的会话包括第一会话；或 者，所述请求切换的会话包括所述第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  11. 根据权利要求9或10所述的方法，其特征在于，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，在所述切换响应消息为切换请求确认消息的情况下，所述切换请求确认消息还包括所述请求切换的会话的被拒绝的承载的标识或被拒绝的数据流的标识。
  14. 根据权利要求9-13任一项所述的方法，其特征在于，还包括：
    所述目标基站接收来自所述终端设备的切换确认消息；
    所述目标基站向核心网设备发送路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
    所述目标基站接收来自所述核心网设备的路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
  15. 根据权利要求14所述的方法，其特征在于，所述路径转移请求还包括被所述目标基站拒绝切换的会话对应的网络切片的指示信息。
  16. 一种通信方法，其特征在于，包括：
    核心网设备接收来自目标基站的路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
    所述核心网设备对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理；
    所述核心网设备向所述目标基站发送路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
  17. 一种通信方法，其特征在于，包括：
    终端设备接收来自源基站的无线资源控制RRC连接释放消息；
    所述终端设备释放RRC连接；
    所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括所述源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
  18. 一种基站，其特征在于，所述基站为源基站，所述源基站包括处理器和收发器：
    所述处理器通过所述收发器向目标基站发送切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    所述处理器通过所述收发器接收来自所述目标基站的切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基 站拒绝切换的会话对应的原因信息。
  19. 根据权利要求18所述的基站，其特征在于，所述请求切换的会话包括第一会话；或者，所述请求切换的会话包括所述第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  20. 根据权利要求18或19所述的基站，其特征在于，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
  21. 根据权利要求18-20任一项所述的基站，其特征在于，在所述切换响应消息为切换请求确认消息的情况下，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
  22. 根据权利要求21所述的基站，其特征在于，还包括：
    在所述切换响应消息为切换请求确认消息的情况下，所述处理器通过所述收发器向所述终端设备发送切换命令，所述切换命令包括被所述目标基站拒绝切换的会话对应的重发指示信息。
  23. 根据权利要求18-20任一项所述的基站，其特征在于，
    所述处理器通过所述收发器在所述切换响应消息为切换失败消息的情况下，向所述终端设备发送无线资源控制RRC连接释放消息。
  24. 根据权利要求23所述的基站，其特征在于，所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
  25. 一种基站，其特征在于，所述基站为目标基站，所述目标基站包括处理器和收发器：
    所述处理器通过所述收发器接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    所述处理器通过所述收发器向所述源基站发送切换响应消息，所述切换响应消息包括拒绝指示信息，所述拒绝指示信息用于指示由于网络切片导致所述会话中被所述目标基站拒绝切换的会话对应的原因信息。
  26. 根据权利要求25所述的基站，其特征在于，所述请求切换的会话包括第一会话；或者，所述请求切换的会话包括所述第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  27. 根据权利要求25或26所述的基站，其特征在于，所述原因信息包括：所述目标基站不支持所述拒绝切换的会话对应的网络切片，或者，所述目标基站支持的所述拒绝切换的会话对应的网络切片资源受限。
  28. 根据权利要求25-27任一项所述的基站，其特征在于，所述切换响应消息还包括被所述目标基站拒绝切换的会话对应的重发指示信息，所述会话对应的重发指示信息用于指示是否允许所述终端设备将所述拒绝切换的会话包含的数据流路由到所述目标基站支持的网络切片。
  29. 一种核心网设备，其特征在于，所述核心网设备包括处理器和收发器：
    所述处理器通过所述收发器接收来自目标基站的路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
    所述处理器用于对确认切换的会话执行路径转移处理，对拒绝切换的会话执行去激活或删除处理；
    所述处理器通过所述收发器向所述目标基站发送路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
  30. 一种终端设备，其特征在于，所述终端设备包括处理器和收发器：
    所述处理器通过所述收发器接收来自源基站的无线资源控制RRC连接释放消息；
    所述处理器释放RRC连接；所述RRC连接释放消息包括源小区的邻小区支持的网络切片的指示信息；或者，包括所述源小区的邻小区所属TA/RA支持的网络切片的指示信息；或者，包括所述源基站的邻基站支持的网络切片的信息。
  31. 根据权利要求16所述的方法，其特征在于，所述路径转移请求消息还包括：被所述目标基站拒绝切换的会话对应的原因信息。
  32. 根据权利要求31所述的方法，其特征在于，所述原因信息包括所述目标基站不支持拒绝切换的会话对应的网络切片。
  33. 根据权利要求32所述的方法，其特征在于，所述核心网设备对拒绝切换的会话执行去激活或删除处理，包括：所述核心网设备对因所述目标基站不支持被拒绝切换的会话对应的网络切片而被拒绝的所述会话执行删除处理。
  34. 一种通信方法，其特征在于，包括：
    目标基站向核心网设备发送路径转移请求，所述路径转移请求包括所述目标基站确认切换的会话的标识和所述目标基站拒绝切换的会话的标识；
    所述目标基站接收所述核心网设备发送的路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
  35. 根据权利要求34所述的方法，其特征在于，所述路径转移请求响应消息还包括：
    被所述目标基站拒绝切换的会话对应的原因信息。
  36. 根据权利要求35所述的方法，其特征在于，原因信息包括：所述目标基站不支持拒绝切换的会话对应的网络切片。
  37. 根据权利要求34-36任一所述的方法，其特征在于，在所述目标基站向所述核心网设备发送所述路径转移请求前，所述方法还包括：
    所述目标基站接收来自源基站的切换请求，
    所述目标基站根据网络切片的支持情况和资源使用情况以及所述切换请求进行接入控制。
  38. 根据权利要求34-36任一所述的方法，其特征在于，在所述目标基站向所述核心网设备发送所述路径转移请求前，所述方法还包括：
    所述目标基站接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述目标基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    如果所述目标基站不支持所述会话对应的网络切片，所述目标基站拒绝所述会话。
  39. 根据权利要求38所述的方法，其特征在于，所述网络切片的指示信息是单网络切片 选择辅助信息S-NSSAI。
  40. 根据权利要求38或39所述的方法，其特征在于，所述请求切换的会话包括第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  41. 根据权利要求34-40任一项所述的方法，其特征在于，所述方法还包括：所述目标基站向所述源基站发送切换确认消息；所述目标基站确认切换的会话中部分数据流被拒绝。
  42. 根据权利要求41所述的方法，其特征在于，所述切换请求确认消息还包括用于指示所述部分数据流被拒绝的原因信息。
  43. 根据权利要求42所述的方法，其特征在于，所述用于指示所述部分数据流被拒绝的原因信息包括以下任一：所述部分数据流的标识重复、资源受限、所述部分数据流对应服务质量QoS组合无效。
  44. 一种通信方法，其特征在于：
    基站接收第一核心网设备发送的消息，所述消息包括所述第一核心网设备服务的公共陆地移动网络PLMN支持的网络切片的指示信息；
    所述基站使用所述指示信息选择为终端设备提供服务的核心网设备。
  45. 如权44所述的方法，其特征在于：所述消息为AMF配置更新消息。
  46. 如权44所述的方法，其特征在于：所述消息NG接口建立响应。
  47. 如权46所述的方法，其特征在于：所述方法还包括：所述基站向所述核心网设备发送NG接口建立请求。
  48. 如权44-47任一所述的方法，其特征在于，所述核心网设备服务的PLMN支持的网络切片的指示信息是所述核心网设备所服务的各个PLMN分别支持的网络切片的指示信息。
  49. 如权44-48任一所述的方法，其特征在于，所述网络切片的指示信息包括单网络切片选择辅助信息S-NSSAI。
  50. 一种通信方法，其特征在于：
    核心网设备确定所述核心网设备服务的公共陆地移动网络PLMN支持的网络切片的指示信息；
    所述核心网设备向基站发送第二消息，所述第二消息包括所述核心网设备服务的PLMN支持的网络切片的指示信息。
  51. 如权50所述的方法，其特征在于：所述第二消息为AMF配置更新消息。
  52. 如权50所述的方法，其特征在于：所述第二消息NG接口建立响应。
  53. 如权52所述的方法，其特征在于：所述方法还包括：所述核心网设备接收所述基站发送的NG接口建立请求。
  54. 如权50-52任一所述的方法，其特征在于，所述核心网设备服务的PLMN支持的网络切片的指示信息是所述核心网设备所服务的各个PLMN分别支持的网络切片的指示信息。
  55. 如权29所述的核心网设备，其特征在于，所述路径转移请求消息还包括：被目标基站拒绝切换的会话对应的原因信息。
  56. 根据权利要求55所述的核心网设备，其特征在于，所述原因信息包括目标基站不支持拒绝切换的会话对应的网络切片。
  57. 根据权利要求29所述的核心网设备，其特征在于，所述处理器具体用于对因所述目 标基站不支持被拒绝切换的会话对应的网络切片而被拒绝的所述会话执行删除处理。
  58. 一种基站，其特征在于，包括：
    发送单元，用于向核心网设备发送路径转移请求，所述路径转移请求包括所述基站确认切换的会话的标识和所述基站拒绝切换的会话的标识；
    接收单元，用于接收所述核心网设备发送的路径转移请求响应消息，所述路径转移请求响应消息包括成功转移路径的会话的标识。
  59. 根据权利要求58所述的基站，其特征在于，所述路径转移请求响应消息还包括：
    被目标基站拒绝切换的会话对应的原因信息。
  60. 根据权利要求59所述的基站，其特征在于，原因信息包括：目标基站不支持拒绝切换的会话对应的网络切片。
  61. 根据权利要求58-60任一所述的基站，其特征在于，
    所述接收单元，还用于接收来自源基站的切换请求，
    所述基站还包括处理器，所述处理器用于根据网络切片的支持情况和资源使用情况以及所述切换请求进行接入控制。
  62. 根据权利要求58-60任一所述的基站，其特征在于，
    所述接收单元，还用于接收来自源基站的切换请求，所述切换请求用于请求将终端设备的会话从所述源基站切换至所述基站，所述切换请求包括请求切换的会话的标识和所述会话对应的网络切片的指示信息；
    所述基站还包括处理器，所述处理器用于在所述基站不支持所述会话对应的网络切片的情况下，拒绝所述会话。
  63. 根据权利要求62所述的基站，其特征在于，所述网络切片的指示信息是单网络切片选择辅助信息S-NSSAI。
  64. 根据权利要求62或63所述的方法，其特征在于，所述请求切换的会话包括第一会话和第二会话；
    所述第一会话对应的网络切片是所述目标基站支持的，所述第二会话对应的网络切片是所述目标基站不支持的。
  65. 根据权利要求58-64任一项所述的基站，其特征在于，所述发送单元还用于向所述源基站发送切换确认消息；所述目标基站确认切换的会话中部分数据流被拒绝。
  66. 根据权利要求65所述的基站，其特征在于，所述切换请求确认消息还包括用于指示所述部分数据流被拒绝的原因信息。
  67. 根据权利要求46所述的基站，其特征在于，所述用于指示所述部分数据流被拒绝的原因信息包括以下任一：所述部分数据流的标识重复、资源受限、所述部分数据流对应服务质量QoS组合无效。
  68. 一种基站，其特征在于包括：
    接收单元，用于接收第一核心网设备发送的消息，所述消息包括所述第一核心网设备服务的公共陆地移动网络PLMN支持的网络切片的指示信息；
    处理单元，用于使用所述指示信息选择为终端设备提供服务的核心网设备。
  69. 如权68所述的基站，其特征在于：所述消息为AMF配置更新消息。
  70. 如权68所述的基站，其特征在于：所述消息N2接口建立响应。
  71. 如权70所述的基站，其特征在于：还包括发送单元，所述发送单元用于向所述核心 网设备发送N2接口建立请求。
  72. 如权68-71任一所述的基站，其特征在于，所述核心网设备服务的PLMN支持的网络切片是的指示信息是所述核心网设备所服务的各个PLMN分别支持的网络切片的指示信息。
  73. 如权68-72任一所述的方法，其特征在于，所述网络切片的指示信息包括单网络切片选择辅助信息S-NSSAI。
  74. 一种核心网设备，其特征在于：
    处理单元，用于确定所述核心网设备服务的公共陆地移动网络PLMN支持的网络切片的指示信息；
    发送单元，用于向基站发送第二消息，所述第二消息包括所述核心网设备服务的PLMN支持的网络切片的指示信息。
  75. 如权74所述的核心网设备，其特征在于：所述第二消息为AMF配置更新消息。
  76. 如权74所述的核心网设备，其特征在于：所述第二消息NG接口建立响应。
  77. 如权76所述的核心网设备，其特征在于还包括接收单元，所述接收单元用于接收所述基站发送的NG接口建立请求。
  78. 如权74-77任一所述的核心网设备，其特征在于，所述核心网设备服务的PLMN支持的网络切片的指示信息是所述核心网设备所服务的各个PLMN分别支持的网络切片的指示信息。
  79. 一种通信设备，其特征在于，用于执行权利要求1-17、31-54、或73中任意一项所述的方法。
  80. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行权利要求1-17、31-54、或73中任意一项所述的方法。
PCT/CN2018/099875 2017-08-11 2018-08-10 通信方法及源基站、目标基站、核心网设备、终端设备 WO2019029674A1 (zh)

Priority Applications (13)

Application Number Priority Date Filing Date Title
IL269926A IL269926B2 (en) 2017-08-11 2018-08-10 Communication method, source base station, destination base station, network core device and terminal device
BR112019019985A BR112019019985A2 (pt) 2017-08-11 2018-08-10 método de comunicação, estação de base fonte, estação de base alvo, dispositivo de rede principal, e dispositivo terminal
KR1020197026830A KR102311745B1 (ko) 2017-08-11 2018-08-10 통신 방법, 소스 기지국, 타깃 기지국, 코어 네트워크 장치 및 단말 장치
AU2018315286A AU2018315286B2 (en) 2017-08-11 2018-08-10 Communication method, source base station, target base station, core network device, and terminal device
EP18842877.5A EP3576458B1 (en) 2017-08-11 2018-08-10 Communication method, source base station, target base station, core network device, and terminal device
EP21189454.8A EP4007367B1 (en) 2017-08-11 2018-08-10 Communication methods, target base station and core network device
KR1020217031973A KR102498517B1 (ko) 2017-08-11 2018-08-10 통신 방법, 소스 기지국, 타깃 기지국, 코어 네트워크 장치 및 단말 장치
RU2019132118A RU2772653C2 (ru) 2017-08-11 2018-08-10 Способ связи, исходная базовая станция, целевая базовая станция, устройство базовой сети и оконечное устройство
JP2019544921A JP7031944B2 (ja) 2017-08-11 2018-08-10 通信方法、ソース基地局、ターゲット基地局、コアネットワークデバイス、および端末デバイス
EP24177020.5A EP4444025A2 (en) 2017-08-11 2018-08-10 Communication method, source base station, target base station, core network device, and terminal device
US16/443,304 US10952105B2 (en) 2017-08-11 2019-06-17 Communication method, source base station, target base station, core network device, and terminal device
US17/199,928 US11758441B2 (en) 2017-08-11 2021-03-12 Communication method, source base station, target base station, core network device, and terminal device
US18/364,932 US20240040443A1 (en) 2017-08-11 2023-08-03 Communication method, source base station, target base station, core network device, and terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710686415.2A CN109392038B (zh) 2017-08-11 2017-08-11 通信方法及源基站、目标基站、核心网设备、终端设备
CN201710686415.2 2017-08-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/443,304 Continuation US10952105B2 (en) 2017-08-11 2019-06-17 Communication method, source base station, target base station, core network device, and terminal device

Publications (1)

Publication Number Publication Date
WO2019029674A1 true WO2019029674A1 (zh) 2019-02-14

Family

ID=64640370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099875 WO2019029674A1 (zh) 2017-08-11 2018-08-10 通信方法及源基站、目标基站、核心网设备、终端设备

Country Status (9)

Country Link
US (3) US10952105B2 (zh)
EP (3) EP4007367B1 (zh)
JP (1) JP7031944B2 (zh)
KR (2) KR102498517B1 (zh)
CN (4) CN109041138B (zh)
AU (1) AU2018315286B2 (zh)
BR (1) BR112019019985A2 (zh)
IL (1) IL269926B2 (zh)
WO (1) WO2019029674A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020200469A1 (en) * 2019-04-05 2020-10-08 Nokia Technologies Oy Methods for handling load variations in handover scenarios
EP3996417A4 (en) * 2019-07-25 2022-08-31 Huawei Technologies Co., Ltd. DELIVERY METHOD AND DEVICE
EP3944716A4 (en) * 2019-04-03 2022-12-28 ZTE Corporation METHOD AND APPARATUS FOR SESSION PROCESSING, NETWORK DEVICE AND STORAGE MEDIUM
EP4000311B1 (en) * 2019-08-23 2023-07-26 Qualcomm Incorporated Full configuration handover techniques

Families Citing this family (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4138457B1 (en) * 2016-08-10 2024-08-21 Nec Corporation Radio access network node, core network node, and methods therefor
CN114501561A (zh) * 2017-01-06 2022-05-13 荣耀终端有限公司 一种通信方法、接入网设备、核心网设备和用户设备
CN109561434B (zh) * 2017-09-26 2023-04-18 上海诺基亚贝尔股份有限公司 用于保证通信服务的方法、设备以及计算机可读介质
CN111279751A (zh) * 2017-11-09 2020-06-12 华为技术有限公司 用于获取切片支持信息的装置和方法
CN111093233B (zh) * 2018-10-24 2022-09-06 中国移动通信有限公司研究院 一种切换控制方法、装置及基站
CN111356248B (zh) * 2018-12-20 2022-05-13 大唐移动通信设备有限公司 一种接入网设备间建立连接的方法及装置
CN111436086B (zh) * 2019-01-15 2021-02-23 华为技术有限公司 安全保护方法及装置
EP3920587A4 (en) * 2019-02-03 2022-03-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD AND DEVICE FOR SERVICE PROCESSING, CHIP AND COMPUTER PROGRAM
CN111586772B (zh) * 2019-02-18 2021-06-22 华为技术有限公司 一种通信方法及装置
CN111726808B (zh) * 2019-03-21 2022-06-10 华为技术有限公司 通信方法和装置
CN114466383A (zh) * 2019-04-01 2022-05-10 华为技术有限公司 数据处理方法和信息处理装置
CN113261340B (zh) * 2019-04-01 2022-10-18 Oppo广东移动通信有限公司 传输信息的方法、终端设备、基站和核心网设备
CN112969244B (zh) * 2019-04-02 2022-06-07 荣耀终端有限公司 一种会话恢复方法及其装置
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置
CN112188544A (zh) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 一种基站间用户设备网络切片信息处理的方法和装置
CN112398891B (zh) * 2019-08-16 2023-04-18 华为技术有限公司 一种通信方法和装置
CN112449389B (zh) * 2019-09-05 2023-07-21 中国移动通信有限公司研究院 一种切换方法、源基站、目标基站及终端
CN114828101A (zh) * 2019-09-26 2022-07-29 华为技术有限公司 通信方法及装置
WO2021056449A1 (zh) * 2019-09-27 2021-04-01 华为技术有限公司 一种会话切换方法、装置及相关设备
US11711735B2 (en) * 2019-10-04 2023-07-25 Qualcomm Incorporated Carrier aggregation (CA) configuration during dual-active-protocol stack (DAPs) handover (HO)
CN112788704B (zh) * 2019-11-06 2022-05-10 华为技术有限公司 网络切片的使用控制方法、装置及系统
CN114902724A (zh) * 2019-12-31 2022-08-12 华为技术有限公司 通信方法及装置
CN113163457A (zh) * 2020-01-22 2021-07-23 北京三星通信技术研究有限公司 一种会话建立方法及切换方法和设备
US12114336B2 (en) * 2020-02-14 2024-10-08 Kt Corporation Methods for processing multicast/broadcast service data and apparatuses thereof
CN115088304B (zh) * 2020-03-19 2024-09-06 华为技术有限公司 小区切换方法和装置
US11516699B2 (en) * 2020-04-08 2022-11-29 Qualcomm Incorporated Processing mapped 5G system (5GS) quality of service (QoS) information in evolved packet system (EPS)
CN113645666A (zh) * 2020-04-27 2021-11-12 华为技术有限公司 流量控制方法、网络设备与通信系统
WO2021217672A1 (zh) * 2020-04-30 2021-11-04 华为技术有限公司 网络切片的负载控制方法及相关产品
WO2021226926A1 (en) * 2020-05-14 2021-11-18 Qualcomm Incorporated Methods and systems to restore pocket data network connectivity in non-standalone mode
CN115516914A (zh) * 2020-05-14 2022-12-23 Oppo广东移动通信有限公司 切换的方法和设备
CN113709764B (zh) * 2020-05-21 2023-06-27 华为技术有限公司 一种通信方法及装置
KR20210144205A (ko) * 2020-05-21 2021-11-30 삼성전자주식회사 네트워크 슬라이싱을 지원하는 무선 통신 시스템에서 세션 수립 방법 및 장치
CN113766581A (zh) * 2020-06-03 2021-12-07 华为技术有限公司 通信方法以及相关联的通信装置、介质和芯片
EP4162726A1 (en) * 2020-06-04 2023-04-12 Telefonaktiebolaget LM ERICSSON (PUBL) Next generation handover failure due to unsupported user equipment capabilities
CN113873581B (zh) * 2020-06-30 2024-04-09 华为技术有限公司 小区选择的方法和装置
CN113950111A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 一种会话切换方法及装置
WO2022016429A1 (zh) * 2020-07-22 2022-01-27 Oppo广东移动通信有限公司 切换方法、装置、设备及存储介质
CN116097749A (zh) * 2020-07-28 2023-05-09 联想(北京)有限公司 用于在ntn环境中处置cho执行条件的方法及设备
CN114071607A (zh) * 2020-08-06 2022-02-18 大唐移动通信设备有限公司 切片重映射方法、装置及存储介质
CN114079934A (zh) * 2020-08-12 2022-02-22 华为技术有限公司 一种中继通信方法及通信装置
US11218416B1 (en) 2020-08-18 2022-01-04 Verizon Patent And Licensing Inc. Service aware admission control for IoT applications
US11871285B2 (en) 2020-09-24 2024-01-09 Electronics And Telecommunications Research Institute Handover processing method based slice and device for performing the method
KR102616123B1 (ko) * 2020-09-24 2023-12-21 한국전자통신연구원 핸드오버 시 유틸리티 슬라이스 기반의 서비스 연속성 보장 방법
CN112492657B (zh) * 2020-12-15 2023-04-07 中国联合网络通信集团有限公司 网络切换方法及基站
US20240129818A1 (en) * 2021-01-12 2024-04-18 Ntt Docomo, Inc. Radio base station and terminal
CN114916024B (zh) * 2021-02-08 2024-05-14 中国电信股份有限公司 小区间切换方法、基站、pcf实体及系统
CN115134761A (zh) * 2021-03-29 2022-09-30 维沃移动通信有限公司 切换方法、装置、网络侧设备及终端
US11722419B1 (en) * 2021-04-01 2023-08-08 T-Mobile Usa, Inc. Bandwidth-dependent selection of a packet routing node
CN117296372A (zh) * 2021-05-21 2023-12-26 Oppo广东移动通信有限公司 一种终端设备间的业务切换的方法及装置
CN115551029A (zh) * 2021-06-29 2022-12-30 华为技术有限公司 网络切换方法、系统及相关设备
CN113473564B (zh) * 2021-07-23 2022-08-12 中国联合网络通信集团有限公司 网络切片切换的方法、建立pdu会话的方法及装置
CN114095986B (zh) * 2021-11-03 2024-02-13 中国联合网络通信集团有限公司 一种通信方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012155657A1 (zh) * 2011-07-27 2012-11-22 中兴通讯股份有限公司 一种ue切换到混合小区的方法、系统及基站
CN104105152A (zh) * 2013-04-03 2014-10-15 中国移动通信集团公司 一种业务迁移方法、网络侧设备及终端
CN106454943A (zh) * 2015-08-12 2017-02-22 北京三星通信技术研究有限公司 一种节点管理范围的控制方法与设备
CN106792931A (zh) * 2015-11-24 2017-05-31 展讯通信（上海）有限公司 Mtc终端小区重选控制方法及装置
CN106982410A (zh) * 2016-01-16 2017-07-25 华为技术有限公司 一种切换的方法、基站及终端设备

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100893860B1 (ko) * 2004-06-10 2009-04-20 엘지전자 주식회사 광대역 무선 접속 시스템에 적용되는 핸드오버 수행 방법및 핸드오버 실패시 통신 재개 방법
CN101193440A (zh) * 2006-12-01 2008-06-04 华为技术有限公司 在切换过程中确定分组数据转发方式的方法、系统及装置
EP2028890B1 (en) * 2007-08-12 2019-01-02 LG Electronics Inc. Handover method with link failure recovery, wireless device and base station for implementing such method
CN101674621B (zh) * 2008-09-08 2012-05-23 中国移动通信集团公司 一种移动切换方法、系统及装置
KR101690651B1 (ko) * 2010-02-25 2016-12-29 삼성전자주식회사 핸드오버 수행 방법 및 그 장치
CN102238658A (zh) * 2010-04-30 2011-11-09 北京三星通信技术研究有限公司 一种支持网关节点重选的方法
CN102256326B (zh) * 2010-05-19 2016-06-15 中兴通讯股份有限公司 一种实现路由选择的方法和装置
US8406160B2 (en) * 2010-05-21 2013-03-26 Qualcomm Incorporated Time-sliced search of radio access technologies during connected-mode radio link failure
CN102413494B (zh) 2010-09-21 2016-06-01 北京三星通信技术研究有限公司 一种检测无线链路失败或切换失败原因的方法
KR20140062484A (ko) * 2011-08-11 2014-05-23 인터디지탈 패튼 홀딩스, 인크 모바일 릴레이 핸드오버
US20130132286A1 (en) 2011-11-17 2013-05-23 General Motors Llc Method and systems for servicing a subscriber vehicle
CN104885524A (zh) * 2013-01-25 2015-09-02 富士通株式会社 基于上行信号的切换方法、上行信号的配置方法、用户设备以及基站
EP2981132A4 (en) * 2013-03-29 2016-10-12 Nec Corp COMMUNICATION DEVICE AND TRANSFER PROCESSING IN A RADIO COMMUNICATION SYSTEM
KR102143792B1 (ko) 2014-01-29 2020-08-12 삼성전자주식회사 단말의 이동성을 보장하면서 효율적으로 세션을 관리하기 위한 방법 및 장치
CN106465435A (zh) * 2014-03-21 2017-02-22 诺基亚通信公司 双连接重建
CN105451153B (zh) * 2014-07-28 2019-02-01 上海诺基亚贝尔股份有限公司 在通信系统中用于控制ProSe业务的方法及装置
CN104539596A (zh) * 2014-12-18 2015-04-22 华为技术有限公司 流媒体传输的方法、装置及系统
CN107409132B (zh) * 2015-03-10 2020-06-02 华为技术有限公司 软件定义网络控制信令动态配置流分割的方法和网络节点
WO2017007383A1 (en) * 2015-07-06 2017-01-12 Telefonaktiebolaget Lm Ericsson (Publ) Handover control in mobile communication system
JP7030681B2 (ja) 2015-07-16 2022-03-07 インテル コーポレイション デバイスプロファイルに基づいて構成されるネットワークアクセス
CN106375987B (zh) * 2015-07-22 2021-08-20 中兴通讯股份有限公司 一种网络切片的选择方法及系统
US10616820B2 (en) 2015-08-25 2020-04-07 Lg Electronics Inc. Base station connecting method and user equipment performing same
US9775045B2 (en) * 2015-09-11 2017-09-26 Intel IP Corporation Slicing architecture for wireless communication
KR101795787B1 (ko) * 2016-10-26 2017-11-08 에스케이 텔레콤주식회사 이동통신 시스템에서 코어 네트워크를 선택하는 방법 및 장치
CN106900015B (zh) * 2015-12-18 2021-02-12 中兴通讯股份有限公司 一种跨基站切换过程中重建立的处理方法和装置
WO2017113109A1 (en) * 2015-12-29 2017-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for virtualized network service provision
CN106937362B (zh) * 2015-12-31 2020-04-14 华为技术有限公司 网络切片管理装置和网络切片管理方法
US10893405B2 (en) * 2016-02-05 2021-01-12 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods performed therein for enabling communication in a communication network
US10708828B2 (en) * 2016-03-01 2020-07-07 Telefonaktiebolaget Lm Ericsson (Publ) Handover initiated alignment of pending interest tables
EP3437354B1 (en) * 2016-03-31 2022-03-23 NEC Corporation Sdn-based methods and apparatuses for providing tdd radio access network services
CN110401972B (zh) * 2016-04-08 2022-04-22 大唐移动通信设备有限公司 在多网络切片的网络中路由消息的方法、设备及系统
US10042665B2 (en) * 2016-06-13 2018-08-07 Verizon Patent And Licensing Inc. Customer premises equipment (CPE) with virtual machines for different service providers
CN108702810B (zh) * 2016-07-29 2021-09-14 Lg 电子株式会社 用于第一无线电接入网络节点的方法和装置
JP6658893B2 (ja) * 2016-08-10 2020-03-04 日本電気株式会社 無線アクセスネットワークノード、無線端末、コアネットワークノード、及びこれらの方法
US11323335B2 (en) * 2016-10-18 2022-05-03 Telefonaktiebolaget Lm Ericsson (Publ) SLA handling in network slices
CN106792936B (zh) * 2016-12-08 2020-04-03 上海华为技术有限公司 一种保持业务连续性的pgw切换方法及通信设备
US20200059989A1 (en) * 2017-08-16 2020-02-20 Lenovo (Singapore) Pte. Ltd. Indicating a packet data unit session as unavailable

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012155657A1 (zh) * 2011-07-27 2012-11-22 中兴通讯股份有限公司 一种ue切换到混合小区的方法、系统及基站
CN104105152A (zh) * 2013-04-03 2014-10-15 中国移动通信集团公司 一种业务迁移方法、网络侧设备及终端
CN106454943A (zh) * 2015-08-12 2017-02-22 北京三星通信技术研究有限公司 一种节点管理范围的控制方法与设备
CN106792931A (zh) * 2015-11-24 2017-05-31 展讯通信（上海）有限公司 Mtc终端小区重选控制方法及装置
CN106982410A (zh) * 2016-01-16 2017-07-25 华为技术有限公司 一种切换的方法、基站及终端设备

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3944716A4 (en) * 2019-04-03 2022-12-28 ZTE Corporation METHOD AND APPARATUS FOR SESSION PROCESSING, NETWORK DEVICE AND STORAGE MEDIUM
US12047457B2 (en) 2019-04-03 2024-07-23 Zte Corporation Session processing method and apparatus, network device and storage medium
WO2020200469A1 (en) * 2019-04-05 2020-10-08 Nokia Technologies Oy Methods for handling load variations in handover scenarios
US12069522B2 (en) 2019-04-05 2024-08-20 Nokia Technologies Oy Methods for handling load variations in handover scenarios
EP3996417A4 (en) * 2019-07-25 2022-08-31 Huawei Technologies Co., Ltd. DELIVERY METHOD AND DEVICE
EP4000311B1 (en) * 2019-08-23 2023-07-26 Qualcomm Incorporated Full configuration handover techniques

Also Published As

Publication number Publication date
EP3576458B1 (en) 2021-08-04
EP4007367B1 (en) 2024-06-12
JP2020517130A (ja) 2020-06-11
CN109041138A (zh) 2018-12-18
US11758441B2 (en) 2023-09-12
IL269926B2 (en) 2024-01-01
CN109168180A (zh) 2019-01-08
US20240040443A1 (en) 2024-02-01
US10952105B2 (en) 2021-03-16
CN109041138B (zh) 2019-08-13
EP3576458A1 (en) 2019-12-04
KR102498517B1 (ko) 2023-02-09
US20210282058A1 (en) 2021-09-09
KR20190117648A (ko) 2019-10-16
IL269926A (zh) 2019-11-28
RU2019132118A (ru) 2021-04-12
AU2018315286B2 (en) 2021-02-11
KR20210123434A (ko) 2021-10-13
EP4444025A2 (en) 2024-10-09
CN111491345B (zh) 2021-04-20
RU2019132118A3 (zh) 2021-11-26
US20190306761A1 (en) 2019-10-03
CN109168180B (zh) 2020-03-10
KR102311745B1 (ko) 2021-10-08
JP7031944B2 (ja) 2022-03-08
CN109392038A (zh) 2019-02-26
AU2018315286A1 (en) 2019-09-26
CN111491345A (zh) 2020-08-04
EP3576458A4 (en) 2020-07-22
IL269926B1 (en) 2023-09-01
EP4007367A1 (en) 2022-06-01
BR112019019985A2 (pt) 2020-04-28
CN109392038B (zh) 2022-09-09

Similar Documents

Publication Publication Date Title
US11758441B2 (en) Communication method, source base station, target base station, core network device, and terminal device
JP7401575B2 (ja) 通信方法、アクセスネットワークデバイス、およびコアネットワークデバイス
WO2019137471A1 (zh) 通信方法、接入网设备和终端设备
CN102598786B (zh) 基站间的切换方法、基站、和通讯系统
WO2019033796A1 (zh) 会话处理方法及相关设备
CN109474954B (zh) 一种会话建立方法及装置
WO2020216099A1 (zh) 通信方法及相关设备
RU2772653C2 (ru) Способ связи, исходная базовая станция, целевая базовая станция, устройство базовой сети и оконечное устройство
WO2021056449A1 (zh) 一种会话切换方法、装置及相关设备
CN116506866A (zh) 一种节点移动的机制和相应的节点
CN117676741A (zh) QoS信息的发送方法、接收方法、装置、设备及介质

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: 18842877

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019544921

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018842877

Country of ref document: EP

Effective date: 20190829

ENP Entry into the national phase

Ref document number: 20197026830

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018315286

Country of ref document: AU

Date of ref document: 20180810

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019019985

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112019019985

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190924