Hyperframe number HFN processing method, device, terminal and base station

Abstract

The present application provides a HFN processing method, device, terminal and base station. The method includes: receiving a PDCP data packet sent by a network side device; determining 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; if the first HFN is different from the second HFN, the first HFN is processed. Using this method, when the network side device sends a PDCP data packet, it can indicate whether the first HFN corresponding to the PDCP data packet is the HFN (second HFN) initially sent to the terminal, so that the terminal can process the first HFN corresponding to the PDCP data packet, determine the updated HFN, and ensure that the HFN determined by the terminal is synchronized with the HFN when the network side device sends data.

Description

Technical Field

[0001] The present application relates to the field of wireless technology, and in particular to a hyper frame number (HFN) processing method, device, terminal and base station. Background Art

[0002] In the current New Radio (NR) technology, when sending service data packets, the Packet Data Convergence Protocol Layer (PDCP) on the network side uses the data packet number of the corresponding PDCP data packet, that is, the COUNT value, when performing operations such as integrity protection and encryption on the PDCP data packet. The terminal UE side also uses the COUNT value corresponding to the PDCP data PDU when performing corresponding integrity checks and decryption operations after receiving the PDCP data protocol data unit (PDU).

[0003] For multicast broadcast service (MBS) data transmission, according to the prior art, all UEs receive the same PDCP data PDU on the same multicast broadcast service radio bearer (MBS Radio Bearer, MRB). When a specific UE starts to receive the MRB corresponding to a certain 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 COUNT value corresponding to the first PDCP data PDU received by the UE is not 0, and the HFN value in the corresponding COUNT value may not be 0. If the UE continues to use the unicast mechanism and assumes that the HFN corresponding to the first received PDCP data PDU starts from 0, the corresponding relationship between the PDCP data PDU received on the UE side and the COUNT value will be different from the corresponding corresponding relationship on the network side.

[0004] In order to ensure that the HFN on the UE side is valid in the MBS service, there is currently research on the technology of sending HFN from the network side to the terminal. The specific method can be that the network side device sends the specific value of HFN to the terminal through Radio Resource Control (RRC) signaling. The network side device can send PDCP data PDU after the terminal receives the HFN. However, since 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 a delay in the reception of RRC signaling. It may also be because the HFN and PDCP data PDU are sent to the terminal by different network units, resulting in the initial HFN received by the terminal being inconsistent with the HFN actually used in the PDCP data PDU. Summary of the invention

[0005] The purpose of the present application is to provide a hyperframe number (HFN) processing method, device, terminal and base station, which are used to solve the problem in the prior art that the initial HFN received by the terminal is not synchronized with the HFN actually used in the PDCP data PDU.

[0006] The embodiment of the present application provides a method for processing a hyperframe number HFN, wherein the method is executed by a terminal and includes:

[0007] Receive PDCP data packets sent by network side devices;

[0008] Determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein the second HFN is sent to the terminal by the network side device through signaling;

[0009] If the first HFN is different from the second HFN, the first HFN is processed.

[0010] Optionally, in the HFN processing method, the PDCP data packet further includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same;

[0011] Wherein, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same includes:

[0012] According to the HFN update indication information, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

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

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

[0015] A second indication bit indicating that the first HFN is the same as the second HFN;

[0016] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0017] Optionally, in the HFN processing method, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit (PDU) of the PDCP data packet, or via a PDCP control PDU of the PDCP data packet.

[0018] Optionally, in the HFN processing method, the processing of the first HFN includes:

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

[0020] Optionally, in the HFN processing method, when the HFN update indication includes a value corresponding to the lowest N bits of the first HFN, the processing of the first HFN includes:

[0021] According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

[0022] Optionally, in the HFN processing method, the determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same includes:

[0023] According to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same; wherein the first SN is sent to the terminal by the network side device through signaling.

[0024] Optionally, the HFN processing method further comprises:

[0025] According to the first SN, a first window and a second window are determined; wherein the first window is [SN ini , 2 maxSN –1 -1], the second window is [0, 2 maxSN–1 -1-SN ini ]; SNini is the first SN, maxSN is the maximum value of SN;

[0026] Wherein, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the first SN and the second SN in the PDCP data packet includes:

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

[0028] 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.

[0029] Optionally, the HFN processing method further comprises:

[0030] When the second SN is located outside the first SN window and the second SN window, abnormal report information is fed back to the network side device.

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

[0032] Determining whether the PDCP data packet is the first data packet of service data of the received MBS service;

[0033] When the PDCP data packet is the first data packet of service data of the received MBS service, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0034] The embodiment of the present application further provides a method for processing a hyperframe number HFN, wherein the method is performed by a network side device and includes:

[0035] Send PDCP data packets to the terminal;

[0036] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

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

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

[0039] A second indication bit indicating that the first HFN is the same as the second HFN;

[0040] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0041] The embodiment of the present application further provides a terminal, which includes a memory, a transceiver, and a processor:

[0042] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0043] Receive PDCP data packets sent by network side devices;

[0044] Determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein the second HFN is sent to the terminal by the network side device through signaling;

[0045] If the first HFN is different from the second HFN, the first HFN is processed.

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

[0047] The processor determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, specifically:

[0048] According to the HFN update indication information, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0049] Optionally, in the terminal, the HFN update indication information includes at least one of the following:

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

[0051] A second indication bit indicating that the first HFN is the same as the second HFN;

[0052] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0053] Optionally, in the terminal, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or is sent via a PDCP control PDU of the PDCP data packet.

[0054] Optionally, in the terminal, the processor processes the first HFN by:

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

[0056] Optionally, in the terminal, when the HFN update indication includes a value corresponding to the lowest N bits of the first HFN, the processor processes the first HFN, specifically:

[0057] According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

[0058] Optionally, in the terminal, the processor determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, specifically:

[0059] According to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same; wherein the first SN is sent to the terminal by the network side device through signaling.

[0060] Optionally, in the terminal, the processor is further configured to:

[0061] According to the first SN, a first window and a second window are determined; wherein the first window is [SN ini , 2 maxSN –1 -1], the second window is [0, 2 maxSN–1 -1-SN ini ]; SN ini is the first SN, maxSN is the maximum value of SN;

[0062] Wherein, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the first SN and the second SN in the PDCP data packet includes:

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

[0064] 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.

[0065] Optionally, in the terminal, the processor is further configured to:

[0066] When the second SN is located outside the first SN window and the second SN window, abnormal report information is fed back to the network side device.

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

[0068] Determining whether the PDCP data packet is the first data packet of service data of the received MBS service;

[0069] When the PDCP data packet is the first data packet of service data of the received MBS service, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0070] The embodiment of the present application further provides a network side device, which includes a memory, a transceiver and a processor:

[0071] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0072] Send PDCP data packets to the terminal;

[0073] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

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

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

[0076] A second indication bit indicating that the first HFN is the same as the second HFN;

[0077] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0078] The embodiment of the present application further provides a hyperframe number HFN processing device, which is executed by a terminal, and the device includes:

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

[0080] a determining unit, configured to determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein the second HFN is sent to the terminal by the network side device through signaling;

[0081] A processing unit is configured to process the first HFN if the first HFN is different from the second HFN.

[0082] The present application also provides a hyperframe number HFN processing device of another embodiment, wherein the device is executed by a network side device, and the device includes:

[0083] A sending unit, used to send a PDCP data packet to a terminal;

[0084] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

[0085] An embodiment of the present application further 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 hyperframe number HFN processing method as described in any one of the above items.

[0086] The beneficial effects of the above technical solution of the present application are as follows:

[0087] The HFN processing method described in the embodiment of the present application 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 a 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 data packet, the HFN determined by the terminal is synchronized with the HFN when the network side device sends data. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] Figure 1 A schematic diagram of the structure of a system used by the method described in the embodiment of the present application;

[0089] Figure 2 A schematic diagram to illustrate the process of SN flipping;

[0090] Figure 3 A schematic diagram of a process flow of a HFN treatment method according to one embodiment of the present application;

[0091] Figure 4This is one of the implementation structures of the HFN update indication information in the embodiment of the present application;

[0092] Figure 5 This is the second implementation structure of the HFN update indication information in the embodiment of the present application;

[0093] Figure 6 This is the third implementation structure of the HFN update indication information in the embodiment of the present application;

[0094] Figure 7 This is a schematic diagram of the principle of the first window and the second window set in the embodiment of the present application;

[0095] Figure 8 This is a flow chart of a HFN treatment method according to another embodiment of the present application;

[0096] Fig. 9 This is a schematic diagram of the structure of the terminal described in the embodiment of the present application;

[0097] Fig.10 This is a schematic diagram of the structure of the network side device described in the embodiment of the present application;

[0098] Fig.11 This is a schematic structural diagram of a HFN processing device according to one embodiment of the present application;

[0099] Fig.12 It is a structural schematic diagram of a HFN processing device according to another embodiment of the present application. DETAILED DESCRIPTION

[0100] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0101] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0102] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

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

[0104] See also Figure 1 , Figure 1 is a structural diagram of a network system to which the embodiments of the present application can be applied, such as Figure 1 As shown, it includes a terminal 11 and a network side device 12, wherein the terminal 11 may be a user equipment (UE), for example, it may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (PDA for short), a mobile Internet device (Mobile Internet Device, MID) or a wearable device (Wearable Device) and other terminal side devices. It should be noted that the specific type of the user terminal 11 is not limited in the embodiment of the present application. The above-mentioned network side device 12 may be a base station of 5G and later versions (for example: gNB, 5G NR NB), or a base station in other communication systems, or referred to as a node B. It should be noted that in the embodiment of the present application, only a 5G base station is taken as an example, but the specific type of the base station 12 is not limited.

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

[0106] After the configuration is completed, the downlink data arrives at the Radio Access Network (RAN) in the form of Quality of Service flow (QoS flow) data packets. The Service Data Adaptation Protocol Layer (SDAP) in the RAN regards the data packets as SDAP service data units (SDUs), maps them to the correct downlink radio bearer, and sends them as SDAP protocol data units (PDUs) to the Packet Data Convergence Protocol Layer (PDCP) in the RAN through the internal interface associated with the downlink radio bearer.

[0107] After receiving the SDAP PDU, the PDCP layer processes it as a PDCP SDU. Specifically, the following processes should be performed in sequence: After receiving the data packet from the upper layer, the PDCP layer will number each data packet before transmission (called the COUNT value), where the first few bits of the data packet number are called the Hyper Frame Number (HFN), and the last few bits of the data packet number are called the PDCP Sequence Number (SN). Then, header compression is performed depending on the configuration, and security operations such as integrity protection and encryption are performed depending on the configuration, forming a PDCP header and generating 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).

[0108] Each PDCP PDU maintains a SN. The main functions of the SN include: maintaining the position of the PDCP PDU in the PDCP buffer, forming a COUNT value together with the HFN, and being used for encryption, decryption and sorting of the PDCP PDU.

[0109] The length of the SN can be varied depending on the amount of data traffic. Currently, in the NR system, the length of the PDCP SN is 12 bits and 18 bits respectively. The length of the downlink (DL) receiving window of the PDCP entity is set to 2 [pdcp -SN-SizeDL]–1 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; conversely, the smaller the SN length, the smaller the PDCP window and the smaller the occupied buffer.

[0110] For HFN, in the existing unicast reception process, the terminal will maintain HFN separately. When initializing the transmission, HFN will be set to 0. When the window slides and causes the SN to exceed the maximum length of the window, HFN will automatically flip. In MBS services, when the terminal performs service reception, the service may have been executed for a period of time. To avoid the problem that the UE side cannot know the HFN of the initialization data packet, the network side device can send the specific HFN value to the terminal through Radio Resource Control (RRC) signaling.

[0111] After the network side device sends the specific value of HFN to the terminal through signaling, after the terminal receives HFN, the network side device sends PDCP data PDU. However, since 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 a delay in the reception of RRC signaling. It may also be because the HFN and PDCP data PDU are sent to the terminal by different network units, resulting in the initial HFN received by the terminal being inconsistent with the HFN actually used in the PDCP data PDU.

[0112] For example, Figure 2 As shown in the figure, 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 been updated. For example, since the SN has been flipped, that is, the SN has reached the maximum value and needs to be counted from zero, the HFN needs to be increased by 1, resulting in the initial HFN obtained by the terminal being inconsistent with the HFN actually used in the received PDCP data PDU.

[0113] To solve the above problems, an embodiment of the present application 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 a 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 an updated HFN, so that for the received PDCP data packet, the HFN determined by the terminal is synchronized with the HFN when the network side device sends data.

[0114] In one embodiment of the present application, a HFN processing method is provided, which is executed by a terminal, such as Figure 3 As shown, the method includes:

[0115] S310, receiving a PDCP data packet sent by a network side device;

[0116] S320, determining whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein the second HFN is sent to the terminal by the network side device through signaling;

[0117] S330: If the first HFN is different from the second HFN, process the first HFN.

[0118] Optionally, the HFN processing method described in the embodiment of the present application is applied to a data transmission method in which a network side device sends a HFN of a PDCP data packet to be sent to a terminal before sending a PDCP data packet to the terminal. Optionally, in step S310, the PDCP data packet sent by the network side device can be but is not limited to only being MBS data. Using the method described in the embodiment of the present application, 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.

[0119] Compared with the prior art, 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. The HFN processing method described in the embodiment of the present application is adopted. According to the PDCP data packet sent by the network side device, the terminal determines 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 problem that the HFN determined by the terminal is not synchronized with the HFN when the network side device sends data.

[0120] Optionally, the method further comprises:

[0121] Acquire data configuration information sent by a network side device; the data configuration information includes the second HFN.

[0122] 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 via RRC signaling.

[0123] Optionally, the MBS configuration information includes, in addition to the second HFN number, at least one of a resource location of the MBS, logical channel configuration information, and Radio Network Temporary Identity (RNTI) information.

[0124] In the embodiment of the present application, 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.

[0125] In one implementation of the HFN processing method described in the embodiments of the present application, when a network side device sends a PDCP data packet to a terminal, the network side device directly indicates through the sent PDCP data packet whether the HFN number when the network side device sends the PDCP data packet is the first HFN number (that is, whether the first HFN and the second HFN corresponding to the PDCP data packet are the same), which can also be understood as indicating whether the HFN of the currently sent PDCP data packet is updated compared to the initially indicated HFN.

[0126] In this implementation, in step S310, when a PDCP data packet sent by a network device is received, the PDCP data packet includes HFN update indication information for indicating whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network device are the same.

[0127] Optionally, the HFN update indication information includes at least one of the following:

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

[0129] A second indication bit indicating that the first HFN is the same as the second HFN;

[0130] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0131] Optionally, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or is sent via a PDCP control PDU of the PDCP data packet.

[0132] In one embodiment, optionally, the PDCP data packet sent by the network side device includes a preset indication bit, wherein the preset indication bit is a first value, such as 1, indicating that the first HFN corresponding to the PDCP data packet is 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 is updated; the preset indication bit is a second value, such as 0, indicating 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 the data, the HFN of the data packet sent by the network side device has not been updated.

[0133] In one implementation manner, for example, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, such as Figure 4 As shown, the HFN update indication information is sent in the message header of the PDCP data PDU, and the indication bit 1 in the message header of the PDCP data PDU is the HFN update indication information, and the HFN update indication information may include 1 bit, which is used to indicate whether the HFN of the PDCP data packet sent by the network side device is updated compared to the second HFN indicated by the network side device before sending the data. Optionally, the message header also includes the SN of the sent PDCP data.

[0134] Specifically, the indicator bit I is a first value, such as 1, which is used to indicate that compared with the second HFN indicated by the network side device before sending the data, the HFN of the PDCP data packet sent by the network side device is updated, that is, the first HFN corresponding to the PDCP data packet is different from the second HFN; when the indicator bit I is a second value, such as 0, it is used to indicate that compared with the second HFN indicated by the network side device before sending the 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.

[0135] In another implementation manner, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the data, such as Figure 5 As shown, the HFN update indication information is sent in the message header of the PDCP data PDU, and the message header of the PDCP data PDU includes an indication bit I and a number bit HFN L 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 is updated compared to the second HFN indicated by the network side device before sending the data, that is, whether the first HFN and the second HFN corresponding to the PDCP data packet are the same. L , with a length of N bits, where N is an integer greater than 1, such as Figure 5 As shown, the HFN used to indicate that the network side device sends 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; where the first bit is the lowest bit of the first HFN, and N is an integer greater than or equal to 1. When N is equal to 1, the number HFN L Only the value of the least significant bit of the first HFN is indicated.

[0136] In another implementation manner, the HFN update indication information is sent via a packet data convergence protocol layer PDCP control protocol data unit PDU of the data, that is, a PDCP control PDU is added to send the HFN update indication information. In the embodiments of the present application, one implementation manner, such as Figure 6 As shown, optionally, the HFN update indication information sent by the PDCP control PDU includes the number bit HFN L , with a length of M bits, where M is an integer greater than or equal to 1, such as Figure 6 As shown, the HFN used to indicate that the network side device sends 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; where the first bit is the lowest bit of the first HFN, and N is an integer greater than or equal to 1. When N is equal to 1, the number HFN L It only indicates the value of the least significant bit of the first HFN. It should be noted that the specific implementation of the PDCP data packet sent by the network side device to indicate the HFN update indication information is not limited to the above-listed methods, and each implementation method is not illustrated here.

[0137] In one implementation of the present application, in step S330, if the first HFN is different from the second HFN, processing the first HFN includes:

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

[0139] In another implementation manner, when the HFN update indication includes indicating a value corresponding to the lowest N bits of the first HFN, in step S330, the processing of the first HFN includes:

[0140] According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

[0141] The specific implementation process of the HFN treatment method described in this application is described below in conjunction with specific embodiments.

[0142] The HFN processing method described in the embodiment of the present application is adopted. In this embodiment, the PDCP data packet sent by the network side device indicates HFN update indication information. The specific implementation process of this embodiment includes the following steps:

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

[0144] After receiving the MBS configuration information, the terminal feeds back a configuration success message to the network side device;

[0145] 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;

[0146] Using the HFN processing method described in the embodiment of the present application, the PDCP data packet sent by the network side device includes HFN update indication information.

[0147] The terminal determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the HFN update indication information, and processes the first HFN when it is determined that the first HFN and the second HFN are not the same.

[0148] One implementation method, combined with Figure 4 As shown, when the HFN update indication information includes only the indication bit 1, which is used to indicate whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, whether the first HFN corresponding to the PDCP data packet is the same as the second HFN is determined according to the value of the indication bit 1. Wherein, when the value of the indication 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, it is considered that the SN is flipped, and it is determined that the value of the first HFN should be increased by 1 compared with the second HFN.

[0149] Based on this, a value obtained by adding 1 to the second HFN is determined as the first HFN. When the second HFN is 10010001001001, the first HFN obtained by adding 1 is 10010001001010.

[0150] When the value of the indicator bit I 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 first HFN corresponding to the PDCP data packet is equal to the second HFN, that is, 10010001001001.

[0151] Another embodiment, combined with Figure 5As shown, the HFN update indication information in the message header of the PDCP data PDU includes an indication bit I and a number bit HFN L When the value of the indicator bit I is 1, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same. When the value of the indicator bit I is 1, it is determined that the first HFN and the second HFN corresponding to the PDCP data packet are different, that is, when the network side device sends the PDCP data packet, the HFN is updated, and it is considered that the SN is flipped; when the value of the indicator bit I is 0, it is determined that the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0152] In addition, when the value of the indicator bit I is 1, the number bit HFN is further determined. L The indicated value is based on the HFN number. L The corresponding bit of the second HFN is updated according to the indicated value to obtain the first HFN corresponding to the PDCP data packet.

[0153] For example, combining Figure 5 As shown, HFN L When including the lowest first and second digits, HFN L The lowest first digit of the HFN number indicated is 0. L When the lowest second bit of the indicated corresponding HFN number is 1, when the second HFN is 10010001001001, the corresponding bit of the second HFN is updated, and the first HFN corresponding to the PDCP data packet is 10010001001010.

[0154] In another embodiment, the HFN update indication information is sent via PDCP control PDU, combined with Figure 6 As shown, the HFN update indication information includes the number HFN L The message header of the PDCP control PDU includes a PDU type Type, which is used to indicate that the first HFN corresponding to the PDCP data packet indicated by the PDCP control PDU is updated compared to the second HFN. According to the PDCP control PDU, the terminal reads the number HFN in the message header of the PDCP control PDU. L , in HFN L The lowest first digit of the HFN number indicated is 0. L When the lowest second bit of the indicated corresponding HFN number is 1 and the second HFN is 10010001001001, the corresponding bit of the second HFN is updated, and the first HFN corresponding to the PDCP data packet is 10010001001010.

[0155] According to another embodiment of the present invention, the HFN processing method determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the SN in the PDCP data packet.

[0156] In this embodiment, combined Figure 3 In step S320, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same includes:

[0157] According to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same; wherein the first SN is sent to the terminal by the network side device through signaling.

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

[0159] 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 implementation, the MBS configuration information includes the MBS resource location, the logical channel configuration information, the 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.

[0160] Similar to 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.

[0161] 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 [SN ini , 2 maxSN–1 -1], the second window is [0, 2 maxSN–1 -1-SN ini ]; SN ini is the first SN, and maxSN is the maximum value of SN.

[0162] Wherein, in step S320, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the first SN and the second SN in the PDCP data packet includes:

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

[0164] 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.

[0165] Specifically, after the terminal receives the PDCP data packet sent by the network side device, it 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 which window the second SN belongs to. It can determine whether the SN is flipped, thereby further determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0166] Combination Figure 7 As shown, according to the first SN of the PDCP data packet to be sent indicated by the network side device in the signaling, such as SN ini , the SN number range [0, maxSN] can be divided into two windows, namely the first window [SN ini , 2 maxSN–1 -1] and the second window [0, 2 maxSN–1 -1-SN ini ], it can be understood that when the SN does not flip, the PDCP data packet sent is from SN ini When the SN is flipped, the PDCP data packet sent is numbered from 0, and the renumbered SN is in the second window. Therefore, according to the second SN in the PDCP data packet, the second SN is compared with the first window and the second window to determine whether the SN is flipped, thereby further determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0167] 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. The first HFN is processed, and a value obtained by adding 1 to the second HFN is determined as the first HFN corresponding to the PDCP data packet.

[0168] With this implementation, when the second SN is outside the first SN window and the second SN window, the terminal considers that an illegal PDCP data packet has been received, and then feeds back abnormal report information to the network side device to feed back abnormality of the current link.

[0169] In the embodiment of the present invention, when any of the above implementations is used to determine that the first HFN corresponding to the PDCP data packet is the same as the second HFN, it is determined that the first HFN corresponding to the PDCP data packet sent by the network side device is equal to the second HFN.

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

[0171] Determining whether the PDCP data packet is the first data packet of service data of the received MBS service;

[0172] When the PDCP data packet is the first data packet of service data of the received MBS service, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0173] According to the method described in the embodiment of the present application, for the first PDCP data packet of the received MBS data, it is determined whether the first HFN corresponding to the PDCP data packet is the same as the second HFN, and if it is determined that the first HFN is not the same as the second HFN, the first HFN is further processed. In addition, for the PDCP data packet received after the first PDCP data packet, the corresponding HFN of the PDCP data packet received thereafter is further determined according to the corresponding first HFN determined by the first PDCP data packet, that is, the corresponding HFN is determined in a usual manner.

[0174] By adopting the HFN processing method described in the embodiment of the present application, after receiving a PDCP data packet sent by a network side device, it is possible to determine whether the first HFN corresponding to the PDCP data packet is the same as the HFN initially sent to the terminal by the network side device according to the HFN update indication information in the PDCP data packet, or according to the SN in the PDCP data packet. If it is determined that the two are not the same, the first HFN corresponding to the PDCP data packet is processed to determine the updated HFN, so that for the received PDCP data packet, the HFN determined by the terminal is synchronized with the HFN when the network side device sends data.

[0175] The present application also provides a method for processing a hyperframe number HFN, which is executed by a network side device, such as Figure 8 As shown, the method includes:

[0176] S810, sending a PDCP data packet to the terminal;

[0177] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

[0178] By adopting the hyperframe number HFN processing method described in the embodiment of the present application, the PDCP data packet sent by the network side device to the terminal includes HFN update indication information. According to the HFN update indication information, the terminal can determine whether the first HFN corresponding to the PDCP data packet is the same as the HFN initially sent to the terminal by the network side device, thereby ensuring that the HFN determined by the terminal is synchronized with the HFN when the network side device sends data.

[0179] Optionally, the HFN update indication information includes at least one of the following:

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

[0181] A second indication bit indicating that the first HFN is the same as the second HFN;

[0182] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0183] In the embodiment of the present application, the specific implementation method of sending the HFN update indication information through the PDCP data packet can be combined with Figures 4 to 6 , and refer to the above instructions, which will not be explained in detail here.

[0184] Another embodiment of the present application further provides a terminal, such as Fig. 9 As shown, it includes a memory 910, a transceiver 920 and a processor 900:

[0185] 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 program in the memory and perform the following operations:

[0186] Receive PDCP data packets sent by network side devices;

[0187] Determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein the second HFN is sent to the terminal by the network side device through signaling;

[0188] If the first HFN is different from the second HFN, the first HFN is processed.

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

[0190] The processor 900 determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, specifically:

[0191] According to the HFN update indication information, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0192] Optionally, in the terminal, the HFN update indication information includes at least one of the following:

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

[0194] A second indication bit indicating that the first HFN is the same as the second HFN;

[0195] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0196] Optionally, in the terminal, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or is sent via a PDCP control PDU of the PDCP data packet.

[0197] Optionally, in the terminal, the processor 900 processes the first HFN, specifically:

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

[0199] Optionally, in the terminal, when the HFN update indication includes a value corresponding to the lowest N bits of the first HFN, the processor processes the first HFN, specifically:

[0200] According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

[0201] Optionally, in the terminal, the processor 900 determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, specifically:

[0202] According to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same; wherein the first SN is sent to the terminal by the network side device through signaling.

[0203] Optionally, in the terminal, the processor 900 is further configured to:

[0204] According to the first SN, a first window and a second window are determined; wherein the first window is [SN ini , 2 maxSN –1 -1], the second window is [0, 2 maxSN–1 -1-SN ini ]; SN ini is the first SN, maxSN is the maximum value of SN;

[0205] Wherein, determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the first SN and the second SN in the PDCP data packet includes:

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

[0207] 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.

[0208] Optionally, in the terminal, the processor 900 is further configured to:

[0209] When the second SN is located outside the first SN window and the second SN window, abnormal report information is fed back to the network side device.

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

[0211] Determining whether the PDCP data packet is the first data packet of service data of the received MBS service;

[0212] When the PDCP data packet is the first data packet of service data of the received MBS service, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

[0213] Among them, Fig. 9In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 900 and various circuits of memory represented by memory 910 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 920 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 930 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0214] 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.

[0215] Optionally, the processor 900 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0216] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0217] The present application also provides a network side device, such as Fig.10 As shown, it includes a memory 1010, a transceiver 1020 and a processor 1000:

[0218] The memory 1010 is used to store a computer program; 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 program in the memory and perform the following operations:

[0219] Send PDCP data packets to the terminal;

[0220] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

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

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

[0223] A second indication bit indicating that the first HFN is the same as the second HFN;

[0224] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0225] Among them, Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1000 and various circuits of memory represented by memory 1010 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1020 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1010 may store data used by the processor 1000 when performing operations.

[0226] The processor 1000 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0227] Another embodiment of the present application further provides a hyperframe number HFN processing device, which is executed by a terminal, such as Fig.11 As shown, the hyperframe number HFN processing device 1100 includes:

[0228] The receiving unit 1110 is configured to receive a PDCP data packet sent by a network side device;

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

[0230] 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 device, the PDCP data packet further includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same;

[0231] The determining unit 1120 determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, specifically:

[0232] According to the HFN update indication information, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

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

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

[0235] A second indication bit indicating that the first HFN is the same as the second HFN;

[0236] Indicates the value corresponding to the lowest N bits of the first HFN; where N is an integer greater than or equal to 1.

[0237] Optionally, in the HFN processing device, the HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit (PDU) of the PDCP data packet, or is sent via a PDCP control PDU of the PDCP data packet.

[0238] Optionally, in the HFN processing device, the processing unit 1130 processes the first HFN by:

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

[0240] Optionally, in the HFN processing device, when the HFN update indication includes a value corresponding to the lowest N bits of the first HFN, the processing unit 1130 processes the first HFN by:

[0241] According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

[0242] Optionally, in the HFN processing device, the determining unit 1120 determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same, comprising:

[0243] According to the first SN and the second SN in the PDCP data packet, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same; wherein the first SN is sent to the terminal by the network side device through signaling.

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

[0245] According to the first SN, a first window and a second window are determined; wherein the first window is [SN ini , 2 maxSN –1 -1], the second window is [0, 2 maxSN–1 -1-SN ini ]; SN ini is the first SN, maxSN is the maximum value of SN;

[0246] The determining unit 1120 determines whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the first SN and the second SN in the PDCP data packet, specifically:

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

[0248] 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.

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

[0250] When the second SN is located outside the first SN window and the second SN window, abnormal report information is fed back to the network side device.

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

[0252] Determining whether the PDCP data packet is the first data packet of service data of the received MBS service;

[0253] 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 and the second HFN corresponding to the PDCP data packet are the same. The embodiment of the present application also provides a super frame number HFN processing device, which is executed by a network side device, such as Fig.12 As shown, the hyperframe number HFN processing device 1200 includes:

[0254] The sending unit 1210 is configured to send a PDCP data packet to a terminal;

[0255] The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling. Optionally, the HFN processing device, wherein the HFN update indication information includes at least one of the following:

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

[0257] A second indication bit indicating that the first HFN is the same as the second HFN;

[0258] 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 superframe number HFN processing method and superframe number HFN processing device of the present application are based on the same application concept, can implement all the method steps implemented by the above method embodiment, and can achieve the same technical effect, and the parts and beneficial effects of the present embodiment that are the same as those of the method embodiment will not be specifically described here.

[0259] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0260] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art 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, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0261] An embodiment of the present application further 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 hyperframe number HFN processing method as described in any one of the above items.

[0262] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0263] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0264] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0265] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0266] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0267] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for processing a hyperframe number HFN, characterized in that: Executed by a terminal, the method includes: receiving a PDCP data packet sent by a network side device, wherein the PDCP data packet further includes HFN update indication information, wherein the HFN update indication information is used to indicate whether a first HFN and a second HFN corresponding to the PDCP data packet sent by the network side device are the same; Determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein 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, processing the first HFN; The step of determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same includes: determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the HFN update indication information.

2. The HFN processing method according to claim 1, characterized in that: 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; A second indication bit 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; where N is an integer greater than or equal to 1.

3. The HFN processing method according to claim 2, characterized in that: The HFN update indication information is sent via a packet data convergence protocol layer PDCP data protocol data unit PDU of the PDCP data packet, or via a PDCP control PDU of the PDCP data packet.

4. The HFN processing method according to claim 1, characterized in that: The processing of the first HFN includes: A value obtained by adding 1 to the second HFN is determined as the first HFN.

5. The HFN processing method according to claim 2, characterized in that: In a case where the HFN update indication includes indicating a value corresponding to the lowest N bits of the first HFN, the processing of the first HFN includes: According to the values ​​corresponding to the lowest N bits, corresponding bits of the second HFN number are updated to obtain the first HFN number.

6. The HFN processing method according to claim 1, characterized in that: After receiving the PDCP data packet sent by the network side device, the method further includes: Determining whether the PDCP data packet is the first data packet of service data of the received MBS service; When the PDCP data packet is the first data packet of service data of the received MBS service, it is determined whether the first HFN and the second HFN corresponding to the PDCP data packet are the same.

7. A method for processing a hyperframe number HFN, characterized in that: The method is performed by a network side device and includes: Send PDCP data packets to the terminal; The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

8. The HFN treatment method according to claim 7, characterized in that: 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; A second indication bit 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; where N is an integer greater than or equal to 1.

9. A terminal, characterized in that: Includes memory, transceiver and processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: receiving a PDCP data packet sent by a network side device, wherein the PDCP data packet includes HFN update indication information, wherein the HFN update indication information is used to indicate whether a first HFN and a second HFN corresponding to the PDCP data packet sent by the network side device are the same; Determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, wherein 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, processing the first HFN; The step of determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same includes: determining whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the HFN update indication information.

10. The terminal according to claim 9, characterized in that: 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; A second indication bit 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; where N is an integer greater than or equal to 1.

11. A network side device, characterized in that: Includes memory, transceiver and processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Send PDCP data packets to the terminal; The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

12. A hyperframe number HFN processing device, characterized in that: Executed by a terminal, the device includes: A receiving unit, configured to receive a PDCP data packet sent by a network side device, wherein the PDCP data packet further includes HFN update indication information, wherein the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; a determining unit, configured to determine whether a first HFN and a second HFN corresponding to the PDCP data packet are the same, 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 determining unit is specifically configured to determine whether the first HFN and the second HFN corresponding to the PDCP data packet are the same according to the HFN update indication information.

13. A hyperframe number HFN processing device, characterized in that: The method is executed by a network side device, and the device includes: A sending unit, used to send a PDCP data packet to a terminal; The PDCP data packet includes HFN update indication information, and the HFN update indication information is used to indicate whether the first HFN and the second HFN corresponding to the PDCP data packet sent by the network side device are the same; the second HFN is sent to the terminal by the network side device through signaling.

14. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the hyperframe number HFN processing method according to any one of claims 1 to 6, or execute the hyperframe number HFN processing method according to any one of claims 7 to 8.

Images