CN113938968A - Data transmission method, device and equipment - Google Patents
Data transmission method, device and equipment Download PDFInfo
- Publication number
- CN113938968A CN113938968A CN202010677289.6A CN202010677289A CN113938968A CN 113938968 A CN113938968 A CN 113938968A CN 202010677289 A CN202010677289 A CN 202010677289A CN 113938968 A CN113938968 A CN 113938968A
- Authority
- CN
- China
- Prior art keywords
- target
- data packet
- service
- target service
- cell
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a data transmission method, a data transmission device and data transmission equipment, belongs to the technical field of communication, and can solve the problems of discontinuous service data reception and service data packet loss in a dual-connection mobility management process. The method comprises the following steps: under the condition of receiving a mobility management command and receiving a target service through a source cell, executing a first target operation on a bearer of the source cell and executing a second target operation on the bearer of the target cell; the mobility management command is used for indicating the target cell to receive the target service; the first target operation includes: processing the cache data in the load of the source cell and delivering the cache data to a high layer in sequence; the second target operation includes: establishing or rebuilding a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after a mobility management command is received.
Description
Technical Field
The present application belongs to the field of communications technologies, and in particular, to a data transmission method, apparatus, and device.
Background
Dual connectivity means that the UE can establish a connection in two Cell groups, i.e., a Master Cell Group (MCG) and a Secondary Cell Group (SCG), simultaneously. Wherein, the MCG at least includes a Primary Cell (PCell) and possibly at least one Secondary Cell (SCell); the SCG includes at least a Primary Secondary Cell (PSCell) and possibly at least one SCell. During a dual connectivity mobility procedure (e.g., handover or secondary cell group handover (SCG change)), the UE may establish a connection between the source cell and the target cell at the same time, and then release the connection with the source cell and maintain the connection with the target cell only.
However, in the dual connectivity mobility management process, since if the UE is handed over from one cell to another cell, there is a high possibility that the phenomenon of discontinuous reception of service data and packet loss of service data may occur.
Disclosure of Invention
An object 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 during a dual connectivity mobility management process.
In order to solve the technical problem, the present application is implemented as follows:
in a first aspect, a data transmission method is provided, which is applied to a UE, and includes: under the condition of receiving a mobility management command and receiving a target service through a source cell, executing a first target operation on a bearer of the source cell and executing 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 cache data in the load of the source cell and delivering the cache data to a high layer in sequence; the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
In a second aspect, a data transmission method is provided, which is applied to a source node device, and includes: in the mobility management process, under the condition of receiving the target service through the source cell, executing a third target operation; wherein the third target operation is configured to indicate the target service to a target node device.
In a third aspect, a data transmission method is provided, which is applied to a target node device, and includes: in the process of mobility management, under the condition of receiving a target service through a source cell, sending a data packet of the target service to UE through the load of a target cell according to the data packet information of the target service.
In a fourth aspect, there is provided a data transmission apparatus, comprising: the execution module is used for executing a first target operation on the load bearing of the source cell and executing a second target operation on the load bearing of the target cell under the conditions that the mobility management command is received and the target service is received through the source 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 cache data in the load of the source cell and delivering the cache data to a high layer in sequence; the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
In a fifth aspect, there is provided a data transmission apparatus, comprising: an execution module, configured to execute a third target operation in a mobility management process under a condition that a target service is received through a source cell; wherein the third target operation is configured to indicate the target service to a target node device.
In a sixth aspect, there is provided a data transmission apparatus, comprising: and the sending module is used for sending the data packet of the target service to the UE through the load of the target cell according to the data packet information of the target service under the condition of receiving the target service through the source cell in the mobility management process.
In a seventh aspect, a UE is provided, the UE comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.
In an eighth aspect, there is provided a node device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the second or third aspect.
In a ninth aspect, there is provided a readable storage medium on which is stored a program or instructions which, when executed by a processor, carries out the steps of the method of the first aspect or the steps of the method of the second or third aspect.
In a tenth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the second aspect or the third aspect.
In this embodiment of the present application, when the UE receives a mobility management command and receives a target service through a source cell, the UE is enabled to perform a first target operation on a bearer of the source cell (i.e., process and sequentially deliver buffer data in the bearer of the source cell to a higher layer), and perform a second target operation on the bearer of the target cell (i.e., the UE establishes or reestablishes a protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command). Therefore, the UE can process the data borne by the target cell after processing the data borne by the source cell, so that the repeated sending of the data packet of the target service is avoided, the loss of the data packet is also avoided, and the energy efficiency of the communication system is improved.
Drawings
Fig. 1 is an architecture diagram of a communication system to which a data transmission method provided in an embodiment of the present application is applied;
fig. 2 is a flowchart of a method of data transmission according to an embodiment of the present application;
fig. 3 is a second flowchart of a data transmission method according to an embodiment of the present application;
fig. 4 is a third flowchart of a method of data transmission according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a data transmission device according to an embodiment of the present application;
fig. 6 is a second schematic structural diagram of a data transmission device according to an embodiment of the present application;
fig. 7 is a third schematic structural diagram of a data transmission device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a node device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Technical terms related to the embodiments of the present application will be explained below:
1. multimedia Broadcast Multicast Service (MBMS) or Broadcast Multicast Service (MBS)
In the LTE system, MBMS/MBS services can be transmitted in the following two ways:
MBMS/MBS transmission mode 1: the MBMS service is transmitted through a Physical Multicast Channel (PMCH) Physical Channel in an MBMS Single Frequency Network (MBSFN) subframe. The Control information is transmitted through system information (e.g., SIB13) and a broadcast Control Channel (MCCH), and the data is transmitted through a broadcast Traffic Channel (MTCH).
MBMS/MBS transmission mode 2: and a Physical Downlink Shared Channel (PDSCH) Channel scheduled by a PDCCH (Physical Downlink Control Channel). The Control information is transmitted through system information (e.g., SIB20) and a Single Cell Multicast Control Channel (SC-MCCH), and the data is transmitted through a Single Cell Multicast Traffic Channel (SC-MTCH). The SC-MCCH is transmitted through a PDSCH scheduled by a PDCCH (Single Cell-Radio Network Temporary Identity, SC-RNTI), and the SC-MTCH is transmitted through a PDSCH scheduled by G-RNTI PDCCH.
The MBS service is transmitted through a specific mrb (mbms Radio bearer) Radio bearer. Wherein, the MBS service may be marked by the following identifier: temporary Mobile Group Identity (TMGI), QoS flow ID.
When the core network node sends multicast service data to the base stations in a multicast mode, the core network node can send the same service data to a plurality of base stations simultaneously.
2. Unicast
The unicast reception of the UE is received through a specific unicast data Radio bearer (drb). Wherein, 5G, the protocol stack of unicast transmission (or reception) includes from top to bottom in proper order: service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC).
3、DC
The UE may establish a connection at the same time in two Cell groups, i.e., a Master Cell Group (MCG) and a Secondary Cell Group (SCG). The MCG includes a Primary Cell (PCell) and a Secondary Cell (SCell), and the SCG includes a Primary and a Secondary Cell (PSCell). It should be noted that the PCell and the PSCell may both be referred to as a SpCell (Special Cell).
4. Other terms
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as 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), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)thGeneration, 6G) communication system.
Fig. 1 shows a system architecture diagram of a communication system to which embodiments of the present application are applicable. The communication system includes a terminal 11 and a network-side device 12.
Illustratively, network-side device 12 may serve at least one cell group (e.g., MCG or SCG). Wherein, one MCG includes at least one PCell and possibly at least one SCell; an MCG includes at least one PSCell and possibly at least one SCell.
Illustratively, the network-side device includes a node device, and the node device includes a source node device and a target node device.
Illustratively, the terminal 11 may also be referred to as a terminal Device or a User Equipment (UE), and the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a terminal-side Device called a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, an ultra-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and the like, where the Wearable Device includes: bracelets, earphones, glasses and the like. 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, where 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 (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.
The data transmission method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
The data transmission method provided by the embodiment of the application can be applied to the UE, in other words, the data transmission method can be executed by software or hardware installed in the UE. As shown in fig. 2, a data transmission method provided in an embodiment of the present application may include the following step 201.
Step 201: and under the condition of receiving the mobility management command and receiving the target service through the source cell, executing a first target operation on the bearer of the source cell and executing a second target operation on the bearer of the target cell.
In this embodiment, the target traffic includes unicast traffic and/or multicast traffic.
Illustratively, when the UE receives a multicast service through a unicast bearer or a multicast bearer in a source cell, the UE receives a mobility management command sent by a network side device, and when the UE receives the multicast service through the unicast bearer or the multicast bearer in the mobility management command, the UE performs a first target operation on the bearer in the source cell and performs a second target operation on the bearer in the target cell.
In the embodiment of the present application, the data transmission method provided in the embodiment of the present application is applied to a dual-link mobility management process. The dual connectivity mobility management procedure includes a handover procedure or an SCG change procedure (i.e., an SCG change procedure). That is, when the UE changes its serving cell, connections are simultaneously established with the source cell and the target cell, and then the connection with the source cell is released and only the connection with the target cell is maintained. For example, the PCell serving cell of the UE is changed from cell 1 to cell 2 during the handover, the UE simultaneously establishes a connection with cell 1 and cell 2 during the change, and then releases the connection with cell 1 and only maintains the connection with cell 2.
In this embodiment, the mobility management command is used to instruct a target cell to receive a target service. Illustratively, the mobility management command includes any one of: a switching command, an auxiliary cell group SCG changing command, an SCG adding command and an SCG deleting command.
In one example, the handover command is used to instruct a change to the PCell. The SCG change command is used to instruct to change the SCG (e.g., PSCell change), where the source cell is a cell of the source SCG and the target cell is a cell of the target SCG. The SCG addition command is used to indicate to add SCG (e.g., PSCell addition), where the source cell is a cell of MCG and the target cell is a cell of SCG. The SCG delete command is used to instruct to delete SCG (e.g., PSCell release), where the source cell is a cell of SCG and the target cell is a cell of MCG.
In an embodiment of the present application, the first target operation includes: a first operation, the first operation being: and processing the buffer data in the load of the source cell and delivering the buffer data to a high layer in sequence. The second target operation includes: establishing or rebuilding a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
It should be noted that, the first target operation may be predefined, protocol-specified, or indicated by the network side, and this is not limited in this embodiment of the application. Similarly, the second target operation may be predefined, protocol-specified, or indicated by the network side, which is not limited in this embodiment of the application.
Optionally, in this embodiment of the present application, the first target operation further includes: a second operation, the second operation being: and deleting the PDCP entity of the bearer of the source cell.
It can be understood that the UE performs any one of the following processing actions for the bearer of the source cell according to the network side indication or the agreement:
processing behavior of bearer of source cell 1: and after the UE processes the cache data in the PDCP entity carried by the source cell and delivers the cache data to the upper layer in sequence, the UE deletes the PDCP entity carried by the source cell.
Processing behavior of bearer of source cell 2: and the UE processes the buffered data in the PDCP entity carried by the source cell and delivers the processed buffered data to a higher layer in sequence.
It can be understood that, according to the network side indication or the agreement, the UE performs any one of the following processing actions on the bearer of the target cell:
processing behavior of bearer of target cell 1: and after receiving the mobility management command, establishing or reestablishing a protocol entity corresponding to the target cell bearer. For example, after receiving the mobility management command, the UE establishes or reestablishes the PDCP entity carried by the target cell during the process of processing the unicast bearer of the source cell.
Processing behavior of the bearer of the target cell 2: after executing the processing action 1 carried by the source cell or the processing action 2 carried by the source cell, establishing or rebuilding a protocol entity corresponding to the bearing of the target cell. For example, after the UE receives the mobility management command, the UE processes the bearer in the source cell, and after all the buffered data carried in the source cell are processed, the UE starts to establish or reestablish the PDCP entity carried in the target cell, thereby ensuring that the received data is delivered in a forward manner.
Optionally, in this embodiment of the application, the data type of the data carried by the source cell may include at least one of the following: a PDCP (Packet Data Convergence Protocol) layer Packet, a PDCP layer control Packet, and a PDCP layer Data. That is, the data carried by the source cell may include at least one of the following: a carried PDCP layer data packet, a carried PDCP layer control packet and a carried PDCP layer data. The PDCP layer Data packet may be a PDCP Data PDU, the PDCP layer control packet may be a PDCP control PDU (e.g., a Robust Header Compression (ROHC) feedback packet), and the PDCP layer Data may be a PDCP PDU.
In one example, the PDCP layer data (e.g., PDCP PDUs) described above include, but are not limited to: a Signaling Radio Bearers (SRB) control packet, an SRB data packet, a data Radio Bearers (SRB) control packet, a DRB data packet, a PDCP control packet, and a PDCP data packet.
Similarly, the data type of the data carried by the target cell may also include the data type, which is not described herein again.
Optionally, in this embodiment of the present application, the data transmission method provided in this embodiment of the present application may further include the following steps 201a1 and 201a 2:
step 201a 1: and caching the data packet received by the load bearing of the target cell before the first target operation is executed on the load bearing of the source cell.
Step 201a 2: and after the first target operation is executed on the load bearing of the source cell, delivering the data packet received by the load bearing of the target cell to a higher layer.
For example, for the above "processing behavior 1 of the bearer of the target cell", 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 (e.g., after all the buffered data packets are delivered to the higher layer protocol entity, or after the "bearer of the source cell" is deleted), and then begin to deliver the data packets received from the "bearer of the target cell" to the higher layer protocol entity.
Optionally, in this embodiment of the present application, the data transmission method provided in this embodiment of the present application may further include the following step 201 b:
step 201 b: and sending the data packet information of the target service received from the load of the source cell to the network side equipment through the load of the target cell.
Further optionally, in this embodiment of the application, the data packet information includes at least one of the following: the number of the first missing data packet, the number of the last received data packet, the bitmap indication of the received data packet; wherein the bitmap indication indicates whether the corresponding data packet is successfully received.
Illustratively, the UE sends packet information of a received packet (e.g., the number of the first lost packet, and/or the number of the last received packet, and/or a bitmap indication (each bit indicates whether a packet with a specific number is successfully received)) from the "bearer of the source cell" to the network side device through the "bearer of the target cell".
Thus, when the UE receives the mobility management command and receives the target service through the source cell, the UE performs a first target operation on the bearer of the source cell (i.e., processes the buffer data in the bearer of the source cell and delivers the buffer data to a higher layer in sequence), and performs a second target operation on the bearer of the target cell (i.e., the UE establishes or reestablishes a protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command). Therefore, the UE can process the data borne by the target cell after processing the data borne by the source cell, so that the repeated sending of the data packet of the target service is avoided, the loss of the data packet is also avoided, and the energy efficiency of the communication system is improved.
The data transmission method provided by the embodiment of the application can be applied to the 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, a data transmission method provided in an embodiment of the present application may include step 301.
Step 301: in the mobility management procedure, a third target operation is performed in case of receiving a target service through the source cell.
Wherein the third target operation is used to indicate a target service to a target node device.
Optionally, in an embodiment of the present application, the third target operation includes at least one of:
informing the data packet information of the target service to the target node equipment;
forwarding the data packet of the target service to the target node equipment;
indicating the service information of the target service to the target node equipment;
and indicating the bearing identification of the target service to the target node equipment.
Optionally, in this embodiment of the present application, the service information of the target service includes at least one of the following: a service identifier (e.g., TMGI), a service name (e.g., XX tv station), a service interpretation (e.g., a multicast service distribution channel (e.g., a central tv station program transmitted through a broadcast television network), a multicast service feature (e.g., voice or video)), a service transmission address (e.g., TCP and/or IP address and a transmission port number corresponding to the address), a service transmission Protocol (e.g., Hypertext Transfer Protocol (HTTP) or Simple Message Transfer Protocol (SMTP)), a session identifier (e.g., MBS session-1), a service type indicator (e.g., multicast service or RNTI service), and a scheduling identifier (e.g., MBS-1).
Optionally, in this embodiment of the present application, the bearer identifier of the target service includes at least one of:
a Tunnel identifier (such as GTP-U Tunnel-1) between the source node device and the core network node device;
a data flow identification (e.g., QoS flow-1);
a Session identifier (e.g., PDU Session-1);
a radio bearer identification (e.g., DRB-1) of the source node;
the logical channel identification (e.g., LCID-1) of the source node.
Optionally, in this embodiment of the present application, the data packet information of the target service includes at least one of the following: the number of the last transmitted data packet (e.g., the data packet with GTP SN ═ 1 was transmitted but no feedback of successful reception of the UE has been received yet), the number of the last successfully transmitted data packet (e.g., the data packet with GTP SN ═ 1 was transmitted and no feedback of successful reception of the UE was received), the number of the last unsuccessfully transmitted data packet (e.g., the data packet with GTP SN ═ 1 was transmitted and no feedback of successful reception of the UE was received), the number of the first unsuccessfully transmitted data packet (e.g., the data packet with GTP SN ═ 1 was transmitted and no feedback of unsuccessful reception of the UE was received yet)), the number of the next transmitted data packet (e.g., the data packet with GTP SN ═ 1 has not been transmitted at the source node device, the source node device wants to be transmitted next to the UE at the target node device with SN ═ 1), the bitmap indicates (e.g., bit 1/2/3 represents GTP SN 1/2/3, bit-1 represents that a GTP SN-1 data packet is received, bit-2/3 represents 0 represents that a data packet of GTP SN-2/3 is not received, and a target correspondence relationship (for example, the core network number of the data packet 1/2/3 is GTP-U SN-1/2/3, the number of the corresponding source node is PDCP COUNT-1/2/3, and a correspondence relationship exists between the two numbers).
Wherein, the target corresponding relation comprises: and the core network node equipment determines the mapping relation between the number of the data packet of the target service and the number of the data packet of the target service in the access network node equipment. The above-mentioned bit map indication is used for indicating the transmission status of the corresponding data packet, and it is understood that the above-mentioned bit map indication is used for indicating whether the corresponding data packet is successfully received.
It should be noted that the numbering manners of the data packets in the above-mentioned "data packet information of the carried target service" mainly include the following two numbering manners:
numbering system 1: the number of the data packet is determined by the core network node device. For example, when a core network node device (e.g., UPF) sends a packet of multicast traffic to a base station (e.g., gNB), the packet carries numbering information (e.g., in the header of a GTP-U tunnel).
Numbering system 2: the number of the data packet is determined by node devices of the access network, such as a source node device and a destination node device. E.g., PDCP SN or COUNT determined by the PDCP entity of the source node device.
Optionally, in this embodiment of the application, a behavior that the source node device forwards the data packet of the target service to the target node device includes at least one of the following:
indicating the number determined by the core network node device for the data packet of the target service (i.e. indicating the number determined by the core network node device for the forwarded data packet of the target service, for example, the core network number of the data packet 1/2/3 is GTP-U SN-1/2/3);
a transmission number indicating that the data packet of the target service is transmitted at the source node device of the access network (i.e. a transmission number indicating that the forwarded data packet of the target service is transmitted at the source node device of the access network, for example, data packet 1/2/3 is forwarded, and a number indicating that the data packet 1/2/3 at the source node device is PDCP COUNT-1/2/3);
indicating the transmission number of the data packet of the target service at the target node device of the access network (indicating the transmission number of the forwarded data packet of the target service at the target node device of the access network, example 1: forwarding the data packet 1/2/3 and indicating the number of the data packet 1/2/3 at the target node device to be PDCP COUNT-1/2/3; example 2: forwarding the data packet 1/2/3 and indicating the start number of the data packet 1/2/3 at the target node device to be PDCP COUNT-1);
a target correspondence is indicated (i.e. a correspondence indicating a "core network node device determined number" of the forwarded data packet of the target service and a "transmission number of a node device of the access network", e.g. the core network number of the data packet 1/2/3 is GTP-U SN-1/2/3 and the number of the corresponding source node is PDCP COUNT-1/2/3).
The target corresponding relation is a mapping relation between a number determined by the core network node equipment for the data packet of the target service and a number of the data packet of the target service in the node equipment of the access network.
In this way, in the mobility management process, when the target service is received through the source cell, the target node device is enabled to send the data packets which are not sent to the UE by notifying the data packet information of the target service to the target node device, so that not only the repeated sending of the data packets is avoided, but also the loss of the data packets is avoided.
The data transmission method provided by the embodiment of the application can be applied to the 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, a data transmission method provided in an embodiment of the present application may include the following step 401.
Step 401: in the process of mobility management, under the condition of receiving the target service through the source cell, the data packet of the target service is sent to the UE through the load of the target cell according to the data packet information of the target service.
Optionally, in this embodiment of the present application, the data packet information of the target service includes at least one of the following:
the source cell indicated by the UE carries the received data packet information of the target service,
and the source node equipment indicates the data packet information of the target service to the target node equipment.
Optionally, in this embodiment of the application, the data packet information of the target service, which is indicated to the target node device by the source node device, includes at least one of the following:
the source node device informs the data packet information of the target service of the target node device;
service information of the target service;
carrying identification of the target service;
and the source node equipment forwards the data packet of the target service to the number information carried by the target node equipment.
Illustratively, the number information includes at least one of:
the core network node equipment determines the number of the data packet of the target service;
the sending number of the data packet of the target service in the source node equipment of the access network;
the sending number of the data packet of the target service at the target node equipment of the access network;
and (4) target corresponding relation.
The target corresponding relation is a mapping relation between a number determined by the core network node equipment for the data packet of the target service and a number of the data packet of the target service in the node equipment of the access network.
It should be noted that, the same technical terms as those described above in the above description can be explained by referring to the above description, and are not repeated herein.
For example, the source node device indicates that the core network numbers of the 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 equipment has the same core network number for the same data packet which is sent to the source node equipment and the target node equipment by the broadcast data. At this time, if the target node device receives the data packet GTP-U SN-1/2/3 from the core network node device, and the receiving status of the multicast data packet received from the UE side is: when the PDCP COUNT-1 is received and the data packet of the PDCP COUNT-2/3 is not received, the target node device knows that the data packet GTP-U SN-1 received from the core network node device has been successfully received according to the correspondence between the core network number and the access network number (i.e., the target correspondence), and then the target node device sends the data packet GTP-U SN-2/3 received from the core network node device to the UE.
In this way, in the mobility management process, when the source cell receives the target service, the data packets which are not yet sent to the UE are sent according to the data packet information of the target service from the source node device, the UE information and the core network information, which are collected by the target node device, so that not only are the repeated sending of the data packets avoided, but also the loss of the data packets is avoided.
It should be noted that, in the data transmission method provided in the embodiment of the present application, the execution main body may be a data transmission device, or a control module in the data transmission device for executing the data transmission method. In the embodiment of the present application, a data transmission method performed by a data transmission device is taken as an example, and the data transmission device provided in the embodiment of the present application is described.
As shown in fig. 5, the data transmission device 500 provided in this embodiment of the present application may include: an execution module 501, wherein:
an executing module 501, configured to execute a first target operation on a bearer of a source cell and execute a second target operation on the bearer of a target cell when a mobility management command is received and a target service is received through the source 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 cache data in the load of the source cell and delivering the cache data to a high layer in sequence; the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
Optionally, in this embodiment of the present application, the first target operation further includes: and deleting the PDCP entity carried by the source cell.
Optionally, in this embodiment of the present application, the mobility management command includes any one of: a switching command, an auxiliary cell group SCG changing command, an SCG adding command and an SCG deleting command.
Optionally, in this embodiment of the present application, the executing module 501 is further configured to cache a data packet received by the bearer of the target cell before the first target operation is performed on the bearer of the source cell; the executing module 501 is further configured to deliver the data packet received by the bearer of the target cell to a higher layer after the first target operation is executed on the bearer of the source cell.
Optionally, in this embodiment of the present application, the apparatus 500 further includes: a sending module 502, wherein: a sending module 502, configured to send the data packet information of the target service received from the bearer of the source cell to a network side device through the bearer of the target cell.
Optionally, in an embodiment of the present application, the data packet information includes at least one of: the number of the first missing data packet, the number of the last received data packet, the bitmap indication of the received data packet; wherein the bitmap indication indicates whether the corresponding data packet is successfully received.
In the data transmission apparatus provided in the embodiment of the present application, when the UE receives a mobility management command and receives a target service through a source cell, the UE is enabled to perform a first target operation on a bearer of the source cell (i.e., process and sequentially deliver cache data in the bearer of the source cell to a higher layer), and perform a second target operation on the bearer of the target cell (i.e., the UE establishes or reestablishes a protocol entity corresponding to the bearer of the target cell after performing the first target operation or receiving the mobility management command). Therefore, the UE can process the data borne by the target cell after processing the data borne by the source cell, so that the repeated sending of the data packet of the target service is avoided, the loss of the data packet is also avoided, and the energy efficiency of the communication system is improved.
As shown in fig. 6, a data transmission device 600 provided in this embodiment of the present application may include: an execution module 601, wherein: an execution module, configured to execute a third target operation in a mobility management process under a condition that a target service is received through a source cell; wherein the third target operation is configured to indicate the target service to a target node device.
Optionally, in an embodiment of the present application, the third target operation includes at least one of:
informing the data packet information of the target service to target node equipment;
forwarding the data packet of the target service to the target node equipment;
indicating the service information of the target service to the target node equipment;
and indicating the bearing identification of the target service to the target node equipment.
Optionally, in this embodiment of the present application, the service information of the target service includes at least one of the following:
service identification, service name, service explanation, service characteristics, service sending address, service sending protocol, session identification, service type indication and scheduling identification.
Optionally, in this embodiment of the present application, the bearer identifier of the target service includes at least one of:
a tunnel identifier between the source node device and the core network node device;
a data stream identification;
a session identifier;
a radio bearer identity of the source node;
logical channel identification of the source node.
Optionally, in this embodiment of the present application, the data packet information of the target service includes at least one of the following: the number of the last transmitted data packet, the number of the last successfully transmitted data packet, the number of the last unsuccessfully transmitted data packet, the number of the first unsuccessfully transmitted data packet, the number of the next transmitted data packet, the bitmap indication and the target corresponding relation; the target correspondence includes: the core network node equipment determines the mapping relation between the number of the data packet of the target service and the number of the data packet of the target service in the access network node equipment; the above-mentioned bitmap indication is used to indicate whether the corresponding data packet was received successfully.
Optionally, in this embodiment of the application, the forwarding the data packet of the target service to the target node device includes at least one of the following:
indicating the number determined by the core network node device for the data packet of the target service,
a transmission number of the data packet indicating the target service at the source node device of the access network,
a transmission number of the data packet indicating the target service at the target node device of the access network,
indicating the target correspondence.
The target correspondence relationship is a mapping relationship between a number determined by the core network node device for the data packet of the target service and a number of the data packet of the target service in the node device of the access network.
In the data transmission apparatus provided in the embodiment of the present application, in the mobility management process, when the source cell receives the target service, the target node device is notified of the data packet information of the target service, so that the target node device sends the data packet that is not yet sent to the UE, thereby not only avoiding repeated sending of the data packets, but also avoiding loss of the data packets.
As shown in fig. 7, a data transmission device 700 provided in this embodiment of the present application may include: an execution module 701, wherein:
an executing module 701, configured to send, according to the data packet information of the target service, a data packet of the target service to a user equipment UE through a bearer of a target cell in a mobility management process when the target service is received by a source cell.
Optionally, in this embodiment of the present application, the data packet information of the target service includes at least one of the following:
the source cell indicated by the UE carries the received data packet information of the target service,
and the source node equipment indicates the data packet information of the target service to the target node equipment.
Optionally, in this embodiment of the application, the data packet information of the target service, which is indicated to the target node device by the source node device, includes at least one of the following:
the source node device notifies the destination node device of the packet information of the destination service;
service information of the target service;
the bearing mark of the target service;
the source node equipment forwards the data packet of the target service to the number information carried by the target node equipment;
wherein the number information includes at least one of:
the core network node device determines the number for the data packet of the target service,
the transmission number of the data packet of the target service at the source node equipment of the access network,
the transmission number of the data packet of the target service at the target node device of the access network,
a target correspondence;
the target correspondence relationship is a mapping relationship between a number determined by the core network node device for the data packet of the target service and a number of the data packet of the target service in the node device of the access network.
In the data transmission apparatus provided in the embodiment of the present application, in a mobility management process, when a source cell receives a target service, a data packet that has not been sent to a UE is sent according to data packet information of the target service, UE information, and core network information, which are collected by a target node device, from the source node device, so that not only repeated sending of the data packets is avoided, but also loss of the data packets is avoided.
The data transmission device in the 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 can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.
The data transmission device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The data transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 2 to fig. 4, and achieve the same technical effect, and is not described here again to avoid repetition.
Optionally, as shown in fig. 8, an embodiment of the present application further provides a communication device 800, which includes a processor 801, a memory 802, and a program or an instruction stored on the memory 802 and executable on the processor 801, for example, when the communication device 800 is a terminal, the program or the instruction is executed by the processor 801 to implement the processes of the data transmission method embodiment shown in fig. 2, and the same technical effect can be achieved. When the communication device 800 is a node device, the program or the instructions are executed by the processor 801 to implement the processes of the data transmission method embodiments shown in fig. 3 or fig. 4, and the same technical effect can be achieved, and for avoiding repetition, the details are not described here again.
Fig. 9 is a schematic diagram of a hardware structure of a terminal for implementing the 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.
Those skilled in the art will appreciate that the terminal 900 may further include a power source (e.g., 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 management functions through the power management system. The terminal structure shown in fig. 9 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.
It should be understood that, in the embodiment of the present application, the input Unit 904 may include a Graphics Processing Unit (GPU) 9041 and a microphone 9042, and the Graphics Processing Unit 9041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. 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, an organic light emitting diode, or the like. The user input unit 907 includes a touch panel 9071 and other input devices 9072. A touch panel 9071 also referred to as 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, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
In this embodiment of the application, the radio frequency unit 901 receives downlink data from a network side device and then processes the downlink data to the processor 910; in addition, the uplink data is sent to the network side equipment. Generally, 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 processor 910 is configured to, when receiving a mobility management command and a source cell receives a target service, perform a first target operation on a bearer of the source cell, and perform a second target operation on a bearer of a target cell; 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: processing the cache data in the load of the source cell and delivering the cache data to a high layer in sequence; the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
Optionally, in this embodiment of the present application, the first target operation further includes: a second operation, the second operation being: and deleting the PDCP entity carried by the source cell.
Optionally, in this embodiment of the present application, the mobility management command includes any one of: a switching command, an auxiliary cell group SCG changing command, an SCG adding command and an SCG deleting command.
Optionally, in this embodiment of the application, the processor 910 is further configured to buffer a data packet received by the bearer of the target cell until the first target operation is performed on the bearer of the source cell, and deliver the data packet received by the bearer of the target cell to a higher layer.
Optionally, in this embodiment of the application, the radio frequency unit 901 is configured to send the data packet information of the target service, which is received from the bearer of the source cell, to a network side device through the bearer of the target cell.
Optionally, in an embodiment of the present application, the data packet information includes at least one of: the number of the first missing data packet, the number of the last received data packet, the bitmap indication of the received data packet; wherein the bitmap indication indicates whether the corresponding data packet is successfully received.
In the terminal provided in the embodiment of the present application, when the terminal receives a mobility management command and the source cell receives a target service, the terminal is enabled to execute a first target operation on a bearer of the source cell (i.e., process and sequentially deliver cache data in the bearer of the source cell to a higher layer), and execute a second target operation on the bearer of the target cell (i.e., the terminal establishes or reestablishes a protocol entity corresponding to the bearer of the target cell after executing the first target operation or receiving the mobility management command). Therefore, the terminal can process the data borne by the target cell after processing the data borne by the source cell, so that the repeated sending of the data packet of the target service is avoided, the loss of the data packet is also avoided, and the energy efficiency of the communication system is improved.
Specifically, the embodiment of the application further provides node equipment. As shown in fig. 10, the node apparatus 100 includes: antenna 101, radio frequency device 102, baseband device 103. Antenna 101 is connected to radio frequency device 102. In the uplink direction, rf device 102 receives information via antenna 101 and sends the received information to baseband device 103 for processing. In the downlink direction, the baseband device 103 processes information to be transmitted and transmits the information to the rf device 102, and the rf device 102 processes the received information and transmits the processed information through the antenna 101.
The above-mentioned band processing apparatus may be located in the baseband apparatus 103, and the method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 103, where the baseband apparatus 103 includes the processor 104 and the memory 105.
The baseband apparatus 103 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 10, where one of the chips, for example, the processor 104, is connected to the memory 105 to call up a program in the memory 105 to perform the node device operation shown in the above method embodiment.
The baseband device 103 may further include a network interface 106, such as a Common Public Radio Interface (CPRI), for exchanging information with the radio frequency device 102.
Specifically, the node of the embodiment of the present invention further includes: the instructions or programs stored in the memory 105 and capable of being executed on the processor 104, and the processor 104 invokes the instructions or programs in the memory 105 to execute the methods executed by the modules shown in fig. 3 or fig. 4, and achieve the same technical effects, which are not described herein in detail to avoid repetition.
The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the data transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The 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 configured to run a network-side device program or an instruction, so as to implement each process of the data transmission method embodiment, and achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (28)
1. A data transmission method is applied to User Equipment (UE), and is characterized by comprising the following steps:
under the condition that a mobility management command is received and a target service is received through a source cell, executing a first target operation on a bearer of the source cell and executing a second target operation on the bearer of the target cell;
wherein the mobility management command is used to instruct reception of the target service at the target cell;
the first target operation includes: processing the cache data in the load of the source cell and delivering the cache data to a high layer in sequence;
the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
2. The method of claim 1, wherein the first target operation further comprises: and deleting the carried packet data convergence protocol PDCP entity of the source cell.
3. The method according to claim 1, wherein the mobility management command comprises any of: a switching command, an auxiliary cell group SCG changing command, an SCG adding command and an SCG deleting command.
4. The method of claim 1, further comprising:
caching data packets received by the bearer of the target cell before the bearer of the source cell is subjected to the first target operation;
and after the first target operation is executed on the bearer of the source cell, delivering the data packet received by the bearer of the target cell to a higher layer.
5. The method of claim 1, further comprising:
and sending the data packet information of the target service received from the load of the source cell to network side equipment through the load of the target cell.
6. The method of claim 5, wherein the packet information comprises at least one of: the number of the first missing data packet, the number of the last received data packet, the bitmap indication of the received data packet;
wherein the bitmap indication indicates whether the corresponding data packet was received successfully.
7. A data transmission method is applied to source node equipment, and is characterized in that the method comprises the following steps:
in the process of mobility management, under the condition that a source cell receives a target service, a third target operation is executed;
wherein the third target operation is to indicate the target traffic to a target node device.
8. The method of claim 7, wherein the third target operation comprises at least one of:
informing the data packet information of the target service to target node equipment;
forwarding the data packet of the target service to the target node equipment;
indicating the service information of the target service to the target node equipment;
and indicating the bearing identification of the target service to the target node equipment.
9. The method of claim 7, wherein the service information of the target service comprises at least one of:
service identification, service name, service explanation, service characteristics, service sending address, service sending protocol, session identification, service type indication and scheduling identification.
10. The method of claim 7, wherein the bearer identification of the target service comprises at least one of:
a tunnel identifier between the source node device and the core network node device;
a data stream identification;
a session identifier;
a radio bearer identity of the source node;
logical channel identification of the source node.
11. The method of claim 7, wherein the packet information of the target service comprises at least one of the following: the number of the last transmitted data packet, the number of the last successfully transmitted data packet, the number of the last unsuccessfully transmitted data packet, the number of the first unsuccessfully transmitted data packet, the number of the next transmitted data packet, the bitmap indication and the target corresponding relation;
the target correspondence includes: the core network node equipment determines the mapping relation between the number of the data packet of the target service and the number of the data packet of the target service in the access network node equipment;
the bitmap indication indicates whether the corresponding data packet was received successfully.
12. The method of claim 8, wherein forwarding the data packet of the target service to the target node device comprises at least one of:
indicating the number determined by the core network node device for the data packet of the target service,
indicating the sending number of the data packet of the target service at the source node equipment of the access network,
a transmission number of the data packet of the target service at the target node device of the access network is indicated,
indicating a target correspondence;
the target corresponding relation is a mapping relation between a number determined by the core network node equipment for the data packet of the target service and a number of the data packet of the target service in the node equipment of the access network.
13. A data transmission method is applied to target node equipment, and is characterized in that the method comprises the following steps:
in the process of mobility management, under the condition of receiving a target service through a source cell, sending a data packet of the target service to User Equipment (UE) through the load of a target cell according to the data packet information of the target service.
14. The method of claim 13, wherein the packet information of the target service comprises at least one of:
the source cell indicated by the UE carries the received data packet information of the target service,
and the source node equipment indicates the data packet information of the target service to the target node equipment.
15. The method of claim 14, wherein the packet information of the target service indicated to the target node device by the source node device comprises at least one of:
the source node device informs the data packet information of the target service of the target node device;
service information of the target service;
the bearing identification of the target service;
the source node equipment forwards the data packet of the target service to the number information carried by the target node equipment;
wherein the numbering information comprises at least one of:
the core network node device determines a number for the data packet of the target service,
the sending number of the data packet of the target service at the source node equipment of the access network,
the sending number of the data packet of the target service at the target node equipment of the access network,
a target correspondence;
the target corresponding relation is a mapping relation between a number determined by the core network node equipment for the data packet of the target service and a number of the data packet of the target service in the node equipment of the access network.
16. A data transmission apparatus, characterized in that the apparatus comprises:
the execution module is used for executing a first target operation on the load bearing of the source cell and executing a second target operation on the load bearing of the target cell under the conditions that the mobility management command is received and the target service is received through the source cell;
wherein the mobility management command is used to instruct reception of the target service at the target cell;
the first target operation includes: processing the cache data in the load of the source cell and delivering the cache data to a high layer in sequence;
the second target operation includes: establishing or reestablishing a protocol entity corresponding to the load of the target cell when a preset condition is met; the predetermined conditions include: after the first target operation is executed, or after the mobility management command is received.
17. The apparatus of claim 16, wherein the first target operation further comprises: and deleting the carried packet data convergence protocol PDCP entity of the source cell.
18. The apparatus of claim 16, wherein the execution module is further configured to: caching data packets received by the bearer of the target cell before the bearer of the source cell is subjected to the first target operation;
the execution module is further configured to: and after the first target operation is executed on the bearer of the source cell, delivering the data packet received by the bearer of the target cell to a higher layer.
19. The apparatus of claim 16, further comprising: a sending module, wherein:
and the sending module is used for sending the data packet information of the target service received from the bearer of the source cell to network side equipment through the bearer of the target cell.
20. A data transmission apparatus, characterized in that the apparatus comprises:
an execution module, configured to execute a third target operation when the source cell receives the target service in a mobility management process;
wherein the third target operation is to indicate the target traffic to a target node device.
21. The apparatus of claim 20, wherein the third target operation comprises at least one of:
informing the data packet information of the target service to target node equipment;
forwarding the data packet of the target service to the target node equipment;
indicating the service information of the target service to the target node equipment;
and indicating the bearing identification of the target service to the target node equipment.
22. The apparatus of claim 20, wherein the packet information of the target service comprises at least one of: the number of the last transmitted data packet, the number of the last successfully transmitted data packet, the number of the last unsuccessfully transmitted data packet, the number of the first unsuccessfully transmitted data packet, the number of the next transmitted data packet, the bitmap indication and the target corresponding relation;
the target correspondence includes: the core network node equipment determines the mapping relation between the number of the data packet of the target service and the number of the data packet of the target service in the access network node equipment;
the bitmap indication indicates whether the corresponding data packet was received successfully.
23. The apparatus of claim 20, wherein the forwarding the data packet of the target service to the target node device comprises at least one of:
indicating the number determined by the core network node device for the data packet of the target service,
indicating the sending number of the data packet of the target service at the source node equipment of the access network,
a transmission number of the data packet of the target service at the target node device of the access network is indicated,
indicating a target correspondence;
the target corresponding relation is a mapping relation between a number determined by the core network node equipment for the data packet of the target service and a number of the data packet of the target service in the node equipment of the access network.
24. A data transmission apparatus, characterized in that the apparatus comprises:
and the sending module is used for sending the data packet of the target service to User Equipment (UE) through the load of the target cell according to the data packet information of the target service under the condition that the source cell receives the target service in the mobility management process.
25. The apparatus of claim 24, wherein the packet information of the target service comprises at least one of:
the source cell indicated by the UE carries the received data packet information of the target service,
and the source node equipment indicates the data packet information of the target service to the target node equipment.
26. A user equipment, UE, comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, implement the steps of the data transmission method according to any of claims 1 to 6.
27. A node device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing a data transmission method as claimed in any one of claims 7 to 12 or the steps of implementing a data transmission method as claimed in any one of claims 13 to 15.
28. A readable storage medium, on which a program or instructions are stored, which, when executed by the processor, implement the data transmission method of any one of claims 1 to 6, or the data transmission method of any one of claims 7 to 12, or the steps of the data transmission method of any one of claims 13 to 15.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010677289.6A CN113938968B (en) | 2020-07-14 | 2020-07-14 | Data transmission method, device and equipment |
PCT/CN2021/105855 WO2022012480A1 (en) | 2020-07-14 | 2021-07-12 | Data transmission method and apparatus, and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010677289.6A CN113938968B (en) | 2020-07-14 | 2020-07-14 | Data transmission method, device and equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN113938968A true CN113938968A (en) | 2022-01-14 |
CN113938968B CN113938968B (en) | 2023-01-31 |
Family
ID=79273956
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010677289.6A Active CN113938968B (en) | 2020-07-14 | 2020-07-14 | Data transmission method, device and equipment |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN113938968B (en) |
WO (1) | WO2022012480A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024159543A1 (en) * | 2023-02-03 | 2024-08-08 | 北京小米移动软件有限公司 | Control method and apparatus for transport entity |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104955064A (en) * | 2014-03-28 | 2015-09-30 | 上海贝尔股份有限公司 | Method for processing user equipment terminal RLC/PDCP entity in dual-connection system and equipment thereof |
US20190394669A1 (en) * | 2017-08-11 | 2019-12-26 | Huawei Technologies Co., Ltd. | Data Transmission Method And Data Transmission Apparatus |
CN110944368A (en) * | 2018-09-25 | 2020-03-31 | 电信科学技术研究院有限公司 | Method and equipment for transmitting data in switching process |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11546815B2 (en) * | 2017-03-22 | 2023-01-03 | Idac Holdings, Inc. | System and methods for phased reconfiguration in wireless systems |
CN110351896B (en) * | 2018-04-04 | 2021-07-09 | 华为技术有限公司 | Connection reestablishment method and device |
CN109548107B (en) * | 2019-01-18 | 2021-09-21 | 中国科学院上海高等研究院 | Method, system, medium, and device for dual connection handover based on communication network |
-
2020
- 2020-07-14 CN CN202010677289.6A patent/CN113938968B/en active Active
-
2021
- 2021-07-12 WO PCT/CN2021/105855 patent/WO2022012480A1/en active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104955064A (en) * | 2014-03-28 | 2015-09-30 | 上海贝尔股份有限公司 | Method for processing user equipment terminal RLC/PDCP entity in dual-connection system and equipment thereof |
US20190394669A1 (en) * | 2017-08-11 | 2019-12-26 | Huawei Technologies Co., Ltd. | Data Transmission Method And Data Transmission Apparatus |
CN110944368A (en) * | 2018-09-25 | 2020-03-31 | 电信科学技术研究院有限公司 | Method and equipment for transmitting data in switching process |
Non-Patent Citations (4)
Title |
---|
ERICSSON: "R2-1907318 "User plane aspects of Make-Before-Break"", 《3GPP TSG_RAN\WG2_RL2》 * |
ERICSSON等: "R2-2001753 "Introduction of Even futher Mobility enhancement in E-UTRAN"", 《3GPP TSG_RAN\WG2_RL2》 * |
INTEL CORPORATION: "R2-2000461 "Report of [108#66][LTE NR Mob] Open issues for LTE and NR mobility"", 《3GPP TSG_RAN\WG2_RL2》 * |
QUALCOMM INCORPORATED: "R2-1905785 "User Plane changes to minimize the mobility interruption during DCRS based HO"", 《3GPP TSG_RAN\WG2_RL2》 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2024159543A1 (en) * | 2023-02-03 | 2024-08-08 | 北京小米移动软件有限公司 | Control method and apparatus for transport entity |
Also Published As
Publication number | Publication date |
---|---|
WO2022012480A1 (en) | 2022-01-20 |
CN113938968B (en) | 2023-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP4304212A1 (en) | Multicast service receiving method, multicast service configuration method, terminal, and network side device | |
CN113923713A (en) | Data processing method and device | |
WO2022033560A1 (en) | Capability reporting method, terminal device and network device | |
CN114422094A (en) | PDCP repeated configuration, activation or deactivation method and terminal | |
WO2022012526A1 (en) | Processing method, sending method and related device | |
WO2022042440A1 (en) | User plane data transmission method and network node | |
WO2022012583A1 (en) | Data processing method, data processing apparatus, and first terminal | |
CN113938968B (en) | Data transmission method, device and equipment | |
CN113938977A (en) | Data transmission method, data transmission device, network side equipment and first terminal | |
CN114079878A (en) | Data transmission method and device and communication equipment | |
CN115696216A (en) | Method for receiving multicast broadcast service business and related equipment | |
CN114501490A (en) | Service transfer method, terminal and network side equipment | |
WO2022017480A1 (en) | Method and apparatus for managing target service, and communication device | |
CN113596737A (en) | Data retransmission method and device, target node, source node and terminal | |
JP7473689B2 (en) | Mode switching method, terminal and network side device | |
CN113950007B (en) | Service transmission method, device and communication equipment | |
US20240048503A1 (en) | Resource Release Method and Apparatus, Network Node and Storage Medium | |
CN113950042B (en) | Identification method, transmission method and related equipment | |
WO2023186138A1 (en) | Multicast session/service transmission method, apparatus, chip and module device | |
WO2022206552A1 (en) | Handover method and apparatus, network side device, and terminal | |
WO2022206505A1 (en) | Service data processing method and apparatus, and device | |
WO2023280022A1 (en) | Multi-path communication method, and device | |
CA3196935A1 (en) | Sn synchronization method, apparatus and device for multicast broadcast service, and readable storage medium | |
CN113972966A (en) | Service processing method, device and related equipment | |
CN114501487A (en) | Communication transfer method, terminal and network side equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |