WO2022012480A1 - 数据传输方法、装置及设备 - Google Patents

数据传输方法、装置及设备 Download PDF

Info

Publication number
WO2022012480A1
WO2022012480A1 PCT/CN2021/105855 CN2021105855W WO2022012480A1 WO 2022012480 A1 WO2022012480 A1 WO 2022012480A1 CN 2021105855 W CN2021105855 W CN 2021105855W WO 2022012480 A1 WO2022012480 A1 WO 2022012480A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
data packet
node device
service
target service
Prior art date
Application number
PCT/CN2021/105855
Other languages
English (en)
French (fr)
Inventor
吴昱民
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2022012480A1 publication Critical patent/WO2022012480A1/zh

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
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a data transmission method, apparatus and device.
  • Dual connectivity means that the UE can establish connections in two cell groups (ie, a primary cell group (Master Cell Group, MCG) and a secondary cell group (Secondary Cell Group, SCG)) at the same time.
  • the MCG includes at least a primary cell (Primary Cell, PCell), and may also include at least one secondary cell (Secondary Cell, SCell);
  • the SCG includes at least a primary secondary cell (Primary Secondary Cell, PSCell), and may also include at least one SCell.
  • the UE can establish a connection between the source cell and the target cell at the same time, and then the UE releases the connection with the source cell and only maintains the connection with the target cell. Connection.
  • dual-connectivity mobility eg, handover or secondary cell group handover (SCG change)
  • SCG change secondary cell group handover
  • the purpose of the embodiments of the present application is to provide a data transmission method, apparatus, and device, which can solve the problems of discontinuous service data reception and service data packet loss in the dual-connectivity mobility management process.
  • a data transmission method applied to a UE, the method includes: when a mobility management command is received and a target service is received through a source cell, performing a first target operation on the bearer of the source cell , performing a second target operation on the bearer of the target cell; wherein the mobility management command is used to instruct the target cell to receive the target service; the first target operation includes: processing the buffered data in the bearer of the source cell.
  • the second target operation includes: establishing or re-establishing a protocol entity corresponding to the bearer of the target cell when a predetermined condition is met; the predetermined condition includes: after the first target operation is performed, or, receiving After the above mobility management command.
  • a data transmission method is provided, which is applied to a source node device.
  • the method includes: in a mobility management process, in the case of receiving a target service through a source cell, performing a third target operation;
  • the three-target operation is used to indicate the above-mentioned target service to the target node device.
  • a data transmission method applied to a target node device, the method includes: in a mobility management process, in the case of receiving a target service through a source cell, according to the data packet information of the target service, transfer The data packet of the above target service is sent to the UE through the bearer of the target cell.
  • a data transmission apparatus comprising: an execution module configured to execute a first target operation on a bearer of a source cell when a mobility management command is received and a target service is received through the source cell , performing a second target operation on the bearer of the target cell; wherein the mobility management command is used to instruct the target cell to receive the target service;
  • the first target operation includes: processing the buffered data in the bearer of the source cell
  • the second target operation includes: establishing or re-establishing a protocol entity corresponding to the bearer of the target cell when a predetermined condition is met; the predetermined condition includes: after the first target operation is performed, or, receiving After the above mobility management command.
  • a data transmission device comprising: an execution module configured to execute a third target operation in the case of receiving a target service through a source cell in a mobility management process; wherein the above-mentioned third The target operation is used to indicate the above target service to the target node device.
  • a data transmission device comprising: a sending module for, in a mobility management process, in the case of receiving a target service through a source cell, according to the data packet information of the target service, send the above-mentioned target service.
  • the data packet of the target service is sent to the UE through the bearer of the target cell.
  • a UE in a seventh aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor. The steps of implementing the method as described in the first aspect.
  • a node device in an eighth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the processor When executed, the steps of the method as described in the second aspect or the third aspect are implemented.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps as described in the first aspect are implemented.
  • a chip in a tenth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction, and implement the method described in the first aspect. the method described, or implement the method described in the second aspect or the third aspect.
  • the UE when the UE receives the mobility management command and receives the target service through the source cell, let the UE perform the first target operation on the bearer of the source cell (that is, perform the first target operation on the bearer of the source cell) process and submit them to the upper layer in order), perform the second target operation on the bearer of the target cell (that is, the UE establishes or re-establishes the protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command) .
  • the UE can process the data carried by the target cell after processing the data carried by the source cell, which not only avoids the repeated transmission of data packets of the target service, but also avoids the loss of data packets and improves the energy efficiency of the communication system. .
  • FIG. 1 is an architectural diagram of a communication system to which the data transmission method provided by an embodiment of the present application is applied;
  • FIG. 5 is one of the schematic structural diagrams of a data transmission apparatus provided by an embodiment of the present application.
  • FIG. 6 is a second schematic structural diagram of a data transmission apparatus provided by an embodiment of the present application.
  • FIG. 7 is a third schematic structural diagram of a data transmission apparatus provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a node device provided by an embodiment of the present application.
  • Multimedia Broadcast and Multicast Service (MBMS) or Multicast Broadcast Service (MBS)
  • MBMS/MBS services can be sent in the following two ways:
  • MBMS/MBS sending mode 1 Send through the physical multicast channel (Physical Multicast Channel, PMCH) in the 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 (eg, SIB13) and a broadcast control channel (Multicast Control Channel, MCCH), and data is sent through a broadcast traffic channel (Multicast Traffic Channel, MTCH).
  • system information eg, SIB13
  • MCCH Multicast Control Channel
  • MTCH Multicast Traffic Channel
  • MBMS/MBS transmission mode 2 Send through the Physical Downlink Shared Channel (PDSCH) channel scheduled by the Physical Downlink Control Channel (PDCCH).
  • the control information is sent through the system information (eg, SIB20) and the single cell broadcast control channel (Single Cell Multicast Control Channel, SC-MCCH), and the data is sent through the single cell broadcast service channel (Single Cell Multicast Traffic Channel, SC-MTCH) .
  • the SC-MCCH is sent through the PDSCH scheduled by the Single Cell-Radio Network Temporary Identity (SC-RNTI) PDCCH
  • SC-MTCH is sent through the PDSCH scheduled by the G-RNTI PDCCH.
  • SC-RNTI Single Cell-Radio Network Temporary Identity
  • the MBS service is sent through a specific MRB (MBMS Radio Bearer) radio bearer.
  • MRB MBMS Radio Bearer
  • the above MBS service can be marked by the following identifiers: Temporary Mobile Group Identity (TMGI), QoS flow ID.
  • TMGI Temporary Mobile Group Identity
  • QoS flow ID QoS flow ID
  • the core network node When the core network node sends multicast service data to the base station in a multicast manner, the core network node will simultaneously send the same service data to multiple base stations.
  • the unicast reception of the UE is received through a specific unicast data radio bearer (DRB (Data Radio Bearer)).
  • DRB Data Radio Bearer
  • the protocol stack of unicast transmission (or reception) includes from top to bottom: Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), wireless link Control (Radio Link Control, RLC), media access control (Medium Access Control, MAC).
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • the UE may establish connections in two cell groups (ie, a primary cell group (Master Cell Group, MCG) and a secondary cell group (Secondary Cell Group, SCG)) at the same time.
  • the MCG includes a primary cell (Primary Cell, PCell) and a secondary cell (Secondary Cell, SCell), and the SCG includes a primary secondary cell (Primary Secondary Cell, PSCell) and the SCell.
  • PCell Primary Cell
  • SCell Secondary Cell
  • PSCell Primary Secondary Cell
  • both PCell and PSCell may also be called SpCell (Special Cell, special cell).
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • NR terminology is used in most of the following description, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation, 6G) communication system.
  • FIG. 1 shows a system architecture diagram of a communication system to which an embodiment of the present application can be applied.
  • the communication system includes a terminal 11 and a network side device 12 .
  • the network-side device 12 may serve at least one cell group (eg, MCG or SCG).
  • MCG includes at least one PCell, and possibly at least one SCell;
  • MCG includes at least one PSCell, and possibly at least one SCell.
  • the above-mentioned network side device includes a node device, and the node device includes a source node device and a target node device.
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, Personal Digital Assistant (PDA), PDA, Netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (MID), Wearable Device (Wearable Device) or Vehicle-mounted equipment (VUE), pedestrian terminal (PUE) and other terminal-side equipment, wearable equipment includes: bracelets, headphones, glasses, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 .
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • a data transmission method provided by an embodiment of the present application can be applied to a UE, in other words, the data transmission method can be executed by software or hardware installed in the UE. As shown in FIG. 2 , the data transmission method provided by this embodiment of the present application may include the following step 201 .
  • Step 201 In the case of receiving the mobility management command and receiving the target service through the source cell, perform the first target operation on the bearer of the source cell, and perform the second target operation on the bearer of the target cell.
  • the above-mentioned target service includes a unicast service and/or a multicast service.
  • the UE when the UE receives the multicast service through the unicast bearer or the multicast bearer in the source cell, the UE receives the mobility management command sent by the network side device, and in the mobility management command, the UE is in the target cell through the
  • the unicast bearer or the multicast bearer receives the multicast service
  • the first target operation is performed on the bearer of the source cell
  • the second target operation is performed on the bearer of the target cell.
  • the data transmission methods provided by the embodiments of the present application are applied in the dual-link mobility management process.
  • the above-mentioned dual-connectivity mobility management process includes a handover process or an SCG change process (ie, an SCG change process). That is, when the UE changes its serving cell, it establishes the connection with the source cell and the target cell at the same time, then releases the connection with the source cell, and only maintains the connection with the target cell. For example, during the handover process, the PCell serving cell of the UE is changed from cell 1 to cell 2. During the change process, the UE establishes connections with both cell 1 and cell 2 at the same time, then releases the connection with cell 1, and only maintains the connection with cell 2. connect.
  • SCG change process ie, an SCG change process
  • the above mobility management command is used to instruct the target cell to receive the target service.
  • the above mobility management command includes any one of the following: a handover command, a secondary cell group SCG change command, an SCG addition command, and an SCG deletion command.
  • the above switching command is used to instruct to change the PCell.
  • the above SCG change command is used to instruct to change the SCG (for example, PSCell change), in this case, the source cell is the cell of the source SCG, and the target cell is the cell of the target SCG).
  • the above SCG addition command is used to instruct to add an SCG (eg, PSCell addition).
  • the source cell is the cell of the MCG
  • the target cell is the cell of the SCG.
  • the above SCG deletion command is used to instruct deletion of the SCG (eg, PSCell release). At this time, the source cell is the cell of the SCG, and the target cell is the cell of the MCG.
  • the above-mentioned first target operation includes: a first operation, where the first operation is: process the buffered data in the bearer of the source cell and deliver it to a higher layer in sequence.
  • the above-mentioned second target operation includes: establishing or re-establishing a protocol entity corresponding to the bearer of the target cell when a predetermined condition is met; the above-mentioned predetermined condition includes: after executing the first target operation, or receiving the mobility management command after.
  • first target operation may be predefined, specified by a protocol, or indicated by the network side, which is not limited in this embodiment of the present application.
  • second target operation may be predefined, specified by a protocol, or indicated by the network side, which is not limited in this embodiment of the present application.
  • the above-mentioned first target operation further includes: a second operation, where the above-mentioned second operation is: deleting the PDCP entity carried by the source cell.
  • the UE performs any of the following processing actions for the bearer of the source cell according to the network side instruction or agreement:
  • Processing behavior 1 of the bearer of the source cell After the UE processes the cached data in the PDCP entity of the bearer of the source cell and submits it to the upper layer in sequence, the UE deletes the PDCP entity of the bearer of the source cell.
  • Processing behavior 2 of the bearer of the source cell The UE processes the buffered data in the PDCP entity of the bearer of the source cell and delivers it to the upper layer in sequence.
  • the UE performs any of the following processing actions on the bearer of the target cell according to the network side instruction or agreement:
  • the processing behavior of the bearer of the target cell 1 After receiving the mobility management command, a protocol entity corresponding to the bearer of the target cell is established or re-established. For example, after the UE receives the mobility management command, in the process of processing the unicast bearer of the source cell, the UE simultaneously establishes or re-establishes the PDCP entity borne by the target cell.
  • the bearer processing action 2 of the target cell after the "source cell bearer processing action 1" or “source cell bearer processing action 2" is executed, the protocol entity corresponding to the target cell bearer is established or re-established. For example, after the UE receives the mobility management command, the UE first processes the bearer of the source cell, and only after the buffered data carried by the source cell is processed, the UE starts to establish or re-establish the PDCP entity carried by the target cell, so as to ensure In-order submission of received data.
  • the data type of the data carried by the source cell may include at least one of the following: PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol) layer data packet, PDCP layer control packet, PDCP layer layer data. That is, the data carried by the source cell may include at least one of the following: PDCP layer data packets carried, PDCP layer control packets carried, and PDCP layer data carried.
  • PDCP Packet Data Convergence Protocol
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • the above-mentioned PDCP layer data packets may be PDCP Data PDUs
  • the above-mentioned PDCP layer control packets may be PDCP control PDUs (eg, robust header compression (Robust Header Compression, ROHC) feedback packets)
  • the above-mentioned PDCP layer data may be PDCP PDUs.
  • the above PDCP layer data includes but is not limited to: Signaling Radio Bearers (SRB) control packets, SRB data packets, and Data Radio Bearers (SRB) control packets packet, DRB data packet, PDCP control packet, and PDCP data packet.
  • SRB Signaling Radio Bearers
  • SRB Data Radio Bearers
  • the data type of the data carried by the target cell may also include the above-mentioned data type, which will not be repeated here.
  • the data transmission method provided by the embodiment of the present application may further include the following steps 201a1 and 201a2:
  • Step 201a1 Before performing the first target operation on the bearer of the source cell, buffer the data packets received by the bearer of the target cell.
  • Step 201a2 After the first target operation is performed on the bearer of the source cell, the data packet received by the bearer of the target cell is delivered to the upper layer.
  • the UE may buffer the data packets received from the "bearer of the target cell” until the data of the "bearer of the source cell" is processed (for example, After all buffered data packets are delivered to the high-level protocol entity, or the "bearer of the source cell” is deleted), the data packets received from the "bearer of the target cell” are delivered to the high-level protocol entity.
  • the data transmission method provided by the embodiment of the present application may further include the following step 201b:
  • Step 201b The data packet information of the target service received from the bearer of the source cell is sent to the network side device through the bearer of the target cell.
  • the above-mentioned data packet information includes at least one of the following: the number of the first lost data packet, the number of the last received data packet, and the bitmap of the received data packet Indication; wherein, the above bitmap indication is used to indicate whether the corresponding data packet is successfully received.
  • the data packet information (eg, the number of the first lost data packet, and/or, the number of the last received data packet, and /or, the bitmap indication of the received data packet (each bit indicates whether a data packet with a specific number is successfully received) is sent to the network side device through the "bearer of the target cell".
  • the UE when the UE receives the mobility management command and receives the target service through the source cell, let the UE perform the first target operation on the bearer of the source cell (that is, process the buffered data in the bearer of the source cell and submit it in sequence). to a higher layer), perform the second target operation on the bearer of the target cell (ie, the UE establishes or re-establishes a protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command).
  • the UE can process the data carried by the target cell after processing the data carried by the source cell, which not only avoids the repeated transmission of data packets of the target service, but also avoids the loss of data packets and improves the energy efficiency of the communication system. .
  • a data transmission method provided by an embodiment of the present application can be applied to a source node device, in other words, the data transmission method can be executed by software or hardware installed in the source node device. As shown in FIG. 3 , the data transmission method provided by this embodiment of the present application may include step 301 .
  • Step 301 In the mobility management process, in the case of receiving the target service through the source cell, perform a third target operation.
  • the above-mentioned third target operation is used to indicate the target service to the target node device.
  • the above-mentioned third target operation includes at least one of the following:
  • the bearer identifier of the target service is indicated to the target node device.
  • the service information of the above target service includes at least one of the following: service identifier (eg, TMGI), service name (eg, XX TV station), service explanation (eg, multicast service release channel) (e.g. CCTV programs sent through radio and television networks), multicast service characteristics (e.g., voice, or video)), service sending address (e.g., TCP and/or IP address, and the sending port number corresponding to the address) , service sending protocol (eg, Hypertext Transport Protocol (HTTP), or Simple Message Transfer Protocol (Simple Message Transfer Protocol, SMTP)), session identifier (eg, MBS session-1), service type indication (e.g. multicast service or unicast service), scheduling identifier (e.g. MBS RNTI-1).
  • service identifier eg, TMGI
  • service name e.g, XX TV station
  • service explanation e.g, multicast service release channel
  • multicast service characteristics e.g., voice, or video
  • the bearer identifier of the above-mentioned target service includes at least one of the following:
  • the tunnel identifier between the source node device and the core network node device (for example, GTP-U Tunnel-1);
  • Data flow identification (eg, QoS flow-1);
  • Session ID (eg, PDU Session-1);
  • the radio bearer identity of the source node eg, DRB-1
  • the logical channel identification of the source node (eg, LCID-1).
  • the number of the data packet is GTP
  • the above-mentioned target correspondence includes: a mapping relationship between the number determined by the core network node device for the data packet of the target service and the number of the data packet of the target service in the access network node device.
  • the above bitmap indication is used to indicate the sending status of the corresponding data packet. It can be understood that the above bitmap indication is used to indicate whether the corresponding data packet is successfully received.
  • the numbering methods for the numbering of the data packets in the above-mentioned "data packet information of the target service carried" mainly include the following two numbering methods:
  • Numbering method 1 The number of the data packet is determined by the core network node device. For example, when a core network node device (eg, UPF) sends a data packet of a multicast service to a base station (eg, gNB), the data packet carries number information (eg, carried in the packet header of the GTP-U tunnel).
  • a core network node device eg, UPF
  • gNB base station
  • number information eg, carried in the packet header of the GTP-U tunnel.
  • Numbering method 2 The number of the data packet is determined by the node devices (such as the source node device and the target node device) of the access network. For example, the PDCP SN or COUNT determined by the PDCP entity of the source node device.
  • the above-mentioned behavior of the source node device forwarding the data packet of the target service to the target node device includes at least one of the following:
  • the core network node device Indicate the number determined by the core network node device for the data packet of the target service (that is, the number determined by the core network node device indicating the data packet of the forwarded target service, for example, the core network number of the data packet 1/2/3 is GTP -USN-1/2/3);
  • the sending number of the data packet indicating the target service at the source node device of the access network (that is, the sending number of the data packet indicating the forwarded target service at the source node device of the access network, for example, the forwarded data packet 1/2/3 , and indicate that the number of the data packet 1/2/3 in the source node device is PDCP COUNT-1/2/3);
  • Example 1 The data packet 1/2/3 has been forwarded , and indicate that the number of the data packet 1/2/3 in the target node device is PDCP COUNT-1/2/3;
  • Example 2 The data packet 1/2/3 is forwarded, and the data packet 1/2/3 is indicated in the target The starting number of the node device is PDCP COUNT-1);
  • the target correspondence that is, the correspondence between the "number determined by the core network node device" of the data packet indicating the forwarded target service and the "sending number of the node device of the access network", for example, the data packet 1/2/3
  • the number of the core network is GTP-US SN-1/2/3
  • the number of the corresponding source node is PDCP COUNT-1/2/3).
  • the above-mentioned target correspondence is a mapping relationship between the number determined by the core network node device for the data packet of the target service and the number of the data packet of the target service in the node device of the access network.
  • the target node device in the case of receiving the target service through the source cell, the target node device is made to send the data packets that have not been sent to the UE by notifying the target node device of the data packet information of the target service. , which not only avoids the repeated transmission of these data packets, but also avoids the loss of these data packets.
  • a data transmission method provided by an embodiment of the present application can be applied to a source node device, in other words, the data transmission method can be executed by software or hardware installed in the source node device. As shown in FIG. 4 , the data transmission method provided by this embodiment of the present application may include the following step 401 .
  • Step 401 In the mobility management process, in the case of receiving the target service through the source cell, according to the data packet information of the target service, the data packet of the target service is sent to the UE through the bearer of the target cell.
  • the data packet information of the above-mentioned target service includes at least one of the following:
  • the source cell indicated by the UE bears the received data packet information of the target service
  • the data packet information of the target service indicated by the source node device to the target node device.
  • the data packet information of the target service indicated by the source node device to the target node device includes at least one of the following:
  • the bearer identifier of the target service
  • the source node device forwards the data packet of the target service to the serial number information carried by the target node device.
  • the above numbering information includes at least one of the following:
  • the number determined by the core network node device for the data packet of the target service is the number determined by the core network node device for the data packet of the target service
  • the sending number of the data packet of the target service in the source node device of the access network is the sending number of the data packet of the target service in the source node device of the access network
  • the sending number of the data packet of the target service in the target node device of the access network is the sending number of the data packet of the target service in the target node device of the access network
  • the above-mentioned target correspondence is a mapping relationship between the serial number determined by the core network node device for the data packet of the target service and the serial number of the data packet of the target service in the access network node device.
  • the source node device indicates that the core network numbers of data packets 1/2/3 are GTP-U SN-1/2/3 respectively, and the corresponding source node device number is PDCP COUNT-1/2/3.
  • the core network node device has the same core network number for the same data packet that the broadcast data is sent to the source node device and the target node device.
  • the target node device receives the data packet GTP-US SN-1/2/3 from the core network node device, and receives the UE's multicast data packet from the UE side, the reception status is: PDCP COUNT-1 is received arrives, and the data packet of PDCP COUNT-2/3 has not been received, then the target node device knows that the data is received from the core network node device according to the corresponding relationship between the core network number and the access network number (that is, the above-mentioned target corresponding relationship). The packet GTP-U SN-1 has been successfully received, and the target node device sends the data packet GTP-U SN-2/3 received from the core network node device to the UE.
  • the source cell when the source cell receives the target service, according to the data packet information of the target service from the source node device, the UE information and the core network information collected by the target node device, the The data packets sent to the UE are sent, which not only avoids the repeated transmission of these data packets, but also avoids the loss of these data packets.
  • the execution body may be a data transmission device, or a control module in the data transmission device for executing the data transmission method.
  • the data transmission device provided by the embodiment of the present application is described by taking the data transmission method performed by the data transmission device as an example.
  • the data transmission apparatus 500 provided by an embodiment of the present application may include: an execution module 501, wherein:
  • the execution module 501 is configured to perform a first target operation on the bearer of the source cell, and perform a second target operation on the bearer of the target cell when the mobility management command is received and the target service is received through the source cell; wherein, The above-mentioned mobility management command is used to instruct the above-mentioned target cell to receive the above-mentioned target service;
  • the above-mentioned first target operation includes: processing the buffered data in the bearer of the above-mentioned source cell and delivering it to the upper layer in sequence;
  • the above-mentioned second target operation includes: A protocol entity corresponding to the bearer of the target cell is established or re-established when a predetermined condition is satisfied; the predetermined condition includes: after the first target operation is performed, or after the mobility management command is received.
  • the above-mentioned first target operation further includes: deleting the PDCP entity carried by the above-mentioned source cell.
  • the above mobility management command includes any one of the following: a handover command, a secondary cell group SCG change command, an SCG addition command, and an SCG deletion command.
  • the above-mentioned execution module 501 is further configured to buffer the data packets received by the bearer of the target cell before the first target operation is performed on the bearer of the source cell; the above-mentioned execution module 501 is further configured to: After the first target operation is performed on the bearer of the source cell, the data packet received by the bearer of the target cell is delivered to the upper layer.
  • the above-mentioned apparatus 500 further includes: a sending module 502, wherein: the sending module 502 is configured to send the data packet information of the above-mentioned target service received from the bearer of the above-mentioned source cell, through the above-mentioned target service The bearer of the cell is sent to the network side device.
  • the above-mentioned data packet information includes at least one of the following: the number of the first lost data packet, the number of the last received data packet, and the bitmap indication of the received data packet. ; wherein, the above bitmap indication is used to indicate whether the corresponding data packet is successfully received.
  • the UE when the UE receives the mobility management command and receives the target service through the source cell, the UE performs the first target operation on the bearer of the source cell (that is, the first target operation in the bearer of the source cell). Cache the data for processing and submit it to the upper layer in order), and perform the second target operation on the bearer of the target cell (that is, the UE establishes or re-establishes the bearer corresponding to the target cell after performing the first target operation or receiving the mobility management command. agreement entity).
  • the UE can process the data carried by the target cell after processing the data carried by the source cell, which not only avoids the repeated transmission of data packets of the target service, but also avoids the loss of data packets and improves the energy efficiency of the communication system. .
  • a data transmission apparatus 600 provided by an embodiment of the present application may include: an execution module 601, wherein: the execution module is used for, during the mobility management process, When the target service is received through the source cell, a third target operation is performed; wherein the third target operation is used to indicate the target service to the target node device.
  • the above-mentioned third target operation includes at least one of the following:
  • the bearer identifier of the target service is indicated to the target node device.
  • the service information of the above-mentioned target service includes at least one of the following:
  • Service identifier Service identifier, service name, service explanation, service characteristics, service sending address, service sending protocol, session identifier, service type indication, and scheduling identifier.
  • the bearer identifier of the above-mentioned target service includes at least one of the following:
  • the tunnel identifier between the source node device and the core network node device
  • the logical channel identifier of the source node is the logical channel identifier of the source node.
  • the data packet information of the above-mentioned target service includes at least one of the following: the number of the last data packet sent, the number of the last successfully sent data packet, and the last data packet that was not sent successfully.
  • the above target correspondence includes: the core network node device is the data packet of the above target service The mapping relationship between the determined number and the number of the data packet of the target service in the access network node device; the above-mentioned bitmap indication is used to indicate whether the corresponding data packet is successfully received.
  • the above-mentioned forwarding of the data packet of the above-mentioned target service to the above-mentioned target node device includes at least one of the following:
  • the target correspondence is a mapping relationship between the serial number determined by the core network node device for the data packet of the target service and the serial number of the target service data packet in the access network node device.
  • the target node equipment in the process of mobility management, when the source cell receives the target service, the target node equipment is notified of the data packet information of the target service, so that the target node equipment has not yet sent the data.
  • the data packets to the UE are sent, so as not only to avoid the repeated transmission of these data packets, but also to avoid the loss of these data packets.
  • a data transmission apparatus provided by an embodiment of the present application may include: an execution module 701, wherein:
  • the execution module 701 is configured to, in the mobility management process, in the case of receiving the target service through the source cell, according to the data packet information of the target service, send the data packet of the target service to the user equipment UE through the bearer of the target cell .
  • the data packet information of the above-mentioned target service includes at least one of the following:
  • the source cell indicated by the UE bears the received data packet information of the target service
  • the data packet information of the target service indicated by the source node device to the target node device.
  • the data packet information of the target service indicated by the source node device to the target node device includes at least one of the following:
  • the source node device forwards the data packet of the target service to the number information carried by the target node device;
  • the above numbering information includes at least one of the following:
  • the target correspondence is a mapping relationship between the serial number determined by the core network node device for the data packet of the target service and the serial number of the target service data packet in the access network node device.
  • the data transmission apparatus in the process of mobility management, when the source cell receives the target service, the data packet information of the target service from the source node device, UE information and The information of the core network is used to send the data packets that have not been sent to the UE, which not only avoids the repeated transmission of these data packets, but also avoids the loss of these data packets.
  • the data transmission device in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the data transmission device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the data transmission apparatus provided in the embodiments of the present application can implement each process implemented by the method embodiments in FIG. 2 to FIG. 4 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • an embodiment of the present application further provides a communication device 800, including a processor 801, a memory 802, a program or instruction stored in the memory 802 and executable on the processor 801,
  • a communication device 800 including a processor 801, a memory 802, a program or instruction stored in the memory 802 and executable on the processor 801,
  • the communication device 800 is a terminal
  • the program or instruction is executed by the processor 801
  • each process of the above-mentioned data transmission method embodiment shown in FIG. 2 can be implemented, and the same technical effect can be achieved.
  • the communication device 800 is a node device, when the program or instruction is executed by the processor 801, each process of the data transmission method embodiment shown in FIG. 3 or FIG. 4 is implemented, and the same technical effect can be achieved. In order to avoid repetition, I won't go into details here.
  • FIG. 9 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 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, and a processor 910 and other components .
  • the terminal 900 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 910 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 9 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 904 may include a graphics processor (Graphics Processing Unit, GPU) 9041 and a microphone 9042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 907 includes a touch panel 9071 and other input devices 9072 .
  • the touch panel 9071 is also called a touch screen.
  • the touch panel 9071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 901 receives the downlink data from the network side device, and then processes it to the processor 910; in addition, sends the uplink data to the network side device.
  • 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.
  • Memory 909 may be used to store software programs or instructions as well as various data.
  • the memory 909 may mainly include a stored program or instruction area and a stored data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 909 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 910 may include one or more processing units; optionally, the processor 910 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 910.
  • the processor 910 is configured to perform the first target operation on the bearer of the source cell, and perform the second target operation on the bearer of the target cell when the mobility management command is received and the source cell receives the target service; wherein , the mobility management command is used to instruct the target cell to receive the target service;
  • the first target operation includes: a first operation;
  • the first operation is: process the buffered data in the bearer of the source cell and sequentially Submit to the upper layer;
  • the second target operation includes: establishing or re-establishing a protocol entity corresponding to the bearer of the target cell when a predetermined condition is met;
  • the predetermined condition includes: after the first target operation is performed, or receiving the mobile after sex management orders.
  • the above-mentioned first target operation further includes: a second operation, where the above-mentioned second operation is: deleting the PDCP entity carried by the above-mentioned source cell.
  • the above mobility management command includes any one of the following: a handover command, a secondary cell group SCG change command, an SCG addition command, and an SCG deletion command.
  • the above-mentioned processor 910 is further configured to cache the data packets received by the bearer of the above-mentioned target cell until the above-mentioned first target operation is performed on the above-mentioned bearer of the above-mentioned source cell, and then store the above-mentioned bearer.
  • the data packets received by the bearer of the target cell are delivered to the upper layer.
  • the radio frequency unit 901 is configured to send the data packet information of the target service received from the bearer of the source cell to the network side device through the bearer of the target cell.
  • the above-mentioned data packet information includes at least one of the following: the number of the first lost data packet, the number of the last received data packet, and the bitmap indication of the received data packet. ; wherein, the above bitmap indication is used to indicate whether the corresponding data packet is successfully received.
  • the terminal when the terminal receives the mobility management command and the source cell receives the target service, the terminal is allowed to perform the first target operation on the bearer of the source cell (that is, the buffered data in the bearer of the source cell is processed by the terminal). process and submit them to the upper layer in order), and perform the second target operation on the bearer of the target cell (that is, the terminal establishes or re-establishes the protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command) .
  • the first target operation on the bearer of the source cell that is, the buffered data in the bearer of the source cell is processed by the terminal. process and submit them to the upper layer in order
  • the second target operation on the bearer of the target cell that is, the terminal establishes or re-establishes the protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command
  • the terminal can process the data carried by the target cell after processing the data carried by the source cell, which not only avoids the repeated transmission of data packets of the target service, but also avoids the loss of data packets, and improves the energy efficiency of the communication system. .
  • an embodiment of the present application further provides a node device.
  • the node device 100 includes: an antenna 101 , a radio frequency device 102 , and a baseband device 103 .
  • the antenna 101 is connected to the radio frequency device 102 .
  • the radio frequency device 102 receives information through the antenna 101, and sends the received information to the baseband device 103 for processing.
  • the baseband device 103 processes the information to be sent and sends it to the radio frequency device 102
  • the radio frequency device 102 processes the received information and sends it out through the antenna 101 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 103 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 103 , where the baseband apparatus 103 includes a processor 104 and a memory 105 .
  • the baseband device 103 may include, for example, at least one baseband board on which multiple chips are arranged. As shown in FIG. 10 , one of the chips is, for example, the processor 104 , which is connected to the memory 105 to call a program in the memory 105 to execute The node devices shown in the above method embodiments operate.
  • the baseband device 103 may further include a network interface 106 for exchanging information with the radio frequency device 102, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the node in this embodiment of the present invention further includes: an instruction or program stored on the memory 105 and executable on the processor 104, and the processor 104 invokes the instruction or program in the memory 105 to execute each of the instructions shown in FIG. 3 or FIG. 4 .
  • the method implemented by the module achieves the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing data transmission method embodiment can be achieved, and the same can be achieved. In order to avoid repetition, the technical effect will not be repeated here.
  • the processor is the processor in the terminal 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), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where 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 network-side device program or instruction to implement the above data transmission method
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network-side device program or instruction to implement the above data transmission method
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including 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 this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

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

Abstract

本申请公开了一种数据传输方法、装置及设备，其中，该方法包括：在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；上述移动性管理命令用于指示在目标小区接收目标业务；上述第一目标操作包括：将源小区的承载中的缓存数据进行处理并按序递交到高层；上述第二目标操作包括：在满足预定条件时建立或重建立目标小区的承载对应的协议实体；上述预定条件包括：执行完第一目标操作之后，或，接收到移动性管理命令之后。

Description

数据传输方法、装置及设备
相关申请的交叉引用
本申请主张在2020年07月14日在中国提交的中国专利申请号202010677289.6的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种数据传输方法、装置及设备。
背景技术
双连接是指UE可以在两个小区组(即，主小区组(Master Cell Group，MCG)和辅小区组(Secondary Cell Group，SCG))同时建立连接。其中，MCG至少包括主小区(Primary Cell，PCell)，可能还包括至少一个辅小区(Secondary Cell，SCell)；SCG至少包括主辅小区(Primary Secondary Cell，PSCell)，可能还包括至少一个SCell。在双连接移动过程中(如，切换或辅小区组切换(SCG change))，UE可以同时在源小区和目标小区建立连接，然后，UE释放与源小区间的连接，仅仅保持与目标小区间的连接。
然而，在双连接移动性管理过程中，由于如果UE从一个小区切换到另外一个小区，则很有可能出现业务数据接收不连续和业务数据丢包的现象。
发明内容
本申请实施例的目的是提供一种数据传输方法、装置及设备，能够解决双连接移动性管理过程中所出现的业务数据接收不连续和业务数据丢包的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种数据传输方法，应用于UE，该方法包括：在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对上述源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；其中，上述移动性管理命令用于指示在上述目标小区接收上述目标业务；上述第一目标操作包括：将上述源小区的承载中的缓存数据进行处理并按序递交到高层；上述第二目标操作包括：在满足预定条件时建立或重建立上述目标小区的承载对应的协议实体；上述预定条件包括：执行完上述第一目标操作之后，或，接收到上述移动性管理命令之后。
第二方面，提供了一种数据传输方法，应用于源节点设备，该方法包括：在移动性管理过程中，在通过源小区接收目标业务的情况下，执行第三目标操作；其中，上述第三目标操作用于向目标节点设备指示上述目标业务。
第三方面，提供了一种数据传输方法，应用于目标节点设备，该方法包括：在移动性管理过程中，在通过源小区接收目标业务的情况下，根据上述目标业务的数据包信息，将上述目标业务的数据包通过目标小区的承载发送至UE。
第四方面，提供了一种数据传输装置，该装置包括：执行模块，用于在接收到移 动性管理命令、且通过源小区接收目标业务的情况下，对源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；其中，上述移动性管理命令用于指示在上述目标小区接收上述目标业务；上述第一目标操作包括：将上述源小区的承载中的缓存数据进行处理并按序递交到高层；上述第二目标操作包括：在满足预定条件时建立或重建立上述目标小区的承载对应的协议实体；上述预定条件包括：执行完上述第一目标操作之后，或，接收到上述移动性管理命令之后。
第五方面，提供了一种数据传输装置，该装置包括：执行模块，用于在移动性管理过程中，在通过源小区接收目标业务的情况下，执行第三目标操作；其中，上述第三目标操作用于向目标节点设备指示上述目标业务。
第六方面，提供了一种数据传输装置，该装置包括：发送模块，用于在移动性管理过程中，在通过源小区接收目标业务的情况下，根据上述目标业务的数据包信息，将上述目标业务的数据包通过目标小区的承载发送至UE。
第七方面，提供了一种UE，该UE包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第八方面，提供了一种节点设备，该节点设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面或第三方面所述的方法的步骤。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面或第三方面所述的方法的步骤。
第十方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法，或实现如第二方面或第三方面所述的方法。
在本申请实施例中，在UE接收到移动性管理命令、且通过源小区接收目标业务的情况下，让UE对源小区的承载执行第一目标操作(即将源小区的承载中的缓存数据进行处理并按序递交到高层)，对目标小区的承载执行第二目标操作(即UE在执行完第一目标操作或接收到移动性管理命令之后建立或重建立目标小区的承载对应的协议实体)。如此，UE便可在处理完源小区的承载的数据后再处理目标小区的承载的数据，不仅避免了目标业务的数据包的重复发送，还避免了数据包的丢失，提高了通信系统的能效。
附图说明
图1是本申请实施例提供的数据传输方法所应用的通信系统的架构图；
图2是本申请实施例提供的一种数据传输方法的方法流程图之一；
图3是本申请实施例提供的一种数据传输方法的方法流程图之二；
图4是本申请实施例提供的一种数据传输方法的方法流程图之三；
图5是本申请实施例提供的一种数据传输装置的结构示意图之一；
图6是本申请实施例提供的一种数据传输装置的结构示意图之二；
图7是本申请实施例提供的一种数据传输装置的结构示意图之三；
图8是本申请实施例提供的一种通信设备的结构示意图；
图9是本申请实施例提供的一种终端的结构示意图；
图10是本申请实施例提供的一种节点设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
以下将对本申请实施例涉及的技术术语进行解释说明：
1、多媒体广播多播业务(Multimedia Broadcast and Multicast Service，MBMS)或广播多播业务(Multicast Broadcast Service，MBS)
在LTE系统中，MBMS/MBS业务可以通过以下两种方式发送：
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通过G-RNTI PDCCH调度的PDSCH发送。
MBS业务是通过特定的MRB(MBMS Radio Bearer)无线承载进行发送的。其中，上述MBS业务可以通过以下标识标记：临时移动组标识(Temporary Mobile Group Identity，TMGI)，QoS flow ID。
核心网节点当采用多播方式给基站发送多播业务数据的时候，核心网节点会将相同的业务数据同时发送给多个基站。
2、单播
UE的单播接收是通过特定的单播数据无线承载(DRB(Data Radio Bearer))进行接收的。其中5G，单播发送(或接收)的协议栈从上至下依次包括：业务数据适配协议(Service Data Adaptation Protocol，SDAP)，包数据汇聚协议(Packet Data Convergence Protocol，PDCP)，无线链路控制(Radio Link Control，RLC)，媒体接入控制(Medium Access Control，MAC)。
3、DC
UE可以在两个小区组(即，主小区组(Master Cell Group，MCG)和辅小区组(Secondary Cell Group，SCG))同时建立连接。其中，MCG包括主小区(Primary Cell，PCell)和辅小区(Secondary Cell，SCell)，SCG包括主辅小区(Primary Secondary Cell，PSCell)和SCell。应注意的是，PCell和PSCell又都可以称为SpCell(Special Cell，特殊小区)。
4、其他术语
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种通信系统的系统架构图。该通信系统包括终端11和网络侧设备12。
示例性的，网络侧设备12可以服务至少一个小区群(如MCG或SCG)。其中，一个MCG中至少包括一个PCell，可能还包括至少一个SCell；一个MCG中至少包括一个PSCell，可能还包括至少一个SCell。
示例性的，上述网络侧设备包括节点设备，该节点设备包括源节点设备和目标节点设备。
示例性的，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、 无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的数据传输方法进行详细地说明。
本申请实施例提供的一种数据传输方法，该数据传输方法可以应用于UE，换言之，该数据传输方法可以由安装在UE中的软件或硬件来执行。如图2所示，本申请实施例提供的数据传输方法可以包括下述的步骤201。
步骤201：在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作。
在本申请实施例中，上述的目标业务包括单播业务和/或多播业务。
示例性的，当UE在源小区通过单播承载或多播承载接收多播业务的时候，UE接收到网络侧设备发送的移动性管理命令，且该移动性管理命令中UE在目标小区是通过单播承载或多播承载接收该多播业务的时候，会对源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作。
在本申请实施例中，本申请实施例提供的数据传输方法应用于双链接移动性管理过程中。其中，上述双连接移动性管理过程包括切换过程或SCG变更过程(即SCG change过程)。即，当UE变更其服务小区的时候，同时建立与源小区和目标小区的连接，然后，释放与源小区间的连接，仅仅保持与目标小区间的连接。如，切换过程中UE的PCell服务小区从小区1变更为小区2，UE在变更过程中同时建立与小区1和小区2的连接，然后释放与小区1间的连接，仅保持与小区2间的连接。
在本申请实施例中，上述移动性管理命令用于指示在目标小区接收目标业务。示例性的，上述移动性管理命令包括以下任一项：切换命令，辅小区组SCG变更命令，SCG添加命令，SCG删除命令。
在一种示例中，上述切换命令用于指示变更PCell。上述SCG变更命令用于指示变更SCG(如，PSCell change)，此时，源小区为源SCG的小区，目标小区为目标SCG的小区)。上述SCG添加命令用于指示添加SCG(如，PSCell addition)，此时，源小区为MCG的小区，目标小区为SCG的小区。上述SCG删除命令用于指示删除SCG(如，PSCell release)，此时，源小区为SCG的小区，目标小区为MCG的小区。
在本申请实施例中，上述第一目标操作包括：第一操作，该第一操作为：将所述源小区的承载中的缓存数据进行处理并按序递交到高层。上述第二目标操作包括：在满足预定条件时建立或重建立目标小区的承载对应的协议实体；上述预定条件包括：执行完所述第一目标操作之后，或，接收到所述移动性管理命令之后。
需要说明的是，上述第一目标操作可以是预定义的、协议规定的或网络侧指示的，本申请实施例对此不做限定。同理，上述第二目标操作可以是预定义的、协议规定的或网络 侧指示的，本申请实施例对此不做限定。
可选地，在本申请实施例中，上述第一目标操作还包括：第二操作，上述第二操作为：删除源小区的承载的PDCP实体。
可以理解，UE根据网络侧指示或协议约定，对于源小区的承载执行如下任一种处理行为：
源小区的承载的处理行为1：UE将该源小区的承载的PDCP实体中的缓存数据进行处理并按顺序递交到高层后，UE删除该源小区的承载的PDCP实体。
源小区的承载的处理行为2：UE将该源小区的承载的PDCP实体中的缓存数据进行处理并按顺序递交到高层。
可以理解，UE根据网络侧指示或协议约定，对目标小区的承载执行如下任一种处理行为：
目标小区的承载的处理行为1：在接收到移动性管理命令后建立或重建立目标小区承载对应的协议实体。例如，UE在接收到移动性管理命令后，在对源小区的单播承载进行处理的过程中，同时UE建立或重建立目标小区承载的PDCP实体。
目标小区的承载的处理行为2：在执行完“源小区承载的处理行为1”或“源小区承载的处理行为2”之后，建立或重建立目标小区承载对应的协议实体。例如，UE在接收到移动性管理命令后，UE先通过对于源小区承载进行处理，该源小区承载的缓存数据都处理完成后，UE才开始建立或重建立目标小区承载的PDCP实体，从而保证接收数据的按顺递交。
可选地，在本申请实施例中，上述源小区的承载的数据的数据类型可以包括以下至少一项：PDCP(Packet Data Convergence Protocol，包数据汇聚协议)层数据包，PDCP层控制包，PDCP层数据。即上述源小区的承载的数据可以包括以下至少一种：承载的PDCP层数据包，承载的PDCP层控制包，承载的PDCP层数据。其中，上述的PDCP层数据包可以为PDCP Data PDU，上述的PDCP层控制包可以为PDCP control PDU(如，鲁棒头压缩(Robust Header Compression，ROHC)反馈包)，上述的PDCP层数据可以为PDCP PDU。
在一种示例中，上述PDCP层数据(如，PDCP PDU)包括但不限于：信令无线承载(Signalling Radio Bearers，SRB)控制包、SRB数据包、数据无线承载(Date Radio Bearers，SRB)控制包、DRB数据包、PDCP控制包以及PDCP数据包。
同理，上述目标小区的承载的数据的数据类型也可以包括上述数据类型，此处，不在赘述。
可选地，在本申请实施例中，本申请实施例提供的数据传输方法，还可以包括如下步骤201a1和步骤201a2：
步骤201a1：对源小区的承载执行完第一目标操作之前，将目标小区的承载接收到的数据包缓存。
步骤201a2：对源小区的承载执行完第一目标操作之后，将目标小区的承载接收到的数据包递交至高层。
示例性的，针对上述“目标小区的承载的处理行为1”，UE可以将从“目标小区的承载”接收到的数据包缓存，直到“源小区的承载”的数据都处理完成后(如，将所有缓存的数据包都递交到高层协议实体后，或将“源小区的承载”删除后)，才开始将从“目标小区的承载”接收到的数据包递交到高层协议实体。
可选地，在本申请实施例中，本申请实施例提供的数据传输方法，还可以包括如下步骤201b：
步骤201b：将从源小区的承载接收到的目标业务的数据包信息，通过目标小区的承载发送至网络侧设备。
进一步可选地，在本申请实施例中，上述数据包信息包括以下至少一项：第一个丢失的数据包的编号，最后一个接收到的数据包的编号，接收到的数据包的比特图指示；其中，上述比特图指示用于指示相应数据包是否接收成功。
示例性的，UE将从“源小区的承载”接收到的数据包的数据包信息(如，第一个丢失的数据包的编号，和/或，最后一个接收到的数据包的编号，和/或，接收到的数据包的比特图指示(每bit指示一个特定编号的数据包是否接收成功))，通过“目标小区的承载”发送给网络侧设备。
如此，在UE接收到移动性管理命令、且通过源小区接收目标业务的情况下，让UE对源小区的承载执行第一目标操作(即将源小区的承载中的缓存数据进行处理并按序递交到高层)，对目标小区的承载执行第二目标操作(即UE在执行完第一目标操作或接收到移动性管理命令之后建立或重建立目标小区的承载对应的协议实体)。如此，UE便可在处理完源小区的承载的数据后再处理目标小区的承载的数据，不仅避免了目标业务的数据包的重复发送，还避免了数据包的丢失，提高了通信系统的能效。
本申请实施例提供的一种数据传输方法，该数据传输方法可以应用于源节点设备，换言之，该数据传输方法可以由安装在源节点设备中的软件或硬件来执行。如图3所示，本申请实施例提供的数据传输方法可以包括步骤301。
步骤301：在移动性管理过程中，在通过源小区接收目标业务的情况下，执行第三目标操作。
其中，上述第三目标操作用于向目标节点设备指示目标业务。
可选地，在本申请实施例中，上述第三目标操作包括以下至少一项：
将目标业务的数据包信息通知给目标节点设备；
将目标业务的数据包转发给目标节点设备；
向目标节点设备指示该目标业务的业务信息；
向目标节点设备指示该目标业务的承载标识。
可选地，在本申请实施例中，上述目标业务的业务信息包括以下至少一项：业务标识(如，TMGI)，业务名称(如，XX电视台)，业务解释(如，多播业务发布渠道(如，通过广电网络发送的中央电视台节目)，多播业务特征(如，语音，或视频))，业务的发送地址(如，TCP和/或IP地址，以及该地址对应的发送端口号)，业务的发送协议(如， 超文本传输协议(Hypertext Transport Protocol，HTTP)，或简单消息传输协议(Simple Message Transfer Protocol，SMTP))，会话标识(如，MBS session-1)，业务类型指示(如，多播业务或单播业务)，调度标识(如，MBS RNTI-1)。
可选地，在本申请实施例中，上述目标业务的承载标识包括以下至少一项：
源节点设备与核心网节点设备间的隧道标识(如，GTP-U Tunnel-1)；
数据流标识(如，QoS flow-1)；
会话标识(如，PDU Session-1)；
源节点的无线承载标识(如，DRB-1)；
源节点的逻辑信道标识(如，LCID-1)。
可选地，在本申请实施例中，上述目标业务的数据包信息包括以下至少一项：最后一个发送的数据包的编号(如，GTP SN＝1的数据包发送了，但是还没有收到UE的成功接收反馈)，最后一个成功发送的数据包的编号(如，GTP SN＝1的数据包发送了，且收到UE的成功接收反馈)，最后一个未发送成功的数据包的编号(如，GTP SN＝1的数据包发送了，且收到UE的没有成功接收的反馈)，第一个未发送成功的数据包的编号(如，GTP SN＝1的数据包发送了，且收到UE的没有成功接收的反馈))，下一个发送的数据包的编号(如，GTP SN＝1在源节点设备还没有被发送，源节点设备希望在目标节点设备下一个要发送给UE的数据包的编号为GTP SN＝1)，比特图指示(如，比特1/2/3分别代表GTP SN＝1/2/3，bit-1取值1代表GTP SN-1数据包接收到了，bit-2/3取值0代表GTP SN-2/3的数据包没有接收)，目标对应关系(如，数据包1/2/3的核心网编号为GTP-U SN-1/2/3，且对应的源节点的编号为PDCP COUNT-1/2/3，两者编号间存在对应关系)。
其中，上述目标对应关系包括：核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在接入网节点设备的编号间的映射关系。上述比特图指示用于指示相应数据包的发送状态，可以理解，上述比特图指示用于指示相应数据包是否接收成功。
应注意的是，上述“承载的目标业务的数据包信息”中的数据包的编号的编号方式主要包括以下两种编号方式：
编号方式1：由核心网节点设备确定数据包的编号。例如，核心网节点设备(如，UPF)将多播业务的数据包发送给基站(如，gNB)的时候，该数据包携带编号信息(如，携带在GTP-U tunnel的包头中)。
编号方式2：由接入网的节点设备(如源节点设备和目标节点设备)确定数据包的编号。例如，源节点设备的PDCP实体确定的PDCP SN或COUNT。
可选地，在本申请实施例中，上述源节点设备将目标业务的数据包转发给目标节点设备的行为，包括以下至少一项：
指示核心网节点设备为所述目标业务的数据包确定的编号(即指示转发的目标业务的数据包的核心网节点设备确定的编号，如，数据包1/2/3的核心网编号为GTP-U SN-1/2/3)；
指示目标业务的数据包在接入网的源节点设备的发送编号(即指示转发的目标业务的数据包在接入网的源节点设备的发送编号，如，转发了数据包1/2/3，并指示数据包1/2/3 在源节点设备的编号为PDCP COUNT-1/2/3)；
指示目标业务的数据包在接入网的目标节点设备的发送编号(指示转发的目标业务的数据包在接入网的目标节点设备的发送编号，例1：转发了数据包1/2/3，并指示数据包1/2/3在目标节点设备的编号为PDCP COUNT-1/2/3；例2：转发了数据包1/2/3，并指示数据包1/2/3在目标节点设备的其起始编号为PDCP COUNT-1)；
指示目标对应关系(即，指示转发的目标业务的数据包的“核心网节点设备确定的编号”与“接入网的节点设备的发送编号”的对应关系，如，数据包1/2/3的核心网编号为GTP-U SN-1/2/3，且对应的源节点的编号为PDCP COUNT-1/2/3)。
其中，上述目标对应关系为核心网节点设备为目标业务的数据包确定的编号与目标业务的数据包在接入网的节点设备的编号间的映射关系。
如此，在移动性管理过程中，在通过源小区接收目标业务的情况下，通过将目标业务的数据包信息通知给目标节点设备，从而使得目标节点设备对还未发送给UE的数据包进行发送，这样不仅避免这些数据包的重复发送，还避免了这些数据包的丢失。
本申请实施例提供的一种数据传输方法，该数据传输方法可以应用于源节点设备，换言之，该数据传输方法可以由安装在源节点设备中的软件或硬件来执行。如图4所示，本申请实施例提供的数据传输方法可以包括下述的步骤401。
步骤401：在移动性管理过程中，在通过源小区接收目标业务的情况下，根据目标业务的数据包信息，将目标业务的数据包通过目标小区的承载发送至UE。
可选地，在本申请实施例中，上述目标业务的数据包信息包括以下至少一项：
UE指示的源小区承载接收到的目标业务的数据包信息，
源节点设备向目标节点设备指示的目标业务的数据包信息。
可选地，在本申请实施例中，上述源节点设备向目标节点设备指示的目标业务的数据包信息包括以下至少一项：
源节点设备通知给目标节点设备的该目标业务的数据包信息；
目标业务的业务信息；
目标业务的承载标识；
源节点设备将目标业务的数据包转发给目标节点设备携带的编号信息。
示例性的，上述编号信息包括以下至少一项：
核心网节点设备为该目标业务的数据包确定的编号；
目标业务的数据包在接入网的源节点设备的发送编号；
目标业务的数据包在接入网的目标节点设备的发送编号；
目标对应关系。
其中，上述目标对应关系为核心网节点设备为目标业务的数据包确定的编号与该目标业务的数据包在接入网的节点设备的编号间的映射关系。
需要说明的是，上述内容中与上文描述相同的技术术语的解释，可以参见上文描述，此处不再赘述。
举例说明，源节点设备指示数据包1/2/3的核心网编号分别为GTP-U SN-1/2/3，且对应的源节点设备的编号为PDCP COUNT-1/2/3。核心网节点设备对于广播数据发送给源节点设备和目标节点设备的相同数据包的核心网编号相同。此时，若目标节点设备从核心网节点设备接收到数据包GTP-U SN-1/2/3，并且从UE侧接收到UE的多播数据包的接收状态为：PDCP COUNT-1被接收到了、且PDCP COUNT-2/3的数据包还没有接收到，则，目标节点设备根据核心网编号和接入网编号的对应关系(即上述目标对应关系)知道从核心网节点设备接收到数据包GTP-U SN-1已经被接收成功了，则目标节点设备将从核心网节点设备接收到的数据包GTP-U SN-2/3发送给UE。
如此，在移动性管理过程中，在源小区接收目标业务的情况下，根据目标节点设备收集到的来自源节点设备的目标业务的数据包信息、UE的信息以及核心网的信息，对还未发送给UE的数据包进行发送，这样不仅避免这些数据包的重复发送，还避免了这些数据包的丢失。
需要说明的是，本申请实施例提供的数据传输方法，执行主体可以为数据传输装置，或者，该数据传输装置中的用于执行数据传输方法的控制模块。本申请实施例中以数据传输装置执行数据传输方法为例，说明本申请实施例提供的数据传输装置。
本申请实施例提供的一种数据传输装置，如图5所示，本申请实施例提供的数据传输装置500可以包括：执行模块501，其中：
执行模块501，用于在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对上述源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；其中，上述移动性管理命令用于指示在上述目标小区接收上述目标业务；上述第一目标操作包括：将上述源小区的承载中的缓存数据进行处理并按序递交到高层；上述第二目标操作包括：在满足预定条件时建立或重建立上述目标小区的承载对应的协议实体；上述预定条件包括：执行完上述第一目标操作之后，或，接收到上述移动性管理命令之后。
可选地，在本申请实施例中，上述第一目标操作还包括：删除上述源小区的承载的PDCP实体。
可选地，在本申请实施例中，上述移动性管理命令包括以下任一项：切换命令，辅小区组SCG变更命令，SCG添加命令，SCG删除命令。
可选地，在本申请实施例中，上述执行模块501，还用于对源小区的承载执行完第一目标操作之前，将目标小区的承载接收到的数据包缓存；上述执行模块501，还用于对上述源小区的承载执行完上述第一目标操作之后，将上述目标小区的承载接收到的数据包递交至高层。
可选地，在本申请实施例中，上述装置500还包括：发送模块502，其中：发送模块502，用于将从上述源小区的承载接收到的上述目标业务的数据包信息，通过上述目标小区的承载发送至网络侧设备。
可选地，在本申请实施例中，上述数据包信息包括以下至少一项：第一个丢失的数据 包的编号，最后一个接收到的数据包的编号，接收到的数据包的比特图指示；其中，上述比特图指示用于指示相应数据包是否接收成功。
本申请实施例提供的数据传输装置，在UE接收到移动性管理命令、且通过源小区接收目标业务的情况下，让UE对源小区的承载执行第一目标操作(即将源小区的承载中的缓存数据进行处理并按序递交到高层)，对目标小区的承载执行第二目标操作(即UE在执行完第一目标操作或接收到移动性管理命令之后建立或重建立目标小区的承载对应的协议实体)。如此，UE便可在处理完源小区的承载的数据后再处理目标小区的承载的数据，不仅避免了目标业务的数据包的重复发送，还避免了数据包的丢失，提高了通信系统的能效。
本申请实施例提供的一种数据传输装置，如图6所示，本申请实施例提供的数据传输装置600可以包括：执行模块601，其中：执行模块，用于在移动性管理过程中，在通过源小区接收目标业务的情况下，执行第三目标操作；其中，上述第三目标操作用于向目标节点设备指示上述目标业务。
可选地，在本申请实施例中，上述第三目标操作包括以下至少一项：
将上述目标业务的数据包信息通知给目标节点设备；
将上述目标业务的数据包转发给上述目标节点设备；
向上述目标节点设备指示上述目标业务的业务信息；
向上述目标节点设备指示上述目标业务的承载标识。
可选地，在本申请实施例中，上述目标业务的业务信息包括以下至少一项：
业务标识，业务名称，业务解释，业务特征，业务的发送地址，业务的发送协议，会话标识，业务类型指示，调度标识。
可选地，在本申请实施例中，上述目标业务的承载标识包括以下至少一项：
源节点设备与核心网节点设备间的隧道标识；
数据流标识；
会话标识；
源节点的无线承载标识；
源节点的逻辑信道标识。
可选地，在本申请实施例中，上述目标业务的数据包信息包括以下至少一项：最后一个发送的数据包的编号，最后一个成功发送的数据包的编号，最后一个未发送成功的数据包的编号，第一个未发送成功的数据包的编号，下一个发送的数据包的编号，比特图指示，目标对应关系；上述目标对应关系包括：核心网节点设备为上述目标业务的数据包确定的编号与上述目标业务的数据包在接入网节点设备的编号间的映射关系；上述比特图指示用于指示相应数据包是否接收成功。
可选地，在本申请实施例中，上述将上述目标业务的数据包转发给上述目标节点设备，包括以下至少一项：
指示核心网节点设备为上述目标业务的数据包确定的编号，
指示上述目标业务的数据包在接入网的源节点设备的发送编号，
指示上述目标业务的数据包在接入网的目标节点设备的发送编号，
指示目标对应关系。
其中，上述目标对应关系为上述核心网节点设备为上述目标业务的数据包确定的编号与上述目标业务的数据包在上述接入网的节点设备的编号间的映射关系。
本申请实施例提供的数据传输装置，在移动性管理过程中，在源小区接收目标业务的情况下，通过将目标业务的数据包信息通知给目标节点设备，从而使得目标节点设备对还未发送给UE的数据包进行发送，这样不仅避免这些数据包的重复发送，还避免了这些数据包的丢失。
本申请实施例提供的一种数据传输装置，如图7所示，本申请实施例提供的数据传输装置700可以包括：执行模块701，其中：
执行模块701，用于在移动性管理过程中，在通过源小区接收目标业务的情况下，根据上述目标业务的数据包信息，将上述目标业务的数据包通过目标小区的承载发送至用户设备UE。
可选地，在本申请实施例中，上述目标业务的数据包信息包括以下至少一项：
UE指示的源小区承载接收到的上述目标业务的数据包信息，
源节点设备向目标节点设备指示的上述目标业务的数据包信息。
可选地，在本申请实施例中，上述源节点设备向目标节点设备指示的上述目标业务的数据包信息包括以下至少一项：
上述源节点设备通知给上述目标节点设备的上述目标业务的数据包信息；
上述目标业务的业务信息；
上述目标业务的承载标识；
上述源节点设备将上述目标业务的数据包转发给上述目标节点设备携带的编号信息；
其中，上述编号信息包括以下至少一项：
核心网节点设备为上述目标业务的数据包确定的编号，
上述目标业务的数据包在接入网的源节点设备的发送编号，
上述目标业务的数据包在接入网的目标节点设备的发送编号，
目标对应关系；
其中，上述目标对应关系为上述核心网节点设备为上述目标业务的数据包确定的编号与上述目标业务的数据包在上述接入网的节点设备的编号间的映射关系。
本申请实施例提供的数据传输装置，在移动性管理过程中，在源小区接收目标业务的情况下，根据目标节点设备收集到的来自源节点设备的目标业务的数据包信息、UE的信息以及核心网的信息，对还未发送给UE的数据包进行发送，这样不仅避免这些数据包的 重复发送，还避免了这些数据包的丢失。
本申请实施例中的数据传输装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的数据传输装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的数据传输装置能够实现图2至图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图8所示，本申请实施例还提供一种通信设备800，包括处理器801，存储器802，存储在存储器802上并可在所述处理器801上运行的程序或指令，例如，该通信设备800为终端时，该程序或指令被处理器801执行时实现上述图2所示的数据传输方法实施例的各个过程，且能达到相同的技术效果。该通信设备800为节点设备时，该程序或指令被处理器801执行时实现上述图3或图4所示的数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图9为实现本申请实施例的一种终端的硬件结构示意图。
该终端900包括但不限于：射频单元901、网络模块902、音频输出单元903、输入单元904、传感器905、显示单元906、用户输入单元907、接口单元908、存储器909、以及处理器910等部件。
本领域技术人员可以理解，终端900还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器910逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图9中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元904可以包括图形处理器(Graphics Processing Unit，GPU)9041和麦克风9042，图形处理器9041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元906可包括显示面板9061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板9061。用户输入单元907包括触控面板9071以及其他输入设备9072。触控面板9071，也称为触摸屏。触控面板9071可包括触摸检测装置和触摸控制器两个部分。其他输入设备9072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元901将来自网络侧设备的下行数据接收后，给处理器910处理；另外，将上行的数据发送给网络侧设备。通常，射频单元901包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器909可用于存储软件程序或指令以及各种数据。存储器909可主要包括存储程 序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器909可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器910可包括一个或多个处理单元；可选的，处理器910可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器910中。
其中，处理器910，用于在接收到移动性管理命令、且源小区接收目标业务的情况下，对上述源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；其中，上述移动性管理命令用于指示在上述目标小区接收上述目标业务；上述第一目标操作包括：第一操作；上述第一操作为：将上述源小区的承载中的缓存数据进行处理并按序递交到高层；上述第二目标操作包括：在满足预定条件时建立或重建立上述目标小区的承载对应的协议实体；上述预定条件包括：执行完上述第一目标操作之后，或，接收到上述移动性管理命令之后。
可选地，在本申请实施例中，上述第一目标操作还包括：第二操作，上述第二操作为：删除上述源小区的承载的PDCP实体。
可选地，在本申请实施例中，上述移动性管理命令包括以下任一项：切换命令，辅小区组SCG变更命令，SCG添加命令，SCG删除命令。
可选地，在本申请实施例中，上述处理器910，还用于将上述目标小区的承载接收到的数据包缓存，直至对上述源小区的承载执行完上述第一目标操作之后，将上述目标小区的承载接收到的数据包递交至高层。
可选地，在本申请实施例中，上述射频单元901，用于将从上述源小区的承载接收到的上述目标业务的数据包信息，通过上述目标小区的承载发送至网络侧设备。
可选地，在本申请实施例中，上述数据包信息包括以下至少一项：第一个丢失的数据包的编号，最后一个接收到的数据包的编号，接收到的数据包的比特图指示；其中，上述比特图指示用于指示相应数据包是否接收成功。
本申请实施例提供的终端，在终端接收到移动性管理命令、且源小区接收目标业务的情况下，让终端对源小区的承载执行第一目标操作(即将源小区的承载中的缓存数据进行处理并按序递交到高层)，对目标小区的承载执行第二目标操作(即终端在执行完第一目标操作或接收到移动性管理命令之后建立或重建立目标小区的承载对应的协议实体)。如此，终端便可在处理完源小区的承载的数据后再处理目标小区的承载的数据，不仅避免了目标业务的数据包的重复发送，还避免了数据包的丢失，提高了通信系统的能效。
具体地，本申请实施例还提供了一种节点设备。如图10所示，该节点设备100包括： 天线101、射频装置102、基带装置103。天线101与射频装置102连接。在上行方向上，射频装置102通过天线101接收信息，将接收的信息发送给基带装置103进行处理。在下行方向上，基带装置103对要发送的信息进行处理，并发送给射频装置102，射频装置102对收到的信息进行处理后经过天线101发送出去。
上述频带处理装置可以位于基带装置103中，以上实施例中网络侧设备执行的方法可以在基带装置103中实现，该基带装置103包括处理器104和存储器105。
基带装置103例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图10所示，其中一个芯片例如为处理器104，与存储器105连接，以调用存储器105中的程序，执行以上方法实施例中所示的节点设备操作。
该基带装置103还可以包括网络接口106，用于与射频装置102交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的节点还包括：存储在存储器105上并可在处理器104上运行的指令或程序，处理器104调用存储器105中的指令或程序执行图3或图4所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡 献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (38)

  1. 一种数据传输方法，所述方法包括：
    用户设备UE在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对所述源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；
    其中，所述移动性管理命令用于指示在所述目标小区接收所述目标业务；
    所述第一目标操作包括：将所述源小区的承载中的缓存数据进行处理并按序递交到高层；
    所述第二目标操作包括：在满足预定条件时建立或重建立所述目标小区的承载对应的协议实体；所述预定条件包括：执行完所述第一目标操作之后，或，接收到所述移动性管理命令之后。
  2. 根据权利要求1所述的方法，其中，所述第一目标操作还包括：删除所述源小区的承载的包数据汇聚协议PDCP实体。
  3. 根据权利要求1所述的方法，其中，所述移动性管理命令包括以下任一项：切换命令，辅小区组SCG变更命令，SCG添加命令，SCG删除命令。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述UE对所述源小区的承载执行完所述第一目标操作之前，将所述目标小区的承载接收到的数据包缓存；
    所述UE对所述源小区的承载执行完所述第一目标操作之后，将所述目标小区的承载接收到的数据包递交至高层。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述UE将从所述源小区的承载接收到的所述目标业务的数据包信息，通过所述目标小区的承载发送至网络侧设备。
  6. 根据权利要求5所述的方法，其中，所述数据包信息包括以下至少一项：第一个丢失的数据包的编号，最后一个接收到的数据包的编号，接收到的数据包的比特图指示；
    其中，所述比特图指示用于指示相应数据包是否接收成功。
  7. 一种数据传输方法，所述方法包括：
    源节点设备在移动性管理过程中，在源小区接收目标业务的情况下，执行第三目标操作；
    其中，所述第三目标操作用于向目标节点设备指示所述目标业务。
  8. 根据权利要求7所述的方法，其中，所述第三目标操作包括以下至少一项：
    将所述目标业务的数据包信息通知给目标节点设备；
    将所述目标业务的数据包转发给所述目标节点设备；
    向所述目标节点设备指示所述目标业务的业务信息；
    向所述目标节点设备指示所述目标业务的承载标识。
  9. 根据权利要求7所述的方法，其中，所述目标业务的业务信息包括以下至少一项：
    业务标识，业务名称，业务解释，业务特征，业务的发送地址，业务的发送协议，会话标识，业务类型指示，调度标识。
  10. 根据权利要求7所述的方法，其中，所述目标业务的承载标识包括以下至少一项：
    源节点设备与核心网节点设备间的隧道标识；
    数据流标识；
    会话标识；
    源节点的无线承载标识；
    源节点的逻辑信道标识。
  11. 根据权利要求7所述的方法，其中，所述目标业务的数据包信息包括以下至少一项：最后一个发送的数据包的编号，最后一个成功发送的数据包的编号，最后一个未发送成功的数据包的编号，第一个未发送成功的数据包的编号，下一个发送的数据包的编号，比特图指示，目标对应关系；
    所述目标对应关系包括：核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在接入网节点设备的编号间的映射关系；
    所述比特图指示用于指示相应数据包是否接收成功。
  12. 根据权利要求8所述的方法，其中，所述将所述目标业务的数据包转发给所述目标节点设备，包括以下至少一项：
    指示核心网节点设备为所述目标业务的数据包确定的编号，
    指示所述目标业务的数据包在接入网的源节点设备的发送编号，
    指示所述目标业务的数据包在接入网的目标节点设备的发送编号，
    指示目标对应关系；
    其中，所述目标对应关系为所述核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在所述接入网的节点设备的编号间的映射关系。
  13. 一种数据传输方法，所述方法包括：
    目标节点设备在移动性管理过程中，在通过源小区接收目标业务的情况下，根据所述目标业务的数据包信息，将所述目标业务的数据包通过目标小区的承载发送至用户设备UE。
  14. 根据权利要求13所述的方法，其中，所述目标业务的数据包信息包括以下至少一项：
    UE指示的源小区承载接收到的所述目标业务的数据包信息，
    源节点设备向目标节点设备指示的所述目标业务的数据包信息。
  15. 根据权利要求14所述的方法，其中，所述源节点设备向目标节点设备指示的所述目标业务的数据包信息包括以下至少一项：
    所述源节点设备通知给所述目标节点设备的所述目标业务的数据包信息；
    所述目标业务的业务信息；
    所述目标业务的承载标识；
    所述源节点设备将所述目标业务的数据包转发给所述目标节点设备携带的编号信息；
    其中，所述编号信息包括以下至少一项：
    核心网节点设备为所述目标业务的数据包确定的编号，
    所述目标业务的数据包在接入网的源节点设备的发送编号，
    所述目标业务的数据包在接入网的目标节点设备的发送编号，
    目标对应关系；
    所述目标对应关系为所述核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在所述接入网的节点设备的编号间的映射关系。
  16. 一种数据传输装置，所述装置包括：
    执行模块，用于在接收到移动性管理命令、且通过源小区接收目标业务的情况下，对所述源小区的承载执行第一目标操作，对目标小区的承载执行第二目标操作；
    其中，所述移动性管理命令用于指示在所述目标小区接收所述目标业务；
    所述第一目标操作包括：将所述源小区的承载中的缓存数据进行处理并按序递交到高层；
    所述第二目标操作包括：在满足预定条件时建立或重建立所述目标小区的承载对应的协议实体；所述预定条件包括：执行完所述第一目标操作之后，或，接收到所述移动性管理命令之后。
  17. 根据权利要求16所述的装置，其中，所述第一目标操作还包括：删除所述源小区的承载的包数据汇聚协议PDCP实体。
  18. 根据权利要求16所述的装置，其中，所述执行模块，还用于：对所述源小区的承载执行完所述第一目标操作之前，将所述目标小区的承载接收到的数据包缓存；
    所述执行模块，还用于：对所述源小区的承载执行完所述第一目标操作之后，将所述目标小区的承载接收到的数据包递交至高层。
  19. 根据权利要求16所述的装置，其中，所述装置还包括：发送模块，其中：
    所述发送模块，用于将从所述源小区的承载接收到的所述目标业务的数据包信息，通过所述目标小区的承载发送至网络侧设备。
  20. 根据权利要求19所述的装置，其中，所述数据包信息包括以下至少一项：第一个丢失的数据包的编号，最后一个接收到的数据包的编号，接收到的数据包的比特图指示；
    其中，所述比特图指示用于指示相应数据包是否接收成功。
  21. 根据权利要求16所述的装置，其中，所述移动性管理命令包括以下任一项：切换命令，辅小区组SCG变更命令，SCG添加命令，SCG删除命令。
  22. 一种数据传输装置，所述装置包括：
    执行模块，用于在移动性管理过程中，在源小区接收目标业务的情况下，执行第三目标操作；
    其中，所述第三目标操作用于向目标节点设备指示所述目标业务。
  23. 根据权利要求22所述的装置，其中，所述第三目标操作包括以下至少一项：
    将所述目标业务的数据包信息通知给目标节点设备；
    将所述目标业务的数据包转发给所述目标节点设备；
    向所述目标节点设备指示所述目标业务的业务信息；
    向所述目标节点设备指示所述目标业务的承载标识。
  24. 根据权利要求22所述的装置，其中，所述目标业务的业务信息包括以下至少 一项：
    业务标识，业务名称，业务解释，业务特征，业务的发送地址，业务的发送协议，会话标识，业务类型指示，调度标识。
  25. 根据权利要求22所述的装置，其中，所述目标业务的承载标识包括以下至少一项：
    源节点设备与核心网节点设备间的隧道标识；
    数据流标识；
    会话标识；
    源节点的无线承载标识；
    源节点的逻辑信道标识。
  26. 根据权利要求22所述的装置，其中，所述目标业务的数据包信息包括以下至少一项：最后一个发送的数据包的编号，最后一个成功发送的数据包的编号，最后一个未发送成功的数据包的编号，第一个未发送成功的数据包的编号，下一个发送的数据包的编号，比特图指示，目标对应关系；
    所述目标对应关系包括：核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在接入网节点设备的编号间的映射关系；
    所述比特图指示用于指示相应数据包是否接收成功。
  27. 根据权利要求22所述的装置，其中，所述将所述目标业务的数据包转发给所述目标节点设备，包括以下至少一项：
    指示核心网节点设备为所述目标业务的数据包确定的编号，
    指示所述目标业务的数据包在接入网的源节点设备的发送编号，
    指示所述目标业务的数据包在接入网的目标节点设备的发送编号，
    指示目标对应关系；
    其中，所述目标对应关系为所述核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在所述接入网的节点设备的编号间的映射关系。
  28. 一种数据传输装置，所述装置包括：
    发送模块，用于在移动性管理过程中，在源小区接收目标业务的情况下，根据所述目标业务的数据包信息，将所述目标业务的数据包通过目标小区的承载发送至用户设备UE。
  29. 根据权利要求28所述的装置，其中，所述目标业务的数据包信息包括以下至少一项：
    UE指示的源小区承载接收到的所述目标业务的数据包信息，
    源节点设备向目标节点设备指示的所述目标业务的数据包信息。
  30. 根据权利要求29所述的装置，其中，所述源节点设备向目标节点设备指示的所述目标业务的数据包信息包括以下至少一项：
    所述源节点设备通知给所述目标节点设备的所述目标业务的数据包信息；
    所述目标业务的业务信息；
    所述目标业务的承载标识；
    所述源节点设备将所述目标业务的数据包转发给所述目标节点设备携带的编号信 息；
    其中，所述编号信息包括以下至少一项：
    核心网节点设备为所述目标业务的数据包确定的编号，
    所述目标业务的数据包在接入网的源节点设备的发送编号，
    所述目标业务的数据包在接入网的目标节点设备的发送编号，
    目标对应关系；
    所述目标对应关系为所述核心网节点设备为所述目标业务的数据包确定的编号与所述目标业务的数据包在所述接入网的节点设备的编号间的映射关系。
  31. 一种UE，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至6中任一项所述的数据传输方法的步骤。
  32. 一种节点设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求7至12中任一项所述的数据传输方法，或者，实现如权利要求13至15中任一项所述的数据传输方法的步骤。
  33. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至6中任一项所述的数据传输方法，或者，实现如权利要求7至12中任一项所述的数据传输方法，或者，实现如权利要求13至15中任一项所述的数据传输方法的步骤。
  34. 一种数据传输装置，被配置成用于执行如权利要求1至6中任一项所述的数据传输方法，或者，如权利要求7至12中任一项所述的数据传输方法，或者，如权利要求13至15中任一项所述的数据传输方法的步骤。
  35. 一种UE，被配置成用于执行如权利要求1至6中任一项所述的数据传输方法。
  36. 一种节点设备，被配置成用于执行如权利要求7至12中任一项所述的数据传输方法，或者，如权利要求13至15中任一项所述的数据传输方法。
  37. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，以实现如权利要求1至6中任一项所述的数据传输方法，或者，如权利要求7至12中任一项所述的数据传输方法，或者，如权利要求13至15中任一项所述的数据传输方法的步骤。
  38. 一种计算机软件产品，所述计算机软件产品被存储在非易失的存储介质中，所述计算机软件产品被配置成被至少一个处理器执行，以实现如权利要求1至6中任一项所述的数据传输方法，或者，如权利要求7至12中任一项所述的数据传输方法，或者，如权利要求13至15中任一项所述的数据传输方法的步骤。
