CN117426126A

CN117426126A - Variable maintenance method and device and terminal equipment

Info

Publication number: CN117426126A
Application number: CN202180098994.3A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-09-29
Filing date: 2021-09-29
Publication date: 2024-01-19
Also published as: WO2023050185A1

Abstract

The embodiment of the application provides a variable maintenance method and device and terminal equipment, wherein the method comprises the following steps: the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring a first HFN and a first SN; the terminal equipment receives a first data packet and acquires a second SN of the first data packet; the terminal device determines a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN.

Description

Variable maintenance method and device and terminal equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a variable maintenance method and device and terminal equipment.

Background

In a New Radio (NR) system, a multicast broadcast service (Multicast Broadcast Service, MBS) service of a multicast type is supported. The terminal device receives the multicast type MBS service in a radio resource control (Radio Resource Control, RRC) connected state. The terminal device may receive the multicast MBS service in a Point-To-MultiPoint (PTM) manner or a Point-To-Point (PTP) manner.

For multicast type MBS services, the MBS service is addressed to all terminal equipments in a certain group. For such a scenario, how the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) reception-related variables of the terminal device side are maintained to ensure that the data packet can be normally received is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a variable maintenance method and device, terminal equipment, a chip, a computer readable storage medium, a computer program product and a computer program.

The method for maintaining the variable provided by the embodiment of the application comprises the following steps:

the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring a first Hyper Frame Number (HFN) and a first Serial Number (SN);

the terminal equipment receives a first data packet and acquires a second SN of the first data packet;

the terminal device determines a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN.

The variable maintenance device provided by the embodiment of the application is applied to terminal equipment, and comprises:

a receiving unit, configured to receive first configuration information sent by a network device, where the first configuration information is used to configure a first HFN and a first SN; receiving a first data packet and acquiring a second SN of the first data packet;

And the determining unit is used for determining a second HFN associated with the second SN based on the first SN, the second SN and the first HFN.

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the maintenance method of the variables.

The chip provided by the embodiment of the application is used for realizing the maintenance method of the variable.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the maintenance method of the variable.

The computer readable storage medium provided in the embodiments of the present application is used to store a computer program, where the computer program makes a computer execute the above-mentioned maintenance method of variables.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the method for maintaining the variable.

The computer program provided in the embodiments of the present application, when executed on a computer, causes the computer to execute the above-described maintenance method for variables.

Through the technical scheme, the network equipment configures the first HFN and the first SN for the terminal equipment; after receiving the first data packet, the terminal equipment acquires a second SN of the first data packet; the terminal device determines a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN. In this way, it is clear how the terminal device maintains variables (i.e., HFN and SN) related to PDCP reception, so as to provide a guarantee for the terminal device to normally receive the data packet, so that the loss of the data packet is as small as possible, and the transmission reliability of the data packet is improved.

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 embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

fig. 2 is a schematic diagram of a protocol stack corresponding to a PTM mode and a PTP mode in the embodiment of the present application;

fig. 3 is a schematic diagram of MBS service transmission according to PTM mode and PTP mode provided in the embodiment of the present application;

fig. 4 is a schematic diagram of the value of a variable associated with a PDCP receive window according to an embodiment of the present application;

Fig. 5 is a schematic diagram of an HFN in which step-out occurs according to an embodiment of the present application;

FIG. 6 is a flow chart of a method for maintaining variables provided by an embodiment of the present application;

fig. 7 is a schematic diagram one of HFN indication provided in an embodiment of the present application;

fig. 8 is a schematic diagram two of HFN indication provided in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a variable maintenance device provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG. 11 is a schematic block diagram of a chip of an embodiment of the present application;

fig. 12 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that the present embodiments are illustrated by way of example only with respect to communication system 100, but the present embodiments are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 may be any terminal device including, but not limited to, a terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may 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 (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example a session management function+a data gateway (Session Management Function + Core Packet Gateway, smf+pgw-C) device of the core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form a new network entity by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited in the embodiment of the present application.

It should be noted that fig. 1 illustrates, by way of example, a system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, reference to "indication" may be a direct indication, an indirect indication, or an indication that there is an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that, in the embodiments of the present application, reference to "corresponding" may mean that there is a direct correspondence or an indirect correspondence between the two, or may mean that there is an association between the two, or may be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (e.g., including terminal devices and network devices), and the present application is not limited to a specific implementation thereof. Such as predefined may refer to what is defined in the protocol. It should also be understood that, in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

With the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life business, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

At early deployment of NRs, full NR coverage is difficult to acquire, so typical network coverage is wide area LTE coverage and island coverage mode of NRs. And a large amount of LTE is deployed below 6GHz, and the frequency spectrum below 6GHz which can be used for 5G is few. NR must study spectral applications above 6GHz while high-band coverage is limited and signal fading is fast. Meanwhile, in order to protect the mobile operators from early investment in LTE, a working mode of tight coupling (tight interworking) between LTE and NR is proposed.

RRC state

5G for the purposes of reducing air interface signaling and fast recovery of radio connections, fast recovery of data traffic, a new radio resource control (Radio Resource Control, RRC) state, namely an RRC INACTIVE (RRC_INACTIVE) state, is defined. This state is different from the RRC IDLE (rrc_idle) state and the RRC ACTIVE (rrc_active) state. Wherein,

1) Rrc_idle state (simply referred to as IDLE state): mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and paging areas are 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 UE contexts on the base station side and UE side. The network side knows that the location of the UE is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the UE and the base station.

3) Rrc_inactive state (simply referred to as INACTIVE state): mobility is cell selection reselection based on UE, there is a connection between CN-NRs, UE context exists on a certain base station, paging is triggered by RAN, paging area based on RAN is managed by RAN, network side knows UE location is based on paging area level of RAN.

Multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, MBMS)

MBMS is a technology for transmitting data from one data source to a plurality of terminal equipments through a shared network resource, which can effectively utilize the network resource while providing a multimedia service, and realize broadcasting and multicasting of a multimedia service of a higher rate (e.g., 256 kbps).

Due to the low MBMS spectrum efficiency, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In LTE, 3GPP has therefore explicitly proposed to enhance the support capability for the downlink high speed MBMS service and to determine the design requirements for the physical layer and the air interface.

The 3gpp R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. a multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MBSFN), wherein the MBSFN uses a unified frequency to simultaneously transmit traffic data in all cells, but synchronization between the cells is guaranteed. The method can greatly improve the overall signal-to-noise ratio distribution 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 protocols.

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 terminal devices in an idle state or a connected state.

A single cell point-to-multipoint (Single Cell Point To Multiploint, SC-PTM) concept is introduced in 3gpp r13, SC-PTM being based on the MBMS network architecture.

