CN117812638A

CN117812638A - Data transmission method, terminal and network side entity

Info

Publication number: CN117812638A
Application number: CN202211216434.6A
Authority: CN
Inventors: 谌丽
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-02
Also published as: WO2024066704A1

Abstract

The invention provides a data transmission method, a terminal and a network side entity, and relates to the technical field of communication, wherein the method comprises the following steps: the terminal generates a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU; the terminal sends the PDCP PDU to a network side entity. The invention can solve the problem that the network side and the terminal in the user-centric network cannot distinguish the data from or to different network side entities, thereby influencing the continuous reliability transmission of the data.

Description

Data transmission method, terminal and network side entity

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method, a terminal, and a network entity.

Background

The sixth generation mobile communication (6G) introduces the idea of a user-centric network, and a terminal can be flexibly connected to one or more Access Points (APs), as shown in fig. 1, which is a schematic diagram of a user-centric network architecture, where a clouding control unit (Cloud-based Control Unit, CCU) includes a management plane and a control plane. Distributed data units (Distributed Data Unit, DDU) are used for localized data acquisition and transmission. A Flexible cell is a Flexible cell serving a UE, and a User Equipment or terminal (UE) is always in the center of the Flexible cell, and an AP within a detectable range of the UE is used as a candidate set to dynamically provide radio link service for the UE.

In a user-centric network, the network side dynamically adjusts the AP and the AP combination to serve the UE, and the UE does not need to execute a switching process when moving among the APs. Therefore, the network side and the UE are scheduled and transmitted by the unique identification of the UE, and the unique cell radio network temporary identification (Cell Radio Network Temporary Identifier, C-RNTI) and the physical cell identification (Physical Cell Identifier, PCI) in the cell of the base station are not used for UE identification. However, when the UE is connected to multiple network side entities (such as DDU or AP) (such as Flexible cell3 in fig. 1), for one service bearer, since there are different network side entities, the network side and the terminal cannot distinguish data from or to the different network side entities, thereby affecting continuous reliable transmission of data.

Disclosure of Invention

The invention provides a data transmission method, a terminal and a network side entity, which solve the problem that in a network with a user as a center, when the terminal is connected with a plurality of network side entities, the network side and the terminal cannot distinguish data from or to different network side entities, so that continuous reliability transmission of the data is affected.

The embodiment of the invention provides a data transmission method, which is applied to a terminal and comprises the following steps:

The terminal generates a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

the terminal sends the PDCP PDU to a network side entity.

Optionally, the terminal is associated with one or more network side entities, where the network side entities are one or more of the following:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the terminal generates a packet data convergence protocol PDCP protocol data unit PDU, including:

the terminal generates PDCP PDU according to the preset information; the preset information is used for indicating whether the indication identifier is added in the PDCP header of the PDCP PDU to indicate the PDCP processing mode for generating the PDCP PDU.

Optionally, the method for generating the packet data convergence protocol PDCP protocol data unit PDU by the terminal or generating the PDCP processing mode of the PDCP PDU includes at least one or a combination of the following:

the terminal identifies the data packet adopting the same encryption algorithm and/or key in the same signaling radio bearer SRB or data radio bearer DRB, and adds the same indication identifier in the PDCP header aiming at the data packet adopting the same encryption algorithm and key;

The terminal identifies the data packet adopting the same integrity protection algorithm and/or key in the same SRB or DRB, and adds the same indication mark in the PDCP header aiming at the data packet adopting the same integrity protection algorithm and key;

the terminal identifies data packets adopting the same robust packet header compression algorithm and/or the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same robust packet header compression algorithm and the same context relation; the terminal identifies data packets adopting the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same context relation;

the terminal identifies the data packets which adopt the same compression algorithm configuration and/or the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets which adopt the same compression algorithm configuration and/or the same context relation.

Optionally, the preset information is predefined by a protocol or configured by a network side.

the terminal determines a network side entity which receives the PDCP PDU;

And the terminal generates PDCP PDU according to the PDCP processing mode corresponding to the network side entity.

Optionally, the terminal generates a packet data convergence protocol PDCP protocol data unit PDU, including one of the following:

the terminal respectively executes target compression processing on the data of different network side entities and respectively generates PDCP PDUs according to the data after the target compression processing;

the terminal jointly executes target compression processing on data of a plurality of network side entities, and generates PDCP PDUs according to the data after the target compression processing;

wherein the target compression process includes: at least one or a combination of a robustness header compression process, an ethernet header compression process and a user data compression process.

Optionally, in the case that different network side entities correspond to different transmission resources, the PDCP PDU does not carry the indication identifier.

Optionally, the case that the different network side entities correspond to different transmission resources includes at least one or a combination of more of the following:

the dynamic scheduling command of the uplink resource indicates that different uplink resources correspond to different network side entities;

indicating different uplink resources to correspond to different network side entities in a pre-configuration signaling of the uplink resources;

Dynamically scheduling different uplink resources to correspond to different network side entities;

different uplink resources are preconfigured to correspond to different network side entities.

Optionally, the indication is identified as reserved N bits of the PDCP header, or the indication is identified as N bits of the PDCP header except reserved bits;

n is a positive integer, and is determined by the maximum number of network side entities to which the terminal can be connected.

the terminal receives a packet data convergence protocol PDCP protocol data unit PDU sent by a network side entity; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and the terminal executes PDCP processing on the PDCP PDU according to the indication identifier.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the terminal performs PDCP processing on the PDCP PDU according to the indication identifier, including at least one or a combination of more of the following:

The terminal identifies PDCP PDUs carrying different indication marks in the same signaling radio bearer SRB or data radio bearer DRB, and executes PDCP decryption processing by adopting the same decryption algorithm and/or key aiming at the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same SRB or DRB, and executes PDCP integrity verification processing by adopting the same integrity verification algorithm and/or key aiming at the PDCP PDUs carrying the same indication mark;

the terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs PDCP robustness packet header decompression processing by adopting the same robustness packet header decompression algorithm and/or context relation aiming at the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs PDCP Ethernet header decompression processing by adopting the same context relation aiming at the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs PDCP user data decompression processing by adopting the same compression algorithm configuration and/or context relation aiming at the PDCP PDUs carrying the same indication marks.

Optionally, the terminal performs PDCP processing on the PDCP PDU according to the indication identifier, including one of the following:

the terminal respectively executes PDCP processing on PDCP PDUs of different network side entities according to the indication mark;

the terminal jointly executes target decompression processing on the data of PDCP PDUs of different network side entities according to the indication mark;

wherein the target decompression process includes: at least one or a combination of a robust header decompression process, an ethernet header decompression process, and a user data decompression process.

Optionally, when the PDCP PDU does not carry the indication identifier, the terminal further includes at least one or more of the following combinations after receiving a PDCP PDU sent by the network side entity:

the terminal determines a network side entity corresponding to the PDCP PDU according to the indication in the dynamic scheduling command of the uplink resource, and executes PDCP processing on the PDCP PDU according to a PDCP processing mode corresponding to the network side entity;

the terminal determines a network side entity corresponding to the PDCP PDU according to the indication in the pre-configuration signaling of the transmission resource, and executes PDCP processing on the PDCP PDU according to the PDCP processing mode corresponding to the network side entity;

The terminal executes PDCP processing on the PDCP PDU according to a PDCP processing mode corresponding to the network side entity according to the network side entity corresponding to the dynamically scheduled uplink resource;

and the terminal executes the PDCP processing of the PDCP PDU according to the PDCP processing mode corresponding to the network side entity according to the network side entity corresponding to the preconfigured uplink resource.

Optionally, the method further comprises:

the terminal sends a PDCP status report to the network entity; wherein, the PDCP status report carries the indication identifier.

Optionally, the sending, by the terminal, a PDCP status report to the network side entity includes:

and the terminal sends the PDCP status report to a plurality of network side entities connected with the terminal.

The embodiment of the invention provides a data transmission method, which is applied to a network side entity and comprises the following steps:

a network side entity generates a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

The network side entity sends the PDCP PDU to a terminal.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, including:

the network side entity generates PDCP PDU according to the preset information; the preset information is used for indicating whether the indication identifier is added in the PDCP header of the PDCP PDU to indicate the PDCP processing mode for generating the PDCP PDU.

Optionally, the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, or generates a PDCP processing mode of the PDCP PDU includes at least one or a combination of more of the following:

the network side entity identifies the data packet adopting the same encryption algorithm and/or key in the same signaling radio bearer SRB or data radio bearer DRB, and adds the same indication identifier in the PDCP header aiming at the data packet adopting the same encryption algorithm and key;

the network side entity identifies the data packet adopting the same integrity protection algorithm and/or key in the same SRB or DRB, and adds the same indication identifier in the PDCP header aiming at the data packet adopting the same integrity protection algorithm and key;

The network side entity identifies data packets adopting the same robustness packet header compression algorithm and/or the same context relation in the same DRB, and adds the same indication identifier in a PDCP header aiming at the data packets adopting the same robustness packet header compression algorithm and the same context relation; the terminal identifies data packets adopting the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same context relation;

the network side entity identifies the data packets which adopt the same compression algorithm configuration and/or the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets which adopt the same compression algorithm configuration and/or the same context relation.

Optionally, the network side entity is a first network side entity, and the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, including one of the following:

the first network side entity executes target compression processing on the data of the first network side entity and generates PDCP PDU according to the data after the target compression processing;

The first network side entity receives target compression processed data sent by a second network side entity and generates PDCP PDU according to the target compression processed data;

the target compression processing data sent by the second network side entity is determined after the second network side entity performs target compression processing on the data of the first network side entity, and the target compression processing includes: at least one or a combination of a robustness header compression process, an ethernet header compression process and a user data compression process.

Optionally, the case that different network side entities correspond to different transmission resources includes at least one or a combination of more of the following:

the dynamic scheduling command of the downlink resource indicates that different downlink resources correspond to different network side entities;

indicating different downlink resources to correspond to different network side entities in a pre-configuration signaling of the downlink resources;

dynamically scheduling different downlink resources to correspond to different network side entities;

different downlink resources are preconfigured to correspond to different network side entities.

the network entity receives a packet data convergence protocol PDCP protocol data unit PDU sent by the terminal; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

the network side entity performs PDCP processing on the PDCP PDU.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the network side entity is a second network side entity, and the network side entity performs PDCP processing on the PDCP PDU, including at least one or a combination of more of the following:

the second network side entity executes PDCP processing on the PDCP PDU corresponding to the second network side entity according to the indication mark;

The second network side entity receives the data after decryption processing and integrity verification processing sent by the first network side entity, and performs target decompression processing on the data after decryption processing and integrity verification processing of different first network side entities;

the data after decryption processing and integrity verification processing sent by the first network side entity is determined by the first network side entity by executing decryption processing and integrity verification processing on the PDU corresponding to the first network side entity according to the indication identifier; the target compression process includes: at least one or a combination of a robust header decompression process, an ethernet header decompression process, and a user data decompression process.

Optionally, in the case that the PDCP PDU does not carry the indication identifier, the network side entity receives a packet data convergence protocol PDCP protocol data unit PDU sent by the network side entity, including at least one or a combination of more of the following:

the network side entity receives the PDCP PDU at the uplink resource corresponding to the network side entity according to the indication in the dynamic scheduling command of the uplink resource;

the network side entity receives the PDCP PDU at the uplink resource corresponding to the network side entity according to the indication in the pre-configuration signaling of the uplink resource;

The network side entity receives the PDCP PDU at the dynamically scheduled uplink resource;

the network side entity receives the PDCP PDU at the preconfigured uplink resource.

Optionally, the method further comprises:

the network side entity sends a PDCP status report to the terminal; wherein, the PDCP status report carries the indication identifier.

Optionally, the network side entity sends a PDCP status report to the terminal, including:

and any network entity connected with the terminal sends the PDCP status report to the terminal.

The embodiment of the invention provides a terminal, which comprises a memory, a transceiver and a processor;

wherein the memory is used for storing a computer program; the transceiver is used for receiving and transmitting data under the control of the processor; the processor is configured to read the computer program in the memory and perform the following operations:

generating PDCP PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

And sending the PDCP PDU to a network side entity.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

generating PDCP PDU according to the preset information; the preset information is used for indicating whether the indication identifier is added in the PDCP header of the PDCP PDU to indicate the PDCP processing mode for generating the PDCP PDU.

Optionally, the processor is configured to read the computer program in the memory and perform at least one or more of the following operations:

the terminal determines a network side entity which receives the PDCP PDU;

Optionally, the processor is configured to read the computer program in the memory and perform one of the following operations:

receiving PDCP PDU sent by a network side entity; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, in the case that the PDCP PDU does not carry the indication identifier, the processor is further configured to read a computer program in the memory and perform at least one or more of the following operations:

transmitting a PDCP status report to the network side entity; wherein, the PDCP status report carries the indication identifier.

and sending the PDCP status report to a plurality of network side entities connected with the terminal.

The embodiment of the invention provides a network side entity, which comprises a memory, a transceiver and a processor;

Generating a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

the network side entity sends the PDCP PDU to a terminal.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the network side entity is a first network side entity, and the processor is configured to read the computer program in the memory and perform one of the following operations:

receiving a packet data convergence protocol PDCP protocol data unit PDU sent by a terminal; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and performing PDCP processing on the PDCP PDU.

a network side PDCP entity;

a distributed data unit, DDU, entity;

An access point, AP, entity.

Optionally, the network side entity is a second network side entity, and the processor is configured to read the computer program in the memory and perform one or more of the following operations:

Optionally, in the case that the PDCP PDU does not carry the indication identifier, the processor is configured to read a computer program in the memory and perform one or more of the following operations:

transmitting a PDCP status report to the terminal; wherein, the PDCP status report carries the indication identifier.

An embodiment of the present invention provides a terminal including:

a first generating unit, configured to generate a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and the first sending unit is used for sending the PDCP PDU to the network side entity.

An embodiment of the present invention provides a terminal including:

a first receiving unit, configured to receive a packet data convergence protocol PDCP protocol data unit PDU sent by a network side entity; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and the first processing unit is used for executing PDCP processing on the PDCP PDU according to the indication identifier.

An embodiment of the present invention provides a network side entity, including:

a second generating unit, configured to generate a PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and the second sending unit is used for sending the PDCP PDU to the terminal.

A second receiving unit, configured to receive a packet data convergence protocol PDCP protocol data unit PDU sent by the terminal; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

and the second processing unit is used for executing PDCP processing on the PDCP PDU.

An embodiment of the invention provides a processor-readable storage medium having stored thereon a computer program, characterized in that the computer program when executed by a processor realizes the steps of the data transmission method described above.

The technical scheme of the invention has the beneficial effects that:

in the above scheme, in uplink transmission or downlink transmission, the PDCP PDU transmitted between the terminal and the network side entity carries an indication identifier for indicating the network side entity corresponding to the PDCP PDU, so that in uplink transmission or downlink transmission, PDCP PDUs from or to different network side entities can be distinguished between the terminal and the network side entity, thereby ensuring that data in the network with the user as the center can be continuously and reliably transmitted.

Drawings

FIG. 1 shows a schematic diagram of a user centric network architecture;

fig. 2 shows a CU-DU partitioning diagram of a 5G base station;

FIG. 3 is a diagram showing 5G user plane protocol stack partitioning;

FIG. 4 is a diagram showing 5G control plane protocol stack partitioning;

FIG. 5 shows a 5G DAPS schematic;

fig. 6 shows one of flowcharts of a data transmission method at a terminal side according to an embodiment of the present invention;

fig. 7 shows a second flowchart of a data transmission method at the terminal side according to an embodiment of the present invention;

fig. 8 shows one of flowcharts of a data transmission method of a network side entity according to an embodiment of the present invention;

fig. 9 shows a second flowchart of a data transmission method of a network entity according to an embodiment of the present invention;

fig. 10a shows one of schematic diagrams of a PDCP header including an indication identifier corresponding to encryption and decryption and/or integrity protection and verification according to an embodiment of the present invention;

fig. 10b is a schematic diagram showing a PDCP header including encryption and decryption and/or integrity protection and verification corresponding indication marks according to an embodiment of the present invention;

fig. 11a shows one of schematic diagrams of a PDCP header including an indication identifier corresponding to ROHC according to an embodiment of the present invention;

fig. 11b shows a second schematic diagram of a PDCP header including indication marks corresponding to ROHC according to an embodiment of the present invention;

fig. 12a shows one of schematic diagrams of adding indication marks in an ROHC feedback PDCP control PDU according to an embodiment of the present invention;

Fig. 12b is a schematic diagram showing a second embodiment of adding indication marks in an ROHC feedback PDCP control PDU;

FIG. 13a is a diagram illustrating one of the schemes of adding indication marks to an EHC feedback PDCP control PDU in accordance with an embodiment of the present invention;

FIG. 13b is a diagram illustrating a second embodiment of adding indication marks to an EHC feedback PDCP control PDU;

FIG. 14a is a schematic diagram showing adding indication identifier in a UDC feedback PDCP control PDU according to an embodiment of the present invention;

FIG. 14b is a diagram showing a second embodiment of adding indication marks to a UDC feedback PDCP control PDU;

FIG. 15 shows one of the block diagrams of the terminal of an embodiment of the invention;

FIG. 16 shows a second block diagram of a terminal according to an embodiment of the invention;

FIG. 17 shows a third block diagram of a terminal according to an embodiment of the invention;

FIG. 18 shows one of the block diagrams of the network side entity of the embodiment of the present invention;

FIG. 19 is a second block diagram of a network entity according to an embodiment of the present invention;

fig. 20 shows a third block diagram of a network-side entity according to an embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided merely to facilitate a thorough understanding of embodiments of the invention. It will therefore be apparent to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

In addition, the terms "system" and "network" are often used interchangeably herein.

The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G system. For example, suitable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (general packet Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR), and the like. Terminal devices and network devices are included in these various systems. Core network parts such as evolved packet system (Evolved Packet System, EPS), 5G system (5 GS) etc. may also be included in the system.

Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmissions may each be made between a network device and a terminal device using one or more antennas, and the MIMO transmissions may be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.

In the embodiment of the invention, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "plurality" in the embodiments of the present application means two or more, and other adjectives are similar thereto.

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The following describes a 5G wireless network system and a 6G wireless network system, respectively:

in the 5G wireless network system, the 5G base station gNB may be divided into a Central Unit (CU) and a Distributed Unit (DU), as shown in fig. 2, the CU includes a Central Unit control plane (Central Unit Control Plane, CU-CP) and a Central Unit user plane (Central Unit User Plane, CU-UP), and a transmission/reception Point (TRP) is connected below the DU. The partitioning of the 5G control plane and user plane protocol stacks between CUs, DUs is shown in fig. 3 and 4, where the traffic data adaptation protocol (Service Data Adaptation Protocol, SDAP) and PDCP layer are at CUs, radio link control (Radio Link Control, RLC), medium access control (Medium Access Control, MAC) and physical layer are at DUs.

For one traffic bearer, the user plane anchor is SDAP and PDCP, which is typically focused on the PDCP layer since SDAP is responsible only for quality of service (Quality of Service, qoS) flow mapping to data radio bearers (Data Radio Bearer, DRB). When the anchor point mode of the user plane of the network side changes, namely the SDAP layer and the PDCP layer change, the most typical scene is CU change, the SDAP layer and the PDCP layer need to be rebuilt, and the corresponding functions are reconfigured and started. This scenario corresponds to inter-CU handover in 5G, where traffic data is interrupted due to re-establishment of the SDAP and PDCP layers and other handover procedures. For the PDCP layer, after PDCP change (re-establishment), security (key) is changed, and the context of the robust header compression (Robust Header Compression, ROHC), the ethernet header compression (Ethernet Header Compression, EHC) and the user plane data compression (User Data Compression, UDC) is affected.

In a 5G system, a dual-active protocol stack (Dual Active Protocol Stack, DAPS) switching mechanism is introduced, and during the switching process, the UE and the source cell simultaneously maintain connection in a dual-protocol stack manner. The UE maintains 2 sets of security keys (one set corresponding to the source cell and the other set corresponding to the target cell). The UE performs integrity protection and decryption according to the corresponding key when receiving the data packet. The UE orders the data packets received from the source cell and the target cell. Since the scheduling identities (e.g., C-RNTI, PCI, etc.) employed by the source cell and the target cell are different, the UE can identify data from different PDCP entities and perform corresponding operations according to ciphering, integrity protection, header compression, etc. configurations of the corresponding PDCP entities, respectively, as shown in fig. 5.

As with continued reference to fig. 1,6G, introducing the idea of a user centric network, a terminal can flexibly connect to one or more APs, which if an AP is an integrated base station, then it is a base station that comprises full functionality; if the AP is based on the distributed structure shown in fig. 1, the AP corresponds to TRP. Wherein, the CCU executes 5G traditional control plane function, also executes UE context management, and executes functions such as AP/TRP selection. The DDU may perform the CU-UP function described above, i.e., the SDAP, PDCP layer functions are performed at the DDU. The UE is associated with one or more APs in a flexible cell whose coverage is formed by all APs that can be detected by the UE to provide wireless access services to the UE.

Because in the user-centric network, the network side dynamically adjusts the AP and the AP combination to serve the UE, the UE does not need to execute a switching process when moving between the APs. Therefore, the network side and the UE use the unique identification of the UE for scheduling and transmission, and the unique C-RNTI and PCI inside the cell of the base station are not used for carrying out the UE identification. When the UE is connected to multiple network side entities, for a service bearer, due to the different network side entities, the network side and the terminal cannot distinguish data from or to the different network side entities, especially for the case that multiple APs connected to the UE are deployed in the same frequency, and cannot distinguish data paths through physical layer transmission resources, thereby affecting continuous reliable transmission of data.

The invention provides a data transmission method, a terminal and a network side entity, which solve the problem that a user is in a central network, and the network side and the terminal cannot distinguish data from or to different network side entities, so that continuous reliability transmission of the data is affected. The method and the terminal (or the network side entity) are based on the same application conception, and because the principle of solving the problem by the method and the terminal (or the network side entity) is similar, the implementation of the method and the terminal (or the network side entity) can be referred to each other, and the repetition is omitted.

As shown in fig. 6, an embodiment of the present invention provides a data transmission method, which specifically includes the following steps:

step 61: the terminal generates PDCP PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU.

Optionally, the terminal is associated with one or more network side entities, the network side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the PDCP PDU is a PDCP data PDU, or a PDCP control PDU.

Optionally, the indication is identified as reserved N bits of the PDCP header, or the indication is identified as N bits of the PDCP header other than reserved bits. That is, the reserved N bits of the PDCP header are used to indicate the network side entity corresponding to the PDCP PDU, or other bits (e.g., a new N bit may be used) except the reserved N bits in the PDCP header are used to indicate the network side entity corresponding to the PDCP PDU. For example, for uplink transmission, the indication flag (or N bits) is used to indicate to which network side entity the PDCP PDU is transmitted.

N is a positive integer, and is determined by the maximum number of network side entities to which the terminal can be connected. For example, if the terminal is connected to two network side entities at most, a 1bit indication identifier can be adopted; if the terminal is connected to 4 network side entities at most, 2bit indication identification can be adopted, and so on.

Step 62: the terminal sends the PDCP PDU to a network side entity.

For example: the terminal is connected with more than one network side entity and can carry out uplink and/or downlink data transmission, and in particular, when the terminal and the network side entities have different air interface transmission channels, the terminal carries an indication identifier for indicating the network side entity corresponding to the PDCP PDU in the PDCP PDU sent to the network side entity by the terminal.

In the above scheme, the PDCP PDU generated by the terminal carries an indication identifier for indicating the network side entity corresponding to the PDCP PDU, so that when the terminal sends the PDCP PDU to the network side, the corresponding network side entity can determine the PDCP PDU belonging to itself based on the indication identifier, thereby ensuring that the data in the network with the user as the center can be continuously and reliably transmitted.

Optionally, the terminal generates a packet data convergence protocol PDCP protocol data unit PDU comprising at least one or a combination of:

the terminal identifies the data packet adopting the same encryption algorithm and/or key in the same signaling radio bearer SRB or data radio bearer DRB, and adds the same indication identifier in the PDCP header aiming at the data packet adopting the same encryption algorithm and key; for example: for secure encryption and decryption (Ciphering and deciphering): and identifying data packets adopting different encryption algorithms and/or keys in the same signaling radio bearer SRB or data radio bearer DRB, wherein the data packets adopting the same encryption algorithm and key adopt the same indication identifier.

The terminal identifies the data packet adopting the same integrity protection algorithm and/or key in the same SRB or DRB, and adds the same indication mark in the PDCP header aiming at the data packet adopting the same integrity protection algorithm and key; for example: for integrity protection and verification (Integrity protection and verification): and identifying data packets adopting different integrity protection algorithms and/or keys in the same SRB or DRB, wherein the data packets adopting the same integrity protection algorithm and key adopt the same indication identifier.

The terminal identifies data packets adopting the same robust packet header compression algorithm and/or the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same robust packet header compression algorithm and the same context relation; for example: for ROHC: and identifying data packets with different header compression algorithms and/or contexts in the same DRB, wherein the data packets with the same header compression algorithm and the data packets with the same context relationship adopt the same PDCP header identification. Optionally, the same indication identity may also be used for classification of associated PDCP control PDUs, such as PDCP control PDU (PDCP Control PDU format for interspersed ROHC feedback) for ROHC feedback.

The terminal identifies data packets adopting the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same context relation; for example: for EHC: in the same DRB, data packets with different contexts are identified, and data packets with the same context relationship use the same PDCP header identification. The same indication identity may also be employed for classification of associated PDCP control PDUs, such as PDCP control PDU (PDCP Control PDU format for EHC feedback) for EHC feedback.

The terminal identifies the data packets which adopt the same compression algorithm configuration and/or the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets which adopt the same compression algorithm configuration and/or the same context relation. For example: for UDC: in the same DRB, data packets with different configurations and/or different contexts are identified, and data packets with the same compression algorithm configuration (such as buffer size and dictionary) and context are identified by the same indication. Optionally, PDCP control PDU (PDCP Control PDU format for UDC feedback) for associated PDCP control PDUs, such as for UDC feedback, may also be classified with the same indication identity.

Optionally, the terminal generates PDCP PDUs, including:

Specifically, the preset information predefined by a protocol or configured by a network side, that is, whether the indication identifier is added to the PDCP header of the PDCP PDU by the protocol or configured by the network side, indicates a PDCP processing manner of generating the PDCP PDU, which may be explicitly or implicitly indicated. For example: the network side entities AP1 and AP2 are respectively corresponding to the network side entities AP1 and AP1, and the network side entity AP1 is set as an anchor AP or a master AP, so that the indication for AP1 may not be performed, and the indication for AP2 may be performed. In this way, when the terminal generates the PDCP PDU, according to the preset information, for the network side entity indicating that the PDCP processing mode of generating the PDCP PDU needs to be added with the indication identifier, a corresponding indication identifier is added in the PDCP PDU sent thereto; for a network side entity that does not indicate that the indication identifier needs to be added to indicate the PDCP processing mode of generating the PDCP PDU, a corresponding indication identifier that is not added in the PDCP PDU sent thereto may be used.

For example: the preset information is used for indicating whether the indication identifier is added in the PDCP header of the PDCP PDU to indicate the PDCP processing mode for generating the PDCP PDU, and comprises at least one or a combination of more of the following steps:

Optionally, the terminal generates PDCP PDUs, including: the terminal determines a network side entity which receives the PDCP PDU; and the terminal adds the indication identifier corresponding to the network side entity in the PDCP header of the PDCP PDU sent to the network side entity.

Optionally, the terminal generates PDCP PDUs, including: the terminal determines a network side entity which receives the PDCP PDU; and the terminal generates PDCP PDU according to the PDCP processing mode corresponding to the network side entity.

Specifically, the manner in which the terminal determines the network side entity that receives the PDCP PDU includes, but is not limited to, a combination of at least one or more of the following:

the terminal determines a network side entity for receiving the PDCP PDU based on the indication in the dynamic scheduling command of the uplink resource; for example: explicit indication of which PDCP entity or DDU or AP or TRP the uplink transmission is for in the dynamic scheduling command of the uplink resource;

the terminal determines a network side entity for receiving the PDCP PDU based on an indication in a pre-configuration signaling of an uplink resource; for example: explicit indication of which PDCP entity or DDU or AP or TRP the uplink transmission is for in the pre-configuration signaling of the uplink resource;

The terminal determines a network side entity receiving the PDCP PDU according to a network side entity corresponding to the dynamic scheduling or preconfigured uplink resource, namely, the network side entity implicitly indicates uplink transmission through a dynamic scheduling command of the uplink resource or a preconfigured signaling of the uplink resource; for example: the dynamic scheduling or pre-configuring that the APs to which the different PDCP entities belong have different transmission resources (such as different frequency bands), the terminal can determine which PDCP entity is transmitted by the uplink transmission based on the uplink transmission resources currently used;

a network side entity for determining to receive the PDCP PDU is realized by a terminal; for example: the terminal may decide a network side entity receiving the PDCP PDU according to a channel quality measurement, wherein the channel quality measurement may include, but is not limited to, one of the following: reference signal received power (Reference Signal Received Power, RSRP), reference signal received quality (Reference Signal Received Quality, RSRQ), and the like.

It should be further noted that, when different network side entities correspond to different transmission resources, when the terminal generates a PDCP PDU (i.e., sends the PDCP PDU to the network side entity), the indication identifier corresponding to the network side entity may or may not be added to the PDCP PDU. Wherein the different network side entities correspond to different transmission resources, and include at least one or a combination of more of the following: the dynamic scheduling command of the uplink resource indicates that different uplink resources correspond to different network side entities; indicating different uplink resources to correspond to different network side entities in a pre-configuration signaling of the uplink resources; dynamically scheduling different uplink resources to correspond to different network side entities; different uplink resources are preconfigured to correspond to different network side entities.

For example, the terminal may determine, based on an indication in a dynamic scheduling command of an uplink resource, or based on an indication in a pre-configuration signaling of the uplink resource, or according to a network side entity corresponding to the dynamically scheduled or pre-configured uplink resource, a network side entity receiving the PDCP PDU, where when the terminal generates the PDCP PDU sent to the network side entity, the terminal may or may not add an indication identifier corresponding to the network side entity in the PDCP PDU. In the case that the terminal determines the network side entity receiving the PDCP PDU, the terminal needs to add an indication identifier corresponding to the network side entity in the PDCP PDU when generating the PDCP PDU sent to the network side entity.

Further, in case that the terminal determines the network side entity that receives the PDCP PDU, the terminal may generate the PDCP PDU according to the preset information and in a PDCP processing manner corresponding to the network side entity.

Optionally, the terminal generates PDCP PDUs including one of:

the terminal respectively executes target compression processing on the data of different network side entities and respectively generates PDCP PDUs according to the data after the target compression processing; wherein the target compression process includes: at least one or a combination of a robustness header compression process, an ethernet header compression process and a user data compression process. The method comprises the following steps: the terminal is connected with more than one network side entity and can carry out uplink and/or downlink data transmission, specifically, under the condition that different air interface transmission channels exist between the terminal and the network side entities, the terminal sends different network side entities to the data of one DRB according to the uplink resource allocation of the network side entity, and can respectively execute any one of different compression algorithms, contexts, sequences and the like for different network side entities to generate PDCP PDUs sent to different network side entities. Of course, when the terminal generates PDCP PDUs for different network side entities, it may not need to perform any one of different compression algorithms, contexts, and sequences.

For example: when the terminal connects network side entities AP1 and AP2 in a flexible cell and the terminal needs to send data to the network side entities AP1 and AP2, the terminal executes robustness packet header compression processing, ethernet header compression processing, user data compression processing and the like for the data of the AP1, then executes integrity protection processing, encryption processing and the like, and adds a PDCP header to generate a PDCP PDU1 corresponding to the AP 1; after performing the robustness packet header compression process, the ethernet header compression process, the user data compression process on the data of the AP2, performing the integrity protection process, the ciphering process, and the like, adding the PDCP header to generate a PDCP PDU2 corresponding to the AP 2. At this time, any of compression algorithms, contexts, ranks, and the like, which the terminal performs with respect to the data of the AP1 and the AP2, may be the same or different.

The terminal jointly executes target compression processing on data of a plurality of network side entities, and generates PDCP PDUs according to the data after the target compression processing; wherein the target compression process includes: at least one or a combination of a robustness header compression process, an ethernet header compression process and a user data compression process. The method comprises the following steps: the terminal is connected with more than one network side entity and can carry out uplink and/or downlink data transmission, specifically, under the condition that different air interface transmission channels exist between the terminal and the network side entities, the terminal carries out compression processing on data of one DRB according to the same compression algorithm and context, and then sends different network side entities according to uplink resource allocation of the network side entities, and any distinguishing actions such as different compression algorithms, contexts, sequencing and the like are not needed to be adopted for different network side entities.

For example: when the terminal connects network side entities AP1 and AP2 in a flexible cell and the terminal needs to send data to the network side entities AP1 and AP2, the terminal performs robust packet header compression processing, ethernet header compression processing, user data compression processing and the like on the data of AP1 and AP2, performs integrity protection processing, encryption processing and the like on the data after the compression processing of AP1, adds PDCP header to generate PDCP PDU1 corresponding to AP1, performs integrity protection processing, encryption processing and the like on the data after the compression processing of AP2, and adds PDCP header to generate PDCP PDU2 corresponding to AP 2.

The embodiment of the invention also provides a data transmission method, which comprises the following steps:

the terminal determines a network side entity corresponding to uplink transmission according to a dynamic scheduling command of uplink resources and/or a pre-configuration signaling of the uplink resources; wherein, the dynamic scheduling command of the uplink resource and/or the pre-configuration signaling of the uplink resource indicate that different network side entities correspond to different transmission resources;

and the terminal sends the PDCP PDU to the network entity.

Optionally, the PDCP PDU does not carry the indication identifier.

