CN111356178B - Transmission method, transmitting side PDCP entity and receiving side PDCP entity - Google Patents

Transmission method, transmitting side PDCP entity and receiving side PDCP entity Download PDF

Info

Publication number
CN111356178B
CN111356178B CN201811583625.XA CN201811583625A CN111356178B CN 111356178 B CN111356178 B CN 111356178B CN 201811583625 A CN201811583625 A CN 201811583625A CN 111356178 B CN111356178 B CN 111356178B
Authority
CN
China
Prior art keywords
pdu
pdcp
sdap
marker control
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811583625.XA
Other languages
Chinese (zh)
Other versions
CN111356178A (en
Inventor
孙军帅
王莹莹
黄学艳
韩星宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN201811583625.XA priority Critical patent/CN111356178B/en
Publication of CN111356178A publication Critical patent/CN111356178A/en
Application granted granted Critical
Publication of CN111356178B publication Critical patent/CN111356178B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity

Landscapes

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

Abstract

The invention provides a transmission method, a sending end PDCP entity and a receiving end PDCP entity, wherein the method corresponding to the sending end PDCP entity comprises the following steps: and sending a target PDCP PDU carrying the SDAP End-Marker Control PDU. In the invention, the SDAP End-Marker Control PDU is carried in the PDCP PDU, so that the SDAP End-Marker Control PDU can be transmitted along with the PDCP PDU. The transmission method is simple to implement, and the system overhead required by transmission is low.

Description

Transmission method, sending end PDCP entity and receiving end PDCP entity
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a transmission method, a sending side PDCP entity, and a receiving side PDCP entity.
Background
A Control PDU (Protocol Data Unit), namely, an SDAP End-Marker Control PDU (Service Data Adaptation Protocol End Marker Control Protocol Data Unit), is introduced into an SDAP (Service Data Adaptation Protocol). The End-Marker Control PDU may be used in a UE (User Equipment) side SDAP entity, and is used to instruct to stop mapping of an SDAP SDU (Service Data Unit) of a QoS (Quality of Service) flow.
However, the format of the SDAP End-Marker Control PDU is different from that of a normal SDAP data PDU, so that the SDAP End-Marker Control PDU cannot be processed in a manner of processing other data of the SDAP at the PDCP entity.
Disclosure of Invention
The invention aims to provide a transmission method, a sending End PDCP entity and a receiving End PDCP entity, so as to solve the problem that an SDAP End-Marker Control PDU can not be processed normally in the PDCP entity.
In order to achieve the above object, in a first aspect, the present invention provides a transmission method for a packet data convergence protocol PDCP entity at a sending end, where the method includes:
and sending a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU.
In a second aspect, the present invention provides a transmission method for receiving a packet data convergence protocol PDCP entity, the method including:
and receiving a target PDCP protocol data unit PDU carrying a SDAPEnd-Marker Control protocol data unit SDAPEnd-Marker Control PDU.
In a third aspect, the present invention provides a sending-end packet data convergence protocol PDCP entity, including a transceiver, where the transceiver is configured to:
and sending a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU.
In a fourth aspect, the present invention provides a receiving-end packet data convergence protocol PDCP entity, comprising a transceiver configured to:
and receiving a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU.
In a fifth aspect, the present invention provides a sending-end packet data convergence protocol PDCP entity, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor; wherein the processor implements the transmission method of the first aspect when executing the program.
In a sixth aspect, the present invention provides a receiving-end packet data convergence protocol PDCP entity, comprising a memory, a processor and a computer program stored in the memory and executable on the processor; wherein the processor implements the transmission method of the second aspect when executing the program.
In a seventh aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, where the program, when executed by a processor, implements steps in a transmission method corresponding to a packet data convergence protocol PDCP entity at a sending end.
In an eighth aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements steps in a transmission method corresponding to a receiving-end packet data convergence protocol PDCP entity.
The technical scheme of the invention at least has the following beneficial effects:
by carrying the SDAP End-Marker Control PDU in the PDCP PDU, the SDAP End-Marker Control PDU can be transmitted along with the PDCP PDU. The transmission method is simple to implement, and the system overhead required by transmission is low.
Drawings
FIG. 1 shows a format of a PDCP Control PDU according to an embodiment of the present invention;
FIG. 2 shows another PDCP Control PDU format according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a transmission method according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a manner of processing an SDAP End-Marker Control PDU according to an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating another manner of processing an SDAP End-Marker Control PDU according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating another example of processing an SDAP End-Marker Control PDU according to an embodiment of the present invention;
FIG. 7 is a diagram illustrating another example of processing an SDAP End-Marker Control PDU according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a PDCP SUD carrying an SDAP End-Marker Control PDU according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of a PDCP SUD carrying more than one SDAP End-Marker Control PDU according to an embodiment of the present invention;
FIG. 10 is a diagram illustrating an SDAP End-Marker Control PDU is carried in a target PDCP PDU according to an embodiment of the present invention;
fig. 11 is a flowchart illustrating another transmission method according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a transmitting end PDCP entity according to an embodiment of the present invention;
fig. 13 is a schematic diagram illustrating a structure of another sending-end PDCP entity according to an embodiment of the present invention;
fig. 14 is a schematic structural diagram of a receiving end PDCP entity according to an embodiment of the present invention;
fig. 15 is a schematic diagram illustrating a structure of another sending-end PDCP entity according to an embodiment of the present invention;
fig. 16 is a schematic structural diagram of another receiving-end PDCP entity according to an embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
The chinese and english references of the communication terms referred to in this application are as follows:
and (4) SDAP: service Data Adaptation Protocol;
PDCP: packet Data Convergence Protocol;
SDU: service Data Unit, service Data Unit;
PDU: protocol Data Unit, protocol Data Unit;
SDAP End-Marker Control PDU: the service data adaptation protocol end mark controls the protocol data unit;
QoS: quality of Service;
the UE: user Equipment, user Equipment;
AM: acknowledged Mode, acknowledged Mode;
UM: unacknowledded Mode, unacknowledged Mode;
ROHC: RObust Header Compression;
DRB: data Radio Bearer, data Radio Bearer;
RB: radio Bearer, radio Bearer;
SN: sequence number, sequence number;
MAC-I: message Authentication Code for Integrity, integrity protection Message Authentication Code.
In 37.234SDAP protocol, a Control SDAP End-Marker Control PDU is introduced, where the Control SDAP End-Marker Control PDU may be used in a UE-side SDAP entity to indicate an SDAP SDU Mapping (Reflective Mapping) for stopping QoS flows.
The 38.323 protocol specifies the format of the SDAP End-Marker Control PDU, for example, FIG. 1 shows the format of a PDCP Control PDU carrying a PDCP status report, which is applicable to AM DRBs; also for example, fig. 2 shows the format of PDCP Control PDU carrying one ROHC feedback, which is applicable to UM DRBs and AM DRBs.
In the above format specified in the 38.323 protocol, the SDAP End-Marker Control PDU has no IP header, and thus it cannot be processed to form a PDCP PDU as an SDAP data PDU.
In view of this, an embodiment of the present invention provides a transmission method to solve the above problem and implement transmission of an SDAP End-Marker Control PDU.
Referring to fig. 3, fig. 3 is a schematic flow chart of a transmission method according to an embodiment of the present invention. As shown in fig. 3, a transmission method for a transmitting side PDCP entity includes the following steps:
step 301: and sending a target PDCP PDU carrying the SDAP End-Marker Control PDU.
The embodiment of the invention needs to carry SDAP End-Marker Control PDU in PDCP PDU, which can be received from an upper layer, unprocessed SDAP End-Marker Control PDU, or SDAP End-Marker Control PDU processed by header compression processing and/or integrity protection processing and/or encryption processing.
In the step, the target PDCP PDU carrying the SDAP End-Marker Control PDU is sent, so that the transmission of the SDAP End-Marker Control PDU is realized.
In the embodiment of the invention, the SDAP End-Marker Control PDU is carried in the PDCP PDU, so that the SDAP End-Marker Control PDU can be transmitted along with the PDCP PDU. The transmission method is simple to implement, and the system overhead required by transmission is low.
In the specific embodiment of the present invention, the SDAP End-Marker Control PDU in the finally generated PDCP PDU may be data obtained through operations such as header compression processing and/or integrity protection processing and/or encryption processing, or may be an original SDAP End-Marker Control PDU without any processing, which is respectively described below.
After the SDAP entity sends the SDAP End-Marker Control PDU to the sending End PDCP entity, the sending End PDCP entity may not perform any processing on the SDAP End-Marker Control PDU, or the SDAP End-Marker Control PDU may be directly added to other types of PDCP SDUs without performing SN (Sequence number) adding, header compression, integrity protection, and ciphering operations of the sending End PDCP entity. Here, the other type of PDCP SDU may be a PDCP SDU subjected to header compression processing, integrity protection processing, and ciphering processing. The method is equivalent to that a PDCP SDU for bearing an SDAP End-Marker Control PDU is added in PDCP PDUs corresponding to other types of PDCP SDUs.
For the case of performing operations such as header compression processing and/or integrity protection processing and/or encryption processing on the SDAP End-Marker Control PDU, the header compression processing and/or integrity protection processing and/or encryption processing on the SDAP End-Marker Control PDU can be performed in two ways, which are described below.
The method I comprises the following steps: header compression processing and/or integrity protection processing and/or ciphering processing for the SDAP End-Marker Control PDU are independent of the PDCP SDUs.
As shown in fig. 4, the SDAP End-Marker Control PDU is separately subjected to header compression processing and/or integrity protection processing and/or ciphering processing, and the processed SDAP End-Marker Control PDU is added to the PDCP SDU which is subjected to the header compression processing, integrity protection processing and ciphering processing, so as to obtain a target PDCP PDU.
Specifically, after performing header compression processing and/or integrity protection processing and/or ciphering processing on the SDAP End-Marker Control PDU alone, the sending End PDCP entity adds the SDAP End-Marker Control PDU to the PDCP SDU which has completed header compression processing, integrity protection processing and ciphering processing, and finally adds a PDCP header by the PDCP entity to obtain the final PDCP PDU. Further, the sending End PDCP entity may add SN (Sequence number), header compression, integrity protection, and ciphering to the SDAP End-Marker Control PDU and then add the resulting PDU to the PDCP SDU.
Here, the single header compression processing and/or integrity protection processing and/or ciphering processing performed on the SDAP End-Marker Control PDU as the PDCP SDU may include the following cases: taking the SDAP End-Marker Control PDU as a PDCP SDU to carry out header compression treatment independently; or, taking the SDAP End-Marker Control PDU as the PDCP SDU to carry out integrity protection processing independently; or, the SDAP End-Marker Control PDU is used as PDCP SDU for encryption processing; or, the SDAP End-Marker Control PDU is used as a PDCP SDU to carry out header compression processing and integrity protection processing independently; or, taking the SDAP End-Marker Control PDU as the PDCP SDU to carry out integrity protection processing and encryption processing independently; or, the SDAP End-Marker Control PDU is used as a PDCP SDU to carry out header compression processing and encryption processing independently; or, the SDAP End-Marker Control PDU is used as the PDCP SDU to carry out header compression processing, integrity protection processing and encryption processing independently.
After the SDAP End-Marker Control PDU is used as a PDCP SDU to be subjected to header compression processing and/or integrity protection processing and/or encryption processing independently, the sending End PDCP entity can put the SDAP End-Marker Control PDU into a PDCP PDU corresponding to a PDCP SDU data packet for sending.
The second method comprises the following steps: and adding the SDAP End-Marker Control PDU to the PDCP SDU, and performing header compression processing and/or integrity protection processing and/or encryption processing together with the PDCP SDU.
Specifically, as shown in fig. 5, the SDAP End-Marker Control PDU is added to the PDCP SDU to generate a first PDCP SDU, and the first PDCP SDU is subjected to header compression, integrity protection, and encryption to obtain a target PDCP PDU. Or, the SDAP End-Marker Control PDU is used as a PDCP SDU, and is directly added into a PDCP SDU data packet which is not subjected to header compression processing, integrity protection processing and encryption processing, and then header compression processing, integrity protection processing and encryption processing are carried out together. Here, header compression processing may be performed using the data IP format of this packet, and integrity protection processing and ciphering processing may be performed using the PDCP SN of this packet.
As shown in fig. 6, the SDAP End-Marker Control PDU is added to the PDCP SDU subjected to the header compression processing to generate a second PDCP SDU, and the integrity protection processing and the ciphering processing are performed on the second PDCP SDU to obtain a target PDCP PDU. Or, the SDAP End-Marker Control PDU is used as a PDCP SDU, and is directly added into a PDCP SDU data packet only subjected to header compression processing, and then integrity protection processing and encryption processing are carried out together. Here, the PDCP SN of this packet may be used for integrity protection processing and ciphering processing.
As shown in fig. 7, the SDAP End-Marker Control PDU is added to the PDCP SDU that has undergone header compression and integrity protection processing, so as to generate a third PDCP SDU, and the third PDCP SDU is encrypted to obtain a target PDCP PDU. Or, the SDAP End-Marker Control PDU is used as a PDCP SDU, and is directly added into a PDCP SDU data packet which is only subjected to header compression processing and integrity protection processing, and then encryption processing is carried out together. Here, the PDCP SN of this packet may be used for ciphering.
In the embodiment of the present invention, the SDAP End-Marker Control PDU may be transmitted in units of UE or RB. Thus, the RB carrying the target PDCP PDU may be any one of the following RBs:
the RB of the UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS flow of the SDAP End-Marker Control PDU.
When transmitting in units of UEs, the SDAP End-Marker Control PDU may be sent on any one RB of the UE to which it belongs, or on multiple RBs simultaneously or in a time-sharing manner. Any RB of the UE can carry the SDAP End-Marker Control PDU for transmission as long as there is a transmission opportunity. After the QoS flow completes the transmission Mapping (Reflective Mapping), the SDAP End-Marker Control PDU may be sent on the source DRB, the target DRB, or both RBs simultaneously.
When transmitting in units of RBs, the SDAP End-Marker Control PDU may be sent one or more times on the RBs to which the QoS stream belongs.
In the embodiment of the invention, an indication field can be added into a target PDCP PDU carrying the SDAP End-Marker Control PDU.
The method comprises the steps of adding a first indication field for indicating whether the target PDCP PDU carries the SDAP End-Marker Control PDU or not in the target PDCP PDU carrying the SDAP End-Marker Control PDU.
For example, an SDAP End-Marker Control PDU Indicator, abbreviated as EMCI (i.e., a first indication field), may be defined, and the EMCI indicates whether the target PDCP PDU carries the SDAP End-Marker Control PDU.
The EMCI occupies at least 1 bit in length, and any one of PDCP PDU headers (PDCP PDU headers) or bits of consecutive several "R" fields ("R" fields) may be defined as EMCI. If the EMCI length is fixed to 1 bit, 1 bit of one "R" field may be selected. The EMCI can have two values which respectively represent that the SDAP End-Marker Control PDU is carried and the SDAP End-Marker Control PDU is not carried, the 'carrying' can be marked by using a digital 1, and the 'not carrying' can be marked by using a digital 0.
And a second indication field for indicating the number or the length of the SDAP End-Marker Control PDU carried in the target PDCP PDU can be added into the target PDCP PDU carrying the SDAP End-Marker Control PDU.
For example, an SDAP End-Marker Control PDU Number, which is abbreviated as EMCN (i.e. the second indication field), may be defined, and the Number of the SDAP End-Marker Control PDUs carried in the target PDCP PDU is indicated by the EMCN.
The EMCN occupies at least 1 bit in length, and any one of the PDCP PDU headers or bits of consecutive several "R" fields can be defined as the EMCN. If the EMCN length is fixed to 1 bit, 1 bit of one 'R' field is selected. The EMCN may have two values, which respectively indicate that the number of PDUs carrying the SDAP End-Marker Control is 1 and the number of PDUs carrying the SDAP End-Marker Control is more than 1, and may use the number 1 to identify "the number is more than 1" and the number 0 to identify "the number is 1".
For the case that the number of PDUs carrying the SDAP End-Marker Control PDU is n (n is a positive integer), the SDAP End-Marker Control PDU exists in the PDCP PDU in units of n bytes.
When the number of the SDAP End-Marker Control PDU is 1, the SDAP End-Marker Control PDU exists in a PDCP PDU in a unit with the length of 1 byte.
FIG. 8 is a diagram illustrating PDCP SDUs when the number of PDUs carrying SDAP End-Marker Control is 1.
When the number of the SDAP End-Marker Control PDUs is more than 1, the PDCP PDUs are added with the number indication or the length indication of the SDAP End-Marker Control PDUs besides the SDAP End-Marker Control PDUs. If it is "Length indication", its unit is bytes, then it is the byte length of the sum of the lengths of all SDAP End-Marker Control PDUs. Since the length of one SDAP End-Marker Control PDU is 1 byte, the number of SDAP End-Marker Control PDUs can be obtained according to the number of bytes of the total length. If it is "number indication", the total byte length can be found based on the length of each SDAP End-Marker Control PDU being 1 byte. FIG. 9 is a diagram illustrating a PDCP SDU when the number of PDUs carrying SDAP End-Marker Control is more than 1.
In the embodiment of the invention, the target PDCP PDU can be a PDCP data PDU and also can be a PDCP control PDU. The location of the SDAP End-Marker Control PDU in the target PDCP PDU can also vary among different types of PDUs.
When the SDAP End-Marker Control PDU is carried in the PDCP data PDU, the SDAP End-Marker Control PDU can be positioned between the head of the PDCP PDU and the PDCP SDU, for example, immediately after the head of the PDCP PDU; or,
the SDAP End-Marker Control PDU can also be located between the PDCP SDU and MAC-I, e.g., immediately following the PDCP SDU; or,
the SDAP End-Marker Control PDU can also be located after the MAC-I, or at the End of the entire PDCP PDU, e.g., immediately after the MAC-I.
When the SDAP End-Marker Control PDU is carried in the PDCP Control PDU, the SDAP End-Marker Control PDU can be located between the header of the PDCP PDU and the Control content, e.g., immediately after the header of the PDCP PDU; or,
the SDAP End-Marker Control PDU may be located after the Control content.
In the embodiment of the invention, the PDCP entity at the sending End can determine the values of EMCI and EMCN according to the number of SDAP End-Marker Control PDUs needing to be sent, and carries the corresponding SDAP End-Marker Control PDUs by combining PDCP data SDUs or PDCP Control SDUs needing to be sent.
Fig. 10 shows an example of carrying the SDAP End-Marker Control PDU in the target PDCP PDU, where in fig. 10, two "R" fields in the PDCP SDU are defined as EMCI and EMCN, respectively, and the SDAP End-Marker Control PDU is put at the End of Data (Data).
In summary, the embodiment of the present invention enables the SDAP End-Marker Control PDU to be transmitted along with the PDCP PDU by carrying the SDAP End-Marker Control PDU in the PDCP PDU. The transmission method is simple to implement, and the system overhead required by transmission is low.
Referring to fig. 11, fig. 11 is a flowchart illustrating a transmission method according to an embodiment of the present invention. As shown in fig. 11, a transmission method for a receiving side PDCP entity includes the following steps:
step 401: and receiving a target PDCP PDU carrying the SDAP End-Marker Control PDU.
When receiving the PDCP PDU, the receiving side PDCP entity may remove the PDCP PDU header, and determine whether the PDCP PDU carries an SDAP End-Marker Control PDU.
If the PDCP PDU carries the SDAP End-Marker Control PDU, the PDCP entity at the receiving End can judge whether the SDAP End-Marker Control PDU is contained in encryption/integrity protection, and if the SDAP End-Marker Control PDU is contained in the encryption/integrity protection, the PDCP PDU is sent to an SDAP protocol sublayer after decryption/integrity protection is finished; otherwise, directly sending to SDAP protocol sub-layer.
The receiving End PDCP entity may determine whether the SDAP End-Marker Control PDU is included in the ciphering/integrity protection according to the protocol specification, or may determine whether the SDAP End-Marker Control PDU is included in the ciphering/integrity protection according to the instruction of the sending End PDCP entity.
The receiving End PDCP entity can judge whether the SDAP End-Marker Control PDU exists according to the EMCI field in the PDCP PDU head, and if so, can judge the number of the SDAP End-Marker Control PDU carried by the PDCP PDU according to the EMCN field in the PDCP PDU head; then, obtaining SDAP End-Marker Control PDU and uploading to SDAP protocol sub-layer.
Optionally, the SDAP End-Marker Control PDU is an SDAP End-Marker Control PDU that is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
Optionally, the RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the UE to which the SDAP End-Marker Control PDU belongs;
the RB for the QoS flow of the SDAP End-Marker Control PDU is generated.
Optionally, the PDCP PDU further includes: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: and the second indication field is used for indicating the number or the length of the SDAP End-Marker Control PDU carried in the PDCP PDU.
Optionally, the first indication field and/or the second indication field is located in the header of the target PDCP PDU.
Optionally, when the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is located between the PDCP PDU header and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
The embodiment of the present invention can be implemented with reference to the embodiments shown in fig. 3 to 10, and has the same beneficial effects, and is not described in detail for avoiding repetition.
Referring to fig. 12, an embodiment of the present invention provides a transmitting side PDCP entity, as shown in fig. 12, the transmitting side PDCP entity 500 includes a transceiver 501, where the transceiver 501 is configured to:
and sending a target PDCP PDU of the SDAP End-Marker Control PDU.
Optionally, the SDAP End-Marker Control PDU is an SDAP End-Marker Control PDU that is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
Optionally, as shown in fig. 13, the sending-end PDCP entity 500 further includes a processor 502, and the processor 502 is configured to:
taking the SDAP End-Marker Control PDU received from the SDAP entity as a PDCP SDU to carry out header compression processing and/or integrity protection processing and/or encryption processing, and adding the processed SDAP End-Marker Control PDU into the PDCP SDU which is subjected to header compression processing, integrity protection processing and encryption processing to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into a PDCP SDU to generate a first PDCP SDU, and performing header compression processing, integrity protection processing and encryption processing on the first PDCP SDU to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to the header compression processing to generate a second PDCP SDU, and carrying out integrity protection processing and encryption processing on the second PDCP SDU to obtain a target PDCP PDU;
or,
and adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to header compression and integrity protection processing to generate a third PDCP SDU, and encrypting the third PDCP SDU to obtain the target PDCP PDU.
Optionally, the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
Optionally, the first indication field and/or the second indication field are located in the header of the target PDCP PDU.
Optionally, when the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is located between the PDCP PDU header and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
It should be noted that, in the embodiment of the present invention, the sending-end PDCP entity 500 may be the sending-end PDCP entity in any implementation manner in the embodiment of the present invention shown in fig. 3 to 10, and any implementation manner in the embodiment of the present invention shown in fig. 3 to 10 may be implemented by the sending-end PDCP entity 500 in this embodiment to achieve the same beneficial effects, which is not described herein again.
Referring to fig. 14, an embodiment of the present invention provides a receiving-end PDCP entity, as shown in fig. 14, the receiving-end PDCP entity 600 includes a transceiver 601, where the transceiver 601 is configured to:
and receiving a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU.
Optionally, the SDAP End-Marker Control PDU is an SDAP End-Marker Control PDU that is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
Optionally, the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
Optionally, the first indication field and/or the second indication field are located in the header of the target PDCP PDU.
Optionally, when the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is located between the PDCP PDU header and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
It should be noted that, in the embodiment of the present invention, the receiving-end PDCP entity 600 may be the receiving-end PDCP entity in any implementation manner in the embodiment of the present invention shown in fig. 11, and any implementation manner in the embodiment of the present invention shown in fig. 11 may be implemented by the receiving-end PDCP entity 600 in this embodiment, so as to achieve the same beneficial effects, and details are not repeated here.
Referring to fig. 15, another sending-end PDCP entity according to the embodiment of the present invention, as shown in fig. 15, the sending-end PDCP entity 700 includes a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702; the computer program when executed by the processor 702 performs the steps of:
and sending a target PDCP PDU of the SDAP End-Marker Control PDU.
In FIG. 15, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 702, and various circuits of memory, represented by memory 701, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 702 is responsible for managing the bus architecture and general processing, and the memory 701 may store data used by the processor 702 in performing operations.
Optionally, the SDAP End-Marker Control PDU is an SDAP End-Marker Control PDU that is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
Optionally, when the processor 702 executes the program, the following is further implemented:
taking the SDAP End-Marker Control PDU received from the SDAP entity as a PDCP SDU to carry out header compression processing and/or integrity protection processing and/or encryption processing, and adding the processed SDAP End-Marker Control PDU into the PDCP SDU which is subjected to header compression processing, integrity protection processing and encryption processing to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into a PDCP SDU to generate a first PDCP SDU, and performing header compression processing, integrity protection processing and encryption processing on the first PDCP SDU to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to the header compression processing to generate a second PDCP SDU, and carrying out integrity protection processing and encryption processing on the second PDCP SDU to obtain a target PDCP PDU;
or,
and adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDUs subjected to header compression and integrity protection processing to generate a third PDCP SDU, and encrypting the third PDCP SDU to obtain the target PDCP PDU.
Optionally, the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
Optionally, the first indication field and/or the second indication field are located in the header of the target PDCP PDU.
Optionally, when the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is located between the PDCP PDU header and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
It should be noted that, in the embodiment of the present invention, the sending-end PDCP entity 500 may be the sending-end PDCP entity in any implementation manner in the embodiment of the present invention shown in fig. 3 to 10, and any implementation manner in the embodiment of the present invention shown in fig. 3 to 10 may be implemented by the sending-end PDCP entity 500 in this embodiment to achieve the same beneficial effects, which is not described herein again.
Referring to fig. 16, an embodiment of the present invention provides another receiving-side PDCP entity, as shown in fig. 16, the receiving-side PDCP entity 800 includes a memory 801, a processor 802, and a computer program stored in the memory 801 and capable of running on the processor 802; the computer program when executed by the processor 802 implements the steps of:
and receiving a target PDCP PDU of the SDAP End-Marker Control PDU.
In FIG. 16, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 802 and various circuits represented by memory 801 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 802 is responsible for managing the bus architecture and general processing, and the memory 801 may store data used by the processor 802 in performing operations.
Optionally, the SDAP End-Marker Control PDU is an SDAP End-Marker Control PDU that is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
Optionally, the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating an RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
Optionally, the target PDCP PDU further includes: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
Optionally, the first indication field and/or the second indication field are located at the header of the target PDCP PDU.
Optionally, when the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is located between the PDCP PDU header and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
It should be noted that, in the embodiment of the present invention, the receiving-end PDCP entity 800 may be a receiving-end PDCP entity in any implementation manner in the embodiment of the present invention shown in fig. 11, and any implementation manner in the embodiment of the present invention shown in fig. 11 may be implemented by the receiving-end PDCP entity 800 in this embodiment, so as to achieve the same beneficial effects, and details are not repeated here.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the processes of the transmission method embodiment, and can achieve the same technical effects, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims (29)

1. A transmission method for a Packet Data Convergence Protocol (PDCP) entity at a sending end, the method comprising:
sending a target PDCP protocol data unit PDU which carries a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU;
the SDAP End-Marker Control PDU is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
2. The transmission method according to claim 1, wherein before the sending the target PDCP PDU carrying the SDAP End-Marker Control PDU, the transmission method further comprises:
taking the SDAP End-Marker Control PDU received from the SDAP entity as a PDCP SDU to carry out header compression processing and/or integrity protection processing and/or encryption processing, and adding the processed SDAP End-Marker Control PDU into the PDCP SDU which is subjected to header compression processing, integrity protection processing and encryption processing to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into a PDCP SDU to generate a first PDCP SDU, and performing header compression processing, integrity protection processing and encryption processing on the first PDCP SDU to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to the header compression processing to generate a second PDCP SDU, and carrying out integrity protection processing and encryption processing on the second PDCP SDU to obtain a target PDCP PDU;
or,
and adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to header compression and integrity protection processing to generate a third PDCP SDU, and encrypting the third PDCP SDU to obtain the target PDCP PDU.
3. The transmission method according to any one of claims 1 to 2, wherein the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
4. The transmission method according to any one of claims 1 to 2, wherein the target PDCP PDU further comprises: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
5. The transmission method according to claim 4, wherein the target PDCP PDU further comprises: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
6. The transmission method according to claim 5, wherein the first indication field and/or the second indication field is located in the header of the target PDCP PDU.
7. The transmission method according to any one of claims 1 to 2, characterized in that:
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between a PDCP PDU head and a PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an integrity protection message verification code MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
8. A transmission method for a packet data convergence protocol PDCP entity at a receiving end, the method comprising:
receiving a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU;
the SDAP End-Marker Control PDU is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
9. The transmission method according to claim 8, wherein the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating the RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
10. The transmission method according to claim 8, wherein the target PDCP PDU further comprises: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
11. The transmission method according to claim 10, wherein the target PDCP PDU further comprises: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
12. The transmission method according to claim 11, wherein the first indication field and/or the second indication field is located in the target PDCP PDU header.
13. The transmission method according to claim 8, characterized in that:
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between a PDCP PDU head and a PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
14. A transmitting-end packet data convergence protocol, PDCP, entity comprising a transceiver configured to:
sending a target PDCP protocol data unit PDU which carries a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU;
the SDAP End-Marker Control PDU is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
15. The transmitting side PDCP entity of claim 14, further comprising a processor configured to:
taking the SDAP End-Marker Control PDU received from the SDAP entity as a PDCP SDU to carry out header compression processing and/or integrity protection processing and/or encryption processing, and adding the processed SDAP End-Marker Control PDU into the PDCP SDU which is subjected to header compression processing, integrity protection processing and encryption processing to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into a PDCP SDU to generate a first PDCP SDU, and performing header compression processing, integrity protection processing and encryption processing on the first PDCP SDU to obtain a target PDCP PDU;
or,
adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDU subjected to the header compression processing to generate a second PDCP SDU, and carrying out integrity protection processing and encryption processing on the second PDCP SDU to obtain a target PDCP PDU;
or,
and adding the SDAP End-Marker Control PDU received from the SDAP entity into the PDCP SDUs subjected to header compression and integrity protection processing to generate a third PDCP SDU, and encrypting the third PDCP SDU to obtain the target PDCP PDU.
16. The transmitting side PDCP entity according to any of claims 14 to 15, wherein the radio bearer RB carrying the target PDCP PDU is any of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating an RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
17. The transmitting side PDCP entity according to any of claims 14 to 15, wherein the target PDCP PDU further comprises: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
18. The transmitting end PDCP entity of claim 17, wherein the target PDCP PDU further comprises: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
19. The transmitting end PDCP entity of claim 18, wherein the first indication field and/or the second indication field is located in the target PDCP PDU header.
20. The transmitting side PDCP entity according to any one of claims 14 to 15, wherein:
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an integrity protection message verification code MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
21. A receiving-end packet data convergence protocol, PDCP, entity comprising a transceiver configured to:
receiving a target PDCP protocol data unit PDU carrying a SDAP End-Marker Control protocol data unit SDAP End-Marker Control PDU;
the SDAP End-Marker Control PDU is subjected to header compression processing and/or integrity protection processing and/or encryption processing.
22. The receiving side PDCP entity of claim 21, wherein the radio bearer RB carrying the target PDCP PDU is any one of the following RBs:
the RB of the user equipment UE to which the SDAP End-Marker Control PDU belongs;
and generating an RB of the QoS (quality of service) flow of the SDAP End-Marker Control PDU.
23. The receiving side PDCP entity of claim 21, wherein the target PDCP PDU further comprises: a first indication field, configured to indicate whether the target PDCP PDU carries an SDAP End-Marker Control PDU.
24. The receiving side PDCP entity of claim 23, wherein the target PDCP PDU further comprises: a second indication field, configured to indicate the number or length of the SDAP End-Marker Control PDU carried in the target PDCP PDU.
25. The receiving end PDCP entity of claim 24, wherein the first indication field and/or the second indication field is located at a header of the target PDCP PDU.
26. The receiving end PDCP entity of claim 21, wherein:
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the PDCP SDU;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned between the PDCP SDU and the MAC-I;
or,
under the condition that the target PDCP PDU is a data PDU, the SDAP End-Marker Control PDU is positioned behind an integrity protection message verification code MAC-I;
or,
under the condition that the target PDCP PDU is a Control PDU, the SDAP End-Marker Control PDU is positioned between the PDCP PDU head and the Control content;
or,
and under the condition that the target PDCP PDU is the Control PDU, the SDAP End-Marker Control PDU is positioned behind the Control content.
27. A transmitting-end packet data convergence protocol, PDCP, entity comprising a memory, a processor, and a computer program stored on the memory and executable on the processor; characterized in that the processor, when executing the computer program, implements the transmission method according to any one of claims 1 to 7.
28. A receiving-end packet data convergence protocol, PDCP, entity comprising a memory, a processor and a computer program stored on said memory and executable on said processor; characterized in that the processor, when executing the computer program, implements the transmission method according to any one of claims 8 to 13.
29. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the steps in the transmission method according to any one of claims 1 to 7; or the program is executed by a processor to implement the steps in the transmission method according to any one of claims 8 to 13.
CN201811583625.XA 2018-12-24 2018-12-24 Transmission method, transmitting side PDCP entity and receiving side PDCP entity Active CN111356178B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811583625.XA CN111356178B (en) 2018-12-24 2018-12-24 Transmission method, transmitting side PDCP entity and receiving side PDCP entity

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811583625.XA CN111356178B (en) 2018-12-24 2018-12-24 Transmission method, transmitting side PDCP entity and receiving side PDCP entity

Publications (2)

Publication Number Publication Date
CN111356178A CN111356178A (en) 2020-06-30
CN111356178B true CN111356178B (en) 2023-04-07

Family

ID=71195586

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811583625.XA Active CN111356178B (en) 2018-12-24 2018-12-24 Transmission method, transmitting side PDCP entity and receiving side PDCP entity

Country Status (1)

Country Link
CN (1) CN111356178B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111435930B (en) * 2019-01-11 2022-09-16 中国移动通信有限公司研究院 Control PDU (protocol data Unit) sending method and device, electronic equipment and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009018318A2 (en) * 2007-08-02 2009-02-05 Interdigital Patent Holdings, Inc. Packet data convergence protocol procedures

Also Published As

Publication number Publication date
CN111356178A (en) 2020-06-30

Similar Documents

Publication Publication Date Title
CN107094142B (en) Method and device for decompressing and compressing uplink data
RU2728893C1 (en) Method of implementing safety, device and system
JP4955809B2 (en) Data transmission method in wireless communication system
CN112003937B (en) Satellite data transmission method, device, computer equipment and storage medium
CN111510278B (en) Hyper frame number HFN synchronization method, terminal and storage medium
CN109714292A (en) The method and apparatus of transmitting message
CN108632326B (en) Method and device for transmitting data by protocol data unit
CN110071935B (en) Method for realizing SDAP (software development association protocol) head assembly of terminal in 5G system
EP1687998B1 (en) Method and apparatus to inline encryption and decryption for a wireless station
US10419212B2 (en) Methods, systems, apparatuses, and devices for securing network communications using multiple security protocols
US20230145440A1 (en) Method and device for selective user plane security in wireless communication system
WO2017148419A1 (en) Data transmission method and server
JP2022043097A (en) Communication method of user device, communication method of radio access node, user device, and radio access node
CN111356178B (en) Transmission method, transmitting side PDCP entity and receiving side PDCP entity
WO2024032742A1 (en) Service processing method and apparatus, device, storage medium, and program product
CN112566123B (en) Method and device for determining abnormal network node
WO2018214070A1 (en) Decoding method and device
CN102422592A (en) Wireless communication apparatus and wireless communication method
CN112333768A (en) Apparatus and method for data packet retransmission between multilink devices
CN108810981B (en) Data transmission method and device
WO2019015487A1 (en) Data retransmission method, rlc entity and mac entity
WO2022021258A1 (en) Communication method and apparatus
CN108012289B (en) PDU (protocol data Unit) sending method and device and PDU receiving method and device
CN114615657A (en) Data segmentation decryption method and device in 5G communication
CN114423001A (en) Decryption method, server and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant