WO2018202148A1 - 一种数据传输方法、相关设备及系统 - Google Patents

一种数据传输方法、相关设备及系统 Download PDF

Info

Publication number
WO2018202148A1
WO2018202148A1 PCT/CN2018/085663 CN2018085663W WO2018202148A1 WO 2018202148 A1 WO2018202148 A1 WO 2018202148A1 CN 2018085663 W CN2018085663 W CN 2018085663W WO 2018202148 A1 WO2018202148 A1 WO 2018202148A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
identifier
message
address
transmission
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/085663
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 EP18794755.1A priority Critical patent/EP3614735B1/en
Publication of WO2018202148A1 publication Critical patent/WO2018202148A1/zh
Priority to US16/672,819 priority patent/US11368882B2/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/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data transmission method, related device, and system.
  • RRC radio resource control
  • RNA Notification Area
  • RAN Radio Access Network
  • the network needs to be notified after the RNA.
  • the RNA is composed of one cell or multiple cells. If multiple cells are used, the multiple cells belong to the same base station, and may belong to different base stations.
  • the different base stations may be the same radio access type (Radio Access Type, The base station of the RAT) may also be a base station of a different RAT.
  • the terminal in the RRC deactivated state performs downlink synchronization with the new serving base station (ie, the non-resident base station, the second base station) through cell reselection. If the terminal in the RRC deactivated state needs to perform downlink data transmission, the terminal first establishes an RRC connection with the new serving base station (ie, the second base station), and then moves the previous camping base station (ie, the first base station) to pass the data. The Xn interface is transmitted to the new serving base station, and the new serving base station transmits the data to the terminal.
  • the new serving base station ie, the non-resident base station, the second base station
  • the terminal first establishes an RRC connection with the new serving base station (ie, the second base station), and then moves the previous camping base station (ie, the first base station) to pass the data.
  • the Xn interface is transmitted to the new serving base station, and the new serving base station transmits the data to the terminal.
  • the terminal If the terminal in the RRC deactivation state needs to perform uplink data transmission, the terminal first transmits the uplink data to the new serving base station, and then the new serving base station transmits the uplink data to the camping base station through the Xn interface, and then transmits the uplink data to the camping base station. To the core network.
  • the terminal in the RRC connected state will switch from the source base station (ie, the first base station) to the target base station (ie, the second base station) by handover.
  • the terminal in the connected state will maintain data transmission with the source base station and the target base station simultaneously for a period of time.
  • the target base station transmits the received uplink data to the source base station through the Xn interface, and then the source base station transmits the uplink data to the core network.
  • the first base station and the second base station can perform data communication between each other through the Xn interface, but perform data transmission for the terminal in the RRC deactivated state and the terminal in the RRC connected state during the handover process.
  • the transmission of uplink data does not give a specific data communication method. In this way, when the first base station and the second base station perform mutual data transmission, for the transmitting base station, it is not known how to identify the data to be transmitted. Similarly, for the receiving base station, it is not known what data is sent by the current transmitting base station, which is likely to cause communication confusion.
  • the present invention discloses a data transmission method, a related device, and a system, which can solve the problem that when the first base station and the second base station perform mutual data transmission in the prior art, the base station of the transceiver base station may not know how to identify the data to be transmitted, and know the current data. Problems such as transmitted data improve the efficiency of data transmission.
  • a data transmission method comprising:
  • the first base station sends a second message to the second base station, where the second message carries at least one address, and the address is associated with the data.
  • the first message may carry data transmission indication information, where the data transmission indication information is used to indicate that the second base station needs to transmit data to the first base station.
  • the first base station may allocate at least one address to the data to be transmitted by the second base station, and notify the first base station.
  • the number of addresses is determined by the second base station according to an identifier of the at least one first transmission granularity and a mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity.
  • the number of identifiers of the second transmission granularity Specifically, if the data of the at least one first transmission granularity (that is, the identifier of the at least one first transmission granularity) needs to be transmitted to the first base station, the second base station may be configured according to different transmission granularities.
  • the mapping relationship between the identifiers determines the number of identifiers of the second transmission granularity actually transmitted.
  • the mapping relationship is a correspondence between data of different transmission granularities, for example, in which specific PDU session a certain QoS flow corresponds.
  • the first message carries an identifier of the at least one first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity, where the first transport granularity is identified by And the first base station needs to send the data corresponding to the identifier of the first transmission granularity to the first base station; before the first base station sends the second message to the second base station, the method further includes: Determining, by the first base station, the number of identifiers of the second transmission granularity according to the identifier of the at least one first transmission granularity and the mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity; The first base station allocates the same number of addresses as the number of identifiers of the second transmission granularity to the data to be transmitted according to the number of identifiers of the second transmission granularity.
  • the data indication information may be specifically used to indicate, by the second base station, which first transmission granularity data (ie, at least one identifier of the first transmission granularity) is currently required to be transmitted by the first base station by using the first transmission granularity, and further Indicates a mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity, where the first base station may sequentially determine the number of identifiers of the second transmission granularity when actually transmitting data according to the second transmission granularity. And allocating the same number of addresses as the number of identifiers of the second transmission granularity.
  • first transmission granularity data ie, at least one identifier of the first transmission granularity
  • each of the data of the second transmission granularity to be transmitted (ie, the identifier of each second transmission granularity) can be assigned an address to ensure that when the data of the second transmission granularity is actually transmitted,
  • the addresses can be identified one by one, which improves the efficiency of data transmission between the first base station and the second base station.
  • the first message carries an identifier of the at least one first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity, where the first transport granularity is identified by And the first base station needs to send the data corresponding to the identifier of the first transmission granularity to the first base station; before the first base station sends the second message to the second base station, the method further includes: Determining, by the first base station, an identifier of the at least one second transmission granularity according to the identifier of the at least one first transmission granularity and the mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity; The first base station allocates a corresponding address to each of the identifiers of the at least one second transmission granularity; the second message further carries an identifier of a second transmission granularity corresponding to each of the at least one address
  • the first base station may allocate an address for each identifier of the second transmission granularity, and the second transmission granularity is different.
  • the identifier corresponds to a different address.
  • An address is allocated not only to the data to be transmitted in the second base station, but also a mapping relationship between the identifier of the second transmission granularity and the address.
  • each of the data of the second transmission granularity to be transmitted (ie, the identifier of each second transmission granularity) can be assigned an address to ensure that when the data of the second transmission granularity is actually transmitted,
  • the addresses can be identified one by one, which improves the efficiency of data transmission between the first base station and the second base station.
  • the first message carries an identifier of at least one second transmission granularity
  • the identifier of the second transmission granularity is used to identify that the second base station needs to send the first base station to the first base station.
  • the data corresponding to the identifier of the second transmission granularity, before the first base station sends the second message to the second base station, the method further includes: the first base station is each of the identifiers of the at least one second transmission granularity Identifying an address corresponding to the allocation; the second message further carries an identifier of a second transmission granularity corresponding to each of the at least one address, and the number of the identifier of the at least one second transmission granularity and the number of the at least one address The same amount.
  • each of the data of the second transmission granularity to be transmitted (ie, the identifier of each second transmission granularity) can be assigned an address to ensure that when the data of the second transmission granularity is actually transmitted,
  • the addresses can be identified one by one, which improves the efficiency of data transmission between the first base station and the second base station.
  • the method further includes: the first base station receiving a third message sent by the second base station, where the third message carries a second transmission granularity corresponding to each of the at least one address Logo.
  • the first base station can learn the address corresponding to the identifier of the second transmission granularity to be transmitted in the second base station, and can ensure that when the data of the second transmission granularity is actually transmitted,
  • the data of the second transmission granularity can be identified by using the address, and the efficiency of data transmission between the first base station and the second base station is improved.
  • a data transmission method comprising:
  • the second base station sends a first message to the first base station, where the first message is used to indicate that the second base station needs to perform data transmission;
  • the first message may carry data indication information, where the data indication information may be used to indicate that the second base station needs to perform data transmission.
  • the data indication information may be specifically used to indicate which second transmission granularity or data of the first transmission granularity exists in the second base station to be transmitted.
  • the first message carries a number of addresses
  • the number of at least one address in the second message is the same as the number of addresses in the first message.
  • the number of addresses is determined according to a transmission granularity.
  • the first message carries an identifier of the at least one first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity, where the first transport granularity is identified by
  • the data corresponding to the identifier of the first transmission granularity needs to be sent to the first base station; the number of at least one address in the second message and at least one of the first messages
  • the number of identifiers of the second transmission granularity is the same; wherein the number of identifiers of the second transmission granularity is an identifier according to the at least one first transmission granularity, and an identifier of the first transmission granularity and a second transmission
  • the mapping relationship of the granularity of the identification is determined.
  • the first message carries an identifier of the at least one first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity, where the first transport granularity is identified by
  • the second base station needs to send the data corresponding to the identifier of the first transmission granularity to the first base station;
  • the second message further carries an identifier of the second transmission granularity corresponding to each of the at least one address,
  • the number of the at least one address in the second message is the same as the number of the identifiers of the at least one first transmission granularity in the first message; wherein the identifier of the second transmission granularity is according to the at least one
  • the identifier of a transmission granularity and the mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity are determined.
  • the first message carries an identifier of the at least one first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity, where the first transport granularity is identified by
  • the second base station needs to send the data corresponding to the identifier of the first transmission granularity to the first base station; the second message further carries an identifier of the second transmission granularity corresponding to each of the at least one address,
  • the number of the at least one address in the second message is the same as the number of identifiers of the at least one second transmission granularity in the first message.
  • the second base station needs to transmit data corresponding to the identifier of the at least one second transmission granularity to the first base station, where the method further includes: the second base station is the at least Each of the addresses is assigned an identifier of the second transmission granularity, and the different addresses correspond to different identifiers of the second transmission granularity; the second base station sends a third message to the first base station, where the third The message carries an identifier of a second transmission granularity corresponding to each of the at least one address.
  • the second base station knows which second transmission granularity data (ie, the identifier of the at least one second transmission granularity) that the user wants to send to the first base station, and the second base station may be the Each of the at least one address in the two messages is assigned an identifier of a corresponding second transmission granularity. In this way, when the data of the second transmission granularity is actually transmitted, the address can be used to identify one by one, which improves the efficiency of data transmission between the first base station and the second base station.
  • second transmission granularity data ie, the identifier of the at least one second transmission granularity
  • the first message is further used to indicate that the second base station sends data to be transmitted to the first base station according to a second transmission granularity.
  • the first message carries a number of addresses, the number of at least one address in the second message, and an address in the first message The number is the same.
  • the first base station allocates, for the data to be transmitted by the second base station, the same number of addresses as the number of addresses.
  • the number of addresses is determined based on a transmission granularity. Specifically, if the first base station and the second base station actually perform data transmission by using the second transmission granularity, the number of the addresses is the number of identifiers of the second transmission granularity determined by the second base station. That is, the number of data that the second base station actually sends to the first base station to transmit the second transmission granularity.
  • the first transmission granularity or the second transmission granularity includes any one of the following: a quality of service QoS flow, a protocol data unit PDU session, data
  • the radio carries the DRB.
  • a data transmission method comprising:
  • the first base station sends a first message to the second base station, where the first message carries an address corresponding to the first identifier of the at least one first transmission granularity, where the address is used to identify the first base station and the second base station Data of the first transmission granularity transmitted between;
  • the second base station Receiving a second message sent by the second base station, where the second message carries a second identifier of a first transmission granularity, and the second identifier is one or more of the at least one first identifier.
  • the method before the first base station sends the first message to the second base station, the method further includes: the first base station assigning, for each first identifier in the first identifier of the at least one first transmission granularity Corresponding addresses, different addresses corresponding to different first identifiers of the first transmission granularity.
  • the first identifier or the second identifier of the first transmission granularity may include any one of the following: a QoS flow identifier, a PDU session identifier, and a DRB identifier.
  • a data transmission method comprising:
  • the first message sent by the first base station, where the first message carries an address corresponding to the first identifier of the at least one first transmission granularity, where the address is used to identify the first base station and the second Data of the first transmission granularity transmitted between base stations;
  • the second base station sends a second message to the first base station, where the second message carries a second identifier of the first transmission granularity, and the second identifier is one or more of the at least one first identifier .
  • the method further includes: the second base station according to the air interface resource And selecting, by the first identifier of the first transmission granularity, the second identifier.
  • the air interface resource information may include time-frequency resource information of the air interface, and the like.
  • the first transmission granularity may include any one of the following: a quality of service QoS flow, a protocol data unit PDU session, and a data radio bearer DRB.
  • a first base station comprising functional units for performing the method of the above first aspect.
  • a second base station comprising functional units for performing the method of the second aspect above.
  • a first base station comprising functional units for performing the method of the third aspect above.
  • a second base station comprising functional units for performing the method of the above fourth aspect.
  • a first base station comprising: a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, the processor is configured to execute the instruction, The communication interface is for communicating with other devices under the control of the processor; wherein the processor executes the instructions described above to perform the method described in the first aspect above.
  • a second base station comprising: a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, the processor is configured to execute the instruction, The communication interface is for communicating with other devices under the control of the processor; wherein the processor executes the instructions to perform the method described in the second aspect above.
  • a first base station comprising: a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, the processor is configured to execute the instruction, The communication interface is for communicating with other devices under the control of the processor; wherein the processor executes the instructions to perform the method described in the third aspect above.
  • a second base station comprising: a memory, a communication interface, and a processor coupled to the memory and a communication interface; the memory is configured to store an instruction, the processor is configured to execute the instruction, The communication interface is for communicating with other devices under the control of the processor; wherein the processor executes the instructions to perform the method described in the fourth aspect above.
  • a data transmission system including a first base station and a second base station, where the first base station may be the first base station described in the foregoing fifth aspect or the ninth aspect;
  • the second base station may be the second base station described in the sixth aspect or the tenth aspect.
  • a data transmission system including a first base station and a second base station, where the first base station may be the first base station described in the seventh aspect or the eleventh aspect;
  • the second base station may be the second base station described in the eighth aspect or the twelfth aspect.
  • a computer readable storage medium storing program code for task processing.
  • the program code includes instructions for performing the method described in the first aspect above.
  • a computer readable storage medium storing program code for task processing.
  • the program code includes instructions for performing the method described in the second aspect above.
  • a computer readable storage medium storing program code for task processing.
  • the program code includes instructions for performing the method described in the third aspect above.
  • a computer readable storage medium storing program code for task processing.
  • the program code includes instructions for performing the method described in the fourth aspect above.
  • the foregoing solution can solve the problem that when the first base station and the second base station perform data transmission in the prior art, one end base station does not know how to identify data to be transmitted, and the other end base station does not know what data is currently received, and the like. The efficiency of data transmission.
  • FIG. 1 is a schematic diagram of a network frame according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a downlink data transmission method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of still another downlink data transmission method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of an uplink data transmission method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of still another data transmission method according to an embodiment of the present invention.
  • FIG. 7A is a schematic structural diagram of a first base station according to an embodiment of the present invention.
  • FIG. 7B is a schematic structural diagram of still another first base station according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a second base station according to an embodiment of the present disclosure.
  • FIG. 8B is a schematic structural diagram of still another second base station according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a data transmission system according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a network framework according to an embodiment of the present invention.
  • the network framework diagram includes a core network, a first base station, a second base station, and a user equipment (UE).
  • the network framework diagram may also include other base stations, such as the third base station shown in the figure.
  • the terminal after the UE establishes an RRC connection with the first base station and the terminal is in an RRC connected state, if the terminal moves from the first base station to the coverage of the second base station and the first base station due to the mobility of the terminal It is decided to switch the terminal to the second base station, where the first base station is the source base station and the second base station is the target base station.
  • the first base station converts the terminal from the RRC connection state by using a state transition process.
  • the terminal and the first base station retain the same (or part of) terminal context information as when connected.
  • the terminal in the RRC deactivated state does not need to report measurement information, such as channel quality feedback information, to the network side in real time.
  • the first base station is a camping base station (Anchor gNodeB, AgNB), and the second base station is a serving base station of the terminal in the RRC deactivated state, in order to interact with the network, for example, to transmit uplink data or perform RNA update. (New gNodeB, NgNB).
  • the terminal context information in the RRC connection state may include information such as capability information of the terminal, bearer configuration information of the terminal, and the like, which are not limited by the present invention.
  • the serving base station refers to a new base station that is moved from the camping base station to the cell when the UE is in the RRC deactivated state, that is, the base station where the UE is currently located.
  • There may be mutual communication between the UE and the serving base station for example, the UE may receive a broadcast message sent by the serving base station, and the UE may also perform communication interaction with the network side (core network) through the serving base station.
  • the network side core network
  • the core network may include an AMF network element (Access and Mobility Management Function, Chinese: access and mobility management functions).
  • AMF network element is a core network control plane network element, and provides user (UE) mobility management and access management functions.
  • the first base station, the second base station, and the third base station may refer to a 3G base station (NodeB), a 4G base station (eNodeB, such as an eLTE base station), or a 5G base station (gNodeB), and the present invention Not limited.
  • NodeB 3G base station
  • eNodeB 4G base station
  • gNodeB 5G base station
  • An eLTE base station (ie, a 4G base station) refers to an E-UTRAN base station (Evolved UMTS Terrestrial Radio Access Network) that supports connection to a 5G core network.
  • the eLTE base station can support the RRC connection status, the RRC deactivation status, and the like of the terminal UE.
  • the base station, the core network, and the terminal UE all retain corresponding terminal context information, and the base station and the core network reserve corresponding connections for the terminal. That is, when the UE switches from the RRC deactivation state to the RRC connection state, there is no need to reactivate the communication link between the base station (such as the camping base station AgNB) and the core network control plane network element (such as the AMF network element).
  • the base station such as the camping base station AgNB
  • the core network control plane network element such as the AMF network element
  • the first base station, the second base station, and the third base station can each perform data communication with the core network through an interface between the base station and the core network.
  • the first base station and the second base station can perform mutual data communication through an Inter base station (Inter-BS) interface (such as an Xn interface).
  • Inter-BS Inter base station
  • the NgNB can transmit the uplink data to the camping base station AgNB through the Xn interface, and transmit the uplink data to the core network by the AgNB. If the downlink data needs to be transmitted to the camping base station AgNB, the core network may send the downlink data to the camping base station AgNB, and the camping base station sends the downlink data to the serving base station NgNB through the Xn interface.
  • FIG. 2 is a schematic diagram of a data transmission method according to an embodiment of the present invention. The method includes the following implementation steps.
  • the terminal UE in the RRC deactivated state transmits data to the first base station, and the terminal moves from the first base station to the second base station due to the mobility of the terminal. If there is data to be transmitted between the terminal and the core network, mutual data communication can be performed through the communication link of the terminal->second base station->first base station->core network. Therefore, when the first base station and the second base station are in actual data communication, the second base station needs to acquire corresponding address information of the first base station, and is used by the second base station to transmit data on an interface between the base stations (for example, an Xn interface).
  • an interface between the base stations for example, an Xn interface
  • Step S201 The second base station sends a first message to the first base station, where the first message is used to indicate that the second base station needs to perform data transmission.
  • the first base station receives the first message.
  • the first message may specifically indicate that data of the at least one first transmission granularity needs to be transmitted from the first base station to the second base station through an interface between the base stations (eg, an Xn interface), where the first transmission granularity may be It is a Quality of Service Flow (QoS Flow), a Packet Data Unit Session (PDU Session), and a Data Radio Bearer (DRB). That is, the first message may carry at least one identifier of the first transmission granularity, such as flow1, Session1, and the like. The identifier of the first transmission granularity is used to identify which first transmission granularity data of the second base station needs to be transmitted from the first base station to the second base station through the interface between the base stations.
  • QoS Flow Quality of Service Flow
  • PDU Session Packet Data Unit Session
  • DRB Data Radio Bearer
  • the first message may indicate which specific QoS flow needs to transmit data, and may indicate which specific DRB needs to perform data transmission, and may also indicate which specific PDU session needs to transmit data.
  • the first message may further include information that the first base station wants the number of addresses allocated by the second base station, the mapping relationship between data having different transmission granularities, and the like. This will be specifically explained in the following examples.
  • Step S202 The first base station allocates at least one address for data to be transmitted by the second base station, where the address is associated with the data.
  • the first base station may allocate at least one address at a second transmission granularity for data to be transmitted by the second base station.
  • the second transmission granularity refer to the related description of the first transmission granularity in the foregoing embodiment, and details are not described herein again.
  • the allocated address may be used to identify the QoS flow transmitted by the Xn interface, that is, the first base station may identify which QoS flow the data packet received from the Xn interface belongs to by the address; and may also be used to identify the Xn interface transmission.
  • the DRB that is, through the address, the first base station can identify which DRB the data packet received from the Xn interface belongs to; and can also be used to identify the PDU session transmitted by the Xn interface, that is, the first base station can recognize that the data packet is received from the Xn interface. Which PDU session the packet belongs to.
  • the address may be an Internet Protocol Address (IP Address), which may be used for data transmission of the Xn interface data plane.
  • IP Address Internet Protocol Address
  • a tunnel port identifier such as a tunnel port identifier of a General Packet Radio Service Tunneling Protocol (GTP)
  • GTP General Packet Radio Service Tunneling Protocol
  • the transceiver base station can identify the session, data radio bearer or stream that needs to be transmitted on the interface between the base stations (for example, the Xn interface) through the address (may also include the tunnel port identifier, which is collectively referred to as an address in the present case).
  • This address can be used for the transmission of uplink or downlink data of an interface between base stations (for example, an Xn interface).
  • the address involved in the present invention may include not only an Internet Protocol address, but also a tunnel port identifier, or another address used for data transmission between interfaces of the base station, which is not limited in the embodiment of the present invention.
  • Step S203 The first base station sends a second message to the second base station, where the second message carries the at least one address.
  • the second base station receives the second message.
  • the first base station notifies the first base station of at least one address allocated for the data to be transmitted in the form of a second message.
  • the second message may further carry an identifier of a second transmission granularity corresponding to each of the at least one address. That is, the binding/mapping relationship (one-to-one mapping) between the identifiers of the respective second transmission granularities and the respective addresses is carried.
  • An address corresponding to a second transmission granularity that is, an address is used to identify data of a specific second transmission granularity that is sent by the second base station to the first base station through the base station interface, that is, which specific one is used to identify
  • the second transmission granularity (such as QoS flow) needs to be transmitted through an interface between base stations (such as the Xn interface).
  • the first message may be further used to indicate that the second base station transmits data to the first base station according to the second transmission granularity.
  • the protocol specifies that the base stations of the transmitting and receiving terminals are aware of the transmission granularity used when actually communicating, and the second transmission granularity is assumed.
  • the second base station may not notify the first base station of the second transmission granularity used in actual communication by using the first message.
  • the second transmission granularity may be a transmission unit used when the second base station actually sends data to be transmitted to the first base station.
  • the first transmission granularity may refer to the second base station notifying the first base station of the transmission units corresponding to the data to be transmitted that exist in the second base station.
  • the first message is further configured to indicate that data of the at least one second transmission granularity in the second base station needs to be transmitted by the first base station to the second base station through an interface between the base stations (eg, an Xn interface). . That is, the first message may further carry an identifier of the at least one second transmission granularity, where the identifier of the second transmission granularity is used to identify which specific second transmission granularity (such as a PDU session) the second base station needs to pass. To transmit data from the first base station to the second base station.
  • each of the at least one address is used to identify that the data to be transmitted has different data or data streams in the second transmission granularity form, that is, different addresses are used to identify the location.
  • Different data or data streams of the second transmission granularity in the transmitted data are mentioned.
  • the address 1 is used to identify a certain data stream having a Session granularity in the data to be transmitted, such as Session1 that needs to perform data transmission.
  • the first message if the first message carries the number of addresses, that is, the first message is used to indicate/notify the second base station that the number of addresses allocated by the first base station is required ( That is, the number of addresses, the first base station may allocate the same number of addresses as the number of addresses to the data to be transmitted.
  • the number of addresses may be determined based on the transmission granularity.
  • the number of the addresses is determined by the second base station according to an identifier of the at least one first transmission granularity, and a mapping relationship between the identifier of the first transmission granularity and the identifier of the first transmission granularity.
  • the number of identifiers of the second transmission granularity That is, the number of data of the at least one second transmission granularity that the second base station wants to send to the first base station.
  • the mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity may be understood as a mapping relationship between data of each second transport granularity and data of each first transport granularity.
  • the second base station establishes three session sessions for data transmission, which are Session1 data to Session3 data. Among them, three flow flow data are created under the Session1 data, which are flow1 data to flow3 data. Below the Seeion2 data, three flow flow data are created, which are flow4 data to flow6 data.
  • the Seeion3 data plane is created with four flow flow data, which are flow7 data to flow10 data.
  • the second transmission granularity is the session session data
  • the first transmission granularity is the flow flow data
  • the mapping relationship between the identifier of each second transmission granularity and the identifier of the first transmission granularity is also as described above, for example, Session1 data.
  • the second base station may be aware that: flow2 corresponds to Session1, and flow5 corresponds to Session2. That is, Session 1 and Session 2 are determined by the second base station to determine that it actually needs to transmit data to the first base station. At this time, it is also determined that the number of session sessions (ie, the number of addresses) that the second base station needs to send to the first base station is 2.
  • the number of addresses may be the number of data of the second transmission granularity when the second base station transmits data to the first base station according to the second transmission granularity, or the second transmission granularity.
  • the number of identifiers may be the number of data of the second transmission granularity when the second base station transmits data to the first base station according to the second transmission granularity, or the second transmission granularity.
  • step S202 if the first message is used to indicate that the second base station has data to be transmitted and transmitted to the first base station, the first base station may use the number of addresses set by default.
  • the data to be transmitted is allocated with the same number of addresses as the number of addresses.
  • the first base station may allocate the same number of addresses as the number of addresses to the data to be transmitted according to the number of addresses carried in other flow messages.
  • step S202 if the first message carries an identifier of at least one second transmission granularity, that is, the first message is used to indicate that the second base station has at least one second transmission granularity.
  • the first base station may allocate a corresponding address for each identifier in the identifier of the at least one second transmission granularity, and the identifier corresponds to a second transmission granularity identifier. . That is, the first base station may allocate a corresponding address for each of the data of the at least one second transmission granularity, and one address corresponds to data of a second transmission granularity.
  • the first base station not only configures an address for each second transmission granularity data (ie, an identifier of each second transmission granularity), but also configures a mapping relationship between the data of the second transmission granularity and the address. That is, an address corresponds to an identifier of a second transmission granularity.
  • the second base station notifies the first base station by the first message that the second base station needs to transmit data to the first base station with Session1 and Session3.
  • the first base station may respectively configure an address corresponding to Session1 and Session2, which is assumed to be address 1 and address 2.
  • the identification of the second transmission granularity here is seeion1 and seeion2.
  • Address 1 is used to identify Session 1 for data transmission
  • Address 2 is used to identify Session 2 for data transmission.
  • step S102 if the first message carries at least one identifier of the first transport granularity, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity (ie, the first transport granularity)
  • the data corresponds to which second data granularity data belongs to). That is, the first message may be specifically used to indicate that the identifier that the second base station has at least one first transmission granularity needs to transmit data through an interface between the base stations.
  • the first message is further used to indicate that the second base station actually transmits data to the first base station in the form of the second transmission granularity.
  • the first base station when the first base station determines that the second base station actually transmits data to the first base station according to the second transmission granularity, the first base station may be configured according to the at least one first transmission granularity.
  • the first A base station may allocate, for the data to be transmitted by the second base station, an address equal to the number of identifiers of the second transmission granularity.
  • the first base station may be the at least one Each of the identifiers of the second transport granularity is assigned a corresponding address.
  • the first base station After the first base station knows the identifier of the at least one second transmission granularity that the second base station needs to send to the first base station, that is, the data of the second transmission granularity to be transmitted, the first base station An address may be allocated not only for the identifier of the at least one second transmission granularity, but also a mapping/binding relationship between the identifiers of the second transmission granularities and each of the addresses (one-to-one mapping). That is, an address is used to identify data of a second transmission granularity, that is, to identify a data or data stream having a second transmission granularity.
  • the second base station notifies the first base station by using a first message that the second base station will send two flow data, flow2 and flow5, to the first base station according to the seeion granularity (ie, the second transmission granularity).
  • the mapping relationship between the identifier of the first transmission granularity and the identifier of the second granularity in the above example is cited.
  • the first base station After the first base station receives the first message, it can be learned that the flow2 data corresponds to the Session1 data, and the flow5 data corresponds to the Session2 data, that is, the first base station can determine that the second base station currently wants to send the Session1 and Session2 data to the first base station. .
  • the first base station can allocate corresponding addresses for the seeion1 and Session2 data respectively, for example, assigning address 1 to the Session1 data and assigning the address 2 to the Session2 data. Then, the first base station may use a second message to map the address assigned to the identifier of the data of the second transport granularity in the second base station and the identifier of the data of the second transport granularity to the address (Session1 data corresponds to address 1, and Session2 data corresponds to address 2) to the second base station.
  • the mapping relationship between the address and the identifier of the second transmission granularity data is not carried (ie, the at least one address Corresponding to the identification of the second transmission granularity).
  • the second base station may allocate a corresponding address for each of the identifiers of the at least one second transmission granularity.
  • the second base station may send a third message to the first base station, where the third message carries an identifier of a second transmission granularity corresponding to each of the at least one address. That is, the second base station notifies the first base station of the identifier of the second transmission granularity allocated for each of the at least one address by using the third message.
  • the first message may include a paging message, a terminal context response message, a terminal context request message, and the like
  • the second message may include a terminal context request message, a data transmission address notification message, and a terminal context response message.
  • the third message may include a data transmission address notification message, which is specifically described in the following embodiments.
  • the second base station may continue to perform the foregoing steps S201 to S203 to obtain at least one address re-allocated by the first base station, and repeat the process until the number of addresses allocated by the first base station is not less than the The number of data of the second transmission granularity to be transmitted by the transmitting end (ie, the number of identifiers of the second transmission granularity).
  • the second base station may repeatedly perform steps S201 to S203 until the number of the addresses allocated by the first base station is not less than the number of identifiers of the second transmission granularity, so as to be at least Each of the identifiers of the second transmission granularity is assigned an address.
  • the addresses allocated by the first base station for the data to be transmitted by the second base station that is, the identifier of the at least one second transmission granularity are different from each other.
  • the second base station may send a first message to the first base station to notify the second base station that the data to be transmitted needs to be transmitted.
  • the first base station may be assumed that four addresses are set by default according to the number of addresses set by default, and the same number of addresses as the number of addresses is allocated.
  • four addresses are assigned, assuming that they are assigned from address 1 to address 4.
  • the first base station may send a second message to the second base station to notify the second base station of the allocated four addresses.
  • Receiving the second message at the second base station learns that the first base station allocates 4 addresses, which is less than the number of seeion data to be transmitted (4 ⁇ 7). Therefore, the second base station needs to send the first message to the first base station again, so as to acquire the four new addresses newly allocated by the first base station for the session data to be transmitted by the second base station, which are assumed to be address 5 to address 8, respectively. At this point, 8 addresses are enough to bind and transmit 7 seeion data.
  • the second base station may allocate corresponding addresses for each of the seven seeion data, assuming that the seeion1 data corresponds to the assigned address 1, Session 2 The data corresponds to the assigned address 2, ..., and the Session 7 data corresponds to the assigned address 7.
  • the second base station may further send a third message to the first base station, to notify the first base station of the address corresponding to each of the seven seeion data.
  • a header of the address corresponding to the session data may be added in front of the session data, so that the session data corresponding to the address is identified by the address.
  • the header of the address 1 can be added before the Session1 data, so that the Session1 data is received at the first base station.
  • the second base station can be a camping base station (AgNB) and the first base station can be a serving base station (NgNB).
  • AgNB camping base station
  • NgNB serving base station
  • FIG. 3 is a schematic flowchart diagram of a downlink data transmission method, where the method includes the following implementation steps.
  • Step S301 The camping base station sends a first paging message to the serving base station, where the paging message carries the identifier information of the terminal UE, and the identifier information may uniquely indicate the terminal in the range of the RNA.
  • the serving base station receives the second paging message.
  • the first paging message may further carry downlink data indication information, where the downlink data indication information is used to indicate downlink data to be transmitted that exists in the camping base station.
  • the first paging message may further carry an address number indication information, where the number of address indication information indicates the number of addresses that the serving base station needs to allocate, so as to implement an interface between the base station and the base station (such as an Xn interface). Transmitting, to the serving base station, downlink data to be transmitted of the terminal reserved by the camping base station.
  • the downlink data to be transmitted by the terminal is also the data to be transmitted that the camping base station needs to send to the serving base station through the Xn interface.
  • the first paging message herein may be an embodiment of the first message.
  • the serving base station may allocate at least one address for data to be transmitted by the camping base station.
  • Step S302 The serving base station sends a second paging message to the terminal, where the second paging message carries the identifier information of the terminal UE. Correspondingly, the terminal receives the second paging message.
  • Step S303 The terminal sends an RRC Connection Resume Request message (RRC Connection Resume Request) to the serving base station, where the RRC Connection Recovery Request message is used to request to restore an RRC connection between the terminal and the serving base station.
  • the serving base station receives the RRC Connection Recovery Request message.
  • the RRC connection recovery request message carries the identifier information of the terminal, and the identifier information may uniquely indicate the terminal in the RNA area.
  • the identifier information such as Resume ID information, may also be restored.
  • the terminal when the terminal receives the second paging message sent by the serving base station, the terminal needs to go to the serving base station (that is, the base station where the terminal is currently located, because the terminal is in an RRC deactivated state. Sending an RRC connection recovery request message to establish an RRC connection between the terminal and the serving base station, facilitating secure data communication between the terminal and the serving base station.
  • the serving base station that is, the base station where the terminal is currently located
  • Step S304 The serving base station sends a terminal context request message (Retrieve UE Context Request) to the camping base station, where the terminal context request message is used to acquire terminal context information reserved in the camping base station, where the terminal context is The request message carries the at least one address.
  • the camping base station receives the terminal context request message.
  • the serving base station After the serving base station receives the RRC connection recovery request message, it finds that there is no terminal context information in the own base station, and therefore sends a terminal context request message to the camping base station to obtain the reserved in the resident base station. Terminal context information.
  • the terminal context request message may carry the at least one address to notify at least one address configured by the serving base station to the resident base station.
  • the terminal context request message herein may be an embodiment of the second message.
  • Step S305 The camping base station allocates an identifier of the second transmission granularity corresponding to each address in the at least one address, and acquires terminal context information retained in the resident base station.
  • the camping base station may acquire terminal context information acquired by the camping base station. And for the camping base station, it knows which second transmission granularity data needs to be transmitted to the serving base station (such as seeion1 and seeison2 that need to perform data transmission). It is assumed that the camping base station knows that it will also send the data to be transmitted to the serving base station according to the second transmission granularity (such as the Session granularity), and knows that the identifier of the second transmission granularity corresponding to the data to be transmitted to the serving base station is currently required, and the camping base station Each of the at least one address may be assigned an identifier of a corresponding second transmission granularity according to the received at least one address. An address corresponds to an identifier of a second transmission granularity.
  • the resident base station may map each of the at least one address to the identifier of the at least one second transmission granularity one-to-one. Specifically, the camping base station determines an address used by a downlink PDU session/DRB/QoS flow transmitted on the Xn interface.
  • the second transmission granularity For a description of the second transmission granularity, reference may be made to the related description in the foregoing embodiments, and details are not described herein again.
  • Step S306 the camping base station sends a terminal context response message (Retrieve UE Context Response) to the serving base station, where the terminal context response message carries the second transmission granularity corresponding to the terminal context information and the at least one address respectively. logo.
  • the serving base station receives the terminal context response message.
  • the terminal context response message may carry an identifier of at least one second transmission granularity, where the identifier of the second transmission granularity is used to indicate/identify that the resident base station needs to send the to the serving base station A data identifying a corresponding second transmission granularity.
  • the identifier of the second transmission granularity may include any one of the following: a PDU session identifier, a QoS flow identifier, and a DRB identifier.
  • the terminal context response message may further indicate a mapping relationship between identifiers of different transmission granularities, that is, a mapping relationship between the PDU session, the QoS flow, and any two or three of the DRBs.
  • the mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity is included.
  • the mapping relationship may indicate which PDU session corresponds to each specific QoS flow, which DRB corresponds to each specific QoS flow, and which PDU session corresponds to each specific DRB.
  • DRB1 and DRB2 correspond to PDU session 1
  • DRB3 and DRB4 correspond to PDU session 2
  • QoS flow 1 and QoS flow 2 correspond to DRB3, so QoS flow 1 and QoS flow 2 correspond to PDU session 2.
  • the terminal context response message may further include a mapping relationship between the address in the step S305 and the identifier of the second transmission granularity, where the mapping relationship indicates that the downlink data of the PDU session/DRB/QoS flow is The address used when transmitting on the Xn interface.
  • the serving base station allocates three addresses for the data to be transmitted by the camping base station, which are address 1 to address 3, respectively.
  • the resident base station knows that Session 1, Session 2 and Session 3, which need to transmit data to the serving base station, and after the serving base station notifies the above three addresses to the camping base station, the camping base station can bind the three addresses to the three sessions.
  • / mapping an address corresponds to a Session.
  • the camping base station assigns address 1 to Session1, address 2 to Session2, and address 3 to Session3.
  • the camping base station may notify the serving base station of the binding/mapping relationship between the address and the session.
  • the camping base station may carry, in the terminal context response message, the identifier of the second transmission granularity corresponding to each of the obtained at least one address of the obtained terminal uplink and downlink information, to notify the Residing base station.
  • the terminal context message described herein may be an embodiment of the third message.
  • Step S307 The serving base station establishes an RRC connection between the terminal and the serving base station according to the terminal context information.
  • the serving base station receives the terminal context response message, and may obtain information such as the terminal context information, the identifier of the second transmission granularity corresponding to each of the at least one address, and the like by message parsing.
  • the serving base station may establish an RRC connection between the terminal and the serving base station according to the terminal context information.
  • the serving base station may store an identifier of a second transmission granularity corresponding to each of the at least one address, so that the resident base station sends data corresponding to the identifiers of the second transmission granularities to the serving base station.
  • the serving base station can learn, according to the mapping relationship between the address and the identifier of the second transmission granularity, which second transmission granularity data is currently transmitted by the camping base station, that is, which specific PDUs are used by the camping base station.
  • the session/DRB/QoS flow carries the data.
  • the serving base station allocates two addresses, which are address 1 and address 2, for the data to be transmitted by the camping base station, and notifies the camping base station by using the terminal context request message.
  • the camping base station needs to send the Session1 data and the Session2 data.
  • the resident base station can respectively allocate an address for the Session1 data and the Session2 data, and assume that the Session1 data is assigned an address 1, and the Session2 data is assigned to an address 2. .
  • the binding/mapping relationship between the foregoing address and the data of the second transmission granularity (ie, the data to be transmitted, the Session1 data and the Session2 data) is notified to the serving base station by using the terminal context response message.
  • the camping base station base station may add a corresponding address in front of the data to be transmitted to notify the serving base station of the data to be transmitted currently transmitted. For example, when the resident base station transmits the Session1 data, the header of the address 1 can be added before the Session1 data.
  • the serving base station When the serving base station receives the seeion1 data carrying the address 1 packet header, the serving base station can determine the Session1 data corresponding to the address 1 sent by the currently camping base station according to the mapping relationship between the address 1 and the Session 1 data. Similarly, the serving base station can determine the Session 2 data corresponding to the address 2 sent by the currently camping base station according to the mapping relationship between the address 2 and the Session 2 data.
  • Step S308 The serving base station sends an RRC Connection Resume Response message (RRC Connection Resume Response) to the terminal UE to notify to resume establishing an RRC connection between the terminal and the serving base station.
  • RRC Connection Resume Response RRC Connection Resume Response
  • the serving base station may establish an RRC connection between the UE and the serving base station according to the acquired terminal context information in response to the RRC connection recovery request message. Then, the serving base station may send an RRC connection recovery response message to the terminal UE, informing the UE that the RRC connection between the established UE and the serving base station has been resumed, so that the subsequent UE and the serving base station perform secure data communication with each other.
  • the service The base station may allocate the same number of addresses as the number of addresses to the data to be transmitted (ie, downlink data) according to the number of addresses set by default or the number of addresses carried in other process messages.
  • the first paging message may further carry an address number indication information, where the address number indication information is used to indicate the number of addresses that the serving base station needs to allocate.
  • the address number indication information is used to indicate the number of addresses that the serving base station needs to allocate.
  • the first paging message may be further used to notify the camping base station to send data to be transmitted to the serving base station according to the second transmission granularity, that is, the granularity of data transmission by the camping base station through the Xn interface.
  • the first transmission granularity and the second transmission granularity may include any one of a QoS flow, a PDU session, and a radio bearer DRB.
  • the number of addresses carried in the first paging message is determined according to a transmission granularity.
  • the number of the addresses may be an identifier of the at least one first transmission granularity that the camping base station transmits according to the current requirement, and a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity.
  • the data corresponding to the identifier of the first transport granularity that the camping base station wants to transmit is flow1 data. , flow2 data, flow5 data, and flow7 data.
  • the resident base station knows that the actual transmittable data to the serving base station is seeion1 data, seeion2 data, and seeion3 data, and also knows that the number of the session data to be transmitted is 3, that is, the address. The number is 3.
  • the serving base station may transmit the allocated at least one address in the terminal context request message to the camping base station in step S203.
  • the camping base station itself knows which second transmission granularity data (ie, at least one second transmission granularity identifier) that it wants to send to the serving base station, As described above for Session 1 to Session 3 data, the resident base station may assign an identifier of a corresponding second transmission granularity to each of the at least one address. Different addresses are used to identify different data or data streams in the second transmission granularity form of the data to be transmitted.
  • the serving base station allocates three addresses for the data to be transmitted by the camping base station, which are address 1 to address 3, respectively.
  • the camping base station knows that it needs to send the Session1 data, the Session2 data and the Session3 data to the serving base station.
  • the camping base station can tie the three addresses with the three session data. Fixed/mapped, one address corresponds to one session data. It is assumed that the camping base station assigns address 1 correspondingly to Session 1 data, address 2 corresponds to Session 2 data, and address 3 corresponds to assigning Session 3 data.
  • the camping base station may notify the serving base station of the binding/mapping relationship between the foregoing address and the session data.
  • FIG. 4 is a schematic flowchart diagram of still another downlink data transmission method, where the method includes the following implementation steps.
  • Step S401 The camping base station sends a first paging message to the serving base station, where the first paging message carries the identifier information of the terminal, and the identifier information may uniquely indicate the terminal in the range of the RNA.
  • the serving base station receives the second paging message.
  • Step S402 The serving base station sends a second paging message to the terminal, where the second paging message carries the identification information of the terminal.
  • the camping base station may send the first paging message to the serving base station through the Xn interface.
  • the serving base station may forward the second paging message to the terminal to the terminal UE through the common channel.
  • the first paging message and the second paging message are both used to request to find/search for a terminal corresponding to the identification information.
  • the first paging message and the second paging message may refer to the same message.
  • Step S403 The terminal sends an RRC Connection Resume Request message (RRC Connection Resume Request) to the serving base station, where the RRC Connection Recovery Request message is used to request to restore an RRC connection between the terminal and the serving base station.
  • the serving base station receives the RRC Connection Recovery Request message.
  • the RRC connection recovery request message may carry identification information of the terminal, and the identification information may uniquely indicate the terminal in the RNA area.
  • the identification information may also be recovery identification information, such as Resume ID information.
  • Step S404 The serving base station sends a terminal context request message (Retrieve UE Context Request) to the camping base station, where the terminal context request message is used to acquire terminal context information reserved in the camping base station to establish a terminal UE. RRC connection with the serving base station.
  • a terminal context request message (Retrieve UE Context Request)
  • Step S405 The camping base station receives the RRC connection recovery message, and acquires terminal context information reserved in the camping base station.
  • step S402 to step S405 refer to the related description of step S302 to step S304 in the foregoing embodiment, and details are not described herein again.
  • Step S406 The camping base station sends a terminal context response message (Retrieve UE Context Response) to the serving base station, where the terminal context response message carries the terminal context information, and the terminal context response message carries downlink data indication information.
  • the downlink data indication information is used to indicate that the downlink data to be transmitted by the camping base station needs to be transmitted.
  • the downlink data indication information may be specifically used to indicate which second transmission granularity data (ie, the identifier of the at least one second transmission granularity) that the resident base station needs to transmit to the serving base station.
  • the terminal context response message may carry at least one identifier of the second transmission granularity, where the identifier of the second transmission granularity is used to indicate that the resident base station needs to send the identifier to the serving base station.
  • the identifier of the second transmission granularity may be a PDU session identifier, a QoS flow identifier, or a DRB identifier.
  • the terminal context response message may also indicate a mapping relationship between identifiers of different transport granularities, that is, indicating a mapping relationship between any two or three of different PDU sessions, QoS flows, and DRBs. And including a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity.
  • the mapping relationship indicates which PDU session corresponds to each specific QoS flow, which DRB corresponds to each specific QoS flow, and which PDU session corresponds to each specific DRB. For example, DRB1 and DRB2 correspond to PDU session 1, DRB3 and DRB4 correspond to PDU session 2, QoS flow 1 and QoS flow 2 correspond to DRB3, so QoS flow 1 and QoS flow 2 correspond to PDU session 2.
  • the downlink data indication information may be specifically used to indicate, at the first transmission granularity, downlink data that is to be transmitted at the camping base station.
  • the first transmission granularity may be any one of a PDU session, a DRB, and a QoS flow.
  • the downlink data indication information may be included in the PDU session.
  • the first transmission granularity is a QoS flow
  • Table 1 below gives (partially) a specific embodiment of a terminal context response message (ie, the first message).
  • the identifier of the PDU session (identified as the identifier of the second transmission granularity) may be carried in L3, and the mapping/binding between the identifier of the PDU session and the identifier of the QoS flow in L3 and L4 to L6 is indicated.
  • the L7 further indicates that the second base station informs the first base station to perform data transmission by using the granularity of the QoS flow (which may be regarded as the first transmission granularity), that is, the data to be transmitted is indicated by the granularity of the QoS flow.
  • the granularity of the QoS flow which may be regarded as the first transmission granularity
  • the first transmission granularity is a PDU session, and a portion of a specific embodiment of a terminal context response message (ie, the first message) is given in Table 2 below.
  • the L3 can carry the identifier of the PDU session (which can be regarded as the identifier of the second transmission granularity), and the mapping/binding relationship between the identifier of the PDU session and the identifier of the QoS flow indicated in L3 and L7. That is, which QoS flows need to be established under a specific PDU session. In L3 and L4, it is indicated which PDU sessions need to transmit data, that is, the identifier of the PDU session indicating the data transmission.
  • L3 and L4 further indicate that the second base station informs the first base station to transmit data according to the granularity (first transmission granularity) of the PDU session, that is, the data to be transmitted is indicated by the granularity of the PDU session.
  • the downlink data indication information specifically indicates, at a first transmission granularity, which downlink data of the first transmission granularity that the camping base station has, that is, an identifier of the at least one first transmission granularity, needs to be transmitted, and further A mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity is indicated.
  • the serving base station may determine, according to the mapping between the identifier of the at least one first transmission granularity and the identifier of the first transport granularity and the identifier of the second transport granularity, the identifier of the corresponding at least one second transport granularity.
  • the first transmission granularity is a QoS flow
  • the second transmission granularity is a PDU session.
  • the mapping relationship indicated in Table 1 above it may be determined in which PDU session the identity of each QoS flow belongs to.
  • the downlink data indication information is carried, and the second transmission granularity or the first transmission that is required to perform downlink data transmission exists for the resident base station.
  • the granularity will carry the downlink data indication information.
  • Step S407 Correspondingly, the serving base station receives the terminal context response message.
  • the serving base station allocates a corresponding address to each identifier of the identifier of the at least one second transmission granularity, and an address corresponds to an identifier of a second transmission granularity.
  • the serving base station allocates an address to the data to be transmitted at a second transmission granularity based on a downlink data indication message in S406, and a mapping relationship between the PDU session, the DRB, and the QoS flow, and sends the address to the resident base station. And sending a data forwarding address notification message, where the data transmission address notification message includes address information corresponding to the data to be transmitted.
  • the second transmission granularity may be a QoS flow, a DRB, or a PDU session.
  • the second transmission granularity may be a QoS flow, or may be a DRB, or may be a PDU session; if the first transmission granularity is a DRB, the second transmission granularity may be a DRB. It can also be a PDU session; if the first transmission granularity is a PDU session, the second transmission granularity is a PDU session.
  • the first transmission granularity is a QoS flow. If the QoS flow 1 is in the downlink data to be transmitted by the camping base station, the serving base station allocates an address for the PDU session 2.
  • Step S408 The serving base station sends a data transmission address notification message to the resident base station, where the data transmission address notification message carries an identifier of a second transmission granularity corresponding to each of the at least one address.
  • the serving base station may notify the at least one address allocated by the serving base station to the data to be transmitted by the camping base station, and the identifier of the second transmission granularity corresponding to each of the at least one address to the station by using the data transmission address notification message.
  • the data transfer address notification message herein may be another embodiment of the second message.
  • a portion of a specific embodiment of a data transmission address notification message (i.e., a second message) is exemplarily shown.
  • the identifier of the PDU session (ie, the identifier of the second transmission granularity) is carried in L6, and the mapping/binding relationship between the identifier of the PDU session and the downlink address is jointly indicated in L6 and L7 (ie, the a mapping relationship between the identifier of the second transmission granularity and the address).
  • L6 and L7 ie, the a mapping relationship between the identifier of the second transmission granularity and the address.
  • Step S409 The serving base station sends an RRC Connection Resume message to the terminal, where the RRC connection recovery message is used to notify the terminal to resume establishing an RRC connection with the serving base station.
  • the step S408 and the step S409 may be in parallel, that is, the step S408 may be performed after the step S409 is performed, which is not limited in the embodiment of the present invention.
  • the second base station may be a serving base station (NgNB) and the first base station may be a camping base station (AgNB).
  • NgNB serving base station
  • AgNB camping base station
  • FIG. 5 is a schematic flowchart diagram of an uplink data transmission method, and the method includes the following implementation steps.
  • Step S501 The terminal sends an RRC Connection Resume Request message (RRC Connection Resume Request) to the serving base station, where the RRC Connection Recovery Request message is used to request to resume the RRC connection between the terminal and the serving base station.
  • the serving base station receives the RRC Connection Recovery Request message.
  • Step S502 The serving base station sends a terminal context request message (Retrieve UE Context Request) to the camping base station, where the terminal context request message is used to acquire terminal context information reserved in the camping base station, and is further used to indicate The serving base station needs to transmit uplink data to be transmitted to the resident base station.
  • the camping base station receives the terminal context request message.
  • the terminal context request message carries uplink data indication information, where the uplink data indication information is used to indicate that the serving base station needs to transmit uplink data to be transmitted to the resident base station.
  • the uplink data indication information may be specifically used to indicate which second transmission granularity uplink data (ie, the identifier of the at least one second transmission granularity) currently exists in the serving base station needs to be transmitted to the resident base station.
  • the terminal context request message herein may be yet another embodiment of the first message.
  • the terminal context request message may carry an identifier of at least one second transmission granularity, where the identifier of the second transmission granularity is used to indicate that the serving base station needs to transmit the identifier corresponding to the resident base station.
  • the uplink data of the second transmission granularity may be a PDU session identifier, a QoS flow session identifier, or a DRB identifier.
  • the terminal context response message further indicates a mapping relationship between identifiers of different transmission granularities, that is, a mapping relationship between the PDU session, the QoS flow, and any two or three of the DRBs.
  • a mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity is included.
  • Step S503 The camping base station allocates a corresponding address for each identifier of the at least one identifier of the second transport granularity, and acquires terminal context information. Different addresses are used to identify different data streams in the second transmission granularity form in the data to be transmitted.
  • the camping base station may acquire terminal context information reserved in the camping base station.
  • the camping base station knows which uplink data of the second transmission granularity (ie, the identifier of the at least one second transmission granularity) that the serving base station needs to transmit
  • the resident base station may be the identifier of the at least one second transmission granularity.
  • Each of the identifiers is assigned a corresponding address, and an identifier of the second transport granularity corresponds to an address.
  • the camping base station allocates an address for the data to be transmitted at the second transmission granularity. That is, the camping base station allocates a downlink PDU session/DRB/QoS flow transmitted on the Xn interface and determines its corresponding adopted address.
  • Step S504 The camping base station sends a terminal context response message (Retrieve UE Context Response) to the serving base station, where the terminal context response message carries the second transmission granularity corresponding to the terminal context information and the at least one address respectively. logo.
  • the serving base station receives the terminal context response message.
  • the camping base station may notify the serving base station in the form of a terminal context response message after acquiring the terminal context information and assigning the corresponding address to each of the identifiers of the at least one second transport granularity.
  • the terminal context response message herein may be another embodiment of the second message.
  • Step S505 The serving base station establishes an RRC connection between the terminal UE and the serving base station according to the terminal context information.
  • Step S506 The serving base station sends an RRC Connection Resume Response message (RRC Connection Resume Response) to the terminal, where the RRC Connection Recovery Response message is used to notify the terminal to resume establishing an RRC connection with the serving base station.
  • RRC Connection Resume Response RRC Connection Resume Response
  • step S504 can also be performed after the step S506, which is not limited by the embodiment of the present invention.
  • the terminal context request message in step S502 is used to indicate that the serving base station needs to transmit uplink data to be transmitted to the camping base station, but does not indicate which second transmission granularity exists in the serving base station.
  • the camping base station may set the number of addresses according to the default or other The number of addresses carried in the flow message is the same as the number of addresses in the data to be transmitted by the serving base station (here, the uplink data).
  • the terminal context request message in step S502 is used to indicate that the serving base station needs to transmit uplink data to be transmitted to the camping base station, and the terminal context request message carries the number of addresses (That is, the number of the base station to which the serving base station needs to be located is allocated.
  • the camping base station can allocate the same number of addresses as the number of addresses to be transmitted for the serving base station (here, the uplink data).
  • the terminal context response message carries the terminal context information and the at least one address (that is, the same number of addresses as the number of addresses), and does not carry the at least one address respectively.
  • the terminal context information that is, the same number of addresses as the number of addresses
  • the terminal context request message may be further used to indicate that the serving base station actually sends uplink data to be transmitted to the camping base station according to the second transmission granularity.
  • the serving base station knows which first transmission granularity data (ie, at least one first transmission granularity identifier) needs to be transmitted to the camping base station, and the serving base station may be according to at least one first transmission granularity. Identifying, by the mapping relationship between the identifier of the first transmission granularity and the identifier of the second transmission granularity, determining an identifier of the corresponding at least one second transmission granularity and/or an identifier of the at least one second transmission granularity Number. The number of identifiers of the at least one second transmission granularity is the number of the addresses.
  • the terminal context request message in step S502 is used to indicate which first transmission granularity data (ie, the identifier of the at least one first transmission granularity) of the serving base station needs to be transmitted to the resident base station,
  • the terminal context request message further carries a mapping relationship between the identifier of the second transport granularity and the identifier of the first transport granularity.
  • the terminal context request message is further used to indicate that the serving base station actually sends data to be transmitted to the camping base station according to the second transmission granularity.
  • the camping base station receives the terminal context request message.
  • the camping base station may identify, according to the at least one first transmission granularity, and the location in step S503.
  • the mapping relationship between the identifier of the first transport granularity and the identifier of the second transport granularity determines an identifier of the corresponding at least one second transport granularity and/or a number of identifiers of the at least one second transport granularity.
  • step S503 may be continued.
  • the camping base station may be the serving base station in step S503.
  • the data to be transmitted (here, the uplink data) is assigned the same number of addresses as the number of addresses.
  • the terminal context response message carries the at least one address (that is, the same number of addresses as the number of addresses), and does not carry the second transmission granularity corresponding to each of the at least one address.
  • the resident base station may allocate, for each address of the at least one address, a corresponding identifier of the second transmission granularity (ie, allocate one for transmitting the certain one to be transmitted on the Xn interface).
  • the data has a data or data stream in the form of a second transport granularity).
  • the camping base station may send a data transmission address notification message to the serving base station, where the data transmission address notification message carries an identifier of a second transmission granularity corresponding to each of the at least one address, to transmit the address and the second transmission A binding/mapping relationship between the granularity identifiers is notified to the serving base station.
  • the serving base station receives the data transmission address notification message, where the data transmission address notification message may be another embodiment of the third message.
  • FIG. 6 is a schematic flowchart diagram of another data transmission method according to an embodiment of the present invention, where the method includes the following implementation steps.
  • the data transmission involved herein is uplink data transmission
  • the first base station may be a source base station
  • the second base station may be a target base station.
  • the terminal UE in the connected state transmits uplink data to the first base station (ie, the source base station), and the terminal moves from the first base station to the second base station due to mobility of the terminal, and based on information such as measurement reports, the first base station It is decided to switch the terminal to the second base station (ie, the target base station).
  • the terminal needs to send uplink data to the two base stations at the same time in the process of the handover.
  • the terminal may send uplink data to the core network side through a communication link of the terminal->second base station->first base station->core network and a communication link of the terminal->first base station->core network. Therefore, the second base station needs to obtain corresponding uplink address information of the first base station, and is used by the second base station to transmit uplink data on the Xn interface.
  • Step S601 The first base station sends a first message to the second base station, where the first message carries an address corresponding to the first identifier of the at least one first transmission granularity, where the address is used to identify the first base station and the Data of the first transmission granularity that needs to be transmitted between the second base stations.
  • the second base station receives the first message.
  • the first transmission granularity may include any of the following: a PDU session, a QoS flow, a DRB.
  • the identifier of the first transmission granularity may be any one of the following: a PDU session identifier, a QoS flow identifier, and a DRB identifier.
  • the first message may carry uplink data indication information, where the uplink data indication information may be specifically used to indicate which first transmission granularity (ie, at least the first identifier of the first transmission granularity) needs to perform data.
  • the transmitting may also indicate an address corresponding to each of the first identifiers of the at least first transmission granularity.
  • the first message may carry the first identifier of the at least one first transmission granularity, and when the first base station actually sends the first message to the second base station, each of the first An address corresponding to the first identifier of a transmission granularity is added to the first message for transmission. That is, the first base station notifies the second base station of the address corresponding to the first identifier of the at least one first transmission granularity by using the first message.
  • the address here may also be the uplink data transmission address information corresponding to the first identifier of the first transmission granularity.
  • the first identifier of a first transmission granularity corresponds to an address (or an uplink data transmission address information).
  • the QoS flow as the first transmission granularity as an example (the PDU session and the DRB are the first transmission granularity can also be easily obtained based on the following table), and the specific embodiment of the first message is given in Table 4 below. The part in it.
  • L3 can carry the identifier of the PDU session (which can be regarded as the first identifier of the first transmission granularity), and the mapping/binding between the identifier of the PDU session and the identifier of the QoS flow in L3 and L6.
  • L6 and L7 indicate the mapping relationship between the identifier and the address of the QoS flow, that is, the uplink address (or uplink address information) corresponding to a specific QoS flow.
  • the method before the first base station sends the first message to the second base station, the method further includes: the first base station assigning a corresponding address to the identifier of the at least one first transmission granularity.
  • the first base station may identify according to the at least one second transmission granularity. And mapping the identifier of the first transport granularity to the identifier of the second transport granularity, and determining a first identifier of the corresponding at least one first transport granularity. Then, the first base station may allocate a corresponding address for each of the first identifiers of the at least one first transmission granularity.
  • the first identifier that is not for each first transmission granularity carries the uplink data indication information
  • the second transmission granularity or the first transmission granularity that the downlink data transmission needs to be performed for the resident base station is Will carry downstream data indication information.
  • Step S602 The second base station determines, according to the air interface resource information, a second identifier of the first transmission granularity, where the second identifier is one or more of the at least one first identifier.
  • the second base station may determine, according to factors such as time-frequency resources of the air interface, which first transmission granularity that needs to be data transmission is established for the terminal/the first base station. That is, the second base station may determine, according to the resource information such as the time-frequency resource of the air interface, the second identifier of the first transmission granularity from the first identifier of the first transmission granularity.
  • the second identifier of the first transmission granularity may include any one or more of the following: a PDU session, a DRB, and a QoS flow.
  • the information about the air interface resource may be information about the usage of the air interface resource, and may include information such as the time-frequency resource of the air interface.
  • Step S603 The second base station sends a second message to the first base station, where the second message carries the second identifier of the first transmission granularity. Correspondingly, the second base station receives the second message.
  • the second base station may notify the first base station of the second identifier of the first transmission granularity that is required to perform data transmission.
  • the first message may be a Handover Request ACK, or other process messages, which are not limited in the embodiment of the present invention.
  • the foregoing solution can solve the problem that the first base station and the second base station in the prior art do not know how to identify the data to be transmitted when the data transmission is performed, and the other end does not know what data is currently received, and the data transmission is improved. Efficient.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of the interaction between the first base station and the second base station, and optionally participates in the interaction of the terminal.
  • the first base station or the second base station includes corresponding hardware structures and/or software modules for performing respective functions.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present invention.
  • the embodiment of the present invention may perform the division of functional units on the first base station and the second base station according to the foregoing method example.
  • each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 7A shows a possible structural diagram of the first base station involved in the above embodiment.
  • the first base station 500 includes a processing unit 502 and a communication unit 503.
  • the processing unit 502 is configured to perform control and management on the action of the first base station 500.
  • the processing unit 502 is configured to support the first base station 500 to perform step S202 in FIG. 2, step S306 in FIG. Step S406 and step S408 in FIG. 4, step S503 in FIG. 5, and/or other steps for performing the techniques described herein.
  • the communication unit 503 is configured to support communication between the first base station 500 and other network devices.
  • the communication unit 503 is configured to support the first base station 500 to perform step S203 in FIG. 2, step S303 and step S307 in FIG. S403 and step S407, step S504 in FIG. 5, and/or other steps for performing the techniques described herein.
  • processing unit 502 is configured to support first base station 500 to perform step S601 in FIG. 6, and/or to perform other steps of the techniques described herein.
  • the communication unit 503 is configured to support communication between the first base station 500 and other network devices, for example, the communication unit 503 is configured to support the first base station 500 to perform step S601 in FIG. 6, and/or to perform other steps of the techniques described herein. .
  • the first base station 500 may further include a storage unit 501, configured to store program codes and data of the first base station 500.
  • the processing unit 502 can be a processor or a controller, for example, can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • a hardware chip can also be further included.
  • the hardware chip described above may be an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a Complex Programmable Logic Device (CPLD), a Field Programmable Logic Gate Array (FPGA), a General Array Logic (GAL), or any combination thereof.
  • the communication unit 503 includes a communication interface, a transceiver, a transceiver circuit, and the like.
  • the communication interface is a collective name and may include one or more interfaces, such as an interface between the first base station and the second base station.
  • the storage unit 501 can be a memory.
  • the memory may include a volatile memory (English: volatile memory), such as a random-access memory (RAM); the memory may also include a non-volatile memory, such as a flash memory. (English: flash memory), hard disk (English: hard disk drive, abbreviated: HDD) or solid state drive (English: solid-state drive, abbreviation: SSD); the memory 410 may also include a combination of the above types of memory.
  • the first base station involved in the embodiment of the present invention may be the first base station shown in FIG. 7B.
  • the first base station 500 includes a processor 512, a communication interface 513, and a memory 511.
  • the first base station 500 may further include a bus 514.
  • the communication interface 513, the processor 512, and the memory 511 may be connected to each other through a bus 514; the bus 514 may be divided into an address bus, a data bus, a control bus, and the like.
  • the bus 514 may be divided into an address bus, a data bus, a control bus, and the like.
  • Only one thick line is shown in Figure 7B, but it does not mean that there is only one bus or one type of bus.
  • the first base station may be any one of the following: a serving base station, a camping base station, a source base station, and a target base station.
  • the specific implementation of the first base station shown in FIG. 7A or FIG. 7B may also refer to the corresponding description of the foregoing method embodiments, and details are not described herein again.
  • FIG. 8A is a schematic diagram showing a possible structure of a second base station involved in the foregoing embodiment.
  • the second base station 600 includes a processing unit 602 and a communication unit 603.
  • the processing unit 602 is configured to perform control and management on the action of the second base station 600.
  • the processing unit 602 is configured to support the second base station 600 to perform step S304 in FIG. 3, step S404 in FIG. Step S505 in FIG. 5, step S503 in FIG. 6, and/or other steps for performing the techniques described herein.
  • the communication unit 503 is configured to support communication between the second base station 600 and other network devices.
  • the communication unit 603 is configured to support the second base station 600 to perform step S201 in FIG. 2, step S301 and step S305 in FIG. S401 and step S405, step S502 and step S506 in Fig. 5, step S603 in Fig. 6, and/or other steps for performing the techniques described herein.
  • processing unit 602 is configured to support second base station 600 in performing step S602 of FIG. 6, and/or to perform other steps of the techniques described herein.
  • the communication unit 503 is configured to support communication between the second base station 600 and other network devices, for example, the communication unit 603 is configured to support the second base station 600 to perform step S603 in FIG. 6, and/or to perform other steps of the techniques described herein. .
  • the second base station 600 may further include a storage unit 601, configured to store program codes and data of the second base station 600.
  • the processing unit 602 can be a processor or a controller, and can be, for example, a CPU, an NP, or a combination of a CPU and an NP.
  • a hardware chip can also be further included.
  • the above hardware chip may be an ASIC, a PLD, or a combination thereof.
  • the above PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
  • the communication unit 603 includes a communication interface, a transceiver, a transceiver circuit, and the like.
  • the communication interface is a collective name and may include one or more interfaces, such as an interface between the first base station and the second base station.
  • the storage unit 601 can be a memory.
  • the memory may include volatile memory, such as RAM; the memory may also include non-volatile memory, such as flash, HDD or SSD; the memory may also include a combination of the types of memory described above.
  • the second base station involved in the embodiment of the present invention may be the second base station shown in FIG. 8B.
  • the second base station 600 includes a processor 612, a communication interface 613, and a memory 611.
  • the second base station 600 may further include a bus 614.
  • the communication interface 613, the processor 612, and the memory 611 may be connected to each other through a bus 614; the bus 614 may be divided into an address bus, a data bus, a control bus, and the like.
  • the bus 614 may be divided into an address bus, a data bus, a control bus, and the like.
  • Only one thick line is shown in Figure 8B, but it does not mean that there is only one bus or one type of bus.
  • the second base station may be any one of the following: a serving base station, a camping base station, a source base station, and a target base station.
  • FIG. 8A or FIG. 8B may also correspond to the corresponding description of the foregoing method embodiments, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of a data transmission system provided by the present invention.
  • the system 700 includes a first base station 500 and a second base station 600.
  • the first base station 500 may be the first base station 500 shown in FIG. 7A or FIG. 7B, and details are not described herein.
  • the second base station 600 may be the second base station 600 shown in FIG. 8A or FIG. 8B, and details are not described herein again.
  • the foregoing solution can solve the problem that the first base station and the second base station in the prior art do not know how to identify the data to be transmitted when the data transmission is performed, and the other end does not know what data is currently received, and the data transmission is improved. Efficient.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, which can be stored in RAM, flash memory, read only memory (English: Read Only Memory, ROM), and Erasable Programmable ROM (EPROM).
  • An electrically erasable programmable read only memory (English: Electron EPROM, EEPROM), a register, a hard disk, a removable hard disk, a compact disk read only (CD-ROM), or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in the first base station or the second base station.
  • the processor and the storage medium may also be present in the first base station or the second base station as discrete components.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本发明实施例公开了一种数据传输方法、相关设备及系统，所述方法包括：第一基站接收第二基站发送的第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；所述第一基站向所述第二基站发送第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。通过实施本发明实施例，能够解决现有技术中第一基站和第二基站在进行数据传输时，一端不知道如何标识待传输的数据，另一端不知道当前接收的数据，提升了数据传输的高效性。

Description

一种数据传输方法、相关设备及系统 技术领域
本发明涉及通信技术领域，尤其涉及一种数据传输方法、相关设备及系统。
背景技术
在下一代网络(5G)中为用户设备(User Equipment，UE)定义了三种无线资源控制(Radio Resource Control，RRC)状态分别为：RRC空闲状态(RRC Idle State)、RRC去激活状态(RRC Inactive State)、RRC连接状态(RRC Connected State)。
当终端处于RRC去激活状态时，终端在无线接入网(Radio Access Network，RAN)的通知区域(RAN based Notification Area，RNA)内部移动时，不会向网络侧反馈信道质量状况，并在移出RNA后需要通知网络。其中，RNA由一个小区或者多个小区组成，若由多个小区组成，该多个小区属于同一基站，也可以属于不同的基站，该不同的基站可以是同一无线接入类型(Radio Access Type，RAT)的基站，也可以是不同RAT的基站。
由于处于RRC去激活状态的终端的移动性，处于RRC去激活状态的终端会通过小区重选与新的服务基站(即非驻留基站，第二基站)进行下行同步。若处于RRC去激活状态的终端需要进行下行数据传输，则该终端首先会与该新服务基站(即第二基站)建立RRC连接，然后移动之前的驻留基站(即第一基站)将数据通过Xn接口传输至新服务基站，再由新服务基站将数据传输至终端。若处于RRC去激活状态的终端需要进行上行数据传输，则该终端首先会将上行数据传输至新服务基站，然后新服务基站通过Xn接口将上行数据传输至驻留基站，再由驻留基站传输至核心网。
由于处于RRC连接状态的终端的移动性，处于RRC连接状态的终端会通过切换从源基站(即第一基站)切换至目标基站(即第二基站)。在切换的过程中，为了保证零毫秒的时延，连接状态的终端将会在一段时间内同时与源基站和目标基站保持数据传输。在这段时间内，目标基站会通过Xn接口将接受到的上行数据传输给源基站，然后由源基站传输至核心网。
现有技术中，第一基站和第二基站可通过Xn接口进行相互之间的数据通信，但针对处于RRC去激活状态的终端进行数据的传输、及处于RRC连接态的终端在切换过程中进行上行数据的传输，并未给出具体的数据通信方式。这样在第一基站与第二基站进行相互数据传输时，针对发送端基站而言，并不知道如何标识待传输的数据。同样针对接收端基站而言，也不知道当前发送端基站发送的是什么数据，容易造成通信混乱。
发明内容
本申请公开了一种数据传输方法、相关设备及系统，能够解决现有技术中第一基站和第二基站进行相互数据传输时，收发端基站可能出现不知道如何标识待传输的数据、知悉当前传输的数据等问题，提升了数据传输的高效性。
第一方面，提供了一种数据传输方法，所述方法包括：
第一基站接收第二基站发送的第一消息，所述第一消息用于指示所述第二基站需要进 行数据的传输；
所述第一基站向所述第二基站发送第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
具体的，所述第一消息中可携带数据传输指示信息，该数据传输指示信息用于指示第二基站需要向第一基站传输数据。所述第一基站接收所述第一消息后可为所述第二基站待传输的数据分配至少一个地址，并通知给所述第一基站。通过上述方案，第一基站和第二基站在进行数据传输时，一端基站知道如何标识待传输的数据，另一端基站知道当前接收的是什么数据，可提升数据传输的高效性。
在一些可能的实施例中，所述地址个数是所述第二基站根据至少一个第一传输粒度的标识和所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系确定的所述第二传输粒度的标识的个数。具体的，若所述第二基站中存在有至少一个第一传输粒度的数据(即至少一个第一传输粒度的标识)需要向第一基站传输，则所述第二基站可根据不同传输粒度的标识之间的映射关系确定出实际传输的所述第二传输粒度的标识的个数。所述映射关系为不同传输粒度的数据之间的对应关系，例如某个QoS流对应在哪个具体的PDU会话中。
在一些可能的实施例中，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述第一基站向所述第二基站发送第二消息之前，还包括：所述第一基站根据所述至少一个第一传输粒度的标识以及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定所述第二传输粒度的标识的个数；所述第一基站根据所述第二传输粒度的标识的个数，为所述待传输的数据分配与所述第二传输粒度的标识的个数数量相同的地址。
具体的，所述数据指示信息可具体用于指示所述第二基站以第一传输粒度告知第一基站当前需要传输哪些第一传输粒度的数据(即至少一个第一传输粒度的标识)，还指示有第一传输粒度的标识与第二传输粒度的标识的映射关系，则所述第一基站可依次确定出实际按照第二传输粒度传输数据时所述第二传输粒度的标识的个数，并分配与所述第二传输粒度的标识的个数数量相同的地址。
通过实施上述步骤，能够为每个待传输的第二传输粒度的数据(即每个第二传输粒度的标识)分配一个地址，保证在实际传输所述第二传输粒度的数据时，利用所述地址能够一一标识，提升了第一基站与第二基站间数据传输的高效性。
在一些可能的实施例中，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述第一基站向所述第二基站发送第二消息之前，还包括：所述第一基站根据所述至少一个第一传输粒度的标识以及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定至少一个所述第二传输粒度的标识；所述第一基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识。
具体的，第一基站在获知到所述第二基站存在的至少一个第二传输粒度的标识后，可为每个所述第二传输粒度的标识分配一个地址，不同的所述第二传输粒度的标识对应不同的地址。不仅为所述第二基站中待传输的数据分配了地址，还配置了所述第二传输粒度的标识与所述地址之间的映射关系。
通过实施上述步骤，能够为每个待传输的第二传输粒度的数据(即每个第二传输粒度的标识)分配一个地址，保证在实际传输所述第二传输粒度的数据时，利用所述地址能够一一标识，提升了第一基站与第二基站间数据传输的高效性。
在一些可能的实施例中，所述第一消息携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第二传输粒度的标识所对应的数据；所述第一基站向所述第二基站发送第二消息之前，还包括：所述第一基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述至少一个第二传输粒度的标识的个数与所述至少一个地址的个数数量相同。
通过实施上述步骤，能够为每个待传输的第二传输粒度的数据(即每个第二传输粒度的标识)分配一个地址，保证在实际传输所述第二传输粒度的数据时，利用所述地址能够一一标识，提升了第一基站与第二基站间数据传输的高效性。
在一些可能的实施例中，所述方法还包括：所述第一基站接收所述第二基站发送的第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
通过实施上述步骤，所述第一基站可获知到所述第二基站中每个待传输的第二传输粒度的标识所对应的地址，能够保证在实际传输所述第二传输粒度的数据时，利用所述地址能够一一标识所述第二传输粒度的数据，提升了第一基站与第二基站间数据传输的高效性。
第二方面，提供了又一种数据传输方法，所述方法包括：
第二基站向第一基站发送第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；
接收所述第一基站发送的第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
具体的，所述第一消息可携带数据指示信息，所述数据指示信息可用于指示所述第二基站需要进行数据的传输。可选地，所述数据指示信息可具体用于指示所述第二基站存在哪些第二传输粒度或第一传输粒度的数据待传输。通过上述方案，第一基站和第二基站在进行数据传输时，一端基站知道如何标识待传输的数据，另一端基站知道当前接收的是什么数据，可提升数据传输的高效性。
在一些可能的实施例中，所述第一消息携带地址个数，所述第二消息中的至少一个地址的个数与所述第一消息中的地址个数相同。具体的，所述地址个数是根据传输粒度而确定的。
在一些可能的实施例中，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述第二消息中的至少一个地址的个数与所述第一消息中至少一个第二传输粒度的标识的个数相同；其 中，所述第二传输粒度的标识的个数是根据所述至少一个第一传输粒度的标识、及所述第一传输粒度的标识与第二传输粒度的标识的映射关系确定的。
在一些可能的实施例中，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述第二消息中的至少一个地址的个数与所述第一消息中至少一个第一传输粒度的标识的个数相同；其中，所述第二传输粒度的标识是根据所述至少一个第一传输粒度的标识、及所述第一传输粒度的标识与第二传输粒度的标识的映射关系确定的。
在一些可能的实施例中，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述第二消息中的至少一个地址的个数与所述第一消息中至少一个第二传输粒度的标识的个数相同。
在一些可能的实施例中，所述第二基站存在至少一个第二传输粒度的标识所对应的数据需要向所述第一基站传输，所述方法还包括：所述第二基站为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识，不同的地址对应不同的第二传输粒度的标识；所述第二基站向所述第一基站发送第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
通过执行上述步骤，所述第二基站知道自己想要向所述第一基站发送哪些第二传输粒度的数据(即至少一个第二传输粒度的标识)，所述第二基站可为所述第二消息中所述至少一个地址中的每个地址分配对应的第二传输粒度的标识。这样能够保证在实际传输所述第二传输粒度的数据时，利用所述地址能够一一标识，提升了第一基站与第二基站间数据传输的高效性。
结合第一方面或第二方面，在一些可能的实施方案中，所述第一消息还用于指示所述第二基站按照第二传输粒度向所述第一基站发送待传输的数据。
结合第一方面或第二方面，在一些可能的实施方案中，所述第一消息携带地址个数，所述第二消息中的至少一个地址的个数与所述第一消息中的地址个数相同。具体的，所述第一基站为所述第二基站待传输的数据分配与所述地址个数数量相同的地址。
结合第一方面或第二方面，在一些可能的实施例中，所述地址个数是根据传输粒度而确定的。具体的，若所述第一基站与所述第二基站实际以第二传输粒度进行数据传输，则所述地址个数是所述第二基站确定的所述第二传输粒度的标识的个数，即是所述第二基站实际向向所述第一基站发送第二传输粒度的数据的个数。
结合第一方面或第二方面，在一些可能的实施例中，所述第一传输粒度或所述第二传输粒度包括以下中的任一项：服务质量QoS流、协议数据单元PDU会话、数据无线承载DRB。
第三方面，提供了又一种数据传输方法，所述方法包括：
第一基站向第二基站发送第一消息，所述第一消息携带至少一个第一传输粒度的第一 标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
接收所述第二基站发送的第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
在一些可能的实施例中，所述第一基站向第二基站发送第一消息之前，还包括：所述第一基站为至少一个第一传输粒度的第一标识中的每个第一标识分配对应的地址，不同的地址对应不同的第一传输粒度的第一标识。
具体的，所述第一传输粒度的第一标识或第二标识可包括以下中的任一项：QoS流标识、PDU会话标识、DRB标识。
通过上述方案，第一基站和第二基站在进行数据传输时，一端基站知道如何标识待传输的数据，另一端基站知道当前接收的是什么数据，可提升数据传输的高效性。
第四方面，提供了又一种数据传输方法，所述方法包括：
第二基站接收第一基站发送的第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
所述第二基站向所述第一基站发送第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
在一些实施例中，所述第二基站接收第一基站发送的第一消息之后，所述第二基站向所述第一基站发送第二消息之前，还包括：所述第二基站根据空口资源信息，从所述第一传输粒度的第一标识中选择所述第二标识。具体的，所述空口资源信息可包括空口的时频资源信息等。
通过上述方案，第一基站和第二基站在进行数据传输时，一端基站知道如何标识待传输的数据，另一端基站知道当前接收的是什么数据，可提升数据传输的高效性。
结合第三方面或第四方面，在一些可能的实施例中，所述第一传输粒度可包括以下中的任一项：服务质量QoS流、协议数据单元PDU会话、数据无线承载DRB。
第五方面，提供了一种第一基站，包括用于执行上述第一方面的方法的功能单元。
第六方面，提供了一种第二基站，包括用于执行上述第二方面的方法的功能单元。
第七方面，提供了一种第一基站，包括用于执行上述第三方面的方法的功能单元。
第八方面，提供了一种第二基站，包括用于执行上述第四方面的方法的功能单元。
第九方面，提供了一种第一基站，包括存储器、通信接口及与所述存储器和通信接口耦合的处理器；所述存储器用于存储指令，所述处理器用于执行所述指令，所述通信接口用于在所述处理器的控制下与其他设备进行通信；其中，所述处理器执行所述指令时执行上述第一方面描述的方法。
第十方面，提供了一种第二基站，包括存储器、通信接口及与所述存储器和通信接口耦合的处理器；所述存储器用于存储指令，所述处理器用于执行所述指令，所述通信接口用于在所述处理器的控制下与其他设备进行通信；其中，所述处理器执行所述指令时执行上述第二方面描述的方法。
第十一方面，提供了一种第一基站，包括存储器、通信接口及与所述存储器和通信接 口耦合的处理器；所述存储器用于存储指令，所述处理器用于执行所述指令，所述通信接口用于在所述处理器的控制下与其他设备进行通信；其中，所述处理器执行所述指令时执行上述第三方面描述的方法。
第十二方面，提供了一种第二基站，包括存储器、通信接口及与所述存储器和通信接口耦合的处理器；所述存储器用于存储指令，所述处理器用于执行所述指令，所述通信接口用于在所述处理器的控制下与其他设备进行通信；其中，所述处理器执行所述指令时执行上述第四方面描述的方法。
第十三方面，提供了一种数据传输系统，包括第一基站和第二基站，其中，所述第一基站可以是上述第五方面或第九方面内容所述的第一基站；所述第二基站可以是上述第六方面或第十方面内容所述的第二基站。
第十四方面，提供了又一种数据传输系统，包括第一基站和第二基站，其中，所述第一基站可以是上述第七方面或第十一方面内容所述的第一基站；所述第二基站可以是上述第八方面或第十二方面内容所述的第二基站。
第十五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储了用于任务处理的程序代码。所述程序代码包括用于执行上述第一方面描述的方法的指令。
第十六方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储了用于任务处理的程序代码。所述程序代码包括用于执行上述第二方面描述的方法的指令。
第十七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储了用于任务处理的程序代码。所述程序代码包括用于执行上述第三方面描述的方法的指令。
第十八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储了用于任务处理的程序代码。所述程序代码包括用于执行上述第四方面描述的方法的指令。
通过上述方案，能够解决现有技术中第一基站和第二基站在进行数据传输时，一端基站不知道如何标识待传输的数据，另一端基站不知道当前接收的是什么数据等问题，提升了数据传输的高效性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍。
图1是本发明实施例提供的一种网络框架示意图；
图2是本发明实施例提供的一种数据传输方法的流程示意图；
图3是本发明实施例提供的一种下行数据传输方法的流程示意图；
图4是本发明实施例提供的又一种下行数据传输方法的流程示意图；
图5是本发明实施例提供的一种上行数据传输方法的流程示意图；
图6是本发明实施例提供的又一种数据传输方法的流程示意图；
图7A是本发明实施例提供的一种第一基站的结构示意图；
图7B是本发明实施例提供的又一种第一基站的结构示意图；
图8A是本发明实施例提供的一种第二基站的结构示意图；
图8B是本发明实施例提供的又一种第二基站的结构示意图；
图9是本发明实施例提供的一种数据传输系统的结构示意图。
具体实施方式
下面将结合本发明的附图，对本发明实施例中的技术方案进行详细描述。
请参见图1，是本发明实施例提供的一种网络框架示意图。该网络框架示意图包括核心网、第一基站、第二基站和用户终端(User Equipment，UE)。可选地，该网络框架示意图还可包括其他基站，如图示给出的第三基站。
在一些实施例中，在UE与第一基站建立了RRC连接后并且终端处于RRC连接状态后，若由于终端的移动性，该终端从第一基站移动到第二基站的覆盖范围并且第一基站决定将终端切换至第二基站，则此时第一基站为源基站，第二基站为目标基站。
可选地，在UE与第一基站建立了RRC连接后并且终端处于RRC连接状态后，若终端在一段时间内没有数据传输，则第一基站会通过状态转换的过程将终端从RRC连接态转换为RRC去激活状态，此时终端与第一基站均保留与连接态时相同的(或者部分的)终端上下文信息。但是处于RRC去激活状态的终端并不需要实时向网络侧报告测量信息，例如信道质量反馈信息。
若所述处于RRC去激活状态的终端从第一基站移动到第二基站的覆盖范围下，与第二基站(或者属于第二基站的小区)保持下行同步，并且在第二基站的覆盖范围内需要与网络进行交互，例如需要传输上行数据或者进行RNA更新等，则此时第一基站为驻留基站(Anchor gNodeB，AgNB)，第二基站为所述处于RRC去激活状态的终端的服务基站(New gNodeB，NgNB)。
所述RRC连接状态下的终端上下文信息可包括：终端的能力信息、终端的承载配置信息等信息，本发明不做限定。
服务基站是指UE处于RRC去激活状态时从驻留基站进行小区移动，重新切换到的新的基站，即UE当前所在的基站。UE和服务基站之间可存在相互通信，例如UE可接收服务基站发送的广播消息，且UE还可通过服务基站与网络侧(核心网)进行通信交互。
核心网可包括AMF网元(Access and Mobility Management Function，中文：接入以及移动性管理功能)。AMF网元为核心网控制面网元，提供用户(UE)的移动性管理和接入管理的功能。
在一些实施例中，所述第一基站、第二基站、及所述第三基站可以是指3G基站(NodeB)、4G基站(eNodeB，如eLTE基站)、或5G基站(gNodeB)，本发明不做限定。
eLTE基站(即4G基站)是指支持连接到5G核心网的E-UTRAN基站(Evolved UMTS Terrestrial Radio Access Network，中文：演进的UMTS陆地无线接入网)。eLTE基站可支持终端UE的RRC连接状态、RRC去激活状态等。
如图1所示，在UE处于RRC去激活状态时，基站、核心网和终端UE都保留有相应的终端上下文信息，并且基站与核心网为该终端保留了相应的连接。即是，当UE从RRC去激活状态切换至RRC连接状态时，不需要重新激活基站(如驻留基站AgNB)与核心网控制面网元(如AMF网元)之间的通信链路。
在一些实施例中，第一基站、第二基站和第三基站均可通过基站与核心网之间的接口 与核心网进行相互间的数据通信。第一基站和第二基站可通过基站间(Inter base station，Inter-BS)接口(如Xn接口)进行相互数据通信。
具体的，如果服务基站NgNB存在有上行数据需要传输到网络侧，则NgNB可通过Xn接口将上行数据传输给驻留基站AgNB，在由AgNB将上行数据传输至核心网。如果核心网存在有下行数据需要传输给驻留基站AgNB，则核心网可将下行数据发送给驻留基站AgNB，由驻留基站通过Xn接口将下行数据发送给服务基站NgNB。
基于图1所示网络框架示意图，请参见图2，是本发明实施例提供的一种数据传输方法，所述方法包括如下实施步骤。
本申请中，处于RRC去激活状态的终端UE向第一基站发送数据，由于终端的移动性，终端从第一基站移动到第二基站。如果终端与核心网之间存在数据需要传输，则可通过终端->第二基站->第一基站->核心网的通信链路进行相互的数据通信。因此在第一基站和第二基站实际数据通信时，第二基站需要获取第一基站相应的地址信息，用于第二基站在基站间的接口(例如Xn接口)上传输数据。
步骤S201、第二基站向第一基站发送第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输。相应地，所述第一基站接收所述第一消息。
在一些实施例中，所述第一消息可具体指示至少一个第一传输粒度的数据需要经过基站间的接口(例如Xn接口)由第一基站传输至第二基站，所述第一传输粒度可以为服务质量流(Quality of Service Flow，QoS Flow)，协议数据单元会话(Packet Date Unit Session，PDU session)、数据无线承载(Data Radio Bearer，DRB)。也即是，所述第一消息可携带至少一个第一传输粒度的标识，如flow1、Session1等。所述第一传输粒度的标识用于标识当前所述第二基站通过基站间的接口需要将哪些第一传输粒度的数据由第一基站传输至第二基站。
具体来说，第一消息可以指示哪一个具体的QoS流需要进行数据的传输，也可以指示哪一个具体的DRB需要进行数据传输，还可以指示哪一个具体的PDU会话需要进行数据的传输。
可选地，第一消息中还可以包括第一基站希望第二基站分配的地址个数、具备不同传输粒度的数据之间的映射关系等信息。这里将在下述实施例中进行具体阐述。
步骤S202、所述第一基站为所述第二基站待传输的数据分配至少一个地址，所述地址与所述数据相关联。
本申请中，所述第一基站可为所述第二基站待传输的数据以第二传输粒度分配至少一个地址。关于第二传输粒度可参见前述实施例中第一传输粒度的相关阐述，这里不再赘述。
具体来说，分配的地址可以用于标识Xn接口传输的QoS流，即通过该地址，第一基站可以识别从Xn接口接收的数据包属于哪一个QoS流；也可以用于标识Xn接口传输的DRB，即通过该地址，第一基站可以识别从Xn接口接收的数据包属于哪一个DRB；还可以用于标识Xn接口传输的PDU会话，即通过该地址，第一基站可以识别从Xn接口接收的数据包属于哪一个PDU会话。
在一些实施例中，所述地址可以是互联网协议地址(Internet Protocol Address，IP  Address)，该地址可以用于Xn接口数据面的数据传输。可选地，在该地址的基础上同时还可添加携带隧道端口标识，例如通用分组无线服务隧道协议(GPRS Tunnelling Protocol，GTP)的隧道端口标识，用于收发端基站间数据面的数据传输。收发端基站可通过该地址(也许还包括隧道端口标识，在本案中，统一称为地址)，可以识别需要在基站间的接口(例如Xn接口)上传输的会话、数据无线承载或者流，因此该地址可以用于基站间的接口(例如Xn接口)的上行或者下行数据的传输。
需要说明的是，本发明所涉及的地址不仅可以包括互联网协议地址、还可包括隧道端口标识、或者其他用于基站间的接口进行数据传输的地址，本发明实施例不做限定。
步骤S203、所述第一基站向所述第二基站发送第二消息，所述第二消息携带所述至少一个地址。相应地，所述第二基站接收所述第二消息。
具体的，所述第一基站以第二消息的形式将为所述待传输的数据分配的至少一个地址通知给所述第一基站。
在一些实施例中，所述第二消息还可携带所述至少一个地址各自对应的第二传输粒度的标识。即携带有各个第二传输粒度的标识与各个地址之间的绑定/映射关系(一一映射)。一个地址对应一个第二传输粒度的标识，即是一个地址用于标识所述第二基站通过基站接口向第一基站发送的某个具体的第二传输粒度的数据，即用于标识哪一个具体的第二传输粒度(如QoS流)需要通过基站间的接口(如Xn接口)进行数据的传输。
上述步骤S201中，所述第一消息还可用于指示所述第二基站按照第二传输粒度向所述第一基站传输数据。由于所述第二基站和所述第一基站进行相互通信时，由于协议规定收发端双方基站已知悉实际通信时所采用的传输粒度，假设为第二传输粒度。此时所述第二基站可不用通过所述第一消息将实际通信时所采用的所述第二传输粒度通知给所述第一基站。
所述第二传输粒度可以是指所述第二基站实际向第一基站发送待传输的数据时所采用的传输单位。所述第一传输粒度可以是指所述第二基站向所述第一基站告知所述第二基站存在哪些待传输的数据所对应的传输单位。关于第一传输粒度和第二传输粒度的相关阐述可具体参见前述实施例中的相关描述，这里不再赘述。
在一些实施例中，所述第一消息还可用于指示所述第二基站中存在至少一个第二传输粒度的数据需要经过基站间的接口(例如Xn接口)由第一基站传输至第二基站。也即是，所述第一消息还可携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于标识所述第二基站需要通过哪些具体的第二传输粒度(如PDU会话)来将数据由第一基站传输至第二基站。
在步骤S202中，所述至少一个地址中的每个地址用于标识所述待传输的数据中具备所述第二传输粒度形式的不同的数据或数据流，即是不同的地址用于标识所述待传输的数据中不同的所述第二传输粒度的数据或数据流。例如地址1用于标识所述待传输的数据中具备Session粒度的某个数据流，如需要进行数据传输的Session1。
在步骤S202中的一种实施方式中，若所述第一消息携带有地址个数，即所述第一消息用于指示/通知所述第二基站需要所述第一基站分配地址的数量(即地址个数)，则所述第一基站可为所述待传输的数据分配与所述地址个数数量相同的地址。
在一些实施例中，所述地址个数可以是根据传输粒度确定到的。可选地，所述所述地址个数是所述第二基站根据至少一个第一传输粒度的标识，及第一传输粒度的标识与第一传输粒度的标识之间的映射关系，确定到的所述第二传输粒度的标识的个数。也即是所述第二基站确定的自己想要向所述第一基站发送的至少一个第二传输粒度的数据的个数。
所述第一传输粒度的标识与所述第二传输粒度的标识之间的映射关系可以理解为：各个第二传输粒度的数据与各个第一传输粒度的数据之间的映射关系。例如，第二基站建立有3个会话Session进行数据传输，分别为Session1数据至Session3数据。其中，Session1数据下面建立有3个流flow数据，分别为flow1数据至flow3数据。Seeion2数据下面建立有3个流flow数据，分别为flow4数据至flow6数据。Seeion3数据面建立有4个流flow数据，分别为flow7数据至flow10数据。这里的第二传输粒度即为会话Session数据，第一传输粒度即为流flow数据，且各个第二传输粒度的标识与第一传输粒度的标识之间的映射关系也如上所述，例如Session1数据对应有3个flow数据，分别为flow1数据至flow3数据。
举例来说，假设第二基站想要向第一基站进行数据传输的flow有两个，分别为flow2和flow5，且实际按照seeion粒度(即第二传输粒度)来传输数据。这里的第一传输粒度为flow。引用上述第一传输粒度的标识与第二传输粒度的标识(即第一传输粒度的数据与第二传输粒度的数据)之间的映射关系，第二基站可知悉：flow2对应Session1，flow5对应Session2，即是第二基站可确定到自己实际需要向第一基站传输数据的是Session1和Session2。此时也确定到第二基站需要向第一基站发送会话Session的个数(即地址个数)为2。
在一些实施例中，所述地址个数可以是所述第二基站按照第二传输粒度向第一基站传输数据时所述第二传输粒度的数据的个数，或所述第二传输粒度的标识的个数。
在步骤S202的又一种实施方式中，若所述第一消息用于指示所述第二基站存在待传输的数据向第一基站传输，则第一基站可按照默认设置的地址个数来为所述待传输的数据分配与所述地址个数数量相同的地址。或者，第一基站可根据其他流程消息中携带的地址个数为所述待传输的数据分配与所述地址个数数量相同的地址。
在步骤S202的又一种实施方式中，若所述第一消息携带有至少一个第二传输粒度的标识，即所述第一消息用于指示所述第二基站存在至少一个第二传输粒度的标识需要通过基站间的接口进行数据的传输，则所述第一基站可为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址，一个地址对应一个第二传输粒度的标识。也即是，所述第一基站可为所述至少一个第二传输粒度的数据中的每个数据分配对应的地址，一个地址对应一个第二传输粒度的数据。
这里，第一基站不仅为每个第二传输粒度的数据(即每个第二传输粒度的标识)配置了地址，还配置了所述第二传输粒度的数据与所述地址之间的映射关系，即一个地址对应一个第二传输粒度的标识。
举例来说，假设第二基站通过第一消息通知第一基站：第二基站需要向第一基站传输数据的有Session1和Session3。在第一基站接收该第一消息后，第一基站可分别为Session1和Session2对应配置一个地址，假设为地址1和地址2。这里的第二传输粒度的标识为 seeion1和seeion2。地址1用于标识需要进行数据传输的Session1，地址2用于标识需要进行数据传输的Session2。
在步骤S102的又一种实施方式，若所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系(即第一传输粒度的数据对应归属在哪个第二数据粒度的数据中)。即是所述第一消息可具体用于指示所述第二基站存在至少一个第一传输粒度的标识需要通过基站间的接口进行数据的传输。可选地，所述第一消息还可用于指示所述第二基站实际以所述第二传输粒度的形式向所述第一基站传输数据。
相应地，在所述第一基站确定到所述第二基站实际按照所述第二传输粒度的形式向第一基站传输数据时，所述第一基站可根据所述至少一个第一传输粒度的标识，及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定出对应的至少一个所述第二传输粒度的标识或所述第二传输粒度的标识的个数。
一种可能的实现方式中，在第一基站确定到与所述至少一个第一传输粒度的标识所对应的所述第二传输粒度的标识的个数(即地址个数)后，所述第一基站可为所述第二基站待传输的数据分配与所述第二传输粒度的标识的个数数量相等的地址。
另一种可能的实现方式中，在第一基站确定到与所述至少一个第一传输粒度的标识所对应的至少一个第二传输粒度的标识后，所述第一基站可为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址。
可以理解的，在所述第一基站知悉所述第二基站需要向第一基站发送的至少一个第二传输粒度的标识(即要传输哪些第二传输粒度的数据)后，所述第一基站不仅可为所述至少一个第二传输粒度的标识对应分配了地址，还配置了各个所述第二传输粒度的标识与各个所述地址之间的映射/绑定关系(一一映射)。即一个地址用于标识一个第二传输粒度的数据，即标识一个具备第二传输粒度形式的数据或数据流。
举例来说，假设第二基站通过第一消息通知所述第一基站：第二基站将按照seeion粒度(即第二传输粒度)向第一基站发送flow2和flow5这两个flow数据。引用上述例子中第一传输粒度的标识与第二传粒度的标识之间的映射关系。在第一基站接收到所述第一消息后，可知悉到flow2数据对应Session1数据，flow5数据对应Session2数据，即第一基站可确定到第二基站当前想要向第一基站发送Session1和Session2数据。接着，第一基站可分别为seeion1和Session2数据分配对应的地址，例如为Session1数据分配地址1，为Session2数据分配地址2。然后，所述第一基站可通过第二消息将为第二基站中的第二传输粒度的数据的标识分配的地址及所述第二传输粒度的数据的标识与所述地址之间的映射关系(即Session1数据对应地址1，Session2数据对应地址2)通知给第二基站。
在一些实施例中，若步骤S203所述第二消息中携带所述至少一个地址，不携带所述地址与所述第二传输粒度的数据的标识之间的映射关系(即所述至少一个地址各自对应的第二传输粒度的标识)。在第二基站接收所述第二消息获知到所述至少一个地址后，由于第二基站知道自己想要向第一基站发送哪些第二传输粒度的数据(即至少一个第二传输粒度的标识)，此时所述第二基站可为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址。
相应地，所述第二基站可向所述第一基站发送第三消息，所述第三消息携带有所述至 少一个地址各自对应的第二传输粒度的标识。也即是所述第二基站通过第三消息将为所述至少一个地址中的每个地址分配的第二传输粒度的标识通知给所述第一基站。
在一些实施例中，所述第一消息可以包括寻呼消息、终端上下文响应消息、终端上下文请求消息等，所述第二消息可以包括终端上下文请求消息、数据传输地址通知消息、终端上下文响应消息等，所述第三消息可以包括数据传输地址通知消息，在下述实施例中进行相关地具体阐述。
在一些实施例中，若所述至少一个地址的地址个数少于所述第二基站中待传输的所述第二传输粒度的数据的个数(即所述第二传输粒度的标识的个数)，则所述第二基站可继续执行上述步骤S201至S203以获取所述第一基站重新分配的至少一个地址，重复流程，直至所述第一基站分配的地址的数量不少于所述发送端待传输的所述第二传输粒度的数据的个数(即所述第二传输粒度的标识的个数)。
特别是，在步骤S202所述第一基站按照默认设置的地址个数或其他流程消息中携带的地址个数分配所述至少一个地址的情况下，很容易出现分配的所述地址的地址个数少于所述第二传输粒度的标识的个数。此时，第二基站可重复执行步骤S201至步骤S203，直至所述第一基站分配的所述地址的个数不少于所述第二传输粒度的标识的个数，以便能为所述至少一个第二传输粒度的标识中的每个标识对应分配一个地址。
需要说明的是，所述第一基站为所述第二基站待传输的数据(即至少一个第二传输粒度的标识)分配的地址互不相同。
举例来说，假设第二基站想要向第一基站进行数据传输的有7个seeion，分别为seeison1数据至Session7数据。第二基站可向第一基站发送第一消息通知第二基站存在待传输的数据需要传输。在第一基站接收到第一消息后，可根据默认设置的地址个数，假设默认设置4个地址，分配与所述地址个数数量相同的地址。这里即分配有4个地址，假设分配为地址1至地址4。第一基站可向第二基站发送第二消息，以将上述分配的4个地址通知给第二基站。在第二基站接收所述第二消息获知到第一基站分配了4个地址，少于需要传输的seeion数据的数量(4<7)。因此，第二基站需再次向第一基站发送第一消息，以便再次获取到第一基站为第二基站待传输的Session数据新分配的4个地址，假设分别为地址5至地址8。此时8个地址足以用来绑定传输7个seeion数据了。在第二基站获知到第一基站分配的8个地址(即地址1至地址8)后，所述第二基站可为7个seeion数据各自分配对应的地址，假设seeion1数据对应分配地址1，Session2数据对应分配地址2，…，Session7数据对应分配地址7。可选地，第二基站还可向第一基站发送第三消息，以将上述为7个seeion数据各自对应分配的地址通知给所述第一基站。
在第二基站实际向第一基站发送seeison数据时，可在Session数据前面添加上该Session数据对应分配的地址的包头，以通过该地址来标识与该地址对应的Session数据。例如，在第二基站实际向第一基站发送seeison1数据(具体向第一基站的地址1发送seeison1数据)时，可在Session1数据前添加上地址1的包头，这样在第一基站接收到Session1数据时，可通过解析包头中的地址1获知到当前第二基站发送的是与地址1对应的Session1数据。
基于前述实施例，下面介绍本发明实施例涉及的下行数据传输的实施例。在下行数据 传输实施例中，第二基站可为驻留基站(AgNB)，第一基站可为服务基站(NgNB)。
图3和图4分别示出了两种下行数据传输实施例。其中图3示出了一种下行数据传输方法的流程示意图，所述方法包括如下实施步骤。
步骤S301、驻留基站向服务基站发送第一寻呼消息(paging)，所述寻呼消息携带终端UE的标识信息，该标识信息可以在RNA范围内唯一指示所述终端。相应地，所述服务基站接收所述第二寻呼消息。
在一些实施例中，该第一寻呼消息还可以携带下行数据指示信息，该下行数据指示信息用于指示在驻留基站存在该终端的待传输的下行数据。
可选的，该第一寻呼消息还可以携带地址个数指示信息，所述地址个数指示信息指示服务基站需要分配的地址个数，以实现驻留基站通过基站间的接口(如Xn接口)向服务基站传输驻留基站保留的所述终端的待传输的下行数据。所述终端的待传输的下行数据也是所述驻留基站需要通过Xn接口向所述服务基站发送的待传输的数据。这里的第一寻呼消息可以是所述第一消息的一种体现方式。
在一些实施例中，在服务基站接收到第一寻呼消息后，可通过消息解析获知到驻留基站需要向服务基站传输下行数据。那么所述服务基站可为所述驻留基站待传输的数据分配至少一个地址。
步骤S302、所述服务基站向终端发送第二寻呼消息，所述第二寻呼消息携带终端UE的标识信息。相应地，所述终端接收所述第二寻呼消息。
步骤S303、所述终端向所述服务基站发送RRC连接恢复请求消息(RRC Connection Resume Request)，所述RRC连接恢复请求消息用于请求恢复所述终端与所述服务基站之间的RRC连接。相应地，所述服务基站接收所述RRC连接恢复请求消息。
所述RRC连接恢复请求消息携带终端的标识信息，该标识信息可以在RNA区域唯一指示所述终端，在本案中，也可是恢复标识信息，如Resume ID信息。
具体的，在所述终端接收到所述服务基站发送的第二寻呼消息时，由于所述终端处于RRC去激活状态，因此所述终端还需向服务基站(即当前所述终端所在的基站)发送RRC连接恢复请求消息，以建立所述终端与所述服务基站之间的RRC连接，方便所述终端与所述服务基站之间的安全数据通信。
步骤S304、所述服务基站向所述驻留基站发送终端上下文请求消息(Retrieve UE Context Request)，所述终端上下文请求消息用于获取所述驻留基站中保留的终端上下文信息，所述终端上下文请求消息携带有所述至少一个地址。相应地，所述驻留基站接收所述终端上下文请求消息。
具体的，在所述服务基站接收到所述RRC连接恢复请求消息后，发现自身基站中并不没有终端上下文信息，因此向驻留基站发送终端上下文请求消息，以获取所述驻留基站中保留的终端上下文信息。此外，所述终端上下文请求消息中可携带有所述至少一个地址，以将所述服务基站配置的至少一个地址通知给所述驻留基站。这里的终端上下文请求消息可以是第二消息的一种体现方式。
步骤S305、所述驻留基站为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识，并获取所述驻留基站中保留的终端上下文信息。
具体的，所述驻留基站在接收到所述终端上下文请求消息后，可获取所述驻留基站中获取的终端上下文信息。且针对所述驻留基站而言，自己知道需要向服务基站传输哪些第二传输粒度的数据(如需要进行数据传输的seeion1和seeison2)。假设驻留基站知悉自身也将按照第二传输粒度(如Session粒度)向服务基站发送待传输的数据，且知悉当前需要向服务基站传输数据所对应的第二传输粒度的标识，则驻留基站可根据接收的所述至少一个地址，分别为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识。一个地址对应一个第二传输粒度的标识。
也即是，所述驻留基站可将所述至少一个地址中的每个地址与至少一个第二传输粒度的标识进行一一映射。具体的，所述驻留基站确定出某一个在Xn接口上传输的下行PDU会话/DRB/QoS流所采用的地址。关于第二传输粒度的介绍可具体参见前述实施例中的相关阐述，这里不再赘述。
步骤S306、所述驻留基站向所述服务基站发送终端上下文响应消息(Retrieve UE Context Response)，所述终端上下文响应消息携带所述终端上下文信息和所述至少一个地址各自对应的第二传输粒度的标识。相应地，所述服务基站接收所述终端上下文响应消息。
在一些实施例中，所述终端上下文响应消息可携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于指示/标识所述驻留基站需要向所述服务基站发送所述标识对应的第二传输粒度的数据。所述第二传输粒度的标识可包括以下中的任一项：PDU会话标识、QoS流标识、DRB标识。
可选地，所述终端上下文响应消息还可指示不同传输粒度的标识之间的映射关系，也即是所述PDU会话、QoS流、以及DRB中任意两者或三者之间的映射关系，其中包括有第一传输粒度的标识与第二传输粒度的标识之间的映射关系。具体的，映射关系可指示每个具体的QoS流对应哪一个PDU会话，每个具体的QoS流对应哪一个DRB，每个具体的DRB对应哪一个PDU会话。例如DRB1和DRB2对应PDU会话1，DRB3和DRB4对应PDU会话2，QoS流1和QoS流2对应DRB3，因此QoS流1和QoS流2对应PDU会话2。
可选地，所述终端上下文响应消息还可包括步骤S305中的所述地址与所述第二传输粒度的标识之间的映射关系，该映射关系指示PDU会话/DRB/QoS流的下行数据在Xn接口上传输时所采用的地址。
举例来说，假设服务基站为驻留基站待传输的数据分配了3个地址，分别为地址1至地址3。驻留基站知悉自己需要向服务基站进行数据传输的Session1、Session2和Session3，在服务基站将上述3个地址通知给驻留基站后，驻留基站可将这3个地址与3个Session进行绑定/映射，一个地址对应一个Session。假设驻留基站将地址1对应分配给Session1，地址2对应分配给Session2，地址3对应分配Session3。可选地，驻留基站可将上述地址与Session之间的绑定/映射关系通知给服务基站。
具体的，所述驻留基站可将获取的终端上下信息和分配的所述至少一个地址中每个地址对应的第二传输粒度的标识，携带在所述终端上下文响应消息中，以通知给所述驻留基站。这里所述终端上下文消息可以是第三消息的一种体现方式。
步骤S307、所述服务基站根据所述终端上下文信息，建立所述终端与所述服务基站之 间的RRC连接。
具体的，所述服务基站接收所述终端上下文响应消息，可通过消息解析获知所述终端上下文信息、所述至少一个地址各自对应的第二传输粒度的标识等信息。所述服务基站可根据所述终端上下文信息，建立所述终端与所述服务基站间的RRC连接。
在一些实施例中，所述服务基站可存储所述至少一个地址各自对应的第二传输粒度的标识，以便所述驻留基站向所述服务基站发送这些第二传输粒度的标识所对应的数据(如Session1数据)时，服务基站可根据地址与第二传输粒度的标识之间的映射关系，获知当前驻留基站发送的是哪些第二传输粒度的数据，即驻留基站使用哪些具体的PDU会话/DRB/QoS流进行数据的传输。
举例来说，引用图2所述实施例，服务基站为驻留基站待传输的数据分配了2个地址，分别为地址1和地址2，且通过终端上下文请求消息通知给驻留基站。驻留基站当前需要发送Session1数据和Session2数据，在获知到地址1和地址2后，驻留基站可分别为Session1数据和Session2数据分配一个地址，假设为Session1数据分配地址1，Session2数据分配地址2。且将上述地址与第二传输粒度的数据(即待传输的数据，Session1数据和Session2数据)之间的绑定/映射关系通过终端上下文响应消息通知给服务基站。在驻留基站实际以Session粒度传输这两个待传输的数据时，驻留基站基站可在待传输的数据前面添加上对应的地址，以通知服务基站当前传输的待传输数据。例如，驻留基站在传输Session1数据时，可在Session1数据前添加地址1的包头。在服务基站接收到携带地址1包头的seeion1数据时，可根据地址1与Session1数据的映射关系，服务基站可确定出当前驻留基站发送的与地址1对应的Session1数据。同样，服务基站可根据地址2与Session2数据的映射关系，确定出当前驻留基站发送的与地址2对应的Session2数据。
步骤S308、所述服务基站向所述终端UE发送RRC连接恢复响应消息(RRC Connection Resume Response)，以通知恢复建立所述终端与所述服务基站间的RRC连接。
具体的，服务基站可响应RRC连接恢复请求消息，根据获取的终端上下文信息建立UE与服务基站之间的RRC连接。接着，服务基站可向终端UE发送RRC连接恢复响应消息，通知UE已恢复建立UE与服务基站间的RRC连接，以便后续UE与服务基站进行相互间的安全数据通信。
在一些实施例中，若所述第一寻呼消息用于指示/通知驻留基站存在待传输的下行数据需要向服务基站传输，则在服务基站接收到所述第一寻呼消息后，服务基站可按照默认设置的地址个数或者其他流程消息中携带的地址个数，为所述待传输的数据(即下行数据)分配与所述地址个数数量相同的地址。
在一些实施例中，所述第一寻呼消息还可携带地址个数指示信息，所述地址个数指示信息用于指示服务基站需要分配的地址个数。在服务基站知悉需要分配地址的个数后，可根据所述地址个数为所述待传输的数据分配与所述地址个数数量相同的地址。
在一些实施例中，所述第一寻呼消息还可用于通知驻留基站按照第二传输粒度向服务基站发送待传输的数据，即驻留基站通过Xn接口进行数据传输的粒度。
所述第一传输粒度和所述第二传输粒度可以包括QoS流(flow)、PDU会话(seeion)、无线承载DRB中的任意一种。
在一些实施例中，所述第一寻呼消息中携带的地址个数是根据传输粒度确定的。具体的，所述地址个数可以是驻留基站根据当前需要传输的至少一个第一传输粒度的标识，和所述第一传输粒度的标识与所述第二传输粒度的标识之间的映射关系确定的。具体可参见前述实施例中的相关具体阐述，这里不再赘述。
举例来说，引用图2所述实施例第一传输粒度的标识与第二传输粒度的标识间的映射关系，假设驻留基站想要传输的第一传输粒度的标识所对应的数据为flow1数据、flow2数据、flow5数据和flow7数据。根据flow数据与seeion数据之间的映射关系，驻留基站可知实际可向服务基站传输的是seeion1数据、seeion2数据和seeion3数据，同时也知道了想要传输Session数据的个数为3，即地址个数为3。
在一些实施例中，步骤S203中所述服务基站可将分配的至少一个地址携带在所述终端上下文请求消息中传输给驻留基站。相应地，在所述驻留基站接收到所述至少一个地址后，由于驻留基站自身知悉自己想要向服务基站发送的哪些第二传输粒度的数据(即至少一个第二传输粒度的标识，如上述的Session1至Session3数据)，所述驻留基站可为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识。不同的地址用于标识所述待传输的数据中具备所述第二传输粒度形式的不同的数据或数据流。
举例来说，假设服务基站为驻留基站待传输的数据分配了3个地址，分别为地址1至地址3。驻留基站知悉自己需要向服务基站发送Session1数据、Session2数据和Session3数据，在服务基站将上述3个地址通知给驻留基站后，驻留基站可将这3个地址与3个Session数据进行绑定/映射，一个地址对应一个Session数据。假设驻留基站将地址1对应分配给Session1数据，地址2对应分配给Session2数据，地址3对应分配Session3数据。可选地，驻留基站可将上述地址与Session数据之间的绑定/映射关系通知给服务基站。
图4示出了又一种下行数据传输方法的流程示意图，所述方法包括如下实施步骤。
步骤S401、驻留基站向服务基站发送第一寻呼消息(paging)，所述第一寻呼消息携带终端的标识信息，该标识信息可以在RNA范围内唯一指示所述终端。相应地，所述服务基站接收所述第二寻呼消息。
步骤S402、所述服务基站向终端发送第二寻呼消息，所述第二寻呼消息携带终端的标识信息。
具体的，驻留基站可通过Xn接口将第一寻呼消息发送给服务基站。服务基站可通过公共信道向终端发送所述第二寻呼消息转发给终端UE。所述第一寻呼消息和所述第二寻呼消息均用于请求寻找/搜索与所述标识信息所对应的终端。在一些实施例中，所述第一寻呼消息和所述第二寻呼消息可以是指同一个消息。
步骤S403、所述终端向服务基站发送RRC连接恢复请求消息(RRC Connection Resume Request)，所述RRC连接恢复请求消息用于请求恢复所述终端与所述服务基站之间的RRC连接。相应地，所述服务基站接收所述RRC连接恢复请求消息。
所述RRC连接恢复请求消息可携带终端的标识信息，该标识信息可以在RNA区域唯一指示所述终端。在本案中，该标识信息也可是恢复标识信息，如Resume ID信息。
步骤S404、所述服务基站向所述驻留基站发送终端上下文请求消息(Retrieve UE  Context Request)，所述终端上下文请求消息用于获取所述驻留基站中保留的终端上下文信息，以建立终端UE与服务基站间的RRC连接。
步骤S405、所述驻留基站接收所述RRC连接恢复消息，获取所述驻留基站中保留的终端上下文信息。关于步骤S402至步骤S405可具体参见前述实施例中步骤S302至步骤S304的相关描述，这里不再赘述。
步骤S406、所述驻留基站向所述服务基站发送终端上下文响应消息(Retrieve UE Context Response)，所述终端上下文响应消息携带所述终端上下文信息，所述终端上下文响应消息携带下行数据指示信息，所述下行数据指示信息用于指示所述驻留基站存在待传输的下行数据需要传输。
具体的，所述下行数据指示信息可具体用于指示所述驻留基站需要向所述服务基站传输哪些第二传输粒度的数据(即至少一个第二传输粒度的标识)。在一些程度上可理解为：所述终端上下文响应消息中可携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于指示所述驻留基站需要向所述服务基站发送该标识对应的第二传输粒度的数据。所述第二传输粒度的标识可以是PDU会话标识、也可以是QoS流标识、还可以是DRB标识。
在一些实施例中，所述终端上下文响应消息还可指示不同传输粒度的标识之间的映射关系，即指示有不同的PDU会话、QoS流、DRB中任意两者或三者之间的映射关系，其中包括有第一传输粒度的标识与第二传输粒度的标识之间的映射关系。具体的，该映射关系指示每个具体的QoS流对应哪一个PDU会话，每个具体的QoS流对应哪一个DRB，每个具体的DRB对应哪一个PDU会话。例如DRB1和DRB2对应PDU会话1，DRB3和DRB4对应PDU会话2，QoS流1和QoS流2对应DRB3，因此QoS流1和QoS流2对应PDU会话2。
在一些实施例中，所述下行数据指示信息可具体用于以第一传输粒度指示在驻留基站存在有待传输的下行数据。第一传输粒度可以为PDU会话、DRB、QoS流中的任一项。举例来说，若第一传输粒度为PDU会话，则对于任何一个PDU会话来说，若第二基站希望在Xn接口发送下行数据，则在该PDU会话中可包括所述下行数据指示信息。
示例性地，第一传输粒度为QoS流，如下表1给出一种终端上下文响应消息(即第一消息)的具体体现方式中(部分)。
表1
Figure PCTCN2018085663-appb-000001
由上述表1可知，L3中可携带有PDU会话的标识(可视为第二传输粒度的标识)、L3 和L4至L6中指示了PDU会话的标识与QoS流的标识之间的映射/绑定关系，即某个具体的PDU会话下需要建立哪几个QoS流。L6和L7中指示了哪些QoS流需要进行数据的传输，即指示了进行数据传输的QoS流的标识。具体的，L7中还指示了第二基站以QoS流的粒度(可视为第一传输粒度)告知第一基站进行数据的传输，即以QoS流的粒度指示待传输的数据。
示例性地，第一传输粒度为PDU会话，如下表2给出一种终端上下文响应消息(即第一消息)的具体体现方式中的部分。
表2
Figure PCTCN2018085663-appb-000002
由上述表2可知，L3中可携带有PDU会话的标识(可视为第二传输粒度的标识)、L3和L7中指示了PDU会话的标识与QoS流的标识之间的映射/绑定关系，即某个具体的PDU会话下需要建立哪几个QoS流。L3和L4中指示了哪些PDU会话需要进行数据的传输，即指示了进行数据传输的PDU会话的标识。具体的，L3和L4中还指示了第二基站以PDU会话的粒度(第一传输粒度)告知第一基站进行数据的传输，即以PDU会话的粒度指示待传输的数据。
在一些实施例中，所述下行数据指示信息具体以第一传输粒度指示所述驻留基站存在有哪些第一传输粒度的下行数据(即至少一个第一传输粒度的标识)需要传输，且还指示了第一传输粒度的标识与第二传输粒度的标识之间的映射关系。那么所述服务基站可根据所述至少一个第一传输粒度的标识、和第一传输粒度的标识与第二传输粒度的标识之间的映射关系，确定出对应的至少一个第二传输粒度的标识。例如第一传输粒度为QoS流，第二传输粒度为PDU会话，可根据上述表1中指示的映射关系，可确定每个QoS流的标识所对应归属在哪个的PDU会话中。具体可参见前述实施例的相关介绍，这里不再赘述。
需要说明的是，并非针对每一个第二传输粒度或第一传输粒度的标识都携带有下行数据指示信息，针对于驻留基站存在有需进行下行数据传输的这些第二传输粒度或第一传输粒度，才会携带有下行数据指示信息。
步骤S407、相应地，所述服务基站接收所述终端上下文响应消息。所述服务基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址，一个地址对应一个第二传输粒度的标识。
具体的，所述服务基站基于S406中的下行数据指示消息，以及PDU会话、DRB和QoS流之间的映射关系，以第二传输粒度为待传输的数据分配地址，并向所述驻留基站发 送数据传输地址通知消息(Data Forwarding Address Notification)，所述数据传输地址通知消息包括待传输数据对应的地址信息。第二传输粒度可以是QoS流，也可以是DRB，也可以是PDU会话。具体的，若第一传输粒度为QoS流，则第二传输粒度可以是QoS流，也可以是DRB，也可以是PDU会话；若第一传输粒度为DRB，则第二传输粒度可以是DRB，也可以是PDU会话；若第一传输粒度为PDU会话，则第二传输粒度为PDU会话。举例来说，若DRB1和DRB2对应PDU会话1，DRB3和DRB4对应PDU会话2，QoS流1和QoS流2对应DRB3，因此QoS流1和QoS流2对应PDU会话2，且第二传输粒度为PDU会话，第一传输粒度为QoS流，若QoS流1在驻留基站有待传输的下行数据，则服务基站为PDU会话2分配地址。
步骤S408、所述服务基站向所述驻留基站发送数据传输地址通知消息，所述数据传输地址通知消息携带有所述至少一个地址各自对应的第二传输粒度的标识。
具体的，所述服务基站可通过数据传输地址通知消息，将服务基站为驻留基站待传输的数据分配的至少一个地址，及所述至少一个地址各自对应的第二传输粒度的标识通知给驻留基站。这里的数据传输地址通知消息可以是第二消息的又一种体现方式。
参见如下表3示例性地给出一种数据传输地址通知消息(即第二消息)的具体体现方式中的部分。
表3
Figure PCTCN2018085663-appb-000003
由上述表3可知，L6中携带了PDU会话的标识(即第二传输粒度的标识)、L6和L7中共同指示了PDU会话的标识与下行地址之间的映射/绑定关系(即所述第二传输粒度的标识与所述地址之间的映射关系)。具体的，某个具体的PDU会话对应的某个具体的下行地址。
步骤S409、所述服务基站向所述终端发送RRC连接恢复消息(RRC Connection Resume)，所述RRC连接恢复消息用于通知所述终端恢复建立了与所述服务基站之间的RRC连接。需要说明的是，步骤S408和步骤S409可以是并列地，也即是可以先执行步骤S409后执行步骤S408，本发明实施例不做限定。
基于前述实施例，下面介绍本发明实施例涉及的上行数据传输的实施例。在上行数据传输实施例中，第二基站可为服务基站(NgNB)，第一基站可为驻留基站(AgNB)。
图5示出了一种上行数据传输方法的流程示意图，所述方法包括如下实施步骤。
步骤S501、终端向服务基站发送RRC连接恢复请求消息(RRC Connection Resume Request)，所述RRC连接恢复请求消息用于请求恢复所述终端与所述服务基站之间的RRC连接。相应地，所述服务基站接收所述RRC连接恢复请求消息。
步骤S502、所述服务基站向所述驻留基站发送终端上下文请求消息(Retrieve UE Context Request)，所述终端上下文请求消息用于获取所述驻留基站中保留的终端上下文信息，还用于指示所述服务基站存在待传输的上行数据需要向所述驻留基站传输。相应地，所述驻留基站接收所述终端上下文请求消息。
具体的，所述终端上下文请求消息携带有上行数据指示信息，所述上行数据指示信息用于指示所述服务基站存在待传输的上行数据需要向所述驻留基站传输。
在一些实施例中，所述上行数据指示信息可具体用于指示服务基站当前存在哪些第二传输粒度的上行数据(即至少一个第二传输粒度的标识)需要传输给驻留基站。这里的终端上下文请求消息可以是第一消息的又一种体现方式。关于步骤S501至步骤S502可具体参见前述实施例中的相关描述，这里不再赘述。
在一些实施例中，所述终端上下文请求消息可携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于指示所述服务基站需要向所述驻留基站传输所述标识对应的第二传输粒度的上行数据。所述第二传输粒度的标识可以是PDU会话标识、也可以是QoS流会话标识、还可以是DRB标识。
可选地，所述终端上下文响应消息还指示不同传输粒度的标识之间的映射关系，也即是所述PDU会话、QoS流、以及DRB中任意两者或三者之间的映射关系，当然包括第一传输粒度的标识与第二传输粒度的标识之间的映射关系。具体可参见前述相关实施例，这里不再赘述。
步骤S503、所述驻留基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址，并获取终端上下文信息。不同的地址用于标识所述待传输的数据中具备所述第二传输粒度形式的不同数据流。
具体的，所述驻留基站接收所述终端上下文请求消息后，可获取所述驻留基站中保留的终端上下文信息。同时，在驻留基站知悉服务基站当前需要传输哪些第二传输粒度的上行数据(即至少一个第二传输粒度的标识)后，所述驻留基站可为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址，一个第二传输粒度的标识对应一个地址。
也即是，所述驻留基站以第二传输粒度为待传输的数据分配地址。即所述驻留基站为在Xn接口上传输的下行PDU会话/DRB/QoS流分配并确定出其对应采用的地址。
步骤S504、所述驻留基站向所述服务基站发送终端上下文响应消息(Retrieve UE Context Response)，所述终端上下文响应消息携带所述终端上下文信息和所述至少一个地址各自对应的第二传输粒度的标识。相应地，所述服务基站接收所述终端上下文响应消息。
具体的，所述驻留基站在获取到终端上下文信息，及为至少一个第二传输粒度的标识各自分配对应的地址后，可以终端上下文响应消息的形式通知给服务基站。这里的终端上下文响应消息可以是第二消息的又一种体现方式。
步骤S505、所述服务基站根据所述终端上下文信息，建立所述终端UE与所述服务基 站之间的RRC连接。
步骤S506、所述服务基站向所述终端发送RRC连接恢复响应消息(RRC Connection Resume Response)，所述RRC连接恢复响应消息用于通知所述终端恢复建立了与所述服务基站之间的RRC连接。
需要说明的是，步骤S504还可放在步骤S506之后执行，本发明实施例不做限定。
在一些实施例中，步骤S502中所述终端上下文请求消息用于指示所述服务基站存在待传输的上行数据需要向所述驻留基站传输，但不指出所述服务基站存在哪些第二传输粒度的数据(即至少一个第二传输粒度的标识)需要向驻留基站传输时，步骤S403在驻留基站接收到所述终端上下文请求消息后，驻留基站可根据默认设置的地址个数或其他流程消息中携带的地址个数为所述服务基站待传输的数据(这里即上行数据)分配与所述地址个数数量相同的地址。
在一些实施例中，步骤S502中所述终端上下文请求消息用于指示所述服务基站存在待传输的上行数据需要向所述驻留基站传输，且所述终端上下文请求消息携带有地址个数(即服务基站需要驻留基站分配地址的个数)，则在步骤S503中驻留基站可为所述服务基站待传输的数据(这里即上行数据)分配与所述地址个数数量相同的地址。
相应地，在步骤S504中所述终端上下文响应消息就携带了所述终端上下文信息和所述至少一个地址(即与所述地址个数数量相同的地址)，并不是携带所述至少一个地址各自对应的第二传输粒度的标识。
在一些实施例中，所述终端上下文请求消息还可用于指示所述服务基站实际按照第二传输粒度向驻留基站发送待传输的上行数据。
在一些实施例中，所述服务基站知悉自己需要向驻留基站发送哪些第一传输粒度的数据(即至少一个第一传输粒度的标识)，所述服务基站可根据至少一个第一传输粒度的标识、及所述第一传输粒度的标识与所述第二传输粒度的标识之间的映射关系，确定出对应的至少一个第二传输粒度的标识和/或至少一个第二传输粒度的标识的个数。这里所述至少一个第二传输粒度的标识的个数即是所述地址个数。
在一些实施例中，步骤S502中所述终端上下文请求消息用于指示所述服务基站存在哪些第一传输粒度的数据(即至少一个第一传输粒度的标识)需要向所述驻留基站传输，此时所述终端上下文请求消息还携带有所述第二传输粒度的标识与所述第一传输粒度的标识之间的映射关系。可选地，所述终端上下文请求消息还用于指示所述服务基站实际按照第二传输粒度向所述驻留基站发送待传输的数据。
相应地，所述驻留基站接收所述终端上下文请求消息。在所述驻留基站确定到所述服务基站实际按照第二传输粒度向所述驻留基站传输数据时，在步骤S503中驻留基站可根据所述至少一个第一传输粒度的标识、及所述第一传输粒度的标识与所述第二传输粒度的标识之间的映射关系确定出对应的至少一个第二传输粒度的标识和/或至少一个第二传输粒度的标识的个数。
在一种可能的实施方式中，如果驻留基站确定到所述至少一个第二传输粒度的标识，则可继续执行步骤S503。
在又一种可能的实施方式中，如果驻留基站确定到所述至少一个第二传输粒度的标识 的个数(即地址个数)后，在步骤S503中驻留基站可为所述服务基站待传输的数据(这里即上行数据)分配与所述地址个数数量相同的地址。同样在步骤S504中所述终端上下文响应消息就携带的是所述至少一个地址(即与所述地址个数数量相同的地址)，并不是携带所述至少一个地址各自对应的第二传输粒度的标识。
在一些实施例中，如果步骤S504中向驻留基站发送的所述终端上下文响应消息中携带的是所述至少一个地址，而不是所述至少一个地址各自对应的第二传输粒度的标识；那么驻留基站在获知到所述至少一个地址后，可为所述至少一个地址中每个地址分配对应的第二传输粒度的标识(即分配一个用于在Xn接口上传输某个所述待传输的数据中具备第二传输粒度形式的数据或数据流)。
可选地，所述驻留基站可向服务基站发送数据传输地址通知消息，所述数据传输地址通知消息携带所述至少一个地址各自对应的第二传输粒度的标识，以将地址与第二传输粒度的标识之间的绑定/映射关系通知给所述服务基站。相应地，所述服务基站接收所述数据传输地址通知消息，这里的数据传输地址通知消息可以是第三消息的又一种体现方式。
需要说明的是，关于步骤S501至步骤S504具体可参见前述实施例中的相关内容描述，这里不再赘述。
基于前述实施例，图6示出了本发明实施例提供的另一种数据传输方法的流程示意图，所述方法包括如下实施步骤。这里涉及的数据传输为上行数据传输，第一基站可为源基站，第二基站可为目标基站。
本申请中，处于连接状态的终端UE向第一基站(即源基站)发送上行数据，由于终端的移动性，终端从第一基站移动到第二基站，并且基于测量报告等信息，第一基站决定将终端切换至第二基站(即目标基站)，为了保证终端的零毫秒切换时延，在切换的过程中的一段时间内，终端需要同时向两个基站发送上行数据。具体来说，终端可以通过终端->第二基站->第一基站->核心网的通信链路和终端->第一基站->核心网的通信链路向核心网侧发送上行数据。因此第二基站需要获取第一基站相应的上行地址信息，用于第二基站在Xn接口上传输上行数据。
步骤S601、第一基站向第二基站发送第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站与所述第二基站间需要传输的所述第一传输粒度的数据。相应地，所述第二基站接收所述第一消息。
在一些实施例中，所述第一传输粒度可以包括以下中的任一项：PDU会话、QoS流、DRB。所述第一传输粒度的标识可以是以下中的任一项：PDU会话标识、QoS流标识、DRB标识。
在一些实施例中，所述第一消息可携带上行数据指示信息，所述上行数据指示信息可具体用于指示哪些第一传输粒度(即至少第一传输粒度的第一标识)需要进行数据的传输，还可指示所述至少第一传输粒度的第一标识各自对应的地址。在一定程度上可理解为所述第一消息可携带所述至少一个第一传输粒度的第一标识，所述第一基站实际向所述第二基站发送第一消息时，会将每个第一传输粒度的第一标识各自对应的地址添加到所述第一消息中进行传输。即是所述第一基站通过所述第一消息实际也是将所述至少一个第一传输粒 度的第一标识各自对应的地址通知给所述第二基站。
这里的地址也可是所述第一传输粒度的第一标识对应的上行数据传输地址信息。一个第一传输粒度的第一标识对应一个地址(或一个上行数据传输地址信息)。
示例性地，以QoS流为第一传输粒度作为示例(以PDU会话和DRB为第一传输粒度也可很容易的基于下表得到)，如下表4给出一种第一消息的具体体现方式中的部分。
表4
Figure PCTCN2018085663-appb-000004
由上述表4可知，L3中可携带有PDU会话的标识(可视为第一传输粒度的第一标识)、L3和L6中指示了PDU会话的标识与QoS流的标识之间的映射/绑定关系，即某个具体的PDU会话下可建立哪几个QoS流，即一个PDU会话标识可对应至少一个QoS流的标识。L6和L7中指示了QoS流的标识与地址之间的映射关系，即某个具体的QoS流对应的上行地址(或上行地址信息)。
在一些实施例中，第一基站向第二基站发送第一消息之前，还包括：所述第一基站为所述至少一个第一传输粒度的标识分配对应的地址。具体可参见前述实施例中的相关描述，这里不再赘述。
在一些实施例中，若所述第一基站获知到所述终端UE需要进行数据传输的至少一个第二传输粒度的标识，则所述第一基站可根据所述至少一个第二传输粒度的标识，及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定出对应的至少一个第一传输粒度的第一标识。接着，所述第一基站可为所述至少一个第一传输粒度的第一标识中的每个第一标识分配对应的地址。具体可参见前述实施例中的相关描述，这里不再赘述。
需要说明的是，并非针对每一个第一传输粒度的第一标识都携带有上行数据指示信息，针对于驻留基站存在有需进行下行数据传输的这些第二传输粒度或第一传输粒度，才会携带有下行数据指示信息。
步骤S602、所述第二基站根据空口资源信息，确定出第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
具体的，所述第二基站可根据空口的时频资源等因素决定为所述终端/所述第一基站建立哪些需要进行数据传输的第一传输粒度。即所述第二基站可根据空口的时频资源等资源信息，从所述第一传输粒度的第一标识中确定出所述第一传输粒度的第二标识。所述第一传输粒度的第二标识可包括以下中的任一项或多项：PDU会话、DRB、QoS流。所述空口资源信息可以是指空口资源的使用信息，可包括空口的时频资源等信息。
步骤S603、所述第二基站向所述第一基站发送第二消息，所述第二消息携带所述第一传输粒度的第二标识。相应地，所述第二基站接收所述第二消息。
具体的，所述第二基站可将确认建立的需要进行数据传输的所述第一传输粒度的第二标识通过第二消息通知给第一基站。
所述第一消息可以是指切换请求响应消息(Handover Request ACK)、或者其他流程消息等，本发明实施例不做限定。
通过上述方案，能够解决现有技术中第一基站和第二基站在进行数据传输时，一端不知道如何标识待传输的数据，另一端不知道当前接收的是什么数据等问题，提升了数据传输的高效性。
上述主要从第一基站和第二基站交互的角度对本发明实施例提供的方案进行了介绍，可选地还参与有终端的交互。可以理解的是，第一基站或第二基站为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本发明中所公开的实施例描述的各示例的单元及算法步骤，本发明实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本发明实施例的技术方案的范围。
本发明实施例可以根据上述方法示例对第一基站和第二基站进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图7A示出了上述实施例中所涉及的第一基站的一种可能的结构示意图。第一基站500包括：处理单元502和通信单元503。处理单元502用于对第一基站500的动作进行控制管理，例如，在本发明的一种实施方式中处理单元502用于支持第一基站500执行图2中的步骤S202，图3中步骤S306，图4中的步骤S406和步骤S408，图5中步骤S503，和/或用于执行本文所描述的技术的其它步骤。通信单元503用于支持第一基站500与其它网络设备的通信，例如，通信单元503用于支持第一基站500执行图2中的步骤S203，图3中步骤S303和步骤S307，图4中步骤S403和步骤S407，图5中步骤S504，和/或用于执行本文所描述的技术的其它步骤。在本发明的另一种实施方式中，处理单元502用于支持第一基站500执行图6中的步骤S601，和/或用于执行本文所描述的技术的其它步骤。通信单元503用于支持第一基站500与其它网络设备的通信，例如，通信单元503用于支持第一基站500执行图6中步骤S601，和/或用于执行本文所描述的技术的其它步骤。
可选地，第一基站500还可以包括存储单元501，用于存储第一基站500的程序代码和数据。
其中，处理单元502可以是处理器或控制器，例如可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(ASIC)，可编程逻辑器件(PLD)或 其组合。上述PLD可以是复杂可编程逻辑器件(CPLD)，现场可编程逻辑门阵列(FPGA)，通用阵列逻辑(GAL)或其任意组合。
通信单元503包括通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口，例如第一基站与第二基站之间的接口。
存储单元501可以是存储器。存储器可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器410还可以包括上述种类的存储器的组合。
当处理单元502为处理器，通信单元503为通信接口，存储单元501为存储器时，本发明实施例所涉及的第一基站可以为图7B所示的第一基站。
参阅图7B所示，该第一基站500包括：处理器512、通信接口513、存储器511。可选地，第一基站500还可以包括总线514。其中，通信接口513、处理器512以及存储器511可以通过总线514相互连接；所述总线514可以分为地址总线、数据总线、控制总线等。为便于表示，图7B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一些实施例中，所述第一基站可以是以下中的任一项：服务基站、驻留基站、源基站、目标基站。
上述图7A或图7B所示的第一基站的具体实现还可以对应参照上述方法实施例的相应描述，此处不再赘述。
请参见图8A，图8A示出了上述实施例中所涉及的第二基站的一种可能的结构示意图。第二基站600包括：处理单元602和通信单元603。处理单元602用于对第二基站600的动作进行控制管理，例如，在本发明的一种实施方式中处理单元602用于支持第二基站600执行图3中的步骤S304，图4中步骤S404，图5中步骤S505，图6中步骤S503，和/或用于执行本文所描述的技术的其它步骤。通信单元503用于支持第二基站600与其它网络设备的通信，例如，通信单元603用于支持第二基站600执行图2中的步骤S201，图3中步骤S301和步骤S305，图4中步骤S401和步骤S405，图5中步骤S502和步骤S506，图6中步骤S603，和/或用于执行本文所描述的技术的其它步骤。
在本发明的又一种实施方式中处理单元602用于支持第二基站600执行图6中步骤S602，和/或用于执行本文所描述的技术的其它步骤。通信单元503用于支持第二基站600与其它网络设备的通信，例如，通信单元603用于支持第二基站600执行图6中步骤S603，和/或用于执行本文所描述的技术的其它步骤。
可选地，第二基站600还可以包括存储单元601，用于存储第二基站600的程序代码和数据。
其中，处理单元602可以是处理器或控制器，例如可以是CPU，NP或者CPU和NP的组合。还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，PLD或其组合。上述PLD可以是CPLD，FPGA，GAL或其任意组合。
通信单元603包括通信接口、收发器、收发电路等，其中，通信接口是统称，可以包括一个或多个接口，例如第一基站与第二基站之间的接口。
存储单元601可以是存储器。存储器可以包括易失性存储器，例如RAM；存储器也可以包括非易失性存储器，例如flash，HDD或SSD；存储器还可以包括上述种类的存储器的组合。
当处理单元602为处理器，通信单元603为通信接口，存储单元601为存储器时，本发明实施例所涉及的第二基站可以为图8B所示的第二基站。
参阅图8B所示，该第二基站600包括：处理器612、通信接口613、存储器611。可选地，第二基站600还可以包括总线614。其中，通信接口613、处理器612以及存储器611可以通过总线614相互连接；所述总线614可以分为地址总线、数据总线、控制总线等。为便于表示，图8B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在一些实施例中，所述第二基站可以是以下中的任一项：服务基站、驻留基站、源基站、目标基站。
上述图8A或图8B所示的第二基站的具体实现还可以对应上述方法实施例的相应描述，此处不再赘述。
请参见图9，图9示出了本发明提供的一种数据传输系统的结构示意图。所述系统700包括第一基站500和第二基站600。其中，第一基站500可以是图7A或图7B所示的第一基站500，这里不再赘述；第二基站600可以是图8A或图8B所示的第二基站600，这里不再赘述。
上述图9所示的数据传输系统的具体实现还可以对应上述方法实施例的相应描述，此处不再赘述。
通过上述方案，能够解决现有技术中第一基站和第二基站在进行数据传输时，一端不知道如何标识待传输的数据，另一端不知道当前接收的是什么数据等问题，提升了数据传输的高效性。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM、闪存、只读存储器(英文：Read Only Memory，ROM)、可擦除可编程只读存储器(英文：Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(英文：Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于第一基站或第二基站中。当然，处理器和存储介质也可以作为分立组件存在于第一基站或第二基站中。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (25)

  1. 一种数据传输方法，其特征在于，所述方法包括：
    第一基站接收第二基站发送的第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；
    所述第一基站向所述第二基站发送第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
  2. 根据权利要求1所述的方法，其特征在于，所述第一消息携带地址个数，所述第二消息中的至少一个地址的个数与所述第一消息中的地址个数相同。
  3. 根据权利要求1所述的方法，其特征在于，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；
    所述第一基站向所述第二基站发送第二消息之前，还包括：
    所述第一基站根据所述至少一个第一传输粒度的标识以及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定至少一个所述第二传输粒度的标识；
    所述第一基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识。
  4. 根据权利要求1所述的方法，其特征在于，所述第一消息携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第二传输粒度的标识所对应的数据；
    所述第一基站向所述第二基站发送第二消息之前，还包括：
    所述第一基站为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述至少一个第二传输粒度的标识的个数与所述至少一个地址的个数数量相同。
  5. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一基站接收所述第二基站发送的第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第一传输粒度或所述第二传输粒度包括以下中的任一项：服务质量QoS流、协议数据单元PDU会话、数据无线承载DRB。
  7. 一种数据传输方法，其特征在于，所述方法包括：
    第二基站向第一基站发送第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；
    接收所述第一基站发送的第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
  8. 根据权利要求7所述的方法，其特征在于，所述第一消息携带地址个数，所述第二消息中的至少一个地址的个数与所述第一消息中的地址个数相同。
  9. 根据权利要求7所述的方法，其特征在于，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；
    所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述第二消息中的至少一个地址的个数与所述第一消息中至少一个第一传输粒度的标识的个数相同；其中，所述第二传输粒度的标识是根据所述至少一个第一传输粒度的标识、及所述第一传输粒度的标识与第二传输粒度的标识的映射关系确定的。
  10. 根据权利要求7所述的方法，其特征在于，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；
    所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述第二消息中的至少一个地址的个数与所述第一消息中至少一个第二传输粒度的标识的个数相同。
  11. 根据权利要求7-10中任一项所述的方法，其特征在于，所述第二基站存在至少一个第二传输粒度的标识所对应的数据需要向所述第一基站传输，所述方法还包括：
    所述第二基站为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识，不同的地址对应不同的第二传输粒度的标识；
    所述第二基站向所述第一基站发送第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
  12. 一种数据传输方法，其特征在于，所述方法包括：
    第一基站向第二基站发送第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
    接收所述第二基站发送的第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
  13. 根据权利要求12所述的方法，其特征在于，所述第一基站向第二基站发送第一消息之前，还包括：
    所述第一基站为至少一个第一传输粒度的第一标识中的每个第一标识分配对应的地址，不同的地址对应不同的第一传输粒度的第一标识。
  14. 一种数据传输方法，其特征在于，所述方法包括：
    第二基站接收第一基站发送的第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
    所述第二基站向所述第一基站发送第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
  15. 根据权利要求14所述的方法，其特征在于，所述第二基站接收第一基站发送的第一消息之后，所述第二基站向所述第一基站发送第二消息之前，还包括：
    所述第二基站根据空口资源信息，从所述第一传输粒度的第一标识中选择所述第二标识。
  16. 一种第一基站，其特征在于，包括通信单元，其中：
    所述通信单元，用于接收第二基站发送的第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；
    所述通信单元，还用于向所述第二基站发送第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
  17. 根据权利要求16所述的第一基站，其特征在于，所述第一基站还包括处理单元，所述第一消息携带至少一个第一传输粒度的标识、及第一传输粒度的标识与第二传输粒度的标识的映射关系，所述第一传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第一传输粒度的标识所对应的数据；所述通信单元用于向所述第二基站发送第二消息之前，
    所述处理单元，用于根据所述至少一个第一传输粒度的标识以及所述第一传输粒度的标识与所述第二传输粒度的标识的映射关系，确定至少一个所述第二传输粒度的标识；
    所述处理单元，还用于为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识。
  18. 根据权利要求16所述的第一基站，其特征在于，所述第一基站还包括处理单元，所述第一消息携带至少一个第二传输粒度的标识，所述第二传输粒度的标识用于标识所述第二基站需要向所述第一基站发送所述第二传输粒度的标识所对应的数据；所述通信单元用于向所述第二基站发送第二消息之前，
    所述处理单元，用于为所述至少一个第二传输粒度的标识中的每个标识分配对应的地址；所述第二消息还携带所述至少一个地址各自对应的第二传输粒度的标识，所述至少一个第二传输粒度的标识的个数与所述至少一个地址的个数数量相同。
  19. 根据权利要求16所述的第一基站，其特征在于，
    所述通信单元，还用于接收所述第二基站发送的第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
  20. 一种第二基站，其特征在于，包括通信单元，其中：
    所述通信单元，用于向第一基站发送第一消息，所述第一消息用于指示所述第二基站需要进行数据的传输；
    所述通信单元，还用于接收所述第一基站发送的第二消息，所述第二消息携带至少一个地址，所述地址与所述数据相关联。
  21. 根据权利要求20所述的第二基站，其特征在于，所述第二基站还包括处理单元，所述第二基站存在至少一个第二传输粒度的标识所对应的数据需要向所述第一基站传输，
    所述处理单元，用于为所述至少一个地址中的每个地址分配对应的第二传输粒度的标识，不同的地址对应不同的第二传输粒度的标识；
    所述通信单元，还用于向所述第一基站发送第三消息，所述第三消息携带所述至少一个地址各自对应的第二传输粒度的标识。
  22. 一种第一基站，其特征在于，包括通信单元，其中：
    所述通信单元，用于向第二基站发送第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
    所述通信单元，还用于接收所述第二基站发送的第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
  23. 根据权利要求22所述的第一基站，其特征在于，还包括处理单元，所述通信单元用于向第二基站发送第一消息之前，
    所述处理单元，用于为至少一个第一传输粒度的第一标识中的每个第一标识分配对应的地址，不同的地址对应不同的第一传输粒度的第一标识。
  24. 一种第二基站，其特征在于，包括通信单元，其中：
    所述通信单元，用于接收第一基站发送的第一消息，所述第一消息携带至少一个第一传输粒度的第一标识各自对应的地址，所述地址用于标识所述第一基站和所述第二基站之间传输的所述第一传输粒度的数据；
    所述通信单元，还用于向所述第一基站发送第二消息，所述第二消息携带第一传输粒度的第二标识，所述第二标识为所述至少一个第一标识中的一个或多个。
  25. 根据权利要求24所述的第二基站，其特征在于，还包括处理单元，所述通信单元用于向所述第一基站发送第二消息之前，
    所述处理单元，用于根据空口资源信息，从所述第一传输粒度的第一标识中选择所述第二标识。
PCT/CN2018/085663 2017-05-05 2018-05-04 一种数据传输方法、相关设备及系统 Ceased WO2018202148A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18794755.1A EP3614735B1 (en) 2017-05-05 2018-05-04 Data transmission methods and devices
US16/672,819 US11368882B2 (en) 2017-05-05 2019-11-04 Data transmission method, and related device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710323435.3 2017-05-05
CN201710323435.3A CN109246772B (zh) 2017-05-05 2017-05-05 一种数据传输方法、相关设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/672,819 Continuation US11368882B2 (en) 2017-05-05 2019-11-04 Data transmission method, and related device and system

Publications (1)

Publication Number Publication Date
WO2018202148A1 true WO2018202148A1 (zh) 2018-11-08

Family

ID=64015875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085663 Ceased WO2018202148A1 (zh) 2017-05-05 2018-05-04 一种数据传输方法、相关设备及系统

Country Status (4)

Country Link
US (1) US11368882B2 (zh)
EP (1) EP3614735B1 (zh)
CN (2) CN113055880A (zh)
WO (1) WO2018202148A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021161621A1 (ja) * 2020-02-13 2021-08-19 日本電気株式会社 Ｒａｎノード、無線端末、及びこれらのための方法

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12295056B2 (en) * 2018-12-12 2025-05-06 Comcast Cable Communications, Llc Network assisted connection
WO2020147120A1 (en) * 2019-01-18 2020-07-23 Qualcomm Incorporated Early measurement reporting
CN111757418B (zh) * 2019-03-27 2021-11-05 大唐移动通信设备有限公司 一种数据传输方法、装置及无线接入网节点
CN116113075A (zh) 2019-03-29 2023-05-12 华为技术有限公司 一种数据传输方法及装置
CN114189847A (zh) * 2020-09-14 2022-03-15 华为技术有限公司 通信的方法和装置
EP4128978B1 (en) * 2020-10-21 2026-01-28 Peninsula Technologies, LLC Downlink data of small data transmission procedure
CN116998219A (zh) 2020-11-09 2023-11-03 欧芬诺有限责任公司 多播和广播服务的不连续接收操作
CN114339850B (zh) * 2021-11-30 2023-08-25 浙江三维利普维网络有限公司 基站数据的传输方法和装置、存储介质及电子装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7130285B2 (en) * 2000-04-12 2006-10-31 Samsung Electronics Co., Ltd. Method for providing concurrent service handoff in a mobile communication system
CN101043714A (zh) * 2006-03-21 2007-09-26 华为技术有限公司 实现用户设备的移动性管理的方法及系统
CN105814942A (zh) * 2013-12-13 2016-07-27 夏普株式会社 针对多连接操作的系统和方法

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656992A (zh) * 2008-08-19 2010-02-24 华为技术有限公司 资源释放方法和系统、基站、服务网关和移动性管理网元
GB2472789A (en) * 2009-08-17 2011-02-23 Nec Corp In a lte-advanced network a target enb sends a source enb information to indicate to the ue which of multiple component carriers is to be used for initail acc
CN102497396B (zh) * 2011-11-30 2015-07-22 华为技术有限公司 通信方法、基站、基站控制器和移动交换中心
EP2645803B1 (en) * 2012-03-27 2019-07-31 BlackBerry Limited Enb storing rrc configuration information at another network component
US9451530B2 (en) * 2012-11-02 2016-09-20 Telefonaktiebolaget L M Ericsson (Publ) Methods for base-station-to-base-station connection management
KR20140102112A (ko) 2013-02-13 2014-08-21 주식회사 케이티 스몰셀 활성화 또는 비활성화 방법 및 장치
KR102101517B1 (ko) * 2013-09-27 2020-04-16 이노스카이 주식회사 이중연결 방식을 이용하는 무선통신 시스템에서 서빙셀의 활성화/비활성화 방법 및 장치
CN104918329B (zh) 2014-03-13 2019-06-25 中国移动通信集团公司 一种通信处理方法、装置及基站
CN105992293B (zh) * 2015-02-09 2020-01-07 电信科学技术研究院 一种进行网络间切换的方法和设备
WO2018084678A2 (en) * 2016-11-04 2018-05-11 Samsung Electronics Co., Ltd. Method and apparatus for provisioning quality of service in next radio
US10582560B2 (en) * 2017-03-17 2020-03-03 Ofinno, Llc Radio access network notification area update failure
US10264622B2 (en) * 2017-03-17 2019-04-16 Ofinno Technologies, Llc Inactive state data forwarding
US10349380B2 (en) * 2017-03-17 2019-07-09 Ofinno, Llc Radio access network area information
US10849022B2 (en) * 2017-03-17 2020-11-24 Ofinno, Llc Cell selection of inactive state wireless device
US10368334B2 (en) * 2017-03-17 2019-07-30 Ofinno Technologies, Llc Radio access network paging area configuration
CN108632810B (zh) * 2017-03-24 2021-08-20 华为技术有限公司 控制终端设备状态的方法、终端设备和网络设备
CN107257553B (zh) * 2017-05-04 2020-10-09 上海华为技术有限公司 用户面链路建立方法、基站及移动性管理设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7130285B2 (en) * 2000-04-12 2006-10-31 Samsung Electronics Co., Ltd. Method for providing concurrent service handoff in a mobile communication system
CN101043714A (zh) * 2006-03-21 2007-09-26 华为技术有限公司 实现用户设备的移动性管理的方法及系统
CN105814942A (zh) * 2013-12-13 2016-07-27 夏普株式会社 针对多连接操作的系统和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3614735A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021161621A1 (ja) * 2020-02-13 2021-08-19 日本電気株式会社 Ｒａｎノード、無線端末、及びこれらのための方法
US12245315B2 (en) 2020-02-13 2025-03-04 Nec Corporation Ran node, radio terminal, and methods therefor

Also Published As

Publication number Publication date
CN109246772B (zh) 2021-02-23
EP3614735B1 (en) 2021-12-08
CN109246772A (zh) 2019-01-18
EP3614735A1 (en) 2020-02-26
CN113055880A (zh) 2021-06-29
US11368882B2 (en) 2022-06-21
US20200068452A1 (en) 2020-02-27
EP3614735A4 (en) 2020-05-06

Similar Documents

Publication Publication Date Title
WO2018202148A1 (zh) 一种数据传输方法、相关设备及系统
CN109274474B (zh) 一种基于反转服务流特性的通信方法及装置
EP3576453B1 (en) Method, network element, and system for implementing data processing, and storage medium
CN107534987B (zh) 一种数据调度方法、基站及系统
CN110831248A (zh) 一种通知方法、装置及基站
JP7837447B2 (ja) 通信制御方法、ユーザ装置、チップセット、プログラム及び移動通信システム
AU2015401354B2 (en) Evolved multimedia broadcast/multicast service embms system and management method
WO2021134725A1 (zh) 通信方法及装置
WO2017118199A1 (zh) 一种数据调度方法、基站及系统
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
WO2017020253A1 (zh) 用于辅基站切换的方法、网络设备和用户设备
CN104813725A (zh) 数据传输装置和方法
CN111405625B (zh) 一种切换方法、基站、通信系统及存储介质
JP2017508364A (ja) セカンダリ基地局及びマスター基地局によって実行される通信方法、並びに対応する基地局
KR102346388B1 (ko) 데이터 포워드 터널 확정 방법, 접속과 이동성 관리 기기 및 기지국
WO2020001257A1 (zh) 一种数据传输方法及装置
CN108156633A (zh) 数据流重映射方法及装置和用户设备、ran设备
CN107005893A (zh) 服务质量的控制方法、设备及系统
WO2021214378A1 (en) Secondary f1-c interface for integrated access and backhaul (iab) node
JP2023549941A (ja) 伝送方法、通知方法、伝送ユニット及びネットワーク側機器
CN111787628B (zh) 一种传输方法、终端及网络设备
WO2018202204A1 (zh) 一种基于反转服务流特性的通信方法及装置
CN120018214A (zh) 服务质量调整方法、装置、设备和存储介质
BR112018013931B1 (pt) Método de agendamento de dados, estação de base e sistema

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

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

Country of ref document: EP

Effective date: 20191120