WO2021218788A1 - 数据重传方法、装置、目标节点、源节点及终端 - Google Patents

数据重传方法、装置、目标节点、源节点及终端 Download PDF

Info

Publication number
WO2021218788A1
WO2021218788A1 PCT/CN2021/089120 CN2021089120W WO2021218788A1 WO 2021218788 A1 WO2021218788 A1 WO 2021218788A1 CN 2021089120 W CN2021089120 W CN 2021089120W WO 2021218788 A1 WO2021218788 A1 WO 2021218788A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
target node
data packet
source
node
Prior art date
Application number
PCT/CN2021/089120
Other languages
English (en)
French (fr)
Inventor
张艳霞
谢振华
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to JP2022566295A priority Critical patent/JP7392176B2/ja
Priority to KR1020227041248A priority patent/KR20230004786A/ko
Priority to EP21795959.2A priority patent/EP4124080A4/en
Publication of WO2021218788A1 publication Critical patent/WO2021218788A1/zh
Priority to US17/968,665 priority patent/US20230039646A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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/0009—Control or signalling for completing the hand-off for a plurality of users or terminals, e.g. group communication or moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/165—Performing reselection for specific purposes for reducing network power consumption
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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
    • H04W36/16—Performing reselection for specific purposes

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a data retransmission method, device, target node, source node, and terminal.
  • Multimedia broadcast and multicast service Multimedia Broadcast and Multicast Service
  • MBS broadcast multicast service
  • MBMS/MBS transmission method 1 Send through physical multicast channel (PMCH) in MBMS single frequency network (Multimedia Broadcast Multicast service Single Frequency Network, MBSFN) subframe.
  • PMCH physical multicast channel
  • MBSFN Multimedia Broadcast Multicast service Single Frequency Network
  • control information is sent through system information (such as system information block SIB13) and broadcast control channel (Multicast Control Channel, MCCH), and data is sent through broadcast service channel (Multicast Traffic Channel, MTCH).
  • system information such as system information block SIB13
  • MCCH Multicast Control Channel
  • MTCH Multicast Traffic Channel
  • MBMS/MBS transmission mode 2 Transmission via a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) scheduled by a physical downlink control channel (Physical Downlink Control Channel, PDCCH).
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Downlink Control Channel
  • the control information is sent through system information (such as the system information block SIB20) and the single cell broadcast control channel (Single Cell Multicast Control Channel, SC-MCCH), and the data is sent through the Single Cell Multicast Traffic Channel (SC-MTCH). )send.
  • system information such as the system information block SIB20
  • SC-MCCH Single Cell Multicast Control Channel
  • SC-MTCH Single Cell Multicast Traffic Channel
  • the SC-MCCH is sent through the PDSCH scheduled by the Single Cell Radio Network Temporary Identity (SC-RNTI) PDCCH
  • SC-RNTI Single Cell Radio Network Temporary Identity
  • G-RNTI Group Radio Network Temporary Identity
  • MBS service is transmitted through a specific MBMS Radio Bearer (MBMS Radio Bearer, MRB).
  • MBS business can be marked by the following identification:
  • TMGI Temporary Mobile Group Identity
  • the terminal When the terminal switches from a cell that provides multicast services in multicast mode to another cell that provides services in multicast mode, the terminal may lose part of its data due to handover and/or data transmission between the two cells is not synchronized, which is a minimum The terminal loses data.
  • the purpose of the embodiments of this application is to provide a data retransmission method, device, target node, source node, and terminal, which can solve the problem of handover and/or data transmission between the two cells when the terminal switches between the cells of the multicast service.
  • Asynchronization may cause the terminal to lose some data.
  • an embodiment of the present application provides a data retransmission method, which is applied to a target node, and includes:
  • N is an integer greater than or equal to 1;
  • mapping relationship data retransmission is performed.
  • an embodiment of the present application provides a data retransmission method, which is applied to a source node, and includes:
  • N is an integer greater than or equal to 1.
  • an embodiment of the present application provides a data retransmission method, which is applied to a terminal, and includes:
  • the source PDCP sequence number of the data packet is the PDCP sequence number allocated by the source node to the data packet.
  • an embodiment of the present application provides a data retransmission device, which is applied to a target node, and includes:
  • the relationship acquisition module is used to acquire the mapping relationship between the GTP-U serial numbers of the N data packets sent by the source node and the source PDCP serial numbers respectively allocated by the source node to the N data packets;
  • N is an integer greater than or equal to 1 ;
  • the data retransmission module is used to perform data retransmission according to the mapping relationship.
  • an embodiment of the present application provides a data retransmission device, which is applied to a source node, and includes:
  • the relationship sending module is configured to send the mapping relationship between the GTP-U sequence numbers of N data packets and the source PDCP sequence numbers respectively allocated by the source node to the N data packets to the target node; N is an integer greater than or equal to 1.
  • an embodiment of the present application provides a data retransmission device, which is applied to a terminal, and includes:
  • the retransmission receiving module is configured to receive the data packet retransmitted by the target node according to the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number after the terminal is switched to the target node;
  • the source PDCP sequence number of the data packet is the PDCP sequence number allocated by the source node to the data packet.
  • an embodiment of the present application provides a communication device that includes a processor, a memory, and a program or instruction that is stored on the memory and can run on the processor.
  • the program or instruction is The processor implements the steps of the method described in the first aspect or the second aspect or the third aspect when executed.
  • an embodiment of the present application provides a readable storage medium that stores a program or instruction on the readable storage medium, and when the program or instruction is executed by a processor, it implements the first aspect or the second aspect or the first aspect.
  • an embodiment of the present application provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run a program or an instruction to implement the chip as in the first aspect Or the method described in the second or third aspect.
  • an embodiment of the present application also provides an electronic device configured to execute the method described in the first aspect or the second aspect or the third aspect.
  • an embodiment of the present application also provides a data retransmission device, which is configured to execute the method as described in the first aspect or the second aspect or the third aspect.
  • the embodiments of the present application also provide a computer program product, which is executed by at least one processor to implement the method according to the first aspect or the second aspect or the third aspect.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing the terminal handover
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • FIG. 1 shows one of the steps of the data retransmission method provided by the embodiment of the present application
  • FIG. 2 shows the second step flow chart of the data retransmission method provided by the embodiment of the present application
  • FIG. 3 shows the third step flow chart of the data retransmission method provided by the embodiment of the present application
  • FIG. 4 shows an interactive schematic diagram of an example of a data retransmission method provided by an embodiment of the present application
  • FIG. 5 shows one of the schematic structural diagrams of the data retransmission device provided by the embodiment of the present application
  • FIG. 6 shows the second structural diagram of the data retransmission device provided by the embodiment of the present application.
  • FIG. 7 shows the third structural diagram of a data retransmission device provided by an embodiment of the present application.
  • FIG. 8 shows a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • FIG. 9 shows a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • the data retransmission method, device, target node, source node, and terminal provided in the embodiments of the present application can be applied to a wireless communication system.
  • the wireless communication system may adopt a 5G system, or an evolved Long Term Evolution (eLTE) system, or a subsequent evolved communication system.
  • eLTE evolved Long Term Evolution
  • the terminal provided by the embodiment of the application may be a mobile phone, a tablet computer, a notebook computer, an Ultra-Mobile Personal Computer (UMPC), a netbook, a wearable device (Wearable Device), a vehicle-mounted device, or a personal digital assistant (Personal Digital Assistant). Digital Assistant, PDA) etc.
  • UMPC Ultra-Mobile Personal Computer
  • netbook a wearable device
  • Vehicle-mounted device or a personal digital assistant (Personal Digital Assistant).
  • PDA Personal Digital Assistant
  • an embodiment of the present application provides a data retransmission method, which is applied to a target node, and includes:
  • Step 101 Obtain the mapping relationship between the GTP-U sequence numbers of the N data packets sent by the source node and the source PDCP sequence numbers respectively allocated by the source node for the N data packets; N is an integer greater than or equal to 1; where, GPRS tunnelling protocol user plane sequence number (GPRS Tunnelling Protocol user plane sequence number, GTP-U sequence number, also called GTP-U SN). Packet Data Convergence Protocol Sequence Number (Packet Data Convergence Protocol Sequence Number, PDCP sequence number, also called PDCP SN).
  • Step 102 Perform data retransmission according to the mapping relationship.
  • the source node and the target node are both network nodes that use the multicast mode for multicast transmission, and the terminal is likely to cause data loss during the process of switching from the source node to the target node; in this application, the target node is based on the data packet
  • the mapping relationship between the GTP-U sequence number and the source PDCP sequence number is used for data retransmission, reducing the amount of data lost by the terminal during the handover process, to further meet the business needs of the multicast service, so as to solve the data caused by the terminal during the handover process Lost problem.
  • step 102 includes:
  • mapping relationship data retransmission is performed through terminal dedicated scheduling resources or temporary scheduling resources.
  • terminal-specific scheduling resources can be radio resources scheduled through terminal-specific scheduling (such as terminal C-RNTI); temporary scheduling resources can be through temporary scheduling (such as temporary G-RNTI allocated to the terminal by the target node, that is, the difference
  • the target node uses the multicast mode to transmit the scheduling information of the multicast service, such as G-RNTI) to schedule the radio resources.
  • the method further includes:
  • the receiving status indication information of the terminal to the data packet sent by the source node, where the receiving status indication information is used to indicate the source PDCP sequence number of at least one first data packet; the first data packet is not before the node switch The data packet received by the terminal.
  • the terminal actively reports the PDCP status report to the target node when or after establishing a connection with the target node, so that the target node can learn the receiving status indication information of the terminal; or the target node requests or the source node instructs the terminal to report PDCP to the target node Status report to obtain the receiving status indication information of the terminal.
  • the target node is based on the PDCP status report.
  • the mapping relationship between GTP-U SN and PDCP SN is obtained from the source node, it can be determined that the data packet corresponding to GTP-U SN is not received by the terminal, and the data that has not been received can be retransmitted.
  • step 102 includes:
  • the data transmission according to the source PDCP sequence number of the at least one first data packet and the mapping relationship includes:
  • mapping relationship data retransmission starts from the first data packet with the smallest PDCP sequence number in the at least one first data packet.
  • step 101 includes:
  • the GTP-U sequence number and the source PDCP sequence number of the source node When the source node decides to switch the terminal to the target node, the GTP-U sequence number and the source PDCP sequence number of the source node’s first data packet to be sent; for example, the source node is the first to switch the terminal to the target node.
  • the timing for the source node to initiate the status indication information may be when the source node decides to send a handover command to the terminal, or when the source node sends a handover command to the terminal, or after the source node sends a handover command to the terminal, which is not specifically limited here.
  • the method before step 102, the method further includes:
  • the forwarded data packet may be data cached by the source node and/or new data obtained from the core network node.
  • the source node when the source node forwards the data packet to the destination node, it may also provide a mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, where the source PDCP sequence number is the source node allocated for the data packet PDCP serial number.
  • the receiving the N data packets forwarded by the source node in the order of the GTP-U sequence numbers of the N data packets includes:
  • the second data packet is the next data packet that is being sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet to be sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet that the terminal did not receive before the handover.
  • step 102 includes:
  • mapping relationship the next data packet of the data packet being sent by the source node when the terminal is switched to the target node starts to perform data retransmission in order
  • the mapping relationship when the terminal is switched to the target node, the first data packet to be sent of the source node is retransmitted in sequence.
  • the method before step 101, the method further includes:
  • the handover request message carries at least one of a multicast service identifier and first indication information that instructs the source node to request the forwarding of the multicast service data;
  • the multicast service identifier can be TMGI, or a multicast service sequence number (for example, the source node obtains a list of multicast services that the target node can support through the Xn interface establishment process, and the source node can use the multicast service sequence number in the list Indicates the corresponding multicast service).
  • the first indication information is DL forwarding IE (downlink forwarding IE).
  • the IE is set to the first value, it means that the source node requests to forward the corresponding multicast service data.
  • the IE is set to the second value, it means that the source The node does not request to forward the corresponding multicast service data.
  • the first indication information is a 1-bit indication.
  • the first indication information is a specific indication. When the specific indication exists, it means that the source node requests to forward the corresponding multicast service data, and when the specific indication does not exist, it means that the source node does not request to forward the corresponding multicast service data.
  • the multicast service identifier may be TMGI;
  • the second indication information indicating that the target node agrees to forward the multicast service data for example, the second indication information is a specific IE, and when the specific IE exists, it means that the target node agrees to the multicast service data forwarding, and the target can be based on the information provided by the IE.
  • the GTP-U sequence number performs data forwarding. When the specific IE does not exist, it means that the target node does not agree with the multicast service data forwarding.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid Automatic Repeat reQuest (HARQ) process information used for data retransmission; for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • Configuration information of public resources used for multicast data transmission in multicast mode where the configuration information of the public resources may be scheduling information when the target node sends the multicast service in multicast mode, for example, the corresponding multicast service Scheduling information G-RNTI (this G-RNTI is different from the above-mentioned temporary G-RNTI).
  • the source node determines whether to request the forwarding of multicast service data based on the requirements of the multicast service. For example, if a certain multicast service has a higher quality of service (such as higher reliability), the source node carries the request in the handover request. Forward the first indication information of the multicast service data. Otherwise, the first indication information is not carried.
  • the method before step 102, the method further includes:
  • the handover command message carries at least one of the following information:
  • Multicast service identifier the multicast service identifier may be TMGI.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • the configuration information of the public resource may be the scheduling information when the target node sends the multicast service in a multicast manner, for example, the scheduling information G-RNTI corresponding to a certain multicast service (the G-RNTI is different from the aforementioned temporary G-RNTI). ).
  • the method further includes:
  • step 102 the method further includes:
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing The amount of data lost by the terminal during the handover process can further meet the service requirements of the multicast service, so as to solve the problem of data loss caused by the terminal during the handover process.
  • an embodiment of the present application also provides a data retransmission method, which is applied to a source node, and includes:
  • Step 201 Send a mapping relationship between the GTP-U sequence numbers of N data packets and the source PDCP sequence numbers respectively allocated by the source node for the N data packets to the target node; N is an integer greater than or equal to 1.
  • the GPRS Tunnelling Protocol user plane sequence number (GPRS Tunnelling Protocol user plane sequence number, GTP-U sequence number, may also be referred to as GTP-U SN).
  • Packet Data Convergence Protocol Sequence Number (Packet Data Convergence Protocol Sequence Number, PDCP sequence number, also called PDCP SN).
  • the source node and the target node are both network nodes that use the multicast mode for multicast transmission, and the terminal is likely to cause data loss during the process of switching from the source node to the target node; in this application, the target node is based on the data packet
  • the mapping relationship between the GTP-U sequence number and the source PDCP sequence number is used for data retransmission, reducing the amount of data lost by the terminal during the handover process, to further meet the business needs of the multicast service, so as to solve the data caused by the terminal during the handover process Lost problem.
  • the execution subject may be a data retransmission device, or a control module in the data retransmission device for executing the loaded data retransmission method.
  • the data retransmission method executed by the data retransmission device is taken as an example to illustrate the data retransmission method provided in the embodiment of this application.
  • step 201 includes:
  • the status indication information includes at least one of the following information:
  • the GTP-U sequence number and the source PDCP sequence number of the source node When the source node decides to switch the terminal to the target node, the GTP-U sequence number and the source PDCP sequence number of the source node’s first data packet to be sent; for example, the source node is the first to switch the terminal to the target node.
  • the timing for the source node to initiate the status indication information may be when the source node decides to send a handover command to the terminal, or when the source node sends a handover command to the terminal, or after the source node sends a handover command to the terminal, which is not specifically limited here.
  • the method further includes:
  • the data packets are forwarded to the target node in the order of the GTP-U sequence numbers of the N data packets.
  • the forwarded data packet may be data cached by the source node and/or new data obtained from the core network node.
  • the source node when the source node forwards the data packet to the destination node, it may also provide a mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, where the source PDCP sequence number is the source node allocated for the data packet PDCP serial number.
  • the forwarding of the data packets to the target node in the order of the GTP-U sequence numbers of the N data packets includes:
  • the second data packet is the next data packet that is being sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet to be sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet that the terminal did not receive before the handover.
  • the method before step 201, the method further includes:
  • the handover request message carries at least one of a multicast service identifier and first indication information that instructs the source node to request the forwarding of multicast service data; wherein the multicast service identifier may It is a TMGI or a multicast service sequence number (for example, the source node obtains a list of multicast services that the target node can support through the Xn interface establishment process, and the source node can indicate the corresponding multicast service through the multicast service sequence number in the list).
  • the first indication information is DL forwarding IE (downlink forwarding IE). When the IE is set to the first value, it means that the source node requests to forward the corresponding multicast service data.
  • the first indication information is a 1-bit indication. If the 1-bit value is “1”, it means that the source node requests to forward the corresponding multicast service data. If the 1-bit value is “0”, it means that the source node does not Request to forward the corresponding multicast service data.
  • the first indication information is a specific indication. When the specific indication exists, it means that the source node requests to forward the corresponding multicast service data, and when the specific indication does not exist, it means that the source node does not request to forward the corresponding multicast service data.
  • the multicast service identifier may be TMGI;
  • the second indication information indicating that the target node agrees to forward the multicast service data for example, the second indication information is a specific IE, and when the specific IE exists, it means that the target node agrees to the multicast service data forwarding, and the target can be based on the information provided by the IE.
  • the GTP-U sequence number performs data forwarding. When the specific IE does not exist, it means that the target node does not agree with the multicast service data forwarding.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • Configuration information of public resources used for multicast data transmission in multicast mode where the configuration information of the public resources may be scheduling information when the target node sends the multicast service in multicast mode, for example, the corresponding multicast service Scheduling information G-RNTI (this G-RNTI is different from the above-mentioned temporary G-RNTI).
  • the source node determines whether to request the forwarding of multicast service data based on the requirements of the multicast service. For example, if a certain multicast service has a higher quality of service (such as higher reliability), the source node carries the request in the handover request. Forward the first indication information of the multicast service data. Otherwise, the first indication information is not carried.
  • the method further includes:
  • the handover command message carries at least one of the following information:
  • Multicast service identifier the multicast service identifier may be TMGI.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • the configuration information of the public resource may be the scheduling information when the target node sends the multicast service in a multicast manner, for example, the scheduling information G-RNTI corresponding to a certain multicast service (the G-RNTI is different from the aforementioned temporary G-RNTI). ).
  • the method further includes:
  • the method further includes:
  • the source node When the first timer expires, the source node does not receive the stop data forwarding instruction sent by the target node, and stops data packet forwarding.
  • the source node maintains a timer (the first timer). When the timer expires, if it does not receive an instruction to stop data forwarding from the target node, the source node automatically stops data forwarding.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing The amount of data lost by the terminal during the handover process can further meet the service requirements of the multicast service, so as to solve the problem of data loss caused by the terminal during the handover process.
  • the execution subject may be a data retransmission device, or a control module in the data retransmission device for executing the loaded data retransmission method.
  • the data retransmission method performed by the data retransmission device is taken as an example to illustrate the data retransmission method provided in the embodiment of the present application.
  • an embodiment of the present application also provides a data retransmission method, which is applied to a terminal, and includes:
  • Step 301 After the terminal switches to the target node, receive a data packet retransmitted by the target node according to the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number;
  • the source PDCP sequence number of the data packet is the PDCP sequence number allocated by the source node to the data packet.
  • the GPRS Tunnelling Protocol user plane sequence number (GPRS Tunnelling Protocol user plane sequence number, GTP-U sequence number, may also be referred to as GTP-U SN).
  • Packet Data Convergence Protocol Sequence Number (Packet Data Convergence Protocol Sequence Number, PDCP sequence number, also called PDCP SN).
  • the terminal maintains two sets of protocol stacks, corresponding to the source MRB (first protocol stack) and target MBR (second protocol stack) respectively.
  • the data received by the terminal based on the data retransmission configuration corresponds to the protocol stack of the source MRB
  • the data received based on the common resource configuration of the target cell corresponds to the protocol stack of the target MRB.
  • the terminal receives C-RNTI or temporary G-RNTI or G-RNTI data transmitted through a specific HARQ process
  • the data is submitted to the protocol stack corresponding to the source MRB.
  • the terminal receives the data through the public HARQ process through G-RNTI
  • the common resource configuration information sent by the target cell to send multicast service data in a multicast manner may be carried in a handover command, or it may be obtained by the terminal handing over to the target cell by reading the system information of the target cell. , It can also be sent by the target cell to the terminal through dedicated signaling.
  • step 301 includes:
  • the data packet retransmitted by the target node is received.
  • the method also includes:
  • the terminal can maintain two sets of protocol stacks, namely the first protocol stack based on the source node and the second protocol stack based on the target node. It can simultaneously receive the retransmitted data sent by the target node and the target node can send it by multicast.
  • the multicast business data In order to ensure that the data submitted by the terminal to the higher layer (such as the application layer) is in order, the terminal needs to buffer the received data sent by the target node in multicast mode first, and the retransmission ends when the terminal receives the data sent by the target node After the data of the first protocol stack is delivered to the upper layer, the cached data sent by the target node in multicast mode can be delivered to the upper layer.
  • the data received by the terminal based on the first protocol stack and the second protocol stack may have duplicate data, and the application layer of the terminal may perform repetitive detection to discard or eliminate duplicate data.
  • the terminal can maintain two sets of protocol stacks, namely the first protocol stack based on the source node and the second protocol stack based on the target node. After the terminal receives the data retransmission end instruction sent by the target node and submits the data of the first protocol stack to the higher layer, it can start to receive the data sent by the target node in a multicast manner based on the second protocol stack.
  • step 301 includes:
  • the data packet retransmitted by the target node is received.
  • terminal-specific scheduling resources can be radio resources scheduled through terminal-specific scheduling (such as terminal C-RNTI); temporary scheduling resources can be through temporary scheduling (such as temporary G-RNTI allocated to the terminal by the target node, that is, the difference
  • the target node uses the multicast mode to transmit the scheduling information of the multicast service, such as G-RNTI) to schedule the radio resources.
  • the method further includes:
  • the handover command message carries at least one of the following information:
  • Multicast service identifier the multicast service identifier may be TMGI.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • the configuration information of the public resource may be the scheduling information when the target node sends the multicast service in a multicast manner, for example, the scheduling information G-RNTI corresponding to a certain multicast service (the G-RNTI is different from the aforementioned temporary G-RNTI). ).
  • the method further includes at least one of the following:
  • the re-establishment behavior includes processing the data in the buffer of the receiving RLC entity and submitting it to a higher layer (such as a PDCP entity, this behavior Applicable to RLC configuration with reordering function), and to initialize the receiving window of the receiving RLC entity;
  • a higher layer such as a PDCP entity, this behavior Applicable to RLC configuration with reordering function
  • Trigger status report feedback the status report is used to indicate the receiving status of the data packet on the terminal side; if the handover command indicates that the network side (such as the target node) will retransmit a certain multicast service, the terminal feeds back downlink data to the network side The receiving status (such as PDCP status report).
  • the receiving PDCP entity and RLC entity corresponding to the multicast mode of the multicast service refer to the protocol stack entity used when the terminal receives the multicast service sent by the source node in the multicast mode.
  • the receiving PDCP entity and RLC entity corresponding to the source node are the protocol stack entities used by the terminal when the source node receives the source node to send data in a multicast manner.
  • the terminal uses the protocol stack entity to receive the retransmission sent by the target node. Transfer data.
  • the terminal can immediately submit the data of the protocol stack entity to the higher layer (such as understanding the release of PDCP, RLC entities), or wait for the timer maintained by the protocol stack entity After the timeout, the data of the protocol stack entity is delivered to the higher layer.
  • the receiving PDCP entity and RLC entity corresponding to the target node are protocol stack entities used when the terminal receives the target node to send data in a multicast manner when the terminal is at the target node.
  • the method further includes:
  • the method further includes:
  • the network side configures the terminal with temporary scheduling resources (such as temporary G-RNTI), when the terminal receives the data retransmission end indication sent by the target node, it can be understood that the target node may not use the temporary scheduling in the future.
  • temporary scheduling resources such as temporary G-RNTI
  • the terminal can stop monitoring the temporary scheduling resource, or when the terminal decides or starts to deliver the first protocol stack data to the higher layer, it stops monitoring the temporary scheduling resource.
  • the method further includes at least one of the following:
  • the releasing behavior includes processing the data in the buffer of the receiving PDCP entity and submitting it to a higher layer, and releasing the receiving PDCP entity;
  • the release behavior includes processing the data in the buffer of the receiving RLC entity and submitting it to a higher layer (such as a PDCP entity, this behavior is applicable to RLC) Configured with reordering function), and the receiving RLC entity will be released;
  • the method further includes:
  • the receiving status indication information of the terminal to the data packet sent by the source node is used to indicate the source PDCP sequence number of at least one first data packet; the first data packet is the processing node Data packets not received by the terminal before switching.
  • the terminal actively reports the PDCP status report to the target node when or after establishing a connection with the target node, so that the target node can learn the receiving status indication information of the terminal; or the target node requests or the source node instructs the terminal to report PDCP to the target node Status report to obtain the receiving status indication information of the terminal.
  • the target node is based on the PDCP status report.
  • the mapping relationship between GTP-U SN and PDCP SN is obtained from the source node, it can be determined that the data packet corresponding to GTP-U SN is not received by the terminal, and the data that has not been received can be retransmitted.
  • step 301 includes:
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing The amount of data lost by the terminal during the handover process can further meet the service requirements of the multicast service, so as to solve the problem of data loss caused by the terminal during the handover process.
  • the execution subject may be a data retransmission device, or a control module in the data retransmission device for executing the loaded data retransmission method.
  • the data retransmission method performed by the data retransmission device is taken as an example to illustrate the data retransmission method provided in the embodiment of the present application.
  • the data retransmission method includes the following steps:
  • Step 1 The source node sends a handover request message to the target node, and the handover request message carries multicast related information.
  • the multicast service information includes one or more of the following contents:
  • the multicast service identifier can be TMGI or the sequence number of the multicast service (for example, the source node obtains the list of multicast services that the target node can support through the Xn interface establishment process, and the source node can use the multicast service list in the list).
  • the serial number of the broadcast service indicates the corresponding multicast service).
  • the first indication information that instructs the source node to request the forwarding of multicast service data is DL forwarding IE (downlink forwarding IE).
  • the first indication information is a 1-bit indication. If the 1-bit value is “1”, it means that the source node requests to forward the corresponding multicast service data. If the 1-bit value is “0”, it means that the source node does not Request to forward the corresponding multicast service data.
  • the first indication information is a specific indication. When the specific indication exists, it means that the source node requests to forward the corresponding multicast service data, and when the specific indication does not exist, it means that the source node does not request to forward the corresponding multicast service data.
  • the target node sends a handover response message to the source node, where the handover response message carries information related to the multicast service.
  • the multicast service related information includes one or more of the following:
  • the multicast service identifier may be TMGI;
  • the second indication information indicating that the target node agrees to forward the multicast service data for example, the second indication information is a specific IE, and when the specific IE exists, it means that the target node agrees to the multicast service data forwarding, and the target can be based on the information provided by the IE.
  • the GTP-U sequence number performs data forwarding. When the specific IE does not exist, it means that the target node does not agree with the multicast service data forwarding.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • the configuration information of the public resource may be the scheduling information when the target node sends the multicast service in a multicast manner, for example, the scheduling information G-RNTI corresponding to a certain multicast service (the G-RNTI is different from the aforementioned temporary G-RNTI). ).
  • Step 3 The source node sends status indication information to the target node.
  • the status indication information is used to display the mapping relationship between the GTP-U sequence numbers of the N data packets and the source PDCP sequence numbers.
  • the status indication information includes the following information: At least one:
  • the GTP-U sequence number and the source PDCP sequence number of the source node When the source node decides to switch the terminal to the target node, the GTP-U sequence number and the source PDCP sequence number of the source node’s first data packet to be sent; for example, the source node is the first to switch the terminal to the target node.
  • the timing for the source node to initiate the status indication information may be when the source node decides to send a switching command to the terminal, or when the source node sends a switching command to the terminal, or after the source node sends a switching command to the terminal, there is no specific limitation here.
  • Step 3.1 the source node forwards data to the target node.
  • the source node forwards data to the target node in sequence (GTP-U SN), and the data may be data cached by the source node and/or new data obtained from a core network node.
  • the source node provides the mapping relationship between the GTP-U SN of the data packet and the source PDCP SN when forwarding data to the target node, where the source PDCP SN is the PDCP sequence number allocated by the source node to the data packet.
  • the data packets corresponding to the status indication information of the source node when the source node is switched from the terminal are sent in order. Or, when the source node switches from the terminal, the next data packet corresponding to the state indication information of the source node starts to be sent in sequence.
  • step 3 and step 3.1 can be independent processes or a combined process.
  • Step 4 The source node sends a handover command message to the terminal, and the handover command message carries information related to the multicast service.
  • the information related to the multicast service includes at least one of the following:
  • Multicast service identifier the multicast service identifier may be TMGI.
  • the first retransmission indication information that indicates whether the target node performs data retransmission; for example, the first retransmission indication information is 1-bit indication information, and when the 1-bit indication information takes the value "1", it means that the target node will perform data retransmission.
  • the target node schedules multicast service data through the C-RNTI of the terminal; when the 1-bit indication information takes a value of "0", it means that the target node will not retransmit data.
  • the target node can schedule multiple data through the terminal’s C-RNTI.
  • the second retransmission indication information is temporary multicast data scheduling information (such as temporary G-RNTI), when the indication exists, it means that the target node schedules multicast data through the temporary G-RNTI.
  • Hybrid automatic repeat request HARQ process information for data retransmission for example, when the terminal switches to the target node, the target node retransmits the multicast data through a specific HARQ process.
  • Configuration information of public resources used for multicast data transmission in the multicast mode wherein the configuration information of the public resources may be scheduling information when the target node sends the multicast service in multicast mode, for example, a certain multicast service corresponds to The scheduling information G-RNTI.
  • Step 5 The terminal receives the handover command message sent by the source node, where the handover command message carries information related to the multicast service.
  • the terminal initiates a connection establishment process with the target node.
  • the behavior of the terminal also includes one or more of the following:
  • Trigger status report feedback and the status report is used to indicate the receiving status of the data packet on the terminal side.
  • Step 6 the target node performs data retransmission, and the resource for the data retransmission is to schedule radio resources through terminal-specific scheduling (such as C-RNTI) or temporary scheduling (such as temporary G-RNTI).
  • the terminal maintains two sets of protocol stacks, respectively corresponding to the source MRB (first protocol stack) and target MBR (second protocol stack).
  • the data received by the terminal based on the data retransmission configuration corresponds to the protocol stack of the source MRB
  • the data received based on the common resource configuration of the target cell corresponds to the protocol stack of the target MRB.
  • the terminal receives C-RNTI or temporary G-RNTI or G-RNTI data transmitted through a specific HARQ process
  • the data is submitted to the protocol stack corresponding to the source MRB.
  • the terminal receives the data through the public HARQ process through G-RNTI
  • Step 7 The target node instructs the source node to stop data forwarding.
  • the target node decides when to instruct the source node to stop data forwarding based on the following information:
  • step 7 may be before or after step 8.
  • the source node maintains a timer, and when the timer expires, if it does not receive an instruction to stop data forwarding from the target node, the source node automatically stops data forwarding.
  • Step 8 The target node sends to the terminal third indication information indicating that the data retransmission of the target node ends.
  • the behavior of the terminal further includes one or more of the following:
  • the receiving PDCP entity and RLC entity corresponding to the source node are the protocol stack entities used when the terminal receives the source node to send data in multicast mode when the terminal is at the source node.
  • the terminal uses the protocol stack entity to receive Retransmitted data sent by the target node.
  • the terminal can immediately submit the data of the protocol stack entity to the higher layer (such as understanding the release of PDCP, RLC entities), or wait for the timer maintained by the protocol stack entity After the timeout, the data of the protocol stack entity is delivered to the higher layer.
  • the receiving PDCP entity and the RLC entity corresponding to the target node are the protocol stack entities used when the terminal receives the target node to send data in a multicast manner when the terminal is at the target node.
  • the UE stops monitoring the temporary G-RNTI.
  • the network side configures a temporary scheduling resource (such as temporary G-RNTI) for the UE, when the terminal receives the data retransmission end indication sent by the target node, it can be understood that the target node may not use the temporary scheduling resource in the future.
  • the terminal can stop monitoring the temporary scheduling resource, or when the terminal decides or starts to deliver the first protocol stack data to the higher layer, it stops monitoring the temporary scheduling resource.
  • an embodiment of the present application also provides a data retransmission device 500, which is applied to a target node, and includes:
  • the relationship acquisition module 501 is configured to acquire the mapping relationship between the GTP-U sequence numbers of the N data packets sent by the source node and the source PDCP sequence numbers respectively allocated by the source node for the N data packets; N is greater than or equal to 1 Integer
  • the data retransmission module 502 is configured to perform data retransmission according to the mapping relationship.
  • the device further includes:
  • the information acquisition module is configured to acquire the receiving status indication information of the data packet sent by the source node by the terminal, and the receiving status indication information is used to indicate the source PDCP sequence number of at least one first data packet; the first data packet Data packets not received by the terminal before the node switching;
  • the data retransmission module includes:
  • the first data retransmission submodule is configured to perform data transmission according to the source PDCP sequence number of the at least one first data packet and the mapping relationship.
  • the first data retransmission submodule includes:
  • the first data retransmission unit is configured to perform data retransmission starting from the first data packet with the smallest PDCP sequence number in the at least one first data packet according to the mapping relationship.
  • the relationship acquisition module includes:
  • the relationship acquisition submodule is configured to receive status indication information sent by the source node, where the status indication information includes at least one of the following information:
  • the device further includes:
  • the data receiving module is configured to receive data packets forwarded by the source node in the order of the GTP-U sequence numbers of the N data packets.
  • the data receiving module includes:
  • a data receiving submodule configured to receive data packets forwarded by the source node in the order of GTP-U sequence numbers starting from the second data packet;
  • the second data packet is the next data packet that is being sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet to be sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet that the terminal did not receive before the handover.
  • the data retransmission module includes:
  • the second data retransmission sub-module is configured to, according to the mapping relationship, start data retransmission in sequence after the next data packet of the data packet being sent by the source node when the terminal is switched to the target node;
  • the first data packet to be sent of the source node when switching from the terminal to the target node is used to sequentially retransmit data.
  • the device further includes:
  • the request receiving module is configured to receive a handover request message sent by the source node, where the handover request message carries at least one of a multicast service identifier and first indication information that instructs the source node to request the forwarding of multicast service data;
  • the response sending module is configured to send a handover response message to the source node, and the handover response message carries at least one of the following information:
  • Second indication information indicating that the target node agrees to forward the multicast service data
  • First retransmission indication information indicating whether the target node performs data retransmission
  • Second retransmission indication information indicating the resource for the target node to perform data retransmission
  • the device further includes:
  • the second connection module is configured to establish a connection with the terminal that receives the handover command message sent by the source node; the handover command message carries at least one of the following information:
  • First retransmission indication information indicating whether the target node performs data retransmission
  • Second retransmission indication information indicating the resource for the target node to perform data retransmission
  • the device further includes:
  • the instruction sending module is configured to send an instruction to stop data forwarding to the source node according to the buffered data state of the target node.
  • the device further includes:
  • the third sending module is configured to send third indication information to the terminal, where the third indication information is used to indicate the end of the data retransmission of the target node.
  • the data retransmission device provided by the embodiment of the present application can implement each process implemented by the data retransmission device in the method embodiment of FIG. 1. To avoid repetition, details are not repeated here.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing the terminal handover
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • an embodiment of the present application further provides a communication device, the communication device being a target node, including a processor, a memory, a program or instruction stored in the memory and running on the processor, the program or instruction When executed by a processor, each process of the foregoing data retransmission method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • an embodiment of the present application also provides a data retransmission device 600, which is applied to a source node, and includes:
  • the relationship sending module 601 is configured to send a mapping relationship between the GTP-U sequence numbers of N data packets and the source PDCP sequence numbers respectively allocated by the source node for the N data packets to the target node; N is an integer greater than or equal to 1 .
  • the relationship sending module includes:
  • the relationship sending submodule is used to send status indication information to the target node, where the status indication information includes at least one of the following information:
  • the device further includes:
  • the data forwarding module is configured to forward data packets to the target node in the order of the GTP-U sequence numbers of the N data packets.
  • the data forwarding module includes:
  • a data forwarding submodule configured to forward the data packet to the target node in the order of the GTP-U sequence number starting from the second data packet;
  • the second data packet is the next data packet that is being sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet to be sent by the source node when the terminal switches to the target node;
  • the second data packet is the first data packet that the terminal did not receive before the handover.
  • the device further includes:
  • a request sending module configured to send a handover request message to the target node, where the handover request message carries at least one of a multicast service identifier and first indication information that instructs the source node to request the forwarding of the multicast service data;
  • the response receiving module is configured to receive a handover response message sent by the target node, where the handover response message carries at least one of the following information:
  • Second indication information indicating that the target node agrees to forward the multicast service data
  • First retransmission indication information indicating whether the target node performs data retransmission
  • Second retransmission indication information indicating the resource for the target node to perform data retransmission
  • the device further includes:
  • the command sending module is configured to send a handover command message to the terminal, where the handover command message carries at least one of the following information:
  • First retransmission indication information indicating whether the target node performs data retransmission
  • Second retransmission indication information indicating the resource for the target node to perform data retransmission
  • the device further includes:
  • the stop module is used to receive the stop data forwarding instruction sent by the target node, and stop the data packet forwarding;
  • the source node does not receive the stop data forwarding instruction sent by the target node, and stops the data packet forwarding.
  • the data retransmission device provided in the embodiment of the present application can implement each process implemented by the data retransmission device in the method embodiment of FIG. 2. In order to avoid repetition, details are not repeated here.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number to reduce the terminal handover.
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • an embodiment of the present application further provides a communication device, which is a source node and includes a processor, a memory, a program or instruction stored on the memory and running on the processor, the program or instruction When executed by a processor, each process of the foregoing data retransmission method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • an embodiment of the present application also provides a data retransmission device 700, which is applied to a terminal, and includes:
  • the retransmission receiving module 701 is configured to receive a data packet retransmitted by the target node according to the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number after the terminal switches to the target node;
  • the source PDCP sequence number of the data packet is the PDCP sequence number allocated by the source node to the data packet.
  • the retransmission receiving module includes:
  • the first submodule is configured to receive the data packet retransmitted by the target node based on the first protocol stack of the source node.
  • the retransmission receiving module includes:
  • the retransmission receiving sub-module is configured to receive the data packet retransmitted by the target node according to terminal dedicated resources or temporary scheduling resources.
  • the device further includes:
  • the command receiving module is used to receive the handover command message sent by the source node
  • the first connection module is configured to establish a connection with the target node according to the handover command message; wherein, the handover command message carries at least one of the following information:
  • First retransmission indication information indicating whether the target node performs data retransmission
  • Second retransmission indication information indicating the resource for the target node to perform data retransmission
  • the device further includes at least one of the following modules:
  • the first retention module is configured to keep the multicast service indicated by the handover command message and the receiving PDCP entity corresponding to the source node unchanged;
  • the first reconstruction module is configured to reconstruct the receiving radio link control RLC entity corresponding to the multicast mode of the multicast service indicated by the handover command message;
  • the first feedback module is used to trigger status report feedback, and the status report is used to indicate the receiving status of the data packet on the terminal side.
  • the device further includes:
  • the stop instruction receiving module is configured to receive third instruction information sent by the target node, where the third instruction information is used to indicate the end of data retransmission of the target node.
  • the device further includes:
  • the fourth receiving module is configured to receive the multicast service data sent by the target node based on the second protocol stack of the target node.
  • the device further includes at least one of the following modules:
  • a first release module configured to release the multicast service indicated by the handover command message and the receiving PDCP entity corresponding to the source node;
  • a second release module configured to release the multicast service indicated by the handover command message and the receiving RLC entity corresponding to the source node
  • the first indication module is used to indicate that the multicast service indicated by the handover command message and the receiving PDCP entity corresponding to the target node can deliver data to the upper layer in order;
  • the second indication module is used to indicate that the multicast service indicated by the handover command message and the receiving RLC entity corresponding to the target node can deliver data to the upper layer in order.
  • the data retransmission device provided in the embodiment of the present application can implement each process implemented by the data retransmission device in the method embodiment of FIG. 3. To avoid repetition, details are not repeated here.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing the terminal handover
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • an embodiment of the present application further provides a communication device.
  • the communication device is a terminal, including a processor, a memory, a program or instruction stored in the memory and running on the processor, and the program or instruction is When the processor executes, each process of the foregoing data retransmission method embodiment is realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the data retransmission device in the embodiment of the present application may be a device, or a component, integrated circuit, or chip in a terminal.
  • the device can be a mobile electronic device or a non-mobile electronic device.
  • the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a handheld computer, a vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (personal digital assistant). assistant, PDA), etc.
  • Non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PC), televisions (television, TV), teller machines or self-service machines, etc., this application The embodiments are not specifically limited.
  • the data retransmission device in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.
  • FIG. 8 is a structural diagram of a network side device (a target node or a source node) according to an embodiment of the present application, which can realize the details of the above-mentioned information receiving method and achieve the same effect.
  • the network side device 1300 includes: a processor 1301, a transceiver 1302, a memory 1303, and a bus interface, where:
  • the processor 1301 is configured to read a program in the memory 1303 and execute the following process:
  • N is an integer greater than or equal to 1;
  • mapping relationship data retransmission is performed.
  • the processor 1301 is configured to read a program in the memory 1303, and execute the following process:
  • N is an integer greater than or equal to 1.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing the terminal handover
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 1301 and various circuits of the memory represented by the memory 1303 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, will not be further described herein.
  • the bus interface provides the interface.
  • the transceiver 1302 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • FIG. 9 is a schematic diagram of the hardware structure of an electronic device that implements each embodiment of the present application.
  • the electronic device 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, a processor 910, etc. part.
  • the electronic device 900 may also include a power source (such as a battery) for supplying power to various components.
  • the power source may be logically connected to the processor 910 through a power management system, so that the power management system can manage charging, discharging, and power management. Consumption management and other functions.
  • the structure of the electronic device shown in FIG. 9 does not constitute a limitation on the electronic device.
  • the electronic device may include more or fewer components than those shown in the figure, or some components may be combined, or different component arrangements, which will not be repeated here. .
  • the radio frequency unit 901 (write if there is one) is used to receive the data retransmitted by the target node according to the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number after the terminal is switched to the target node Bag;
  • the source PDCP sequence number of the data packet is the PDCP sequence number allocated by the source node to the data packet.
  • the target node when the terminal is handed over from the multicast cell to the multicast cell, the target node performs data retransmission based on the mapping relationship between the GTP-U sequence number of the data packet and the source PDCP sequence number, reducing the terminal handover
  • the amount of data lost during the process can further meet the business requirements of the multicast service, so as to solve the problem of data loss caused by the terminal in the handover process.
  • the radio frequency unit 901 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the base station, it is processed by the processor 910; Uplink data is sent to the base station.
  • the radio frequency unit 901 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 901 can also communicate with the network and other devices through a wireless communication system.
  • the electronic device provides users with wireless broadband Internet access through the network module 902, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 903 can convert the audio data received by the radio frequency unit 901 or the network module 902 or stored in the memory 909 into an audio signal and output it as sound. Moreover, the audio output unit 903 may also provide audio output related to a specific function performed by the electronic device 900 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 903 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 904 is used to receive audio or video signals.
  • the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042.
  • the graphics processor 9041 is configured to provide an image of a still picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed.
  • the processed image frame may be displayed on the display unit 906.
  • the image frames processed by the graphics processor 9041 may be stored in the memory 909 (or other storage medium) or sent via the radio frequency unit 901 or the network module 902.
  • the microphone 9042 can receive sound and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 901 for output in the case of a telephone call mode.
  • the electronic device 900 further includes at least one sensor 905, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 9061 according to the brightness of the ambient light.
  • the proximity sensor can close the display panel 9061 and the display panel 9061 when the electronic device 900 is moved to the ear. / Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes), and can detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of electronic devices (such as horizontal and vertical screen switching, related games) , Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; sensor 905 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, Infrared sensors, etc., will not be repeated here.
  • the display unit 906 is used to display information input by the user or information provided to the user.
  • the display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 907 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the electronic device.
  • the user input unit 907 includes a touch panel 9071 and other input devices 9072.
  • the touch panel 9071 also called a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 9071 or near the touch panel 9071. operate).
  • the touch panel 9071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 910, the command sent by the processor 910 is received and executed.
  • the touch panel 9071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 907 may also include other input devices 9072.
  • other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 9071 can cover the display panel 9061.
  • the touch panel 9071 detects a touch operation on or near it, it transmits it to the processor 910 to determine the type of the touch event, and then the processor 910 determines the type of touch event according to the touch.
  • the type of event provides corresponding visual output on the display panel 9061.
  • the touch panel 9071 and the display panel 9061 are used as two independent components to implement the input and output functions of the electronic device, in some embodiments, the touch panel 9071 and the display panel 9061 can be integrated
  • the implementation of the input and output functions of the electronic device is not specifically limited here.
  • the interface unit 908 is an interface for connecting an external device and the electronic device 900.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 908 can be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the electronic device 900 or can be used to connect the electronic device 900 to an external device. Transfer data between devices.
  • the memory 909 can be used to store software programs and various data.
  • the memory 909 may mainly include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc.
  • the memory 909 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 910 is the control center of the electronic device, which uses various interfaces and lines to connect the various parts of the entire electronic device, runs or executes software programs and/or modules stored in the memory 909, and calls data stored in the memory 909 , Perform various functions of electronic equipment and process data, so as to monitor the electronic equipment as a whole.
  • the processor 910 may include one or more processing units; preferably, the processor 910 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem The processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 910.
  • the electronic device 900 may also include a power source (such as a battery) for supplying power to various components.
  • a power source such as a battery
  • the power source may be logically connected to the processor 910 through a power management system, so that functions such as charging, discharging, and power management can be managed through the power management system. .
  • the electronic device 900 includes some functional modules that are not shown, which will not be repeated here.
  • the embodiment of the present application also provides a readable storage medium with a program or instruction stored on the readable storage medium.
  • the program or instruction is executed by a processor, each process of the foregoing data retransmission method embodiment is realized, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.
  • the processor is the processor in the electronic device described in the foregoing embodiment.
  • the readable storage medium includes a computer readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk.
  • An embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the foregoing data retransmission method embodiment
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a program or an instruction to implement the foregoing data retransmission method embodiment
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • An embodiment of the present application also provides an electronic device configured to perform each process of the foregoing data retransmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a data retransmission device configured to perform each process of the foregoing data retransmission method embodiment, and can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the embodiments of the present application also provide a computer program product.
  • the computer program product is executed by at least one processor to perform each process of the above-mentioned data retransmission method embodiment, and can achieve the same technical effect. In order to avoid repetition, it will not be repeated here. Go into details.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.
  • a terminal which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Abstract

本申请公开了一种数据重传方法、装置、目标节点、源节点及终端，该方法包括：获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；根据所述映射关系，进行数据重传。

Description

数据重传方法、装置、目标节点、源节点及终端
相关申请的交叉引用
本申请主张在2020年4月30日在中国提交的中国专利申请号No.202010367115.X的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种数据重传方法、装置、目标节点、源节点及终端。
背景技术
多媒体广播多播业务(Multimedia Broadcast and Multicast Service，MBMS)或广播多播业务(Multicast Broadcast Service，MBS)具体以下2种发送方式：
MBMS/MBS发送方式1：通过在MBMS单频网(Multimedia Broadcast multicast service Single Frequency Network，MBSFN)子帧中通过物理多播信道(Physical Multicast Channel，PMCH)发送。其中，控制信息通过系统信息(如系统信息块SIB13)和广播控制信道(Multicast Control Channel，MCCH)发送，数据通过广播业务信道(Multicast Traffic Channel，MTCH)发送。
MBMS/MBS发送方式2：通过物理下行控制信道(Physical Downlink Control Channel，PDCCH)调度的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)发送。其中，控制信息通过系统信息(如系统信息块SIB20)和单小区广播控制信道(Single Cell Multicast Control Channel，SC-MCCH)发送，数据通过单小区广播业务信道(Single Cell Multicast Traffic Channel，SC-MTCH)发送。其中，SC-MCCH通过单小区无线网络临时标识(Single Cell Radio Network Temporary Identity，SC-RNTI)PDCCH调度的PDSCH发送，SC-MTCH通过组无线网络临时标识(Group Radio Network Temporary Identity，G-RNTI)PDCCH调度的PDSCH发送。
MBS业务是通过特定的MBMS无线承载(MBMS Radio Bearer，MRB)进行发送的。MBS业务可以通过以下标识标记：
临时移动组标识(Temporary Mobile Group Identity，TMGI)；
服务质量流标识(QoS flow ID)。
当终端从一个以多播方式提供多播业务的小区切换到另一个以多播方式提供业务的小区时，由于切换和/或两个小区的数据发送不同步可能导致终端丢失部分数据，为最小化终端丢失数据。例如，源节点和目标节点的数据发送不同步(比如目标节点后进入多播组)，终端在源节点接收到了GTP-U SN(数据包标识)＝1,2的数据包，切换到目标节点时，目标节点正在发送GTP-U SN＝6的数据包，则终端在切换过程中丢失了GTP-U SN＝3,4,5的数据包。
发明内容
本申请实施例的目的是提供一种数据重传方法、装置、目标节点、源节点及终端，能够解决终端在多播业务的小区间进行切换时，由于切换和/或两个小区的数据发送不同步可能导致终端丢失部分数据的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，本申请实施例提供了一种数据重传方法，应用于目标节点，包括：
获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
根据所述映射关系，进行数据重传。
第二方面，本申请实施例提供了一种数据重传方法，应用于源节点，包括：
向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
第三方面，本申请实施例提供了一种数据重传方法，应用于终端，包括：
在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
第四方面，本申请实施例提供了一种数据重传装置，应用于目标节点， 包括：
关系获取模块，用于获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
数据重传模块，用于根据所述映射关系，进行数据重传。
第五方面，本申请实施例提供了一种数据重传装置，应用于源节点，包括：
关系发送模块，用于向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
第六方面，本申请实施例提供了一种数据重传装置，应用于终端，包括：
重传接收模块，用于在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
第七方面，本申请实施例提供了一种通信设备，该通信设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面或第二方面或第三方面所述的方法的步骤。
第八方面，本申请实施例提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面或第二方面或第三方面所述的方法的步骤。
第九方面，本申请实施例提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面或第二方面或第三方面所述的方法。
第十方面，本申请实施例还提供了一种电子设备，被配置成用于执行如第一方面或第二方面或第三方面所述的方法。
第十一方面，本申请实施例还提供了一种数据重传装置，被配置成用于执行如第一方面或第二方面或第三方面所述的方法。
第十二方面，本申请实施例还提供了一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如第一方面或第二方面或第三方面所述的方法。
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
附图说明
图1表示本申请实施例提供的数据重传方法的步骤流程图之一；
图2表示本申请实施例提供的数据重传方法的步骤流程图之二；
图3表示本申请实施例提供的数据重传方法的步骤流程图之三；
图4表示本申请实施例提供的数据重传方法的示例的交互示意图；
图5表示本申请实施例提供的数据重传装置的结构示意图之一；
图6表示本申请实施例提供的数据重传装置的结构示意图之二；
图7表示本申请实施例提供的数据重传装置的结构示意图之三；
图8表示本申请实施例提供的网络侧设备的结构示意图；
图9表示本申请实施例提供的终端的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”，一般表示前后关联对象是一种“或”的关 系。
下面结合附图介绍本申请的实施例。本申请实施例提供的数据重传方法、装置、目标节点、源节点及终端可以应用于无线通信系统中。该无线通信系统可以为采用5G系统，或者演进型长期演进(Evolved Long Term Evolution，eLTE)系统，或者后续演进通信系统。
本申请实施例提供的终端可以为手机、平板电脑、笔记本电脑、超级移动个人计算机(Ultra-Mobile Personal Computer，UMPC)、上网本、可穿戴式设备(Wearable Device)、车载设备或者个人数字助理(Personal Digital Assistant，PDA)等。需要说明的是，在本申请实施例中并不限定终端的具体类型。本申请实施例中以LTE以及NR系统为例，然不限于此系统，本申请提供的技术方案可以应用于存在相同问题的其他系统。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的数据重传方法、装置、目标节点、源节点及终端进行详细地说明
如图1所示，本申请实施例提供了一种数据重传方法，应用于目标节点，包括：
步骤101，获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；其中，GPRS隧道协议用户面序列号(GPRS Tunnelling Protocol user plane sequence number，GTP-U序列号，也可称为GTP-U SN)，。分组数据汇聚协议序列号(Packet Data Convergence Protocol Sequence Number，PDCP序列号，也可称为PDCP SN)。
步骤102，根据所述映射关系，进行数据重传。
本申请实施例中，源节点和目标节点均为采用多播模式进行多播传输的网络节点，终端从源节点切换至目标节点的过程中易导致数据丢失；本申请中由目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
作为本申请的一个可选实施例，步骤102包括：
根据所述映射关系，通过终端专用调度资源或临时调度资源进行数据重 传。
其中，终端专用调度资源可以为通过终端专用调度(如终端的C-RNTI)来调度的无线资源；临时调度资源可以为通过临时调度(如目标节点分配给终端的临时G-RNTI，也就是区别于目标节点使用多播方式传输所述多播业务的调度信息，比如G-RNTI)来调度的无线资源。
目标节点基于从源节点获取到的GTP-U序列号和源PDCP序列号的映射关系进行数据传输。例如，源节点指示的其中一对GTP-U SN＝5和源PDCP SN＝5，源节点对该数据包分配的PDCP SN＝5，则目标节点重用该PDCP SN＝5对GTP-U SN＝5的数据进行重传。另一种情况，源节点指示一对GTP-U SN＝6和PDCP SN＝None，源节点还没有对该数据包分配PDCP SN，则目标节点需要按序依次编号，比如PDCP SN＝6，则目标节点使用该PDCP SN＝6对GTP-U SN＝6的数据进行重传。
作为一个可选实施例，步骤102之前，所述方法还包括：
获取所述终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包。
例如，终端在与目标节点建立连接时或之后及时主动向目标节点上报PDCP状态报告，从而使得目标节点能够获知终端的接收状态指示信息；或者，目标节点请求或源节点指示终端向目标节点上报PDCP状态报告，从而获得终端的接收状态指示信息。
需要说明的是，所述PDCP状态报告用于指示终端侧接收状态，如用于指示PDCP SN＝1的包接收到了，PDCP SN＝2的包没有接收到等，目标节点基于所述PDCP状态报告以及从源节点获取到GTP-U SN和PDCP SN的映射关系，可以确定GTP-U SN对应的数据包是终端没有接收到的，进而可以对没有接收到的数据进行重传。
相应的，步骤102包括：
根据所述至少一个第一数据包的源PDCP序列号以及所述映射关系，进行数据传输。
其中，所述根据所述至少一个第一数据包的源PDCP序列号以及所述映 射关系，进行数据传输，包括：
根据所述映射关系，从所述至少一个第一数据包中PDCP序列号最小的第一数据包开始进行数据重传。
例如，终端上报的第一数据包的源PDCP序列号为3和4，目标节点根据映射关系，查找源PDCP序列＝3的数据包的GTP-U序列号，并从GTP-U序列号对应的数据包开始按序进行数据重传。
可选的，本申请上述实施例中，步骤101包括：
接收所述源节点发送的状态指示信息，所述状态指示信息包括下述信息的至少一项：
源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点将终端切换到目标节点时源节点正在发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配的PDCP层编号为PDCP SN＝5。
源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点决定将终端切换到目标节点时源节点第一个待发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配或将为其分配的PDCP层编号为PDCP SN＝5。
在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号；源节点可以基于终端发送的PDCP状态报告确定在切换之前没有被终端接收的数据包的GTP-U SN和PDCP SN。
其中，源节点发起状态指示信息的时机可以是源节点决定向终端发送切换命令时或源节点向终端发送切换命令时或源节点向终端发送切换命令后，在此不做具体限定。
可选地，本申请的至少一个实施例中，步骤102之前，所述方法还包括：
接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的数据包。该转发的数据包可以是源节点缓存的数据和/或从核心网节点获取的新数据。
可选地，源节点向目标节点转发数据包时还可以提供该数据包的GTP-U序列号和源PDCP序列号的映射关系，其中，源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
其中，所述接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的所述N个数据包，包括：
接收所述源节点从第二数据包开始按照GTP-U序列号的顺序转发的数据包；
其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
比如，终端切换时源节点下一个等待发送GTP-U SN＝6(假设该包对应PDCP SN＝6)的数据包，则源节点按照GTP-U SN＝6/PDCP SN＝6开始按序向目标节点转发数据。如果源节点获取到GTP-U SN＝2/PDCP SN＝2的包没有收到(假设其他的数据包都收到了)，则源节点按序向目标节点转发GTP-U SN＝2/PDCP SN＝2、GTP-U SN＝6/PDCP SN＝6的数据包。
相应的，步骤102包括：
根据所述映射关系，从所述终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包开始按序进行数据重传；
或者，
根据所述映射关系，从所述终端切换到目标节点时所述源节点的第一个待发送的数据包按序进行数据重传。
可选的，本申请的至少一个实施例中，步骤101之前，所述方法还包括：
接收所述源节点发送的切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示信息中的至少一项；
其中，该多播业务标识可以是TMGI，或者多播业务序号(比如源节点通过Xn接口建立过程获取到目标节点能够支持的多播业务列表，则源节点可以通过该列表中的多播业务序号指示对应的多播业务)。例如，第一指示信息为DL forwarding IE(下行转发IE)，当该IE设置为第一值时，表示源节点请求转发对应的多播业务数据，当该IE设置为第二值时，表示源节点不请求转发对应的多播业务数据。再例如，第一指示信息为1比特指示，若该1比特 取值为“1”，表示源节点请求转发对应的多播业务数据，若该1比特取值为“0”，表示源节点不请求转发对应的多播业务数据。又例如，第一指示信息为一个特定指示，当该特定指示存在时表示源节点请求转发对应的多播业务数据，当该特定指示不存在时表示源节点不请求转发对应的多播业务数据。
向所述源节点发送切换响应消息，所述切换响应消息中携带以下信息的至少一项：
多播业务标识；所述多播业务标识可以是TMGI；
指示目标节点同意进行多播业务数据转发的第二指示信息；例如该第二指示信息为一个特定IE，当该特定IE存在时表示目标节点同意多播业务数据转发，目标可以基于该IE提供的GTP-U序列号进行数据转发，当该特定IE不存在时表示目标节点不同意多播业务数据转发。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
其中，源节点基于多播业务的需求确定是否请求请求转发多播业务数据，比如，某多播业务的服务质量QoS需求较高(如可靠性较高)，则源节点在切换请求中携带请求转发多播业务数据的第一指示信息。反之，不携带第一指示信息。
作为本申请的又一可选实施例，步骤102之前，所述方法还包括：
与接收到所述源节点发送的切换命令消息的终端建立连接；所述切换命令消息携带以下信息的至少一项：
多播业务标识；所述多播业务标识可以是TMGI。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息。其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
本申请实施例中，若源节点按照N个数据包的GTP-U序列号的顺序转发的数据包，所述方法还包括：
根据所述目标节点的缓存数据状态，向所述源节点发送停止数据转发指示。
例如，源节点向目标节点转发GTP-U SN＝3,4,5，...的数据包，如果目标节点接收到GTP-U SN＝5对应的数据包且其缓存中有GTP-U SN＝5的数据包则指示源节点停止数据转发。或者，如果目标节点接收到GTP-U SN＝5对应的数据包且目标节点的缓存中有GTP-U SN＝6的数据包则指示源节点停止数据转发。
进一步的，步骤102之后，所述方法还包括：
向终端发送第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
综上，在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
如图2所示，本申请实施例还提供一种数据重传方法，应用于源节点，包括：
步骤201，向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
其中，GPRS隧道协议用户面序列号(GPRS Tunnelling Protocol user plane sequence number，GTP-U序列号，也可称为GTP-U SN)。分组数据汇聚协议序列号(Packet Data Convergence Protocol Sequence Number，PDCP序列号，也可称为PDCP SN)。
本申请实施例中，源节点和目标节点均为采用多播模式进行多播传输的网络节点，终端从源节点切换至目标节点的过程中易导致数据丢失；本申请中由目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
需要说明的是，本申请实施例提供的数据重传方法，执行主体可以为数据重传装置，或者该数据重传装置中的用于执行加载数据重传方法的控制模块。本申请实施例中以数据重传装置执行加载数据重传方法为例，说明本申 请实施例提供的数据重传方法。
可选的，本申请上述实施例中，步骤201包括：
向目标节点发送状态指示信息，所述状态指示信息包括下述信息的至少一项：
源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点将终端切换到目标节点时源节点正在发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配的PDCP层编号为PDCP SN＝5。
源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点决定将终端切换到目标节点时源节点第一个待发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配或将为其分配的PDCP层编号为PDCP SN＝5。
在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号；源节点可以基于终端发送的PDCP状态报告确定在切换之前没有被终端接收的数据包的GTP-U SN和PDCP SN。
其中，源节点发起状态指示信息的时机可以是源节点决定向终端发送切换命令时或源节点向终端发送切换命令时或源节点向终端发送切换命令后，在此不做具体限定。
可选地，本申请的至少一个实施例中，所述方法还包括：
按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包。
该转发的数据包可以是源节点缓存的数据和/或从核心网节点获取的新数据。
可选地，源节点向目标节点转发数据包时还可以提供该数据包的GTP-U序列号和源PDCP序列号的映射关系，其中，源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
其中，所述按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包，包括：
从第二数据包开始按照GTP-U序列号的顺序向所述目标节点转发数据包；
其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
比如，终端切换时源节点下一个等待发送GTP-U SN＝6(假设该包对应PDCP SN＝6)的数据包，则源节点按照GTP-U SN＝6/PDCP SN＝6开始按序向目标节点转发数据。如果源节点获取到GTP-U SN＝2/PDCP SN＝2的包没有收到(假设其他的数据包都收到了)，则源节点按序向目标节点转发GTP-U SN＝2/PDCP SN＝2、GTP-U SN＝6/PDCP SN＝6的数据包。
可选的，本申请的至少一个实施例中，步骤201之前，所述方法还包括：
向所述目标节点发送切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示信息中的至少一项；其中，该多播业务标识可以是TMGI，或者多播业务序号(比如源节点通过Xn接口建立过程获取到目标节点能够支持的多播业务列表，则源节点可以通过该列表中的多播业务序号指示对应的多播业务)。例如，第一指示信息为DL forwarding IE(下行转发IE)，当该IE设置为第一值时，表示源节点请求转发对应的多播业务数据，当该IE设置为第二值时，表示源节点不请求转发对应的多播业务数据。再例如，第一指示信息为1比特指示，若该1比特取值为“1”，表示源节点请求转发对应的多播业务数据，若该1比特取值为“0”，表示源节点不请求转发对应的多播业务数据。又例如，第一指示信息为一个特定指示，当该特定指示存在时表示源节点请求转发对应的多播业务数据，当该特定指示不存在时表示源节点不请求转发对应的多播业务数据。
接收所述目标节点发送的切换响应消息，所述切换响应消息中携带以下信息的至少一项：
多播业务标识；所述多播业务标识可以是TMGI；
指示目标节点同意进行多播业务数据转发的第二指示信息；例如该第二指示信息为一个特定IE，当该特定IE存在时表示目标节点同意多播业务数据转发，目标可以基于该IE提供的GTP-U序列号进行数据转发，当该特定 IE不存在时表示目标节点不同意多播业务数据转发。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
其中，源节点基于多播业务的需求确定是否请求请求转发多播业务数据，比如，某多播业务的服务质量QoS需求较高(如可靠性较高)，则源节点在切换请求中携带请求转发多播业务数据的第一指示信息。反之，不携带第一指示信息。
作为本申请的又一可选实施例，所述方法还包括：
向终端发送切换命令消息，所述切换命令消息携带以下信息的至少一项：
多播业务标识；所述多播业务标识可以是TMGI。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息。其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
本申请实施例中，若源节点按照N个数据包的GTP-U序列号的顺序转发的数据包，所述方法还包括：
接收所述目标节点发送的停止数据转发指示，并停止数据包转发；例如，源节点向目标节点转发GTP-U SN＝3,4,5，...的数据包，如果目标节点接收到GTP-U SN＝5对应的数据包且其缓存中有GTP-U SN＝5的数据包则指示源节点停止数据转发。或者，如果目标节点接收到GTP-U SN＝5对应的数据包且目标节点的缓存中有GTP-U SN＝6的数据包则指示源节点停止数据转发。
或者，所述方法还包括：
在第一定时器超时，所述源节点未接收到所述目标节点发送的停止数据转发指示，停止数据包转发。源节点维持一个定时器(第一定时器)，当定时器超时，如果没有从目标节点接收到停止数据转发指示，则源节点自动停止数据转发。
综上，在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
需要说明的是，本申请实施例提供的数据重传方法，执行主体可以为数据重传装置，或者该数据重传装置中的用于执行加载数据重传方法的控制模块。本申请实施例中以数据重传装置执行加载数据重传方法为例，说明本申请实施例提供的数据重传方法。
如图3所示，本申请实施例还提供一种数据重传方法，应用于终端，包括：
步骤301，在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
其中，GPRS隧道协议用户面序列号(GPRS Tunnelling Protocol user plane sequence number，GTP-U序列号，也可称为GTP-U SN)。分组数据汇聚协议序列号(Packet Data Convergence Protocol Sequence Number，PDCP序列号，也可称为PDCP SN)。
终端维护两套协议栈，分别对应源MRB(第一协议栈)和目标MBR(第二协议栈)。终端基于数据重传配置接收的数据对应于源MRB的协议栈，基于目标小区的公共资源配置接收的数据对应于目标MRB的协议栈。(如终端接收到C-RNTI或临时G-RNTI或G-RNTI通过特定HARQ进程传输的数据时，将该数据递交给源MRB对应的协议栈，当终端接收到通过G-RNTI通过公共HARQ进程传输的数据时，将该数据递交给目标MRB对应的协议栈)。
需要说明的是，所述目标小区发送以多播方式发送多播业务数据的公共资源配置信息可以是切换命令中携带的，也可以是终端切换到目标小区通过读取目标小区的系统信息获取的，也可以是目标小区通过专用信令发送给终端的。
可选的，步骤301包括：
基于源节点的第一协议栈，接收所述目标节点重传的数据包。
和/或，
所述方法还包括：
基于目标节点的第二协议栈，接收所述目标节点发送的多播业务的数据。
需要说明的是，终端可以维护两套协议栈，即基于源节点的第一协议栈和基于目标节点的第二协议栈，可同时接收目标节点发送的重传数据以及目标节点通过多播方式发送的多播业务数据。为保证终端向高层(如应用层)递交的数据是按序的，终端需要先将接收到的通过目标节点以多播方式发送的数据缓存起来，当终端接收到目标节点发送的数据重传结束指示，并将第一协议栈的数据递交到高层后，才可以开始将缓存的通过目标节点以多播方式发送的数据递交高层。终端基于第一协议栈和第二协议栈接收到的数据可能存在重复数据，终端的应用层可执行重复性检测，以丢弃或剔除重复数据。
需要说明的是，终端可以维护两套协议栈，即基于源节点的第一协议栈和基于目标节点的第二协议栈。当终端接收到目标节点发送的数据重传结束指示，并将第一协议栈的数据递交到高层后，才可以开始基于第二协议栈接收目标节点以多播方式发送的数据。
作为本申请的一个可选实施例，步骤301包括：
根据终端专用资源或临时调度资源，接收所述目标节点重传的数据包。
其中，终端专用调度资源可以为通过终端专用调度(如终端的C-RNTI)来调度的无线资源；临时调度资源可以为通过临时调度(如目标节点分配给终端的临时G-RNTI，也就是区别于目标节点使用多播方式传输所述多播业务的调度信息，比如G-RNTI)来调度的无线资源。
目标节点基于从源节点获取到的GTP-U序列号和源PDCP序列号的映射关系进行数据传输。例如，源节点指示的其中一对GTP-U SN＝5和源PDCP SN＝5，源节点对该数据包分配的PDCP SN＝5，则目标节点重用该PDCP SN＝5对GTP-U SN＝5的数据进行重传。另一种情况，源节点指示一对GTP-U SN＝6和PDCP SN＝None，源节点还没有对该数据包分配PDCP SN，则目标节点需要按序依次编号，比如PDCP SN＝6，则目标节点使用该PDCP SN＝6对GTP-U SN＝6的数据进行重传
作为一个可选实施例，步骤301之前，所述方法还包括：
接收源节点发送的切换命令消息；
根据所述切换命令消息与所述目标节点建立连接；其中，切换命令消息携带以下信息的至少一项：
多播业务标识；所述多播业务标识可以是TMGI。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息。其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
进一步的，终端接收到切换命令消息之后，所述方法还包括以下至少一项：
保持所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体不变；
重建所述切换命令消息指示的多播业务的多播模式对应的接收无线链路控制RLC实体；所述重建行为包括将接收RLC实体缓存中的数据处理后递交到高层(如PDCP实体，此行为适用于RLC配置有重排序功能)，以及将接收RLC实体的接收窗口初始化；
触发状态报告反馈，所述状态报告用于指示终端侧对数据包的接收状态；如切换命令中指示网络侧(如目标节点)将对某多播业务进行重传，终端向网络侧反馈下行数据的接收状态(如PDCP状态报告)。
需要说明的是，所述多播业务的多播模式对应的接收PDCP实体、RLC实体指的是终端接收源节点通过多播方式发送的所述多播业务时使用的协议栈实体。
所述源节点对应的接收PDCP实体、RLC实体为终端在源节点时接收源节点以多播方式发送数据时使用的协议栈实体，切换后，终端使用所述协议栈实体接收目标节点发送的重传数据。当终端接收到目标节点发送的数据重传结束指示后，可立即将所述协议栈实体的数据递交到高层(如理解释放PDCP、RLC实体)，也可以等所述协议栈实体维护的定时器超时后将所述协议栈实体的数据递交高层。
所述目标节点对应的接收PDCP实体、RLC实体为终端在目标节点时接收目标节点以多播方式发送数据时使用的协议栈实体。
本申请实施例中，步骤301之后，所述方法还包括：
接收所述目标节点发送的第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
相应的，如果网络侧给终端配置了临时G-RNTI(即目标节点采用临时调度资源给终端重传数据)，所述方法还包括：
停止监听临时调度资源，所述临时调度资源用于目标节点进行数据重传。
可以理解的是，如果网络侧给终端配置了临时调度资源(如临时G-RNTI)，当终端接收到目标节点发送的数据重传结束指示后，可理解为目标节点后续可能不在使用该临时调度资源传输重传数据，则终端可停止监听所述临时调度资源，或者当终端决定或开始将第一协议栈数据递交高层时，停止监听所述临时调度资源。
进一步的，终端接收到第三指示信息之后，所述方法还包括以下至少一项：
释放所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体；所述释放行为包括将接收PDCP实体缓存中的数据处理后递交到高层，以及将释放接收PDCP实体；
释放所述切换命令消息指示的多播业务与所述源节点对应的接收RLC实体；所述释放行为包括将接收RLC实体缓存中的数据处理后递交到高层(如 PDCP实体，此行为适用于RLC配置有重排序功能)，以及将释放接收RLC实体；
指示所述切换命令消息指示的多播业务与所述目标节点对应的接收PDCP实体可以按序向上层递交数据；
指示所述切换命令消息指示的多播业务与所述目标节点对应的接收RLC实体可以按序向上层递交数据。
作为一个可选实施例，步骤301之前，所述方法还包括：
向目标节点发送所述终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包。
例如，终端在与目标节点建立连接时或之后及时主动向目标节点上报PDCP状态报告，从而使得目标节点能够获知终端的接收状态指示信息；或者，目标节点请求或源节点指示终端向目标节点上报PDCP状态报告，从而获得终端的接收状态指示信息。
需要说明的是，所述PDCP状态报告用于指示终端侧接收状态，如用于指示PDCP SN＝1的包接收到了，PDCP SN＝2的包没有接收到等，目标节点基于所述PDCP状态报告以及从源节点获取到GTP-U SN和PDCP SN的映射关系，可以确定GTP-U SN对应的数据包是终端没有接收到的，进而可以对没有接收到的数据进行重传。
相应的，步骤301包括：
接收所述目标节点根据所述映射关系从所述至少一个第一数据包中PDCP序列号最小的第一数据包开始重传的数据包。
例如，终端上报的第一数据包的源PDCP序列号为3和4，目标节点根据映射关系，查找源PDCP序列＝3的数据包的GTP-U序列号，并从GTP-U序列号对应的数据包开始按序进行数据重传。
综上，在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
需要说明的是，本申请实施例提供的数据重传方法，执行主体可以为数据重传装置，或者该数据重传装置中的用于执行加载数据重传方法的控制模块。本申请实施例中以数据重传装置执行加载数据重传方法为例，说明本申请实施例提供的数据重传方法。
为了更清楚的描述本申请提供的数据重传方法，下面结合一个示例对该数据重传方法进行描述。如图4所示，该数据重传方法包括以下步骤：
步骤1，源节点向目标节点发送切换请求消息，所述切换请求消息中携带多播相关信息。其中，所述多播业务信息包含以下一项或多项内容：
多播业务标识；该多播业务标识可以是TMGI，或者多播业务序号(比如源节点通过Xn接口建立过程获取到目标节点能够支持的多播业务列表，则源节点可以通过该列表中的多播业务序号指示对应的多播业务)。
指示源节点请求转发多播业务数据的第一指示信息；例如，第一指示信息为DL forwarding IE(下行转发IE)，当该IE设置为第一值时，表示源节点请求转发对应的多播业务数据，当该IE设置为第二值时，表示源节点不请求转发对应的多播业务数据。再例如，第一指示信息为1比特指示，若该1比特取值为“1”，表示源节点请求转发对应的多播业务数据，若该1比特取值为“0”，表示源节点不请求转发对应的多播业务数据。又例如，第一指示信息为一个特定指示，当该特定指示存在时表示源节点请求转发对应的多播业务数据，当该特定指示不存在时表示源节点不请求转发对应的多播业务数据。
目标节点向源节点发送切换响应消息，所述切换响应消息中携带多播业务相关信息。其中，所述多播业务相关信息包含以下一项或多项：
多播业务标识；所述多播业务标识可以是TMGI；
指示目标节点同意进行多播业务数据转发的第二指示信息；例如该第二指示信息为一个特定IE，当该特定IE存在时表示目标节点同意多播业务数据转发，目标可以基于该IE提供的GTP-U序列号进行数据转发，当该特定IE不存在时表示目标节点不同意多播业务数据转发。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数 据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息。其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI(该G-RNTI不同于上述临时G-RNTI)。
步骤3，源节点向目标节点发送状态指示信息，所述状态指示信息用于展示N个数据包的GTP-U序列号和源PDCP序列号的映射关系，所述状态指示信息包括下述信息的至少一项：
源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点将终端切换到目标节点时源节点正在发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配的PDCP层编号为PDCP SN＝5。
源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；例如，源节点决定将终端切换到目标节点时源节点第一个待发送的数据包为GTP-U SN＝3对应的数据包，源节点为其分配或将为其分配的PDCP层编号为PDCP SN＝5。
在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号；源节点可以基于终端发送的PDCP状态报告确定在切换之前没有被终端接收的数据包的GTP-U SN和PDCP SN。
其中，源节点发起状态指示信息的时机可以是源节点决定向终端发送切 换命令时或源节点向终端发送切换命令时或源节点向终端发送切换命令后，在此不做具体限定。
步骤3.1，源节点向目标节点转发数据。例如，源节点按序(GTP-U SN)向目标节点转发数据，所述数据可以是源节点缓存的数据和/或从核心网节点获取的新数据。
其中，源节点向目标节点转发数据时提供该数据包的GTP-U SN和源PDCP SN的映射关系，其中所述源PDCP SN为源节点为所述数据包分配的PDCP序列号。
其中，源节点从终端切换时源节点的状态指示信息对应的数据包开始按序发送。或，源节点从终端切换时源节点的状态指示信息对应的下一个数据包开始按序发送。
额外的，如果源节点获取到了终端的接收状态信息，则源节点从终端第一个没有接收到的数据开始按序转发数据。比如，终端切换时源节点下一个等待发送GTP-U SN＝6(假设该包对应PDCP SN＝6)的数据包，则源节点按照GTP-U SN＝6/PDCP SN＝6开始按序向目标节点转发数据。如果源节点获取到GTP-U SN＝2/PDCP SN＝2的包没有收到(假设其他的数据包都收到了)，则源节点按序向目标节点转发GTP-U SN＝2/PDCP SN＝2、GTP-U SN＝6/PDCP SN＝6的数据包。
其中，步骤3和步骤3.1可以是独立的过程，也可以是合并的过程。
步骤4，源节点向终端发送切换命令消息，所述切换命令消息中携带多播业务相关信息。其中所述多播业务相关信息包含以下内容的至少一项：
多播业务标识；所述多播业务标识可以是TMGI。
指示目标节点是否进行数据重传的第一重传指示信息；例如，该第一重传指示信息为1比特指示信息，当该1比特指示信息取值为“1”，表示目标节点会进行数据重传，此时，目标节点通过终端的C-RNTI调度多播业务数据；当该1比特指示信息取值为“0”，表示目标节点不会进行数据重传。
指示目标节点进行数据重传的资源的第二重传指示信息；例如，将MRB对应的一个特定域设置为第一值，当终端切换到目标节点后目标节点可以通过终端的C-RNTI调度多播业务数据；或者，当第二重传指示信息为临时的 多播数据调度信息(如临时G-RNTI)，当该指示存在时，表示目标节点通过该临时的G-RNTI调度多播数据。
用于进行数据重传的混合自动重传请求HARQ进程信息；例如，当终端切换到目标节点后目标节点通过特定的HARQ进程重传多播数据。比如，目标节点正在使用HARQ process ID＝1,2以多播模式传输多播业务，对该终端，目标节点为其分配特定的HARQ process ID＝3为终端重传该多播业务数据。
用于通过多播模式进行多播数据传输的公共资源的配置信息；其中所述公共资源的配置信息可以是目标节点以多播方式发送该多播业务时的调度信息，例如某多播业务对应的调度信息G-RNTI。
步骤5，终端接收源节点发送的切换命令消息，所述切换命令消息中携带多播业务相关信息。终端发起与目标节点的连接建立过程。此外，终端的行为还包括以下一项或多项：
保持所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体不变；
重建所述切换命令消息指示的多播业务的多播模式对应的接收无线链路控制RLC实体；
触发状态报告反馈，所述状态报告用于指示终端侧对数据包的接收状态。
步骤6，目标节点进行数据重传，所述数据重传的资源为通过终端专用调度(如C-RNTI)或临时调度(如临时G-RNTI)来调度无线资源。目标节点基于从源节点获取到的GTP-U SN和源PDCP SN映射关系进行数据重传。例如源节点指示的其中一对GTP-U SN＝5和源PDCP SN＝5，源节点对该数据包分配的PDCP SN＝5，则目标节点重用该PDCP SN＝5对GTP-U SN＝5的数据进行重传。另一种情况，源节点指示一对GTP-U SN＝6和PDCP SN＝None，源节点还没有对该数据包分配PDCP SN，则目标节点需要按序依次编号，比如PDCP SN＝6，则目标节点使用该PDCP SN＝6对GTP-U SN＝6的数据进行重传。
需要说明的是，终端维护两套协议栈，分别对应源MRB(第一协议栈)和目标MBR(第二协议栈)。终端基于数据重传配置接收的数据对应于源MRB的协议栈，基于目标小区的公共资源配置接收的数据对应于目标MRB的协 议栈。(如终端接收到C-RNTI或临时G-RNTI或G-RNTI通过特定HARQ进程传输的数据时，将该数据递交给源MRB对应的协议栈，当终端接收到通过G-RNTI通过公共HARQ进程传输的数据时，将该数据递交给目标MRB对应的协议栈)。
步骤7，目标节点指示源节点停止数据转发。例如，目标节点基于以下信息决定指示源节点停止数据转发的时机：
基于目标节点的缓存数据或发送状态，如源节点向目标节点转发GTP-U SN＝3,4,5，...的数据包，如果目标节点接收到GTP-U SN＝5对应的数据包且其缓存中有GTP-U SN＝5的数据包则指示源节点停止数据转发。或如果目标节点接收到GTP-U SN＝5对应的数据包且其缓存中有GTP-U SN＝6的数据包则指示源节点停止数据转发。如源节点向目标节点转发GTP-U SN＝3,4,5，...的数据包，如果目标节点接收到GTP-U SN＝5对应的数据包且目标节点正在发送GTP-U SN＝5的数据包则指示源节点停止数据转发。或如果目标节点接收到GTP-U SN＝5对应的数据包且其目标节点第一个等待传输的数据为对应于GTP-U SN＝6的数据包则指示源节点停止数据转发。
可选的，步骤7可以在步骤8之前或之后。
或者，源节点维持一个定时器，当定时器超时，如果没有从目标节点接收到停止数据转发的指示信息，则源节点自动停止数据转发。
步骤8，目标节点向终端发送指示目标节点的数据重传结束的第三指示信息。当终端接收到第三指示信息后，终端的行为还包括以下一项或多项：
释放所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体；
释放所述切换命令消息指示的多播业务与所述源节点对应的接收RLC实体；
指示所述切换命令消息指示的多播业务与所述目标节点对应的接收PDCP实体可以按序向上层递交数据；
指示所述切换命令消息指示的多播业务与所述目标节点对应的接收RLC实体可以按序向上层递交数据。
需要说明的是，所述源节点对应的接收PDCP实体、RLC实体为终端在 源节点时接收源节点以多播方式发送数据时使用的协议栈实体，切换后，终端使用所述协议栈实体接收目标节点发送的重传数据。当终端接收到目标节点发送的数据重传结束指示后，可立即将所述协议栈实体的数据递交到高层(如理解释放PDCP、RLC实体)，也可以等所述协议栈实体维护的定时器超时后将所述协议栈实体的数据递交高层。
需要说明的是，所述目标节点对应的接收PDCP实体、RLC实体为终端在目标节点时接收目标节点以多播方式发送数据时使用的协议栈实体。
额外的，如果网络侧给UE配置了临时G-RNTI，UE停止监听该临时G-RNTI。
可以理解的，如果网络侧给UE配置了临时调度资源(如临时G-RNTI)，当终端接收到目标节点发送的数据重传结束指示后，可理解为目标节点后续可能不在使用该临时调度资源传输重传数据，则终端可停止监听所述临时调度资源，或者当终端决定或开始将第一协议栈数据递交高层时，停止监听所述临时调度资源。
如图5所示，本申请实施例还提供一种数据重传装置500，应用于目标节点，包括：
关系获取模块501，用于获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
数据重传模块502，用于根据所述映射关系，进行数据重传。
作为本申请的至少一个可选实施例，所述装置还包括：
信息获取模块，用于获取所述终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包；
所述数据重传模块包括：
第一数据重传子模块，用于根据所述至少一个第一数据包的源PDCP序列号以及所述映射关系，进行数据传输。
作为本申请的至少一个可选实施例，所述第一数据重传子模块包括：
第一数据重传单元，用于根据所述映射关系，从所述至少一个第一数据 包中PDCP序列号最小的第一数据包开始进行数据重传。
作为本申请的至少一个可选实施例，所述关系获取模块包括：
关系获取子模块，用于接收所述源节点发送的状态指示信息，所述状态指示信息包括下述信息的至少一项：
源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；
源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；
在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
作为本申请的至少一个可选实施例，所述装置还包括：
数据接收模块，用于接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的数据包。
作为本申请的至少一个可选实施例，所述数据接收模块包括：
数据接收子模块，用于接收所述源节点从第二数据包开始按照GTP-U序列号的顺序转发的数据包；
其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
作为本申请的至少一个可选实施例，所述数据重传模块包括：
第二数据重传子模块，用于根据所述映射关系，从所述终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包开始按序进行数据重传；
或者，用于根据所述映射关系，从所述终端切换到目标节点时所述源节点的第一个待发送的数据包按序进行数据重传。
作为本申请的至少一个可选实施例，所述装置还包括：
请求接收模块，用于接收所述源节点发送的切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示 信息中的至少一项；
响应发送模块，用于向所述源节点发送切换响应消息，所述切换响应消息中携带以下信息的至少一项：
多播业务标识；
指示目标节点同意进行多播业务数据转发的第二指示信息；
指示目标节点是否进行数据重传的第一重传指示信息；
指示目标节点进行数据重传的资源的第二重传指示信息；
用于进行数据重传的混合自动重传请求HARQ进程信息；
用于通过多播模式进行多播数据传输的公共资源的配置信息。
作为本申请的至少一个可选实施例，所述装置还包括：
第二连接模块，用于与接收到所述源节点发送的切换命令消息的终端建立连接；所述切换命令消息携带以下信息的至少一项：
多播业务标识；
指示目标节点是否进行数据重传的第一重传指示信息；
指示目标节点进行数据重传的资源的第二重传指示信息；
用于进行数据重传的混合自动重传请求HARQ进程信息；
用于通过多播模式进行多播数据传输的公共资源的配置信息。
作为本申请的至少一个可选实施例，所述装置还包括：
指示发送模块，用于根据所述目标节点的缓存数据状态，向所述源节点发送停止数据转发指示。
作为本申请的至少一个可选实施例，所述装置还包括：
第三发送模块用于向终端发送第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
本申请实施例提供的数据重传装置能够实现图1的方法实施例中数据重传装置实现的各个过程，为避免重复，这里不再赘述
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
可选的，本申请实施例还提供一种通信设备，该通信设备为目标节点，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的程序或指令，该程序或指令被处理器执行时实现上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
如图6所示，本申请实施例还提供一种数据重传装置600，应用于源节点，包括：
关系发送模块601，用于向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
作为本申请的至少一个可选实施例，所述关系发送模块包括：
关系发送子模块，用于向目标节点发送状态指示信息，所述状态指示信息包括下述信息的至少一项：
源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；
源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；
在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
作为本申请的至少一个可选实施例，所述装置还包括：
数据转发模块，用于按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包。
作为本申请的至少一个可选实施例，所述数据转发模块包括：
数据转发子模块，用于从第二数据包开始按照GTP-U序列号的顺序向所述目标节点转发数据包；
其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
作为本申请的至少一个可选实施例，所述装置还包括：
请求发送模块，用于向所述目标节点发送切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示信息中的至少一项；
响应接收模块，用于接收所述目标节点发送的切换响应消息，所述切换响应消息中携带以下信息的至少一项：
多播业务标识；
指示目标节点同意进行多播业务数据转发的第二指示信息；
指示目标节点是否进行数据重传的第一重传指示信息；
指示目标节点进行数据重传的资源的第二重传指示信息；
用于进行数据重传的混合自动重传请求HARQ进程信息；
用于通过多播模式进行多播数据传输的公共资源的配置信息。
作为本申请的至少一个可选实施例，所述装置还包括：
命令发送模块，用于向终端发送切换命令消息，所述切换命令消息携带以下信息的至少一项：
多播业务标识；
指示目标节点是否进行数据重传的第一重传指示信息；
指示目标节点进行数据重传的资源的第二重传指示信息；
用于进行数据重传的混合自动重传请求HARQ进程信息；
用于通过多播模式进行多播数据传输的公共资源的配置信息。
作为本申请的至少一个可选实施例，所述装置还包括：
停止模块，用于接收所述目标节点发送的停止数据转发指示，并停止数据包转发；
或者，用于在第一定时器超时，所述源节点未接收到所述目标节点发送的停止数据转发指示，停止数据包转发。
本申请实施例提供的数据重传装置能够实现图2的方法实施例中数据重传装置实现的各个过程，为避免重复，这里不再赘述
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重 传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
可选的，本申请实施例还提供一种通信设备，该通信设备为源节点，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的程序或指令，该程序或指令被处理器执行时实现上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
如图7所示，本申请实施例还提供一种数据重传装置700，应用于终端，包括：
重传接收模块701，用于在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
作为本申请的至少一个可选实施例，所述重传接收模块包括：
第一子模块，用于基于源节点的第一协议栈，接收所述目标节点重传的数据包。
作为本申请的至少一个可选实施例，所述重传接收模块包括：
重传接收子模块，用于根据终端专用资源或临时调度资源，接收所述目标节点重传的数据包。
作为本申请的至少一个可选实施例，所述装置还包括：
命令接收模块，用于接收源节点发送的切换命令消息；
第一连接模块，用于根据所述切换命令消息与所述目标节点建立连接；其中，切换命令消息携带以下信息的至少一项：
多播业务标识；
指示目标节点是否进行数据重传的第一重传指示信息；
指示目标节点进行数据重传的资源的第二重传指示信息；
用于进行数据重传的混合自动重传请求HARQ进程信息；
用于通过多播模式进行多播数据传输的公共资源的配置信息。
作为本申请的至少一个可选实施例，所述装置还包括以下至少一个模块：
第一保持模块，用于保持所述切换命令消息指示的多播业务与所述源节 点对应的接收PDCP实体不变；
第一重建模块，用于重建所述切换命令消息指示的多播业务的多播模式对应的接收无线链路控制RLC实体；
第一反馈模块，用于触发状态报告反馈，所述状态报告用于指示终端侧对数据包的接收状态。
作为本申请的至少一个可选实施例，所述装置还包括：
停止指示接收模块，用于接收所述目标节点发送的第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
作为本申请的至少一个可选实施例，所述装置还包括：
第四接收模块，用于基于目标节点的第二协议栈，接收所述目标节点发送的多播业务的数据。
作为本申请的至少一个可选实施例，所述装置还包括以下至少一个模块：
第一释放模块，用于释放所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体；
第二释放模块，用于释放所述切换命令消息指示的多播业务与所述源节点对应的接收RLC实体；
第一指示模块，用于指示所述切换命令消息指示的多播业务与所述目标节点对应的接收PDCP实体可以按序向上层递交数据；
第二指示模块，用于指示所述切换命令消息指示的多播业务与所述目标节点对应的接收RLC实体可以按序向上层递交数据。
本申请实施例提供的数据重传装置能够实现图3的方法实施例中数据重传装置实现的各个过程，为避免重复，这里不再赘述
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
可选的，本申请实施例还提供一种通信设备，该通信设备为终端，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的程序或指令，该程序或指令被处理器执行时实现上述数据重传方法实施例的各个过程，且 能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例中的数据重传装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动电子设备，也可以为非移动电子设备。示例性的，移动电子设备可以为手机、平板电脑、笔记本电脑、掌上电脑、车载电子设备、可穿戴设备、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本或者个人数字助理(personal digital assistant，PDA)等，非移动电子设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的数据重传装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
图8是本申请一实施例的网络侧设备(目标节点或源节点)的结构图，能够实现上述的信息接收方法的细节，并达到相同的效果。如图8所示，网络侧设备1300包括：处理器1301、收发机1302、存储器1303和总线接口，其中：
处理器1301，用于读取存储器1303中的程序，执行下列过程：
获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
根据所述映射关系，进行数据重传。
或者，处理器1301，用于读取存储器1303中的程序，执行下列过程：
向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1301代表的一个或多个处理器和存储器1303代表的存储器的各种电路链 接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1302可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
图9为实现本申请各个实施例的一种电子设备的硬件结构示意图。
该电子设备900包括但不限于：射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909、以及处理器910等部件。
本领域技术人员可以理解，电子设备900还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器910逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图9中示出的电子设备结构并不构成对电子设备的限定，电子设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
其中，射频单元901(如果有则写)，用于在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
在本申请实施例中，在终端由多播小区切换到多播小区的过程中，目标节点基于数据包的GTP-U序列号和源PDCP序列号的映射关系进行数据重传，减少终端在切换过程丢失的数据量，以进一步满足多播业务的业务需求，从而能够解决终端在切换过程中导致的数据丢失问题。
应理解的是，本申请实施例中，射频单元901可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器910处理；另外，将上行的数据发送给基站。通常，射频单元901包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元901还可以通过无线通信系统与网络和其他设备通信。
电子设备通过网络模块902为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元903可以将射频单元901或网络模块902接收的或者在存储器909中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元903还可以提供与电子设备900执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元903包括扬声器、蜂鸣器以及受话器等。
输入单元904用于接收音频或视频信号。输入单元904可以包括图形处理器(Graphics Processing Unit，GPU)9041和麦克风9042，图形处理器9041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元906上。经图形处理器9041处理后的图像帧可以存储在存储器909(或其它存储介质)中或者经由射频单元901或网络模块902进行发送。麦克风9042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元901发送到移动通信基站的格式输出。
电子设备900还包括至少一种传感器905，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板9061的亮度，接近传感器可在电子设备900移动到耳边时，关闭显示面板9061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别电子设备姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器905还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元906用于显示由用户输入的信息或提供给用户的信息。显示单元906可包括显示面板9061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板9061。
用户输入单元907可用于接收输入的数字或字符信息，以及产生与电子 设备的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元907包括触控面板9071以及其他输入设备9072。触控面板9071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板9071上或在触控面板9071附近的操作)。触控面板9071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器910，接收处理器910发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板9071。除了触控面板9071，用户输入单元907还可以包括其他输入设备9072。具体地，其他输入设备9072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板9071可覆盖在显示面板9061上，当触控面板9071检测到在其上或附近的触摸操作后，传送给处理器910以确定触摸事件的类型，随后处理器910根据触摸事件的类型在显示面板9061上提供相应的视觉输出。虽然在图9中，触控面板9071与显示面板9061是作为两个独立的部件来实现电子设备的输入和输出功能，但是在某些实施例中，可以将触控面板9071与显示面板9061集成而实现电子设备的输入和输出功能，具体此处不做限定。
接口单元908为外部装置与电子设备900连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元908可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到电子设备900内的一个或多个元件或者可以用于在电子设备900和外部装置之间传输数据。
存储器909可用于存储软件程序以及各种数据。存储器909可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可 存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器909可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器910是电子设备的控制中心，利用各种接口和线路连接整个电子设备的各个部分，通过运行或执行存储在存储器909内的软件程序和/或模块，以及调用存储在存储器909内的数据，执行电子设备的各种功能和处理数据，从而对电子设备进行整体监控。处理器910可包括一个或多个处理单元；优选的，处理器910可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器910中。
电子设备900还可以包括给各个部件供电的电源(比如电池)，优选的，电源可以通过电源管理系统与处理器910逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，电子设备900包括一些未示出的功能模块，在此不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
本申请实施例还提供了一种电子设备，被配置成用于执行上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再 赘述。
本申请实施例还提供了一种数据重传装置被配置成用于执行上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种计算机程序产品，所述计算机程序产品被至少一个处理器执行上述数据重传方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限 于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (53)

  1. 一种数据重传方法，应用于目标节点，包括：
    获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
    根据所述映射关系，进行数据重传。
  2. 根据权利要求1所述的方法，其中，所述根据所述映射关系，进行数据重传，包括：
    根据所述映射关系，通过终端专用调度资源或临时调度资源进行数据重传。
  3. 根据权利要求1所述的方法，其中，所述根据所述映射关系，进行数据重传之前，所述方法还包括：
    获取终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包；
    所述根据所述映射关系，进行数据重传，包括：
    根据所述至少一个第一数据包的源PDCP序列号以及所述映射关系，进行数据传输。
  4. 根据权利要求3所述的方法，其中，所述根据所述至少一个第一数据包的源PDCP序列号以及所述映射关系，进行数据传输，包括：
    根据所述映射关系，从所述至少一个第一数据包中PDCP序列号最小的第一数据包开始进行数据重传。
  5. 根据权利要求1所述的方法，其中，所述获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系，包括：
    接收所述源节点发送的状态指示信息，所述状态指示信息包括下述信息的至少一项：
    源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；
    源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；
    在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
  6. 根据权利要求5所述的方法，其中，所述根据所述映射关系，进行数据重传之前，所述方法还包括：
    接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的数据包。
  7. 根据权利要求6所述的方法，其中，所述接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的所述N个数据包，包括：
    接收所述源节点从第二数据包开始按照GTP-U序列号的顺序转发的数据包；
    其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
    或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
    或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
  8. 根据权利要求7所述的方法，其中，所述根据所述映射关系，进行数据重传，包括：
    根据所述映射关系，从所述终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包开始按序进行数据重传；
    或者，
    根据所述映射关系，从所述终端切换到目标节点时所述源节点的第一个待发送的数据包按序进行数据重传。
  9. 根据权利要求1所述的方法，其中，所述获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系之前，所述方法还包括：
    接收所述源节点发送的切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示信息中的至少一项；
    向所述源节点发送切换响应消息，所述切换响应消息中携带以下信息的 至少一项：
    多播业务标识；
    指示目标节点同意进行多播业务数据转发的第二指示信息；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  10. 根据权利要求1所述的方法，其中，所述根据所述映射关系，进行数据重传之前，所述方法还包括：
    与接收到所述源节点发送的切换命令消息的终端建立连接；所述切换命令消息携带以下信息的至少一项：
    多播业务标识；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  11. 根据权利要求6或7所述的方法，还包括：
    根据所述目标节点的缓存数据状态，向所述源节点发送停止数据转发指示。
  12. 根据权利要求1所述的方法，其中，所述根据所述映射关系，进行数据重传之后，所述方法还包括：
    向终端发送第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
  13. 一种数据重传方法，应用于源节点，包括：
    向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
  14. 根据权利要求13所述的方法，其中，所述向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系，包括：
    向目标节点发送状态指示信息，所述状态指示信息包括下述信息的至少一项：
    源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；
    源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；
    在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
  15. 根据权利要求13所述的方法，还包括：
    按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包。
  16. 根据权利要求15所述的方法，其中，所述按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包，包括：
    从第二数据包开始按照GTP-U序列号的顺序向所述目标节点转发数据包；
    其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
    或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
    或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
  17. 根据权利要求13所述的方法，其中，所述向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系之前，所述方法还包括：
    向所述目标节点发送切换请求消息，所述切换请求消息中携带多播业务标识和指示源节点请求转发多播业务数据的第一指示信息中的至少一项；
    接收所述目标节点发送的切换响应消息，所述切换响应消息中携带以下信息的至少一项：
    多播业务标识；
    指示目标节点同意进行多播业务数据转发的第二指示信息；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  18. 根据权利要求17所述的方法，还包括：
    向终端发送切换命令消息，所述切换命令消息携带以下信息的至少一项：
    多播业务标识；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  19. 根据权利要求15所述的方法，还包括：
    接收所述目标节点发送的停止数据转发指示，并停止数据包转发；
    或者，
    在第一定时器超时，所述源节点未接收到所述目标节点发送的停止数据转发指示，停止数据包转发。
  20. 一种数据重传方法，应用于终端，包括：
    在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
    其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
  21. 根据权利要求20所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包，包括：
    基于源节点的第一协议栈，接收所述目标节点重传的数据包。
  22. 根据权利要求20所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包，包括：
    根据终端专用资源或临时调度资源，接收所述目标节点重传的数据包。
  23. 根据权利要求20所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包之前，所述方法还包括：
    接收源节点发送的切换命令消息；
    根据所述切换命令消息与所述目标节点建立连接；其中，切换命令消息携带以下信息的至少一项：
    多播业务标识；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  24. 根据权利要求23所述的方法，还包括以下至少一项：
    保持所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体不变；
    重建所述切换命令消息指示的多播业务的多播模式对应的接收无线链路控制RLC实体；
    触发状态报告反馈，所述状态报告用于指示终端侧对数据包的接收状态。
  25. 根据权利要求20所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包之后，所述方法还包括：
    接收所述目标节点发送的第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
  26. 根据权利要求25所述的方法，还包括：
    停止监听临时调度资源，所述临时调度资源用于目标节点进行数据重传。
  27. 根据权利要求20所述的方法，还包括：
    基于目标节点的第二协议栈，接收所述目标节点发送的多播业务的数据。
  28. 根据权利要求25所述的方法，还包括以下至少一项：
    释放所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体；
    释放所述切换命令消息指示的多播业务与所述源节点对应的接收RLC实体；
    指示所述切换命令消息指示的多播业务与所述目标节点对应的接收 PDCP实体可以按序向上层递交数据；
    指示所述切换命令消息指示的多播业务与所述目标节点对应的接收RLC实体可以按序向上层递交数据。
  29. 根据权利要求20所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包之前，所述方法还包括：
    向目标节点发送所述终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包。
  30. 根据权利要求29所述的方法，其中，所述接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包，包括：
    接收所述目标节点根据所述映射关系从所述至少一个第一数据包中PDCP序列号最小的第一数据包开始重传的数据包。
  31. 一种数据重传装置，应用于目标节点，包括：
    关系获取模块，用于获取源节点发送的N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数；
    数据重传模块，用于根据所述映射关系，进行数据重传。
  32. 根据权利要求31所述的装置，还包括：
    信息获取模块，用于获取终端对源节点发送的数据包的接收状态指示信息，所述接收状态指示信息用于指示至少一个第一数据包的源PDCP序列号；所述第一数据包为进行节点切换之前没有被终端接收的数据包；
    所述数据重传模块包括：
    第一数据重传子模块，用于根据所述至少一个第一数据包的源PDCP序列号以及所述映射关系，进行数据传输。
  33. 根据权利要求31所述的装置，其中，所述关系获取模块包括：
    关系获取子模块，用于接收所述源节点发送的状态指示信息，所述状态指示信息包括下述信息的至少一项：
    源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U 序列号和源PDCP序列号；
    源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据包的GTP-U序列号和源PDCP序列号；
    在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
  34. 根据权利要求33所述的装置，还包括：
    数据接收模块，用于接收所述源节点按照N个数据包的GTP-U序列号的顺序转发的数据包。
  35. 根据权利要求34所述的装置，其中，所述数据接收模块包括：
    数据接收子模块，用于接收所述源节点从第二数据包开始按照GTP-U序列号的顺序转发的数据包；
    其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
    或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
    或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
  36. 根据权利要求34或35所述的装置，还包括：
    指示发送模块，用于根据所述目标节点的缓存数据状态，向所述源节点发送停止数据转发指示。
  37. 一种数据重传装置，应用于源节点，包括：
    关系发送模块，用于向目标节点发送N个数据包的GTP-U序列号和源节点为所述N个数据包分别分配的源PDCP序列号的映射关系；N为大于或者等于1的整数。
  38. 根据权利要求37所述的装置，其中，所述关系发送模块包括：
    关系发送子模块，用于向目标节点发送状态指示信息，所述状态指示信息包括下述信息的至少一项：
    源节点将终端切换到目标节点时所述源节点正在发送的数据包的GTP-U序列号和源PDCP序列号；
    源节点决定将终端切换到目标节点时所述源节点的第一个待发送的数据 包的GTP-U序列号和源PDCP序列号；
    在切换之前没有被终端接收的数据包的GTP-U序列号和源PDCP序列号。
  39. 根据权利要求37所述的装置，还包括：
    数据转发模块，用于按照N个数据包的GTP-U序列号的顺序向所述目标节点转发数据包。
  40. 根据权利要求39所述的装置，其中，所述数据转发模块包括：
    数据转发子模块，用于从第二数据包开始按照GTP-U序列号的顺序向所述目标节点转发数据包；
    其中，所述第二数据包为终端切换到目标节点时所述源节点正在发送的数据包的下一个数据包；
    或者，所述第二数据包为终端切换到目标节点时所述源节点的第一个待发送的数据包；
    或者，所述第二数据包为切换之前所述终端第一个没有接收到的数据包。
  41. 根据权利要求39所述的装置，还包括：
    停止模块，用于接收所述目标节点发送的停止数据转发指示，并停止数据包转发；
    或者，用于在第一定时器超时，所述源节点未接收到所述目标节点发送的停止数据转发指示，停止数据包转发。
  42. 一种数据重传装置，应用于终端，包括：
    重传接收模块，用于在所述终端切换到目标节点后，接收所述目标节点根据数据包的GTP-U序列号和源PDCP序列号的映射关系重传的数据包；
    其中，所述数据包的源PDCP序列号为源节点为所述数据包分配的PDCP序列号。
  43. 根据权利要求42所述的装置，其中，所述重传接收模块包括：
    重传接收子模块，用于根据终端专用资源或临时调度资源，接收所述目标节点重传的数据包。
  44. 根据权利要求42所述的装置，还包括：
    命令接收模块，用于接收源节点发送的切换命令消息；
    第一连接模块，用于根据所述切换命令消息与所述目标节点建立连接；其中，切换命令消息携带以下信息的至少一项：
    多播业务标识；
    指示目标节点是否进行数据重传的第一重传指示信息；
    指示目标节点进行数据重传的资源的第二重传指示信息；
    用于进行数据重传的混合自动重传请求HARQ进程信息；
    用于通过多播模式进行多播数据传输的公共资源的配置信息。
  45. 根据权利要求44所述的装置，还包括以下至少一个模块：
    第一保持模块，用于保持所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体不变；
    第一重建模块，用于重建所述切换命令消息指示的多播业务的多播模式对应的接收无线链路控制RLC实体；
    第一反馈模块，用于触发状态报告反馈，所述状态报告用于指示终端侧对数据包的接收状态。
  46. 根据权利要求42所述的装置，还包括：
    停止指示接收模块，用于接收所述目标节点发送的第三指示信息，所述第三指示信息用于指示目标节点的数据重传结束。
  47. 根据权利要求46所述的装置，还包括以下至少一个模块：
    第一释放模块，用于释放所述切换命令消息指示的多播业务与所述源节点对应的接收PDCP实体；
    第二释放模块，用于释放所述切换命令消息指示的多播业务与所述源节点对应的接收RLC实体；
    第一指示模块，用于指示所述切换命令消息指示的多播业务与所述目标节点对应的接收PDCP实体可以按序向上层递交数据；
    第二指示模块，用于指示所述切换命令消息指示的多播业务与所述目标节点对应的接收RLC实体可以按序向上层递交数据。
  48. 一种电子设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至12中任一项所述的数据重传方法的步骤；或者，所述程序或指 令被所述处理器执行时实现如权利要求13至19中任一项所述的数据重传方法的步骤；或者，所述程序或指令被所述处理器执行时实现如权利要求20至30中任一项所述的数据重传方法的步骤。
  49. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-12中任一项所述的数据重传方法的步骤；或者，所述程序或指令被处理器执行时实现如权利要求13-19中任一项所述的数据重传方法的步骤；或者，所述程序或指令被处理器执行时实现如权利要求20-30中任一项所述的数据重传方法的步骤。
  50. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1-12中任一项所述的数据重传方法的步骤；或者，如权利要求13-19中任一项所述的数据重传方法；或者，如权利要求20-30中任一项所述的数据重传方法。
  51. 一种电子设备，被配置成用于执行如权利要求1至12中任一项所述的数据重传方法；或者，如权利要求13至19中任一项所述的数据重传方法；或者，如权利要求20至30中任一项所述的数据重传方法。
  52. 一种数据重传装置，被配置成用于执行如权利要求1-12中任一项所述的数据重传方法的步骤；或者，如权利要求13-19中任一项所述的数据重传方法；或者，如权利要求20-30中任一项所述的数据重传方法。
  53. 一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如权利要求1-12中任一项所述的数据重传方法的步骤；或者，如权利要求13-19中任一项所述的数据重传方法；或者，如权利要求20-30中任一项所述的数据重传方法。
PCT/CN2021/089120 2020-04-30 2021-04-23 数据重传方法、装置、目标节点、源节点及终端 WO2021218788A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2022566295A JP7392176B2 (ja) 2020-04-30 2021-04-23 データ再送方法、装置、ターゲットノード、ソースノード及び端末
KR1020227041248A KR20230004786A (ko) 2020-04-30 2021-04-23 데이터 재전송 방법, 디바이스, 타겟 노드, 소스 노드 및 단말
EP21795959.2A EP4124080A4 (en) 2020-04-30 2021-04-23 DATA RETRANSMISSION METHOD AND DEVICE, DESTINATION NODE, SOURCE NODE AND TERMINAL
US17/968,665 US20230039646A1 (en) 2020-04-30 2022-10-18 Data retransmission method, data retransmission apparatus, target node, source node, and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010367115.X 2020-04-30
CN202010367115.XA CN113596736B (zh) 2020-04-30 2020-04-30 数据重传方法、装置、目标节点、源节点及终端

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/968,665 Continuation US20230039646A1 (en) 2020-04-30 2022-10-18 Data retransmission method, data retransmission apparatus, target node, source node, and terminal

Publications (1)

Publication Number Publication Date
WO2021218788A1 true WO2021218788A1 (zh) 2021-11-04

Family

ID=78237614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/089120 WO2021218788A1 (zh) 2020-04-30 2021-04-23 数据重传方法、装置、目标节点、源节点及终端

Country Status (6)

Country Link
US (1) US20230039646A1 (zh)
EP (1) EP4124080A4 (zh)
JP (1) JP7392176B2 (zh)
KR (1) KR20230004786A (zh)
CN (1) CN113596736B (zh)
WO (1) WO2021218788A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023102898A1 (zh) * 2021-12-10 2023-06-15 Oppo广东移动通信有限公司 重传方式的确定方法及定时器的控制方法、装置
CN117318898B (zh) * 2023-11-24 2024-02-09 合肥奎芯集成电路设计有限公司 高速串行接口中重复数据包的处理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101843138A (zh) * 2007-10-01 2010-09-22 高通股份有限公司 在切换期间在下行链路中按顺序传送分组数据汇聚协议(pdcp)业务数据
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
CN107078968A (zh) * 2014-09-02 2017-08-18 诺基亚通信公司 无线网络中的多连接性的分组序列编号
CN107925905A (zh) * 2015-08-19 2018-04-17 三星电子株式会社 用于处理向wlan载波卸载drb的方法和无线通信系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101400156B (zh) * 2007-09-29 2012-06-06 华为技术有限公司 基于s1切换的下行及上行数据包转发方法
KR101667507B1 (ko) * 2012-11-29 2016-10-18 후아웨이 테크놀러지 컴퍼니 리미티드 데이터 전송 제어 방법, 장치 및 시스템
EP3247145B1 (en) * 2015-02-05 2019-05-08 Huawei Technologies Co., Ltd. Method and device for indicating need of blind detection in subframes
US10728812B2 (en) * 2016-08-11 2020-07-28 Lg Electronics Inc. Method and apparatus for supporting MBMS service continuity
CN110475299B (zh) * 2018-05-10 2021-06-29 维沃移动通信有限公司 一种切换小区的方法及装置
CN110620640B (zh) * 2018-06-19 2021-09-21 维沃移动通信有限公司 一种数据传输方法、终端及节点设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101843138A (zh) * 2007-10-01 2010-09-22 高通股份有限公司 在切换期间在下行链路中按顺序传送分组数据汇聚协议(pdcp)业务数据
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
CN107078968A (zh) * 2014-09-02 2017-08-18 诺基亚通信公司 无线网络中的多连接性的分组序列编号
CN107925905A (zh) * 2015-08-19 2018-04-17 三星电子株式会社 用于处理向wlan载波卸载drb的方法和无线通信系统

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4124080A4 (en) 2023-08-30
CN113596736B (zh) 2022-09-02
JP7392176B2 (ja) 2023-12-05
JP2023523816A (ja) 2023-06-07
US20230039646A1 (en) 2023-02-09
EP4124080A1 (en) 2023-01-25
CN113596736A (zh) 2021-11-02
KR20230004786A (ko) 2023-01-06

