CN115174491A - Communication method and communication device - Google Patents

Communication method and communication device Download PDF

Info

Publication number
CN115174491A
CN115174491A CN202110362488.2A CN202110362488A CN115174491A CN 115174491 A CN115174491 A CN 115174491A CN 202110362488 A CN202110362488 A CN 202110362488A CN 115174491 A CN115174491 A CN 115174491A
Authority
CN
China
Prior art keywords
information
hfn
pdcp pdu
count
pdcp
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.)
Pending
Application number
CN202110362488.2A
Other languages
Chinese (zh)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202110362488.2A priority Critical patent/CN115174491A/en
Priority to PCT/CN2022/084954 priority patent/WO2022206983A1/en
Publication of CN115174491A publication Critical patent/CN115174491A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/0079—Receiver details
    • 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/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements

Landscapes

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

Abstract

The application relates to a communication method and a communication device, in the method, a terminal device receives first information from a network device, wherein the first information comprises information of a first HFN and information of a first SN, or the information of the first HFN and the information of an SN range, or the information of a COUNT range; receiving a first PDCP PDU from a network device, the first PDCP PDU comprising a second SN; and determining the HFN of the first PDCP PDU according to the first information and the second SN. By adopting the method, the terminal equipment can determine the HFN of the first PDCP PDU according to the first information provided by the network equipment, so that the terminal equipment and the network equipment can align the HFN of the PDCP PDU, and the reliability is further improved.

Description

Communication method and communication device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a communication method and a communication apparatus.
Background
Currently, wireless communication systems are widely deployed to provide various types of communication such as voice services, data services, and so on. The communication system comprises one or more terminal devices, which are connected to a core network through an access network to realize communication among a plurality of communication devices. In some scenarios, for example, a New Radio (NR) multicast/broadcast scenario, the reliability requirement on data service transmission is high.
In the prior art, when performing unicast communication, a receiving end and a transmitting end may communicate using the same initial Hyper Frame Number (HFN) value, and accordingly, both the receiving end and the transmitting end may perform subsequent HFN maintenance based on the same initial HFN value and the same mechanism. However, for some scenarios, for example, in a multicast broadcast service communication scenario, when a terminal device starts to receive a certain multicast service, and a network device may have transmitted the multicast service for a certain period of time, the terminal device cannot determine the HFN used by the network device, so that the HFN cannot be aligned between the terminal device and the network device.
Disclosure of Invention
The application provides a communication method and device, which can improve the reliability of data communication.
In a first aspect, an embodiment of the present application provides a communication method, which is applied to a terminal device or may also be applied to a chip inside the terminal device. In the method, the terminal device receives first information from a network device, where the first information includes any one of: information of the first HFN and information of the first SN; or, information of the first HFN and information of the SN range; alternatively, information of COUNT range; receiving a first PDCP PDU from the network device, the first PDCP PDU comprising a second SN; and determining the HFN of the first PDCP PDU according to the first information and the second SN.
In the scheme, the terminal equipment receives first information from the network equipment, and determines an HFN corresponding to the first PDCP PDU according to the first information and second SN information carried in the received PDCP PDU; so that the terminal device and the network device can align the initial value of HFN or HFN of PDCP PDU. The normal receiving of data is ensured, the problem of packet loss or out-of-order delivery caused by the misalignment of HFNs is avoided, and the reliability is improved. In addition, the method can also be beneficial to decryption and integrity verification of the terminal equipment side, so that the problem of packet loss caused by unsuccessful integrity verification is avoided, and the reliability is improved. In addition, compared with the scheme that the terminal device sets RX _ DELIV as the COUNT provided by the network device, the method can avoid the problems of packet loss and/or window jam at the receiving side (for example, the window cannot slide due to the fact that part of data cannot be successfully received, so that data cannot be delivered to an upper layer, and communication delay is increased) caused by unreasonable setting of the COUNT, thereby improving the reliability of data reception, improving the communication efficiency, and reducing the communication delay.
In one possible implementation, the first information includes information of a first HFN and information of a first SN, and the determining the HFN of the first PDCP PDU according to the first information and the second SN includes any one or more of:
if the second SN is less than the difference between the first SN and a first parameter, the HFN of the first PDCP PDU is equal to the first HFN plus 1; the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than or equal to the sum of the first SN and a first parameter; the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and a first parameter and/or the second SN is less than a sum of the first SN and the first parameter.
In another possible implementation manner, the first information includes: information of a first HFN and information of a SN range, said determining an HFN of said first PDCP PDU based on said first information and said second SN, comprising any one or more of:
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is within the range of SNs; the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than a minimum value within the range of SNs; the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than a maximum value within the range of SNs.
Optionally, the information of the SN range includes information of a third SN and information of a fourth SN, and it is understood that the information of the SN range may be determined by the information of the third SN and the information of the fourth SN. In one possible implementation, the information of the third SN is a lower boundary of the SN range (or referred to as a minimum value of the SN range), and the information of the fourth SN is an upper boundary of the SN range (or referred to as a maximum value of the SN range).
Optionally, the minimum value in the SN range is 0; optionally, the maximum value in the SN range is 2 X-1 Where X represents the number of bits corresponding to the SN length.
In yet another possible implementation manner, the first information includes information of a COUNT range, and the determining the HFN of the first PDCP PDU according to the first information and the second SN includes any one or more of the following:
if the second SN is greater than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range; and if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
The information of the COUNT range includes: the information of the first COUNT and the information of the second COUNT, it is understood that the COUNT range may be determined by the information of the first COUNT and the information of the second COUNT. There are various ways to implement the information about the first COUNT and the information about the second COUNT:
in one possible design, the first COUNT information and the second COUNT information may include: in this embodiment, the information of the fifth SN is common to the information of the first HFN, the information of the second HFN, and the information of the fifth SN. For example, the default terminal device may perform an operation with the information of the fifth SN and the information of the first HFN and the information of the second HFN, respectively, to obtain the information of the first COUNT and the information of the second COUNT, so that the network device does not need to repeatedly indicate the information of the fifth SN, thereby saving signaling overhead.
In another possible design, the information of the first COUNT and the information of the second COUNT include: information of the first HFN and information of the second HFN and information of the sixth SN and information of the seventh SN, in this way, the information of the first HFN has information of its corresponding SN (for example, information of the sixth SN or information of the seventh SN), the information of the second HFN also has information of its corresponding SN (for example, information of the seventh SN or information of the sixth SN), and the information of which SN the information of the HFN corresponds to may be indicated by the network device or predefined by the protocol, for example, the information order of the default HFN is the same as the information order of its corresponding SN, or the information of the first SN after the information of the default HFN is information of its corresponding SN.
In yet another possible design, the information on the first COUNT and the information on the second COUNT may include: in this way, the HFN information corresponding to the first COUNT is shared, for example, the default terminal device may perform an operation by using the HFN information corresponding to the first COUNT and the information of the eighth SN to obtain the information of the second COUNT, so that the network device does not need to repeatedly indicate the HFN information corresponding to the second COUNT, thereby saving signaling overhead.
In a possible implementation manner, the first information is carried in a radio resource control RRC message, or a broadcast message, or a radio bearer configuration or PDCP control PDU corresponding to the first PDCP PDU.
In one possible implementation, the method further includes: before receiving first information from a network device, sending a request message to the network device, where the request message is used to request the first information.
Therefore, the terminal device can send a request message to the network device to inform the network device of the requirement of the network device for the first information, and accordingly, the network device can send the first information according to the request message sent by the terminal device, so that on one hand, the mode of obtaining the first information by the terminal device is more flexible, and in addition, the resource waste caused by the fact that the network device sends the first information to unnecessary terminal devices can be avoided.
In one possible implementation, the method further includes: setting a first state variable according to one of the following methods: setting the minimum value or the maximum value in the received COUNT of the first PDCP PDU and the COUNT corresponding to the first information as the first state variable; setting the minimum value or the maximum value in the COUNT of the received N PDCP PDUs as the first state variable, wherein N is a positive integer; setting the minimum value or the maximum value of the COUNT of the received N PDCP PDUs and the COUNT corresponding to the first information as the first state variable, wherein N is a positive integer; setting a minimum value or a maximum value in a COUNT of PDCP PDUs received within a first time period T as the first state variable; setting the minimum value or the maximum value of the COUNT of the PDCP PDU received in the first time period T and the COUNT corresponding to the first information as the first state variable.
In one possible implementation, any one or more of the first PDCP PDU, the received N PDCP PDUs, the PDCP PDUs received within the first time period T, and the first information is associated with the first PDCP entity or with the first radio bearer.
In one possible implementation, the first PDCP entity and/or the first radio bearer is associated with a first service, which includes a broadcast service and/or a multicast service.
In one possible implementation, the first PDCP PDU includes a first PDCP PDU received by the terminal device.
In a second aspect, a communication method is provided, which is applied to a network device or a chip inside the network device. In the method, a network device sends first information to a terminal device, wherein the first information comprises any one of the following: information of the first HFN and information of the first SN; or, information of the first HFN and information of the SN range; alternatively, information of COUNT range; and sending a first PDCP PDU to the terminal equipment, wherein the first PDCP PDU comprises a second SN. Reference may be made to the description relating to the first aspect with regard to possible implementations and technical effects of the first information.
In a possible implementation manner, before the network device sends the first information to the terminal device, the method further includes: and receiving a request message sent by the terminal equipment, wherein the request message is used for requesting the first information.
Optionally, the request message is carried in a radio resource control RRC message, or a broadcast message, or a downlink control information DCI, or a media access control unit MAC CE, or a message in a random access process.
Optionally, the message in the random access procedure includes: a first message of the random access procedure (e.g., msg1 or MsgA), or a third message of the random access procedure (e.g., msg 3).
In one possible implementation, the network device counts a first number, where the first number includes: the number of request messages received by the network device; or the number of terminal devices requesting the first information; if the first preset condition is met, the network equipment sends first information in a broadcast and/or multicast mode; if the first preset condition is not met, the network device sends the first information in a unicast mode, wherein the first preset condition may be: the first number is not greater than or less than a preset number.
Therefore, the network equipment can send the first information in a unicast mode when the number of terminal equipment requesting to acquire the first information is small, so that unnecessary information reception of the terminal equipment can be avoided; when the number of terminal devices requesting the first information is large, the first information is sent in a broadcast and/or multicast mode, so that resource waste caused by excessive unicast sending of the first information can be avoided.
With regard to the technical effects brought about by some possible implementations of the second aspect, reference may be made to the introduction of the technical effects of the first aspect or the respective implementations of the first aspect.
In a third aspect, a communication method is provided, which is applied to a terminal device or a chip inside the terminal device. In the method, a terminal device receives a PDCP PDU from a network device; the terminal equipment receives first indication information from network equipment, wherein the first indication information is used for indicating whether HFN exists in PDCP PDU or indicating whether COUNT exists in PDCP PDU; or,
the first indication information is used for indicating a PDCP PDU format type, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In a possible implementation manner, the terminal device sends capability information to the network device, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate a format type supported by the terminal device, or is used to indicate whether the terminal device supports only the first type.
In a possible implementation manner, second indication information is received from the network device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate format types supported by the network device, or is used to indicate whether the network device supports only the first type.
In a possible implementation manner, the first indication information is carried in a radio resource control RRC message, or a PDCP control PDU, or a radio bearer configuration corresponding to the PDCP PDU or the PDCP PDU.
In a possible implementation manner, any one or more of the first indication information, the second indication information, and the format type is corresponding to a first PDCP entity or a first radio bearer.
In one possible implementation, the first PDCP entity and/or the first radio bearer is associated with a first service, which includes a broadcast service and/or a multicast service.
Therefore, on one hand, the HFN information or the COUNT information is carried in the PDCP PDU, so that the terminal equipment can quickly determine the HFN for receiving the PDCP PDU, the HFN between the terminal equipment and the network equipment is maintained more flexibly, and the continuity and the reliability of the service are improved.
In a fourth aspect, a communication method is provided, which is applied to a network device or a chip inside the network device. In the method, a network device sends a PDCP PDU to a terminal device; the network equipment sends first indication information to the terminal equipment, wherein the first indication information is used for indicating whether HFN exists in PDCP PDU or indicating whether COUNT exists in PDCP PDU; or,
the first indication information is used for indicating a PDCP PDU format type, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In a possible implementation manner, the network device receives capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate a format type supported by the terminal device, or is used to indicate whether the terminal device supports only a first type.
In a possible implementation manner, the network device sends second indication information to the terminal device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate format types supported by the network device, or is used to indicate whether the network device supports only the first type.
In a possible implementation manner, the first indication information is carried in a radio resource control RRC message, or a PDCP control PDU, or the PDCP PDU or a radio bearer configuration corresponding to the PDCP PDU.
In a possible implementation manner, any one or more of the first indication information, the second indication information, and the format type is corresponding to a first PDCP entity or a first radio bearer.
In one possible implementation, the first PDCP entity and/or the first radio bearer is associated with a first service, which includes a broadcast service and/or a multicast service.
With regard to the technical effects brought about by some possible implementations of the fourth aspect, reference may be made to the introduction of the second aspect or the technical effects of the respective implementations of the second aspect.
In a fifth aspect, a communication device is provided, where the communication device is configured to perform the method in the first aspect or any possible implementation manner of the first aspect, and specifically, the communication device may include modules, for example, a sending module and a receiving module, and optionally, may further include a processing module, configured to perform the method in any optional implementation manner of the first aspect or the first aspect. For example, the sending module and the receiving module may belong to a transceiver module, and the sending module and the receiving module may be different functional modules, or may also be the same functional module (i.e., a transceiver module or a transceiver unit), but can implement the sending function and the receiving function. Illustratively, the communication device is a communication device, or a chip or other component provided in a communication device. Illustratively, the communication device is a terminal device. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor. Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may be the same functional module (e.g., a transceiver), but capable of implementing the sending function and the receiving function. If the communication device is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the communication device is a chip disposed in a communication device, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication device to realize transceiving of information through the radio frequency transceiving component.
The transceiver unit is configured to receive first information from a network device, where the first information includes any one of:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
a transceiving unit, further configured to receive a first PDCP PDU from the network device, where the first PDCP PDU includes a second SN;
a processing unit, configured to determine the HFN of the first PDCP PDU according to the first information and the second SN.
In a sixth aspect, a communications apparatus is provided. The communication device is configured to perform the method in any optional implementation manner of the second aspect or the second aspect, and specifically, the communication device may include modules, for example, a sending module and a receiving module, and optionally, may further include a processing module, configured to perform the method in any optional implementation manner of the first aspect or the first aspect. For example, the sending module and the receiving module may belong to a transceiver module, and the sending module and the receiving module may be different functional modules, or may also be the same functional module (i.e., a transceiver module or a transceiver unit), but can implement the sending function and the receiving function. Illustratively, the communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device. For example, the transceiver module may be implemented by a transceiver, and the processing module may be implemented by a processor. Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may be the same functional module (e.g., a transceiver), but capable of implementing the sending function and the receiving function. If the communication means is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the communication device is a chip disposed in a communication device, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication device to realize transceiving of information through the radio frequency transceiving component.
The receiving and sending unit is configured to send first information to a terminal device, where the first information includes any one of:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
and the transceiving unit is further configured to send a first PDCP PDU to the terminal device, where the first PDCP PDU includes the second SN.
In a seventh aspect, a communication apparatus is provided, where the communication apparatus is configured to perform the method in any possible implementation manner of the third aspect or the third aspect, and specifically, the communication apparatus may include means for performing the method in any optional implementation manner of the first aspect or the first aspect, for example, the communication apparatus includes a sending module and a receiving module, and optionally, may further include a processing module. For example, the sending module and the receiving module may belong to a transceiver module, and the sending module and the receiving module may be different functional modules, or may also be the same functional module (i.e., a transceiver module or a transceiver unit), but can implement the sending function and the receiving function. Illustratively, the communication device is a communication device, or a chip or other component provided in the communication device. Illustratively, the communication device is a terminal device. For example, the transceiver module may also be implemented by a transceiver, and the processing module may also be implemented by a processor. Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may be the same functional module (e.g., a transceiver), but capable of implementing the sending function and the receiving function. If the communication device is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the communication device is a chip disposed in a communication device, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication device to realize transceiving of information through the radio frequency transceiving component.
The receiving and sending unit is used for receiving PDCP PDUs from the network equipment;
the transceiver unit is further configured to receive first indication information from a network device, where the first indication information is used to indicate whether an HFN exists in a PDCP PDU or whether a COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating a PDCP PDU format type, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In an eighth aspect, a communication device is provided, where the communication device is configured to perform the method in any possible implementation manner of the fourth aspect or the fourth aspect, and specifically, the communication device may include modules, such as a sending module and a receiving module, and optionally, may further include a processing module, configured to perform the method in any optional implementation manner of the first aspect or the first aspect. For example, the sending module and the receiving module may belong to a transceiver module, and the sending module and the receiving module may be different functional modules, or may also be the same functional module (that is, a transceiver module or called a transceiver unit), but can implement a sending function and a receiving function. Illustratively, the communication device is a communication device, or a chip or other component provided in a communication device. Illustratively, the communication device is a terminal device. For example, the transceiver module may be implemented by a transceiver, and the processing module may be implemented by a processor. Alternatively, the sending module may be implemented by a sender, the receiving module may be implemented by a receiver, and the sender and the receiver may be different functional modules, or may be the same functional module (e.g., a transceiver), but capable of implementing the sending function and the receiving function. If the communication device is a communication device, the transceiver is implemented, for example, by an antenna, a feeder, a codec, etc. in the communication device. Alternatively, if the communication device is a chip disposed in a communication device, the transceiver (or the transmitter and the receiver) is, for example, a communication interface in the chip, and the communication interface is connected with a radio frequency transceiving component in the communication device to realize transceiving of information through the radio frequency transceiving component.
The receiving and sending unit is used for sending the PDCP PDU to the terminal equipment; the transceiving unit is further configured to send first indication information to a terminal device, where the first indication information is used to indicate whether a first HFN exists in a PDCP PDU or whether a COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating a format type of PDCP PDU, the format type includes a first type and/or a second type, the PDCP PDU corresponding to the first type includes information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not include the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In a ninth aspect, a communication device is provided. The communication device includes one or more processors and optionally a communication interface, which may be used to communicate with other devices or apparatuses. Optionally, the communication device may also include one or more memories for storing computer instructions. The one or more processors and the one or more memories are mutually coupled for implementing the methods described above for the first aspect or the various alternative embodiments of the third aspect. Alternatively, the communication device may not include a memory, and at least one memory may be located external to the communication device. The one or more processors, the one or more memories and the communication interface are mutually coupled for implementing the methods described above for the first aspect or the various alternative embodiments of the third aspect or the third aspect. For example, the communication device may also include one or more computer programs, stored in one or more memories, the one or more computer programs including computer instructions. The computer instructions stored by the one or more memories, when executed by the one or more processors, cause the communications apparatus to perform the methods described above in the first aspect or the various alternative embodiments of the third aspect. Illustratively, the communication device is a communication device, or a chip or other component provided in a communication device. Illustratively, the communication device is a terminal device.
Where the communication means is a communication device, the communication interface is implemented, for example, by a transceiver (or a transmitter and a receiver) in the communication device, for example, by an antenna, a feeder, a codec, etc. in the communication device. Or, if the communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to realize transceiving of information through the radio frequency transceiving component.
In a tenth aspect, a communication device is provided. The communication device includes one or more processors and optionally a communication interface, which may be used to communicate with other devices or apparatuses. Optionally, the communication device may further include one or more memories for storing computer instructions. The one or more processors and the one or more memories are mutually coupled for implementing the methods described above for the second aspect or various alternative embodiments of the fourth aspect or the fourth aspect. Alternatively, the communication device may not include a memory, and at least one memory may be located external to the communication device. The one or more processors, the one or more memories and the communication interface are mutually coupled for implementing the methods described above for the second aspect or various alternative embodiments of the fourth aspect or the fourth aspect. For example, the communication device may also include one or more computer programs, stored in one or more memories, the one or more computer programs including computer instructions. The one or more processors, when executing the computer instructions stored by the one or more memories, cause the communication device to perform the methods described above in the second aspect or various alternative embodiments of the fourth aspect or the fourth aspect. Illustratively, the communication device is a communication device, or a chip or other component provided in a communication device. Illustratively, the communication device is a network device, e.g., an access network device, e.g., a base station.
Where the communication means is a communication device, the communication interface is implemented, for example, by a transceiver (or a transmitter and a receiver) in the communication device, for example, by an antenna, a feeder, a codec, etc. in the communication device. Or, if the communication device is a chip disposed in the communication apparatus, the communication interface is, for example, an input/output interface, such as an input/output pin, of the chip, and the communication interface is connected to a radio frequency transceiving component in the communication apparatus to implement transceiving of information through the radio frequency transceiving component.
In an eleventh aspect, there is provided a computer program product comprising: a computer program (also referred to as code, or instructions), which when executed, causes a computer to perform any of the aspects described above or the methods in any of the possible implementations of the aspects.
In a twelfth aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code, or instructions) that, when executed on a computer, causes the computer to perform the method of any one of the above aspects or any one of the possible implementations of the aspect.
In a thirteenth aspect, a chip system is provided, the chip system comprising one or more processors and a communication interface, the processors being coupled to the communication interface for implementing the method of any one of the above aspects or any one of the possible implementations of this aspect.
Optionally, the chip system may further include a memory, for example, the processor may read and execute a software program stored in the memory to implement the method provided in the first aspect or any one of the optional embodiments. Alternatively, the memory may not be included in the chip system, but may be located outside the chip system, and the processor may read and execute a software program stored in the external memory to implement the method in any one of the above aspects or any possible implementation manner of the aspect.
Drawings
Fig. 1 is a schematic diagram of a network architecture suitable for use in the embodiment of the present application;
FIG. 2 is a schematic diagram of another network architecture suitable for use in embodiments of the present application;
FIG. 3 is a schematic diagram of another network architecture suitable for use in embodiments of the present application;
fig. 4a is a schematic diagram of COUNT provided in an embodiment of the present application;
fig. 4b is a schematic diagram illustrating a process of determining HFN according to an embodiment of the present application;
fig. 4c is a schematic diagram illustrating a position relationship between HFN information and corresponding SNs according to an embodiment of the present disclosure;
fig. 4d is a schematic diagram of a position relationship between another HFN information and its corresponding SN according to the embodiment of the present application;
fig. 5 is a flowchart illustrating a communication method according to an embodiment of the present application;
fig. 6 is a flowchart illustrating another communication method according to an embodiment of the present application;
FIG. 7a is a diagram illustrating a PDCP PDU format according to an embodiment of the present application;
FIG. 7b is a diagram illustrating another PDCP PDU format according to an embodiment of the present application;
FIG. 7c is a diagram illustrating a PDCP PDU format according to an embodiment of the present application;
FIG. 7d is a diagram illustrating another PDCP PDU format according to an embodiment of the present application;
FIG. 7e is a diagram illustrating another PDCP PDU format according to an embodiment of the present application;
FIG. 7f is a diagram illustrating another PDCP PDU format according to an embodiment of the present application;
fig. 8 is a flowchart illustrating a further communication method according to an embodiment of the present application;
fig. 9 is a schematic block diagram of a terminal device provided in an embodiment of the present application;
fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application;
fig. 11 is a schematic block diagram of a communication device according to an embodiment of the present application;
fig. 12 is another schematic block diagram of a communication device according to an embodiment of the present application;
fig. 13 is a further schematic block diagram of a communication device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
First, some terms in the embodiments of the present application are explained so as to be easily understood by those skilled in the art.
(1) The terminal equipment: the terminal device is a device with a wireless transceiving function, and may be a fixed device, a mobile device, a handheld device (e.g., a mobile phone), a wearable device, an in-vehicle device, or a wireless apparatus (e.g., a communication module, a modem, or a chip system) built in the above device. The terminal device is used for connecting people, objects, machines and the like, and can be widely used in various scenes, such as but not limited to the following scenes: cellular communication, device-to-device communication (D2D), vehicle-to-all (V2X), machine-to-machine/machine-type communication (M2M/MTC), internet of things (IoT), virtual Reality (VR), augmented Reality (AR), industrial control (industrial control), unmanned driving (self driving), remote medical (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart traffic, smart city (smart city), unmanned aerial vehicle, robot, etc. scenarios. The terminal device may be sometimes referred to as a User Equipment (UE), a terminal, an access station, a UE station, a remote station, a wireless communication device, or a user equipment, and for convenience of description, the terminal device is described herein by taking the UE as an example.
(2) A network device: including, for example, access network equipment, and/or core network equipment. The access network equipment is equipment with a wireless transceiving function and is used for communicating with the terminal equipment. The access network device includes, but is not limited to, a base station (BTS, node B, eNodeB/eNB, or gbnodeb/gNB), a Transmission Reception Point (TRP), a base station for subsequent evolution in 3GPP, an access Node, a wireless relay Node, a wireless backhaul Node, and the like in the above communication system. The base station may be: macro base stations, micro base stations, pico base stations, small stations, relay stations, etc. Multiple base stations may support the same access technology network as mentioned above, or may support different access technologies networks as mentioned above. A base station may include one or more co-sited or non-co-sited transmission receiving points. The network device may also be a wireless controller, a Centralized Unit (CU), and/or a Distributed Unit (DU) in a Cloud Radio Access Network (CRAN) scenario. The network device may also be a server, a wearable device, or a vehicle mounted device, etc. For example, the network device in V2X technology may be a Road Side Unit (RSU). The following description will take the access network device as a base station as an example. The multiple network devices in the communication system may be base stations of the same type or base stations of different types. The base station may communicate with the terminal device, and may also communicate with the terminal device through the relay station. A terminal device may communicate with multiple base stations in different access technologies. The core network equipment is used for realizing the functions of mobile management, data processing, session management, policy, charging and the like. The names of devices implementing the core network function in systems with different access technologies may be different, and this application does not limit this. Taking a 5G system as an example, the core network device includes: an access and mobility management function (AMF), a Session Management Function (SMF), or a User Plane Function (UPF), etc.
(3) In the embodiment of the application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address list, word processing software, instant messaging software and the like. Furthermore, the embodiment of the present application does not particularly limit the specific structure of the execution main body of the method provided by the embodiment of the present application, as long as the communication can be performed according to the method provided by the embodiment of the present application by running the program recorded with the code of the method provided by the embodiment of the present application, for example, the execution main body of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module capable of calling the program and executing the program in the terminal device or the network device.
In addition, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact Disk (CD), digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
(4) The terms "system" and "network" in the embodiments of the present application may be used interchangeably. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a alone, A and B together, and B alone, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, "at least one of A, B, and C" includes A, B, C, AB, AC, BC, or ABC.
And, unless specifically stated otherwise, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing between a plurality of objects, and do not limit the order, sequence, priority, or importance of the plurality of objects. For example, the first SN and the second SN are merely for distinguishing different SNs, and do not indicate a difference in priority, importance, or the like between the two SNs.
The technical scheme of the application is further described in detail in the following with the accompanying drawings of the specification.
Fig. 1 is a schematic diagram of a communication system suitable for use in the embodiment of the present application. As shown in fig. 1, the terminal device 130 may access a wireless network to obtain services of an external network (e.g., the internet) through the wireless network, or may communicate with other devices through the wireless network, such as may communicate with other terminal devices. The wireless network includes a Radio Access Network (RAN) device 110 and a Core Network (CN) device 120, where the RAN device 110 is configured to access a terminal device 130 to the wireless network, and the CN device 120 is configured to manage the terminal device and provide a gateway for communicating with an external network. It should be understood that the number of each device in the communication system shown in fig. 1 is merely an illustration, and the embodiment of the present application is not limited thereto, and in practical applications, more terminal devices 130, more RAN devices 110, and other devices may also be included in the communication system.
Fig. 2 is a schematic diagram of another network architecture applicable to the embodiment of the present application. As shown in fig. 2, the network architecture includes CN devices, RAN devices, and terminal devices. The RAN device includes a baseband device and a radio frequency device, where the baseband device may be implemented by one node or by multiple nodes, and the radio frequency device may be implemented independently by being pulled away from the baseband device, or integrated in the baseband device, or partially integrated independently, or partially integrated in the baseband device. For example, in an LTE communication system, a RAN equipment (eNB) includes a baseband device and a radio frequency device, where the radio frequency device may be remotely arranged with respect to the baseband device, e.g., a Remote Radio Unit (RRU) is a remote radio unit arranged with respect to a BBU.
The communication between the RAN device and the terminal device follows a certain protocol layer structure, for example, the control plane protocol layer structure may include functions of protocol layers such as a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a physical layer; the user plane protocol layer structure can comprise the functions of protocol layers such as a PDCP layer, an RLC layer, an MAC layer, a physical layer and the like; in a possible implementation, a Service Data Adaptation (SDAP) layer may be further included above the PDCP layer.
The RAN device may implement the functions of the protocol layers, such as RRC, PDCP, RLC, and MAC, by one node, or may implement the functions of the protocol layers by a plurality of nodes. For example, in an evolved structure, the RAN equipment may include CUs) and DUs, which may be centrally controlled by one CU. As shown in fig. 2, the CU and the DU may be divided according to protocol layers of the radio network, for example, functions of a PDCP layer and above are provided in the CU, and functions of protocol layers below the PDCP layer, for example, a RLC layer and a MAC layer, are provided in the DU.
This division of the protocol layers is only an example, and it is also possible to divide the protocol layers at other protocol layers, for example, at the RLC layer, and set the functions of the RLC layer and the protocol layers above to CU, and the functions of the protocol layers below the RLC layer to DU; alternatively, the functions are divided into some protocol layers, for example, a part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are provided in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are provided in the DU. In addition, the processing time may be divided in other manners, for example, by time delay, a function that needs to satisfy the time delay requirement for processing is provided in the DU, and a function that does not need to satisfy the time delay requirement is provided in the CU.
In addition, the radio frequency device may be integrated independently, not placed in the DU, or integrated in the DU, or partially remote and partially integrated in the DU, which is not limited herein.
Fig. 3 is a schematic diagram of another network architecture applicable to the embodiment of the present application. With respect to the network architecture shown in fig. 2, the Control Plane (CP) and the User Plane (UP) of the CU may also be separated and implemented by being divided into different entities, namely, a Control Plane (CP) CU entity (i.e., a CU-CP entity) and a User Plane (UP) CU entity (i.e., a CU-UP entity), respectively.
In the above network architecture, the signaling generated by the CU may be sent to the terminal device through the DU, or the signaling generated by the terminal device may be sent to the CU through the DU. The DU may directly encapsulate the signaling through a protocol layer without parsing and then transmit the encapsulated signaling to the terminal device or the CU. In the following embodiments, if transmission of such signaling between the DU and the terminal device is involved, in this case, the transmission or reception of the signaling by the DU includes such a scenario. For example, the signaling of the RRC or PDCP layer is finally processed as the signaling of the PHY layer to be sent to the terminal device, or is converted from the received signaling of the PHY layer. Under this architecture, the signaling of the RRC or PDCP layer can also be considered as being sent by the DU, or sent by the DU and the radio bearer.
The network architecture illustrated in fig. 1, fig. 2, or fig. 3 may be applied to communication systems of various Radio Access Technologies (RATs), for example, an LTE communication system, a 5G (or new radio, NR) communication system, a transition system between the LTE communication system and the 5G communication system, a 4.5G communication system, and certainly a future communication system. The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the communication network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. For example, the present invention may be applied to a broadcast multicast scenario, or a vehicle to evolution (V2X) scenario.
The apparatus in the following embodiments of the present application may be located in a terminal device or a network device according to the functions implemented by the apparatus. When the above structure of CU-DU is adopted, the network device may be a CU node, or a DU node, or a RAN device including the CU node and the DU node.
In the present embodiment, "if" may be understood as "when …" or "when … condition is satisfied" or "in the case of …"; in addition, "located" may also be understood as "occupied" or "at"; this is not differentiated by the present application and may be used instead in the following description.
It should be noted that in the embodiment of the present application, the "HFN of a PDCP Protocol Data Unit (PDU)" may be understood as "HFN corresponding to a PDCP PDU"; this is not differentiated by the present application and may be used instead in the following description.
It should be noted that in this embodiment of the present application, "multicast" may also be understood as "multicast", "broadcast", "multicast broadcast"; this is not differentiated in the present application and is used instead in the following description.
In the embodiments of the present application, "setting" may be understood as: "determine" is not a distinction in this application and may be used instead in the following description.
In the present embodiment, the term "SN" may be understood as: "PDCP SN", which is not differentiated herein, may be used instead in the following description.
It should be noted that in the embodiment of the present application, the "COUNT of PDCP PDU" may be understood as: "COUNT corresponding to PDCP PDU", which is not distinguished in this application, may be used instead in the following description.
It should be noted that in the embodiments of the present application, "exist" may be understood as "include" or "include", which is not differentiated in the present application, and may be used alternatively in the following description.
It should be noted that in the embodiments of the present application, "field" may be understood as "field", which is not differentiated in the present application, and may be used instead in the following description.
It should be noted that in the embodiments of the present application, the "PDU header" may be understood as "PDCP PDU (or first PDCP PDU) header" or "PDCP PDU (or first PDCP PDU) header", which is not distinguished by the present application and may be used alternatively in the following description.
Optionally, in the embodiment of the present application, the PDCP PDU may be understood as a "first PDCP PDU", which is not distinguished in the present application and may be used alternatively in the following description.
For example, the receive-side window may include (or be understood as) a reordering window.
The following describes related art features related to embodiments of the present application.
In the prior art, the COUNT may be used for integrity protection and ciphering of the PDCP data packet, after a sending end ciphers the data packet using the COUNT, the ciphered data packet is sent to a receiving end, and the receiving end needs to obtain the COUNT to decipher the data packet. One COUNT is associated with each PDCP PDU, where COUNT is 32 bits. As shown in fig. 4a, the COUNT may be composed of two parts, i.e., a Hyper Frame Number (HFN) of a higher bit and a PDCP Sequence Number (SN) of a lower bit. Wherein, the length of the PDCP SN is configured by an upper layer (for example, a radio access control RRC layer) or a network device, and the length of the HFN is changed along with the change of the length of the PDCP SN. For example, the length of the PDCP SNs may be 12 bits or 18 bits, and accordingly, the length of the HFNs may be (32-PDCP SN size) bits, wherein the PDCP SN size is a number of bits corresponding to the length of the PDCP SNs. For example, if the PDCP SN size is 12 bits, the HFN has a length of (32-12) bits, i.e., 20 bits.
Both communication parties (for example, the terminal device 130 and the radio access network device 110) may maintain their HFNs, and may use the same initial HFN value (for example, HFN starts from 0) before data transmission, and in the data transmission process, after a sending end encrypts and/or integrity-protects a data packet using COUNT, the encrypted data packet and SN of the data packet are sent to a receiving end. After parsing the SN of the data packet, the receiving end may determine the COUNT of the received PDCP data PDU according to the SN and the HFN calculated by the receiving end, and then decrypt and/or check the integrity of the data packet using the COUNT. Fig. 4b shows a schematic process diagram of a method for estimating HFN by a conventional receiving end, which includes:
step 1, receiving PDCP PDU, determining PDCP SN of PDCP PDU;
step 2, if the PDCP SN of the PDCP PDU < the SN part of the state variable and the difference of the reordering window size, step 3 is performed, otherwise step 4 is performed.
Step 3, PDCP HFN of PDCP PDU = HFN part +1 of state variable.
Step 4, if PDCP SN > = SN part of status variable plus reordering window size, then step 5 is executed, otherwise step 6 is executed.
Step 5, PDCP HFN of PDCP PDU = HFN part-1 of the state variable.
Step 6, PDCP HFN of PDCP PDU = HFN part of state variable
And determining the COUNT of the PDCP PDU according to the calculated PDCP HFN of the PDCP PDU and the calculated PDCP SN of the PDCP PDU. As above, the reordering window size is equal to 2 (X-1) The state variable indicates the COUNT of the first PDCP SDU which is not transferred to the upper layer but is still waiting. The initial value is 0. Furthermore, the ">= "means greater than or equal to.
As can be seen from the above technical features, in the existing mechanism, before data transceiving, the receiving end and the transmitting end may maintain the same initial HFN value (e.g., HFN starts from 0), and accordingly, both the transceiving ends may perform HFN maintenance based on the same initial HFN value and the same mechanism. However, for some scenarios, before the terminal device and the network device perform data transceiving, the terminal device may have already transmitted a data packet for a certain period of time, and the terminal device may not be able to correctly determine the HFN value, in other words, the HFN between the terminal device and the network device is out of synchronization, and the data packet subsequently transceived by the terminal device and the network device may be out of synchronization due to the HFN. It may cause the COUNT understood by the terminal device and the network device to be inconsistent, which may further cause the decrypted data to be a problematic or invalid data packet, which affects the reliability of data communication. It may also cause the terminal device to fail to perform integrity check correctly, and then discard the data packet, which affects the reliability of data communication. When the terminal device feeds back the status report to the network device, the network device may not correctly understand the receiving status of the terminal device, and may further cause an erroneous packet loss or perform an unnecessary retransmission, which affects the reliability and/or communication efficiency of data communication. It may also result in out-of-order delivery of the terminal device, affecting the reliability and/or communication efficiency of the data communication.
Some of the scenarios described above include, but are not limited to, the following two scenarios: 1) The method comprises the steps that a terminal device newly joins a network device which is sending Multicast and Broadcast Service (MBS), and if the MBS is sent by the network device for a period of time before, HFNs between the terminal device and the network device are not synchronized; 2) The network device newly joins the MBS service, but the MBS service has been transmitted in other network devices for a period of time, so that HFNs between the network device and the terminal devices served by the network device are not synchronized.
Based on this, embodiments of the present application provide a communication method and apparatus, so as to solve the problem of HFN asynchronism between a terminal device and a network device. Illustratively, the method provided by the embodiments of the present application may include two possible schemes, which are referred to as scheme one and scheme two for convenience of description.
In the first scheme, the terminal equipment receives first information from the network equipment, and determines an HFN corresponding to the received PDCP PDU according to the first information and second SN information carried in the received PDCP PDU; as such, by the network device providing the first information, the secondary terminal device determines the HFN of the received PDCP PDU so that the terminal device and the network device can align the HFN of the PDCP PDU or an initial value of the HFN. The method and the device ensure the normal receiving of the data, avoid the problems of packet loss or disorder delivery caused by the misalignment of the HFNs, and are beneficial to improving the reliability. In addition, the method can also be beneficial to decryption and integrity verification of the terminal equipment side, so that the problem of packet loss caused by unsuccessful integrity verification is avoided, and the reliability is improved. In addition, compared with the scheme that the terminal device sets RX _ DELIV as the COUNT provided by the network device, the method can avoid the problems of packet loss and/or window jam at the receiving side (for example, because some data are not successfully received, the window cannot slide, the data cannot be delivered to an upper layer, and the communication delay is increased) caused by unreasonable setting of the COUNT, thereby improving the reliability of data reception, improving the communication efficiency, and reducing the communication delay.
In the second scheme, the terminal device receives first indication information from the network device, determines whether the PDCP PDU carries HFN information or COUNT information according to the first indication information, and if the PDCP PDU carries HFN information or COUNT information, the terminal device may determine, according to the HFN information or COUNT information, an HFN for receiving the PDCP PDU. Therefore, on one hand, the HFN information or the COUNT information is carried in the PDCP PDU/PDU head, so that the terminal equipment can accurately determine the HFN of the received PDCP PDU, the HFN between the terminal equipment and the network equipment is simpler and/or more flexible to maintain, the normal receiving of data is ensured, the problems of packet loss or out-of-order delivery caused by the misalignment of the HFNs are avoided, and the reliability is improved. In addition, the method can also be beneficial to decryption and integrity verification of the terminal equipment side, so that the problem of packet loss caused by unsuccessful integrity verification is avoided, and the reliability is improved. In addition, compared with the scheme that the terminal device sets RX _ DELIV as the COUNT provided by the network device, the method can avoid the problems of packet loss and/or window jam at the receiving side (for example, the window cannot slide due to the fact that part of data cannot be successfully received, so that data cannot be delivered to an upper layer, and communication delay is increased) caused by unreasonable setting of the COUNT, thereby improving the reliability of data reception, improving the communication efficiency, and reducing the communication delay. On the other hand, by introducing the first indication information, the PDCP PDU (or PDU header) does not need to carry the HFN information or COUNT information all the time, and overhead of air interface resources can be reduced. Meanwhile, the terminal equipment can correctly determine the format of the PDCP PDU (or the PDU header), so that the PDCP PDU (or the PDU header) can be correctly decoded, and the reliability of data reception is improved.
The method provided by the present application is explained below. It should be understood that, in the method embodiments described below, only the network device and the terminal device are taken as the execution subjects, but the network device and the terminal device are not limited to be the execution subjects, and the network device and the terminal device may be replaced by devices capable of implementing the methods in the application. For example, the network device may be replaced with a chip configured in the network device, and the terminal device may be replaced with a chip configured in the terminal device.
Fig. 5 is a flowchart corresponding to a communication method provided in an embodiment of the present application, and as shown in fig. 5, the method includes:
s501, the terminal device receives first information from the network device, and correspondingly, the network device sends the first information to the terminal device.
The first information includes any one of information of the first HFN and information of the first SN; or, information of the first HFN and information of the SN range; or, COUNT range information.
The first information includes information of the first HFN and information of the first SN: the first information includes information of the first COUNT. It is understood that the terminal device determines the information of the first HFN and the information of the first SN according to the information of the first COUNT. As shown in fig. 4a, the COUNT may include a high HFN and a low SN. It can be understood that the terminal device determines the information of the first HFN and the information of the first SN according to the information of the first COUNT, and specifically may be: the terminal device sets the high bits of the first COUNT as the bits of the first HFN and sets the low bits of the first COUNT as the bits of the first SN.
It is to be understood that the (1) information of the first HFN may include the first HFN value or an index of the first HFN. The information of the first SN may include a value of the first SN or an index of the first SN.
Alternatively, the information of the first HFN may include information of all bits or a part of bits of the first HFN.
Alternatively, the information of the first SN may include information of all bits or a part of bits of the first SN.
(2) The information of the SN range may include (or be referred to as, or be replaced by) information of a third SN and information of a fourth SN, and it is understood that the information of the SN range may be determined by the information of the third SN and the information of the fourth SN. In one possible implementation, the third SN is the lower bound of the SN range (or the lowest value in the SN range), and the fourth SN is the upper bound of the SN range (or the highest value in the SN range). For example, the SN range may be: a SN greater than (or, greater than or equal to) the third SN and less than (or, less than or equal to) the fourth SN. For example, the third SN is less than or equal to the fourth SN. For example, the minimum value (or third SN) in the SN range may be 0. For example, the maximum value (or fourth SN) in the SN range can be 2 X -1. Where X represents the number of bits corresponding to SN (or SN length). For example, the third SN is 50, the fourth SN is 100, the SN range is: greater than (or, greater than or equal to) 50, less than (or, less than or equal to) 100, specifically, the SN range may be one of: greater than 50 and less than 100; greater than or equal to 50 and less than 100; greater than 50 and less than or equal to 100; greater than or equal to 50 and less than or equal to 100.
Alternatively, the information of the third SN may include information of all bits or information of a part of bits of the third SN.
Alternatively, the information of the fourth SN may include information of all bits or information of a part of bits of the fourth SN.
As can be seen from the above, the third SN and the fourth SN are configurable, in other words, the third SN and the fourth SN are variable. For example, the minimum value of the third SN is 0. For example, the maximum value of the fourth SN is 2 X -1。
The first information including information of the first HFN and information of the SN range can be understood (or replaced with): the first information includes information of the first COUNT and information of the fourth SN; or, information of the third SN and information of the second COUNT. It is understood that the terminal device determines the information of the first HFN and the information of the third SN according to the information of the first COUNT. It is understood that the terminal device determines the information of the first HFN and the information of the fourth SN according to the information of the second COUNT. As shown in fig. 4a, the COUNT may include a high HFN and a low SN. It can be understood that the terminal device determines the information of the first HFN and the information of the third SN according to the information of the first COUNT, and specifically may be: the terminal device sets the high bits of the first COUNT as the bits of the first HFN, and sets the low bits of the first COUNT as the bits of the third SN. The terminal device determines the information of the first HFN and the information of the fourth SN according to the information of the second COUNT, and specifically may be: the terminal device sets the high bits of the second COUNT as the bits of the first HFN, and sets the low bits of the first COUNT as the bits of the fourth SN.
In one possible implementation, the network device may send one of information of the third SN and information of the fourth SN. Or, the first information sent by the network device may include one of information of the third SN and information of the fourth SN. It is to be understood that the terminal device receives one of the information of the third SN and the information of the fourth SN from the network device. In this case, the terminal device determines the other of the information of the third SN and the information of the fourth SN from one of the information of the third SN and the information of the fourth SN. For example, if the network device sends the information of the third SN but does not send the information of the fourth SN, or the first information may include the information of the third SN but not include the information of the fourth SN, the terminal device determines the information of the fourth SN according to the information of the third SN. For example, the fourth SN is equal to the third SN + b, b being an integer. For example, b may be 2 (X-1) . Where X represents the number of bits corresponding to SN (or SN length). For another example, if the network device sends the information of the fourth SN but does not send the information of the third SN, or the first information includes the information of the fourth SN but does not include the information of the third SN; and the terminal equipment determines the information of the third SN according to the information of the fourth SN. For example, the third SN is equal to the fourth SN-b, b being an integer. For example, b may be 2 (X -1) . Where X represents the number of bits corresponding to SN (or SN length).
It should be noted that b may be protocol-specific, or may be indicated by a network device for a terminal device, or may be preconfigured, which is not limited in this application.
(3) The COUNT range information includes (or is referred to or replaced by): information of the first COUNT andthe second COUNT information, it is understood that the COUNT range can be determined by the first COUNT information and the second COUNT information. In one possible implementation, the first COUNT is the lower boundary of the COUNT range (or the lowest value in the COUNT range), and the second COUNT is the upper boundary of the COUNT range (or the highest value in the COUNT range). For example, the COUNT range may include/be: greater than (or, greater than or equal to) the first COUNT, and less than (or, less than or equal to) the second COUNT. For example, the first COUNT is less than or equal to the second COUNT. For example, the minimum value (or first COUNT) in the COUNT range is 0. For example, the maximum value (or second COUNT) in the COUNT range is 2 Y -1. Where Y represents the number of bits corresponding to COUNT (or COUNT length). For example, a first COUNT of 1000, a second COUNT of 1500, and a COUNT range including/being: greater than (or, greater than or equal to) 1000, and less than (or, less than or equal to) 1500, in particular the COUNT range may be one of: greater than 1000 and less than 1500; greater than or equal to 1000 and less than 1500; greater than 1000 and less than or equal to 1500; greater than or equal to 1000 and less than or equal to 1500.
Alternatively, the information of the first COUNT may include information of all bits or information of a part of bits of the first COUNT.
Alternatively, the information of the second COUNT may include information of all bits or information of a part of bits of the second COUNT.
As can be seen from the above, the first COUNT and the second COUNT are configurable, in other words, the first COUNT and the second COUNT are variable. For example, the first COUNT has a minimum value of 0. For example, the second COUNT has a maximum value of 2 Y -1。
There are various implementations of the information about the first COUNT and the information about the second COUNT, and the following description is made in conjunction with the implementations A1 to A4.
Implementation A1The information of the first COUNT and the information of the second COUNT may include: information of the second HFN and information of the third HFN and information of the fifth SN.
In this embodiment, the information of the fifth SN is common. For example, the terminal device may obtain the information of the first COUNT and the information of the second COUNT by combining the information of the second HFN and the information of the third HFN, respectively, according to the information of the fifth SN. By this method, the network device does not need to repeat the information indicating the fifth SN, thereby signaling overhead can be saved.
As shown in fig. 4a, the COUNT may include a high HFN and a low SN. It can be understood that, the terminal device obtains the information of the first COUNT according to the information of the fifth SN and the information of the second HFN, and specifically, the terminal device may set the bit of the second HFN as the high bit of the first COUNT, and set the bit of the fifth SN as the low bit of the first COUNT. The terminal device obtains the information of the second COUNT according to the information of the fifth SN and the information of the third HFN, and specifically, the terminal device may set a bit of the third HFN as a high bit of the second COUNT, and set a bit of the fifth SN as a low bit of the second COUNT.
Alternatively, the information of the second HFN may include information of all bits or information of a part of bits of the second HFN. Alternatively, the information of the third HFN may include information of all bits or information of a part of bits of the third HFN. Alternatively, the information of the fifth SN may include information of all bits or information of a part of bits of the fifth SN.
In one possible implementation, the network device may send one of the information of the second HFN and the information of the third HFN. Or, the first information sent by the network device may include one of information of the second HFN and information of the third HFN. It is to be appreciated that the terminal device receives one of the information of the second HFN and the information of the third HFN from the network device. In this case, the terminal device determines the other of the information of the second HFN and the information of the third HFN from one of the information of the second HFN and the information of the third HFN. For example, if the network device sends the information of the second HFN but does not send the information of the third HFN, or the first information includes the information of the second HFN but does not include the information of the third HFN, the terminal device determines the information of the third HFN according to the information of the second HFN. For example, the third HFN is equal to the second HFN + m, m being an integer. For example, m may be 1. For another example, if the network device sends the information of the third HFN but does not send the information of the second HFN, or the first information includes the information of the third HFN but does not include the information of the second HFN; and the terminal equipment determines the information of the second HFN according to the information of the third HFN. For example, the second HFN is equal to the third HFN-m, m being an integer. For example, m may be 1.
It should be noted that m may be protocol-specific, may also be indicated by a network device for a terminal device, or may be preconfigured, and the present application is not limited.
Implementation A2The information of the first COUNT and the information of the second COUNT may include: information of a fourth HFN and information of a fifth HFN and information of a sixth SN and information of a seventh SN.
In this embodiment, the information of the fourth HFN has information of its corresponding SN (for example, information of the sixth SN or information of the seventh SN), and the information of the fifth HFN also has information of its corresponding SN (for example, information of the seventh SN or information of the sixth SN), and the information of the HFN corresponding to which SN is indicated by the network device or predefined by the protocol may be understood as long as the terminal device and the network device keep the same understanding, which is not limited by the present invention.
For example, as shown in fig. 4c, the terminal device may learn that there is a corresponding relationship between the information of the fourth HFN and the information of the sixth SN, and further determine the information of the first COUNT (or the information of the second COUNT) according to the information of the fourth HFN and the information of the sixth SN; accordingly, the terminal device may know that there is a corresponding relationship between the information of the fifth HFN and the information of the seventh SN, and further determine the information of the second COUNT (or the information of the first COUNT) according to the information of the fifth HFN and the information of the seventh SN.
For another example, as shown in fig. 4d, the terminal device may learn that there are corresponding relationships between the information of the fourth HFN and the information of the sixth SN, and between the information of the fifth HFN and the information of the seventh SN, and further determine the information of the first COUNT and the information of the second COUNT according to the two corresponding relationships.
It should be noted that, determining the information of the first COUNT according to the information of the fourth HFN and the information of the sixth SN, and determining the information of the second COUNT according to the information of the fifth HFN and the information of the seventh SN may refer to the explanation of obtaining the information of the first COUNT according to the information of the fifth SN and the information of the second HFN in implementation A1, and details are not described here again.
Optionally, the information of the fourth HFN may include information of all bits or information of a part of bits of the fourth HFN. Optionally, the information of the fifth HFN may include information of all bits or information of a part of bits of the fifth HFN.
Alternatively, the information of the sixth SN may include information of all bits or information of a part of bits of the sixth SN.
Alternatively, the information of the seventh SN may include information of all bits or information of a part of bits of the seventh SN.
In one possible implementation, the network device may send one of the information of the fourth HFN and the information of the fifth HFN. Or, the first information sent by the network device may include one of information of the fourth HFN and information of the fifth HFN. It is to be understood that the terminal device receives one of the information of the fourth HFN and the information of the fifth HFN from the network device. In this case, the terminal device determines the other of the information of the fourth HFN and the information of the fifth HFN from one of the information of the fourth HFN and the information of the fifth HFN. For example, if the network device transmits the information of the fourth HFN but does not transmit the information of the fifth HFN, or the first information may include the information of the fourth HFN but not include the information of the fifth HFN, the terminal device determines the information of the fifth HFN according to the information of the fourth HFN. For example, the fifth HFN is equal to the fourth HFN + n, n being an integer. For example, n may be 1. For another example, if the network device sends the information of the fifth HFN but does not send the information of the fourth HFN, or the first information includes the information of the fifth HFN but does not include the information of the fourth HFN; and the terminal equipment determines the information of the fourth HFN according to the information of the fifth HFN. For example, the fourth HFN is equal to the fifth HFN-n, n being an integer. For example, n may be 1.
It should be noted that n may be protocol-specific, may also be indicated by the network device for the terminal device, or may be preconfigured, and the present application is not limited.
Possible implementationNow, the network device may transmit one of information of the sixth SN and information of the seventh SN. Or, the first information sent by the network device may include one of information of the sixth SN and information of the seventh SN. It is understood that the terminal device receives one of the information of the sixth SN and the information of the seventh SN from the network device. In this case, the terminal device determines the other of the information of the sixth SN and the information of the seventh SN from one of the information of the sixth SN and the information of the seventh SN. For example, if the network device sends the information of the sixth SN but does not send the information of the seventh SN, or the first information may include the information of the sixth SN but not include the information of the seventh SN, the terminal device determines the information of the seventh SN according to the information of the sixth SN. For example, the seventh SN is equal to the sixth SN + p, p being an integer. For example, p may be 2 (X-1) . Where X represents the number of bits corresponding to SN (or SN length). For another example, if the network device sends the information of the seventh SN but does not send the information of the sixth SN, or the first information includes the information of the seventh SN but does not include the information of the sixth SN; and the terminal equipment determines the information of the sixth SN according to the information of the seventh SN. For example, the sixth SN is equal to the seventh SN-p, p being an integer. For example, p may be 2 (X -1) . Where X represents the number of bits corresponding to SN (or SN length).
It should be noted that p may be a protocol-specific one, or may be indicated by a network device for a terminal device, or may be preconfigured, which is not limited in the present application.
Implementation mode A3:the information of the first COUNT and the information of the second COUNT may include: information of the first COUNT/information of the second COUNT and information of the eighth SN.
In this manner, in one possible implementation, HFN information corresponding to the first COUNT/the second COUNT may be shared.
In this manner, in another possible implementation, the terminal device may determine, according to the HFN information corresponding to the first COUNT (or the HFN information corresponding to the second COUNT), the HFN information corresponding to the second COUNT (or the HFN information corresponding to the first COUNT).
For example, the terminal device may determine information of an HFN corresponding to the second COUNT from information of an HFN corresponding to the first COUNT. For example, the HFN corresponding to the second COUNT is equal to HFN + v corresponding to the first COUNT, v being an integer. For example, v may be 1.
For example, the terminal device may determine the information of the HFN corresponding to the first COUNT according to the information of the HFN corresponding to the second COUNT. For example, the HFN corresponding to the first COUNT is equal to HFN-v corresponding to the second COUNT, v being an integer. For example, v may be 1.
It should be noted that v may be protocol-specific, may also be indicated by a network device for a terminal device, or may be preconfigured, and the present application is not limited.
For example, the terminal device may obtain the second COUNT/first COUNT information according to the HFN information and the eighth SN information corresponding to the first COUNT/second COUNT. By the method, the network device does not need to repeatedly indicate the HFN information corresponding to the second COUNT/the first COUNT, thereby saving signaling overhead.
As shown in fig. 4a, the COUNT may include an upper HFN and a lower SN. It can be understood that the terminal device obtains the second COUNT/first COUNT information according to the HFN information corresponding to the first COUNT/second COUNT and the eighth SN information. For example, the terminal device sets bits of HFNs corresponding to the first COUNT/the second COUNT to upper bits of the second COUNT/the first COUNT, and sets bits of the eighth SN to lower bits of the second COUNT/the first COUNT. For example, the terminal device determines HFN information corresponding to the second COUNT (or HFN information corresponding to the first COUNT) according to HFN information corresponding to the first COUNT (or HFN information corresponding to the second COUNT), sets bits of the determined HFN corresponding to the second COUNT (or HFN corresponding to the first COUNT) to be higher bits of the second COUNT/the first COUNT, and sets bits of the eighth SN to be lower bits of the second COUNT/the first COUNT.
Alternatively, the information of the first COUNT may include information of all bits or information of a part of bits of the first COUNT.
Alternatively, the information of the second COUNT may include information of all bits or information of a part of bits of the second COUNT.
Alternatively, the information of the eighth SN may include information of all bits or a part of bits of the eighth SN.
Implementation A4The information of the first COUNT and the information of the second COUNT may include: information of the sixth HFN, information of the ninth SN, and information of the tenth SN.
In this manner, the information of the sixth HFN may be shared, in one possible implementation.
In this manner, according to another possible implementation, the terminal device may determine, according to the information of the sixth HFN, HFN information corresponding to the second COUNT (or HFN information corresponding to the first COUNT).
For example, the terminal device determines the second COUNT (or information of the HFN corresponding to the first COUNT) according to the information of the sixth HFN. For example, the HFN corresponding to the second/first COUNT is equal to the sixth HFN + q or the sixth HFN-q, q being an integer. For example, q may be 1.
It should be noted that q may be protocol-specific, may also be indicated by a network device for a terminal device, or may be preconfigured, and the present application is not limited.
For example, the terminal device may obtain the information of the first COUNT and the information of the second COUNT by respectively combining the information of the ninth SN and the tenth SN according to the information of the sixth HFN. By the method, the network device does not need to repeat the information indicating the sixth HFN or the HFN information corresponding to the second/first COUNT, and the signaling overhead can be saved.
For example, the terminal device obtains the information of the first COUNT according to the information of the ninth SN and the information of the sixth HFN, specifically, the terminal device may set the bit of the sixth HFN as the high bit of the first COUNT, and set the bit of the ninth SN as the low bit of the first COUNT.
For example, the terminal device obtains the information of the second COUNT according to the information of the tenth SN and the information of the sixth HFN, and specifically, the terminal device may set the bit of the sixth HFN as the high bit of the second COUNT, and set the bit of the tenth SN as the low bit of the second COUNT.
For example, the terminal device obtains the information of the first COUNT according to the information of the ninth SN and the information of the sixth HFN, and specifically may be: and the terminal equipment determines the information of the HFN corresponding to the first COUNT according to the information of the sixth HFN, sets the determined bit of the HFN corresponding to the first COUNT as the high bit of the first COUNT, and sets the bit of the ninth SN as the low bit of the first COUNT.
For example, the terminal device obtains the information of the second COUNT according to the information of the tenth SN and the information of the sixth HFN, and specifically may be: and the terminal equipment determines the information of the HFN corresponding to the second COUNT according to the information of the sixth HFN, sets the determined bit of the HFN corresponding to the second COUNT as the high bit of the second COUNT, and sets the bit of the tenth SN as the low bit of the second COUNT. Alternatively, the information of the sixth HFN may include information of all bits or a part of bits of the sixth HFN.
Alternatively, the information of the ninth SN may include information of all bits or a part of bits of the ninth SN.
Alternatively, the information of the tenth SN may include information of all bits or a part of bits of the tenth SN.
For the information involved in the implementations A1 to A4, the specific indication manner may be an explicit indication or an implicit indication. It is to be understood that if an explicit indication is employed, the network device may indicate according to an explicit bit (or field), and accordingly, the terminal device may determine corresponding information according to the explicit bit (or field); if implicit indication is employed, the network device can implicitly indicate from existing bits (or fields) or other information without introducing additional bits (or fields) to indicate. For example, for the information of the first HFN, if explicitly indicated, the network device may indicate the information of the first HFN by an explicit bit (or field), where the information of the first HFN includes a value of the first HFN or an index of the first HFN; if implicitly indicated, since the COUNT is composed of the HFN and the SN, the network device may implicitly indicate the first HFN information according to the COUNT information, and accordingly, the terminal device may determine the first HFN information according to the COUNT information.
It can be understood that, if the information of the first HFN includes the index of the first HFN, the terminal device may determine, according to a corresponding relationship among the index, the index of the HFN, and the HFN value, the HFN value corresponding to the index of the first HFN.
In addition, the specific indication mode may be direct indication or indirect indication with respect to the information related to the first information. It can be understood that if the indication is direct indication, the terminal device can directly determine corresponding information according to the indication information; if the indirect indication is adopted, the terminal equipment indirectly determines corresponding information according to the indication information and the auxiliary parameters. For example, for the information of the first SN, if direct indication is adopted, the terminal device may directly determine the first SN according to the information of the first SN; if the indirect indication manner is adopted, the terminal device may indirectly determine the first SN according to the information of the first SN and the parameter r, and exemplarily, the terminal device determines that the first SN is (SN + r corresponding to the information of the first SN) or (SN-r corresponding to the information of the first SN). For another example, for the information of the first HFN, if the direct indication is adopted, the terminal device may directly determine the first HFN according to the information of the first HFN; if the indirect indication manner is adopted, the terminal device may indirectly determine the first HFN according to the information of the first HFN and the parameter s, for example, the terminal device determines that the first HFN is (HFN + s corresponding to the information of the first HFN) or (HFN-s corresponding to the information of the first HFN). The parameter r and/or s may be obtained by the terminal device itself or obtained from the network device, where if the terminal device obtains the parameter r and/or s by using a Subscriber Identity Module (SIM) card preset by the terminal device, or by using a protocol preset, or the like; by adopting the method, communication resources or signaling overhead between the terminal equipment and the network equipment can be saved. If the terminal device obtains from the network device, the terminal device may obtain the information through a dedicated signaling, broadcast information, multicast information, and system information, which is not limited in the present application. Specifically, the dedicated signaling may be a Radio Resource Control (RRC) message, a Media Access Control (MAC) Control Element (CE), a Downlink Control Information (DCI), or other messages, which is not limited in the present invention.
In a possible implementation manner, the first information is carried in a radio resource control RRC message, or a broadcast message, or a radio bearer configuration (or a first radio bearer configuration) corresponding to the first PDCP PDU, or a PDCP control PDU, or a configuration corresponding to the first service. The first service comprises a broadcast service and/or a multicast service.
In a possible implementation manner, the method further includes: before S501, the terminal device sends a request message to the network device, where the request message is used to request first information; accordingly, the network device receives the request message sent by the terminal device.
Optionally, the request message may also be used to indicate that the terminal device is interested in the first service, or to indicate that the terminal device is receiving the first service, or to indicate that the terminal device is no longer interested in the first service, or to indicate that the terminal device is no longer receiving the first service. It should be noted that the request message may be implicitly used to request the first information, i.e. the role of the request message is not limited, nor is the name of the request message limited.
Wherein the first information is associated with the first PDCP entity and/or the first radio bearer.
The first PDCP entity and/or the first radio bearer is associated with the first traffic. The first service comprises a broadcast and/or multicast service.
Optionally, the request message is carried in a radio resource control RRC message, or a medium access control element MAC CE, or a message in a random access procedure.
Optionally, the message in the random access procedure includes: a first message of the random access procedure (e.g., msg1 or MsgA), or a third message of the random access procedure (e.g., msg 3).
Optionally, the network device may count a first number, the first number comprising: the number of request messages received by the network device; or the number of terminal devices requesting the first information; if the first preset condition is met, the network equipment sends first information in a broadcast and/or multicast mode; if the first preset condition is not met, the network device sends the first information in a unicast mode, wherein the first preset condition may be: the first number is greater than or equal to a preset number.
Therefore, the terminal device can send a request message to the network device to inform the network device of the requirement of the network device on the first information, and correspondingly, the network device can send the first information according to the request message sent by the terminal device, so that the terminal device can obtain the first information more flexibly; in addition, the network equipment can adopt a unicast mode to send the first information when the number of terminal equipment requesting to acquire the first information is small, so that unnecessary information receiving of the terminal equipment can be avoided; when a plurality of terminal devices requesting the first information exist, the first information is sent in a broadcast and/or multicast mode, so that resource waste caused by excessive unicast sending of the first information can be avoided.
S502, the terminal equipment receives a first PDCP PDU from the network equipment, wherein the first PDCP PDU comprises a second SN; accordingly, the network device transmits the first PDCP PDU to the terminal device.
Optionally, data corresponding to the first PDCP PDU may be scrambled by the first RNTI or the second RNTI, where the data may be a Transport Block (TB) or a MAC PDU.
It should be noted that the data corresponding to the first PDCP PDU may include multiple data, and the multiple data may be scrambled by different RNTIs. For example, some data is scrambled by the first RNTI and some data is scrambled by the second RNTI.
The first RNTI and/or the second RNTI is associated with a broadcast and/or multicast service.
The first RNTI may be used for unicast and may be used for any one or any combination of the following: for scheduling dynamic resources, for retransmission of dynamic resources, for activating configuration resources, for reactivating configuration resources, for deactivating configuration resources, for scheduling retransmission of configuration resources, for scrambling (e.g. for scrambling PDCCH or PDSCH).
For example, the first RNTI may be a Cell radio network temporary identifier (C-RNTI), a configured scheduling RNTI (CS-RNTI).
The second RNTI is for broadcast and/or multicast and may be for any one or any number of: for scheduling dynamic resources, for retransmission of dynamic resources, for activating configuration resources, for reactivating configuration resources, for deactivating configuration resources, for scheduling retransmission of configuration resources, for scrambling (e.g., for scrambling PDCCH or PDSCH).
For example, the second RNTI may be a group RNTI (G-RNTI).
Optionally, the first PDCP PDU is associated with a first channel (or a first logical channel).
The first channel (or first logical channel) may include a channel associated with any one or more of the first traffic, the first PDCP entity, the first radio bearer. For example, the first Channel may comprise a multicast broadcast Traffic Channel and/or a Dedicated Traffic Channel (DTCH).
For example, the channel associated with the first service may include: a channel associated with unicast transmission of the first service and/or a channel associated with multicast transmission of the first service.
It should be noted that, the multicast broadcast traffic channel may be replaced with: channels for broadcast and/or multicast, or logical channels for broadcast and/or multicast services (e.g. channels for transmitting services)
In one possible implementation, the first channel is a multicast/multicast broadcast traffic logical channel (MTCH),
optionally, the first PDCP PDU is associated with a first RLC entity.
The first RLC entity may include an RLC entity associated with the first service.
In one possible implementation, the first RLC entity is associated with a multicast broadcast traffic channel corresponding to a first service (or first radio bearer).
In one possible implementation, the first RLC entity is associated with a dedicated traffic channel corresponding to a first service (or first radio bearer).
For example, the network device may transmit a first PDCP PDU over a first logical channel, and accordingly, the terminal device may receive the first PDCP PDU over the first logical channel. Here, the first logical channel is associated with a broadcast and/or multicast service.
It should be noted that S502 may be executed before S501, or S501 and S502 may also be executed simultaneously, and the sequence of S501 and S502 is not limited in this embodiment.
S503, the terminal equipment determines the HFN of the first PDCP PDU according to the first information and the second SN.
As described in S501, the first information may include a plurality of possible information for determining the HFN of the first PDCP PDU, which is described in connection with examples a1 to a3 below.
Example a1: the first information includes information of the first HFN and information of the first SN.
The determining, by the terminal device, the HFN of the first PDCP PDU according to the first information and the second SN may include: and the terminal equipment determines the HFN of the first PDCP PDU according to the first information, the second SN and the first parameter.
It is understood that the first SN may be determined directly or indirectly by the terminal device through information of the first SN, and for the first SN, reference may be made to the description of the first SN in S501, which is not described herein again.
It is understood that the first HFN may be determined directly or indirectly by the terminal device through information of the first HFN.
For example a1, the terminal device may determine the HFN of the first PDCP PDU in a variety of ways, e.g., the terminal device may determine the HFN of the first PDCP PDU based on the second SN, the first SN, and the first parameter.
The first parameter may be obtained by the terminal device itself or obtained from the network device, for a specific manner, refer to the obtaining manner of parameter a in S501, which is not described herein again.
Alternatively, the first parameter may be a window size (or 2) (X-1) ) Or window size (or 2) (X-1) ) And performing mathematical operation on the pre-acquired parameter, where the pre-acquired parameter may be acquired by the terminal device itself or acquired from the network device, and the specific manner refers to the manner of acquiring the parameter r in S501, which is not described herein again. WhereinAnd X represents the number of bits corresponding to SN (or SN length). The mathematical operations include one or more of: addition, subtraction, multiplication, division, power, evolution, logarithm, etc., which are not limited in this respect.
Illustratively, the pre-obtained parameter may be t1, t2 or t3, and accordingly, the first parameter may be (window size-t 1), or (window size + t 1), or (window size x t 2), or (window size x 2) t3 ) Or (window size 2) (-t3) ). For example, the window size may be 2 (X-1) . Alternatively, the number of bits of the SN may be 12 bits, or 16 bits, or 18 bits, which is not limited by the present invention.
The following embodiments a1 to a3 are explained:
mode a1: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than the difference between the first SN and the first parameter;
if the second SN is greater than or equal to the sum of the first SN and the first parameter, the HFN of the first PDCP PDU is equal to the first HFN minus 1;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and the first parameter and the second SN is less than a sum of the first SN and the first parameter.
It should be noted that "the second SN is equal to the sum of the first SN and the first parameter, and the HFN of the first PDCP PDU is equal to the first HFN minus 1" is only one possible example.
It should be noted that "the second SN is equal to the difference between the first SN and the first parameter, and the HFN of the first PDCP PDU is equal to the first HFN" is only one possible example.
It should be noted that, for the case where the second SN is equal to the difference between the first SN and the first parameter or the second SN is equal to the sum of the first SN and the first parameter in the present application, the HFN of the first PDCP PDU may be equal to one of the following: the first HFN, the first HFN plus 1, and the first HFN minus 1, which is not limited in the present invention.
For example, the SN has a length of 12 bits, i.e., the SN has a value range of 0 to 4095, and accordingly, one round of SN space corresponding to one HFN is 0 to 4095. If the value of the first parameter is 2048, the first HFN carried by the network device through the first information is equal to 11, and the first SN is equal to 2500, the sum of the first SN and the first parameter is 4548, and the difference between the first SN and the first parameter is 452. As shown in the method a1, if the second SN is equal to 800,800 is greater than the difference between the first SN and the first parameter and is less than the sum of the first SN and the first parameter, i.e., 800 is greater than 452 and 800 is less than 4548, the HFN of the first PDCP PDU is equal to the first HFN, i.e., the HFN of the first PDCP PDU is equal to 11; if the second SN is equal to 200,200 is less than the difference between the first SN and the first parameter, i.e. 200 is less than 452, the HFN of the first PDCP PDU is equal to the first HFN plus 1, i.e. the HFN of the first PDCP PDU is equal to 12.
Mode a2: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than the difference between the first SN and the first parameter;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and the first parameter.
Mode a3: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
if the second SN is greater than or equal to the sum of the first SN and the first parameter, the HFN of the first PDCP PDU is equal to the first HFN minus 1;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is less than a sum of the first SN and the first parameter.
Any one or more of the modes a1 to a3 may be combined, and the present application is not limited thereto.
Example a2: the first information includes information of the first HFN and information of the SN range.
For example a2, there are various ways for the terminal device to determine the HFN of the first PDCP PDU, and the following description will take the way b1 and the way b2 as examples.
Mode b1: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is within the range of SNs;
if the second SN is less than the minimum value in the SN range, the HFN of the first PDCP PDU is equal to the first HFN plus 1;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than a maximum value within the range of SNs.
The minimum value within the SN range may be understood or replaced by a third SN.
The maximum value within the SN range may be understood or replaced by a fourth SN.
The second SN can be understood or replaced within the SN range by: the second SN is greater than or equal to the third SN, and the second SN is less than or equal to the fourth SN.
It should be noted that "the second SN is equal to the minimum value in the SN range, and the HFN of the first PDCP PDU is equal to the first HFN" is only one possible example.
It should be noted that "the second SN is equal to the maximum value in the SN range, and the HFN of the first PDCP PDU is equal to the first HFN" is only one possible example.
It should be noted that, for the case where the second SN is equal to the minimum value in the SN range or the second SN is equal to the maximum value in the SN range in the present application, the HFN of the first PDCP PDU may be equal to one of the following: the first HFN, the first HFN plus 1, and the first HFN minus 1, which is not limited in the present invention.
For example, the SN has a length of 12 bits, i.e. the SN has a value ranging from 0 to 4095, and accordingly, one HFN corresponds to one round of SN space ranging from 0 to 4095, and the SN ranges from 0 to 1700. As shown in the method b1, if the second SN is equal to 2000,2000 is greater than the maximum value in the SN range, i.e., 2000 is greater than 1700, the HFN of the first PDCP PDU is equal to the first HFN minus 1, i.e., the HFN of the first PDCP PDU is equal to 10; if the second SN is equal to 800,800 is greater than the minimum value in the SN range and less than the maximum value in the SN range, i.e., 800 is greater than 300 and 800 is less than 1700, the HFN of the first PDCP PDU is equal to the first HFN, i.e., the HFN of the first PDCP PDU is equal to 11.
Mode b2: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
if the value corresponding to the received SN range starts from 0, and if the second SN is in the SN range, the HFN of the first PDCP PDU is equal to the first HFN;
if the value corresponding to the received SN range starts from 0 and if the second SN is larger than the maximum value in the SN range, the HFN of the first PDCP PDU is equal to the first HFN minus 1;
if the received SN range corresponds to a value with the maximum value of SN (for example, 2) X -1) ending and if the second SN is within the SN range, the HFN of the first PDCP PDU equals the first HFN;
if the received SN range corresponds to a value with the maximum value of SN (for example, 2) X -1) end and the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than a minimum value within the SN range.
"the value corresponding to the SN range starts from 0" can be understood/replaced by: the minimum value (or third SN) in the SN range is 0.
"the value corresponding to the SN range is the maximum value of SN (e.g. 2) X -1) end "it is possible to understand or replace: the maximum value (or fourth SN) in the SN range is 2 X -1。
For example, one possible implementation, a process for a terminal device to determine an HFN of a first PDCP PDU includes:
step 1, if the value corresponding to the received SN range starts from 0, executing step 2, and if not, executing step 3;
step 2, if the second SN is in the range of the SNs, the HFN of the first PDCP PDU is equal to the first HFN, otherwise, the HFN of the first PDCP PDU is equal to the first HFN minus 1;
step 3, if the value corresponding to the received SN range is the maximum value of SN (for example, 2) X -1) end and if the second SN is within the above SN range, the HFN of the first PDCP PDU equals the first HFN, otherwise the HFN of the first PDCP PDU equals the first HFN plus 1.
For example, the SN has a length of 12 bits, i.e., the SN has a value range of 0 to 4095, and accordingly, one round of SN space corresponding to one HFN is 0 to 4095. The first parameter takes the value 2048. The received SN ranges from 0 to 2000, and the first HFN equals 11. If the received second SN is 1000, it can be known from the above implementation method that the second SN is within the SN range, that is, 1000 is within the range of 0 to 2000, and at this time, the HFN of the first PDCP PDU is equal to the first HFN, that is, the HFN of the first PDCP PDU is equal to 11; if the received second SN is 3000, the second SN is not in the SN range, and the HFN of the first PDCP PDU is equal to the first HFN minus 1, i.e., the HFN of the first PDCP PDU is equal to 10.
For another example, the SN length is 12 bits, i.e. the value range of SN is 0 to 4095, and correspondingly, one round of SN space corresponding to one HFN is 0 to 4095. The first parameter takes the value 2048. The received SN ranges from 2500 to 4095 and the first HFN equals 11. If the received second SN is 3000, the implementation method may find that the second SN is within the SN range, that is, 3000 is within the range of 2500 to 4095, and at this time, the HFN of the first PDCP PDU is equal to the first HFN, that is, the HFN of the first PDCP PDU is equal to 11; if the received second SN is 2000, when the second SN is not in the SN range, i.e., 2000 is not in the range of 2500-4095, when the HFN of the first PDCP PDU is equal to the first HFN plus 1, i.e., the HFN of the first PDCP PDU is equal to 12.
Example a3: the first information includes information of a COUNT range.
For example a3, there are various ways for the terminal device to determine the HFN of the first PDCP PDU, and the following description will take the way c1 and the way c2 as examples.
Mode c1: the terminal equipment determines the HFN of the first PDCP PDU, and any item of the following items is included:
if the second SN is larger than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range;
if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
Optionally, the SN corresponding to the maximum value in the COUNT range is less than or equal to the SN corresponding to the minimum value in the COUNT range.
Optionally, the HFN corresponding to the minimum value in the COUNT range is different from the HFN corresponding to the maximum value in the COUNT range. For example, the HFN corresponding to the minimum value in the COUNT range is equal to HFN-1 corresponding to the maximum value in the COUNT range, or the HFN corresponding to the maximum value in the COUNT range is equal to HFN +1 corresponding to the minimum value in the COUNT range.
Optionally, the difference between the maximum value in the COUNT range and the minimum value in the COUNT range is less than or equal to 2 X Or (2) X -1). The difference between the maximum value in the COUNT range and the minimum value in the COUNT range may be the maximum value in the COUNT range minus the minimum value in the COUNT range.
Alternatively, the lowest value in the COUNT range may be understood or replaced with the first COUNT.
Alternatively, the maximum value in the COUNT range may be understood or replaced by the second COUNT.
Alternatively, the SN corresponding to the minimum value in the COUNT range may be understood or replaced by any one of the fifth SN, the sixth SN, the SN corresponding to the first COUNT, the eighth SN, the ninth SN, and the ninth SN.
Alternatively, the SN corresponding to the maximum value in the COUNT range may be understood or replaced by any one of the fifth SN, the seventh SN, the eighth SN, the SN corresponding to the second COUNT, the tenth SN, and the tenth SN.
Alternatively, the HFN corresponding to the minimum value in the COUNT range may be understood or replaced by any one of the second HFN, the fourth HFN, the HFN corresponding to the first COUNT, the HFN corresponding to the second COUNT (or, the HFN-v corresponding to the second COUNT), the sixth HFN, and the sixth HFN (or, the sixth HFN-q).
Alternatively, the HFN corresponding to the maximum value in the COUNT range may be understood or replaced by any one of the third HFN, the fifth HFN, the HFN corresponding to the first COUNT (or, the HFN + v corresponding to the first COUNT), the HFN corresponding to the second COUNT, the sixth HFN (or, the sixth HFN + q), and the sixth HFN.
For example, with reference to the description in section S501, table 1 gives 6 possible values for the SN corresponding to the minimum value in the COUNT range, the SN corresponding to the maximum value in the COUNT range, the HFN corresponding to the minimum value in the COUNT range, and the HFN corresponding to the maximum value in the COUNT range.
TABLE 1
Figure RE-GDA0003259029160000261
Figure RE-GDA0003259029160000271
Mode c2: the terminal device determines the HFN of the first PDCP PDU, including any one or more of:
meeting a first condition, if the second SN is larger than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range;
the first condition is satisfied, and if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
Wherein the first condition comprises any one or more of:
the information of the first COUNT and the information of the second COUNT may include: the information of the second HFN and the information of the third HFN and the information of the fifth SN, the information of the fourth HFN and the information of the fifth HFN and the information of the sixth SN and the information of the seventh SN, and the information of the first COUNT and the information of the second COUNT may include: any one of information of the first COUNT/information of the second COUNT and information of the eighth SN, information of the sixth HFN and information of the ninth SN and information of the tenth SN;
the SN corresponding to the maximum value in the COUNT range is less than or equal to the SN corresponding to the minimum value in the COUNT range;
the HFN corresponding to the minimum value in the COUNT range is different from the HFN corresponding to the maximum value in the COUNT range;
the difference between the maximum value in the COUNT range and the minimum value in the COUNT range is less than or equal to 2 SN number of bits Or less than or equal to (2) SN number of bits -1)。
S504, the end device sets a first state variable.
Illustratively, the terminal device may set the first state variable according to one of the following ways:
mode d1: setting the first state variable as the minimum value or the maximum value or the average value in the received COUNT of the first PDCP PDU and the COUNT corresponding to the first information;
mode d2: setting a first state variable as a minimum value or a maximum value or an average value in the COUNTs of the received N PDCP PDUs, wherein N is a positive integer;
mode d3: setting a first state variable as a minimum value or a maximum value or an average value in the COUNT of the received N PDCP PDUs and the COUNT corresponding to the first information, wherein N is a positive integer or a non-negative integer;
mode d4: setting a first state variable as a minimum value or a maximum value or an average value in the COUNTs of the PDCP PDUs received within a first time period T;
mode d5: and setting the first state variable as the minimum value or the maximum value or the average value in the COUNT of the PDCP PDU received in the first time period T and the COUNT corresponding to the first information.
Optionally, the first state variable may be a state variable used in a PDCP data transmission procedure;
optionally, the first state variable may include a state variable maintained by the terminal device (or, a PDCP entity of the terminal device).
For example, the first state variables may include RX _ NEXT and/or RX _ DELIV.
For example, RX _ NEXT may indicate the COUNT of the NEXT expected received PDCP PDU.
For example, RX _ DELIV may indicate the COUNT of the next PDCP PDU that is not delivered to the upper layer, waiting. For example, RX _ DELIV may be understood as the lower bound of the reordering window.
For example, in the present application, the upper layer may include any one or more of an SDAP layer, an RRC layer, a NAS layer, and an APP layer.
Any plurality of the above-described embodiments d1 to d5 may be combined with each other. For example, the first state variable is set to a minimum value or a maximum value or an average value among COUNTs of N PDCP PDUs received within the first time period T, where N is a positive integer. For example, the first state variable is set to a minimum value or a maximum value or an average value among the COUNT of N PDCP PDUs received within the first time period T and the COUNT corresponding to the first information, where N is a positive integer or a non-negative integer.
Illustratively, any one or more of the first PDCP PDU, the received N PDCP PDUs, the PDCP PDUs received within the first time period T, the N PDCP PDUs received within the first time period T, the first information is associated with the first PDCP entity or with the first radio bearer with the first service.
Illustratively, the first PDCP entity and/or the first radio bearer is associated with first traffic, the first traffic including broadcast traffic and/or multicast traffic.
Illustratively, the first PDCP PDU includes the first PDCP PDU received by the terminal device.
In one possible implementation, for a first PDCP PDU (or, N PDCP PDUs received, or, PDCP PDUs received within a first time period T), the terminal device may determine the HFN of the PDCP PDU according to the method described herein; based on the method, HFNs of the PDCP PDU are aligned between the terminal equipment and the network equipment; for a PDCP PDU received later, the terminal device may determine the HFN of the PDCP PDU based on methods in the prior art. It can be understood that the method for determining the HFN of the PDCP PDU, which is described in the present application, is not limited by the present application.
It should be noted that S504 may be implemented as a single embodiment, or may be implemented as an optional step in combination with any one or more of S501 to S503, which is not limited in the present invention.
It should be noted that, for the HFN of the PDCP PDU related in S504, the terminal device may determine the HFN of the PDCP PDU according to the method described in this application, the terminal device may also determine the HFN of the PDCP PDU based on a method in the prior art, and the terminal device may also determine the HFN of the PDCP PDU based on other methods, which is not limited herein. The HFN of the different PDCP PDUs involved in S504 may also be determined by different methods, which are not limited herein.
By adopting the method, the terminal equipment receives first information from the network equipment, and determines the HFN corresponding to the first PDCP PDU according to the first information and second SN information carried in the received PDCP PDU; so that the terminal device and the network device can align the HFN or initial value of the HFN of the PDCP PDUs. The normal receiving of data is ensured, the problem of packet loss or out-of-order delivery caused by the misalignment of HFNs is avoided, and the reliability is improved. In addition, the method can also be beneficial to decryption and integrity verification of the terminal equipment side, so that the problem of packet loss caused by unsuccessful integrity verification is avoided, and the reliability is improved. In addition, compared with the scheme that the terminal device sets RX _ DELIV as the COUNT provided by the network device, the method can avoid the problems of packet loss and/or window jam at the receiving side (for example, the window cannot slide due to the fact that part of data cannot be successfully received, so that data cannot be delivered to an upper layer, and communication delay is increased) caused by unreasonable setting of the COUNT, thereby improving the reliability of data reception, improving the communication efficiency, and reducing the communication delay.
Fig. 6 is a schematic flowchart of a communication method according to an embodiment of the present application, and as shown in fig. 6, the method includes:
s600, the network equipment sends the PDCP PDU to the terminal equipment, and correspondingly, the terminal equipment receives the PDCP PDU from the network equipment.
For example, the PDCP PDUs may include/be replaced/understood as: the first PDCP PDU.
In this embodiment, the PDCP PDU (or the first PDCP PDU) may include (or be replaced with): a PDU header, or a PDCP PDU (or first PDCP PDU) header, or a PDU header of a PDCP PDU (or first PDCP PDU), or a header of a PDCP PDU (or first PDCP PDU).
It should be noted that S600 is optional.
It should be noted that S600 may be executed before S601, or S600 and S601 may also be executed simultaneously, or S600 may also be executed after S601, and the order of S600 and S601 is not limited in this embodiment of the application.
S601, the network device sends first indication information to the terminal device, and accordingly the terminal device receives the first indication information from the network device.
The first indication information is used for indicating whether HFN exists in PDCP PDU (or PDU header) or whether COUNT exists in PDCP PDU (or PDU header); or, the first indication information is used to indicate a format type of PDCP PDU (or PDU header), the format type includes a first type and/or a second type, the first type corresponding PDCP PDU (or PDU header) includes information of HFN or information of COUNT, and the second type corresponding PDCP PDU (or PDU header) does not include information of HFN or information of COUNT; or, the first indication information is used to indicate whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU (or, PDU header); or, the first indication information is used to indicate whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU (or, PDU header); or, the first indication information is used for indicating whether only SN information is included in the PDCP PDU (or, PDU header); or the first indication information is used to indicate whether the information of the COUNT or the information of the HFN is not included in the PDCP PDU (or, the PDU header).
It is to be understood that, in this embodiment, the description and the location of the occurrence of the PDCP PDU may be replaced by a "PDU header", for example, the first indication information is used to indicate whether there is an HFN in the PDCP header or information used to indicate whether there is a COUNT in the PDCP header, which is not limited in this application.
Wherein the indication field may include at least one of the following information (or, fields): SN, reserved bit R, PDU type, data, integrity Message Authentication Code MAC-I (Message Authentication Code for Integrity).
Alternatively, the HFN field may include the HFN value or an index of the HFN.
Optionally, the HFN field may be used to indicate information of HFN of the PDCP PDU.
For example, the number of bits (or the number of bits occupied) of the HFN field may be 20 bits, or 14 bits, or 16 bits, and as mentioned above, the HFN field is specifically the number of bits occupied in the PDCP PDU/PDU header and the position of the HFN field in the PDCP PDU (or PDU header), which is not limited in this application.
Optionally, the HFN field may include information of all bits or a part of bits of HFN of the HFN/PDCP PDU.
Optionally, the COUNT field includes a COUNT value or an index of the COUNT.
Optionally, the COUNT field may be used for information indicating the COUNT of the PDCP PDU.
For example, the number of bits (or the number of bits occupied) in the COUNT field may be 32 bits, and as mentioned above, the number of bits occupied by the COUNT field in the PDCP PDU (or PDU header) and the position of the COUNT field in the PDCP PDU (or PDU header) are only examples, which is not limited in this application.
Alternatively, the COUNT field may include information of all bits or information of a part of bits of the COUNT (or, the COUNT of the PDCP PDU).
Optionally, the SN field includes an SN value or an index of the SN.
Optionally, the SN field may be used for information indicating the SN of the PDCP PDU.
For example, the number of bits (or the number of bits occupied) of the SN field may be 12 bits, or 18 bits, or 16 bits, and as mentioned above, the number of bits occupied by the SN field in the PDCP PDU (or PDU header) and the position of the SN field in the PDCP PDU (or PDU header) are only examples, and the application is not limited thereto.
Alternatively, the SN field may include information of all bits or information of partial bits of the SN (or the SN of the PDCP PDU).
Optionally, the R field is reserved bits.
Optionally, the PDU type field may be used to indicate whether the PDCP PDU is a PDCP data PDU or a PDCP control PDU. For example, the PDU type may be represented by D/C.
For example, the number of bits (or the number of bits occupied) of the PDCP type field may be 1 bit, and as mentioned above, the number of bits occupied by the PDCP type field in the PDCP PDU (or PDU header) and the position of the PDCP type field in the PDCP PDU (or PDU header) are only examples, which is not limited in this application.
Optionally, the data field may include any one or more of: PDCP Service Data Unit (SDU), compressed PDCP SDU, uncompressed PDCP SDU. For example, data may be represented by Data. For example, the Data field may be represented by a Data field.
For example, any one or more of PDCP SDUs, compressed PDCP SDUs, uncompressed PDCP SDUs may include: user plane data, and/or control plane data.
For example, the number of bits of the data field (or the number of occupied bits) may be variable. For example, the number of bits of the data field (or the number of occupied bits) may be X bytes, or 8 by Y bits, where X and/or Y may be positive integers.
Alternatively, the MAC-I domain may be used for integrity protection.
For example, the number of bits (or the occupied number of bits) in the MAC-I domain may be 32 bits, which is only an example as described above, the number of bits specifically occupied by the MAC-I domain in the PDCP PDU and the position of the MAC-I domain in the PDCP PDU, and the application is not limited thereto.
Optionally, the first indication Information may be carried in a variety of possible messages, such as a radio resource Control RRC message, or a PDCP Control PDU, or a PDCP PDU (or a first PDCP PDU), or a radio bearer configuration corresponding to the PDCP PDU (or a radio bearer configuration corresponding to the first PDCP PDU, or a first radio bearer configuration), or a configuration corresponding to the first service, or Downlink Control Information (DCI), or a Media Access Control (MAC) Control Element (CE), or other possible messages, which is not limited in particular.
The first service comprises a broadcast service and/or a multicast service.
It is understood that the first indication information is carried in the PDCP PDU (or the first PDCP PDU), and the terminal device receives the PDCP PDU (or the first PDCP PDU) and also obtains the first indication information. In this possible case, S600 and S601 may be understood as being performed simultaneously. S600 and S601 may understand or be replaced with: the network equipment sends PDCP PDU to the terminal equipment, and correspondingly, the terminal equipment receives the PDCP PDU from the network equipment, wherein the PDCP PDU contains the first indication information.
Further, the first indication information may be implemented in various ways, and as a possible implementation manner, the first indication information may include 1 or more bits, and further indicate content information carried by the PDCP PDU through different values of the bits. For example, if the first indication information indicates whether HFN information exists in the PDCP PDU, the first indication information may include 1 bit, and when the bit is set to "1", the HFN information exists in the indicated PDCP PDU, and when the bit is set to "0", the HFN information does not exist in the indicated PDCP PDU. For another example, if the first indication information indicates a format type of the PDCP PDU, the first indication information may include 1 bit, and when the bit takes a value of "1", the indicated format type of the PDCP PDU is the first type, and when the bit takes a value of "0", the indicated format type of the PDCP PDU is the second type. In this example, the first indication information may also include 2 bits, when the bit position is "00", the indicated PDCP PDU format type is the first type, when the bit position is "01", the indicated PDCP PDU format type is the second type, when the bit position is "10", the indicated PDCP PDU format type is the third type, and when the bit position is "11", the indicated PDCP PDU format type is the existing PDCP PDU type or the reserved type. It can be understood that, as mentioned above, the number of bits used specifically and the meanings corresponding to different values are merely examples, and the embodiments of the present application may not be limited.
As another possible implementation manner, the first indication information may include 1 or more fields, and then indicate content information carried by the PDCP PDU through the presence or absence of the 1 or more fields. For example, if the first indication information indicates whether HFN information exists in the PDCP PDU, the first indication information may include 1 field, and if the field exists in the first indication information, the information indicating that HFN information exists in the PDCP PDU; if this field does not exist, it indicates that no HFN information exists in the PDCP PDU. It is understood that, as mentioned above, the number of the fields specifically used and the corresponding meaning of the existence of different fields are only examples, and the embodiment of the present application may not be limited.
Optionally, the PDCP PDU (or the first PDCP PDU) may include: PDCP data PDUs and/or PDCP control PDUs.
For example, PDCP data PDUs can be used to transmit any one or more of the following: PDU header, user plane data, control plane data, MAC-I.
For example, PDCP control PDUs can be used to transmit any one or more of the following: PDU Header, PDCP status report, robust Header Compression (ROHC) feedback, ethernet Header Compression (EHC) feedback.
Alternatively, the first indication information may be located anywhere in the PDCP PDU (or first PDCP PDU)/PDU header, in other words, the first indication information occupies the Z-th bit in the PDCP PDU (or first PDCP PDU)/PDU header, or the first indication information may occupy 1 bit or more from the Z-th bit of the PDCP PDU (or first PDCP PDU)/PDU header, where Z is a positive integer greater than or equal to 1.
It should be noted that the PDCP PDU may be a byte aligned (i.e., multiple of 8 bits) bit string. As shown in fig. 7a, the bit string is represented by a table, where the most significant bit is the leftmost bit of the first row of the table and the least significant bit is the rightmost bit of the last row of the table. The most significant bit may be referred to as a first bit, and from the most significant bit, the first bit, the second bit, the third bit, and so on are sequentially arranged from left to right and from top to bottom.
In one possible implementation, the first indication information is located in the 1 st bit (or most significant bit) of the PDCP PDU (or PDU header), and the first indication information is used to indicate whether HFN information is present in the PDCP PDU (or PDU header). As shown in fig. 7a to 7b, the value of the first indication information (e.g., indicated by H) may be set to indicate whether HFN information exists in the PDCP PDU (or PDU header), where the HFN information occupies 14 bits, and the SN information occupies 18 bits, and the HFN information may precede the SN information. It is understood that the information of the HFN may also follow the information of the SN.
For example, as shown in fig. 7a, the PDCP PDU includes the following information, where each 8 bits is 1 byte:
the first indication information: 1 bit;
reserving a bit: namely reserved bits, including 7 bits;
an HFN domain: 14 bits;
SN field: 18 bits;
a data field.
For another example, as shown in FIG. 7b, the PDCP PDU includes the following information, wherein each 8 bits is 1 byte:
the first indication information: 1 bit;
reserving a bit: namely reserved bits, comprising 5 bits;
SN field: 18 bits;
a data field.
In another possible implementation, the first indication information is located in the 2 nd bit of the PDCP PDU (or PDU header), and the first indication information is used to indicate whether HFN information exists in the PDCP PDU (or PDU header), where the PDCP PDU (or PDU header) includes a D/C field and a MAC-I field. As shown in fig. 7c to 7d, the value of the first indication information may be set to indicate whether HFN information exists in the PDCP PDU (or PDU header), where the HFN information occupies 14 bits, and the SN information occupies 18 bits, and the HFN information may precede the SN information. It is understood that the information of the HFN may also follow the information of the SN.
For example, as shown in fig. 7c, the PDCP PDU includes the following information, wherein each 8 bits is 1 byte:
PDU type field: 1 bit;
the first indication information: 1 bit;
reserving a bit: namely reserved bits, including 6 bits;
an HFN domain: 14 bits;
SN field: 18 bits;
a data field;
MAC-I domain: 32 bits.
For another example, as shown in fig. 7d, the PDCP PDU includes the following information, where each 8 bits is 1 byte:
PDU type field: 1 bit;
the first indication information: 1 bit;
reserving a bit: namely reserved bits, including 4 bits;
SN field: 18 bits;
a data field;
MAC-I domain: 32 bits.
It should be noted that the above are only examples, and in the present application, any one or more of the COUNT, HFN, SN, R, D/C, data, and MAC-I may be optionally included in the PDCP PDU, and are not limited to exist.
Optionally, the terminal device may receive a PDCP PDU corresponding to the third type from the network device, where the format of the PDCP PDU (or PDU header) corresponding to the third type may have multiple implementation manners, and the following description takes implementation manner a1 and implementation manner a2 as an example:
implementation mode a1: the PDCP PDU (or PDU header) does not include the first indication information, but includes one of the following: information of COUNT, or information of HFN and information of SN.
Optionally, the PDCP PDU (or PDU header) may include at least one of: reserved bits R, PDU type, data, MAC-I.
For implementation a1, for example, as shown in fig. 7e, the PDCP PDU (or PDU header) includes an HFN field, an SN field and a Data field, wherein the HFN field occupies 14 bits and the SN field occupies 18 bits.
Implementation mode a2: the first indication information is not included in the PDCP PDU (or PDU header), and the PDCP PDU (or PDU header) satisfies one of the following conditions: information including SN, information not including HFN or information of COUNT, information including SN and not including HFN or information of COUNT.
Optionally, the PDCP PDU (or PDU header) may include at least one of: reserved bits R, PDU type, data, MAC-I.
For implementation a2, for example, as shown in fig. 7f, the PDCP PDU includes information of a reserved bit R, SN and information of a Data field, where the reserved bit R occupies 6 bits and the SN field occupies 18 bits.
It can be understood that the above is only an example, and the number of bits corresponding to each field in the PDCP PDU corresponding to the third type may not be limited.
It should be noted that, if the network device always carries HFN information or COUNT information in the PDCP PDU (or PDU header), it may be ensured that HFN is aligned between the terminal device and the network device, but this has a large overhead for air interface resources, which wastes resources. First indication information may be added to the PDCP PDU/PDU header for the terminal device to determine whether HFN information or COUNT information is included in the PDCP PDU (or PDU header), or to determine the format of the PDCP PDU (or PDU header) for correctly decoding the PDCP PDU (or PDU header). In this case, the network device may carry information of HFN or information of COUNT in PDCP PDU (or PDU header) if needed, so that the network device and the terminal device may align HFN; in case it is not needed (e.g., the terminal device receiving the first service or corresponding to the first radio bearer is already aligned with the network device for HFN), the HFN information or the COUNT information may not be carried in the PDCP PDU (or PDU header). In this way, overhead of air interface resources can be saved.
The determination of when the network device carries the HFN information or the COUNT information in the PDCP PDU (or PDU header), and when the network device does not carry the HFN information or the COUNT information in the PDCP PDU (or PDU header) may be made by the network device based on certain parameters, or may depend on the implementation of the network device. Here, some parameters may include at least one of: feedback information (for example, ACK or NACK) of the terminal device, the number of terminal devices sending the feedback information, time for the network device to send the first indication information, and the number of PDCP PDUs carrying HFN information or COUNT information sent. Wherein the feedback information includes at least one of: hybrid automatic repeat request (HARQ) feedback, channel State Information (CSI), rank Indication (RI), RLC status report, PDCP status report.
For example, the network device determines that a new terminal device is interested in data corresponding to the first service or the first radio bearer, or the network device determines that a new terminal device is to receive data corresponding to the first service or the first radio bearer, and the network device may carry information of HFN or information of COUNT in PDCP PDU (or PDU header) sent to the terminal device. For example, the PDCP PDUs transmitted to the terminal device may include: the PDCP PDU sent to the terminal device by Point To Point (PTP) or the PDCP PDU sent to the terminal device by Point To Multipoint (PTM) is transmitted.
For example, the network device determines that it will start transmitting data corresponding to the first traffic or the first radio bearer, and the network device may carry information of HFN or information of COUNT in a PDCP PDU/PDU header sent to the terminal device(s). For example, PDCP PDUs transmitted to the terminal device(s) may include: PDCP PDUs transmitted to the terminal device(s) by PTP mode or PDCP PDUs transmitted to the terminal device(s) by PTM mode, respectively.
For example, the network device may determine, according to the feedback from the terminal device, that each terminal device receiving the data corresponding to the first service or the first radio bearer has received at least one PDCP PDU containing HFN information or COUNT information, so that the network device may determine that the PDCP PDU/PDU header does not carry HFN information or COUNT information.
For example, the network device may determine, according to the feedback of the terminal device, that the terminal device receiving the first service or the data corresponding to the first radio bearer has received at least one PDCP PDU containing HFN information or COUNT information, so that the network device may determine that the HFN information or COUNT information is not carried in the PDCP PDU (or PDU header).
For another example, the network device may determine that the subsequent PDCP PDU does not carry the HFN information or the COUNT information according to that the time of the sent PDCP PDU carrying the HFN information or the COUNT information is greater than a preset threshold, and specifically, the network device may determine that the network device does not carry the HFN information or the COUNT information in the PDCP PDU/PDU header.
For another example, the network device may determine that the subsequent PDCP PDU (or PDU header) does not carry the HFN information or the COUNT information according to that the number of the PDCP PDUs carrying the HFN information or the COUNT information is greater than a preset threshold, and specifically, the network device may determine that the subsequent PDCP PDU (or PDU header) does not carry the HFN information or the COUNT information.
For example, the number of PDCP PDUs carrying HFN information or COUNT information that are transmitted may include: the number of PDCP PDUs carrying HFN information or COUNT information which are continuously transmitted.
S602, the terminal equipment decodes the PDCP PDU according to the first indication information.
It should be noted that, as an optional step, in S602, after receiving the first indication information, the terminal device may determine or know a format of the PDCP PDU (or PDU header) (or a format type of the PDU header of the PDCP PDU, or a format type of the PDU header), in other words, the terminal device may know content (for example, whether the HFN is included) included in the PDCP PDU (or PDU header) according to the first indication information, and then decode the PDCP PDU (or PDU header) according to the first indication information.
In this way, the terminal device may obtain the PDCP PDU (or the format of the PDU header, or the content information carried thereby) before decoding the PDCP PDU (or the PDU header), may correctly decode the meaning of each field in the PDCP PDU (or the PDU header), or may correctly decode the PDCP PDU.
It should be noted that S602 may be understood or replaced by: the terminal device may determine, according to the first indication information: information on whether HFN exists in PDCP PDU (or PDU header), or information on whether COUNT exists in PDCP PDU (or PDU header); or, the format type of the PDCP PDU (or, PDU header) includes a first type and/or a second type, the PDCP PDU (or, PDU header) corresponding to the first type includes information of HFN or information of COUNT, and the PDCP PDU (or, PDU header) corresponding to the second type does not include information of HFN or information of COUNT; or, whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU (or, PDU header); or, whether HFN information or COUNT information exists before or after the indication field of the PDCP PDU (or, PDU header); or, information whether only the SN is included in the PDCP PDU (or, PDU header); or whether the information of the COUNT or the information of the HFN is not included in the PDCP PDU (or PDU header).
S603, the terminal device sends the capability information to the network device.
Accordingly, the network device receives the capability information transmitted by the terminal device.
S603 is optional.
The capability information is used for indicating whether the terminal equipment supports format type conversion or indicating format types supported by the terminal equipment or indicating whether the terminal equipment supports only the first type or indicating the format type to be received or expected to be received or capable of being received by the terminal equipment or the PDCP PDU format type or the PDU header format type. Here, the format type may include at least one of a first type, a second type, or a third type, and for the description of the first type, the second type, and the third type, reference may be made to the related description in S601, which is not described herein again.
For example, whether the terminal device supports format type conversion may be understood as: whether the terminal equipment supports the format type of the first type and/or the second type; or, whether the terminal equipment supports the PDCP PDU (or the PDCP PDU format) carrying the first indication information; or, whether the terminal device supports PDCP PDUs (or PDCP PDU format) carrying HFN information or COUNT information.
Optionally, the capability information may be carried in a variety of possible messages, such as a Radio Resource Control (RRC) message or other possible messages, which is not limited specifically.
It should be noted that S603 may be implemented as a single embodiment, or may be implemented as an optional step in combination with any one or more of S600, S601, and S604, which is not limited in this respect.
S604, the terminal device receives second indication information from the network device.
Accordingly, the network device sends the second indication information to the terminal device.
S604 is optional.
The second indication information is used for indicating whether the network equipment supports format type conversion or indicating format types supported by the network equipment or indicating whether the network equipment only supports the first type or indicating the format type to be sent or can be sent by the network equipment or indicating the format type to be sent or the format type of the PDCP PDU header or the PDU header.
For example, whether the network device supports format type conversion may be understood as whether the network device supports a first type and/or a second type of format type; or, whether the network device supports the PDCP PDU (or the PDCP PDU format) carrying the first indication information; or whether the network device supports PDCP PDUs (or PDCP PDU format) carrying HFN information or COUNT information.
Optionally, the second indication Information may be carried in a variety of possible messages, such as a radio resource Control RRC message, or a PDCP Control PDU, or a PDCP PDU (or a first PDCP PDU), or a radio bearer configuration corresponding to the PDCP PDU (or a radio bearer configuration corresponding to the first PDCP PDU, or a first radio bearer configuration), or a configuration corresponding to the first service, or Downlink Control Information (DCI), or a Media Access Control (MAC) Control Element (CE), or other possible messages, which is not limited in particular.
It should be noted that S604 may be implemented as a single embodiment, or may be combined with any one or more of S600, S601, and S603 as an optional step, which is not limited in the present invention.
Optionally, any one or more of the first indication information, the second indication information, the format type, the capability information, the PDCP PDU (or the first PDCP PDU) is associated with any one or more of the first PDCP entity, the first radio bearer, the first traffic.
Optionally, the first PDCP entity and/or the first radio bearer is associated with the first traffic.
Optionally, the first PDCP PDU is associated with a first channel (or a first logical channel).
The first channel (or first logical channel) may include a channel associated with any one or more of the first traffic, the first PDCP entity, the first radio bearer. For example, the first Channel may include a multicast broadcast Traffic Channel and/or a Dedicated Traffic Channel (DTCH).
For example, the channel associated with the first service may include: a channel associated with unicast transmission of the first service and/or a channel associated with multicast transmission of the first service.
It should be noted that, the multicast broadcast traffic channel may be replaced with: channels for broadcast and/or multicast or logical channels for broadcast and/or multicast services (e.g. channels for transmission of services)
In one possible implementation, the first channel is a broadcast traffic logical channel (MTCH),
optionally, the first PDCP PDU is associated with a first RLC entity. The first RLC entity may include an RLC entity associated with the first service.
In one possible implementation, the first RLC entity is associated with a multicast broadcast traffic channel corresponding to a first service (or first radio bearer).
In one possible implementation, the first RLC entity is associated with a dedicated traffic channel corresponding to a first service (or first radio bearer).
It should be noted that S604 may be executed before S603, or S604 and S603 may also be executed simultaneously, or S601 may also be executed after S604, or S601 may also be executed after S603, and the sequence of S601, S603, and S604 is not limited in this embodiment of the application.
It should be noted that, the present application does not limit the sequence of HFN and SN in PDCP PDU, nor the close proximity between HFN and SN. As just an example, it is understood that the order of HFN and SN may be reversed. There may or may not be a gap between the HFN and the SN.
By adopting the method, the terminal equipment receives the first indication information from the network equipment, determines whether the PDCP PDU (or the PDU header) carries the HFN information or the COUNT information according to the first indication information, and if the PDCP PDU (or the PDU header) carries the HFN information or the COUNT information, the terminal equipment can determine the HFN for receiving the PDCP PDU according to the HFN information or the COUNT information. Therefore, on one hand, the HFN information or the COUNT information is carried in the PDCP PDU/PDU head, so that the terminal equipment can accurately determine the HFN of the received PDCP PDU, the HFN between the terminal equipment and the network equipment is simpler and/or more flexible to maintain, the normal receiving of data is ensured, the problems of packet loss or out-of-order delivery caused by the misalignment of the HFNs are avoided, and the reliability is improved. In addition, the method can also be beneficial to decryption and integrity verification of the terminal equipment side, so that the problem of packet loss caused by unsuccessful integrity verification is avoided, and the reliability is improved. In addition, compared with the scheme that the terminal device sets RX _ DELIV as the COUNT provided by the network device, the method can avoid the problems of packet loss and/or window jam at the receiving side (for example, the window cannot slide due to the fact that part of data cannot be successfully received, so that data cannot be delivered to an upper layer, and communication delay is increased) caused by unreasonable setting of the COUNT, thereby improving the reliability of data reception, improving the communication efficiency, and reducing the communication delay. On the other hand, by introducing the first indication information, the PDCP PDU (or PDU header) does not need to carry the HFN information or COUNT information all the time, and overhead of air interface resources can be reduced. Meanwhile, the terminal equipment can correctly determine the format of the PDCP PDU (or the PDU header), so that the PDCP PDU (or the PDU header) can be correctly decoded, and the reliability of data reception is improved.
It is understood that the above embodiments may be combined with each other.
Fig. 8 is a flowchart illustrating a further communication method according to an embodiment of the present application, as shown in fig. 8, including:
s801, optionally, the terminal device sends capability information to the network device.
Accordingly, the network device receives the capability information sent by the terminal device.
S801 is optional.
It should be noted that, as described above, the content related to the capability information may refer to the description related to fig. 6, and is not described herein again.
S802, optionally, the terminal device receives second indication information from the network device.
Accordingly, the network device sends the second indication information to the terminal device.
S802 is optional.
It should be noted that, as described above, the content related to the second indication information may refer to the description related to fig. 6, and is not described herein again.
S803, optionally, the network device determines to transmit a third type of PDCP PDU.
Optionally, the network device may determine whether to transmit the third type PDCP PDU according to the capability information transmitted by the terminal device.
For example, the network device determines that the terminal device does not support the first type and/or the second type of PDCP PDUs, and the network device transmits a third type of PDCP PDUs.
Optionally, the network device determines when to transmit the third type of PDCP PDUs and how long to transmit the third type of PDCP PDUs, which may be determined by the network device according to preset rules, or depending on the implementation of the network device.
Optionally, the network device may determine to transmit the third type of PDCP PDU according to at least one of: the number of the feedback information of the terminal equipment, the number of the terminal equipment sending the feedback information, and the time of the network equipment sending the first indication information. Wherein the feedback information includes at least one of: hybrid automatic repeat request (HARQ), channel State Information (CSI), rank Indication (RI).
For example, the network device may determine that each UE in a certain service (e.g., MBS) group receives a PDCP PDU containing MBS data according to the HARQ feedback amount of the terminal device, so that the network device may determine that the PDCP PDU does not carry HFN information or COUNT information.
For another example, the network device may determine that the subsequent PDCP PDU does not carry HFN information or COUNT information according to that the time for transmitting the PDCP PDU carrying HFN information or COUNT information is greater than a preset threshold.
S804, the network equipment sends the third type PDCP PDU to the terminal equipment.
Accordingly, the terminal device receives the PDCP PDUs of the third type from the network device.
It should be noted that, as described above, a possible implementation manner of the third type PDCP PDU may refer to the description related to fig. 6, and is not described herein again.
By the method, the network equipment can send the third type of PDCP PDU to the terminal equipment, and the sending modes of the PDCP PDU are enriched. In addition, the network device may further send a third type of PDCP PDU to the terminal device based on the capabilities of the terminal device, which may avoid the network device from sending PDCP PDUs of types that it does not support for the terminal device, e.g., PDCP PDUs of the first type and/or the second type. Optionally, the terminal device may also align HFN based on the third type of PDCP PDU and the network device.
It should be noted that S804 and S803 may be executed simultaneously, or S804 may also execute the sequence of S803 and S804 after S803, which is not limited in this embodiment of the present application.
It should be noted that (1) the embodiments corresponding to fig. 5, fig. 6, and fig. 8 may be implemented individually or may also be implemented in combination (for example, all or part of the solutions related in fig. 5 may be combined with the embodiment corresponding to fig. 8), and are not limited specifically.
(2) The step numbers of the flowcharts (such as fig. 5, 6, and 8) described in the embodiment of the present application are only an example of an execution flow, and do not limit the sequence of executing the steps, and there is no strict execution sequence between steps that have no time sequence dependency relationship with each other in the embodiment of the present application.
For the above method flow, the present application also provides a communication device, which is configured to execute the above method flow.
Fig. 9 shows a possible exemplary block diagram of the apparatus involved in the embodiments of the present application. As shown in fig. 9, the apparatus 900 may include: a transceiving unit 920 and a processing unit 910. The processing unit 910 is configured to control and manage the operations of the apparatus 900, and the transceiver 920 may include a receiving unit and/or a transmitting unit, which are respectively configured to perform receiving and transmitting operations. The element of the transceiver 920 may be a receiver or a transceiver, and the hardware element of the processing unit 910 may be a processor.
The communication apparatus 900 may be the terminal device in the foregoing embodiment, or may also be a chip disposed in the terminal device, and the apparatus 900 may execute the flow corresponding to the terminal device in the foregoing method embodiment. The processing unit 910 may enable the apparatus 900 to perform the actions of the terminal device in the above method examples. Alternatively, the processing unit 910 mainly performs the internal actions of the terminal device in the method example, and the transceiving unit 920 may support the previous communication of the apparatus 900 with other devices.
Specifically, in one embodiment, the transceiving unit 920 is configured to receive first information from a network device, where the first information includes any one of the following:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
a transceiving unit 920, further configured to receive a first PDCP PDU from the network device, where the first PDCP PDU includes a second SN;
a processing unit 910, configured to determine an HFN of the first PDCP PDU according to the first information and the second SN.
In one possible design, the first information includes information of a first HFN and information of a first SN, and the processing unit 910 is specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, where the determining includes any one or more of:
if the second SN is less than the difference between the first SN and a first parameter, the HFN of the first PDCP PDU is equal to the first HFN plus 1;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than or equal to the sum of the first SN and a first parameter;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and a first parameter and/or the second SN is less than a sum of the first SN and the first parameter.
In one possible design, the first information includes: the processing unit 910 is specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, and includes any one or more of the following:
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is within the range of SNs;
the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than a minimum value within the range of SNs;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than a maximum value within the range of SNs.
In one possible design, the first information includes information of a COUNT range, and the processing unit 910 is specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, where the determining includes any one or more of:
if the second SN is greater than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range;
and if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
In one possible design, the processing unit 910 is further configured to:
setting a first state variable according to one of the following methods:
setting the minimum value or the maximum value in the received COUNT of the first PDCP PDU and the COUNT corresponding to the first information as the first state variable;
setting the minimum value or the maximum value in the COUNT of the received N PDCP PDUs as the first state variable, wherein N is a positive integer;
setting the minimum value or the maximum value of the COUNT of the received N PDCP PDUs and the COUNT corresponding to the first information as the first state variable, wherein N is a positive integer;
setting a minimum value or a maximum value in a COUNT of PDCP PDUs received within a first time period T as the first state variable;
setting the minimum value or the maximum value of the COUNT of the PDCP PDU received in the first time period T and the COUNT corresponding to the first information as the first state variable.
In one possible design, any one or more of the first PDCP PDU, the received N PDCP PDUs, the PDCP PDUs received within the first time period T, the first information is associated with the first PDCP entity or with the first radio bearer.
In one possible design, the first PDCP entity and/or the first radio bearer is associated with first traffic, the first traffic including broadcast traffic and/or multicast traffic.
Specifically, in another embodiment, the transceiver unit 920 is configured to receive first indication information from a network device, where the first indication information is used to indicate whether HFN exists in PDCP PDUs or whether COUNT exists in PDCP PDUs; or,
the first indication information is used for indicating a PDCP PDU format type, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In a possible design, the transceiving unit 920 is further configured to send, to the network device, capability information, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate a format type supported by the terminal device, or is used to indicate whether the terminal device supports only the first type.
In a possible design, the transceiver 920 is further configured to receive second indication information from the network device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate format types supported by the network device, or is used to indicate whether the network device supports only the first type.
Fig. 10 shows a possible exemplary block diagram of the apparatus involved in the embodiments of the present application. As shown in fig. 10, the apparatus 1000 may include: a transceiver unit 1020 and a processing unit 1010. The processing unit 1010 is configured to control and manage actions of the apparatus 1000, and the transceiver 1020 may include a receiving unit and/or a transmitting unit, which are configured to perform receiving and transmitting operations, respectively. The element of the transceiver 1020 may be a receiver or a transceiver, and the hardware element of the processing unit 1010 may be a processor.
The communication apparatus 1000 may be the network device in the foregoing embodiment, or may also be a chip disposed in the network device, and the apparatus 1000 may execute a flow corresponding to the network device in the foregoing method embodiment. Processing unit 1010 may enable apparatus 1000 to perform the actions of the network device in the above method examples. Alternatively, the processing unit 1010 mainly performs internal actions of the network device in the method example, and the transceiver unit 1020 may support previous communication between the apparatus 1000 and other devices.
Specifically, in one embodiment, the transceiver unit 1020 is configured to transmit first information to the terminal device, where the first information includes any one of the following:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
the transceiver unit 1020 is further configured to send a first PDCP PDU to the terminal device, where the first PDCP PDU includes a second SN.
Specifically, in another embodiment, the transceiver unit 1020 is configured to receive first indication information from a network device, where the first indication information is used to indicate whether HFN exists in PDCP PDUs or whether COUNT exists in PDCP PDUs; or,
the first indication information is used for indicating a PDCP PDU format type, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
In a possible design, the transceiver unit 1020 is further configured to receive capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate format types supported by the terminal device, or is used to indicate whether the terminal device supports only the first type.
In a possible design, the transceiver 1020 is further configured to send second indication information to the terminal device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate a format type supported by the network device, or is used to indicate whether the network device supports only the first type.
When the communication device is a UE, fig. 11 shows a simplified structural diagram of the UE. For ease of understanding and illustration, in fig. 11, the UE is exemplified by a handset. As shown in fig. 11, the UE includes a processor, a memory, radio frequency circuitry, an antenna, and input-output devices. The processor is mainly used for processing communication protocols and communication data, controlling the UE, executing software programs, processing data of the software programs, and the like. The memory is used primarily for storing software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used for receiving data input by users and outputting data to the users. It should be noted that some kinds of UEs may not have input/output devices.
When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs baseband signals to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is sent to the UE, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data. For ease of illustration, only one memory and processor are shown in FIG. 11. In an actual UE product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment of the present application.
Please refer to fig. 12, which is a schematic structural diagram of a terminal device according to an embodiment of the present application. It may be the terminal device in the above embodiment, for implementing the operation of the terminal device in the above embodiment. As shown in fig. 3, the terminal device includes: an antenna 1210, a radio frequency part 1220, a signal processing part 1230. The antenna 1210 is connected to the radio frequency part 1220. In the downlink direction, the rf part 1220 receives information transmitted from the network device through the antenna 1210, and transmits the information to the signal processing part 1230 for processing. In the uplink direction, the signal processing portion 1230 processes the information of the terminal device and sends the information to the rf portion 1220, and the rf portion 1220 processes the information of the terminal device and sends the processed information to the network device through the antenna 1210.
The signal processing portion 1230 may include a modem subsystem for implementing processing of various communication protocol layers of data; the system also comprises a central processing subsystem used for processing the operating system and the application layer of the terminal equipment; in addition, other subsystems, such as a multimedia subsystem for controlling a camera, a screen display, etc. of the terminal device, a peripheral subsystem for connecting with other devices, etc. may be included. The modem subsystem may be a separately provided chip. Alternatively, the above means for the terminal device may be located at the modem subsystem.
The modem subsystem may include one or more processing elements 1231, including, for example, a master CPU and other integrated circuits. The modem subsystem may also include a storage element 1232 and an interface circuit 1233. The storage element 1232 is used to store data and programs, but a program for executing the method executed by the terminal device in the above method may not be stored in the storage element 1232, but stored in a memory outside the modem subsystem, and the modem subsystem is loaded for use when used. The interface circuit 1233 is used to communicate with other subsystems. The above apparatus for a terminal device may be located in a modem subsystem, which may be implemented by a chip comprising at least one processing element for performing the steps of any of the methods performed by the above terminal device, and interface circuitry for communicating with other apparatus. In one implementation, the unit for the terminal device to implement each step in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the terminal device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the terminal device in the above method embodiment. The memory elements may be memory elements with the processing elements on the same chip, i.e. on-chip memory elements.
In another implementation, the program for executing the method performed by the terminal device in the above method may be in a memory element on a different chip than the processing element, i.e. an off-chip memory element. At this time, the processing element calls or loads a program from the off-chip storage element onto the on-chip storage element to call and execute the method executed by the terminal device in the above method embodiment.
In yet another implementation, the unit of the terminal device implementing the steps of the above method may be configured as one or more processing elements disposed on the modem subsystem, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.
The units of the terminal device for implementing the steps of the above method can be integrated together and implemented in the form of a system-on-a-chip (SOC) chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the processing element calls the stored program of the storage element to realize the method executed by the terminal equipment; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above terminal device; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.
It is seen that the above apparatus for a terminal device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the terminal devices provided by the above method embodiments. The processing element may: namely, the method calls the program stored in the storage element to execute part or all of the steps executed by the terminal equipment; it is also possible to: that is, some or all of the steps performed by the terminal device are performed by integrated logic circuits of hardware in the processor element in combination with the instructions; of course, some or all of the steps performed by the terminal device may be performed in combination with the first manner and the second manner.
The processing elements herein, like those described above, may be a general purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
The storage element may be a memory or a combination of a plurality of storage elements.
Please refer to fig. 13, which is a schematic structural diagram of a network device according to an embodiment of the present application. For implementing the operations of the network device (such as the second network device) in the above embodiments. As shown in fig. 13, the network device includes: antenna 1301, radio frequency device 1302, baseband device 1303. The antenna 1301 is connected to the radio frequency device 1302. In the uplink direction, the rf device 1302 receives information sent by the terminal device through the antenna 1301, and sends the information sent by the terminal device to the baseband device 1303 for processing. In the downlink direction, the baseband device 1303 processes the information of the terminal device and sends the information to the rf device 1302, and the rf device 1302 processes the information of the terminal device and sends the information to the terminal device through the antenna 1301.
The baseband device 1303 may include one or more processing elements 13031, e.g., including a main CPU and other integrated circuits. In addition, the baseband device 1303 may further include a storage element 13032 and an interface 13033, where the storage element 13032 is used to store programs and data; the interface 13033 is used for exchanging information with the radio frequency device 1302, and is, for example, a Common Public Radio Interface (CPRI). The above means for a network device may be located on the baseband means 1303, for example, the above means for a network device may be a chip on the baseband means 1303, the chip including at least one processing element and an interface circuit, wherein the processing element is configured to perform each step of any one of the methods performed by the above network device, and the interface circuit is configured to communicate with other devices. In one implementation, the unit of the network device for implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the network device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing element, i.e. on-chip memory elements, or may be memory elements on a different chip than the processing element, i.e. off-chip memory elements.
In another implementation, the unit of the network device for implementing the steps of the above method may be configured as one or more processing elements, which are disposed on the baseband apparatus, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.
The units of the network device implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC), for example, a baseband device including the SOC chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the method executed by the network equipment is realized in the form that the processing element calls the stored program of the storage element; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above network device; or, the above implementation manners may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.
It is seen that the above apparatus for a network device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the network devices provided by the above method embodiments. The processing element may: namely, calling the program stored in the storage element to execute part or all of the steps executed by the network equipment; it is also possible in a second way: that is, some or all of the steps performed by the network device are performed by integrated logic circuitry of hardware in the processor element in combination with instructions; of course, some or all of the steps performed by the above network device may also be performed in combination with the first manner and the second manner.
The processing elements herein, like those described above, may be a general purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
The storage element may be a memory or a combination of a plurality of storage elements.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.

Claims (32)

1. A communication method is applied to a terminal device and comprises the following steps:
receiving first information from a network device, the first information comprising any one of:
information of a first hyper frame number, HFN, and information of a first sequence number, SN; or,
information of the first HFN and information of the SN range; or,
counting COUNT range information;
receiving a first packet data convergence layer protocol, PDCP, protocol data unit, PDU from the network device, the first PDCP PDU comprising a second SN;
and determining the HFN of the first PDCP PDU according to the first information and the second SN.
2. The method of claim 1, wherein the first information comprises information of a first HFN and information of a first SN, and wherein determining the HFN of the first PDCP PDU from the first information and the second SN comprises any one or more of:
if the second SN is less than the difference between the first SN and a first parameter, the HFN of the first PDCP PDU is equal to the first HFN plus 1;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than or equal to a sum of the first SN and a first parameter;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and a first parameter and/or the second SN is less than a sum of the first SN and the first parameter.
3. The method of claim 1, wherein the first information comprises: information of a first HFN and information of a SN range, said determining an HFN of said first PDCP PDU based on said first information and said second SN, comprising any one or more of:
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is within the range of SNs;
if the second SN is less than a minimum value in the SN range, the HFN of the first PDCP PDU is equal to the first HFN plus 1;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than a maximum value within the range of SNs.
4. The method of claim 1, wherein the first information comprises a COUNT range information, and wherein determining the HFN of the first PDCP PDU based on the first information and the second SN comprises any one or more of:
if the second SN is greater than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range;
and if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
5. The method according to any one of claims 1-4, further comprising:
setting a first state variable according to one of the following methods:
setting the minimum value or the maximum value in the received COUNT of the first PDCP PDU and the COUNT corresponding to the first information as the first state variable;
setting the minimum value or the maximum value in the COUNT of the received N PDCP PDUs as the first state variable, wherein N is a positive integer;
setting the minimum value or the maximum value of the COUNT of the received N PDCP PDUs and the COUNT corresponding to the first information as the first state variable, wherein N is a positive integer;
setting a minimum value or a maximum value in a COUNT of PDCP PDUs received within a first time period T as the first state variable;
setting the minimum value or the maximum value of the COUNT of the PDCP PDU received in the first time period T and the COUNT corresponding to the first information as the first state variable.
6. The method of any of claims 1-5 wherein any one or more of the first PDCP PDU, the received N PDCP PDUs, the PDCP PDUs received within the first time period T, the first information is associated with a first PDCP entity or with a first radio bearer.
7. The method of any of claims 1-6, wherein the first PDCP entity and/or the first radio bearer is associated with first traffic, wherein the first traffic comprises broadcast traffic and/or multicast traffic.
8. A communication method applied to a network device includes:
sending first information to a terminal device, wherein the first information comprises any one of the following:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
and sending a first PDCP PDU to the terminal equipment, wherein the first PDCP PDU comprises a second SN.
9. A communication method is applied to a terminal device and comprises the following steps:
receiving a PDCP PDU from a network device;
receiving first indication information from the network device,
the first indication information is used for indicating whether HFN exists in the PDCP PDU or indicating whether COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating a format type of the PDCP PDU, the format type includes a first type and/or a second type, the PDCP PDU corresponding to the first type includes information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not include the information of HFN or information of COUNT; or,
the first indication information is used to indicate whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
10. The method of claim 9, further comprising:
and sending capability information to the network equipment, wherein the capability information is used for indicating whether the terminal equipment supports format type conversion or indicating the format types supported by the terminal equipment or indicating whether the terminal equipment only supports the first type.
11. The method of claim 9 or 10, further comprising:
receiving second indication information from the network device, wherein the second indication information is used for indicating whether the network device supports format type conversion or indicating format types supported by the network device or indicating whether the network device only supports the first type.
12. A communication method applied to a network device includes:
transmitting PDCP PDU to the terminal equipment;
transmitting first indication information to the terminal device, wherein the first indication information is used for indicating whether HFN exists in the PDCP PDU or indicating whether COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating the format type of the PDCP PDU, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used to indicate whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
13. The method of claim 12, further comprising:
and receiving capability information sent by the terminal equipment, wherein the capability information is used for indicating whether the terminal equipment supports format type conversion or indicating the format types supported by the terminal equipment or indicating whether the terminal equipment only supports the first type.
14. The method of claim 12 or 13, further comprising:
and sending second indication information to the terminal equipment, wherein the second indication information is used for indicating whether the network equipment supports format type conversion or indicating the format types supported by the network equipment or indicating whether the network equipment only supports the first type.
15. A communications apparatus, comprising:
a transceiver unit, configured to receive first information from a network device, where the first information includes any one of:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
the transceiver unit is further configured to receive a first PDCP PDU from the network device, where the first PDCP PDU includes a second SN;
and the processing unit is used for determining the HFN of the first PDCP PDU according to the first information and the second SN.
16. The apparatus of claim 15, wherein the first information comprises information of a first HFN and information of a first SN, and wherein the processing unit, being specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, comprises any one or more of:
if the second SN is less than the difference between the first SN and a first parameter, the HFN of the first PDCP PDU is equal to the first HFN plus 1;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than or equal to the sum of the first SN and a first parameter;
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is greater than or equal to a difference between the first SN and a first parameter and/or the second SN is less than a sum of the first SN and the first parameter.
17. The apparatus of claim 15, wherein the first information comprises: the processing unit is specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, and includes any one or more of the following:
the HFN of the first PDCP PDU is equal to the first HFN if the second SN is within the range of SNs;
the HFN of the first PDCP PDU is equal to the first HFN plus 1 if the second SN is less than a minimum value within the range of SNs;
the HFN of the first PDCP PDU is equal to the first HFN minus 1 if the second SN is greater than a maximum value within the range of SNs.
18. The apparatus according to claim 15, wherein the first information comprises information of a COUNT range, and wherein the processing unit, specifically configured to determine the HFN of the first PDCP PDU according to the first information and the second SN, comprises any one or more of:
if the second SN is greater than or equal to the SN corresponding to the minimum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the minimum value in the COUNT range;
and if the second SN is less than or equal to the SN corresponding to the maximum value in the COUNT range, the HFN of the first PDCP PDU is equal to the HFN corresponding to the maximum value in the COUNT range.
19. The apparatus according to any of claims 15-18, wherein the processing unit is further configured to:
setting a first state variable according to one of the following methods:
setting the minimum value or the maximum value in the received COUNT of the first PDCP PDU and the COUNT corresponding to the first information as the first state variable;
setting the minimum value or the maximum value in the COUNT of the received N PDCP PDUs as the first state variable, wherein N is a positive integer;
setting the minimum value or the maximum value of the COUNT of the received N PDCP PDUs and the COUNT corresponding to the first information as the first state variable, wherein N is a positive integer;
setting a minimum value or a maximum value in a COUNT of PDCP PDUs received within a first time period T as the first state variable;
setting the minimum value or the maximum value of the COUNT of the PDCP PDU received in the first time period T and the COUNT corresponding to the first information as the first state variable.
20. The apparatus of any of claims 15-19, wherein any one or more of the first PDCP PDU, the received N PDCP PDUs, the PDCP PDUs received within the first time period T, the first information is associated with a first PDCP entity or with a first radio bearer.
21. The apparatus of any of claims 15-20, wherein the first PDCP entity and/or the first radio bearer is associated with a first service, wherein the first service comprises a broadcast service and/or a multicast service.
22. A communications apparatus, comprising:
a transceiving unit, configured to send first information to a terminal device, where the first information includes any one of:
information of the first HFN and information of the first SN; or,
information of the first HFN and information of the SN range; or,
information of COUNT range;
the transceiver unit is further configured to send a first PDCP PDU to the terminal device, where the first PDCP PDU includes a second SN.
23. A communications apparatus, comprising:
a transceiving unit, configured to receive a PDCP PDU from a network device;
a transceiver unit, further configured to receive first indication information from the network device, where the first indication information is used to indicate whether an HFN exists in the PDCP PDU or whether a COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating the format type of the PDCP PDU, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used to indicate whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether information of HFN or information of COUNT exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
24. The apparatus of claim 23, further comprising:
the transceiving unit is further configured to send capability information to the network device, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate a format type supported by the terminal device, or is used to indicate whether the terminal device supports only a first type.
25. The apparatus of claim 23 or 24, further comprising:
the transceiver unit is further configured to receive second indication information from the network device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate a format type supported by the network device, or is used to indicate whether the network device supports only the first type.
26. A communications apparatus, comprising:
a receiving and sending unit, configured to send a PDCP PDU to a terminal device;
a transceiving unit, further configured to send first indication information to the terminal device, where the first indication information is used to indicate whether a first HFN exists in the PDCP PDU or whether a COUNT exists in the PDCP PDU; or,
the first indication information is used for indicating the format type of the PDCP PDU, the format type comprises a first type and/or a second type, the PDCP PDU corresponding to the first type comprises information of HFN or information of COUNT, and the PDCP PDU corresponding to the second type does not comprise the information of HFN or information of COUNT; or,
the first indication information is used to indicate whether HFN information or COUNT information exists before or after the first indication information in the PDCP PDU; or,
the first indication information is used for indicating whether HFN information or COUNT information exists before or after an indication field of the PDCP PDU;
wherein the indication field comprises at least one of the following information: SN, reserved bit R, PDU type, data, integrity message authentication code MAC-I.
27. The apparatus of claim 26, further comprising:
the receiving and sending unit is further configured to receive capability information sent by the terminal device, where the capability information is used to indicate whether the terminal device supports format type conversion, or is used to indicate a format type supported by the terminal device, or is used to indicate whether the terminal device only supports a first type.
28. The apparatus of claim 26 or 27, further comprising:
a transceiver unit, further configured to send second indication information to the terminal device, where the second indication information is used to indicate whether the network device supports format type conversion, or is used to indicate a format type supported by the network device, or is used to indicate whether the network device only supports the first type.
29. A communications apparatus comprising at least one processor and a memory, the memory having instructions stored thereon, wherein the instructions, when executed on a computer, cause the computer to perform the method of any of claims 1-7 or 9-11.
30. A communications apparatus comprising at least one processor and a memory, the memory having instructions stored thereon, wherein the instructions, when executed on a computer, cause the computer to perform the method of any of claims 8 or 12-14.
31. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-7 or 9-11.
32. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 8 or 12-14.
CN202110362488.2A 2021-04-02 2021-04-02 Communication method and communication device Pending CN115174491A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110362488.2A CN115174491A (en) 2021-04-02 2021-04-02 Communication method and communication device
PCT/CN2022/084954 WO2022206983A1 (en) 2021-04-02 2022-04-02 Communication method and communication apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110362488.2A CN115174491A (en) 2021-04-02 2021-04-02 Communication method and communication device

