Wireless communication method and device

Abstract

Provided are a wireless communication method and a device. The method comprises: a first device receives first information sent by a second device, the first information being used for enabling or activating a first behavior, or the first information being used for configuring parameters of first data, or the first information being used for determining a transmission resource of the first data, wherein the first data is data having an association relationship, and the first behavior is related to the first data. In embodiments of the present application, a resource for transmitting the first data can be scheduled on the basis of the first information, facilitating the implementation of the coordinated / synchronous transmission of the first data. For example, on the basis of the first information, more transmission resources can be allocated to data that need to be synchronously transmitted, facilitating the arrival of said data at a peer end as soon as possible, and reducing the transmission time delay of said data.

Description

Method and device for wireless communication Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to wireless communication methods and devices. Background Art

[0002] Related data often requires coordinated and synchronized transmission. For example, in extended reality (XR) video streaming services, multiple data streams, including voice, video, text, and control information, often need to be displayed to users simultaneously. However, achieving coordinated and synchronized transmission of related data is a pressing issue.

[0003] Summary of the Invention

[0004] The present application provides a method and device for wireless communication. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a method for wireless communication is provided, the method comprising: a first device receiving first information sent by a second device, the first information being used to enable or activate a first behavior, or the first information being used to configure parameters of first data, or the first information being used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0006] In a second aspect, a method for wireless communication is provided, the method comprising: a second device sends first information to a first device, the first information being used to enable or activate a first behavior, or the first information being used to configure parameters of first data, or the first information being used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0007] According to a third aspect, a method for wireless communication is provided, the method comprising: a terminal device receiving tenth information sent by a network device, the tenth information being used to indicate configuration information of packet-based Packet Data Convergence Protocol (PDCP) data copy transmission.

[0008] In a fourth aspect, a method for wireless communication is provided, the method comprising: a network device sending tenth information to a terminal device, the tenth information being used to indicate configuration information of packet-based Packet Data Convergence Protocol (PDCP) data copy transmission.

[0009] In a fifth aspect, a method for wireless communication is provided, the method comprising: a first network device sends a cell switching request to a second network device to execute a cell switching process of a terminal device, the cell switching process being determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, the first data is data with an associated relationship, the first network device is a source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

[0010] In a sixth aspect, a method for wireless communication is provided, the method comprising: a second network device receives a cell switching request sent by a first network device to execute a cell switching process of a terminal device, the cell switching process being determined based on thirteenth information, wherein the thirteenth information is related to the transmission of data with an associated relationship, the first network device is a source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

[0011] In the seventh aspect, a method for wireless communication is provided, the method comprising: a terminal device performs cell switching, the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, and the first data is data with an associated relationship.

[0012] In the eighth aspect, a communication device is provided, which is a first device, and the device includes: a receiving unit, used to receive first information sent by a second device, the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine the transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0013] In the ninth aspect, a communication device is provided, which is a second device, and the device includes: a sending unit, used to send first information to the first device, the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine the transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0014] In a tenth aspect, a terminal device is provided, which includes: a receiving unit, used to receive tenth information sent by a network device, and the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol PDCP data copy transmission.

[0015] In an eleventh aspect, a network device is provided, comprising: a sending unit, configured to send tenth information to a terminal device, wherein the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol (PDCP) data replication transmission.

[0016] In the twelfth aspect, a network device is provided, which is a first network device, and the network device includes: a sending unit, used to send a cell switching request to a second network device to execute a cell switching process of the terminal device, and the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, the first data is data with an associated relationship, the first network device is the source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

[0017] In the thirteenth aspect, a network device is provided, which is a second network device, and the network device includes: a receiving unit, used to receive a cell switching request sent by a first network device to execute a cell switching process of a terminal device, and the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of data with an associated relationship, the first network device is the source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

[0018] In the fourteenth aspect, a terminal device is provided, which includes: an execution unit for executing cell switching, and the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, and the first data is data with an associated relationship.

[0019] In the fifteenth aspect, a terminal device is provided, including a processor and a memory, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute a method as described in any one of the first aspect, the second aspect, the third aspect or the seventh aspect.

[0020] In the sixteenth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store programs, and the processor is used to call the programs in the memory to execute a method as described in any one of the first aspect, the second aspect, the fourth aspect, the fifth aspect or the sixth aspect.

[0021] In the seventeenth aspect, a terminal device is provided, comprising a processor, wherein the memory is used to store programs and to call programs from the memory to execute a method as described in any one of the first aspect, the second aspect, the third aspect or the seventh aspect.

[0022] In the eighteenth aspect, a network device is provided, including a processor, wherein the memory is used to store a program and to call the program from the memory to execute a method as described in any one of the first aspect, the second aspect, the fourth aspect, the fifth aspect or the sixth aspect.

[0023] In the nineteenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes any one of the methods in the first aspect, the second aspect, the third aspect or the seventh aspect.

[0024] In the twentieth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes any one of the methods in the first, second, fourth, fifth or sixth aspects.

[0025] In a twenty-first aspect, a communication system is provided, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device and / or network device in the solution provided in the embodiment of the present application.

[0026] In aspect 22, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of aspect 1, aspect 2, aspect 3 or aspect 7.

[0027] In aspect 23, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute any one of the methods in aspect 1, aspect 2, aspect 4, aspect 5 or aspect 6.

[0028] In aspect 24, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of aspect 1, aspect 2, aspect 3 or aspect 7.

[0029] In aspect 25, a computer program product is provided, comprising a program, wherein the program enables a computer to execute any one of the methods described in aspect 1, aspect 2, aspect 4, aspect 5 or aspect 6.

[0030] In aspect 26, a computer program is provided, which enables a computer to execute the method described in any one of aspect 1, aspect 2, aspect 3 or aspect 7.

[0031] In aspect 27, a computer program is provided, which enables a computer to execute the method described in any one of aspect 1, aspect 2, aspect 4, aspect 5 or aspect 6.

[0032] In the embodiments of the present application, resources for transmitting the first data can be scheduled based on the first information, which helps achieve coordinated / synchronous transmission of the first data. For example, based on the first information, more transmission resources can be allocated to data that requires synchronous transmission, which helps the data that requires synchronous transmission reach the other end as quickly as possible and reduces the transmission delay of the data that requires synchronous transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] FIG1 is a wireless communication system used in an embodiment of the present application.

[0034] FIG2 is a schematic diagram of a cell handover process.

[0035] FIG3 is a schematic flowchart of a method for wireless communication provided in an embodiment of the present application.

[0036] FIG4 is a schematic flowchart of a method for wireless communication provided in another embodiment of the present application.

[0037] FIG5 is a flowchart of a method for wireless communication provided in yet another embodiment of the present application.

[0038] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0039] FIG7 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

[0040] FIG8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

[0041] FIG9 is a schematic structural diagram of a network device provided in an embodiment of the present application.

[0042] FIG10 is a schematic structural diagram of another network device provided in an embodiment of the present application.

[0043] FIG11 is a schematic structural diagram of another network device provided in an embodiment of the present application.

[0044] FIG12 is a schematic structural diagram of another terminal device provided in an embodiment of the present application.

[0045] FIG13 is a schematic structural diagram of a device for communication according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The technical solution in this application will be described below with reference to the accompanying drawings.

[0047] Figure 1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0048] FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0049] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0050] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0051] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0052] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network equipment.

[0053] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0054] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0055] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0056] It should be understood that the communication devices referred to in this application may be network devices or terminal devices. For example, the first communication device may be a network device, and the second communication device may be a terminal device. In another example, the first communication device may be a terminal device, and the second communication device may be a network device. In another example, both the first communication device and the second communication device may be network devices, or both may be terminal devices.

[0057] It should also be understood that all or part of the functions of the communication device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (eg, a cloud platform).

[0058] Currently, with the increasing demand for speed, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services, the 3GPP international standards organization has begun developing 5G. The main application scenarios for 5G are: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communications (mMTC).

[0059] eMBB still aims to provide users with multimedia content, services, and data, and demand for this technology is growing rapidly. However, since eMBB can be deployed in diverse scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary significantly. Therefore, it cannot be generalized and requires detailed analysis based on specific deployment scenarios. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety. Typical characteristics of mMTC include high connection density, small data volumes, latency-insensitive services, low module costs, and long service life.

[0060] NR can also be deployed independently. In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new RRC state is defined, namely RRC inactive state (RRC_INACTIVE). This state is different from RRC idle state (RRC_IDLE) and RRC active state (RRC_ACTIVE). The following introduces these three states respectively.

[0061] The RRC connection state may refer to the state in which the terminal device is in when the RRC release is not performed after the random access process is completed. An RRC connection exists between the terminal device and a network device (e.g., an access network device). In the RRC connection state, the terminal device can transmit data with the network device, such as downlink data transmission and / or uplink data transmission. Alternatively, the terminal device can also transmit terminal device-specific data channels and / or control channels with the network device to transmit specific information or unicast information of the terminal device.

[0062] In the RRC connected state, the network device can determine the cell-level location information of the terminal device, that is, the network device can determine the cell to which the terminal device belongs. In the RRC connected state, after the terminal device moves, such as from one cell to another, the network device can control the terminal device to perform cell handover. Therefore, it can be seen that the mobility management of the terminal device in the RRC connected state may include cell handover. In addition, the mobility management of the terminal device in the RRC connected state can be controlled by the network device. Accordingly, the terminal device can switch to a designated cell according to the instructions issued by the network device.

[0063] The RRC idle state refers to the state of the terminal device when it is resident in a cell but is not performing random access. The terminal device usually enters the RRC idle state after being powered on or after RRC is released. In the RRC idle state, there is no RRC connection between the terminal device and the network device (such as the resident network device), the network device does not store the context of the terminal device, and no connection is established between the network device and the core network for the terminal device. If the terminal device needs to enter the RRC connected state from the RRC idle state, it is necessary to initiate the RRC connection establishment process.

[0064] In the RRC idle state, the core network (CN) can send a paging message to the terminal device, that is, the paging process can be triggered by the CN. Optionally, the paging area can also be configured by the CN. In some cases, for a terminal device in the RRC idle state, when the terminal device moves (for example, from one cell to another), the terminal device can initiate a cell reselection process. In other cases, for a terminal device in the RRC idle state, when the terminal device needs to access a cell, the terminal device can initiate a cell selection process. That is, the mobility management of the terminal device in the RRC idle state may include cell reselection and / or cell selection.

[0065] The RRC inactive state is defined to reduce air interface signaling, quickly restore wireless connections, and quickly resume data services. The RRC inactive state is a state between the connected and idle states. A terminal device previously entered the RRC connected state and then released the RRC connection with the network device, but the network device retained the terminal device's context. Furthermore, the connection established between the network device and the core network for the terminal device is not released. This means that the user plane and control plane bearers between the RAN and CN are still maintained, indicating a CN-NR connection.

[0066] In the RRC inactive state, the RAN can send a paging message to the terminal device, that is, the paging process can be triggered by the RAN. The RAN-based paging area is managed by the RAN, and the network equipment can know the location of the terminal device based on the RAN paging area level.

[0067] In some cases, for a terminal device in an RRC inactive state, when the terminal device moves (for example, from one cell to another), the terminal device may initiate a cell reselection process. In other cases, for a terminal device in an RRC inactive state, when the terminal device needs to access a cell, the terminal device may initiate a cell selection process. In other words, the mobility management of a terminal device in an RRC inactive state may include cell reselection and / or cell selection.

[0068] Cell switching

[0069] Cell handover (HO) aims to improve the continuity of services provided by the communication system to terminal devices. In a wireless communication system, a terminal device can move from one cell (also known as the "source cell") to another cell (also known as the "target cell").

[0070] Figure 2 is a schematic diagram of a cell handover process. The process shown in Figure 2 involves interactions between a terminal device, a source base station, a target base station, a mobility management entity, and a serving gateway. The schematic diagram of the process shown in Figure 2 may include steps S201 to S219.

[0071] In step S201, area restrictions are provided.

[0072] In step S202, the source base station sends a measurement control to the terminal device.

[0073] In step S203, the terminal device reports a measurement report to the source base station.

[0074] The source base station may make a handover decision based on the reporting result of the UE.

[0075] In step S204, the source base station sends a cell handover request to the target base station.

[0076] The source base station sends a handover request to the target base station based on the terminal device's report. The handover request message carries information related to the PDU session. This information includes slice information and QoS flow-level QoS profile information (e.g., 5QI, corresponding to QoS parameters).

[0077] In step S205, the target base station performs admission control.

[0078] When the slice information is sent to the target base station, the target base station performs slice-aware access control. If the PDU session in the Handover request corresponds to a slice that the target base station does not support, the target base station will reject the PDU session. When the target base station agrees to the handover request, it will configure the RRC message mobilityControlInformation for the terminal device, which includes information for RACH resources, C-RNTI, target base station security algorithm, and target base station system information.

[0079] In step S206, the handover request is responded to.

[0080] In step S207, the control information is moved.

[0081] The source base station forwards the mobilityControlInformation to the terminal device. After receiving the handover command, the terminal device initiates a random access process to the target base station.

[0082] In step S208, the source base station sends the SN transfer status to the target base station.

[0083] The source base station will send an SN STATUS TRANSFER message to the target base station to inform the target base station of the uplink PDCP SN reception status and the downlink PDCP SN transmission status.

[0084] In step S209, synchronization.

[0085] In step S210, periodic uplink authorization is performed.

[0086] In step S211, uplink authorization and timing advance.

[0087] In step S212, RRC configuration is completed.

[0088] From step S209 to step S212 , the terminal device performs random access with the target base station.

[0089] In step S213, the target base station sends a path switching request to the mobility management entity.

[0090] When the terminal device successfully accesses the target base station (random access is successful), the target base station will send a PATH SWITCH REQUEST to request the mobility management entity to switch the downlink path.

[0091] In step S214, the mobility management entity sends a modify bearer request to the serving gateway.

[0092] In step S215, the serving gateway switches the downlink path.

[0093] In step S216, the mobility management entity receives the modify bearer response sent by the serving gateway.

[0094] In step S217, the target base station receives the path switching response sent by the mobility management entity.

[0095] In step S218, the target base station instructs the source base station to release the terminal device context.

[0096] After the path switching is completed, the target base station will instruct the source base station to release the UE context, and the switching is completed.

[0097] In step S219, the source base station releases resources.

[0098] XR

[0099] At the 3GPP RAN#88e meeting, a research project titled "eXtended reality (XR) and cloud game (CG) evaluations for NR" was approved. The services studied in this project include augmented reality (AR), virtual reality (VR), and cloud gaming. A key service of XR / CG is video streaming, with an arrival rate (measured in frames per second) of 30fps, 60fps, 90fps, and 120fps. The corresponding video stream period is {33.33ms, 16.67ms, 11.11ms, 8.33ms}.

[0100] XR data features variable packet sizes with a large average. For example, for AR / VR with a 100Mbps data rate, the average uplink packet size is 20,833 bytes, the maximum is 31,250 bytes, and the minimum is 10,417 bytes. This means that the size of the packet to be transmitted in each cycle is between [10,417 bytes and 31,250 bytes]. In a real-world system with 100Mbps bandwidth, transmitting a 20,833-byte packet requires approximately four time slots of transmission resources.

[0101] Currently, 3GPP supports configuring multiple physical uplink shared channel (PUSCH) occasions within a CG cycle for transmitting XR large data packets. Alternatively, multiple CGs can be configured to transmit XR large data packets. When the amount of data transmitted in a particular transmission is relatively small and does not require the use of multiple pre-configured PUSCH occasions, the terminal device can notify the base station of the unused PUSCH occasions. The base station can then reallocate the unused PUSCH occasions to other terminal devices for data transmission, thereby improving system efficiency.

[0102] Application layer data exchanged between terminal devices and application servers or peer terminal devices, such as AR / VR / CG / live video, typically includes data streams in multiple modes (or modalities), such as voice, video, text, and control information (this type of data stream can also be called a multimodal data stream). These data streams typically require synchronization between data streams, for example, voice, video, subtitles, and other data need to be displayed synchronously to the user. The current practice for video playback is to synchronize multiple data streams through the application layer, such as caching multiple received data streams, extracting the corresponding data frames of multiple data streams based on the timestamps of the playback data streams, and displaying them synchronously to the user.

[0103] Related data, such as the multimodal data mentioned above, often requires coordinated or synchronized transmission. Related technologies use application-layer caching to support this coordinated or synchronized transmission. However, how to support and enhance this coordinated or synchronized transmission of related data remains a pressing issue.

[0104] Data with an associated relationship may involve one terminal device or multiple terminal devices. For example, the sender and receiver of data with an associated relationship may involve one terminal device or multiple terminal devices. Therefore, how to support and enhance the coordinated / synchronous transmission requirements of data with an associated relationship may include how to support coordinated transmission for multi-modality flows with a single UE; and how to enable application synchronization and QoS policy coordination for multi-modal data flows among multiple UEs.

[0105] FIG3 is a schematic flowchart of a method for wireless communication provided in an embodiment of the present application to solve the above-mentioned problem.

[0106] The method shown in FIG3 is described from the perspective of interaction between a first device and a second device. The first device and the second device may be any type of network device and terminal device mentioned above.

[0107] In an embodiment of the present application, the first device may be a transmitter of data with an associated relationship (i.e., the first data), and the second device may be a receiver of data with an associated relationship. For example, the first device is a first terminal device, and the second device may be a network device or a second terminal device. For another example, the first device is a first network device, and the second device may be a terminal device or a second network device. That is to say, the method provided in an embodiment of the present application can be applied to the coordination / synchronization of first data between terminal devices and terminal devices, and can also be applied to the coordination / synchronization of first data between terminal devices and network devices. In other words, the transmitter of the first data may be a terminal device or a network device, and the receiver of the first data may be a terminal device or a network device.

[0108] The method shown in FIG3 may include step S310 .

[0109] In step S310, the first device receives the first information sent by the second device. Alternatively, the second device sends the first information to the first device.

[0110] The first information may be used to enable or activate the first behavior, or the first information may be used to configure parameters of the first data, or the first information may be used to determine transmission resources of the first data.

[0111] The first data may be data with an associated relationship, such as the data in the multimodal data stream mentioned above. The associated relationship mentioned here may include but is not limited to synchronization, coordination, and dependency relationships. For example, data with an associated relationship may refer to data with synchronous transmission, coordinated / synchronous transmission, or synchronous or collaborative transmission requirements. For another example, the first data may refer to data that needs to be displayed to the user at the same time, or data that depends on other data to perform data processing.

[0112] The above-mentioned association relationship can be an association relationship of data in a terminal device, or an association relationship of data between multiple terminal devices, or an association relationship of data in a packet data unit set (PDU set), or an association relationship of data between multiple PDU sets, or an association relationship of data between multiple quality of service flows QoS flows.

[0113] In some embodiments, the first information can be used to enable or activate a first behavior, and the first behavior can be related to the first data. For example, the first behavior can be an associated processing behavior of the first data, or a collaborative processing behavior. As an example, the first behavior can include one or more of data packet deletion, requesting transmission resources, duplicating transmission, parameter configuration, and priority processing. Among them, the deletion of the above-mentioned data packets can, for example, include deleting other data packets in the first data when some data packets in the first data are deleted, or deleting the second data associated with the first data when the first data is deleted; the above-mentioned request for transmission resources can, for example, include requesting more transmission resources for the first data, or giving the first data a higher priority in the allocation of transmission resources; the above-mentioned duplication transmission can, for example, include activating duplication transmission for the first data, or adjusting the duplication transmission strategy of the first data; the above-mentioned parameter configuration can, for example, refer to configuring different parameters for the first data and other data; and the above-mentioned priority processing can, for example, include increasing the priority of the logical channel (logical channel, LCH) and data radio bearer (data radio bearer, DRB) corresponding to the first data, etc. For example, the first behavior may be a behavior supporting first data coordination / synchronous transmission, such as a behavior supporting first data coordination / synchronous transmission associated with a logical channel / logical channel priority (LCP), a behavior supporting first data coordination / synchronous transmission associated with a packet data convergence protocol (PDCP), and a behavior supporting first data coordination / synchronous transmission associated with allocating or scheduling transmission resources (such as configuration authorization, dynamic authorization), etc.

[0114] The first information may include one enabling or activating instruction information to indicate enabling or activating multiple behaviors included in the first behavior. The first information may also include multiple enabling or activating instruction information, with different enabling or activating instruction information being used for different contents of the first behavior.

[0115] In some embodiments, the first information may be used to configure parameters of the first data. For example, the first information may be used to configure or indicate that one or more DRBs, LCHs, PDCPs, configured grants (CGs), and dynamic grants (DGs) associated with the first data have associated transmission requirements. For another example, the first information may be used to configure or indicate an association relationship between one or more DRBs, LCHs, PDCPs, CGs, and DGs associated with the first data.

[0116] In some embodiments, the first information may be used to determine a transmission resource for the first data. For example, the first information may be used to configure transmission parameters of the first data, such as parameters associated with one or more of DRB, LCH, PDCP, configured grant CG, dynamic grant DG, and duplicate transmission.

[0117] In embodiments of the present application, resources for transmitting the first data can be scheduled based on the first information, thereby facilitating coordinated / synchronous transmission of the first data. For example, based on the first information, more transmission resources can be allocated to data requiring synchronous transmission, thereby facilitating faster arrival of the data requiring synchronous transmission at the peer end and reducing transmission latency of the data requiring synchronous transmission.

[0118] In some embodiments, the first information may include first configuration information, and the first configuration information may be used to configure parameters of a DRB / LCH, or the first configuration information may be used to configure parameters of one or more terminal devices. A mapping relationship exists between the first data and the DRB / LCH, and / or a mapping relationship exists between the first data and the one or more terminal devices.

[0119] For example, when one or more DRBs / LCHs are used to transmit first data, the first configuration information may be used to configure parameters of the one or more DRBs / LCHs. As an example, the first configuration information may be used to indicate that the DRBs / LCHs have synchronization or coordinated transmission requirements, or the first configuration information may be used to identify DRBs / LCHs that have associated or synchronization or coordinated transmission requirements. As another example, the first configuration information may be used to indicate an associated relationship between DRBs / LCHs that have synchronization or coordinated transmission requirements.

[0120] For another example, when a mapping relationship exists between the first data and one or more terminal devices, that is, the sender and receiver of the first data involve one or more terminal devices, the first configuration information can be used to configure the one or more terminal devices. For example, the first configuration information can be used to identify multiple terminal devices that have associated, synchronized, or coordinated transmission requirements. For another example, the first configuration information can be used to indicate the associated relationship between terminal devices that have synchronized or coordinated transmission requirements.

[0121] In some embodiments, the above-mentioned first configuration information can indicate or identify that the DRB / LCH has a synchronization or coordinated transmission requirement through an associated flag. For example, if the associated identification bit in the first configuration information corresponding to the DRB / LCH (or the first configuration information used to configure the DRB / LCH) is "1", it can indicate that the DRB / LCH has an associated or synchronized or coordinated transmission requirement; if the associated identification bit in the first configuration information corresponding to the DRB / LCH is "0", it can indicate that the DRB / LCH does not have an associated or synchronized or coordinated transmission requirement. For another example, if the associated identification bit in the first configuration information corresponding to the DRB / LCH is "0", it can indicate that the DRB / LCH has an associated or synchronized or coordinated transmission requirement; if the associated identification bit in the first configuration information corresponding to the DRB / LCH is "1", it can indicate that the DRB / LCH does not have an associated or synchronized or coordinated transmission requirement.

[0122] The association relationship between DRB / LCH and / or terminal equipment can be indicated explicitly or implicitly.

[0123] For example, the association relationship can be indicated by an association identifier, such as the same association identifier can be configured in the first configuration information corresponding to the DRB / LCH and / or terminal device with the association relationship. As an example, if the first terminal device and the second terminal device have an association or synchronization or cooperative transmission requirement, the association identifiers of the first terminal device and the second terminal device can both be X, and if the first LCH and the second LCH have an association or synchronization or cooperative transmission requirement, the association identifiers of the first LCH and the second LCH can both be Y. As another example, the first configuration information may include the identifier of the DRB / LCH and / or terminal device with the association relationship. If the first configuration information includes the identifiers of the first terminal device and the second terminal device, the first terminal device and the second terminal device have an association or synchronization or cooperative transmission requirement.

[0124] For another example, the association between DRB / LCH and / or terminal device can be implicitly indicated by priority. As an example, if a first LCH and a second LCH have an association, synchronization, or coordinated transmission requirement, the first LCH and the second LCH can be configured with the same priority. In other words, the association between DRB / LCH and / or terminal device is implicitly indicated by the same priority.

[0125] The first LCH and the second LCH may be LCHs corresponding to the same terminal device, or may be LCHs corresponding to different terminal devices.

[0126] In an embodiment of the present application, the first information can configure the DRB / LCH and / or terminal device with an associated relationship, so that the system can identify the DRB / LCH and / or terminal device with an associated relationship, so that the system can schedule resources based on the associated relationship, thereby facilitating the synchronous or coordinated transmission of the first data.

[0127] As mentioned above, the first information may be used to determine a transmission resource for the first data. In some embodiments, the first information may include a transmission parameter, which may be related to a transmission process of the first data.

[0128] The first information may include a set of transmission parameters for determining the transmission resources of the first data. Taking LCH as an example, the transmission resources of the first data may be determined based on parameters such as the priority of the LCH included in the first information.

[0129] The first information may include multiple sets of transmission parameters. For example, the multiple sets of transmission parameters may include a set of transmission parameters for unrelated data, or a set of default transmission parameters. In another example, the multiple sets of transmission parameters may include one or more sets of transmission parameters for the first data.

[0130] For example, the first information may include a first transmission parameter and a second transmission parameter, and the first transmission parameter is different from the second transmission parameter. The first transmission parameter and the second transmission parameter being different here may refer to at least one parameter among multiple parameters included in the first transmission parameter and the second transmission parameter being different.

[0131] In some embodiments, the first transmission parameter and / or the second transmission parameter may be for one DRB / LCH or one terminal device; or the first transmission parameter and / or the second transmission parameter may be for multiple DRBs / LCHs; or the first transmission parameter and / or the second transmission parameter may be for multiple terminal devices. In other words, the configuration granularity of the first transmission parameter and / or the second transmission parameter may be one DRB / LCH, one terminal device, multiple DRBs / LCHs, or multiple terminal devices.

[0132] In some embodiments, the first transmission parameter and / or the second transmission parameter may be configured for PDCP / radio link control (RLC) / media access control (MAC) / physical layer (PHY).

[0133] In some embodiments, the first transmission parameter may be used when synchronization transmission is not activated / not indicated, or when the first condition is satisfied, and / or the second transmission parameter may be used when synchronization transmission is activated / indicated, or when the second condition is satisfied.

[0134] The aforementioned synchronous transmission activation / indication situation may refer to a situation where the first device is activated and can perform synchronous transmission, or the first device receives instruction information for performing synchronous transmission. The aforementioned synchronous transmission inactivation / non-indication situation may refer to a situation where the first device is not activated and can perform synchronous transmission, or does not receive instruction information for performing synchronous transmission.

[0135] In some embodiments, the second condition may include at least one of at least one terminal device among a plurality of terminal devices configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified as synchronized or associated. That is, the second condition may include at least one of the following: the existence of one or more terminal devices associated with the first data; at least one terminal device among the one or more terminal devices associated with the first data is configured with a synchronization or cooperative transmission requirement, and / or an association relationship with a synchronization or cooperative transmission requirement is configured; the existence of a terminal device that enables the first behavior; and the existence of a terminal device that is identified as synchronized or associated, or the existence of a terminal device in an association relationship configured with a synchronization or cooperative transmission requirement.

[0136] In some embodiments, the second condition may include at least one of the following: configuration or existence of at least one of a plurality of associated LCHs / logical channel groups (LCGs), an LCH / LCG with the first behavior enabled, and an LCH / LCG identified as synchronized or associated. That is, the second condition may include the existence of one or more LCHs / LCGs associated with the first data; at least one of the one or more LCHs / LCGs associated with the first data is configured with synchronization or cooperative transmission requirements, and / or an association relationship with synchronization or cooperative transmission requirements is configured; the existence of an LCH / LCG with the first behavior enabled; and the existence of an LCH / LCG identified as synchronized or associated, or the existence of an LCH / LCG with an association relationship configured with synchronization or cooperative transmission requirements.

[0137] In some embodiments, the second condition may include that the first transmission parameter is used for a first duration.

[0138] In some embodiments, the second condition may be associated with a transmission delay of the first data.

[0139] For example, the second condition may include the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the transmission delay of one of the identified synchronized or associated DRB / LCHs meeting the first threshold.

[0140] For another example, the second condition may include that the transmission delay of an associated terminal device, at least one of the associated multiple terminal devices, a terminal device that enables the first behavior, or one of the identified synchronized or associated terminal devices satisfies a fourth threshold.

[0141] The transmission delay may include one or more of the following: the remaining transmission delay, the transmission delay of the data to be transmitted, or the tolerable transmission delay. For another example, the transmission delay may be one or more of the following: the minimum transmission delay, the maximum transmission delay, the transmission delay of each data packet, or the average transmission delay of multiple data packets. Furthermore, the transmission delay may be a combination of the aforementioned transmission delays, such as the maximum tolerable transmission delay or the minimum tolerable transmission delay.

[0142] It should be noted that the transmission delay mentioned in the embodiments of the present application can be one or more of the above-mentioned transmission delays. For the sake of brevity, they will not be described in detail below.

[0143] In some embodiments, the second condition may be associated with the total amount of the first data.

[0144] For example, the second condition may include the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the total amount of data of one of the identified synchronized or associated DRB / LCHs meeting the second threshold.

[0145] For another example, the second condition may include that the total amount of data of one of the associated terminal devices, at least one of the associated terminal devices, the terminal device enabling the first behavior, or the terminal device identified for synchronization or association satisfies a fifth threshold.

[0146] In some embodiments, the second condition may be associated with the amount of the first data to be transmitted.

[0147] For example, the second condition may include an associated DRB / LCH, at least one of the associated multiple DRB / LCHs, a DRB / LCH of a terminal device with the first behavior enabled, or the amount of data remaining to be transmitted in one of the identified synchronized or associated DRB / LCHs satisfies a third threshold.

[0148] For example, the second condition may include that the amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, or one of the identified synchronized or associated terminal devices meets a sixth threshold.

[0149] In some embodiments, the second condition may include the network device indicating that the first behavior is enabled or activated. For example, the second condition may include the network device indicating that the first behavior associated with one or more terminal devices / DRBs / LCHs is enabled or activated.

[0150] In some embodiments, the second condition may include the network device indicating use of the second transmission parameter.

[0151] In some embodiments, the second condition may be associated with feedback from the network device, such as NACK. For example, the associated terminal device, at least one terminal device among multiple associated terminal devices receives feedback from the network device, or receives feedback from the network device involving an associated DRB / LCH, at least one DRB / LCH among multiple associated DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, or one of the DRB / LCHs identified as synchronized or associated. For another example, the associated terminal device, at least one terminal device among multiple associated terminal devices receives feedback from the network device for a number of times greater than or equal to a threshold, or receives feedback from the network device involving an associated DRB / LCH, at least one DRB / LCH among multiple associated DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, or one of the DRB / LCHs identified as synchronized or associated.

[0152] In some embodiments, the above-mentioned "satisfying the threshold" associated with the second condition may refer to being greater than or equal to the threshold, or may refer to being less than or equal to the threshold. For example, if the transmission speed of the DRB / LCH using the second transmission parameter is greater than the transmission speed using the first transmission parameter, then the remaining amount of data to be transmitted meets the third threshold, which may mean that the remaining amount of data to be transmitted is greater than or equal to the third threshold. That is, when the remaining amount of data of the first data to be transmitted is large, a transmission parameter with a faster transmission speed may be used to help meet the synchronous or collaborative transmission requirements of the first data. For another example, if the transmission speed of the DRB / LCH using the second transmission parameter is less than the transmission speed using the first transmission parameter, then the remaining amount of data to be transmitted meets the third threshold, which may mean that the remaining amount of data to be transmitted is less than or equal to the third threshold. That is, when the remaining amount of data of the first data to be transmitted is small, a transmission parameter with a slower transmission speed may be used to allocate more or higher priority transmission resources to other data, thereby helping to improve the overall performance of the system.

[0153] In some embodiments, the first condition may include at least one of at least one terminal device among a plurality of terminal devices that is not configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified as synchronized or associated. For example, the first condition may include the absence of one or more terminal devices associated with the first data, or one or more terminal devices are not involved in the transmission of associated data; the first condition may also include that at least one terminal device or all terminal devices among the one or more terminal devices associated with the first data are not configured with synchronization or collaborative transmission requirements, and / or are not configured with an association relationship with synchronization or collaborative transmission requirements. For another example, the first condition may include the absence of a terminal device that has the first behavior enabled, or one or more terminal devices have not enabled the first behavior. For another example, the first condition may include the absence of a terminal device that is identified as synchronized or associated, or the absence of a terminal device that has an association relationship configured with synchronization or collaborative transmission requirements.

[0154] In some embodiments, the first condition may include at least one of the following: at least one LCH / LCG among the plurality of LCH / LCGs that is not configured or associated, an LCH / LCG with the first behavior enabled, and an LCH / LCG identified as synchronized or associated. That is, the first condition may include the absence of one or more LCH / LCGs associated with the first data; at least one of the one or more LCH / LCGs associated with the first data, or all LCH / LCGs not configured with synchronization or cooperative transmission requirements, and / or no association relationship with synchronization or cooperative transmission requirements is configured; there is no LCH / LCG with the first behavior enabled, or all LCH / LCGs do not have the first behavior enabled; and there is no LCH / LCG identified as synchronized or associated, or there is no LCH / LCG with an association relationship configured with synchronization or cooperative transmission requirements.

[0155] In some embodiments, the first condition may include that the second transmission parameter is used for a second duration.

[0156] In some embodiments, the first condition may be associated with a transmission delay of the first data.

[0157] For example, the first condition may include the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the transmission delay of one of the identified synchronized or associated DRB / LCHs meeting the seventh threshold.

[0158] For another example, the first condition may include that the transmission delay of an associated terminal device, at least one of the associated multiple terminal devices, a terminal device that enables the first behavior, or one of the identified synchronized or associated terminal devices satisfies a tenth threshold.

[0159] In some embodiments, the first condition may be associated with the total amount of the first data.

[0160] For example, the first condition may include the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the total amount of data of one of the identified synchronized or associated DRB / LCHs meeting the eighth threshold.

[0161] For another example, the first condition may include that the total amount of data of one of the associated terminal devices, at least one of the associated terminal devices, the terminal device that enables the first behavior, and the terminal devices identified as synchronized or associated meets an eleventh threshold.

[0162] In some embodiments, the first condition may be associated with the amount of first data to be transmitted.

[0163] For example, the first condition may include the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the amount of data remaining to be transmitted of one of the DRB / LCHs identified as synchronized or associated satisfies the ninth threshold.

[0164] For example, the first condition may include that the amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, or one of the identified synchronized or associated terminal devices meets a twelfth threshold.

[0165] In some embodiments, the network device indicates that the first behavior is not enabled or deactivated. For example, the first condition may include the network device indicating that the first behavior associated with one or more terminal devices / DRBs / LCHs is not enabled or deactivated.

[0166] In some embodiments, the first condition may include the network device indicating use of the first transmission parameter.

[0167] In some embodiments, the first condition may be associated with feedback from the network device, such as NACK. For example, the associated terminal device, at least one terminal device among multiple associated terminal devices, or all terminal devices do not receive feedback from the network device, or do not receive feedback from the network device involving the associated DRB / LCH, at least one DRB / LCH among multiple associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, or one of the network devices identified as synchronized or associated DRB / LCHs. For another example, the number of times that the associated terminal device, at least one terminal device among multiple associated terminal devices, or all terminal devices receive feedback from the network device is less than or equal to a threshold, or the number of times that the associated terminal device, at least one DRB / LCH among multiple associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, or one of the network devices identified as synchronized or associated DRB / LCHs is less than or equal to a threshold.

[0168] In some embodiments, the above-mentioned "satisfying the threshold" associated with the first condition may refer to being greater than or equal to the threshold, or may refer to being less than or equal to the threshold. For example, if the transmission speed of the DRB / LCH using the second transmission parameter is greater than the transmission speed using the first transmission parameter, then the total amount of data satisfies the eighth threshold, which may refer to the total amount of data being less than or equal to the eighth threshold. That is, when the total amount of the first data is small, a transmission parameter with a slower transmission speed may be used to allocate more or higher priority transmission resources to other data, thereby helping to improve the overall performance of the system. For another example, if the transmission speed of the DRB / LCH using the second transmission parameter is less than the transmission speed using the first transmission parameter, then the total amount of data satisfies the eighth threshold, which may refer to the total amount of data being greater than or equal to the eighth threshold. That is, when the total amount of the first data is large, a transmission parameter with a faster transmission speed may be used to help meet the synchronous or collaborative transmission requirements of the first data.

[0169] In some embodiments, the first transmission parameter and / or the second transmission parameter may include one or more of the following: logical channel priority (LCH priority); priority bit rate (prioritisedBitRate); allowed uplink grant (UL grant) or dynamic grant; allowed configuration grant list (allowed-CG list); duplication transmission (duplication); repetition (repetition); duplication transmission of logical channel (LCH of duplication); retransmission; tolerated transmission delay; and modulation and coding acheme (MCS).

[0170] In some embodiments, the uplink authorization or dynamic authorization allowed by the first transmission parameter and / or the second transmission parameter is indicated by an identifier of the uplink authorization or dynamic authorization, or an identifier of the DRB / LCH corresponding to the uplink authorization or dynamic authorization, or matching information of the uplink authorization or dynamic authorization and DRB / LCH, or the correspondence between the uplink authorization or dynamic authorization and DRB / LCH.

[0171] For example, the above-mentioned indication signaling or configuration parameters of the uplink grant or dynamic grant may indicate or include the flag / marker of the DG or UL grant, or indicate or include the identifier of the DRB / LCH that can be used for transmission (i.e., the corresponding DRB / LCH of the uplink grant or dynamic grant). If the flag / marker of one or more DRB / LCHs is consistent with the flag / marker of the DRB / LCH indicated or included in the indication signaling or configuration parameters of the uplink grant or dynamic grant, then the DG / UL grant can be used to transmit the corresponding DRB / LCH, or the corresponding DRB / LCH can be transmitted in the DG / UL grant. For another example, only the DRB / LCH that can be used for transmission indicated in the indication signaling or configuration parameters of the uplink grant or dynamic grant can be transmitted in the DG / UL grant. For another example, the indication signaling or configuration parameter may include or indicate a DG / UL grant and its corresponding DRB / LCH, or may include or indicate multiple DG / UL grants, multiple DRB / LCHs, and a matching relationship between multiple DG / UL grants and multiple DRB / LCHs. As an example, if the matching relationship indicated or included in the indication signaling or configuration parameter indicates that the first DG / UL grant matches the second DRB / LCH, the first DG / UL grant may be used to transmit the second DRB / LCH, or the second DRB / LCH may be transmitted on the first DG / UL grant.

[0172] In some embodiments, the first transmission parameter and the second transmission parameter satisfy one or more of the following: the logical channel priority in the second transmission parameter is higher than the logical channel priority in the first transmission parameter; the priority bit ratio in the second transmission parameter is higher than the priority bit ratio in the first transmission parameter; the logical channel priority in the second transmission parameter is lower than the logical channel priority in the first transmission parameter, and the tolerated transmission delay in the second transmission parameter is less than the tolerated transmission delay in the first transmission parameter, and the allowed configuration authorization list in the second transmission parameter is more than the allowed configuration authorization list in the first transmission parameter; the second transmission parameter includes an activation indication of the Packet Data Convergence Protocol PDCP; the number of copy transmissions in the second transmission parameter is greater than the number of copy transmissions in the first transmission parameter; the number of retransmissions in the second transmission parameter is greater than the number of retransmissions in the first transmission parameter; and the order of the modulation and coding strategy in the second transmission parameter is lower than the order of the modulation and coding strategy in the first transmission parameter.

[0173] In an embodiment of the present application, the setting of the second transmission parameter helps to improve the transmission speed and transmission success rate of the first data. For example, compared with the first transmission parameter, the second transmission parameter makes the LCH associated with the first data have a higher priority, a higher priority bit rate, and more allowed configuration authorization lists, thereby making the transmission speed of the LCH associated with the first data faster than other LCHs. For another example, compared with the first transmission parameter, the second transmission parameter makes the PDCP retransmission of the LCH associated with the first data activated or has more copy transmission times, and the order of the modulation and coding strategy is lower, thereby making the first data successfully transmitted, or having a higher transmission success rate, compared with the data of other LCHs.

[0174] In some embodiments, the method shown in FIG3 may further include step S320 .

[0175] In step S320, if the first device is a terminal device and the second device is a network device, the first device sends the second information to the second device. Alternatively, the second device receives the second information sent by the first device. The second information can be used to request transmission resources, request transmission of the first data, or indicate a transmission requirement for the first data.

[0176] For example, if there is associated data transmission or related parameters for associated data transmission are configured, the terminal device can send a second message to the network device. For another example, during the transmission of first data, if transmitting the first data on the currently allocated resources may not meet the synchronization or coordinated transmission requirements of the first data, the terminal device can send a second message to the network device to request transmission resources, or in other words, request additional transmission resources.

[0177] In some embodiments, when the third condition is met, the first device may send the second information to the second device, and the third condition includes one or more of the following: at least one terminal device among the multiple terminal devices that are configured or associated, a terminal device that enables the first behavior, and at least one of the terminal devices that are identified as synchronized or associated; at least one LCH / LCG among the multiple LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; the first transmission parameter uses the first duration; the second transmission parameter is configured or used; data of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that are identified as synchronized or associated arrives; the transmission delay of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that are identified as synchronized or associated meets the thirteenth threshold. ; The data volume of the associated DRB / LCH, at least one DRB / LCH among the associated multiple DRB / LCHs, the DRB / LCH of the terminal device with the first behavior enabled, and one of the DRB / LCHs identified as synchronized or associated meets the fourteenth threshold; data of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device with the first behavior enabled, and one of the terminal devices identified as synchronized or associated arrives; data to be transmitted from the associated terminal device, or information about data to be transmitted, is received; the first device receives third information, and the third information is used for the terminal device associated with the first device to request the first device to send second information; the transmission delay of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device with the first behavior enabled, and one of the terminal devices identified as synchronized or associated meets the fifteenth threshold; the data volume of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device with the first behavior enabled, and one of the terminal devices identified as synchronized or associated meets the sixteenth threshold; and the network device instructs to enable or activate the first behavior.

[0178] For example, "satisfying a threshold" associated with the third condition can mean being greater than or equal to the threshold, or less than or equal to the threshold. As an example, "transmission delay meeting the fifteenth threshold" can mean that the remaining transmission delay is greater than or equal to the fifteenth threshold, or that the tolerated transmission delay is less than or equal to the fifteenth threshold. It should be noted that the fifteenth threshold corresponding to different types of transmission delay can be the same or different.

[0179] In some embodiments, when a terminal device requests resources from a network device, it may directly initiate a resource request or report the status of the first data, such as cache and / or transmission status, to the network device to indicate its resource requirements. In other embodiments, when a terminal device requests resources from a network device, it may also simultaneously report the status of the first data, such as cache and / or transmission status, to provide reference information for resource allocation by the network device.

[0180] For example, the first device may send fourth information to the second device, where the fourth information is used to indicate the cache status or transmission status of the first data. As mentioned above, the first device mentioned here may be a terminal device, and the second device may be a network device.

[0181] If the logical channel associated with the first data, or the associated logical channels include a first LCH and a second LCH, the fourth information may be used to indicate one or more of the following: an association relationship between the first LCH and the second LCH; an identifier of the first LCH or a corresponding DRB; an identifier of the second LCH or a corresponding DRB; a transmission delay and / or data size of the first LCH; and a transmission delay and / or data size of the second LCH. The first LCH and the second LCH are associated logical channels.

[0182] If the first data is associated with multiple terminal devices, or the associated terminal devices include the first terminal device and the second terminal device, or the associated logical channel corresponds to the first terminal device and the second terminal device, the fourth information can be used to indicate one or more of the following: the association relationship between the first terminal device and the second terminal device; the identification of the first terminal device; the identification of the second terminal device; the identification of the DRB / LCH with an associated relationship of the first terminal device; the identification of the DRB / LCH with an associated relationship of the second terminal device; the transmission delay and / or data size of the first terminal device; the transmission delay and / or data size of the second terminal device; the transmission delay and / or data size of the associated logical channel of the first terminal device; and the associated transmission delay and / or data size of the second terminal device.

[0183] In some embodiments, the transmission delay and / or data volume of the above-mentioned first terminal device and the transmission delay and / or data volume of the second terminal device can be the transmission delay and / or data volume for each terminal device, or the transmission delay and / or data volume for each LCH in the terminal device, or the transmission delay and / or data volume for each data packet in the terminal device.

[0184] In other embodiments, the transmission delay and / or data volume of the first terminal device may include the transmission delay and / or data volume of an LCH with an associated relationship within the first terminal device, and may also include the transmission delay and / or data volume of an LCH with no associated relationship within the first terminal device. The transmission delay and / or data volume of the second terminal device may include the transmission delay and / or data volume of an LCH with an associated relationship within the second terminal device, and may also include the transmission delay and / or data volume of an LCH with no associated relationship within the second terminal device.

[0185] In some embodiments, the fourth information may be used to indicate information associated with a specific LCH, where the specific LCH may be a more important portion of the multiple LCHs associated with the first data. By reporting the relevant information of the specific LCH, the amount of reported data can be reduced, which helps to save resource overhead.

[0186] In some embodiments, the second information and / or the fourth information may be carried in a medium access control control element (MAC CE), uplink control information (UCI) or a scheduling request (SR).

[0187] In some cases, such as when part or all of the first data cannot be transmitted, or when part or all of the first data is useless or invalid, the first device and / or the second device needs to delete part or all of the first data. The case where part or all of the first data is useless or invalid mentioned here can be, for example, retransmission of the first data when the receiving end has already received the first data.

[0188] In some embodiments, the first device deletes part or all of the first data, or the first device deletes part or all of the first data based on the first information, or the first device deletes part or all of the first data when the first behavior is enabled or activated.

[0189] If the first device deletes part or all of the first data, the second device also needs to delete the related data. In some embodiments, the first device may send fifth information to the second device to indicate the data deleted by the first device; data associated with the data deleted by the first device, or data that the second device needs to delete. For example, the fifth information may be used to indicate one or more of the following: an identifier indicating that there are lost or delayed data packets; an indication that a data packet does not need to be transmitted or is considered received; an indication that part or all of the data in the first data cannot be transmitted; a request to the second device to delete part or all of the data in the first data; an identifier indicating the data that cannot be transmitted in the first data; or an identifier indicating the data to be deleted in the first data. If the transmission of the first data involves a first terminal device and a second terminal device, the second device may be a first network device corresponding to the first terminal device, or a second network device corresponding to the second terminal device.

[0190] The above introduces the synchronous or coordinated transmission method of the first data based on DRB / LCH / LCP. The following will introduce the synchronous or coordinated transmission method of the first data based on DRB / PDCP.

[0191] In some embodiments, the first information may include second configuration information, where the second configuration information is used to configure a DRB / PDCP, or to configure one or more terminal devices. A mapping relationship exists between the DRB / PDCP and the first data, and / or a mapping relationship exists between the multiple terminal devices and the first data. That is, the second configuration information may be used to configure a DRB / PDCP / terminal device associated with the first data.

[0192] For example, the second configuration information may be used to indicate or identify that the DRB / PDCP / terminal device associated with the first data has a synchronization or coordinated transmission requirement. As an example, the second configuration information may be used to indicate that the DRB / PDCP has a synchronization or coordinated transmission requirement, or the second configuration information may be used to identify the DRB / PDCP with the associated or synchronization or coordinated transmission requirement, or the second configuration information may be used to identify multiple terminal devices with the associated or synchronization or coordinated transmission requirement.

[0193] For another example, the second configuration information may be used to enable or activate deletion of data packets based on association relationships, or the second configuration information may be used to enable or activate sending / triggering behavior of the first information.

[0194] For another example, the second configuration information may be used to indicate or identify the association relationship of the DRB / PDCP associated with the first data. The association relationship may be indicated or identified explicitly or implicitly. As an example, the explicit indication or identification of the association relationship may refer to identifying the association flag and / or the associated DRB / PDCP, and the implicit indication or identification of the association relationship may refer to configuring the same or similar underlying parameters, such as LCH parameters, for the DRB / PDCP with the association relationship.

[0195] In some cases, or in other words, when certain conditions are met, such as when the first data transmission is successful, or when the first data transmission fails, or when the first data is no longer needed, or when part or all of the first data is deleted, it is necessary to delete part or all of the first data in the first device and / or the second device. If the first device deletes part or all of the first data, the first device may, for example, send first indication information to the second device to indicate information associated with the deleted data.

[0196] In some embodiments, when the fourth condition is met, the first device may send a first indication message to the second device, wherein the fourth condition includes one or more of the following: an associated data packet is deleted; a transmission failure indication is received from the second device; N transmission failure indications are received from the second device; a transmission failure indication is received from the second device within a third time period; the successfully transmitted PDU / PDU set meets the first ratio; the number of successfully transmitted PDU / PDU sets meets the seventeenth threshold; the PDU / PDU set at a specific location is not transmitted or is successfully transmitted; and a PDU / PDU set of a specific type is not transmitted or is successfully transmitted.

[0197] The above-mentioned transmission failure indication may be a transmission failure indication for a data packet, or a transmission failure indication for any data packet in the PDCP / RLC / terminal device cache, or a transmission failure indication for a data packet with a specific identifier in the PDCP / RLC / terminal device cache.

[0198] The transmission failure indication may be carried in a PDCP / RLC status report, for example, or may be indicated via a hybrid automatic repeat-request (HARQ) or a negative acknowledgement (NACK).

[0199] In some embodiments, the first indication information may indicate data deletion information of the first device, or the first indication information may indicate information about data that needs to be deleted by the second device, or the first indication information may indicate data deletion information of the first device and data information associated with the deleted data.

[0200] For example, if the associated DRB / PDCP includes a first data packet and a second data packet, the first indication information can be used to indicate one or more of the following: indicating the existence of an associated terminal device identifier; indicating the existence of an associated DRB / PDCP identifier; indicating the existence of an identifier of a delayed or lost data packet; indicating the identifier of the first data packet; indicating the identifier of the data packet associated with the first data packet; indicating the identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH corresponding to the first data packet; indicating the identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH of the data packet associated with the first data packet; indicating the identifier of the terminal device associated with the first data packet; indicating the identifier of the corresponding terminal device of the data packet associated with the first data packet; indicating that the first data packet is not needed; indicating that the first data packet and the second data packet are not needed; indicating deletion information of the first data packet; instructing the network device to delete the first data packet; and instructing the network device to delete the first data packet and the second data packet. The identifier of the data packet mentioned here can be, for example, the serial number of the data packet.

[0201] It should be noted that the association relationship between the first data packet and the second data packet may be indicated in the first indication information, or may be carried in the PDU or the header of the data packet.

[0202] For another example, if part of the first data is deleted, the other data in the first data may be deleted, or the first data may be deleted. For example, if the PDU set or PDU to which the first data packet belongs is deleted, the first device may delete the second data packet.

[0203] In some embodiments, the first indication information may be deletion indication information for a specific data packet, or a terminal device, or a QoS flow / DRB / PDCP / RLC, or a data packet cached by the terminal device. The specific data packet mentioned here may be a data packet with a specific identifier, or a data packet with a specific priority.

[0204] In order to improve the transmission performance of the first data, the method shown in FIG3 may further include step S330.

[0205] In step S330 , the first device activates or deactivates the data packet-based copy transmission, or the first device activates or deactivates the data packet-based copy transmission according to the first information.

[0206] In some embodiments, the first device may activate or deactivate the copy transmission of the associated data packet, or the first device may activate or deactivate the copy transmission of the associated data packet according to the first information.

[0207] For example, if the transmission delay of the first data meets the threshold, such as the remaining transmission delay is greater than or equal to the threshold, or the tolerable transmission delay is less than or equal to the threshold, the first device can activate the copy transmission to improve the transmission success rate of the first data and reduce the transmission delay of the first data. For another example, if the transmission delay of the first data meets the threshold, such as the remaining transmission delay is less than or equal to the threshold, or the tolerable transmission delay is greater than or equal to the threshold, the first device can deactivate the copy transmission. In this way, it can help improve the overall performance of the system while meeting the synchronization or collaborative transmission requirements of the first data. For another example, when the behavior that supports associated data transmission is enabled or activated, such as the first behavior mentioned above, the copy transmission can be activated to improve the synchronization or collaborative transmission performance of the first data.

[0208] As an example, the first device activates the copy transmission when one or more of the following conditions are met: the transmission delay of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the eighteenth threshold; the transmission delay of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the nineteenth threshold; and the network device instructs the enabling or activation of the first behavior.

[0209] In order to reduce system overhead, after activating the duplicate transmission of the associated data packet for a fourth time period, the first device may deactivate the duplicate transmission of the associated data packet.

[0210] The copy transmission may be configured to target one or more of the following: all data packets; specific data packets; each PDU; and each PDU set.

[0211] The following describes a support solution for synchronous or coordinated transmission of first data from the perspective of network scheduling, allocation or configuration of transmission resources.

[0212] In some embodiments, the first information described above may further include sixth information, where the sixth information may be used to indicate a first transmission resource of the terminal device, where the first transmission resource is used to transmit the first data. For example, the sixth information may include an identifier of the first transmission resource or an identifier of a specific DRB / LCH / terminal device.

[0213] In some embodiments, the sixth information may be carried in radio resource control RRC configuration and / or DCI signaling.

[0214] In some embodiments, the first transmission resource may be a configured authorization resource or a dynamic authorization resource.

[0215] In some embodiments, the first transmission resource may include one or more transmission resources. For example, the CG may include one or more uplink or downlink transmission resources within a period. If the first transmission resource includes multiple transmission resources, the multiple transmission resources may be continuous or discontinuous resources, such as resources that are not equally spaced within a period.

[0216] In some embodiments, the configuration information of the associated DRB / PDCP / LCH may include a synchronization or coordinated transmission requirement identifier, or a synchronization or coordinated transmission association relationship. The LCH mapping restrictions of the associated DRB / PDCP / LCH may be the same or different, such as the same LCH priority, the same available DG, and the same available CG.

[0217] For example, the association relationship of synchronous or coordinated transmission can be explicitly indicated or identified, or can be implicitly indicated or identified. As an example, the explicit indication or identification of the association relationship can refer to identifying the association flag and / or the associated DRB / PDCP, and the implicit indication or identification of the association relationship can refer to configuring the same or similar underlying parameters, such as LCH parameters, for the DRB / PDCP with the association relationship.

[0218] In some embodiments, specific configured authorization resources and / or specific dynamic authorization resources can be used to transmit data of a specific DRB / LCH / terminal device, or to transmit data of an associated DRB / PDCP / LCH.

[0219] In some embodiments, the terminal device may request additional transmission resources from the network device to support synchronous or coordinated transmission of the first data. For example, the method shown in FIG3 may further include step S340.

[0220] In step S340, if the first device is a terminal device and the second device is a network device, the first device sends second indication information to the second device. Alternatively, the second device receives the second indication information sent by the first device. The second indication information can be used to request a second transmission resource, which is used to transmit the first data.

[0221] In some embodiments, the second indication information may also indicate the transmission status of the first data, or information associated with the transmission of the first data. For example, the second indication information may be used to indicate one or more of the following: at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, or at least one terminal device that is identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, or at least one LCH / LCG that is identified as synchronized or associated; at least one of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, or a DRB / LCH that is identified as synchronized or associated is not transmitted or is not transmitted. Success; the transmission delay of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the amount of data to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the identification of the DRB / LCH in the associated DRB / LCH that was not transmitted or was not successfully transmitted; and the identification of the DRB / LCH associated with the DRB / LCH that was not transmitted or was not successfully transmitted.

[0222] The second indication information may be a general indication, that is, indication information for all associated DRBs / LCHs, or may be indication information for 1□ DRBs.

[0223] In some embodiments, the second indication information may be carried in MAC CE signaling or UCI, such as unused transmission occasion (UTO).

[0224] In some embodiments, if the transmission resources of the first DRB / LCH / terminal device include multiple transmission opportunities, such as multiple transmission opportunities with configured authorization or dynamic authorization, the usage strategy of the above multiple transmission opportunities can be adjusted to support the synchronous or coordinated transmission of the first data.

[0225] For example, the transmission resources of the first DRB / LCH / terminal device can be used to transmit information or data of the second DRB / LCH / terminal device, where the first DRB / LCH is associated with the second DRB / LCH.

[0226] As an example, if the first DRB / LCH / terminal device has no data to be transmitted and the second DRB / LCH / terminal device has data to be transmitted, the information or data of the second DRB / LCH / terminal device is transmitted using one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device.

[0227] As another example, if a first DRB / LCH / terminal device has data to be transmitted, a second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

[0228] As another example, if a first DRB / LCH / terminal device has data to be transmitted, a second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, then no padding is added, and / or, the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

[0229] In some embodiments, the priority of transmission resources, or the priority of authorization, can be determined based on the association relationship of DRB / LCH / terminal device to support the synchronous or coordinated transmission of the first data. For example, the authorization corresponding to the associated DRB / LCH / terminal device can be transmitted preferentially. For another example, the priority of the transmission resources corresponding to the associated DRB / LCH can be higher than the priority of the transmission resources corresponding to the non-associated DRB / LCH. For another example, in the process of determining the priority of transmission resources, the synchronous or coordinated transmission requirements of the associated data are considered, such as the tolerated transmission delay, or the remaining transmission delay, or the data volume of the associated data.

[0230] As an example, the priority of the transmission resource or the priority of authorization can be determined based on one or more of the following: whether at least one of the multiple associated terminal devices, the terminal device with the first behavior enabled, and at least one of the terminal devices identified as synchronized or associated is configured or exists; whether at least one of the multiple associated LCH / LCGs, the LCH / LCG with the first behavior enabled, and at least one of the LCH / LCGs identified as synchronized or associated is configured or exists; whether the second transmission parameter is configured or used; whether the transmission resource carries the first data; whether the priority of the transmission resource is higher than the twentieth threshold; whether the transmission resource is a specific transmission resource; whether the transmission delay of the first data is less than or equal to the twenty-first threshold; whether the data volume of the first data is greater than or equal to the twenty-second threshold; whether the data that can be carried on the transmission resource has an associated relationship; whether the transmission delay of the data that can be carried on the transmission resource meets the twenty-third threshold; whether the amount of data to be transmitted of the data that can be carried on the transmission resource meets the twenty-fourth threshold.

[0231] The above-mentioned specific transmission resource may refer to a transmission resource with a specific identifier, or a transmission resource with a specific priority.

[0232] In some embodiments, the priority of the hybrid automatic repeat request HARQ process can be determined based on the association relationship between DRB / LCH / terminal device, or the associated HARQ process can be transmitted using transmission resources. For example, the HARQ process corresponding to the associated DRB / LCH can be transmitted preferentially. For another example, the priority of the HARQ process corresponding to the associated DRB / LCH can be higher than the priority of the HARQ process corresponding to the non-associated DRB / LCH. For another example, in the process of determining the priority of the HARQ process, the synchronization or coordinated transmission requirements of the associated data are considered, such as the tolerated transmission delay, or the remaining transmission delay, or the data volume of the associated data.

[0233] For example, the priority of the HARQ process can be determined based on one or more of the following: whether at least one of the multiple associated terminal devices, the terminal device with the first behavior enabled, and the terminal device identified as synchronized or associated is configured or exists; whether the second transmission parameter is configured or used; whether the HARQ process corresponds to at least one of the multiple associated terminal devices, the terminal device with the first behavior enabled, and the terminal device identified as synchronized or associated; whether the HARQ process corresponds to at least one LCH / LCG among the multiple associated LCH / LCGs, the LCH / LCG with the first behavior enabled, and the LCH / LCG identified as synchronized or associated; whether the HARQ process corresponds to the LCH / LCG configured or using the second transmission parameter; whether the HARQ process corresponds to the terminal device configured or using the second transmission parameter; whether the transmission resource carries the first data; whether the priority of the transmission resource is higher than the twenty-fifth threshold; whether the transmission resource is a specific transmission resource; whether the HARQ process corresponds to the first data; whether the transmission delay of the data corresponding to the HARQ process is less than or equal to the twenty-sixth threshold; whether the amount of data corresponding to the HARQ process is greater than or equal to the twenty-seventh threshold; can be carried on the HARQ whether the data of the processes are associated; whether the transmission delay of the data that can be carried in the HARQ process meets the twenty-eighth threshold; and whether the amount of data to be transmitted that can be carried in the HARQ process meets the twenty-ninth threshold.

[0234] In some embodiments, if there is an associated DRB / LCH, the transmitting end or the receiving end may cache the associated data and send it to the opposite end or the upper layer when all the associated data have arrived.

[0235] For example, the first device may cache the first data; when all the first data arrives, the first device sends the first data to the second device.

[0236] For another example, the second device receives first data sent by the first device; the second device buffers the first data; when all the first data arrives, the second device sends the first data to a higher layer, such as an RLC entity.

[0237] As mentioned above, the transmission of first data may involve one or more terminal devices. When the transmission of first data involves multiple terminal devices, the multiple terminal devices may correspond to the same network device or different network devices. The following describes methods for interacting with information associated with the first data in various situations described herein.

[0238] In some embodiments, the information associated with the first data may include an association relationship, such as an association relationship between a terminal device, a quality of service flow, and a DRB / PDCP / RLC / PDU (i.e., the seventh information), or the information associated with the first data may include configuration information of the associated DRB / LCH or update information of the configuration information (i.e., the eighth information), or if the transmission of the first data involves a first terminal device and a second terminal device, the information associated with the first data may include information associated with the first terminal device and / or the second terminal device (i.e., the ninth information), such as configuration information and / or allocated or scheduled resource information, etc.

[0239] For example, the first device may send seventh information to the second device, and the seventh information may be used to indicate an association relationship between the terminal device, the quality of service flow, and the DRB / PDCP / RLC / PDU, or to indicate a need for an association relationship.

[0240] As an example, the seventh information can be used to indicate one or more of the following: association / co-transmission / synchronization or co-transmission requirements between terminal devices; association / co-transmission / synchronization or co-transmission requirements of service quality flows; association / co-transmission / synchronization or co-transmission requirements between DRB / PDCP / RLC; and association / co-transmission / synchronization or co-transmission requirements of packet data unit PDU sessions.

[0241] Optionally, the first device may send the seventh information to the second device under specific circumstances. For example, if the seventh information changes, and / or the seventh information has not been reported, and / or the seventh information is obtained, the first device may send the seventh information to the second device. Optionally, the first device may periodically send the seventh information to the second device.

[0242] For another example, the first device may send eighth information to the second device, where the eighth information may be used to indicate configuration information of the associated DRB / LCH or update information of the configuration information.

[0243] For another example, the first device may send ninth information to the second device, and the ninth information may be related to the first terminal device and / or the second terminal device. The first terminal device and the second terminal device have a mapping relationship with the associated DRB / LCH, where the first device is the first network device corresponding to the first terminal device, and the second device is the second network device corresponding to the second terminal device.

[0244] Optionally, the ninth information may include one or more of the following: resource information allocated or scheduled by the first network device to the first terminal device; recommended information for the second network device to allocate or schedule resources for the second terminal device; RRC signaling configured by the first network device for the first terminal device; recommended information for the second network device to configure RRC for the second terminal device; mapping relationship between QoS flow and DRB / LCH / PDCP configured by the first network device for the first terminal device; recommended information for the second network device to configure QoS flow and DRB / LCH / PDCP mapping relationship for the second terminal device; at least one of the time information, timestamp information and associated information of the first terminal device; and at least one of the time information, timestamp information and associated information of the second terminal device.

[0245] In some embodiments, the second device can determine one or more of the following information of the second terminal device based on the ninth information: whether the first behavior is enabled; resource scheduling or allocation information; configured RRC signaling; QoS flow and DRB / LCH / PDCP mapping relationship; and association information of the second terminal device.

[0246] In some embodiments, the first device may obtain the ninth information from a core network node, a network device, or a high layer of a terminal device.

[0247] In some embodiments, the ninth information may be information about an associated DRB / LCH / PDCP, an associated terminal device, or an associated QoS flow, or an associated PDU session.

[0248] In some embodiments, the ninth information may be exchanged through the N2 interface.

[0249] If the transmission of the first data involves a first terminal device, and the first terminal device corresponds to a first network device, the first device may be the first terminal device, and the second device may be the first network device. In other words, the first terminal device may exchange the above-mentioned one or more types of information with the first network device.

[0250] If the transmission of the first data involves a first terminal device and a second terminal device, and the first terminal device and the second terminal device correspond to a first network device and a second network device, respectively, the first device may be the first network device and the second device may be the second network device. In other words, the first network device and the second network device may exchange one or more of the above-mentioned information.

[0251] If the transmission of the first data involves a first terminal device and a second terminal device, and both the first terminal device and the second terminal device correspond to a first network device, the first device can be the first terminal device and / or the first network device, and the second device can be the first network device and / or the second terminal device. In other words, the first terminal device and the second terminal device can exchange the above-mentioned one or more types of information through the first network device.

[0252] By exchanging the configuration of the first terminal device and / or the second terminal device, or resource scheduling information, or information such as the association relationship between the first network device and the second network device, the configuration and scheduling strategy of the first data can be determined based on the association relationship. For example, the first network device can determine the resource scheduling and allocation method of the first terminal device based on the resources allocated by the second network device to the second terminal, thereby helping to reduce the complexity of the synchronization or collaborative transmission method of the first data.

[0253] It should be noted that whether the first device and / or the second device performs the first behavior, whether or how to identify the association or synchronization information, and whether / how to report or interact with the association or synchronization information can be controlled by the CN or the base station.

[0254] An embodiment of the present application provides another method for wireless communication, which facilitates synchronous or coordinated transmission of first data through data packet-based PDCP data replication transmission.

[0255] Figure 4 is a schematic flow chart of a method for wireless communication provided by another embodiment of the present application. The method shown in Figure 4 is introduced from the perspective of interaction between a terminal device and a network device, and the method may include step S410.

[0256] In step S410, the terminal device receives the tenth information sent by the network device. Alternatively, the network device receives the tenth information sent by the terminal device. The tenth information may be used to indicate configuration information for PDCP data replication transmission based on a data packet.

[0257] In some embodiments, the tenth information may indicate a data packet for which the packet-based PDCP data copy transmission method may be configured, activated, or used, or may indicate a data packet for which the packet-based PDCP data copy transmission method may not be configured, activated, or used.

[0258] In some embodiments, whether packet-based PDCP data replication transmission can be configured, activated, or used for a data packet can be determined based on the importance level of the data packet. The level mentioned here can be a level index, a grade, or a high or low level indication; the importance can be a priority, reliability, etc.; the importance level can be, for example, the importance level of a PDU set or a data packet.

[0259] In some embodiments, the tenth information may further indicate an initial state, such as an importance level of the activatable packet-based PDCP data copy transmission corresponding to the initial state.

[0260] In some embodiments, the tenth information can be used to indicate one or more of the following: the importance level of the activatable packet-based PDCP data copy transmission corresponding to the initial state; the PDU set importance level using the configuration information; the importance level of the data packet using the packet-based PDCP data copy transmission; indicating that the data packet meeting a specific PDU set importance level uses the packet-based PDCP data copy transmission; indicating that the data packet or PDU set greater than or equal to the first importance level uses the packet-based PDCP data copy transmission.

[0261] If the tenth information includes configuration information of packet-based PDCP data copy transmission, the tenth information can be used to indicate whether packet / PDU set-based PDCP data copy transmission is enabled, or the tenth information can be used to indicate the initial state of packet / PDU set-based PDCP data copy transmission, such as activation or deactivation.

[0262] In some embodiments, the tenth information may be configuration information for the terminal device, and / or the tenth information may be configuration information for the data radio bearer DRB / PDCP.

[0263] In some embodiments, the tenth information may be carried in radio resource control RRC signaling, and / or the tenth information may be carried in PDCP configuration information.

[0264] In some embodiments, the method shown in FIG. 4 may further include step S420 .

[0265] In step S420, the terminal device receives the eleventh information sent by the network device. Alternatively, the network device sends the eleventh information to the terminal device. The eleventh information is used to indicate activation or deactivation of data packet-based PDCP data replication transmission.

[0266] In some embodiments, the eleventh information may be carried in DCI, MAC CE, or RRC signaling.

[0267] In some embodiments, the eleventh information may be control signaling for the terminal device, or for all DRBs, or for one or more DRBs. For example, the eleventh information may be control signaling for one DRB, or for several DRBs, or for one or more specific DRBs. For another example, if the DRBs associated with the first data include a first DRB and a second DRB, the eleventh information may be control signaling for the first DRB, or for the first DRB and the second DRB.

[0268] In some embodiments, the eleventh information may include a logical channel identification (LCID), and the LCID may be used to identify or recognize the eleventh information. For example, the eleventh information is carried in MAC CE signaling, and the LCID may be an identifier carried in a header of the MAC CE.

[0269] In some embodiments, the eleventh information may include PDCP duplicate transmission activation / deactivation indication information for PDU set, or PDCP activation / deactivation indication information for data packet, or PDCP duplicate transmission activation / deactivation indication information for PDU.

[0270] In some embodiments, the method shown in FIG. 4 may further include step S430 .

[0271] In step S430, the terminal device receives the twelfth information sent by the network device, or the network device sends the twelfth information to the terminal device. The twelfth information may be used to indicate activation or deactivation of PDCP data replication transmission based on DRB or RLC.

[0272] If the terminal device receives the eleventh information and the twelfth information, the terminal device may use packet-based PDCP data replication transmission (i.e., determine the replication transmission strategy according to the eleventh information), or may use DRB- or RLC-based PDCP data replication transmission (i.e., determine the replication transmission strategy according to the twelfth information); or, the terminal device determines the replication transmission strategy to be used based on the importance level of the packet.

[0273] For example, the terminal device determines the copy transmission strategy to be used based on the importance level of the data packet, which may include: data packets greater than or equal to the second importance level use all the first transmission resources for copy transmission, and data packets less than or equal to the second importance level use part of the first transmission resources for copy transmission; or, data packets greater than or equal to the third importance level use all the first transmission resources for copy transmission, and data packets less than or equal to the third importance level are not copied and transmitted; or, data packets greater than or equal to the fourth importance level use part of the first transmission resources for copy transmission, and data packets less than or equal to the fourth importance level are not copied and transmitted; or, data packets greater than or equal to the second importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the second importance level are not copied and transmitted; or, data packets greater than or equal to the third importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the third importance level are not copied and transmitted; or, data packets greater than or equal to the fourth importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the fourth importance level are not copied and transmitted; or The data packets at the second importance level have their copy transmission policy determined based on the eleventh information, and the data packets less than or equal to the second importance level have their copy transmission policy determined based on the twelfth information; or, the data packets at or above the third importance level have their copy transmission policy determined based on the eleventh information, and the data packets less than or equal to the third importance level have their copy transmission policy determined based on the twelfth information; or, the data packets at or above the fourth importance level have their copy transmission policy determined based on the eleventh information, and the data packets less than or equal to the fourth importance level have their copy transmission policy determined based on the twelfth information; or, the data packets at or above the second importance level have their copy transmission policy determined based on the twelfth information, and the data packets less than or equal to the second importance level have their copy transmission policy determined based on the eleventh information; or, the data packets at or above the third importance level have their copy transmission policy determined based on the twelfth information, and the data packets less than or equal to the third importance level have their copy transmission policy determined based on the eleventh information; or, the data packets at or above the fourth importance level have their copy transmission policy determined based on the twelfth information, and the data packets less than or equal to the fourth importance level have their copy transmission policy determined based on the eleventh information.

[0274] In some embodiments, the eleventh information may include one or more of the following: a DRB identifier; an LCH identifier; a data packet importance level; and an identifier of the LCH used by data packets of a specific importance level.

[0275] It should be noted that the first duration, second duration, third duration and fourth duration mentioned in the embodiments of the present application can all be achieved through corresponding timers.

[0276] When a terminal device moves from one cell to another, in order to ensure the communication quality of the terminal device, the terminal device can perform cell handover. Figure 5 is a flowchart of a method for wireless communication provided by another embodiment of the present application to solve the problem of supporting synchronous or coordinated transmission of first data during cell handover.

[0277] The method shown in Figure 5 is described from the perspective of the interaction between a first network device, a second network device, and a terminal device, wherein the first network device is the source network device of the terminal device, and the second network device is the candidate target network device of the terminal device. In other words, the first network device is the network device corresponding to the serving cell of the terminal device, and the second network device is the network device corresponding to the candidate target cell of the terminal device.

[0278] The method shown in FIG. 5 may include step S510 .

[0279] In step S510, the first network device sends a cell handover request to the second network device. Alternatively, the second network device receives the cell handover request sent by the first network device. The exchange of cell handover requests executes a cell handover process for the terminal device. The cell handover process may be determined based on thirteenth information. The thirteenth information is related to the transmission of the first data, and the first data is associated data.

[0280] In some embodiments, the thirteenth information may include one or more of the following information: the association relationship of service quality flows; the association relationship between multiple terminal devices; and whether PDU set is enabled; wherein the multiple terminal devices are receivers and / or senders of the first data.

[0281] The embodiment of the present application determines the cell switching process, such as determining the target cell, or determining the transmission strategy of the first data after the cell switching, through the thirteenth information associated with the first data. During the cell switching process, the processing of related data can be considered, thereby facilitating the synchronous or coordinated transmission of the first data.

[0282] In some embodiments, the thirteenth information may be obtained by the first network device or the second network device. The following describes a method for the first network device to obtain the thirteenth information and a method for the second network device to obtain the thirteenth information.

[0283] In some embodiments, the first network device may obtain the thirteenth information before sending the cell switching request. For example, the method shown in FIG5 may further include step S520.

[0284] In step S520, the first network device receives the thirteenth information sent by the terminal device or the core network node, or the terminal device sends the thirteenth information to the first network device.

[0285] Step S520 may be performed before step S510, that is, before the first network device sends a cell handover request to the second network device, step S520 is performed.

[0286] For example, the terminal device may use a UEassistanceInformation message to send the thirteenth information to the first network device, or the thirteenth information may be carried in the UEassistanceInformation message.

[0287] In some embodiments, the core network node may be one or more of the following: an application function network element; a user plane function network element; a mobility management function network element; and a session management function network element.

[0288] In some embodiments, the thirteenth information may be sent / received periodically. In other embodiments, the thirteenth information may be sent / received under specific circumstances to save overhead. For example, the first network device receives the thirteenth information sent by the terminal device when one or more of the following conditions are met: the terminal device has not sent the thirteenth information to the first network device; the terminal device establishes or modifies part or all of the content of the thirteenth information; the terminal device initiates a service request; the reporting prohibition timer is not running; and part or all of the content of the thirteenth information changes.

[0289] In some embodiments, the cell handover request message may include thirteenth information, where the thirteenth information is associated with the terminal device, such as the thirteenth information including relevant information about the first data associated with the terminal device. For example, if the first data is associated with multiple QoS flows, the thirteenth information may include the QoS flow associated with the terminal device among the multiple QoS flows. For another example, if the first data involves multiple terminal devices, the thirteenth information may include information about other terminal devices associated with the terminal device.

[0290] In some embodiments, the first network device may receive the fourteenth information sent by the second network device. Alternatively, the second network device may send the fourteenth information to the first network device. The fourteenth information is a response message to the handover request message, and the fourteenth information is determined based on the thirteenth message.

[0291] For example, the fourteenth information may include whether the second network device supports terminal device access. For another example, if the second network device does not support the terminal device access, the fourteenth information may also include the reason why the second network device does not support the terminal device access, such as the second network device does not support PDU set, and / or the second network device does not support the transmission of the first data. As an example, the fourteenth information may include one or more of the following: whether the second network device supports terminal device access; whether the second network device supports PDU set; and whether the second network device supports the transmission of the first data.

[0292] In some embodiments, the first network device may determine whether the second network device is the target network device of the terminal device based on the fourteenth information.

[0293] In order to reduce the interaction between the first network device and the second network device and lower the overhead, the first network device may initiate a cell switching request based on the second network device's transmission capability to support related data.

[0294] In some embodiments, before the first network device sends a cell switching request to the second network device, the first network device may obtain thirteenth information, which may be information associated with the second network device, such as whether the second network device supports the transmission of associated data, or whether the second network device supports PDU set.

[0295] For example, the thirteenth information may include one or more of the following information: the association relationship of service quality flows; the association relationship between multiple terminal devices; and whether PDU set is enabled; wherein the multiple terminal devices are receivers and / or senders of the first data.

[0296] In some embodiments, the first network device may obtain the thirteenth information from a core network node, an operation and maintenance management (OAM), a network device adjacent to the first network device, or the second network device.

[0297] The core network node may be, for example, one or more of the following: an application function network element; a user plane function network element; a mobility management function network element; and a session management function network element.

[0298] In some embodiments, the first network device may obtain the thirteenth information in response to one or more of the following situations: a request from the first network device; an update of the thirteenth information; a periodic update time; establishment of an interface between the second network device and the first network device; establishment of an interface between the second network device and the core network node; and acquisition of the thirteenth information.

[0299] In some embodiments, the first network device may send a cell handover request to the second network device based on the thirteenth information. For example, if there are multiple second network devices, the first network device may not select a network device that does not support the first data transmission and / or does not support PDU set; or the first network device may select or prioritize a network device that supports the first data transmission and / or supports PDU set.

[0300] In some embodiments, the first data may include associated multimodal data streams and / or associated data packets.

[0301] In order to facilitate the target network device to process the first data, such as processing the first data transmitted before cell switching, the first network device may send information associated with the first data to the second network device. For example, the first network device may send the transmission delay of the first data to the second network device; or the first network device may send the transmission delay of the PDU set to which the first data belongs to the second network device; or the transmission delay of the data, data packet, or PDU set associated with the first data sent by the first network device to the second network device. For another example, the first network device may send the identifier of the PDU set that does not meet the delay requirement to the second network device.

[0302] The following describes a method for the second network device to obtain the thirteenth information.

[0303] In some embodiments, the second network device may obtain thirteenth information associated with the terminal device. For example, the thirteenth information may include one or more of the following information: an association relationship of a quality of service flow; an association relationship between multiple terminal devices; and whether PDU set is enabled; wherein the multiple terminal devices are receivers and / or senders of the associated data.

[0304] The second network device may obtain the thirteenth information before receiving the cell switching request sent by the first network device, when the second network device receives the cell switching request sent by the first network device, or after the second network device receives the cell switching request sent by the first network device.

[0305] In some embodiments, the second network device may obtain the thirteenth information from a core network node or an operation and maintenance management (OAM), or obtain the thirteenth information from the first network device. For example, the core network node may be one or more of the following: an application function network element; a user plane function network element; a mobility management function network element; and a session management function network element.

[0306] In some embodiments, the second network device obtains the thirteenth information in response to one or more of the following situations: a request from the second network device; an update of the thirteenth information; a periodic update time; establishment of an interface between the second network device and the first network device; establishment of an interface between the second network device and the core network node; and acquisition of the thirteenth information.

[0307] In some embodiments, the second network device may send fourteenth information to the first network device, where the fourteenth information is a response message to the handover request message, and the fourteenth information is determined based on the thirteenth message.

[0308] In some embodiments, the fourteenth information may include one or more of the following: whether the second network device supports terminal device access; whether the second network device supports PDU set; and whether the second network device supports transmission of the first data.

[0309] When the terminal device switches to the second network device, the terminal device may report the thirteenth information to the second network device, such as reporting the thirteenth information via a UEassistanceInformation message. Alternatively, the second network device may obtain the thirteenth information from the terminal device. The thirteenth information is associated with the terminal device, such as whether the terminal device supports PDU set and association relationship information.

[0310] In some embodiments, when one or more of the following conditions are met, the second network device can receive or obtain the thirteenth information sent by the terminal device: the terminal device receives a cell switching command; the terminal device has not reported the thirteenth information to the first network device; the terminal device has not reported the thirteenth information; the terminal device reports the thirteenth information within the first time (such as the last 1s) before the cell switching; the second network device requests the terminal device to send the thirteenth information; and the terminal device is configured to report the thirteenth information to the target network device after the cell switching.

[0311] Based on the thirteenth information reported by the terminal device, the second network device can adjust the resource configuration or DRB parameters to support the transmission of the first data.

[0312] After the terminal device switches to the second network device, the second network device needs to perform relevant processing on the first data to support the continuity of its synchronous or coordinated transmission.

[0313] If the first network device does not support the transmission of associated data, or does not support the PDU set operation, the second network device may add relevant information of the PDU set to the first data / data packet, or the second network device may add header information to the first data / data packet, wherein the first data / data packet is part of the first data transmitted by the first network device before the terminal device performs cell switching, and the header information indicates relevant information of the PDU set or indicates the PDU set to which the data packet belongs.

[0314] If the first data / data packet is successfully transmitted or fails to be transmitted, or if the first data / data packet is no longer needed, the second network device may delete the first data / data packet, or data associated with the first data. For example, if the transmission delay of the first data / data packet is greater than or equal to a first threshold, the second network device may delete the first data / data packet. For another example, if the transmission delay of the first data / data packet is greater than or equal to a first threshold, the second network device may delete all data packets in the PDU set to which the first data / data packet belongs, or delete the data, data packets, or PDU set associated with the first data / data packet.

[0315] Before performing relevant processing on the first data, the second network device needs to obtain relevant information of the first data, such as transmission delay and association relationship.

[0316] For example, as described above, the first network device may send information associated with the first data to the second network device. That is, the second network device may obtain information associated with the first data from the first network device.

[0317] For another example, the terminal device may send information associated with the first data to the second network device, or the second network device may obtain information associated with the first data from the terminal device. For example, the transmission delay of the first data from the terminal device to the second network device; or the transmission delay of the PDU set to which the first data belongs from the terminal device to the second network device; or the transmission delay of data, data packets, or PDU sets associated with the first data from the terminal device to the second network device.

[0318] In some embodiments, when the target cell is determined or the target network device is determined, the terminal device may perform a cell handover. For example, the first network device may indicate the target network device to the terminal device and / or instruct the terminal device to perform a cell handover.

[0319] The above-mentioned cell switching process can be determined based on the thirteenth information, wherein the thirteenth information is related to the transmission of the first data, and the first data is data with an associated relationship.

[0320] In the embodiment of the present application, by considering the transmission of associated data during the cell switching process, it helps to ensure the service continuity related to the first data and the synchronous or coordinated transmission of the first data during the switching process.

[0321] It should be noted that the various methods for supporting first data synchronization or collaborative transmission provided in the embodiments of the present application can be used individually or in combination.

[0322] It should be noted that A / B mentioned in the embodiments of this application may refer to A or B.

[0323] The following describes the method provided in the embodiment of the present application by taking the first data as multimodal data as an example.

[0324] Example 1

[0325] Embodiment 1 is a method for supporting data transmission with an associated relationship provided by an embodiment of the present application in a cell switching scenario.

[0326] As an implementation method, the source base station or the target base station obtains multi-modal related information (such as QoS flow association information, or association information between UEs), or PDU set enable information, selects a suitable target cell to switch, or selects the QoS flow / UE to be received or rejected.

[0327] As an implementation method, when switching to the target base station, the UE reports multimodal related information (such as QoS flow association information, or association information between UEs), or PDU set enable information to the target base station. Optionally, the report can use UE assistance information. Optionally, the report is used by the target base station to adjust resource configuration or DRB parameters.

[0328] As an implementation method, if the source base station does not support multimodality or PDU set handling, but the target base station does, the target base station may, on the one hand, request the UE to report the information, or obtain the information from the CN. On the other hand, the target base station may add PDU set-related information to the data / data packets forwarded by the source base station.

[0329] As an implementation method, if the target base station supports multi-modality or PDU set handling, if the transmission delay of the data / data packet forwarded from the source base station is greater than or equal to a threshold (such as a first duration or PSDB), the target base station deletes the data / data packet. Furthermore, the target base station deletes other data packets of the PDU set to which the data / data packet belongs, and / or deletes other data / data packets / PDU sets that have association / denpendency / coordinated transmission with the data / data packet. Optionally, the other data / data packets / PDU sets correspond to the same or different UEs as the data / data packets, or correspond to the same or different QoS flows / DRBs / LCHs. Optionally, the source base station may notify the target network device that PDU-set-1 in the PDU has failed to reach latency requirement (source notify target that PDUs in PDU-set-1 has failed to reach latency requirement), or notify the target base station of the remaining allowed transmission delay information.

[0330] A possible implementation of the first embodiment is as follows.

[0331] In some embodiments, the source base station sends a handover request message to the candidate target base station or cell. The handover request message also includes multimodal related information (e.g., QoS flow association information, or association information between UEs), and / or information on whether PDU set is enabled (e.g., the RAN performs a PDU set enable operation).

[0332] Optionally, the source base station obtains the information through a CN, such as one of AF / UPF / AMF / SMF.

[0333] Optionally, the source base station obtains the information through a UE report. For example, the UE report uses a UEassistanceinformation message. For example, the situation in which the UE reports the information includes at least one of the following: the UE has not reported the information, the UE establishes or modifies a related QoS flow / PDU session, the UE requests a service request, the reporting prohibition timer is not running, or the information that the UE needs to report is different from the information previously reported.

[0334] In some embodiments, the candidate target base station or cell determines whether it can receive the UE handover, or the QoS flow that can be accepted / rejected, based on the handover information, including multi-modality related information and / or information on whether PDU set is enabled.

[0335] Optionally, if the candidate target base station or cell does not support the PDU set operation, the target cell or base station rejects the UE handover, or rejects the related QoS flow. For example, the target cell or base station informs the source base station of the rejection reason (e.g., through a handover response message or a handover request ACK. For example, the reason may be that the PDU set is not supported, or that associated access is not supported).

[0336] In some embodiments, the source base station selects a suitable target cell based on feedback information from the target base station and hands over the UE to the suitable cell.

[0337] Optionally, the source base station preferentially selects a target cell that can support multi-mode and / or PDU set enable operation (especially when there are multiple candidate target cells).

[0338] Optionally, the source base station does not select a target cell that does not support multi-mode and / or does not support PDU set enable operation (especially when there are multiple candidate target cells).

[0339] Another possible implementation of the first embodiment is as follows.

[0340] In some embodiments, the source base station sends a handover request message to a candidate target base station or cell.

[0341] In some embodiments, the target base station obtains multi-modality-related information of the UE (e.g., QoS flow association information, or association information between UEs) to which the source base station requests handover from the core network node or OAM, and / or information on whether PDU set is enabled (e.g., RAN performs a PDU set enable operation). Optionally, the core network node may be one of the SMF / UPF / AMF.

[0342] Optionally, the information is requested to be sent by the target base station, or is updated, i.e., interactively, or periodically interactively, or is acquired, i.e., interactively, or is interactively during the interface establishment process.

[0343] In some embodiments, the candidate target base station or cell determines whether the UE handover can be received, or the QoS flow that can be received / rejected, based on the handover information, as well as multimodal related information and / or information on whether the PDU set is enabled.

[0344] Optionally, if the candidate target base station or cell does not support PDU set operation, the target cell or base station rejects the UE handover, or rejects the related QoS flow. Optionally, the target cell or base station informs the source base station of the reason for the rejection (for example, through a handover response message or a handover request ACK. For example, the reason may be that PDU set is not supported, or that associated access is not supported).

[0345] In some embodiments, the source base station selects a suitable target cell based on feedback information from the target base station and hands over the UE to the suitable cell.

[0346] Optionally, the source base station preferentially selects a target cell that can support multi-mode and / or PDU set enable operation (especially when there are multiple candidate target cells).

[0347] Optionally, the source base station does not select a target cell that does not support multi-mode and / or does not support PDU set enable operation (especially when there are multiple candidate target cells).

[0348] Another possible implementation of the first embodiment is as follows.

[0349] In some embodiments, the source base station obtains information related to multimodality (e.g., association information of QoS flow, or association information between UEs) and / or information on whether PDU set is enabled (e.g., RAN performs PDU set enable operation) from the core network node or OAM or candidate target base station or neighboring base station (e.g., whether support is supported, support capability). For example, the core network node can be one of SMF / UPF / AMF.

[0350] Optionally, the information is requested to be sent by the source base station, or is updated, i.e., interactively, or periodically interactively, or is acquired, i.e., interactively, or is interactively during the interface establishment process.

[0351] In some embodiments, the source base station sends a handover request message to a candidate target base station or cell.

[0352] Optionally, the source base station preferentially selects a target cell that supports multi-mode and / or PDU set enable operation as a candidate handover target cell and sends a handover request message to the cell. (In particular, when there are multiple candidate target cells)

[0353] Optionally, the source base station does not select a target cell that does not support multi-mode and / or does not support PDU set enable operation. Accordingly, the source base station does not send a handover request message to the cell or base station. (In particular, when there are multiple candidate target cells)

[0354] In some embodiments, the candidate target base station or cell determines whether it can receive the UE handover, or whether it can receive / reject the QoS flow based on the handover information.

[0355] In some embodiments, the source base station selects a suitable target cell based on feedback information from the target base station and hands over the UE to the suitable cell.

[0356] Another possible implementation of the first embodiment is as follows.

[0357] In some embodiments, when the UE switches to the target base station, it reports to the target base station multimodal related information (such as QoS flow association information, or association information between UEs), or PDU set enable information to the target base station.

[0358] Optionally, the reporting may adopt UE assistance information.

[0359] Optionally, the report is used by the target base station to adjust resource configuration or DRB parameters, or to allow or prevent switching or access of the associated UE, or to request the associated UE to switch to the cell of this base station.

[0360] Optionally, the UE reports the information if at least one of the following conditions is met. The conditions include: the UE receives a HO command, the UE has not reported the information in the source cell, the UE has not previously reported the information, the UE reported the information within a period of time (such as the last 1 second) before the HO (for example, using UE assistance information to report the information), and the UE is configured to report the information in the cell after handover or the target cell.

[0361] Optionally, when the UE reports the information, or after reporting, the UE starts or restarts a prohibition timer. The prohibition timer is used to prohibit the UE from reporting the information again during the timer running period.

[0362] The HO method supporting multimodality or PDU set awareness provided in the embodiments of the present application ensures service continuity or coordinated transmission during the switching process.

[0363] Example 2

[0364] Embodiment 2 is a method for supporting synchronous or collaborative transmission of associated data provided by an embodiment of the present application during data transmission.

[0365] The method provided in the embodiment of the present application can be based on one or more of LCH / LCP, PDCP, Grant, acquisition of UE internal association or synchronization information, and acquisition of association or synchronization information between UEs to support synchronous or coordinated transmission of associated data.

[0366] For the above-mentioned multiple implementation methods, whether the transmitter, or receiver, or UE of the associated data performs the said behavior, such as including at least one of the following: LCH / LCP behavior, PDCP behavior, grant behavior, whether / how to identify the association or synchronization information, whether / how to report or interact with the association or synchronization information, can be controlled by the CN or, or the base station. Specifically, if the base station or CN instructs the UE to enable the said function or behavior, or the base station or CN configures specific parameters, then the transmitter, or receiver, or UE, performs at least one optional scheme in at least one implementation method of the following multiple implementation methods. It should be noted that each optional scheme in each of the following implementation methods can be used independently or in combination with each other.

[0367] The following describes a method for supporting synchronous or coordinated transmission of associated data based on LCH / LCP.

[0368] In some embodiments, a DRB / LCH with coordination / synchronization requirements is configured, or a DRB / LCH with coordination / synchronization requirements is associated. The association relationship can be explicit (e.g., identifying an association flag and / or an associated DRB / LCH identifier) ​​or implicit (e.g., having the same configured priority). Optionally, upon learning of the association relationship, the gNB performs related configuration or configuration update (e.g., the gNB determines the associated QoS flow based on a UE report or a CN instruction).

[0369] Optionally, the associated DRB / LCH involves one UE, but multiple DRB / LCHs.

[0370] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations may exchange the configuration information of the DRB / LCH, or update the configuration.

[0371] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations can exchange second information. The second information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information recommended for the base station of the associated UE to allocate or schedule for the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station of the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), the mapping relationship between the QoS flow configured for the UE of this base station and DRB / LCH / PDCP, the mapping relationship between the QoS flow configured for the associated UE by the base station of the associated UE and DRB / LCH / PDCP, the time information, timestamp information, and at least one of the associated information of the associated UE obtained by this base station, the time information, timestamp information, and at least one of the associated information of the UE under this base station with an existing association relationship obtained by this base station. For example, the interaction may be performed through the N2 interface.

[0372] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to the same base station, the configuration information of UE1 and UE2 can be coordinated.

[0373] In some embodiments, transmission resources (CG / DG) are allocated or scheduled for transmitting associated data. For example, in the case of DCI scheduling resources or RRC configuration resources, a specific identifier is indicated, or LCH identification information that the resource can carry is indicated. Accordingly, only the data of the LCH with the specific identifier or LCH identifier can be mapped to the resource transmission. Optionally, the resource can be a CG and / or a DG. Optionally, for the LCH, a new LCH mapping restriction is introduced to identify the specific identifier or specific resource.

[0374] Optionally, the associated DRB / LCH involves one UE, but multiple DRB / LCHs.

[0375] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations may exchange the configuration information of the DRB / LCH, or update the configuration.

[0376] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations can exchange second information. The second information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information recommended for the base station of the associated UE to allocate or schedule for the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station of the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), the mapping relationship between the QoS flow configured for the UE of this base station and DRB / LCH / PDCP, the mapping relationship between the QoS flow configured for the associated UE by the base station of the associated UE and DRB / LCH / PDCP, the time information, timestamp information, and at least one of the associated information of the associated UE obtained by this base station, the time information, timestamp information, and at least one of the associated information of the UE under this base station with an existing association relationship obtained by this base station. Optionally, the interaction may be performed through the N2 interface.

[0377] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to the same base station, the configuration information of UE1 and UE2 can be coordinated.

[0378] In some embodiments, multiple sets of LCH parameters are configured. If the transmission delay or data size of the associated DRB / LCH meets the threshold, or, according to the NW indication, or NW feedback (such as feedback involving NACK of the associated DRB / LCH, or M times NACK), the UE uses the second set of LCH parameters for DRB / LCH. The use of the second set of parameters can be for the associated DRB / LCH or for DRB / LCHs. After the first duration, or, the transmission delay or data size of the associated DRB / LCH meets the threshold, or, the NW indicates to modify the LCH parameters, the UE fallbacks to normal transmission for the DRB / LCH. Optionally, the benefit of the second set of parameters is to ensure that the data of the associated DRB / LCH can be preferentially packaged / transmitted to the opposite end, or, to ensure that the data of the associated DRB / LCHs can be transmitted to the opposite end within a period of time, or, to ensure that the time difference of the data of the associated DRB / LCHs transmitted to the opposite end is within a certain range. In another implementation, the second set of parameters enables other associated DRB / LCHs to be transmitted first (for example, the priority of the first LCH is high, but the non-associated LCH, or the priority of the first LCH is high, but the delay tolerance is long, the second set of parameters can also be used to enable other associated DRB / LCHs to be transmitted first).

[0379] Optionally, the associated DRB / LCH involves one UE, but multiple DRB / LCHs.

[0380] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations may exchange the configuration information of the DRB / LCH, or update the configuration.

[0381] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to different base stations, the base stations can exchange second information. The second information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information recommended for the base station of the associated UE to allocate or schedule for the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station of the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), the mapping relationship between the QoS flow configured for the UE of this base station and DRB / LCH / PDCP, the mapping relationship between the QoS flow configured for the associated UE by the base station of the associated UE and DRB / LCH / PDCP, the time information, timestamp information, and at least one of the associated information of the associated UE obtained by this base station, the time information, timestamp information, and at least one of the associated information of the UE under this base station with an existing association relationship obtained by this base station. Optionally, the interaction may be performed through the N2 interface.

[0382] Optionally, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. If the base stations of UE1 and UE2 correspond to the same base station, the configuration information of UE1 and UE2 can be coordinated.

[0383] In some embodiments, new indication information is introduced, such as a new MAC CE or UCI or SR, to request resources from the network to transmit the associated DRB / LCH or its retransmission when the transmission delay or data size of the associated DRB / LCH meets the threshold. Alternatively, the remaining time / data size of the current LCH and the associated LCH is reported. Alternatively, the NW is informed that the associated DRB / LCH cannot be transmitted or the NW is requested to delete the data of the associated DRB / LCH that has been received (such as the LCH / SN of the packet that the UE notifies to discard).

[0384] Optionally, the new indication information is reported to the base station when specific conditions are met. For example, the new indication information may be reported when the associated data arrives, or when the remaining delay of the associated data is lower than a first threshold, or when the amount of the associated data is greater than a second threshold, or when the associated data is discarded or no longer needed.

[0385] In some embodiments, if there is an associated DRB / LCH, the transmitting end or the receiving end may buffer the associated data and send it to the opposite end or the upper layer when all the associated data have arrived.

[0386] The following describes a method for supporting synchronous or coordinated transmission of associated data based on PDCP.

[0387] In some embodiments, if the associated DRB / LCH is DRB1 and DRB2, if the PDU set or PDU of DRB1 is discarded, the transmitter also discards the data packet of DRB2. Optionally, the transmitting PDCP instructs the RLC entity to discard the deleted PDCP SDU / PDU. Optionally, the PDCP entities of DRB1 and DRB2 exchange the packet loss information.

[0388] In some embodiments, the associated DRB / LCH is DRB1 and DRB2. When the PDU set or PDU of DRB1 is discarded, the transmitter instructs the receiver to discard the data packets of which SNs of DRB1 / 2, or indicates the data packets of which SNs have gaps. Alternatively, the receiver discards the data packets of the SN of DRB1 and its associated DRB2 according to the instruction of the disarded DRB1. (For the data packet level, the UE and / or network needs to know the association relationship of the data packet level). Optionally, the instruction or the receiving end packet deletion is performed when one of the following conditions is met: the successfully transmitted PDU / PDU set meets the predefined / configured ratio, the number of successfully transmitted PDU / PDU sets meets the predefined / configured threshold, the PDU / PDU set at a specific position (such as the first position) is not transmitted or transmitted successfully, and the PDU / PDU set of a specific type (such as importance, priority) is not transmitted or transmitted successfully.

[0389] In some embodiments, if the transmission delay of the associated DRB / LCH meets a threshold, the UE activates duplication for the associated DRB / LCH. After a first duration, the UE falls back to normal transmission. Alternatively, if the transmission delay of the associated DRB / LCH meets threshold 2, the UE deactivates duplication for the associated DRB / LCH. After a second duration, the UE falls back to normal transmission.

[0390] In some embodiments, if there is an associated DRB / LCH, the transmitting end or the receiving end may buffer the associated data and send it to the opposite end or the upper layer when all the associated data have arrived.

[0391] In some embodiments, the associated DRB / LCH is DRB1 and DRB2. When the PDU set or PDU of DRB1 does not meet the conditions such as delay, the receiving end instructs the sending end to discard the data packets of DRB1 and the associated DRB2 (for the data packets, the corresponding SN and / or DRB / LCH index can be indicated).

[0392] In some embodiments, the associated DRB / LCH is DRB1 and DRB2. When the PDU set or PDU delay of DRB1 reaches a certain threshold (optionally, the data packet of DRB2 has been received at this time), or when the data of one of the DRBs arrives, or when at least one of the associated data packets arrives, the receiving end instructs the sending end to send or resend the data packet of DRB1 (for the data packet, the corresponding SN and / or DRB / LCH index can be indicated). (For the data packet level, the UE and / or the network needs to know the association relationship of the data packet level). Optionally, the indication information can be carried in the control PDU. For example, the indication information can be a status report (RLC status report and / or PDCP status report).

[0393] In some embodiments, if the associated DRB / LCH involves multiple UEs, and the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2, when the PDU set or PDU of DRB1 is discarded, UE2 also discards the data packet of DRB2. Optionally, UE1 instructs UE2 of packet deletion information, including at least one of the following: the associated DRB identifier, the associated packet identifier, the deleted packet identifier, the packet identifier to be deleted, and the UE identifier. Optionally, the PDCP of UE1 or UE2 instructs its RLC entity to discard the deleted PDCP SDU / PDU. Optionally, the packet deletion information can be indicated to UE2 upon UE2's request.

[0394] In some embodiments, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2, when the PDU set or PDU of DRB1 is discarded, UE1 instructs the corresponding base station to discard the data packets of which SNs of DRB1, or indicates the data packets of which SNs of DRB1 have gaps. Alternatively, UE2 instructs the corresponding base station to discard the data packets of which SNs of DRB1 / 2, or indicates the data packets of which SNs of DRB1 / 2 have gaps (optionally, if corresponding to different base stations, the base station corresponding to UE1 exchanges the information related to DRB2 to the base station corresponding to UE2, or the base station corresponding to DRB2). Alternatively, UE1 instructs the corresponding base station to discard the data packets of which SNs of DRB1, or indicates the data packets of which SNs of DRB1 have gaps (optionally, if corresponding to different base stations, the base station corresponding to UE1 tells the base station corresponding to UE2 which packets of DRB1 are discarded / gapped, and then the base station corresponding to UE2 determines which packets of UE2 / DRB2 are discarded). It should be noted that, for the data packet level, the UE and / or the network needs to know the association relationship of the data packet level. Optionally, the indication or receiving end packet deletion is performed when one of the following conditions is met: the successfully transmitted PDU / PDU set meets the predefined / configured ratio, the number of successfully transmitted PDU / PDU sets meets the predefined / configured threshold, the PDU / PDU set at a specific position (such as the first position) is not transmitted or is successfully transmitted, and the PDU / PDU set of a specific type (such as importance, priority) is not transmitted or is successfully transmitted.

[0395] In some embodiments, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. If the transmission delay of the associated DRB1 / UE1 meets the threshold, UE1 starts duplication for the associated DRB / LCH. After the first time period, fallback to normal transmission. If the transmission delay of the associated DRB1 / UE1 meets threshold 2, UE1 deactivates duplication for the associated DRB / LCH. After the second time period, fallback to normal transmission. Optionally, UE1 and UE2 can learn which associated data packets are (such as at least one of UE identifier, DRB identifier, LCH identifier, and data packet SN), and / or information of the associated data packets (such as delay) through interactive information.

[0396] In some embodiments, if the associated DRB / LCH involves multiple UEs, the associated DRB / LCHs are DRB1 and DRB2, corresponding to UE1 and UE2. Optionally, if there are associated DRB / LCHs, the respective UEs, or respective base stations, or the transmitting end or receiving end may buffer the associated data and send it to the peer end or higher layer when all the associated data arrives.

[0397] In some embodiments, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. When the PDU set or PDU of DRB1 does not meet the conditions such as delay, the receiving end of UE1 instructs UE1 to discard the data packets of DRB1 and the associated DRB2 (correspondingly, UE1 tells UE2 to discard the related data packets). Alternatively, the receiving end of UE1 instructs UE1 to discard the data packets of DRB1 (in addition, if corresponding to different base stations, the base station of UE1 interacts with the base station of UE2 to delete the associated data packets of DRB2, or informs the base station of UE2 which data packets of DRB1 are deleted by the base station of UE1. The base station of UE2 deletes the associated data packets of DRB2 and / or instructs UE2 to delete which data packets of DRB2) and the associated data packets of DRB2. Note: For the data packets, the corresponding SN and / or DRB / LCH index can be indicated.

[0398] In some embodiments, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. When the PDU set or PDU delay of DRB1 reaches a certain threshold (the data packet of DRB2 has been received at this time), or when the data of one of the DRBs arrives, or when at least one of the associated data packets arrives (optionally, if corresponding to different base stations, the base stations need to exchange packet arrival information / delay information), the receiving end instructs the sending end to send or resend the data packet of DRB1 (for the data packet, the corresponding SN and / or DRB / LCH index can be indicated). For example, when the associated data packet of UE2 arrives, the base station of UE2 informs the base station of UE1 of the information, and the base station of UE1 instructs UE1 to send the associated data packet (the indication information can be sent through the control PDU. The indication information can carry at least one of the DRB information, LCH information, and packet identification information). It should be noted that, for the data packet level, the UE and / or the network needs to know the association relationship of the data packet level. Optionally, the indication information can be carried in the control PDU. For example, the indication information may be a status report (RLC status report and / or PDCP status report).

[0399] The following introduces a method for supporting synchronous or collaborative transmission of linked data based on Grant.

[0400] In some embodiments, for multiple CG occasions, even if the current DRB / LCH has no data to transmit, if the associated DRB / LCH has data to transmit but has not yet been transmitted, these CG occasions are used to transmit the data to be transmitted. Alternatively, if the associated DRB / LCH has data to transmit, a request is made to the network, such as through a UTO-UCI, for additional UL grants.

[0401] Optional, applicable to the case where the associated DRB / LCH involves one UE.

[0402] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. For example, UE2 has data to be transmitted through UE1's resources, and UE2 and UE1 exchange data information to be transmitted. At the same time, in the case of transmission through UE1's resources, UE2's identification information needs to be carried to indicate that the data belongs to UE2. (Optionally, if multiple base stations are involved, UE1's base station exchanges UE2's data with UE2's base station).

[0403] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. For example, UE2 requests resources through UE1, and UE2 exchanges the amount of data to be transmitted / delay information with UE1, which is used for UE1 to request resources from the network. (Optionally, if multiple base stations are involved, the base station of UE1 informs the base station of UE2 of the request. The base station of UE2 allocates or schedules resources to UE2).

[0404] In some embodiments, if there is an associated DRB / LCH and there are remaining resources in the available grant, the data packet of the associated DRB / LCH may be transmitted without adding padding.

[0405] Optional, applicable to the case where the associated DRB / LCH involves one UE.

[0406] Optionally, if the associated DRB / LCH involves multiple UEs. The associated DRB / LCH is DRB1 and DRB2, corresponding to UE1 and UE2. For example, UE2 has data to be transmitted through UE1's resources, and UE2 and UE1 exchange data information to be transmitted. At the same time, in the case of transmission through UE1's resources, it is necessary to carry UE1's identification information to indicate that the data belongs to UE2. (Optionally, if multiple base stations are involved, UE1's base station exchanges UE2's data with UE2's base station).

[0407] In some embodiments, during the prioritization process, the association relationship is considered. That is, if the transmission delay of the associated DRB / LCH meets the threshold, the grant corresponding to the data is preferentially transmitted. Alternatively, the HARQ process corresponding to the data is preferentially selected.

[0408] Optional, applicable to the case where the associated DRB / LCH involves one UE.

[0409] Optional, if the associated DRB / LCH involves multiple UEs.

[0410] Optionally, if multiple UEs are involved in the associated DRB / LCH, the UEs can exchange results on whether resources are prioritized, or which resources are prioritized.

[0411] In some embodiments, for urgent data, even if the data priority is lower, the terminal device can request additional transmission resources, such as requesting transmission resources through MAC CE, PUCCH (SR or UTO-UCI), or giving priority to the data in LCH prioritization, HARQ-PID selection and LCP (Even if the data is of lower LCH prio, but if it becomes urgent, UE can 1) request additional grant (The request would be MAC CE, PUCCH (SR or UTO-UCI)), 2) prio it in LCH prioritization, HARQ-PID-selection, and LCP).

[0412] In some embodiments, if the LCH of the data is higher, but the data has not arrived or the data is not urgent, the terminal device can de-prio it in LCH prioritization, HARQ-PID-selection, and LCP, or lower its corresponding priority (if the data is of higher LCH, but if it is not urgent due to the pairing data has not arrived, UE can 1) de-prio it in LCH prioritization, HARQ-PID-selection, and LCP).

[0413] The following introduces a method for obtaining synchronous or coordinated transmission of associated data based on UE internal association or synchronization information (this method is mainly aimed at multimodal data within the UE. Optionally, it can also be used for multimodal data between UEs).

[0414] In some embodiments, packet-level can be implemented in the following manner.

[0415] Optionally, the gNB obtains the time stamp information / coordination information per packets and uses this information for scheduling. This information can be obtained from the CN / AF / UE.

[0416] Optionally, the gNB obtains the time stamp information / coordination information per packets and uses this information for discarding / LCH adjustment. This information is obtained from the UE application layer.

[0417] Optionally, the timestamp information is the time when the packet is expected to arrive at the other end, or the time when decoding is expected, or the latest processing time, or the packet sending time, or the packet grouping time, or the remaining packet time.

[0418] In some embodiments, QoS flow level can be implemented in the following manner.

[0419] Optionally, the gNB knows the association relationship between QoS flows and uses this information for scheduling / RRC parameter adaptation. This information is obtained from the CN. Optionally, the CN information is from the AF.

[0420] Optionally, the UE knows the association relationship between QoS flows and uses this information for discarding / LCH adjustment. The information can be obtained from the CN or the UE application layer. Optionally, the CN can obtain the information from the AF.

[0421] The following introduces a method for supporting synchronous or coordinated transmission of associated data based on association or synchronization information between UEs (this method is mainly aimed at multimodal data between UEs. Optionally, this method can also be used for multimodal data within a UE).

[0422] Inter-UE multimodality involves multiple senders and / or multiple receivers. Therefore, interaction between senders and / or receivers is required. Alternatively, the configuration / behavior of one sender-receiver pair may affect the configuration / behavior of another sender-receiver pair.

[0423] For packet-level, it can include at least one of the following:

[0424] In some embodiments, for DL: the gNB obtains one of time information, timestamp information, and association information.

[0425] Optionally, the information comes from a CN or AF. Optionally, the information is synchronization or association information. Optionally, the information involves multiple base stations (DL transmission) or multiple UEs (DL reception). Optionally, based on the information, the base station performs UE function activation control or scheduling / configuration / resource allocation.

[0426] Optionally, if the DL transmitting end involves a base station, or multiple UEs at the receiving end correspond to one base station, the base station performs UE function enablement control or scheduling / configuration / resource allocation on the multiple UEs based on one of the time information, timestamp information, and association information.

[0427] Optionally, if the DL transmitting end involves multiple base stations, or the multiple UEs at the receiving end belong to different base stations, the multiple base stations can exchange first information. Optionally, the first information is determined based on one of the time information, timestamp information, and associated information. The first information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information allocated or scheduled for the associated UE by the base station that recommends the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station that recommends the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), at least one of the time information, timestamp information, and associated information of the associated UE obtained by this base station, and at least one of the time information, timestamp information, and associated information of the UE under this base station with an existing association relationship obtained by this base station. Optionally, the interaction can be performed through the N2 interface.

[0428] In some embodiments, for UL: the UE obtains one of time information, timestamp information, and association information.

[0429] Optionally, the information is obtained through high-layer interaction of the UE, or is carried through a high-layer packet or a high-layer packet header.

[0430] Optionally, the UE obtains information about which UEs are associated with it. Optionally, the association information is indicated to the UE via the CN or the base station.

[0431] Optionally, the information is exchanged between associated UEs. For example, UE1 and UE2 are associated. UE1 exchanges one of UE1's time information, timestamp information, and association information with UE2, or UE1 requests UE2 to exchange one of UE2's time information, timestamp information, and association information.

[0432] Optionally, the UE reports one of the time information, timestamp information, and associated information to the base station. Optionally, one of the time information, timestamp information, and associated information is carried by a low-layer (for example, at least one of SDAP / PDCP / RLC / MAC) data packet or data packet header, or is carried by a low-layer control PDU. Optionally, one of the time information, timestamp information, and associated information is used by the base station to perform UE function enablement control, or scheduling / configuration / resource allocation. Optionally, if the receiving end involves multiple base stations, or the associated UEs correspond to different base stations, then the information can also be used by the base station to determine the second information, and / or for the base stations involved to exchange the second information. The second information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information allocated or scheduled for the associated UE by the base station that recommends the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station that recommends the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), at least one of the time information, timestamp information, and association information of the associated UE obtained by this base station, and at least one of the time information, timestamp information, and association information of the UE under this base station with an existing association relationship obtained by this base station. Optionally, the interaction can be performed through the N2 interface.

[0433] Optionally, the time stamp information is the time when the packet is expected to arrive at the other end, or the time when it is expected to be decoded, or the latest processing time, or the packet sending time, or the packet assembly time, or the remaining packet time.

[0434] For QoS flow-level, include at least one of the following:

[0435] In some embodiments, for DL: the gNB obtains one of synchronization or association information. The information is for a QoS flow.

[0436] Optionally, the information comes from a CN or AF. Optionally, the information involves multiple base stations (DL transmission) or multiple UEs (DL reception). Optionally, based on the information, the base station performs UE function activation control, or scheduling / configuration / resource allocation, or RLC / QoS flow mapping.

[0437] Optionally, if the DL transmitting end involves a base station, or multiple UEs at the receiving end correspond to one base station, the base station performs UE function enablement control, or scheduling / configuration / resource allocation, or RLC / QoS flow mapping on the multiple UEs based on one of the synchronization or association information.

[0438] Optionally, if the DL transmitting end involves multiple base stations, or the multiple UEs at the receiving end belong to different base stations, the multiple base stations can exchange third information. For example, the third information is determined based on one of the synchronization or association information. The third information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information allocated or scheduled for the associated UE by the base station recommended for the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), RRC information configured for the associated UE by the base station recommended for the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), at least one of the synchronization or association information obtained by this base station (for example, whether there is an association, which UEs are associated, which QoS flows are associated, etc.), the mapping relationship between the QoS flow configured for the UE of this base station and DRB / LCH / PDCP, and the mapping relationship between the QoS flow configured for the associated UE by the base station recommended for the associated UE and DRB / LCH / PDCP. For example, the interaction can be carried out through the N2 interface.

[0439] In some embodiments, for UL: UE acquires one of synchronization or association information.

[0440] Optionally, the information, or which other UEs the UE is associated with, or which QoS flows of the UE are associated with which QoS flows of other UEs, is obtained through high-layer interaction of the UE, or is carried in a high-layer packet or a high-layer packet header. Optionally, the high layer is an application layer.

[0441] Optionally, the UE obtains information about which UEs are associated, or which QoS flows of the UE are associated with which QoS flows of another UE. Optionally, the association information is indicated to the UE via the CN or the base station.

[0442] Optionally, the information, or which other UEs a UE is associated with, is exchanged between UEs. For example, if UE1 learns that UE1 is associated with UE2, or that QoS flow1 of UE1 is associated with QoS flow2 of UE2, UE1 exchanges the association information with UE2.

[0443] Optionally, the UE reports the synchronization or association information to the base station. For example, the synchronization or association information is carried by an RRC message (such as UE assistance info), or is carried by a low-layer (such as at least one of SDAP / PDCP / RLC / MAC) data packet or data packet header, or is carried by a low-layer control PDU. Optionally, the synchronization or association information is used to indicate which associated UEs are, and / or which associated QoS flows are. Optionally, the synchronization or association information is used by the base station to perform UE function enablement control, or scheduling / configuration / resource allocation. Optionally, if the receiving end involves multiple base stations, or the associated UEs correspond to different base stations, then the information can also be used by the base station to determine the fourth information, and / or for the base stations involved to exchange the fourth information. The fourth information includes at least one of the following: resource information allocated or scheduled for the UE of this base station, resource information allocated or scheduled for the associated UE by the base station recommended for the associated UE, RRC information configured for the UE of this base station (such as LCH configuration, MAC configuration, PDCP configuration, etc.), the mapping relationship between the QoS flow configured for the UE of this base station and DRB / LCH / PDCP, the mapping relationship between the QoS flow configured for the associated UE by the base station recommended for the associated UE and DRB / LCH / PDCP, the RRC information configured for the associated UE by the base station recommended for the associated UE (such as LCH configuration, MAC configuration, PDCP configuration, etc.), and synchronization or association information acquired by this base station. For example, the interaction can be carried out through the N2 interface.

[0444] A possible implementation of the second embodiment is as follows.

[0445] In some embodiments, the network configures the DRB or LCH.

[0446] Optionally, the configuration information is sent to the UE via dedicated signaling. For example, the configuration information can be sent to the UE via DRB-config or logicalchannelconfig.

[0447] Optionally, the configured DRB or LCH corresponds to or reflects or indicates that there is a coordination / synchronization requirement.

[0448] Optionally, when the network configures a DRB / LCH, the network identifies or configures a DRB / LCH with the coordination / synchronization requirement, or associates the DRB / LCH with the coordination / synchronization requirement. Optionally, the association relationship, or the coordination / synchronization requirement, may be explicit (e.g., identifying an association flag and / or an associated DRB / LCH identifier) ​​or implicit (e.g., having the same configured priority). Optionally, when the gNB learns of the coordination / association relationship, the gNB performs relevant configuration or configuration update (e.g., the gNB determines the associated QoS flow / DRB / LCH based on a UE report or CN indication).

[0449] Optionally, the network allocates or schedules transmission resources (CG / DG) for transmitting the associated data.

[0450] Optionally, the network configures multiple sets of configuration or transmission parameters, for example, the transmission or configuration parameters are for PDCP / RLC / MAC / PHY configuration or transmission.

[0451] For example, different sets of parameters are used in different situations or scenarios.

[0452] For example, the parameters are used to associate DRB / LCHs, or to associate DRB / LCHs that meet the conditions.

[0453] For example, one set of parameters is a default configuration, or when the synchronization / coordinated transmission is not activated / not indicated / does not meet the usage conditions. The other set, such as another set / sets of parameters, is used when the synchronization / coordinated transmission is activated / indicated / meets the usage conditions.

[0454] For example, the parameters include at least one of the following: LCH priority, prioritized BitRate, allowed-CG list, duplication, LCH of duplication, repetition, MCS.

[0455] For example, if the transmission delay or data volume of the associated DRB / LCH meets the threshold, or, according to the NW indication, or NW feedback (such as feedback involving NACK of the associated DRB / LCH, or M times NACK), for DRB / LCH, the UE uses the second set of LCH parameters. The use of the second set of parameters can be for the associated DRB / LCH or for DRB / LCHs. After the first duration, or, the transmission delay or data volume of the associated DRB / LCH meets the threshold, or, the NW indicates to modify the LCH parameters, the UE fallbacks to normal transmission for the DRB / LCH. Optionally, the benefit of the second set of parameters is to ensure that the data of the associated DRB / LCH can be preferentially packaged / transmitted to the opposite end, or, to ensure that the data of the associated DRB / LCHs can be transmitted to the opposite end within a period of time, or, to ensure that the time difference of the data of the associated DRB / LCHs transmitted to the opposite end is within a certain range.

[0456] For example, compared with the first transmission parameters, the second transmission parameters make the LCH associated with the first data have a higher priority, a higher priority bit rate, and more allowed configuration authorization lists, so that the LCH associated with the first data can be transmitted faster than other LCHs (the 2nd set of parameters can let the associated LCH with higher LCH priority, higher prioritisedBitRate, more allowed-CG list. With this, the associated LCHs can be transmitted quickly than other LCHs).

[0457] For example, compared with the first transmission parameters, the second transmission parameters activate the PDCP retransmission of the LCH associated with the first data or have more copy transmission times, and the modulation and coding strategy has a lower order, so that the first data can be successfully transmitted compared with the data of other LCHs, or the transmission success rate is higher (the the 2nd set of parameters can let the associated LCH with activating PDCP duplication / bigger number of repetitions, or lower MCS. With this, the retx can be avoided, then the data of this associated LCHs can be transmitted successfully (without extra retx time)).

[0458] Optionally, UE reporting is introduced, for example, a new MAC CE, UCI, or SR is introduced to request resources from the network when the transmission delay or data size of the associated DRB / LCH meets a threshold. Optionally, the resource request is used for the UE to transmit the associated DRB / LCH or its retransmission.

[0459] Optionally, UE reporting is introduced, for example, a new MAC CE or UCI or SR is introduced to report the remaining time and / or data size of the LCH, or to report the remaining time and / or data size of the LCH and associated LCHs. As an example, the LCH is a specific or associated LCH.

[0460] Optionally, UE reporting is introduced, for example, a new MAC CE or UCI or SR is introduced to indicate to the NW that the associated DRB / LCH cannot be transmitted or to request the NW to delete the associated DRB / LCH data that has been received (such as the LCH / SN of the packet that the UE notifies to discard).

[0461] Optionally, if there is an associated DRB / LCH, the transmitter or receiver may buffer the associated data and send it to the peer end or higher layer when all associated data have arrived.

[0462] For example, the sending end may buffer the associated data and send it to the other end when all the associated data have arrived.

[0463] For example, the receiving end may buffer the associated data and send it to the upper layer when all associated data have arrived.

[0464] In some embodiments, the network is aware of the coordination / synchronization requirements prior to the above-mentioned network configuration.

[0465] Optionally, the coordination / synchronization requirement is notified by the CN to the base station, such as the SMF / UPF / AMF / AF notifies the base station, or the coordination / synchronization requirement is reported by the UE to the base station.

[0466] Optionally, the coordination / synchronization requirement is based on UE reporting, or based on QoS flow reporting, or based on PDU session reporting.

[0467] Optionally, when the coordination / synchronization requirement changes, or when the coordination / synchronization requirement is learned, or when the coordination / synchronization requirement is periodically notified to the base station.

[0468] Another possible implementation of the second embodiment is as follows.

[0469] In some embodiments, the network configures DRB or PDCP.

[0470] Optionally, the configuration information may be sent to the UE via dedicated signaling. For example, the configuration information may be sent to the UE via DRB-config or PDCP-config.

[0471] Optionally, the configured DRB or PDCP corresponds or responds or indicates that there is a coordination / synchronization requirement.

[0472] Optionally, when the network configures DRB / PDCP, it identifies or configures the DRB / PDCP with the coordination / synchronization requirement, or associates the DRB / PDCP with the coordination / synchronization requirement. Optionally, the association relationship, or the coordination / synchronization requirement, can be explicit (for example, identifying an association flag and / or an associated DRB / PDCP identifier) ​​or implicit (for example, configuring the same or similar low-layer parameters, such as LCH parameters). Optionally, when the gNB learns of the coordination / association relationship, it performs relevant configuration or configuration update (for example, the gNB determines the associated QoS flow / DRB / PDCP / LCH based on the UE report or CN indication).

[0473] Optionally, the network allocates or schedules transmission resources (CG / DG) for transmitting the associated data.

[0474] Optionally, if a DRB / PDCP packet is deleted, the associated DRB / PDCP packet is also deleted. For example, if the associated DRB / PDCPs are DRB1 and DRB2, and the PDU set or PDU of DRB1 is discarded, the transmitter also discards the DRB2 packet. Optionally, the transmitting PDCP instructs the RLC entity to discard the deleted PDCP SDU / PDU.

[0475] Optionally, if a DRB / PDCP data packet is deleted, the sender instructs the receiver of the deletion information, or the sender instructs the receiver to delete the packet. Optionally, if a DRB / PDCP data packet is deleted, the sender instructs the receiver of the deletion information (optionally, including the association relationship between the DRB or the data packet), or the sender instructs the receiver to delete the packet and the associated packets of the packet and the data packets of the associated DRB. For example, the sender instructs to discard or identify the data packet and / or its associated packets (further including the corresponding DRB identifier) ​​that are no longer needed or considered completed, such as a sequence number. For example, the associated DRB / LCH is DRB1 and DRB2, and when the PDU set or PDU of DRB1 is discarded, the sender instructs the receiver to discard the data packets of which SNs of DRB1 / 2. For example, the receiver discards the data packet of the SN of DRB1 and its associated data packet of DRB2 according to the instruction of the disarded DRB1. (For the data packet level, the UE and / or network needs to know the association relationship at the data packet level). Optionally, the packet deletion at the sending end, or the indication, or the packet deletion at the receiving end is performed when one of the following conditions is met: the successfully transmitted PDU / PDU set meets a predefined / configured ratio, the number of successfully transmitted PDU / PDU sets meets a predefined / configured threshold, the PDU / PDU set at a specific position (such as the first position) is not transmitted or is transmitted successfully, and the PDU / PDU set of a specific type (such as importance, priority) is not transmitted or is transmitted successfully.

[0476] Optionally, when certain conditions are met, the UE activates the duplication of the associated DRB. For example, the duplication is for all data in the DRB, or for specific data packets in the DRB, or per-PDU duplication, or per-PDU set duplication. For example, if the transmission delay of the associated DRB / LCH meets the threshold, the UE turns on the duplication for the associated DRB / LCH. After a first duration, fallback to normal transmission. For example, the first duration can be a first timer. For example, when the UE activates or turns on duplication, the first timer is started.

[0477] Optionally, if there is an associated DRB / LCH, the transmitter or receiver may buffer the associated data and send it to the peer end or higher layer when all associated data have arrived.

[0478] For example, the sending end may buffer the associated data and send it to the other end when all the associated data have arrived.

[0479] For example, the receiving end may buffer the associated data and send it to the upper layer when all associated data have arrived.

[0480] In some embodiments, before the above network configuration, the UE and / or the network are aware of the coordination / synchronization requirements.

[0481] Optionally, the coordination / synchronization requirement is notified by the CN to the base station, such as the SMF / UPF / AMF / AF notifies the base station, or the coordination / synchronization requirement is reported by the UE to the base station.

[0482] Optionally, the coordination / synchronization requirement is based on UE reporting, or based on QoS flow reporting, or based on PDU session reporting.

[0483] Optionally, the coordination / synchronization requirement is notified to the UE by the CN, such as the SMF / UPF / AMF / AF notifying the UE, or the coordination / synchronization requirement is notified to the UE by the base station, or the UE upper layer, such as the NAS, notifies the UE AS.

[0484] Optionally, when the coordination / synchronization requirement changes, or when the coordination / synchronization requirement is learned, or when the coordination / synchronization requirement is periodically notified to the base station.

[0485] Another possible implementation of the second embodiment is as follows.

[0486] In some embodiments, the network allocates or schedules or configures transmission resources, such as UL / DL transmission resources, to the UE.

[0487] Optionally, it is configured to the UE through dedicated signaling, for example, CG or DG.

[0488] Optionally, the CG may have one or more transmission resources in one period.

[0489] Optionally, the UL / DL resources may be continuous or discontinuous resources, and may be resources with unequal intervals within a pattern.

[0490] Optionally, the configured DRB or PDCP or LCH corresponds or reflects or indicates that there is a coordination / synchronization requirement. Optionally, the LCH mapping restrictions of the associated DRB / PDCP / LCH are the same or different, for example, the LCH priority is the same, the available DG is the same, and the available CG is the same.

[0491] Optionally, a specific CG / DG party may transmit the associated DRB / PDCP / LCH, or the associated DRB / PDCP / LCH party may transmit at a specific CG / DG.

[0492] Optionally, when the network configures a DRB / PDCP, the network identifies or configures a DRB / PDCP with the coordination / synchronization requirement, or associates the DRB / PDCP with the coordination / synchronization requirement. For example, the association relationship or the coordination / synchronization requirement may be explicit (e.g., identifying an association flag and / or an associated DRB / PDCP identifier) ​​or implicit (e.g., configuring the same or similar lower layer parameters, such as LCH parameters). For example, when the gNB learns of the coordination / association relationship, it performs relevant configuration or configuration update (e.g., the gNB determines the associated QoS flow / DRB / PDCP / LCH based on a UE report or a CN instruction).

[0493] Optionally, the UE may send indication information to the network, where the indication information may be MAC CE or UCI.

[0494] For example, the indication information is used to request additional transmission resources.

[0495] For example, the indication information is used to indicate to the network that several associated DRBs / LCHs have not been transmitted / have not been successfully transmitted, and / or to indicate the delay (e.g., remaining delay) and / or the total amount of data to be transmitted for several associated DRBs / LCHs. Optionally, an overall indication of the indication may be a per-DRB indication. Optionally, the delay may be a minimum delay.

[0496] For example, the indication information is used to indicate to the network that an associated DRB / LCH has not been transmitted / has not been successfully transmitted, and / or to indicate the latency (e.g., remaining latency) and / or the amount of data to be transmitted of the associated DRB / LCH. Optionally, the indication may be a per-DRB indication. Optionally, the latency may be a minimum latency.

[0497] For example, if there is an associated DRB1, the indication information is used to indicate to the network whether the data of DRB1 has not been transmitted / has not been successfully transmitted, and / or to indicate the delay (e.g., remaining delay) and / or the amount of data to be transmitted of DRB1. Optionally, the indication can be a per-DRB indication. Optionally, the delay can be a minimum delay.

[0498] As an example, the UE indicates the information using a new MAC CE or UTO-UCI.

[0499] As an example, for multiple CG occasions, even if the current DRB / LCH has no data to transmit, if the associated DRB / LCH has data to transmit but has not yet been transmitted, these CG occasions will be used to transmit the data to be transmitted. For example, for UTO-UCI, if the associated DRB / LCH has data to transmit, an additional UL grant will be requested from the network.

[0500] Optionally, if there is an associated DRB / LCH and there are available grant resources, the associated DRB / LCH data packets can be transmitted without adding padding.

[0501] Optionally, during the prioritization process, association relationships are considered. That is, if the transmission delay of the associated DRB / LCH meets the threshold, the grant corresponding to the data is transmitted first. Alternatively, the HARQ process corresponding to the data is selected first, or other non-associated DRB / HARQ processes are considered to have lower priority, or other associated DRB / HARQ processes that do not meet the conditions are considered to have lower priority.

[0502] In some embodiments, before the network configures the above information, the UE and / or the network learns the coordination / synchronization requirements.

[0503] Optionally, the coordination / synchronization requirement is notified by the CN to the base station, such as the SMF / UPF / AMF / AF notifies the base station, or the coordination / synchronization requirement is reported by the UE to the base station.

[0504] Optionally, the coordination / synchronization requirement is based on UE reporting, or based on QoS flow reporting, or based on PDU session reporting.

[0505] Optionally, the coordination / synchronization requirement is notified to the UE by the CN, such as the SMF / UPF / AMF / AF notifying the UE, or the coordination / synchronization requirement is notified to the UE by the base station, or the UE upper layer, such as the NAS, notifies the UE AS.

[0506] Optionally, when the coordination / synchronization requirement changes, or when the coordination / synchronization requirement is learned, or when the coordination / synchronization requirement is periodically notified to the base station.

[0507] Example 3

[0508] Embodiment 3 is a method for replicating and transmitting data packets provided in an embodiment of the present application to support synchronous or coordinated transmission of associated data.

[0509] In some embodiments, a PDCP data duplication transmission configuration for data packets is introduced.

[0510] Optionally, in the RRC configuration, a PSI level for duplicate transmission can be configured. The configuration is specific to the UE or DRB. That is, duplicate transmission is performed on packets with a level higher than or equal to the PSI level.

[0511] Optionally, in the RRC configuration, configure the initial level information of the PSI that can use duplicate transmission.

[0512] In some embodiments, a PDCP duplicate transport MAC CE for data packets is introduced.

[0513] Optionally, the MAC CE is a MAC CE for all DRBs, or a MAC CE per DRB.

[0514] Optionally, the MAC CE corresponds to a new LCID

[0515] Optionally, the MAC CE is Per-PDU-set PDCP duplication (de) activation mac-ce, or Per-PDU PDCP duplication (de) activation mac-ce.

[0516] Optionally, the MAC CE can be used alone to perform duplication of DRB data packets.

[0517] For example, according to the instruction of the MAC CE, the UE determines which DBR, for which PSI level to perform duplicate transmission, and which LCH to use.

[0518] Optionally, the MAC CE may be used together with an existing duplication MAC CE.

[0519] For example, when the UE receives both the existing duplication MAC CE and the new MAC CE, the UE uses data packet (PSI level) duplication. Otherwise, the UE uses DRB level duplication.

[0520] For example, when the UE receives an existing duplication MAC CE and a new MAC CE, the UE uses different duplications for different PSIs. For example, for a high PSI level, the UE uses the LCH of all duplications, and for a low PSI level, the UE uses the LCH of the duplication indicated by part (MAC CE). For another example, for a high PSI level, the UE uses the LCH of all duplications, and for a low PSI level, the UE does not use duplication. For another example, for a high PSI level, the UE uses the LCH of the duplication indicated by part (MAC CE), and does not use duplication transmission for UEs with a low PSI level.

[0521] Optionally, the MAC CE includes at least one of the following information: a DRB identifier, an LCH identifier (which can identify which LCH identifier is used by a specific PSI), and a PSI level.

[0522] It should be noted that the existing duplication MAC CE can also refer to the duplication MAC CE supported by R17 and earlier versions (NR or LTE). For XR services, RAN2#122 agreed to introduce a new 8-bit BS table. Therefore, since there is an LCH / LCG that can be configured to use the existing BS table (8-bit and / or 5-bit) and the new 8-bit BS table, how the UE reports the BS and how to select the BS table needs to be considered. At least one of the following methods can be considered:

[0523] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the new BS table for encoding if the data volume the UE buffered is larger than the minimum value of the new BS table.

[0524] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the new BS table for encoding if the data volume the UE buffered is not larger or smaller than the minimum value of the new BS table.

[0525] Alternatively, if the LCG is eligible to use both the existing and new BS tables, the UE may select the new BS table for encoding if the amount of data buffered by the UE matches the new BS table or is within the range of the new BS table.

[0526] Optionally, if the LCG is eligible to use both the existing and new BS tables, the UE may select the legacy BS table for encoding if the amount of data buffered by the UE matches the legacy BS table, or is less than or equal to the maximum value of the legacy BS table, or is within the range of the legacy BS table.

[0527] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the BS table for encoding. This BS table to be used is indicated by the gNB.

[0528] Optionally, the new BS table is an 8-bit BS table.

[0529] Optionally, the legacy BS table is an 8-bit or 5-bit table.

[0530] Optionally, if an LCG is eligible to use the legacy BS tables, the UE chooses the legacy BS table.

[0531] Optionally, a new LCID is introduced to indicate whether it is a new MAC CE.

[0532] Optionally, the selected BS table is indicated in the new MAC CE. The indication of the selected BS table can be for the UE, or for the MAC CE, or for the LCH, or for the LCG, or for the PDU set, or for information on the amount of data to be transmitted that meets specific conditions. The specific condition can be at least one of the following: a specific LCH, a specific LCG, a specific service, a specific transmission delay, or a specific residual delay.

[0533] Optionally, a new MAC CE associated with a new eLCID is introduced to contain the BS information of the XR service as well as a new field indicating the selected BS table.

[0534] Optionally, A new MAC CE only contains BS information of XR services (which may further include other information, such as delay or remaining time information), or, A new MAC CE only contains BS information of a specific LCH / LCG (which may further include other information, such as delay or remaining time information), and the specific LCH / LCG is a LCH / LCG that is configured to use or can use the legacy and new BS tables.

[0535] Optionally, the new MAC CE includes information of one or more LCGs, or includes information of one or more LCHs, or includes information of one or more LCHs of an LCG.

[0536] Optionally, the BS information is information about the amount of data to be transmitted of an LCG, or information about the amount of data to be transmitted of an LCH, or information about the amount of data to be transmitted of a PDU set, or information about the amount of data to be transmitted under a specific condition. The specific condition may be at least one of the following: a specific LCH, a specific LCG, a specific service, a specific transmission delay, or a specific residual delay.

[0537] Optionally, the new MAC CE only includes an 8-bit BS table and does not support a 5-bit BS table.

[0538] Optionally, the new MAC CE includes an 8-bit BS table, or includes a 5-bit BS table.

[0539] Optionally, the new MAC CE includes an 8-bit BS table and a 5-bit BS table.

[0540] Optionally, the new MAC CE is for Regular BSR / Periodic BSR.

[0541] Optionally, the new MAC CE is for a padding BSR.

[0542] For example, as mentioned above, the BS range of the new BS table is different from that of the old BS table. When the terminal reports the data volume of the XR service, it needs to decide which BS table to select. Generally, the determination of the BS table depends on the amount of data buffered by the UE and the BS range covered by the BS table. In one implementation, for an LCG configured to use new and existing BS tables, if the amount of data buffered by the UE is greater than the minimum value of the new BS table, the UE selects the new BS table for encoding. Otherwise, the UE will select the existing BS table. Therefore, the UE needs to indicate which BS table is selected in the gNB. A new MAC CE is associated with a new eLCID (1-8 bytes) to contain BS information and a new field indicating the selected BS table.(As assumed, the new BS table has a different BS range from the legacy BS tables. When the UE reports the data volume of the XR service, the UE needs to decide which BS table to be selected. Normally, the BS table determination depends on the data volume the UE buffered and the BS range the BS table covered. In one implementation, for the LCG configured to use the new and legacy BS table, the UE selects the new BS table for encoding if the data volume the UE buffered is larger than the minimum value of the new BS table. Otherwise, the UE selects the legacy BS table. Accordingly, the UE needs to indicate the gNB with the information that which BS table is selected. A new MAC CE associated with a new eLCID(one-octet) should be introduced to contain the BS information as well as a new field indicating the selected BS table.).

[0543] Optionally, the existing BSR MAC CE only includes BS information of non-XR services, or a new MAC CE only includes BS information of non-specific LCH / LCG, where the specific LCH / LCG is configured to be used or configured or configured to use the existing and new BS tables.

[0544] Optionally, the existing BSR MAC CE includes the BS information of the LCH / LCG when the BSR triggering conditions are met, or includes the BS information of the LCH / LCG for data to be transmitted (the LCH / LCG for data to be transmitted may be one or more). Optionally, the LCH / LCG may include BS information for non-XR services, or BS information for non-specific LCH / LCG, and the specific LCH / LCG is a LCH / LCG configured to use or can use the legacy and new BS tables. Optionally, the LCH / LCG may include BS information for XR services, or BS information for a specific LCH / LCG, and the specific LCH / LCG is a LCH / LCG configured to use or configured to use existing and new BS tables.

[0545] Optionally, in the case of existing BSR MAC CE reporting, no matter which LCH / LCG, or for which service (such as whether it is XR), there is an existing BS table.

[0546] Optionally, in the case of existing BSR MAC CE reporting, for non-XR services, or for LCH / LCG that is not configured to use the legacy and new BS tables, the legacy BS table is used.

[0547] Optionally, in the case of existing BSR MAC CE reporting, for XR services, or for LCH / LCG configured to use legacy and new BS tables, the legacy BS table and / or the new BS table are used.

[0548] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the new BS table for encoding if the data volume the UE buffered is larger than the minimum value of the new BS table.

[0549] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the new BS table for encoding if the data volume the UE buffered is not larger or smaller than the minimum value of the new BS table.

[0550] Alternatively, if the LCG is eligible to use both the existing and new BS tables, the UE may select the new BS table for encoding if the amount of data buffered by the UE matches the new BS table or is within the range of the new BS table.

[0551] Optionally, if the LCG is eligible to use both the existing and new BS tables, the UE may select the legacy BS table for encoding if the amount of data buffered by the UE matches the legacy BS table, or is less than or equal to the maximum value of the legacy BS table, or is within the range of the legacy BS table.

[0552] Optionally, if an LCG is eligible to use both the legacy and new BS tables, the UE chooses the BS table for encoding. This BS table to be used is indicated by the gNB.

[0553] Optionally, the BS table is an 8-bit BS table

[0554] Optionally, the BS table is an 8-bit or 5-bit BS table

[0555] Optionally, the BS table may be a new table or a legacy table. It should be noted that “ / ” represents an “and / or” relationship.

[0556] Optional, for Regular and Periodic BSR, including the following.

[0557] For Regular and Periodic BSR, the MAC entity shall:

[0558] 1> If more than one LCG has data available for transmission when the MAC PDU containing the BSR is to be built:

[0559] 2> Report Long BSR for all LCGs which have data available for transmission.

[0560] 1> Otherwise (else):

[0561] 2>Report enhanced short BSR (report enhanced Short BSR).

[0562] Optionally, in the enhanced short BSR, the BS table occupies 8 bits. Optionally, the enhanced short BSR carries the identifier of the LCH / LCG of the corresponding BS.

[0563] or,

[0564] For Regular and Periodic BSR, the MAC entity shall:

[0565] 1> If more than one LCG has data available for transmission when the MAC PDU containing the BSR is to be built:

[0566] 2> Report Long BSR for all LCGs which have data available for transmission.

[0567] 1>else:

[0568] 2> If the LCG with data available for transmission is an XR LCG or an LCG configured to use the new and legacy BS tables, an enhanced Short BSR is reported. Otherwise, a Short BSR is reported.

[0569] Optionally, in the enhanced short BSR, the BS table occupies 8 bits. Optionally, the enhanced short BSR carries the identifier of the LCH / LCG of the corresponding BS.

[0570] Optional, for Regular and Periodic BSR, including the following.

[0571] For Padding BSR, the MAC entity shall:

[0572] 1> If the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

[0573] 2> If more than one LCG has data available for transmission when the BSR is to be built:

[0574] 3> If the number of padding bits is equal to the size of the Short BSR plus its subheader:

[0575] 4> If the LCG with data available for transmission is an XR LCG or an LCG configured to use the new and legacy BS tables, report an enhanced Short Truncated BSR of the LCG with the highest priority logical channel with data available for transmission. Otherwise, report a Short Truncated BSR.

[0576] 3>else:

[0577] 4> report Long Truncated BSR of the LCG(s) with the logical channels having data available for transmission following a decreasing order of the highest priority logical channel (with or without data available for transmission) in each of these LCG(s), and in case of equal priority, in increasing order of LCGID.

[0578] 2>else:

[0579] 3> If the LCG with data available for transmission is an XR LCG or an LCG configured to use both new and legacy BS tables, report an enhanced Short BSR of the LCG with the highest priority logical channel with data available for transmission. Otherwise, report a Short BSR.

[0580] 1> If the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader:

[0581] 2> Report Long BSR for all LCGs which have data available for transmission.

[0582] Optionally, in the enhanced short Truncated BSR and / or enhanced Short BSR, the BS table occupies 8 bits. Optionally, in the enhanced short Truncated BSR and / or enhanced Short BSR, the identifier of the LCH / LCG of the corresponding BS is carried.

[0583] or,

[0584] For Padding BSR, the MAC entity shall:

[0585] 1> If the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

[0586] 2> If more than one LCG has data available for transmission when the BSR is to be built:

[0587] 3> If the number of padding bits is equal to the size of the Short BSR plus its subheader:

[0588] 4>Short Truncated BSR report enhanced Short Truncated BSR of the LCG with the highest priority logical channel with data available for transmission.

[0589] 3>else:

[0590] 4> report Long Truncated BSR of the LCG(s) with the logical channels having data available for transmission following a decreasing order of the highest priority logical channel(with or without data available for transmission)in each of these LCG(s),and in case of equal priority,in increasing order of LCGID.

[0591] 2>else:

[0592] 3>Report enhanced Short BSR.

[0593] 1> If the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader:

[0594] 2> Report Long BSR for all LCGs which have data available for transmission.

[0595] Optionally, in the enhanced short Truncated BSR and / or enhanced Short BSR, the BS table occupies 8 bits. Optionally, in the enhanced short Truncated BSR and / or enhanced Short BSR, the identifier of the LCH / LCG of the corresponding BS is carried.

[0596] It should be noted that the legacy BS table (or existing BS table) refers to the BS table supported by R17 and earlier versions (NR or LTE).

[0597] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device shown in FIG6 may be the first device mentioned above, and the device 600 may include a receiving unit 610.

[0598] The receiving unit 610 is used to receive first information sent by a second device, where the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0599] In some embodiments, the first information includes first configuration information, and the first configuration information is used to configure parameters of a data radio bearer DRB / logical channel LCH, or the first configuration information is used to configure parameters of one or more terminal devices.

[0600] In some embodiments, there is a mapping relationship between the first data and the DRB / LCH, and / or there is a mapping relationship between the first data and the one or more terminal devices.

[0601] In some embodiments, the first configuration information is used to indicate that the DRB / LCH has a synchronization or cooperative transmission requirement, or the first configuration information is used to identify a DRB / LCH with an associated or synchronization or cooperative transmission requirement, or the first configuration information is used to identify a plurality of the terminal devices with an associated or synchronization or cooperative transmission requirement.

[0602] In some embodiments, the first configuration information is used to indicate the association relationship of DRB / LCH with synchronization or cooperative transmission requirements, or the first configuration information is used to indicate the association relationship of terminal devices with synchronization or cooperative transmission requirements.

[0603] In some embodiments, the first information includes transmission parameters, and the transmission parameters are related to the transmission process of the first data.

[0604] In some embodiments, the first information includes a first transmission parameter and a second transmission parameter, and the first transmission parameter is different from the second transmission parameter.

[0605] In some embodiments, the first transmission parameter is used when synchronous transmission is not activated / not indicated, or when a first condition is satisfied, and / or the second transmission parameter is used when synchronous transmission is activated / indicated, or when a second condition is satisfied.

[0606] In some embodiments, the second condition includes one or more of the following: at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and at least one terminal device that is identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / logical channel groups LCG that are configured or associated, an LCH / LCG that enables the first behavior, and at least one LCH / LCG that is identified as synchronized or associated; the first transmission parameter uses a first duration; the transmission delay of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that are identified as synchronized or associated meets a first threshold; the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and the DRB / LCH that is identified as synchronized or associated The total amount of data of one of the associated DRB / LCH, at least one DRB / LCH of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and the DRB / LCH identified as synchronized or associated meets the third threshold; the transmission delay of the associated terminal device, at least one terminal device of the associated multiple terminal devices, the terminal device that enables the first behavior, and the terminal device identified as synchronized or associated meets the fourth threshold; the total amount of data of the associated terminal device, at least one terminal device of the associated multiple terminal devices, the terminal device that enables the first behavior, and the terminal device identified as synchronized or associated meets the fifth threshold; the remaining amount of data to be transmitted of the associated terminal device, at least one terminal device of the associated multiple terminal devices, the terminal device that enables the first behavior, and the terminal device identified as synchronized or associated meets the sixth threshold; the network device indicates the enabling or activation of the first behavior; and the network device indicates the use of the second transmission parameter.

[0607] In some embodiments, the first condition includes one or more of the following: at least one terminal device among a plurality of terminal devices that is not configured or does not exist in association, a terminal device that enables the first behavior, and at least one terminal device that is identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / LCGs that is not configured or does not exist in association, an LCH / LCG that enables the first behavior, and at least one LCH / LCG that is identified as synchronized or associated; the second transmission parameter uses a second duration; the transmission delay of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that is identified as synchronized or associated meets the seventh threshold; the total amount of data of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that is identified as synchronized or associated meets the eighth threshold ; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the ninth threshold; the transmission delay of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the tenth threshold; the total amount of data of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the eleventh threshold; the amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the twelfth threshold; the network device indicates not to enable or deactivate the first behavior; and the network device indicates to use the first transmission parameter.

[0608] In some embodiments, the first transmission parameter and / or the second transmission parameter is for one DRB / LCH or one terminal device; or the first transmission parameter and / or the second transmission parameter is for multiple DRB / LCHs; or the first transmission parameter and / or the second transmission parameter is for multiple terminal devices.

[0609] In some embodiments, the first transmission parameter and / or the second transmission parameter include one or more of the following: logical channel priority; priority bit ratio; allowed uplink authorization or dynamic authorization; allowed configuration authorization list; copy transmission; repeated transmission; copy transmission of logical channel; retransmission; tolerated transmission delay; and modulation and coding strategy.

[0610] In some embodiments, the uplink authorization or the dynamic authorization allowed by the first transmission parameter and / or the second transmission parameter is indicated by an identifier of the uplink authorization or the dynamic authorization, or an identifier of the DRB / LCH corresponding to the uplink authorization or the dynamic authorization, or matching information of the uplink authorization or the dynamic authorization and DRB / LCH, or the correspondence between the uplink authorization or the dynamic authorization and DRB / LCH.

[0611] In some embodiments, the first transmission parameter and the second transmission parameter satisfy one or more of the following: the logical channel priority in the second transmission parameter is higher than the logical channel priority in the first transmission parameter; the priority bit ratio in the second transmission parameter is higher than the priority bit ratio in the first transmission parameter; the logical channel priority in the second transmission parameter is lower than the logical channel priority in the first transmission parameter, and the tolerated transmission delay in the second transmission parameter is less than the tolerated transmission delay in the first transmission parameter, and the allowed configuration authorization list in the second transmission parameter is more than the allowed configuration authorization list in the first transmission parameter; the second transmission parameter includes an activation indication of the Packet Data Convergence Protocol PDCP; the number of copy transmissions in the second transmission parameter is greater than the number of copy transmissions in the first transmission parameter; the number of retransmissions in the second transmission parameter is greater than the number of retransmissions in the first transmission parameter; and the order of the modulation and coding strategy in the second transmission parameter is lower than the order of the modulation and coding strategy in the first transmission parameter.

[0612] In some embodiments, if the first device is a terminal device and the second device is a network device, the first device also includes a first sending unit for sending second information to the second device, and the second information is used to request transmission resources, or the second information is used to request transmission of the first data, or the second information is used to indicate the transmission requirements of the first data.

[0613] In some embodiments, the first device sends the second information to the second device, including: when a third condition is met, the first device sends the second information to the second device, and the third condition includes one or more of the following: at least one terminal device among the multiple terminal devices is configured or exists, the terminal device that enables the first behavior, and at least one of the terminal devices identified as synchronized or associated; at least one LCH / LCG among the multiple LCH / LCGs is configured or exists, the LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; the first transmission parameter uses a first duration; the second transmission parameter is configured or used; data of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated arrives; the transmission time of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated The delay meets the thirteenth threshold; the data volume of the associated DRB / LCH, at least one DRB / LCH among the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the fourteenth threshold; data of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated arrives; the data to be transmitted of the associated terminal device, or the information of the data to be transmitted, is received; the first device receives third information, and the third information is used for the terminal device associated with the first device to request the first device to send the second information; the transmission delay of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the fifteenth threshold; the data volume of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the sixteenth threshold; and the network device instructs to enable or activate the first behavior.

[0614] In some embodiments, the first device further includes a second sending unit, configured to send fourth information to the second device, where the fourth information is used to indicate a cache status or a transmission status of the first data.

[0615] In some embodiments, the associated logical channel includes a first LCH and a second LCH, and the fourth information is used to indicate one or more of the following: the association relationship between the first LCH and the second LCH; the identifier of the first LCH or the corresponding DRB; the identifier of the second LCH or the corresponding DRB; the transmission delay and / or data size of the first LCH; and the transmission delay and / or data size of the second LCH.

[0616] In some embodiments, the associated logical channel corresponds to a first terminal device and a second terminal device, and the fourth information is used to indicate one or more of the following: an association relationship between the first terminal device and the second terminal device; an identifier of the first terminal device; an identifier of the second terminal device; an identifier of the associated DRB / LCH of the first terminal device; an identifier of the associated DRB / LCH of the second terminal device; a transmission delay and / or data size of the first terminal device; a transmission delay and / or data size of the second terminal device; a transmission delay and / or data size of the associated logical channel of the first terminal device; and an associated transmission delay and / or data size of the second terminal device.

[0617] In some embodiments, the first device also includes a deletion unit for deleting part or all of the first data, or deleting part or all of the first data based on the first information, or deleting part or all of the first data when the first behavior is enabled or activated.

[0618] In some embodiments, the first device also includes a third sending unit for sending fifth information to the second device, and the fifth information is used for one or more of the following: an identifier indicating that there are lost or delayed data packets; an identifier indicating that a data packet does not need to be transmitted or is considered received; an identifier indicating that part or all of the first data cannot be transmitted; a request to the second device to delete part or all of the first data; an identifier of data in the first data that cannot be transmitted; or an identifier of data to be deleted in the first data.

[0619] In some embodiments, the first information includes second configuration information, and the second configuration information is used to configure DRB / PDCP, or to configure one or more terminal devices.

[0620] In some embodiments, there is a mapping relationship between the DRB / PDCP and the first data, and / or there is a mapping relationship between the multiple terminal devices and the first data.

[0621] In some embodiments, the second configuration information is used to indicate that the DRB / PDCP has a synchronization or collaborative transmission requirement, or the second configuration information is used to identify a DRB / PDCP with an associated or synchronization or collaborative transmission requirement, or the second configuration information is used to identify multiple terminal devices with an associated or synchronization or collaborative transmission requirement, or the second configuration information is used to enable or activate the deletion of data packets based on the association relationship, or the second configuration information is used to enable or activate the sending / triggering behavior of the first information.

[0622] In some embodiments, the second configuration information is used to indicate an association relationship between DRB / PDCP with synchronization or coordinated transmission requirements.

[0623] In some embodiments, the first device also includes: a fourth sending unit, used to send the first indication information to the second device when a fourth condition is met, wherein the fourth condition includes one or more of the following: an associated data packet is deleted; a transmission failure indication is received from the second device; N transmission failure indications are received from the second device; a transmission failure indication is received from the second device within a third time period; the successfully transmitted protocol data unit PDU / protocol data unit set PDU set meets the first ratio; the number of successfully transmitted PDU / PDU sets meets the seventeenth threshold; the PDU / PDU set at a specific location is not transmitted or is successfully transmitted; and a specific type of PDU / PDU set is not transmitted or is successfully transmitted.

[0624] In some embodiments, the associated DRB / PDCP includes a first data packet and a second data packet, and the first indication information is used to indicate one or more of the following: an identifier of an associated terminal device; an identifier of an associated DRB / PDCP; an identifier of a delayed or lost data packet; an identifier of the first data packet; an identifier of a data packet associated with the first data packet; an identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH corresponding to the first data packet; an identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH of the data packet associated with the first data packet; an identifier of the terminal device associated with the first data packet; an identifier of the terminal device corresponding to the data packet associated with the first data packet; an indication that the first data packet is not required; an indication that the first data packet and the second data packet are not required; an indication of deletion information of the first data packet; an indication of the network device deleting the first data packet; and an indication of the network device deleting the first data packet and the second data packet.

[0625] In some embodiments, if the PDU set or PDU to which the first data packet belongs is deleted, the first device deletes the second data packet.

[0626] In some embodiments, the transmission failure indication is for a data packet, or all data packets in the PDCP / radio link control RLC / the terminal device cache, or a data packet with a specific identifier in the PDCP / RLC / the terminal device cache.

[0627] In some embodiments, the first indication information is deletion indication information for a specific data packet, or the terminal device, or a quality of service flow QoS flow / DRB / PDCP / RLC, or a data packet cached by the terminal device.

[0628] In some embodiments, the first device further includes: a first execution unit, configured to activate or deactivate the data packet-based copy transmission, or to activate or deactivate the data packet-based copy transmission according to the first information.

[0629] In some embodiments, the first device activates or deactivates the copy transmission of the associated data packet, or the first device activates or deactivates the copy transmission of the associated data packet according to first information.

[0630] In some embodiments, the first device activates the copy transmission when one or more of the following conditions are met: the transmission delay of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the eighteenth threshold; the transmission delay of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the nineteenth threshold; and the network device indicates the enabling or activation of the first behavior.

[0631] In some embodiments, the first device further includes: a second execution unit, configured to deactivate the copy transmission of the associated data packet after a fourth duration of activating the copy transmission of the associated data packet.

[0632] In some embodiments, the duplicate transmission is configured for one or more of: all data packets; specific data packets; each PDU; and each PDU set.

[0633] In some embodiments, the first information further includes sixth information, and the sixth information is used to indicate a first transmission resource of the terminal device, and the first transmission resource is used to transmit the first data.

[0634] In some embodiments, the sixth information includes an identifier of the first transmission resource or an identifier of a specific DRB / LCH / terminal device.

[0635] In some embodiments, the sixth information is carried in radio resource control RRC configuration and / or DCI signaling.

[0636] In some embodiments, the first transmission resource may be a configured authorization resource or a dynamic authorization resource.

[0637] In some embodiments, the first transmission resource includes one or more transmission resources.

[0638] In some embodiments, if the first transmission resource includes multiple transmission resources, the multiple transmission resources are continuous or non-contiguous.

[0639] In some embodiments, the configuration information of the associated DRB / PDCP / LCH includes a synchronization or cooperative transmission requirement identifier, or an association relationship of synchronization or cooperative transmission.

[0640] In some embodiments, the specific configured authorization resources and / or the specific dynamic authorization resources are used to transmit data of a specific DRB / LCH / terminal device, or to transmit data of an associated DRB / PDCP / LCH.

[0641] In some embodiments, if the first device is the terminal device and the second device is the network device, the first device includes a fifth sending unit for sending second indication information to the second device, the second indication information is used to request a second transmission resource, and the second transmission resource is used to transmit the first data.

[0642] In some embodiments, the second indication information is used to indicate one or more of the following: at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and at least one of the terminal devices identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; at least one of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, and a DRB / LCH that is identified as synchronized or associated is not transmitted or is not transmitted. transmission success; the transmission delay of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the amount of data to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the identification of the DRB / LCH that was not transmitted or not transmitted successfully in the associated DRB / LCH; and the identification of the DRB / LCH associated with the DRB / LCH that was not transmitted or not transmitted successfully.

[0643] In some embodiments, the second indication information is carried in media access control signaling or uplink control information.

[0644] In some embodiments, the transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, wherein the first DRB / LCH is associated with the second DRB / LCH.

[0645] In some embodiments, the transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, including: if the first DRB / LCH / terminal device has no data to be transmitted and the second DRB / LCH / terminal device has data to be transmitted, then one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device are used to transmit the information or data of the second DRB / LCH / terminal device; or if the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, then the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

[0646] In some embodiments, if the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, then no padding is added, and / or, the information or data of the second DRB / LCH / terminal device is transmitted using the remaining resources.

[0647] In some embodiments, the priority of transmission resources, or the priority of authorization, is determined based on the association relationship between DRB / LCH / terminal device.

[0648] In some embodiments, the priority of the transmission resource is determined based on one or more of the following: whether at least one of the multiple associated terminal devices is configured or exists, the terminal device with the first behavior enabled, and at least one of the terminal devices identified as synchronized or associated is configured or exists; whether at least one of the multiple associated LCH / LCGs is configured or exists, the LCH / LCG with the first behavior enabled, and at least one of the LCH / LCGs identified as synchronized or associated; whether the second transmission parameter is configured or used; whether the transmission resource carries the first data; whether the priority of the transmission resource is higher than the twentieth threshold; whether the transmission resource is a specific transmission resource; whether the transmission delay of the first data is less than or equal to the twenty-first threshold; whether the data volume of the first data is greater than or equal to the twenty-second threshold; whether the data that can be carried on the transmission resource has an associated relationship; whether the transmission delay of the data that can be carried on the transmission resource meets the twenty-third threshold; whether the amount of data to be transmitted that can be carried on the transmission resource meets the twenty-fourth threshold.

[0649] In some embodiments, the priority of the hybrid automatic repeat request HARQ process is determined based on the association relationship between DRB / LCH / terminal device, or the associated HARQ process is transmitted using the transmission resource.

[0650] In some embodiments, the priority of the HARQ process is determined based on one or more of the following: whether at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and at least one of the terminal devices identified as synchronized or associated is configured or exists; whether the second transmission parameter is configured or used; whether the HARQ process corresponds to at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and at least one of the terminal devices identified as synchronized or associated; whether the HARQ process corresponds to at least one of the associated multiple LCH / LCGs, the LCH / LCG enabling the first behavior, and at least one of the LCH / LCGs identified as synchronized or associated; whether the HARQ process corresponds to the configuration or use of using LCH / LCG with the second transmission parameter; whether the HARQ process corresponds to the terminal device configured with or using the second transmission parameter; whether the transmission resource carries the first data; whether the transmission resource priority is higher than the twenty-fifth threshold; whether the transmission resource is a specific transmission resource; whether the HARQ process corresponds to the first data; whether the transmission delay of the data corresponding to the HARQ process is less than or equal to the twenty-sixth threshold; whether the amount of data corresponding to the HARQ process is greater than or equal to the twenty-seventh threshold; whether the data that can be carried in the HARQ process has an associated relationship; whether the transmission delay of the data that can be carried in the HARQ process meets the twenty-eighth threshold; and whether the amount of data to be transmitted that can be carried in the HARQ process meets the twenty-ninth threshold.

[0651] In some embodiments, the first device further includes a cache unit for caching the first data; and a sixth sending unit for sending the first data to the second device when all the first data arrive.

[0652] In some embodiments, the first device also includes a seventh sending unit for sending seventh information to the second device, wherein the seventh information is used to indicate the association relationship between the terminal device, the quality of service flow, and the DRB / PDCP / RLC / PDU, or to indicate the need for having the association relationship.

[0653] In some embodiments, the seventh information is used to indicate one or more of the following: association / co-transmission / synchronization or cooperative transmission requirements between terminal devices; association / co-transmission / synchronization or cooperative transmission requirements of service quality flows; association / co-transmission / synchronization or cooperative transmission requirements between DRB / PDCP / RLC; and association / co-transmission / synchronization or cooperative transmission requirements of packet data unit PDU sessions.

[0654] In some embodiments, if the seventh information changes, and / or the seventh information has not been reported, and / or the seventh information is obtained, the first device sends the seventh information to the second device; or the first device periodically sends the seventh information to the second device.

[0655] In some embodiments, the first device further includes: an eighth sending unit, configured to send eighth information to the second device, wherein the eighth information is used to indicate configuration information of the associated DRB / LCH or update information of the configuration information.

[0656] In some embodiments, the first device further includes: a ninth sending unit, configured to send ninth information to the second device, where the ninth information is related to the first terminal device and / or the second terminal device.

[0657] In some embodiments, a mapping relationship exists between the first terminal device and the second terminal device and the associated DRB / LCH, the first device is a first network device corresponding to the first terminal device, and the second device is a second network device corresponding to the second terminal device.

[0658] In some embodiments, the ninth information includes one or more of the following: resource information allocated or scheduled by the first network device to the first terminal device; recommended information for the second network device to allocate or schedule resources for the second terminal device; RRC signaling configured by the first network device for the first terminal device; recommended information for the second network device to configure RRC for the second terminal device; the mapping relationship between QoS flow and DRB / LCH / PDCP configured by the first network device for the first terminal device; recommended information for the second network device to configure QoS flow and DRB / LCH / PDCP mapping relationship for the second terminal device; at least one of the time information, timestamp information and associated information of the first terminal device; and at least one of the time information, timestamp information and associated information of the second terminal device.

[0659] In some embodiments, the first device obtains the ninth information from a core network node, the network device, or a higher layer of the terminal device.

[0660] In some embodiments, the ninth information is information about an associated DRB / LCH / PDCP, an associated terminal device, or an associated QoS flow, or an associated PDU session.

[0661] FIG7 is a schematic structural diagram of another communication device provided in an embodiment of the present application. The communication device shown in FIG7 may be the second device mentioned above, and the device 700 may include a first sending unit 710.

[0662] The first sending unit 710 is used to send first information to the first device, where the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

[0663] In some embodiments, the first information includes first configuration information, and the first configuration information is used to configure parameters of a data radio bearer DRB / logical channel LCH, or the first configuration information is used to configure parameters of one or more terminal devices.

[0664] In some embodiments, there is a mapping relationship between the first data and the DRB / LCH, and / or there is a mapping relationship between the first data and the one or more terminal devices.

[0665] In some embodiments, the first configuration information is used to indicate that the DRB / LCH has a synchronization or cooperative transmission requirement, or the first configuration information is used to identify a DRB / LCH with an associated or synchronization or cooperative transmission requirement, or the first configuration information is used to identify a plurality of the terminal devices with an associated or synchronization or cooperative transmission requirement.

[0666] In some embodiments, the first configuration information is used to indicate the association relationship of DRB / LCH with synchronization or cooperative transmission requirements, or the first configuration information is used to indicate the association relationship of terminal devices with synchronization or cooperative transmission requirements.

[0667] In some embodiments, the first information includes transmission parameters, and the transmission parameters are related to the transmission process of the first data.

[0668] In some embodiments, the first information includes a first transmission parameter and a second transmission parameter, and the first transmission parameter is different from the second transmission parameter.

[0669] In some embodiments, the first transmission parameter is used when synchronous transmission is not activated / not indicated, or when a first condition is satisfied, and / or the second transmission parameter is used when synchronous transmission is activated / indicated, or when a second condition is satisfied.

[0670] In some embodiments, the second condition includes one or more of the following: at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and at least one terminal device that is identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / logical channel groups LCG that are configured or associated, an LCH / LCG that enables the first behavior, and at least one LCH / LCG that is identified as synchronized or associated; the first transmission parameter uses a first duration; the transmission delay of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that are identified as synchronized or associated meets the first threshold; the total amount of data of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that are identified as synchronized or associated meets The second threshold; the amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the third threshold; the transmission delay of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the fourth threshold; the total amount of data of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the fifth threshold; the amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the sixth threshold; the network device instructs to enable or activate the first behavior; and the network device instructs to use the second transmission parameter.

[0671] In some embodiments, the first condition includes one or more of the following: at least one terminal device among a plurality of terminal devices that is not configured or does not exist in association, a terminal device that enables the first behavior, and at least one terminal device that is identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / LCGs that is not configured or does not exist in association, an LCH / LCG that enables the first behavior, and at least one LCH / LCG that is identified as synchronized or associated; the second transmission parameter uses a second duration; the transmission delay of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that is identified as synchronized or associated meets the seventh threshold; the total amount of data of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs that is identified as synchronized or associated meets the eighth threshold ; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the ninth threshold; the transmission delay of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the tenth threshold; the total amount of data of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the eleventh threshold; the amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the twelfth threshold; the network device indicates not to enable or deactivate the first behavior; and the network device indicates to use the first transmission parameter.

[0672] In some embodiments, the second transmission parameter and / or the first transmission parameter is for one DRB / LCH or one terminal device; or the second transmission parameter and / or the first transmission parameter is for multiple DRB / LCHs; or the second transmission parameter and / or the first transmission parameter is for multiple terminal devices.

[0673] In some embodiments, the first transmission parameter and / or the second transmission parameter include one or more of the following: logical channel priority; priority bit ratio; allowed uplink authorization or dynamic authorization; allowed configuration authorization list; copy transmission; repeated transmission; copy transmission of logical channel; retransmission; tolerated transmission delay; and modulation and coding strategy.

[0674] In some embodiments, the uplink authorization or the dynamic authorization allowed by the first transmission parameter and / or the second transmission parameter is indicated by an identifier of the uplink authorization or the dynamic authorization, or an identifier of the DRB / LCH corresponding to the uplink authorization or the dynamic authorization, or matching information of the uplink authorization or the dynamic authorization and DRB / LCH, or the correspondence between the uplink authorization or the dynamic authorization and DRB / LCH.

[0675] In some embodiments, the first transmission parameter and the second transmission parameter satisfy one or more of the following: the logical channel priority in the second transmission parameter is higher than the logical channel priority in the first transmission parameter; the priority bit ratio in the second transmission parameter is higher than the priority bit ratio in the first transmission parameter; the logical channel priority in the second transmission parameter is lower than the logical channel priority in the first transmission parameter, and the tolerated transmission delay in the second transmission parameter is less than the tolerated transmission delay in the first transmission parameter, and the allowed configuration authorization list in the second transmission parameter is more than the allowed configuration authorization list in the first transmission parameter; the second transmission parameter includes an activation indication of the Packet Data Convergence Protocol PDCP; the number of copy transmissions in the second transmission parameter is greater than the number of copy transmissions in the first transmission parameter; the number of retransmissions in the second transmission parameter is greater than the number of retransmissions in the first transmission parameter; and the order of the modulation and coding strategy in the second transmission parameter is lower than the order of the modulation and coding strategy in the first transmission parameter.

[0676] In some embodiments, if the first device is a terminal device and the second device is a network device, the second device also includes: a first receiving unit, used to receive second information sent by the first device, the second information is used to request transmission resources, or the second information is used to request transmission of the first data, or the second information is used to indicate the transmission requirements of the first data.

[0677] In some embodiments, the second device receives the second information sent by the first device, including: when a third condition is met, the second device receives the second information sent by the first device, and the third condition includes one or more of the following: at least one terminal device among the multiple terminal devices is configured or exists, the terminal device that enables the first behavior, and at least one of the terminal devices identified as synchronized or associated; at least one LCH / LCG among the multiple LCH / LCGs is configured or exists, the LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; the first transmission parameter uses a first duration; the second transmission parameter is configured or used; data of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated arrives; transmission of the associated DRB / LCH, at least one DRB / LCH among the multiple DRB / LCHs associated, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated The delay meets the thirteenth threshold; the data volume of the associated DRB / LCH, at least one DRB / LCH among the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the fourteenth threshold; data of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated arrives; the data to be transmitted of the associated terminal device, or the information of the data to be transmitted, is received; the first device receives third information, and the third information is used for the terminal device associated with the first device to request the first device to send the second information; the transmission delay of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the fifteenth threshold; the data volume of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device that enables the first behavior, and one of the terminal devices identified as synchronized or associated meets the sixteenth threshold; and the network device instructs to enable or activate the first behavior.

[0678] In some embodiments, the second device further includes: a second receiving unit, configured to receive fourth information sent by the first device, where the fourth information is used to indicate a cache status or a transmission status of the first data.

[0679] In some embodiments, the associated logical channel includes a first LCH and a second LCH, and the fourth information is used to indicate one or more of the following: the association relationship between the first LCH and the second LCH; the identifier of the first LCH or the corresponding DRB; the identifier of the second LCH or the corresponding DRB; the transmission delay and / or data size of the first LCH; and the transmission delay and / or data size of the second LCH.

[0680] In some embodiments, the associated logical channel corresponds to a first terminal device and a second terminal device, and the fourth information is used to indicate one or more of the following: an association relationship between the first terminal device and the second terminal device; an identifier of the first terminal device; an identifier of the second terminal device; an identifier of the associated DRB / LCH of the first terminal device; an identifier of the associated DRB / LCH of the second terminal device; a transmission delay and / or data size of the first terminal device; a transmission delay and / or data size of the second terminal device; a transmission delay and / or data size of the associated logical channel of the first terminal device; and an associated transmission delay and / or data size of the second terminal device.

[0681] In some embodiments, the second device includes a third receiving unit for receiving fifth information sent by the first device, and the fifth information is used for one or more of the following: an identifier indicating that there are lost or delayed data packets; an identifier indicating that a data packet does not need to be transmitted or is considered received; an identifier indicating that part or all of the first data cannot be transmitted; a request to the second device to delete part or all of the first data; an identifier indicating data in the first data that cannot be transmitted; or an identifier indicating data in the first data to be deleted.

[0682] In some embodiments, the first information includes second configuration information, and the second configuration information is used to configure DRB / PDCP, or to configure one or more terminal devices.

[0683] In some embodiments, there is a mapping relationship between the DRB / PDCP and the first data, and / or there is a mapping relationship between the multiple terminal devices and the first data.

[0684] In some embodiments, the second configuration information is used to indicate that the DRB / PDCP has a synchronization or collaborative transmission requirement, or the second configuration information is used to identify a DRB / PDCP with an associated or synchronization or collaborative transmission requirement, or the second configuration information is used to identify multiple terminal devices with an associated or synchronization or collaborative transmission requirement, or the second configuration information is used to enable or activate the deletion of data packets based on the association relationship, or the second configuration information is used to enable or activate the sending / triggering behavior of the first information.

[0685] In some embodiments, the second configuration information is used to indicate an association relationship between DRB / PDCP with synchronization or coordinated transmission requirements.

[0686] In some embodiments, the second device includes a fourth receiving unit for receiving the first indication information sent by the first device when a fourth condition is met, wherein the fourth condition includes one or more of the following: an associated data packet is deleted; a transmission failure indication is received from the second device; N transmission failure indications are received from the second device; a transmission failure indication is received from the second device within a third time period; the successfully transmitted protocol data unit PDU / protocol data unit set PDU set meets the first ratio; the number of successfully transmitted PDUs / PDU sets meets the seventeenth threshold; a PDU / PDU set at a specific location is not transmitted or is successfully transmitted; and a PDU / PDU set of a specific type is not transmitted or is successfully transmitted.

[0687] In some embodiments, the associated DRB / PDCP includes a first data packet and a second data packet, and the first indication information is used to indicate one or more of the following: an identifier of an associated terminal device; an identifier of an associated DRB / PDCP; an identifier of a delayed or lost data packet; an identifier of the first data packet; an identifier of a data packet associated with the first data packet; an identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH corresponding to the first data packet; an identifier of the DRB / PDCP / LCH or DRB / PDCP / LCH of the data packet associated with the first data packet; an identifier of the terminal device associated with the first data packet; an identifier of the terminal device corresponding to the data packet associated with the first data packet; an indication that the first data packet is not required; an indication that the first data packet and the second data packet are not required; an indication of deletion information of the first data packet; an indication of the network device deleting the first data packet; and an indication of the network device deleting the first data packet and the second data packet.

[0688] In some embodiments, the transmission failure indication is for a data packet, or all data packets in the PDCP / radio link control RLC / the terminal device cache, or a data packet with a specific identifier in the PDCP / RLC / the terminal device cache.

[0689] In some embodiments, the first indication information is deletion indication information for a specific data packet, or the terminal device, or a quality of service flow QoS flow / DRB / PDCP / RLC, or a data packet cached by the terminal device.

[0690] In some embodiments, the first information further includes sixth information, and the sixth information is used to indicate a first transmission resource of the terminal device, and the first transmission resource is used to transmit the first data.

[0691] In some embodiments, the sixth information includes an identifier of the first transmission resource or an identifier of a specific DRB / LCH / terminal device.

[0692] In some embodiments, the sixth information is carried in radio resource control RRC configuration and / or DCI signaling.

[0693] In some embodiments, the first transmission resource may be a configured authorization resource or a dynamic authorization resource.

[0694] In some embodiments, the first transmission resource includes one or more transmission resources.

[0695] In some embodiments, if the first transmission resource includes multiple transmission resources, the multiple transmission resources are continuous or non-contiguous.

[0696] In some embodiments, the configuration information of the associated DRB / PDCP / LCH includes a synchronization or cooperative transmission requirement identifier, or an association relationship of synchronization or cooperative transmission.

[0697] In some embodiments, the specific configured authorization resources and / or the specific dynamic authorization resources are used to transmit data of a specific DRB / LCH / terminal device, or to transmit data of an associated DRB / PDCP / LCH.

[0698] In some embodiments, if the first device is the terminal device and the second device is the network device, the second device includes a fifth receiving unit for receiving second indication information sent by the first device, the second indication information is used to request a second transmission resource, and the second transmission resource is used to transmit the first data.

[0699] In some embodiments, the second indication information is used to indicate one or more of the following: at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and at least one of the terminal devices identified as synchronized or associated; at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; at least one of the associated DRB / LCH, at least one DRB / LCH among a plurality of associated DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, and a DRB / LCH that is identified as synchronized or associated is not transmitted or is not transmitted. transmission success; the transmission delay of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the amount of data to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated; the identification of the DRB / LCH that was not transmitted or not transmitted successfully in the associated DRB / LCH; and the identification of the DRB / LCH associated with the DRB / LCH that was not transmitted or not transmitted successfully.

[0700] In some embodiments, the second indication information is carried in media access control signaling or uplink control information.

[0701] In some embodiments, the transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, wherein the first DRB / LCH is associated with the second DRB / LCH.

[0702] In some embodiments, the transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, including: if the first DRB / LCH / terminal device has no data to be transmitted and the second DRB / LCH / terminal device has data to be transmitted, then one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device are used to transmit the information or data of the second DRB / LCH / terminal device; or if the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, then the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

[0703] In some embodiments, if the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, then no padding is added, and / or, the information or data of the second DRB / LCH / terminal device is transmitted using the remaining resources.

[0704] In some embodiments, the priority of transmission resources, or the priority of authorization, is determined based on the association relationship between DRB / LCH / terminal device.

[0705] In some embodiments, the priority of the transmission resource is determined based on one or more of the following: whether at least one of the associated multiple terminal devices is configured or exists, the terminal device that enables the first behavior, and at least one of the terminal devices that are identified as synchronized or associated; whether at least one of the associated multiple LCHs / LCGs is configured or exists, the LCH / LCG that enables the first behavior, and at least one of the LCH / LCGs that are identified as synchronized or associated; whether the second transmission parameter is configured or used; whether the transmission resource carries the first data;

[0706] Whether the priority of the transmission resource is higher than the 20th threshold; whether the transmission resource is a specific transmission resource; whether the transmission delay of the first data is less than or equal to the 21st threshold; whether the data volume of the first data is greater than or equal to the 22nd threshold; whether the data that can be carried on the transmission resource has an associated relationship; whether the transmission delay of the data that can be carried on the transmission resource meets the 23rd threshold; whether the amount of data to be transmitted that can be carried on the transmission resource meets the 24th threshold.

[0707] In some embodiments, the priority of the hybrid automatic repeat request HARQ process is determined based on the association relationship between DRB / LCH / terminal device, or the associated HARQ process is transmitted using the transmission resource.

[0708] In some embodiments, the priority of the HARQ process is determined based on one or more of the following: whether at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and at least one of the terminal devices identified as synchronized or associated is configured or exists; whether the second transmission parameter is configured or used; whether the HARQ process corresponds to at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and at least one of the terminal devices identified as synchronized or associated; whether the HARQ process corresponds to at least one of the associated multiple LCH / LCGs, the LCH / LCG enabling the first behavior, and at least one of the LCH / LCGs identified as synchronized or associated; whether the HARQ process corresponds to the configuration or use of using LCH / LCG with the second transmission parameter; whether the HARQ process corresponds to the terminal device configured with or using the second transmission parameter; whether the transmission resource carries the first data; whether the transmission resource priority is higher than the twenty-fifth threshold; whether the transmission resource is a specific transmission resource; whether the HARQ process corresponds to the first data; whether the transmission delay of the data corresponding to the HARQ process is less than or equal to the twenty-sixth threshold; whether the amount of data corresponding to the HARQ process is greater than or equal to the twenty-seventh threshold; whether the data that can be carried in the HARQ process has an associated relationship; whether the transmission delay of the data that can be carried in the HARQ process meets the twenty-eighth threshold; and whether the amount of data to be transmitted that can be carried in the HARQ process meets the twenty-ninth threshold.

[0709] In some embodiments, the second device includes a sixth receiving unit for receiving the first data sent by the first device; a cache unit for the second device to cache the first data; and a second sending unit for sending the first data to a higher layer when all the first data arrive.

[0710] In some embodiments, the second device includes an eighth receiving unit for receiving seventh information sent by the first device, where the seventh information is used to indicate the association relationship between the terminal device, quality of service flow, and DRB / PDCP / RLC / PDU, or to indicate the need for having the association relationship.

[0711] In some embodiments, the seventh information is used to indicate one or more of the following: association / co-transmission / synchronization or cooperative transmission requirements between terminal devices; association / co-transmission / synchronization or cooperative transmission requirements of service quality flows; association / co-transmission / synchronization or cooperative transmission requirements between DRB / PDCP / RLC; and association / co-transmission / synchronization or cooperative transmission requirements of packet data unit PDU sessions.

[0712] In some embodiments, if the seventh information changes, and / or the seventh information has not been reported, and / or the seventh information is obtained, the second device receives the seventh information sent by the first device; or the second device periodically receives the seventh information sent by the first device.

[0713] In some embodiments, the second device includes a ninth receiving unit for receiving eighth information sent by the first device, where the eighth information is used to indicate configuration information of the associated DRB / LCH or update information of the configuration information.

[0714] In some embodiments, the second device includes a tenth receiving unit, configured to receive ninth information sent by the first device, where the ninth information is related to the first terminal device and / or the second terminal device.

[0715] In some embodiments, a mapping relationship exists between the first terminal device and the second terminal device and the associated DRB / LCH, the first device is a first network device corresponding to the first terminal device, and the second device is a second network device corresponding to the second terminal device.

[0716] In some embodiments, the ninth information includes one or more of the following: resource information allocated or scheduled by the first network device to the first terminal device; recommended information for the second network device to allocate or schedule resources for the second terminal device; RRC signaling configured by the first network device for the first terminal device; recommended information for the second network device to configure RRC for the second terminal device; the mapping relationship between QoS flow and DRB / LCH / PDCP configured by the first network device for the first terminal device; recommended information for the second network device to configure QoS flow and DRB / LCH / PDCP mapping relationship for the second terminal device; at least one of the time information, timestamp information and associated information of the first terminal device; and at least one of the time information, timestamp information and associated information of the second terminal device.

[0717] In some embodiments, the second device is the second network device, then the second device determines one or more of the following information of the second terminal device based on the ninth information: whether the first behavior is enabled; resource scheduling or allocation information; configured RRC signaling; QoS flow and DRB / LCH / PDCP mapping relationship; and association information of the second terminal device.

[0718] In some embodiments, the ninth information is information about an associated DRB / LCH / PDCP, an associated terminal device, or an associated QoS flow, or an associated PDU session.

[0719] FIG8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application. The terminal device 800 may include a first receiving unit 810 .

[0720] The first receiving unit 810 is configured to receive tenth information sent by a network device, where the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol (PDCP) data replication transmission.

[0721] In some embodiments, the tenth information is used to indicate one or more of the following: the importance level of the activatable packet-based PDCP data copy transmission corresponding to the initial state; the importance level of the protocol data unit set PDU set using the configuration information; the importance level of the data packet using packet-based PDCP data copy transmission; indicating that the data packet meeting a specific PDU set importance level uses packet-based PDCP data copy transmission; indicating that the data packet or PDU set greater than or equal to the first importance level uses packet-based PDCP data copy transmission.

[0722] In some embodiments, if the tenth information includes configuration information of packet-based PDCP data copy transmission, the tenth information is used to indicate whether packet / PDU set-based PDCP data copy transmission is enabled, or the tenth information is used to indicate the initial state of packet / PDU set-based PDCP data copy transmission.

[0723] In some embodiments, the tenth information is configuration information for the terminal device, and / or the tenth information is configuration information for data radio bearer DRB / PDCP.

[0724] In some embodiments, the tenth information is carried in radio resource control RRC signaling, and / or the tenth information is carried in PDCP configuration information.

[0725] In some embodiments, the terminal device includes a second receiving unit for receiving eleventh information sent by the network device, where the eleventh information is used to indicate activation or deactivation of data packet-based PDCP data copy transmission.

[0726] In some embodiments, the eleventh information is carried in downlink control information DCI or media access control signaling or RRC signaling.

[0727] In some embodiments, the eleventh information is control signaling for the terminal device, or for all DRBs, or for one or more DRBs.

[0728] In some embodiments, the eleventh information includes a logical channel identifier LCID, and the LCID is used to identify or recognize the eleventh information.

[0729] In some embodiments, the eleventh information includes PDCP duplicate transmission activation / deactivation indication information for PDU set, or PDCP activation / deactivation indication information for data packet, or PDCP duplicate transmission activation / deactivation indication information for PDU.

[0730] In some embodiments, the terminal device includes a third receiving unit for receiving twelfth information sent by the network device, where the twelfth information is used to indicate activation or deactivation of PDCP data copy transmission based on DRB or RLC.

[0731] In some embodiments, if the terminal device receives the eleventh information and the twelfth information, the terminal device uses the packet-based PDCP data replication transmission, or uses the DRB or RLC-based PDCP data replication transmission; or, the terminal device determines the replication transmission strategy to be used based on the packet importance level.

[0732] In some embodiments, the terminal device determines the copy transmission strategy to be used based on the importance level of the data packet, including: data packets greater than or equal to the second importance level use all the first transmission resources for copy transmission, and data packets less than or equal to the second importance level use part of the first transmission resources for copy transmission; or, data packets greater than or equal to the third importance level use all the first transmission resources for copy transmission, and data packets less than or equal to the third importance level are not copied and transmitted; or, data packets greater than or equal to the fourth importance level use part of the first transmission resources for copy transmission, and data packets less than or equal to the fourth importance level are not copied and transmitted; or, data packets greater than or equal to the second importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the second importance level are not copied and transmitted; or, data packets greater than or equal to the third importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the third importance level are not copied and transmitted; or, data packets greater than or equal to the fourth importance level determine their copy transmission strategy based on the eleventh information, and data packets less than or equal to the fourth importance level are not copied and transmitted; or The data packets of the second importance level determine their copy transmission policy based on the eleventh information, and the data packets of less than or equal to the second importance level determine their copy transmission policy based on the twelfth information; or, the data packets of greater than or equal to the third importance level determine their copy transmission policy based on the eleventh information, and the data packets of less than or equal to the third importance level determine their copy transmission policy based on the twelfth information; or, the data packets of greater than or equal to the fourth importance level determine their copy transmission policy based on the eleventh information, and the data packets of less than or equal to the fourth importance level determine their copy transmission policy based on the twelfth information; or, the data packets of greater than or equal to the second importance level determine their copy transmission policy based on the twelfth information, and the data packets of less than or equal to the second importance level determine their copy transmission policy based on the eleventh information; or, the data packets of greater than or equal to the third importance level determine their copy transmission policy based on the twelfth information, and the data packets of less than or equal to the third importance level determine their copy transmission policy based on the eleventh information; or, the data packets of greater than or equal to the fourth importance level determine their copy transmission policy based on the twelfth information, and the data packets of less than or equal to the fourth importance level determine their copy transmission policy based on the eleventh information.

[0733] In some embodiments, the eleventh information includes one or more of the following: a DRB identifier; an LCH identifier; a data packet importance level; and an identifier of the LCH used by data packets of a specific importance level.

[0734] FIG9 is a schematic structural diagram of a network device provided in an embodiment of the present application. The network device 900 may include a first sending unit 910 .

[0735] The first sending unit 910 is used to send tenth information to the terminal device, where the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol PDCP data replication transmission.

[0736] In some embodiments, the tenth information is used to indicate one or more of the following: the importance level of the activatable packet-based PDCP data copy transmission corresponding to the initial state; the importance level of the protocol data unit set PDU set using the configuration information; the importance level of the data packet using packet-based PDCP data copy transmission; indicating that the data packet meeting a specific PDU set importance level uses packet-based PDCP data copy transmission; indicating that the data packet or PDU set greater than or equal to the first importance level uses packet-based PDCP data copy transmission.

[0737] In some emb...

Claims

1. A method for wireless communication, characterized in that: include: A first device receives first information sent by a second device, where the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

2. The method according to claim 1, characterized in that The first information includes first configuration information, and the first configuration information is used to configure parameters of a data radio bearer DRB / logical channel LCH, or the first configuration information is used to configure parameters of one or more terminal devices.

3. The method according to claim 2, characterized in that There is a mapping relationship between the first data and the DRB / LCH, and / or there is a mapping relationship between the first data and the one or more terminal devices.

4. The method according to claim 2 or 3, characterized in that: The first configuration information is used to indicate that the DRB / LCH has a synchronization or cooperative transmission requirement, or the first configuration information is used to identify a DRB / LCH with an associated or synchronization or cooperative transmission requirement, or the first configuration information is used to identify a plurality of terminal devices with an associated or synchronization or cooperative transmission requirement.

5. The method according to any one of claims 2 to 4, characterized in that: The first configuration information is used to indicate the association relationship of DRB / LCH with synchronization or coordinated transmission requirements, or the first configuration information is used to indicate the association relationship of terminal devices with synchronization or coordinated transmission requirements.

6. The method according to any one of claims 1 to 5, characterized in that The first information includes transmission parameters, and the transmission parameters are related to a transmission process of the first data.

7. The method according to claim 6, characterized in that The first information includes a first transmission parameter and a second transmission parameter, and the first transmission parameter is different from the second transmission parameter.

8. The method according to claim 7, characterized in that The first transmission parameter is used when synchronous transmission is not activated / not indicated, or the first condition is met, and / or The second transmission parameter is used for synchronous transmission activation / indication, or when the second condition is met.

9. The method according to claim 8, characterized in that The second condition includes one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG of a plurality of LCH / logical channel groups LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified as synchronized or associated; The first transmission parameter uses a first duration; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated satisfies the first threshold; The total amount of data of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the second threshold; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the third threshold; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated meets a fourth threshold; The total amount of data of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets the fifth threshold; The amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and one of the identified synchronized or associated terminal devices meets a sixth threshold; The network device indicates to enable or activate the first behavior; and The network device indicates to use the second transmission parameter.

10. The method according to claim 8 or 9, characterized in that: The first condition includes one or more of the following: at least one of at least one of the plurality of terminal devices that are not configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified for synchronization or association; at least one of at least one LCH / LCG among a plurality of LCH / LCGs that are not configured or associated, an LCH / LCG for which the first behavior is enabled, and an LCH / LCG identified for synchronization or association; The second transmission parameter uses a second duration; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated meets the seventh threshold; associated DRB / LCH, at least one DRB / LCH among the associated multiple DRB / LCHs, and a terminal device that enables the first behavior The total amount of data of one of the DRB / LCH of the standby device and the DRB / LCH identified as synchronized or associated meets the eighth threshold; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the ninth threshold; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated satisfies a tenth threshold; The total amount of data of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets an eleventh threshold; The amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and one of the identified synchronized or associated terminal devices meets a twelfth threshold; The network device indicates not to enable or deactivate the first behavior; and The network device indicates to use the first transmission parameter.

11. The method according to any one of claims 7 to 10, characterized in that: The first transmission parameter and / or the second transmission parameter is for one DRB / LCH or one terminal device; or The first transmission parameter and / or the second transmission parameter is for multiple DRBs / LCHs; or The first transmission parameter and / or the second transmission parameter are for multiple terminal devices.

12. The method according to any one of claims 7 to 11, characterized in that: The first transmission parameter and / or the second transmission parameter includes one or more of the following: Logical channel priority; Priority bit ratio; Uplink grants or dynamic grants allowed; List of allowed configuration authorizations; Copy transfer; Repeated transmission; Duplicate transmission of logical channels; Retransmission; Tolerable transmission delay; and Modulation and coding strategies.

13. The method according to claim 12, characterized in that The uplink authorization or the dynamic authorization allowed by the first transmission parameter and / or the second transmission parameter is indicated by the identifier of the uplink authorization or the dynamic authorization, or the identifier of the DRB / LCH corresponding to the uplink authorization or the dynamic authorization, or the matching information of the uplink authorization or the dynamic authorization and DRB / LCH, or the correspondence between the uplink authorization or the dynamic authorization and DRB / LCH.

14. The method according to any one of claims 7 to 13, characterized in that: The first transmission parameter and the second transmission parameter satisfy one or more of the following: The logical channel priority in the second transmission parameter is higher than the logical channel priority in the first transmission parameter; The priority bit ratio in the second transmission parameter is higher than the priority bit ratio in the first transmission parameter; The logical channel priority in the second transmission parameter is lower than the logical channel priority in the first transmission parameter, and the tolerated transmission delay in the second transmission parameter is smaller than the tolerated transmission delay in the first transmission parameter, The allowed configuration authorization list in the second transmission parameter is greater than the allowed configuration authorization list in the first transmission parameter; The second transmission parameter includes an activation indication of a packet data convergence protocol PDCP; The number of copy transmissions in the second transmission parameter is greater than the number of copy transmissions in the first transmission parameter; The number of retransmissions in the second transmission parameter is greater than the number of retransmissions in the first transmission parameter; as well as An order of a modulation and coding strategy in the second transmission parameters is lower than an order of a modulation and coding strategy in the first transmission parameters.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: If the first device is a terminal device and the second device is a network device, the first device sends second information to the second device, where the second information is used to request transmission resources, or the second information is used to request transmission of the first data, or the second information is used to indicate transmission requirements for the first data.

16. The method according to claim 15, characterized in that The first device sending second information to the second device includes: When a third condition is met, the first device sends second information to the second device, where the third condition includes one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified to be synchronized or associated; The first transmission parameter uses a first duration; configuring or using the second transmission parameter; Arrival of data of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated meets the thirteenth threshold; The data volume of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the fourteenth threshold; Arrival of data from one of the associated terminal device, at least one terminal device among the associated plurality of terminal devices, the terminal device enabling the first behavior, the terminal device identified for synchronization or the associated terminal device; Receiving data to be transmitted or information about data to be transmitted from an associated terminal device; The first device receives third information, where the third information is used by a terminal device associated with the first device to request the first device to send the second information; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the identified synchronized or associated terminal devices meets the fifteenth threshold; The data volume of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets the sixteenth threshold; and The network device instructs enabling or activating the first behavior.

17. The method according to any one of claims 1 to 16, characterized in that The method further comprises: The first device sends fourth information to the second device, where the fourth information is used to indicate a cache status or a transmission status of the first data.

18. The method according to claim 17, characterized in that The associated logical channels include a first LCH and a second LCH, and the fourth information is used to indicate one or more of the following: an association relationship between the first LCH and the second LCH; an identifier of the first LCH or a corresponding DRB; an identifier of the second LCH or a corresponding DRB; The transmission delay and / or data volume of the first LCH; and The transmission delay and / or data volume of the second LCH.

19. The method according to claim 17 or 18, characterized in that The associated logical channel corresponds to the first terminal device and the second terminal device, and the fourth information is used to indicate one or more of the following: The association relationship between the first terminal device and the second terminal device; an identifier of the first terminal device; an identifier of the second terminal device; An identifier of the DRB / LCH with an associated relationship of the first terminal device; An identifier of the associated DRB / LCH of the second terminal device; The transmission delay and / or data volume of the first terminal device; The transmission delay and / or data volume of the second terminal device; The transmission delay and / or data volume of the associated logical channel of the first terminal device; as well as The associated transmission delay and / or data volume size of the second terminal device.

20. The method according to any one of claims 1 to 19, characterized in that The method further comprises: The first device deletes part or all of the first data, or the first device deletes part or all of the first data according to the first information, or the first device deletes part or all of the first data when the first behavior is enabled or activated.

21. The method according to any one of claims 1 to 20, characterized in that The method further comprises: The first device sends fifth information to the second device, where the fifth information is used for one or more of the following: An indicator of lost or delayed packets; Indicates that a packet does not need to be transmitted or is considered received; Indicating that part or all of the first data cannot be transmitted; Requesting the second device to delete part or all of the first data; an identifier indicating data in the first data that cannot be transmitted; or Indicates an identifier of data to be deleted in the first data.

22. The method according to any one of claims 1 to 21, characterized in that The first information includes second configuration information, and the second configuration information is used to configure DRB / PDCP, or to configure one or more terminal devices.

23. The method according to claim 22, characterized in that There is a mapping relationship between the DRB / PDCP and the first data, and / or there is a mapping relationship between the multiple terminal devices and the first data.

24. The method according to claim 22 or 23, characterized in that The second configuration information is used to indicate that the DRB / PDCP has synchronization or coordinated transmission requirements, or, The second configuration information is used to identify a DRB / PDCP having an associated or synchronized or coordinated transmission requirement, or, The second configuration information is used to identify a plurality of terminal devices having associated or synchronized or coordinated transmission requirements, or, The second configuration information is used to enable or activate deletion of data packets based on association relationships, or, The second configuration information is used to enable or activate the sending / triggering behavior of the first information.

25. The method according to any one of claims 22 to 24, characterized in that The second configuration information is used to indicate the association relationship of DRB / PDCP with synchronization or coordinated transmission requirements.

26. The method according to any one of claims 22 to 25, characterized in that The method further comprises: When a fourth condition is met, the first device sends the first indication information to the second device, where the fourth condition includes one or more of the following: The associated data packets are deleted; receiving a transmission failure indication from the second device; receiving N transmission failure indications from the second device; receiving a transmission failure indication from the second device within a third time period; The successfully transmitted protocol data unit PDU / protocol data unit set PDU set meets the first ratio; The number of successfully transmitted PDUs / PDU sets meets the seventeenth threshold; The PDU / PDU set at a specific location was not transmitted or was successfully transmitted; and A specific type of PDU / PDU set was not transmitted or was transmitted successfully.

27. The method according to claim 26, characterized in that: The associated DRB / PDCP includes a first data packet and a second data packet, and the first indication information is used to indicate one or more of the following: Indicates the terminal device identification with which there is an association; Indicates the presence of an associated DRB / PDCP identifier; Identification of packets that indicate delay or loss; An identifier indicating the first data packet; indicating an identifier of a data packet associated with the first data packet; Indicating the DRB / PDCP / LCH or an identifier of the DRB / PDCP / LCH corresponding to the first data packet; Indicating a DRB / PDCP / LCH or an identifier of a DRB / PDCP / LCH of a data packet associated with the first data packet; Indicates an identifier of a terminal device associated with the first data packet; Indicates an identifier of a terminal device corresponding to a data packet associated with the first data packet; indicating that the first data packet is not needed; indicating that the first data packet and the second data packet are not needed; indicating deletion information of the first data packet; instructing the network device to delete the first data packet; as well as Instruct the network device to delete the first data packet and the second data packet.

28. The method according to claim 27, characterized in that If the PDU set or PDU to which the first data packet belongs is deleted, the first device deletes the second data packet.

29. The method according to claim 26, characterized in that The transmission failure indication is for a data packet, or all data packets in the PDCP / radio link control RLC / terminal device cache, or a data packet with a specific identifier in the PDCP / RLC / terminal device cache.

30. The method according to any one of claims 26 to 29, characterized in that The first indication information is deletion indication information for a specific data packet, or the terminal device, or a quality of service flow QoS flow / DRB / PDCP / RLC, or a data packet cached by the terminal device.

31. The method according to any one of claims 1 to 30, characterized in that The method further comprises: The first device activates or deactivates the data packet-based copy transmission, or the first device activates or deactivates the data packet-based copy transmission according to the first information.

32. The method according to claim 31, characterized in that The first device activates or deactivates the copy transmission of the associated data packet, or the first device activates or deactivates the copy transmission of the associated data packet according to first information.

33. The method according to claim 31 or 32, characterized in that The first device activates the replication transmission when one or more of the following conditions are met: The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated meets the eighteenth threshold; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated satisfies a nineteenth threshold; and The network device indicates enabling or activating a first behavior.

34. The method according to any one of claims 31 to 33, characterized in that The method further comprises: After activating the duplicate transmission of the associated data packet for a fourth time period, the first device deactivates the duplicate transmission of the associated data packet.

35. The method according to any one of claims 31 to 34, characterized in that The replication transport is configured for one or more of the following: All packets; Specific data packets; Each PDU; as well as Each PDU set.

36. The method according to any one of claims 1 to 35, characterized in that The first information also includes sixth information, where the sixth information is used to indicate a first transmission resource of the terminal device, and the first transmission resource is used to transmit the first data.

37. The method according to claim 36, characterized in that The sixth information includes an identifier of the first transmission resource or an identifier of a specific DRB / LCH / terminal device.

38. The method according to claim 36 or 37, characterized in that The sixth information is carried in the radio resource control RRC configuration and / or DCI signaling.

39. The method according to any one of claims 36 to 38, characterized in that The first transmission resource may be a configured authorization resource or a dynamic authorization resource.

40. The method according to any one of claims 36 to 39, characterized in that The first transmission resource includes one or more transmission resources.

41. The method according to claim 40, characterized in that If the first transmission resource includes a plurality of transmission resources, the plurality of transmission resources are continuous or non-continuous.

42. The method according to any one of claims 36 to 41, characterized in that The configuration information of the associated DRB / PDCP / LCH includes a synchronization or coordinated transmission requirement identifier, or an association relationship of synchronization or coordinated transmission.

43. The method according to any one of claims 36 to 42, characterized in that The specific configured authorization resources and / or the specific dynamic authorization resources are used to transmit data of a specific DRB / LCH / terminal device, or to transmit data of associated DRB / PDCP / LCH.

44. The method according to any one of claims 1 to 43, characterized in that The method further comprises: If the first device is the terminal device and the second device is the network device, the first device sends second indication information to the second device, where the second indication information is used to request a second transmission resource, and the second transmission resource is used to transmit the first data.

45. The method according to claim 44, characterized in that The second indication information is used to indicate one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified to be synchronized or associated; At least one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated is not transmitted or is not successfully transmitted; an associated DRB / LCH, at least one of the associated multiple DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, and a transmission delay of one of the DRB / LCHs that is identified as synchronized or associated; an associated DRB / LCH, at least one of the associated multiple DRB / LCHs, a DRB / LCH of the terminal device enabling the first behavior, and an amount of data to be transmitted of one of the DRB / LCHs identified for synchronization or association; Identification of the DRB / LCH that was not transmitted or was not successfully transmitted in the associated DRB / LCH; and The identifier of the DRB / LCH associated with the DRB / LCH that was not transmitted or was not successfully transmitted.

46. ​​The method according to any one of claims 44 or 45, characterized in that The second indication information is carried in media access control signaling or uplink control information.

47. The method according to any one of claims 1 to 46, characterized in that The transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, wherein the first DRB / LCH is associated with the second DRB / LCH.

48. The method according to claim 47, characterized in that The transmission resource of the first DRB / LCH / terminal device is used to transmit information or data of the second DRB / LCH / terminal device, including: If the first DRB / LCH / terminal device has no data to be transmitted, and the second DRB / LCH / terminal device has data to be transmitted, use one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device to transmit the information or data of the second DRB / LCH / terminal device; or If the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

49. The method according to claim 48, characterized in that If the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, no padding is added, and / or the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

50. The method according to any one of claims 1 to 49, characterized in that Based on the association relationship between DRB / LCH / terminal device, the priority of transmission resources or authorization is determined.

51. The method according to claim 50, characterized in that The priority of the transmission resource is determined based on one or more of the following: whether at least one of the plurality of terminal devices associated with each other is configured or exists, a terminal device enabling the first behavior, and a terminal device identified as synchronized or associated; whether at least one of the plurality of associated LCHs / LCGs is configured or exists, the LCH / LCG for which the first behavior is enabled, and the LCH / LCG identified to be synchronized or associated; whether to configure or use the second transmission parameter; whether the transmission resource carries the first data; Whether the transmission resource priority is higher than the twentieth threshold; Whether the transmission resource is a specific transmission resource; whether the transmission delay of the first data is less than or equal to a twenty-first threshold; whether the data volume of the first data is greater than or equal to a twenty-second threshold; whether the data that can be carried on the transmission resource have an associated relationship; whether the transmission delay of the data that can be carried on the transmission resource meets a twenty-third threshold; Whether the amount of data to be transmitted that can be carried on the transmission resource meets a twenty-fourth threshold.

52. The method according to any one of claims 1 to 51, characterized in that Based on the association relationship between DRB / LCH / terminal device, the priority of the hybrid automatic repeat request HARQ process is determined, or the associated HARQ process is transmitted using the transmission resources.

53. The method according to claim 52, characterized in that The priority of the HARQ process is determined based on one or more of the following: whether at least one of the plurality of terminal devices associated with each other is configured or exists, a terminal device enabling the first behavior, and a terminal device identified as synchronized or associated; whether to configure or use the second transmission parameter; Whether the HARQ process corresponds to at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated; Whether the HARQ process corresponds to at least one of the associated multiple LCH / LCGs, the LCH / LCG enabling the first behavior, and the LCH / LCG identified as synchronized or associated; Whether the HARQ process corresponds to an LCH / LCG configured with or using a second transmission parameter; Whether the HARQ process corresponds to the terminal device configured or using the second transmission parameter; whether the transmission resource carries the first data; Whether the transmission resource priority is higher than a twenty-fifth threshold; Whether the transmission resource is a specific transmission resource; whether the HARQ process corresponds to the first data; Whether the transmission delay of the data corresponding to the HARQ process is less than or equal to the twenty-sixth threshold; Whether the amount of data corresponding to the HARQ process is greater than or equal to a twenty-seventh threshold; Whether the data that can be carried in the HARQ process has an associated relationship; whether the transmission delay of the data carried in the HARQ process satisfies a twenty-eighth threshold; as well as Whether the amount of data to be transmitted that can be carried in the HARQ process meets a twenty-ninth threshold.

54. The method according to any one of claims 1 to 53, characterized in that The method further comprises: The first device caches the first data; When all of the first data arrives, the first device sends the first data to the second device.

55. The method according to any one of claims 1 to 54, characterized in that The method further comprises: The first device sends seventh information to the second device, where the seventh information is used to indicate an association relationship between the terminal device, the quality of service flow, and the DRB / PDCP / RLC / PDU, or to indicate a need for the association relationship.

56. The method according to claim 55, characterized in that The seventh information is used to indicate one or more of the following: Association / cooperative transmission / synchronization or cooperative transmission requirements between terminal devices; Association / co-transmission / synchronization or co-transmission requirements of quality of service flows; Association / co-transmission / synchronization or co-transmission requirements between DRB / PDCP / RLC; and Association / co-transmission / synchronization or co-transmission requirements of packet data unit (PDU) sessions.

57. The method according to claim 55 or 56, characterized in that If the seventh information is changed, and / or the seventh information has not been reported, and / or the seventh information is acquired, the first device sends the seventh information to the second device; Or the first device periodically sends the seventh information to the second device.

58. The method according to any one of claims 1 to 57, characterized in that The method further comprises: The first device sends eighth information to the second device, where the eighth information is used to indicate configuration information of the associated DRB / LCH or update information of the configuration information.

59. The method according to any one of claims 1 to 58, characterized in that The method further comprises: The first device sends ninth information to the second device, where the ninth information is related to the first terminal device and / or the second terminal device.

60. The method according to claim 59, characterized in that There is a mapping relationship between the first terminal device and the second terminal device and the associated DRB / LCH, the first device is a first network device corresponding to the first terminal device, and the second device is a second network device corresponding to the second terminal device.

61. The method according to claim 59 or 60, characterized in that The ninth information includes one or more of the following: Resource information allocated or scheduled by the first network device for the first terminal device; Recommendation information for allocating or scheduling resources by the second network device for the second terminal device; RRC signaling configured by the first network device for the first terminal device; The second network device configures RRC suggestion information for the second terminal device; a mapping relationship between the QoS flow configured by the first network device for the first terminal device and the DRB / LCH / PDCP; The second network device configures, for the second terminal device, recommendation information on a mapping relationship between a QoS flow and a DRB / LCH / PDCP; At least one of the time information, timestamp information and associated information of the first terminal device; and At least one of the time information, timestamp information and associated information of the second terminal device.

62. The method according to any one of claims 59 to 61, characterized in that The first device obtains the ninth information from a core network node, the network device, or a high layer of the terminal device.

63. The method according to any one of claims 59 to 62, characterized in that The ninth information is information about the associated DRB / LCH / PDCP, the associated terminal device, or the associated QoS flow, or the associated PDU session.

64. A method for wireless communication, characterized in that: include: The second device sends first information to the first device, where the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

65. The method according to claim 64, characterized in that The first information includes first configuration information, and the first configuration information is used to configure parameters of a data radio bearer DRB / logical channel LCH, or the first configuration information is used to configure parameters of one or more terminal devices.

66. The method according to claim 65, characterized in that There is a mapping relationship between the first data and the DRB / LCH, and / or there is a mapping relationship between the first data and the one or more terminal devices.

67. The method according to claim 65 or 66, characterized in that The first configuration information is used to indicate that the DRB / LCH has a synchronization or cooperative transmission requirement, or the first configuration information is used to identify a DRB / LCH with an associated or synchronization or cooperative transmission requirement, or the first configuration information is used to identify a plurality of terminal devices with an associated or synchronization or cooperative transmission requirement.

68. The method according to any one of claims 65 to 67, characterized in that The first configuration information is used to indicate the association relationship of DRB / LCH with synchronization or coordinated transmission requirements, or the first configuration information is used to indicate the association relationship of terminal devices with synchronization or coordinated transmission requirements.

69. The method according to any one of claims 64 to 68, characterized in that The first information includes transmission parameters, and the transmission parameters are related to a transmission process of the first data.

70. The method according to claim 69, characterized in that The first information includes a first transmission parameter and a second transmission parameter, and the first transmission parameter is different from the second transmission parameter.

71. The method according to claim 70, characterized in that The first transmission parameter is used when synchronous transmission is not activated / not indicated, or the first condition is met, and / or The second transmission parameter is used for synchronous transmission activation / indication, or when the second condition is met.

72. The method according to claim 71, characterized in that The second condition includes one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG of a plurality of LCH / logical channel groups LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified as synchronized or associated; The first transmission parameter uses a first duration; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated satisfies the first threshold; The total amount of data of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the second threshold; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the third threshold; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated meets a fourth threshold; The total amount of data of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets the fifth threshold; The amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and one of the identified synchronized or associated terminal devices meets a sixth threshold; The network device instructs to enable or activate the first behavior; and The network device indicates to use the second transmission parameter.

73. The method according to claim 71 or 72, characterized in that The first condition includes one or more of the following: at least one of at least one of the plurality of terminal devices that are not configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified for synchronization or association; at least one of at least one LCH / LCG among a plurality of LCH / LCGs that are not configured or associated, an LCH / LCG for which the first behavior is enabled, and an LCH / LCG identified for synchronization or association; The second transmission parameter uses a second duration; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated meets the seventh threshold; The total amount of data of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the eighth threshold; The amount of data remaining to be transmitted of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device that enables the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the ninth threshold; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified as synchronized or associated satisfies a tenth threshold; The total amount of data of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets an eleventh threshold; The amount of data remaining to be transmitted of the associated terminal device, at least one of the associated multiple terminal devices, the terminal device enabling the first behavior, and one of the identified synchronized or associated terminal devices meets a twelfth threshold; The network device indicates not to enable or deactivate the first behavior; and The network device indicates to use the first transmission parameter.

74. The method according to any one of claims 70 to 73, characterized in that The second transmission parameter and / or the first transmission parameter is for one DRB / LCH or one terminal device; or The second transmission parameter and / or the first transmission parameter are for multiple DRBs / LCHs; or The second transmission parameter and / or the first transmission parameter are for multiple terminal devices.

75. The method according to any one of claims 70 to 74, characterized in that The first transmission parameter and / or the second transmission parameter includes one or more of the following: Logical channel priority; Priority bit ratio; Uplink grants or dynamic grants allowed; List of allowed configuration authorizations; Copy transfer; Repeated transmission; Duplicate transmission of logical channels; Retransmission; Tolerable transmission delay; and Modulation and coding strategies.

76. The method according to claim 75, characterized in that The uplink authorization or the dynamic authorization allowed by the first transmission parameter and / or the second transmission parameter is indicated by the identifier of the uplink authorization or the dynamic authorization, or the identifier of the DRB / LCH corresponding to the uplink authorization or the dynamic authorization, or the matching information of the uplink authorization or the dynamic authorization and DRB / LCH, or the correspondence between the uplink authorization or the dynamic authorization and DRB / LCH.

77. The method according to any one of claims 70 to 76, characterized in that The first transmission parameter and the second transmission parameter satisfy one or more of the following: The logical channel priority in the second transmission parameter is higher than the logical channel priority in the first transmission parameter; The priority bit ratio in the second transmission parameter is higher than the priority bit ratio in the first transmission parameter; The logical channel priority in the second transmission parameter is lower than the logical channel priority in the first transmission parameter, and the tolerated transmission delay in the second transmission parameter is smaller than the tolerated transmission delay in the first transmission parameter, The allowed configuration authorization list in the second transmission parameter is greater than the allowed configuration authorization list in the first transmission parameter; The second transmission parameter includes an activation indication of a packet data convergence protocol PDCP; The number of copy transmissions in the second transmission parameter is greater than the number of copy transmissions in the first transmission parameter; The number of retransmissions in the second transmission parameter is greater than the number of retransmissions in the first transmission parameter; as well as An order of a modulation and coding strategy in the second transmission parameters is lower than an order of a modulation and coding strategy in the first transmission parameters.

78. The method according to any one of claims 64 to 77, characterized in that The method further comprises: If the first device is a terminal device and the second device is a network device, the second device receives second information sent by the first device, and the second information is used to request transmission resources, or the second information is used to request transmission of the first data, or the second information is used to indicate transmission requirements of the first data.

79. The method according to claim 78, characterized in that The second device receiving the second information sent by the first device includes: When a third condition is met, the second device receives the second information sent by the first device, and the third condition includes one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified to be synchronized or associated; The first transmission parameter uses a first duration; configuring or using the second transmission parameter; Arrival of data of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated; The transmission delay of one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated meets the thirteenth threshold; The data volume of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and one of the DRB / LCHs identified as synchronized or associated meets the fourteenth threshold; Arrival of data from one of the associated terminal device, at least one terminal device among the associated plurality of terminal devices, the terminal device enabling the first behavior, the terminal device identified for synchronization or the associated terminal device; Receiving data to be transmitted or information about data to be transmitted from an associated terminal device; The first device receives third information, where the third information is used by a terminal device associated with the first device to request the first device to send the second information; The transmission delay of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the identified synchronized or associated terminal devices meets the fifteenth threshold; The data volume of one of the associated terminal device, at least one terminal device among the associated multiple terminal devices, the terminal device enabling the first behavior, and the terminal device identified to be synchronized or associated meets the sixteenth threshold; and The network device instructs enabling or activating the first behavior.

80. The method according to any one of claims 64 to 79, characterized in that The method further comprises: The second device receives fourth information sent by the first device, where the fourth information is used to indicate a cache status or a transmission status of the first data.

81. The method according to claim 80, characterized in that The associated logical channels include a first LCH and a second LCH, and the fourth information is used to indicate one or more of the following: an association relationship between the first LCH and the second LCH; an identifier of the first LCH or a corresponding DRB; an identifier of the second LCH or a corresponding DRB; The transmission delay and / or data volume of the first LCH; and The transmission delay and / or data volume of the second LCH.

82. The method according to claim 80 or 81, characterized in that The associated logical channel corresponds to the first terminal device and the second terminal device, and the fourth information is used to indicate one or more of the following: The association relationship between the first terminal device and the second terminal device; an identifier of the first terminal device; an identifier of the second terminal device; An identifier of the DRB / LCH with an associated relationship of the first terminal device; An identifier of the associated DRB / LCH of the second terminal device; The transmission delay and / or data volume of the first terminal device; The transmission delay and / or data volume of the second terminal device; The transmission delay and / or data volume of the associated logical channel of the first terminal device; as well as The associated transmission delay and / or data volume size of the second terminal device.

83. The method according to any one of claims 64 to 82, characterized in that The method further comprises: The second device receives fifth information sent by the first device, where the fifth information is used for one or more of the following: An indicator of lost or delayed packets; Indicates that a packet does not need to be transmitted or is considered received; Indicating that part or all of the first data cannot be transmitted; Requesting the second device to delete part or all of the first data; an identifier indicating data in the first data that cannot be transmitted; or Indicates an identifier of data to be deleted in the first data.

84. The method according to any one of claims 64 to 83, characterized in that The first information includes second configuration information, and the second configuration information is used to configure DRB / PDCP, or to configure one or more terminal devices.

85. The method according to claim 84, characterized in that There is a mapping relationship between the DRB / PDCP and the first data, and / or there is a mapping relationship between the multiple terminal devices and the first data.

86. The method according to claim 84 or 85, characterized in that The second configuration information is used to indicate that the DRB / PDCP has synchronization or coordinated transmission requirements, or, The second configuration information is used to identify a DRB / PDCP having an associated or synchronized or coordinated transmission requirement, or, The second configuration information is used to identify a plurality of terminal devices having associated or synchronized or coordinated transmission requirements, or, The second configuration information is used to enable or activate deletion of data packets based on association relationships, or, The second configuration information is used to enable or activate the sending / triggering behavior of the first information.

87. The method according to any one of claims 84 to 86, characterized in that The second configuration information is used to indicate the association relationship of DRB / PDCP with synchronization or coordinated transmission requirements.

88. The method according to any one of claims 84 to 87, characterized in that The method further comprises: When a fourth condition is met, the second device receives the first indication information sent by the first device, where the fourth condition includes one or more of the following: The associated data packets are deleted; receiving a transmission failure indication from the second device; receiving N transmission failure indications from the second device; receiving a transmission failure indication from the second device within a third time period; The successfully transmitted protocol data unit PDU / protocol data unit set PDU set meets the first ratio; The number of successfully transmitted PDUs / PDU sets meets the seventeenth threshold; The PDU / PDU set at a specific location was not transmitted or was successfully transmitted; and A specific type of PDU / PDU set was not transmitted or was transmitted successfully.

89. The method according to claim 88, characterized in that: The associated DRB / PDCP includes a first data packet and a second data packet, and the first indication information is used to indicate one or more of the following: Indicates the terminal device identification with which there is an association; Indicates the presence of an associated DRB / PDCP identifier; Identification of packets that indicate delay or loss; An identifier indicating the first data packet; indicating an identifier of a data packet associated with the first data packet; Indicating the DRB / PDCP / LCH or an identifier of the DRB / PDCP / LCH corresponding to the first data packet; Indicating a DRB / PDCP / LCH or an identifier of a DRB / PDCP / LCH of a data packet associated with the first data packet; Indicates an identifier of a terminal device associated with the first data packet; Indicates an identifier of a terminal device corresponding to a data packet associated with the first data packet; indicating that the first data packet is not needed; indicating that the first data packet and the second data packet are not needed; indicating deletion information of the first data packet; instructing the network device to delete the first data packet; as well as Instruct the network device to delete the first data packet and the second data packet.

90. The method according to claim 88, characterized in that The transmission failure indication is for a data packet, or all data packets in the PDCP / radio link control RLC / terminal device cache, or a data packet with a specific identifier in the PDCP / RLC / terminal device cache.

91. The method according to any one of claims 88 to 90, characterized in that The first indication information is deletion indication information for a specific data packet, or the terminal device, or a quality of service flow QoS flow / DRB / PDCP / RLC, or a data packet cached by the terminal device.

92. The method according to any one of claims 64 to 91, characterized in that The first information also includes sixth information, where the sixth information is used to indicate a first transmission resource of the terminal device, and the first transmission resource is used to transmit the first data.

93. The method according to claim 92, characterized in that The sixth information includes an identifier of the first transmission resource or an identifier of a specific DRB / LCH / terminal device.

94. The method according to claim 92 or 93, characterized in that The sixth information is carried in the radio resource control RRC configuration and / or DCI signaling.

95. The method according to any one of claims 92-94, characterized in that The first transmission resource may be a configured authorization resource or a dynamic authorization resource.

96. The method according to any one of claims 92-95, characterized in that The first transmission resource includes one or more transmission resources.

97. The method according to claim 96, characterized in that If the first transmission resource includes a plurality of transmission resources, the plurality of transmission resources are continuous or non-continuous.

98. The method according to any one of claims 92-97, characterized in that The configuration information of the associated DRB / PDCP / LCH includes a synchronization or coordinated transmission requirement identifier, or an association relationship of synchronization or coordinated transmission.

99. The method according to any one of claims 92 to 98, characterized in that The specific configured authorization resources and / or the specific dynamic authorization resources are used to transmit data of a specific DRB / LCH / terminal device, or to transmit data of associated DRB / PDCP / LCH.

100. The method according to any one of claims 64 to 99, characterized in that The method further comprises: If the first device is the terminal device and the second device is the network device, the second device receives second indication information sent by the first device, where the second indication information is used to request a second transmission resource, and the second transmission resource is used to transmit the first data.

101. The method according to claim 100, characterized in that The second indication information is used to indicate one or more of the following: At least one of at least one terminal device among a plurality of terminal devices that are configured or associated, a terminal device that enables the first behavior, and a terminal device that is identified to be synchronized or associated; At least one of at least one LCH / LCG among a plurality of LCH / LCGs that are configured or associated, an LCH / LCG that enables the first behavior, and an LCH / LCG that is identified to be synchronized or associated; At least one of the associated DRB / LCH, at least one of the associated multiple DRB / LCHs, the DRB / LCH of the terminal device enabling the first behavior, and the DRB / LCH identified as synchronized or associated is not transmitted or is not successfully transmitted; an associated DRB / LCH, at least one of the associated multiple DRB / LCHs, a DRB / LCH of a terminal device that enables the first behavior, and a transmission delay of one of the DRB / LCHs that is identified as synchronized or associated; an associated DRB / LCH, at least one of the associated multiple DRB / LCHs, a DRB / LCH of the terminal device enabling the first behavior, and an amount of data to be transmitted of one of the DRB / LCHs identified for synchronization or association; Identification of the DRB / LCH that was not transmitted or was not successfully transmitted in the associated DRB / LCH; and The identifier of the DRB / LCH associated with the DRB / LCH that was not transmitted or was not successfully transmitted.

102. The method according to any one of claims 100 or 101, characterized in that The second indication information is carried in media access control signaling or uplink control information.

103. The method according to any one of claims 64 to 102, characterized in that: The transmission resources of the first DRB / LCH / terminal device are used to transmit information or data of the second DRB / LCH / terminal device, wherein the first DRB / LCH is associated with the second DRB / LCH.

104. The method according to claim 103, characterized in that The transmission resource of the first DRB / LCH / terminal device is used to transmit information or data of the second DRB / LCH / terminal device, including: If the first DRB / LCH / terminal device has no data to be transmitted, and the second DRB / LCH / terminal device has data to be transmitted, use one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device to transmit the information or data of the second DRB / LCH / terminal device; or If the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

105. The method according to claim 104, characterized in that If the first DRB / LCH / terminal device has data to be transmitted, the second DRB / LCH / terminal device has data to be transmitted, and one or more transmission opportunities in the transmission resources of the first DRB / LCH / terminal device include remaining resources, no padding is added, and / or the remaining resources are used to transmit the information or data of the second DRB / LCH / terminal device.

106. The method according to any one of claims 64-105, characterized in that Based on the association relationship between DRB / LCH / terminal device, the priority of transmission resources or authorization is determined.

107. The method according to claim 106, characterized in that The priority of the transmission resource is determined based on one or more of the following: whether at least one of the plurality of terminal devices associated with each other is configured or exists, a terminal device enabling the first behavior, and a terminal device identified as synchronized or associated; whether at least one of the plurality of associated LCHs / LCGs is configured or exists, the LCH / LCG for which the first behavior is enabled, and the LCH / LCG identified to be synchronized or associated; whether to configure or use the second transmission parameter; whether the transmission resource carries the first data; Whether the transmission resource priority is higher than the twentieth threshold; Whether the transmission resource is a specific transmission resource; whether the transmission delay of the first data is less than or equal to a twenty-first threshold; whether the data volume of the first data is greater than or equal to a twenty-second threshold; whether the data that can be carried on the transmission resource have an associated relationship; whether the transmission delay of the data that can be carried on the transmission resource meets a twenty-third threshold; Whether the amount of data to be transmitted that can be carried on the transmission resource meets a twenty-fourth threshold.

108. The method according to any one of claims 64-107, characterized in that Based on the association relationship between DRB / LCH / terminal device, the priority of the hybrid automatic repeat request HARQ process is determined, or the associated HARQ process is transmitted using the transmission resources.

109. The method according to claim 108, characterized in that The priority of the HARQ process is determined based on one or more of the following: whether at least one of the plurality of terminal devices associated with each other is configured or exists, a terminal device enabling the first behavior, and a terminal device identified as synchronized or associated; whether to configure or use the second transmission parameter; Whether the HARQ process corresponds to at least one terminal device among the associated multiple terminal devices, and whether the terminal device that enables the first behavior device, at least one of a terminal device to be synchronized or associated; Whether the HARQ process corresponds to at least one of the associated multiple LCH / LCGs, the LCH / LCG enabling the first behavior, and the LCH / LCG identified as synchronized or associated; Whether the HARQ process corresponds to an LCH / LCG configured with or using a second transmission parameter; Whether the HARQ process corresponds to the terminal device configured or using the second transmission parameter; whether the transmission resource carries the first data; Whether the transmission resource priority is higher than a twenty-fifth threshold; Whether the transmission resource is a specific transmission resource; whether the HARQ process corresponds to the first data; Whether the transmission delay of the data corresponding to the HARQ process is less than or equal to the twenty-sixth threshold; Whether the amount of data corresponding to the HARQ process is greater than or equal to a twenty-seventh threshold; Whether the data that can be carried in the HARQ process has an associated relationship; whether the transmission delay of the data carried in the HARQ process satisfies a twenty-eighth threshold; as well as Whether the amount of data to be transmitted that can be carried in the HARQ process meets a twenty-ninth threshold.

110. The method according to any one of claims 64 to 109, characterized in that The method further comprises: The second device receives the first data sent by the first device; The second device caches the first data; When all the first data arrive, the second device sends the first data to a higher layer.

111. The method according to any one of claims 64 to 110, characterized in that The method further comprises: The second device receives the seventh information sent by the first device, where the seventh information is used to indicate the association relationship between the terminal device, the service quality flow, and the DRB / PDCP / RLC / PDU, or to indicate the need for having the association relationship.

112. The method according to claim 111, characterized in that The seventh information is used to indicate one or more of the following: Association / cooperative transmission / synchronization or cooperative transmission requirements between terminal devices; Association / co-transmission / synchronization or co-transmission requirements of quality of service flows; Association / co-transmission / synchronization or co-transmission requirements between DRB / PDCP / RLC; and Association / co-transmission / synchronization or co-transmission requirements of packet data unit (PDU) sessions.

113. The method according to claim 111 or 112, characterized in that If the seventh information is changed, and / or the seventh information has not been reported, and / or the seventh information is acquired, the second device receives the seventh information sent by the first device; Or the second device periodically receives the seventh information sent by the first device.

114. The method according to any one of claims 64 to 113, characterized in that The method further comprises: The second device receives the eighth information sent by the first device, where the eighth information is used to indicate the configuration information of the associated DRB / LCH or the update information of the configuration information.

115. The method according to any one of claims 64 to 114, characterized in that The method further comprises: The second device receives ninth information sent by the first device, where the ninth information is related to the first terminal device and / or the second terminal device.

116. The method according to claim 115, characterized in that There is a mapping relationship between the first terminal device and the second terminal device and the associated DRB / LCH, the first device is a first network device corresponding to the first terminal device, and the second device is a second network device corresponding to the second terminal device.

117. The method according to claim 115 or 116, characterized in that The ninth information includes one or more of the following: Resource information allocated or scheduled by the first network device for the first terminal device; Recommendation information for allocating or scheduling resources by the second network device for the second terminal device; RRC signaling configured by the first network device for the first terminal device; The second network device configures RRC suggestion information for the second terminal device; a mapping relationship between the QoS flow configured by the first network device for the first terminal device and the DRB / LCH / PDCP; The second network device configures, for the second terminal device, recommendation information on a mapping relationship between a QoS flow and a DRB / LCH / PDCP; At least one of the time information, timestamp information and associated information of the first terminal device; and At least one of the time information, timestamp information and associated information of the second terminal device.

118. The method according to any one of claims 115 to 117, characterized in that If the second device is the second network device, the second device determines one or more of the following information of the second terminal device based on the ninth information: Whether to enable the first behavior; resource scheduling or allocation information; Configured RRC signaling; QoS flow and DRB / LCH / PDCP mapping relationship; and The associated information of the second terminal device.

119. The method according to any one of claims 115 to 118, characterized in that The ninth information is information about the associated DRB / LCH / PDCP, the associated terminal device, or the associated QoS flow, or the associated PDU session.

120. A method for wireless communication, characterized in that: include: The terminal device receives the tenth information sent by the network device, where the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol PDCP data replication transmission.

121. The method according to claim 120, characterized in that The tenth information is used to indicate one or more of the following: The importance level of the packet-based PDCP data copy transmission that can be activated corresponding to the initial state; A protocol data unit set PDU set importance level using the configuration information; Importance level of packets transmitted using packet-based PDCP data replication; Indicates that packets meeting a specific PDU set importance level are transmitted using packet-based PDCP data replication; Indicates that packets or PDU sets with an importance level greater than or equal to the first importance level are transmitted using packet-based PDCP data copying.

122. The method according to claim 120 or 121, characterized in that If the tenth information includes configuration information of data packet-based PDCP data copy transmission, the tenth information is used to indicate whether data packet / PDU set-based PDCP data copy transmission is enabled, or the tenth information is used to indicate the initial state of data packet / PDU set-based PDCP data copy transmission.

123. The method according to any one of claims 120-122, characterized in that The tenth information is configuration information for the terminal device, and / or the tenth information is configuration information for data radio bearer DRB / PDCP.

124. The method according to any one of claims 120 to 123, characterized in that The tenth information is carried in radio resource control RRC signaling, and / or the tenth information is carried in configuration information of PDCP.

125. The method according to any one of claims 120 to 124, characterized in that The method further comprises: The terminal device receives the eleventh information sent by the network device, and the eleventh information is used to indicate the activation or deactivation of the data packet-based PDCP data copy transmission.

126. The method according to claim 125, characterized in that The eleventh information is carried in downlink control information DCI or media access control signaling or RRC signaling.

127. The method according to claim 125 or 126, characterized in that The eleventh information is control signaling for the terminal device, or for all DRBs, or for one or more DRBs.

128. The method according to any one of claims 125-127, characterized in that The eleventh information includes a logical channel identifier LCID, and the LCID is used to identify or recognize the eleventh information.

129. The method according to any one of claims 125-128, characterized in that The eleventh information includes PDCP duplicate transmission activation / deactivation indication information for PDU set, or PDCP activation / deactivation indication information for data packet, or PDCP duplicate transmission activation / deactivation indication information for PDU.

130. The method according to any one of claims 125-129, characterized in that The method further comprises: The terminal device receives the twelfth information sent by the network device, and the twelfth information is used to indicate the activation or deactivation of PDCP data copy transmission based on DRB or RLC.

131. The method according to claim 130, characterized in that If the terminal device receives the eleventh information and the twelfth information, the terminal device uses the packet-based PDCP data replication transmission, or uses the DRB or RLC-based PDCP data replication transmission; or, the terminal device determines the replication transmission strategy to be used based on the importance level of the packet.

132. The method according to claim 131, characterized in that The terminal device determines the copy transmission strategy to be used based on the importance level of the data packet, including: Data packets with a level greater than or equal to the second importance level are replicated using all of the first transmission resources, and data packets with a level less than or equal to the second importance level are replicated using part of the first transmission resources; Alternatively, data packets with a level greater than or equal to the third importance level are replicated and transmitted using all of the first transmission resources, and data packets with a level less than or equal to the third importance level are not replicated and transmitted; Alternatively, data packets with a level greater than or equal to a fourth importance level are replicated and transmitted using part of the first transmission resources, and data packets with a level less than or equal to the fourth importance level are not replicated and transmitted; Alternatively, the data packets with a level greater than or equal to the second importance level determine their copy transmission strategy based on the eleventh information, and the data packets with a level less than or equal to the second importance level are not copied and transmitted; Alternatively, the data packets with a level greater than or equal to the third importance level determine their copy transmission strategy based on the eleventh information, and the data packets with a level less than or equal to the third importance level are not copied and transmitted; Alternatively, packets with a level greater than or equal to the fourth importance level determine their replication transmission strategy based on the eleventh information, and packets with a level less than or equal to the fourth importance level determine their replication transmission strategy based on the eleventh information. The data packets at the fourth importance level are not transmitted in duplicate; Alternatively, the data packets with a level greater than or equal to the second importance level determine their copy transmission strategy based on the eleventh information, and the data packets with a level less than or equal to the second importance level determine their copy transmission strategy based on the twelfth information; Alternatively, the data packets with a level greater than or equal to the third importance level determine their copy transmission strategy based on the eleventh information, and the data packets with a level less than or equal to the third importance level determine their copy transmission strategy based on the twelfth information; Alternatively, the data packets with a level greater than or equal to the fourth importance level determine their copy transmission strategy based on the eleventh information, and the data packets with a level less than or equal to the fourth importance level determine their copy transmission strategy based on the twelfth information; Alternatively, the data packets with a level greater than or equal to the second importance level determine their copy transmission strategy based on the twelfth information, and the data packets with a level less than or equal to the second importance level determine their copy transmission strategy based on the eleventh information; Alternatively, the data packets with a level greater than or equal to the third importance level determine their copy transmission strategy based on the twelfth information, and the data packets with a level less than or equal to the third importance level determine their copy transmission strategy based on the eleventh information; Alternatively, the data packets with a level greater than or equal to the fourth importance level determine their copy transmission strategy based on the twelfth information, and the data packets with a level less than or equal to the fourth importance level determine their copy transmission strategy based on the eleventh information.

133. The method according to any one of claims 125-132, characterized in that The eleventh information includes one or more of the following: DRB logo; LCH logo; Packet importance level; and Identifies the LCH used by packets of a specific importance level.

134. A method for wireless communication, characterized in that: include: The network device sends tenth information to the terminal device, where the tenth information is used to indicate configuration information of packet-based Packet Data Convergence Protocol PDCP data replication transmission.

135. The method according to claim 134, characterized in that The tenth information is used to indicate one or more of the following: The importance level of the packet-based PDCP data copy transmission that can be activated corresponding to the initial state; A protocol data unit set PDU set importance level using the configuration information; Importance level of packets transmitted using packet-based PDCP data replication; Indicates that packets meeting a specific PDU set importance level are transmitted using packet-based PDCP data replication; Indicates that packets or PDU sets with an importance level greater than or equal to the first importance level are transmitted using packet-based PDCP data copying.

136. The method according to claim 134 or 135, characterized in that If the tenth information includes configuration information of data packet-based PDCP data copy transmission, the tenth information is used to indicate whether data packet / PDU set-based PDCP data copy transmission is enabled, or the tenth information is used to indicate the initial state of data packet / PDU set-based PDCP data copy transmission.

137. The method according to any one of claims 134-136, characterized in that The tenth information is configuration information for the terminal device, and / or the tenth information is configuration information for data radio bearer DRB / PDCP.

138. The method according to any one of claims 134-137, characterized in that The tenth information is carried in radio resource control RRC signaling, and / or the tenth information is carried in configuration information of PDCP.

139. The method according to any one of claims 134-138, characterized in that The method further comprises: The network device sends an eleventh message to the terminal device, where the eleventh message is used to indicate activation or deactivation of data packet-based PDCP data copy transmission.

140. The method according to claim 139, characterized in that The eleventh information is carried in downlink control information DCI or media access control signaling or RRC signaling.

141. The method according to claim 139 or 140, characterized in that The eleventh information is control signaling for the terminal device, or for all DRBs, or for one or more DRBs.

142. The method according to any one of claims 139-141, characterized in that The eleventh information includes a logical channel identifier LCID, and the LCID is used to identify or recognize the eleventh information.

143. The method according to any one of claims 139-142, characterized in that The eleventh information includes PDCP duplicate transmission activation / deactivation indication information for PDU set, or PDCP activation / deactivation indication information for data packet, or PDCP duplicate transmission activation / deactivation indication information for PDU.

144. The method according to any one of claims 139-143, characterized in that The method further comprises: The network device sends twelfth information to the terminal device, where the twelfth information is used to indicate activation or deactivation of DRB- or RLC-based PDCP data copy transmission.

145. The method according to any one of claims 139-144, characterized in that The eleventh information includes one or more of the following: DRB logo; LCH logo; Packet importance level; and Identifies the LCH used by packets of a specific importance level.

146. A method for wireless communication, characterized in that: include: The first network device sends a cell switching request to the second network device to execute a cell switching process of the terminal device, wherein the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, the first data is data with an associated relationship, the first network device is a source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

147. The method according to claim 146, characterized in that The cell switching request message includes the thirteenth information, wherein the thirteenth information is associated with the terminal device.

148. The method according to claim 147, characterized in that Before the first network device sends the cell switching request to the second network device, the method further includes: The first network device receives the thirteenth information sent by the terminal device or the core network node.

149. The method according to claim 148, characterized in that The core network node is one or more of the following: Application function network element; User plane functional network element; Mobility management function network element; and Session management functional network element.

150. The method according to claim 148 or 149, characterized in that When one or more of the following conditions are met, the first network device receives the thirteenth information sent by the terminal device: The terminal device has not sent the thirteenth information to the first network device; The terminal device establishes or modifies part or all of the content in the thirteenth information; The terminal device initiates a service request; The reporting prohibition timer is not running; as well as Part or all of the content of the thirteenth information has changed.

151. The method according to any one of claims 146-150, characterized in that The method further comprises: The first network device receives fourteenth information sent by the second network device, where the fourteenth information is a response message to the switching request message, and the fourteenth information is determined based on the thirteenth message.

152. The method according to claim 151, characterized in that The fourteenth information includes one or more of the following: Whether the second network device supports access by the terminal device; Whether the second network device supports a protocol data unit set PDU set; as well as Whether the second network device supports transmission of the first data.

153. The method according to claim 151 or 152, characterized in that The method further comprises: The first network device determines whether the second network device is the target network device of the terminal device based on the fourteenth information.

154. The method according to claim 146, characterized in that Before the first network device sends the cell switching request to the second network device, the method further includes: The first network device obtains the thirteenth information, and the thirteenth information is associated with the second network device.

155. The method according to claim 154, characterized in that The first network device obtains the thirteenth information from a core network node, operation maintenance management OAM, a network device adjacent to the first network device, or the second network device.

156. The method according to claim 155, characterized in that The core network node is one or more of the following: Application function network element; User plane functional network element; Mobility management function network element; and Session management functional network element.

157. The method according to any one of claims 154-156, characterized in that In response to one or more of the following situations, the first network device obtains the thirteenth information: a request of the first network device; Updates to the thirteenth information; Periodic update time; establishing an interface between the second network device and the first network device; Establishing an interface between the second network device and the core network node; as well as The thirteenth information is obtained.

158. The method according to any one of claims 154-157, characterized in that The first network device sending a cell switching request to the second network device includes: The first network device sends the cell switching request to the second network device based on the thirteenth information.

159. The method according to any one of claims 146-158, characterized in that If there are multiple second network devices, the first network device does not select a network device that does not support the first data transmission and / or does not support PDU set; or The first network device selects a network device that supports the first data transmission and / or supports PDU set.

160. The method according to any one of claims 146-159, characterized in that The thirteenth information includes one or more of the following information: The association of quality of service flows; The association relationship between multiple terminal devices; and Whether PDU set is enabled; Among them, the multiple terminal devices are recipients and / or senders of the first data.

161. The method according to any one of claims 146-160, characterized in that The first data includes associated multimodal data streams and / or associated data packets.

162. The method according to any one of claims 146-161, characterized in that The method further comprises: The transmission delay of the first data sent by the first network device to the second network device; or The transmission delay of the PDU set to which the first data belongs sent by the first network device to the second network device; or The transmission delay of data, data packet or PDU set associated with the first data sent by the first network device to the second network device.

163. A method for wireless communication, characterized in that: include: The second network device receives the cell switching request sent by the first network device to execute the cell switching process of the terminal device, wherein the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of data with an associated relationship, the first network device is the source network device of the terminal device, and the second network device is the candidate target network device of the terminal device.

164. The method according to claim 163, characterized in that The cell switching request message includes the thirteenth information, wherein the thirteenth information is associated with the terminal device.

165. The method according to claim 163, characterized in that Before the second network device receives the cell switching request sent by the first network device, or when the second network device receives the cell switching request sent by the first network device, or after the second network device receives the cell switching request sent by the first network device, the method further includes: The second network device obtains the thirteenth information, wherein the thirteenth information is associated with the terminal device.

166. The method according to claim 165, characterized in that The thirteenth information is obtained by the second network device from the core network node or the operation maintenance management OAM, or the thirteenth information is obtained by the second network device from the first network device.

167. The method according to claim 166, characterized in that The core network node is one or more of the following: Application function network element; User plane functional network element; Mobility management function network element; and Session management functional network element.

168. The method according to any one of claims 165-167, characterized in that In response to one or more of the following situations, the second network device obtains the thirteenth information: a request of the second network device; Updates to the thirteenth information; Periodic update time; establishing an interface between the second network device and the first network device; Establishing an interface between the second network device and the core network node; as well as The thirteenth information is obtained.

169. The method according to any one of claims 163-168, characterized in that The method further comprises: The second network device sends fourteenth information to the first network device, where the fourteenth information is a response message to the switching request message, and the fourteenth information is determined based on the thirteenth message.

170. The method according to claim 169, characterized in that The fourteenth information includes one or more of the following: Whether the second network device supports access by the terminal device; Whether the second network device supports a protocol data unit set PDU set; as well as Whether the second network device supports transmission of the first data.

171. The method according to claim 163, characterized in that The second network device receiving the cell switching request sent by the first network device includes: The second network device receives a cell switching request sent by the first network device, where the cell switching request is determined based on the thirteenth information, wherein the thirteenth information is associated with the second network device.

172. The method according to any one of claims 163-171, characterized in that The thirteenth information includes one or more of the following information: The association of quality of service flows; The association relationship between multiple terminal devices; and Whether PDU set is enabled; The multiple terminal devices are receivers and / or senders of the associated data.

173. The method according to any one of claims 163-172, characterized in that The first data includes associated multimodal data streams and / or associated data packets.

174. The method according to claim 163, characterized in that If the terminal device switches to the second network device, the method further includes: The second network device receives the thirteenth information sent by the terminal device, and the thirteenth information is associated with the terminal device.

175. The method according to claim 174, characterized in that When one or more of the following conditions are met, the second network device receives or obtains the thirteenth information sent by the terminal device: The terminal device receives a cell switching command; The terminal device has not reported the thirteenth information to the first network device; The terminal device has not reported the thirteenth information; The terminal device reports the thirteenth information within a first time before the cell switching; The second network device requests the terminal device to send the thirteenth information; and The terminal device is configured to report the thirteenth information to the target network device after the cell switching.

176. The method according to any one of claims 163-175, characterized in that If the terminal device switches to the second network device, the method further includes: The second network device adds relevant information of the PDU set to the first data / data packet, or the second network device adds header information to the first data / data packet, wherein the first data / data packet is part of the first data transmitted by the first network device before the terminal device performs cell switching, and the header information indicates relevant information of the PDU set or indicates the PDU set to which the data packet belongs.

177. The method according to claim 176, characterized in that If the transmission delay of the first data / data packet is greater than or equal to the first threshold, the second network device deletes the first data / data packet.

178. The method according to claim 177, characterized in that If the transmission delay of the first data / data packet is greater than or equal to the first threshold, the second network device deletes all data packets of the PDU set to which the first data / data packet belongs, or deletes data, data packets or PDU sets associated with the first data / data packet.

179. The method according to any one of claims 163-178, characterized in that The transmission delay of the first data sent by the first network device or the terminal device to the second network device; or The transmission delay of the PDU set to which the first data belongs and which is received by the second network device and sent by the first network device or the terminal device; or The second network device receives the data, data packet or PDU set transmission delay associated with the first data sent by the first network device or the terminal device.

180. A method for wireless communication, characterized in that: include: The terminal device performs a cell switching, and the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, and the first data is data with an associated relationship.

181. The method according to claim 180, characterized in that The thirteenth information is carried in the request message for the cell switching, wherein the thirteenth information is associated with the terminal device.

182. The method according to claim 181, characterized in that Before the terminal device performs cell switching, the method further includes: The terminal device sends the thirteenth information to a first network device, wherein the first network device is a source network device before the terminal device performs the cell switching.

183. The method according to claim 182, characterized in that When one or more of the following conditions are met, the terminal device sends the thirteenth information to the first network device: The terminal device has not sent the thirteenth information to the first network device; The terminal device establishes or modifies part or all of the content in the thirteenth information; The terminal device initiates a service request; The reporting prohibition timer is not running; as well as Part or all of the content of the thirteenth information has changed.

184. The method according to any one of claims 180-183, characterized in that The thirteenth information includes one or more of the following information: The association of quality of service flows; The association relationship between multiple terminal devices; as well as Whether the protocol data unit set PDU set is enabled; Among them, the multiple terminal devices are recipients and / or senders of the first data.

185. The method according to any one of claims 180-184, characterized in that The first data includes associated multimodal data streams and / or associated data packets.

186. The method according to claim 180, characterized in that If the terminal device switches to the second network device, the method further includes: The terminal device sends the thirteenth information to the second network device, and the thirteenth information is associated with the terminal device.

187. The method according to claim 186, characterized in that When one or more of the following conditions are met, the terminal device sends the thirteenth information to the second network device: The terminal device receives a cell switching command; The terminal device has not reported the thirteenth information to the first network device; The terminal device has not reported the thirteenth information; The terminal device reports the thirteenth information within a first time before the cell switching; The second network device requests the terminal device to send the thirteenth information; and The terminal device is configured to report the thirteenth information to the target network device after the cell switching.

188. The method according to any one of claims 180-187, characterized in that The method further comprises: The transmission delay of the terminal device sending the first data to the second network device; or The transmission delay of the PDU set to which the first data belongs sent by the terminal device to the second network device; or The transmission delay of data, data packet or PDU set associated with the first data sent by the terminal device to the second network device.

189. A communication device, characterized in that: The device is a first device, and the device includes: A receiving unit is used to receive first information sent by a second device, wherein the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

190. A communication device, characterized in that: The device is a second device, and the device includes: A sending unit is used to send first information to a first device, wherein the first information is used to enable or activate a first behavior, or the first information is used to configure parameters of first data, or the first information is used to determine transmission resources of the first data, wherein the first data is data with an associated relationship, and the first behavior is related to the first data.

191. A terminal device, characterized in that: include: The receiving unit is used to receive tenth information sent by the network device, where the tenth information is used to indicate configuration information of packet data convergence protocol PDCP data replication transmission based on data packets.

192. A network device, characterized in that: include: The sending unit is used to send tenth information to the terminal device, where the tenth information is used to indicate configuration information of packet-based packet data convergence protocol PDCP data replication transmission.

193. A network device, characterized in that: The network device is a first network device, and the network device includes: A sending unit, used for sending a cell switching request to a second network device to execute a cell switching process of a terminal device, wherein the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, the first data is data with an associated relationship, the first network device is a source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

194. A network device, characterized in that: The network device is a second network device, and the network device includes: a receiving unit, configured to receive a cell switching request sent by a first network device to execute a cell switching process of a terminal device, wherein the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of data having an associated relationship, and the The first network device is a source network device of the terminal device, and the second network device is a candidate target network device of the terminal device.

195. A terminal device, characterized in that: include: An execution unit is used to execute a cell switching process, wherein the cell switching process is determined based on thirteenth information, wherein the thirteenth information is related to the transmission of first data, and the first data is data with an associated relationship.

196. A terminal device, characterized in that: It comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

197. A network device, characterized in that: It comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method as described in any one of claims 1-63, 64-119, 134-145, 146-162, and 163-179.

198. A device, characterized in that: It comprises a processor for calling a program from a memory to execute a method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

199. A device, characterized in that: It comprises a processor for calling a program from a memory to execute a method as described in any one of claims 1-63, 64-119, 134-145, 146-162, 163-179.

200. A chip, characterized in that: It comprises a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

201. A chip, characterized in that: It comprises a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1-63, 64-119, 134-145, 146-162, 163-179.

202. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing the computer to execute the method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

203. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing the computer to execute the method as described in any one of claims 1-63, 64-119, 134-145, 146-162, 163-179.

204. A computer program product, characterized in that It comprises a program which enables a computer to execute the method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

205. A computer program product, characterized in that It comprises a program which enables a computer to execute the method as described in any one of claims 1-63, 64-119, 134-145, 146-162, 163-179.

206. A computer program, characterized in that The computer program enables a computer to execute the method as described in any one of claims 1-63, 64-119, 120-133, 180-188.

207. A computer program, characterized in that The computer program enables a computer to execute the method as described in any one of claims 1-63, 64-119, 134-145, 146-162, 163-179.

Images