WO2025231619A1 - Wireless communication method and apparatus, device, and storage medium - Google Patents

Abstract

The present application relates to the technical field of communications. Provided are a wireless communication method and apparatus, a device, and a storage medium. The method comprises: a PDCP layer or entity performs an action related to a reordering timer (210). The present application specifies a data packet handling means by a communication device from multiple perspectives, and can effectively support varying data transmission requirements.

Description

Wireless communication methods, apparatus, devices and storage media Technical Field

This application relates to the field of communication technology, and in particular to a wireless communication method, apparatus, device, and storage medium.

Background Technology

With people's pursuit of speed, latency, high-speed mobility, and energy efficiency, as well as the diversity and complexity of business in future life, communication technologies are constantly evolving. The main application scenarios of 5G (5th-Generation) include: eMBB (Enhanced Mobile Broadband), URLLC (Ultra-Reliable Low Latency Communication), and mMTC (Massive Machine-Type Communication).

Further research is needed on wireless communication technologies for different application scenarios.

Summary of the Invention

This application provides a wireless communication method, apparatus, device, and storage medium. The technical solutions provided by this application are as follows:

According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being performed by a communication device, the method comprising: a PDCP (Packet Data Convergence Protocol) layer or entity performing behavior related to a reordering timer.

According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a communication device, the method comprising: performing a resource mapping operation related to a data or logical channel based on a second rule and/or first information.

According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a terminal device, the method comprising: performing actions related to data transmission based on at least two objects having association or cooperation.

According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being performed by a network device, the method comprising: acquiring association or collaboration information, the association or collaboration information being used to indicate at least two objects having association or collaboration.

According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a communication device, the method comprising: processing data packets based on FEC (Forward Error Correction) information.

According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a processing module for performing actions related to a reordering timer by a PDCP layer or entity.

According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a processing module, configured to perform a resource mapping operation related to a data or logical channel based on a second rule and/or first information.

According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a processing module for performing data transmission-related actions based on at least two objects having association or cooperation.

According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a processing module configured to acquire association or collaboration information, the association or collaboration information being used to indicate at least two objects having association or collaboration.

According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a processing module for processing data packets based on FEC information.

According to one aspect of the embodiments of this application, a communication device is provided, the communication device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the above-described wireless communication method.

According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein the storage medium stores a computer program for execution by a processor to implement the above-described wireless communication method.

According to one aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and/or program instructions, which, when the chip is running, are used to implement the above-described wireless communication method.

According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, and a processor reading from the computer-readable storage medium and executing the computer instructions to implement the above-described wireless communication method.

The technical solutions provided in this application embodiment can include the following beneficial effects: This application embodiment specifies the processing method of data packets by communication devices from multiple different perspectives, which can effectively support the transmission needs of different data.

Attached Figure Description

Figure 1 is a schematic diagram of a network architecture provided in one embodiment of this application.

Figure 2 is a flowchart of a wireless communication method provided in an embodiment of this application.

Figure 3 is a flowchart of a wireless communication method provided in another embodiment of this application.

Figure 4 is a flowchart of a wireless communication method provided in another embodiment of this application.

Figure 5 is a flowchart of a wireless communication method provided in another embodiment of this application.

Figure 6 is a flowchart of a wireless communication method provided in another embodiment of this application.

Figure 7 is a block diagram of a wireless communication device provided in one embodiment of this application.

Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

Detailed Implementation

To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution systems of NR system, and LTE-Bass on unlicensed spectrum. This includes LTE-U (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, Non-Terrestrial Networks (NTN) systems, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th Generation (5G) systems, Beyond 5G (B5G) systems, 6th Generation (6G) systems, and other communication systems.

Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

The communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.

The embodiments of this application can be applied to both non-terrestrial network (NTN) systems and terrestrial network (TN) systems. NTN typically uses satellite communication to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and other NTN systems may be included in the future.

Please refer to Figure 1, which shows a schematic diagram of a network architecture 100 provided in one embodiment of this application. The network architecture 100 may include: a terminal device 10, an access network device 20, and a core network element 30.

Terminal device 10 can refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. In some embodiments, terminal device 10 can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in 5GS (5th Generation System), or terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and this application embodiment is not limited to these. For ease of description, the devices mentioned above are collectively referred to as terminal devices. There are usually multiple terminal devices 10, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. Terminal devices can also be simply referred to as terminals or UEs, the meaning of which will be understood by those skilled in the art.

Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned devices providing wireless communication functionality to terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between terminal device 10 and core network element 30 through access network device 20. For example, in an LTE (Long Term Evolution) system, access network device 20 can be one or more eNodeBs in an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or an EUTRAN; in a 5G NR system, access network device 20 can be one or more gNBs in a RAN (Radio Access Network). In the embodiments of this application, unless otherwise specified, "network device" refers to access network device 20, such as a base station.

Core network element 30 is a network element deployed in the core network. Its main functions are to provide user connectivity, manage users, and carry out service delivery, serving as an interface to external networks. For example, core network elements in a 5G NR system may include... Network elements such as AMF (Access and Mobility Management Function), UPF (User Plane Function), and SMF (Session Management Function).

In some embodiments, the access network device 20 and the core network element 30 communicate with each other via some air interface technology, such as the NG interface in a 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via some air interface technology, such as the Uu interface.

The "5G NR system" in this application embodiment can also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this application embodiment can be applied to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (such as B5G (Beyond 5G) systems, 6G systems (6th Generation System), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems. This application does not limit these applications.

In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) on the carrier used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

The NR protocol stack's L2 (Layer 2) is divided into four sub-layers: MAC (Medium Access Control), RLC (Radio Link Control), PDCP, and SDAP (Service Data Adaptation Protocol).

This application primarily concerns the PDCP layer, which is described below. For uplink, the PDCP layer is mainly responsible for receiving PDCP SDUs from the SDAP layer, processing them to generate PDCP PDUs (Protocol Data Units), and then delivering them to the corresponding RLC layer. For downlink, the PDCP layer is mainly responsible for receiving PDCP PDUs delivered from the RLC layer, processing them to remove the PDCP header, and then delivering them to the SDAP layer. PDCP and radio bearers are in one-to-one correspondence; each radio bearer (including SRBs (Signalling Radio Bearers) and DRBs (Data Radio Bearers)) is associated with a PDCP entity. The functions provided by the NR PDCP layer are mostly similar to those in LTE, mainly including: maintenance of PDCP sender or receiver sequence numbers; header compression and decompression; encryption and decryption, integrity protection; timer-based PDCP SDU discarding; routing functions for split bearers; copy transmission functions; reordering and in-order delivery functions.

The PDCP layer is similar to LTE in its data transmission and reception process. One improvement is that NR PDCP uses an absolute count method (COUNT) for maintaining local variables and performing conditional comparisons during data transmission and reception. This significantly improves protocol readability. The COUNT consists of a serial number (SN) and a superframe number, with a fixed size of 32 bits. It's important to note that the PDCP PDU header still includes the SN, not the COUNT value, thus not increasing air interface transmission overhead.

Specifically, for uplink transmission, the PDCP transmission side maintains a local COUNT value for TX_NEXT, initially set to 0. Each time a new PDCP PDU is generated, the SN in the corresponding header is set to the value corresponding to TX_NEXT, and TX_NEXT is incremented by 1. The PDCP transmission side performs header compression, integrity protection, and encryption operations on the PDCP SDU sequentially according to the network configuration. For downlink reception, the PDCP receiver maintains a receive window based on the COUNT value of a local variable. This receive window is maintained by the following local variables.

RX_NEXT: The COUNT value corresponding to the next expected PDCP SDU.

RX_DELIV: The COUNT value corresponding to the next PDCP SDU expected to be delivered to the uplink. This variable determines the lower boundary of the receive window.

RX_REORD: The COUNT corresponding to the PDCP PDU that triggered the sorting timer.

Based on the PUSH window mechanism, the PDCP receiver processes the received PDCP PDUs.

NR PDCP also supports data replication. Simply put, based on network-side configuration and activation commands, PDCP PDU can be copied into two identical copies and delivered to different RLC entities.

When a PDCP entity is associated with multiple RLC entities, the corresponding RLC entities share the same transmission mode. The transmission modes of RLC entities (referred to as RLC transmission modes) include the following: AM (Acknowledged Mode), UM (Unacknowledged Mode), and TM (Transparent Mode).

Please refer to Figure 2, which shows a flowchart of a wireless communication method provided in one embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 210.

Step 210: The PDCP layer or entity performs actions related to the reordering timer.

In some embodiments, the PDCP layer or entity of the communication device performs behavior related to the reordering timer.

In some embodiments, the communication device can be a terminal device (i.e., UE) or a network device (such as a base station). In this embodiment, the communication device acts as a receiving device, receiving data packets. The PDCP layer or entity of the communication device can also be referred to as the receiving PDCP entity.

In some embodiments, a reordering timer is used by the PDCP layer or entity to determine when to deliver the packets it receives.

In some embodiments, the duration of the reordering timer is configured by the upper layer, NR SL (sidelink) communication, or SL SRB4. Except for NR SL communication or SL SRB4, the reordering timer is determined by the UE implementation. This reordering timer is used to detect the loss of PDCP layer data PDUs. If one reordering timer is running, another reordering timer should not be started; that is, only one reordering timer runs for each receiving PDCP entity at a given time.

In some embodiments, actions related to the reordering timer are performed, including: determining the value of the reordering timer, and/or processing data packets based on the reordering timer. In some embodiments, the PDCP layer or entity determines the value of the reordering timer, and/or the PDCP layer or entity processes data packets based on the reordering timer. The value of the reordering timer can also be understood as the length of the reordering timer, referring to the duration of the reordering timer.

In some embodiments, determining the value of the reordering timer includes: determining the value of the reordering timer based on a first rule, wherein the first rule is related to the RLC transmission mode corresponding to the data packet. As described above, RLC transmission modes include AM, UM, and TM modes. Exemplarily, the first rule is related to the RLC transmission mode used by the data packet. Exemplarily, the first rule is related to the RLC transmission mode of data packets that have not yet been received. In some embodiments, the value of the reordering timer is determined based on the RLC transmission mode corresponding to the data packet.

In some embodiments, the first rule includes: when the RLC transmission mode corresponding to the data packet includes at least AM, the reordering timer value is a first value, and/or, when the RLC transmission mode corresponding to the data packet includes only UM, the reordering timer value is a second value. Exemplarily, the first value refers to the value of the reordering timer corresponding to AM, or the value of the first reordering timer, or the value of the default reordering timer. Exemplarily, the second value refers to the value of the reordering timer corresponding to UM, or the value of the second reordering timer. Exemplarily, the correspondence between RLC transmission modes and reordering timer values is pre-configured or defined, such as pre-configuring or defining the values of the reordering timer corresponding to AM and the reordering timer corresponding to UM, and the first or second value is determined based on this. Exemplarily, the values of the first and second reordering timers are different, and these two values can be pre-configured or defined. Exemplarily, the default reordering timer value can also be pre-configured or defined. Exemplarily, the aforementioned first value is greater than the second value.

In some embodiments, the RLC transmission mode corresponding to the data packet is indicated by at least one of the following methods: control PDU, data PDU.

In some embodiments, the control PDU originates from the data packet sending device.

In some embodiments, the control PDU carries at least one of the following information: SN (Serial Number), bitmap, and RLC transmission mode. The SN refers to the serial number of the data packet, such as the starting SN, which is the SN of the first data packet sent by the sending device. The bitmap indicates the RLC transmission mode corresponding to one or more data packets, where each bit in the bitmap indicates the RLC transmission mode corresponding to a data packet.

In some embodiments, the control PDU is generated based on information from the RLC layer of the transmitting device, or it is generated by the PDCP layer of the transmitting device itself. For example, the PDCP layer of the transmitting device obtains the RLC transmission mode information corresponding to the data packet from the RLC layer of the transmitting device through inter-layer interaction, generates the control PDU accordingly, and then sends the control PDU to the receiving device. For example, the PDCP layer of the transmitting device itself knows the RLC transmission mode information corresponding to the data packet, generates the control PDU accordingly, and then sends the control PDU to the receiving device.

For example, if the control PDU indicates the following information to the receiving device: data packets with SN=5, 6, 7, 8, 9, and corresponding RLC transmission modes are AM, AM, AM, AM, AM, UM respectively, then the receiving device knows that there are at least AM packets with SN=6, 7, 8. RX_DELIV(SN=5) < RX_NEXT(SN=9), the reordering timer is not running, so RX_REORD to RX_NEXT is updated to start the reordering timer. The value of the reordering timer is related to AM.

In some embodiments, the header or payload of a data PDU carries indication information indicating the RLC transmission mode corresponding to the current data packet, and/or the RLC transmission mode corresponding to the next data packet. Alternatively, the indication information indicates whether the RLC transmission mode corresponding to the current data packet has changed, remained unchanged, or changed for the next data packet. This indication information can be carried in every PDCP data PDU, or only in the last or first data packet corresponding to a change in RLC transmission mode. This scheme is applicable when the SN gap is less than X, where X can be a network configuration value.

For example, if the first PDU indicating a change in RLC transmission mode changes, and the receiving device receives a packet with SN=5 that is AM and a packet with SN=9 that is UM, then the receiving device knows that at least one packet with SN=6, 7, or 8 is AM. RX_DELIV(SN=5) < RX_NEXT(SN=9), the reordering timer is not running, so RX_REORD to RX_NEXT is updated to start the reordering timer. The value of the reordering timer is related to AM.

Using the above method, the PDCP layer of the receiving device determines the value of the reordering timer based on the RLC transmission mode corresponding to the data packet, thereby enabling the processing of data packets based on this reordering timer. In this way, different values for the reordering timer can be determined for different RLC transmission modes, ensuring that the reordering timer value is adapted to the RLC transmission mode, effectively supporting different data transmission requirements and accelerating the speed at which the PDCP layer delivers data packets to the upper layer.

In some embodiments, processing data packets based on a reordering timer includes: submitting the packet to a higher layer if the reordering timer times out. Data packets. Here, "higher layer" refers to the layer above the PDCP layer of the receiving device, also known as the SDAP layer.

In some embodiments, delivering a data packet to a higher layer when the reordering timer times out includes performing at least one of the following actions:

1) After decompressing the header, if it was not decompressed beforehand, the data packets are submitted to the higher layer in ascending order of the relevant COUNT values; the data packets are:

a) All PDCP SDUs with relevant COUNT values < RX_REORD have been stored;

b) All stored PDCP SDU(s) and the COUNT values(s) consecutively associated starting from RX_REORD;

2) Update RX_DELIV to the COUNT value of the first PDCP SDU that has not been committed to the higher level, and the COUNT value is greater than or equal to RX_REORD;

3) If RX_DELIV < RX_NEXT, then:

a) Update RX_REORD to RX_NEXT;

b) Start the t-Reordering timer.

Using the above method, the PDCP layer or entity of the receiving device performs the above actions on the data packet when the reordering timer times out, ensuring that the received data packet can be delivered to the higher layer in a timely manner.

In some embodiments, a PDCP layer or entity is associated with multiple RLC entities, and at least two RLC entities correspond to different RLC transmission modes. That is, different RLC entities associated with a PDCP entity may have different RLC transmission modes.

In existing technologies, the transmission modes of multiple RLC entities associated with a PDCP entity must be identical. However, in implementation, the transmission requirements (such as reliability and latency) of data packets from a PDCP entity may differ. The same RLC transmission mode cannot effectively support the transmission requirements of different data. Specifically, if a PDCP data packet is transmitted from AM RLC, reliability can be guaranteed but there will be significant latency; if it is transmitted from UM RLC, transmission latency can be reduced but reliable transmission cannot be guaranteed. Therefore, this application proposes that a PDCP entity be associated with RLC entities with different RLC transmission modes, so that data packets with different transmission requirements are transmitted from different RLC entities. Furthermore, when a PDCP entity is associated with multiple RLC entities with different RLC transmission modes, when the PDCP entity receives multiple data packets from different RLC transmission modes, the value of the reordering timer is determined to better accelerate the delivery speed to higher layers.

In some embodiments, when the communication device is a terminal device, the RLC transmission mode corresponding to each of the multiple RLC entities is determined by the network configuration (i.e., network device configuration) or the terminal device. Optionally, if the terminal device determines the RLC transmission mode, it may further notify the network device of the selected RLC transmission mode. In some embodiments, when the communication device is a network device, the RLC transmission mode corresponding to each of the multiple RLC entities is determined by the network device.

In some embodiments, the terminal device determines a PDCP entity and multiple associated RLC entities. Further, the terminal device determines the RLC transmission mode corresponding to each of the multiple RLC entities. The PDCP entity can be a PDCP entity of the transmitting device (i.e., a transmitting PDCP entity) or a PDCP entity of the receiving device (i.e., a receiving PDCP entity). RLC transmission modes include AM, UM, and TM modes.

In some embodiments, the RLC transmission mode corresponding to each of the multiple RLC entities is related to at least one of the following factors: whether the ability to use different RLC transmission modes for different RLC entities is supported; whether to select different RLC entities to use different RLC transmission modes; the selected RLC transmission modes corresponding to each of the multiple RLC entities; service characteristics; and the RLC transmission modes used by the different RLC entities as configured.

In some embodiments, when the communication device is a terminal device, the RLC transmission mode corresponding to each of the multiple RLC entities is related to at least one of the following factors: whether the terminal device supports the ability of different RLC entities to use different RLC transmission modes; whether the terminal device selects different RLC entities to use different RLC transmission modes; the RLC transmission modes corresponding to each of the multiple RLC entities selected by the terminal device; the service characteristics of the terminal device; and the RLC transmission modes used by the different RLC entities configured.

In some embodiments, when the communication device is a network device, the RLC transmission mode corresponding to each of the multiple RLC entities is related to at least one of the following factors: whether the network device supports the ability of different RLC entities to use different RLC transmission modes; whether the network device selects different RLC entities to use different RLC transmission modes; the RLC transmission modes corresponding to each of the multiple RLC entities selected by the network device; the service characteristics of the network device; and the RLC transmission modes used by the different RLC entities as configured.

In some embodiments, when the network configures the RLC transmission modes corresponding to multiple RLC entities of the terminal device, the terminal device may send at least one of the following information to the network device: capability information, selection information, and service characteristics. The capability information indicates whether the terminal device supports the ability of different RLC entities to use different RLC transmission modes; the selection information indicates whether the terminal device selects different RLC entities to use different RLC transmission modes; and the service characteristics include services or data with different transmission requirements in a DRB or PDCP entity or QoS flow, or the service characteristics include the need to perform different processing on different services or data in a DRB or PDCP entity or QoS flow. Based on the above information, the network device determines whether to configure or use different transmission modes for different RLC entities. Optionally, the above service characteristics may also be sent to the network device by the core network element.

In some embodiments, where the terminal device determines the RLC transmission mode corresponding to each of its multiple RLC entities, the terminal device can determine this based on at least one of the following: capability information, selection information, and service characteristics. Explanations of these information can be found above and will not be repeated here. Based on the above information, the terminal device determines whether to configure or use different transmission modes for different RLC entities.

In some embodiments, the PDCP layer delivers data packets to the lower layer (i.e., the RLC layer). This delivery includes split transmissions, duplication transmissions, or other transmission scenarios. Data packets delivered from the PDCP layer to the lower layer undergo different RLC processing depending on the RLC entity's transmission mode.

Using the above method, a PDCP entity is associated with RLC entities of different RLC transmission modes, so that data packets with different transmission requirements are transmitted from different RLC entities, thereby effectively supporting the transmission requirements of different data.

Please refer to Figure 3, which shows a flowchart of a wireless communication method provided in another embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 310.

Step 310: The communication device performs a resource mapping operation related to the data or logical channel based on the second rule and/or the first information.

In some embodiments, the communication device may be a terminal device (i.e., UE) or a network device (such as a base station).

In some embodiments, the terminal device receives an uplink grant and performs resource mapping operations related to the data or logical channel (LCH) based on a second rule and/or first information. In some embodiments, the uplink grant can be a CG (Configured Grant) and/or a DG (Dynamic Grant).

In some embodiments, the first information is carried in configuration or scheduling information.

In some embodiments, the first information is directed to either CG or DG.

In some embodiments, the uplink authorization includes first information, which is indicated by RRC (Radio Resource Control) signaling or DCI (Downlink Control Information).

In some embodiments, performing resource mapping operations related to data or logical channels includes at least one of the following: 1) determining a mapping between data and resources; 2) determining a mapping between logical channels and resources; 3) determining an LCP (Logical Channel Prioritization) mapping restriction; 4) determining whether data can be transmitted in the first resource or with priority; 5) determining whether logical channels can be transmitted in the first resource or with priority.

In some embodiments, the logical channel satisfies at least one of the following conditions: 1) The index of the logical channel is a first index; wherein, the first index can be understood as a specific index value, that is, the index of the logical channel is a specific index value; 2) The priority of the logical channel is a first priority; wherein, the first priority can be understood as a specific priority, that is, the priority of the logical channel is a specific priority, or in other words, the priority value of the logical channel is a specific priority value; 3) The delay corresponding to the logical channel satisfies a first condition; wherein, the first condition includes at least one of the following: there is a delay requirement, the delay requirement is less than or equal to a first threshold value, and the delay value is less than or equal to a second threshold value; 4) The logical channel carries data whose delay satisfies a second condition; wherein, the second condition includes at least one of the following: there is a delay requirement, the delay requirement is less than or equal to a third threshold value, and the delay value is less than or equal to a fourth threshold value.

In some embodiments, the data satisfies at least one of the following conditions: 1) the data is data of a first logical channel; wherein, the first logical channel can be understood as a specific logical channel, that is, the data is data of a specific logical channel; 2) the data delay satisfies a first requirement; wherein, the first requirement includes at least one of the following: there is a delay requirement, the delay requirement is less than or equal to a fifth threshold value, and the delay value is less than or equal to a sixth threshold value; 3) the data is data of the first logical channel and has arrived; 4) the data delay satisfies the first requirement and has arrived; 5) the data is data of the first logical channel and has arrived for a first duration; 6) the data delay satisfies the first requirement and has arrived for a first duration.

In some embodiments, the aforementioned latency includes at least one of the following: latency, remaining latency, remaining time of a PDCP discard timer, a PDCP discard timer for low PSI (PDU set important), a packet set delay budget (PSDB), a packet delay budget (PDB), latency requirements, and QoS configuration for latency.

In some embodiments, the first duration may be configured by the network, or pre-configured, or predefined, or determined by the terminal device.

In some embodiments, the network is configured with multiple sets, such as two sets of LCP mapping restriction configurations and/or two sets of LCH configuration parameters. Optionally, the multiple sets of LCP mapping restriction configurations may include a first LCP mapping restriction configuration and a second LCP mapping restriction configuration, and the multiple sets of LCH configuration parameters may include a first LCH configuration parameter and a second LCH configuration parameter. When the logical channel exists, or the data exists, or the data meets the conditions described above, or the logical channel meets the conditions described above, the terminal device uses another set of LCP mapping restriction configurations (such as the second LCP mapping restriction configuration) and/or another set of LCH configuration parameters (such as the second LCH configuration parameters). When the terminal device is initially configured, or receives RRC configuration, or receives updated LCH/LCP configuration, or the logical channel does not exist, or the data does not exist, or the data does not meet the conditions described above, or the logical channel does not meet the conditions described above, the terminal device uses the first set of LCP mapping restriction configurations (such as the first LCP mapping restriction configuration) and/or the first set of LCH configuration parameters (such as the first LCH configuration parameters). Optionally, the first set of LCP mapping restriction configurations mentioned above can also be regarded as the default LCP mapping restriction configurations, and the first set of LCH configuration parameters can also be regarded as the default LCH configuration parameters.

In some embodiments, the network configures multiple sets, such as two sets of LCP mapping restriction configurations, and/or two sets of LCH configuration parameters. Optionally, the multiple sets of LCP mapping restriction configurations may include a first LCP mapping restriction configuration and a second LCP mapping restriction configuration, and the multiple sets of LCH configuration parameters may include a first LCH configuration parameter and a second LCH configuration parameter. The terminal device uses the mapping restriction indicated by the network when the logical channel exists, or the data exists, or the data meets the conditions described above, or the logical channel meets the conditions described above. The configuration includes (e.g., a second LCP mapping restriction configuration) and/or network-indicated LCH configuration parameters (e.g., second LCH configuration parameters), or a specific LCP mapping restriction configuration (e.g., a second LCP mapping restriction configuration) and/or a specific LCH configuration parameter (e.g., second LCH configuration parameters). When the terminal device is initially configured, or receives RRC configuration, or receives updated LCH/LCP configuration, or the logical channel does not exist, or the data does not exist, or the data does not meet the conditions described above, or the logical channel does not meet the conditions described above, a first set of LCP mapping restriction configurations (e.g., a first LCP mapping restriction configuration) and/or a first set of LCH configuration parameters (e.g., a first LCH configuration parameter) is used. Optionally, the aforementioned first set of LCP mapping restriction configurations can also be considered as the default LCP mapping restriction configuration, and the first set of LCH configuration parameters can also be considered as the default LCH configuration parameters.

In some embodiments, the network device configures a set of LCP mapping restriction configurations and/or LCH configuration parameters, as well as changed values for these parameters. The terminal device uses the changed values of these parameters to determine the LCP mapping restriction configurations and/or LCH configuration parameter values when the logical channel exists, or the data exists, or the data meets the conditions described above, or the logical channel meets the conditions described above. The terminal device uses the set of LCP mapping restriction configurations and/or LCH configuration parameters when the terminal device is initially configured, or receives RRC configuration, or receives updated LCH/LCP configuration, or the logical channel does not exist, or the data does not exist, or the data does not meet the conditions described above, or the logical channel does not meet the conditions described above.

In some embodiments, the network device configures a set of LCP mapping restriction configurations and/or LCH configuration parameters. The terminal device uses this set of LCP mapping restriction configurations and/or LCH configuration parameters when: in the initial configuration, or upon receiving RRC configuration, or upon receiving an updated LCH/LCP configuration, or when the logical channel does not exist, or when the data does not exist, or when the data does not meet the conditions described above, or when the logical channel does not meet the conditions described above. When the logical channel exists, or when the data exists, or when the data meets the conditions described above, or when the logical channel meets the conditions described above, the terminal device modifies the values of the LCP mapping restriction and/or LCH configuration parameters (e.g., relaxing the LCP mapping restriction, modifying the LCH priority (modifying the priority to high, or higher than threshold 1, or between threshold 2 and threshold 3, or higher than a certain threshold but lower than the priority of SRB or MAC CE).

In some embodiments, the first information has at least one of the following functions: 1) indicating whether a configured or scheduled resource is a first resource; wherein, the first resource can be understood as a specific resource, that is, whether the configured or scheduled resource is a specific resource; 2) indicating whether the configured or scheduled resource carries first data or a first logical channel; wherein, the first data can be understood as specific data, and the first logical channel can be understood as a specific logical channel, that is, whether the configured or scheduled resource carries specific data or a specific logical channel; 3) determining the mapping between data and resources; 4) determining the mapping between logical channels and resources; 5) determining whether data can be transmitted or preferentially transmitted on the first resource; 6) determining whether the logical channel can be transmitted or preferentially transmitted on the first resource; 7) determining LCP mapping restrictions.

In some embodiments, where the first information indicates that the configured or scheduled resource is a first resource:

The aforementioned resources are used or used solely for carrying the aforementioned data or logical channels; or,

The aforementioned resources shall preferentially carry the aforementioned data or logical channels. Optionally, if there are remaining transmission resources after the aforementioned resources have carried the aforementioned data or logical channels, they may be used to carry other data or logical channels; or,

The aforementioned resources are carried by the first LCP process for the data or logical channel. For example, based on the latency of the data or logical channel, or based on the existence of the data or logical channel, the priority of the data or logical channel is adjusted, or the mapping restrictions of the logical channel are adjusted, or the available resources of the logical channel are allocated; or,

The aforementioned resources are subject to a first LCP mapping restriction. For example, based on the configured LCP mapping restriction, a logical channel cannot be transmitted using resources configured or scheduled by a specific CG or DG. However, if the first information indicates that the uplink grant is for the first resource, the uplink grant can carry that logical channel or can carry all logical channels with pending data transmission, or the configured LCP mapping restriction can be broken; or...

The aforementioned resources, if there are remaining transmission resources in the existing LCP process, will carry the aforementioned data or logical channels.

In some embodiments, where the first information indicates configured or scheduled resources, which are used or dedicated to carrying first data or a first logical channel:

The aforementioned resources are used or used solely for carrying the aforementioned data or logical channels; or,

The aforementioned resources shall preferentially carry the aforementioned data or logical channels. Optionally, if there are remaining transmission resources after the aforementioned resources have carried the aforementioned data or logical channels, they may be used to carry other data or logical channels; or,

The aforementioned resources are carried by the first LCP process for the data or logical channel. For example, based on the latency of the data or logical channel, or based on the existence of the data or logical channel, the priority of the data or logical channel is adjusted, or the mapping restrictions of the logical channel are adjusted, or the available resources of the logical channel are allocated; or,

The aforementioned resources are subject to a first LCP mapping restriction. For example, based on the configured LCP mapping restriction, a logical channel cannot be transmitted using resources configured or scheduled by a specific CG or DG. However, if the first information indicates that the uplink grant is for the first resource, the uplink grant may carry the logical channel or may carry all logical channels with data to be transmitted, or the configured LCP mapping restriction may be broken.

In some embodiments, when the first information is used to determine the mapping between the data and the resource, or to determine the mapping between the logical channel and the resource, or to determine whether the data can be transmitted or preferentially transmitted in the first resource, or to determine whether the logical channel can be transmitted or preferentially transmitted in the first resource, or to determine LCP mapping restrictions, and the first information appears, or the first information is a first value (e.g., the first value can be a specific value):

The aforementioned resources are used or used solely for carrying the aforementioned data or logical channels; or,

The aforementioned resources shall preferentially carry the aforementioned data or logical channels. Optionally, if there are remaining transmission resources after the aforementioned resources have carried the aforementioned data or logical channels, they may be used to carry other data or logical channels; or,

The aforementioned resources are carried by the first LCP process for the data or logical channel. For example, based on the latency of the data or logical channel, or based on the existence of the data or logical channel, the priority of the data or logical channel is adjusted, or the mapping restrictions of the logical channel are adjusted, or the available resources of the logical channel are allocated; or,

The aforementioned resources are subject to a first LCP mapping restriction. For example, based on the configured LCP mapping restriction, a logical channel cannot be transmitted using resources configured or scheduled by a specific CG or DG. However, if the first information indicates that the uplink grant is for the first resource, the uplink grant can carry that logical channel or can carry all logical channels with pending data transmission, or the configured LCP mapping restriction can be broken; or...

The aforementioned resources, if there are remaining transmission resources in the existing LCP process, will carry the aforementioned data or logical channels.

Using the above method, the communication device performs resource mapping operations related to data or logical channels based on the second rule and/or the first information, thereby mapping data or logical channels to appropriate resources for transmission and effectively supporting the transmission needs of different data.

Please refer to Figure 4, which shows a flowchart of a wireless communication method provided in another embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 410.

Step 410: The terminal device performs actions related to data transmission based on at least two objects that are associated or coordinated.

In some embodiments, the object can be any of the following: data stream, QoS stream, DRB, RLC entity, logical channel, or data packet. In some embodiments, the data packet can be any of the following: PDU, PDU set, or data burst. Additionally, the aforementioned data stream can be an SDF (Service Data Flow).

In some embodiments, performing data transmission-related actions includes at least one of the following: 1) adjusting the priorities of at least two objects to be the same or similar; 2) using a different set of logical channel priorities for at least two objects; 3) adjusting the priorities of at least two objects to a first priority, where the first priority is the highest priority within the first priority range; 4) adjusting the priorities of at least two objects to a second priority, where the second priority is a network-configured or predefined priority; 5) mapping at least two objects, or packets corresponding to at least two objects, to available configured or scheduled resources; 6) determining at least two objects, or packets corresponding to at least two objects, to relax or disregard configured LCP mapping restrictions; 7) determining at least two objects, or packets corresponding to at least two objects, to use a different set of LCP mapping restrictions.

In some embodiments, if the object is any of the following: data stream, QoS stream, DRB, RLC entity, logical channel, then the data transmission related behavior can be performed as one of 1) to 4) above.

In some embodiments, if the object is any of the following: data stream, QoS stream, DRB, RLC entity, logical channel, data packet, then the data transmission related behavior can be one of 1) to 4) above, or one of 5) to 7) above, or one of 1) to 4) above and one of 5) to 7) above, or one of 1) to 4) above and one of 5) and 6) to 7) above, or one of 1) to 4) above and 5), or one of 1) to 4) above and one of 6) to 7) above, or one of 5) and 6) to 7) above.

In some embodiments, for 1) above, the priority of at least two objects can be adjusted to a target priority, wherein the target priority can be one of the priorities of the at least two objects, that is, the priority of all other objects in the at least two objects except for one object is adjusted to be the same as the priority of the one object; or, the target priority can be another priority that is different from the priority of any of the at least two objects, that is, the priority of the at least two objects is adjusted to the other priority.

In some embodiments, for the “at least two objects” mentioned elsewhere in 1) to 7) above, except for “data packets corresponding to at least two objects”, the “object” is one of a data stream, QoS stream, DRB, RLC entity, logical channel, or data packet; the “object” in “data packets corresponding to at least two objects” is one of a data stream, QoS stream, DRB, RLC entity, or logical channel.

In some embodiments, for 5) above, at least two objects, or the data packets corresponding to at least two objects, are mapped to any available configuration or scheduled resource, or to the nearest available configuration or scheduled resource, or to an available configuration or scheduled resource with a specific identifier, or to an available configuration or scheduled resource of a specific type.

In some embodiments, for 2) above, the other set of logical channel priorities refers to a set of logical channel priorities other than those used for objects that are not associated or cooperative. This other set of logical channel priorities may be configured by the network, or pre-configured, or predefined, or determined by the terminal device.

In some embodiments, for 7) above, another set of LCP mapping restrictions refers to a set of LCP mapping restrictions other than those used for objects that do not have association or cooperation. This other set of LCP mapping restrictions may be determined by network configuration, pre-configuration, pre-definition, or by the end device.

In some embodiments, for 1) above, for data streams or QoS streams or DRBs or logical channels with association or coordination, if there are data packets with association or coordination requirements/information in the buffer (e.g., UE buffer) of the terminal device or in the data to be transmitted of the terminal device, or if there are data packets to be transmitted in the data streams or QoS streams or DRBs or logical channels with association or coordination requirements/information, then the terminal device will adjust the priority of the data streams or QoS streams or DRBs or logical channels with association or coordination to the same or similar priority.

In some embodiments, for 3) above, for data streams or QoS streams or DRBs or logical channels with association or coordination, if there are data packets with association or coordination requirements/information in the terminal device's buffer (e.g., UE buffer) or in the terminal device's data to be transmitted, Alternatively, if there are data packets to be transmitted in the associated or coordinated data stream, QoS stream, DRB, or logical channel, the terminal device will adjust the priority of the associated or coordinated data stream, QoS stream, DRB, or logical channel to the first priority, which is the highest priority within the first priority range. The first priority range can be the priority range of the data stream, QoS stream, DRB, or logical channel, or a priority range below a certain threshold, or a range below the priority of the SRB and/or a specific DRB. For example, the terminal device may adjust the priority of the associated or coordinated data stream, QoS stream, DRB, or logical channel to the highest priority, optionally, to the highest priority below a certain threshold, or to the highest priority within a certain range, or to the highest priority other than the priority of the SRB and/or a specific DRB.

In some embodiments, for 4) above, for data streams or QoS streams or DRBs or logical channels with association or cooperation, if there are data packets with association or cooperation requirements/information in the buffer (such as UE buffer) of the terminal device or in the data to be transmitted of the terminal device, or if there are data packets to be transmitted in the data streams or QoS streams or DRBs or logical channels with association or cooperation requirements/information, then the terminal device will adjust the priority of the data streams or QoS streams or DRBs or logical channels with association or cooperation to a second priority, where the second priority is a priority configured by the network or predefined.

In some embodiments, for 5) above, for data streams or QoS streams or DRBs or logical channels with association or coordination, if there are data packets with association or coordination requirements/information in the buffer (e.g., UE buffer) of the terminal device or in the data to be transmitted of the terminal device, or if there are data packets to be transmitted in the data streams or QoS streams or DRBs or logical channels with association or coordination requirements/information, then the terminal device will map the data streams or QoS streams or DRBs or logical channels with association or coordination, or the data packets corresponding to the aforementioned data streams or QoS streams or DRBs or logical channels with association or coordination, to any available configuration or scheduling resource, or to the nearest available configuration or scheduling resource, or to an available configuration or scheduling resource with a specific identifier, or to an available configuration or scheduling resource of a specific type.

In some embodiments, for 6) above, for data streams or QoS streams or DRBs or logical channels with association or cooperation, if there are data packets with association or cooperation requirements/information in the buffer (e.g., UE buffer) of the terminal device, or in the data to be transmitted of the terminal device, or if there are data packets to be transmitted in the data streams or QoS streams or DRBs or logical channels with association or cooperation requirements/information, then the terminal device determines that there are data streams or QoS streams or DRBs or logical channels with association or cooperation, or determines the data packets corresponding to the aforementioned data streams or QoS streams or DRBs or logical channels with association or cooperation, relaxes or does not comply with the configured LCP mapping restrictions, or uses another set of LCP mapping restrictions.

In some embodiments, the data transmission-related behavior is performed when at least two objects satisfy at least one of the following conditions: 1) at least two objects exist; 2) both at least two objects arrive; 3) both at least two objects are pending transmission; 4) both at least two objects are pending transmission, and the arrival time satisfies a second duration; 5) at least one of the at least two objects arrives; 6) the arrival of at least one of the at least two objects satisfies a third duration; 7) at least one of the at least two objects is pending transmission; 8) at least one of the at least two objects has been transmitted; 9) at least one of the at least two objects has been transmitted, and the transmission time satisfies a fourth duration; 10) at least one of the at least two objects has been transmitted, and at least one or all of the remaining objects have arrived. 11) At least one of the above at least two objects has been transmitted, and the transmission time satisfies the fourth duration, and at least one of the remaining objects has arrived or all of them have arrived; 12) At least one of the above at least two objects has been transmitted, and at least one of the remaining objects has arrived or all of them have arrived, and the arrival time of at least one of the remaining objects satisfies the fifth duration; 13) At least one of the above at least two objects has been transmitted, and the transmission time satisfies the fourth duration, and at least one of the remaining objects has arrived or all of them have arrived, and the arrival time of at least one of the remaining objects satisfies the sixth duration; 14) The delay difference between the above at least two objects satisfies the first condition; 15) There exists a data packet to be transmitted corresponding to the above at least two objects; 16) The delay difference between the data packets to be transmitted corresponding to the above at least two objects satisfies the first condition.

In some embodiments, the term "arrived" can be replaced with "waiting in the buffer" or "available". Optionally, "arrived" can mean arriving at the access layer, the PDCP layer, the RLC layer, or the MAC layer.

In some embodiments, for 4) above, both of the above at least two objects are to be transmitted, and the arrival time satisfies the second duration. The "arrival time" can be all the data packets in the at least two objects, the first data packet to arrive, or the last data packet to arrive.

In some embodiments, the second duration, third duration, fourth duration, fifth duration, sixth duration, and first condition described above may be configured by the network, or pre-configured, or pre-defined, or determined by the terminal device.

In some embodiments, the delay difference satisfies a first condition, including any one of the following: the delay difference is less than or equal to a first threshold; the delay difference is less than or equal to a tolerable delay threshold; the delay difference is less than or equal to a maximum tolerable delay threshold; the delay difference is less than or equal to a tolerable delay threshold minus a first value; the delay difference is less than or equal to a maximum tolerable delay threshold minus a second value.

In some embodiments, the delay difference can be any of the following: packet arrival delay difference, packet transmission delay difference, packet deletion delay difference, or packet arrival delay difference at the receiving end. The packet deletion delay difference can be determined based on the remaining time of the PDCP layer's discard timer. Optionally, the discard timer can be a PDCP discard timer, a PDCP discard timer for low PSI, or a discard timer from other PDCP layers.

In some embodiments, the delay is any one of the following: packet arrival delay, packet transmission delay, packet deletion delay, and packet arrival delay at the receiving end. The packet deletion delay can be based on the remaining time of the discard timer in the PDCP layer. The time interval is determined. Optionally, the discard timer can be a PDCP discard timer, a PDCP discard timer for low PSI, or a discard timer for other PDCP layers.

In some embodiments, the first threshold, the tolerance delay threshold, the maximum tolerance delay threshold, the first value, and the second value may be configured by the network, pre-configured, pre-defined, or determined by the terminal device.

In some embodiments, the presence of associated or coordinated data packets is determined by the Access Stratum (AS) of the terminal device based on higher-layer interactions or instructions, or based on information in the data packets, to determine whether a data packet is an associated data packet and/or to determine which data stream, QoS stream, DRB, or logical channel it is associated with.

In some embodiments, the latency difference of associated or coordinated data packets is determined by the access layer of the terminal device based on higher-layer interactions, higher-layer instructions, information in the data packets, or by the terminal device itself (such as the PDCP or RLC layer).

Using the above method, the terminal device performs data transmission-related actions based on at least two related or cooperative objects, which can ensure that related or cooperative data packets are transmitted together or as quickly as possible.

Please refer to Figure 5, which shows a flowchart of a wireless communication method provided in another embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 510.

Step 510: The network device obtains association or collaboration information, which is used to indicate at least two objects that are associated or collaborate.

In some embodiments, the network device is a base station.

In some embodiments, the object is any of the following: data stream, QoS stream, DRB, RLC entity, logical channel, or data packet.

In some embodiments, association or coordination information is reported by the terminal device to the network device. For example, in an uplink transmission scenario, the terminal device sends association or coordination information to the network device, which indicates at least two objects that are associated or coordinated with the terminal device.

In some embodiments, association or coordination information is sent from core network elements to network devices. For example, in an uplink transmission scenario, core network elements send association or coordination information to network devices, which indicates that the terminal device has at least two associated or coordinated objects. As another example, in a downlink transmission scenario, core network elements send association or coordination information to network devices, which indicates that the network device has at least two associated or coordinated objects.

In some embodiments, association or coordination information is used to indicate at least two data streams that are associated or coordinated. In this case, the association or coordination information may include identification information of at least two data streams that are associated or coordinated and/or QoS streams. There is a mapping relationship between QoS streams and data streams, and the corresponding data stream can be determined based on the identification information of the QoS stream.

In some embodiments, association or coordination information is used to indicate at least two QoS flows that are associated or coordinated. In this case, association or coordination information may include identification information of the at least two QoS flows that are associated or coordinated.

In some embodiments, association or collaboration information is used to indicate at least two DRBs that are associated or collaborate. In this case, association or collaboration information may include identification information of the at least two DRBs that are associated or collaborate.

In some embodiments, association or collaboration information is used to indicate at least two RLC entities that are associated or collaborate. In this case, association or collaboration information may include identification information of the at least two RLC entities that are associated or collaborate.

In some embodiments, association or coordination information is used to indicate at least two logical channels that are associated or coordinated. In this case, association or coordination information may include identification information of at least two logical channels that are associated or coordinated.

In some embodiments, association or coordination information is used to indicate at least two data packets that are associated or coordinated. In this case, association or coordination information may include identification information (or serial numbers) of the at least two data packets that are associated or coordinated.

In some embodiments, the associated or collaborative information may also include associated requirement information, such as at least one of the following: tolerance latency threshold, maximum tolerance latency threshold, etc. This application does not limit this information.

In some embodiments, a QoS stream can only be mapped to one data stream. That is, one data stream is mapped to one QoS stream, and for another data stream, that other data stream is mapped to another QoS stream.

In some embodiments, a QoS flow supports mapping one or more data flows. That is, one or more data flows can be mapped to the same QoS flow. Optionally, a QoS flow may contain packets with association or coordination requirements, or packets without association or coordination requirements. Optionally, a QoS flow may contain multiple packets with association or coordination requirements, but the association or coordination identifiers of the associated or coordinated packets are different. Optionally, associated or coordinated data flows can be mapped to one QoS flow or to different QoS flows. Optionally, a QoS flow may contain data flows with association or coordination requirements, or data flows without association or coordination requirements. Optionally, a QoS flow may contain multiple data flows with association or coordination requirements, but the association or coordination identifiers of the associated or coordinated data flows are different.

In some embodiments, the aforementioned association or collaboration is determined based on at least one of the following: the IP (Internet Protocol) 5-tuple of the data packet, and the association or collaboration identifier. Exemplarily, the IP 5-tuple may be an SDF filer. Exemplarily, the association or collaboration identifier is a multi-modal service ID, which indicates the existence of an association or collaboration.

In some embodiments, the association or coordination information acquired by the network device targets a second object, which can be any of the following: data flow, QoS flow, DRB, RLC entity, logical channel, or data packet. Optionally, the second object may be the same as or different from the object described above.

In some embodiments, the network device configures RRC parameters and/or allocates resources based on association or coordination information, and/or enables or disables the aforementioned data transmission-related behaviors based on association or coordination information. The configuration of RRC parameters and/or allocation of resources includes, but is not limited to, at least one of the following: logical channel parameters (such as priority), CG/DG resource configuration, LCP mapping restrictions, etc.

By using the above method, association or coordination information is sent to network devices, enabling the network devices to know at least two objects that are associated or coordinated, thereby allocating appropriate resources to the at least two objects that are associated or coordinated, and ensuring that data packets that are associated or coordinated are transmitted together or as quickly as possible.

Please refer to Figure 6, which shows a flowchart of a wireless communication method provided in another embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include the following step 610.

Step 610: The communication device processes the data packets based on the FEC information.

In some embodiments, the communication device may be a terminal device (i.e., UE) or a network device (such as a base station).

In some embodiments, FEC information is for a set of packets, which may be a PDU set or a data burst.

In some embodiments, FEC information is used to indicate at least one of the following: 1) enabling or disabling processing of data packets based on FEC information; 2) the minimum number of data packets required to recover or decode a set of data packets; 3) the minimum number of data packets tolerable for failure or loss for a set of data packets; 4) a first ratio, which is the ratio of the number of data packets required to recover or decode a set of data packets to the total number of data packets in the set of data packets; 5) a second ratio, which is the ratio of the minimum number of data packets tolerable for failure or loss for a set of data packets to the total number of data packets in the set of data packets; 6) data packets belonging to the source packet; and 7) data packets belonging to the repair packet.

In some embodiments, the FEC information includes at least one of the following: a first ratio, the minimum number of packets required to recover or decode the packet set, and the total number of packets in the packet set.

In some embodiments, the FEC information includes at least one of the following: the minimum number of data packets (or the number of source data packets) required to recover or decode the data packet set, the total number of data packets in the data packet set, and the number of redundant data packets (or the number of data packets to be recovered).

In some embodiments, the FEC information includes at least one of the following: identification information. The identification information is used to identify whether the data packet is a source packet or a repair packet. Further, it may also include: which source packets the repair packet is a repair packet for.

In some embodiments, FEC information is configured or indicated for a set of packets; or, FEC information is configured or indicated for a QoS flow; or, FEC information is configured or indicated separately for sets of packets of different importance (i.e., different PSIs (PDU set important)); or, FEC information is configured or indicated for multiple sets of packets with the same importance.

In some embodiments, the data packets are processed based on FEC information, including: starting a PDCP discard timer based on PDCP SDUs received from higher layers, or a PDCP discard timer for low PSI.

In some embodiments, the data packets are processed based on FEC information, including:

Based on FEC information, if a set of packets meets the second condition, delete the packets and/or their corresponding PDUs from that set of packets; or,

Based on FEC information, if a data packet set meets the second condition, delete the untransmitted data packets and/or their corresponding PDUs from that data packet set; or,

Based on FEC information, if a set of data packets meets the second condition, delete the data packets and/or their corresponding PDUs that were not successfully transmitted or did not receive ACK (Acknowledgement) feedback.

In some embodiments, the second condition includes at least one of the following: 1) a data packet loss of greater than or equal to a first proportion in the data packet set, where the first proportion is the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; 2) a drop timer corresponding to the data packet set times out; 3) a drop timer for at least one data packet in the data packet set times out; 4) the number of data packets in the data packet set that are neither lost nor timed out is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; 5) the number of data packets in the data packet set that are neither lost, successfully transmitted, or have received an ACK is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; 6) all source data packets in the data packet set are transmitted or successfully transmitted or have received an ACK feedback; 7) the data packet set contains timed-out or dropped data packets, and the timed-out or dropped data packets are neither transmitted nor successfully transmitted. 8) The packet set contains timed-out or dropped packets that were not transmitted, were not successfully transmitted, or did not receive an ACK, and their total number is greater than or equal to the minimum number of packets required to recover or decode the packet set; 9) The packet set contains timed-out or dropped packets that were not transmitted, were not successfully transmitted, or did not receive an ACK, and their total number is greater than or equal to the minimum number of packets that the packet set can tolerate for failure or loss; 10) The packet set contains timed-out or dropped packets that were not transmitted, were not successfully transmitted, or did not receive an ACK, and the packet includes at least one source packet; 11) The packet set contains lost or timed-out packets that include at least one source packet. 12) The data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include all recovered data packets.

In some embodiments, whether a data packet is lost depends on whether feedback and/or a timer expires. For example, it depends on whether there is a NACK feedback (1 or N) for the data packet, or a NACK feedback (1 or N) for the MAC PDU carrying the data packet. The timer can be a discard timer (PDCP discard timer, or PDCP discard timer for low PSI). Optionally, if an ACK is received before the timer expires, the data packet is considered not lost. Optionally, if a NACK or N NACKs are received before the timer expires, the data packet is considered lost.

In some embodiments, the second condition includes: a first proportion of data packets in the data packet set is lost, or the discard timer corresponding to the data packet set times out.

In some embodiments, the second condition includes: there exists a set of packets in which packets are lost, or whose drop timers expire, and the number of packets that have not expired or been lost is greater than or equal to the minimum number of packets required to recover or decode the set of packets.

In some embodiments, the second condition includes: there is a packet loss in a packet set, or its drop timer expires, and the timed-out or lost packets include one or W or all of the source packets. The value of W can be determined by network configuration, pre-configuration, pre-definition, or by the terminal device.

In some embodiments, the second condition includes: there is a set of packets in which packets are lost, or whose drop timers expire, and the timed-out or lost packets include all recoverable packets.

In some embodiments, the second condition includes: a greater than or equal to a first proportion of data packets in the data packet set are lost, or for a data packet set, there is a greater than or equal to a first proportion of data packet loss.

In some embodiments, the second condition includes: there exists a set of data packets in which the number of data packets that are neither lost nor timed out is greater than or equal to the minimum number of data packets required to recover or decode the set of data packets.

In some embodiments, the second condition includes: there exists a set of data packets in which the number of lost data packets is greater than or equal to the number of source data packets.

In some embodiments, the second condition includes: there exists a set of data packets in which the number of lost data packets is greater than or equal to the number of recovered data packets.

In some embodiments, the second condition includes: the timer for dropping packets in the packet set that is greater than or equal to the number of packets allowed to fail times out; or the packet set that is greater than or equal to the number of packets allowed to fail times out without receiving an ACK or receiving a NACK, or the packets being considered lost; or the packet set that is greater than or equal to the number of packets allowed to fail times out without receiving an ACK or receiving a NACK, or the packets being considered lost. Optionally, the number of packets allowed to fail is directly known or determined based on a failure rate or success rate. For example, the number of packets allowed to fail is notified. For example, the number of packets in the packet set minus the number of packets that need to succeed. For example, the failure rate multiplied by the number of packets in the packet set. For example, (1 - success rate) multiplied by the number of packets in the packet set.

In some embodiments, the second condition includes: the number of first data packets in the data packet set is greater than or equal to the number of data packets that need to be successfully transmitted; wherein the first data packet is a data packet that receives an ACK feedback, or a data packet that receives an ACK feedback before the corresponding discard timer expires, or a data packet that is successfully transmitted before the corresponding discard timer expires. Optionally, the number of data packets that need to be successfully transmitted is directly known, or determined based on a failure rate or a success rate. For example, the number of data packets that need to be successfully transmitted is notified, or the number of source data packets is notified. For example, the number of data packets in the data packet set minus the number of data packets allowed to fail. For example, the success rate multiplied by the number of data packets in the data packet set. For example, (1 - failure rate) multiplied by the number of data packets in the data packet set.

In some embodiments, for a set of data packets, if the discard timer for at least N data packets times out, all data packets in the set are deleted, where N is the number of data packets that need to be successfully transmitted.

In some embodiments, for a set of data packets, if the timers for at least M data packets expire, all data packets in the set are deleted, where M is the number of data packets allowed to fail.

In some embodiments, processing data packets based on FEC information includes: based on FEC information, if a data packet set does not meet the second condition described above, not deleting data packets and/or their corresponding PDUs in the data packet set; or, based on FEC information, if a data packet set does not meet the second condition described above, not deleting untransmitted data packets and/or their corresponding PDUs in the data packet set; or, based on FEC information, if a data packet set does not meet the second condition described above, not deleting data packets and/or their corresponding PDUs in the data packet set that were not successfully transmitted or for which no ACK feedback was received.

In some embodiments, processing data packets based on FEC information includes: based on FEC information, if a set of data packets satisfies a third condition, prioritizing the transmission of data packets in that set of data packets.

In some embodiments, the third condition includes at least one of the following: 1) In the data packet set, there are data packets with a transmission delay greater than or equal to a first proportion, the first proportion being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; 2) The number of data packets that have been transmitted in the data packet set is less than the minimum number of data packets required to recover or decode the data packet set; 3) The source data packets in the data packet set need to be transmitted.

In some embodiments, preferential transmission includes at least one of the following: 1) adjusting the priority of the logical channel corresponding to the data packet; 2) using a different set of logical channel priorities for the logical channel corresponding to the data packet; 3) relaxing or not adhering to the configured LCP mapping restrictions; 4) 5) Use another set of LCP mapping restrictions; 6) Transmit the data packet using the first resource, where the first resource can be understood as a specific resource, that is, transmit the data packet using a specific resource; 7) Use the first LCP procedure, where the first LCP procedure can be understood as a specific LCP procedure, that is, use a specific LCP procedure, for example, based on the delay of the above data or logical channel, based on the existence of the above data or logical channel, adjust the priority of the above data or logical channel, or adjust the mapping restrictions of the above logical channel, or perform the allocation of available resources for the logical channel.

By using the above method to process data packets in the data packet set based on FEC information, it is possible to ensure that data packets in the same data packet set are transmitted together or as quickly as possible.

The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

Please refer to Figure 7, which shows a block diagram of a wireless communication device according to an embodiment of this application. This device has the functionality to implement the method example described above; the functionality can be implemented in hardware or by hardware executing corresponding software. This device can be the communication device described above, or it can be disposed within a communication device. As shown in Figure 7, the device 700 may include a processing module 710.

In some embodiments, the processing module 710 is configured to perform actions related to the reordering timer by the PDCP layer or entity.

In some embodiments, the processing module 710 is used to determine the value of the reordering timer; and/or to process data packets based on the reordering timer.

In some embodiments, the processing module 710 is used to determine the value of the reordering timer based on a first rule, wherein the first rule is related to the RLC transmission mode corresponding to the data packet.

In some embodiments, when the RLC transmission mode corresponding to the data packet includes at least AM, the reordering timer takes a first value; and/or, when the RLC transmission mode corresponding to the data packet includes only UM, the reordering timer takes a second value.

In some embodiments, the RLC transmission mode corresponding to the data packet is indicated by at least one of the following methods: control PDU, data PDU.

In some embodiments, the processing module 710 is configured to deliver the data packet to a higher layer if the reordering timer times out.

In some embodiments, the PDCP layer or entity is associated with multiple RLC entities, and at least two RLC entities correspond to different RLC transmission modes.

In some embodiments, when the communication device is a terminal device, the RLC transmission mode corresponding to each of the plurality of RLC entities is configured by the network or determined by the terminal device; or, when the communication device is a network device, the RLC transmission mode corresponding to each of the plurality of RLC entities is determined by the network device.

In some embodiments, the RLC transmission mode corresponding to each of the plurality of RLC entities is related to at least one of the following factors: whether the ability to use different RLC transmission modes for different RLC entities is supported; whether to select different RLC entities to use different RLC transmission modes; the selected RLC transmission mode corresponding to each of the plurality of RLC entities; service characteristics; and the RLC transmission mode configured for use by different RLC entities.

In some embodiments, the processing module 710 is configured to perform resource mapping operations related to data or logical channels based on a second rule and/or first information.

In some embodiments, performing resource mapping operations related to data or logical channels includes at least one of the following: determining a mapping between the data and resources; determining a mapping between the logical channel and resources; determining LCP mapping constraints; determining whether the data can be transmitted or preferentially transmitted via a first resource; and determining whether the logical channel can be transmitted or preferentially transmitted via a first resource.

In some embodiments, the logical channel satisfies at least one of the following conditions: the index of the logical channel is a first index; the priority of the logical channel is a first priority; the latency corresponding to the logical channel satisfies a first condition; and the logical channel carries data whose latency satisfies a second condition.

In some embodiments, the data satisfies at least one of the following conditions: the data is data of a first logical channel; the delay of the data satisfies a first requirement; the data is data of a first logical channel and has arrived; the delay of the data satisfies the first requirement and has arrived; the data is data of a first logical channel and has arrived for a first duration; the delay of the data satisfies the first requirement and has arrived for a first duration.

In some embodiments, the latency includes at least one of the following: latency, remaining latency, remaining time of the PDCP drop timer, PDCP drop timer for a set of low-importance PDUs, packet set latency budget, packet latency budget, latency requirement, and QoS configuration for latency.

In some embodiments, the first information has at least one of the following functions: indicating whether a configured or scheduled resource is a first resource; indicating whether a configured or scheduled resource carries first data or a first logical channel; determining the mapping between the data and the resource; determining the mapping between the logical channel and the resource; determining whether the data can be transmitted or preferentially transmitted on the first resource; determining whether the logical channel can be transmitted or preferentially transmitted on the first resource; and determining LCP mapping restrictions.

In some embodiments, where the first information indicates that the configured or scheduled resource is the first resource: the resource is used for or The resource may be used solely to carry the data or the logical channel; or, the resource may be used preferentially to carry the data or the logical channel; or, the resource may be used to carry the data or the logical channel using a first LCP process; or, the resource may be used to apply a first LCP mapping restriction; or, the resource may be used to carry the data or the logical channel if there are remaining transmission resources according to the existing LCP process.

In some embodiments, where the first information indicates the configuration or scheduling of resources, and the resources are used or dedicated to carrying the first data or the first logical channel: the resources are used or only used to carry the data or the logical channel; or, the resources preferentially carry the data or the logical channel; or, the resources carry the data or the logical channel using a first LCP process; or, the resources are subject to a first LCP mapping restriction.

In some embodiments, when the first information is used to determine the mapping between the data and the resource, or to determine the mapping between the logical channel and the resource, or to determine whether the data can be transmitted or preferentially transmitted using the first resource, or to determine whether the logical channel can be transmitted or preferentially transmitted using the first resource, or to determine LCP mapping limitations, and the first information occurs, or the first information is a first value: the resource is used or only used to carry the data or the logical channel; or, the resource preferentially carries the data or the logical channel; or, the resource carries the data or the logical channel using a first LCP procedure; or, the resource uses a first LCP mapping limitation; or, the resource carries the data or the logical channel if there are remaining transmission resources according to the existing LCP procedure. In some embodiments, the first information is carried in configuration or scheduling information; or, the first information is for CG or DG.

In some embodiments, the processing module 710 is used to perform data transfer-related actions based on at least two objects that are associated or cooperative.

In some embodiments, the object is any one of the following: data stream, QoS stream, DRB, RLC entity, logical channel, data packet.

In some embodiments, performing data transmission-related actions includes at least one of the following: adjusting the priorities of the at least two objects to be the same or similar; using another set of logical channel priorities for the at least two objects; adjusting the priorities of the at least two objects to a first priority, the first priority being the highest priority within a first priority range; adjusting the priorities of the at least two objects to a second priority, the second priority being a network-configured or predefined priority; mapping the at least two objects, or the data packets corresponding to the at least two objects, to available configured or scheduled resources; determining that the at least two objects, or the data packets corresponding to the at least two objects, relax or disregard configured LCP mapping restrictions; determining that the at least two objects, or the data packets corresponding to the at least two objects, use another set of LCP mapping restrictions.

In some embodiments, the data transmission-related behavior is performed if at least one of the following conditions is met by the at least two objects: the at least two objects exist; both at least two objects have arrived; both at least two objects are pending transmission; both at least two objects are pending transmission and the arrival time satisfies a second duration; at least one of the at least two objects has arrived; the arrival time of at least one of the at least two objects satisfies a third duration; at least one of the at least two objects is pending transmission; at least one of the at least two objects has been transmitted; at least one of the at least two objects has been transmitted and the transmission time satisfies a fourth duration; at least one of the at least two objects has been transmitted, and at least one or all of the remaining objects have arrived. At least one of the at least two objects has been transmitted, and the transmission time satisfies the fourth duration; at least one of the remaining objects has arrived or all of them have arrived; at least one of the at least two objects has been transmitted, and at least one of the remaining objects has arrived or all of them have arrived; the arrival time of at least one of the remaining objects satisfies the fifth duration; at least one of the at least two objects has been transmitted, and the transmission time satisfies the fourth duration; at least one of the remaining objects has arrived or all of them have arrived; the arrival time of at least one of the remaining objects satisfies the sixth duration; the delay difference between the at least two objects satisfies the first condition; there exists a data packet to be transmitted corresponding to the at least two objects; the delay difference between the data packets to be transmitted corresponding to the at least two objects satisfies the first condition.

In some embodiments, the delay difference satisfies a first condition, including any one of the following: the delay difference is less than or equal to a first threshold; the delay difference is less than or equal to a tolerable delay threshold; the delay difference is less than or equal to a maximum tolerable delay threshold; the delay difference is less than or equal to a tolerable delay threshold minus a first value; the delay difference is less than or equal to a maximum tolerable delay threshold minus a second value.

In some embodiments, the delay difference is any one of the following: data packet arrival delay difference, data packet transmission delay difference, data packet deletion delay difference, and data packet arrival delay difference at the receiving end; and/or, the delay is any one of the following: data packet arrival delay, data packet transmission delay, data packet deletion delay, and data packet arrival delay at the receiving end.

In some embodiments, the processing module 710 is used to obtain association or collaboration information, which is used to indicate at least two objects that are associated or collaborated.

In some embodiments, the object is any one of the following: data stream, QoS stream, DRB, RLC entity, logical channel, data packet.

In some embodiments, a QoS flow can only map one data flow, or a QoS flow can map one or more data flows.

In some embodiments, the association or collaboration is determined based on at least one of the following: the IP 5-tuple of the data packet, the association or collaboration identifier.

In some embodiments, the association or collaboration information is reported by the terminal device to the network device, and/or sent by the core network element to the network device.

In some embodiments, the associated or collaborative information is directed to a second object, which is any one of the following: data stream, QoS stream, DRB, RLC entity, logical channel, or data packet.

In some embodiments, the processing module 710 is further configured to configure Radio Resource Control (RRC) parameters and/or allocate resources based on the association or coordination information; and/or to enable or disable the execution of data transmission-related behaviors based on the association or coordination information.

In some embodiments, the processing module 710 is used to process data packets based on FEC information.

In some embodiments, the FEC information is used to indicate at least one of the following: enabling or disabling the processing of data packets based on the FEC information; the minimum number of data packets required to recover or decode the data packet set; the minimum number of data packets tolerating failure or loss for the data packet set; a first ratio, which is the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a second ratio, which is the ratio of the minimum number of data packets tolerating failure or loss for the data packet set to the total number of data packets in the data packet set; data packets belonging to the source data packet; and data packets belonging to the recovery data packet.

In some embodiments, the FEC information is configured or indicated for a set of packets; or, the FEC information is configured or indicated for a QoS flow; or, the FEC information is configured or indicated for separate sets of packets of different importance; or, the FEC information is configured or indicated for multiple sets of packets with the same importance; wherein the set of packets is a data burst or a set of PDUs.

In some embodiments, the processing module 710 is configured to: based on the FEC information, delete data packets and/or their corresponding PDUs in a data packet set if a data packet set meets the second condition; or, based on the FEC information, delete untransmitted data packets and/or their corresponding PDUs in a data packet set if a data packet set meets the second condition; or, based on the FEC information, delete data packets and/or their corresponding PDUs in a data packet set that were not successfully transmitted or did not receive ACK feedback if a data packet set meets the second condition.

In some embodiments, the second condition includes at least one of the following: a data packet loss rate greater than or equal to a first proportion in the data packet set, where the first proportion is the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a timer for discarding the data packet set times out; a timer for discarding at least one data packet in the data packet set times out; the number of data packets in the data packet set that are neither lost nor timed out is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; the number of data packets in the data packet set that are neither lost, successfully transmitted, or have received an ACK is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; all source data packets in the data packet set are transmitted or successfully transmitted or have received an ACK feedback; the data packet set contains timed-out or discarded data packets, and the total number of timed-out or discarded data packets is greater than or equal to the first proportion, where the first proportion is the ratio of the number of data packets required to recover or decode the data packet set. The data packet set is defined as follows: the total number of data packets in the data packet set minus the minimum number of data packets required to recover or decode the data packet set; the data packet set contains timed-out or dropped data packets, which are either not transmitted, not successfully transmitted, or do not receive ACK feedback, and their total number is greater than or equal to the minimum number of failed or lost data packets that the data packet set can tolerate; the data packet set contains timed-out or dropped data packets, which are either not transmitted, not successfully transmitted, or do not receive ACK feedback, and the data packet includes at least one source data packet; the data packet set contains timed-out or dropped data packets, which are either not transmitted, not successfully transmitted, or do not receive ACK feedback, and the data packet includes all recovery data packets; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include at least one source data packet; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include all recovery data packets.

In some embodiments, the processing unit 710 is configured to, based on the FEC information, prioritize the transmission of data packets in a data packet set if a data packet set satisfies a third condition.

In some embodiments, the third condition includes at least one of the following: in the data packet set, there are data packets with a transmission delay greater than or equal to a first proportion, the first proportion being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; the number of data packets already transmitted in the data packet set is less than the minimum number of data packets required to recover or decode the data packet set; and the source data packets in the data packet set need to be transmitted.

In some embodiments, the priority transmission includes at least one of the following: adjusting the priority of the logical channel corresponding to the data packet; using a different set of logical channel priorities for the logical channel corresponding to the data packet; relaxing or not adhering to configured LCP mapping restrictions; using a different set of LCP mapping restrictions; transmitting the data packet using a first resource; and using a first LCP procedure.

It should be noted that the above embodiments only illustrate the division of the above functional modules when implementing the device. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here. For details not described in detail in the apparatus embodiments, please refer to the above method embodiments.

Please refer to Figure 8, which shows a schematic diagram of a communication device provided in one embodiment of this application. This communication device can be the aforementioned terminal device or network device. The communication device 800 may include a processor 801, a transceiver 802, and a memory 803. The processor 801 is used to implement various processing functions of the communication device 800, such as implementing the functions of the aforementioned processing modules, generating information to be sent, processing received information, controlling transmission and/or reception, etc. The transceiver 802 is used to implement transmission and/or reception functions.

The processor 801 includes one or more processing cores. The processor 801 executes various functional applications and information processing by running software programs and modules. The transceiver 802 may include a receiver and a transmitter; for example, the receiver and transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna. The memory 803 may be connected to the processor 801 and the transceiver 802. The memory 803 can be used to store computer programs executed by the processor, and the processor 801 executes these computer programs to implement the various steps in the above method embodiments.

In some embodiments, processor 801 is used to perform actions related to the reordering timer by the PDCP layer or entity.

In some embodiments, the processor 801 is configured to perform resource mapping operations related to data or logical channels based on a second rule and/or first information.

In some embodiments, processor 801 is used to perform data transfer-related actions based on at least two objects that are associated or cooperative.

In some embodiments, processor 801 is configured to acquire association or collaboration information, which is used to indicate at least two objects that are associated or collaborated.

In some embodiments, the processor 801 is used to process data packets based on FEC information.

For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

Furthermore, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, statically accessible memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

This application embodiment also provides a computer-readable storage medium storing a computer program for execution by a processor to implement the aforementioned wireless communication method. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

This application also provides a chip, which includes programmable logic circuits and/or program instructions, and is used to implement the above-described wireless communication method when the chip is running.

This application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-described wireless communication method.

It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

In some embodiments of this application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

In some embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as BLE protocol, Wi-Fi protocol, and related protocols applied in future communication systems. This application does not limit the scope of these protocols.

In this article, "multiple" refers to two or more. "And/or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and/or B can represent: A alone, A and B simultaneously, or B alone. The character "/" generally indicates that the preceding and following related objects have an "or" relationship.

In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims (84)

A wireless communication method, characterized in that the method is executed by a communication device, the method comprising: The Packet Data Convergence Protocol (PDCP) layer or entity performs actions related to the reordering timer. The method according to claim 1, wherein performing the actions related to the reordering timer includes: determining the value of the reordering timer; and/or processing data packets based on the reordering timer. The method according to claim 2, wherein determining the value of the reordering timer includes: determining the value of the reordering timer based on a first rule, wherein the first rule is related to the Radio Link Control (RLC) transmission mode corresponding to the data packet. According to the method of claim 3, the reordering timer is set to a first value when the RLC transmission mode corresponding to the data packet includes at least the acknowledged mode AM; and/or, the reordering timer is set to a second value when the RLC transmission mode corresponding to the data packet includes only the unacknowledged mode UM. According to the method of claim 3 or 4, the RLC transmission mode corresponding to the data packet is indicated by at least one of the following methods: Control Protocol Data Unit (PDU) and Data PDU. The method according to any one of claims 2 to 5, wherein processing the data packet based on the reordering timer includes: submitting the data packet to a higher layer if the reordering timer times out. The method according to any one of claims 1 to 6 is characterized in that the PDCP layer or entity is associated with multiple RLC entities, and at least two RLC entities correspond to different RLC transmission modes. According to the method of claim 7, wherein, when the communication device is a terminal device, the RLC transmission mode corresponding to each of the plurality of RLC entities is configured by the network or determined by the terminal device; or, when the communication device is a network device, the RLC transmission mode corresponding to each of the plurality of RLC entities is determined by the network device. The method according to claim 7 or 8 is characterized in that the RLC transmission mode corresponding to each of the plurality of RLC entities is related to at least one of the following factors: whether the ability to use different RLC transmission modes for different RLC entities is supported; whether different RLC entities are selected to use different RLC transmission modes; the selected RLC transmission mode corresponding to each of the plurality of RLC entities; service characteristics; and the RLC transmission mode used by the different RLC entities configured. A wireless communication method, characterized in that the method is executed by a communication device, the method comprising: Based on the second rule and/or the first information, perform resource mapping operations related to data or logical channels. The method according to claim 10, wherein performing the resource mapping operation related to data or logical channel includes at least one of the following: determining a mapping between the data and resources; determining a mapping between the logical channel and resources; determining a logical channel priority (LCP) mapping limit; determining whether the data can be transmitted in the first resource or with priority; and determining whether the logical channel can be transmitted in the first resource or with priority. According to the method of claim 10 or 11, the logical channel satisfies at least one of the following conditions: the index of the logical channel is a first index; the priority of the logical channel is a first priority; the delay corresponding to the logical channel satisfies a first condition; and the logical channel carries data whose delay satisfies a second condition. The method according to any one of claims 10 to 12, characterized in that the data satisfies at least one of the following conditions: the data is data of a first logical channel; the delay of the data satisfies a first requirement; the data is data of a first logical channel and has arrived; the delay of the data satisfies the first requirement and has arrived; the data is data of a first logical channel and has arrived for a first duration; the delay of the data satisfies the first requirement and has arrived for a first duration. The method according to claim 12 or 13 is characterized in that the delay includes at least one of the following: delay, remaining delay, remaining time of the Packet Data Convergence Protocol (PDCP) drop timer, PDCP drop timer for low-importance Protocol Data Unit (PDU) sets, packet set delay budget, packet delay budget, delay requirement, and QoS configuration for delay. The method according to any one of claims 10 to 14, wherein the first information has at least one of the following functions: indicating whether the configured or scheduled resource is a first resource; indicating whether the configured or scheduled resource carries first data or a first logical channel; determining the mapping between the data and the resource; determining the mapping between the logical channel and the resource; determining whether the data can be transmitted or preferentially transmitted on the first resource; determining whether the logical channel can be transmitted or preferentially transmitted on the first resource; and determining LCP mapping restrictions. According to the method of claim 15, wherein when the first information indicates that the configured or scheduled resource is the first resource: the resource is used or only used to carry the data or the logical channel; or, the resource preferentially carries the data or the logical channel; or, the resource carries the data or the logical channel using a first LCP process; or, the resource is subject to a first LCP mapping restriction; or, the resource carries the data or the logical channel if there are remaining transmission resources according to the existing LCP process. The method according to claim 15 or 16 is characterized in that, when the first information indicates the configuration or scheduling of resources, and the resources are used or dedicated to carrying the first data or the first logical channel: the resources are used or only used to carry the data or the logical channel; or, the resources preferentially carry the data or the logical channel; or, the resources carry the data or the logical channel using a first LCP process; or, the resources are subject to a first LCP mapping restriction. The method according to any one of claims 15 to 17, characterized in that, when the first information is used to determine the mapping between the data and the resource, or to determine the mapping between the logical channel and the resource, or to determine whether the data can be transmitted or preferentially transmitted using the first resource, or to determine whether the logical channel can be transmitted or preferentially transmitted using the first resource, or to determine LCP mapping restrictions, and the first information occurs, or the first information is a first value: the resource is used or only used to carry the data or the logical channel; or, the resource preferentially carries the data or the logical channel; or, the resource carries the data or the logical channel using a first LCP process; or, the resource uses a first LCP mapping restriction; or, the resource carries the data or the logical channel if there are remaining transmission resources according to the existing LCP process. The method according to any one of claims 10 to 18, wherein the first information is carried in configuration or scheduling information; or, the first information is for configuration authorization CG or dynamic authorization DG. A wireless communication method, characterized in that the method is executed by a terminal device, the method comprising: Perform data transfer-related actions based on at least two related or collaborative objects. The method according to claim 20 is characterized in that the object is any one of the following: data stream, Quality of Service (QoS) stream, Data Radio Bearer (DRB), Radio Link Control (RLC) entity, logical channel, and data packet. The method according to claim 20, wherein performing the data transmission related actions includes at least one of the following: adjusting the priorities of the at least two objects to be the same or similar; using another set of logical channel priorities for the at least two objects; adjusting the priorities of the at least two objects to a first priority, the first priority being the highest priority within the first priority range; adjusting the priorities of the at least two objects to a second priority, the second priority being a network-configured or predefined priority; mapping the at least two objects, or the data packets corresponding to the at least two objects, to available configured or scheduled resources; determining that the at least two objects, or the data packets corresponding to the at least two objects, relax or disregard configured LCP mapping restrictions; determining that the at least two objects, or the data packets corresponding to the at least two objects, use another set of LCP mapping restrictions. The method according to claim 20 is characterized in that, when the at least two objects satisfy at least one of the following conditions, the data transmission related behavior is performed: the at least two objects exist; both at least two objects have arrived; both at least two objects are pending transmission; both at least two objects are pending transmission and the arrival time satisfies a second duration; at least one of the at least two objects has arrived; the arrival of at least one of the at least two objects satisfies a third duration; at least one of the at least two objects is pending transmission; at least one of the at least two objects has been transmitted; at least one of the at least two objects has been transmitted and the transmission time satisfies a fourth duration; at least one of the at least two objects has been transmitted and at least one of the remaining objects has arrived. The following conditions must be met: 1. All of the remaining objects have arrived; 2. At least one of the at least two objects has been transmitted, and the transmission time satisfies the fourth duration; 3. At least one of the remaining objects has arrived, or all of them have arrived; 4. The delay difference between the at least two objects satisfies the first condition; 5. There exists a data packet to be transmitted corresponding to the at least two objects; 6. The delay difference between the data packets to be transmitted corresponding to the at least two objects satisfies the first condition. According to the method of claim 23, the delay difference satisfies a first condition, including any one of the following: the delay difference is less than or equal to a first threshold; the delay difference is less than or equal to a tolerable delay threshold; the delay difference is less than or equal to a maximum tolerable delay threshold; the delay difference is less than or equal to a tolerable delay threshold minus a first value; the delay difference is less than or equal to a maximum tolerable delay threshold minus a second value. The method according to claim 23 or 24 is characterized in that the delay difference is any one of the following: data packet arrival delay difference, data packet transmission delay difference, data packet deletion delay difference, data packet arrival delay difference at the receiving end; and/or, the delay is any one of the following: data packet arrival delay, data packet transmission delay, data packet deletion delay, data packet arrival delay at the receiving end. A wireless communication method, characterized in that the method is executed by a network device, the method comprising: Obtain association or collaboration information, which is used to indicate at least two objects that are associated or collaborated. The method according to claim 26 is characterized in that the object is any one of the following: data stream, Quality of Service (QoS) stream, Data Radio Bearer (DRB), Radio Link Control (RLC) entity, logical channel, and data packet. The method according to claim 26 or 27 is characterized in that a QoS stream supports mapping only one data stream, or a QoS stream supports mapping one or more data streams. The method according to any one of claims 26 to 28, wherein the association or coordination is determined based on at least one of the following: the Internet Protocol IP 5-tuple of the data packet, and the association or coordination identifier. The method according to any one of claims 26 to 29, wherein the association or coordination information is reported by the terminal device to the network device, and/or sent by the core network element to the network device. The method according to claim 30 is characterized in that the object of the association or coordination information is a second object, and the second object is any one of the following: data stream, QoS stream, DRB, RLC entity, logical channel, data packet. The method according to any one of claims 26 to 31, characterized in that the method further comprises: configuring Radio Resource Control (RRC) parameters and/or allocating resources according to the association or coordination information; and/or enabling or de-enabling the performance of data transmission-related behaviors according to the association or coordination information. A wireless communication method, characterized in that the method is executed by a communication device, the method comprising: Data packets are processed based on Forward Error Correction (FEC) information. The method according to claim 33, wherein the FEC information is used to indicate at least one of the following: enabling or disabling the processing of data packets based on the FEC information; the minimum number of data packets required to recover or decode the data packet set; the minimum number of data packets tolerating failure or loss for the data packet set; a first ratio, the first ratio being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a second ratio, the second ratio being the ratio of the minimum number of data packets tolerating failure or loss for the data packet set to the total number of data packets in the data packet set; data packets belonging to the source data packet; and data packets belonging to the recovered data packet. According to the method of claim 33 or 34, the FEC information is configured or indicated for a set of data packets; or, the FEC information is configured or indicated for a Quality of Service (QoS) flow; or, the FEC information is configured or indicated for data packet sets of different importance respectively; or, the FEC information is configured or indicated for multiple data packet sets of equal importance; wherein the data packet set is a data burst or a set of Protocol Data Units (PDUs). The method according to any one of claims 33 to 35, characterized in that, processing the data packets based on FEC information includes: based on the FEC information, deleting data packets and/or their corresponding PDUs from a data packet set if a data packet set satisfies a second condition; or, based on the FEC information, deleting untransmitted data packets and/or their corresponding PDUs from a data packet set if a data packet set satisfies the second condition; or, based on the FEC information, deleting data packets and/or their corresponding PDUs from a data packet set that were not successfully transmitted or did not receive a positive ACK feedback from a data packet set if a data packet set satisfies the second condition. According to the method of claim 36, the second condition includes at least one of the following: a data packet loss rate greater than or equal to a first proportion in the data packet set, where the first proportion is the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a timer for discarding the data packet set times out; a timer for discarding at least one data packet in the data packet set times out; the number of data packets in the data packet set that are neither lost nor timed out is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; the number of data packets in the data packet set that are neither lost, successfully transmitted, or have received an ACK is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; all source data packets in the data packet set are transmitted or successfully transmitted or have received an ACK feedback; the data packet set contains timed-out or discarded data packets, and the timed-out or discarded data packets are neither transmitted, successfully transmitted, nor have received an ACK feedback, and their total number is greater than [a certain number]. Or equal to, the total number of data packets in the data packet set minus the minimum number of data packets required to recover or decode the data packet set; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and their total number is greater than or equal to, the minimum number of data packets that the data packet set can tolerate failure or loss; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and the data packet includes at least one source data packet; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and the data packet includes all recovery data packets; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include at least one source data packet; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include all recovery data packets. The method according to any one of claims 33 to 37, wherein processing the data packets based on FEC information includes: prioritizing the transmission of data packets in a data packet set if the data packet set satisfies a third condition based on the FEC information. The method according to claim 38, wherein the third condition includes at least one of the following: in the data packet set, there are data packets with a transmission delay greater than or equal to a first proportion, the first proportion being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; the number of data packets already transmitted in the data packet set is less than the minimum number of data packets required to recover or decode the data packet set; and the source data packets in the data packet set need to be transmitted. The method according to claim 38 or 39 is characterized in that the priority transmission includes at least one of the following methods: adjusting the priority of the logical channel corresponding to the data packet; using another set of logical channel priorities for the logical channel corresponding to the data packet; relaxing or not complying with the configured LCP mapping restrictions; using another set of LCP mapping restrictions; transmitting the data packet using a first resource; and using a first logical channel priority LCP procedure. A wireless communication device, characterized in that the device comprises: The processing module is used by the Packet Data Convergence Protocol (PDCP) layer or entity to perform behaviors related to the reordering timer. The apparatus according to claim 41, wherein performing the actions related to the reordering timer includes: determining the value of the reordering timer; and/or processing data packets based on the reordering timer. The apparatus according to claim 42, wherein determining the value of the reordering timer includes: determining the value of the reordering timer based on a first rule, wherein the first rule is related to the Radio Link Control (RLC) transmission mode corresponding to the data packet. The apparatus according to claim 43 is characterized in that, when the RLC transmission mode corresponding to the data packet includes at least the acknowledged mode AM, the reordering timer takes the value of a first value; and/or, when the RLC transmission mode corresponding to the data packet includes only the unacknowledged mode UM, the reordering timer takes the value of a second value. The apparatus according to claim 43 or 44 is characterized in that the RLC transmission mode corresponding to the data packet is indicated by at least one of the following methods: Control Protocol Data Unit (PDU) and Data PDU. The apparatus according to any one of claims 42 to 45, wherein processing the data packet based on the reordering timer includes: delivering the data packet to a higher layer if the reordering timer times out. The apparatus according to any one of claims 41 to 46 is characterized in that the PDCP layer or entity is associated with multiple RLC entities, and at least two RLC entities correspond to different RLC transmission modes. The apparatus according to claim 47 is characterized in that, when the communication device is a terminal device, the RLC transmission mode corresponding to each of the plurality of RLC entities is configured by the network or determined by the terminal device; or, when the communication device is a network device, the RLC transmission mode corresponding to each of the plurality of RLC entities is determined by the network device. The apparatus according to claim 47 or 48 is characterized in that the RLC transmission mode corresponding to each of the plurality of RLC entities is related to at least one of the following factors: whether the ability to use different RLC transmission modes for different RLC entities is supported; whether different RLC entities are selected to use different RLC transmission modes; the selected RLC transmission mode corresponding to each of the plurality of RLC entities; service characteristics; and the RLC transmission mode configured for use by different RLC entities. A wireless communication device, characterized in that the device comprises: The processing module is used to perform resource mapping operations related to data or logical channels based on the second rule and/or the first information. The apparatus according to claim 50, wherein performing the resource mapping operation related to data or logical channels includes at least one of the following: determining a mapping between the data and resources; determining a mapping between the logical channels and resources; determining a logical channel priority (LCP) mapping limit; determining whether the data can be transmitted via a first resource or with priority; and determining whether the logical channels can be transmitted via a first resource or with priority. The apparatus according to claim 50 or 51 is characterized in that the logical channel satisfies at least one of the following conditions: the index of the logical channel is a first index; the priority of the logical channel is a first priority; the delay corresponding to the logical channel satisfies a first condition; and the logical channel carries data whose delay satisfies a second condition. The apparatus according to any one of claims 50 to 52, wherein the data satisfies at least one of the following conditions: the data is data of a first logical channel; the delay of the data satisfies a first requirement; the data is data of a first logical channel and has arrived; the delay of the data satisfies the first requirement and has arrived; the data is data of a first logical channel and has arrived for a first duration; the delay of the data satisfies the first requirement and has arrived for a first duration. The apparatus according to claim 52 or 53 is characterized in that the delay includes at least one of the following: delay, remaining delay, remaining time of the Packet Data Convergence Protocol (PDCP) drop timer, PDCP drop timer for a set of low-importance Protocol Data Units (PDUs), packet set delay budget, packet delay budget, delay requirement, and QoS configuration for delay. The apparatus according to any one of claims 50 to 54, wherein the first information has at least one of the following functions: indicating whether the configured or scheduled resource is a first resource; indicating whether the configured or scheduled resource carries first data or a first logical channel; determining the mapping between the data and the resource; determining the mapping between the logical channel and the resource; determining whether the data can be transmitted or preferentially transmitted on the first resource; determining whether the logical channel can be transmitted or preferentially transmitted on the first resource; and determining LCP mapping restrictions. The apparatus according to claim 55 is characterized in that, when the resource configured or scheduled by the first information is the first resource: the resource is used or only used to carry the data or the logical channel; or, the resource preferentially carries the data or the logical channel; or, the resource carries the data or the logical channel using a first LCP process; or, the resource is subject to a first LCP mapping restriction; or, the resource carries the data or the logical channel if there are remaining transmission resources according to the existing LCP process. The apparatus according to claim 55 or 56 is characterized in that, when the first information indicates the configuration or scheduling of resources, and the resources are used or dedicated to carrying the first data or the first logical channel: the resources are used or only used to carry the data or the logical channel; or, the resources preferentially carry the data or the logical channel; or, the resources use a first LCP process to carry the data or the logical channel. The data or the logical channel; or, the resource is constrained by a first LCP mapping. The apparatus according to any one of claims 55 to 57 is characterized in that, when the first information is used to determine the mapping between the data and the resource, or to determine the mapping between the logical channel and the resource, or to determine whether the data can be transmitted or preferentially transmitted using the first resource, or to determine whether the logical channel can be transmitted or preferentially transmitted using the first resource, or to determine LCP mapping restrictions, and the first information occurs, or the first information is a first value: the resource is used or only used to carry the data or the logical channel; or, the resource preferentially carries the data or the logical channel; or, the resource carries the data or the logical channel using a first LCP process; or, the resource uses a first LCP mapping restriction; or, the resource carries the data or the logical channel if there are remaining transmission resources according to the existing LCP process. The apparatus according to any one of claims 50 to 58, wherein the first information is carried in configuration or scheduling information; or, the first information is for configuration authorization CG or dynamic authorization DG. A wireless communication device, characterized in that the device comprises: The processing module is used to perform data transfer-related behaviors based on at least two objects that are related or cooperative. The apparatus according to claim 60 is characterized in that the object is any one of the following: data stream, Quality of Service (QoS) stream, Data Radio Bearer (DRB), Radio Link Control (RLC) entity, logical channel, and data packet. The apparatus according to claim 60, wherein performing the data transmission related actions includes at least one of the following: adjusting the priorities of the at least two objects to be the same or similar; using another set of logical channel priorities for the at least two objects; adjusting the priorities of the at least two objects to a first priority, the first priority being the highest priority within a first priority range; adjusting the priorities of the at least two objects to a second priority, the second priority being a network-configured or predefined priority; mapping the at least two objects, or the data packets corresponding to the at least two objects, to available configured or scheduled resources; determining that the at least two objects, or the data packets corresponding to the at least two objects, relax or disregard configured LCP mapping restrictions; determining that the at least two objects, or the data packets corresponding to the at least two objects, use another set of LCP mapping restrictions. The apparatus according to claim 60 is characterized in that, when at least two objects satisfy at least one of the following conditions, the data transmission related behavior is performed: the at least two objects exist; both at least two objects have arrived; both at least two objects are to be transmitted; both at least two objects are to be transmitted and the arrival time satisfies a second duration; at least one of the at least two objects has arrived; the arrival time of at least one of the at least two objects satisfies a third duration; at least one of the at least two objects is to be transmitted; at least one of the at least two objects has been transmitted; at least one of the at least two objects has been transmitted and the transmission time satisfies a fourth duration; at least one of the at least two objects has been transmitted and at least one of the remaining objects has arrived. The following conditions must be met: 1. All of the remaining objects have arrived; 2. At least one of the at least two objects has been transmitted, and the transmission time satisfies the fourth duration; 3. At least one of the remaining objects has arrived, or all of them have arrived; 4. The delay difference between the at least two objects satisfies the first condition; 5. There exists a data packet to be transmitted corresponding to the at least two objects; 6. The delay difference between the data packets to be transmitted corresponding to the at least two objects satisfies the first condition. The apparatus according to claim 63 is characterized in that the delay difference satisfies a first condition, including any one of the following: the delay difference is less than or equal to a first threshold; the delay difference is less than or equal to a tolerable delay threshold; the delay difference is less than or equal to a maximum tolerable delay threshold; the delay difference is less than or equal to a tolerable delay threshold minus a first value; the delay difference is less than or equal to a maximum tolerable delay threshold minus a second value. The apparatus according to claim 63 or 64 is characterized in that the delay difference is any one of the following: data packet arrival delay difference, data packet transmission delay difference, data packet deletion delay difference, data packet arrival delay difference; and/or, the delay is any one of the following: data packet arrival delay, data packet transmission delay, data packet deletion delay, data packet arrival delay. A wireless communication device, characterized in that the device comprises: A processing module is used to obtain association or collaboration information, which is used to indicate at least two objects that are associated or collaborated. The apparatus according to claim 66 is characterized in that the object is any one of the following: data stream, Quality of Service (QoS) stream, Data Radio Bearer (DRB), Radio Link Control (RLC) entity, logical channel, and data packet. The apparatus according to claim 66 or 67 is characterized in that a QoS stream supports mapping only one data stream, or a QoS stream supports mapping one or more data streams. The apparatus according to any one of claims 66 to 68, wherein the association or coordination is determined based on at least one of the following: the Internet Protocol IP 5-tuple of the data packet, and the association or coordination identifier. The apparatus according to any one of claims 66 to 69 is characterized in that the association or coordination information is reported by the terminal device to the network device, and/or sent by the core network element to the network device. The apparatus according to claim 70 is characterized in that the associated or coordinated information is directed to a second object, which is any one of the following: data stream, QoS stream, DRB, RLC entity, logical channel, data packet. The apparatus according to any one of claims 66 to 71, wherein the processing module is further configured to: configure Radio Resource Control (RRC) parameters and/or allocate resources according to the association or coordination information; and/or, enable or disable the execution of data transmission-related actions according to the association or coordination information. A wireless communication device, characterized in that the device comprises: The processing module is used to process data packets based on forward error correction (FEC) information. The apparatus according to claim 73, wherein the FEC information is used to indicate at least one of the following: enabling or disabling the processing of data packets based on the FEC information; the minimum number of data packets required to recover or decode the data packet set; the minimum number of data packets tolerating failure or loss for the data packet set; a first ratio, the first ratio being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a second ratio, the second ratio being the ratio of the minimum number of data packets tolerating failure or loss for the data packet set to the total number of data packets in the data packet set; data packets belonging to the source data packet; and data packets belonging to the recovered data packet. The apparatus according to claim 73 or 74, wherein the FEC information is configured or indicated for a set of data packets; or, the FEC information is configured or indicated for a Quality of Service (QoS) flow; or, the FEC information is configured or indicated for data packet sets of different importance respectively; or, the FEC information is configured or indicated for multiple data packet sets of equal importance; wherein the data packet set is a data burst or a set of Protocol Data Units (PDUs). The apparatus according to any one of claims 73 to 75, wherein the processing module is configured to: based on the FEC information, delete data packets and/or their corresponding PDUs in a data packet set if a data packet set satisfies a second condition; or, based on the FEC information, delete untransmitted data packets and/or their corresponding PDUs in a data packet set if a data packet set satisfies a second condition; or, based on the FEC information, delete data packets and/or their corresponding PDUs in a data packet set that were not successfully transmitted or did not receive a positive ACK feedback if a data packet set satisfies a second condition. The apparatus according to claim 76, wherein the second condition includes at least one of the following: a data packet loss rate greater than or equal to a first proportion in the data packet set, the first proportion being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; a timer for discarding the data packet set timeout; a timer for discarding at least one data packet in the data packet set timeout; the number of data packets in the data packet set that are neither lost nor timed out is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; the number of data packets in the data packet set that are neither lost, successfully transmitted, or have received an ACK is greater than or equal to the minimum number of data packets required to recover or decode the data packet set; all source data packets in the data packet set are transmitted or successfully transmitted or have received an ACK feedback; the data packet set contains timed-out or discarded data packets, and the timed-out or discarded data packets are neither transmitted, successfully transmitted, nor have received an ACK feedback, and their total number is greater than [a certain number]. Or equal to, the total number of data packets in the data packet set minus the minimum number of data packets required to recover or decode the data packet set; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and their total number is greater than or equal to, the minimum number of data packets that the data packet set can tolerate failure or loss; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and the data packet includes at least one source data packet; the data packet set contains timed-out or dropped data packets, the timed-out or dropped data packets were not transmitted, were not successfully transmitted, or did not receive ACK feedback, and the data packet includes all recovery data packets; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include at least one source data packet; the data packet set contains lost or timed-out data packets, and the lost or timed-out data packets include all recovery data packets. The apparatus according to any one of claims 73 to 77, wherein the processing module is configured to: based on the FEC information, prioritize transmitting data packets in a data packet set if a data packet set satisfies a third condition. The apparatus according to claim 78, wherein the third condition includes at least one of the following: in the data packet set, there exist data packets with a transmission delay greater than or equal to a first proportion, the first proportion being the ratio of the number of data packets required to recover or decode the data packet set to the total number of data packets in the data packet set; the number of data packets already transmitted in the data packet set is less than the minimum number of data packets required to recover or decode the data packet set; and the source data packets in the data packet set need to be transmitted. The apparatus according to claim 78 or 79, wherein the priority transmission includes at least one of the following methods: adjusting the priority of the logical channel corresponding to the data packet; using another set of priorities for the logical channel corresponding to the data packet; relaxing or not complying with the configured LCP mapping restrictions; using another set of LCP mapping restrictions; transmitting the data packet using a first resource; and using a first logical channel priority LCP procedure. A communication device, characterized in that the communication device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program to implement the method as claimed in any one of claims 1 to 9, or the method as claimed in any one of claims 10 to 19, or the method as claimed in any one of claims 20 to 25, or the method as claimed in any one of claims 26 to 32, or the method as claimed in any one of claims 33 to 40. A computer-readable storage medium, characterized in that the storage medium stores a computer program, the computer program being executed by a processor to implement the method as claimed in any one of claims 1 to 9, or the method as claimed in any one of claims 10 to 19. Or the method as described in any one of claims 20 to 25, or the method as described in any one of claims 26 to 32, or the method as described in any one of claims 33 to 40. A chip, characterized in that the chip includes programmable logic circuitry and/or program instructions, which, when the chip is running, are used to implement the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 19, or the method as described in any one of claims 20 to 25, or the method as described in any one of claims 26 to 32, or the method as described in any one of claims 33 to 40. A computer program product, characterized in that the computer program product includes computer instructions stored in a computer-readable storage medium, wherein a processor reads from the computer-readable storage medium and executes the computer instructions to implement the method as claimed in any one of claims 1 to 9, or the method as claimed in any one of claims 10 to 19, or the method as claimed in any one of claims 20 to 25, or the method as claimed in any one of claims 26 to 32, or the method as claimed in any one of claims 33 to 40.