Publications (1)

Publication Number Publication Date
CN115174491A true CN115174491A (en) 2022-10-11

Family

ID=83458106

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110362488.2A Pending CN115174491A (en) 2021-04-02 2021-04-02 Communication method and communication device

Country Status (2)

Country Link
CN (1) CN115174491A (en)
WO (1) WO2022206983A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686494A (en) * 2008-09-22 2010-03-31 大唐移动通信设备有限公司 Method and device for processing packets by packet data convergence protocol (PDCP) layer
US20130315201A1 (en) * 2012-05-23 2013-11-28 Nvidia Corporation Processing data units
CN103533586A (en) * 2012-07-03 2014-01-22 电信科学技术研究院 Method and apparatus for signaling interaction and layer reconstruction in switching process
US20190044880A1 (en) * 2017-08-07 2019-02-07 Lg Electronics Inc. Method for handling state variables of a pdcp entity in wireless communication system and a device therefor
CN110858828A (en) * 2018-08-22 2020-03-03 普天信息技术有限公司 PDCP SDU reordering method and device
CN111818630A (en) * 2019-07-12 2020-10-23 维沃移动通信有限公司 State variable maintenance method and device and user equipment
WO2021056152A1 (en) * 2019-09-23 2021-04-01 Oppo广东移动通信有限公司 Information configuration method and apparatus, terminal device, and network device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070258591A1 (en) * 2006-05-05 2007-11-08 Interdigital Technology Corporation Ciphering control and synchronization in a wireless communication system
CN104168640A (en) * 2013-05-17 2014-11-26 中兴通讯股份有限公司 Reception end PDCP layer HFN out-off-step recovering method and device
US10694377B2 (en) * 2018-09-19 2020-06-23 Samsung Electronics Co., Ltd. Method and apparatus for identifying security key in next generation mobile communication system

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686494A (en) * 2008-09-22 2010-03-31 大唐移动通信设备有限公司 Method and device for processing packets by packet data convergence protocol (PDCP) layer
US20130315201A1 (en) * 2012-05-23 2013-11-28 Nvidia Corporation Processing data units
CN103533586A (en) * 2012-07-03 2014-01-22 电信科学技术研究院 Method and apparatus for signaling interaction and layer reconstruction in switching process
US20190044880A1 (en) * 2017-08-07 2019-02-07 Lg Electronics Inc. Method for handling state variables of a pdcp entity in wireless communication system and a device therefor
CN110858828A (en) * 2018-08-22 2020-03-03 普天信息技术有限公司 PDCP SDU reordering method and device
CN111818630A (en) * 2019-07-12 2020-10-23 维沃移动通信有限公司 State variable maintenance method and device and user equipment
WO2021056152A1 (en) * 2019-09-23 2021-04-01 Oppo广东移动通信有限公司 Information configuration method and apparatus, terminal device, and network device