PCT/CN2021/105855 2020-07-14 2021-07-12 数据传输方法、装置及设备 WO2022012480A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010677289.6 2020-07-14
CN202010677289.6A CN113938968B (zh) 2020-07-14 2020-07-14 数据传输方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2022012480A1 true WO2022012480A1 (zh) 2022-01-20

Family

ID=79273956

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/105855 WO2022012480A1 (zh) 2020-07-14 2021-07-12 数据传输方法、装置及设备

Country Status (2)

Country Link
CN (1) CN113938968B (zh)
WO (1) WO2022012480A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175719A1 (en) * 2017-03-22 2018-09-27 Idac Holdings, Inc. System and methods for phased reconfiguration in wireless systems
CN109548107A (zh) * 2019-01-18 2019-03-29 中国科学院上海高等研究院 基于通信网络双连接切换的方法、系统、介质及设备
CN110351896A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 一种连接重建立方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104955064B (zh) * 2014-03-28 2019-01-11 上海诺基亚贝尔股份有限公司 一种在双连接系统中处理用户设备端rlc/pdcp实体的方法与设备
CN108882334B (zh) * 2017-08-11 2019-11-05 华为技术有限公司 一种数据传输方法、核心网用户面设备和源基站
CN110944368A (zh) * 2018-09-25 2020-03-31 电信科学技术研究院有限公司 一种切换过程中传输数据的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175719A1 (en) * 2017-03-22 2018-09-27 Idac Holdings, Inc. System and methods for phased reconfiguration in wireless systems
CN110351896A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 一种连接重建立方法及装置
CN109548107A (zh) * 2019-01-18 2019-03-29 中国科学院上海高等研究院 基于通信网络双连接切换的方法、系统、介质及设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON, CHINA TELECOM: "Introduction of Even further Mobility enhancement in E-UTRAN", 3GPP DRAFT; R2-2001753, vol. RAN WG2, 11 March 2020 (2020-03-11), pages 1 - 92, XP051864492 *
ERICSSON: "User plane aspects of Make-Before-Break", 3GPP DRAFT; R2-1907318, vol. RAN WG2, 2 May 2019 (2019-05-02), Reno, Nevada, USA, pages 1 - 4, XP051711603 *
INTEL CORPORATION: "Report of [108#66][LTE NR Mob] Open issues for LTE and NR mobility (Intel)", 3GPP DRAFT; R2-2000461, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, 14 February 2020 (2020-02-14), Elbonia, pages 1 - 99, XP051849049 *

Also Published As

Publication number Publication date
CN113938968A (zh) 2022-01-14
CN113938968B (zh) 2023-01-31

Similar Documents

Publication Publication Date Title
WO2022089349A1 (zh) Pdcp重复的配置、激活或去激活方法和终端
US20230039646A1 (en) Data retransmission method, data retransmission apparatus, target node, source node, and terminal
US20230422346A1 (en) Multicast service receiving method, multicast service configuration method, terminal, and network side device
WO2022012525A1 (zh) 数据传输方法、数据传输装置、网络侧设备及第一终端
WO2022033560A1 (zh) 上报能力的方法、终端设备和网络设备
WO2022042440A1 (zh) 用户面数据的传输方法和网络节点
TW202224455A (zh) 用於mbs的無線通信的裝置和方法
WO2022012526A1 (zh) 处理方法、发送方法及相关设备
WO2022012480A1 (zh) 数据传输方法、装置及设备
WO2022028463A1 (zh) 多播业务的接收方法、配置方法、终端及网络侧设备
WO2022078394A1 (zh) 多播业务的传输方法、装置及通信设备
WO2021197468A1 (zh) 承载变更方法、网络设备及终端设备
WO2022017480A1 (zh) 管理目标业务的方法、装置和通信设备
WO2022012583A1 (zh) 数据处理方法、数据处理装置及第一终端
WO2022206505A1 (zh) 业务数据处理方法、装置及设备
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
WO2022078393A1 (zh) 多播广播业务的sn同步方法、装置、设备及可读存储介质
WO2022222885A1 (zh) 资源释放方法、装置、网络节点及存储介质
JP7473689B2 (ja) モード切り替え方法、端末及びネットワーク側機器
WO2022206552A1 (zh) 切换方法、装置、网络侧设备及终端
WO2022237619A1 (zh) Rrc消息的传输方法及装置、终端及可读存储介质
CN113596737B (zh) 数据重传方法、装置、目标节点、源节点及终端
WO2023280014A1 (zh) 单播侧链路通信方法、装置及终端
WO2023186138A1 (zh) 一种多播会话/业务的传输方法、装置、芯片及模组设备
WO2023280022A1 (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: 21841472

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21841472

Country of ref document: EP

Kind code of ref document: A1

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

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30.06.23)

122 Ep: pct application non-entry in european phase

Ref document number: 21841472

Country of ref document: EP

Kind code of ref document: A1