WO2022152257A1 - 多播业务的信息交互方法及基站 - Google Patents

多播业务的信息交互方法及基站 Download PDF

Info

Publication number
WO2022152257A1
WO2022152257A1 PCT/CN2022/072075 CN2022072075W WO2022152257A1 WO 2022152257 A1 WO2022152257 A1 WO 2022152257A1 CN 2022072075 W CN2022072075 W CN 2022072075W WO 2022152257 A1 WO2022152257 A1 WO 2022152257A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
data packet
multicast service
target base
source base
Prior art date
Application number
PCT/CN2022/072075
Other languages
English (en)
French (fr)
Inventor
张玅琦
刘亮
韩星宇
Original Assignee
中国移动通信有限公司研究院
中国移动通信集团有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国移动通信有限公司研究院, 中国移动通信集团有限公司 filed Critical 中国移动通信有限公司研究院
Publication of WO2022152257A1 publication Critical patent/WO2022152257A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • 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/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/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present application relates to the field of mobile communication technologies, and in particular, to an information exchange method and base station for multicast services.
  • MBS Multicast Broadcast Service
  • an important goal in the multicast service is to ensure the service continuity of the terminal in the process of moving between base stations.
  • a terminal is handed over from a base station or cell that has established a multicast service session to another base station or cell that has also established a multicast service session, how to ensure that data packets can be transmitted to the terminal without being lost during the handover process is urgently needed. solved problem.
  • the data interaction process in the traditional switching scenario is shown in Figure 1.
  • service continuity is mainly achieved by the source base station sending a SN STATUS TRANSFER message to the target base station.
  • the source base station after the source base station sends a handover command to the terminal, the source base station establishes a data forwarding channel with the target base station, and sends a SN STATUS TRANSFER message to the target base station to inform the target base station of the downlink PDCP of the data radio bearer (DRB).
  • DRB data radio bearer
  • the downlink Packet Data Convergence Protocol (PDCP) sequence number (Sequence Number, SN) transmission status indicates that the target base station will allocate the next PDCP SN to the unallocated new PDCP SDU, ensuring the Sequential transmission also avoids repeated transmission; for data packets that have been allocated PDCP SNs but are not acknowledged by the terminal under the source base station, the source base station can re-forward PDCP SDUs and SNs by establishing a downlink data forwarding channel.
  • PDCP Packet Data Convergence Protocol
  • At least one embodiment of the present application provides an information exchange method and a base station for a multicast service.
  • At least one embodiment provides a method for exchanging information for multicast services, applied to a target base station, including:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station.
  • the status information of the data packet of the multicast service at the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the state information of the data packet of the multicast service at the target base station includes: the state information of the data packet of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station includes: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the method further includes:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the method further includes:
  • the state information of the data packet of the multicast service at the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the status information of the data packet of the multicast service at the source base station includes:
  • the first SN is the latest SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the state information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packets of the multicast service that need to be forwarded by the source base station include: data packets of the first type, and/or data packets of the second type; wherein,
  • the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the first SN is the data packet of the multicast service at the source base station.
  • the latest PDCP SN that has been allocated on the side, the first SN is smaller than the third SN;
  • the second type of data packet is a data packet corresponding to the second SN.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein,
  • the third type of data packet is a data packet corresponding to a fourth SN
  • the fourth SN is a PDCP SN that is smaller than the third SN in the second SN.
  • the method after sending the state information of the data packet of the multicast service at the target base station to the source base station, the method further includes:
  • a stop transmission message sent by the source base station is received; the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the sending to the source base station the status information of the data packet of the multicast service at the target base station includes:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station through a handover request reply (which can be expressed as HANDOVER REQUEST ACKNWLEDGE in English).
  • the receiving state information of the data packet of the multicast service sent by the source base station in the source base station includes:
  • a handover request (which can be expressed as HANDOVER REQUEST in English) message or a serial number status transfer (which can be expressed as SN STATUS TRANSFER in English) message
  • the state information of the multicast service data packet sent by the source base station in the source base station is received .
  • At least one embodiment provides an information exchange method for a multicast service, applied to a source base station, including:
  • the status information of the data packet of the multicast service at the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the state information of the data packet of the multicast service at the target base station includes: the state information of the data packet of the multicast service currently buffered by the target base station.
  • the state information of the data packet of the multicast service currently buffered by the target base station includes: the SN of the first data packet of the multicast service currently buffered by the target base station.
  • the method further includes:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the method further includes:
  • the state information of the data packet of the multicast service at the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the status information of the data packet of the multicast service at the source base station includes:
  • the first SN is the latest SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the state information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packets of the multicast service that need to be forwarded by the source base station include: data packets of the first type, and/or data packets of the second type; wherein,
  • the first type of data packet is a data packet that is not buffered by the target base station; the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the The first SN is the latest PDCP SN that has been allocated by the data packet of the multicast service at the source base station side, and the first SN is smaller than the third SN;
  • the second type of data packet is a data packet corresponding to the second SN.
  • the method further includes:
  • the first type of data packet and/or the second type of data packet is forwarded to the target base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein,
  • the third type of data packet is a data packet corresponding to a fourth SN
  • the fourth SN is a PDCP SN that is smaller than the third SN in the second SN.
  • the method further includes:
  • the third type of data packet is forwarded to the target base station.
  • the method after receiving the status information of the data packet of the multicast service in the target base station sent by the target base station, the method further includes:
  • the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the receiving state information of the data packet of the multicast service sent by the target base station in the target base station includes:
  • the state information of the data packet of the multicast service sent by the target base station in the target base station is received.
  • the state information on the source base station of the data packet of the multicast service sent to the target base station includes:
  • the state information of the data packet of the multicast service in the source base station is sent to the target base station through a handover request message or a sequence number state transfer message.
  • At least one embodiment provides a target base station including a transceiver and a processor, wherein,
  • the transceiver is configured to send, to the source base station, the status information of the data packet of the multicast service at the target base station.
  • At least one embodiment provides a target base station, including:
  • the sending module is configured to send the state information of the data packet of the multicast service in the target base station to the source base station.
  • At least one embodiment provides a target base station, comprising: a processor, a memory, and a program stored on the memory and executable on the processor, the program being executed by the When executed by the processor, the steps of any of the above-mentioned methods on the side of the target base station are implemented.
  • At least one embodiment provides a source base station including a transceiver and a processor, wherein,
  • the transceiver is configured to receive state information of the multicast service data packet sent by the target base station in the target base station.
  • At least one embodiment provides a source base station, including:
  • the receiving module is configured to receive the state information of the data packet of the multicast service sent by the target base station in the target base station.
  • At least one embodiment provides a source base station, comprising: a processor, a memory, and a program stored on the memory and executable on the processor, the program being The processor implements the steps of any method on the source base station side when executed by the processor.
  • At least one embodiment provides a computer-readable storage medium, where a program is stored on the computer-readable storage medium, and when the program is executed by a processor, the above-mentioned target base station side or source Steps of any method on the base station side.
  • the information exchange method and base station for a multicast service provided by the embodiments of the present application can improve multicast service data through information exchange between base stations when a terminal in a multicast service scenario switches between two base stations. Packet transmission reliability to ensure continuity of multicast services. In addition, the embodiments of the present application can also save unnecessary repeated data transmission and save transmission resources.
  • FIG. 1 is a schematic diagram of a handover process of the related art
  • FIG. 2 is a schematic diagram of a MBS handover process of the related art
  • FIG. 3 is a flowchart when the method for exchanging information for multicast services according to an embodiment of the present application is applied to a target base station;
  • FIG. 4 is a flowchart when the method for exchanging information of a multicast service according to an embodiment of the present application is applied to a source base station;
  • FIG. 5 is a schematic diagram of an application scenario of an information exchange method for a multicast service according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of another application scenario of the information exchange method of the multicast service according to the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a target base station provided by an embodiment of the present application.
  • FIG. 8 is another schematic structural diagram of a target base station provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a source base station according to an embodiment of the present application.
  • FIG. 10 is another schematic structural diagram of a source base station according to an embodiment of the present application.
  • LTE Long Time Evolution
  • LTE-A Long Time Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • a CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA).
  • UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants.
  • a TDMA system may implement a radio technology such as the Global System for Mobile Communication (GSM).
  • GSM Global System for Mobile Communication
  • OFDMA systems can implement radios such as UltraMobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.21 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. technology.
  • UMB UltraMobile Broadband
  • E-UTRA Evolution-UTRA
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • Flash-OFDM Flash-OFDM
  • UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).
  • LTE and higher LTE eg LTE-A
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for both the systems and radio technologies mentioned above, as well as for other systems and radio technologies.
  • 3GPP2 3rd Generation Partnership Project 2
  • NR terminology is used in much of the following description, although these techniques are also applicable to applications other than NR system applications.
  • the core network User Plane Function (UPF) node needs to provide the two base stations Send the same packet.
  • the source base station sends MBS data packets to all connected terminals under the coverage of the base station that request the MBS, so the handover of a certain terminal does not affect the transmission of MBS data packets of the source base station.
  • the establishment of the connection between the target base station and the new terminal after the handover does not affect the target base station's sending of MBS data packets to all connected terminals within the coverage that have requested the MBS service.
  • the source base station After the source base station sends a handover command to the terminal, the source base station establishes a data forwarding channel, and sends a SN STATUS TRANSFER message to the target base station, informing the target base station of the PDCP SN of the latest MBS data packet, and the PDCP count (COUNT) value can also be used.
  • the terminal After the terminal establishes a connection with the target base station, it sends a PDCP status report (STATUS REPORT, SR) to the target base station to inform the target base station of the SN of the latest MBS data packet received by the terminal at the source base station.
  • STATUS REPORT, SR PDCP status report
  • the terminals under the coverage of different base stations at the same time may not receive MBS packets from the core network. same. Because the base station transmits data packets in different air interface environments, it is difficult to ensure the continuity of the MBS service and the efficiency is low when the terminal is handed over.
  • the source base station needs to forward the data packet to the target base station before receiving the MBS data transmission end identifier. At this time, the target base station may have obtained the same data packet from the UPF, and the data packets on the interface and the air interface are repeated. Transmission results in a waste of transmission resources.
  • an embodiment of the present application provides an information exchange method for a multicast service.
  • a terminal receives a data packet of a multicast service (such as MBS) under a source base station .
  • a multicast service such as MBS
  • both the source base station and the target base station have established the multicast service session, and the core network node (eg UPF or MB-UPF) sends the multicast service data to the source base station and the target base station.
  • the core network node eg UPF or MB-UPF
  • Step 31 Send to the source base station the status information of the data packet of the multicast service at the target base station.
  • the above step 31 may be performed in the handover preparation stage of the terminal, after the terminal successfully accesses the target base station, or after receiving the SN status information sent by the source base station, that is, the target base station may be in the handover preparation stage of the terminal, after the terminal successfully accesses the target base station. Or after receiving the SN state transfer information sent by the source base station, send the state information of the data packet of the multicast service at the target base station to the source base station.
  • the source base station can obtain the actual sending state of the data packets of the multicast service on the target base station side, including but not limited to the latest current state of the target base station.
  • the status information of the data packet of the multicast service in the target base station may include: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the state information of the data packet of the multicast service in the target base station may include: state information of the data packet of the multicast service currently buffered by the target base station.
  • the PDCP SN of the data packets of the multicast service currently buffered by the target base station may specifically include the PDCP SNs of all data packets currently buffered, or the PDCP SNs of the currently buffered start and end data packets, or the currently buffered PDCP SNs of the data packets.
  • the state information of the data packet of the multicast service currently buffered by the target base station may include: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the PDCP SN of the first data packet is usually the SN of the PDCP PDU.
  • the buffer usually also includes PDCP SNs of other data packets of the multicast service.
  • the PDCP SNs of other data packets are usually larger than the PDCP SN of the first data packet, and usually the PDCP SNs of these data packets are consecutive.
  • the source base station can determine the data packets that need to be forwarded for the multicast service according to the state information of the data packets of the multicast service sent by the target base station in the target base station, and forward them to the target base station.
  • the base station can receive at least one of the following information sent by the source base station:
  • the unacknowledged data packet of the terminal before the PDCP SN forwarded by the source base station refers to the data packet that has been sent to the terminal on the source base station side, but the reception confirmation feedback of the terminal has not been received, and the The PDCP SN of the data packet is before the PDCP SN of the first data packet of the multicast service currently buffered by the target base station. That is to say, the data packet is a data packet that the terminal fails to successfully receive from the source base station, and the data packet has been sent on the target base station side and the cache is cleared, and the terminal cannot obtain the data packet from the target base station side.
  • the source base station forwards these data packets to the target base station, so as to send these data packets to the terminal through the target base station to ensure the reliability of data transmission.
  • the data packets forwarded by the source base station before the PDCP SN that have not yet been allocated a PDCP SN means that the source base station side is a data packet for which a PDCP SN has not been allocated in the data packets of the multicast service received from the core network node,
  • the base station assigns a PDCP SN to the data packets before sending them, that is, the data packets are received from the core network but have not been sent to the terminal. If the subsequently allocated PDCP SN of these data packets is before the PDCP SN of the first data packet of the multicast service currently buffered by the target base station, the data packet has been sent on the target base station side and the cache is cleared. , the terminal cannot obtain the data packets from the target base station side, therefore, these data packets can be forwarded to the target base station to send these data packets to the terminal through the target base station to ensure the reliability of data transmission.
  • the PDCP SN information sent by the source base station and the terminal has confirmed the corresponding data packets can inform the target base station which data packets have been successfully sent by the source base station. Save transmission resources.
  • the PDCP SN information corresponding to the data packets sent by the source base station and unacknowledged by the terminal can inform the target base station which data packets have been sent by the source base station, but have not received the data packets of the terminal's reception confirmation feedback. In this way, The target base station can continue to send these data packets to the source base station.
  • the target base station may receive the status information of the data packet of the multicast service at the source base station, and the information is sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station may include: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the status information of the data packet of the multicast service at the source base station may include: the first SN of the multicast service and/or the terminal-unacknowledged PDCP PDU carried by the GTP-U extension header of the multicast service.
  • the first SN is the latest PDCP SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the first PDCP SN may also be replaced by a PDCP COUNT value.
  • the state information of the data packet of the multicast service at the target base station may include: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station may specifically include: a first type of data packet, and/or a second type of data packet; wherein, the first type of data packet The data packet is a data packet whose SN is between the first SN and the third SN of the first data packet currently buffered by the target base station, wherein the first SN is smaller than the third SN; the second type of data packet is the data packet corresponding to the second SN.
  • the PDCP SN of the first type of data packet is larger than the first SN and smaller than the third SN of the first data packet currently buffered by the target base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station may specifically include: a third type of data packet; wherein, the third type of data packet is a data packet corresponding to the fourth SN , the fourth SN is a PDCP SN smaller than the third SN in the second SN.
  • the method may further include:
  • a stop transmission message sent by the source base station is received; the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • step 31 may include:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station through the handover request reply message.
  • the receiving the state information of the data packet of the multicast service sent by the source base station in the source base station may include:
  • the state information of the data packet of the multicast service sent by the source base station in the source base station is received through a handover request message or a sequence number state transfer message.
  • the target base station may also receive the source At least one of the following information sent by the base station, and according to at least one of the following information, determine the data packets that the target base station needs to send to the terminal and the data packets that do not need to be sent to the terminal:
  • the PDCP SN information corresponding to the data packet is sent by the source base station and confirmed by the terminal.
  • the target base station may no longer need to continue sending to the terminal.
  • the target base station For the data packets corresponding to the PDCP SN information corresponding to the data packets that are sent by the source base station and are not acknowledged by the terminal, the target base station needs to continue sending to the terminal.
  • the state information of the data packets of the multicast service in the target base station may also be used to inform or instruct the source base station to stop forwarding data.
  • the source base station determines that it does not need to send the data of the multicast service according to the status information of the data packets of the multicast service in the target base station, or the source base station has completed forwarding the data of the multicast service to the target base station.
  • the source base station sends a message (ie, the above stop transmission message) to instruct to end the data forwarding process from the source base station to the target base station, so that the data forwarding can be ended in time.
  • the data packet of the multicast service that needs to be forwarded by the source base station is indicated by the SN of the data packet, and the indication mode of the SN is any one of the following modes:
  • C) Indicate by the start and end range of the SN; for example, the start SN and the end SN may be indicated, the start SN and the number of specific SNs may also be indicated, and the end SN and the number of specific SNs may also be indicated.
  • the method for exchanging information for multicast services includes:
  • Step 41 Receive state information on the target base station of the data packet of the multicast service sent by the target base station.
  • the source base station can obtain the status information of the data packets of the multicast service at the target base station, and then the source base station can determine whether it needs to forward the data to the target base station according to the status information of the data packets of the multicast service at the target base station. Forward the data packets of the multicast service, and, when the data packets need to be forwarded, forward the corresponding data packets to the target base station, so as to improve the transmission reliability of the multicast service, and avoid or reduce unnecessary transmission. data packets, saving transmission resources.
  • the status information of the data packet of the multicast service in the target base station may include: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the state information of the data packet of the multicast service in the target base station may include: state information of the data packet of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station may include: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the source base station determines whether the data packet of the multicast service needs to be forwarded to the target base station according to the state information of the data packet of the multicast service currently buffered by the target base station, and, when the data packet needs to be forwarded, to the target base station.
  • the target base station forwards the corresponding data packet.
  • the source base station may send at least one of the following information to the target base station:
  • the source base station may send the state information of the data packet of the multicast service in the source base station to the target base station.
  • the state information of the data packet of the multicast service in the source base station may include: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the status information of the data packet of the multicast service at the source base station may include: the first SN of the multicast service and/or the terminal-unacknowledged PDCP PDU carried by the GTP-U extension header of the multicast service.
  • the state information of the data packet of the multicast service at the target base station may include: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station may include: a first type of data packet, and/or a second type of data packet; wherein, the first type of data The packet is a data packet that is not buffered by the target base station, and the SN is between the first SN and the third SN of the first data packet currently buffered by the target base station, wherein the first SN is smaller than the third SN; In other words, the PDCP SN of the first type of data packet is greater than the first SN and smaller than the third SN of the first data packet currently buffered by the target base station; the second type of data packet is the data corresponding to the second SN Bag.
  • the source base station may also forward and send the first type of data packet and/or the second type of data packet to the target base station according to the state information of the data packet of the multicast service in the target base station data pack.
  • the data packet of the multicast service that needs to be forwarded by the source base station may include: a third type of data packet; wherein, the third type of data packet is a data packet corresponding to the fourth SN, The fourth SN is a PDCP SN of the second SN that is smaller than the third SN.
  • the source base station may further forward the data packet of the third type to the target base station according to the state information of the data packet of the multicast service in the target base station.
  • the source base station can also send at least one of the following information to the target base station, so as to improve the data packet transmission efficiency of the target base station and reduce or avoid sending unnecessary data packets:
  • the method may further include:
  • the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • step 41 may include:
  • the state information of the data packet of the multicast service sent by the target base station in the target base station is received.
  • the sending to the target base station the status information of the data packet of the multicast service at the source base station may include:
  • the state information of the data packet of the multicast service in the source base station is sent to the target base station through a handover request message or a sequence number state transfer message.
  • the speed at which the source base station and the target base station transmit the MBS data packets will be described in different situations.
  • the NG-US SN of the data packet transmitted between the UPF and the base station is used as the PDCP SN of the data packet transmitted between the base stations.
  • the transmission speed of the MBS data packets of the source base station is faster than that of the target base station.
  • the target base station After the handover occurs to the target base station, it interacts with the target base station and learns that the target base station side has sent the data packets of SN1 to 5.
  • the following situations may occur:
  • the target base station can send to the source base station the status information of the data packets of the multicast service in the target base station (hereinafter referred to as status information), informing that the data packets after number 8 are sent by the target base station, and the source base station ends the data packets in advance. Forward, plays the role of the end marker.
  • the terminal needs to re-receive the data packet of No. 3 and continue to receive the data packets of No. 6 to 8 after the handover.
  • the target base station If the target base station has buffered the data packet No. 3, the target base station sends the status information to the source base station, informing its own buffer information, and informing the source base station that it does not need to send the data packet No. 3 again. If the base station does not buffer the data packet No. 3, at this time, the target base station sends the status information to the source base station, informing the source base station that only the data packet No. 3 needs to be sent repeatedly.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the terminal can continue to receive data packets numbered 6 to 8 after the handover.
  • the target base station sends the status information to the source base station, informing that the data packets after number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of end identification.
  • the source base station sends the data packet numbered 8 during the interaction with the terminal, the terminal has actually received it but did not feed it back to the source base station before handover.
  • the target base station sends the state information to the source base station, informing that the data packets after number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the source base station transmits MBS data packets at a slower rate than the target base station.
  • the source base station transmits packets from SN1 to 5 at the air interface
  • the target base station transmits packets from SN1 to 8 at the air interface.
  • the following situations may occur:
  • the terminal receives all the data packets of the source base station at the source base station side. After switching to the target base station, due to the fast arrival of data packets at the target base station, the terminal will supplement and receive data packets numbered 6 to 8 first.
  • the target base station has buffered data packets numbered 6 to 8.
  • the target base station can directly send the buffered data packets to the terminal through the buffer.
  • the target base station sends the state information to the source base station at the same time, notifying its own cache information, that is, notifying the source base station that it does not need to forward the data packets numbered 6 to 8.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the target base station does not buffer data packets numbered 6 to 8.
  • the target base station sends the status information to the source base station to notify its own cache status, thereby informing the source base station that the terminal has not received the data packets numbered 6 to 8, and requests the source base station to forward only the data packets numbered 6 to 8.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the source base station loses the data packet numbered 3 during the interaction with the terminal. After switching to the target base station, the terminal will first re-receive the lost data packet number 3 and the data packets number 6 to 8.
  • the target base station has buffered data packets of number 3 and later.
  • the target base station can directly send the buffered data packets to the terminal through the buffer.
  • the target base station sends the state information to the source base station to notify its own cache information, so that the source base station does not need to forward data packets with numbers 3 and later.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the target base station does not buffer the packet number 3 but has buffered the packets number 6 to 8.
  • the target base station can send data packets that have not been received before to the terminal through the buffer.
  • the target base station sends the state information to the source base station, informing its own cache information, and requests the source base station to forward only the data packet with the number 3 to reduce repeated forwarding of the data packet.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the target base station may send the state information to the source base station, requesting the source base station to forward the data packet of the forwarding number 3 lost by the target base station and the data packets of the number 6 to 8 that have not been received before.
  • the signaling informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the target base station can directly send the buffered data packets to the terminal through the buffer.
  • the target base station sends the state information to the source base station to notify its own cache information, so that the source base station does not need to forward data packets with numbers 5 and later.
  • the source base station ends the forwarding of the data packet in advance, which plays the role of an end identifier.
  • the terminal will first send a PDCP status report to the target base station to inform the target base station that it has actually received the data packet No. 5.
  • the source base station does not need to repeatedly send the data packet numbered 5.
  • the target base station sends the status information according to its own buffer status to inform the source base station whether to send data packets numbered 6 to 8.
  • the state information informs that the data packets after the number 8 are sent by the target base station, and the source base station ends the forwarding of the data packets in advance, which plays the role of an end identification.
  • the specific content of the status information includes various situations:
  • the status information includes the PDCP SN corresponding to the first buffered data packet of the target base station, the PDCP SN of the unbuffered data packet of the target base station, and the PDCP SN that did not successfully receive the data packet before the terminal handover.
  • the target base station if the target base station has already buffered the data packets that need to be forwarded, the data forwarding through the source base station is not required, and the interaction process between base stations is ended in advance to reduce user plane data transmission; if the target base station If the forwarding data packets are not buffered, the source base station only needs to send such data packets.
  • the status information includes PDCP SNs corresponding to all data packets that require the source base station to perform data forwarding.
  • the state information can clearly inform the source base station which data packets need to be sent repeatedly, which can be indicated by identifying the reception conditions of all data packets within a certain range, such as in the form of a bitmap, when a certain PDCP SN corresponds to the flag bit. When set (for example, the value is 1), it indicates that the data packet needs to be sent repeatedly.
  • This message format allows the source base station to forward only the data packets not buffered by the target base station and the data packets that were not successfully received by the terminal before handover.
  • the status information includes the PDCP SN of the data packet transmitted by the target base station at the time of the terminal handover, the PDCP SN of the target base station not buffered the data packet, and the PDCP SN of the data packet that was not successfully received before the terminal handover.
  • the status information includes the number of the data packet transmitted by the target base station at the time of the terminal handover. No further data forwarding is required. The source base station only needs to forward the data packets that have not been successfully received before the terminal handover and the forwarded data packets that are not buffered.
  • the source base station transmits data packets faster than the target base station, since the data packets arrive at the target base station slowly, the source base station only needs to forward the data packets that were not successfully received before the terminal handover.
  • the embodiments of the present application can ensure reliable transmission of data packets and continuity of multicast services through an interaction process between base stations when a terminal switches between two base stations in a multicast service scenario.
  • the embodiment of the present application provides a target base station shown in FIG. 7 , including:
  • the sending module 71 is configured to send the state information of the data packet of the multicast service in the target base station to the source base station.
  • the embodiments of the present application can notify the source base station of the data packet status information of the target base station, so that the source base station can perform data forwarding more effectively, improve data transmission efficiency and reliability, and save transmission resources.
  • the state information of the data packet of the multicast service at the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the status information of the data packets of the multicast service in the target base station includes: status information of the data packets of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station includes: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the target base station further includes:
  • a first receiving module configured to receive at least one of the following information sent by the source base station:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the target base station further includes:
  • the second receiving module is configured to receive the status information on the source base station of the data packet of the multicast service sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the first SN of the multicast service and/or the extension header of the GTP-U corresponds to a PDCP PDU that is not acknowledged by the terminal. the second SN of the PDCP SDU;
  • the first SN is the latest PDCP SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the status information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packets of the multicast service that need to be forwarded by the source base station include: first-type data packets, and/or second-type data packets; wherein,
  • the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the first SN is the data packet of the multicast service at the source base station.
  • the latest PDCP SN that has been allocated on the side, the first SN is smaller than the third SN;
  • the second type of data packet is a data packet corresponding to the second SN.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein,
  • the third type of data packet is a data packet corresponding to a fourth SN
  • the fourth SN is a PDCP SN that is smaller than the third SN in the second SN.
  • the target base station further includes:
  • the first receiving module is configured to receive at least one of the following information sent by the source base station, and determine the data packets that the target base station needs to send to the terminal and the data packets that do not need to be sent to the terminal:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the second receiving module is configured to receive a stop transmission message sent by the source base station; the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the sending module 71 is configured to send the state information of the data packets of the multicast service in the target base station to the source base station through a handover request reply message.
  • the second receiving module is configured to receive the state information of the multicast service data packet in the source base station sent by the source base station through a handover request message or a sequence number state transfer message.
  • the apparatus in this embodiment is a device corresponding to the method shown in FIG. 3 above, and the implementation manners in each of the above embodiments are applicable to the embodiments of the device, and the same technical effect can also be achieved.
  • the above-mentioned device provided in the embodiment of the present application can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.
  • an embodiment of the present application provides a schematic structural diagram of a target base station, including: a processor 801, a transceiver 802, a memory 803, and a bus interface, wherein:
  • the target base station further includes: a program stored on the memory 803 and executable on the processor 801, and the program implements the following steps when executed by the processor 801:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station.
  • the state information of the data packet of the multicast service at the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the status information of the data packets of the multicast service in the target base station includes: status information of the data packets of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station includes: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the processor further implements the following steps when executing the program: receiving at least one of the following information sent by the source base station:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service in the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the first SN of the multicast service and/or the extension header of the GTP-U corresponds to a PDCP PDU that is not acknowledged by the terminal. the second SN of the PDCP SDU;
  • the first SN is the latest PDCP SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the status information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packets of the multicast service that need to be forwarded by the source base station include: first-type data packets, and/or second-type data packets; wherein,
  • the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the first SN is the data packet of the multicast service at the source base station.
  • the latest PDCP SN that has been allocated on the side, the first SN is smaller than the third SN;
  • the second type of data packet is a data packet corresponding to the second SN.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein,
  • the third type of data packet is a data packet corresponding to a fourth SN
  • the fourth SN is a PDCP SN that is smaller than the third SN in the second SN.
  • the processor further implements the following steps when executing the program: receiving at least one of the following information sent by the source base station, and determining a data packet that the target base station needs to send to the terminal and packets that do not need to be sent to said terminal:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the processor further implements the following steps when executing the program:
  • a stop transmission message sent by the source base station is received; the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station through the handover request reply message.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service sent by the source base station in the source base station is received through a handover request message or a sequence number state transfer message.
  • the bus architecture may include any number of interconnected buses and bridges, in particular one or more processors represented by processor 801 and various circuits of memory represented by memory 803 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 802 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the processor 801 is responsible for managing the bus architecture and general processing, and the memory 803 may store data used by the processor 801 in performing operations.
  • the terminal in this embodiment is a device corresponding to the method shown in FIG. 3 above, and the implementation manners in the above embodiments are all applicable to the embodiments of the terminal, and the same technical effect can also be achieved.
  • the transceiver 802 and the memory 803, as well as the transceiver 802 and the processor 801 can be communicated and connected through a bus interface, the function of the processor 801 can also be realized by the transceiver 802, and the function of the transceiver 802 can also be realized by the processor 801 implementation.
  • a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the following steps are implemented:
  • the state information of the data packet of the multicast service in the target base station is sent to the source base station.
  • the program When the program is executed by the processor, it can realize all the implementation manners in the above-mentioned information exchange method applied to the multicast service on the target base station side, and can achieve the same technical effect. To avoid repetition, it is not repeated here.
  • the embodiment of the present application provides a source base station shown in FIG. 9, including:
  • the receiving module 91 is configured to receive the status information of the data packet of the multicast service sent by the target base station in the target base station.
  • the embodiments of the present application can enable the source base station to obtain the data packet status information of the target base station, thereby helping the source base station to perform data forwarding more effectively, improving data transmission efficiency and reliability, and saving transmission resources.
  • the state information of the data packet of the multicast service in the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the status information of the data packets of the multicast service in the target base station includes: status information of the data packets of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station includes: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the source base station further includes:
  • the first sending module is configured to send at least one of the following information to the target base station:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the source base station further includes:
  • the second sending module is configured to send, to the target base station, the state information of the data packet of the multicast service at the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the first SN of the multicast service and/or the extension header of the GTP-U corresponds to a PDCP PDU that is not acknowledged by the terminal.
  • the status information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a first type of data packet, and/or a second type of data packet; wherein, the first type of data packet is a data packet not buffered by the target base station; the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the first SN is the The latest PDCP SN that the data packet of the multicast service has been allocated on the source base station side, the first SN is smaller than the third SN; the second type of data packet is the data packet corresponding to the second SN.
  • the source base station further includes:
  • the third sending module is configured to forward and send the first type data packet and/or the second type data packet to the target base station according to the state information of the data packet of the multicast service in the target base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein, the third type of data packet is a data packet corresponding to the fourth SN, so The fourth SN is a PDCP SN of the second SN that is smaller than the third SN.
  • the source base station further includes:
  • the fourth sending module is configured to forward and send the third type of data packet to the target base station according to the state information of the data packet of the multicast service in the target base station.
  • the source base station further includes:
  • a fifth sending module configured to send at least one of the following information to the target base station:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the second sending module is configured to send a stop transmission message to the target base station; the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the receiving module 91 is configured to receive the status information of the data packet of the multicast service sent by the target base station in the target base station through a handover request reply message.
  • the second sending module is configured to send, to the target base station, the state information of the data packet of the multicast service at the source base station through a handover request message or a sequence number state transfer message.
  • the device in this embodiment is a device corresponding to the method shown in FIG. 4 , and the implementation manners in the above embodiments are all applicable to the embodiments of the device, and the same technical effect can also be achieved. It should be noted here that the above-mentioned device provided by the embodiment of the present application can realize all the method steps realized by the above-mentioned method embodiment, and can achieve the same technical effect, and the same as the method embodiment in this embodiment is not repeated here. The parts and beneficial effects will be described in detail.
  • an embodiment of the present application provides a schematic structural diagram of a network-side device, including: a processor 1001, a transceiver 1002, a memory 1003, and a bus interface, where:
  • the network-side device further includes: a program stored on the memory 1003 and executable on the processor 1001, and the program implements the following steps when executed by the processor 1001:
  • the state information of the data packet of the multicast service in the target base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the target base station.
  • the status information of the data packets of the multicast service in the target base station includes: status information of the data packets of the multicast service currently buffered by the target base station.
  • the status information of the data packet of the multicast service currently buffered by the target base station includes: the PDCP SN of the first data packet of the multicast service currently buffered by the target base station.
  • the processor further implements the following steps when executing the program:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service in the source base station includes: the PDCP SN of the data packet of the multicast service that is currently newly sent by the source base station.
  • the state information of the data packet of the multicast service in the source base station includes: the first SN of the multicast service and/or the extension header of the GTP-U corresponds to a PDCP PDU that is not acknowledged by the terminal. the second SN of the PDCP SDU;
  • the first SN is the latest PDCP SN that has been allocated on the source base station side for the data packet of the multicast service.
  • the status information of the data packet of the multicast service at the target base station includes: the data packet of the multicast service that needs to be forwarded by the source base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a first type of data packet, and/or a second type of data packet; wherein, the first type of data packet is a data packet not buffered by the target base station; the PDCP SN of the first type of data packet is greater than the first SN, and is smaller than the third SN of the first data packet currently buffered by the target base station, wherein the first SN is the The latest PDCP SN that the data packet of the multicast service has been allocated on the source base station side, the first SN is smaller than the third SN; the second type of data packet is the data packet corresponding to the second SN.
  • the processor further implements the following steps when executing the program:
  • the first type of data packet and/or the second type of data packet is forwarded to the target base station.
  • the data packet of the multicast service that needs to be forwarded by the source base station includes: a third type of data packet; wherein, the third type of data packet is a data packet corresponding to the fourth SN, so The fourth SN is a PDCP SN of the second SN that is smaller than the third SN.
  • the processor further implements the following steps when executing the program:
  • the third type of data packet is forwarded to the target base station.
  • the processor further implements the following steps when executing the program:
  • PDCP SN information corresponding to the data packets sent by the source base station and not acknowledged by the terminal.
  • the processor further implements the following steps when executing the program:
  • the stop transmission message is used to instruct to end the data forwarding process from the source base station to the target base station.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service sent by the target base station in the target base station is received.
  • the processor further implements the following steps when executing the program:
  • the state information of the data packet of the multicast service in the source base station is sent to the target base station through a handover request message or a sequence number state transfer message.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1002 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1003 may store data used by the processor 1001 in performing operations.
  • the terminal in this embodiment is a device corresponding to the method shown in FIG. 4 , and the implementation manners in the above embodiments are all applicable to the embodiments of the terminal, and the same technical effect can also be achieved.
  • the transceiver 1002 and the memory 1003, as well as the transceiver 1002 and the processor 1001 can be communicated and connected through a bus interface, the function of the processor 1001 can also be realized by the transceiver 1002, and the function of the transceiver 1002 can also be realized by the processor 1001 realized.
  • a computer-readable storage medium on which a program is stored, and when the program is executed by a processor, the following steps are implemented:
  • the program When the program is executed by the processor, it can realize all the implementation manners in the above-mentioned information exchange method applied to the multicast service of the source base station, and can achieve the same technical effect. To avoid repetition, it is not repeated here.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art or the parts of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Landscapes

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