Optionally, the dynamic scheduling command of the uplink resource and/or the pre-configured signaling of the uplink resource may explicitly or implicitly indicate different network side entities corresponding to different uplink resources. The different network side entities corresponding to different uplink resources are specifically: under the condition that the terminal is connected to a plurality of network side entities, different network side entities allocate different transmission resources for the terminal, and uplink resources allocated among the network side entities are not overlapped. In this way, for different network side entities connected with the terminal, different network side entities corresponding to uplink transmission and/or downlink transmission can be distinguished based on different resources allocated between the network side entities, and at this time, the indication identifier may not be carried in the PDCP PDU of uplink transmission or downlink transmission.

For example: the situation that the different network side entities correspond to different transmission resources comprises at least one or a combination of more of the following: the dynamic scheduling command of the uplink resource indicates that different uplink resources correspond to different network side entities; indicating different uplink resources to correspond to different network side entities in a pre-configuration signaling of the uplink resources; dynamically scheduling different uplink resources to correspond to different network side entities; different uplink resources are preconfigured to correspond to different network side entities. In particular, reference may be made to the above embodiments, and in order to avoid repetition, the description is omitted here.

As shown in fig. 7, an embodiment of the present invention provides a data transmission method, including the following steps:

step 71: the terminal receives PDCP PDU sent by the network side entity; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU.

Alternatively, the process may be carried out in a single-stage,

the terminal is associated with one or more network side entities, the network side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the PDCP PDU is a PDCP data PDU, or a PDCP control PDU.

Step 72: and the terminal executes PDCP processing on the PDCP PDU according to the indication identifier.

Specifically, the terminal may identify and obtain the network side entity corresponding to the PDCP PDU according to the indication identifier. Further, the terminal may perform PDCP processing on the PDCP PDU according to a PDCP processing manner corresponding to the network side entity. For example: when the network side entity corresponding to the PDCP PDU is pre-defined in protocol or the network side is configured with the PDCP processing mode that needs to add the indication identifier to the PDCP header of the PDCP PDU to indicate the PDCP PDU generation, PDCP processing may be performed on the PDCP PDU based on the PDCP processing mode indicated by the indication identifier.

Optionally, the PDCP processing includes a combination of at least one or more of: decryption processing; integrity verification processing; decompressing the robust packet header; decompressing the Ethernet head; and (5) user data decompression processing.

In the above scheme, the terminal receives the indication identifier of the network side entity corresponding to the PDCP PDU carried in the PDCP PDU sent by the network side entity, so that the terminal can identify and obtain the network side entity corresponding to the PDCP PDU according to the indication identifier, and further can execute PDCP processing on the PDCP PDU based on the PDCP processing mode corresponding to the network side entity, thereby ensuring that the data in the network with the user as the center can be continuously and reliably transmitted.

Optionally, the terminal performs PDCP processing on the PDCP PDU according to the indication identifier, including at least one or a combination of the following:

the terminal identifies PDCP PDUs carrying different indication marks in the same SRB or DRB, and executes PDCP decryption processing by adopting the same decryption algorithm and/or key aiming at the PDCP PDUs carrying the same indication mark; for example: for secure ciphering and deciphering, packets employing the same deciphering algorithm and/or key employ the same indication identifier, and the terminal may identify PDCP PDUs employing different deciphering algorithms and/or keys in one SRB or DRB based on the indication identifier, and perform PDCP deciphering processing for PDCP PDUs carrying the same indication identifier using the same deciphering algorithm and/or key.

The terminal identifies PDCP PDUs carrying different indication marks in the same SRB or DRB, and executes PDCP integrity verification processing by adopting the same integrity verification algorithm and/or key aiming at the PDCP PDUs carrying the same indication mark; for example: for integrity protection and verification, the data packets adopting the same integrity protection algorithm and/or key adopt the same indication identifier, the terminal can identify PDCP PDUs adopting different integrity protection algorithms and/or keys in the same SRB or DRB based on the indication identifier, and execute PDCP integrity verification processing by adopting the same integrity verification algorithm and/or key aiming at the PDCP PDUs carrying the same indication identifier.

The terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs robust packet header decompression processing by adopting the same header decompression algorithm and/or context relation for the PDCP PDUs carrying the same indication marks; for example: for ROHC, the same header compression algorithm and/or the same packet with the same context are/is used for the same indication identifier, the terminal identifies PDCP PDUs with different header decompression algorithms and/or contexts in the same DRB based on the indication identifier, and performs robust header decompression processing for PDCP PDUs carrying the same indication identifier by using the same header decompression algorithm and/or context. Optionally, the associated PDCP control PDUs are also classified with the same indication identity.

The terminal identifies PDCP PDUs of the same DRB, and performs Ethernet header decompression processing by adopting the same context relation aiming at the PDCP PDUs carrying the same indication identifier; for example: for the EHC, the data packets adopting the same context relation adopt the same indication identifier, the terminal identifies PDCP PDUs adopting different context relations in the same DRB based on the indication identifier, and performs Ethernet header decompression processing on the PDCP PDUs carrying the same indication identifier by adopting the same context relation. Alternatively, the associated PDCP control PDUs may also be classified with the same indication identity.

The terminal identifies PDCP PDU of the same DRB and executes PDCP user data decompression processing by adopting the same user data compression algorithm configuration and/or context relation aiming at the PDCP PDU carrying the same indication mark. For example: for UDC, the data packets adopting the same context relationship adopt the same indication identifier, the terminal identifies PDCP PDUs adopting different context relationships in the same DRB based on the indication identifier, and performs Ethernet header decompression processing on the PDCP PDUs carrying the same indication identifier by adopting the same context relationship. Alternatively, the associated PDCP control PDUs may also be classified with the same indication identity.

the terminal jointly executes target decompression processing on the data of PDCP PDUs of different network side entities according to the indication mark; the method comprises the following steps: the terminal receives PDCP PDUs from different network side entities, the PDCP PDUs are jointly sequenced according to the same compression algorithm and/or context, target decompression processing is sequentially carried out on the PDCP PDUs from different network side entities, and further optionally, if the corresponding DRB of the PDCP is configured with encryption and/or integrity protection, the terminal executes target decompression processing after executing decryption and integrity verification on the PDCP PDUs.

For example: in the case that the terminal is connected to a plurality of network side entities, if the terminal receives PDCP PDUs transmitted by the plurality of network side entities, as an implementation manner, the terminal may perform PDCP processing for PDCP PDUs transmitted by different network side entities according to PDCP processing modes corresponding to the corresponding network side entities, respectively. As yet another implementation, the terminal may identify an indication identifier in the PDCP PDU, perform ROHC header decompression, EHC header decompression and UDC verification, joint ordering, etc. for PDCP PDUs of different network side entities according to the same compression algorithm and/or context, etc. Optionally, when the corresponding radio bearer is configured with ciphering and/or integrity protection, the terminal may identify an indication identifier in the PDCP PDU, and perform decryption processing and integrity verification processing separately for the PDCP PDU corresponding to the same network side entity, and then perform ROHC header decompression, EHC header compression, UDC verification, joint ordering, and the like on data after decryption processing and integrity verification processing for different network entities according to the same compression algorithm and/or context. This approach requires that different network side entities coordinate the addition of PDCP SNs in the order of header compression or data compression so that the terminal can perform header decompression or UDC verification in the correct order after receiving it. The terminal performs PDCP packet ordering uniformly on packets from different network side entities.

Optionally, in the case that the PDCP PDU does not carry the indication identifier, after the terminal receives a PDCP protocol data unit PDU sent by the network side entity, the method further includes at least one or more of the following combinations:

Optionally, the data transmission method further includes:

In this embodiment, when the terminal receives that the PDCP PDU sent by the network side entity carries the indication identifier, the terminal sends a PDCP status report to the network side entity, which also carries the corresponding indication identifier, so that the network side device can learn the PDCP PDU corresponding to the PDCP status report or the network side entity. Alternatively, the PDCP status report format may be based on the status report format of the existing protocol.

Optionally, the terminal sends a PDCP status report to the network side entity, including:

In this embodiment, the PDCP status report sent by the uplink terminal may be received by a plurality of network side entities (e.g., DDUs) connected to the terminal.

It should be noted that, the terminal may employ a plurality of protocol stacks corresponding to the network side PDCP entities, respectively; or, the terminal has only one protocol stack, and in one PDCP entity, data from or to PDCP entities of different network sides is processed separately.

The terminal according to the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more Core Networks (CNs) via a radio access Network (Radio Access Network, RAN), which may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access Network. Such as personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDAs), and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (access terminal), user terminal device (user terminal), user agent (user agent), user equipment (user device), and the embodiments of the present application are not limited.

As shown in fig. 8, an embodiment of the present invention provides a downlink network side method, which includes the following steps:

step 81: a network side entity generates PDCP PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

step 82: the network side entity sends the PDCP PDU to a terminal.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

For example: when the network side entity generates PDCP PDUs, different network side entities can only process the respective PDCP PDUs; if the network side entity 1 carries out PDCP layer processing on the data to be sent to the terminal, PDCP PDU is generated; the network side entity 2 performs PDCP layer processing for data to be transmitted to the terminal, generates PDCP PDUs, and the like. Or, after performing header compression processing on data of different network side entities by one network side entity (such as the PDCP entity of the anchor AP or the main AP), the data after header compression processing is sent to the PDCP entity corresponding to each to perform ciphering and integrity protection processing, so as to generate PDCP PDUs.

Optionally, the case that different network side entities correspond to different transmission resources includes at least one or a combination of the following:

Optionally, the indication is identified as reserved N bits of the PDCP header, or the indication is identified as N bits of the PDCP header other than reserved bits;

The data transmission method of the network side entity in the embodiment of the invention is similar to the uplink data transmission method of the terminal side, and can achieve the same technical effect, and in order to avoid repetition, the similarities are not repeated.

As shown in fig. 9, the embodiment of the present invention further provides a data transmission method, which includes the following steps:

Step 91: a network side entity receives PDCP PDU sent by a terminal; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

step 92: the network side entity performs PDCP processing on the PDCP PDU.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

For example: when the network side entity performs PDCP processing of PDCP PDUs, different network side entities may perform PDCP processing only for respective PDCP PDUs; if the network side entity 1 performs PDCP layer processing for the PDCP PDU sent to itself; the network side entity 2 performs PDCP layer processing or the like for PDCP PDUs transmitted to itself. Or, after receiving the data packet, the different PDCP entities on the network side complete decryption and integrity verification, submit the data packet to the same PDCP entity (such as the PDCP entity of the anchor AP or the main AP), and perform ROHC header decompression, EHC header compression and UDC verification. PDCP packet ordering (reordering) is also uniformly implemented in a PDCP entity performing the ROHC, EHC, UDC function, etc.

Optionally, the data transmission method further includes:

In this embodiment, when the terminal receives that the PDCP PDU sent by the network side entity carries the indication identifier, the terminal sends a PDCP status report to the network side entity, which also carries the corresponding indication identifier, so that the network side device can learn the PDCP PDU corresponding to the PDCP status report or the network side entity. Alternatively, the PDCP status report format may be based on the status report format of the existing protocol. For the downlink PDCP status report, any network side entity (e.g., an AP corresponding to the DDU) may send the downlink PDCP status report to the terminal.

The network device according to the embodiment of the present application may be a base station, where the base station may include a plurality of cells for providing services for a terminal. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. The network device may be operable to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), and the like. In some network structures, the network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

The following describes a data transmission method according to an embodiment of the present invention with reference to specific embodiments:

example 1: protection and verification of encryption and decryption and/or integrity

Process 1: optionally, the network side sends a configuration command to the terminal, the configuration command indicates that the terminal needs to add an indication identifier for encryption and decryption and/or integrity protection and verification, and further optionally, the configuration command indicates a correspondence between an indication message in a PDCP header of the PDCP PDU and the network side entity. If the configuration command is not added in the protocol, the protocol defaults to the PDCP PDU format, and the indication mark is arranged in the PDCP header of the PDCP PDU format.

Process 2:

for downlink transmission, the terminal receives the PDCP PDU, and determines the processing mode of the PDCP PDU according to the configuration of the network side and the PDCP PDU format, and the PDCP PDU format is shown below.

For uplink transmission, the terminal needs to determine the network side entity to which the data packet needs to be sent, where the manner in which the terminal determines to send the data packet to a different network side entity is any one of the following:

the base station indicates which network side entity the uplink transmission is directed to in a dynamic scheduling command of the uplink resource or a pre-configuration signaling of the uplink resource. Alternatively, the terminal may not add the indication identifier to the PDCP header in this manner.

When the APs to which different PDCP entities belong have different transmission resources (e.g., different frequency bands), the terminal may determine to which PDCP entity the uplink transmission is directed based on the currently used uplink transmission resources. Alternatively, the terminal may not add the indication identifier to the PDCP header in this manner.

The terminal performs a decision on how to add the indication identifier so that the PDCP entity corresponding to the indication identifier receives the uplink transmission. E.g., the terminal can decide which AP (corresponding PDCP entity) the data packet is sent to based on channel quality measurements (e.g., RSRP).

The PDCP PDU format is designed as follows:

an example of adding an indication identifier in the PDCP header of the SRB based on the PDCP data PDU format is shown in fig. 10a and 10b, employing an N-bit identifier. Wherein fig. 10a corresponds to a scenario in which at most two DDUs are connected, and fig. 10b corresponds to a scenario in which at most 4 DDUs are connected. Since encryption and decryption and integrity protection keys are specific to each PDCP entity, one identification information may be used to indicate both encryption and decryption and integrity protection for the corresponding PDCP entity (i.e., DDU or AP).

Similarly, for the DRB PDCP data PDU, the original reserved bits of the PDCP header are used as PDCP entity (DDU/AP) indication information in the same manner. As shown in fig. 10a and 10b, pdc index-c/I corresponds to different PDCP entities.

Example 2: for ROHC

Process 2:

The PDCP PDU format is designed as follows:

for ROHC, examples of adding indication identifiers based on PDCP data PDUs of 12bit PDCP SN are shown in fig. 11a and 11b, where fig. 11a corresponds to a scenario in which at most two DDUs are connected, and fig. 11b corresponds to a scenario in which at most 4 DDUs are connected. The indication identifier may indicate a network side entity corresponding to the current data packet. Fig. 12a and 12b correspond to fig. 11a and 11b, respectively, in the format of adding indication information in the ROHC feedback PDCU control PDU. The PDCP index-ROHC corresponds to different PDCP entities.

Process 3: the different PDCP entities of the network independently execute ROHC header compression or decompression header compression; alternatively, ROHC header compression or decompression is performed by one network side PDCP entity.

Uplink transmission: after the network side different PDCP entities receive the data packet and finish decryption and integrity verification, the data packet is submitted to the same PDCP entity (such as the PDCP entity of an anchor point AP or a main AP) to execute ROHC decompression. PDCP packet ordering (reordering) is also uniformly implemented in a PDCP entity performing ROHC functions.

And (3) downlink transmission: and the UE uniformly executes ROHC header decompression after respectively finishing decryption and integrity verification on the data packets from different PDCP entities. This approach requires that the network side different PDCP entities coordinate the addition of PDCP SNs in the header compression order so that the terminal can decompress the header in the correct order after receiving it. The terminal performs PDCP packet ordering uniformly on packets from different PDCP entities.

Example 3: for EHC or UDC

The RRC configuration message may be configured to indicate the PDCP entity (DDU/AP) corresponding to the ROHC/EHC/UDC with 1 indication information, or may be configured to indicate the corresponding PDCP entity (DDU/AP) with different indication information, respectively.

Process 2:

The PDCP PDU format is designed as follows:

for the EHC and/or the UDC, the manner of adding the indication identifier in the PDCP data PDU is the same as that of the ROHC, and the ROHC/EHC/UDC may indicate the corresponding PDCP entity (DDU/AP) by using 1 indication information, or may respectively indicate the corresponding PDCP entity (DDU/AP) by using different indication information.

Examples of formats corresponding to EHC feedback or UDC feedback PDCP control PDUs are shown in fig. 13a, 13b and fig. 14a, 14b, respectively. The PDCP index-EHCs correspond to different PDCP entities.

Process 3: the network side different PDCP entities each independently perform EHC header compression or decompression and/or UDC data compression and decompression; alternatively, EHC header compression or decompression, and/or UDC data compression and decompression are performed by one network side PDCP entity.

Uplink transmission: after the network side different PDCP entities receive the data packet and complete decryption and integrity verification, the data packet is submitted to the same PDCP entity (such as the PDCP entity of the anchor AP or the main AP), and EHC header decompression and/or UDC data decompression are performed. PDCP packet ordering (reordering) is also uniformly implemented in a PDCP entity performing ROHC functions.

And (3) downlink transmission: and the UE uniformly executes EHC header decompression and/or UDC verification after respectively completing decryption and integrity verification of the data packets from different PDCP entities. This approach requires that the network side different PDCP entities coordinate the addition of PDCP SNs in the header compression order so that the terminal can decompress the header in the correct order after receiving it. The terminal performs PDCP packet ordering uniformly on packets from different PDCP entities.

The foregoing embodiments are respectively described with respect to the data transmission method of the present invention, and the following embodiments will further describe corresponding network devices with reference to the accompanying drawings.

As shown in fig. 15, an embodiment of the present invention provides a terminal, a memory 1520, a transceiver 1500, a processor 1510; wherein the memory 1520 is used for storing a computer program; a transceiver 1500 for receiving and transmitting data under the control of the processor 1510; a processor 1510 for reading the computer program in the memory and performing the following operations:

and sending the PDCP PDU to a network side entity.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

the end identifies the data packet adopting the same encryption algorithm and/or key in the same signaling radio bearer SRB or data radio bearer DRB, and adds the same indication mark in the PDCP header aiming at the data packet adopting the same encryption algorithm and key;

identifying data packets adopting the same integrity protection algorithm and/or key in the same SRB or DRB, and adding the same indication identifier in the PDCP header aiming at the data packets adopting the same integrity protection algorithm and key;

identifying data packets adopting the same robustness packet header compression algorithm and/or the context relation in the same DRB, and adding the same indication identifier in the PDCP header aiming at the data packets adopting the same robustness packet header compression algorithm and the context relation; the terminal identifies data packets adopting the same context relation in the same DRB, and adds the same indication identifier in the PDCP header aiming at the data packets adopting the same context relation;

and identifying the data packets which adopt the same compression algorithm configuration and/or the same context relation in the same DRB, and adding the same indication identifier in the PDCP header aiming at the data packets which adopt the same compression algorithm configuration and/or the same context relation.

determining a network side entity receiving the PDCP PDU;

and generating the PDCP PDU according to the PDCP processing mode corresponding to the network side entity.

respectively executing target compression processing on data of different network side entities, and respectively generating PDCP PDUs according to the data after the target compression processing;

performing target compression processing on data of a plurality of network side entities together, and respectively generating PDCP PDUs according to the data subjected to the target compression processing;

Alternatively, as shown in fig. 15, an embodiment of the present invention provides a terminal including a memory 1520, a transceiver 1500, and a processor 1510; wherein the memory 1520 is used for storing a computer program; a transceiver 1500 for receiving and transmitting data under the control of the processor 1510; a processor 1510 for reading the computer program in the memory and performing the following operations:

And executing PDCP processing on the PDCP PDU according to the indication mark.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

identifying PDCP PDUs carrying different indication marks in the same signaling radio bearer SRB or data radio bearer DRB, and executing PDCP decryption processing by adopting the same decryption algorithm and/or key aiming at the PDCP PDUs carrying the same indication marks;

identifying PDCP PDUs carrying different indication marks in the same SRB or DRB, and executing PDCP integrity verification processing by adopting the same integrity verification algorithm and/or key aiming at the PDCP PDUs carrying the same indication marks;

identifying PDCP PDUs carrying different indication marks in the same DRB, and executing PDCP robustness packet header decompression processing by adopting the same robustness packet header decompression algorithm and/or context relation aiming at the PDCP PDUs carrying the same indication marks;

identifying PDCP PDUs carrying different indication marks in the same DRB, and executing PDCP Ethernet header decompression processing by adopting the same context relation aiming at the PDCP PDUs carrying the same indication marks;

And identifying the PDCP PDUs carrying different indication marks in the same DRB, and executing PDCP user data decompression processing by adopting the same compression algorithm configuration and/or context relation aiming at the PDCP PDUs carrying the same indication marks.

according to the indication mark, PDCP processing is respectively carried out on PDCP PDUs of different network side entities;

according to the indication mark, performing target decompression processing on the data of PDCP PDUs of different network side entities;

determining a network side entity corresponding to the PDCP PDU according to an instruction in a dynamic scheduling command of an uplink resource, and executing PDCP processing on the PDCP PDU according to a PDCP processing mode corresponding to the network side entity;

Determining a network side entity corresponding to the PDCP PDU according to an indication in a pre-configuration signaling of a transmission resource, and executing PDCP processing on the PDCP PDU according to a PDCP processing mode corresponding to the network side entity;

according to a network side entity corresponding to the dynamically scheduled uplink resource, performing PDCP processing on the PDCP PDU according to a PDCP processing mode corresponding to the network side entity;

and executing the PDCP processing of the PDCP PDU according to the PDCP processing mode corresponding to the network side entity according to the network side entity corresponding to the preconfigured uplink resource.

Wherein in fig. 15, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 1510 and various circuits of memory represented by memory 1520, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 1500 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium, including wireless channels, wired channels, optical cables, etc. The user interface 1530 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc. The processor 1510 is responsible for managing the bus architecture and general processing, and the memory 1520 may store data used by the processor 1510 in performing operations.

The processor 1510 may be a Central Processing Unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device, CPLD), or it may employ a multi-core architecture.

It should be noted that, the terminal provided by the embodiment of the present invention can implement all the method steps implemented by the embodiment of the data transmission method at the terminal side, and can achieve the same technical effects, and the details of the same parts and beneficial effects as those of the embodiment of the method in the embodiment are not described in detail herein.

As shown in fig. 16, an embodiment of the present invention further provides a terminal, including:

a first generating unit 1610, configured to generate a packet data convergence protocol PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

a first sending unit 1620 configured to send the PDCP PDU to a network side entity.

A network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the first generating unit is specifically configured to:

Optionally, the first generating unit is specifically configured to perform at least one or more of the following combinations:

identifying data packets adopting the same encryption algorithm and/or key in the same signaling radio bearer SRB or data radio bearer DRB, and adding the same indication identifier in the PDCP header aiming at the data packets adopting the same encryption algorithm and key;

Optionally, the first generating unit is specifically configured to:

determining a network side entity receiving the PDCP PDU;

Optionally, the first generating unit is specifically configured to perform one of the following:

As shown in fig. 17, an embodiment of the present invention further provides a terminal, including:

a first receiving unit 1710, configured to receive a packet data convergence protocol PDCP protocol data unit PDU sent by a network side entity; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

a first processing unit 1720 configured to perform PDCP processing on the PDCP PDU according to the indication identifier.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the first processing unit is specifically configured to perform at least one or more of the following:

Optionally, the first processing unit is specifically configured to perform one of the following:

Optionally, the terminal further comprises a first determining unit, where the first determining unit is configured to perform at least one or more of the following combinations:

Optionally, the terminal further includes:

a third sending unit, configured to send a PDCP status report to the network side entity; wherein, the PDCP status report carries the indication identifier.

Optionally, the third sending unit is specifically configured to:

It should be noted that, the terminal provided by the embodiment of the present invention can implement all the method steps implemented by the embodiment of the data transmission method on the terminal side, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the embodiment of the method in the embodiment are omitted herein.

As shown in fig. 18, the present embodiment provides a network-side entity, including a memory 1820, a transceiver 1800, and a processor 1810; wherein the memory 1820 is used for storing a computer program; a transceiver 1800 for receiving and transmitting data under the control of the processor 1810; a processor 1810 for reading the computer program in the memory and performing the following operations:

the network side entity sends the PDCP PDU to a terminal.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

performing target compression processing on the data of the first network side entity, and generating PDCP PDU according to the data after the target compression processing;

receiving target compression processed data sent by a second network side entity, and generating PDCP PDU according to the target compression processed data;

Alternatively, as shown in fig. 18, the present embodiment provides a network-side entity, including a memory 1820, a transceiver 1800, and a processor 1810; wherein the memory 1820 is used for storing a computer program; a transceiver 1800 for receiving and transmitting data under the control of the processor 1810; a processor 1810 for reading the computer program in the memory and performing the following operations:

And performing PDCP processing on the PDCP PDU.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

receiving the PDCP PDU at the uplink resource corresponding to the network side entity according to the indication in the dynamic scheduling command of the uplink resource;

receiving the PDCP PDU at the uplink resource corresponding to the network side entity according to the indication in the pre-configuration signaling of the uplink resource;

receiving the PDCP PDU at a dynamically scheduled uplink resource;

and receiving the PDCP PDU at the preconfigured uplink resource.

Wherein in fig. 18, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 1810 and various circuits of memory represented by memory 1820, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1800 may be a number of elements, i.e., include a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1810 is responsible for managing the bus architecture and general processing, with the memory 1820 storing data used by the processor 1810 in performing operations.

The processor 1810 may be a Central Processing Unit (CPU), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA), or complex programmable logic device (Complex Programmable Logic Device, CPLD), or it may employ a multi-core architecture.

It should be noted that, the network side entity provided in this embodiment of the present invention can implement all the method steps implemented in the method embodiment applied to the network side entity, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.

As shown in fig. 19, the embodiment of the present application further provides a network side entity, including:

a second generating unit 1910 configured to generate a PDCP protocol data unit PDU; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

a second transmitting unit 1920 configured to transmit the PDCP PDU to the terminal.

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the second generating unit 1910 is specifically configured to:

Optionally, the second generating unit 1910 is specifically configured to combine at least one or more of the following, or a PDCP processing manner for generating the PDCP PDU includes at least one or more of the following:

Optionally, the network-side entity is a first network-side entity, and the second generating unit 1910 is specifically configured to:

As shown in fig. 20, an embodiment of the present invention provides a network side entity, including:

a second receiving unit 2010, configured to receive a packet data convergence protocol PDCP protocol data unit PDU sent by a terminal; the PDCP header of the PDCP PDU carries an indication identifier for indicating a network side entity corresponding to the PDCP PDU;

a second processing unit 2020, configured to perform PDCP processing on the PDCP PDU.

a network side PDCP entity;

A distributed data unit, DDU, entity;

an access point, AP, entity.

Optionally, the second processing unit 2020 is specifically configured to at least one or more of the following in combination:

performing PDCP processing on the PDCP PDU corresponding to the second network side entity according to the indication identifier;

receiving data after decryption processing and integrity verification processing sent by a first network side entity, and jointly executing target decompression processing on the data after decryption processing and integrity verification processing of different first network side entities;

Optionally, in the case that the PDCP PDU does not carry the indication identifier, the second receiving unit 2010 is specifically configured to at least one or a combination of the following:

receiving the PDCP PDU at a dynamically scheduled uplink resource;

and receiving the PDCP PDU at the preconfigured uplink resource.

Optionally, the network side entity further includes:

a fourth transmitting unit, configured to transmit a PDCP status report to the terminal; wherein, the PDCP status report carries the indication identifier.

Optionally, any network side entity connected with the terminal sends the PDCP status report to the terminal.

The embodiment of the invention also provides a processor readable storage medium, which stores a computer program, wherein the computer program is used for enabling the processor to execute the steps of the data transmission method of the terminal side or the network side entity, and the same technical effects can be achieved, so that repetition is avoided, and the description is omitted here.

The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), and the like.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Furthermore, it should be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. Also, the steps of performing the series of processes described above may naturally be performed in chronological order in the order of description, but are not necessarily performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those of ordinary skill in the art that all or any of the steps or components of the methods and apparatus of the present invention may be implemented in hardware, firmware, software, or a combination thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art after reading this description of the invention.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A data transmission method, comprising:

the terminal sends the PDCP PDU to a network side entity.

2. The data transmission method according to claim 1, wherein the terminal is associated with one or more network side entities, the network side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

3. The data transmission method according to claim 1, wherein the terminal generates a packet data convergence protocol PDCP protocol data unit PDU, comprising:

4. A data transmission method according to any one of claims 1 to 3, wherein the terminal generates packet data convergence protocol, PDCP, protocol data units, PDUs, or PDCP processing means for generating said PDCP PDUs comprises at least one or a combination of:

5. A data transmission method according to claim 3, characterized in that the preset information is predefined by a protocol or configured by a network side.

6. A data transmission method according to any one of claims 1 to 3, wherein the terminal generates a packet data convergence protocol, PDCP, protocol data unit, PDU, comprising:

the terminal determines a network side entity which receives the PDCP PDU;

7. A data transmission method according to any one of claims 1 to 3, wherein the terminal generates packet data convergence protocol, PDCP, protocol data units, PDUs, comprising one of:

8. The data transmission method according to claim 1, wherein the PDCP PDU does not carry the indication identifier in case that different network side entities correspond to different transmission resources.

9. The data transmission method according to claim 8, wherein the case that the different network side entities correspond to different transmission resources includes at least one or a combination of more of the following:

10. The data transmission method according to claim 1, wherein the indication is identified as reserved N bits of the PDCP header or as N bits of the PDCP header other than reserved bits;

11. A data transmission method, comprising:

12. The data transmission method according to claim 11, wherein the terminal is associated with one or more network side entities, the network side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

13. The data transmission method according to claim 11, wherein the terminal performs PDCP processing on the PDCP PDU according to the indication identifier, including at least one or a combination of:

the terminal identifies PDCP PDUs carrying different indication marks in the same signaling radio bearer SRB or data radio bearer DRB, and adopts the same decryption algorithm and/or key to execute decryption processing aiming at the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same SRB or DRB, and executes integrity verification processing by adopting the same integrity verification algorithm and/or key aiming at the PDCP PDUs carrying the same indication mark;

The terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs robust packet header decompression processing by adopting the same robust packet header decompression algorithm and/or context relation for the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and performs Ethernet header decompression processing by adopting the same context relation aiming at the PDCP PDUs carrying the same indication marks;

the terminal identifies PDCP PDUs carrying different indication marks in the same DRB, and executes user data decompression processing by adopting the same user data compression algorithm configuration and/or context relation aiming at the PDCP PDUs carrying the same indication marks.

14. The data transmission method according to any one of claims 11 to 13, wherein the terminal performs PDCP processing on the PDCP PDU according to the indication identity, comprising one of:

15. The data transmission method according to claim 11, wherein, in the case that the PDCP PDU does not carry the indication identifier, the terminal further comprises at least one or more of the following combinations after receiving a packet data convergence protocol PDCP protocol data unit PDU sent by a network side entity:

16. The data transmission method according to claim 11, wherein the indication is identified as reserved N bits of the PDCP header or as N bits of the PDCP header other than reserved bits;

17. The data transmission method according to claim 11, further comprising:

18. The data transmission method according to claim 17, wherein the terminal sends a PDCP status report to the network side entity, comprising:

19. A data transmission method, comprising:

The network side entity sends the PDCP PDU to a terminal.

20. The data transmission method according to claim 19, wherein the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, comprising:

21. The data transmission method according to claim 19 or 20, wherein the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, or generates PDCP processing of the PDCP PDU, comprises at least one or a combination of:

22. The data transmission method according to claim 19 or 20, wherein the network side entity is a first network side entity, and wherein the network side entity generates a packet data convergence protocol PDCP protocol data unit PDU, comprising one of:

23. The data transmission method according to claim 19, wherein the PDCP PDU does not carry the indication identifier in case that different network side entities correspond to different transmission resources.

24. A data transmission method, comprising:

the network side entity performs PDCP processing on the PDCP PDU.

25. The data transmission method according to claim 24, wherein the network side entity is a second network side entity, and wherein the network side entity performs PDCP processing on the PDCP PDU, including at least one or a combination of:

26. The data transmission method according to claim 24, further comprising:

27. A terminal comprising a memory, a transceiver, and a processor;

and sending the PDCP PDU to a network side entity.

28. The terminal of claim 27, wherein the terminal is associated with one or more network side entities, the network side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

29. The terminal of claim 27, wherein the processor is configured to read the computer program in the memory and perform the following:

30. The terminal according to any of the claims 27 to 29, wherein the processor is configured to read the computer program in the memory and perform at least one or more of the following:

31. The terminal according to any of the claims 27 to 29, wherein the processor is adapted to read a computer program in the memory and to perform one of the following operations:

32. The terminal of claim 27, wherein the indication identifier is not carried in the PDCP PDU in case that different network side entities correspond to different transmission resources.

33. A terminal comprising a memory, a transceiver, and a processor;

34. The terminal of claim 33, wherein the terminal is associated with one or more network-side entities, the network-side entities being one or more of:

a network side PDCP entity;

a distributed data unit, DDU, entity;

an access point, AP, entity.

35. The terminal of claim 33, wherein the processor is configured to read the computer program in the memory and perform at least one or more of the following:

36. The terminal according to any of the claims 33 to 35, wherein the processor is configured to read a computer program in the memory and to perform one of the following operations:

37. The terminal of claim 33, wherein the processor is further configured to read the computer program in the memory and perform at least one or more of the following operations if the indication identifier is not carried in the PDCP PDU:

38. A network side entity, which is characterized by comprising a memory, a transceiver and a processor;

the network side entity sends the PDCP PDU to a terminal.

39. The network-side entity of claim 38, wherein the processor is configured to read the computer program in the memory and perform the following operations:

40. The network side entity of claim 38 or 39, wherein the network side entity is a first network side entity, and wherein the processor is configured to read the computer program in the memory and perform one of:

41. The network side entity of claim 40 wherein the indication identifier is not carried in the PDCP PDU in case of different network side entities corresponding to different transmission resources.

42. A network side entity, which is characterized by comprising a memory, a transceiver and a processor;

And performing PDCP processing on the PDCP PDU.

43. The network side entity of claim 42, wherein the network side entity is a second network side entity, and wherein the processor is configured to read the computer program in the memory and perform one or more of:

44. A terminal, comprising:

45. A terminal, comprising:

46. A network side entity, comprising:

and the second sending unit is used for sending the PDCP PDU to the terminal.

47. A network side entity, comprising:

48. A processor readable storage medium having stored thereon a computer program, characterized in that the computer program when executed by a processor realizes the steps of the data transmission method according to any of claims 1 to 10, or the steps of the data transmission method according to any of claims 11 to 18, or the steps of the data transmission method according to any of claims 19 to 23, or the steps of the data transmission method according to any of claims 24 to 26.