Similar Documents

Publication Publication Date Title
WO2019196690A1 (zh) 旁链路的传输方法和终端
US20230039646A1 (en) Data retransmission method, data retransmission apparatus, target node, source node, and terminal
WO2020063442A1 (zh) 双连接切换方法、终端及网络设备
WO2021147778A1 (zh) 承载建立方法、配置方法、终端及网络侧设备
WO2021037148A1 (zh) 数据传输方法及终端
US20230018193A1 (en) Mobility management method, source base station, target base station, and terminal device
WO2020063263A1 (zh) 旁链路的链路释放方法及终端
WO2021136473A1 (zh) 多播业务的传输方法、传输处理方法及相关设备
WO2020169028A1 (zh) 副链路组播通信的配置方法和终端
WO2021083337A1 (zh) 无线链路失败处理方法及装置
WO2020088178A1 (zh) 处理方法及终端
CN110324195B (zh) 一种接收方法、发送方法及通信设备
CN111278165A (zh) 连接建立方法、终端设备及网络设备
WO2022022699A1 (zh) 数据传输方法、终端及网络侧设备
WO2021213381A1 (zh) 寻呼响应方法、终端及网络设备
US20210153246A1 (en) Random access method, terminal device and network device
WO2020088475A1 (zh) 一种反馈信息传输方法和设备
WO2020063452A1 (zh) 一种资源调度方法和装置
US20220201564A1 (en) Data transmission method, terminal, and network node
WO2021218848A1 (zh) 数据重传方法、装置、目标节点、源节点及终端
WO2019214472A1 (zh) 操作方法及终端
CN111614443B (zh) 终端能力上报、信息接收方法、终端及网络设备
WO2021213429A1 (zh) 数据接收、信息配置方法、终端及网络设备
WO2021027715A1 (zh) 多媒体多播广播业务的配置方法、终端和网络侧设备
WO2022012480A1 (zh) 数据传输方法、装置及设备

Legal Events

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

Ref document number: 21795959

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021795959

Country of ref document: EP

Effective date: 20221018

ENP Entry into the national phase

Ref document number: 2022566295

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227041248

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE