A method and device for determining superframe number of packet data convergence protocol entity

Abstract

The present disclosure discloses a method and apparatus for determining a hyperframe number (HFN) for a Packet Data Convergence Protocol (PDCP) entity, applicable to the field of communications technology. The method, configured to be executed by a terminal device, includes: receiving indication information sent by a network device, wherein the indication information includes hyperframe number (HFN) information; and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures and improving data transmission reliability.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and device for determining a superframe number of a packet data convergence protocol entity. Background Art

[0002] In a communication system, network devices continuously transmit data, and therefore, the hyperframe number (HFN) used by these devices continuously increases. When a new terminal device joins and receives data from the network device, it is unaware of the HFN value used by the network device. Consequently, the terminal device cannot use the correct COUNT value to decrypt or verify the integrity of the received data, resulting in decryption or integrity verification failure. Summary of the Invention

[0003] The embodiments of the present disclosure provide a method and apparatus for determining a superframe number of a packet data convergence protocol entity, which can be applied in the field of communication technology.

[0004] In a first aspect, an embodiment of the present disclosure provides a method for determining a hyperframe number of a packet data convergence protocol entity, the method being configured to be executed by a terminal device, the method comprising: receiving indication information sent by a network device, wherein the indication information includes hyperframe number HFN information; and determining the HFN value of the packet data convergence protocol PDCP entity based on the HFN information.

[0005] In this solution, the terminal device can first receive the indication information sent by the network device, and then determine the HFN value of the PDCP entity based on the HFN information included in the indication information. This ensures that the terminal device and the network device have a consistent understanding of the HFN value, avoiding data decryption failure or integrity verification failure, and improving data transmission reliability.

[0006] Optionally, the HFN information includes any one of the following items: an HFN value and a count value COUNT.

[0007] Optionally, determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes: determining the HFN value of the PDCP entity based on the HFN information in response to satisfying an applicable condition of the HFN information.

[0008] Optionally, also include:

[0009] receiving applicable conditions of the HFN information sent by the network device;

[0010] or,

[0011] Based on the agreement, determine the applicable conditions of the HFN information

[0012] Optionally, the applicable condition of the HFN information includes any one of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0013] Optionally, the value of the SN includes any of the following:

[0014] Minimum value of SN;

[0015] The maximum value of SN;

[0016] The minimum and maximum values ​​of SN;

[0017] The segment number corresponding to the SN value; and

[0018] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0019] Optionally, the value of the SFN includes any one of the following:

[0020] Minimum value of SFN;

[0021] Maximum value of SFN;

[0022] Minimum and maximum values ​​of SFN;

[0023] The segment number corresponding to the SFN value; and

[0024] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0025] Optionally, satisfying the applicable conditions includes:

[0026] The SN value corresponding to the PDCP data packet received by the terminal device meets the applicable condition;

[0027] or,

[0028] The SFN value corresponding to the PDCP data packet received by the terminal device meets the applicable conditions.

[0029] Optionally, the indication information also includes MBS service information, and the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.

[0030] Optionally, the SFN value corresponding to the received PDCP data packet includes any one of the following:

[0031] The SFN value corresponding to the time position of the last physical data channel of the successful reception of the PCDP data packet;

[0032] The SFN value corresponding to the time position of the first physical data channel where the PCDP data packet is successfully received; and

[0033] The SFN value corresponding to the PDCP data packet is successfully received.

[0034] Optionally, the applicable condition is a value of an SN, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes:

[0035] In response to the application condition not being met and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN being s, updating the HFN information based on the difference s to generate updated HFN information;

[0036] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0037] Optionally, the applicable condition is a SFN value, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes:

[0038] In response to the application condition not being met and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value being k, updating the HFN information based on the difference k to generate updated HFN information;

[0039] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0040] Optionally, the indication information further includes an update mode of the HFN information, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes:

[0041] In response to the applicable condition not being met, updating the HFN information based on the update mode to generate updated HFN information;

[0042] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0043] Optionally, the update mode includes an update step and an update direction.

[0044] Optionally, the receiving instruction information sent by the network device includes:

[0045] receiving, based on the system message, indication information sent by the network device;

[0046] or,

[0047] receiving, based on a broadcast multicast service MBS control channel message, indication information sent by the network device;

[0048] or,

[0049] Based on the exclusive configuration message of the terminal device, receive the indication information sent by the network device.

[0050] Optionally, the indication information further includes MBS service information, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes:

[0051] Based on the HFN information, a HFN value of a PDCP entity corresponding to the MBS service information is determined.

[0052] Optionally, the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0053] Optionally, the method further includes: decrypting or integrity verifying received data corresponding to the MBS service information based on the HFN information.

[0054] Optionally, determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes: in response to the terminal device being a device newly accessing an MBS service, determining the HFN value of the PDCP entity based on the HFN information.

[0055] In a second aspect, an embodiment of the present disclosure provides another method for determining a hyperframe number of a packet data convergence protocol entity, the method being configured to be executed by a network device, the method comprising: sending indication information to a terminal device, wherein the indication information comprises hyperframe number HFN information.

[0056] Optionally, the HFN information includes any one of the following items: an HFN value and a count value COUNT.

[0057] Optionally, the indication information further includes applicable conditions of the HFN information.

[0058] Optionally, the applicable condition of the HFN information includes any one of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0059] Optionally, the value of the SN includes any of the following:

[0060] Minimum value of SN;

[0061] The maximum value of SN;

[0062] The minimum and maximum values ​​of SN;

[0063] The segment number corresponding to the SN value; and

[0064] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0065] Optionally, the value of the SFN includes any one of the following:

[0066] Minimum value of SFN;

[0067] Maximum value of SFN;

[0068] Minimum and maximum values ​​of SFN;

[0069] The segment number corresponding to the SFN value; and

[0070] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0071] Optionally, the indication information also includes MBS service information.

[0072] Optionally, the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0073] Optionally, the indication information further includes an update mode of the HFN information.

[0074] Optionally, the update mode includes an update step and an update direction.

[0075] Optionally, the sending instruction information to the terminal device includes:

[0076] Sending instruction information to the terminal device based on the system message;

[0077] or,

[0078] Sending indication information to the terminal device based on a broadcast multicast service MBS control channel message;

[0079] or,

[0080] Based on the exclusive configuration message of the terminal device, indication information is sent to the terminal device.

[0081] Optionally, also include:

[0082] In response to a change in any information other than the HFN information in the system message, sending first change indication information to the terminal device;

[0083] or,

[0084] In response to a change in any information other than the HFN information in the MBS control channel message, second change indication information is sent to the terminal device.

[0085] In a third aspect, an embodiment of the present disclosure provides a communication device, which is configured on the terminal device side, and the device includes: a transceiver module for receiving indication information sent by a network device, wherein the indication information includes hyperframe number HFN information; and a processing module for determining the HFN value of the packet data convergence protocol PDCP entity based on the HFN information.

[0086] Optionally, the HFN information includes any one of the following items: an HFN value and a count value COUNT.

[0087] Optionally, the processing module is specifically configured to determine, in response to satisfying an applicable condition of the HFN information, a HFN value of the PDCP entity based on the HFN information.

[0088] Optionally, the transceiver module is further configured to receive the applicable conditions of the HFN information sent by the network device;

[0089] or,

[0090] The processing module is further configured to determine applicable conditions of the HFN information based on protocol agreement.

[0091] Optionally, the applicable condition of the HFN information includes any one of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0092] Optionally, the value of the SN includes any of the following:

[0093] Minimum value of SN;

[0094] The maximum value of SN;

[0095] The minimum and maximum values ​​of SN;

[0096] The segment number corresponding to the SN value; and

[0097] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0098] Optionally, the value of the SFN includes any one of the following:

[0099] Minimum value of SFN;

[0100] Maximum value of SFN;

[0101] Minimum and maximum values ​​of SFN;

[0102] The segment number corresponding to the SFN value; and

[0103] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0104] Optionally, satisfying the applicable conditions includes:

[0105] The SN value corresponding to the PDCP data packet received by the terminal device meets the applicable condition;

[0106] or,

[0107] The SFN value corresponding to the PDCP data packet received by the terminal device meets the applicable conditions.

[0108] Optionally, the indication information also includes MBS service information, and the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.

[0109] Optionally, the SFN value corresponding to the received PDCP data packet includes any one of the following:

[0110] The SFN value corresponding to the time position of the last physical data channel of the successful reception of the PCDP data packet;

[0111] The SFN value corresponding to the time position of the first physical data channel where the PCDP data packet is successfully received; and

[0112] The SFN value corresponding to the PDCP data packet is successfully received.

[0113] Optionally, the applicable condition is a value of SN, and the processing module is specifically configured to:

[0114] In response to the application condition not being met and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN being s, updating the HFN information based on the difference s to generate updated HFN information;

[0115] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0116] Optionally, the applicable condition is a value of SFN, and the processing module is specifically configured to:

[0117] In response to the application condition not being met and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value being k, updating the HFN information based on the difference k to generate updated HFN information;

[0118] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0119] Optionally, the indication information further includes an update mode of the HFN information, and the processing module is specifically configured to:

[0120] In response to the applicable condition not being met, updating the HFN information based on the update mode to generate updated HFN information;

[0121] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0122] Optionally, the update mode includes an update step and an update direction.

[0123] Optionally, the transceiver module is specifically configured to:

[0124] receiving, based on the system message, indication information sent by the network device;

[0125] or,

[0126] receiving, based on a broadcast multicast service MBS control channel message, indication information sent by the network device;

[0127] or,

[0128] Based on the exclusive configuration message of the terminal device, receive the indication information sent by the network device.

[0129] Optionally, the indication information further includes MBS service information, and the processing module is specifically configured to:

[0130] Based on the HFN information, a HFN value of a PDCP entity corresponding to the MBS service information is determined.

[0131] Optionally, the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0132] Optionally, the processing module is further configured to perform decryption or integrity verification on received data corresponding to the MBS service information based on the HFN information.

[0133] Optionally, the processing module is specifically configured to:

[0134] In response to the terminal device being a device that newly accesses the MBS service, the HFN value of the PDCP entity is determined based on the HFN information.

[0135] In a fourth aspect, an embodiment of the present disclosure provides another communication device, which is configured on the network device side. The device includes: a transceiver module for sending indication information to the terminal device, wherein the indication information includes super frame number HFN information.

[0136] Optionally, the HFN information includes any one of the following items: an HFN value and a count value COUNT.

[0137] Optionally, the transceiver module is further configured to send applicable conditions of the HFN information to the terminal device.

[0138] Optionally, the applicable condition of the HFN information includes any one of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0139] Optionally, the value of the SN includes any of the following:

[0140] Minimum value of SN;

[0141] The maximum value of SN;

[0142] The minimum and maximum values ​​of SN;

[0143] The segment number corresponding to the SN value; and

[0144] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0145] Optionally, the value of the SFN includes any one of the following:

[0146] Minimum value of SFN;

[0147] Maximum value of SFN;

[0148] Minimum and maximum values ​​of SFN;

[0149] The segment number corresponding to the SFN value; and

[0150] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0151] Optionally, the indication information also includes MBS service information.

[0152] Optionally, the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0153] Optionally, the indication information further includes an update mode of the HFN information.

[0154] Optionally, the update mode includes an update step and an update direction.

[0155] Optionally, the transceiver module is specifically configured to:

[0156] Sending instruction information to the terminal device based on the system message;

[0157] or,

[0158] Sending indication information to the terminal device based on a broadcast multicast service MBS control channel message;

[0159] or,

[0160] Based on the exclusive configuration message of the terminal device, indication information is sent to the terminal device.

[0161] Optionally, the transceiver module is further configured to:

[0162] In response to a change in any information other than the HFN information in the system message, sending first change indication information to the terminal device;

[0163] or,

[0164] In response to a change in any information other than the HFN information in the MBS control channel message, second change indication information is sent to the terminal device.

[0165] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0166] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the second aspect is executed.

[0167] In the seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0168] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0169] In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0170] In a tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0171] In the eleventh aspect, an embodiment of the present disclosure provides a communication system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0172] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the terminal device executes the method described in the above-mentioned first aspect.

[0173] In a thirteenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above-mentioned network device, and when the instructions are executed, the network device executes the method described in the second aspect.

[0174] In a fourteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0175] In a fifteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0176] In the sixteenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method.

[0177] In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system can be composed of a chip or include a chip and other discrete devices.

[0178] In the seventeenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a network device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method.

[0179] In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the network device. The chip system can be composed of chips or include chips and other discrete devices.

[0180] In an eighteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0181] In a nineteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0182] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0183] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0184] Figure 2 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure;

[0185] Figure 3 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0186] Figure 4 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0187] Figure 5 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0188] Figure 6 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0189] Figure 7 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0190] Figure 8 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0191] Figure 9 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by another embodiment of the present disclosure;

[0192] Figure 10 is a structural diagram of a communication device according to an embodiment of the present disclosure;

[0193] Figure 11 is a structural diagram of a communication device according to another embodiment of the present disclosure;

[0194] Figure 12 is a structural diagram of a communication device according to another embodiment of the present disclosure;

[0195] Figure 13 It is a schematic structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0196] To facilitate understanding, the terms involved in this disclosure are first introduced.

[0197] 1. Multimedia broadcast and multicast service (MBMS) or multicast broadcast service (MBS)

[0198] MBS is a practical technology that improves spectrum efficiency and is widely used in communication systems. In 5G new radio access technology (RAT) systems, MBS services can be sent via the physical downlink shared channel (PDSCH) scheduled by the physical downlink control channel (PDCCH).

[0199] 2. Packet Data Convergence Protocol (PDCP)

[0200] PDCP is a radio transport protocol stack that processes radio resource control (RRC) messages and Internet Protocol (IP) packets. It compresses and decompresses IP headers, transmits user data, and maintains sequence numbers (SNs) for radio bearers. It also provides signaling transport services, encrypts and protects consistency of signaling, and decrypts and performs consistency checks on signaling in the reverse direction.

[0201] 3. Encryption and integrity protection

[0202] The communication system can encrypt and integrity-protect the data being sent. Typically, a 32-bit message authentication code for integrity (MAC-I) is added to the end of the PDCP packet to implement integrity protection.

[0203] Generally, a PDCP receiving entity needs to know the PDCP COUNT value in order to decrypt encrypted data or perform integrity verification on the data.

[0204] The PDCP COUNT value may be composed of two parts, the HFN and the PDCP SN, which are 32 bits in total. Typically, the header of a PDCP data packet carries the PDCP SN.

[0205] 4. System frame number (SFN)

[0206] In a communication system, time domain resources can be consecutively numbered using SFNs with a granularity of 10 milliseconds (ms). One SFN can contain 10 subframes, each 1 ms long. The SFN number can be indicated in the master information block (MIB) of the synchronization signal block (SSB).

[0207] In order to better understand the method for determining a superframe number of a packet data convergence protocol entity disclosed in an embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.

[0208] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to a network device and a terminal device. Figure 1 The number and form of devices shown are for example only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown includes a network device 11 and a terminal device 12 as an example.

[0209] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0210] The network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 11 can be an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0211] The terminal device 12 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the terminal device.

[0212] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0213] The method and apparatus for determining a superframe number of a packet data convergence protocol entity provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0214] See Figure 2 , Figure 2 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 2 As shown, the method may include but is not limited to the following steps:

[0215] Step 21: Receive indication information sent by a network device, wherein the indication information includes hyperframe number HFN information.

[0216] Optionally, the HFN information may include any one or more of the following: a HFN value and a count value COUNT.

[0217] It can be understood that the HFN value or COUNT value in the indication information is respectively the HFN value or COUNT value corresponding to the PDCP data packet currently sent by the network device.

[0218] In the present disclosure, in order to prevent a newly added terminal device receiving PDCP data sent by a network device from being unable to use the correct COUNT value to decrypt or perform integrity verification on the PDCP data packet, the network device can send an indication message to the terminal device according to certain rules to indicate the HFN value or count value COUNT corresponding to the current PDCP data to the terminal device.

[0219] Step 22: Determine the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information.

[0220] For example, the indication information received by the terminal device indicates that the HFN value is 1. Then, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0221] Alternatively, the indication information received by the terminal device indicates that the value of COUNT is 0. Then, the terminal device may determine that the HFN value of the PDCP entity is 0.

[0222] Alternatively, the indication information received by the terminal device indicates that the COUNT value is 8. The terminal device knows that the SN value ranges from 0 to 7, and the SN value in the received PDCP data packet is 7, so it can be determined that the HFN value of the PDCP entity is 1.

[0223] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information content, HFN value, COUNT value, etc. in the embodiments of the present disclosure.

[0224] Optionally, for a newly connected terminal device, when the indication information it receives indicates a COUNT value, the terminal device can directly use the COUNT value to decrypt or verify the integrity of the received data packet, and based on the COUNT value and the SN in the received data packet, calculate the HFN value currently used by the network device, and then determine the HFN value of the PDCP entity based on the calculated HFN value.

[0225] Optionally, for a newly connected terminal device, when the indication information it receives indicates an HFN value, the terminal device can use the HFN value to determine the corresponding COUNT value, and then decrypt or verify the integrity of the received data packet.

[0226] In the disclosed embodiments, a terminal device can first receive indication information sent by a network device, and then determine the HFN value of the PDCP entity based on the HFN information included in the indication information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures, and improving data transmission reliability.

[0227] See Figure 3 , Figure 3 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 3 As shown, the method may include but is not limited to the following steps:

[0228] Step 31: Receive indication information sent by a network device, wherein the indication information includes HFN information.

[0229] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0230] Step 32: In response to the applicable condition of the HFN information being met, determine the HFN value of the PDCP entity based on the HFN information.

[0231] Optionally, the applicable conditions of the HFN information may include any one or more of the following: a value of the sequence number SN and a value of the system frame number SFN.

[0232] Optionally, the applicable condition may be indicated by the network device or determined by the terminal device according to the protocol agreement, and this disclosure does not limit this.

[0233] The network device may indicate the applicable conditions of the HFN information to the terminal device at the same time as the HFN information is indicated, or may indicate the applicable conditions of the HFN information to the terminal device separately through other indication information, which is not limited in the present disclosure.

[0234] Optionally, the value of SN can be: the minimum value of SN.

[0235] Correspondingly, when the SN value corresponding to the received PDCP data packet is greater than or equal to the minimum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0236] For example, if the indication information received by the terminal device is: HFN value 1. And the terminal device determines that the applicable condition of the HFN information is: the minimum SN value is 5 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 7, since 7 is greater than the minimum SN value 5 in the applicable condition, the applicable condition of the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0237] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, etc. in the embodiments of the present disclosure.

[0238] Optionally, the value of SN can be: the maximum value of SN.

[0239] Correspondingly, when the SN value corresponding to the received PDCP data packet is less than or equal to the maximum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0240] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or the indication of the network device, that the applicable condition for the HFN information is 5, then when the terminal device determines that the SN value corresponding to the received PDCP data packet is 1, since 1 is less than the maximum SN value of 5 in the applicable condition, the applicable condition for the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0241] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, maximum SN value, etc. in the embodiments of the present disclosure.

[0242] Optionally, the value of SN can be: the minimum value and the maximum value of SN.

[0243] Accordingly, when the SN value corresponding to the received PDCP data packet is greater than or equal to the minimum value and less than or equal to the maximum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0244] For example, if the indication information received by the terminal device is: HFN value 1. And the terminal device determines that the applicable conditions of the HFN information are: the minimum SN value is 1 and the maximum SN value is 5 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2, because 2 is greater than the minimum SN value 1 in the applicable conditions and less than the maximum SN value 5 in the applicable conditions, the applicable conditions of the HFN information are met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0245] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, maximum SN value, etc. in the embodiments of the present disclosure.

[0246] Optionally, the value of SN may be: the segment number corresponding to the value of SN. Accordingly, when the segment number corresponding to the SN value corresponding to the received PDCP data packet is the same as the segment number corresponding to the SN value in the applicable condition, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0247] It is understandable that the segmentation method corresponding to the SN value can be a method agreed upon in the protocol.

[0248] For example, if the indication information received by the terminal device is: the HFN value is 1. And the terminal device determines, according to the protocol agreement or the indication of the network device, that the applicable condition of the HFN information is: the segment number corresponding to the SN value is 1. Then, when the terminal device determines that the segment number corresponding to the SN value corresponding to the received PDCP data packet is 1, and it is the same as the segment number corresponding to the SN value in the applicable condition, the applicable condition of the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0249] It should be noted that the above examples are merely illustrative and cannot be used as a limitation on the indication information, HFN values, segment numbers corresponding to SN values, etc. in the embodiments of the present disclosure.

[0250] Optionally, the value of SN can be: the parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0251] Correspondingly, when the SN value corresponding to the received PDCP data packet is segment numbered n among the m segments, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0252] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is the parameter pair (2, 1) corresponding to the SN value, then the terminal device satisfies the HFN information if it determines that the SN value corresponding to the received PDCP packet is 1 among the two segments. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0253] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, m value, n value, etc. in the embodiments of the present disclosure.

[0254] Optionally, the value of SFN may be: the minimum value of SFN.

[0255] Correspondingly, when the SFN value corresponding to the received PDCP data packet is greater than or equal to the minimum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0256] For example, if the indication information received by the terminal device is: HFN value is 1. And the terminal device determines that the applicable condition of the HFN information is: the minimum SFN value is 5 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 7, since 7 is greater than the minimum SFN value 5 in the applicable condition, the applicable condition of the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0257] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SFN value, etc. in the embodiments of the present disclosure.

[0258] Optionally, the value of SFN may be: the maximum value of SFN.

[0259] Correspondingly, when the SFN value corresponding to the received PDCP data packet is less than or equal to the maximum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0260] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or the indication of the network device, that the applicable condition for the HFN information is 5, then when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 1, since 1 is less than the maximum SFN value of 5 in the applicable condition, the applicable condition for the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0261] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, SFN maximum value, etc. in the embodiments of the present disclosure.

[0262] Optionally, the value of SFN may be: the minimum value and the maximum value of SFN.

[0263] Accordingly, when the SFN value corresponding to the received PDCP data packet is greater than or equal to the minimum value and less than or equal to the maximum value, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0264] For example, if the indication information received by the terminal device is: HFN value is 1. And the terminal device determines the applicable conditions of the HFN information as follows: the minimum SFN value is 1 and the maximum SFN value is 5 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 2, because 2 is greater than the minimum SFN value 1 in the applicable conditions and less than the maximum SFN value 5 in the applicable conditions, the applicable conditions of the HFN information are met. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0265] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, SFN minimum value, SFN maximum value, etc. in the embodiments of the present disclosure.

[0266] Optionally, the SFN value may be a segment number corresponding to the SFN value. Accordingly, when the segment number corresponding to the SFN value corresponding to the received PDCP data packet is the same as the segment number corresponding to the SFN value in the applicable condition, the terminal device may determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0267] It is understandable that the segmentation method corresponding to the SFN value may be a method agreed upon in the protocol.

[0268] For example, if the indication information received by the terminal device is: the HFN value is 1. And the terminal device determines, according to the protocol agreement or the indication of the network device, that the applicable condition of the HFN information is: the segment number corresponding to the SFN value is 1. Then, when the terminal device determines that the segment number corresponding to the SFN value corresponding to the received PDCP data packet is 1, that is, the segment number corresponding to the SFN value in the applicable condition is the same, the applicable condition of the HFN information is met, and the terminal device can determine that the HFN value of the PDCP entity is 1 based on the HFN value indicated by the network device.

[0269] It should be noted that the above examples are merely illustrative and cannot be used as a limitation on the indication information, HFN values, and segment numbers corresponding to SFN values ​​in the embodiments of the present disclosure.

[0270] Optionally, the value of SFN can be: the parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0271] Accordingly, when the SFN value corresponding to the received PDCP data packet is segment numbered j among the m segments, the terminal device can determine the HFN value of the PDCP entity based on the HFN information indicated by the network device.

[0272] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is the parameter pair (2, 1) corresponding to the SFN value, then the terminal device satisfies the HFN information if it determines that the SFN value corresponding to the received PDCP packet is segment number 1 in the two segments. Therefore, based on the HFN value indicated by the network device, the terminal device can determine that the HFN value of the PDCP entity is 1.

[0273] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN values, i values, j values, etc. in the embodiments of the present disclosure.

[0274] Optionally, for a newly connected terminal device, a corresponding HFN value can be determined based on the applicable conditions of the determined HFN information and the received indication information, and then the corresponding COUNT value can be determined using the HFN value to perform data decryption or integrity verification on the received data packet.

[0275] In the disclosed embodiments, a terminal device may first receive HFN information and applicable conditions of the HFN information from a network device. When the applicable conditions of the HFN information are met, the terminal device may determine the HFN value of the PDCP entity based on the received HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption or integrity verification failures and improving data transmission reliability.

[0276] See Figure 4 , Figure 4 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 4 As shown, the method may include but is not limited to the following steps:

[0277] Step 41: Receive indication information sent by a network device based on the system message, wherein the indication information includes HFN information.

[0278] For example, the terminal device may receive indication information sent by the network device based on a system information block (SIB), such as SIB1.

[0279] It is understood that in the present disclosure, network devices may extend the SIB1 message so that the SIB1 can carry indication information. For example, a designated bit may be added to the SIB1, and the value of the designated bit may be used to represent the HFN value and / or COUNT value. Thus, when a terminal device receives the SIB1 message, it can determine the HFN value and / or COUNT value in the indication information based on the value of the designated bit, etc. This disclosure is not limited to this.

[0280] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0281] Optionally, the network device may also send indication information to the terminal device via a broadcast multicast service MBS control channel message, so that the terminal device may receive the indication information sent by the network device based on the MBS control channel message.

[0282] It is understood that in the present disclosure, network devices may extend MBS control channel messages to carry indication information. For example, designated bits may be added to the MBS control channel message, and the value of the designated bits may be used to represent the HFN value and / or COUNT value. Thus, upon receiving the MBS control channel message, a terminal device may determine the HFN value and / or COUNT value in the indication information based on the value of the designated bits. This is not limited in the present disclosure.

[0283] Optionally, the network device may also use a dedicated configuration message of the terminal device to send the indication information to the terminal device, so that the terminal device can receive the indication information sent by the network device based on the dedicated configuration message of the terminal device.

[0284] It is understood that in the present disclosure, a network device may configure a dedicated configuration message for a terminal device so that it carries indication information. For example, a designated bit may be added to the dedicated configuration message for the terminal device, and the value of the designated bit may be used to represent the HFN value and / or COUNT value. Thus, upon receiving the dedicated configuration message, the terminal device may determine the HFN value and / or COUNT value in the indication information based on the value of the designated bit, although this disclosure is not limited thereto.

[0285] Step 42: When the applicable condition of the HFN information is the value of the SN, in response to the applicable condition not being met and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN being s, the HFN information is updated based on the difference s to generate updated HFN information.

[0286] Optionally, the applicable conditions of the HFN information may be indicated by the network device, or may be determined by the terminal device according to a protocol agreement, which is not limited in the present disclosure.

[0287] Optionally, the value of SN can be: the minimum value of SN.

[0288] Correspondingly, when the SN value corresponding to the received PDCP data packet is less than the minimum value, the terminal device can update the HFN information based on the difference s to generate updated HFN information.

[0289] For example, if the indication information received by the terminal device is: HFN value 1. And the terminal device determines that the applicable condition of the HFN information is: the minimum SN value is 3 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SN value corresponding to the received PDCP data packet is 2, because 2 is less than the minimum SN value 3 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the difference s between the SN value 2 and the SN value 3 corresponding to the PDCP data packet received by the terminal device is -1, the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 0.

[0290] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, etc. in the embodiments of the present disclosure.

[0291] Optionally, the value of SN can be: the maximum value of SN.

[0292] Correspondingly, when the SN value corresponding to the received PDCP data packet is greater than the maximum value, the terminal device can update the HFN information based on the difference s to generate updated HFN information.

[0293] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is 3, then when the terminal device determines that the SN value corresponding to the received PDCP packet is 4, since 4 is greater than the maximum SN value of 3 in the applicable condition, the applicable condition for the HFN information is not met. Furthermore, the difference s between the SN value 4 and the SN value 3 corresponding to the PDCP packet received by the terminal device is +1. Therefore, the HFN information is updated based on the difference s, generating an updated HFN information with a HFN value of 2.

[0294] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, maximum SN value, etc. in the embodiments of the present disclosure.

[0295] Optionally, the value of SN can be: the minimum value and the maximum value of SN.

[0296] Correspondingly, when the SN value corresponding to the received PDCP data packet is less than the minimum value or greater than the maximum value, the terminal device can update the HFN information based on the difference s to generate updated HFN information.

[0297] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or the indication of the network device, that the applicable conditions for the HFN information are: the minimum SN value is 2 and the maximum SN value is 5, then when the terminal device determines that the SN value corresponding to the received PDCP data packet is 6, because 6 is greater than the maximum SN value of 5 in the applicable conditions, the applicable conditions for the HFN information are not met, and the difference s between the SN value 6 corresponding to the PDCP data packet received by the terminal device and the maximum SN value of 5 is +1, the HFN information is updated based on the difference s, generating an updated HFN information with a HFN value of 2.

[0298] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, maximum SN value, etc. in the embodiments of the present disclosure.

[0299] Optionally, the value of SN may be: the segment number corresponding to the value of SN. Accordingly, when the segment number corresponding to the SN value corresponding to the received PDCP data packet is different from the segment number corresponding to the SN value in the applicable condition, the terminal device may update the HFN information based on the difference s to generate updated HFN information.

[0300] It is understandable that the segmentation method corresponding to the SN value can be a method agreed upon in the protocol.

[0301] For example, if the indication information received by the terminal device is: the HFN value is 1. And the terminal device determines, according to the protocol agreement or the indication of the network device, that the applicable condition of the HFN information is: the segment number corresponding to the SN value is 1. Then, when the terminal device determines that the segment number corresponding to the SN value corresponding to the received PDCP data packet is 2, the applicable condition of the HFN information is not met, and the difference s between the segment number 2 corresponding to the SN value corresponding to the PDCP data packet received by the terminal device and the segment number 1 specified in the applicable condition is +1. Therefore, the HFN information is updated based on the difference s, and the updated HFN information is generated: the HFN value is 2.

[0302] It should be noted that the above examples are merely illustrative and cannot be used as a limitation on the indication information, HFN values, segment numbers corresponding to SN values, etc. in the embodiments of the present disclosure.

[0303] Optionally, the value of SN can be: the parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0304] Correspondingly, when the segment number of the SN value corresponding to the received PDCP data packet is not n in the m segments, the terminal device can update the HFN information based on the difference s to generate updated HFN information.

[0305] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is the parameter pair (2, 1) corresponding to the SN value, then when the terminal device determines that the SN value corresponding to the received PDCP packet is segment number 2 among two segments, the applicable condition for the HFN information is not met. Furthermore, the difference s between the segment number 2 corresponding to the SN value of the received PDCP packet and the segment number 1 specified in the applicable condition is +1. Therefore, the HFN information is updated based on the difference s, generating an updated HFN information with a HFN value of 2.

[0306] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, m value, n value, etc. in the embodiments of the present disclosure.

[0307] Step 43: Determine the HFN value of the PDCP entity based on the updated HFN information.

[0308] Optionally, the terminal device may determine the updated HFN value as the HFN value of the PDCP entity.

[0309] Optionally, for a newly connected terminal device, the HFN value of the PDCP entity can be determined based on the applicable conditions of the determined HFN information and the received indication information, and then the corresponding COUNT value can be determined using the HFN value to decrypt or verify the integrity of the received data packet.

[0310] In an embodiment of the present disclosure, a terminal device may first receive indication information sent by a network device. Based on the HFN information included in the indication information and the determined SN value, if the SN value is not satisfied and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the SN value is s, the terminal device may update the HFN information based on the difference s. The HFN value of the PDCP entity may then be determined based on the updated HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures and improving data transmission reliability.

[0311] See Figure 5 , Figure 5 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 5 As shown, the method may include but is not limited to the following steps:

[0312] Step 51: Receive indication information sent by a network device based on the MBS control channel message, wherein the indication information includes HFN information.

[0313] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0314] It should be noted that, for the content and specific implementation form of the terminal device receiving the indication information based on the MBS control channel message, reference can be made to other embodiments of the present disclosure and will not be repeated here.

[0315] Step 52: When the applicable condition of the HFN information is the value of the SFN, in response to the applicable condition not being met and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value being k, the HFN information is updated based on the difference k to generate updated HFN information.

[0316] Optionally, the applicable conditions of the HFN information may be indicated by the network device, or may be determined by the terminal device according to a protocol agreement, which is not limited in the present disclosure.

[0317] Optionally, the SFN value corresponding to the PDCP data packet received by the terminal device may include any one or more of the following: the SFN value corresponding to the time position of the last physical data channel of the successful reception of the PCDP data packet; the SFN value corresponding to the time position of the first physical data channel of the successful reception of the PCDP data packet; and the SFN value corresponding to the successful reception of the PDCP data packet.

[0318] For example, the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to the time position of the last physical data channel that successfully receives the PCDP data packet. For example, when receiving a PDCP data packet, the terminal device needs to successfully receive the Physical Downlink Shared Channel (PDSCH) data at time t1 and the PDSCH data at time t2. If time t1 is earlier and time t2 is later, then the SFN value corresponding to time t2 can be determined to be the SFN value corresponding to the PDCP data packet received by the terminal device, and so on. This disclosure does not limit this.

[0319] Alternatively, the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to the time position of the first physical data channel at which the PCDP data packet is successfully received. For example, when receiving a PDCP data packet, the terminal device needs to successfully receive PDSCH data at time t1 and PDSCH data at time t2. If time t1 is earlier and time t2 is later, then the SFN value corresponding to time t1 can be determined to be the SFN value corresponding to the PDCP data packet received by the terminal device, and so on. This disclosure is not limited to this.

[0320] Alternatively, the SFN value corresponding to the PDCP data packet received by the terminal device is the SFN value corresponding to the successfully received PDCP data packet. For example, when the terminal device receives a PDCP data packet, if the time at which the data packet is successfully received is t3, then the SFN value corresponding to time t3 can be determined to be the SFN value corresponding to the PDCP data packet received by the terminal device, and so on. This disclosure is not limited to this.

[0321] Optionally, the value of SFN may be: the minimum value of SFN.

[0322] Correspondingly, when the SFN value corresponding to the received PDCP data packet is less than the minimum value, the terminal device can update the HFN information based on the difference k to generate updated HFN information.

[0323] For example, if the indication information received by the terminal device is: HFN value 1. And the terminal device determines that the applicable condition of the HFN information is: the minimum SFN value is 3 according to the protocol agreement or the indication of the network device. Then, when the terminal device determines that the SFN value corresponding to the received PDCP data packet is 2, because 2 is less than the minimum SN value 3 in the applicable condition, that is, the applicable condition of the HFN information is not met, and the difference k between the SFN value 2 corresponding to the PDCP data packet received by the terminal device and the SFN value 3 is -1, the HFN information is updated based on the difference k, and the updated HFN information is generated: the HFN value is 0.

[0324] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SFN value, etc. in the embodiments of the present disclosure.

[0325] Optionally, the value of SFN may be: the maximum value of SFN.

[0326] Correspondingly, when the SFN value corresponding to the received PDCP data packet is greater than the maximum value, the terminal device can update the HFN information based on the difference k to generate updated HFN information.

[0327] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is 3, then when the terminal device determines that the SFN value corresponding to the received PDCP packet is 4, since 4 is greater than the maximum SFN value of 3 in the applicable condition, the applicable condition for the HFN information is not met. Furthermore, the difference k between the SFN value 4 corresponding to the PDCP packet received by the terminal device and the SFN value 3 is +1. Therefore, the HFN information is updated based on the difference k, generating an updated HFN information with a HFN value of 2.

[0328] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, SFN maximum value, etc. in the embodiments of the present disclosure.

[0329] Optionally, the value of SFN may be: the minimum value and the maximum value of SFN.

[0330] Correspondingly, when the SN value corresponding to the received PDCP data packet is less than the minimum value or greater than the maximum value, the terminal device can update the HFN information based on the difference k to generate updated HFN information.

[0331] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or the network device's indication, that the applicable conditions for the HFN information are: the minimum SFN value is 2 and the maximum SFN value is 5, then when the terminal device determines that the SFN value corresponding to the received PDCP packet is 6, because 6 is greater than the maximum SFN value of 5 in the applicable conditions, the applicable conditions for the HFN information are not met. Furthermore, the difference k between the SFN value 6 corresponding to the PDCP packet received by the terminal device and the maximum SFN value of 5 is +1. Therefore, the HFN information is updated based on the difference k, generating an updated HFN information with a HFN value of 2.

[0332] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, SFN minimum value, SFN maximum value, etc. in the embodiments of the present disclosure.

[0333] Optionally, the SFN value may be a segment number corresponding to the SFN value. Accordingly, when the segment number corresponding to the SFN value corresponding to the received PDCP data packet is different from the segment number corresponding to the SFN value in the applicable condition, the terminal device may update the HFN information based on the difference k to generate updated HFN information.

[0334] It is understandable that the segmentation method corresponding to the SFN value may be a method agreed upon in the protocol.

[0335] For example, if the indication information received by the terminal device is: HFN value 1. And the terminal device determines, according to the protocol agreement or the indication of the network device, that the applicable condition of the HFN information is: the segment number corresponding to the SFN value is 1. Then, when the terminal device determines that the segment number corresponding to the SFN value corresponding to the received PDCP data packet is 2, the applicable condition of the HFN information is not met, and the difference k between the segment number 2 corresponding to the SFN value corresponding to the PDCP data packet received by the terminal device and the segment number 1 corresponding to the SFN value specified in the applicable condition is +1. Therefore, the HFN information is updated based on the difference k, generating updated HFN information: HFN value 2.

[0336] It should be noted that the above examples are merely illustrative and cannot be used as a limitation on the indication information, HFN values, and segment numbers corresponding to SFN values ​​in the embodiments of the present disclosure.

[0337] Optionally, the value of SFN can be: the parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0338] Correspondingly, when the segment number of the SN value corresponding to the received PDCP data packet is not j in the i segments, the terminal device can update the HFN information based on the difference k to generate updated HFN information.

[0339] For example, if the terminal device receives an indication that the HFN value is 1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is the parameter pair (2, 1) corresponding to the SFN value, then when the terminal device determines that the SFN value corresponding to the received PDCP packet is segment number 2 among two segments, the applicable condition for the HFN information is not met. Furthermore, the difference k between segment number 2 corresponding to the SFN value corresponding to the PDCP packet received by the terminal device and segment number 1 specified in the applicable condition is +1. Therefore, the HFN information is updated based on the difference k, generating an updated HFN information with an HFN value of 2.

[0340] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN values, i values, j values, etc. in the embodiments of the present disclosure.

[0341] Step 53: Determine the HFN value of the PDCP entity based on the updated HFN information.

[0342] Optionally, the terminal device may determine the updated HFN value as the HFN value of the PDCP entity.

[0343] Optionally, for a newly connected terminal device, the HFN value of the PDCP entity can be determined based on the applicable conditions of the determined HFN information and the received indication information, and then the corresponding COUNT value can be determined using the HFN value to decrypt or verify the integrity of the received data packet.

[0344] In an embodiment of the present disclosure, a terminal device may first receive indication information sent by a network device. Based on the HFN information included in the indication information and the determined SFN value, if the SFN value is not satisfied and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value is k, the terminal device may update the HFN information based on the difference k and then determine the HFN value of the PDCP entity based on the updated HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures and improving data transmission reliability.

[0345] See Figure 6 , Figure 6 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 6 As shown, the method may include but is not limited to the following steps:

[0346] Step 61: Receive indication information sent by a network device, wherein the indication information includes HFN information and an update mode of the HFN information.

[0347] In the disclosed embodiments, when the network device indicates HFN information to the terminal device, it may also determine an update mode for the HFN information based on the current network status, such as the transmission speed of PDCP packets, and send the update mode to the terminal device. This avoids the situation where the terminal device receives inaccurate HFN information due to the influence of the network status.

[0348] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0349] Optionally, the update mode may include an update step size and an update direction.

[0350] The update step size may be any value set by the network device, such as 1, 2, 3, etc., and this disclosure does not limit this.

[0351] In addition, the update direction can be any direction set by the network device, such as the "+" direction, the "-" direction, etc., and this disclosure does not limit this. Therefore, the update mode of the HFN information can be "HFN value indicated by the indication information + 1", "HFN value indicated by the indication information - 2", "COUNT value indicated by the indication information - 1", etc., and this disclosure does not limit this.

[0352] Step 62: In response to the applicable condition of the HFN information not being met, updating the HFN information based on the update mode to generate updated HFN information.

[0353] Optionally, the applicable conditions of the HFN information may be indicated by the network device, or may be determined by the terminal device according to a protocol agreement, which is not limited in the present disclosure.

[0354] For example, when the PDCP data packet is sent too quickly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information. At this time, the update mode of the HFN information indicated by the network device may be "HFN value indicated by the indication information + 1"; and when the PDCP data packet is sent too slowly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information. At this time, the update mode of the HFN information indicated by the network device may be "HFN value in the indication information - 1", "HFN value in the indication information - 2", etc., and the present disclosure does not limit this.

[0355] For example, the applicable condition of the HFN information is: the minimum value of the SN. Accordingly, when the SN value corresponding to the received PDCP data packet is less than the minimum value, the terminal device can update the HFN information based on the update mode to generate updated HFN information.

[0356] For example, if the terminal device receives an indication message with an HFN value of 1 and an HFN value in the indication message of -1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is a minimum SN value of 3, then when the terminal device determines that the SN value corresponding to the received PDCP packet is 2, since 2 is less than the minimum SN value of 3 in the applicable condition, the applicable condition for the HFN information is not met, the terminal device can update the HFN information, and the updated HFN value is 0.

[0357] Alternatively, the applicable condition of the HFN information is: the maximum value of the SFN. Accordingly, when the SFN value corresponding to the received PDCP data packet is greater than the maximum value, the terminal device can update the HFN information based on the update mode to generate updated HFN information.

[0358] For example, a terminal device receives an indication message with an HFN value of 1, plus the HFN value in the indication message + 1. Furthermore, the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is 3. When the terminal device determines that the SFN value corresponding to the received PDCP packet is 4, since 4 is greater than the maximum SFN value of 3 in the applicable condition, the applicable condition for the HFN information is not met. Therefore, the terminal device updates the HFN information to 2.

[0359] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, maximum SFN value, etc. in the embodiments of the present disclosure.

[0360] It should be noted that, for other situations where the applicable conditions of the HFN information are not met, the content and specific implementation of updating the HFN information based on the update mode can be referred to the description of other embodiments of the present disclosure, and will not be repeated here.

[0361] Step 63: Determine the HFN value of the PDCP entity based on the updated HFN information.

[0362] Optionally, the updated HFN value may be determined as the HFN value of the PDCP entity.

[0363] Optionally, for a newly connected terminal device, the HFN value of the PDCP entity can be determined based on the applicable conditions of the determined HFN information and the received indication information, and then the corresponding COUNT value can be determined using the HFN value to decrypt or verify the integrity of the received data packet.

[0364] In an embodiment of the present disclosure, a terminal device may first receive HFN information sent by a network device. Then, based on the HFN information included in the indication information and the determined applicable conditions for the HFN information, if the applicable conditions for the HFN information are not met, the terminal device may update the HFN information based on an update mode to generate updated HFN information. The HFN value of the PDCP entity may then be determined. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures and improving data transmission reliability.

[0365] See Figure 7 , Figure 7 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a terminal device. Figure 9 As shown, the method may include but is not limited to the following steps:

[0366] Step 71: Receive indication information sent by a network device, wherein the indication information includes HFN information and MBS service information.

[0367] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0368] Optionally, the MBS service information may include at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0369] The MBS service identifier may include a temporary mobile group identifier (TMGI), an MBS session identifier (MBS Session ID), an MBS QoS flow identifier (MBS QoS flow ID), etc., which is not limited in the present disclosure.

[0370] In addition, the style or presentation form of the MBS bearer identifier may be determined by protocol agreement or network device configuration, such as MRB-1, MRB-2, etc., which is not limited in this disclosure.

[0371] Optionally, the protocol entity configuration information carried by the MBS may be PDCP configuration information, which may include: PDCP SN length, or data packet header compression configuration, or configuration of whether integrity detection is required, etc.

[0372] Alternatively, the protocol entity configuration information carried by the MBS may also be a radio link control (RLC) configuration, which may include: PDCP SN length, RLC working mode indication, and the like.

[0373] Alternatively, the protocol entity configuration information carried by the MBS may also be a MAC configuration, which may include a logical channel identifier, etc., which is not limited in the present disclosure.

[0374] Step 72: Determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information.

[0375] For example, the indication information received by the terminal device indicates that for radio bearer MRB-1, the HFN value is 1. Then, the terminal device can determine that the HFN value of the PDCP entity corresponding to radio bearer MRB-1 is 1, etc., which is not limited in this disclosure.

[0376] Optionally, the terminal device may also determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information when the SN value corresponding to the received PDCP data packet meets the applicable conditions of the HFN information.

[0377] For example, the SN value may be the minimum SN value. Accordingly, when the SN value corresponding to the received PDCP data packet is greater than or equal to the minimum value, the terminal device may determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information indicated by the network device.

[0378] Optionally, the PDCP data packet received by the terminal device may be the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.

[0379] For example, if the terminal device receives indication information indicating that the HFN value is 1 and the radio bearer corresponding to the MBS service information is MRB-1, and the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is a minimum SN value of 5, then the PDCP packet received by the terminal device may be the first PDCP packet received from radio bearer MRB-1. Therefore, when the terminal device determines that the SN value corresponding to this PDCP packet is 7, since 7 is greater than the minimum SN value of 5 in the applicable condition, the applicable condition for the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device determines that the HFN value of the PDCP entity corresponding to radio bearer MRB-1 is 1.

[0380] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, minimum SN value, etc. in the embodiments of the present disclosure.

[0381] Optionally, the terminal device may also determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information when the SFN value corresponding to the received PDCP data packet meets the applicable conditions of the HFN information.

[0382] For example, the SFN value may be the maximum SFN value. Accordingly, when the SFN value corresponding to the received PDCP data packet is less than or equal to the maximum value, the terminal device may determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information indicated by the network device.

[0383] For example, a terminal device receives an indication that the HFN value is 1 and the radio bearer corresponding to the MBS service information is MRB-1. Furthermore, the terminal device determines, based on the protocol or instructions from the network device, that the applicable condition for the HFN information is 5. When the terminal device determines that the SFN value corresponding to the received PDCP packet is 1, since 1 is less than the maximum SFN value of 5 in the applicable condition, the applicable condition for the HFN information is met. Therefore, based on the HFN value indicated by the network device, the terminal device determines that the HFN value of the PDCP entity corresponding to radio bearer MRB-1 is 1.

[0384] It should be noted that the above examples are merely illustrative and cannot be used as limitations on the indication information, HFN value, SFN maximum value, etc. in the embodiments of the present disclosure.

[0385] It should be noted that when the SN value and SFN value meet other applicable conditions of the HFN information, the specific content and implementation method of determining the HFN value of the PDCP entity corresponding to the MBS service information can be referred to the description of other embodiments of the present disclosure and will not be repeated here.

[0386] Optionally, for a terminal device that newly accesses the MBS service, the HFN value of the PDCP entity corresponding to the MBS service information may be determined based on the HFN information.

[0387] For example, the indication information received by the terminal device newly accessing the MBS service is: the HFN value is 1, and the radio bearer corresponding to the MBS service is MRB-1. Then the terminal device can determine the HFN value of the PDCP entity corresponding to the radio bearer MRB-1, etc. This disclosure does not limit this.

[0388] Step 73: Decrypt or verify the integrity of the received data corresponding to the MBS service information based on the HFN information.

[0389] For example, the terminal device determines that the HFN value of the PDCP entity corresponding to the wireless bearer MRB-1 is 1, and then can use the HFN value to determine the corresponding COUNT value, and then decrypt or verify the integrity of the received data corresponding to the wireless bearer MRB-1, etc. This disclosure does not limit this.

[0390] In the disclosed embodiments, a terminal device can first receive indication information sent by a network device, and then determine the HFN value of the PDCP entity corresponding to the MBS service information based on the HFN information and MBS service information included in the indication information. The terminal device can then decrypt or perform integrity verification on the received data corresponding to the MBS service information. This ensures that the terminal device and the network device have a consistent understanding of the HFN value, avoiding data decryption or integrity verification failures and improving data transmission reliability.

[0391] See Figure 8 , Figure 8 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a network device. Figure 8 As shown, the method may include but is not limited to the following steps:

[0392] Step 81: Send indication information to the terminal device, wherein the indication information includes hyperframe number HFN information.

[0393] Optionally, the HFN information may include any one or more of the following: a HFN value and a COUNT value.

[0394] Optionally, the network device may send indication information to the terminal device based on the system message, wherein the indication information includes HFN information.

[0395] For example, the network device may extend the SIB1 message so that the SIB1 can carry indication information. For example, a designated bit may be added to the SIB1, and the value of the designated bit may be used to represent the HFN value and / or COUNT value, etc., which is not limited in this disclosure.

[0396] Optionally, the network device may also send indication information to the terminal device based on the broadcast multicast service MBS control channel message.

[0397] It is understood that in the present disclosure, network devices may extend the MBS control channel message to carry indication information. For example, a designated bit may be added to the MBS control channel message, and the value of the designated bit may be used to represent the HFN value and / or COUNT value, etc., although this disclosure does not limit this.

[0398] Optionally, the network device may also send indication information to the terminal device based on a dedicated configuration message of the terminal device.

[0399] It is understood that in the present disclosure, the network device may configure the terminal device's dedicated configuration message to carry indication information. For example, a designated bit may be added to the terminal device's dedicated configuration message, and the value of the designated bit may be used to represent the HFN value and / or COUNT value, etc., although this disclosure does not limit this.

[0400] In the disclosed embodiment, the network device can send an instruction to the terminal device so that the terminal device can receive the HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failure or integrity verification failure, and improving data transmission reliability.

[0401] See Figure 9 , Figure 9 This is a flow chart of a method for determining a superframe number of a packet data convergence protocol entity provided by an embodiment of the present disclosure, and the method is configured to be executed by a network device. Figure 9 As shown, the method may include but is not limited to the following steps:

[0402] Step 91: Send indication information to the terminal device based on the system message, wherein the indication information includes HFN information.

[0403] For example, the network device may extend the SIB1 message so that the SIB1 can carry indication information. For example, a designated bit may be added to the SIB1, and the value of the designated bit may be used to represent the HFN value and / or COUNT value, etc., which is not limited in this disclosure.

[0404] The HFN information includes any one or more of the following: HFN value and COUNT value.

[0405] Step 92: Send the applicable conditions of the HFN information to the terminal device.

[0406] Optionally, the applicable conditions of the HFN information may include any one or more of the following: a value of the sequence number SN and a value of the system frame number SFN.

[0407] Among them, the value of SN may include any one or more of the following: the minimum value of SN; the maximum value of SN; the minimum and maximum values ​​of SN; the segment number corresponding to the value of SN; and the parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all values ​​of SN are equally divided in a specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0408] Optionally, the value of SFN includes any one or more of the following: the minimum value of SFN; the maximum value of SFN; the minimum and maximum values ​​of SFN; the segment number corresponding to the value of SFN; and the parameter pair (i, j) corresponding to the value of SFN, where i is the number of segments after all the values ​​of SFN are equally divided in a specified order, j is the segment number of the current value of SFN in the i segments, and j is an integer less than or equal to i.

[0409] It should be noted that the operations performed by the terminal device based on the applicable conditions of the HFN information and the corresponding effects can refer to the description of the terminal device side in other embodiments of the present disclosure, and will not be repeated here.

[0410] Optionally, the indication information may also include MBS service information.

[0411] The MBS service information may include at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0412] Optionally, the indication information may further include an update mode of the HFN information.

[0413] Optionally, the update mode includes an update step size and an update direction.

[0414] Among them, the update step size can be a value set corresponding to the speed at which the network device sends PDCP data packets. It can be any value, such as 1, 2, 3, etc., and this disclosure does not limit this.

[0415] In addition, the update direction can be any direction set by the network device, such as a “+” direction, a “-” direction, etc., and this disclosure does not limit this.

[0416] For example, when the PDCP data packet is sent too quickly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information. At this time, the update mode of the HFN information indicated by the network device may be "HFN value indicated by the indication information + 1"; and when the PDCP data packet is sent too slowly, the PDCP data packet received by the terminal device may not meet the applicable conditions of the HFN information. At this time, the update mode of the HFN information indicated by the network device may be "HFN value in the indication information - 1", "HFN value in the indication information - 2", etc., and the present disclosure does not limit this.

[0417] It should be noted that the operations performed by the terminal device based on different indication information and the corresponding effects can refer to the description of the terminal device side in other embodiments of the present disclosure, and will not be repeated here.

[0418] Step 93: In response to a change in any information except the HFN information in the system message, first change indication information is sent to the terminal device.

[0419] It is understood that, in order to reduce data transmission, when the network device sends indication information to the terminal device via a system message, it may send first change indication information to the terminal device if any information in the system message other than the HFN information changes. Thus, a change in the HFN value in the system message does not cause the network device to send the first change indication information to the terminal device, thereby reducing data transmission, allowing the terminal device and the network device to maintain a consistent understanding of the HFN value, and ensuring the reliability of data transmission.

[0420] Optionally, the network device may also send second change indication information to the terminal device when any information other than the HFN information in the MBS control channel message changes. Thus, a change in the HFN value in the MBS control channel message does not cause the network device to send the second change indication information to the terminal device, thereby reducing data transmission, allowing the terminal device and the network device to maintain a consistent understanding of the HFN value, and ensuring data transmission reliability.

[0421] In the disclosed embodiments, the network device can send indication information to the terminal device based on the system message, so that the terminal device can receive the HFN information. The network device can also send the terminal device the applicable conditions of the HFN information. When any information other than the HFN information in the system message changes, the network device sends first change indication information to the terminal device. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoids data decryption failures or integrity verification failures, and improves the reliability of data transmission.

[0422] In the embodiments provided above, the methods provided in the embodiments of the present disclosure are described from the perspectives of network devices and terminal devices, respectively. To implement the various functions provided in the methods provided in the embodiments of the present disclosure, the network devices and terminal devices may include hardware structures and software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures and software modules. Certain of the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures and software modules.

[0423] See Figure 10 , which is a structural diagram of a communication device 100 provided in an embodiment of the present disclosure. Figure 10 The communication device 100 shown may include a transceiver module 1001 and a processing module 1002 .

[0424] The transceiver module 1001 may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 1001 may implement a sending function and / or a receiving function.

[0425] It is understandable that the communication device 100 may be a terminal device, a device in a terminal device, or a device that can be used in conjunction with a terminal device.

[0426] The communication device 100 is configured on the terminal device side and includes:

[0427] The transceiver module 1001 is configured to receive indication information sent by a network device, wherein the indication information includes hyperframe number HFN information.

[0428] The processing module 1002 is configured to determine the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information.

[0429] Optionally, the HFN information includes any one or more of the following: an HFN value and a count value COUNT.

[0430] Optionally, the processing module 1002 is specifically configured to: in response to satisfying an applicable condition of the HFN information, determine the HFN value of the PDCP entity based on the HFN information.

[0431] Optionally, the transceiver module 1001 is further configured to receive the applicable conditions of the HFN information sent by the network device;

[0432] or,

[0433] The processing module 1002 is further configured to determine applicable conditions of the HFN information based on protocol agreement.

[0434] Optionally, the applicable conditions of the HFN information include any one or more of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0435] Optionally, the value of the SN includes any one or more of the following:

[0436] Minimum value of SN;

[0437] The maximum value of SN;

[0438] The minimum and maximum values ​​of SN;

[0439] The segment number corresponding to the SN value; and

[0440] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0441] Optionally, the value of the SFN includes any one or more of the following:

[0442] Minimum value of SFN;

[0443] Maximum value of SFN;

[0444] Minimum and maximum values ​​of SFN;

[0445] The segment number corresponding to the SFN value; and

[0446] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0447] Optionally, satisfying the applicable conditions includes:

[0448] The SN value corresponding to the PDCP data packet received by the terminal device meets the applicable condition;

[0449] or,

[0450] The SFN value corresponding to the PDCP data packet received by the terminal device meets the applicable conditions.

[0451] Optionally, the indication information also includes MBS service information, and the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.

[0452] Optionally, the SFN value corresponding to the received PDCP data packet includes any one or more of the following:

[0453] The SFN value corresponding to the time position of the last physical data channel of the successful reception of the PCDP data packet;

[0454] The SFN value corresponding to the time position of the first physical data channel where the PCDP data packet is successfully received; and

[0455] The SFN value corresponding to the PDCP data packet is successfully received.

[0456] Optionally, the applicable condition is the value of SN, and the processing module 1002 is specifically configured to:

[0457] In response to the application condition not being met and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN being s, updating the HFN information based on the difference s to generate updated HFN information;

[0458] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0459] Optionally, the applicable condition is a value of SFN, and the processing module 1002 is specifically configured to:

[0460] In response to the application condition not being met and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value being k, updating the HFN information based on the difference k to generate updated HFN information;

[0461] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0462] Optionally, the indication information further includes an update mode of the HFN information. The processing module 1002 is specifically configured to:

[0463] In response to the applicable condition not being met, updating the HFN information based on the update mode to generate updated HFN information;

[0464] Based on the updated HFN information, a HFN value of the PDCP entity is determined.

[0465] Optionally, the update mode includes an update step and an update direction.

[0466] Optionally, the transceiver module 1001 is specifically configured to:

[0467] receiving, based on the system message, indication information sent by the network device;

[0468] or,

[0469] receiving, based on a broadcast multicast service MBS control channel message, indication information sent by the network device;

[0470] or,

[0471] Based on the exclusive configuration message of the terminal device, receive the indication information sent by the network device.

[0472] Optionally, the indication information further includes MBS service information. The processing module 1002 is specifically configured to determine, based on the HFN information, a HFN value of a PDCP entity corresponding to the MBS service information.

[0473] Optionally, the MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0474] Optionally, the processing module 1002 is further configured to perform decryption or integrity verification on the received data corresponding to the MBS service information based on the HFN information.

[0475] Optionally, the processing module 1002 is specifically configured to determine, in response to the terminal device being a device that newly accesses an MBS service, a HFN value of the PDCP entity based on the HFN information.

[0476] In the communication apparatus provided by the present disclosure, a terminal device can first receive indication information sent by a network device, and then determine the HFN value of the PDCP entity based on the HFN information included in the indication information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failures or integrity verification failures, and improving data transmission reliability.

[0477] See Figure 11 , which is a structural diagram of a communication device 110 provided in an embodiment of the present disclosure. Figure 11 The communication device 110 shown may include a transceiver module 1101 .

[0478] The transceiver module 1101 may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 1101 may implement a sending function and / or a receiving function.

[0479] It is understandable that the communication device 110 may be a network device, a device in a network device, or a device that can be used in conjunction with a network device.

[0480] The communication device 110 is configured on the network device side and includes:

[0481] The transceiver module 1101 is configured to send indication information to a terminal device, wherein the indication information includes hyperframe number HFN information.

[0482] Optionally, the HFN information includes any one or more of the following: an HFN value and a count value COUNT.

[0483] Optionally, the transceiver module is further configured to send applicable conditions of the HFN information to the terminal device.

[0484] Optionally, the applicable conditions of the HFN information include any one or more of the following: a value of a sequence number SN and a value of a system frame number SFN.

[0485] Optionally, the value of the SN includes any one or more of the following:

[0486] Minimum value of SN;

[0487] The maximum value of SN;

[0488] The minimum and maximum values ​​of SN;

[0489] The segment number corresponding to the SN value; and

[0490] The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

[0491] Optionally, the value of the SFN includes any one or more of the following:

[0492] Minimum value of SFN;

[0493] Maximum value of SFN;

[0494] Minimum and maximum values ​​of SFN;

[0495] The segment number corresponding to the SFN value; and

[0496] The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

[0497] Optionally, the indication information also includes MBS service information.

[0498] Optionally, the MBS service information includes at least one or more of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

[0499] Optionally, the indication information further includes an update mode of the HFN information.

[0500] Optionally, the update mode includes an update step and an update direction.

[0501] Optionally, the transceiver module 1101 is specifically configured to:

[0502] Sending instruction information to the terminal device based on the system message;

[0503] or,

[0504] Sending indication information to the terminal device based on a broadcast multicast service MBS control channel message;

[0505] or,

[0506] Based on the exclusive configuration message of the terminal device, indication information is sent to the terminal device.

[0507] Optionally, the transceiver module 1101 is further configured to:

[0508] In response to a change in any information other than the HFN information in the system message, sending first change indication information to the terminal device;

[0509] or,

[0510] In response to a change in any information other than the HFN information in the MBS control channel message, second change indication information is sent to the terminal device.

[0511] In the communication device provided by the present disclosure, a network device can send indication information to a terminal device so that the terminal device can receive HFN information. This allows the terminal device and the network device to maintain a consistent understanding of the HFN value, avoiding data decryption failure or integrity verification failure, and improving the reliability of data transmission.

[0512] See Figure 12 , Figure 12 1 is a schematic diagram of the structure of another communication device 120 provided in an embodiment of the present disclosure. Communication device 120 can be a network device or a terminal device, or a chip, chip system, or processor that supports a network device in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports a terminal device in implementing the above-mentioned method. This device can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0513] The communication device 120 may include one or more processors 1201. The processor 1201 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0514] Optionally, the communication device 120 may further include one or more memories 1202, on which a computer program 1204 may be stored. The processor 1201 executes the computer program 1204 to cause the communication device 120 to perform the method described in the above method embodiment. Optionally, the memory 1202 may also store data. The communication device 120 and the memory 1202 may be provided separately or integrated together.

[0515] Optionally, the communication device 120 may further include a transceiver 1205 and an antenna 1206. The transceiver 1205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 1205 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.

[0516] Optionally, the communication device 120 may further include one or more interface circuits 1207. The interface circuit 1207 is configured to receive code instructions and transmit the code instructions to the processor 1201. The processor 1201 executes the code instructions to enable the communication device 120 to execute the method described in the above method embodiment.

[0517] The communication device 120 is a terminal device: the processor 1201 is used to execute Figure 2 Step 22 in the Figure 3 Step 32 in Figure 4 Step 42 in Figure 4 Step 43 in Figure 5 Step 52 in Figure 5 Step 53 in Figure 6 Step 62 in Figure 6 Step 63 in Figure 7 step 72 in; or Figure 7 Step 73 in the above. The transceiver 1205 is used to perform Figure 2 Step 21 in the Figure 3 Step 31 in Figure 4 Step 41 in Figure 5 Step 51 in Figure 6 step 61 in step 61; or Figure 7Step 71 in .

[0518] The communication device 120 is a network device: the transceiver 1205 is used to perform Figure 8 Step 81 in Figure 9 Step 91 in Figure 9 step 92 in step 92; or Figure 9 Step 93 in .

[0519] In one implementation, processor 1201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0520] In one implementation, processor 1201 may store a computer program 1203. Computer program 1203, when executed on processor 1201, enables communication device 120 to perform the method described in the above method embodiment. Computer program 1203 may be embedded in processor 1201, in which case processor 1201 may be implemented by hardware.

[0521] In one implementation, the communication device 120 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0522] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited thereto. Figure 12 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0523] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0524] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0525] (3) ASIC, such as modem;

[0526] (4) Modules that can be embedded in other devices;

[0527] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0528] (6)Others, etc.

[0529] For the case where the communication device may be a chip or a chip system, see Figure 13 Schematic diagram of the chip structure shown. Figure 13 The chip shown includes a processor 1301 and an interface 1302. There may be one or more processors 1301 and there may be more than one interface 1302.

[0530] For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present disclosure:

[0531] Interface 1302, used to execute Figure 2 Step 21 in the Figure 3 Step 31 in Figure 4 Step 41 in Figure 5 Step 51 in Figure 6 step 61 in step 61; or Figure 7 Step 71 in .

[0532] For the case where the chip is used to implement the functions of the network device in the embodiments of the present disclosure:

[0533] Interface 1302, used to execute Figure 8 Step 81 in Figure 9 Step 91 in Figure 9 step 92 in step 92; or Figure 9 Step 93 in .

[0534] Optionally, the chip further includes a memory 1303, which is used to store necessary computer programs and data.

[0535] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0536] The present disclosure also provides a communication system comprising the aforementioned Figure 10 The communication device as the terminal device in the embodiment and Figure 11 In the embodiment, the communication device as the network device, or the system includes the aforementioned Figure 12 The communication device in the embodiment serves as a terminal device and the communication device serves as a network device.

[0537] The present disclosure also provides a computer-readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0538] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0539] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0540] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0541] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0542] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0543] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0544] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0545] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0546] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A method for determining a superframe number of a packet data convergence protocol entity, characterized in that: The method is configured to be executed by a terminal device, and includes: receiving indication information sent by a network device, wherein the indication information includes hyperframe number HFN information; Determining a HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information; The indication information further includes broadcast multicast service MBS service information. The determining the HFN value of the packet data convergence protocol PDCP entity based on the HFN information includes: Determining, based on the HFN information, a HFN value of a PDCP entity corresponding to the MBS service information; The MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

2. The method according to claim 1, wherein The HFN information includes any one of the following items: a HFN value and a count value COUNT.

3. The method according to claim 1, wherein The determining, based on the HFN information, the HFN value of the Packet Data Convergence Protocol (PDCP) entity includes: In response to satisfying an applicable condition of the HFN information, a HFN value of the PDCP entity is determined based on the HFN information.

4. The method according to claim 3, wherein Also includes: receiving applicable conditions of the HFN information sent by the network device; or, Based on the agreement, the applicable conditions of the HFN information are determined.

5. The method according to claim 4, wherein The applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.

6. The method according to claim 5, wherein The value of SN includes any of the following: Minimum value of SN; The maximum value of SN; The minimum and maximum values ​​of SN; The segment number corresponding to the SN value; and The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

7. The method according to claim 5, wherein The value of the SFN includes any of the following: Minimum value of SFN; Maximum value of SFN; Minimum and maximum values ​​of SFN; The segment number corresponding to the SFN value; and The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

8. The method according to any one of claims 5 to 7, wherein: The applicable conditions include: The SN value corresponding to the PDCP data packet received by the terminal device meets the applicable condition; or, The SFN value corresponding to the PDCP data packet received by the terminal device meets the applicable conditions.

9. The method according to claim 8, wherein The indication information also includes MBS service information, and the received PDCP data packet is the first PDCP data packet received by the terminal device from the radio bearer MRB corresponding to the MBS service information.

10. The method according to claim 8, wherein The SFN value corresponding to the received PDCP data packet includes any one of the following: The SFN value corresponding to the time position of the last physical data channel where a PCDP data packet is successfully received; The SFN value corresponding to the time position of the first physical data channel that successfully receives the PCDP data packet; as well as The SFN value corresponding to the PDCP data packet is successfully received.

11. The method according to claim 4, wherein The applicable condition is a value of the SN, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes: In response to the application condition not being met and the difference between the SN value corresponding to the PDCP data packet received by the terminal device and the value of the SN being s, updating the HFN information based on the difference s to generate updated HFN information; Based on the updated HFN information, a HFN value of the PDCP entity is determined.

12. The method according to claim 4, wherein The applicable condition is a value of the SFN, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes: In response to the application condition not being met and the difference between the SFN value corresponding to the PDCP data packet received by the terminal device and the SFN value being k, updating the HFN information based on the difference k to generate updated HFN information; Based on the updated HFN information, a HFN value of the PDCP entity is determined.

13. The method according to claim 4, wherein The indication information also includes an update mode of the HFN information, and determining the HFN value of the Packet Data Convergence Protocol (PDCP) entity based on the HFN information includes: In response to the applicable condition not being met, updating the HFN information based on the update mode to generate updated HFN information; Based on the updated HFN information, a HFN value of the PDCP entity is determined.

14. The method according to claim 13, wherein The update mode includes an update step size and an update direction.

15. The method according to claim 1, wherein The receiving instruction information sent by the network device includes: receiving, based on the system message, indication information sent by the network device; or, receiving, based on a broadcast multicast service MBS control channel message, indication information sent by the network device; or, Based on the exclusive configuration message of the terminal device, receive the indication information sent by the network device.

16. The method according to claim 1, wherein Also includes: Based on the HFN information, decryption or integrity verification is performed on the received data corresponding to the MBS service information.

17. The method according to claim 1, wherein The determining, based on the HFN information, the HFN value of the Packet Data Convergence Protocol (PDCP) entity includes: In response to the terminal device being a device that newly accesses the MBS service, the HFN value of the PDCP entity is determined based on the HFN information.

18. A method for determining a superframe number of a packet data convergence protocol entity, characterized in that: The method is configured to be executed by a network device, and includes: Sending indication information to the terminal device, wherein the indication information includes hyperframe number HFN information and broadcast multicast MBS service information; The HFN information and MBS service information are used to assist the terminal device in determining the HFN value of the PDCP entity corresponding to the MBS service information; The MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

19. The method according to claim 18, wherein The HFN information includes any one of the following items: a HFN value and a count value COUNT.

20. The method of claim 18, wherein Also includes: Applicable conditions for sending the HFN information to the terminal device.

21. The method according to claim 20, wherein The applicable conditions of the HFN information include any one of the following: the value of the sequence number SN and the value of the system frame number SFN.

22. The method according to claim 21, wherein The value of SN includes any of the following: Minimum value of SN; The maximum value of SN; The minimum and maximum values ​​of SN; The segment number corresponding to the SN value; and The parameter pair (m, n) corresponding to the value of SN, where m is the number of segments after all the values ​​of SN are equally divided in the specified order, n is the segment number of the current value of SN in the m segments, and n is an integer less than or equal to m.

23. The method according to claim 21, wherein The value of the SFN includes any of the following: Minimum value of SFN; Maximum value of SFN; Minimum and maximum values ​​of SFN; The segment number corresponding to the SFN value; and The parameter pair (i, j) corresponding to the SFN value, where i is the number of segments after all SFN values ​​are equally divided in a specified order, j is the segment number of the current SFN value in the i segments, and j is an integer less than or equal to i.

24. The method of claim 18, wherein: The MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

25. The method of claim 18, wherein: The indication information also includes an update mode of the HFN information.

26. The method of claim 25, wherein: The update mode includes an update step size and an update direction.

27. The method according to any one of claims 18 to 26, wherein: The sending of instruction information to the terminal device includes: Sending instruction information to the terminal device based on the system message; or, Sending indication information to the terminal device based on a broadcast multicast service MBS control channel message; or, Based on the exclusive configuration message of the terminal device, indication information is sent to the terminal device.

28. The method of claim 27, wherein: Also includes: In response to a change in any information other than the HFN information in the system message, sending first change indication information to the terminal device; or, In response to a change in any information other than the HFN information in the MBS control channel message, second change indication information is sent to the terminal device.

29. A communication device, characterized in that: The apparatus is configured on the terminal device side, and includes: a transceiver module, configured to receive indication information sent by a network device, wherein the indication information includes hyperframe number HFN information; a processing module, configured to determine a HFN value of a Packet Data Convergence Protocol (PDCP) entity based on the HFN information; The indication information also includes MBS service information, and the processing module is further configured to determine, based on the HFN information, a HFN value of a PDCP entity corresponding to the MBS service information; The MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

30. A communication device, characterized in that: The apparatus is configured on the network device side, and includes: a transceiver module, configured to send indication information to a terminal device, wherein the indication information includes hyperframe number HFN information and MBS service information; The HFN information and MBS service information are used to assist the terminal device in determining the HFN value of the PDCP entity corresponding to the MBS service information; The MBS service information includes at least one of the following: an MBS service identifier, an MBS bearer identifier, and MBS bearer protocol entity configuration information.

31. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 1 to 17; or, the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 18 to 28.

32. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method according to any one of claims 1 to 17; or the processor is configured to execute the code instructions to perform the method according to any one of claims 18 to 28.

33. A computer-readable storage medium for storing instructions, which, when executed, enable the method according to any one of claims 1 to 17 to be implemented; or for storing instructions, which, when executed, enable the method according to any one of claims 18 to 28 to be implemented.

Images