MBMS introduces new logical channels including Single Cell multicast control channel (SC-MCCH) and Single Cell multicast transport channel (SC-MTCH) and Single Cell-Multicast Transport Channel. The SC-MCCH and SC-MTCH are mapped onto a Downlink-Shared Channel (DL-SCH), and further, the DL-SCH is mapped onto a physical Downlink Shared Channel (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 (Hybrid Automatic Repeat reQuest, HARQ) operation.

MBMS introduces a new system information block (System Information Block, SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the 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, the radio frame and subframe for scheduling the SC-MCCH and other information. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m=0, where SFN represents a system frame number of the boundary, and m is a modification period (i.e., SC-MCCH-modification period) of the SC-MCCH configured in SIB20. 2) The radio frame of the scheduling SC-MCCH meets the following conditions: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents the system frame number of the radio frame, MCCH-repetition period represents the repetition period of the SC-MCCH, and MCCH-Offset represents the Offset of the SC-MCCH. 3) The subframes of the scheduling SC-MCCH are indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a physical downlink control channel (Physical Downlink Control Channel, PDCCH). In one aspect, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), i.e., single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling the SC-MCCH, optionally with the SC-RNTI fixed value FFFC. On the other hand, a new RNTI, i.e., a single cell notification RNTI (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, optionally, the SC-N-RNTI is fixed to a value of FFFB; further, the change notification may be indicated with one bit of 8 bits (bits) of DCI 1C. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., scptm configuration) for configuring configuration information of the SC-PTM. The configuration information of the SC-PTM comprises: temporary mobile Group identity (Temporary Mobile Group Identity, TMGI), session identity (session id), group RNTI (G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information, SC-PTM service information of neighbor cells, and the like. Note that SC-PTM in R13 does not support the robust header compression (Robust Header Compression, ROHC) function.

The downlink discontinuous reception of the SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-scheduling cycle, and SC-MTCH-scheduling offset.

When [ (SFN 10) +subframe number ] module (SC-MTCH-scheduling cycle) =sc-MTCH-scheduling offset is satisfied, a timer ondurationtimerscpm is started;

when receiving downlink PDCCH scheduling, starting a timer drx-InactivityTimerSCPTM;

the downstream SC-PTM service is received only when the timer onduration timerscpm or drx-incaactyitimerscpm is running.

The SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely a mode of SIB15 and MBMSInterestindication. The traffic continuity of the terminal device in idle state is based on the concept of frequency priority.

Although the above-described scheme is described by taking the MBMS service as an example, the technical scheme of the embodiment of the present application is not limited thereto. The embodiment of the application is described by taking an MBS service as an example, and the description of the "MBS service" may be replaced by the "MBMS service".

In NR systems, many scenarios require support of multicast type and broadcast type traffic demands, such as in the internet of vehicles, industrial internet, etc. It is necessary to introduce multicast type and broadcast type MBS services in the NR. It should be noted that, the multicast type MBS service refers to an MBS service transmitted through a multicast manner. The broadcast type MBS service refers to an MBS service transmitted through a broadcast manner.

In the NR system, for the multicast type MBS service, the MBS service is addressed to all terminal equipments in a certain group. The terminal equipment receives the multicast MBS service in the RRC connection state, and the terminal equipment can receive the multicast MBS service data in the PTM mode or the PTP mode. Referring to fig. 2, the MBS service data of the ptm mode scrambles corresponding scheduling information through a G-RNTI configured by a network side, and the MBS service data of the PTP mode scrambles corresponding scheduling information through a C-RNTI.

For multicast type MBS service, after receiving the MBS service issued by the core network from the shared tunnel (tunnel), the base station may issue the MSB service to all terminal devices in a group through an air interface. Here, the base station may issue MSB service to all terminal devices in a group in PTP and/or PTM. For example: a group comprises a terminal device 1, a terminal device 2 and a terminal device 3, wherein the base station can issue MBS service to the terminal device 1 in a PTP mode, issue MBS service to the terminal device 2 in a PTP mode, and issue MBS service to the terminal device 3 in a PTP mode; or the base station can issue MBS business to the terminal equipment 1 in a PTP mode, and issue MBS business to the terminal equipment 2 and the terminal equipment 3 in a PTM mode; or, the base station may send the MBS service to the terminal device 1, the terminal device 2 and the terminal device 3 in the PTM mode. Referring to fig. 3, a shared GTP tunnel (Shared GTP tunnel) is used between the core network and the base station to transmit MBS services, i.e., both PTM-mode MBS services and PTP-mode MBS services are shared with the GTP tunnel. The base station transmits MBS service data to the UE1 and the UE2 according to the PTM mode, and transmits MBS service data to the UE3 according to the PTP mode.

Receiving window-associated variables

For multicast-type MBS services, especially for PTM-mode multicast-type MBS services, a plurality of terminal equipments in the MBS group all receive the MBS service. The terminal device needs to be different for maintenance of a variable associated with a receiving window (simply referred to as a receiving window variable), for example, MBS service and unicast service: the initial value of the receive window variable of the MBS service is different from the initial value of the receive window variable of the unicast service.

For the PDCP entity, the corresponding reception window is referred to as a PDCP reception window, and variables associated with the PDCP reception window mainly include: RX_NEXT and RX_DELIV. In some implementations, the initial values of RX_NEXT and RX_DELIV are 0, as in FIG. 4.

Rx_next is used to indicate a first COUNT (COUNT) value, which refers to the COUNT value associated with the NEXT packet that is expected to be received; RX_DELIV is used to indicate a second COUNT value, which refers to the COUNT value associated with the first packet that is not delivered to the upper layer. Here, the data packet refers to PDCP SDUs.

Here, the COUNT value is a numerical value of N bits, N being a positive integer, n=32 as an example. The COUNT value consists of two parts, a Hyper Frame Number (HFN) and a Sequence Number (SN), respectively, where the HFN has a bit length=the bit length of N-SN. It should be noted that the COUNT value is not transmitted on the channel, and the COUNT value is maintained by the terminal device, that is, the HFN and SN in the COUNT value are maintained by the terminal device. Each data packet is associated with a COUNT value, wherein, for the SN portion in the COUNT value, the initial value may be set to the SN of the first data packet received; for the HFN part in the COUNT value, its initial value may be indicated by the network side.

However, when the network side indicates HFN, the network side may occur on the HFN rollover boundary, as shown in fig. 5, and when the network device sends hfn=n indication information to the terminal device; then, the HFN is flipped, i.e. a new SN cycle starts, and the terminal device receives the indication information of hfn=n when hfn=n+1, however, the HFN is out of sync, which results in that the data packet received by the terminal device is associated with an erroneous HFN. For this reason, an entirely new scheme needs to be proposed to maintain PDCP reception related variables.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

Fig. 6 is a flow chart of a method for maintaining a variable according to an embodiment of the present application, as shown in fig. 6, where the method for maintaining a variable includes the following steps:

step 601: the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring the first HFN and the first SN.

Step 602: and the terminal equipment receives the first data packet and acquires the second SN of the first data packet.

Step 603: the terminal device determines a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN.

In the embodiment of the application, the network device configures one HFN (referred to as a first HFN) and one SN (referred to as a first SN) for the terminal device through the first configuration information.

In some alternative embodiments, the network device may be a base station.

In some alternative embodiments, the first configuration information is carried in RRC signaling.

In some alternative embodiments, the first configuration information is for PDCP reception. Specifically, the terminal device determines a variable (such as HFN, SN) related to PDCP reception based on the first configuration information, and further correctly receives the data packet according to the variable.

In some alternative embodiments, the first SN is the SN of the next packet corresponding to when the first HFN is configured.

In this embodiment of the present application, after obtaining the first configuration information, the terminal device receives the first data packet, and obtains the second SN of the first data packet. Here, the second SN is carried in a header of the first data packet. The terminal device obtains an SN (called a second SN) from the header of the first data packet.

In some optional embodiments, the first data packet is a first data packet received by the terminal device after obtaining the first configuration information.

In this embodiment of the present application, the terminal device may determine the second HFN associated with the second SN (i.e. the HFN associated with the first data packet) by:

if the second SN is greater than or equal to the first SN, the terminal equipment determines that the second HFN associated with the second SN is equal to the first HFN; or,

if the second SN is smaller than the first SN, the terminal equipment determines that the second HFN associated with the second SN is equal to the first HFN plus 1.

As an example: the first SN is denoted as SN1, the second SN is denoted as SN2, the first HFN is denoted as HFN1, and the second HFN is denoted as HFN2, then if SN2 is greater than or equal to SN1, hfn2=hfn1; hgn2=hfn1+1 if SN2 is smaller than SN 1.

As shown in fig. 7, the network device indicates hfn=n, sn=m to the terminal device; the terminal device receives sn=1 of the first packet, and since 1 < M, hfn=n+1 associated with the first packet, i.e. sn=1 associated with hfn=n+1.

As shown in fig. 8, the network device indicates hfn=n, sn=m to the terminal device; the terminal device receives sn=m+1 of the first packet, and since m+1 > M, hfn=n associated with the first packet, i.e. sn=m+1.

In some optional embodiments, the terminal receives second configuration information sent by the network device, where the second configuration information is used to configure the first timer; the terminal equipment starts the first timer after obtaining the configuration of the first timer and/or the configuration of the first HFN; if the terminal device does not receive the first data packet before the first timer times out, the terminal device determines that the configuration of the first HFN is invalid; and if the terminal equipment receives the first data packet before the first timer is overtime, the terminal equipment determines that the configuration of the first HFN is valid.

In some alternative embodiments, the second configuration information is carried in radio resource control RRC signaling.

As an example: the terminal receives an RRC signaling sent by the network device, wherein the RRC signaling is used for configuring a first timer (for example, the duration of the first timer); the terminal equipment starts the first timer after obtaining the configuration of the first timer and/or the configuration of the first HFN; if the terminal equipment does not receive the first data packet before the first timer is overtime, the terminal equipment determines that the configuration of the first HFN is invalid; and if the terminal equipment receives a first data packet before the first timer is overtime, the terminal equipment determines that the configuration of the first HFN is valid.

Further, in some optional embodiments, if the terminal device determines that the configuration of the first HFN is invalid, the terminal device sends a first request message to the network device, where the first request message is used to indicate at least one of: the HFN configured by the network device is invalid; the invalid HFN configured by the network device is the first HFN. Further, the first request message is further configured to request the network device to configure a new HFN. The network device further configures a new HFN after receiving the first request message, the new HFN being different from the previously configured HFN (i.e., the first HFN). Optionally, after receiving the first request message, the network device configures a new SN in addition to the new HFN, where the new SN may be the same as or different from the SN previously configured (i.e., the first SN). Furthermore, optionally, after the network device configures the new HFN and the new SN, a new timer may also be configured.

In the above scheme, the COUNT value associated with the first data packet is determined based on the second HFN and the second SN. And the terminal equipment correctly receives the first data based on the COUNT value associated with the first data packet.

The technical scheme of the embodiment of the application specifies how to avoid the problem of asynchronous HFN in the receiving of the multicast MBS service, and ensures the receiving reliability of the MBS service.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described in detail. As another example, any combination of the various embodiments of the present application may be made, as long as it does not depart from the spirit of the present application, which should also be construed as being disclosed herein. For example, the various embodiments and/or technical features of the various embodiments described herein may be combined with any other of the prior art without conflict, and the combined technical solutions should also fall within the scope of protection of the present application.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application. Further, in the embodiment of the present application, the terms "downstream", "upstream" and "sidestream" are used to indicate a transmission direction of signals or data, where "downstream" is used to indicate that the transmission direction of signals or data is a first direction from a station to a user equipment of a cell, "upstream" is used to indicate that the transmission direction of signals or data is a second direction from the user equipment of the cell to the station, and "sidestream" is used to indicate that the transmission direction of signals or data is a third direction from the user equipment 1 to the user equipment 2. For example, "downstream signal" means that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and/or" is merely an association relationship describing the association object, which means that three relationships may exist. Specifically, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 9 is a schematic structural diagram of a variable maintenance device provided in an embodiment of the present application, which is applied to a terminal device, as shown in fig. 9, where the variable maintenance device includes:

a receiving unit 901, configured to receive first configuration information sent by a network device, where the first configuration information is used to configure a first HFN and a first SN; receiving a first data packet and acquiring a second SN of the first data packet;

a determining unit 902, configured to determine a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN.

In some optional embodiments, the determining unit 902 is configured to determine that the second HFN associated with the second SN is equal to the first HFN if the second SN is greater than or equal to the first SN; or if the second SN is smaller than the first SN, determining that the second HFN associated with the second SN is equal to the first HFN plus 1.

In some alternative embodiments, the second SN is carried in a header of the first data packet.

In some optional embodiments, the receiving unit 901 is further configured to receive second configuration information sent by the network device, where the second configuration information is used to configure the first timer;

the apparatus further comprises: a starting unit, configured to start the first timer after obtaining the configuration of the first timer and/or the configuration of the first HFN;

if the receiving unit 901 does not receive the first data packet before the first timer expires, the determining unit 902 determines that the configuration of the first HFN is invalid;

if the receiving unit 901 receives the first data packet before the first timer expires, the determining unit 902 determines that the configuration of the first HFN is valid.

In some alternative embodiments, the apparatus further comprises:

a sending unit 903, configured to send a first request message to the network device if it is determined that the configuration of the first HFN is invalid, where the first request message is used to indicate at least one of:

the HFN configured by the network device is invalid;

the invalid HFN configured by the network device is the first HFN.

In some alternative embodiments, the first request message is further used to request the network device to configure a new HFN.

In some alternative embodiments, the second configuration information is carried in RRC signaling.

In some alternative embodiments, the COUNT value associated with the first data packet is determined based on the second HFN and the second SN.

In some alternative embodiments, the first configuration information is for PDCP reception.

It should be understood by those skilled in the art that the description of the maintenance device for a variable according to the embodiment of the present application may be understood with reference to the description of the maintenance method for a variable according to the embodiment of the present application.

Fig. 10 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 1000 shown in fig. 10 comprises a processor 1010, from which the processor 1010 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 10, the communication device 1000 may also include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

Optionally, as shown in fig. 10, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices.

The transceiver 1030 may include, among other things, a transmitter and a receiver. The transceiver 1030 may further include an antenna, the number of which may be one or more.

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

Optionally, the communication device 1000 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 1000 may implement corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

Fig. 11 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1100 shown in fig. 11 includes a processor 1110, and the processor 1110 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 11, the chip 1100 may also include a memory 1120. Wherein the processor 1110 may call and run a computer program from the memory 1120 to implement the methods in embodiments of the present application.

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

Optionally, the chip 1100 may also include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 1100 may also include an output interface 1140. Wherein the processor 1110 may control the output interface 1140 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Fig. 12 is a schematic block diagram of a communication system 1200 provided in an embodiment of the present application. As shown in fig. 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.

The terminal device 1210 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1220 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks 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 a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct 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 memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein 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 a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

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

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely 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 think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to 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

A method of maintaining a variable, the method comprising:

the method comprises the steps that a terminal device receives first configuration information sent by a network device, wherein the first configuration information is used for configuring a first hyper frame number HFN and a first serial number SN;

the terminal equipment receives a first data packet and acquires a second SN of the first data packet;

the terminal device determines a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN.
The method of claim 1, wherein the terminal device determining a second HFN associated with the second SN based on the first SN, the second SN, and the first HFN comprises:

if the second SN is greater than or equal to the first SN, the terminal equipment determines that the second HFN associated with the second SN is equal to the first HFN; or,

If the second SN is smaller than the first SN, the terminal equipment determines that the second HFN associated with the second SN is equal to the first HFN plus 1.
The method according to claim 1 or 2, wherein the first SN is the SN of the corresponding next packet when the first HFN is configured.
A method according to any of claims 1 to 3, wherein the second SN is carried in a header of the first data packet.
The method according to any one of claims 1 to 4, wherein the first data packet is a first data packet received by the terminal device after obtaining the first configuration information.
The method of any one of claims 1 to 5, wherein the method further comprises:

the terminal receives second configuration information sent by the network equipment, wherein the second configuration information is used for configuring a first timer;

the terminal equipment starts the first timer after obtaining the configuration of the first timer and/or the configuration of the first HFN;

if the terminal device does not receive the first data packet before the first timer times out, the terminal device determines that the configuration of the first HFN is invalid;

And if the terminal equipment receives the first data packet before the first timer is overtime, the terminal equipment determines that the configuration of the first HFN is valid.
The method of claim 6, wherein the method further comprises:

if the terminal device determines that the configuration of the first HFN is invalid, the terminal device sends a first request message to the network device, where the first request message is used to indicate at least one of:

the HFN configured by the network device is invalid;

the invalid HFN configured by the network device is the first HFN.
The method of claim 7, wherein the first request message is further for requesting the network device to configure a new HFN.
The method according to any of claims 6 to 8, wherein the second configuration information is carried in radio resource control, RRC, signaling.
The method according to any of claims 1 to 9, wherein the first configuration information is carried in RRC signaling.
The method of any of claims 1-10, wherein the first packet associated COUNT value is determined based on the second HFN and the second SN.
The method according to any of claims 1 to 11, wherein the first configuration information is for packet data convergence protocol, PDCP, reception.
A maintenance device for a variable, applied to a terminal device, the device comprising:

a receiving unit, configured to receive first configuration information sent by a network device, where the first configuration information is used to configure a first HFN and a first SN; receiving a first data packet and acquiring a second SN of the first data packet;

and the determining unit is used for determining a second HFN associated with the second SN based on the first SN, the second SN and the first HFN.
The apparatus of claim 13, wherein the means for determining determines that a second HFN associated with the second SN is equal to the first HFN if the second SN is greater than or equal to the first SN; or if the second SN is smaller than the first SN, determining that the second HFN associated with the second SN is equal to the first HFN plus 1.
The apparatus of claim 13 or 14, wherein the first SN is a SN of a corresponding next packet when the first HFN is configured.
The apparatus of any of claims 13-15, wherein the second SN is carried in a header of the first data packet.
The apparatus according to any one of claims 13 to 16, wherein the first data packet is a first data packet received by the terminal device after obtaining the first configuration information.
The device according to any one of claims 13 to 17, wherein,

the receiving unit is further configured to receive second configuration information sent by the network device, where the second configuration information is used to configure the first timer;

the apparatus further comprises: a starting unit, configured to start the first timer after obtaining the configuration of the first timer and/or the configuration of the first HFN;

if the receiving unit does not receive the first data packet before the first timer times out, the determining unit determines that the configuration of the first HFN is invalid;

and if the receiving unit receives the first data packet before the first timer times out, the determining unit determines that the configuration of the first HFN is valid.
The apparatus of claim 18, wherein the apparatus further comprises:

a sending unit, configured to send a first request message to the network device if it is determined that the configuration of the first HFN is invalid, where the first request message is used to indicate at least one of:

The HFN configured by the network device is invalid;

the invalid HFN configured by the network device is the first HFN.
The apparatus of claim 19, wherein the first request message is further for requesting the network device to configure a new HFN.
The apparatus of any of claims 18 to 20, wherein the second configuration information is carried in RRC signaling.
The apparatus of any of claims 13 to 21, wherein the first configuration information is carried in RRC signaling.
The apparatus of any of claims 13-22, wherein the first packet associated COUNT value is determined based on the second HFN and the second SN.
The apparatus of any of claims 13-23, wherein the first configuration information is for PDCP reception.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 12.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted 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 1 to 12.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 12.
A computer program which causes a computer to perform the method of any one of claims 1 to 12.