WO2022205230A1 - 一种分组数据汇聚协议实体的超帧号确定方法及其装置 - Google Patents

一种分组数据汇聚协议实体的超帧号确定方法及其装置 Download PDF

Info

Publication number
WO2022205230A1
WO2022205230A1 PCT/CN2021/084755 CN2021084755W WO2022205230A1 WO 2022205230 A1 WO2022205230 A1 WO 2022205230A1 CN 2021084755 W CN2021084755 W CN 2021084755W WO 2022205230 A1 WO2022205230 A1 WO 2022205230A1
Authority
WO
WIPO (PCT)
Prior art keywords
value
hfn
information
terminal device
sfn
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.)
Ceased
Application number
PCT/CN2021/084755
Other languages
English (en)
French (fr)
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.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software 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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to KR1020237037315A priority Critical patent/KR102816866B1/ko
Priority to PCT/CN2021/084755 priority patent/WO2022205230A1/zh
Priority to CN202180000903.8A priority patent/CN115486112B/zh
Priority to EP21933890.2A priority patent/EP4319069A4/en
Priority to JP2023559047A priority patent/JP7592891B2/ja
Priority to BR112023019809A priority patent/BR112023019809A2/pt
Priority to US18/552,355 priority patent/US20240179563A1/en
Publication of WO2022205230A1 publication Critical patent/WO2022205230A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a method and a device for determining a superframe number of a packet data convergence protocol entity.
  • a network device In a communication system, a network device is constantly sending data, so the value of a hyperframe number (hyperframe number, HFN) used by the network device is constantly increasing.
  • HFN hyperframe number
  • the terminal device When a new terminal device joins in to receive the data sent by the network device, the terminal device does not know the HFN value adopted by the network device, so that the terminal device cannot use the correct count value (COUNT) to decrypt or complete the received data. verification, resulting in failure of decryption of data or failure of integrity verification.
  • COUNT correct count value
  • the embodiments of the present disclosure provide a method and a device for determining a superframe number of a packet data convergence protocol entity, which can be applied in the field of communication technologies.
  • an embodiment of the present disclosure provides a method for determining a superframe number of a packet data convergence protocol entity, the method is configured to be executed by a terminal device, and the method includes: receiving indication information sent by a network device, wherein the The indication information includes super frame number HFN information; based on the HFN information, the HFN value of the packet data convergence protocol PDCP entity is determined.
  • the terminal device may first receive the indication information sent by the network device, and then determine the HFN value of the PDCP entity according to the HFN information included in the indication information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • the HFN information includes any one of the following: an HFN value and a count value COUNT.
  • the determining, based on the HFN information, the HFN value of the PDCP entity of the Packet Data Convergence Protocol includes: in response to satisfying the applicable condition of the HFN information, determining the HFN value of the PDCP entity based on the HFN information. HFN value.
  • the applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any of the following:
  • the value of the SFN includes any of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the meeting the applicable conditions includes:
  • the SN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition
  • the SFN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition.
  • the indication information further includes MBS service information
  • the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.
  • the SFN value corresponding to the received PDCP data packet includes any of the following:
  • the SFN value corresponding to the time position of the first physical data channel that successfully receives the PCDP data packet
  • the SFN value corresponding to the PDCP data packet is successfully received.
  • the applicable condition is the value of SN
  • the HFN value of the PDCP entity of the Packet Data Convergence Protocol is determined based on the HFN information, including:
  • the HFN information is updated based on the difference value s, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the applicable condition is the value of SFN
  • the HFN value of the PDCP entity of the Packet Data Convergence Protocol is determined based on the HFN information, including:
  • the HFN information is updated based on the difference k, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the indication information further includes an update mode of the HFN information
  • the determining the HFN value of the Packet Data Convergence Protocol PDCP entity based on the HFN information includes:
  • the HFN value of the PDCP entity is determined.
  • the update mode includes an update step size and an update direction.
  • the receiving indication information sent by the network device includes:
  • the indication information sent by the network device is received.
  • the indication information further includes MBS service information, and determining the HFN value of the Packet Data Convergence Protocol PDCP entity based on the HFN information includes:
  • the HFN value of the PDCP entity corresponding to the MBS service information is determined.
  • the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the method further includes: decrypting or verifying the integrity of the received data corresponding to the MBS service information based on the HFN information.
  • the determining the HFN value of the Packet Data Convergence Protocol PDCP entity based on the HFN information includes: in response to the terminal device being a device newly accessing the MBS service, determining the HFN value based on the HFN information. HFN value of the PDCP entity.
  • the embodiments of the present disclosure provide another method for determining a superframe number of a packet data convergence protocol entity, the method is configured to be executed by a network device, and the method includes: sending indication information to a terminal device, wherein the The indication information includes super frame number HFN information.
  • the HFN information includes any one of the following: an HFN value and a count value COUNT.
  • the indication information further includes applicable conditions of the HFN information.
  • the applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any of the following:
  • the value of the SFN includes any of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the indication information further includes MBS service information.
  • the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the indication information further includes an update mode of the HFN information.
  • the update mode includes an update step size and an update direction.
  • the sending the indication information to the terminal device includes:
  • the indication information is sent to the terminal device.
  • second change indication information is sent to the terminal device.
  • an embodiment of the present disclosure provides a communication apparatus, where the apparatus is configured on the side of a terminal device, and the apparatus includes: a transceiver module, configured to receive indication information sent by a network device, wherein the indication information includes Including super frame number HFN information; processing module for determining the HFN value of the packet data convergence protocol PDCP entity based on the HFN information.
  • the HFN information includes any one of the following: an HFN value and a count value COUNT.
  • the processing module is specifically configured to, in response to satisfying the applicable condition of the HFN information, determine the HFN value of the PDCP entity based on the HFN information.
  • the transceiver module is further configured to receive the applicable conditions of the HFN information sent by the network device;
  • the processing module is further configured to determine the applicable condition of the HFN information based on the agreement.
  • the applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any of the following:
  • the value of the SFN includes any of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the meeting the applicable conditions includes:
  • the SN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition
  • the SFN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition.
  • the indication information further includes MBS service information
  • the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.
  • the SFN value corresponding to the received PDCP data packet includes any of the following:
  • the SFN value corresponding to the time position of the first physical data channel that successfully receives the PCDP data packet
  • the SFN value corresponding to the PDCP data packet is successfully received.
  • the applicable condition is the value of SN
  • the processing module is specifically used for:
  • the HFN information is updated based on the difference value s, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the applicable condition is the value of SFN
  • the processing module is specifically used for:
  • the HFN information is updated based on the difference k, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the indication information further includes an update mode of the HFN information
  • the processing module is specifically configured to:
  • the HFN value of the PDCP entity is determined.
  • the update mode includes an update step size and an update direction.
  • the transceiver module is specifically used for:
  • the indication information sent by the network device is received.
  • the indication information further includes MBS service information
  • the processing module is specifically configured to:
  • the HFN value of the PDCP entity corresponding to the MBS service information is determined.
  • the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the processing module is further configured to decrypt or verify the integrity of the received data corresponding to the MBS service information based on the HFN information.
  • processing module is specifically used for:
  • the HFN value of the PDCP entity is determined based on the HFN information.
  • an embodiment of the present disclosure provides another communication apparatus, the apparatus is configured on a network device side, and the apparatus includes: a transceiver module, configured to send indication information to a terminal device, wherein the indication information includes Including super frame number HFN information.
  • the HFN information includes any one of the following: an HFN value and a count value COUNT.
  • the transceiver module is further configured to send the applicable conditions of the HFN information to the terminal device.
  • the applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any of the following:
  • the value of the SFN includes any of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the indication information further includes MBS service information.
  • the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the indication information further includes an update mode of the HFN information.
  • the update mode includes an update step size and an update direction.
  • the transceiver module is specifically used for:
  • the indication information is sent to the terminal device.
  • the transceiver module is also used for:
  • second change indication information is sent to the terminal device.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor, and when the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor, and when the processor calls a computer program in a memory, the method described in the second aspect above is executed.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, the device includes a processor and an interface circuit, the interface circuit is configured to receive a code instruction and transmit it to the processor, and the processor is configured to run the code instruction to make the code instruction
  • the apparatus performs the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, the device includes a processor and an interface circuit, the interface circuit is configured to receive a code instruction and transmit it to the processor, and the processor is configured to run the code instruction to make the code instruction
  • the apparatus performs the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication system, where the system includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and The communication device of the sixth aspect, or the system includes the communication device of the seventh aspect and the communication device of the eighth aspect, or the system includes the communication device of the ninth aspect and the tenth aspect. the communication device described.
  • an embodiment of the present invention provides a computer-readable storage medium for storing an instruction used by the above-mentioned terminal device, and when the instruction is executed, the terminal device is made to execute the above-mentioned first aspect. method.
  • an embodiment of the present invention provides a computer-readable storage medium for storing an instruction used by the above-mentioned network device, and when the instruction is executed, the network device is made to execute the above-mentioned second aspect. method.
  • the present disclosure also provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to perform the method described in the first aspect above.
  • the present disclosure also provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to perform the method described in the second aspect above.
  • the present disclosure provides a chip system
  • the chip system includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing data involved in the above method and at least one of information.
  • the chip system further includes a memory for storing necessary computer programs and data of the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system
  • the chip system includes at least one processor and an interface for supporting a network device to implement the functions involved in the second aspect, for example, determining or processing data involved in the above method and at least one of information.
  • the chip system further includes a memory for storing necessary computer programs and data of the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect above.
  • the present disclosure provides a computer program that, when executed on a computer, causes the computer to execute the method described in the second aspect above.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity according to another embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity according to another embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity according to another embodiment of the present disclosure
  • FIG. 8 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity according to another embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a communication device according to another embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a communication device according to another embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a chip according to an embodiment of the present disclosure.
  • Multimedia broadcast and multicast service (MBMS) or broadcast multicast service (multicast broadcast service, MBS)
  • MBS multicast broadcast service
  • MBS is a practical technology to improve the efficiency of spectrum usage and is widely used in communication systems.
  • MBS services can be sent through the physical downlink shared channel (PDSCH) scheduled by the physical downlink control channel (PDCCH).
  • PDSCH physical downlink shared channel
  • PDCCH physical downlink control channel
  • PDCP is a wireless transmission protocol stack, which can process radio resource control (radio resource control, RRC) messages and Internet protocol (internet protocol, IP) packets. It can perform IP header compression and decompression, transmit user data and maintain the sequence number (SN) of the radio bearer, and can also provide signaling transmission services, and implement signaling encryption and consistency protection, as well as in the reverse direction. Decryption and consistency checking of signaling.
  • RRC radio resource control
  • IP Internet protocol
  • the communication system can perform encryption processing and integrity protection on the transmitted data.
  • a 32-bit (bit) message authentication code for integrity protection (message authentication code for integrity, MAC-I) can be added at the end of the PDCP data packet to implement the integrity protection function.
  • the PDCP receiving entity needs to know the COUNT value of the PDCP to decrypt encrypted data or perform integrity verification on the data.
  • the COUNT value of PDCP can be composed of two parts of HFN and SN of PDCP, with a total of 32 bits.
  • the header of the PDCP data packet carries the SN number of the PDCP.
  • time domain resources may be serially numbered according to SFN with a granularity of 10 milliseconds (millisecond, ms).
  • SFN can include 10 subframes (subframes), and each subframe is 1 ms.
  • the SFN number can be indicated by the master information block (MIB) information of the synchronous signal block (SSB).
  • MIB master information block
  • SSB synchronous signal block
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure.
  • the communication system may include, but is not limited to, a network device and a terminal device.
  • the number and shape of the devices shown in FIG. 1 are only for examples and do not constitute limitations to the embodiments of the present disclosure. In practical applications, two or more devices may be included. network equipment, two or more terminal equipment.
  • the communication system shown in FIG. 1 includes a network device 11 and a terminal device 12 as an example.
  • LTE long term evolution
  • 5G fifth generation
  • NR 5G new radio
  • the network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals.
  • the network device 11 may be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or a base station in other future mobile communication systems Or an access node in a wireless fidelity (WiFi) system, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network device.
  • the network device provided by the embodiments of the present disclosure may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU).
  • the structure of the network equipment such as the protocol layer of the base station, can be split, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 12 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • a terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (mobile station, MS), a mobile terminal device (mobile terminal, MT), and the like.
  • the terminal device can be a car with a communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid), wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.
  • FIG. 2 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step 21 Receive the indication information sent by the network device, wherein the indication information includes the information of the super frame number HFN.
  • the HFN information may include any one or more of the following: an HFN value and a count value COUNT.
  • the HFN value or the COUNT value in the indication information is the HFN value or the COUNT value corresponding to the PDCP data packet currently sent by the network device, respectively.
  • the network device in order to prevent a new terminal device that receives PDCP data sent by the network device from being unable to use the correct COUNT value to decrypt or verify the integrity of the PDCP data packet, the network device can send instructions to the terminal device according to certain rules. information to indicate the HFN value or the count value COUNT corresponding to the current PDCP data to the terminal device.
  • Step 22 based on the HFN information, determine the HFN value of the PDCP entity of the Packet Data Convergence Protocol.
  • the indication information received by the terminal device indicates that the value of HFN is 1.
  • the terminal device may determine that the HFN value of the PDCP entity is 1.
  • the indication information received by the terminal device indicates that the value of COUNT is 0.
  • the terminal device may determine that the HFN value of the PDCP entity is 0.
  • the indication information received by the terminal device indicates that the value of COUNT is 8.
  • the terminal equipment knows that the SN value is 0 to 7, and the SN value in the received PDCP data packet is 7, so it can be determined that the HFN value of the PDCP entity is 1.
  • the terminal device can directly use the COUNT value to decrypt or decrypt the received data packets. Integrity verification, and based on the COUNT value and the SN in the received data packet, calculate the HFN value currently used by the network device, and then determine the HFN value of the PDCP entity based on the calculated HFN value.
  • the terminal device can use the HFN value to determine the corresponding COUNT value, and then use the HFN value to determine the corresponding COUNT value.
  • Data packets are decrypted or integrity verified.
  • the terminal device may first receive the indication information sent by the network device, and then determine the HFN value of the PDCP entity according to the HFN information included in the indication information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 3 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device. As shown in Figure 3, the method may include but is not limited to the following steps:
  • Step 31 Receive indication information sent by the network device, where the indication information includes HFN information.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • Step 32 in response to satisfying the applicable conditions of the HFN information, determine the HFN value of the PDCP entity based on the HFN information.
  • the applicable conditions of the HFN information may include any one or more of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the applicable condition may be indicated by the network device, or may be determined by the terminal device according to the agreement, which is not limited in the present disclosure.
  • the network device may indicate the applicable conditions of the HFN information while indicating the HFN information to the terminal equipment, or may also indicate the applicable conditions of the HFN information to the terminal equipment through other indication information, which is not covered in this disclosure. limited.
  • the value of SN can be: the minimum value of SN.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SN is 5. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 7, since 7 is greater than the minimum value of 5 in the SN in the applicable condition, that is, the applicable condition of the HFN information is satisfied, so it can be based on the HFN value indicated by the network device.
  • the value of HFN of the PDCP entity is determined to be 1.
  • the value of SN can be: the maximum value of SN.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SN is 5. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 1, because 1 is less than the maximum value of 5 in the applicable condition, that is, the applicable condition of the HFN information is satisfied, so the HFN value indicated by the network device can be used.
  • the value of HFN of the PDCP entity is determined to be 1.
  • the value of SN can be: the minimum value and the maximum value of SN.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device when the SN value corresponding to the received PDCP data packet is greater than or equal to the minimum value and less than or equal to the maximum value.
  • the terminal device determines the applicable conditions of the HFN information according to the agreement or the instruction of the network device as follows: the minimum value of SN is 1 and the maximum value of SN is 5. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2, since 2 is greater than the minimum value of 1 in the applicable conditions and smaller than the maximum value of 5 in the applicable conditions, that is, the application of the HFN information is satisfied. conditions, so that the HFN value of the PDCP entity can be determined to be 1 based on the HFN value indicated by the network device.
  • the value of SN may be: the segment number corresponding to the value of SN.
  • the terminal device can determine the PDCP based on the HFN information indicated by the network device. The entity's HFN value.
  • segmentation method corresponding to the SN value may be a method agreed upon in the protocol.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device as follows: the segment number corresponding to the value of the SN is 1. Then, when the terminal device determines that the segment number corresponding to the SN value corresponding to the received PDCP data packet is 1, which is the same as the segment number corresponding to the SN value in the applicable condition, it satisfies the applicable condition of the HFN information, so that it can Based on the HFN value indicated by the network device, the value of the HFN of the PDCP entity is determined to be 1.
  • the value of SN can be: the parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after dividing all the values of SN in a specified order, and n is the current value of SN.
  • the value of is the segment number in m segments, where n is an integer less than or equal to m.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device when the segment number of the m segments of the SN value corresponding to the received PDCP data packet is n.
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the instruction of the network device: the parameter pair (2, 1) corresponding to the value of the SN. Then, when the terminal device determines that the segment number of the SN value corresponding to the received PDCP data packet is 1 in the two segments, it satisfies the applicable condition of the HFN information, so that the PDCP entity can be determined based on the HFN value indicated by the network device.
  • the value of HFN is 1.
  • the value of SFN can be: the minimum value of SFN.
  • the terminal device may determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SFN is 5. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 7, since 7 is greater than the minimum value of the SFN in the applicable condition, 5, that is, the applicable condition of the HFN information is satisfied, so it can be based on the HFN value indicated by the network device.
  • the value of HFN of the PDCP entity is determined to be 1.
  • the value of SFN can be: the maximum value of SFN.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SFN is 5. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 1, since 1 is less than the maximum value of SFN in the applicable condition, 5, that is, the applicable condition of the HFN information is satisfied, so the HFN value indicated by the network device can be used.
  • the value of HFN of the PDCP entity is determined to be 1.
  • the value of the SFN may be: the minimum value and the maximum value of the SFN.
  • the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device when the SFN value corresponding to the received PDCP data packet is greater than or equal to the minimum value and less than or equal to the maximum value.
  • the terminal device determines the applicable conditions of the HFN information according to the agreement or the instruction of the network device as follows: the minimum value of the SFN is 1 and the maximum value of the SFN is 5. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 2, since 2 is greater than the minimum value of SFN in the applicable conditions 1, and less than the maximum value of SFN in the applicable conditions 5, that is, it satisfies the application of HFN information. conditions, so that the HFN value of the PDCP entity can be determined to be 1 based on the HFN value indicated by the network device.
  • the value of the SFN may be: the segment number corresponding to the value of the SFN.
  • the terminal device can determine the PDCP based on the HFN information indicated by the network device. The entity's HFN value.
  • segmentation mode corresponding to the SFN value may be a protocol agreed-upon mode.
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the instruction of the network device: the segment number corresponding to the value of the SFN is 1. Then, when the terminal device determines that the segment number corresponding to the SFN value corresponding to the received PDCP data packet is 1, that is, it is the same as the segment number corresponding to the SFN value in the applicable conditions, and the applicable conditions of the HFN information are satisfied, so that it can be used. Based on the HFN value indicated by the network device, the value of the HFN of the PDCP entity is determined to be 1.
  • the value of the SFN can be: the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN in a specified order, and j is the current SFN.
  • the value of is the segment number in i segments, and j is an integer less than or equal to i.
  • the terminal device may determine the HFN value of the PDCP entity based on the HFN information indicated by the network device when the segment number of the m segments of the SFN value corresponding to the received PDCP data packet is j.
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the indication of the network device: the parameter pair (2, 1) corresponding to the value of the SFN. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet has a segment number of 1 in the two segments, it satisfies the applicable condition of the HFN information, so that the PDCP entity can be determined based on the HFN value indicated by the network device.
  • the value of HFN is 1.
  • the corresponding HFN value can be determined according to the determined applicable conditions of the HFN information and the received indication information, and then the corresponding COUNT value can be determined by using the HFN value. , perform data decryption or integrity verification on the received data packets.
  • the terminal device can first receive the HFN information and the applicable conditions of the HFN information sent by the network device, and when the applicable conditions of the HFN information are satisfied, can determine the HFN value of the PDCP entity based on the received HFN information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 4 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device. As shown in Figure 4, the method may include but is not limited to the following steps:
  • Step 41 Receive indication information sent by the network device based on the system message, where the indication information includes HFN information.
  • the terminal device may receive the indication information sent by the network device based on a system information block (system information block, SIB), for example, based on SIB1.
  • SIB system information block
  • the network device can extend the SIB1 message, so that the SIB1 can carry the indication information.
  • a specified bit may be added to the SIB1, and the HFN value and/or the COUNT value may be represented by the value of the specified bit. Therefore, when the terminal device receives the SIB1 message, it can determine the HFN value and/or the COUNT value, etc. in the indication information according to the value of the specified bit, which is not limited in the present disclosure.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • the network device can also send the indication information to the terminal device through the broadcast multicast service MBS control channel message, so that the terminal device can receive the indication information sent by the network device based on the MBS control channel message.
  • the network device can extend the MBS control channel message so that the indication information can be carried therein.
  • a designated bit may be added to the MBS control channel message, and the HFN value and/or the COUNT value may be represented by the value of the designated bit. Therefore, when the terminal device receives the MBS control channel message, it can determine the HFN value and/or COUNT value, etc. in the indication information according to the value of the specified bit, which is not limited in the present disclosure.
  • the network device may also use a dedicated configuration message of the terminal device to send indication information to the terminal device. Therefore, the terminal device can receive the indication information sent by the network device based on the dedicated configuration message of the terminal device.
  • the network device can configure the dedicated configuration message of the terminal device, so that the indication information can be carried therein.
  • a designated bit may be added to the dedicated configuration message of the terminal device, and the HFN value and/or the COUNT value may be represented by the value of the designated bit. Therefore, when the terminal device receives the dedicated configuration message, it can determine the HFN value and/or the COUNT value, etc. in the indication information according to the value of the specified bit, which is not limited in the present disclosure.
  • Step 42 when the applicable condition of the HFN information is the value of the SN, in response to not meeting the applicable condition and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN is s, based on the difference value s
  • the HFN information is updated to generate updated HFN information.
  • the applicable condition of the HFN information may be indicated by the network device, or may be determined by the terminal device according to the agreement, which is not limited in the present disclosure.
  • the value of SN can be: the minimum value of SN.
  • the terminal device may update the HFN information based on the difference value s to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SN is 3. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2, since 2 is less than the minimum value of the SN in the applicable condition, 3, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to The difference s between the SN value 2 and the SN value 3 is -1, so the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 0.
  • the value of SN can be: the maximum value of SN.
  • the terminal device may update the HFN information based on the difference value s to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SN is 3. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 4, since 4 is greater than the maximum value of 3 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to The difference s between the SN value 4 and the SN value 3 is +1, so the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 2.
  • the value of SN can be: the minimum value and the maximum value of SN.
  • the terminal device may update the HFN information based on the difference s to generate updated HFN information.
  • the terminal device determines the applicable conditions for the HFN information according to the agreement or the instruction of the network device: the minimum value of the SN is 2 and the maximum value of the SN is 5. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 6, since 6 is greater than the maximum value of 5 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to 5. The difference s between the SN value 6 and the maximum value 5 of the SN is +1, so the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 2.
  • the value of SN may be: the segment number corresponding to the value of SN.
  • the terminal device can update the HFN information based on the difference s to generate Updated HFN information.
  • segmentation method corresponding to the SN value may be a method agreed upon in the protocol.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device as follows: the segment number corresponding to the value of the SN is 1. Then, when the terminal device determines that the segment number corresponding to the SN value corresponding to the received PDCP data packet is 2, the applicable condition of the HFN information is not met, and the segment number corresponding to the SN value corresponding to the PDCP data packet received by the terminal device is 2.
  • the difference value s from the segment number 1 specified in the application condition is +1, so the HFN information is updated based on the difference value s, and the updated HFN information is generated: the HFN value is 2.
  • the value of SN can be: the parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after dividing all the values of SN in a specified order, and n is the current value of SN.
  • the value of is the segment number in m segments, where n is an integer less than or equal to m.
  • the terminal device may update the HFN information based on the difference value s when the segment number of the m segments of the SN value corresponding to the received PDCP data packet is not n, to generate updated HFN information. .
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the instruction of the network device: the parameter pair (2, 1) corresponding to the value of the SN. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2 in the segment number of the two segments, the applicable conditions of the HFN information are not met, and the SN value corresponding to the PDCP data packet received by the terminal device corresponds to The difference s between the segment number 2 of and the segment number 1 specified in the application condition is +1, so the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 2.
  • Step 43 Determine the HFN value of the PDCP entity based on the updated HFN information.
  • the terminal device may determine the updated HFN value as the HFN value of the PDCP entity.
  • the HFN value of the PDCP entity can be determined according to the determined applicable conditions of the HFN information and the received indication information, and then the corresponding COUNT can be determined by using the HFN value. Value to decrypt or verify the integrity of the received data packet.
  • the terminal device may first receive the indication information sent by the network device, and then, according to the HFN information included in the indication information and the determined value of the SN, if the value of the SN is not satisfied and the value received by the terminal device is not satisfied.
  • the HFN information is updated based on the difference s, and then the HFN value of the PDCP entity is determined based on the updated HFN information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 5 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device. As shown in Figure 5, the method may include but is not limited to the following steps:
  • Step 51 Receive indication information sent by the network device based on the MBS control channel message, where the indication information includes HFN information.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • Step 52 when the applicable condition of the HFN information is the value of SFN, in response to not meeting the applicable condition and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the value of SFN is k, based on the difference k
  • the HFN information is updated to generate updated HFN information.
  • the applicable condition of the HFN information may be indicated by the network device, or may be determined by the terminal device according to the agreement, which is not limited in the present disclosure.
  • the SFN value corresponding to the PDCP data packet received by the terminal device may include any one or more of the following: the SFN value corresponding to the time position of the last physical data channel that successfully receives the PCDP data packet; The SFN value corresponding to the time position of the first physical data channel; and the SFN value corresponding to successfully receiving the PDCP data packet.
  • the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to the time position of the last physical data channel that successfully received the PCDP data packet.
  • a terminal device receives a PDCP data packet, it needs to successfully receive the Physical Downlink Shared Channel (PDSCH) data at time t1 and PDSCH data at time t2. If time t1 is before time and time t2 is after, it can be determined that The SFN value corresponding to time t2 is the SFN value corresponding to the PDCP data packet received by the terminal device, etc., which is not limited in the present disclosure.
  • PDSCH Physical Downlink Shared Channel
  • the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to the time position of the first physical data channel that successfully received the PCDP data packet. For example, when a terminal device receives a PDCP data packet, it needs to successfully receive PDSCH data at time t1 and PDSCH data at time t2. If time t1 is before time and time t2 is after time, the SFN value corresponding to time t1 can be determined as the value received by the terminal device.
  • the SFN value corresponding to the PDCP data packet, etc., is not limited in the present disclosure.
  • the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to successfully receiving the PDCP data packet.
  • the terminal device receives the PDCP data packet, and the time when the data packet is successfully received is t3, it can be determined that the SFN value corresponding to the time t3 is the SFN value corresponding to the PDCP data packet received by the terminal device, etc. This disclosure does not do this. limited.
  • the value of SFN can be: the minimum value of SFN.
  • the terminal device may update the HFN information based on the difference k to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SFN is 3.
  • the terminal device determines that the SFN value corresponding to the received PDCP data packet is 2, because 2 is less than the minimum value of 3 in the SN in the applicable conditions, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to The difference k between the SFN value 2 and the SFN value 3 is -1, so the HFN information is updated based on the difference k to generate updated HFN information: the HFN value is 0.
  • the value of SFN can be: the maximum value of SFN.
  • the terminal device may update the HFN information based on the difference k to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SFN is 3. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 4, since 4 is greater than the maximum value of SFN 3 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to The difference k between the SFN value 4 and the SFN value 3 is +1, so the HFN information is updated based on the difference k, and the updated HFN information is generated: the HFN value is 2.
  • the value of the SFN may be: the minimum value and the maximum value of the SFN.
  • the terminal device may update the HFN information based on the difference k to generate updated HFN information.
  • the terminal device determines the applicable conditions of the HFN information according to the agreement or the instruction of the network device as follows: the minimum value of SFN is 2 and the maximum value of SFN is 5. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 6, since 6 is greater than the maximum value of SFN 5 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the PDCP data packet received by the terminal device corresponds to 5.
  • the difference k between the SFN value 6 and the maximum value 5 of the SFN is +1, so the HFN information is updated based on the difference k, and the updated HFN information is generated: the HFN value is 2.
  • the value of the SFN may be: the segment number corresponding to the value of the SFN.
  • the terminal device can update the HFN information based on the difference k when the segment number corresponding to the SFN value corresponding to the received PDCP data packet is different from the segment number corresponding to the SFN value in the applicable conditions, to generate updated HFN information.
  • segmentation mode corresponding to the SFN value may be a protocol agreed-upon mode.
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the instruction of the network device: the segment number corresponding to the value of the SFN is 1. Then, when the terminal device determines that the segment number corresponding to the SFN value corresponding to the received PDCP data packet is 2, that is, the applicable condition of the HFN information is not met, and the segment number corresponding to the SFN value corresponding to the PDCP data packet received by the terminal device is not satisfied. 2.
  • the difference k of the segment number 1 corresponding to the value of the SFN specified in the applicable condition is +1, so the HFN information is updated based on the difference k, and the updated HFN information is generated: the HFN value is 2.
  • the value of the SFN can be: the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN in a specified order, and j is the current SFN.
  • the value of is the segment number in i segments, and j is an integer less than or equal to i.
  • the terminal device may update the HFN information based on the difference k to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the protocol agreement or the indication of the network device: the parameter pair (2, 1) corresponding to the value of the SFN. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 2 in the segment number of the two segments, it does not meet the applicable conditions of the HFN information, and the SFN value corresponding to the PDCP data packet received by the terminal device corresponds to The difference k between the segment number 2 of , and the segment number 1 specified in the application condition is +1, so the HFN information is updated based on the difference k, and the updated HFN information is generated: the HFN value is 2.
  • Step 53 Determine the HFN value of the PDCP entity based on the updated HFN information.
  • the terminal device may determine the updated HFN value as the HFN value of the PDCP entity.
  • the HFN value of the PDCP entity can be determined according to the determined applicable conditions of the HFN information and the received indication information, and then the corresponding COUNT can be determined by using the HFN value. Value to decrypt or verify the integrity of the received data packet.
  • the terminal device may first receive the indication information sent by the network device, and then, according to the HFN information included in the indication information and the determined value of the SFN, if the value of the SFN is not satisfied and the value received by the terminal device
  • the HFN information can be updated based on the difference k, and then the HFN value of the PDCP entity is determined based on the updated HFN information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 6 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device. As shown in Figure 6, the method may include but is not limited to the following steps:
  • Step 61 Receive indication information sent by the network device, where the indication information includes HFN information and an update mode of the HFN information.
  • the network device when the network device indicates the HFN information to the terminal device, it can also determine the update mode of the HFN information based on the current network state, for example, according to the transmission speed of the PDCP data packet, and send the update mode to the terminal device. . This avoids the situation that the HFN information received by the terminal device is inaccurate due to the influence of the network state.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • the update mode may include update step size and update direction.
  • the update step size may be any value set by the network device, for example, may be 1, 2, 3, etc., which is not limited in the present disclosure.
  • the update direction may be any direction set by the network device, for example, it may be a "+" direction, a "-” direction, etc., which is not limited in the present disclosure. Therefore, the update mode of the HFN information may be "the HFN value indicated by the indication information+1", “the HFN value indicated by the indication information-2", “the COUNT value indicated by the indication information-1”, etc., which is not covered by the present disclosure. Do limit.
  • Step 62 in response to not meeting the applicable conditions of the HFN information, update the HFN information based on the update mode to generate updated HFN information.
  • the applicable condition of the HFN information may be indicated by the network device, or may be determined by the terminal device according to the agreement, which is not limited in the present disclosure.
  • the update mode of the HFN information indicated by the network device may be HFN value +1"; and when the PDCP data packet is sent too slowly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information.
  • the update mode of the HFN information indicated by the network device may be "indication"
  • the HFN value in the information-1", “the HFN value in the indication information-2", etc., are not limited in the present disclosure.
  • the applicable condition of HFN information is: the minimum value of SN.
  • the terminal device may update the HFN information based on the update mode to generate updated HFN information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SN is 3. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2, since 2 is less than the minimum value of 3 in the applicable condition, that is, the applicable condition of the HFN information is not met, so the terminal device can perform the HFN information. Update, the updated HFN value is 0.
  • the applicable condition of the HFN information is: the maximum value of the SFN.
  • the terminal device may update the HFN information based on the update mode to generate updated HFN information.
  • the indication information received by the terminal device is: the HFN value is 1, and the HFN value in the indication information is +1.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SFN is 3. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 4, since 4 is greater than the maximum value 3 of the SFN in the applicable condition, that is, the applicable condition of the HFN information is not satisfied. Therefore, the terminal device can update the HFN information, and the updated HFN value is 2.
  • Step 63 Determine the HFN value of the PDCP entity based on the updated HFN information.
  • the updated HFN value may be determined as the HFN value of the PDCP entity.
  • the HFN value of the PDCP entity can be determined according to the determined applicable conditions of the HFN information and the received indication information, and then the corresponding COUNT can be determined by using the HFN value. Value to decrypt or verify the integrity of the received data packet.
  • the terminal device may first receive the HFN information sent by the network device, and then, according to the HFN information included in the indication information and the determined applicable conditions of the HFN information, when the applicable conditions of the HFN information are not met, the terminal equipment may update the HFN information based on the HFN information.
  • the mode updates the HFN information to generate updated HFN information, and then determines the HFN value of the PDCP entity. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 7 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a terminal device.
  • the method may include but is not limited to the following steps:
  • Step 71 Receive indication information sent by the network device, where the indication information includes HFN information and MBS service information.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • the MBS service information may include at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of an MBS bearer protocol entity.
  • the MBS service identifier may include Temporary Mobile Group Identity (TMGI), MBS Session ID (MBS Session ID), MBS Service Flow ID (MBS QoS flow ID), etc., which are not limited in this disclosure .
  • TMGI Temporary Mobile Group Identity
  • MBS Session ID MBS Session ID
  • MBS Service Flow ID MBS Service Flow ID
  • the style or presentation form of the MBS bearer identification may be a protocol agreement or a network device configuration, such as MRB-1, MRB-2, etc., which is not limited in the present disclosure.
  • the configuration information of the protocol entity carried by the MBS may be PDCP configuration information, which may include: PDCP SN length, or data packet header compression configuration, or whether integrity detection is required, and so on.
  • the configuration information of the protocol entity carried by the MBS may also be a radio link control (Radio Link Control, RLC) configuration, which may include: PDCP SN length, RLC working mode indication, and the like.
  • RLC Radio Link Control
  • the configuration information of the protocol entity carried by the MBS may also be a MAC configuration, which may include a logical channel identifier, etc., which is not limited in the present disclosure.
  • Step 72 based on the HFN information, determine the HFN value of the PDCP entity corresponding to the MBS service information.
  • the indication information received by the terminal device indicates that: for the radio bearer MRB-1, the HFN value is 1. Afterwards, the terminal device may determine that the HFN value of the PDCP entity corresponding to the radio bearer MRB-1 is 1, etc., which is not limited in the present disclosure.
  • the terminal device may also determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information when the SN value corresponding to the received PDCP data packet satisfies the applicable condition of the HFN information.
  • the value of SN can be: the minimum value of SN.
  • the terminal device can determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information indicated by the network device.
  • the PDCP data packet received by the terminal device may be the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the minimum value of the SN is 5.
  • the PDCP data packet received by the terminal device may be the first PDCP data packet received by the terminal device from the radio bearer MRB-1, so when the terminal device determines that the SN value corresponding to the PDCP data packet is 7, since 7 is greater than the applicable condition
  • the minimum value of the SN in is 5, that is, the applicable condition of the HFN information is satisfied, so the HFN value of the PDCP entity corresponding to the radio bearer MRB-1 can be determined to be 1 based on the HFN value indicated by the network device.
  • the terminal device may further determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information when the SFN value corresponding to the received PDCP data packet satisfies the applicable condition of the HFN information.
  • the value of SFN may be: the maximum value of SFN.
  • the terminal device can determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information indicated by the network device.
  • the indication information received by the terminal device is: the HFN value is 1, and the radio bearer corresponding to the MBS service information is MRB-1.
  • the terminal device determines the applicable condition of the HFN information according to the agreement or the instruction of the network device: the maximum value of the SFN is 5. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 1, since 1 is less than the maximum value of SFN in the applicable condition, 5, that is, the applicable condition of the HFN information is satisfied, so the HFN value indicated by the network device can be used. It is determined that the value of the HFN of the PDCP entity corresponding to the radio bearer MRB-1 is 1.
  • the specific content and implementation manner of determining the HFN value of the PDCP entity corresponding to the MBS service information may refer to the descriptions of other embodiments of the present disclosure. It will not be repeated here.
  • the HFN value of the PDCP entity corresponding to the MBS service information may be determined based on the HFN information.
  • the terminal device can determine the PDCP entity corresponding to the radio bearer MRB-1
  • the HFN value are not limited in the present disclosure.
  • Step 73 Decrypt or verify the integrity of the received data corresponding to the MBS service information based on the HFN information.
  • the terminal device determines that the HFN value of the PDCP entity corresponding to the radio bearer MRB-1 is 1, and then can use the HFN value to determine the corresponding COUNT value, and then decrypt the received data corresponding to the radio bearer MRB-1. or integrity verification, etc., which are not limited in the present disclosure.
  • the terminal device can first receive the indication information sent by the network device, and then determine the HFN value of the PDCP entity corresponding to the MBS service information according to the HFN information and the MBS service information included in the indication information, and then can compare the HFN value of the PDCP entity corresponding to the MBS service information.
  • the received data corresponding to the MBS service information is decrypted or integrity verified. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 8 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a network device. As shown in Figure 8, the method may include but is not limited to the following steps:
  • Step 81 Send indication information to the terminal device, wherein the indication information includes the information of the super frame number HFN.
  • the HFN information may include any one or more of the following: HFN value and COUNT value.
  • the network device may send indication information to the terminal device based on the system message, where the indication information includes HFN information.
  • the network device can extend the SIB1 message, so that the SIB1 can carry the indication information.
  • a designated bit may be added to the SIB1, and the value of the designated bit may be used to represent the HFN value and/or the COUNT value, etc., which is not limited in the present disclosure.
  • the network device may also send indication information to the terminal device based on the broadcast multicast service MBS control channel message.
  • the network device can extend the MBS control channel message so that the indication information can be carried therein.
  • a specified bit may be added to the MBS control channel message, and the value of the specified bit may be used to represent the HFN value and/or the COUNT value, etc., which is not limited in the present disclosure.
  • the network device may also send indication information to the terminal device based on a dedicated configuration message of the terminal device.
  • the network device can configure the dedicated configuration message of the terminal device, so that the indication information can be carried therein.
  • a specified bit may be added to the dedicated configuration message of the terminal device, and the HFN value and/or the COUNT value, etc. may be represented by the value of the specified bit, which is not limited in the present disclosure.
  • the network device can send indication information to the terminal device, so that the terminal device can receive the HFN information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 9 is a schematic flowchart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, where the method is configured to be executed by a network device.
  • the method may include but is not limited to the following steps:
  • Step 91 based on the system message, send indication information to the terminal device, wherein the indication information includes HFN information.
  • the network device can extend the SIB1 message, so that the SIB1 can carry the indication information.
  • a designated bit may be added to the SIB1, and the value of the designated bit may be used to represent the HFN value and/or the COUNT value, etc., which is not limited in the present disclosure.
  • the HFN information includes any one or more of the following: HFN value and COUNT value.
  • Step 92 Send the applicable conditions of the HFN information to the terminal device.
  • the applicable conditions of the HFN information may include any one or more of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of SN may include any one or more of the following: the minimum value of SN; the maximum value of SN; the minimum value and maximum value of SN; the segment number corresponding to the value of SN; and the corresponding value of SN
  • the parameter pair (m, n) of where m is the number of segments after dividing all the values of SN in the specified order, and n is the segment number of the current value of SN in the m segments, n is an integer less than or equal to m.
  • the value of the SFN includes any one or more of the following: the minimum value of the SFN; the maximum value of the SFN; the minimum value and the maximum value of the SFN; the segment number corresponding to the value of the SFN; and the value of the SFN
  • the indication information may further include MBS service information.
  • the MBS service information may include at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the indication information may further include an update mode of the HFN information.
  • the update mode includes an update step size and an update direction.
  • the update step size may be a value set by the network device according to the speed of sending the PDCP data packet, which may be any value, such as 1, 2, 3, etc., which is not limited in the present disclosure.
  • the update direction may be any direction set by the network device, for example, it may be a "+" direction, a "-" direction, etc., which is not limited in the present disclosure.
  • the update mode of the HFN information indicated by the network device may be "HFN indicated by the indication information" value +1"; and when the PDCP data packet is sent too slowly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information.
  • the update mode of the HFN information indicated by the network device may be "Indication information HFN value-1" in the "indication information-1", "HFN value in the indication information-2", etc., which are not limited in the present disclosure.
  • Step 93 in response to any information change in the system message except the HFN information, send first change indication information to the terminal device.
  • the network device when the network device sends the indication information to the terminal device through the system message, it can send the first change indication information to the terminal device when any information other than the HFN information in the system message is changed. . Therefore, the change of the HFN value in the system message will not cause the network device to send the first change instruction information to the terminal device, thereby reducing data transmission, enabling the terminal device and the network device to keep a consistent understanding of the HFN value, ensuring that data Transmission reliability.
  • the network device may also send the second change indication information to the terminal device when any information other than the HFN information in the MBS control channel message is changed. Therefore, the change of the HFN value in the MBS control channel message will not cause the network device to send the second change indication information to the terminal device, thereby reducing data transmission, enabling the terminal device and the network device to maintain a consistent understanding of the HFN value, ensuring that reliability of data transmission.
  • the network device can send indication information to the terminal device based on the system message, so that the terminal device can receive the HFN information, and can also send the applicable conditions of the HFN information to the terminal device, and remove the HFN information in the system message.
  • the first change instruction information is sent to the terminal device. In this way, the terminal device and the network device can keep a consistent understanding of the value of HFN, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • the methods provided by the embodiments of the present disclosure are respectively introduced from the perspectives of network devices and terminal devices.
  • the network device and the terminal device may include hardware structures and software modules, and implement the above functions in the form of hardware structures, software modules, or hardware structures plus software modules.
  • a certain function among the above functions may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 10 is a schematic structural diagram of a communication apparatus 100 according to an embodiment of the present disclosure.
  • the communication device 100 shown in FIG. 10 may include a transceiver module 1001 and a processing module 1002 .
  • the transceiver module 1001 may include a sending module and/or a receiving module, the sending module is used to implement the sending function, the receiving module is used to implement the receiving function, and the transceiver module 1001 may implement the sending function and/or the receiving function.
  • the communication apparatus 100 may be a terminal device, a device in a terminal device, or a device that can be matched and used with the terminal device.
  • the communication apparatus 100 is configured on the terminal device side, and the apparatus includes:
  • the transceiver module 1001 is configured to receive indication information sent by a network device, wherein the indication information includes super frame number HFN information.
  • the processing module 1002 is configured to determine the HFN value of the Packet Data Convergence Protocol PDCP entity based on the HFN information.
  • the HFN information includes any one or more of the following: an HFN value and a count value COUNT.
  • the processing module 1002 is specifically configured to: in response to satisfying the applicable condition of the HFN information, determine the HFN value of the PDCP entity based on the HFN information.
  • the transceiver module 1001 is further configured to receive the applicable conditions of the HFN information sent by the network device;
  • the processing module 1002 is further configured to determine the applicable condition of the HFN information based on the agreement.
  • the applicable conditions of the HFN information include any one or more of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any one or more of the following:
  • the value of the SFN includes any one or more of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the meeting the applicable conditions includes:
  • the SN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition
  • the SFN value corresponding to the PDCP data packet received by the terminal device satisfies the applicable condition.
  • the indication information further includes MBS service information
  • the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.
  • the SFN value corresponding to the received PDCP data packet includes any one or more of the following:
  • the SFN value corresponding to the time position of the first physical data channel that successfully receives the PCDP data packet
  • the SFN value corresponding to the PDCP data packet is successfully received.
  • the applicable condition is the value of SN
  • the processing module 1002 is specifically used for:
  • the HFN information is updated based on the difference value s, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the applicable condition is the value of SFN
  • the processing module 1002 is specifically used for:
  • the HFN information is updated based on the difference k, to generate updated HFN information
  • the HFN value of the PDCP entity is determined.
  • the indication information further includes an update mode of the HFN information
  • the processing module 1002 is specifically configured to:
  • the HFN value of the PDCP entity is determined.
  • the update mode includes an update step size and an update direction.
  • the transceiver module 1001 is specifically used for:
  • the indication information sent by the network device is received.
  • the indication information further includes MBS service information
  • the processing module 1002 is specifically configured to: determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information.
  • the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of a protocol entity of the MBS bearer.
  • the processing module 1002 is further configured to decrypt or verify the integrity of the received data corresponding to the MBS service information based on the HFN information.
  • the processing module 1002 is specifically configured to determine the HFN value of the PDCP entity based on the HFN information in response to the terminal device being a device newly accessing the MBS service.
  • the terminal device can first receive the indication information sent by the network device, and then determine the HFN value of the PDCP entity according to the HFN information included in the indication information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 11 is a schematic structural diagram of a communication apparatus 110 according to an embodiment of the present disclosure.
  • the communication device 110 shown in FIG. 11 may include a transceiver module 1101 .
  • the transceiver module 1101 may include a sending module and/or a receiving module, the sending module is used to implement the sending function, the receiving module is used to implement the receiving function, and the transceiver module 1101 may implement the sending function and/or the receiving function.
  • the communication device 110 may be a network device, a device in a network device, or a device that can be matched and used with the network device.
  • the communication apparatus 110 is configured on the network device side, and the apparatus includes:
  • the transceiver module 1101 is configured to send indication information to the terminal device, wherein the indication information includes the information of the super frame number HFN.
  • the HFN information includes any one or more of the following: an HFN value and a count value COUNT.
  • the transceiver module is further configured to send the applicable conditions of the HFN information to the terminal device.
  • the applicable conditions of the HFN information include any one or more of the following: the value of the sequence number SN and the value of the system frame number SFN.
  • the value of the SN includes any one or more of the following:
  • the value of the SFN includes any one or more of the following:
  • the parameter pair (i, j) corresponding to the value of the SFN, where i is the number of segments after dividing all the values of the SFN equally in the specified order, and j is the current value of the SFN in the i segments
  • the segment number of , j is an integer less than or equal to i.
  • the indication information further includes MBS service information.
  • the MBS service information includes at least one or more of the following: an MBS service identifier, an MBS bearer identifier, and configuration information of an MBS bearer protocol entity.
  • the indication information further includes an update mode of the HFN information.
  • the update mode includes an update step size and an update direction.
  • the transceiver module 1101 is specifically used for:
  • the indication information is sent to the terminal device.
  • the transceiver module 1101 is further configured to:
  • second change indication information is sent to the terminal device.
  • the network device can send indication information to the terminal device, so that the terminal device can receive the HFN information. Therefore, the terminal device and the network device can keep a consistent understanding of the HFN value, avoid data decryption failure or integrity verification failure, and improve the reliability of data transmission.
  • FIG. 12 is a schematic structural diagram of another communication apparatus 120 provided by an embodiment of the present disclosure.
  • the communication device 120 may be a network device, a terminal device, a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a chip that supports the terminal device to implement the above method. processor etc.
  • the apparatus can be used to implement the methods described in the foregoing method embodiments, and for details, reference may be made to the descriptions in the foregoing method embodiments.
  • the Communication device 120 may include one or more processors 1201 .
  • the processor 1201 may be a general-purpose processor or a special-purpose processor, or the like.
  • it may be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.), execute computer programs, etc. , which processes data from computer programs.
  • the communication apparatus 120 may further include one or more memories 1202 on which a computer program 1204 may be stored, and the processor 1201 executes the computer program 1204, so that the communication apparatus 120 executes the methods described in the foregoing method embodiments. method.
  • the memory 1202 may also store data.
  • the communication device 120 and the memory 1202 can be provided separately or integrated together.
  • the communication device 120 may further include a transceiver 1205 and an antenna 1206 .
  • the transceiver 1205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1205 may include a receiver and a transmitter, the receiver may be called a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be called a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the communication device 120 may further include one or more interface circuits 1207 .
  • the interface circuit 1207 is used to receive code instructions and transmit them to the processor 1201 .
  • the processor 1201 executes the code instructions to cause the communication device 120 to perform the methods described in the above method embodiments.
  • the communication device 120 is a terminal device: the processor 1201 is configured to execute step 22 in FIG. 2 ; execute step 32 in FIG. 3 ; step 42 in FIG. 4 ; step 43 in FIG. 4 ; step 52 in FIG. 5 ; Step 53 in Figure 5; Step 62 in Figure 6; Step 63 in Figure 6; Step 72 in Figure 7; or Step 73 in Figure 7.
  • the transceiver 1205 is configured to perform step 21 in FIG. 2 ; step 31 in FIG. 3 ; step 41 in FIG. 4 ; step 51 in FIG. 5 ; step 61 in FIG. 6 ; or step 71 in FIG. 7 .
  • the communication apparatus 120 is a network device: the transceiver 1205 is configured to perform step 81 in FIG. 8 ; step 91 in FIG. 9 ; step 92 in FIG. 9 ; or step 93 in FIG. 9 .
  • the processor 1201 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • Transceiver circuits, interfaces or interface circuits used to implement receiving and transmitting functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transmission.
  • the processor 1201 may store a computer program 1203, and the computer program 1203 runs on the processor 1201 to enable the communication device 120 to execute the methods described in the above method embodiments.
  • the computer program 1203 may be embodied in the processor 1201, in which case the processor 1201 may be implemented by hardware.
  • the communication apparatus 120 may include a circuit, and the circuit may implement the function of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 12 .
  • the communication apparatus may be a stand-alone device or may be part of a larger device.
  • the communication means may be:
  • the IC set can also include a storage component for storing data and computer programs;
  • ASIC such as modem (Modem);
  • the communication device may be a chip or a chip system
  • the chip shown in FIG. 13 includes a processor 1301 and an interface 1302 .
  • the number of processors 1301 may be one or more, and the number of interfaces 1302 may be multiple.
  • the interface 1302 is used to perform step 21 in FIG. 2 ; perform step 31 in FIG. 3 ; step 41 in FIG. 4 ; step 51 in FIG. 5 ; step 61 in FIG. 6 ; or step 71 in FIG. 7 .
  • the interface 1302 is used to execute step 81 in FIG. 8 ; step 91 in FIG. 9 ; step 92 in FIG. 9 ; or step 93 in FIG. 9 .
  • the chip further includes a memory 1303 for storing necessary computer programs and data.
  • An embodiment of the present disclosure further provides a communication system, where the system includes the communication apparatus as the terminal device in the foregoing embodiment in FIG. 10 and the communication apparatus as the network device in the embodiment in FIG. 11 , or the system includes the communication apparatus in the foregoing embodiment in FIG. 12 .
  • the present disclosure also provides a computer-readable storage medium on which instructions are stored, and when the instructions are executed by a computer, implement the functions of any of the foregoing method embodiments.
  • the present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when the computer program product is executed by a computer.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer program may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state disks, SSD)) etc.
  • At least one in the present disclosure may also be described as one or more, and the plurality may be two, three, four or more, which is not limited by the present disclosure.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C”, and “D”, etc.
  • the technical features described in the “first”, “second”, “third”, “A”, “B”, “C” and “D” described technical features in no order or order of magnitude.
  • the corresponding relationships shown in each table in the present disclosure may be configured or predefined.
  • the values of the information in each table are only examples, and can be configured with other values, which are not limited in the present disclosure.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, for example, splitting, merging, and so on.
  • the names of the parameters shown in the headings in the above tables may also adopt other names that can be understood by the communication device, and the values or representations of the parameters may also be other values or representations that the communication device can understand.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Wait.
  • Predefined in the present disclosure may be understood as defining, predefining, storing, prestoring, prenegotiating, preconfiguring, curing, or prefiring.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例公开了一种分组数据汇聚协议实体的超帧号确定的方法及其装置，可应用于通信技术领域，其中，被配置为由终端设备执行的方法包括：接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息；基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。

Description

一种分组数据汇聚协议实体的超帧号确定方法及其装置 技术领域
本公开涉及通信技术领域，尤其涉及一种分组数据汇聚协议实体的超帧号确定方法及其装置。
背景技术
在通信系统中，网络设备在不停的发送数据，因此，网络设备所采用的超帧号(hyperframenumber，HFN)的数值在不停的增加。当有终端设备新加入进来接收网络设备发送的数据时，终端设备并不知道网络设备采用的HFN值，从而会导致终端设备无法采用正确的计数值(COUNT)对接收的数据进行解密或完整性验证，导致数据的解密失败或完整性验证失败。
发明内容
本公开实施例提供一种分组数据汇聚协议实体的超帧号确定方法及其装置，可应用于通信技术领域中。
第一方面，本公开实施例提供一种分组数据汇聚协议实体的超帧号确定方法，所述方法被配置为由终端设备执行，该方法包括：接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息；基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。
在该方案中，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息，确定出PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
可选的，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
可选的，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：响应于满足所述HFN信息的适用条件，基于所述HFN信息，确定所述PDCP实体的HFN值。
可选的，还包括：
接收所述网络设备发送的所述HFN信息的适用条件；
或者，
基于协议约定，确定所述HFN信息适用条件
可选的，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述满足所述适用条件包括：
所述终端设备接收的PDCP数据包对应的SN值满足所述适用条件；
或者，
所述终端设备接收的PDCP数据包对应的SFN值满足所述适用条件。
可选的，所述指示信息中还包括MBS业务信息，所述接收的PDCP数据包为所述终端设备从所述MBS业务信息对应的无线承载MRB中接收的第一个PDCP数据包。
可选的，所述接收的PDCP数据包对应的SFN值包括以下任一项：
成功接收所述PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值；
成功接收所述PCDP数据包的第一个物理数据信道的时间位置对应的SFN值；以及
成功接收所述PDCP数据包对应的SFN值。
可选的，所述适用条件为SN的取值，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SN值与所述SN的取值的差值为s，基于所述差值s对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述适用条件为SFN的取值，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SFN值与所述SFN的取值的差值为k，基于所述差值k对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述指示信息中还包括所述HFN信息的更新模式，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
响应于未满足所述适用条件，基于所述更新模式对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述接收网络设备发送的指示信息，包括：
基于系统消息，接收所述网络设备发送的指示信息；
或者，
基于广播多播业务MBS控制信道消息，接收所述网络设备发送的指示信息；
或者，
基于所述终端设备的专属配置消息，接收所述网络设备发送的指示信息。
可选的，所述指示信息中还包括MBS业务信息，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
基于所述HFN信息，确定与所述MBS业务信息对应的PDCP实体的HFN值。
可选的，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，还包括：基于所述HFN信息，对与所述MBS业务信息对应的接收数据进行解密或完整性验证。
可选的，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：响应于所述终端设备为新接入MBS业务的设备，基于所述HFN信息，确定所述PDCP实体的HFN值。
第二方面，本公开实施例提供另一种分组数据汇聚协议实体的超帧号确定方法，所述方法被配置为由网络设备执行，该方法包括：向终端设备发送指示信息，其中，所述指示信息中包括超帧号HFN信息。
可选的，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
可选的，所述指示信息中还包括所述HFN信息的适用条件。
可选的，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述指示信息中还包括MBS业务信息。
可选的，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，所述指示信息中还包括所述HFN信息的更新模式。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述向终端设备发送指示信息，包括：
基于系统消息，向所述终端设备发送指示信息；
或者，
基于广播多播业务MBS控制信道消息，向所述终端设备发送指示信息；
或者，
基于所述终端设备的专属配置消息，向所述终端设备发送指示信息。
可选的，还包括：
响应于所述系统消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第一变更指示信息；
或者，
响应于所述MBS控制信道消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第二变更指示信息。
第三方面，本公开实施例提供一种通信装置，所述装置被配置在终端设备侧，所述装置，包括：收发模块，用于接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息；处理模块，用于基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。
可选的，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
可选的，所述处理模块，具体用于响应于满足所述HFN信息的适用条件，基于所述HFN信息，确定所述PDCP实体的HFN值。
可选的，所述收发模块，还用于接收所述网络设备发送的所述HFN信息的适用条件；
或者，
所述处理模块，还用于基于协议约定，确定所述HFN信息的适用条件。
可选的，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述满足所述适用条件包括：
所述终端设备接收的PDCP数据包对应的SN值满足所述适用条件；
或者，
所述终端设备接收的PDCP数据包对应的SFN值满足所述适用条件。
可选的，所述指示信息中还包括MBS业务信息，所述接收的PDCP数据包为所述终端设备从所述MBS业务信息对应的无线承载MRB中接收的第一个PDCP数据包。
可选的，所述接收的PDCP数据包对应的SFN值包括以下任一项：
成功接收所述PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值；
成功接收所述PCDP数据包的第一个物理数据信道的时间位置对应的SFN值；以及
成功接收所述PDCP数据包对应的SFN值。
可选的，所述适用条件为SN的取值，所述处理模块，具体用于：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SN值与所述SN的取值的差值为s，基于所述差值s对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述适用条件为SFN的取值，所述处理模块，具体用于：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SFN值与所述SFN的取值的差值为k，基于所述差值k对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述指示信息中还包括所述HFN信息的更新模式，所述处理模块，具体用于：
响应于未满足所述适用条件，基于所述更新模式对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述收发模块，具体用于：
基于系统消息，接收所述网络设备发送的指示信息；
或者，
基于广播多播业务MBS控制信道消息，接收所述网络设备发送的指示信息；
或者，
基于所述终端设备的专属配置消息，接收所述网络设备发送的指示信息。
可选的，所述指示信息中还包括MBS业务信息，所述处理模块，具体用于：
基于所述HFN信息，确定与所述MBS业务信息对应的PDCP实体的HFN值。
可选的，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，所述处理模块，还用于基于所述HFN信息，对与所述MBS业务信息对应的接收数据进行解密或完整性验证。
可选的，所述处理模块，具体用于：
响应于所述终端设备为新接入MBS业务的设备，基于所述HFN信息，确定所述PDCP实体的HFN值。
第四方面，本公开实施例提供另一种通信装置，所述装置被配置在网络设备侧，所述装置，包括：收发模块，用于向终端设备发送指示信息，其中，所述指示信息中包括超帧号HFN信息。
可选的，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
可选的，所述收发模块，还用于向所述终端设备发送所述HFN信息的适用条件。
可选的，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述指示信息中还包括MBS业务信息。
可选的，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，所述指示信息中还包括所述HFN信息的更新模式。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述收发模块，具体用于：
基于系统消息，向所述终端设备发送指示信息；
或者，
基于广播多播业务MBS控制信道消息，向所述终端设备发送指示信息；
或者，
基于所述终端设备的专属配置消息，向所述终端设备发送指示信息。
可选的，所述收发模块，还用于：
响应于所述系统消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第一变更指示信息；
或者，
响应于所述MBS控制信道消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第二变更指示信息。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种通信系统，该系统包括第三方面所述的通信装置以及第四方面所述的通信装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述网络设备所用的指令，当所述指令被执行时，使所述网络设备执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存网络设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种通信系统的架构示意图；
图2是本公开一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图3是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图4是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图5是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图6是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图7是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图8是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图9是本公开另一实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图；
图10是本公开一实施例的通信装置的结构示意图；
图11是本公开另一实施例的通信装置的结构示意图；
图12是本公开另一实施例的通信装置的结构示意图；
图13是本公开一实施例的芯片的结构示意图。
具体实施方式
为了便于理解，首先介绍本公开涉及的术语。
1、多媒体广播多播业务(multimedia broadcast and multicast service，MBMS)或广播多播业务(multicast broadcast service，MBS)
MBS是一种实用的提高频谱使用效率的技术，广泛应用于通信系统中。在5G新无线接入技术(radio access technology,RAT)系统中，MBS业务可以通过物理下行控制信道(physical downlink control dhannel，PDCCH)调度的物理下行共享信道(physical downlink shared channel，PDSCH)发送。
2、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)
PDCP是一个无线传输协议栈，它可以处理无线资源控制(radio resource control，RRC)消息以及因特网协议(internet protocol，IP)包。它可以进行IP头压缩和解压、传输用户数据并维护无线承载的序列号(sequence number,SN)，还可以提供信令传输服务，并实现信令的加密和一致性保护，以及在反方向上实现信令的解密和一致性检查。
3、加密和完整性保护
通信系统可以对发送的数据进行加密处理和完整性保护。通常，可以在PDCP数据包的末尾添加32比特位(bit)的用于完整性保护的消息验证码(message authentication code for integrity，MAC-I)实现完整性保护功能。
通常，PDCP接收实体需要知道PDCP的COUNT值才能对加密数据进行解密，或对数据进行完整性验证。
其中，PDCP的COUNT值可以由HFN和PDCP的SN两个部分共同组成，共32bit。通常，PDCP数据包的包头携带了PDCP的SN号。
4、系统帧号(system frame number，SFN)
通信系统中，可以将时域资源按照10毫秒(millisecond，ms)粒度的SFN进行连续编号。1个SFN中可以包含有10个子帧(subframe)，每个subframe是1ms。SFN编号可以通过同步信号块(synchronous signal block,SSB)的主信息块(master information block，MIB)信息进行指示。
为了更好的理解本公开实施例公开的一种分组数据汇聚协议实体的超帧号确定的方法，下面首先对本公开实施例适用的通信系统进行描述。
请参见图1，图1为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个网络设备11和一个终端设备12为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的网络设备11是网络侧的一种用于发射或接收信号的实体。例如，网络设备11可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对网络设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备12是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本公开所提供的分组数据汇聚协议实体的超帧号确定方法及其装置进行详细地介绍。
请参见图2，图2是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图2所示，该方法可以包括但不限于如下步骤：
步骤21，接收网络设备发送的指示信息，其中，指示信息中包括超帧号HFN信息。
可选的，HFN信息可以包括以下任一项或多项：HFN值及计数值COUNT。
可以理解的是，指示信息中的HFN值或COUNT值，分别为网络设备当前发送的PDCP数据包对应的HFN值或COUNT值。
本公开中，为了避免新加入接收网络设备发送的PDCP数据的终端设备，无法采用正确的COUNT值对PDCP数据包进行解密或者完整性校验，网络设备可以按照一定的规则，向终端设备发送指示信息，以向终端设备指示当前的PDCP数据对应的HFN值或计数值COUNT。
步骤22，基于HFN信息，确定分组数据汇聚协议PDCP实体的HFN值。
举例来说，终端设备接收的指示信息指示：HFN的值为1。之后，终端设备则可以确定PDCP实体的HFN值为1。
或者,终端设备接收的指示信息指示：COUNT的值为0。之后，终端设备则可以确定PDCP实体的HFN值为0。
或者，终端设备接收的指示信息指示：COUNT的值为8。而终端设备已知SN的取值为0至7，且接收到的PDCP数据包中的SN值为7，则可以确定PDCP实体的HFN值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息内容、HFN值、COUNT值等的限定。
可选的，对于新接入的终端设备而言，当其接收到的指示信息指示的是COUNT值的情况下，该终端设备即可直接利用该COUNT值对接收的数据包进行数据的解密或完整性验证，并基于该COUNT值及接收的数据包中的SN，计算网络设备当前采用的HFN值，然后基于计算得到的HFN值，确定PDCP实体的HFN值。
可选的，对于新接入的终端设备而言，当其接收到的指示信息指示的是HFN值的情况下，该终端设备可以利用该HFN值确定出对应的COUNT值，之后再对接收的数据包进行数据的解密或完整性验证。
本公开实施例，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息，确定出PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图3，图3是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图3所示，该方法可以包括但不限于如下步骤：
步骤31，接收网络设备发送的指示信息，其中，指示信息中包括HFN信息。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
步骤32，响应于满足HFN信息的适用条件，基于HFN信息，确定PDCP实体的HFN值。
可选的，HFN信息的适用条件可以包括以下任一项或多项：序列号SN的取值及系统帧号SFN的取值。
可选的，该适用条件，可以是网络设备指示的，还可以是终端设备根据协议约定确定的，本公开对此不做限定。
其中，网络设备可以在向终端设备指示HFN信息的同时，指示该HFN信息的适用条件，或者，还可以通过其他的指示信息，向终端设备单独指示HFN信息的适用条件，本公开对此不做限定。
可选的，SN的取值可以为：SN的最小值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值大于或等于该最小值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
举例来说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为5。则终端设备在确定收到的PDCP数据包对应的SN值为7时，由于7大于适用条件中的SN的最小值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值等的限定。
可选的，SN的取值可以为：SN的最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值小于或等于该最大值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SN值为1时，由于1小于适用条件中的SN的最大值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最大值等的限定。
可选的，SN的取值可以为：SN的最小值及最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值大于或等于该最小值、且小于或等于该最大值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为1及SN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SN值为2时，由于2大于适用条件中的SN的最小值1、且小于适用条件中的SN的最大值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值、SN的最大值等的限定。
可选的，SN的取值可以为：SN的取值对应的分段编号。相应的，终端设备可以在接收的PDCP数据包对应的SN值对应的分段编号与适用条件中的SN的取值对应的分段编号相同时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
可以理解的是，SN值对应的分段方式,可以为协议约定好的方式。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的取值对应的分段编号为1。则终端设备在确定收到的PDCP数据包对应的SN值对应的分段编号为1，与适用条件中的SN的取值对应的分段编号相同时，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN值对应的分段编号等的限定。
可选的，SN的取值可以为：SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在m个分段中的分段编号，n为小于或等于m的整数。
相应的，终端设备可以在接收的PDCP数据包对应的SN值在m个分段中的分段编号为n时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的取值对应的参数对(2,1)。则终端设备在确定收到的PDCP数据 包对应的SN值在2个分段中的分段编号为1时，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、m的取值、n的取值等的限定。
可选的，SFN的取值可以为：SFN的最小值。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值大于或等于该最小值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
举例来说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最小值为5。则终端设备在确定收到的PDCP数据包对应的SFN值为7时，由于7大于适用条件中的SFN的最小值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最小值等的限定。
可选的，SFN的取值可以为：SFN的最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值小于或等于该最大值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SFN值为1时，由于1小于适用条件中的SFN的最大值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最大值等的限定。
可选的，SFN的取值可以为：SFN的最小值及最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值大于或等于该最小值、且小于或等于该最大值时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最小值为1及SFN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SFN值为2时，由于2大于适用条件中的SFN的最小值1、且小于适用条件中的SFN的最大值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最小值、SFN的最大值等的限定。
可选的，SFN的取值可以为：SFN的取值对应的分段编号。相应的，终端设备可以在接收的PDCP数据包对应的SFN值对应的分段编号与适用条件中的SFN的取值对应的分段编号相同时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
可以理解的是，SFN值对应的分段方式,可以为协议约定好的方式。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的取值对应的分段编号为1。则终端设备在确定收到的PDCP数据包对应的SFN值对应的分段编号为1时，即与适用条件中的SFN的取值对应的分段编号相同，满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN值对应的分段编号等的限定。
可选的，SFN的取值可以为：SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在i个分段中的分段编号，j为小于或等于i的整数。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值在m个分段中的分段编号为j时，即可基于网络设备指示的HFN信息，确定PDCP实体的HFN值。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的取值对应的参数对(2,1)。则终端设备在确定收到的PDCP数据包对应的SFN值在2个分段中的分段编号为1时，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、i的取 值、j的取值等的限定。
可选的，对于新接入的终端设备而言，可以根据确定出的HFN信息的适用条件以及接收到的指示信息，确定出对应的HFN值，之后再利用该HFN值确定出对应的COUNT值，对接收的数据包进行数据的解密或完整性验证。
本公开实施例，终端设备可以先接收网络设备发送的HFN信息及HFN信息的适用条件，在满足HFN信息的适用条件时，可以基于接收的HFN信息，确定PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图4，图4是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图4所示，该方法可以包括但不限于如下步骤：
步骤41，基于系统消息，接收网络设备发送的指示信息，其中，指示信息中包括HFN信息。
比如，终端设备可以基于系统信息块(systeminformationblock，SIB)，比如基于SIB1接收网络设备发送的指示信息。
可以理解的是，本公开中，网络设备可以对SIB1消息进行扩展，以使SIB1中可以携带指示信息。比如，可以在SIB1中增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值。从而终端设备在接收到SIB1消息时，根据指定比特位的取值，即可确定出指示信息中HFN值和/或COUNT值等等，本公开对此不做限定。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
可选的，网络设备还可以通过广播多播业务MBS控制信道消息向终端设备发送指示信息，从而终端设备可以基于MBS控制信道消息，接收网络设备发送的指示信息。
可以理解的是，本公开中，网络设备可以对MBS控制信道消息进行扩展，以使其中可以携带指示信息。比如，可以在MBS控制信道消息中增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值。从而终端设备在接收到MBS控制信道消息时，根据指定比特位的取值，可以确定出指示信息中HFN值和/或COUNT值等等，本公开对此不做限定。
可选的，网络设备还可以使用终端设备的专属配置消息，向终端设备发送指示信息。从而终端设备可以基于终端设备的专属配置消息，接收网络设备发送的指示信息。
可以理解的是，本公开中，网络设备可以对终端设备的专属配置消息进行配置，以使其中可以携带指示信息。比如，可以对终端设备的专属配置消息增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值。从而终端设备在接收到专属配置消息时，根据指定比特位的取值，可以确定出指示信息中HFN值和/或COUNT值等等，本公开对此不做限定。
步骤42，当HFN信息的适用条件为SN的取值时，响应于未满足适用条件、且终端设备接收的PDCP数据包对应的SN值与SN的取值的差值为s，基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
可选的，HFN信息的适用条件，可以是网络设备指示的，还可以是终端设备根据协议约定确定的，本公开对此不做限定。
可选的，SN的取值可以为：SN的最小值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值小于该最小值时，即可基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
举例来说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为3。则终端设备在确定收到的PDCP数据包对应的SN值为2时，由于2小于适用条件中的SN的最小值3，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SN值2与SN的取值3的差值s为-1，从而基于差值s对HFN信息进行更新，生成更新后的HFN信息：HFN值为0。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值等的限定。
可选的，SN的取值可以为：SN的最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值大于该最大值时，即可基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最大值为3。则终端设备在确定收到的PDCP数据包对应的SN值为4时，由于4大于适用条件中的SN的最大值3，即未满足HFN信息的适用条件，且终端设备接收的 PDCP数据包对应的SN值4与SN的取值3的差值s为+1，从而基于差值s对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最大值等的限定。
可选的，SN的取值可以为：SN的最小值及最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值小于该最小值、或大于该最大值时，即可基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为2及SN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SN值为6时，由于6大于适用条件中的SN的最大值5，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SN值6与SN的最大值5的差值s为+1，从而基于差值s对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值、SN的最大值等的限定。
可选的，SN的取值可以为：SN的取值对应的分段编号。相应的，终端设备可以在接收的PDCP数据包对应的SN值对应的分段编号与适用条件中的SN的取值对应的分段编号不同时，基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
可以理解的是，SN值对应的分段方式,可以为协议约定好的方式。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的取值对应的分段编号为1。则终端设备在确定收到的PDCP数据包对应的SN值对应的分段编号为2时，未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SN值对应的分段编号2与适用条件中指定的分段编号1的差值s为+1，从而基于差值s对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN值对应的分段编号等的限定。
可选的，SN的取值可以为：SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在m个分段中的分段编号，n为小于或等于m的整数。
相应的，终端设备可以在接收的PDCP数据包对应的SN值在m个分段中的分段编号不为n时，即可基于差值s对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的取值对应的参数对(2,1)。则终端设备在确定收到的PDCP数据包对应的SN值在2个分段中的分段编号为2时，未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SN值对应的分段编号2与适用条件中指定的分段编号1的差值s为+1，从而基于差值s对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、m的取值、n的取值等的限定。
步骤43，基于更新后的HFN信息，确定PDCP实体的HFN值。
可选的，终端设备，可以将更新后的HFN的值，确定为PDCP实体的HFN值。
可选的，对于新接入的终端设备而言，可以根据确定出的HFN信息的适用条件以及接收到的指示信息，确定出PDCP实体的HFN值，之后再利用该HFN值确定出对应的COUNT值，对接收的数据包进行数据的解密或完整性验证。
本公开实施例，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息，以及确定出的SN的取值，在未满足该SN的取值、且终端设备接收的PDCP数据包对应的SN值与SN的取值的差值为s时，基于差值s对HFN信息进行更新，之后再基于更新后的HFN信息，确定PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图5，图5是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图5所示，该方法可以包括但不限于如下步骤：
步骤51，基于MBS控制信道消息，接收网络设备发送的指示信息，其中，指示信息中包括HFN信息。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
需要说明的是，终端设备基于MBS控制信道消息接收指示信息的内容及具体实现形式，可以参考本公开其他各实施例，此处不再赘述。
步骤52，当HFN信息的适用条件为SFN的取值时，响应于未满足适用条件、且终端设备接收的PDCP数据包对应的SFN值与SFN的取值的差值为k，基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
可选的，HFN信息的适用条件，可以是网络设备指示的，还可以是终端设备根据协议约定确定的，本公开对此不做限定。
可选的，终端设备接收的PDCP数据包对应的SFN值可以包括以下任一项或多项：成功接收PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值；成功接收PCDP数据包的第一个物理数据信道的时间位置对应的SFN值；以及成功接收PDCP数据包对应的SFN值。
举例来说，终端设备接收的PDCP数据包对应的SFN值为成功接收PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值。比如，终端设备在接收PDCP数据包时，需要成功接收t1时刻的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)数据和t2时刻的PDSCH数据，t1时刻在前，t2时刻在后，则可以确定t2时刻对应的SFN值为终端设备接收的PDCP数据包对应的SFN值等等，本公开对此不做限定。
或者，终端设备接收的PDCP数据包对应的SFN值为成功接收PCDP数据包的第一个物理数据信道的时间位置对应的SFN值。比如，终端设备在接收PDCP数据包时，需要成功接收t1时刻的PDSCH数据和t2时刻的PDSCH数据，t1时刻在前，t2时刻在后，则可以确定t1时刻对应的SFN值为终端设备接收的PDCP数据包对应的SFN值等等，本公开对此不做限定。
或者，终端设备接收的PDCP数据包对应的SFN值为成功接收PDCP数据包对应的SFN值。比如，终端设备在接收PDCP数据包时，成功接收数据包的时刻为t3，则可以确定t3时刻对应的SFN值为终端设备接收的PDCP数据包对应的SFN值等等，本公开对此不做限定。
可选的，SFN的取值可以为：SFN的最小值。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值小于该最小值时，即可基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
举例来说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最小值为3。则终端设备在确定收到的PDCP数据包对应的SFN值为2时，由于2小于适用条件中的SN的最小值3，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SFN值2与SFN的取值3的差值k为-1，从而基于差值k对HFN信息进行更新，生成更新后的HFN信息：HFN值为0。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最小值等的限定。
可选的，SFN的取值可以为：SFN的最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SFN值大于该最大值时，即可基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最大值为3。则终端设备在确定收到的PDCP数据包对应的SFN值为4时，由于4大于适用条件中的SFN的最大值3，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SFN值4与SFN的取值3的差值k为+1，从而基于差值k对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最大值等的限定。
可选的，SFN的取值可以为：SFN的最小值及最大值。
相应的，终端设备可以在接收的PDCP数据包对应的SN值小于该最小值、或大于该最大值时，即可基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最小值为2及SFN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SFN值为6时，由于6大于适用条件中的SFN的最大值5，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SFN值6与SFN的最大值5的差值k为+1，从而基于差值k对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的 最小值、SFN的最大值等的限定。
可选的，SFN的取值可以为：SFN的取值对应的分段编号。相应的，终端设备可以在接收的PDCP数据包对应的SFN值对应的分段编号与适用条件中的SFN的取值对应的分段编号不同时，即可基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
可以理解的是，SFN值对应的分段方式,可以为协议约定好的方式。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的取值对应的分段编号为1。则终端设备在确定收到的PDCP数据包对应的SFN值对应的分段编号为2时，即未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SFN值对应的分段编号2与适用条件中指定的SFN的取值对应的分段编号1的差值k为+1，从而基于差值k对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN值对应的分段编号等的限定。
可选的，SFN的取值可以为：SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在i个分段中的分段编号，j为小于或等于i的整数。
相应的，终端设备可以在接收的PDCP数据包对应的SN值在i个分段中的分段编号不为j时，即可基于差值k对HFN信息进行更新，以生成更新后的HFN信息。
比如说，若终端设备接收到的指示信息为：HFN值为1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的取值对应的参数对(2,1)。则终端设备在确定收到的PDCP数据包对应的SFN值在2个分段中的分段编号为2时，未满足HFN信息的适用条件，且终端设备接收的PDCP数据包对应的SFN值对应的分段编号2与适用条件中指定的分段编号1的差值k为+1，从而基于差值k对HFN信息进行更新，生成更新后的HFN信息：HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、i的取值、j的取值等的限定。
步骤53，基于更新后的HFN信息，确定PDCP实体的HFN值。
可选的，终端设备，可以将更新后的HFN的值，确定为PDCP实体的HFN值。
可选的，对于新接入的终端设备而言，可以根据确定出的HFN信息的适用条件以及接收到的指示信息，确定出PDCP实体的HFN值，之后再利用该HFN值确定出对应的COUNT值，对接收的数据包进行数据的解密或完整性验证。
本公开实施例，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息，以及确定出的SFN的取值，在未满足该SFN的取值、且终端设备接收的PDCP数据包对应的SFN值与SFN的取值的差值为k时，可以基于差值k对HFN信息进行更新，再基于更新后的HFN信息，确定PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图6，图6是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图6所示，该方法可以包括但不限于如下步骤：
步骤61，接收网络设备发送的指示信息，其中，指示信息中包括HFN信息及HFN信息的更新模式。
本公开实施例中，网络设备在向终端设备指示HFN信息时，还可以基于当前的网络状态，比如根据PDCP数据包的发送速度，确定HFN信息的更新模式，并将该更新模式发送给终端设备。从而避免由于网络状态影响，导致的终端设备接收到的HFN信息不准确的情况。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
可选的，更新模式可以包括更新步长及更新方向。
其中，更新步长可以为网络设备设置的任意数值，比如可以为1、2、3等等，本公开对此不做限定。
另外，更新方向，可以为网络设备设置的任意方向，比如可以为“+”方向、“-”方向等等，本公开对此不做限定。从而，HFN信息的更新模式，可以为“指示信息指示的HFN值+1”、“指示信息指示的HFN值-2”、“指示信息指示的COUNT值-1”等等，本公开对此不做限定。
步骤62，响应于未满足HFN信息的适用条件，基于更新模式对HFN信息进行更新，以生成更新后的HFN信息。
可选的，HFN信息的适用条件，可以是网络设备指示的，还可以是终端设备根据协议约定确定的，本公开对此不做限定。
举例来说，在PDCP数据包发送过快时，可能导致终端设备接收到的PDCP数据包未满足HFN信息的 适用条件，此时，网络设备指示的HFN信息的更新模式可能为“指示信息指示的HFN值+1”；而在PDCP数据包发送过慢时，可能导致终端设备接收到的PDCP数据包未满足HFN信息的适用条件，此时，网络设备指示的HFN信息的更新模式可能为“指示信息中的HFN值-1”、“指示信息中的HFN值-2”等等，本公开对此不做限定。
比如说，HFN信息的适用条件为：SN的最小值。相应的，终端设备可以在接收的PDCP数据包对应的SN值小于该最小值时，即可基于更新模式对HFN信息进行更新，以生成更新后的HFN信息。
举例来说，若终端设备接收到的指示信息为：HFN值为1、指示信息中的HFN值-1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为3。则终端设备在确定收到的PDCP数据包对应的SN值为2时，由于2小于适用条件中的SN的最小值3，即未满足HFN信息的适用条件，从而终端设备即可对HFN信息进行更新，更新后的HFN值为0。
或者，HFN信息的适用条件为：SFN的最大值。相应的，终端设备可以在接收的PDCP数据包对应的SFN值大于该最大值时，即可基于更新模式对HFN信息进行更新，以生成更新后的HFN信息。
比如说，终端设备接收到的指示信息为：HFN值为1、指示信息中的HFN值+1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最大值为3。则终端设备在确定收到的PDCP数据包对应的SFN值为4时，由于4大于适用条件中的SFN的最大值3，即未满足HFN信息的适用条件。从而终端设备即可对HFN信息进行更新，更新后的HFN值为2。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值、SFN的最大值等的限定。
需要说明的是，对于其他未满足HFN信息的适用条件的情况，基于更新模式对HFN信息进行更新的内容及具体实现形式，可以参考本公开其他各实施例的描述，此处不再赘述。
步骤63，基于更新后的HFN信息，确定PDCP实体的HFN值。
可选的，可以将更新后的HFN的值，确定为PDCP实体的HFN值。
可选的，对于新接入的终端设备而言，可以根据确定出的HFN信息的适用条件以及接收到的指示信息，确定出PDCP实体的HFN值，之后再利用该HFN值确定出对应的COUNT值，对接收的数据包进行数据的解密或完整性验证。
本公开实施例，终端设备可以先接收网络设备发送的HFN信息，之后根据指示信息中包括的HFN信息，以及确定出的HFN信息的适用条件，在未满足HFN信息的适用条件时，可以基于更新模式对HFN信息进行更新，以生成更新后的HFN信息，之后再确定PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图7，图7是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由终端设备执行。如图9所示，该方法可以包括但不限于如下步骤：
步骤71，接收网络设备发送的指示信息，其中，指示信息中包括HFN信息及MBS业务信息。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
可选的，MBS业务信息可以包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
其中，MBS业务标识，可以包括临时移动组标识(Temporary Mobile Group Identity，TMGI)、MBS会话标识(MBS Session ID)、MBS业务流标识(MBS QoS flow ID)等等，本公开对此不做限定。
另外，MBS承载标识的样式或者呈现形式，可以为协议约定或网络设备配置的，比如可以为MRB-1、MRB-2等等，本公开对此不做限定。
可选的，MBS承载的协议实体配置信息，可以为PDCP配置信息，其可以包括：PDCP SN长度，或者数据包头压缩配置，或者是否需要完整性检测的配置等等。
或者，MBS承载的协议实体配置信息也可以为无线链路控制(Radio Link Control，RLC)配置，其可以包括：PDCP SN长度、RLC工作模式指示等等。
或者，MBS承载的协议实体配置信息还可以为MAC配置，其可以包括逻辑信道标识等等，本公开对此不做限定。
步骤72，基于HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
比如，终端设备接收的指示信息指示：对于无线承载MRB-1，HFN值为1。之后，终端设备则可以确定与无线承载MRB-1对应的PDCP实体的HFN值为1等等，本公开对此不做限定。
可选的，终端设备还可以在接收的PDCP数据包对应的SN值满足HFN信息的适用条件时，基于HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
比如说，SN的取值可以为：SN的最小值。相应的，终端设备可以在接收的PDCP数据包对应的SN值大于或等于该最小值时，即可基于网络设备指示的HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
可选的，终端设备接收的PDCP数据包可以为终端设备从MBS业务信息对应的无线承载MRB中接收的第一个PDCP数据包。
举例来说，若终端设备接收到的指示信息为：HFN值为1、与MBS业务信息对应的无线承载为MRB-1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SN的最小值为5。则终端设备接收的PDCP数据包可以为终端设备从无线承载MRB-1中接收的第一个PDCP数据包,从而终端设备在确定该PDCP数据包对应的SN值为7时，由于7大于适用条件中的SN的最小值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定无线承载MRB-1对应的PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SN的最小值等的限定。
可选的，终端设备还可以在接收的PDCP数据包对应的SFN值满足HFN信息的适用条件时，基于HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
比如说，SFN的取值可以为：SFN的最大值。相应的，终端设备可以在接收的PDCP数据包对应的SFN值小于或等于该最大值时，即可基于网络设备指示的HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
比如，终端设备接收到的指示信息为：HFN值为1、与MBS业务信息对应的无线承载为MRB-1。且终端设备根据协议约定或者网络设备的指示确定HFN信息的适用条件为：SFN的最大值为5。则终端设备在确定收到的PDCP数据包对应的SFN值为1时，由于1小于适用条件中的SFN的最大值5，即满足HFN信息的适用条件，从而可以基于网络设备指示的HFN值，确定无线承载MRB-1对应的PDCP实体的HFN的值为1。
需要说明的是，上述示例只是举例说明，不能作为对本公开实施例中指示信息、HFN的值、SFN的最大值等的限定。
需要说明的是，对于SN值、SFN值满足HFN信息的其他适用条件时，确定与MBS业务信息对应的PDCP实体的HFN值的具体内容及实现方式，可以参考本公开其他各个实施例的说明，此处不再赘述。
可选的，对于新接入MBS业务的终端设备，可以基于HFN信息，确定与MBS业务信息对应的PDCP实体的HFN值。
比如，新接入MBS业务的终端设备接收到的指示信息为：HFN值为1、MBS业务对应的无线承载为MRB-1，则该终端设备可以确定出与无线承载MRB-1对应的PDCP实体的HFN值等等，本公开对此不做限定。
步骤73，基于HFN信息，对与MBS业务信息对应的接收数据进行解密或完整性验证。
比如说，终端设备确定出无线承载MRB-1对应的PDCP实体的HFN的值为1，之后可以利用该HFN值确定出对应的COUNT值，再对与无线承载MRB-1对应的接收数据进行解密或完整性验证等等，本公开对此不做限定。
本公开实施例，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息及MBS业务信息，确定出与MBS业务信息对应的PDCP实体的HFN值，之后即可对与MBS业务信息对应的接收数据进行解密或完整性验证。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图8，图8是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由网络设备执行。如图8所示，该方法可以包括但不限于如下步骤：
步骤81，向终端设备发送指示信息，其中，指示信息中包括超帧号HFN信息。
可选的，HFN信息可以包括以下任一项或多项：HFN值及COUNT值。
可选的，网络设备可以基于系统消息，向终端设备发送指示信息，其中，指示信息中包括HFN信息。
比如，网络设备可以对SIB1消息进行扩展，以使SIB1中可以携带指示信息。比如，可以在SIB1中增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值等等，本公开对此不做限定。
可选的，网络设备还可以基于广播多播业务MBS控制信道消息，向所终端设备发送指示信息。
可以理解的是，本公开中，网络设备可以对MBS控制信道消息进行扩展，以使其中可以携带指示信息。比如，可以在MBS控制信道消息中增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值等等，本公开对此不做限定。
可选的，网络设备还可以基于终端设备的专属配置消息，向终端设备发送指示信息。
可以理解的是，本公开中，网络设备可以对终端设备的专属配置消息进行配置，以使其中可以携带指示信息。比如，可以对终端设备的专属配置消息增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值等等，本公开对此不做限定。
本公开实施例，网络设备可以向终端设备发送指示信息，以使终端设备可以接收到HFN信息。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图9，图9是本公开实施例提供的一种分组数据汇聚协议实体的超帧号确定方法的流程示意图,该方法被配置为由网络设备执行。如图9所示，该方法可以包括但不限于如下步骤：
步骤91，基于系统消息，向终端设备发送指示信息，其中，指示信息中包括HFN信息。
比如，网络设备可以对SIB1消息进行扩展，以使SIB1中可以携带指示信息。比如，可以在SIB1中增加指定的比特位，通过指定比特位的取值来表示HFN值和/或COUNT值等等，本公开对此不做限定。
其中，HFN信息包括以下任一项或多项：HFN值及COUNT值。
步骤92，向终端设备发送HFN信息的适用条件。
可选的，HFN信息的适用条件可以包括以下任一项或多项：序列号SN的取值及系统帧号SFN的取值。
其中，SN的取值可以包括以下任一项或多项：SN的最小值；SN的最大值；SN的最小值及最大值；SN的取值对应的分段编号；以及SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，SFN的取值包括以下任一项或多项：SFN的最小值；SFN的最大值；SFN的最小值及最大值；SFN的取值对应的分段编号；以及SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
需要说明的是，终端设备基于HFN信息的适用条件所进行的操作及对应的效果，可以参考本公开其他各实施例中终端设备侧的说明，此处不再赘述。
可选的，指示信息中还可以包括MBS业务信息。
其中，MBS业务信息可以包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，指示信息中还可以包括HFN信息的更新模式。
可选的，更新模式包括更新步长及更新方向。
其中，更新步长，可以为网络设备根据PDCP数据包发送的快慢程度，对应设置的数值，其可以为任意数值，比如1、2、3等等，本公开对此不做限定。
另外，更新方向，可以为网络设备设置的任意方向，比如可以为“+”方向、“-”方向等等，本公开对此不做限定。
比如说，在PDCP数据包发送过快时，可能导致终端设备接收到的PDCP数据包未满足HFN信息的适用条件，此时，网络设备指示的HFN信息的更新模式可能为“指示信息指示的HFN值+1”；而在PDCP数据包发送过慢时，可能导致终端设备接收到的PDCP数据包未满足HFN信息的适用条件，此时，网络设备指示的HFN信息的更新模式可能为“指示信息中的HFN值-1”、“指示信息中的HFN值-2”等等，本公开对此不做限定。
需要说明的是，终端设备基于不同指示信息所进行的操作及对应的效果，可以参考本公开其他各实施例中终端设备侧的说明，此处不再赘述。
步骤93，响应于系统消息中除HFN信息外的任一信息变更，向终端设备发送第一变更指示信息。
可以理解的是，为了减少数据传输，网络设备通过系统消息向终端设备发送指示信息时，可以在系统消息中除HFN信息外的任一信息变更的情况下，向终端设备发送第一变更指示信息。由此，系统消息中HFN值的变更，不会使网络设备向终端设备发送第一变更指示信息，从而减少了数据传输，可以使终端设备和网络设备对于HFN的值保持一致理解，保证了数据传输的可靠性。
可选的，网络设备还可以在MBS控制信道消息中除HFN信息外的任一信息变更的情况下，向终端设备发送第二变更指示信息。由此，MBS控制信道消息中HFN值的变更，不会使网络设备向终端设备发送第二变更指示信息，从而减少了数据传输，可以使终端设备和网络设备对于HFN的值保持一致理解，保证了数据传输的可靠性。
本公开实施例中，网络设备可以基于系统消息，向终端设备发送指示信息，以使终端设备可以接收到HFN信息，还可以向终端设备发送HFN信息的适用条件，并且在系统消息中除HFN信息外的任一信息变更时，向终端设备发送第一变更指示信息。由此可以使终端设备和网络设备对于HFN的值保持一致 理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
上述本公开提供的实施例中，分别从网络设备、终端设备的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，网络设备和终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图10，为本公开实施例提供的一种通信装置100的结构示意图。图10所示的通信装置100可包括收发模块1001和处理模块1002。
收发模块1001可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块1001可以实现发送功能和/或接收功能。
可以理解的是，通信装置100可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。
通信装置100，被配置在终端设备侧，所述装置，包括：
收发模块1001，用于接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息。
处理模块1002，用于基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。
可选的，所述HFN信息包括以下任一项或多项：HFN值及计数值COUNT。
可选的，所述处理模块1002，具体用于：响应于满足所述HFN信息的适用条件，基于所述HFN信息，确定所述PDCP实体的HFN值。
可选的，所述收发模块1001，还用于接收所述网络设备发送的所述HFN信息的适用条件；
或者，
所述处理模块1002，还用于基于协议约定，确定所述HFN信息的适用条件。
可选的，所述HFN信息的适用条件包括以下任一项或多项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项或多项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项或多项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述满足所述适用条件包括：
所述终端设备接收的PDCP数据包对应的SN值满足所述适用条件；
或者，
所述终端设备接收的PDCP数据包对应的SFN值满足所述适用条件。
可选的，所述指示信息中还包括MBS业务信息，所述接收的PDCP数据包为所述终端设备从所述MBS业务信息对应的无线承载MRB中接收的第一个PDCP数据包。
可选的，所述接收的PDCP数据包对应的SFN值包括以下任一项或多项：
成功接收所述PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值；
成功接收所述PCDP数据包的第一个物理数据信道的时间位置对应的SFN值；以及
成功接收所述PDCP数据包对应的SFN值。
可选的，所述适用条件为SN的取值，所述处理模块1002，具体用于：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SN值与所述SN的取值的差值为s，基于所述差值s对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述适用条件为SFN的取值，所述处理模块1002，具体用于：
响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SFN值与所述SFN的取值的差值为k，基于所述差值k对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述指示信息中还包括所述HFN信息的更新模式，所述处理模块1002，具体用于：
响应于未满足所述适用条件，基于所述更新模式对所述HFN信息进行更新，以生成更新后的HFN信息；
基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述收发模块1001，具体用于：
基于系统消息，接收所述网络设备发送的指示信息；
或者，
基于广播多播业务MBS控制信道消息，接收所述网络设备发送的指示信息；
或者，
基于所述终端设备的专属配置消息，接收所述网络设备发送的指示信息。
可选的，所述指示信息中还包括MBS业务信息，所述处理模块1002，具体用于：基于所述HFN信息，确定与所述MBS业务信息对应的PDCP实体的HFN值。
可选的，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，所述处理模块1002，还用于基于所述HFN信息，对与所述MBS业务信息对应的接收数据进行解密或完整性验证。
可选的，所述处理模块1002，具体用于响应于所述终端设备为新接入MBS业务的设备，基于所述HFN信息，确定所述PDCP实体的HFN值。
本公开提供的通信装置，终端设备可以先接收网络设备发送的指示信息，之后根据指示信息中包括的HFN信息，确定出PDCP实体的HFN值。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图11，为本公开实施例提供的一种通信装置110的结构示意图。图11所示的通信装置110可包括收发模块1101。
收发模块1101可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块1101可以实现发送功能和/或接收功能。
可以理解的是，通信装置110可以是网络设备，也可以是网络设备中的装置，还可以是能够与网络设备匹配使用的装置。
通信装置110，被配置在网络设备侧，所述装置，包括：
收发模块1101，用于向终端设备发送指示信息，其中，所述指示信息中包括超帧号HFN信息。
可选的，所述HFN信息包括以下任一项或多项：HFN值及计数值COUNT。
可选的，所述收发模块，还用于向所述终端设备发送所述HFN信息的适用条件。
可选的，所述HFN信息的适用条件包括以下任一项或多项：序列号SN的取值及系统帧号SFN的取值。
可选的，所述SN的取值包括以下任一项或多项：
SN的最小值；
SN的最大值；
SN的最小值及最大值；
SN的取值对应的分段编号；以及
SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
可选的，所述SFN的取值包括以下任一项或多项：
SFN的最小值；
SFN的最大值；
SFN的最小值及最大值；
SFN的取值对应的分段编号；以及
SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
可选的，所述指示信息中还包括MBS业务信息。
可选的，所述MBS业务信息包括以下至少一项或多项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
可选的，所述指示信息中还包括所述HFN信息的更新模式。
可选的，所述更新模式包括更新步长及更新方向。
可选的，所述收发模块1101，具体用于：
基于系统消息，向所述终端设备发送指示信息；
或者，
基于广播多播业务MBS控制信道消息，向所述终端设备发送指示信息；
或者，
基于所述终端设备的专属配置消息，向所述终端设备发送指示信息。
可选的，所述收发模块1101，还用于：
响应于所述系统消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第一变更指示信息；
或者，
响应于所述MBS控制信道消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第二变更指示信息。
本公开提供的通信装置，网络设备可以向终端设备发送指示信息，以使终端设备可以接收到HFN信息。由此，可以使终端设备和网络设备对于HFN的值保持一致理解，避免了数据的解密失败或完整性验证失败，提高了数据传输的可靠性。
请参见图12，图12是本公开实施例提供的另一种通信装置120的结构示意图。通信装置120可以是网络设备，也可以是终端设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置120可以包括一个或多个处理器1201。处理器1201可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置120中还可以包括一个或多个存储器1202，其上可以存有计算机程序1204，处理器1201执行所述计算机程序1204，以使得通信装置120执行上述方法实施例中描述的方法。可选的，所述存储器1202中还可以存储有数据。通信装置120和存储器1202可以单独设置，也可以集成在一起。
可选的，通信装置120还可以包括收发器1205、天线1206。收发器1205可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1205可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置120中还可以包括一个或多个接口电路1207。接口电路1207用于接收代码指令并传输至处理器1201。处理器1201运行所述代码指令以使通信装置120执行上述方法实施例中描述的方法。
通信装置120为终端设备：处理器1201用于执行图2中的步骤22；执行图3中的步骤32；图4中的步骤42；图4中的步骤43；图5中的步骤52；图5中的步骤53；图6中的步骤62；图6中的步骤63；图7中的步骤72；或图7中的步骤73。收发器1205用于执行图2中的步骤21；执行图3中的步骤31；图4中的步骤41；图5中的步骤51；图6中的步骤61；或图7中的步骤71。
通信装置120为网络设备：收发器1205用于执行图8中的步骤81；图9中的步骤91；图9中的步骤92；或图9中的步骤93。
在一种实现方式中，处理器1201中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1201可以存有计算机程序1203，计算机程序1203在处理器1201上运行，可使得通信装置120执行上述方法实施例中描述的方法。计算机程序1203可能固化在处理器1201中，该种情况下，处理器1201可能由硬件实现。
在一种实现方式中，通信装置120可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模 拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者终端设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图12的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图13所示的芯片的结构示意图。图13所示的芯片包括处理器1301和接口1302。其中，处理器1301的数量可以是一个或多个，接口1302的数量可以是多个。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1302，用于执行图2中的步骤21；执行图3中的步骤31；图4中的步骤41；图5中的步骤51；图6中的步骤61；或图7中的步骤71。
对于芯片用于实现本公开实施例中网络设备的功能的情况：
接口1302，用于执行图8中的步骤81；图9中的步骤91；图9中的步骤92；或图9中的步骤93。
可选的，芯片还包括存储器1303，存储器1303用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种通信系统，该系统包括前述图10实施例中作为终端设备的通信装置和图11实施例中作为网络设备的通信装置，或者，该系统包括前述图12实施例中作为终端设备的通信装置和作为网络设备的通信装置。
本公开还提供一种计算机可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开 不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (36)

  1. 一种分组数据汇聚协议实体的超帧号确定方法，其特征在于，所述方法被配置为由终端设备执行，所述方法，包括：
    接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息；
    基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。
  2. 如权利要求1所述的方法，其特征在于，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
  3. 如权利要求1所述的方法，其特征在于，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    响应于满足所述HFN信息的适用条件，基于所述HFN信息，确定所述PDCP实体的HFN值。
  4. 如权利要求3所述的方法，其特征在于，还包括：
    接收所述网络设备发送的所述HFN信息的适用条件；
    或者，
    基于协议约定，确定所述HFN信息的适用条件。
  5. 如权利要求4所述的方法，其特征在于，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
  6. 如权利要求5所述的方法，其特征在于，所述SN的取值包括以下任一项：
    SN的最小值；
    SN的最大值；
    SN的最小值及最大值；
    SN的取值对应的分段编号；以及
    SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
  7. 如权利要求5所述的方法，其特征在于，所述SFN的取值包括以下任一项：
    SFN的最小值；
    SFN的最大值；
    SFN的最小值及最大值；
    SFN的取值对应的分段编号；以及
    SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
  8. 如权利要求5-7任一所述的方法，其特征在于，所述满足所述适用条件包括：
    所述终端设备接收的PDCP数据包对应的SN值满足所述适用条件；
    或者，
    所述终端设备接收的PDCP数据包对应的SFN值满足所述适用条件。
  9. 如权利要求8所述的方法，其特征在于，所述指示信息中还包括MBS业务信息，所述接收的PDCP数据包为所述终端设备从所述MBS业务信息对应的无线承载MRB中接收的第一个PDCP数据包。
  10. 如权利要求8所述的方法，其特征在于，所述接收的PDCP数据包对应的SFN值包括以下任一项：
    成功接收所述PCDP数据包的最后一个物理数据信道的时间位置对应的SFN值；
    成功接收所述PCDP数据包的第一个物理数据信道的时间位置对应的SFN值；以及
    成功接收所述PDCP数据包对应的SFN值。
  11. 如权利要求4-10任一所述的方法，其特征在于，所述适用条件为SN的取值，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SN值与所述SN的取值的差值为s，基于所述差值s对所述HFN信息进行更新，以生成更新后的HFN信息；
    基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
  12. 如权利要求4-10任一所述的方法，其特征在于，所述适用条件为SFN的取值，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    响应于未满足所述适用条件、且所述终端设备接收的PDCP数据包对应的SFN值与所述SFN的取值的差值为k，基于所述差值k对所述HFN信息进行更新，以生成更新后的HFN信息；
    基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
  13. 如权利要求1-10任一所述的方法，其特征在于，所述指示信息中还包括所述HFN信息的更新模式，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    响应于未满足所述适用条件，基于所述更新模式对所述HFN信息进行更新，以生成更新后的HFN信息；
    基于所述更新后的HFN信息，确定所述PDCP实体的HFN值。
  14. 如权利要求13所述的方法，其特征在于，所述更新模式包括更新步长及更新方向。
  15. 如权利要求1-14任一所述的方法，其特征在于，所述接收网络设备发送的指示信息，包括：
    基于系统消息，接收所述网络设备发送的指示信息；
    或者，
    基于广播多播业务MBS控制信道消息，接收所述网络设备发送的指示信息；
    或者，
    基于所述终端设备的专属配置消息，接收所述网络设备发送的指示信息。
  16. 如权利要求1-14任一所述的方法，其特征在于，所述指示信息中还包括MBS业务信息，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    基于所述HFN信息，确定与所述MBS业务信息对应的PDCP实体的HFN值。
  17. 如权利要求16所述的方法，其特征在于，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
  18. 如权利要求16所述的方法，其特征在于，还包括：
    基于所述HFN信息，对与所述MBS业务信息对应的接收数据进行解密或完整性验证。
  19. 如权利要求1-18任一所述的方法，其特征在于，所述基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值，包括：
    响应于所述终端设备为新接入MBS业务的设备，基于所述HFN信息，确定所述PDCP实体的HFN值。
  20. 一种分组数据汇聚协议实体的超帧号确定方法，其特征在于，所述方法被配置为由网络设备执行，所述方法，包括：
    向终端设备发送指示信息，其中，所述指示信息中包括超帧号HFN信息。
  21. 如权利要求20所述的方法，其特征在于，所述HFN信息包括以下任一项：HFN值及计数值COUNT。
  22. 如权利要求20所述的方法，其特征在于，还包括：
    向所述终端设备发送所述HFN信息的适用条件。
  23. 如权利要求22所述的方法，其特征在于，所述HFN信息的适用条件包括以下任一项：序列号SN的取值及系统帧号SFN的取值。
  24. 如权利要求23所述的方法，其特征在于，所述SN的取值包括以下任一项：
    SN的最小值；
    SN的最大值；
    SN的最小值及最大值；
    SN的取值对应的分段编号；以及
    SN的取值对应的参数对(m,n),其中，m为将SN的全部取值按指定顺序等分后的分段数量，n为SN当前的取值在所述m个分段中的分段编号，n为小于或等于m的整数。
  25. 如权利要求23所述的方法，其特征在于，所述SFN的取值包括以下任一项：
    SFN的最小值；
    SFN的最大值；
    SFN的最小值及最大值；
    SFN的取值对应的分段编号；以及
    SFN的取值对应的参数对(i,j),其中，i为将SFN的全部取值按指定顺序等分后的分段数量，j为SFN当前的取值在所述i个分段中的分段编号，j为小于或等于i的整数。
  26. 如权利要求20所述的方法，其特征在于，所述指示信息中还包括MBS业务信息。
  27. 如权利要求26所述的方法，其特征在于，所述MBS业务信息包括以下至少一项：MBS业务标识，MBS承载标识，以及MBS承载的协议实体配置信息。
  28. 如权利要求20所述的方法，其特征在于，所述指示信息中还包括所述HFN信息的更新模式。
  29. 如权利要求28所述的方法，其特征在于，所述更新模式包括更新步长及更新方向。
  30. 如权利要求20-29任一所述的方法，其特征在于，所述向终端设备发送指示信息，包括：
    基于系统消息，向所述终端设备发送指示信息；
    或者，
    基于广播多播业务MBS控制信道消息，向所述终端设备发送指示信息；
    或者，
    基于所述终端设备的专属配置消息，向所述终端设备发送指示信息。
  31. 如权利要求30所述的方法，其特征在于，还包括：
    响应于所述系统消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第一变更指示信息；
    或者，
    响应于所述MBS控制信道消息中除所述HFN信息外的任一信息变更，向所述终端设备发送第二变更指示信息。
  32. 一种通信装置，其特征在于，所述装置被配置在终端设备侧，所述装置，包括：
    收发模块，用于接收网络设备发送的指示信息，其中，所述指示信息中包括超帧号HFN信息；
    处理模块，用于基于所述HFN信息，确定所述分组数据汇聚协议PDCP实体的HFN值。
  33. 一种通信装置，其特征在于，所述装置被配置在网络设备侧，所述装置，包括：
    收发模块，用于向终端设备发送指示信息，其中，所述指示信息中包括超帧号HFN信息。
  34. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至19中任一项所述的方法；或，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求20至31中任一项所述的方法。
  35. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至19中任一项所述的方法；或所述处理器，用于运行所述代码指令以执行如权利要求20至31中任一项所述的方法。
  36. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至19中任一项所述的方法被实现；或，用于存储有指令，当所述指令被执行时，使如权利要求20至31中任一项所述的方法被实现。
