WO2019029643A1 - 通信方法、基站、终端设备和系统 - Google Patents

通信方法、基站、终端设备和系统 Download PDF

Info

Publication number
WO2019029643A1
WO2019029643A1 PCT/CN2018/099713 CN2018099713W WO2019029643A1 WO 2019029643 A1 WO2019029643 A1 WO 2019029643A1 CN 2018099713 W CN2018099713 W CN 2018099713W WO 2019029643 A1 WO2019029643 A1 WO 2019029643A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
information
qos flow
session
target base
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/099713
Other languages
English (en)
French (fr)
Inventor
韩锋
晋英豪
谭巍
李宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP18843499.7A priority Critical patent/EP3661253B1/en
Publication of WO2019029643A1 publication Critical patent/WO2019029643A1/zh
Priority to US16/786,532 priority patent/US11696202B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0044—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of quality context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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
    • 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/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength

Definitions

  • the present application relates to the field of communications and, more particularly, to communication methods, base stations, terminal devices and systems.
  • 5G will support various types of network deployments and application types. These include: higher speed experience and greater bandwidth access capabilities, such as enhanced mobile broadband (eMBB); access and management of larger, lower cost machine-like devices, such as large-scale machines Massive machine type communication (mMTC); lower latency and highly reliable information interaction, such as ultra reliable and low latency communication (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra reliable and low latency communication
  • QoS quality of service
  • the present application provides a communication method, a base station, a terminal device, and a system, which can improve communication efficiency in a handover process of a base station.
  • a communication method including: a source base station sending a handover request message to a target base station, where the handover request message is used to indicate that a first session of the terminal device is handed over from the source base station to the target base station
  • the handover request message includes first information, where the first information includes information of at least one quality of service QoS flow of the first session, the first session is a session corresponding to the terminal device;
  • the target base station receives a handover request response message, where the handover request response message includes second information, where the second information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session, the at least one QoS The flow includes the first QoS flow.
  • the second QoS flow is allowed to be received by the target base station by using the second information in the handover request response message, so that the source base station can
  • the content of the second information performs a handover process based on the QoS flow granularity, which improves the management efficiency and communication efficiency of the base station handover process.
  • the method further includes: the source base station receiving third information from the target base station, where the third information is used to indicate that the target base station refuses to accept the second QoS flow of the first session
  • the at least one QoS flow includes the second QoS flow.
  • the method further includes: the source base station receiving fourth information from the target base station, where the fourth information is used to indicate a reason why the second QoS flow is rejected.
  • the reason that the second QoS flow is rejected includes at least one of the following: insufficient resources, unsupported QoS flow information, unrecognized QoS flow information, and unrecognized QoS flow information.
  • the method further includes: the source base station sending, to the terminal device, fifth information, where the fifth information is used to indicate that the target base station is allowed to accept the first session of the first session. QoS flow.
  • the fifth information is used in a first RRC message, where the first RRC message is used to indicate that the terminal device is handed over from the source base station to the target base station.
  • the method further includes: the source base station receiving sixth information from the target base station, where the sixth information is used to indicate the first QoS flow and the second bearer of the first session
  • the second bearer is a bearer between the terminal device and the target base station; the source base station sends the sixth information to the terminal device.
  • the method further includes: the source base station sending, to the target base station, first data, where the first data is received by the source base station from a core network, corresponding to the first session.
  • the data of the first QoS flow is not limited to: the source base station sending, to the target base station, first data, where the first data is received by the source base station from a core network, corresponding to the first session. The data of the first QoS flow.
  • the source base station sends the first data to the target base station, where the source base station sends the first data to the target base station by using a session tunnel.
  • the method further includes: the source base station sends a first PDCP SDU to the target base station, where the first packet data convergence protocol (PDCP) service data unit (service data unit)
  • the SDU includes a PDCP SDU of the first bearer in the first session, the first bearer is a bearer between the terminal device and the source base station, and the source base station sends a seventh information to the target base station.
  • the seventh information is used to indicate that the first PDCP SDU belongs to an accepted QoS flow and/or a rejected QoS flow.
  • the method further includes: the source base station sending a second PDCP SDU to the target base station, where the second PDCP SDU includes the first base station of the first session by the source base station The PDCP SDU sent by the terminal device and not receiving the response, the second PDCP SDU corresponding to the first QoS flow in the first bearer.
  • the method further includes: the source base station sending eighth information to the terminal device, where the eighth information is used to indicate a sequence number of the second PDCP SDU.
  • a second aspect provides a communication method, including: receiving, by a target base station, a handover request message from a source base station, where the handover request message is used to indicate that a terminal device is handed over from the source base station to the target base station, the handover request The message includes first information, the first information includes information of at least one quality of service QoS flow of the first session, the first session is a session corresponding to the terminal device, and the target base station sends a handover to the source base station Requesting a response message, the handover request response message includes second information, the second information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session, and the at least one QoS flow includes the first A QoS flow.
  • the second QoS flow is allowed to be received by the target base station by using the second information in the handover request response message, so that the source base station can
  • the content of the second information performs a handover process based on the QoS flow granularity, which improves the management efficiency and communication efficiency of the base station handover process.
  • the target base station sends third information to the source base station, where the third information is used to indicate that the target base station refuses to accept the second QoS flow of the first session, At least one QoS flow includes the second QoS flow.
  • the target base station sends fourth information to the source base station, where the fourth information is used to indicate a reason why the second QoS flow is rejected.
  • the method further includes: the reason that the second QoS flow is rejected includes at least one of the following: insufficient resources, unsupported QoS flow information, unrecognized QoS flow information, and unrecognizable QoS flow information.
  • the method further includes: the target base station sending sixth information to the source base station, where the sixth information is used to indicate the first QoS flow and the second bearer of the first session
  • the mapping between the second bearer is a bearer between the terminal device and the target base station.
  • the method further includes: the target base station receiving first data from the source base station, where the first data is received by the source base station from a core network, corresponding to the first session The data of the first QoS flow.
  • the target base station receives the first data from the source base station, where the target base station receives the first data from the source base station by using a session tunnel.
  • the method further includes: the target base station receiving, by the source base station, a first PDCP SDU, where the first PDCP SDU is a PDCP SDU of a first bearer of the first session, where a bearer is a bearer between the terminal device and the source base station; the target base station receives seventh information from the source base station, and the seventh information is used to indicate that the first PDCP SDU belongs to an accepted QoS Stream and/or rejected QoS flows.
  • the method further includes: determining, by the target base station, a third PDCP SDU according to the seventh information, where the third PDCP SDU is corresponding to the first PDCP SDU a PDCP SDU of the switched QoS flow; the target base station transmits the third PDCP SDU to a higher layer, and/or the target base station transmits the third PDCP SDU to the terminal device.
  • the method further includes: the target base station receiving a second PDCP SDU from the source base station, where the second PDCP SDU includes the first base station of the first session by the source base station a PDCP SDU sent by the terminal device and not receiving a response, the second PDCP SDU corresponding to the first QoS flow in the first bearer, and the target base station sending the second PDCP SDU to the terminal device .
  • the method further includes: the target base station receiving a fourth PDCP SDU from the terminal device, where the fourth PDCP SDU includes the terminal device to the source by using the first bearer of the first session a PDCP SDU sent by the base station and not receiving a response, where the fourth PDCP SDU corresponds to the first QoS flow in the first bearer.
  • the method further includes: the target base station receiving, by the terminal device, ninth information, where the ninth information is used to indicate a sequence number of the fourth PDCP SDU;
  • the ninth information is that the fourth PDCP SDU is transmitted to a higher layer.
  • a third aspect provides a communication method, including: receiving, by a terminal device, a first radio resource control RRC message from a source base station, where the first RRC message is used to instruct the terminal device to switch from the source base station to the target
  • the base station the first RRC message includes fifth information, where the fifth information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session; and the terminal device sends the target eNB to the target base station.
  • a first RRC response message the first RRC response message being used to respond to the first RRC message.
  • the terminal device transmits the received QOS flow service according to the admission control result indicated by the fifth information, and maps to the bearer determined by the target base station, thereby avoiding transmitting the rejected data packet, thereby implementing Efficient and reliable inter-cell handover.
  • the method further includes: the terminal device receiving sixth information from the source base station, where the sixth information is used to indicate the first QoS flow and the second bearer of the first session
  • the mapping between the second bearer is a bearer between the terminal device and the target base station.
  • the method further includes: the terminal device receiving a second PDCP SDU from the target base station, where the second PDCP SDU includes the first base station of the first session by the source base station The PDCP SDU sent by the terminal device and not receiving the response, the second PDCP SDU corresponding to the first QoS flow in the first bearer.
  • the method further includes: the terminal device receiving eighth information from the source base station, where the eighth information is used to indicate a sequence number of the second PDCP SDU.
  • the method further includes: the terminal device transmitting the second PDCP SDU to a higher layer according to the eighth information.
  • the method further includes: the terminal device sends a fourth PDCP SDU to the target base station, where the fourth PDCP SDU includes the first bearer of the first session by the terminal device The PDCP SDU sent by the source base station and not receiving the response, the fourth PDCP SDU corresponding to the first QoS flow in the first bearer.
  • the method further includes: the terminal device sends ninth information to the target base station, where the ninth information is used to indicate a sequence number of the fourth PDCP SDU.
  • a base station for performing the method of any of the first aspect or the first aspect of the first aspect.
  • the base station comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a base station for performing the method in any of the possible implementations of the second aspect or the second aspect above.
  • the base station comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • a terminal device for performing the method in any of the possible implementations of the third aspect or the third aspect above.
  • the base station comprises means for performing the method of any of the possible implementations of the third aspect or the third aspect described above.
  • a communication system comprising the base station according to the fourth aspect, the fifth aspect, and the terminal device according to the sixth aspect.
  • a base station comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a base station comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a terminal device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the third aspect or the third aspect.
  • a communication method comprising the base station according to the eighth aspect, the ninth aspect, and the terminal device according to the tenth aspect.
  • a twelfth aspect a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • a thirteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the second aspect or any of the possible implementations of the second aspect.
  • a fourteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the third or third aspect of the third aspect.
  • FIG. 1 is a schematic diagram of a network architecture of an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a communication method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a format of a protocol data unit in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a base station handover procedure according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a communication method according to still another embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a base station according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a base station according to still another embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a base station according to still another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a base station according to still another embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal device according to another embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the terminal device in the embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or User device.
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the base station in the embodiment of the present application may be a device for communicating with a terminal device, where the base station may be a Global System of Mobile communication (GSM) system or Code Division Multiple Access (CDMA).
  • Base station (Base Transceiver Station, BTS), which may also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (Evolutional NodeB in an LTE system).
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • WCDMA Wideband Code Division Multiple Access
  • Evolutional NodeB evolved base station
  • the eNB or the eNodeB may also be a wireless controller in a cloud radio access network (CRAN) scenario, and the embodiment of the present application is not limited.
  • CRAN cloud radio access network
  • 5G will support various types of network deployments and application types. To meet the above requirements, 5G defines a framework based on quality of service (QoS) flows. It can support QoS flows that guarantee flow rates or QoS flows that do not guarantee flow rates.
  • QoS quality of service
  • FIG. 1 is a schematic diagram of a possible network architecture 100 of an embodiment of the present application.
  • Network architecture 100 is one possible implementation of a QoS flow architecture.
  • one terminal device can establish one or more sessions with a core network (CN).
  • the base station can map packets belonging to different sessions to different bearers, and map packets belonging to the same session to one or more bearers.
  • the QoS flow is the minimum granularity for realizing QoS differentiation in the above session.
  • each QoS flow may be assigned a corresponding QoS flow identifier (QFI), and one QFI may be used to indicate one QoS flow. Services with the same QFI in the same session will accept the same scheduling policy or admission control.
  • QFI QoS flow identifier
  • the QFI when the data packet is transmitted between the communication interface between the core network and the base station, the QFI may be carried on the encapsulation header of the data packet.
  • the communication interface between the core network and the base station may be an N3 interface, or the communication interface between the core network and the base station may also be referred to as a Next-generation user plane (NG- U) Tunnel.
  • NG- U Next-generation user plane
  • the foregoing session may be a packet data unit (PDU) session
  • the foregoing bearer may be a data resource bearer (DRB).
  • the foregoing PDU session may be a connection established between the terminal device and the data network, and the connection may be used to provide a PDU connection service, and the type of the connection may be an internet protocol (IP), an Ethernet, or other types.
  • IP internet protocol
  • Ethernet or other types.
  • the method or apparatus of the present application will be described by taking the above-mentioned session as a PDU session and the above-mentioned bearer as a DRB.
  • the foregoing core network may include a core network device, and the core network device may include, for example, a user plane function (UPF) entity, an access and Mobility Management function (AMF), and a session management function. (Session Management function, SMF).
  • UPF user plane function
  • AMF access and Mobility Management function
  • SMF Session Management function
  • 5G defines the packet processing mechanism on the air interface based on DRB. Packets served by one DRB have the same packet handling mechanism in air interface transmission.
  • the base station can establish multiple DRBs with the terminal device to satisfy QoS flows with different packet processing requirements. It should be noted that the same DRB may have a mapping relationship with one QoS flow, or may have a mapping relationship with multiple QoS flows.
  • the base station may map the downlink data packet corresponding to the QoS flow to the corresponding DRB based on the QFI identifier and the QoS rule corresponding to the QFI, and perform downlink transmission.
  • the terminal device maps the uplink data packet corresponding to the QoS flow to the corresponding DRB according to the mapping relationship between the QoS flow and the DRB configured by the base station, and performs uplink transmission.
  • the parameter of the QoS flow may also be referred to as a configuration parameter of the QoS flow.
  • each QoS flow includes at least the following parameters: a 5G QoS Identifier (5QI), an allocation and retention priority (ARP) parameter.
  • a 5G QoS Identifier 5QI
  • ARP allocation and retention priority
  • the ARP parameter can include at least one of the following information:
  • Priority level parameter used to determine whether the QoS flow can be accepted or rejected if the resource is limited.
  • the priority level parameter can be applied to the guaranteed rate bit (guaranteed).
  • Flow bit rate, GBR Flow bit rate, GBR
  • the pre-emption capability parameter a resource used to determine whether the QoS flow can preempt other low-priority QoS flows;
  • the pre-emption vulnerability parameter used to determine whether the QoS flow can be preempted by other high priority QoS flows.
  • the network architecture 100 may perform scheduling or management of data transmission based on a framework of QoS flows, or it may be said that the network architecture 100 may perform admission control management based on QoS flow granularity.
  • the above admission control management may refer to admission control performed by the target base station for the handover procedure.
  • the target base station may determine whether to accept the QoS flow that the source base station requests to handover. In the case of abundant resources, the newly added QoS flow does not affect the normal transmission of other QoS flows. In the case of resource constraints, based on the allocation and retention priority parameters, it is decided whether to accept the traffic transmission mapped to the newly added QoS flow.
  • the embodiment of the present application mainly focuses on how to implement the handover process based on the QoS flow granularity during the handover process of the base station.
  • FIG. 2 is a schematic diagram of a communication method 200 in accordance with an embodiment of the present application.
  • the method of FIG. 2 can be applied to the network architecture 100 of FIG.
  • method 200 can include steps 210-230, which are described in detail below.
  • the source base station sends a handover request message to the target base station, and accordingly, the target base station receives the handover request message from the source base station.
  • the handover request message is used to indicate that the terminal device is handed over from the source base station to the target base station, the handover request message includes first information, and the first information includes information of at least one QoS flow of the first session.
  • the first session is a session corresponding to the terminal device.
  • the foregoing switching the terminal device from the source base station to the target base station may refer to switching the session corresponding to the terminal device from the source base station to the target base station.
  • the first session described above may be a session established between the terminal device and the core network.
  • the first session may be initiated or established by the terminal device, or may be initiated and established by the core network, which is not limited in this embodiment of the present application.
  • the above session can be a PDU session.
  • the foregoing PDU session may be a connection established between the terminal device and the data network, and the connection may be used to provide a PDU connection service, and the type of the connection may be an internet protocol (IP), an Ethernet, or other types.
  • IP internet protocol
  • Ethernet or other types.
  • At least one session can be established between the terminal device and the core network.
  • Each of the at least one session may correspond to at least one bearer, and the bearer may be a bearer established between the terminal device and the base station.
  • the bearer may be a bearer between the terminal device and the source base station; after the terminal device switches from the source base station to the target base station, the bearer may be the terminal device and the target base station. Carrying between.
  • Each of the at least one bearer may have a mapping relationship with at least one QoS flow. In other words, the same bearer can transmit data packets corresponding to one or more QoS flows.
  • the above bearer may be a DRB.
  • the information of the at least one QoS flow of the first session may refer to information of all QoS flows or partial QoS flows in the first session.
  • the information of the at least one QoS flow may include a mapping relationship between the at least one QoS flow and a bearer and/or a parameter of the at least one QoS flow.
  • the first information may indicate one or more bearers included in the first session, and the QoS flows included in each of the multiple one or more bearers.
  • the first information may indicate a parameter of the QoS flow in the first session and a bearer to which the QoS flow is mapped.
  • Table 1 shows a possible implementation form of the first information.
  • PDU sessions list >PDU Session ID (PDU Session ID) >QoS flow list >>>>QFI >>>>QoS flow parameters >RRC context information
  • the format of the first information is not limited in the embodiment of the present application.
  • the first information may be an information element (IE), or may be an indicator.
  • the first information may include an identifier of a PDU session corresponding to the terminal device, and a list of QoS flows included in the PDU session.
  • the list of QoS flows can be represented by QFI.
  • the first information may further include parameters of the QoS flow and RRC context information.
  • Table 2 shows the content included in the parameters of the QoS flow.
  • the parameters of the QOS flow include at least one of the following: 5QI, Allocation and Retention Priority, GBR QoS flow information, and Notification Control.
  • Table 3 shows the content included in the RRC context information.
  • the RRC context information includes a QoS flow and DRB mapping relationship and a configuration parameter of the DRB.
  • the source base station carries information of the at least one QoS flow of the first session in the handover request message, and the purpose is to enable the target base station to perform admission control according to the first information.
  • the target base station performs admission control according to the first information.
  • the above admission control may refer to admission control performed by the target base station for the handover procedure.
  • the target base station may determine whether to accept the source base station to request to switch the QoS flow.
  • the newly added QoS flow does not affect the normal transmission of other QoS flows.
  • resource constraints based on the allocation and retention priority parameters, it is decided whether to accept the traffic transmission mapped to the newly added QoS flow.
  • the above admission control may refer to the target base station determining whether to receive some or all of the QoS flows in the first session according to the current network state and other reference factors.
  • the target base station may determine to receive all or part of the QoS flows in the first session according to the information of the at least one QoS flow included in the first information, or determine to reject all or part of the QoS flows in the first session.
  • the admission control may be based on an ARP parameter of the at least one QoS flow included in the first information. For example, in the case of limited resources, some or all of the QOS flows may be rejected based on the ARP of each QOS flow, and the reason for rejecting the QOS flow is sent to the source base station.
  • the specific process of the admission control of the target base station according to the first information refer to the description in step 230.
  • the terminal device may further perform cell measurement and send a cell measurement report to the source base station.
  • the source base station may determine to send the handover request message to the target base station according to the cell measurement report.
  • the source base station receives a handover request response message from the target base station, where the handover request response message includes second information, where the second information is used to indicate that the target base station is allowed to accept the first session.
  • the first QoS flow the at least one QoS flow including the first QoS flow.
  • the target base station may determine to receive all or part of the QoS flows in the first session according to the first information included in the handover request message. For example, the target base station can perform admission control according to the parameters of the QoS flow and the current load status.
  • the parameters of the above QoS flow may include, for example, ARP parameters.
  • the target base station may send a handover request response message to the source base station according to the result of the admission control, and carry the second information in the handover request response message to indicate that the target base station is allowed to accept the first QoS in the first session. flow.
  • the first QoS flow may be part or all of the QoS flows in the at least one QoS flow.
  • the second QoS flow is allowed to be received by the target base station by using the second information in the handover request response message, so that the source base station can
  • the content of the second information performs a handover process based on the QoS flow granularity, which improves the management efficiency and communication efficiency of the base station handover process.
  • the second information may indicate that the first QoS flow is accepted by the target base station in an explicit and/or implicit manner.
  • the second information can include an identification of the first QoS flow.
  • the identifier of the first QoS flow may be QFI.
  • the source base station can determine which QoS flows in the first session are accepted and which QoS flows are rejected according to the QFI included in the second information.
  • the second information may include an identification of the rejected QoS flow in the first session.
  • the second information above may include the QFI of the rejected QoS flow.
  • the source base station may exclude the rejected QoS flow from the QoS flow in the first session based on the QFI included in the second information, thereby determining the accepted first QoS flow.
  • Table 4 shows a possible implementation of the second information, where the format of the second information is not limited in the embodiment of the present application.
  • the second information may be an IE or an indicator.
  • the second information may include an identifier of the PDU session and a list of QoS flows accepted in the PDU session.
  • the list of QoS flows may include the QFI of the QoS flow.
  • the source base station may further receive third information from the target base station, where the third information is used to indicate that the target base station refuses to receive the second QoS flow of the first session,
  • the at least one QoS flow includes the second QoS flow.
  • Table 5 shows an implementation form of the second information and/or the third information.
  • Table 3 may be a possible implementation manner in which the second information includes both explicit and implicit, or Table 5 may also be a possibility that the handover request response message includes both the second information and the third information. The way to achieve it.
  • the format of the second information or the third information is not limited in the embodiment of the present application.
  • the second information or the third information may be an IE or an indicator.
  • the second information and/or the third information may include an identifier of the accepted PDU session, a list of accepted QoS flows in the PDU session, and a list of rejected QoS flows in the PDU session, specifically
  • the list of QoS flows may include the QFI of the QoS flow.
  • Table 6 shows one possible implementation of the second or third information when the entire PDU session is rejected.
  • Table 4 shows one possible implementation in which the second information is implicit, or Table 6 shows one possible implementation of the third information.
  • the second information or the third information may include a list of rejected PDU sessions, wherein the list of rejected PDU sessions may be represented by an identification of the PDU session.
  • the process of the terminal device switching from the source base station to the target base station there may be various situations as follows.
  • all QoS flows in the first session are rejected by the target base station, or all QoS flows in the first session are accepted, ie the entire first session is rejected or accepted by the target base station.
  • all QoS flows in the same bearer in the first session are rejected by the target base station, or all QoS flows in the same bearer in the first session are accepted by the target base station.
  • part of the QoS flows in the same bearer in the first session are rejected by the target base station, or part of the QoS flows in the same bearer in the first session are accepted by the target base station.
  • the source base station may further receive fourth information from the target base station, where the fourth information is used to indicate a reason why the second QoS flow is rejected.
  • the third information and the fourth information may be carried in the handover response message in step 230, or the third information and the fourth information may be separately sent from the handover response message.
  • the reason that the foregoing second QoS flow is rejected includes at least one of the following: no resource available, unsupported QoS flow information (Not supported), unrecognized QoS flow information (invalid QoS parameter), no Supported QFI (not supported QFI).
  • the insufficient resource may be used to indicate that the target base station does not support the rejected QoS flow.
  • the unrecognized QoS flow information may indicate that the target base station cannot identify the rejected QoS flow.
  • the information that is not supported above may mean that the target base station does not support the QFI.
  • the reason that the foregoing second QoS flow is rejected may further include other factors, and the embodiments of the present application are not enumerated one by one.
  • a transmission control method based on QoS flow granularity is proposed, so that a smaller granularity of service quality management can be realized in the handover process of the base station, and the communication efficiency is improved.
  • the method 200 further includes step 240 and step 250.
  • the terminal device receives a first radio resource control (RRC) message from the source base station, where the first RRC message is used to instruct the terminal device to switch from the source base station to the target.
  • RRC radio resource control
  • the base station, the first RRC message includes fifth information, where the fifth information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session.
  • the fifth information may also not be carried in the first RRC message but separately sent from the first RRC message.
  • the terminal device transmits the received QOS flow service according to the admission control result indicated by the fifth information, and maps to the bearer determined by the target base station, thereby avoiding transmitting the rejected data packet, thereby implementing Efficient and reliable inter-cell handover.
  • the first RRC message may be an RRC connection reconfiguration message.
  • the foregoing first RRC message may include indication information, where the indication information is used to indicate that the second bearer of the first session is established between the terminal device and the target base station, and is used between the terminal device and the target base station. transfer data.
  • the QoS flow carried by the second bearer includes the first QoS flow.
  • the method 200 further includes: the source base station receiving sixth information from the target base station, where the sixth information is used to indicate the first QoS flow and the second bearer of the first session
  • the mapping between the second bearer is a bearer between the terminal device and the target base station.
  • the source base station may send the sixth information to the terminal device.
  • the source base station is equivalent to transparently transmitting the sixth information.
  • the sixth information is actually information transmitted by the target base station to the terminal device.
  • the target base station may send a sixth information to the source base station by using a transparent container, and then forwarded by the source base station to the terminal device.
  • the terminal device may establish a second bearer with the target base station according to the sixth information.
  • the sixth information may be carried in the handover request response message in S230.
  • the sixth information described above may be sent in the form of an accepted QoS list.
  • the foregoing sixth information may be carried in the first RRC message in S240.
  • Table 7 shows a possible implementation form of the sixth information.
  • the format of the sixth information is not limited in the embodiment of the present application.
  • the sixth information described above may be an information element (IE), or may be an indicator.
  • the sixth information may include an identifier of the PDU session and a list of identifiers of the DRBs included in the PDU session.
  • the sixth information further includes a list of QoS flows included in each DRB.
  • the list of QoS flows can be represented by QFI.
  • the sixth information may also include configuration parameters of the DRB.
  • the configuration parameters of the DRB include at least one of the following: physical (physical, PHY) layer configuration parameters, media access control (MAC) layer configuration parameters, radio link control (RLC) layer configuration parameters, and PDCP. Layer configuration parameters and SDAP layer configuration parameters.
  • step 250 the target base station receives a first RRC response message from the terminal device, and the first RRC response message is used to respond to the first RRC message.
  • the first RRC message when the first RRC message is an RRC connection reconfiguration message, the first RRC message may be an RRC connection reconfiguration response message.
  • the terminal device may establish the second bearer with the target base station, and after the establishment is completed, to the target The base station sends the first RRC response message.
  • the first RRC response message may be sent to the target eNB, and the cause of the bearer setup failure is carried in the first RRC response message.
  • the terminal device receives the first RRC message sent by the source base station, where the fifth information included in the first RRC message is used to indicate that the target base station is allowed to accept the first QoS of the first session.
  • the flow so that the terminal device can perform the handover process based on the QoS granularity according to the indication of the fifth information, and improve the communication efficiency in the handover process of the base station.
  • the signaling flow in the process of base station handover is mainly described above, and the process of data forwarding in base station handover will be described next.
  • the source base station or the terminal device side will have a large number of data packets that have not received the response, or the source base station will buffer the data received from the core network and not sent to the terminal device. Therefore, how to ensure lossless handover in the handover scenario is an important issue that the industry needs to solve.
  • the data packet may include a packet data convergence protocol (PDCP) service data unit (SDU).
  • PDCP packet data convergence protocol
  • SDU packet data convergence protocol
  • the foregoing PDCP SDU may be a data packet transmitted by the base station and the terminal device at the PDCP layer.
  • the PDCP layer described above belongs to a sublayer in the data link layer of the wireless access protocol architecture.
  • the above data link layer may also be referred to as layer two.
  • the lower layer sub-protocol of the PDCP layer includes a radio link control layer.
  • the upper layer protocol of the PDCP layer is the RRC layer.
  • a new protocol layer is added between the PDCP layer and the RRC layer, where the protocol layer is a Service Data Adaptation Protocol (SDAP).
  • SDAP Service Data Adaptation Protocol
  • the above SDAP layer functions include, but are not limited to, a mapping for processing QoS flows to the DRB, and for adding a QoS flow ID in the header of the data packet.
  • step 230 in the process of the terminal device switching from the source base station to the target base station, there may be various situations as follows.
  • all QoS flows in the first session are rejected by the target base station, or all QoS flows in the first session are accepted, ie the entire first session is rejected or accepted by the target base station.
  • all QoS flows in the same bearer in the first session are rejected by the target base station, or all QoS flows in the same bearer in the first session are accepted by the target base station.
  • part of the QoS flows in the same bearer in the first session are rejected by the target base station, or part of the QoS flows in the same bearer in the first session are accepted by the target base station.
  • the granularity of data switching between base stations may be based on bearer granularity, and one or more QoS flows may be mapped on the same bearer for data transmission.
  • data switching can be performed between the base stations in the usual manner.
  • the third case since some of the QoS flows in the same bearer are not accepted by the target base station, if data packets corresponding to the unaccepted QoS flows are transmitted, resource waste is caused.
  • the source base station can perform data transfer with the target base station for the entire first session.
  • the data transfer corresponding to the bearer may not be performed between the source base station and the target base station;
  • the embodiment of the present application proposes a plurality of data switching schemes.
  • the scheme of data switching in the present application will be described below in conjunction with both uplink data transmission (UL) and downlink data transmission (DL).
  • the source base station mainly caches two types of data.
  • the first type of data is a new packet received from the core network that has not yet been sent to the terminal.
  • the source base station will continue to receive and buffer the above data packets before receiving the end marker sent by the core network.
  • the second type of data is a data packet that the source base station is transmitting to the terminal device through the first bearer of the first session and has not received the response.
  • the above data packet may be a PDCP SDU, which is being transmitted at the PDCP layer.
  • the above-mentioned data packet that has not received the response may refer to an acknowledgement or response that the PDCP SDU does not receive the RLC layer of the base station.
  • the source base station also caches a third type of data.
  • the third type of data is an out-of-order packet received by the source base station from the terminal device. That is, the serial number of the above data packet is non-contiguous. Because the source base station needs to deliver data packets to the higher layers in order. Therefore, for a data packet whose serial number is not continuous, the source base station needs to temporarily buffer the data packet, and after receiving the remaining data packet, submit it to the upper layer in order.
  • the foregoing data packet may refer to a PDCP SDU, and the upper layer may refer to a protocol layer above the PDCP layer.
  • the above higher layer may be an SDAP layer or an RRC layer.
  • the terminal device further caches a fourth type of data, and the fourth type of data is that the terminal device is transmitting to the source base station through the first bearer of the first session.
  • the above data packet may be a PDCP SDU, which is being transmitted at the PDCP layer.
  • the above-mentioned data packet that has not received the response may indicate that the PDCP SDU has not received the confirmation or response of the RLC layer of the terminal device.
  • the source base station does not transmit the first type of data to the target base station, if the first type of data The corresponding QoS flow is accepted, and the source base station transmits the first type of data to the target base station.
  • the first type of data mentioned above may be the first data in the following.
  • the method 200 further includes: the source base station transmitting first data to the target base station, where the first data is received by the source base station from a core network, corresponding to the first session The data of the first QoS flow.
  • the source base station may transmit the first data to the target base station by using two schemes.
  • the source base station transmits the first data to the target base station at the PDCP layer by using the data packet corresponding to the first QoS flow.
  • the source base station does not continue to serve the data packet corresponding to the first QoS flow, but sends the first data to the target base station through the session tunnel.
  • the session tunnel may be a session-based granular tunnel.
  • the packet format of the session tunnel and the packet format transmitted by the core network to the source base station can be the same. Therefore, after obtaining the first data from the core network, the source base station may send the frame header or the extended frame header update to the target base station directly at the SDAP layer, thereby saving resources for processing the first data and improving communication efficiency.
  • the first data sent by the core network to the terminal device is forwarded by the session tunnel between the source base station and the target base station, and the first data is not required to be transmitted in the PDCP layer, thereby saving time and occupation for processing the first data. Resources to improve communication efficiency.
  • the format of the foregoing session tunnel may include: a General Packet Radio Service Tunneling Protocol (GTP) header, an extension header, and an internet protocol packet (IP packet).
  • GTP General Packet Radio Service Tunneling Protocol
  • IP packet internet protocol packet
  • a QFI identifier and/or a reflective QoS indication (RQI) identifier may be added in the GTP extension header.
  • RQI reflective QoS indication
  • Extended header identifier Extended header type 1100 0100 RQI 1100 0011 QFI ... ...
  • the source base station can transmit the second and/or third type of data to the target base station in two ways for the second type of data of the DL and the third type of data of the UL.
  • the source base station may transmit the second and/or third type of data to the target base station based on the bearer granularity. In other words, the source base station transmits, to the target base station, a data packet corresponding to all QoS flows in one bearer.
  • the source base station can transmit the second and/or third type of data to the target base station based on the QoS flow granularity. In other words, the source base station transmits the data packet corresponding to the accepted first QoS flow to the target base station.
  • the first mode and the second mode are applicable to the three scenarios in which the source base station switches to the target base station.
  • the method 200 further includes: the source base station sending a first PDCP SDU to the target base station, the first PDCP SDU And including a PDCP SDU of the first bearer of the first session, where the first bearer is a bearer between the terminal device and the source base station.
  • the first PDCP SDU may include the second type of data in the DL or the third type of data in the UL.
  • the foregoing first PDCP SDU may include a PDCP SDU sent by the source base station to the terminal device by using the first bearer of the first session, and not receiving the response, and/or, for the UL process, the first PDCP SDU is further And including an out-of-order PDCP SDU received by the source base station from the terminal device by using the first bearer of the first session.
  • the above accepted QoS flow may refer to the foregoing first QoS flow
  • the rejected QoS flow may refer to the second QoS flow.
  • the foregoing second QoS flow may refer to a QoS flow in the first bearer that is not accepted by the target base station.
  • the QoS flow corresponding to the first PDCP SDU may include all QoS flows corresponding to the first bearer.
  • the foregoing first PDCP SDU may include a PDCP SDU corresponding to the first QoS flow and the second QoS flow.
  • the source base station does not distinguish the first PDCP SDU included in the first bearer according to the first QoS flow and the second QoS flow, but transmits all PDCP SDUs included in the first bearer to the target base station.
  • the target base station can distinguish which PDCP SDU corresponds to which QoS flow.
  • the extension header of the PDCP SDU may include an identifier of its corresponding QoS flow.
  • the target base station may read the identity of the QoS flow from the extended header of the PDCP SDU to determine whether the first PDCP SDU corresponds to the accepted QoS flow or the rejected QoS flow.
  • a third PDCP SDU is then determined from the first PDCP SDU, the third PDCPSDU being a PDCP SDU corresponding to the switched QoS flow in the first PDCP SDU.
  • the target base station cannot autonomously resolve the QoS flow corresponding to the PDCP SDU. Therefore, in this case, the method 200 further includes: the source base station transmitting seventh information to the target base station, where the seventh information is used to indicate that the first PDCP SDU belongs to an accepted QoS flow and/or Rejected QoS flow.
  • the above accepted QoS flows and/or rejected QoS flows may also be described as switched QoS flows and/or unswitched QoS flows.
  • the seventh information may include a serial number (SN) of the accepted QoS flow or a sequence number of the rejected QoS flow.
  • the foregoing seventh information may be carried in a sequence number state transmission and a sequence number attribution status (SN status transfer & SN accept status) message.
  • the SN status transfer & SN accept status message may be transmitted between the communication interface between the source base station and the target base station.
  • the communication interface described above can be an Xn interface.
  • the SN status transfer & SN accept status message may be used to indicate the serial number (SN) of the accepted QoS flow or the sequence number of the rejected QoS flow.
  • the foregoing seventh information may be carried in other types of messages, which is not limited in this embodiment of the present application.
  • the method 200 further includes: the target base station determining, according to the seventh information, a third PDCP SDU, where the third PDCP SDU is a PDCP SDU corresponding to the switched QoS flow in the first PDCP SDU; the target base station transmitting the third PDCP SDU to a higher layer, and/or the target base station transmitting the third PDCP SDU to the terminal device.
  • the above-mentioned switched QoS flow may refer to a QoS flow that is switched to the target base station.
  • the above-described switched QoS flow may refer to a first QoS flow.
  • the foregoing third PDCP SDU may be determined according to the seventh information.
  • the target base station may also independently identify its corresponding QoS flow according to the QFI included in the extended header of the first PDCP SDU according to the seventh information, and further determine the third PDCP SDU from the first PDCP SDU. .
  • the first PDCP SDU includes at least one of two types of data.
  • the above two kinds of data are used for UL and DL, respectively.
  • the foregoing first PDCP SDU may include a PDCP SDU sent by the source base station to the terminal device by using the first bearer of the first session, and not receiving the response, and/or, for the UL process, the first PDCP SDU Also included is an out-of-order PDCP SDU received by the source base station from the terminal device through the first bearer of the first session.
  • the third PDCP SDU may also include at least one of the above two types of data.
  • the target base station may send the PDCP SDU for the DL in the third PDCP SDU to the terminal device by using the second bearer.
  • the data for the UL in the third PDCP SDU can then be transmitted to the upper layer.
  • the above higher layer may refer to a protocol layer above the PDCP layer of the base station.
  • the above higher layer may be an SDAP layer or an RRC layer.
  • the method 200 further includes: the target base station receiving a second PDCP SDU from the source base station, where the second PDCP SDU includes the source base station passing the first bearer in the first session
  • the PDCP SDU sent by the terminal device and not receiving the response, and/or the second PDCP SDU includes the out-of-order sequence received by the source base station from the terminal device by using the first bearer of the first session a PDCP SDU, the second PDCP SDU corresponding to a first QoS flow in the first bearer.
  • the source base station after the QoS flow is rejected by the target base station, the source base station does not forward the data corresponding to the rejected QoS flow to the target base station, and only forwards the data corresponding to the accepted QoS flow, thereby saving the base station.
  • the method 200 further includes: the target base station transmitting the second PDCP SDU to the terminal device, and/or the target base station transmitting the second PDCP SDU to a higher layer.
  • the target base station and the terminal device do not transmit data corresponding to the rejected QoS flow during the base station handover process, and only transmit data corresponding to the accepted QoS flow. Therefore, the air interface resource overhead is saved, so that the saved resources can be used for other data transmission, and the efficiency of the system spectrum is improved.
  • the second PDCP SDU includes at least one of two types of data.
  • the above two kinds of data are used for UL and DL, respectively.
  • the foregoing second PDCP SDU may include a PDCP SDU sent by the source base station to the terminal device through the first bearer of the first session, and not receiving the response, and/or, for the UL process, the second PDCP SDU is further And including an out-of-order PDCP SDU received by the source base station from the terminal device by using the first bearer of the first session.
  • the target base station may send the PDCP SDU for the DL in the second PDCP SDU to the terminal device by using the second bearer.
  • the data for the UL in the second PDCP SDU can then be transmitted to the higher layer.
  • the above higher layer may refer to a protocol layer above the PDCP layer of the base station.
  • the above higher layer may be an SDAP layer or an RRC layer.
  • the method 200 further includes: the source base station transmitting eighth information to the terminal device, the eighth information being used to indicate a sequence number of the second PDCP SDU.
  • the first QoS flow that is switched and the second QoS flow that is not switched are included in the first bearer between the terminal device and the source base station.
  • the PDCP SDU sequence number in the first bearer includes the sequence number of the PDCP SDU corresponding to the first QoS flow and the second QoS flow, which may be cross-ordered.
  • the sequence number of the second PDCP SDU may be discontinuous.
  • the terminal device or the base station needs to deliver the PDCP SDU to the upper layer in sequence according to the sequence number.
  • the data corresponding to the second QoS flow is not transmitted between the terminal device and the target base station.
  • the terminal device can identify the second PDCP SDU, so that even if the second PDCP SDU sequence number is discontinuous, the terminal device can transmit the second PDCP SDU to the upper layer without waiting for the second QoS flow. Corresponding data, thereby improving communication efficiency and improving the flexibility of transmission management during handover of the base station.
  • the terminal device also has a fourth type of data, which is a data packet that the terminal device is transmitting to the source base station and has not received a response. .
  • the method further includes: the target base station receiving, by the terminal device, a fourth PDCP SDU, where the fourth PDCP SDU includes, by the terminal device, the first bearer of the first session, sent to the source base station, The PDCP SDU of the response is not received, and the fourth PDCP SDU corresponds to the first QoS flow in the first bearer.
  • the terminal device determines the first QoS flow accepted by the target base station. Further, the terminal device may not send the PDCP SDU corresponding to the second QoS flow that is not accepted to the target base station, but send the fourth PDCP SDU corresponding to the accepted first QoS flow to the target base station.
  • the terminal device does not need to send the PDCP SDU corresponding to the unaccepted QoS flow to the target base station, and only needs to send the PDCP SDU corresponding to the accepted first QoS flow to the target base station, thereby
  • the air interface resources are saved, and the saved resources can be used for other data transmission, thereby improving the system spectrum efficiency.
  • the method 200 further includes: the target base station receiving ninth information from the terminal device, the ninth information being used to indicate a sequence number of the fourth PDCP SDU;
  • the ninth information is that the fourth PDCP SDU is transmitted to a higher layer.
  • the fourth PDCP SDU is a PDCP SDU corresponding to the first QoS flow.
  • the sequence number of the fourth PDCP SDU may be discontinuous.
  • the terminal device or the base station needs to deliver the PDCP SDU to the upper layer in sequence according to the sequence number.
  • the data corresponding to the second QoS flow is not transmitted between the terminal device and the target base station. Therefore, after receiving the ninth information, the target base station can identify the fourth PDCP SDU, so that even if the fourth PDCP SDU sequence number is discontinuous, the target base station can transmit the fourth PDCP SDU to the upper layer without waiting for the second QoS flow.
  • Corresponding PDCP SDU which improves communication efficiency and improves the flexibility of transmission management during base station handover.
  • the terminal device sends the ninth information to the target base station to indicate the sequence number of the fourth PDCP SDU, so that the target base station can also identify the fourth PDCP SDU corresponding to the accepted QoS flow, so that there is no waiting for other The PDCP SDU does not need to submit the fourth PDCP SDU in order.
  • the communication efficiency is improved, and the flexibility of transmission management in the handover process of the base station is improved.
  • FIG. 3 shows a protocol data unit (PDU) format of a PDCP layer in the embodiment of the present application.
  • the PDU can be transmitted between the base station and the terminal device as a control PDU.
  • a PDU type can be used to indicate the type of content indicated by the PDU.
  • the PDU type when the PDU type is set to 100, it may be referred to as the serial number of the PDCP SDU.
  • the PDU can be used to indicate other types of information.
  • Table 6 shows the content type indicated by the PDU when the PDU type is other values. It should be noted that the assignment of the PDU type in Table 6 is only a specific example. Those skilled in the art can understand that the content indicated by the assignment of the PDU type can be defined according to the actual situation, and is not necessarily limited to the example of the present application. Similarly, the manner of the above assignment is also applicable to similar situations in other embodiments of the present application.
  • the first non-transmitted sequence number (FNSS) in FIG. 3 may refer to the sequence number of the first PDCP SDU in the PDCP SDU that is not transmitted.
  • the above-mentioned non-transmitted PDCP SDU may refer to a PDCP SDU corresponding to the rejected QoS flow.
  • the foregoing FNSS may also be replaced by a first transmitted sequence number (first sending SN, FSS), where the FSS may refer to a sequence number of a first PDCP SDU in the transmitted PDCP SDU.
  • the PDCP SDU sent above may refer to a PDCP SDU corresponding to the accepted QoS flow.
  • the D/C in FIG. 3 can be used for the application type of the indication PDU. For example, when D/C is set to 0, the PDU can be represented as a PDU for control. When D/C is set to 1, it can be indicated that the PDU is a PDU for data.
  • FIG. 3 further includes a bitmap, and the bitmap may cooperate with the FNSS or the FSS to indicate whether the PDCP SDU corresponding to the FNSS or the FSS is the transmitted PDCP SDU or the non-transmitted PDCP SDU.
  • the bitmap may cooperate with the FNSS or the FSS to indicate whether the PDCP SDU corresponding to the FNSS or the FSS is the transmitted PDCP SDU or the non-transmitted PDCP SDU.
  • the bitmap when the value of the bitmap is 1, it can be the transmitted PDCP SDU.
  • the bitmap is set to 0, it can be a PDCP SDU that is not sent.
  • Figure 4 illustrates a signaling interaction procedure for base station handover via a core network.
  • the core network device in FIG. 4 may be, for example, an AMF.
  • information is not directly transmitted between the source base station and the target base station, but information is exchanged through the core network device.
  • the same or similar contents as in FIG. 2 in the example of FIG. 4 are not described herein again.
  • the method of Figure 4 includes:
  • the source base station sends a handover requirement message to the core network device.
  • the core network device sends a handover request message to the target base station according to the handover requirement message.
  • the target base station After receiving the handover request response message, the target base station performs admission control, and sends a handover request response message to the core network device.
  • step S220 of FIG. 2 Regard the content of the admission control, reference may be made to step S220 of FIG. 2.
  • the core network device sends a handover request response message to the source base station.
  • the terminal device performs a handover process.
  • FIG. 5 is a schematic diagram of a communication method 500 of an embodiment of the present application.
  • FIG. 5 shows a specific flow of base station handover.
  • the method of FIG. 5 includes:
  • the terminal device reports the measurement result to the source base station.
  • the source base station determines to switch the terminal device to the target base station.
  • the source base station decides to switch the terminal device to a target base station.
  • the source base station sends a handover request message to the target base station, where the handover request message may include a QOS flow message of the session corresponding to the terminal device.
  • the handover request message may include a QOS flow message of the session corresponding to the terminal device.
  • the target base station performs admission control of QoS flow granularity.
  • step S220 of FIG. 2 Regard the content of the admission control, reference may be made to step S220 of FIG. 2.
  • the target base station sends a handover response message to the source base station.
  • the source base station sends an RRC reconfiguration message to the terminal device, where the admission control result is included.
  • the first RRC message in FIG. 2 may be the foregoing RRC reconfiguration message.
  • the RRC reconfiguration message reference may be made to the related description of step S230 of FIG. 2.
  • the foregoing RRC reconfiguration message may include the received QoS flows->DRB mapping and sent to the terminal device.
  • the source base station sends the SN status transfer and the SN home status message to the target base station, and starts the data forwarding process.
  • S508 terminal device synchronizes to the target base station, thereby finally ending the handover process
  • the target base station may send the PDCP Control PDU in FIG. 3 to the terminal device to inform the SN status.
  • the terminal device can transmit the PDCP control PDU of FIG. 3 to the target base station to inform the SN status.
  • the communication method of the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 5.
  • the base station and the terminal device of the embodiment of the present application are described in detail below with reference to FIG.
  • FIG. 6 is a schematic block diagram of a base station 600 according to an embodiment of the present application. It should be understood that the base station 600 can perform the various steps performed by the source base station in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the base station 600 includes: a processing unit 601 and a communication unit 602,
  • the processing unit 601 is configured to send, by using the communication unit 602, a handover request message to the target base station, where the handover request message is used to indicate that the first session of the terminal device is switched from the source base station to the target base station, where
  • the handover request message includes first information, where the first information includes information of at least one quality of service QoS flow of the first session, the first session is a session corresponding to the terminal device, and the communication unit 602 is used by the communication unit 602.
  • the target base station receives a handover request response message, where the handover request response message includes second information, where the second information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session, the at least one QoS The flow includes the first QoS flow.
  • FIG. 7 is a schematic block diagram of a base station 700 according to an embodiment of the present application. It should be understood that the base station 700 is capable of performing the various steps performed by the target base station in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the base station 700 includes: a processing unit 701 and a communication unit 702,
  • the processing unit 701 is configured to receive, by using the communication unit 702, a handover request message, where the handover request message is used to indicate that the terminal device is handed over from the source base station to the target base station, where the handover request message includes First information, the first information includes information of at least one quality of service QoS flow of the first session, the first session is a session corresponding to the terminal device; and is sent by the communication unit 702 to the source base station a handover request response message, where the handover request response message includes second information, the second information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session, and the at least one QoS flow includes the The first QoS flow.
  • FIG. 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application. It should be understood that the terminal device 800 can perform the various steps performed by the terminal device in the methods of FIGS. 1 to 5, and in order to avoid repetition, it will not be described in detail herein.
  • the terminal device 800 includes: a processing unit 801 and a communication unit 802,
  • the processing unit 801 is configured to receive, by using the communication unit 802, a first RRC message from a source base station, where the first RRC message is used to instruct the terminal device to switch from the source base station to the target base station, where the An RRC message includes fifth information, the fifth information is used to indicate that the target base station is allowed to accept the first QoS flow of the first session, and that the first base station sends the first to the target base station by using the communication unit 802.
  • the RRC response message, the first RRC response message is used to respond to the first RRC message.
  • FIG. 9 is a schematic block diagram of a base station 900 according to an embodiment of the present application. It should be understood that the base station 900 can perform the various steps performed by the source base station in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the base station 900 includes: a memory 910, configured to store a program;
  • a communication interface 920 configured to communicate with other devices
  • the processor 930 is configured to execute a program in the memory 910, when the program is executed, the processor 930 is configured to send, by using the communication interface 920, a handover request message to the target base station, where the handover request message is used to indicate And the first session of the terminal device is switched from the source base station to the target base station, where the handover request message includes first information, where the first information includes information of at least one quality of service QoS flow of the first session, where The first session is a session corresponding to the terminal device; and the handover request response message is received from the target base station by using the communication interface 920, where the handover request response message includes second information, where the second information is used to indicate
  • the target base station allows acceptance of a first QoS flow of the first session, the at least one QoS flow including the first QoS flow.
  • FIG. 10 is a schematic block diagram of a base station 1000 according to an embodiment of the present application. It should be understood that the base station 1000 can perform the various steps performed by the target base station in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the base station 1000 includes:
  • a memory 1010 configured to store a program
  • a communication interface 1020 configured to communicate with other devices
  • the processor 1030 is configured to execute a program in the memory 1010, when the program is executed, the processor 1030 is configured to receive, by using the communication interface 1020, a handover request message from a source base station, where the handover request message is used to indicate And switching the terminal device from the source base station to the target base station, where the handover request message includes first information, where the first information includes information of at least one quality of service QoS flow of the first session, where the first session is a session corresponding to the terminal device; and sending, by the communication interface 1020, a handover request response message to the source base station, where the handover request response message includes second information, where the second information is used to indicate that the target base station allows Accepting a first QoS flow of the first session, the at least one QoS flow including the first QoS flow.
  • FIG. 11 is a schematic block diagram of a terminal device 1100 according to an embodiment of the present application. It should be understood that the terminal device 1100 can perform the steps performed by the terminal device in the methods of FIGS. 1 to 5, and is not detailed herein to avoid repetition.
  • the terminal device 1100 includes:
  • a memory 1110 configured to store a program
  • a communication interface 1120 configured to communicate with other devices
  • the processor 1130 is configured to execute a program in the memory 1110, when the program is executed, the processor 1130 is configured to receive, by using the communication interface 1120, a first radio resource control RRC message from a source base station, where the first The RRC message is used to indicate that the terminal device is handed over from the source base station to the target base station, where the first RRC message includes fifth information, and the fifth information is used to indicate that the target base station is allowed to accept the first The first QoS flow of the session; and sending, by the communication interface 1120, a first RRC response message to the target base station, where the first RRC response message is used to respond to the first RRC message.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本申请提供一种通信方法、基站、终端设备和系统，能够提高基站切换过程中的通信效率。该方法包括：源基站向目标基站发送切换请求消息，切换请求消息用于指示将终端设备的第一会话从源基站切换至至目标基站，切换请求消息包括第一信息，第一信息包括第一会话的至少一个服务质量QoS流的信息，第一会话为终端设备对应的会话；源基站从目标基站接收切换请求响应消息，切换请求响应消息包括第二信息，第二信息用于指示目标基站允许接受第一会话的第一QoS流，至少一个QoS流包括第一QoS流。

Description

通信方法、基站、终端设备和系统
本申请要求于2017年08月11日提交中国专利局、申请号为201710687720.3、发明名称为“通信方法、基站、终端设备和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及通信方法、基站、终端设备和系统。
背景技术
随着下一代通信系统研究的全面开展并逐渐深入，业界对5G通信系统研究的具体内容达成了基本共识。5G将支持各种类型的网络部署和应用类型。其中包括：更高速率体验和更大带宽的接入能力，例如增强型移动宽带(enhanced mobile broadband,eMBB)；更大规模、更低成本的机器类设备的接入和管理，例如大规模机器类通信(massive machine type communication,mMTC)；更低时延和高可靠的信息交互，例如超高可靠与低延迟通信(ultra reliable and low latency communication,URLLC)等。为了满足上述需求，5G定义了基于服务质量(quality of service,QoS)流(flow)的框架。
如何基于QoS流的框架对通信网络进行运营和管理，是业界亟待解决的问题。
发明内容
本申请提供一种通信方法、基站、终端设备和系统，能够提高基站切换过程中的通信效率。
第一方面，提供了一种通信方法，包括：源基站向目标基站发送切换请求消息，所述切换请求消息用于指示将终端设备的第一会话从所述源基站切换至所述至目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；所述源基站从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
在本申请实施例中，在基站间切换场景下，通过在切换请求响应消息中携带第二信息，以指示所述目标基站允许接受所述第一会话的第一QoS流，从而源基站可以根据第二信息的内容，执行基于QoS流粒度的切换过程，提高了基站切换过程的管理效率和通信效率。
在一种可能的实现方式中，还包括：所述源基站从所述目标基站接收第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
在一种可能的实现方式中，还包括：所述源基站从所述目标基站接收第四信息，所述 第四信息用于指示所述第二QoS流被拒绝的原因。
在一种可能的实现方式中，所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别QoS流信息。
在一种可能的实现方式中，还包括：所述源基站向所述终端设备发送第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流。
在一种可能的实现方式中，所述第五信息承载于第一无线资源控制RRC消息中，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站。
在一种可能的实现方式中，还包括：所述源基站从所述目标基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载；所述源基站向所述终端设备发送所述第六信息。
在一种可能的实现方式中，还包括：所述源基站向所述目标基站发送第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
在一种可能的实现方式中，所述源基站向所述目标基站发送第一数据，包括：所述源基站通过会话隧道向所述目标基站发送所述第一数据。
在一种可能的实现方式中，还包括：所述源基站向所述目标基站发送第一PDCP SDU，所述第一分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)服务数据单元(service data unit,SDU)包括所述第一会话中第一承载的PDCP SDU，所述第一承载为所述终端设备与所述源基站之间的承载；所述源基站向所述目标基站发送第七信息，所述第七信息用于指示所述第一PDCP SDU属于被接受的QoS流和/或被拒绝的QoS流。
在一种可能的实现方式中，还包括：所述源基站向所述目标基站发送第二PDCP SDU，所述第二PDCP SDU包括所述源基站通过所述第一会话的第一承载向所述终端设备发送的、未收到应答的PDCP SDU，所述第二PDCP SDU对应于所述第一承载中的第一QoS流。
在一种可能的实现方式中，还包括:所述源基站向所述终端设备发送第八信息，所述第八信息用于指示所述第二PDCP SDU的序列号。
第二方面，提供了一种通信方法，包括：目标基站从源基站接收切换请求消息，所述切换请求消息用于指示将终端设备从所述源基站切换至所述目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；所述目标基站向所述源基站发送切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
在本申请实施例中，在基站间切换场景下，通过在切换请求响应消息中携带第二信息，以指示所述目标基站允许接受所述第一会话的第一QoS流，从而源基站可以根据第二信息的内容，执行基于QoS流粒度的切换过程，提高了基站切换过程的管理效率和通信效率。
在一种可能的实现方式中，所述目标基站向所述源基站发送第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
在一种可能的实现方式中，所述目标基站向所述源基站发送第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
在一种可能的实现方式中，还包括：所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别QoS流信息。
在一种可能的实现方式中，还包括：所述目标基站向所述源基站发送第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
在一种可能的实现方式中，还包括：所述目标基站从所述源基站接收第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
在一种可能的实现方式中，所述目标基站从所述源基站接收第一数据，包括：所述目标基站通过会话隧道从所述源基站接收所述第一数据。
在一种可能的实现方式中，还包括：所述目标基站从所述源基站接收第一PDCP SDU，所述第一PDCP SDU是所述第一会话的第一承载的PDCP SDU，所述第一承载为所述终端设备与所述源基站之间的承载；所述目标基站从所述源基站接收第七信息，所述第七信息用于指示所述第一PDCP SDU属于被接受的QoS流和/或被拒绝的QoS流。
在一种可能的实现方式中，，所述方法还包括：所述目标基站根据所述第七信息，确定第三PDCP SDU，所述第三PDCP SDU为所述第一PDCP SDU中对应于被切换的QoS流的PDCP SDU；所述目标基站向高层传输所述第三PDCP SDU，和/或，所述目标基站向终端设备发送所述第三PDCP SDU。
在一种可能的实现方式中，还包括：所述目标基站从所述源基站接收第二PDCP SDU，所述第二PDCP SDU包括所述源基站通过所述第一会话的第一承载向所述终端设备发送的、未收到应答的PDCP SDU，所述第二PDCP SDU对应于所述第一承载中的第一QoS流；所述目标基站向所述终端设备发送所述第二PDCP SDU。
在一种可能的实现方式中，还包括：所述目标基站从终端设备接收第四PDCP SDU，所述第四PDCP SDU包括所述终端设备通过所述第一会话的第一承载向所述源基站发送的、未收到应答的PDCP SDU，所述第四PDCP SDU对应于所述第一承载中的所述第一QoS流。
在一种可能的实现方式中，还包括：所述目标基站从所述终端设备接收第九信息，所述第九信息用于指示所述第四PDCP SDU的序列号；所述目标基站根据所述第九信息，向高层传输所述第四PDCP SDU。
第三方面，提供了一种通信方法，包括：终端设备从源基站接收第一无线资源控制RRC消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流；所述终端设备向所述目标基站发送第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
在本申请实施例中，终端设备将根据第五信息指示的接纳控制结果，传递被接收的QOS流业务，并映射到目的基站决定的承载上，避免了传递被拒绝的数据包，从而实现了高效，可靠的小区间切换。
在一种可能的实现方式中，还包括：所述终端设备从所述源基站接收第六信息，所述 第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
在一种可能的实现方式中，还包括：所述终端设备从所述目标基站接收第二PDCP SDU，所述第二PDCP SDU包括所述源基站通过所述第一会话的第一承载向所述终端设备发送的、未收到应答的PDCP SDU，所述第二PDCP SDU对应于所述第一承载中的第一QoS流。
在一种可能的实现方式中，还包括：所述终端设备从所述源基站接收第八信息，所述第八信息用于指示所述第二PDCP SDU的序列号。
在一种可能的实现方式中，还包括：所述终端设备根据所述第八信息，向高层传输所述第二PDCP SDU。
在一种可能的实现方式中，还包括：所述终端设备向所述目标基站发送第四PDCP SDU，所述第四PDCP SDU包括所述终端设备通过所述第一会话的第一承载向所述源基站发送的、未收到应答的PDCP SDU，所述第四PDCP SDU对应于所述第一承载中的所述第一QoS流。
在一种可能的实现方式中，还包括：所述终端设备向所述目标基站发送第九信息，所述第九信息用于指示所述第四PDCP SDU的序列号。
第四方面，提供了一种基站，该基站用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该基站包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的模块。
第五方面，提供了一种基站，该基站用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该基站包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的模块。
第六方面，提供了一种终端设备，该终端设备用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。具体地，该基站包括用于执行上述第三方面或第三方面的任意可能的实现方式中的方法的模块。
第七方面，提供了一种通信系统，该通信系统包括上述第四方面、第五方面所述的基站和第六方面所述的终端设备。
第八方面，提供了一种基站，该基站包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第九方面，提供了一种基站，该基站包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第十方面，提供了一种终端设备，该终端设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存 储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第三方面或第三方面的任意可能的实现方式中的方法。
第十一方面，提供了一种通信方法，该通信系统包括上述第八方面、第九方面所述的基站和第十方面所述的终端设备。
第十二方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十三方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第十四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第三方面或第三方面的任意可能的实现方式中的方法的指令。
附图说明
图1是本申请实施例的网络架构的示意图。
图2是本申请实施例的通信方法的示意图。
图3是本申请实施例的协议数据单元的格式示意图。
图4是本申请实施例的基站切换流程示意图。
图5是本申请又一实施例的通信方法的示意图。
图6是本申请实施例的基站的结构示意图。
图7是本申请又一实施例的基站的结构示意图。
图8是本申请实施例的终端设备的结构示意图。
图9是本申请又一实施例的基站的结构示意图。
图10是本申请又一实施例的基站的结构示意图。
图11是本申请另一实施例的终端设备的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来的第五代(5th Generation，5G)系统或新无线(New Radio，NR)等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital  Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的基站可以是用于与终端设备通信的设备，该基站可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器等，本申请实施例并不限定。
如上文所述，5G将支持各种类型的网络部署和应用类型。为了满足上述需求，5G定义了基于服务质量(quality of service,QoS)流(flow)的框架。其可以支持保障流速率的QoS流或不保障流速率的QoS流。
下面简单介绍下本申请实施例涉及到的QoS流的架构。
图1是本申请实施例的一种可能的网络架构100的示意图。网络架构100是QoS流架构的一种可能的实现形式。如图1所示，一个终端设备可以与核心网(core network,CN)之间建立一个或多个会话。基站可以将属于不同的会话的数据包映射到不同的承载中，将属于同一会话的包映射到一个或多个承载中。其中，QoS流是在上述会话中实现QoS区分的最小粒度。可选地，可以为每个QoS流分配对应的QoS流标识(QoS flow identifier,QFI)，一个QFI可以用于指示一个QoS流。在同一会话中具有相同QFI的业务将会接受相同的调度策略或接纳控制。其中，在核心网与基站之间的通信接口之间传输数据包时，可以在数据包的封装头上携带QFI。如图1所示，上述核心网与基站之间的通信接口可以是N3接口，或者，上述核心网与基站之间的通信接口也可以称为下一代用户面(Next-generation user plane,NG-U)隧道。
需要说明的是，上述会话可以是分组数据单元(packet data unit,PDU)会话，上述承载可以是数据资源承载(data resource bearer,DRB)。其中，上述PDU会话可以是终端设备与数据网络之间建立的连接，该连接可以用于提供PDU连接服务，上述连接的类型可以是互联网协议(internet protocol,IP)、以太网或其他类型。在一些实施例中，将以上述会话是PDU会话、上述承载是DRB为例对本申请的方法或装置进行描述。此外，上述核心网可以包括核心网设备，核心网设备例如可以包括：用户面功能(user plane function,UPF)实体、接入和移动性管理功能(Access and Mobility Management function,AMF)，会话管理功能(Session Management function,SMF)。
5G基于DRB定义了空口上的数据包处理机制。由一个DRB服务的数据包在空口传输中具有相同的包处理机制。基站可以与终端设备之间建立多个DRB以满足具有不同包处理需求的QoS流。需要说明的是，同一个DRB可以与一个QoS流具有映射关系，也可以与多个QoS流具有映射关系。具体地，对于下行数据传输(down load,DL)，基站可以基于QFI标识和QFI对应的QoS规则(profile)，将QoS流对应的下行数据包映射到对应的DRB上，并进行下行传输。对应上行数据传输(up load,UL)，终端设备根据基 站配置的QoS流到DRB的映射关系，将QoS流对应的上行数据包映射至对应的DRB上，并进行上行传输。
为了便于理解，下面再介绍QoS流的参数。其中，在本申请实施例中，QoS流的参数也可以称为QoS流的配置参数。
具体地，每个QoS流至少包括如下参数：5G QoS标识(5G QoS Identifier,5QI)、分配与保留优先级(an allocation and retention priority,ARP)参数。例如，ARP参数可以包括如下信息中的至少一个：
优先级级别(priority level)参数：用于在资源受限的情况下确定该QoS流能否被接受或能够被拒绝，在一种典型的场景中，priority level参数可以应用于保障速率比特(guaranteed flow bit rate,GBR)QoS流；
抢占能力(the pre-emption capability)参数：用于确定该QoS流能否去抢占其他低优先级的QoS流的资源；
被抢占能力(the pre-emption vulnerability)参数：用于确定该QoS流能否被其他高优先级的QoS流抢占资源。
在本申请实施例中，网络架构100可以基于QoS流的框架进行数据传输的调度或管理，或者也可以说上述网络架构100可以进行基于QoS流粒度的接纳控制管理。其中，上述接纳控制管理可以指目标基站针对切换过程进行的接纳控制。例如，在本申请实施例的方案中，可以指目标基站确定是否接纳源基站请求切换的QoS流。在资源充裕的情况下，新增加的QoS流不影响其他QoS流的正常传输。在资源受限的情况下，基于分配与保留优先级参数，决定能否接纳映射到新增加的QoS流的业务传输。
在通信系统中引入基于QoS流的架构之后，如何在基于QoS流粒度的架构下实现高效率的数据传输的管理或调度，是业界亟待解决的问题。有鉴于此，本申请实施例主要关注在基站切换过程中，如何实现基于QoS流粒度的对切换过程进行管理。
图2是本申请一个实施例的通信方法200的示意图。其中，图2的方法可以应用于图1的网络架构100中。如图2所示，方法200可以包括步骤210-230，下面对图2的步骤进行详细描述。
在步骤210中，源基站向目标基站发送切换请求消息，相应地，目标基站从源基站接收切换请求消息。所述切换请求消息用于指示将终端设备从所述源基站切换至所述至目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个QoS流的信息，所述第一会话为所述终端设备对应的会话。
其中，上述将终端设备从源基站切换至目标基站，可以指将终端设备对应的会话从所述源基站切换至所述目标基站。
应理解，上述第一会话可以是终端设备与核心网之间建立的会话。该第一会话可以是终端设备发起或建立的，也可以是核心网发起并建立的，本申请实施例对此不作限定。例如，上述会话可以PDU会话。其中，上述PDU会话可以是终端设备与数据网络之间建立的连接，该连接可以用于提供PDU连接服务，上述连接的类型可以是互联网协议(internet protocol,IP)、以太网或其他类型。
还应理解，终端设备与核心网之间可以建立至少一个会话。上述至少一个会话中的每个会话可以对应至少一个承载，上述承载可以是终端设备与基站之间建立的承载。例如， 在终端设备从源基站切换至目标基站之前，上述承载可以是终端设备与源基站之间的承载；在终端设备从源基站切换至目标基站之后，上述承载可以是终端设备与目标基站之间的承载。上述至少一个承载中的每个承载可以与至少一个QoS流存在映射关系。换句话说，同一个承载可以传输一个或多个QoS流对应的数据包。作为一个示例，上述承载可以是DRB。
需要说明的是，上述第一会话的至少一个QoS流的信息，可以指所述第一会话中所有QoS流或部分QoS流的信息。具体地，所述至少一个QoS流的信息可以包括所述至少一个QoS流与承载之间的映射关系和/或所述至少一个QoS流的参数。作为一个具体例子，该第一信息可以指示第一会话中包括的一个或多个承载，以及上述多一个或个承载中的每个承载包括的QoS流。或者，该第一信息可以指示第一会话中的QoS流的参数以及上述QoS流映射至的承载。
例如，当第一会话为PDU会话(session)，上述承载为DRB时，表1示出了第一信息的一种可能的实现形式。
表1
PDU会话的列表(PDU sessions list)
>PDU会话标识(PDU Session ID)
>QoS流列表(Qos flow list)
>>>>QFI
>>>>QoS流参数
>RRC上下文信息
本申请实施例对第一信息的格式不作限定。例如，上述第一信息可以是信息单元(information element,IE)，或者也可以是指示符。如表1所示，第一信息中可以包括终端设备对应的PDU会话的标识，以及上述PDU会话包括的QoS流的列表。该QoS流的列表可以采用QFI表示。此外，第一信息还可以包括QoS流的参数以及RRC上下文信息。
例如，表2示出了QoS流的参数包括的内容。如表2所示，QOS流的参数包括以下至少一项：5QI、分配和竞争优先级(Allocation and Retention Priority)、GBR QoS流信息、提醒控制(Notification Control)。
表2
5QI
分配和竞争优先级(Allocation and Retention Priority)
GBR QoS流信息
提醒控制(Notification Control)
例如，表3示出了该RRC上下文信息包括的内容中，如表3所示，RRC上下文信息包括QoS flow与DRB映射关系以及DRB的配置参数。
表3
Figure PCTCN2018099713-appb-000001
Figure PCTCN2018099713-appb-000002
可选地，步骤210中，源基站在该切换请求消息中携带第一会话的至少一个QoS流的信息，其目的在于使目标基站根据该第一信息，进行接纳控制。
可选地，在步骤220中，目标基站根据第一信息，进行接纳控制。
其中，上述接纳控制可以指目标基站针对切换过程进行的接纳控制。例如，在本申请实施例的方案中，可以指目标基站确定是否接纳源基站请求切换QoS流。在资源充裕的情况下，新增加的QoS流不影响其他QoS流的正常传输。在资源受限的情况下，基于分配与保留优先级参数，决定能否接纳映射到新增加的QoS流的业务传输。
示例性地，上述接纳控制可以指目标基站根据当前网络状态以及其他参考因素，确定是否接收第一会话中的部分或全部QoS流。换句话说，目标基站可以根据第一信息包括的至少一个QoS流的信息，确定接收第一会话中的全部或部分QoS流，或确定拒绝第一会话中的全部或部分QoS流。示例性地，该接纳控制可以基于第一信息包括的至少一个QoS流的ARP参数。例如，在资源受限的情况下，可以基于各QOS流的ARP，拒绝部分或全部QOS流，并且向源基站发送拒绝QOS流的原因。其中，目标基站根据第一信息进行接纳控制的具体过程可以参见步骤230中的描述。
可选地，在步骤210之前，终端设备还可以进行小区测量，并向源基站发送小区测量报告。源基站可以根据该小区测量报告，确定向目标基站发送上述切换请求消息。
在步骤230中，所述源基站从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
具体地，目标基站在接收切换请求消息之后，可以根据切换请求消息包括的第一信息，确定接收第一会话中的全部或部分QoS流。例如，目标基站可以根据QoS流的参数和当前负载状况，进行接纳控制。上述QoS流的参数例如可以包括ARP参数。
进一步地，目标基站可以根据接纳控制的结果，向源基站发送切换请求响应消息，并在切换请求响应消息中携带上述第二信息，以指示所述目标基站允许接受第一会话中的第一QoS流。其中，所述第一QoS流可以是所述至少一个QoS流中的部分或全部QoS流。
在本申请实施例中，在基站间切换场景下，通过在切换请求响应消息中携带第二信息，以指示所述目标基站允许接受所述第一会话的第一QoS流，从而源基站可以根据第二信息的内容，执行基于QoS流粒度的切换过程，提高了基站切换过程的管理效率和通信效率。
可选地，第二信息可以采用显式和/或隐式的方式指示被目标基站接受第一QoS流。在显式的方式中，第二信息可以包括第一QoS流的标识。例如，上述第一QoS流的标识可以是QFI。源基站根据第二信息包括的QFI，可以确定第一会话中的哪些QoS流被接受，哪些QoS流被拒绝。或者，在隐式的方式中，第二信息可以包括第一会话中被拒绝的QoS流的标识。例如，上述第二信息可以包括被拒绝的QoS流的QFI。源基站根据第二信息中 包括的QFI，可以从第一会话中的QoS流中排除被拒绝的QoS流，从而确定被接受的第一QoS流。
作为一个具体示例，表4示出了第二信息的一种可能的实现方式，其中，本申请实施例对第二信息的格式不作限定。该第二信息可以是IE，也可以是指示符。如表4所示，第二信息中可以包括PDU会话的标识，以及该PDU会话中接受的QoS流的列表，具体地，QoS流的列表可以包括QoS流的QFI。
表4
被接受的PDU会话的列表(PDU sessions admitted list)
>PDU会话标识(PDU Session ID)
>被接受的QoS流列表(accepted QoS flow list)
>>QFI
进一步地，在一些实施例中，所述源基站还可以从所述目标基站接收第三信息，所述第三信息用于指示所述目标基站拒绝接收所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
作为一个具体例子，表5示出了第二信息和/或第三信息的一种实现形式。具体地，表3可以是第二信息既包括显式又包括隐式的一种可能的实现方式，或者，表5也可以是切换请求响应消息同时包括第二信息和第三信息的一种可能的实现方式。其中，本申请实施例对第二信息或第三信息的格式不作限定。该第二信息或第三信息可以是IE，也可以是指示符。
如表5所示，第二信息和/或第三信息中可以包括被接受的PDU会话的标识、上述PDU会话中被接受的QoS流的列表以及PDU会话中被拒绝的QoS流的列表，具体地，QoS流的列表可以包括QoS流的QFI。
表5
被接受的PDU会话的列表(PDU sessions admitted list)
>PDU会话标识(PDU session ID)
>被接受的QoS流的列表(accepted QoS flow list)
>>QFI
>被拒绝的QoS流的列表(rejected QoS flow list)
>>QFI
可选地，当一个PDU会话中的所有QoS流被拒绝时，则表示整个PDU会话被拒绝。例如，表6示出了整个PDU会话被拒绝时，第二信息或第三信息的一种可能的实现形式。具体地，表4示出了第二信息为隐式的一种可能的实现方式，或者，表6示出了第三信息的一种可能的实现形式。如表6所示，第二信息或第三信息可以包括被拒绝的PDU会话的列表，其中，上述被拒绝的PDU会话的列表可以用PDU会话的标识表示。
表6
Figure PCTCN2018099713-appb-000003
Figure PCTCN2018099713-appb-000004
具体地，在终端设备从源基站切换至目标基站的过程中，可能会存在如下多种情形。在第一种情形中，第一会话中的所有QoS流都被目标基站拒绝，或第一会话中的所有QoS流都被接受，即整个第一会话被目标基站拒绝或接受。在第二种情形中，第一会话中的同一个承载中的所有QoS流都被目标基站拒绝，或第一会话中的同一个承载中的所有QoS流都被目标基站接受。在第三种情形中，第一会话中的同一承载中的部分QoS流被目标基站拒绝，或第一会话中的同一承载中的部分QoS流被目标基站接受。
更进一步地，所述源基站还可以从所述目标基站接收第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
示例性地，上述第三信息、第四信息可以都携带于步骤230中的切换响应消息之中，或者，上述第三信息和第四信息也可以与切换响应消息单独发送。
示例性地，上述第二QoS流被拒绝的原因包括以下至少一项：资源不足(no resource available)、不支持的QoS流信息(Not supported)、无法识别QoS流信息(invalid QoS parameter)、不支持的QFI(not supported QFI)。其中上述资源不足可以指目标基站的空口资源不足，上述不支持的QoS流信息可以指目标基站不支持被拒绝的QoS流，上述无法识别QoS流信息可以指目标基站无法识别该被拒绝的QoS流的信息，上述不支持的可以指目标基站不支持该QFI。或者，上述第二QoS流被拒绝的原因还可以包括其他因素，本申请实施例不再一一枚举。
在本申请实施例中，在基站切换场景下，提出了一种基于QoS流粒度的传输控制方式，从而能够在基站切换过程中实现更小粒度的服务质量管理，提高了通信的效率。
可选地，方法200还包括步骤240和步骤250。
在步骤240中，终端设备从所述源基站接收第一无线资源控制(radio resource control,RRC)消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流。
在一些实施例中，第五信息也可以不携带于上述第一RRC消息中，而是与第一RRC消息分开发送。
在本申请实施例中，终端设备将根据第五信息指示的接纳控制结果，传递被接收的QOS流业务，并映射到目的基站决定的承载上，避免了传递被拒绝的数据包，从而实现了高效，可靠的小区间切换。
在一些实施例中，上述第一RRC消息可以是RRC连接重配置(RRC connection reconfiguration)消息。
在一些实施例中，上述第一RRC消息可以包括指示信息，该指示信息用于指示终端设备与目标基站之间建立所述第一会话的第二承载，以用于终端设备和目标基站之间传输数据。上述第二承载携带(carry)的QoS流包括所述第一QoS流。
作为一个可能的方案，方法200还包括：所述源基站从所述目标基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。源基站在获取该第六信息之后， 可以将该第六信息发送给终端设备。
应理解，由于在切换过程中，目标基站与终端设备尚未建立连接，因此，源基站相当于透传所述第六信息。换句话说，该第六信息实际上是目标基站向终端设备发送的信息。例如，目标基站可以采用透明容器(transparent container)向源基站发送第六信息，然后由源基站转发给终端设备。
进一步地，终端设备在接收第六信息之后，可以根据第六信息，建立与目标基站之间的第二承载。
示例性地，在源基站从目标基站接收上述第六信息的情况下，上述第六信息可以携带于S230中的切换请求响应消息之中。
示例性地，上述第六信息可以是以被接受的QoS列表的形式发送。
示例性地，在目标基站向终端设备转发上述第六信息的情况下，上述第六信息可以携带于S240中的第一RRC消息中。
作为一个具体示例，当上述第一会话为PDU会话(session)，上述承载为DRB时，表7示出了第六信息的一种可能的实现形式。本申请实施例对第六信息的格式不作限定。例如，上述第六信息可以是信息单元(information element,IE)，或者也可以是指示符。如表7所示，第六信息中可以包括PDU会话的标识，以及该PDU会话包括的DRB的标识列表。进一步地，第六信息还包括每个DRB包括的QoS流的列表。该QoS流的列表可以采用QFI表示。此外，第六信息还可以包括DRB的配置参数。DRB的配置参数包括以下至少一项：物理(physical,PHY)层配置参数、媒体接入介质(Media Access Control,MAC)层配置参数、无线链路(Radio Link Control,RLC)层配置参数、PDCP层配置参数、SDAP层配置参数。
表7
Figure PCTCN2018099713-appb-000005
在步骤250中，目标基站从所述终端设备接收第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
在一些实施例中，当上述第一RRC消息是RRC连接重配置(RRC connection reconfiguration)消息的情况下，上述第一RRC消息可以是RRC连接重配置响应(RRC connection reconfiguration response)消息。
在一些实施例中，当上述第一RRC消息包含指示终端设备与目标基站建立第二承载的指示信息时，终端设备可以与目标基站建立该第二承载，并在建立完成之后，向所述目标基站发送该第一RRC响应消息。
在一些实施例中，若终端设备与目标基站建立第二承载失败，也可以向目标基站发送第一RRC响应消息，并在第一RRC响应消息中携带承载建立失败的原因。
在本申请实施例中，终端设备通过接收源基站发送的第一RRC消息，第一RRC消息中包含的第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流，从而终端设备可以根据第五信息的指示，进行基于QoS粒度的切换流程，提高了基站切换过程中的通信效率。
上文主要描述了基站切换过程中的信令流程，接下来将描述基站切换中的数据切换(data forwarding)的过程。在基站切换过程中，源基站或终端设备侧将存在大量的未收到应答的数据包，或者，源基站将缓存从核心网接收的，未向终端设备发送的数据。因此，如何在切换场景中保障无损切换是业界需要解决的重要问题。
其中，上述数据包可以包括分组数据汇聚协议(packet data convergence protocol,PDCP)服务数据单元(service data unit,SDU)。上述PDCP SDU可以是基站与终端设备在PDCP层传输的数据包。上述PDCP层属于无线接入协议体系结构中数据链路层(data link)中的子层。上述数据链路层也可以称为层二。其中，PDCP层的下层子协议包括无线链路控制(radio link control)层。PDCP层的上层协议为RRC层。可选地，在本申请实施例中，在PDCP层与RRC层之间增加了一个新的协议层，该协议层为业务数据适应协议(Service Data Adaptation Protocol,SDAP)。上述SDAP层功能包括并不限于：用于处理QoS流到DRB的映射、用于在数据包的包头增加QoS流ID。
在步骤230中提到，在终端设备从源基站切换至目标基站的过程中，可能会存在如下多种情形。在第一种情形中，第一会话中的所有QoS流都被目标基站拒绝，或第一会话中的所有QoS流都被接受，即整个第一会话被目标基站拒绝或接受。在第二种情形中，第一会话中的同一个承载中的所有QoS流都被目标基站拒绝，或第一会话中的同一个承载中的所有QoS流都被目标基站接受。在第三种情形中，第一会话中的同一承载中的部分QoS流被目标基站拒绝，或第一会话中的同一承载中的部分QoS流被目标基站接受。
通常情况下，基站之间进行数据切换的粒度可以是基于承载粒度的，一个或多个QoS流可以映射在同一承载上进行数据传输。在上述前两种情形中，基站之间可以采用通常的方式进行数据切换。但是，在第三种情形中，由于同一承载中的部分QoS流未被目标基站接受，若传输未被接受的QoS流对应的数据包，则会造成资源的浪费。
具体地，在上述第一种情形中，当第一会话中的所有QoS流都被目标基站拒绝时，源基站和目标基站之间可以不进行第一会话的数据传递，当第一会话中的所有QoS流被接受时，源基站可以与目标基站对整个第一会话进行数据传递。在第二种情形中，当第一会话中的同一承载对应的所有QoS流都被目标基站拒绝时，源基站和目标基站之间可以不进行该承载对应的数据传递；当第一会话中的同一承载对应的所有QoS流被传递时，源基站和目标基站之间可以对整个承载进行数据切换。在第三种情形中，由于同一承载中的部分QoS流未被目标基站接受，若针对整个承载进行数据切换，则会造成资源的浪费。并且，若目标基站在过载情况下拒绝QoS流，则针对整个承载进行数据切换会导致空口传输更加拥塞。
针对上述多种情形，本申请实施例提出了多种数据切换的方案。下面将结合上行数据传输(UL)和下行数据传输(DL)两种情况，描述本申请中的数据切换的方案。
在DL过程中，源基站主要缓存有两种类型的数据。第一种类型的数据为从核心网收到的新的数据包，尚未向终端发送该数据包。在收到核心网发送的结束标记(end marker)之前，源基站将持续接收并缓存上述数据包。第二种类型的数据为源基站通过第一会话的第一承载正在向终端设备传输的、尚未收到应答的数据包。上述数据包可以是PDCP SDU，其正在PDCP层进行传输。上述尚未收到应答的数据包可以指PDCP SDU未收到基站的RLC层的确认或应答。
在UL过程中，源基站还缓存有第三种类型的数据。该第三种类型的数据为源基站从终端设备接收的、乱序的数据包。即上述数据包的序列号是非连续的。因为源基站需要向高层按序递交数据包。因此，对于序列号不连续的数据包，源基站需要将数据包暂时缓存起来，等接收到剩余的数据包之后，一起按序向高层递交。其中，上述数据包可以指PDCP SDU，上述高层可以指PDCP层以上的协议层。例如，上述高层可以是SDAP层或RRC层。另外，在UL过程中，终端设备还缓存有第四种类型的数据，该第四种类型的数据为所述终端设备通过第一会话的第一承载正在向所述源基站传输的、尚未收到应答的数据包。上述数据包可以是PDCP SDU，其正在PDCP层进行传输。上述尚未收到应答的数据包可以指PDCP SDU未收到终端设备的RLC层的确认或应答。
针对DL的两种类型的数据，由于第一种类型的数据是根据QoS流进行传输的，尚未映射至承载。因此，针对上述三种情形中的任意一种情形，若第一种类型的数据对应的QoS流被拒绝，则源基站不向目标基站传输第一种类型的数据，若第一种类型的数据对应的QoS流被接受，则源基站向目标基站传输该第一种类型的数据。其中，上述第一种类型的数据可以为下文中的第一数据。
在一些实施例中，方法200还包括：所述源基站向所述目标基站发送第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
在方法200中，针对第一数据的传输方式，源基站可以通过两种方案向目标基站传输该第一数据。在第一种方案中，源基站将第一QoS流对应的数据包，在PDCP层向目标基站传输第一数据。在第二种方案中，源基站不继续服务于第一QoS流对应的数据包，而是通过会话隧道向目标基站发送所述第一数据。其中，该会话隧道可以是基于会话粒度隧道。由于会话隧道的数据包格式和核心网传输给源基站的数据包格式可以是相同的。所以源基站在从核心网获取该第一数据后，进行帧头或者包括扩展帧头更新后，可以直接在SDAP层向目标基站发送，从而节约了处理第一数据的资源，提高了通信效率。
在本申请实施例中，通过源基站与目标基站之间的会话隧道转发核心网向终端设备发送的第一数据，无需在PDCP层传输第一数据，从而节约了处理第一数据的时间和占用的资源，提高了通信效率。
示例性地，上述会话隧道的格式可以包括：通用分组无线服务隧道协议(General Packet Radio Service tunneling protocol，GTP)(头)header、扩展头(extension header)、互联网协议包(internal protocol packet,IP packet)。
更具体的，可以在GTP扩展头(extension header)中，增加QFI标识和/或反射QoS指示(reflective QoS indication,RQI)标识。一种GTP头的具体实现如下表8所示。如表8所示：
表8
扩展头标识 扩展头类型
1100 0100 RQI
1100 0011 QFI
… …
在方法200中，针对DL的第二种类型的数据以及UL的第三种类型的数据，源基站可以采用两种方式向目标基站传输第二和/或第三种类型的数据。在第一种方式中，源基站可以基于承载粒度向目标基站传输第二和/或第三种类型的数据。或者说，源基站向目标基站传输一个承载中所有QoS流对应的数据包。在第二种方式中，源基站可以基于QoS流粒度向目标基站传输第二和/或第三种类型的数据。或者说，源基站向目标基站传输被接受的第一QoS流对应的数据包。其中，上述第一种方式和第二种方式都可以应用于上述源基站切换至目标基站的三种情形中。
结合上述第一种方式，当第二种类型的数据为下文中的第一PDCP SDU时，方法200还包括：所述源基站向所述目标基站发送第一PDCP SDU，所述第一PDCP SDU包括所述第一会话的第一承载的PDCP SDU，所述第一承载为所述终端设备与所述源基站之间的承载。
其中，上述第一PDCP SDU可以包括上述DL中的第二种类型的数据或上述UL中的第三种类型的数据。例如，对于DL过程，上述第一PDCP SDU可以包括源基站通过第一会话的第一承载向终端设备发送的、未收到应答的PDCP SDU，和/或，对于UL过程，第一PDCP SDU还包括源基站通过第一会话的第一承载从终端设备接收的、乱序的PDCP SDU。
其中，上述被接受的QoS流可以指上述第一QoS流，上述被拒绝的QoS流可以指第二QoS流。上述第二QoS流可以指第一承载中未被目标基站接受的QoS流。
其中，上述第一PDCP SDU对应的QoS流可以包括上述第一承载对应的所有QoS流。或者说，上述第一PDCP SDU可以包括对应于第一QoS流和第二QoS流的PDCP SDU。还可以理解为，源基站不根据第一QoS流和第二QoS流对第一承载包括的第一PDCP SDU进行区分，而是将第一承载包括的所有PDCP SDU向目标基站发送。
结合第一种方式，在一些实施例中，目标基站能够分辨出哪个PDCP SDU对应哪个QoS流。例如，PDCP SDU的扩展头中可以包括其对应的QoS流的标识。目标基站可以从PDCP SDU的扩展头读取QoS流的标识，确定第一PDCP SDU是对应被接受的QoS流还是被拒绝的QoS流。继而从第一PDCP SDU中确定第三PDCP SDU，所述第三PDCPSDU为所述第一PDCP SDU中对应于被切换的QoS流的PDCP SDU。
结合第一种方式，在另一些实施例中，目标基站不能自主分辨PDCP SDU对应的QoS流。因而，在这种情况下，方法200还包括：所述源基站向所述目标基站发送第七信息，所述第七信息用于指示所述第一PDCP SDU属于被接受的QoS流和/或被拒绝的QoS流。
可选地，上述被接受的QoS流和/或被拒绝的QoS流也可以描述为切换的QoS流和/或未切换的QoS流。
示例性地，上述第七信息可以包括被接受的QoS流的序列号(serial number,SN)或被拒绝的QoS流的序列号。
可选地，上述第七信息可以承载于序列号状态传输和序列号归属状态(SN statustransfer&SN accept status)消息中。上述SN status transfer&SN accept status消息可以在源基站和目标基站之间的通信接口之间传输。在一些实施例中，上述通信接口可以是Xn接口。
上述SN status transfer&SN accept status消息可以用于指示被接受的QoS流的序列号(serial number,SN)或被拒绝的QoS流的序列号。
可选地，上述第七信息可以承载于其他类型的消息中，本申请实施例对此不作限定。
结合上述第一种方式，当目标基站从源基站接收第一PDUCP SDU之后，方法200还包括：所述目标基站根据所述第七信息，确定第三PDCP SDU，所述第三PDCP SDU为所述第一PDCP SDU中对应于被切换的QoS流的PDCP SDU；所述目标基站向高层传输所述第三PDCP SDU，和/或，所述目标基站向终端设备发送所述第三PDCP SDU。
其中，上述被切换的QoS流可以指被切换至目标基站的QoS流。在方法200中，上述被切换的QoS流可以指第一QoS流。
可选地，上述第三PDCP SDU可以是根据第七信息确定的。在另外一些实施例中，目标基站也可以不根据第七信息，而是根据第一PDCP SDU的扩展头包括的QFI自主识别其对应的QoS流，进而从第一PDCP SDU中确定第三PDCP SDU。
根据上述的描述可知，第一PDCP SDU包括两种类型的数据中的至少一种。上述两种数据分别用于UL和DL。具体地，对于DL过程，上述第一PDCP SDU可以包括源基站通过第一会话的第一承载向终端设备发送的、未收到应答的PDCP SDU，和/或，对于UL过程，第一PDCP SDU还包括源基站通过第一会话的第一承载从终端设备接收的、乱序的PDCP SDU。因而，第三PDCP SDU也可以包括上述两种类型的数据中的至少一种。目标基站在获取第三PDCP SDU之后，可以通过第二承载将第三PDCP SDU中用于DL的PDCP SDU向终端设备发送。然后可以将第三PDCP SDU中用于UL的数据向高层传输。上述高层可以指基站的PDCP层以上的协议层。例如，上述高层可以是SDAP层或RRC层。
结合上述第二种方式，方法200还包括：所述目标基站从所述源基站接收第二PDCP SDU，所述第二PDCP SDU包括所述源基站通过所述第一会话中的第一承载向所述终端设备发送的、未收到应答的PDCP SDU，和/或，所述第二PDCP SDU包括所述源基站通过所述第一会话的第一承载从所述终端设备接收的、乱序的PDCP SDU，所述第二PDCP SDU对应于所述第一承载中的第一QoS流。
在本申请实施例中，当QoS流被目标基站拒绝之后，源基站不向目标基站转发对应于被拒绝的QoS流的数据，只转发被接受的QoS流对应的数据，因此，节约了基站之间的数据传输的开销。
在一些实施例中，方法200还包括：目标基站向所述终端设备传输所述第二PDCP SDU，和/或，所述目标基站向高层传输所述第二PDCP SDU。
在本申请实施例中，当QoS流被目标基站拒绝之后，目标基站和终端设备在基站切换过程中，不传输对应于被拒绝的QoS流的数据，只传输被接受的QoS流对应的数据，因此，节约了空口资源开销，从而可以将节约的资源用于其他数据传输，提高系统频谱的效率。
根据上述的描述可知，第二PDCP SDU包括两种类型的数据中的至少一种。上述两种数据分别用于UL和DL。例如，对于DL过程，上述第二PDCP SDU可以包括源基站通过第一会话的第一承载向终端设备发送的、未收到应答的PDCP SDU，和/或，对于UL过程，第二PDCP SDU还包括源基站通过第一会话的第一承载从终端设备接收的、乱序的PDCP SDU。因而，目标基站在获取第二PDCP SDU之后，可以通过第二承载将第二PDCP SDU中用于DL的PDCP SDU向终端设备发送。然后可以将第二PDCP SDU中用于UL的数据向高层传输。上述高层可以指基站的PDCP层以上的协议层。例如，上述高层可以是SDAP层或RRC层。
在一些实施例中，方法200还包括：所述源基站向所述终端设备发送第八信息，所述第八信息用于指示所述第二PDCP SDU的序列号。
其中，若终端设备与源基站之间的第一承载中存在被切换的第一QoS流和未被切换的第二QoS流。则第一承载中的PDCP SDU序列号包括第一QoS流和第二QoS流对应的PDCP SDU的序列号可以是交叉排序的。因而第二PDCP SDU的序列号可能是不连续的。通常情况下，终端设备或基站在收到PDCP SDU之后，需要根据序列号按序向高层传递PDCP SDU。但是，由于终端设备与目标基站之间不传输第二QoS流对应的数据。因此，终端设备在收到第八信息之后，可以识别出第二PDCP SDU，从而即使第二PDCP SDU序列号不连续，终端设备也可以向高层传输第二PDCP SDU，而无需等待第二QoS流对应的数据，从而提高了通信效率，以及提高了基站切换过程中传输管理的灵活度。
在上文中还提及，针对UL过程，终端设备还存在第四种类型的数据，该第四种类型的数据为所述终端设备正在向所述源基站传输的、尚未收到应答的数据包。
在方法200中，还包括：所述目标基站从终端设备接收第四PDCP SDU，所述第四PDCP SDU包括所述终端设备通过所述第一会话的第一承载向所述源基站发送的、未收到应答的PDCP SDU，所述第四PDCP SDU对应于所述第一承载中的所述第一QoS流。
示例性地，终端设备在接收到上述第五信息之后，确定被目标基站接受的第一QoS流。进一步地，终端设备可以不向目标基站发送未被接受的第二QoS流对应的PDCP SDU，而是向目标基站发送被接受的第一QoS流对应的第四PDCP SDU。
在本申请实施例中，在基站切换过程中，终端设备无需向目标基站发送未被接受的QoS流对应的PDCP SDU，只需向目标基站发送被接受的第一QoS流对应的PDCP SDU，从而节省了空口资源，该节省的资源可以用于其他数据传输，进而提高了系统频谱效率。
在一些实施例中，方法200还包括：所述目标基站从所述终端设备接收第九信息，所述第九信息用于指示所述第四PDCP SDU的序列号；所述目标基站根据所述第九信息，向高层传输所述第四PDCP SDU。
其中，因为第四PDCP SDU是对应于第一QoS流的PDCP SDU。在基站切换过程中，上述第四PDCP SDU的序列号可能是不连续的。通常情况下，终端设备或基站在收到PDCP SDU之后，需要根据序列号按序向高层传递PDCP SDU。但是，由于终端设备与目标基站之间不传输第二QoS流对应的数据。因此，目标基站在收到第九信息之后，可以识别出第四PDCP SDU，从而即使第四PDCP SDU序列号不连续，目标基站也可以向高层传输第四PDCP SDU，而无需等待第二QoS流对应的PDCP SDU，从而提高了通信效率，以及提高了基站切换过程中传输管理的灵活度。
在本申请实施例中，终端设备通过向目标基站发送第九信息，以指示第四PDCP SDU的序列号，使得目标基站也可以识别被接受的QoS流对应的第四PDCP SDU，从而无需等待其他PDCP SDU，并无需按序提交第四PDCP SDU。从而提高了通信效率，以及提高了基站切换过程中传输管理的灵活度。
可选地，图3示出了本申请实施例的一种PDCP层的协议数据单元(protocol data unit,PDU)格式。该PDU可以作为控制PDU在基站与终端设备之间传输。
如图3所示，PDU类型(PDU type)可以用于指示该PDU指示的内容类型。例如，当PDU类型设置为100时，可以指该PDU用于指示PDCP SDU的序列号。当PDU类型设置为其他数值时，该PDU可以用于指示其他类型的信息。例如，作为示例，表6示出了PDU类型为其他数值时，该PDU指示的内容类型。需要说明的是，表6中对PDU类型赋值只是一种具体示例，本领域人员能够理解，对PDU类型的赋值所指示的内容可以根据实际情况定义，而不必限于本申请的例子。类似的，上述赋值的方式也适用于本申请其他实施例相似的情况。
表9
Figure PCTCN2018099713-appb-000006
另外，图3中的第一个非发送的序列号(first not sending SN,FNSS)可以指不发送的PDCP SDU中的第一个PDCP SDU的序列号。上述不发送的PDCP SDU可以指被拒绝的QoS流对应的PDCP SDU。
在另一种实现方式中，上述FNSS也可以被第一个发送的序列号(first sending SN,FSS)替代，上述FSS可以指发送的PDCP SDU中的第一个PDCP SDU的序列号。上述发送的PDCP SDU可以指被接受的QoS流对应的PDCP SDU。
其中，图3中的D/C可以用于该指示PDU的应用类型。例如，当D/C设置为0时，可以表示该PDU为用于控制的PDU。当D/C设置为1时，可以表示该PDU为用于数据的PDU。
可选地，图3中还包括位图(bitmap)，bitmap可以配合FNSS或FSS，指示FNSS或FSS对应的PDCP SDU是发送的PDCP SDU还是不发送的PDCP SDU。例如，当bitmap的赋值为1时，可以是发送的PDCP SDU，当bitmap的赋值为0时，可以是不发送的PDCP SDU。
图2的例子中由源基站和目标基站之间直接进行信息传输。需要说明的是，图2的方法也适用于经由核心网的基站切换。下面结合介绍经由核心网进行基站切换的信令交互过程。
图4示出了经由核心网进行基站切换的信令交互过程。其中，图4中的核心网设备例如可以是AMF。在图4的方法中，源基站和目标基站之间不直接传输信息，而是通过核心网设备进行信息的交互。图4的例子中与图2相同或相似的内容，此处不再赘述。图4的方法包括：
S410、源基站向核心网设备发送切换需求消息。
S420、核心网设备根据切换需求消息，向目标基站发送切换请求消息。
S430、目标基站在接收到切换请求响应消息之后，进行接纳控制，并向核心网设备发送切换请求响应消息。
具体地，关于接纳控制的内容可以参考图2的步骤S220。
S440、核心网设备向源基站发送切换请求响应消息。
S450、终端设备执行切换过程。
图5本申请实施例的通信方法500的示意图。图5示出了基站切换的具体流程。图5的例子中与图2中相同或相似的内容，请参考图2中的相关实施例，此处不再赘述。如图5所示，图5的方法包括：
S501、终端设备上报测量结果给源基站。
S502、源基站决定将终端设备切换至目标基站。
例如，基于终端设备的上报测量结果，源基站决定将该终端设备切换到一个目标基站。
S503、源基站向目标基站发送切换请求消息，切换请求消息可以包括终端设备对应的会话的QOS flow消息。切换请求消息的具体内容可以参见图2的例子中的相关描述。
S504、目标基站执行QoS flow粒度的接纳控制。
具体地，关于接纳控制的内容可以参考图2的步骤S220。
S505、目标基站发送切换响应消息给源基站。
具体地，关于切换响应消息的内容可以参见图2的步骤S230。
S506、源基站发送RRC重配置消息给终端设备，其内包括接纳控制结果。
具体地，图2中的第一RRC消息可以是上述RRC重配置消息。关于RRC重配置消息可以参见图2的步骤S230的相关描述。
例如，上述RRC重配置消息可以包括接纳的QoS flows->DRB映射发送给终端设备
S507、源基站发送SN status transfer和SN归属状态消息给目标基站，同时启动data forwarding过程。
关于SN status transfer和SN归属状态消息，以及data forwarding相关内容可以参见图2的例子中的描述。
S508终端设备同步到目标基站，从而最终结束了切换过程；
例如，对于DL，目标基站可以发送图3中的PDCP控制PDU给终端设备，告知SN状态。
例如，对于UL，终端设备可以发送图3中的PDCP control PDU给目标基站，告知SN状态。
上文结合图1至图5详细描述了本申请实施例的通信方法，下文将结合图6至图11详细描述本申请实施例的基站和终端设备。
图6是本申请实施例的基站600的示意性框图。应理解，基站600能够执行图1至图5的方法中由源基站执行的各个步骤，为了避免重复，此处不再详述。基站600包括：处理单元601和通信单元602，
所述处理单元601用于通过所述通信单元602向目标基站发送切换请求消息，所述切换请求消息用于指示将终端设备的第一会话从所述源基站切换至所述至目标基站，所述切 换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；通过所述通信单元602从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
图7是本申请实施例的基站700的示意性框图。应理解，基站700能够执行图1至图5的方法中由目标基站执行的各个步骤，为了避免重复，此处不再详述。基站700包括：处理单元701和通信单元702，
所述处理单元701用于通过所述通信单元702从源基站接收切换请求消息，所述切换请求消息用于指示将终端设备从所述源基站切换至所述目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；以及通过所述通信单元702向所述源基站发送切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
图8是本申请实施例的终端设备800的示意性框图。应理解，终端设备800能够执行图1至图5的方法中由终端设备执行的各个步骤，为了避免重复，此处不再详述。终端设备800包括：处理单元801和通信单元802，
所述处理单元801用于通过所述通信单元802从源基站接收第一RRC消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流；以及通过所述通信单元802向所述目标基站发送第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
图9是本申请实施例的基站900的示意性框图。应理解，基站900能够执行图1至图5的方法中由源基站执行的各个步骤，为了避免重复，此处不再详述。基站900包括：存储器910，用于存储程序；
通信接口920，用于和其他设备进行通信；
处理器930，用于执行存储器910中的程序，当所述程序被执行时，所述处理器930用于通过所述通信接口920向目标基站发送切换请求消息，所述切换请求消息用于指示将终端设备的第一会话从所述源基站切换至所述至目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；以及通过所述通信接口920从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
图10是本申请实施例的基站1000的示意性框图。应理解，基站1000能够执行图1至图5的方法中由目标基站执行的各个步骤，为了避免重复，此处不再详述。基站1000包括：
存储器1010，用于存储程序；
通信接口1020，用于和其他设备进行通信；
处理器1030，用于执行存储器1010中的程序，当所述程序被执行时，所述处理器1030 用于通过所述通信接口1020从源基站接收切换请求消息，所述切换请求消息用于指示将终端设备从所述源基站切换至所述目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；以及通过所述通信接口1020向所述源基站发送切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
图11是本申请实施例的终端设备1100的示意性框图。应理解，终端设备1100能够执行图1至图5的方法中由终端设备执行的各个步骤，为了避免重复，此处不再详述。终端设备1100包括：
存储器1110，用于存储程序；
通信接口1120，用于和其他设备进行通信；
处理器1130，用于执行存储器1110中的程序，当所述程序被执行时，所述处理器1130用于通过所述通信接口1120从源基站接收第一无线资源控制RRC消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流；以及通过所述通信接口1120向所述目标基站发送第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计 算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (36)

  1. 一种通信方法，其特征在于，包括：
    源基站向目标基站发送切换请求消息，所述切换请求消息用于指示将终端设备的第一会话从所述源基站切换至所述至目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；
    所述源基站从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
  2. 如权利要求1所述的通信方法，其特征在于，所述方法还包括：所述源基站从所述目标基站接收第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
  3. 如权利要求2所述的通信方法，其特征在于，所述方法还包括：所述源基站从所述目标基站接收第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
  4. 如权利要求3所述的通信方法，其特征在于，所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别5QI信息。
  5. 如权利要求1至4中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述源基站向所述终端设备发送第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流。
  6. 如权利要求5所述的通信方法，其特征在于，所述第五信息承载于第一无线资源控制RRC消息中，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述源基站从所述目标基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载；
    所述源基站向所述终端设备发送所述第六信息。
  8. 如权利要求1至7中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述源基站向所述目标基站发送第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
  9. 如权利要求8所述的通信方法，其特征在于，所述源基站向所述目标基站发送第一数据，包括：所述源基站通过会话隧道向所述目标基站发送所述第一数据。
  10. 一种通信方法，其特征在于，包括：
    目标基站从源基站接收切换请求消息，所述切换请求消息用于指示将终端设备从所述源基站切换至所述目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；
    所述目标基站向所述源基站发送切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
  11. 如权利要求10所述的通信方法，其特征在于，所述方法还包括：所述目标基站向所述源基站发送第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
  12. 如权利要求11所述的通信方法，其特征在于，所述方法还包括：所述目标基站向所述源基站发送第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
  13. 如权利要求12所述的通信方法，其特征在于，所述方法还包括：所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别QoS流信息。
  14. 如权利要求11至13中任一项所述的通信方法，其特征在于，所述方法还包括：所述目标基站向所述源基站发送第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
  15. 如权利要求11至14中任一项所述的通信方法，其特征在于，所述方法还包括：
    所述目标基站从所述源基站接收第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
  16. 如权利要求11至15中任一项所述的通信方法，其特征在于，所述目标基站从所述源基站接收第一数据，包括：所述目标基站通过会话隧道从所述源基站接收所述第一数据。
  17. 一种通信方法，其特征在于，包括：
    终端设备从源基站接收第一无线资源控制RRC消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流；
    所述终端设备向所述目标基站发送第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
  18. 如权利要求17所述的通信方法，其特征在于，所述方法还包括：
    所述终端设备从所述源基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
  19. 一种基站，其特征在于，所述基站为源基站，包括：
    通信接口，
    存储器，用于存储指令，
    处理器，与所述存储器和所述通信接口分别相连，用于执行所述存储器存储的所述指令，以在执行所述指令时执行如下步骤：
    通过所述通信接口向目标基站发送切换请求消息，所述切换请求消息用于指示将终端设备的第一会话从所述源基站切换至所述至目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终 端设备对应的会话；
    通过所述通信接口从所述目标基站接收切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
  20. 如权利要求19所述的基站，其特征在于，所述处理器还用于通过所述通信接口从所述目标基站接收第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
  21. 如权利要求20所述的基站，其特征在于，所述处理器还用于通过所述通信接口从所述目标基站接收第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
  22. 如权利要求21所述的基站，其特征在于，所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别QoS流信息。
  23. 如权利要求19至22中任一项所述的基站，其特征在于，所述处理单元还用于通过所述通信接口向所述终端设备发送第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流。
  24. 如权利要求23所述的基站，其特征在于，所述第五信息承载于第一无线资源控制RRC消息中，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站。
  25. 如权利要求19至24中任一项所述的基站，其特征在于，所述处理器还用于通过所述通信接口从所述目标基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载；所述源基站向所述终端设备发送所述第六信息。
  26. 如权利要求19至25中任一项所述的基站，其特征在于，所述处理器还用于通过所述通信接口向所述目标基站发送第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
  27. 如权利要求26所述的基站，其特征在于，在向所述目标基站发送第一数据方面，所述处理器具体用于通过会话隧道向所述目标基站发送所述第一数据。
  28. 一种基站，其特征在于，所述基站为目标基站，包括：
    通信接口，
    存储器，用于存储指令，
    处理器，与所述存储器和所述通信接口分别相连，用于执行所述存储器存储的所述指令，以在执行所述指令时执行如下步骤：
    通过所述通信接口从源基站接收切换请求消息，所述切换请求消息用于指示将终端设备从所述源基站切换至所述目标基站，所述切换请求消息包括第一信息，所述第一信息包括第一会话的至少一个服务质量QoS流的信息，所述第一会话为所述终端设备对应的会话；
    通过所述通信接口向所述源基站发送切换请求响应消息，所述切换请求响应消息包括第二信息，所述第二信息用于指示所述目标基站允许接受所述第一会话的第一QoS流，所述至少一个QoS流包括所述第一QoS流。
  29. 如权利要求28所述的基站，其特征在于，所述处理器还用于通过所述通信接口向所述源基站发送第三信息，所述第三信息用于指示所述目标基站拒绝接受所述第一会话的第二QoS流，所述至少一个QoS流包括所述第二QoS流。
  30. 如权利要求29所述的基站，其特征在于，所述处理器还用于通过所述通信接口向所述源基站发送第四信息，所述第四信息用于指示所述第二QoS流被拒绝的原因。
  31. 如权利要求30所述的基站，其特征在于，所述第二QoS流被拒绝的原因包括以下至少一项：资源不足、不支持的QoS流信息、无法识别QoS流信息、无法识别QoS流信息。
  32. 如权利要求28至31中任一项所述的基站，其特征在于，所述处理器还用于通过所述通信接口向所述源基站发送第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
  33. 如权利要求28至32中任一项所述的基站，其特征在于，所述处理器还用于从所述源基站接收第一数据，所述第一数据为所述源基站从核心网接收的对应于所述第一会话中所述第一QoS流的数据。
  34. 如权利要求28至33中任一项所述的基站，其特征在于，在从所述源基站接收第一数据方面，所述处理器具体用于通过会话隧道从所述源基站接收所述第一数据。
  35. 一种终端设备，其特征在于，包括：
    通信接口，
    存储器，用于存储指令，
    处理器，与所述存储器和所述通信接口分别相连，用于执行所述存储器存储的所述指令，以在执行所述指令时执行如下步骤：
    通过所述通信接口从源基站接收第一无线资源控制RRC消息，所述第一RRC消息用于指示所述终端设备从所述源基站切换至所述目标基站，所述第一RRC消息包括第五信息，所述第五信息用于指示所述目标基站允许接受所述第一会话的所述第一QoS流；
    通过所述通信接口向所述目标基站发送第一RRC响应消息，所述第一RRC响应消息用于响应所述第一RRC消息。
  36. 如权利要求35所述的终端设备，其特征在于，所述处理器还用于通过所述通信接口从所述源基站接收第六信息，所述第六信息用于指示所述第一QoS流与所述第一会话的第二承载之间的映射关系，所述第二承载为所述终端设备与所述目标基站之间的承载。
PCT/CN2018/099713 2017-08-11 2018-08-09 通信方法、基站、终端设备和系统 Ceased WO2019029643A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18843499.7A EP3661253B1 (en) 2017-08-11 2018-08-09 Communication method, base station, terminal device and system
US16/786,532 US11696202B2 (en) 2017-08-11 2020-02-10 Communication method, base station, terminal device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710687720.3A CN109392004B (zh) 2017-08-11 2017-08-11 通信方法、基站、终端设备和系统
CN201710687720.3 2017-08-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/786,532 Continuation US11696202B2 (en) 2017-08-11 2020-02-10 Communication method, base station, terminal device, and system

Publications (1)

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

Family

ID=65273243

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099713 Ceased WO2019029643A1 (zh) 2017-08-11 2018-08-09 通信方法、基站、终端设备和系统

Country Status (4)

Country Link
US (1) US11696202B2 (zh)
EP (1) EP3661253B1 (zh)
CN (1) CN109392004B (zh)
WO (1) WO2019029643A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111726843A (zh) * 2020-05-29 2020-09-29 新华三技术有限公司成都分公司 一种建立会话的方法、一种设备、一种存储介质
WO2021026818A1 (zh) * 2019-08-14 2021-02-18 华为技术有限公司 一种小区切换的方法、系统及设备
WO2021109474A1 (en) * 2020-05-19 2021-06-10 Zte Corporation Methods and systems for multicast data forwarding during mobility procedures in wireless communication networks

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113261340B (zh) * 2019-04-01 2022-10-18 Oppo广东移动通信有限公司 传输信息的方法、终端设备、基站和核心网设备
CN110677889B (zh) * 2019-09-24 2021-11-23 京信网络系统股份有限公司 数据传输方法、装置、接入网设备和可读存储介质
WO2021114107A1 (zh) * 2019-12-10 2021-06-17 华为技术有限公司 一种数据传输方法及装置
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)
CN121908343A (zh) * 2020-05-29 2026-04-21 北京三星通信技术研究有限公司 支持切换的方法和设备
CN114071578B (zh) * 2020-07-30 2025-11-11 维沃移动通信有限公司 数据传输方法、装置、核心网设备及接入网侧设备
CN114079870B (zh) * 2020-08-13 2023-06-02 华为技术有限公司 通信方法及装置
CN112235777B (zh) * 2020-10-16 2022-11-29 展讯通信（上海）有限公司 信息处理方法及装置
GB2604685A (en) * 2020-10-30 2022-09-14 Samsung Electronics Co Ltd Improvements in and relating to Self-Organised Networks (SONs)
CN116114309A (zh) * 2020-12-18 2023-05-12 华为技术有限公司 数据传输方法、通信装置及通信系统
CN114916005A (zh) * 2021-02-09 2022-08-16 展讯通信（上海）有限公司 传输方法及装置
CN115915257A (zh) * 2021-08-19 2023-04-04 中国移动通信有限公司研究院 一种传输方法、装置、设备及可读存储介质
CN115708383A (zh) * 2021-08-20 2023-02-21 展讯通信（上海）有限公司 基于多模态业务的小区切换方法及相关装置
CN115767652A (zh) * 2021-09-03 2023-03-07 中兴通讯股份有限公司 站点切换方法、基站、存储介质
CN116367209A (zh) * 2021-12-28 2023-06-30 华为技术有限公司 通信方法、装置、存储介质及计算机程序产品
CN114501511B (zh) * 2022-02-15 2025-03-21 华为技术有限公司 测量方法和测量装置
CN116801260A (zh) * 2022-03-15 2023-09-22 维沃移动通信有限公司 多模态业务实现方法、装置及通信设备
CN115190556B (zh) * 2022-06-10 2024-02-27 联想(北京)有限公司 通信方法、源基站、目标基站、通信系统及存储介质
EP4706290A1 (en) * 2023-05-19 2026-03-11 Google Llc Managing protocol data unit sets in handover scenarios

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1930903A (zh) * 2004-03-05 2007-03-14 Lg电子株式会社 在切换期间传送服务信息的移动宽带无线接入系统
CN102131252A (zh) * 2010-01-14 2011-07-20 华为技术有限公司 服务质量信息处理方法、装置以及系统
CN102316540A (zh) * 2010-07-08 2012-01-11 中兴通讯股份有限公司 一种切换时的接入控制方法及系统
WO2017121217A1 (zh) * 2016-01-16 2017-07-20 华为技术有限公司 一种切换的方法、基站及终端设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101467802B1 (ko) 2007-04-12 2014-12-04 엘지전자 주식회사 광대역 무선접속 시스템에서 핸드오버 수행 및 지원 방법
JP6027342B2 (ja) * 2012-06-01 2016-11-16 株式会社Ｎｔｔドコモ 無線通信システム、無線基地局及び通信方法
CN103517358B (zh) * 2012-06-28 2017-02-08 电信科学技术研究院 一种接入点切换过程中传输数据的方法、系统和设备
EP3031288A1 (en) * 2013-08-08 2016-06-15 Telefonaktiebolaget LM Ericsson (publ) S-gw relocation and qos change without mobility
EP3958615A1 (en) * 2016-08-10 2022-02-23 NEC Corporation Radio access network node, radio terminal, core network node, and method therefor
CN108024294B (zh) * 2016-11-02 2020-08-07 中兴通讯股份有限公司 切换方法及装置
WO2018124810A1 (ko) * 2016-12-29 2018-07-05 엘지전자 주식회사 Drb를 확립하는 방법 및 장치
EP3361777B1 (en) * 2017-02-09 2022-02-09 HTC Corporation Device and method for handling evolved long-term evolution network
CN117676719A (zh) * 2017-08-10 2024-03-08 北京三星通信技术研究有限公司 一种数据流的操作控制的方法及设备
CN107302777A (zh) * 2017-08-28 2017-10-27 北京北方烽火科技有限公司 一种通信切换方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1930903A (zh) * 2004-03-05 2007-03-14 Lg电子株式会社 在切换期间传送服务信息的移动宽带无线接入系统
CN102131252A (zh) * 2010-01-14 2011-07-20 华为技术有限公司 服务质量信息处理方法、装置以及系统
CN102316540A (zh) * 2010-07-08 2012-01-11 中兴通讯股份有限公司 一种切换时的接入控制方法及系统
WO2017121217A1 (zh) * 2016-01-16 2017-07-20 华为技术有限公司 一种切换的方法、基站及终端设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "QoS control for unstructured PDU sessions", 3GPP SA WG2 MEETING #122 , S2-174690, 30 June 2017 (2017-06-30), XP051303531 *
HUAWEI ET AL.: "TS 23.502: Handling PDU sessions rejected by RAN during han- dover", SA WG2 MEETING #121, S2-173138, 19 May 2017 (2017-05-19), XP051268605 *
See also references of EP3661253A4

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021026818A1 (zh) * 2019-08-14 2021-02-18 华为技术有限公司 一种小区切换的方法、系统及设备
WO2021109474A1 (en) * 2020-05-19 2021-06-10 Zte Corporation Methods and systems for multicast data forwarding during mobility procedures in wireless communication networks
JP2023526074A (ja) * 2020-05-19 2023-06-20 中興通訊股▲ふん▼有限公司 無線通信ネットワークにおけるモビリティプロシージャの間のマルチキャストデータ自動転送のための方法およびシステム
JP7635261B2 (ja) 2020-05-19 2025-02-25 中興通訊股▲ふん▼有限公司 無線通信ネットワークにおけるモビリティプロシージャの間のマルチキャストデータ自動転送のための方法およびシステム
US12513586B2 (en) 2020-05-19 2025-12-30 Zte Corporation Methods and systems for multicast data forwarding during mobility procedures in wireless communication networks
CN111726843A (zh) * 2020-05-29 2020-09-29 新华三技术有限公司成都分公司 一种建立会话的方法、一种设备、一种存储介质
CN111726843B (zh) * 2020-05-29 2023-11-03 新华三技术有限公司成都分公司 一种建立会话的方法、一种设备、一种存储介质

