CN113661746A

CN113661746A - Information configuration method and device, terminal equipment and network equipment

Info

Publication number: CN113661746A
Application number: CN201980095153.XA
Authority: CN
Inventors: 王淑坤; 卢前溪; 尤心
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-09-23
Filing date: 2019-09-23
Publication date: 2021-11-16
Also published as: WO2021056152A1

Abstract

The embodiment of the application provides an information configuration method and device, terminal equipment and network equipment, wherein the method comprises the following steps: the terminal equipment receives a second Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU), wherein the second PDCP PDU carries Hyper Frame Number (HFN) offset information, and the HFN offset information is used for indicating a difference value of an HFN (high frequency channel) corresponding to a second Sequence Number (SN) corresponding to the second PDCP PDU relative to a first HFN, wherein the first HFN is the HFN corresponding to a first SN corresponding to the first PDCP PDU or the first HFN is a reference HFN.

Description

Information configuration method and device, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to an information configuration method and device, terminal equipment and network equipment.

Background

In a New Radio (NR) system, a Packet Data Convergence Protocol (PDCP) layer has a concept of a Sequence Number (SN) for identifying a Packet. In a multicast scenario, the SN of the PDCP layer of a transmitting end (the transmitting end is a network device) is not initialized according to a receiving end (the receiving end is a terminal device), and the network device and the terminal device need to unify SNs and further unify Hyper Frame Numbers (HFNs). For a terminal device, there is a need to acquire a SN and an HFN, where the SN may be acquired in a header of a PDCP Packet Data Unit (PDU), but the HFN cannot be determined.

Disclosure of Invention

The embodiment of the application provides an information configuration method and device, terminal equipment and network equipment.

The information configuration method provided by the embodiment of the application comprises the following steps:

the terminal equipment receives a second PDCP PDU, wherein the second PDCP PDU carries HFN offset information, and the HFN offset information is used for indicating a difference value of an HFN (high frequency noise figure) which a second SN corresponding to the second PDCP PDU belongs to relative to a first HFN, wherein the first HFN is the HFN which a first SN corresponding to the first PDCP PDU belongs to or is a reference HFN.

the method comprises the steps that terminal equipment receives a first PDCP PDU, wherein the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

the network equipment sends a second PDCP PDU, wherein the second PDCP PDU carries HFN offset information, and the HFN offset information is used for indicating a difference value of an HFN to which a second SN corresponding to the second PDCP PDU belongs relative to a first HFN, wherein the first HFN is the HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.

the network equipment sends a first PDCP PDU, wherein the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

The information configuration device provided by the embodiment of the application comprises:

a receiving unit, configured to receive a second PDCP PDU, where the second PDCP PDU carries HFN offset information, and the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.

a receiving unit, configured to receive a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

a sending unit, configured to send a second PDCP PDU, where the second PDCP PDU carries HFN offset information, and the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.

a sending unit, configured to send a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

The terminal device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the information configuration method.

The network equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory and executing the information configuration method.

The chip provided by the embodiment of the application is used for realizing the information configuration method.

Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the information configuration method.

The computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program enables a computer to execute the information configuration method.

The computer program product provided by the embodiment of the application comprises computer program instructions, and the computer program instructions enable a computer to execute the information configuration method.

The computer program provided by the embodiment of the present application, when running on a computer, causes the computer to execute the above information configuration method.

Through the technical scheme, the NR system supports the broadcast and multicast of the MBMS service, and meanwhile, a scheme is provided, namely a first HFN is configured through first configuration information, a PDCP PDU carries one HFN offset information, and the HFN corresponding to the PDCP PDU can be determined through the first HFN and the HFN offset information; or, the PDCP PDU directly carries the HFN corresponding to the PDCP PDU. Therefore, under a multicast scene, the terminal device can still accurately acquire the HFN, so that the terminal device can perform decryption of the PDCP layer, integrity protection verification of the PDCP layer and maintenance of a receiving window of the PDCP layer.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

FIG. 2 is a diagram of a first SIB related configuration provided by an embodiment of the present application;

fig. 3 is a schematic diagram of a PTM configuration transmission mechanism provided in an embodiment of the present application;

fig. 4 is a PTM channel and a map thereof provided by an embodiment of the present application;

fig. 5 is a first flowchart illustrating an information configuration method according to an embodiment of the present application;

fig. 6 is a second flowchart illustrating an information configuration method according to an embodiment of the present application;

fig. 7 is a first schematic structural diagram of an information configuring apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an information configuring apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a third information configuring apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an information configuring apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a chip of an embodiment of the present application;

fig. 13 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a system, a 5G communication system, a future communication system, or the like.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the Network device 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.

The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminals 120.

Alternatively, the 5G communication system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal 120 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of the services in future life, the third generation partnership project (3)^rdGeneration Partnership Project, 3GPP) the international organization for standardization began developing 5G. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), Low-Latency high-reliability communication (URLLC), and massive Machine-Type communication (mMTC).

On the one hand, the eMBB still targets users to obtain multimedia content, services and data, and its demand is growing very rapidly. On the other hand, because the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference between the capabilities and the requirements is relatively large, it cannot be said that it must be analyzed in detail in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety, and the like. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost and long service life of the module, etc.

RRC state

In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data service, 5G defines a new Radio Resource Control (RRC) state, that is, an RRC INACTIVE (RRC _ INACTIVE) state. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein the content of the first and second substances,

1) RRC _ IDLE state (IDLE state for short): mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no UE context and no RRC connection.

2) RRC _ CONNECTED state (CONNECTED state for short): there is an RRC connection and there is a UE context on the base station side and the UE side. The network side knows that the location of the UE is at a specific cell level. Mobility is network side controlled mobility. Unicast data may be transmitted between the UE and the base station.

3) RRC _ INACTIVE state (INACTIVE state for short): mobility is UE-based cell selection reselection, there is a connection between CN-NRs, UE context exists on a certain base station, paging is triggered by RAN, RAN-based paging area is managed by RAN, and network side knows that UE location is based on RAN's paging area level.

MBMS

The 3GPP Release 6(Release 6, R6) introduced Multimedia Broadcast Multicast Service (MBMS), which is a technology for transmitting data from one data source to multiple UEs through shared network resources, and can provide Multimedia services while effectively utilizing network resources to implement Broadcast and Multicast of higher-rate (e.g., 256kbps) Multimedia services.

Since the MBMS spectrum efficiency in 3GPP R6 is low, it is not enough to effectively carry and support the operation of mobile tv type services. Therefore, in LTE, 3GPP explicitly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.

The 3GPP R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes a Single Frequency Network (SFN) concept, that is, a Multimedia Broadcast multicast service Single Frequency Network (MBSFN), where MBSFN employs a uniform Frequency to simultaneously transmit service data in all cells, but needs to ensure synchronization between the cells. The method can greatly improve the distribution of the overall signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocol.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to the idle-state or connected-state UE.

The 3GPP R13 introduces a Single Cell Point To multipoint (SC-PTM) concept, and SC-PTM is based on the MBMS network architecture.

MBMS introduces new logical channels including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and SC-MTCH are mapped to a Downlink-Shared Channel (DL-SCH), and the DL-SCH is further mapped to a Physical Downlink-Shared Channel (PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a Physical Channel. The SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

MBMS introduces a new System Information Block (SIB) type, SIB 20. Specifically, the configuration information of the SC-MCCH is transmitted through SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and the scheduling of the wireless frame and the subframe of the SC-MCCH. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m ═ 0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH (i.e., SC-MCCH-modification period) configured in SIB 20. 2) And scheduling the radio frame of the SC-MCCH to meet the following requirements: SFN mod MCCH-repetition period ═ MCCH-Offset, where SFN represents the system frame number of a radio frame, MCCH-repetition period represents the repetition period of SC-MCCH, and MCCH-Offset represents the Offset of SC-MCCH. 3) The sub-frame of the SC-MCCH is scheduled and indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), that is, a Single Cell RNTI (SC-RNTI) is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling an SC-MCCH, and optionally, the SC-RNTI is fixedly valued as FFFC. On the other hand, a new RNTI, namely a Single Cell Notification RNTI (SC-N-RNTI) is introduced to identify a PDCCH (e.g., Notification PDCCH) for indicating a change Notification of the SC-MCCH, and optionally, the SC-N-RNTI is fixedly valued as FFFB; further, the change notification may be indicated by one bit of 8 bits (bits) of the DCI 1C. In LTE, the configuration information of SC-PTM is based on SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH which is used for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration) for configuring configuration information of the SC-PTM. The configuration information of SC-PTM includes: temporary Mobile Group Identity (TMGI), session Identity (session id), Group RNTI (G-RNTI), Discontinuous Reception (DRX) configuration information, SC-PTM service information of the neighbor cell, and the like. It should be noted that SC-PTM in R13 does not support Robust Header Compression (ROHC) function.

The downlink discontinuous reception of SC-PTMs is controlled by the following parameters: ondurationTimerSCPTM, drx-InactivetTimeSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

When [ (SFN x 10) + subframe number ] module (SC-MTCH-scheduling cycle) ═ SC-MTCH-scheduling offset is satisfied, starting a timer onDurationTimerSCPTM;

when receiving downlink PDCCH dispatching, starting a timer drx-InactivetyTimerSCPTM;

the downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-inactivityttimerscptm is running.

SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely, SIB15+ MBMSIntestrIndication. The traffic continuity of idle UEs is based on the concept of frequency priority.

In NR, many scenarios need to support multicast and broadcast traffic needs, such as in car networking, industrial internet, etc. It is necessary to introduce MBMS in NR.

On the other hand, a Radio Link Control (RLC) layer (i.e., an RLC entity) has three modes, which are: transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In NR, the RLC AM mode is with an Automatic Repeat-reQuest (ARQ) feedback mechanism. The receiving end transmits an RLC status report to feed back the reception status of the RLC packet as positive Acknowledgement (ACK) or Negative Acknowledgement (NACK). The transmitting end may repeatedly transmit the RLC packet feeding back the NACK.

In NR, the PDCP layer has SN, and only unicast has SN, after the UE enters into RRC connection state, the network side and the UE side both initialize PDCP SN of 0 and HFN of 0. However, in the multicast, the PDCP SN of the transmitting end is not initialized to 0 according to a certain UE. The UE needs to acquire the SNs and HFNs, which are present in the header of the PDCP PDU, but the HFNs are maintained by the UE itself. For a scenario in which the UE reselects from one cell to another cell to receive the multicast service, or a scenario in which the UE initially receives a multicast service in one cell, the UE cannot maintain the HFN. Therefore, after introducing the function of the PDCP layer in multicast, the UE needs to acquire HFN. Therefore, the following technical scheme of the embodiment of the application is provided.

In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, and referring to fig. 2, the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e., the first MCCH).

Further, the first MCCH is used to carry a first signaling, and in this embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (e.g., service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, which may also be called NR MTCH (i.e., the first MTCH) optionally.

Specifically, the first signaling is used to configure a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, for example, the identification information for identifying the service, such as the TMGI, the session id, and the like. The scheduling information corresponding to the traffic channel, for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, for example, G-RNTI, DRX configuration information, and the like.

It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on the PDCCH. Wherein, the RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, which is a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

Further, the first MCCH also carries at least one of: the first indication information is used for indicating whether the MBMS service (corresponding to the TMGI and/or the session identifier) needs RLC feedback or not; second indication information, wherein the second indication information is used for indicating the number of members in a multicast group corresponding to the MBMS service; and third indication information, wherein the third indication information is used for indicating whether the terminal equipment needs to receive the MBMS after entering a connected state. Here, when the terminal device is registered to the MBMS service, the network device assigns a member index number to the terminal device registered to the MBMS service.

It should be noted that, in the embodiment of the present application, naming of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience of description, the first SIB may also be abbreviated as SIB, the first MCCH may also be abbreviated as MCCH, and the first MTCH may also be abbreviated as MTCH, and referring to fig. 3, a PDCCH (i.e., MCCH PDCCH) for scheduling MCCH and a notification PDCCH are configured through SIB, wherein a PDSCH (i.e., MCCH PDSCH) for transmitting MCCH is scheduled through DCI carried by MCCH PDCCH. Further, M PDCCHs (i.e., MTCH 1PDCCH, MTCH 2PDCCH, …, MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules a PDSCH (i.e., MTCH n PDSCH) for transmitting MTCH n, n being an integer of 1 or more and M or less. Referring to fig. 4, MCCH and MTCH are mapped to DL-SCH, which belong to a logical channel, DL-SCH which belongs to a transport channel, and PDSCH which belongs to a physical channel, and further DL-SCH which is mapped to PDSCH.

Fig. 5 is a first schematic flow chart of an information configuration method provided in an embodiment of the present application, and as shown in fig. 5, the information configuration method includes the following steps:

step 501: the terminal equipment receives a second PDCP PDU, wherein the second PDCP PDU carries HFN offset information, and the HFN offset information is used for indicating a difference value of an HFN (high frequency noise figure) which a second SN corresponding to the second PDCP PDU belongs to relative to a first HFN, wherein the first HFN is the HFN which a first SN corresponding to the first PDCP PDU belongs to or is a reference HFN.

In an optional embodiment of the present application, the first HFN is determined by the terminal device through the received first configuration information. Specifically, the network device sends first configuration information, and the terminal device receives the first configuration information, where the first configuration information is used to determine the first HFN. Further, optionally, the network device may be a base station, for example, a gbb.

In this embodiment, the first configuration information is carried in a first MCCH, where the first MCCH is a control channel for an MBMS service. It should be noted that the first MCCH may be understood with reference to the related description. Here, the first HFN is configured through the first MCCH.

In an optional embodiment of the present application, the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN. The first HFN may also be referred to as a reference HFN.

In an optional embodiment, the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information. For example: the first HFN is an HFN to which a first SN corresponding to a first PDCP PDU after the receiving time of the first MCCH belongs.

It should be noted that the PDCP PDU referred to in the embodiments of the present application is used for transmitting the MBMS service, and thus may also be referred to as an MBMS PDCP PDU.

It should be noted that the SNs referred to in the embodiments of the present application may also be referred to as PDCP SNs.

In the embodiment of the application, a network device sends a second PDCP PDU, and a terminal device receives the second PDCP PDU, where the second PDCP PDU carries HFN offset information.

(1) In an optional embodiment, all PDCP PDUs sent by the network device carry the HFN offset information, and correspondingly, all PDCP PDUs received by the terminal device carry the HFN offset information, and the second PDCP PDU belongs to one of the PDCP PDUs.

Specifically, the packet headers of all PDCP PDUs carry HFN offset information (HFN offset), which is a difference value of the HFN to which the SN of the currently received PDCP PDU belongs with respect to the first HFN.

Optionally, the first HFN is a first HFN configured in a first MCCH closest to a reception time of a currently received PDCP PDU.

(2) In another optional embodiment, the first n PDCP PDUs after the first configuration information sent by the network device carry the HFN offset information, and correspondingly, the first n PDCP PDUs after the first configuration information received by the terminal device carry the HFN offset information, where n is a positive integer, and the second PDCP PDU belongs to one of the first n PDCP PDUs.

For example: the first configuration information is carried in a first MCCH, the first n PDCP PDUs after the first MCCH carry HFN offset information (HFN offset), n is greater than or equal to 1 and n is an integer. The HFN offset information is a difference value of an HFN to which a SN of a currently received PDCP PDU belongs with respect to the first HFN. Optionally, the first HFN is a first HFN configured in a first MCCH closest to a reception time of a currently received PDCP PDU.

In an optional embodiment, the terminal device determines a second HFN based on the HFN offset information carried in the second PDCP PDU and the first HFN; the second HFN refers to an HFN to which a second SN corresponding to the second PDCP PDU belongs. Further, the terminal device determines PDCP count information based on the second HFN and a second SN corresponding to the second PDCP PDU, where the PDCP count information is used for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.

In specific implementation, the terminal device receives the first MCCH, acquires the first HFN (i.e., the reference HFN) from the first MCCH, then acquires the HFN offset information from the PDCP PDU, and further determines the HFN corresponding to the PDCP PDU based on the first HFN and the HFN offset information. Further, through the HFN and SN corresponding to the PDCP PDU, PDCP count information (PDCP counter) can be calculated, and then the PDCP count information is used to perform decryption of the PDCP layer and/or integrity protection verification of the PDCP layer and/or maintain a receive window of the PDCP layer.

In an optional embodiment, the terminal device maintains a third HFN according to a SN corresponding to a received third PDCP PDU, where a receiving time of the third PDCP PDU is later than a receiving time of the second PDCP PDU.

In a specific implementation, after determining the second HFN of the second PDCP PDU, and subsequently receiving a PDCP PDU (e.g., a third PDCP PDU), the terminal device may maintain the second HFN, for example, update the second HFN to the third HFN, until the cell is reselected.

Fig. 6 is a second flowchart of an information configuration method provided in the embodiment of the present application, and as shown in fig. 6, the information configuration method includes the following steps:

step 601: the method comprises the steps that terminal equipment receives a first PDCP PDU, wherein the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

In the embodiment of the application, a network device sends a first PDCP PDU, and a terminal device receives the first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs. Further, optionally, the network device may be a base station, for example, a gbb.

In an optional embodiment, all PDCP PDUs sent by the network device carry HFN, and correspondingly, all PDCP PDUs received by the terminal device carry HFN, where the first PDCP PDU belongs to one of the PDCP PDUs.

Specifically, the headers of all PDCP PDUs of the MBMS service carry the complete HFN. After receiving the PDCP PDU, the terminal equipment acquires the HFN and the SN from the packet header of the PDCP PDU.

In an optional embodiment, the terminal device determines PDCP count information based on the first HFN and a first SN corresponding to the first PDCP PDU, wherein the PDCP count information is used for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.

In specific implementation, the terminal device receives the PDCP PDU, acquires the HFN and the SN from the PDCP PDU, and may calculate PDCP count information (PDCP counter) through the HFN and the SN corresponding to the PDCP PDU, and further perform decryption of the PDCP layer and/or integrity protection verification of the PDCP layer and/or maintain a receive window of the PDCP layer by using the PDCP count information.

Fig. 7 is a schematic structural diagram of an information configuration apparatus according to an embodiment of the present application, where as shown in fig. 7, the information configuration apparatus includes:

a receiving unit 701, configured to receive a second PDCP PDU, where the second PDCP PDU carries HFN offset information, and the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.

In an optional embodiment, the first HFN is determined by the terminal device through the received first configuration information.

In an optional embodiment, the first configuration information is carried in a first MCCH, where the first MCCH is a control channel for an MBMS service.

In an optional embodiment, the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information.

In an optional embodiment, all PDCP PDUs received by the receiving unit 701 carry the HFN offset information, and the second PDCP PDU belongs to one of the PDCP PDUs.

In an optional embodiment, the HFN offset information is carried by first n PDCP PDUs after the first configuration information received by the receiving unit 701, where n is a positive integer, and the second PDCP PDU belongs to one of the first n PDCP PDUs.

In an alternative embodiment, the apparatus further comprises:

a determining unit 702, configured to determine a second HFN based on the HFN offset information carried in the second PDCP PDU and the first HFN; the second HFN refers to an HFN to which a second SN corresponding to the second PDCP PDU belongs.

In an optional embodiment, the determining unit 702 is further configured to determine PDCP count information based on the second HFN and a second SN corresponding to the second PDCP PDU, where the PDCP count information is used for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.

In an alternative embodiment, the apparatus further comprises:

a maintaining unit (not shown in the figure), configured to maintain a third HFN according to a SN corresponding to a received third PDCP PDU, where a receiving time of the third PDCP PDU is later than a receiving time of the second PDCP PDU.

It should be understood by those skilled in the art that the related description of the information configuring apparatus in the embodiments of the present application can be understood by referring to the related description of the information configuring method in the embodiments of the present application.

Fig. 8 is a schematic structural diagram of an information configuration apparatus according to an embodiment of the present application, where as shown in fig. 8, the information configuration apparatus includes:

a receiving unit 801, configured to receive a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

In an optional embodiment, all PDCP PDUs received by the receiving unit 801 carry HFN, and the first PDCP PDU belongs to one of the PDCP PDUs.

In an alternative embodiment, the apparatus further comprises:

a determining unit 802, configured to determine PDCP count information based on the first HFN and a first SN corresponding to the first PDCP PDU, where the PDCP count information is used for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.

Fig. 9 is a schematic structural diagram of a third information configuring apparatus provided in the embodiment of the present application, and as shown in fig. 9, the information configuring apparatus includes:

a sending unit 901, configured to send a second PDCP PDU, where the second PDCP PDU carries HFN offset information, where the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.

In an optional embodiment, the sending unit 901 is further configured to send first configuration information, where the first configuration information carries the first HFN.

In an optional embodiment, all PDCP PDUs transmitted by the transmitting unit 901 carry the HFN offset information, and the second PDCP PDU belongs to one of the PDCP PDUs.

In an optional embodiment, the first n PDCP PDUs after the first configuration information sent by the sending unit 901 carry the HFN offset information, where n is a positive integer, and the second PDCP PDU belongs to one of the first n PDCP PDUs.

Fig. 10 is a schematic structural diagram of a fourth information configuring apparatus provided in the embodiment of the present application, and as shown in fig. 10, the information configuring apparatus includes:

a sending unit 1001, configured to send a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.

In an optional embodiment, all PDCP PDUs transmitted by the transmitting unit 1001 carry HFN, and the first PDCP PDU belongs to one of the PDCP PDUs.

Fig. 11 is a schematic structural diagram of a communication device 1100 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 1100 shown in fig. 11 includes a processor 1110, and the processor 1110 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 11, the communication device 1100 may further include a memory 1120. From the memory 1120, the processor 1110 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 1120 may be a separate device from the processor 1110, or may be integrated into the processor 1110.

Optionally, as shown in fig. 11, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 1130 may include a transmitter and a receiver, among others. The transceiver 1130 may further include one or more antennas, which may be present in number.

Optionally, the communication device 1100 may specifically be a network device in the embodiment of the present application, and the communication device 1100 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 1100 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 1100 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 12 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1200 shown in fig. 12 includes a processor 1210, and the processor 1210 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 12, the chip 1200 may further include a memory 1220. From the memory 1220, the processor 1210 may call and execute a computer program to implement the method in the embodiment of the present application.

The memory 1220 may be a separate device from the processor 1210, or may be integrated into the processor 1210.

Optionally, the chip 1200 may further include an input interface 1230. The processor 1210 may control the input interface 1230 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 1200 may further include an output interface 1240. The processor 1210 may control the output interface 1240 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

Fig. 13 is a schematic block diagram of a communication system 1300 provided in an embodiment of the present application. As shown in fig. 13, the communication system 1300 includes a terminal device 1310 and a network device 1320.

The terminal device 1310 may be configured to implement corresponding functions implemented by the terminal device in the foregoing method, and the network device 1320 may be configured to implement corresponding functions implemented by the network device in the foregoing method, for brevity, no further description is provided here.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic random access memory (Dynamic RAM, DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), synchlronous DRAM (SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

An information configuration method, the method comprising:

the terminal equipment receives a second Packet Data Convergence Protocol (PDCP) Packet Data Unit (PDU), wherein the second PDCP PDU carries Hyper Frame Number (HFN) offset information, and the HFN offset information is used for indicating a difference value of an HFN (high frequency channel) corresponding to a second Sequence Number (SN) corresponding to the second PDCP PDU relative to a first HFN, wherein the first HFN is the HFN corresponding to a first SN corresponding to the first PDCP PDU or the first HFN is a reference HFN.
The method of claim 1, wherein the first HFN is determined by the terminal device from received first configuration information.
The method of claim 2, wherein the first configuration information is carried in a first MCCH, the first MCCH being a control channel for MBMS traffic.
The method according to any one of claims 1 to 3, wherein the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information.
The method according to any of claims 1 to 4, wherein all PDCP PDUs received by the terminal device carry the HFN offset information, the second PDCP PDU belonging to one of the PDCP PDUs.
The method according to any one of claims 1 to 4, wherein the HFN offset information is carried by the first n PDCP PDUs after the first configuration information received by the terminal device, n being a positive integer, the second PDCP PDU belonging to one of the first n PDCP PDUs.
The method of any of claims 1-6, wherein the method further comprises:

the terminal equipment determines a second HFN based on the HFN offset information carried in the second PDCP PDU and the first HFN; the second HFN refers to an HFN to which a second SN corresponding to the second PDCP PDU belongs.
The method of claim 7, wherein the method further comprises:

the terminal equipment determines PDCP counting information based on the second HFN and a second SN corresponding to the second PDCP PDU, wherein the PDCP counting information is used for at least one of the following: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.
The method of claim 7 or 8, wherein the method further comprises:

and the terminal equipment maintains a third HFN according to a SN corresponding to a received third PDCP PDU, wherein the receiving time of the third PDCP PDU is later than that of the second PDCP PDU.
An information configuration method, the method comprising:

the method comprises the steps that terminal equipment receives a first PDCP PDU, wherein the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.
The method of claim 10, wherein all PDCP PDUs received by the terminal device carry HFN, and the first PDCP PDU belongs to one of the PDCP PDUs.
The method of claim 10 or 11, wherein the method further comprises:

the terminal equipment determines PDCP counting information based on the first HFN and a first SN corresponding to the first PDCP PDU, wherein the PDCP counting information is used for at least one of the following: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.
An information configuration method, the method comprising:

the network equipment sends a second PDCP PDU, wherein the second PDCP PDU carries HFN offset information, and the HFN offset information is used for indicating a difference value of an HFN to which a second SN corresponding to the second PDCP PDU belongs relative to a first HFN, wherein the first HFN is the HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.
The method of claim 13, wherein the method further comprises:

the network equipment sends first configuration information, and the first configuration information carries the first HFN.
The method of claim 14, wherein the first configuration information is carried in a first MCCH, the first MCCH being a control channel for MBMS traffic.
The method according to any one of claims 13 to 15, wherein the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information.
The method according to any of claims 13 to 16, wherein all PDCP PDUs transmitted by the network device carry the HFN offset information, the second PDCP PDU belonging to one of the all PDCP PDUs.
The method according to any of claims 13 to 16, wherein the HFN offset information is carried by the first n PDCP PDUs after the first configuration information sent by the network device, n being a positive integer, the second PDCP PDU belonging to one of the first n PDCP PDUs.
An information configuration method, the method comprising:

the network equipment sends a first PDCP PDU, wherein the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.
The method of claim 19, wherein all PDCP PDUs transmitted by the network device carry HFNs, and wherein the first PDCP PDU belongs to one of the all PDCP PDUs.
An information configuring apparatus, the apparatus comprising:

a receiving unit, configured to receive a second PDCP PDU, where the second PDCP PDU carries HFN offset information, and the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.
The apparatus of claim 21, wherein the first HFN is determined by the terminal device from received first configuration information.
The apparatus of claim 22, wherein the first configuration information is carried in a first MCCH, the first MCCH being a control channel for MBMS traffic.
The apparatus according to any of claims 21 to 23, wherein the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information.
The apparatus according to any of claims 21-24, wherein all PDCP PDUs received by the receiving unit carry the HFN offset information, the second PDCP PDU belonging to one of the all PDCP PDUs.
The apparatus according to any of claims 21-24, wherein the HFN offset information is carried by first n PDCP PDUs after the first configuration information received by the receiving unit, n being a positive integer, the second PDCP PDU belonging to one of the first n PDCP PDUs.
The apparatus of any one of claims 21 to 26, wherein the apparatus further comprises:

a determining unit, configured to determine a second HFN based on the HFN offset information carried in the second PDCP PDU and the first HFN; the second HFN refers to an HFN to which a second SN corresponding to the second PDCP PDU belongs.
The apparatus of claim 27, wherein the determining unit is further configured to determine PDCP count information based on the second HFN and a second SN corresponding to the second PDCP PDU, the PDCP count information being for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.
The apparatus of claim 27 or 28, wherein the apparatus further comprises:

and the maintenance unit is used for maintaining a third HFN according to a SN corresponding to a received third PDCP PDU, wherein the receiving time of the third PDCP PDU is later than the receiving time of the second PDCP PDU.
An information configuring apparatus, the apparatus comprising:

a receiving unit, configured to receive a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.
The apparatus of claim 30, wherein all PDCP PDUs received by the receiving unit carry HFNs, and the first PDCP PDU belongs to one of the all PDCP PDUs.
The apparatus of claim 30 or 31, wherein the apparatus further comprises:

a determining unit, configured to determine PDCP count information based on the first HFN and a first SN corresponding to the first PDCP PDU, where the PDCP count information is used for at least one of: deciphering the PDCP layer, verifying the integrity protection of the PDCP layer and maintaining a receiving window of the PDCP layer.
An information configuring apparatus, the apparatus comprising:

a sending unit, configured to send a second PDCP PDU, where the second PDCP PDU carries HFN offset information, and the HFN offset information is used to indicate a difference between an HFN to which a second SN corresponding to the second PDCP PDU belongs and a first HFN, where the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs or the first HFN is a reference HFN.
The apparatus of claim 33, wherein the means for transmitting is further configured to transmit first configuration information, the first configuration information carrying the first HFN.
The apparatus of claim 34, wherein the first configuration information is carried in a first MCCH, the first MCCH being a control channel for MBMS traffic.
The apparatus according to any one of claims 33 to 35, wherein the first PDCP PDU is a first PDCP PDU after a reception time of the first configuration information.
The apparatus according to any of claims 33-36, wherein all PDCP PDUs transmitted by the transmitting unit carry the HFN offset information, and the second PDCP PDU belongs to one of the all PDCP PDUs.
The apparatus according to any of claims 33-36, wherein the HFN offset information is carried by first n PDCP PDUs after the first configuration information sent by the sending unit, n is a positive integer, and the second PDCP PDU belongs to one of the first n PDCP PDUs.
An information configuring apparatus, the apparatus comprising:

a sending unit, configured to send a first PDCP PDU, where the first PDCP PDU carries a first HFN, and the first HFN is an HFN to which a first SN corresponding to the first PDCP PDU belongs.
The apparatus of claim 39, wherein all PDCP PDUs transmitted by the transmitting unit carry HFNs, and the first PDCP PDU belongs to one of the all PDCP PDUs.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 12.
A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 13 to 20.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 12.
A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 13 to 20.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 12.
A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 13 to 20.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 12.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 13 to 20.
A computer program for causing a computer to perform the method of any one of claims 1 to 12.
A computer program for causing a computer to perform the method of any one of claims 13 to 20.