PCT/CN2021/084755 2021-03-31 2021-03-31 一种分组数据汇聚协议实体的超帧号确定方法及其装置 Ceased WO2022205230A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020237037315A KR102816866B1 (ko) 2021-03-31 2021-03-31 패킷 데이터 컨버전스 프로토콜 엔티티의 하이퍼 프레임 번호 결정 방법 및 이의 장치
PCT/CN2021/084755 WO2022205230A1 (zh) 2021-03-31 2021-03-31 一种分组数据汇聚协议实体的超帧号确定方法及其装置
CN202180000903.8A CN115486112B (zh) 2021-03-31 2021-03-31 一种分组数据汇聚协议实体的超帧号确定方法及其装置
EP21933890.2A EP4319069A4 (en) 2021-03-31 2021-03-31 METHOD AND APPARATUS FOR DETERMINING THE HYPERFRAME NUMBER OF A PACKET DATA CONVERGENCE PROTOCOL UNIT
JP2023559047A JP7592891B2 (ja) 2021-03-31 2021-03-31 パケットデータコンバージェンスプロトコルエンティティのハイパーフレーム番号決定方法及びその装置
BR112023019809A BR112023019809A2 (pt) 2021-03-31 2021-03-31 Método para determinar um número de hiperquadro de uma entidade de protocolo de convergência de dados em pacotes, dispositivo de comunicação, e, meio de armazenamento legível por computador tendo instruções armazenadas no mesmo
US18/552,355 US20240179563A1 (en) 2021-03-31 2021-03-31 Method and apparatus for determining hyper frame number of packet data convergence protocol entity

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/084755 WO2022205230A1 (zh) 2021-03-31 2021-03-31 一种分组数据汇聚协议实体的超帧号确定方法及其装置

Publications (1)

Publication Number Publication Date
WO2022205230A1 true WO2022205230A1 (zh) 2022-10-06

Family

ID=83457726

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/084755 Ceased WO2022205230A1 (zh) 2021-03-31 2021-03-31 一种分组数据汇聚协议实体的超帧号确定方法及其装置

Country Status (7)

Country Link
US (1) US20240179563A1 (zh)
EP (1) EP4319069A4 (zh)
JP (1) JP7592891B2 (zh)
KR (1) KR102816866B1 (zh)
CN (1) CN115486112B (zh)
BR (1) BR112023019809A2 (zh)
WO (1) WO2022205230A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000028744A2 (en) * 1998-11-05 2000-05-18 Nokia Networks Oy Frame synchronization mechanism
CN101729377A (zh) * 2008-10-30 2010-06-09 华为技术有限公司 超帧号的通知方法、装置和系统
CN102547689A (zh) * 2012-03-12 2012-07-04 华为技术有限公司 一种加解密参数的同步方法及装置
CN102769907A (zh) * 2012-07-03 2012-11-07 中兴通讯股份有限公司 一种超帧号同步的方法、装置及系统

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100703380B1 (ko) 2003-05-14 2007-04-03 삼성전자주식회사 멀티미디어 브로드캐스트/멀티캐스트 서비스를 지원하기 위한 제어정보 송수신 장치 및 방법
DE602006013416D1 (de) 2005-02-07 2010-05-20 Lg Electronics Inc Übertragung von steuerungsdaten entsprechend der gruppierung von diensten in einem mobilen kommunikationssystem
CN101742430A (zh) * 2008-11-20 2010-06-16 华为技术有限公司 数据包处理方法、装置以及基站
CN103650418B (zh) * 2011-06-09 2017-10-31 安华高科技通用Ip(新加坡)公司 用于多播服务的方法和装置
US8750179B2 (en) * 2011-08-15 2014-06-10 Blackberry Limited Efficient multimedia broadcast multicast service continuity methods
CN107529159B (zh) * 2016-06-22 2020-10-02 南京中兴软件有限责任公司 宽带集群下行共享信道的接入层加密、解密、完整性保护方法和装置、安全实现方法
US10320693B2 (en) * 2016-07-06 2019-06-11 Qualcomm Incorporated Method for packet data convergence protocol count synchronization
CN107623913A (zh) * 2016-07-15 2018-01-23 中兴通讯股份有限公司 超帧号hfn的处理方法及装置
WO2018227497A1 (zh) * 2017-06-15 2018-12-20 Oppo广东移动通信有限公司 数据处理方法及相关产品
US20190297502A1 (en) * 2018-03-22 2019-09-26 Lg Electronics Inc. Method and apparatus for performing integrity verification in wireless communication system
CN110636507A (zh) * 2018-06-21 2019-12-31 华为技术有限公司 通信方法和装置
KR102695458B1 (ko) * 2018-09-21 2024-08-14 삼성전자주식회사 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치
CN111866971B (zh) * 2019-04-29 2021-10-22 华为技术有限公司 一种通信方法及装置
CN111510278B (zh) * 2020-04-26 2023-01-13 Oppo广东移动通信有限公司 一种超帧号hfn同步方法及终端、存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000028744A2 (en) * 1998-11-05 2000-05-18 Nokia Networks Oy Frame synchronization mechanism
CN101729377A (zh) * 2008-10-30 2010-06-09 华为技术有限公司 超帧号的通知方法、装置和系统
CN102547689A (zh) * 2012-03-12 2012-07-04 华为技术有限公司 一种加解密参数的同步方法及装置
CN102769907A (zh) * 2012-07-03 2012-11-07 中兴通讯股份有限公司 一种超帧号同步的方法、装置及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Open Issues on Dynamic PTM and PTP Switch", 3GPP DRAFT; R2-2100084, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973302 *
See also references of EP4319069A4 *

Also Published As

Publication number Publication date
CN115486112B (zh) 2025-09-23
KR102816866B1 (ko) 2025-06-10
BR112023019809A2 (pt) 2024-01-16
US20240179563A1 (en) 2024-05-30
EP4319069A4 (en) 2025-01-29
KR20230163525A (ko) 2023-11-30
CN115486112A (zh) 2022-12-16
EP4319069A1 (en) 2024-02-07
JP7592891B2 (ja) 2024-12-02
JP2024512079A (ja) 2024-03-18

Similar Documents

Publication Publication Date Title
US11259362B2 (en) Method for repeatedly transmitting data and device
CN115669181A (zh) 一种确定触发连续lbt失败的方法及装置
JP7741970B2 (ja) ダウンリンク制御情報のアライン方法及びその装置
WO2023115487A1 (zh) 一种人工智能会话的创建方法及其装置
WO2024050778A1 (zh) 一种人工智能服务策略的更新方法及装置
CN115336222A (zh) 一种混合自动重传请求harq反馈的确定方法及其装置
WO2023044620A1 (zh) 一种传输配置指示状态的确定方法及其装置
WO2022205005A1 (zh) 一种数据接收的处理方法及其装置
WO2024207368A1 (zh) 一种卫星覆盖信息确定方法及其装置
WO2024168935A1 (zh) 一种消息验证方法及其装置
JP7592891B2 (ja) パケットデータコンバージェンスプロトコルエンティティのハイパーフレーム番号決定方法及びその装置
RU2825428C2 (ru) Способ и устройство для определения номера гиперкадра объекта протокола конвергенции пакетных данных
WO2022205191A1 (zh) 一种pdcp实体的接收窗口的配置方法及其装置
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
CN115997392A (zh) 侧行链路定位消息的发送方法、接收方法及其装置
WO2023147708A1 (zh) 一种人工智能会话的更新方法及其装置
WO2022266948A1 (zh) 一种物理上行控制信道波束恢复的方法及其装置
WO2022236622A1 (zh) 一种寻呼方法及其装置
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2024086979A1 (zh) 一种传输配置指示tci状态的确定方法及装置
WO2024036520A1 (zh) 一种侧行链路逻辑信道标识的确定方法及装置
WO2024164157A1 (zh) 一种信息发送方法及通信装置
CN118104264A (zh) 一种多路径传输方法/装置/设备及存储介质
CN115553025A (zh) 数据传输方法和装置
WO2023115279A1 (zh) 数据传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21933890

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18552355

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2023559047

Country of ref document: JP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023019809

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 202347070621

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20237037315

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2023127866

Country of ref document: RU

Ref document number: 11202307326T

Country of ref document: SG

Ref document number: 2021933890

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021933890

Country of ref document: EP

Effective date: 20231031

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112023019809

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230926

WWG Wipo information: grant in national office

Ref document number: 202180000903.8

Country of ref document: CN