Abstract

本申请公开一种多播业务的信息交互方法及基站。其中，该方法在应用于目标基站时包括：向源基站发送所述多播业务的数据包在目标基站的状态信息。

Description

多播业务的信息交互方法及基站
相关申请的交叉引用
本申请基于申请号为202110055684.5、申请日为2021年01月15日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及移动通信技术领域，具体涉及一种多播业务的信息交互方法及基站。
背景技术
为了满足车对外界的信息交换(Vehicle to everything，V2X)，公共安全和多媒体等行业的需求，减轻大量单播业务带来的网络拥塞，提升大量用户同时在线的体验，相关技术提出了多播和广播业务(Multicast Broadcast Service，MBS)。该业务通过一个数据源向多个终端发送相同的数据包，实现数据包的共享，旨在有效的提高空口资源的利用率。
其中，多播业务中有个重要的目标就是保证终端在基站间移动过程中的业务连续性。当终端从一个已建立多播业务会话的基站或小区切换到另一个同样建立了多播业务会话的基站或小区时，怎样保证数据包能够在切换的过程中不丢失的传输到终端是现在亟待解决的问题。
传统切换场景下的数据交互流程如图1所示。在传统的切换领域，业务的连续性主要是通过源基站向目标基站发送序号状态传输(SN STATUS TRANSFER)消息来实现。图1中，当源基站发送切换命令给终端后，源基站建立与目标基站之间的数据前转通道，并发送SN STATUS TRANSFER消息给目标基站，告知目标基站数据无线承载(DRB)的下行PDCP SN传输状态，下行分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)序号(Sequence Number，SN)传输状态指示了目标基站将要分配给还未分配的新PDCP SDU的下一个PDCP SN，保证数据包的顺序传输，同时也避免了重复传输发生；对已分配PDCP SN，但终端在源基站下未确认的数据包,源基站可以通过建立下行数据转发通道再次转发PDCP SDU和SN。
在MBS切换流程中，当切换发生在源基站和目标基站都同时建立了相同MBS业务会话的场景中时，如何提高数据包传输的可靠性和多播业务的连续性，是一个亟待解决的问题。
发明内容
为解决相关技术问题，本申请的至少一个实施例提供了一种多播业务的信息交互方法及基站。
根据本申请的一个方面，至少一个实施例提供了一种多播业务的信息交互方法，应用于目标基站，包括：
向源基站发送所述多播业务的数据包在目标基站的状态信息。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
此外，根据本申请的至少一个实施例，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
此外，根据本申请的至少一个实施例，所述方法还包括：
接收所述源基站发送的以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
此外，根据本申请的至少一个实施例，所述方法还包括：
接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在所述源基站的状态信息包括：
所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
此外，根据本申请的至少一个实施例，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
所述第二类数据包是第二SN对应的数据包。
此外，根据本申请的至少一个实施例，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
此外，根据本申请的至少一个实施例，在向源基站发送所述多播业务的数据包在目标基站的状态信息之后，所述方法还包括：
接收所述源基站发送的停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
此外，根据本申请的至少一个实施例，所述向源基站发送所述多播业务的数据包在目标基站的状态信息，包括：
通过切换请求回复(英文可以表达为HANDOVER REQUEST ACKNWLEDGE)消息，向源基站发送所述多播业务的数据包在目标基站的状态信息。
此外，根据本申请的至少一个实施例，所述接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息，包括：
通过切换请求(英文可以表达为HANDOVER REQUEST)消息或序号状态传递(英文可以表达为SN STATUS TRANSFER)消息，接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种多播业务的信息交互方法，应用于源基站，包括：
接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
此外，根据本申请的至少一个实施例，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的SN。
此外，根据本申请的至少一个实施例，所述方法还包括：
向目标基站发送以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
此外，根据本申请的至少一个实施例，所述方法还包括：
向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在所述源基站的状态信息包括：
所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新SN。
此外，根据本申请的至少一个实施例，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
此外，根据本申请的至少一个实施例，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
所述第一类数据包是目标基站未缓存的数据包；所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
所述第二类数据包是第二SN对应的数据包。
此外，根据本申请的至少一个实施例，所述方法还包括：
根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第一类数据包和/或第二类数据包。
此外，根据本申请的至少一个实施例，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
此外，根据本申请的至少一个实施例，所述方法还包括：
根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第三类数据包。
此外，根据本申请的至少一个实施例，在接收目标基站发送的所述多播业务的数据包在目标基站的状态信息之后，所述方法还包括：
向所述目标基站发送停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
此外，根据本申请的至少一个实施例，所述接收目标基站发送的所述多播业务的数据包在目标基站的状态信息，包括：
通过切换请求回复消息，接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
此外，根据本申请的至少一个实施例，所述向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息，包括：
通过切换请求消息或序号状态传递消息，向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种目标基站，包括收发机和处理器，其中，
所述收发机，配置为向源基站发送所述多播业务的数据包在目标基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种目标基站，包括：
发送模块，配置为向源基站发送所述多播业务的数据包在目标基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种目标基站，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现上述目标基站侧任一方法的步骤。
根据本申请的另一方面，至少一个实施例提供了一种源基站，包括收发机和处理器，其中，
所述收发机，配置为接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种源基站，包括：
接收模块，配置为接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
根据本申请的另一方面，至少一个实施例提供了一种源基站，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现上述源基站侧任一方法的步骤。
根据本申请的另一方面，至少一个实施例提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有程序，所述程序被处理器执行时，实现上述目标基站侧或源基站侧任一方法的步骤。
与相关技术相比，本申请实施例提供的多播业务的信息交互方法及基站，在多播业务场景的终端在两个基站间切换时，可以通过基站间的信息交互，提高多播业务数据包的传输可靠性，保证多播业务连续性。另外，本申请实施例还可以在节约不必要的数据重复传输，节约传输资源。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目 的，而并不认为是对本申请的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1为相关技术的一种切换流程的示意图；
图2为相关技术的一种MBS切换流程的示意图；
图3为本申请实施例的多播业务的信息交互方法应用于目标基站时的流程图；
图4为本申请实施例的多播业务的信息交互方法应用于源基站时的流程图；
图5为本申请实施例的多播业务的信息交互方法的一种应用场景示意图；
图6为本申请实施例的多播业务的信息交互方法的另一种应用场景示意图；
图7为本申请实施例提供的目标基站的一种结构示意图；
图8为本申请实施例提供的目标基站的另一种结构示意图；
图9为本申请实施例提供的源基站的一种结构示意图；
图10为本申请实施例提供的源基站的另一种结构示意图。
具体实施方式
下面将参照附图更详细地描述本申请的示例性实施例。虽然附图中显示了本申请的示例性实施例，然而应当理解，可以以各种形式实现本申请而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本申请，并且能够将本申请的范围完整的传达给本领域的技术人员。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。说明书以及权利要求中“和/或”表示所连接对象的至少其中之一。
本文所描述的技术不限于NR系统以及长期演进型(Long Time Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，并且也可用于各种无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal  Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。术语“系统”和“网络”常被可互换地使用。CDMA系统可实现诸如CDMA2000、通用地面无线电接入(Universal Terrestrial Radio Access，UTRA)等无线电技术。UTRA包括宽带CDMA(Wideband Code Division Multiple Access，WCDMA)和其他CDMA变体。TDMA系统可实现诸如全球移动通信系统(Global System for Mobile Communication，GSM)之类的无线电技术。OFDMA系统可实现诸如超移动宽带(UltraMobile Broadband，UMB)、演进型UTRA(Evolution-UTRA，E-UTRA)、IEEE 802.21(Wi-Fi)、IEEE 802.16(WiMAX)、IEEE 802.20、Flash-OFDM等无线电技术。UTRA和E-UTRA是通用移动电信系统(Universal Mobile Telecommunications System，UMTS)的部分。LTE和更高级的LTE(如LTE-A)是使用E-UTRA的新UMTS版本。UTRA、E-UTRA、UMTS、LTE、LTE-A以及GSM在来自名为“第三代伙伴项目”(3rd Generation Partnership Project，3GPP)的组织的文献中描述。CDMA2000和UMB在来自名为“第三代伙伴项目2”(3GPP2)的组织的文献中描述。本文所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了NR系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用。
以下描述提供示例而并非限定权利要求中阐述的范围、适用性或者配置。可以对所讨论的要素的功能和布置作出改变而不会脱离本公开的精神和范围。各种示例可恰适地省略、替代、或添加各种规程或组件。例如，可以按不同于所描述的次序来执行所描述的方法，并且可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
在图2所示的MBS切换流程中，当切换发生在源基站和目标基站都已经建立了相同MBS会话的场景中时，核心网用户面功能(User Plane Function，UPF)节点需要给两个基站发送相同的数据包。由于在MBS业务流程中，源基站要给处在基站覆盖下的、所有请求了所述MBS的连接态终端发送MBS数据包，所以某个终端的切换并不影响源基站MBS数据包的发送。同样地，目标基站与切换后的新终端的连接建立也不影响目标基站向覆盖内的所有请求了MBS业务的连接态终端进行MBS数据包的发送。
当源基站发送切换命令给终端后，源基站建立数据前转通道，并发送SN STATUS TRANSFER消息给目标基站，告知目标基站最新的MBS数据包的PDCP SN，也可以用PDCP计数(COUNT)值。当终端与目标基站建立连接后，向目标基站发送PDCP状态报告(STATUS REPORT,SR)，告知目标基站终端在源基站最新收到的MBS数据包的SN。
由于源基站和目标基站距离终端侧的距离可能不同，且不同基站空口 的传输环境也不相同，所以导致同一时间处在不同基站覆盖内的终端收到从核心网发来的MBS数据包并不相同。由于基站在不同空口环境中传输数据包时存在快慢之分，当终端发生切换时很难保证MBS业务连续性且存在效率低的问题。另外，在切换过程中，源基站在收到MBS数据传输结束标识前需要前转数据包给目标基站，而此时目标基站可能已经从UPF获得相同的数据包，接口上和空口的数据包重复传输导致了传输资源的浪费。
为解决以上问题中的至少一种，本申请实施例提供了一种多播业务的信息交互方法，该信息交互方法中，终端在源基站下接收某个多播业务(如MBS)的数据包。另外，在切换发生之前，源基站和目标基站都已经建立了该多播业务的会话，核心网节点(如UPF或MB-UPF)给源基站和目标基站发送该多播业务的数据。如图3所示，该方法在应用于目标基站侧时，包括：
步骤31，向源基站发送所述多播业务的数据包在目标基站的状态信息。
上述步骤31可以在终端的切换准备阶段、终端成功接入目标基站之后或者接收到源基站发送的SN状态信息之后执行，即，目标基站可以在终端的切换准备阶段、终端成功接入目标基站之后或者接收到源基站发送的SN状态传递信息之后，向源基站发送所述多播业务的数据包在目标基站的状态信息。
通过向源基站发送所述多播业务的数据包在目标基站的状态信息，使得源基站可以获取所述多播业务的数据包在目标基站侧的实际发送状态，包括但不限于目标基站当前最新发送的数据包及其PDCP SN，目标基站已发送哪些数据包及其PDCP SN，目标基站侧缓存的数据包及其PDCP SN等信息，从而可以帮助源基站判断哪些数据包需要前转至目标基站，哪些数据包不需要再进行前转，也可以作为指示消息停止源基站向目标基站的数据前转过程。一方面可以提高数据包传输的可靠性并提升多播的业务连续性，另一方面还可以节约传输资源。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：目标基站当前缓存的所述多播业务的数据包的状态信息。例如，目标基站当前缓存的所述多播业务的数据包的PDCP SN，具体可以包括当前缓存的所有数据包的PDCP SN，或者是当前缓存的起始和终止数据包的PDCP SN，或者当前缓存的起始数据包的PDCP SN，等等。其中，所述目标基站当前缓存的所述多播业务的数据包的状态信息可以包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。该首个数据包的PDCP SN通常为PDCP PDU的SN。缓存中通常还包括所述多播业务的其他数据包的PDCP SN，其他数据包的PDCP SN通常大于首个数据包的PDCP SN，且通常这些数据包的PDCP SN是连续的。
在上述步骤31之后，源基站可以根据目标基站发送的所述多播业务的数据包在目标基站的状态信息，确定所述多播业务需要前转的数据包并转发给目标基站，所述目标基站可以接收源基站发送的以下信息中的至少一种：
1)所述源基站转发的所述PDCP SN之前的终端未确认的数据包。
所述源基站转发的所述PDCP SN之前的终端未确认的数据包是指，在源基站侧已经向所述终端发送，但未接收到所述终端的接收确认反馈的数据包，并且，该数据包的PDCP SN在所述目标基站当前缓存的所述多播业务的首个数据包的PDCP SN之前。也就是说，该数据包是终端未能从源基站成功接收的数据包，并且该数据包在目标基站侧已经发送过了并清除了缓存，终端也无法从目标基站侧获得该数据包。源基站将这些数据包前转至目标基站，以通过目标基站将这些数据包发送给终端，保证数据传输的可靠性。
2)所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包。
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包是指，源基站侧是从核心网节点接收到的所述多播业务的数据包中尚未分配PDCP SN的数据包，基站在发送数据包之前会为其分配PDCP SN，也就是说，这些数据包是从核心网接收到的，但还没有发送给终端。这些数据包后续分配的PDCP SN，如果在所述目标基站当前缓存的所述多播业务的首个数据包的PDCP SN之前，则由于该数据包在目标基站侧已经发送过了并清除了缓存，终端无法从目标基站侧获得该数据包，因此，可以将这些数据包前转至目标基站，以通过目标基站将这些数据包发送给终端，保证数据传输的可靠性。
3)所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息。
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息，可以通知目标基站哪些数据包是源基站已经成功发送了的，这样，目标基站可以不必重复发送这些数据包，以节约传输资源。
4)所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息，可以通知目标基站哪些数据包是源基站已经发送，但未收到终端的接收确认反馈的数据包，这样，目标基站可以继续向源基站发送这些数据包。
在一实施例中，在上述步骤31之前或之后，所述目标基站可以接收所述多播业务的数据包在所述源基站的状态信息，该信息是所述源基站发送的。
其中，在一实施例中，所述多播业务的数据包在所述源基站的状态信 息可以包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息可以包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN。其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。另外，所述第一PDCP SN也可以用PDCP COUNT值代替。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，具体可以包括：第一类数据包，和/或，第二类数据包；其中，所述第一类数据包是SN介于所述第一SN与目标基站当前缓存的首个数据包的第三SN之间的数据包，其中，所述第一SN小于第三SN；所述第二类数据包是第二SN对应的数据包。换句话说，所述第一类数据包的PDCP SN大于所述第一SN，且小于目标基站当前缓存的首个数据包的第三SN。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，具体可以包括：第三类数据包；其中，所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
在一实施例中，在所述步骤31之后，所述方法还可以包括：
接收所述源基站发送的停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述步骤31的具体实现可以包括：
通过切换请求回复消息，向源基站发送所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息，可以包括：
通过切换请求消息或序号状态传递消息，接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
本申请实施例中，在所述多播业务的数据包在目标基站的状态信息包括目标基站当前缓存的所述多播业务的数据包的状态信息的情况下，目标基站还可以接收所述源基站发送的以下信息中的至少一种，并根据以下信息中的至少一种，确定所述目标基站需要向所述终端发送的数据包和不需要向所述终端发送的数据包：
1)所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息。
对于所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息所对应的数据包，目标基站可以不再需要向终端继续发送。
2)所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN 信息。
对于所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息所对应的数据包，目标基站需要向终端继续发送。
在本申请实施例中，所述多播业务的数据包在目标基站的状态信息还可以用于告知或指示源基站停止转发数据。例如，源基站在根据所述多播业务的数据包在目标基站的状态信息，确定不需要发送所述多播业务的数据，或者，在源基站向目标基站转发所述多播业务的数据完毕时，源基站发送消息(即上述停止传输消息)指示结束源基站向目标基站的数据前转过程，从而可以及时结束数据前转。
本申请实施例中，所述需要源基站前转的所述多播业务的数据包通过数据包的SN进行指示，且SN的指示方式为以下方式中的任一种：
A)通过比特位图进行指示；
B)通过各个数据包的SN进行指示；
C)通过SN的起止范围进行指示；例如指示起始的SN和结束的SN，也可以指示起始的SN和具体的SN的数量，还可以指示结束的SN和具体的SN的数量。
请参照图4，本申请实施例提供的多播业务的信息交互方法，在应用于源基站时，包括：
步骤41，接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
通过以上步骤，源基站可以获得所述多播业务的数据包在目标基站的状态信息，进而源基站可以根据所述多播业务的数据包在目标基站的状态信息，确定是否需要向目标基站前转所述多播业务的数据包，以及，在需要前转数据包时，向所述目标基站前转对应的数据包，从而可以提高多播业务的传输可靠性，并避免或减少传输不必要的数据包，节约传输资源。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：目标基站当前缓存的所述多播业务的数据包的状态信息。具体地，目标基站当前缓存的所述多播业务的数据包的状态信息可以包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
源基站根据所述目标基站当前缓存的所述多播业务的数据包的状态信息，确定是否需要向目标基站前转所述多播业务的数据包，以及，在需要前转数据包时，向所述目标基站前转对应的数据包。
具体地，所述源基站可以向所述目标基站发送以下信息中的至少一种：
1)所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
2)所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
3)所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
4)所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，在上述步骤41之前或之后，所述源基站可以向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
其中，在一实施例中，所述多播业务的数据包在所述源基站的状态信息可以包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息可以包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息可以包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，可以包括：第一类数据包，和/或，第二类数据包；其中，所述第一类数据包是目标基站未缓存的，且SN介于所述第一SN与目标基站当前缓存的首个数据包的第三SN之间的数据包，其中，所述第一SN小于第三SN；换句话说，所述第一类数据包的PDCP SN大于所述第一SN，且小于目标基站当前缓存的首个数据包的第三SN；所述第二类数据包是第二SN对应的数据包。此时，在上述步骤41之后，所述源基站还可以根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第一类数据包和/或第二类数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，可以包括：第三类数据包；其中，所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。此时，在上述步骤41之后，所述源基站还可以根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第三类数据包。
另外，所述源基站还可以向目标基站发送以下信息中的至少一种，以提高目标基站的数据包传输效率，减少或避免发送不必要的数据包：
1)所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
2)所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，在所述步骤41之后，所述方法还可以包括：
向所述目标基站发送停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述步骤41的具体实现可以包括：
通过切换请求回复消息，接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息，可以包括：
通过切换请求消息或序号状态传递消息，向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
为了帮助更好地理解以上实施例，下面提供以上方法的若干具体示例。
下面示例中，将源基站和目标基站传输MBS数据包的快慢分情况进行说明。为了便于分析，假定UPF和基站之间传输数据包的NG-U SN作为基站间传输数据包的PDCP SN，这里默认服务质量流标识(QoS Flow ID，QFI)的SN作为NG-U SN。
如图5所示的第一种切换场景中，假设源基站的MBS数据包传输的速度比目标基站快，如图5所示，源基站在空口处传给终端SN1到8的数据包，终端在发生切换接入到目标基站后，和目标基站进行交互，得知目标基站侧已发送了SN1到5的数据包。根据第一种切换场景可能会有以下情况出现：
1)如果源基站在与终端的交互过程中没有发生丢包。由于数据包在目标基站到达速度慢的缘故，切换后的终端可以继续接收编号6到8的数据包。所以目标基站可以向源基站发送所述多播业务的数据包在目标基站的状态信息(下文中简称为状态信息)，告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
2)如果源基站在与终端的交互过程中发生了丢包。
i.如果丢失了编号3的数据包。由于数据包在目标基站到达速度慢的原因，切换后终端需要重收编号3的数据包并继续接收编号6到8的数据包。如果目标基站已缓存编号3的数据包，此时目标基站向源基站发送所述状态信息，告知自己的缓存信息，告知源基站不需要再发送编号3的数据包。如果基站未缓存编号3的数据包，此时目标基站向源基站发送所述状态信息，告知源基站仅需重复发送编号3的数据包。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
ii.如果丢失了编号6的数据包。由于数据包在目标基站到达速度慢的缘故，切换后终端可以继续接收编号6到8的数据包。目标基站向源基站发送所述状态信息，告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
3)如果源基站在与终端的交互过程中发送了编号8的数据包，终端实际已经收到但没有在切换前向源基站反馈。目标基站向源基站发送所述状态信息，告知编号8以后的数据包由目标基站发送，源基站提前结束数 据包的前转，起到结束标识的作用。
如图6所示的第二种切换场景中，假设源基站传输MBS数据包的速度比目标基站慢。如图6所示，源基站在空口处传了SN1到5的包，目标基站在空口处传了SN1到8的包。根据第二种切换场景可能会有以下情况出现：
1)如果源基站在与终端的交互过程中没有发生丢包，终端在源基站侧接收了源基站所有的数据包。在切换到目标基站后，由于数据包在目标基站到达速度快的缘故，终端会先补充接收编号6到8的数据包。
i.如果目标基站已缓存编号6到8的的数据包。目标基站可以通过缓存直接向终端发送缓存的数据包。此时，目标基站同时向源基站发送所述状态信息，告知自己的缓存信息，即告知源基站不需要再转发编号为6到8数据包。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
ii.如果目标基站未缓存编号6到8的的数据包。目标基站向源基站发送所述状态信息，告知自己的缓存状态，从而告知源基站终端未收到编号为6到8的数据包，请求源基站仅转发编号为6到8的数据包。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
2)如果源基站在与终端的交互过程中丢失了编号3的数据包。在切换到目标基站后，终端会先重收编号3的丢失的数据包以及编号6到8的数据包。
i.如果目标基站已缓存编号3及以后的数据包。目标基站可以通过缓存直接向终端发送缓存的数据包。此时，目标基站向源基站发送所述状态信息，告知自己的缓存信息，使源基站不需要再转发编号3及以后的数据包。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
ii.如果目标基站未缓存编号3的数据包但已缓存编号6到8的数据包。目标基站可以通过缓存向终端发送之前未收到的数据包。此时，目标基站向源基站发送所述状态信息，告知自己的缓存信息，请求源基站仅转发编号3的数据包，减少数据包的重复转发。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
iii.如果目标基站未缓存编号8以前的数据包。目标基站可以向源基站发送所述状态信息，请求源基站转发目标基站丢失的转发编号3的数据包以及之前未收到的编号6到8的数据包。同时，该信令告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
3)如果源基站在与终端的交互过程中发送了编号5的数据包，终端实 际已经收到但没有在切换前向源基站反馈。
i.如果目标基站已缓存编号5及以后的数据包，目标基站可以通过缓存直接向终端发送缓存的数据包。此时，目标基站向源基站发送所述状态信息，告知自己的缓存信息，使源基站不需要再转发编号5及以后的数据包。源基站提前结束数据包的前转，起到结束标识的作用。
ii.如果目标基站没有缓存编号5的数据包，终端在切换到目标基站后，终端会先向目标基站发送PDCP状态报告，告知目标基站自己实际已经接收到编号5的数据包。不需要源基站重复发送编号为5的数据包。然后目标基站根据自身缓存情况发送所述状态信息，告知源基站是否要发送编号6到8的数据包。同时，所述状态信息告知编号8以后的数据包由目标基站发送，源基站提前结束数据包的前转，起到结束标识的作用。
基于上面的场景分析，所述状态信息的具体内容包括多种情形：
情形1：所述状态信息中包含目标基站第一个缓存数据包对应的PDCP SN和目标基站未缓存数据包的PDCP SN以及在终端切换前未成功接收数据包的PDCP SN。根据目标基站当前的缓存情况，如果目标基站已经缓存需要前转的数据包，则可以不需要再经过源基站的数据前转，提前结束基站间的交互过程，减少用户面数据传输；如果目标基站未缓存前转数据包，则源基站只需要发送此类数据包。
情形2：所述状态信息中包含需要源基站进行数据前转的所有数据包对应的PDCP SN。所述状态信息中可以明确告知源基站哪些数据包需要重复发送，其中可以通过在一定范围内标识所有数据包的接收情况来指示，如比特位图的形式，当某个PDCP SN对应的标志位被置位(如值为1)时，表示该数据包需要重复发送。这种消息格式让源基站仅转发目标基站未缓存的数据包和终端切换前未成功接收的数据包。
情形3：所述状态信息中包含终端切换时刻目标基站传输数据包的PDCP SN和目标基站未缓存数据包的PDCP SN以及在终端切换前未成功接收数据包的PDCP SN。在源基站传输数据包的速度比目标基站慢的场景中，所述状态信息中包含终端切换时刻目标基站所传输数据包的编号，目的是告诉源基站后面的数据包可以由目标基站直接发送，不需要再经过数据前转。源基站仅需要转发终端切换前未成功接收数据包和未缓存的前转数据包。在源基站传输数据包的速度比目标基站快的场景中，由于数据包到达目标基站慢的缘故，源基站仅需要转发终端切换前未成功接收的数据包即可。
从以上示例可以看出，本申请实施例可以在多播业务场景下终端在两个基站间切换时，通过基站间的交互流程保证数据包的可靠传输以及保证多播业务连续性。
以上介绍了本申请实施例的各种方法。下面将进一步提供实施上述方法的装置。
本申请实施例提供了图7所示的一种目标基站，包括：
发送模块71，配置为向源基站发送所述多播业务的数据包在目标基站的状态信息。
通过以上模块，本申请实施例可以向源基站通知目标基站的数据包状态信息，使得源基站可以更为有效的进行数据前转，提高数据传输效率和可靠性，节约传输资源。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
在一实施例中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
在一实施例中，所述目标基站还包括：
第一接收模块，配置为接收所述源基站发送的以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述目标基站还包括：
第二接收模块，配置为接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
所述第二类数据包是第二SN对应的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
在一实施例中，所述目标基站还包括：
第一接收模块，配置为接收所述源基站发送的以下信息中的至少一种，并确定所述目标基站需要向所述终端发送的数据包和不需要向所述终端发送的数据包：
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述第二接收模块，配置为接收所述源基站发送的停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述发送模块71，配置为通过切换请求回复消息，向源基站发送所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述第二接收模块，配置为通过切换请求消息或序号状态传递消息，接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
需要说明的是，该实施例中的装置是与上述图3所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。在此需要说明的是，本申请实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
请参考图8，本申请实施例提供了目标基站的一结构示意图，包括：处理器801、收发机802、存储器803和总线接口，其中：
在本申请实施例中，目标基站还包括：存储在存储器上803并可在处理器801上运行的程序，所述程序被处理器801执行时实现如下步骤：
向源基站发送所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
在一实施例中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：接收所述源基站发送的以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
所述第二类数据包是第二SN对应的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：接收所述源基站发送的以下信息中的至少一种，并确定所述目标基站需要向所述终端发送的数据包和不需要向所述终端发送的数据包：
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
接收所述源基站发送的停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
通过切换请求回复消息，向源基站发送所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
通过切换请求消息或序号状态传递消息，接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
可理解地，本申请实施例中，所述计算机程序被处理器801执行时可实现上述图3所示的方法实施例的各个过程，且能达到相同的技术效果， 为避免重复，这里不再赘述。
在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器801代表的一个或多个处理器和存储器803代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机802可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器801负责管理总线架构和通常的处理，存储器803可以存储处理器801在执行操作时所使用的数据。
需要说明的是，该实施例中的终端是与上述图3所示的方法对应的设备，上述各实施例中的实现方式均适用于该终端的实施例中，也能达到相同的技术效果。该设备中，收发机802与存储器803，以及收发机802与处理器801均可以通过总线接口通讯连接，处理器801的功能也可以由收发机802实现，收发机802的功能也可以由处理器801实现。在此需要说明的是，本申请实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
在本申请的一些实施例中，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现以下步骤：
向源基站发送所述多播业务的数据包在目标基站的状态信息。
该程序被处理器执行时能实现上述应用于目标基站侧的多播业务的信息交互方法中的所有实现方式，且能达到相同的技术效果，为避免重复，此处不再赘述。
本申请实施例提供了图9所示的一种源基站，包括：
接收模块91，配置为接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
通过以上模块，本申请实施例可以使得源基站获得目标基站的数据包状态信息，从而帮助源基站更为有效的进行数据前转，提高数据传输效率和可靠性，节约传输资源。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
在一实施例中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
在一实施例中，所述源基站还包括：
第一发送模块，配置为向目标基站发送以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述源基站还包括：
第二发送模块，配置为向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，所述第一类数据包是目标基站未缓存的数据包；所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；所述第二类数据包是第二SN对应的数据包。
在一实施例中，所述源基站还包括：
第三发送模块，配置为根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第一类数据包和/或第二类数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
在一实施例中，所述源基站还包括：
第四发送模块，配置为根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第三类数据包。
在一实施例中，所述源基站还包括：
第五发送模块，配置为向目标基站发送以下信息中的至少一种：
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述第二发送模块，配置为向所述目标基站发送停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述接收模块91，配置为通过切换请求回复消息，接 收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述第二发送模块，配置为通过切换请求消息或序号状态传递消息，向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
需要说明的是，该实施例中的装置是与上述图4所示的方法对应的设备，上述各实施例中的实现方式均适用于该设备的实施例中，也能达到相同的技术效果。在此需要说明的是，本申请实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
请参考图10，本申请实施例提供了网络侧设备的一结构示意图，包括：处理器1001、收发机1002、存储器1003和总线接口，其中：
在本申请实施例中，网络侧设备还包括：存储在存储器上1003并可在处理器1001上运行的程序，所述程序被处理器1001执行时实现如下步骤：
接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
在一实施例中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
向目标基站发送以下信息中的至少一种：
所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
在一实施例中，所述多播业务的数据包在所述源基站的状态信息包括：所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
在一实施例中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括： 第一类数据包，和/或，第二类数据包；其中，所述第一类数据包是目标基站未缓存的数据包；所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；所述第二类数据包是第二SN对应的数据包。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第一类数据包和/或第二类数据包。
在一实施例中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述第三SN的PDCP SN。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第三类数据包。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
向目标基站发送以下信息中的至少一种：
所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
向所述目标基站发送停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
通过切换请求回复消息，接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
在一实施例中，所述处理器执行所述程序时还实现以下步骤：
通过切换请求消息或序号状态传递消息，向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
可理解地，本申请实施例中，所述计算机程序被处理器1001执行时可实现上述图4所示的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1001代表的一个或多个处理器和存储器1003代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1002可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器1001负责管理总线架构和通常的处理，存储器1003可以存储 处理器1001在执行操作时所使用的数据。
需要说明的是，该实施例中的终端是与上述图4所示的方法对应的设备，上述各实施例中的实现方式均适用于该终端的实施例中，也能达到相同的技术效果。该设备中，收发机1002与存储器1003，以及收发机1002与处理器1001均可以通过总线接口通讯连接，处理器1001的功能也可以由收发机1002实现，收发机1002的功能也可以由处理器1001实现。在此需要说明的是，本申请实施例提供的上述设备，能够实现上述方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
在本申请的一些实施例中，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现以下步骤：
接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
该程序被处理器执行时能实现上述应用于源基站的多播业务的信息交互方法中的所有实现方式，且能达到相同的技术效果，为避免重复，此处不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (35)

  1. 一种多播业务的信息交互方法，应用于目标基站，包括：
    向源基站发送所述多播业务的数据包在目标基站的状态信息。
  2. 如权利要求1所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的分组数据汇聚协议PDCP序号SN。
  3. 如权利要求1所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
  4. 如权利要求3所述的方法，其中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
  5. 如权利要求4所述的方法，其中，所述方法还包括：
    接收所述源基站发送的以下信息中的至少一种：
    所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
    所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
    所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
    所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信息。
  6. 如权利要求1所述的方法，其中，所述方法还包括：
    接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
  7. 如权利要求6所述的方法，其中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
  8. 如权利要求6所述的方法，其中，所述多播业务的数据包在所述源基站的状态信息包括：
    所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
    其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
  9. 如权利要求1所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
  10. 如权利要求9所述的方法，其中，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
    所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
    所述第二类数据包是第二SN对应的数据包。
  11. 如权利要求9所述的方法，其中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
    所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述目标基站当前缓存的首个数据包的第三SN的PDCP SN。
  12. 如权利要求1所述的方法，其中，在向源基站发送所述多播业务的数据包在目标基站的状态信息之后，所述方法还包括：
    接收所述源基站发送的停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
  13. 如权利要求1所述的方法，其中，所述向源基站发送所述多播业务的数据包在目标基站的状态信息，包括：
    通过切换请求回复消息，向源基站发送所述多播业务的数据包在目标基站的状态信息。
  14. 如权利要求6所述的方法，其中，所述接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息，包括：
    通过切换请求消息或序号状态传递消息，接收所述源基站发送的所述多播业务的数据包在所述源基站的状态信息。
  15. 一种多播业务的信息交互方法，应用于源基站，包括：
    接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
  16. 如权利要求15所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：所述目标基站当前最新发送的所述多播业务的数据包的PDCP SN。
  17. 如权利要求15所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：目标基站当前缓存的所述多播业务的数据包的状态信息。
  18. 如权利要求17所述的方法，其中，目标基站当前缓存的所述多播业务的数据包的状态信息包括：目标基站当前缓存的所述多播业务的首个数据包的PDCP SN。
  19. 如权利要求18所述的方法，其中，所述方法还包括：
    向目标基站发送以下信息中的至少一种：
    所述源基站转发的所述PDCP SN之前的终端未确认的数据包；
    所述源基站转发的所述PDCP SN之前的尚未分配PDCP SN的数据包；
    所述源基站发送的、且所述终端已确认数据包对应的PDCP SN信息；
    所述源基站发送的、且所述终端未确认的数据包对应的PDCP SN信 息。
  20. 如权利要求15所述的方法，其中，所述方法还包括：
    向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
  21. 如权利要求20所述的方法，其中，所述多播业务的数据包在所述源基站的状态信息包括：所述源基站当前最新发送的所述多播业务的数据包的PDCP SN。
  22. 如权利要求20所述的方法，其中，所述多播业务的数据包在所述源基站的状态信息包括：
    所述多播业务的第一SN和/或GTP-U扩展头携带的终端未确认的PDCP PDU对应的PDCP SDU的第二SN；
    其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN。
  23. 如权利要求15所述的方法，其中，所述多播业务的数据包在目标基站的状态信息包括：需要源基站前转的所述多播业务的数据包。
  24. 如权利要求23所述的方法，其中，所述需要源基站前转的所述多播业务的数据包，包括：第一类数据包，和/或，第二类数据包；其中，
    所述第一类数据包是目标基站未缓存的数据包；所述第一类数据包的PDCP SN大于第一SN，且小于目标基站当前缓存的首个数据包的第三SN，其中，所述第一SN为所述多播业务的数据包在源基站侧已分配的最新PDCP SN，所述第一SN小于第三SN；
    所述第二类数据包是第二SN对应的数据包。
  25. 如权利要求24所述的方法，其中，所述方法还包括：
    根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第一类数据包和/或第二类数据包。
  26. 如权利要求23所述的方法，其中，所述需要源基站前转的所述多播业务的数据包，包括：第三类数据包；其中，
    所述第三类数据包是第四SN对应的数据包，所述第四SN是所述第二SN中小于所述目标基站当前缓存的首个数据包的第三SN的PDCP SN。
  27. 如权利要求26所述的方法，其中，所述方法还包括：
    根据所述多播业务的数据包在目标基站的状态信息，向目标基站前转发送所述第三类数据包。
  28. 如权利要求15所述的方法，其中，在接收目标基站发送的所述多播业务的数据包在目标基站的状态信息之后，所述方法还包括：
    向所述目标基站发送停止传输消息；所述停止传输消息用于指示结束所述源基站向所述目标基站的数据前转过程。
  29. 如权利要求15所述的方法，其中，所述接收目标基站发送的所述多播业务的数据包在目标基站的状态信息，包括：
    通过切换请求回复消息，接收目标基站发送的所述多播业务的数据包在目标基站的状态信息。
  30. 如权利要求20所述的方法，其中，所述向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息，包括：
    通过切换请求消息或序号状态传递消息，向所述目标基站发送所述多播业务的数据包在所述源基站的状态信息。
  31. 一种目标基站，包括收发机和处理器，其中，
    所述收发机，配置为向源基站发送所述多播业务的数据包在目标基站的状态信息。
  32. 一种目标基站，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求1至14任一项所述的方法的步骤。
  33. 一种源基站，包括收发机和处理器，其中，
    所述收发机，配置为接收目标基站发送的多播业务的数据包在目标基站的状态信息。
  34. 一种源基站，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序，所述程序被所述处理器执行时实现如权利要求15至30任一项所述的方法的步骤。
  35. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至30任一项所述的方法的步骤。
PCT/CN2022/072075 2021-01-15 2022-01-14 多播业务的信息交互方法及基站 WO2022152257A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110055684.5A CN114765820B (zh) 2021-01-15 2021-01-15 多播业务的信息交互方法及基站
CN202110055684.5 2021-01-15

Publications (1)

Publication Number Publication Date
WO2022152257A1 true WO2022152257A1 (zh) 2022-07-21

Family

ID=82363467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072075 WO2022152257A1 (zh) 2021-01-15 2022-01-14 多播业务的信息交互方法及基站

Country Status (2)

Country Link
CN (1) CN114765820B (zh)
WO (1) WO2022152257A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101035356A (zh) * 2006-03-09 2007-09-12 华为技术有限公司 一种移动终端越区切换中网络侧业务数据的下发方法
CN101267593A (zh) * 2007-03-15 2008-09-17 华为技术有限公司 对目标小区进行组播广播多媒体业务激活的方法及基站
CN101601225A (zh) * 2006-03-22 2009-12-09 Lg电子株式会社 在移动通信系统中支持越区切换的方法
WO2013139778A1 (en) * 2012-03-19 2013-09-26 Telefonaktiebolaget L M Ericsson (Publ) Service continuity in handover situations in cellular communication systems
CN106658418A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 车联网v2x业务数据包传输方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101035356A (zh) * 2006-03-09 2007-09-12 华为技术有限公司 一种移动终端越区切换中网络侧业务数据的下发方法
CN101601225A (zh) * 2006-03-22 2009-12-09 Lg电子株式会社 在移动通信系统中支持越区切换的方法
CN101267593A (zh) * 2007-03-15 2008-09-17 华为技术有限公司 对目标小区进行组播广播多媒体业务激活的方法及基站
WO2013139778A1 (en) * 2012-03-19 2013-09-26 Telefonaktiebolaget L M Ericsson (Publ) Service continuity in handover situations in cellular communication systems
CN106658418A (zh) * 2015-11-02 2017-05-10 中兴通讯股份有限公司 车联网v2x业务数据包传输方法及装置

Also Published As

Publication number Publication date
CN114765820A (zh) 2022-07-19
CN114765820B (zh) 2024-07-02

Similar Documents

Publication Publication Date Title
KR101387475B1 (ko) 복수의 네트워크 엔터티를 포함하는 이동 통신시스템에서의 데이터 처리 방법
JP7174058B2 (ja) 伝送モードを判定するための方法およびデバイス、記憶媒体、ならびに電子デバイス
KR20230003065A (ko) 베어러 구성 방법 및 장치, 컨텍스트 정보 관리 방법 및 장치, 해제 방법 및 장치, 설비
WO2013170789A1 (zh) 一种数据转发的方法、设备及通讯系统
EP2938025B1 (en) Method of data retransmission in collaborative service transmission and access network gateway thereof
KR101371240B1 (ko) 무선 전기통신 네트워크에서의 핸드오버 방법 및 장치
WO2022001928A1 (zh) 通信的方法和装置
WO2018027947A1 (zh) 一种数据处理方法以及相关设备
WO2017201743A1 (zh) 传输方法、基站和终端
CN113271551A (zh) 一种数据流传输方法、终端和网络侧设备
CN110708720A (zh) 切换方法、分布单元、终端、集中单元及计算机存储介质
CN110839267B (zh) 服务节点更新方法、终端设备和网络侧设备
WO2015018009A1 (zh) 用于自动重传的方法、用户设备和基站
CN101415219A (zh) 一种数据处理的方法、系统和装置
WO2022152257A1 (zh) 多播业务的信息交互方法及基站
WO2022151297A1 (zh) 数据传输方法及装置
WO2021190233A1 (zh) 数据传输方法及装置
CN113498025B (zh) 承载变更方法、网络设备及终端设备
CN113475120B (zh) 小区切换时的数据传输方法及装置
WO2023065292A1 (en) Lossless multicast and broadcast data transmissions in handovers
WO2023065291A1 (en) Lossless multicast and broadcast data transmissions in handovers
WO2015089837A1 (zh) 路由优化的方法、路由器及位置管理实体
WO2022147782A1 (en) Methods and apparatuses for handling a mbs at a ran node
WO2023083378A1 (zh) 一种数据传输方法、装置、通信设备和存储介质
US20230020573A1 (en) Transmission tunnel changing method, access network device, and core network device

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 06/11/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 22739132

Country of ref document: EP

Kind code of ref document: A1