Also Published As

Publication number Publication date
WO2022206983A1 (en) 2022-10-06

Similar Documents

Publication Publication Date Title
CN111065074B (en) Electronic device and method thereof
WO2015163601A9 (en) Method for processing received rlc pdus for d2d communication system and device therefor
EP3737183B1 (en) Communication methods, apparatuses and computer-readable storage medium
US11647417B2 (en) Method, apparatus, computer program product and computer program
WO2018053692A1 (en) Data transmission method, device and system
US20220377781A1 (en) Method, apparatus, computer program product and computer program
WO2013152743A1 (en) Method and device for transmitting signals
CN110662299B (en) Communication method, communication apparatus, and storage medium
WO2017054583A1 (en) Downlink control information transmission method in multiple user cooperative communication, base station, and user equipment
AU2017418048A1 (en) Communication apparatus, method and computer program
CN110832950A (en) Enabling efficient processing of redundant packet copies in a wireless communication system
US20200128599A1 (en) Data transmission method, terminal device, and network device
CN113162727A (en) Link-specific block acknowledgement for multi-link communications
WO2020164474A1 (en) Codebook processing method and apparatus
EP4315689A1 (en) Methods and apparatus for disabled harq processes
WO2022150937A1 (en) Method and apparatus for receiving data, and method and apparatus for sending data
US20230276460A1 (en) Method and device in nodes used for wireless communication
US20230189300A1 (en) Communication control method
US11064503B2 (en) Method and apparatus for transmitting control information
CN115174491A (en) Communication method and communication device
US11968683B2 (en) Apparatus, method and computer program
WO2023000177A1 (en) Method, device and computer readable medium for communication
WO2023060402A1 (en) Method and apparatus for multicast and broadcast services
CN117596218A (en) Communication method and device
WO2018232627A1 (en) Communication apparatus, method and computer program

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