CN116017738A

CN116017738A - Method and apparatus for wireless communication

Info

Publication number: CN116017738A
Application number: CN202211600756.0A
Authority: CN
Inventors: 苏怀文
Original assignee: Zeku Technology Beijing Corp Ltd
Current assignee: Zeku Technology Beijing Corp Ltd
Priority date: 2022-12-12
Filing date: 2022-12-12
Publication date: 2023-04-25

Abstract

The application provides a wireless communication method and device, wherein a downlink data packet processing mode based on CB granularity is introduced into L2, so that the memory space occupied by cache data can be reduced, the load of a system for accessing a memory can be reduced, the data packet processing process can be accelerated, and the data packet processing time delay can be reduced. The method of wireless communication includes: receiving a first CB data packet; decoding the first CB data packet to obtain at least one CB data packet descriptor; updating the state variable of the target window or discarding the first CB data packet according to the LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

Description

Method and apparatus for wireless communication

Technical Field

The present invention relates to the field of communications, and more particularly, to a method and apparatus for wireless communications.

Background

At this stage, downstream packets are processed at layer 2 (L2) based on transport block (Transmission Block, TB) granularity. Specifically, the downlink packet processing manner based on TB granularity has the following problems: the medium access control (Media Access Control, MAC) layer must buffer the entire TB before processing the medium access control protocol data units (Media Access Control Protocol Data Unit, MAC PDU), occupies a large memory space, and has a large processing delay; on the other hand, if there are high reliability low latency communication (Ultra-Reliable and Low Latency Communication, URLLC) packets in the TB and the latency requirement is less than one transmission time interval (Transmission Time Interval, TTI), processing based on the TB granularity will not meet the transmission requirement of such downstream packets.

Disclosure of Invention

The application provides a wireless communication method and device, wherein a downlink data packet processing mode based on CB granularity is introduced into L2, so that the memory space occupied by cache data can be reduced, the load of a system for accessing a memory can be reduced, the data packet processing process can be accelerated, and the data packet processing time delay can be reduced.

In a first aspect, a method of wireless communication is provided, comprising:

receiving a first CB data packet;

decoding the first CB data packet to obtain at least one CB data packet descriptor;

updating the state variable of the target window or discarding the first CB data packet according to the LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

In a second aspect, there is provided an apparatus for wireless communication, comprising:

a communication unit, configured to receive a first coded block CB packet;

the processing unit is used for decoding the first CB data packet to obtain at least one CB data packet descriptor;

the processing unit is further configured to update a state variable of the target window or discard the first CB packet according to a logical channel identifier LCID corresponding to the first CB packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

In a third aspect, there is provided a communication device comprising: a transceiver and a processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the transceiver is configured to: receiving a first coded block CB data packet;

the processor is configured to: decoding the first CB data packet to obtain at least one CB data packet descriptor; updating the state variable of the target window or discarding the first CB data packet according to the logic channel identifier LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

In a fourth aspect, a communication device is provided for performing the method of the first aspect or implementations thereof.

In particular, the communication device comprises functional modules for performing the method of the first aspect described above or in various implementations thereof.

In a fifth aspect, a communication device is provided, comprising a processor and a memory; wherein the memory is configured to store a computer program, and the processor is configured to invoke and execute the computer program stored in the memory, to perform the method according to the first aspect or each implementation manner thereof.

In a sixth aspect, there is provided an apparatus for implementing the method of the first aspect or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in the first aspect or implementations thereof described above.

In a seventh aspect, a chip is provided for implementing the method in the first aspect or each implementation manner thereof.

Specifically, the chip includes: 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 as in the first aspect or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, where the computer program causes a computer to execute the method in the first aspect or each implementation manner thereof.

By the technical scheme, a downlink data packet processing mode based on CB granularity is introduced into L2, so that the memory space occupied by cache data can be reduced, the load of a system for accessing a memory can be reduced, the data packet processing process can be accelerated, and the data packet processing time delay can be reduced.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of a packet processing architecture based on TB granularity provided herein.

Fig. 3 is a schematic diagram of a packet processing architecture based on CB granularity according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of a method of wireless communication provided in accordance with an embodiment of the present application.

Fig. 5 is a schematic flow chart of a packet processing based on CB granularity according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a SSCL provided in accordance with an embodiment of the present application.

Fig. 7 is a schematic diagram of an RSCL provided in accordance with an embodiment of the present application.

Fig. 8 is a schematic block diagram of a device for wireless communication provided in accordance with an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of an apparatus provided in accordance with an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication system provided according to 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 for the embodiments herein, are intended to be within the scope of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio, NR system evolution system, LTE over unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR over unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile telecommunication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Exemplary, a communication system 100 to which embodiments of the present application apply 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 device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment 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 device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are 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 be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having 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.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited. Such as predefined may refer to what is defined in the protocol.

In this embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in this application.

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 following 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.

With the development of mobile communication, data throughput is rapidly increasing. In The downstream direction, data rates can reach maximum rates in excess of 10Gbps with delays reduced to below 1ms, as defined by The third generation partnership project (The 3rd Generation Partnership Project,3GPP). The manner in which layer 2 (L2) initiates downstream packet processing is triggered by Transport Block (TB) granularity packets submitted by the physical layer during the transmission time interval (Transmission Time Interval, TTI). Based on the packet processing mode of the TB granularity, on one hand, the MAC layer must buffer the entire TB before processing the MAC PDU; on the other hand, if there are ultra-reliable low latency communication (URLLC) packets in the TB and the latency requirement is less than one TTI, the TB-based process will not meet such requirements.

The data packet processing mode based on the TB granularity has poor real-time performance and is not optimal in space utilization. In NR system, in case of sub-carrier interval of 15khz and TTI of 1ms, the maximum TB size may exceed 10 when the data rate reaches 10Gbps ⁷ Bits. In practice, the TB is divided into a number of smaller-sized Code Blocks (CBs) (N _cb Typical value is 132), the 24-bit CB-level cyclic redundancy check (Cyclical Redundancy Check, CRC) has an error rate (CB) comparable to the TB CRC _err ). Even if CB error detects miss rate (CB _err-TB The probability that no TB error is detected) may rise, but by special design it can be controlled to a level that does not negatively affect the performance of higher layer protocols.

A packet processing architecture based on TB granularity may be as shown in fig. 2. In the TB process, a complete TB block is sent to L2, and L2 first decodes the MAC layer header, and when there is a complete MAC sub-PDU, the MAC sub-PDU is further decoded by a radio link control (Radio Link Control, RLC) header decoder. If the protocol data unit (Protocol Data Unit, PDU) length is long enough to contain a complete RLC PDU, it will be further decoded by a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) header decoder. When the L2 header decoder completes its work, a packet descriptor containing header information and the packet payload source address will be formed. The packet descriptors will be passed to the RLC window checker to identify packets that duplicate or exceed the window, and if the packet passes the RLC window check, the RLC window state variables will be updated. The PDCP count is then derived and decryption is performed in the next step. Finally, if the PDU is located in the PDCP window and is not repeated, the PDCP window state variable is updated.

In decryption, the security engine reads the payload from the source address in the packet descriptor and outputs the decrypted data to a buffer that layer 3 (layer 3, L3) can read. If integrity verification is configured, the output result also includes a message verification code (e.g., X-MAC) that is to be compared to a message verification code (e.g., integrity verification code (MAC-I)) in the PDCP PDU. If the X-MAC matches the MAC-I, the data packet will be handed over to L3 for further processing through integrity verification. In TB mode, L3 transmission control protocol (Transfer Control Protocol, TCP)/internet protocol (Internet Protocol, IP) packet checksum verification may be performed on L2 or L3.

The downlink packet processing method based on TB granularity has the following problems: the MAC layer must buffer the whole TB before processing the MAC PDU, occupy larger memory space, and processing delay is larger; on the other hand, if there is a URLLC packet in the TB and the latency requirement is less than one TTI, the TB granularity based processing will not meet the transmission requirement of such downstream packets.

Based on the above-mentioned problems, the present application proposes a CB granularity-based L2 end-to-end packet processing scheme, and the CB granularity-based downstream packet processing can first reduce the buffer area allocated to the storage packet (e.g. a TB packet is divided into N _cb A CB data packet, the buffer area to be allocated for one CB data packet is 1/N _cb TB buffers), and more importantly, the CB granularity data processing mode has a smaller data processing granularity than the TB granularity data processing mode, which is advantageous for reducing burst access of data, thereby balancing the load of system access to memory. The peak value of Double Data Rate (DDR) access bandwidth is averaged, and the processing delay is reduced to 1/N of the TB processing _cb . Thus, CB granularity processing facilitates power saving and reduced chip memory area while also not introducing performance degradation. When there are multiple MAC sub-PDUs (and multiple RLC PDUs and PDCP PDUs) in the TB, the downlink packet handling approach based on CB granularity also helps to reduce on-chip memory usage for storing packet descriptors, which may typically be hundreds.

In some embodiments, a packet processing architecture based on CB granularity may be as shown in fig. 3. When the TB is changed to CB, a new functional component, i.e., CB manager, is introduced, compared to the TB mode-based packet processing architecture shown in fig. 2, the CB manager may be located in the physical layer. The CB manager functions to ensure that CB packets submitted to layer 2 (L2) are ordered in sequence. When L2 receives the sequence When a CB packet (i.e., CB CRC check passes), the CB packet will immediately trigger L2 processing, similar to receipt of a complete TB. L2 will attempt to decode the CB packet to obtain at least one CB packet descriptor, wherein the CB packet descriptor comprises header information and a CB packet payload source address. The CB packet will go through RLC window inspection but the RLC window state variables will not be updated immediately with the new sequence numbers and then the CB packet descriptors are fed into the security policy component logic (Security Strategy Component Logic, SSCL). Various security policies are checked in the SSCL so that at this stage it can be partly identified whether the CB packet is correct. Even if the packet is correct, care must be taken because of the CB _err May be greater than the packet error rate (Packet Error Rate, PER) of the operator service. This, in turn, therefore involves a new component named reliability policy component logic (Reliability Strategy Component Logic, RSCL) that defines the policy to submit the current CB packet to the upper layers. After all the checks are passed on the CB packet, the RLC window state variable or PDCP window state variable may be eventually updated based on the Sequence Number (SN) in the CB packet descriptor. Updating the RLC window state variable if the at least one CB packet descriptor contains an RLC header; alternatively, in case that the PDCP header is included in the at least one CB packet descriptor, the PDCP window state variable is updated.

In the packet processing based on the TB granularity, a low density parity check code (Low Density Parity Check Code, LDPC)/TURBO decoder transmits a MAC TB to L2 processing. In packet processing based on CB granularity, MAC PDUs are dynamically processed by the CB. The difference between these two granularity processes is that CB granularity processing will increase latency performance, save more on-chip memory, while TB granularity processing will force TURBO/LDPC decoders to store MAC TBs to DDR (meaning cost is large if TBs are stored to on-chip memory) before delivery to L2 processing, and twice the DDR read/write (R/W) consumption.

CB granularity processing is the best choice from a system design perspective. In CB-level design, one problem is that CB CRC is 24 bits, and the reliability of CB CRC is weak, so that it is possible that CB CRC may be correct, but the contents of CB are actually wrong (i.e., the final TB CRC is failed), and thus RSCL enhancement reliability is required.

Fig. 4 is a schematic flow chart of a method 200 of wireless communication according to an embodiment of the present application, as shown in fig. 4, the method 200 of wireless communication may include, but is not limited to, the following:

s210, receiving a first CB data packet;

S220, decoding the first CB data packet to obtain at least one CB data packet descriptor;

s230, updating the state variable of the target window or discarding the first CB data packet according to the LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

In the embodiment of the present application, the method 200 for wireless communication may be applied to a device for receiving and processing CB data packets, or a terminal device integrated with the device; alternatively, the method 200 of wireless communication may be applied to a layer 2 entity, or a terminal device integrated with the layer 2 entity. That is, the execution body of the embodiment of the present application may be a terminal device, and the terminal device includes at least an RLC layer and a PDCP layer.

The method 200 of performing wireless communication by a layer 2 entity is described below as an example.

In the embodiment of the application, in the packet processing based on the CB granularity, the terminal equipment does not wait for the TB CRC to pre-process the CB packet, so that the memory space occupied by cache data can be reduced, the load of a system for accessing a memory can be reduced, the packet processing process can be accelerated, and the packet processing time delay can be reduced.

In some embodiments, in S210, the first CB packet may be received from a CB manager. Specifically, the CB manager may be deployed at the physical layer and may ensure that CB packets submitted to layer 2 are ordered. For example, a TB may split into a plurality of CB packets, and the CB manager may examine the ordering of the plurality of CB packets to ensure that the CB packets submitted to layer 2 are in order.

In some embodiments, a CB packet descriptor in the at least one CB packet descriptor may comprise header information and a CB packet payload source address.

After the PDU session is established, a logical channel identifier (Logical Channel Identity, LCID) corresponding to the downlink packet transmitted in the PDU session may be determined.

In some embodiments, the target window is one of: RLC window, PDCP window.

In some embodiments, the target window is an RLC window in the event that the at least one CB packet descriptor contains an RLC header.

In some embodiments, the target window is a PDCP window in the event that the PDCP header is included in the at least one CB packet descriptor.

In some embodiments, the at least one CB packet descriptor is discarded or deleted after discarding the first CB packet.

In some embodiments, the step S230 may specifically include:

and discarding the first CB data packet under the condition that the LCID corresponding to the first CB data packet is not matched with the LCID stored locally.

That is, in packet processing based on CB granularity, it is necessary to ensure that LCID is correct.

In some embodiments, the step S230 may specifically include:

Storing the at least one CB data packet descriptor under the condition that LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that MAC CE exists after the LCID corresponding to the first CB data packet, and updating the state variable of the target window if the TB CRC corresponding to the first CB data packet is successful after the TB CRC corresponding to the first CB data packet is checked; or alternatively, the process may be performed,

and storing the at least one CB data packet descriptor under the condition that the LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that the MAC CE exists after the LCID corresponding to the first CB data packet, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked.

That is, in this embodiment, in the case where the LCID corresponding to the first CB packet indicates that there is a MAC CE after the LCID corresponding to the first CB packet, in order to ensure transmission of the MAC CE, it is necessary to determine whether to update the state variable of the target window or discard the first CB packet based on the end of the TB CRC check.

The TB CRC corresponding to the first CB packet may be a CRC of the TB to which the first CB packet belongs. For example, the TB x is divided into a plurality of CB packets, where the plurality of CB packets includes the first CB packet, and the TB CRC corresponding to the first CB packet is the CRC of the TB x.

In some embodiments, the step S230 may specifically include:

and under the condition that the LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that no MAC CE exists after the LCID corresponding to the first CB data packet, updating the state variable of the target window or discarding the first CB data packet according to the at least one CB data packet descriptor.

In some embodiments, the updating the state variable of the destination window or discarding the first CB packet according to the at least one CB packet descriptor comprises:

discarding the first CB packet if the PDU SN in the at least one CB packet descriptor is outside the target window; or alternatively, the process may be performed,

and under the condition that the PDU SN in the at least one CB data packet descriptor is positioned in the target window, updating the state variable of the target window or discarding the first CB data packet according to the corresponding integrity check result of the first CB data packet and/or whether the payload of the first CB data packet is damaged.

Thus, in packet processing based on CB granularity, it is necessary to ensure that PDU SN is within the target window, and PDUs outside the target window or repeated may be discarded.

In some embodiments, updating the state variable of the target window or discarding the first CB packet according to the integrity check result corresponding to the first CB packet and/or whether the payload of the first CB packet is damaged comprises:

under the condition of enabling the integrity check, if the integrity check corresponding to the first CB data packet fails, discarding the first CB data packet; or alternatively, the process may be performed,

under the condition of enabling the integrity check, if the integrity check corresponding to the first CB data packet is successful, updating the state variable of the target window or discarding the first CB data packet according to whether the effective load of the first CB data packet is damaged or not; or alternatively, the process may be performed,

and under the condition that the integrity check is not enabled, updating the state variable of the target window or discarding the first CB data packet according to whether the payload of the first CB data packet is damaged.

For example, in the case of integrity check enablement, the at least one CB data packet descriptor further includes a message authentication code (e.g., an X-MAC) that is compared to a message authentication code (e.g., MAC-I) determined based on the payload of the first CB data packet. If the X-MAC matches the MAC-I, then the integrity verification is passed.

Note that in the NR system, PDCP SN is 18 bits, and the SN wraparound problem is less likely to occur, and therefore PDCP superframe number (hyper frame number, HFN) is a certain value. In LTE systems, SN detouring is more likely to occur, and thus the decrypted outgoing data packet may be erroneous. Therefore, whether to discard the first CB packet can be determined by whether the payload of the first CB packet is damaged.

In some embodiments, updating the state variable of the destination window or discarding the first CB packet based on whether the payload of the first CB packet is corrupted comprises:

if the checksum corresponding to the first CB data packet is successfully checked under the condition that the PDU session corresponding to the first CB data packet is of an IP type, updating the state variable of the target window; or alternatively, the process may be performed,

if the PDU session corresponding to the first CB data packet is of an IP type and the checksum corresponding to the first CB data packet fails to check, updating the state variable of the target window or discarding the first CB data packet according to the service quality (Quality of Service, qoS) information corresponding to the first CB data packet; or alternatively, the process may be performed,

if the PDU session corresponding to the first CB data packet is of the Ethernet type, if the CRC corresponding to the first CB data packet is successful, updating the state variable of the target window; or alternatively, the process may be performed,

and if the PDU session corresponding to the first CB data packet is of the Ethernet type, if the CRC corresponding to the first CB data packet fails, updating the state variable of the target window or discarding the first CB data packet according to the QoS information corresponding to the first CB data packet.

For example, for IPv4 packets, the checksum may correspond to a header and a payload; for IPv6 packets, the checksum may correspond to a load.

Specifically, for example, in the case where the PDU session corresponding to the first CB packet is of the IP type, the checksum corresponding to the first CB packet may be a 16-bit complement sum calculated by the IP pseudo packet header and the IP packet data. The IP pseudo packet header is composed of a source IP address, a destination IP address, a protocol number of an IP protocol, and an IP length (in bytes).

Specifically, for example, in the case where the PDU session corresponding to the first CB packet is of an IP type and the first CB packet is a user data protocol (User Data Protocol, UDP) packet in the IP type, the checksum corresponding to the first CB packet may be a 16-bit complement sum calculated by the IP pseudo packet header and the UDP packet data. The IP pseudo-header is composed of a source IP address, a destination IP address, a protocol number of a UDP protocol, and a UDP length (in bytes).

In some embodiments, the updating the state variable of the target window or discarding the first CB packet according to the QoS information corresponding to the first CB packet includes:

determining a first PER according to QoS information corresponding to the first CB data packet;

updating the state variable of the target window in case that the error rate of the CB CRC is less than the first PER; or alternatively, the process may be performed,

caching the first CB data packet under the condition that the error rate of the CB CRC is larger than or equal to the first PER, and updating the state variable of the target window if the TB CRC check corresponding to the first CB data packet is successful after the TB CRC check corresponding to the first CB data packet is finished; or alternatively, the process may be performed,

And caching the first CB data packet under the condition that the error rate of the CB CRC is greater than or equal to the first PER, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked.

Specifically, the packet error rate (Packet error rate, PER) defines a numerical upper limit for PDUs (e.g., IP packets) that have been processed by a sender of a link layer protocol (e.g., RLC entity) but not successfully delivered by a corresponding receiver to an upper layer (PDCP entity). In the case of NR, since PDCP COUNT is a certain value, errors in packets detected after SSCL must be caused by CB of physical layer demodulation errors.

The error rate of the CB CRC is smaller than the first PER, which means that the first CB packet is correct with a high probability, and the TB CRC should not be required to be issued to the upper layer normally. The error rate of the CB CRC is greater than or equal to the first PER, meaning that the error rate of the CB CRC is insufficient to detect an error, requiring further processing of the results of the TB CRC.

Alternatively, the error rate of the CB CRC is a theoretically relatively fixed value, such as 10 ^-6 。

Determining a first PER according to QoS information corresponding to the first CB data packet, and determining a first PDB according to QoS information corresponding to the first CB data packet;

discarding the first CB packet if SRTT < β > is greater than or equal to the first PER; or alternatively, the process may be performed,

if the error rate of the CB CRC is greater than or equal to the first PER, if SRTT is greater than or equal to beta, caching the first CB data packet, and after the TB CRC check corresponding to the first CB data packet is finished, if the TB CRC check corresponding to the first CB data packet is successful, updating the state variable of the target window; or alternatively, the process may be performed,

if the error rate of the CB CRC is greater than or equal to the first PER, buffering the first CB data packet if SRTT is greater than or equal to beta, and after the TB CRC check corresponding to the first CB data packet is finished, discarding the first CB data packet if the TB CRC check corresponding to the first CB data packet fails;

wherein, beta is more than or equal to 2.

In particular, the packet delay budget (Packet Delay Budget, PDB) defines an upper bound on the time that a packet may be delayed between the UE and the user plane function (User Plane Function, UPF) entity. The PDB may include: UE end-to-end (between Access Point (AP) and physical layer), air interface (between UE and Access Network (AN)) and delay between AN and UPF entity (N3 interface).

It should be noted that if SRTT < β×first PDB, the application layer gives enough time to retransmit the protocol stack, so the protocol stack discards the first CB packet also has no problem.

Inside layer 2 at the UE end, the UE end-to-end delay depends largely on the UE functionality provided by the system architecture, the delay caused by the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ), etc. Since radio conditions vary greatly, it is difficult to calculate Round Trip Time (RTT) from the data plane L2 itself. On the other hand, when a TCP/IP connection is established, the RTT value will be adjusted according to a Smooth RTT (SRTT) calculation. That is, a smoothing factor is applied to the RTT, creating a predicted round trip time that is beneficial in ensuring packet delivery.

Alternatively, the SRTT may be calculated based on the following equation 1.

Srtt=srtt (α SRTT) +((1- α) RTT) formula 1

Where α represents a smoothing factor between 0.8RTT and 0.9 RTT.

Alternatively, RTT may be a parameter acquired from the L3 IP layer.

In some embodiments, determining the first PER from preset QoS template information according to QoS information corresponding to the first CB packet;

The preset QoS template information at least comprises a plurality of QoS information and PERs corresponding to the QoS information, and the QoS information comprises QoS information corresponding to the first CB data packet.

In some embodiments, the first PDB is determined from preset QoS template information according to QoS information corresponding to the first CB packet;

the preset QoS template information at least comprises a plurality of QoS information and PDBs corresponding to the QoS information, and the QoS information comprises QoS information corresponding to the first CB data packet.

In some embodiments, the preset QoS template information may be obtained from a Non-Access Stratum (NAS) session management (Session Management, SM) layer.

In some embodiments, the preset QoS template information may be as shown in table 1.

TABLE 1

Note that in table 1 above, qoS may be represented by a 5G QoS indication (5G QoS Indicator,5QI), and resource types may include minimum guaranteed rate (Guaranteed Bit Rate, GBR), non-GBR, and Delay Critical (Delay Critical) GBR. The parameters in table 1 are merely examples and are not limiting to the present application. In addition, the preset QoS template information may further include other parameters, which are not limited in the embodiment of the present application.

In some embodiments, an alternative flow of packet processing based on CB granularity may be as shown in fig. 5, and specifically may include the following steps 0 to 12.

And step 0, receiving a first CB data packet, wherein the first CB data packet is decoded to obtain at least one CB data packet descriptor, and the TB to which the first CB data packet belongs detects the complete MAC sub-PDU.

Step 1, when the LCID corresponding to the first CB packet matches with a locally stored LCID and the LCID corresponding to the first CB packet indicates that there is a MAC CE after the LCID corresponding to the first CB packet, storing the at least one CB packet descriptor until the TB CRC check is finished to trigger an actual process. For example, if the TB CRC corresponding to the first CB packet is checked successfully, updating the state variable of the target window; and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails.

And step 1, discarding the first CB data packet under the condition that the LCID corresponding to the first CB data packet is not matched with the LCID stored locally.

And executing step 2 under the condition that the LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that no MAC CE exists after the LCID corresponding to the first CB data packet.

Step 2, performing layer 2 packet header decoding, in a security policy component logic (SSCL), discarding the first CB data packet if the PDU SN is not in the receiving window; otherwise, step 3 is executed.

Step 3, calculating PDCP COUNT (PDCP COUNT) which includes HFN and PDCP SN, and then performing decryption and integrity check.

Step 4, if the integrity check fails, discarding the first CB data packet; if the integrity check is passed, go to step 11 or execute step 5 or step 6; if the integrity check is not enabled, step 5 or step 6 is performed.

And step 5, if the PDU session corresponding to the first CB data packet is of the Ethernet type, calculating the CRC of the Ethernet frame.

Otherwise

And 6, if the PDU session corresponding to the first CB data packet is of an IP type, calculating an IP packet header and a payload checksum of the IPv4 or calculating a payload checksum of the IPv 6.

Step 7, if the CRC check of the Ethernet frame or the checksum check of the IP is passed, the step 11 is switched to update the RLC/PDCP window state variable and receive the state bitmap, and the process is ended; otherwise, step 8 is performed.

And 8, decoding the first CB data packet to obtain at least one CB data packet descriptor, and checking the at least one CB data packet descriptor in a reliability policy component logic (RSCL) to check the QoS parameters of the current service.

Step 9, if the QoS requirement of the PDU session corresponding to the first CB data packet is smaller than CB _err The payload of the first CB packet may be discarded and at least one CB packet descriptor flows to step 11; otherwise, step 10 is performed.

At least one CB packet descriptor is buffered until the TB CRC ends on the physical layer PHY, step 10. If the TB CRC passes, executing step 11; otherwise, step 12 is performed.

And step 11, updating the RLC/PDCP window state variable and the receiving state bitmap, and ending the process.

Step 12, discarding the buffered at least one CB packet descriptor.

It should be understood that fig. 5 illustrates steps or operations of packet processing based on CB granularity, but these steps or operations are only examples and other operations or variations of the operations in fig. 5 may also be performed by embodiments of the present application.

In some embodiments, security policy component logic (SSCL) may extend error detection by connecting the security engine with a checksum/CRC check engine, as shown in FIG. 6, not only by performing integrity checks defined in the 3GPP data plane, but also by performing corruption checks in Ethernet/IP communications. The data packets may be pipelined through both the security engine and the hardware implementation. If no error is detected, the packet is trusted (PDCP HFN is also trusted) and the RLC window state variable or PDCP window state variable is updated, which will complete the packet processing in layer 2. However, if the SSCL detects an error, then more policies are processed in the reliability policy component logic (RSCL) before the packet is finally discarded.

In some embodiments, reliability policy component logic (RSCL) may be as shown in fig. 7, and when the SSCL detects an error in the packet, the packet will be further input to the RSCL. Wherein the packet error comes from two factors, firstly, PDCP HFN may be an erroneous value in LTE and secondly, there are errors in CB that the security engine and the checksum/CRC check engine do not detect. In either case, reliability is ensured by RSCL.

Optionally, in the RSCL, determining a first PER according to QoS information corresponding to the first CB packet;

Optionally, in the RSCL, determining a first PER according to QoS information corresponding to the first CB packet, and determining a first PDB according to QoS information corresponding to the first CB packet;

wherein, beta is more than or equal to 2.

Optionally, determining the first PER from preset QoS template information according to QoS information corresponding to the first CB packet; the preset QoS template information at least comprises a plurality of QoS information and PERs corresponding to the QoS information, and the QoS information comprises QoS information corresponding to the first CB data packet.

Optionally, determining the first PDB from preset QoS template information according to QoS information corresponding to the first CB packet; the preset QoS template information at least comprises a plurality of QoS information and PDBs corresponding to the QoS information, and the QoS information comprises QoS information corresponding to the first CB data packet.

Therefore, in the embodiment of the application, a downlink data packet processing mode based on CB granularity is introduced into L2, so that the memory space occupied by cache data can be reduced, the load of a system for accessing a memory can be reduced, the data packet processing process can be accelerated, and the data packet processing delay can be reduced.

Further, the downlink data packet processing mode based on the CB granularity can reduce the memory consumption of the physical layer for storing the TB and then forwarding the TB to the data surface. Because the downlink data packet processing mode based on CB granularity reduces the reading and writing of a memory once, the power consumption of the modem is lower. The minimum delay is reduced from 1ms (or 1TTI time) to 1/Ncb (e.g., to 1/132ms when ncb=132) based on the downlink packet processing mode of CB granularity. The downlink data packet processing mode based on CB granularity is easy to realize high-speed and high-throughput data processing.

The method embodiments of the present application are described in detail above with reference to fig. 4 and 7, and the apparatus embodiments of the present application are described in detail below with reference to fig. 8 to 11, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 8 shows a schematic block diagram of a device 300 for wireless communication according to an embodiment of the present application. As shown in fig. 8, the apparatus 300 for wireless communication includes: a communication unit 310 and a processing unit 320;

the communication unit 310 is configured to receive a first coded block CB packet;

the processing unit 320 is configured to decode the first CB packet to obtain at least one CB packet descriptor;

the processing unit 320 is further configured to update a state variable of the target window or discard the first CB packet according to the logical channel identifier LCID corresponding to the first CB packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

In some embodiments, the processing unit 320 is specifically configured to:

under the condition that the LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that a media access control layer control unit (MAC CE) does not exist after the LCID corresponding to the first CB data packet, updating a state variable of a target window or discarding the first CB data packet according to the at least one CB data packet descriptor; or alternatively, the process may be performed,

storing the at least one CB data packet descriptor under the condition that LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that MAC CE exists after the LCID corresponding to the first CB data packet, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked; or alternatively, the process may be performed,

In some embodiments, the processing unit 320 is specifically configured to:

discarding the first CB packet if the PDU sequence number SN in the at least one CB packet descriptor is outside the destination window; or alternatively, the process may be performed,

In some embodiments, the processing unit 320 is specifically configured to:

if the checksum corresponding to the first CB data packet is successfully checked under the condition that the PDU session corresponding to the first CB data packet is of an Internet Protocol (IP) type, updating the state variable of the target window; or alternatively, the process may be performed,

If the PDU session corresponding to the first CB data packet is of an IP type, if the checksum corresponding to the first CB data packet fails to check, updating the state variable of the target window or discarding the first CB data packet according to the QoS information corresponding to the first CB data packet; or alternatively, the process may be performed,

if the Cyclic Redundancy Code (CRC) check corresponding to the first CB data packet is successful under the condition that the PDU session corresponding to the first CB data packet is of an Ethernet type, updating the state variable of the target window; or alternatively, the process may be performed,

In some embodiments, the processing unit 320 is specifically configured to:

determining a first data packet error rate PER according to QoS information corresponding to the first CB data packet;

In some embodiments, the processing unit 320 is specifically configured to:

determining a first PER according to QoS information corresponding to the first CB data packet, and determining a first data packet delay budget PDB according to the QoS information corresponding to the first CB data packet;

discarding the first CB packet if the smooth round trip transmission time SRTT < β > is greater than or equal to the first PER; or alternatively, the process may be performed,

Wherein, beta is more than or equal to 2.

In some embodiments, the processing unit 320 is specifically configured to:

determining a first PER from preset QoS template information according to QoS information corresponding to the first CB data packet;

In some embodiments, the processing unit 320 is specifically configured to:

determining a first PDB from preset QoS template information according to QoS information corresponding to the first CB data packet;

In some embodiments, the target window is one of: a radio link control RLC window, a packet data convergence protocol PDCP window.

In some embodiments, in the case that the at least one CB packet descriptor contains an RLC header, the target window is an RLC window; alternatively, in the case that the at least one CB packet descriptor includes a PDCP header, the target window is a PDCP window.

In some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the wireless communication device 300 according to the embodiments of the present application may correspond to the embodiments of the method of the present application, and that the above and other operations and/or functions of the respective units in the wireless communication device 300 are respectively for implementing the corresponding flow in the method 200 shown in fig. 4, and are not described herein for brevity.

Fig. 9 is a schematic structural diagram of a communication device 400 provided in an embodiment of the present application. The communication device 400 shown in fig. 9 comprises a processor 410, from which the processor 410 may call and run a computer program to implement the method in the embodiments of the present application.

In some embodiments, as shown in fig. 9, the communication device 400 may also include a memory 420. Wherein the processor 410 may call and run a computer program from the memory 420 to implement the methods in embodiments of the present application.

Wherein the memory 420 may be a separate device from the processor 410 or may be integrated into the processor 410.

In some embodiments, as shown in fig. 9, the communication device 400 may further include a transceiver 430, and the processor 410 may control the transceiver 430 to communicate with other devices, and in particular, may transmit information or data to other devices, or receive information or data transmitted by other devices.

Among other things, transceiver 430 may include a transmitter and a receiver. Transceiver 430 may further include antennas, the number of which may be one or more.

In some embodiments, the processor 410 may implement the functions of a processing unit in the terminal device, which are not described herein for brevity.

In some embodiments, the transceiver 430 may implement functions of a communication unit in the terminal device, which are not described herein for brevity.

In some embodiments, the communication device 400 may be specifically a terminal device in the embodiments of the present application, and the communication device 400 may implement a corresponding flow implemented by the terminal device in each method in the embodiments of the present application, which is not described herein for brevity.

Fig. 10 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 500 shown in fig. 10 includes a processor 510, and the processor 510 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

In some embodiments, as shown in fig. 10, the apparatus 500 may further include a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the methods in embodiments of the present application.

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.

In some embodiments, the processor 510 may implement the functions of a processing unit in the terminal device, which are not described herein for brevity.

In some embodiments, the apparatus 500 may further include an input interface 530. The processor 510 may control the input interface 530 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips. Alternatively, the processor 510 may be located on-chip or off-chip.

In some embodiments, the input interface 530 may implement the functionality of a communication unit in the terminal device.

In some embodiments, the apparatus 500 may further include an output interface 540. Wherein the processor 510 may control the output interface 540 to communicate with other devices or chips, and in particular may output information or data to other devices or chips. Alternatively, the processor 510 may be located on-chip or off-chip.

In some embodiments, output interface 540 may implement the functionality of a communication unit in a terminal device.

In some embodiments, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement corresponding flows implemented by the network device in each method in the embodiments of the present application, which are not described herein for brevity.

In some embodiments, the apparatus may be applied to a terminal device in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiments of the present application, which is not described herein for brevity.

In some embodiments, the device mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 11 is a schematic block diagram of a communication system 600 provided in an embodiment of the present application. As shown in fig. 11, the communication system 600 includes a terminal device 610 and a network device 620.

The terminal device 610 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 620 may be used 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.

In some embodiments, the computer readable storage medium may be applied to a terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein 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 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. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or 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 U-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

1. A method of wireless communication, comprising:

receiving a first coded block CB data packet;

updating a state variable of a target window or discarding the first CB data packet according to a logic channel identifier LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

2. The method of claim 1, wherein updating the state variable of the target window or discarding the first CB packet according to the logical channel identifier LCID corresponding to the first CB packet comprises:

updating a state variable of a target window or discarding the first CB data packet according to the at least one CB data packet descriptor when the LCID corresponding to the first CB data packet is matched with a locally stored LCID and indicates that a media access control layer control unit (MAC CE) does not exist after the LCID corresponding to the first CB data packet; or alternatively, the process may be performed,

Storing the at least one CB data packet descriptor under the condition that LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that an MAC CE exists after the LCID corresponding to the first CB data packet, and updating the state variable of the target window if the TB CRC corresponding to the first CB data packet is successful after the TB CRC corresponding to the first CB data packet is checked; or alternatively, the process may be performed,

storing the at least one CB data packet descriptor under the condition that LCID corresponding to the first CB data packet is matched with the LCID stored locally and the LCID corresponding to the first CB data packet indicates that an MAC CE exists after the LCID corresponding to the first CB data packet, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked; or alternatively, the process may be performed,

3. The method of claim 2, wherein updating the state variable of the destination window or discarding the first CB packet according to the at least one CB packet descriptor comprises:

Discarding the first CB packet if the PDU sequence number SN in the at least one CB packet descriptor is outside the target window; or alternatively, the process may be performed,

4. The method of claim 3, wherein the step of,

the updating the state variable of the target window or discarding the first CB data packet according to the integrity check result corresponding to the first CB data packet and/or whether the payload of the first CB data packet is damaged, includes:

5. The method of claim 4, wherein updating the state variable of the destination window or discarding the first CB packet according to whether the payload of the first CB packet is corrupted comprises:

if the checksum corresponding to the first CB data packet is successful in verification under the condition that the PDU session corresponding to the first CB data packet is of an Internet Protocol (IP) type, updating the state variable of the target window; or alternatively, the process may be performed,

if the PDU session corresponding to the first CB data packet is of an IP type, if the checksum corresponding to the first CB data packet fails to check, updating the state variable of a target window or discarding the first CB data packet according to the QoS information corresponding to the first CB data packet; or alternatively, the process may be performed,

6. The method of claim 5, wherein the step of determining the position of the probe is performed,

the updating the state variable of the target window or discarding the first CB data packet according to the QoS information corresponding to the first CB data packet includes:

updating the state variable of the target window in the case that the error rate of the CB CRC is smaller than the first PER; or alternatively, the process may be performed,

caching the first CB data packet under the condition that the error rate of the CB CRC is larger than or equal to the first PER, and updating the state variable of the target window if the TB CRC corresponding to the first CB data packet is successful after the TB CRC of the transmission block corresponding to the first CB data packet is checked; or alternatively, the process may be performed,

and caching the first CB data packet under the condition that the error rate of the CB CRC is larger than or equal to the first PER, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked.

7. The method of claim 5, wherein the step of determining the position of the probe is performed,

if the error rate of the CB CRC is greater than or equal to the first PER, discarding the first CB packet if the smooth round trip transmission time SRTT < β×the first PDB; or alternatively, the process may be performed,

if the error rate of the CB CRC is greater than or equal to the first PER, caching the first CB data packet if SRTT is greater than or equal to beta, and after the TB CRC check corresponding to the first CB data packet is finished, if the TB CRC check corresponding to the first CB data packet is successful, updating the state variable of the target window; or alternatively, the process may be performed,

if the error rate of the CB CRC is greater than or equal to the first PER, caching the first CB data packet if SRTT is greater than or equal to beta, and discarding the first CB data packet if the TB CRC corresponding to the first CB data packet fails after the TB CRC corresponding to the first CB data packet is checked;

Wherein, beta is more than or equal to 2.

8. The method according to claim 6 or 7, wherein,

the determining the first PER according to the QoS information corresponding to the first CB packet includes:

9. The method of claim 7, wherein the step of determining the position of the probe is performed,

the determining the first PDB according to the QoS information corresponding to the first CB packet includes:

10. The method of any one of claims 1 to 7, wherein the target window is one of: a radio link control RLC window, a packet data convergence protocol PDCP window.

11. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

in the case that the at least one CB packet descriptor contains an RLC header, the target window is an RLC window; or alternatively, the process may be performed,

in the case that the at least one CB packet descriptor includes a PDCP header, the target window is a PDCP window.

12. An apparatus for wireless communication, comprising:

a communication unit, configured to receive a first coded block CB packet;

13. A communication device, comprising: a transceiver and a processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the transceiver is configured to: receiving a first coded block CB data packet;

the processor is configured to: decoding the first CB data packet to obtain at least one CB data packet descriptor; updating a state variable of a target window or discarding the first CB data packet according to a logic channel identifier LCID corresponding to the first CB data packet; wherein the state variable of the target window is updated based on the at least one CB packet descriptor.

14. A communication 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 11.

15. A chip, comprising: a processor for calling and running a computer program from a memory, such that the processor performs the method of any of claims 1 to 11.

16. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 11.