WO2023066240A1

WO2023066240A1 - Hyper-frame number (hfn) processing method and apparatus, terminal, and base station

Info

Publication number: WO2023066240A1
Application number: PCT/CN2022/125884
Authority: WO
Inventors: 苗金华; 张大钧; 周锐
Original assignee: 大唐移动通信设备有限公司
Priority date: 2021-10-22
Filing date: 2022-10-18
Publication date: 2023-04-27
Also published as: CN116015577A

Abstract

The present disclosure provides a hyper frame number (HFN) processing method and apparatus, a terminal, and a base station. The method comprises: receiving a PDCP data packet sent by a network-side device; determining whether a first HFN corresponding to the PDCP data packet is the same as a second HFN, the second HFN being sent by the network-side device to a terminal by means of signaling; and if the first HFN is different from the second HFN, processing the first HFN.

Description

Super frame number HFN processing method, device, terminal and base station

Cross References to Related Applications

This disclosure claims priority to Chinese Patent Publication No. 202111237920.1 filed in China on October 22, 2021, the entire contents of which are hereby incorporated by reference.

technical field

The present disclosure relates to the field of wireless technologies, and in particular, refers to a Hyper Frame Number (Hyper Frame Number, HFN) processing method, device, terminal, and base station.

Background technique

In the current New Radio (NR) technology, when sending service data packets, the Packet Data Convergence Protocol Layer (PDCP) on the network side performs operations such as integrity protection and encryption on the PDCP data packets , the data packet number corresponding to the PDCP data packet will be used, that is, the COUNT value, and the terminal side will perform the corresponding integrity check and decryption operation after receiving the PDCP data (data) protocol data unit (Protocol Data Unit, PDU) The COUNT value corresponding to the PDCP data PDU will also be used.

For multicast broadcast service (Multicast broadcast service, MBS) data transmission, according to related technologies, all terminals receive the same PDCP data PDU on the same multicast broadcast service radio bearer (MBS Radio Bearer, MRB). When a specific terminal starts to receive the MRB corresponding to an MBS service, the MBS data may have been transmitted on the MRB for a period of time, that is, the COUNT value of the PDCP data PDU has accumulated to a specific value, that is, the first PDCP received by the terminal The COUNT value corresponding to the data PDU is not 0, and the value of the Hyper Frame Number (Hyper Frame Number, HFN) in the corresponding COUNT value may not be 0 either. If the terminal follows the unicast mechanism and thinks that the HFN corresponding to the first received PDCP data PDU starts from 0, there will be a corresponding relationship between the PDCP data PDU and the COUNT value received by the terminal side and the corresponding correspondence between the network side different situations.

In order to ensure that the HFN on the terminal side is effective in the MBS service, there has been research on the technology of sending the HFN from the network side to the terminal. The specific method may be that the network side device sends the specific value of HFN to the terminal through radio resource control (Radio Resource Control, RRC) signaling. The network side device can send the PDCP data PDU after the terminal receives the HFN. However, because the terminal needs a certain processing delay to receive RRC signaling, for example, when the channel quality is poor, the retransmission of the Radio Link Control (RLC) protocol will cause delays in receiving RRC signaling, and it may also be Since the HFN and the PDCP data PDU are sent to the terminal by different network units, the initial HFN received by the terminal is inconsistent with the HFN actually used in the PDCP data PDU.

Contents of the invention

The purpose of the present disclosure is to provide a Hyper Frame Number (Hyper Frame Number, HFN) processing method, device, terminal and base station, which are used to solve the asynchrony between the initial HFN received by the terminal and the HFN actually used in the PDCP data PDU in the related art The problem.

An embodiment of the present disclosure provides a method for processing a hyperframe number HFN, which is executed by a terminal, and the method includes:

Receive the PDCP data packet sent by the network side device;

Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, where the second HFN is sent to the terminal by the network side device through signaling;

If the first HFN is different from the second HFN, perform processing on the first HFN.

Optionally, in the HFN processing method, wherein, the PDCP packet further includes HFN update indication information, and the HFN update indication information is used to indicate that the first HFN and the second HFN corresponding to the PDCP packet sent by the network side device Whether the two HFNs are the same;

Wherein, determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN according to the HFN update indication information.

Optionally, the HFN processing method, wherein the HFN update indication information includes at least one of the following:

A first indication bit indicating that the first HFN is different from the second HFN;

indicating that the first HFN is the same as the second HFN;

Indicates the value corresponding to the lowest N bits of the first HFN; wherein, N is an integer greater than or equal to 1.

Optionally, in the HFN processing method, wherein, the HFN number update instruction information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP packet, or through the PDCP protocol data unit of the PDCP packet Control (control) PDU transmission.

Optionally, the HFN processing method, wherein the processing the first HFN includes:

A value obtained by adding 1 to the second HFN is determined as the first HFN.

Optionally, in the HFN processing method, in the case where the HFN number update indication includes a value corresponding to the lowest N bits indicating the first HFN, the processing the first HFN includes:

The corresponding bits of the second HFN number are updated according to the value corresponding to the lowest N bits to obtain the first HFN number.

Optionally, the HFN processing method, wherein the determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

According to the first sequence number (Sequence Number, SN) and the second SN in the PDCP data packet, determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN; wherein, the first SN is determined by the second HFN The network side device sends the signaling to the terminal.

Optionally, the HFN processing method, wherein the method also includes:

According to the first SN, determine the first window and the second window; wherein, the first window is [SNini, 2maxSN-1-1], and the second window is [0, 2maxSN-1-1-SNini ]; SNini is the first SN, and maxSN is the maximum value of SN;

Wherein, according to the first SN and the second SN in the PDCP data packet, determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

When the second SN is located in the first window, determine that the first HFN corresponding to the PDCP data packet is the same as the second HFN;

When the second SN is located in the second window, it is determined that the first HFN corresponding to the PDCP data packet is different from the second HFN.

Optionally, the HFN processing method, wherein the method also includes:

When the second SN is outside the first SN window and the second SN window, feeding back abnormality report information to the network side device.

Optionally, in the HFN processing method, after receiving the PDCP data packet sent by the network side device, the method further includes:

Judging whether the PDCP data packet is the first data packet of the service data of the received MBS service;

When the PDCP data packet is the first data packet of the service data of the received MBS service, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN.

An embodiment of the present disclosure also provides a method for processing a hyperframe number HFN, which is executed by a network side device, and the method includes:

Send a PDCP packet to the terminal;

Wherein, the PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN corresponding to the PDCP data packet sent by the network side device is the same as the second HFN; the second HFN is determined by the The network side device sends the signaling to the terminal.

Optionally, in the HFN processing method, the HFN number update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

An embodiment of the present disclosure also provides a terminal, which includes a memory, a transceiver, and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

Receive the PDCP data packet sent by the network side device;

Optionally, the terminal, wherein, the PDCP data packet further includes HFN update indication information, and the HFN update indication information is used to indicate the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device whether the same;

Wherein, the processor determines whether the first HFN corresponding to the PDCP packet is the same as the second HFN, specifically:

Optionally, the terminal, wherein the HFN update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

Optionally, in the terminal, wherein, the HFN number update instruction information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or through the PDCP control ( control) PDU is sent.

Optionally, in the terminal, wherein the processor processes the first HFN, specifically:

A value obtained by adding 1 to the second HFN is determined as the first HFN.

Optionally, in the terminal, wherein, in the case where the HFN number update indication includes a value corresponding to the lowest N bits indicating the first HFN, the processor processes the first HFN, specifically:

Optionally, in the terminal, wherein the processor determines whether the first HFN corresponding to the PDCP packet is the same as the second HFN, specifically:

According to the first SN and the second SN in the PDCP data packet, determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN; wherein, the first SN is signaled by the network side device sent to the terminal.

Optionally, the terminal, wherein the processor is further configured to:

Optionally, in the terminal, after receiving the PDCP data packet sent by the network side device, the processor is further configured to:

An embodiment of the present disclosure also provides a network side device, which includes a memory, a transceiver, and a processor:

Send a PDCP packet to the terminal;

Optionally, in the network side device, the HFN number update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

An embodiment of the present disclosure also provides an apparatus for processing a hyperframe number HFN, wherein, executed by a terminal, the apparatus includes:

a receiving unit, configured to receive a PDCP packet sent by a network side device;

A determining unit, configured to determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, wherein the second HFN is sent to the terminal by the network side device through signaling;

A processing unit, configured to process the first HFN if the first HFN is different from the second HFN.

The present disclosure also provides a hyperframe number HFN processing apparatus in another embodiment, wherein, executed by a network side device, the apparatus includes:

a sending unit, configured to send a PDCP packet to the terminal;

An embodiment of the present disclosure also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the supercomputer described in any one of the preceding items. Frame number HFN processing method.

The beneficial effects of the aforementioned technical solutions of the present disclosure are as follows:

The HFN processing method described in the embodiments of the present disclosure can indicate whether the first HFN corresponding to the PDCP data packet is the HFN (second HFN) initially sent to the terminal when the network side device sends the PDCP data packet, and determine the PDCP data packet When the corresponding first HFN is different from the HFN initially sent to the terminal by the network side device, it can process the first HFN corresponding to the PDCP data packet, and determine the updated HFN, so that for the received PDCP data packet, the terminal determines the The HFN is synchronized with the HFN when the network side device sends data.

Description of drawings

FIG. 1 is a schematic structural diagram of a system to which the method described in an embodiment of the present disclosure is applied;

FIG. 2 is a schematic diagram illustrating the process of SN flipping;

FIG. 3 is a schematic flow diagram of the HFN treatment method described in one embodiment of the present disclosure;

FIG. 4 is one of the implementation structures of HFN update instruction information in an embodiment of the present disclosure;

FIG. 5 is the second implementation structure of HFN update indication information in an embodiment of the present disclosure;

FIG. 6 is the third implementation structure of HFN update instruction information in the embodiment of the present disclosure;

FIG. 7 is a schematic diagram of the principles of the first window and the second window set in the embodiment of the present disclosure;

Fig. 8 is a schematic flow chart of the HFN treatment method according to another embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present disclosure;

Fig. 11 is a schematic structural diagram of the HFN processing device according to one embodiment of the present disclosure;

Fig. 12 is a schematic structural diagram of an HFN processing device according to another embodiment of the present disclosure.

Detailed ways

The term "and/or" in the embodiments of the present disclosure describes the association relationship of associated objects, indicating that there may be three relationships, for example, A and/or B, which may mean: A exists alone, A and B exist simultaneously, and B exists alone These three situations. The character "/" generally indicates that the contextual objects are an "or" relationship.

The term "plurality" in the embodiments of the present disclosure refers to two or more, and other quantifiers are similar.

The following will clearly and completely describe the technical solutions in the embodiments of the present disclosure with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only some of the embodiments of the present disclosure, not all of them. Based on the embodiments in the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present disclosure.

The HFN processing method, device, terminal, and network side equipment provided in the embodiments of the present disclosure may be applied in a wireless communication system. The wireless communication system may be a system using the fifth generation (5th Generation, 5G) mobile communication technology (hereinafter referred to as 5G system). Those skilled in the art can understand that the 5G NR system is only an example and not a limitation.

Referring to FIG. 1, FIG. 1 is a structural diagram of a network system to which an embodiment of the present disclosure is applicable. As shown in FIG. ), for example: it can be a mobile phone, a tablet computer (Tablet Personal Computer, TPC), a laptop computer (Laptop Computer, LC), a personal digital assistant (personal digital assistant, PDA), a mobile Internet device (Mobile Internet Device, MID) or a terminal-side device such as a wearable device (Wearable Device, WD), it should be noted that, in the embodiment of the present disclosure, the specific type of the user terminal 11 is not limited. The above-mentioned network side device 12 may be a base station of 5G and later versions (for example: the next generation base station (the next Generation Node B, gNB), 5G NR wireless base station (Node B, NB)), or a base station in other communication systems, or It is called Node B. It should be noted that in the embodiment of the present disclosure, only the 5G base station is taken as an example, but the specific type of the base station 12 is not limited.

At present, for air interface data transmission, taking the relevant 5G/new air interface (New Radio, NR) technology as an example, before the service transmission starts, the base station informs the user terminal of the service data through Radio Resource Control (RRC) signaling mapping and configuration.

After the configuration is complete, the downlink data arrives at the radio access network (Radio Access Network, RAN) in the form of Quality of Service flow (QoS flow) packets, and the service data adaptation protocol layer (Service Data The Adaptation Protocol Layer (SDAP) treats data packets as SDAP Service Data Units (Service Data Units, SDUs) and maps them to the correct downlink radio bearer as SDAP Protocol Data Units (Protocol Data Units, PDUs). The associated internal interface sends to the Packet Data Convergence Protocol Layer (PDCP) in the RAN.

After receiving the SDAP PDU, the PDCP layer processes it as a PDCP SDU. Specifically, the following processing should be performed in sequence: After receiving the data packets from the upper layer, the PDCP layer will number each data packet (called COUNT value) before transmission, and the first few bits of the data packet number are called superframes Number (Hyper Frame Number, HFN), and the last few digits of the packet number are called PDCP Sequence Number (Sequence Number, SN). Then perform header compression depending on the configuration, perform security operations such as integrity protection and encryption depending on the configuration, form a PDCP header and generate a PDCP PDU, where the PDCP SN will be carried in the PDCP header, and then the PDCP PDU is sent to the radio link control protocol layer (Radio Link Control, RLC).

Among them, each PDCP PDU will maintain an SN. The role of the SN mainly includes: to maintain the position of the PDCP PDU in the PDCP cache, to form a COUNT value together with the HFN, to encrypt, decrypt and sort the PDCP PDU, etc.

According to the amount of data traffic, the length of the SN can include various types. Currently, in the NR system, the lengths of the PDCP SN number are 12 bits (bit) and 18 bits respectively. The downlink (Down Link, DL) receiving window length of the PDCP entity is set to 2[pdcp-SN-SizeDL]–1. Among them, PDCP-SN-SizeDL is the length of the downlink SN number. It can be seen that the longer the SN length, the larger the PDCP window, and the larger the occupied buffer; on the contrary, the smaller the SN length, the smaller the PDCP window, and the smaller the occupied buffer.

For HFN, during the relevant unicast reception process, the terminal will maintain HFN independently. When the transmission is initialized, HFN will be set to 0. When the window slides, causing SN to exceed the maximum length of the window, HFN will automatically flip. In the MBS service, when the terminal performs service reception, the service may have been carried out for a period of time. In order to avoid the problem that the UE side cannot know the HFN of the initialization data packet, the network side device can use the radio resource control (Radio Resource Control, RRC) The signaling sends the specific value of the HFN to the terminal.

After the network-side device sends the specific value of HFN to the terminal through signaling, and after the terminal receives the HFN, the network-side device sends PDCP data PDU. However, because the terminal needs a certain processing delay to receive RRC signaling, for example, when the channel quality is poor, the retransmission of the Radio Link Control (RLC) protocol will cause delays in receiving RRC signaling, and it may also be Since the HFN and the PDCP data PDU are sent to the terminal by different network units, the initial HFN received by the terminal is inconsistent with the HFN actually used in the PDCP data PDU.

For example, as shown in Figure 2, after the network side device sends the HFN through RRC signaling, due to the delay, when the terminal receives the HFN indicated by the RRC signaling, the HFN of the PDCP data PDU sent by the network side device has already An update has been made. For example, because the SN has been reversed, that is, the SN has reached the maximum value, it needs to start counting from zero, and the HFN needs to be incremented by 1. As a result, the initial HFN obtained by the terminal is inconsistent with the HFN actually used in the received PDCP data PDU question.

In order to solve the above problems, an embodiment of the present disclosure provides a HFN processing method, which can indicate whether the first HFN corresponding to the PDCP data packet is the HFN (second HFN) initially sent to the terminal when the network side device sends the PDCP data packet, And when it is determined that the first HFN corresponding to the PDCP data packet is different from the HFN initially sent to the terminal by the network side device, the first HFN corresponding to the PDCP data packet can be processed to determine the updated HFN, so that for the received PDCP For data packets, the HFN determined by the terminal is kept in sync with the HFN when the network side device sends data.

In the embodiments of the present disclosure, one of the embodiments provides a HFN processing method, which is executed by the terminal, as shown in FIG. 3 , the method includes:

S310, receiving a PDCP data packet sent by the network side device;

S320. Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, where the second HFN is sent to the terminal by the network side device through signaling;

S330. If the first HFN is different from the second HFN, process the first HFN.

Optionally, the HFN processing method described in the embodiments of the present disclosure is applied to the HFN data transmission method in which the network side device sends the PDCP data packet to the terminal before sending the PDCP data packet to the terminal. Optionally, in step S310, the PDCP data packet sent by the network side device may be but not limited to be MBS data. Using the method described in the embodiment of the present disclosure, before step S310, the network side device sends the HFN of the PDCP data packet to be sent to the terminal, such as the second HFN.

Compared with related technologies, the terminal determines the HFN number of the received PDCP data packet according to the HFN indicated by the network side device before sending the PDCP data packet, adopts the HFN processing method described in the embodiment of the present disclosure, and according to the PDCP number sent by the network side device data packet, the terminal judges whether the first HFN corresponding to the PDCP data packet is the HFN (second HFN) initially indicated by the network side device, so as to avoid the HFN determined by the terminal being out of sync with the HFN when the network side device sends data question.

Optionally, the method also includes:

Obtain data configuration information sent by the network side device; the data configuration information includes the second HFN.

Wherein, when the PDCP data packet sent by the network side device is MBS data, the data configuration information is MBS configuration information. Optionally, the data configuration information is sent through RRC signaling.

Optionally, in addition to the second HFN number, the MBS configuration information also includes at least one of MBS resource location, logical channel configuration information and radio network temporary identity (Radio Network Temporary Identity, RNTI) information.

In the embodiment of the present disclosure, optionally, after receiving the MBS configuration information sent by the network side device, the terminal feeds back a configuration success message to the network side device. The network side device sends a PDCP data packet to the terminal according to the configuration success message sent by the terminal.

The HFN processing method described in the embodiments of the present disclosure, in one implementation mode, when the network side device sends a PDCP data packet to the terminal, the network side device directly indicates the HFN number when the network side device sends the PDCP data packet through the sent PDCP data packet Whether it is the first HFN number (that is, indicating whether the first HFN corresponding to the PDCP data packet is the same as the second HFN), can also be understood as indicating whether the HFN of the currently sent PDCP data packet is compared with the initially indicated HFN An update occurs.

Using this embodiment, in step S310, when receiving the PDCP data packet sent by the network side device, the PDCP data packet includes HFN number update indication information, which is used to indicate the first HFN corresponding to the PDCP data packet sent by the network side device. Whether the second HFN is the same.

Optionally, the HFN number update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

Optionally, the HFN number update indication information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or is sent through the PDCP control PDU of the PDCP data packet.

In one of the implementation manners, optionally, the PDCP data packet sent by the network side device includes a preset indicator bit, where the preset indicator bit is a first value, such as 1, indicating the first HFN corresponding to the PDCP data packet Different from the second HFN, that is, compared with the second HFN indicated by the network side device before sending the PDCP data packet, the HFN of the PDCP data packet sent by the network side device has been updated; the preset indication bit is the second The value, if it is 0, indicates that the first HFN corresponding to the PDCP data packet is the same as the second HFN, that is, compared with the second HFN indicated by the network side device before sending data, the data packet sent by the network side device HFN did not update.

In one embodiment, for example, the HFN number update instruction information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP packet, as shown in Figure 4, the HFN number update instruction information is in the PDCP data PDU The indication bit I in the message header of the PDCP data PDU is the HFN number update indication information. The HFN number update indication information may include 1 bit, which is used to indicate that the network side device indicates before sending the data. The second HFN is whether the HFN of the PDCP packet sent by the network side device has been updated. Optionally, the message header also includes the SN of the sent PDCP data.

Specifically, the indication bit I is the first value, if it is 1, it is used to indicate that the HFN of the PDCP data packet sent by the network side device has been updated compared to the second HFN indicated by the network side device before sending data , that is, the first HFN corresponding to the PDCP data packet is different from the second HFN; when the indicator bit I is the second value, such as 0, it is used to indicate that it is compared with the second HFN indicated by the network side device before sending data The HFN of the PDCP data packet sent by the network side device is not updated, that is, the first HFN corresponding to the PDCP data packet is the same as the second HFN.

In another embodiment, the HFN number update instruction information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the data, as shown in Figure 5, the HFN number update instruction information is sent in the message header of the PDCP data PDU , the message header of the PDCP data PDU includes an indication bit I and a number bit HFNL. Among them, the indication bit I may include 1 bit, which is used to indicate whether the HFN of the PDCP data packet sent by the network side device has been updated compared with the second HFN indicated by the network side device before sending data, that is, indicates that the PDCP Whether the first HFN corresponding to the data packet is the same as the second HFN. The number bit HFNL, the length is Nbit, and N is an integer greater than 1. As shown in Figure 5, the HFN used to instruct the network side device to send the PDCP data packet has been updated. After the update, the lowest HFN (that is, the first HFN) The value corresponding to N bits, wherein N is an integer greater than or equal to 1; that is, the value from the first bit to the Nth bit used to indicate the first HFN; wherein, the first bit is the lowest bit of the first HFN, N is an integer greater than or equal to 1. In case N is equal to 1, the number bit HFNL indicates only the value of the lowest bit of the first HFN.

In yet another embodiment, the HFN number update instruction information is sent through the packet data convergence protocol layer PDCP control protocol data unit PDU of the data, that is, the PDCP control PDU is added to send the HFN number update instruction information. In the embodiment of the present disclosure, one implementation manner, as shown in FIG. 6, optionally, the HFN number update indication information sent by the PDCP control PDU includes the number bit HFNL, the length is M bits, and M is an integer greater than or equal to 1, As shown in Figure 6, the HFN used to instruct the network side device to send the PDCP data packet is updated, and the value corresponding to the lowest N bits of the updated HFN (that is, the first HFN), where N is an integer greater than or equal to 1 ; That is, the value from the first bit to the Nth bit used to indicate the first HFN; wherein, the first bit is the lowest bit of the first HFN, and N is an integer greater than or equal to 1. In case N is equal to 1, the number bit HFNL indicates only the value of the lowest bit of the first HFN. It should be noted that, the specific implementation manner of indicating the HFN number update indication information through the PDCP data packet sent by the network side device is not limited to the above-mentioned manners, and each implementation manner is not illustrated here.

In the embodiment of the present disclosure, in one implementation manner, in step S330, if the first HFN is different from the second HFN, processing the first HFN includes:

A value obtained by adding 1 to the second HFN is determined as the first HFN.

In another embodiment, in the case where the HFN number update instruction includes indicating the value corresponding to the lowest N bits of the first HFN, in step S330, the processing of the first HFN includes:

The specific implementation process of the HFN processing method described in the present disclosure will be described below in conjunction with specific embodiments.

Using the HFN processing method described in the embodiment of the present disclosure, in this embodiment, the PDCP data packet sent by the network side device indicates the HFN number update instruction information, and the specific implementation process using this embodiment includes the following steps:

The terminal receives the MBS configuration information sent by the network side device; optionally, the MBS configuration information includes MBS resource location, logical channel configuration information, RNTI information and the second HFN of the PDCP data packet to be sent. In this embodiment, if the SN length is set to 18bit, then the HFN length is 32-18=14bit, and the second HFN can be set to 10010001001001;

After receiving the MBS configuration information, the terminal feeds back a successful configuration message to the network side device;

After receiving the configuration success message sent by the terminal, the network side device sends a PDCP data packet of MBS data to the terminal;

Using the HFN processing method described in the embodiments of the present disclosure, the PDCP data packet sent by the network side device includes HFN update instruction information.

The terminal determines whether the first HFN corresponding to the PDCP data packet is the same as the second HFN according to the HFN update indication information, and processes the first HFN when it is determined that the first HFN is different from the second HFN.

In one embodiment, as shown in FIG. 4 , when the HFN number update indication information only includes the indication bit 1, it is used to indicate whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, according to the indication bit 1 , to determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN. Wherein, when the value of the indicator bit 1 is 1, it is determined that the first HFN corresponding to the PDCP data packet is different from the second HFN, that is, when the network side device sends the PDCP data packet, the HFN is updated, and it is considered that the SN A rollover has occurred, and it is determined that the value of the first HFN should be increased by 1 compared to the value of the second HFN.

Based on this, the value obtained by adding 1 to the second HFN is determined as the first HFN. In a case where the second HFN is 10010001001001, the first HFN obtained by adding 1 is 10010001001010.

When the value of the indicator bit 1 is 0, it is determined that the first HFN corresponding to the PDCP data packet is the same as the second HFN, that is, when the network side device sends the PDCP data packet, the HFN is not updated, and it is determined that the PDCP data packet corresponds to The first HFN of is equal to the second HFN, that is, 10010001001001.

In another embodiment, as shown in FIG. 5, when the HFN number update instruction information in the message header of the PDCP data PDU includes the indicator bit 1 and the number bit HFNL, the PDCP data packet sent by the network side device is judged according to the value of the indicator bit 1 Whether the corresponding first HFN is the same as the second HFN. Wherein, when the value of the indicator bit 1 is 1, it is determined that the first HFN corresponding to the PDCP data packet is different from the second HFN, that is, when the network side device sends the PDCP data packet, the HFN is updated, and the SN is considered to be reversed; When the value of the indication bit 1 is 0, it is determined that the first HFN corresponding to the PDCP data packet is the same as the second HFN.

In addition, when the value of the indication bit 1 is 1, the value indicated by the number bit HFNL is further determined, and the corresponding bit of the second HFN is updated according to the value indicated by the number bit HFNL to obtain the first HFN corresponding to the PDCP packet. HFN.

For example, as shown in Figure 5, when HFNL includes the lowest first and second digits, the lowest first digit corresponding to the HFN number indicated by HFNL is 0, and the lowest second digit corresponding to the HFN number indicated by HFNL is 0. When the bit is 1, when the second HFN is 10010001001001, the corresponding bit of the second HFN is updated to obtain that the first HFN corresponding to the PDCP data packet is 10010001001010.

In yet another implementation manner, the HFN number update instruction information is sent through the PDCP control PDU. As shown in FIG. 6 , the HFN number update instruction information includes the number bit HFNL. Wherein, the message header of the PDCP control PDU includes the PDU type Type, which is used to indicate that the PDCP control PDU indicates that the first HFN corresponding to the PDCP data packet is updated compared with the second HFN. According to the PDCP control PDU, the terminal reads the number bit HFNL in the message header of the PDCP control PDU. The lowest first bit of the corresponding HFN number indicated by HFNL is 0, and the lowest second bit of the corresponding HFN number indicated by HFNL is 1. When the second HFN is 10010001001001, update the corresponding bit of the second HFN to obtain the first HFN corresponding to the PDCP data packet as 10010001001010.

According to the HFN processing method in another embodiment of the present invention, according to the SN in the PDCP data packet, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN.

In this embodiment, in conjunction with FIG. 3, in step S320, determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

Optionally, when the network side device sends the second HFN to the terminal, it also sends to the terminal the first SN corresponding to the PDCP data packet to be sent, so that the terminal can determine according to the first SN and the second SN in the PDCP data packet Whether the first HFN corresponding to the sent PDCP data packet is the same as the second HFN.

Optionally, when the PDCP data packet is MBS data, when the network side device sends MBS configuration information to the terminal, the MBS configuration information includes the first SN and the second HFN. Specifically, in this embodiment, the MBS configuration information includes MBS resource location, logical channel configuration information, RNTI information, the second HFN corresponding to the PDCP data packet to be sent, and the first SN corresponding to the PDCP data packet to be sent.

Same as the previous embodiment, after receiving the MBS configuration information sent by the network side device, the terminal feeds back a configuration success message to the network side device.

Further, after receiving the MBS configuration information, the method further includes: determining a first window and a second window according to the first SN; wherein, the first window is [SNini, 2maxSN–1-1], The second window is [0, 2maxSN−1-1-SNini]; SNini is the first SN, and maxSN is the maximum value of SN.

Wherein, in step S320, according to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, including:

Specifically, after receiving the PDCP data packet sent by the network-side device, the terminal determines the SN in the PDCP data packet, that is, obtains the second SN, compares the second SN with the first window and the second window, and determines that the second SN belongs to the Which window can determine whether the SN is reversed, so as to further determine whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

As shown in Figure 7, according to the first SN of the PDCP packet to be sent indicated by the network side device in the signaling, such as SNini, the number range [0, maxSN] of the SN can be divided into two windows, that is, the first SN The first window [SNini, 2maxSN–1-1] and the second window [0, 2maxSN–1-1-SNini], it can be understood that when the SN does not flip, the sent PDCP packets continue to be numbered from SNini, It is located in the first window; when the SN flips, the sent PDCP data packets are numbered from 0, and the renumbered SN will be in the second window. Therefore, according to the second SN in the PDCP data packet, comparing the second SN with the first window and the second window, it can be determined whether the SN is reversed, thereby further determining the first HFN and the first HFN corresponding to the PDCP data packet. Whether the second HFN is the same.

In this embodiment, when the second SN is located in the second window, it is determined that the first HFN corresponding to the PDCP data packet is different from the second HFN, and it is considered that the SN has been flipped, then the first HFN is processed , determining a value obtained by adding 1 to the second HFN as the first HFN corresponding to the PDCP data packet.

With this embodiment, when the second SN is outside the first SN window and the second SN window, the terminal considers that it has received an illegal PDCP packet, and feeds back abnormality report information to the network side device, using An abnormality occurred in the feedback current link.

In the embodiment of the present invention, when it is determined that the first HFN corresponding to the PDCP data packet is the same as the second HFN by using any of the above-mentioned implementation methods, it is determined that the first HFN corresponding to the PDCP data packet sent by the network side device is also equal to the second HFN. HFN.

The HFN processing method described in the embodiment of the present disclosure, after receiving the PDCP data packet sent by the network side device, the method further includes:

Using the method described in the embodiment of the present disclosure, for the first PDCP data packet of the received MBS data, determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, and determine whether the first HFN and the second HFN If the HFNs are different, further process the first HFN. In addition, for the PDCP data packets received after the first PDCP data packet, according to the corresponding first HFN determined by the first PDCP data packet, the corresponding HFN of the subsequent PDCP data packets received is further determined, that is, determined in the usual way Corresponds to HFN.

Using the HFN processing method described in the embodiments of the present disclosure, after receiving the PDCP data packet sent by the network side device, it can be determined according to the HFN update indication information in the PDCP data packet, or according to the SN in the PDCP data packet, the corresponding Whether the first HFN of the network side device is the same as the HFN initially sent to the terminal by the network side device, and if it is determined that the two are not the same, process the first HFN corresponding to the PDCP data packet, and determine the updated HFN, so that for the received For PDCP data packets, the HFN determined by the terminal is kept in sync with the HFN when the network side device sends data.

An embodiment of the present disclosure also provides a method for processing a hyperframe number HFN, which is executed by a network side device, as shown in FIG. 8 , the method includes:

S810, sending a PDCP data packet to the terminal;

Using the super frame number HFN processing method described in the embodiment of the present disclosure, the PDCP data packet sent by the network side device to the terminal includes HFN update indication information, and according to the HFN update indication information, the terminal can determine the No. 1 corresponding to the PDCP data packet Whether the HFN is the same as the HFN initially sent to the terminal by the network-side device, to ensure that the HFN determined by the terminal is synchronized with the HFN when the network-side device sends data.

indicating that the first HFN is the same as the second HFN;

In the embodiment of the present disclosure, the specific implementation manner of sending the HFN update indication information through the PDCP data packet can be referred to the above description with reference to FIG. 4 to FIG. 6 , and will not be described in detail here.

Another embodiment of the present disclosure also provides a terminal, as shown in FIG. 9 , including a memory 910, a transceiver 920, and a processor 900:

The memory 910 is used to store computer programs; the transceiver 920 is used to send and receive data under the control of the processor; the processor 900 is used to read the computer programs in the memory and perform the following operations:

Receive the PDCP data packet sent by the network side device;

Wherein, the processor 900 determines whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, specifically:

indicating that the first HFN is the same as the second HFN;

Optionally, in the terminal, wherein the HFN number update indication information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or through the PDCP control control of the PDCP data packet PDUs are sent.

Optionally, in the terminal, wherein the processor 900 processes the first HFN, specifically:

A value obtained by adding 1 to the second HFN is determined as the first HFN.

Optionally, in the terminal, wherein the processor 900 determines whether the first HFN corresponding to the PDCP packet is the same as the second HFN, specifically:

Optionally, the terminal, wherein the processor 900 is further configured to:

Optionally, in the terminal, after receiving the PDCP data packet sent by the network side device, the processor 900 is further configured to:

Wherein, in FIG. 9 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 900 and various circuits of the memory represented by the memory 910 are linked together. The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein. The bus interface provides the interface. Transceiver 920 may be a plurality of elements, including a transmitter and a receiver, providing means for communicating with various other devices over transmission media, including wireless channels, wired channels, fiber optic cables, etc. Transmission medium. For different user equipments, the user interface 930 may also be an interface capable of connecting externally and internally to required equipment, and the connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

The processor 900 is responsible for managing the bus architecture and general processing, and the memory 910 can store data used by the processor 900 when performing operations.

Optionally, the processor 900 may be a central processing unit (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device ( Complex Programmable Logic Device, CPLD), the processor can also adopt a multi-core architecture.

The processor is used to execute any one of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions by calling the computer program stored in the memory. The processor and memory may also be physically separated.

An embodiment of the present disclosure also provides a network side device, as shown in FIG. 10 , including a memory 1010, a transceiver 1020, and a processor 1000:

The memory 1010 is used to store computer programs; the transceiver 1020 is used to send and receive data under the control of the processor; the processor 1000 is used to read the computer programs in the memory and perform the following operations:

Send a PDCP packet to the terminal;

indicating that the first HFN is the same as the second HFN;

Wherein, in FIG. 10 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1000 and various circuits of the memory represented by the memory 1010 are linked together. The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein. The bus interface provides the interface. The transceiver 1020 may be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical cables, and other transmission media. The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1010 can store data used by the processor 1000 when performing operations.

The processor 1000 may be a central processing device (CPU), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field-Programmable Gate Array, FPGA) or a complex programmable logic device (Complex Programmable Logic Device , CPLD), the processor can also adopt a multi-core architecture.

Another embodiment of the present disclosure also provides a super frame number HFN processing device, which is executed by a terminal. As shown in FIG. 11 , the super frame number HFN processing device 1100 includes:

A receiving unit 1110, configured to receive a PDCP data packet sent by a network side device;

A determining unit 1120, configured to determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, wherein the second HFN is sent to the terminal by the network side device through signaling;

The processing unit 1130 is configured to process the first HFN if the first HFN is different from the second HFN. Optionally, in the HFN processing apparatus, wherein, the PDCP data packet further includes HFN update indication information, and the HFN update indication information is used to indicate that the first HFN corresponding to the PDCP data packet sent by the network side device and the second HFN Whether the two HFNs are the same;

Wherein, the determining unit 1120 determines whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, specifically:

Optionally, in the HFN processing device, the HFN update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

Optionally, in the HFN processing device, wherein, the HFN number update indication information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP packet, or through the PDCP protocol data unit of the PDCP packet Control control PDU transmission.

Optionally, in the HFN processing apparatus, wherein the processing unit 1130 processes the first HFN, specifically:

A value obtained by adding 1 to the second HFN is determined as the first HFN.

Optionally, in the HFN processing apparatus, in the case where the HFN number update indication includes a value corresponding to the lowest N bits indicating the first HFN, the processing unit 1130 processes the first HFN, Specifically:

Optionally, in the HFN processing apparatus, wherein the determining unit 1120 determines whether the first HFN corresponding to the PDCP packet is the same as the second HFN, including:

Optionally, in the HFN processing device, the determining unit 1120 is further configured to:

Wherein, the determining unit 1120 determines whether the first HFN corresponding to the PDCP data packet is the same as the second HFN according to the first SN and the second SN in the PDCP data packet, specifically:

Optionally, in the HFN processing device, the processing unit 1130 is further configured to:

Optionally, in the HFN processing apparatus, after receiving the PDCP data packet sent by the network side device, the determining unit 1120 is further configured to:

Judging whether the PDCP packet is the first packet of the service data of the received MBS service;

When the PDCP data packet is the first data packet of the service data of the received MBS service, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN. The embodiment of the present disclosure also provides a hyperframe number HFN processing device, which is executed by a network side device. As shown in FIG. 12 , the hyperframe number HFN processing device 1200 includes:

A sending unit 1210, configured to send a PDCP data packet to the terminal;

Wherein, the PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN corresponding to the PDCP data packet sent by the network side device is the same as the second HFN; the second HFN is determined by the The network side device sends the signaling to the terminal. Optionally, in the HFN processing device, the HFN number update indication information includes at least one of the following:

indicating that the first HFN is the same as the second HFN;

Indicates the value corresponding to the lowest N bits of the first HFN; wherein, N is an integer greater than or equal to 1. It should be noted that the HFN processing method of the present disclosure and the HFN processing device of the HFN are based on the same disclosed concept, can realize all the method steps realized by the above-mentioned method embodiments, and can achieve the same technical effect, here Parts and beneficial effects in this embodiment that are the same as those in the method embodiment will not be described in detail again.

It should be noted that the division of the units in the embodiment of the present disclosure is schematic, and is only a logical function division, and there may be another division manner in actual implementation. In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on such an understanding, the essence of the technical solution of the present disclosure or the part that contributes to the related technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium. Several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in various embodiments of the present disclosure. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (Magneto-Optical disk, MO) etc.) , Optical storage (such as Compact Disk (CD), Digital Versatile Disc (DVD), Blu-ray Disc (Blu-ray Disc, BD), High-Definition Versatile Disc (HVD), etc.), and Semiconductor memory (such as ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), non-volatile memory ( NAND FLASH), Solid State Disk (Solid State Disk, SSD)), etc.

Those skilled in the art should understand that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Accordingly, the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) having computer-usable program code embodied therein.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each procedure and/or block in the flowchart and/or block diagrams, and combinations of procedures and/or blocks in the flowchart and/or block diagrams can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine, such that instructions executed by the processor of the computer or other programmable data processing equipment produce Means for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These processor-executable instructions may also be stored in a processor-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the processor-readable memory produce a manufacturing product, the instruction device realizes the functions specified in one or more procedures of the flow chart and/or one or more blocks of the block diagram.

These processor-executable instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented The executed instructions provide steps for implementing the functions specified in the procedure or procedures of the flowchart and/or the block or blocks of the block diagrams.

It should be noted that it should be understood that the division of the above modules is only a division of logical functions, which may be fully or partially integrated into a physical entity or physically separated during actual implementation. And these modules can all be implemented in the form of calling software through processing elements; they can also be implemented in the form of hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in the form of hardware. For example, the determining module may be a separate processing element, or may be integrated into a chip of the above-mentioned device. In addition, it may also be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device may Call and execute the functions of the modules identified above. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, and can also be implemented independently. The processing element mentioned here may be an integrated circuit with signal processing capability. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.

For example, each module, unit, subunit or submodule may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (Application Specific Integrated Circuit, ASIC), or, one or Multiple microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA), etc. For another example, when one of the above modules is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can call program codes. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

The terms "first", "second" and the like in the specification and claims of the present disclosure are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the disclosure described herein are practiced, for example, in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus. In addition, the use of "and/or" in the description and claims means at least one of the connected objects, such as A and/or B and/or C, means that it includes A alone, B alone, C alone, and both A and B Existence, both B and C exist, both A and C exist, and there are 7 situations where A, B, and C all exist. Similarly, the use of "at least one of A and B" in the present specification and claims should be understood as "A alone, B alone, or both A and B exist".

Obviously, those skilled in the art can make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and equivalent technologies thereof, the present disclosure also intends to include these modifications and variations.

Claims

A method for processing a hyperframe number HFN, executed by a terminal, the method comprising:

Receive the PDCP data packet sent by the network side device;

Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, where the second HFN is sent to the terminal by the network side device through signaling;

If the first HFN is different from the second HFN, perform processing on the first HFN.
The HFN processing method according to claim 1, wherein the PDCP data packet further includes HFN update indication information, and the HFN update indication information is used to indicate the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device Whether the two HFNs are the same;

Wherein, determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN according to the HFN update indication information.
The HFN processing method according to claim 2, wherein the HFN update indication information includes at least one of the following:

A first indication bit indicating that the first HFN is different from the second HFN;

indicating that the first HFN is the same as the second HFN;

Indicates the value corresponding to the lowest N bits of the first HFN; wherein, N is an integer greater than or equal to 1.
The HFN processing method according to claim 3, wherein the HFN number update indication information is sent through the packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or through the PDCP of the PDCP data packet Control control PDU transmission.
The HFN processing method according to claim 1, wherein said processing the first HFN comprises:

A value obtained by adding 1 to the second HFN is determined as the first HFN.
The HFN processing method according to claim 3, wherein, in the case where the HFN number update indication includes a value corresponding to the lowest N bits indicating the first HFN, said processing the first HFN includes:

The corresponding bits of the second HFN number are updated according to the value corresponding to the lowest N bits to obtain the first HFN number.
The HFN processing method according to claim 1, wherein said determining whether the first HFN corresponding to the PDCP packet is the same as the second HFN comprises:

According to the first SN and the second SN in the PDCP data packet, determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN; wherein, the first SN is signaled by the network side device sent to the terminal.
The HFN processing method according to claim 7, further comprising:

According to the first SN, determine the first window and the second window; wherein, the first window is [SNini, 2maxSN-1-1], and the second window is [0, 2maxSN-1-1-SNini ]; SNini is the first SN, and maxSN is the maximum value of SN;

Wherein, according to the first SN and the second SN in the PDCP data packet, determining whether the first HFN corresponding to the PDCP data packet is the same as the second HFN includes:

When the second SN is located in the first window, determine that the first HFN corresponding to the PDCP data packet is the same as the second HFN;

When the second SN is located in the second window, it is determined that the first HFN corresponding to the PDCP data packet is different from the second HFN.
The HFN processing method according to claim 8, said method further comprising:

When the second SN is outside the first SN window and the second SN window, feeding back abnormality report information to the network side device.
The HFN processing method according to claim 1, after receiving the PDCP packet sent by the network side device, further comprising:

Judging whether the PDCP data packet is the first data packet of the service data of the received MBS service;

When the PDCP data packet is the first data packet of the service data of the received MBS service, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN.
A method for processing a hyperframe number HFN, performed by a network side device, the method comprising:

Send a PDCP packet to the terminal;

Wherein, the PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN corresponding to the PDCP data packet sent by the network side device is the same as the second HFN; the second HFN is determined by the The network side device sends the signaling to the terminal.
The HFN processing method according to claim 11, wherein the HFN number update instruction information includes at least one of the following:

A first indication bit indicating that the first HFN is different from the second HFN;

indicating that the first HFN is the same as the second HFN;

Indicates the value corresponding to the lowest N bits of the first HFN; wherein, N is an integer greater than or equal to 1.
A terminal comprising a memory, a transceiver and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

Receive the PDCP data packet sent by the network side device;

Determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, where the second HFN is sent to the terminal by the network side device through signaling;

If the first HFN is different from the second HFN, perform processing on the first HFN.
The terminal according to claim 13, wherein the HFN update indication information includes at least one of the following:

A first indication bit indicating that the first HFN is different from the second HFN;

indicating that the first HFN is the same as the second HFN;

Indicates the value corresponding to the lowest N bits of the first HFN; wherein, N is an integer greater than or equal to 1.
A network side device, including a memory, a transceiver and a processor:

The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

Send a PDCP packet to the terminal;

Wherein, the PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN corresponding to the PDCP data packet sent by the network side device is the same as the second HFN; the second HFN is determined by the The network side device sends the signaling to the terminal.
A super frame number HFN processing device, executed by a terminal, comprising:

a receiving unit, configured to receive a PDCP packet sent by a network side device;

A determining unit, configured to determine whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, wherein the second HFN is sent to the terminal by the network side device through signaling;

A processing unit, configured to process the first HFN if the first HFN is different from the second HFN.
A super frame number HFN processing device, executed by a network side device, comprising:

a sending unit, configured to send a PDCP packet to the terminal;

Wherein, the PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN corresponding to the PDCP data packet sent by the network side device is the same as the second HFN; the second HFN is determined by the The network side device sends the signaling to the terminal.
A processor-readable storage medium, the processor-readable storage medium stores a computer program, the computer program is used to enable the processor to perform the hyperframe number HFN processing described in any one of claims 1 to 10 method, or execute the hyperframe number HFN processing method described in any one of claims 11 to 12.