Also Published As

Publication number Publication date
EP3661253A4 (en) 2020-07-29
US20200178145A1 (en) 2020-06-04
EP3661253B1 (en) 2025-10-08
US11696202B2 (en) 2023-07-04
EP3661253A1 (en) 2020-06-03
CN109392004B (zh) 2021-09-21
CN109392004A (zh) 2019-02-26

Similar Documents

Publication Publication Date Title
US11696202B2 (en) Communication method, base station, terminal device, and system
EP3737145B1 (en) Communication method, device and system
CN109923891B (zh) 在无线通信系统中应用反映型服务质量的方法及其设备
CN113411850B (zh) 切换方法和设备
US12464464B2 (en) Managing a ue preferred configuration
CN104813725B (zh) 数据传输装置和方法
US11457392B2 (en) Handover method and apparatus
WO2023051634A1 (zh) 通信方法及装置
CN109246757B (zh) 一种新型服务质量架构在双连接系统的配置方法及装置
EP3664507B1 (en) Communication methods for a master base station and a terminal
US20190230682A1 (en) Data transmission method, apparatus, and system
CN107005907A (zh) 用于辅基站切换的方法、网络设备和用户设备
CN110351890B (zh) 集中式单元-分布式单元架构下的通信方法、通信设备
CN108156633A (zh) 数据流重映射方法及装置和用户设备、ran设备
CN110505714A (zh) 多链接通信方法、设备和终端
KR102459063B1 (ko) 전송 장치 및 전송 장치에서 통신을 처리하기 위해 수행되는 방법
WO2022011659A1 (en) Data forwarding in centralized unit and distributed unit split architectures
CN111294980A (zh) 无线承载建立方法及装置
US20250056359A1 (en) Method and apparatus for handover associated with usage of a pdu set
US20250227606A1 (en) Methods, devices, and systems for performing network slice replacement during mobility
EP4165901B1 (en) Data forwarding for user equipment with data transmission
CN103517447B (zh) 传输数据的方法和装置
WO2025025177A1 (en) A method to solve timeout problem of pdu session split
CN121098801A (zh) 用于队列管理的装置和方法

Legal Events

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

Ref document number: 18843499

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018843499

Country of ref document: EP

Effective date: 20200225

WWG Wipo information: grant in national office

Ref document number: 2018843499

Country of ref document: EP