Method of wireless communication and communication device

Abstract

A wireless communication method and communication device are provided. The method includes: a second device sending first information to a first device, the first information being associated with synchronous or cooperative transmission of at least one object. In this embodiment, the second device can send the first information to the first device, the first information being associated with synchronous or cooperative transmission of at least one object, which helps the first device obtain the transmission requirements (e.g., synchronous or cooperative transmission requirements) of at least one object based on the first information, so as to achieve synchronization or cooperation of at least one object during the transmission phase. Compared with conventional solutions that rely on the receiving end to store at least one object to achieve synchronous or cooperative transmission of at least one object, this helps to reduce the storage space requirements of the receiving end.

Description

Wireless communication method and communication device Technical Field

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

[0002] In some scenarios, multiple objects need to be presented to the user in a synchronized or coordinated manner. Currently, synchronization of multiple objects can only be achieved at the application layer. This means caching multiple objects at the application layer and presenting them to the user in a synchronized or coordinated manner based on their timestamps. However, this approach of caching multiple objects at the application layer places certain requirements on the device's storage space, limiting its applicable scenarios.

[0003] In some scenarios, multiple objects may include multi-modality flows. Typically, multi-modality flows may include voice data streams, video data streams, and subtitle data streams, wherein the voice data streams, video data streams, and subtitle data streams need to be displayed to the user synchronously, that is, the multi-modal data streams need to be presented to the user in a synchronous or collaborative manner. Currently, multi-modal data streams can only be synchronized at the application layer, that is, the received multi-modal data streams are cached at the application layer, and the data frames of different data streams in the multi-modal data stream are extracted according to the timestamp of the played data stream, and the data frames of different data streams are synchronously displayed to the user. However, this solution of caching multi-modal data streams at the application layer has certain requirements on the size of the storage space of the device, which limits the scenarios in which the solution is applicable.

[0004] Summary of the Invention

[0005] The present application provides a wireless communication method and a communication device. The following introduces various aspects of the present application.

[0006] In a first aspect, a method for wireless communication is provided, comprising: a second device sending first information to a first device, where the first information is associated with synchronous transmission or cooperative transmission of at least one object.

[0007] In a second aspect, a method for wireless communication is provided, including: a first device receiving first information sent by a second device, where the first information is associated with synchronous transmission or cooperative transmission of at least one object.

[0008] According to a third aspect, a communication device is provided, which is a second device and includes: a sending unit configured to send first information to a first device, where the first information is associated with synchronous transmission or collaborative transmission of at least one object.

[0009] In a fourth aspect, a communication device is provided, which is a first device and includes: a receiving unit, configured to receive first information sent by a second device, wherein the first information is associated with synchronous transmission or collaborative transmission of at least one object.

[0010] In a fifth aspect, a communication device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the first aspect.

[0011] In the sixth aspect, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the second aspect.

[0012] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a communication device to execute part or all of the steps in the methods of the above aspects.

[0014] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0015] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0016] In an embodiment of the present application, a second device may send first information to a first device, where the first information is associated with the synchronous transmission or coordinated transmission of at least one object, thereby helping the first device obtain the transmission requirements (e.g., synchronous transmission requirements or coordinated transmission requirements) of the at least one object based on the first information, thereby achieving synchronization or coordination of the at least one object during the transmission phase. Compared to traditional solutions that rely on the receiving end to store at least one object to achieve synchronous transmission or coordinated transmission of the at least one object, this helps reduce the storage space requirements on the receiving end. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] FIG2 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0019] FIG3 is a schematic diagram of a service data adaptation protocol (SDAP) control protocol data unit (PDU) in an embodiment of the present application.

[0020] FIG4 is a schematic diagram of an SDAP control PDU in another embodiment of the present application.

[0021] FIG5 is a schematic diagram of an SDAP control PDU in another embodiment of the present application.

[0022] FIG6 is a schematic diagram of the structure of an SDAP data PDU in an embodiment of the present application.

[0023] FIG7 is a schematic diagram of the structure of an SDAP data PDU in an embodiment of the present application.

[0024] FIG8 is a schematic flowchart of the wireless communication method in Example 1 of the present application.

[0025] Figure 9 is a schematic flowchart of the wireless communication method in Example 2 of the present application.

[0026] FIG10 is a schematic diagram of a communication device according to an embodiment of the present application.

[0027] FIG11 is a schematic diagram of a communication device according to an embodiment of the present application.

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

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

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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, a modem or a 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.

[0036] 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.

[0037] 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 may include a CU and a DU. The gNB may also include an AAU.

[0038] 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.

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

[0040] Application scenarios of communication systems

[0041] Currently, the main application scenarios of communication systems (e.g., 5G) can include enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC), and massive machine type communication (mMTC).

[0042] Demand for eMBB, which can be applied to scenarios such as users accessing multimedia content, services, and data, is growing rapidly. Furthermore, eMBB can be deployed in diverse environments, such as indoors, in urban areas, and in rural areas. The capabilities and requirements for eMBB vary significantly in these environments.

[0043] URLLC can be applied to scenarios such as industrial automation, power automation, remote medical operations (surgery), and traffic safety. Typical features of mMTC include high connection density, small data volumes, latency-insensitive services, low module cost, and long service life.

[0044] Radio resource control (RRC) state and mobility management

[0045] Currently, the protocol defines three RRC states of terminal devices: RRC connected (RRC_connected) state, RRC idle (RRC-idle) state and RRC inactive (RRC-inactive) state.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] XR

[0054] In some meetings (for example, the 3GPP RAN#88e meeting), a research project called "Evolving Extended Reality (XR) and Cloud Gaming (CG) in NR" was proposed. The XR services studied in this project may include augmented reality (AR) and virtual reality (VR). One of the main services in the XR service and / or CG service is the video stream service, which has a high requirement for the transmission rate. For example, the video stream service has a high requirement for the transmission rate. The transmission rate requirement of the video stream service can be 30fps, 60fps, 90fps, or 120fps. Accordingly, the corresponding period of the video stream service is {33.33ms, 16.67ms, 11.11ms, 8.33ms}.

[0055] Currently, XR service data features variable data size and a relatively large average. For AR / VR services with a 100Mbps data transmission rate, the average uplink data packet size is 20,833 bytes, with a maximum of 31,250 bytes and a minimum of 10,417 bytes. This means that the size of the data packet to be transmitted in each cycle is between [10,417 bytes and 31,250 bytes]. Typically, in a 100Mbps bandwidth communication system, transmitting a 20,833-byte data packet takes approximately four time slots.

[0056] In some scenarios, it is proposed that multiple PUSCH opportunities (occasion) can be configured within a CG cycle to transmit data packets with large data volumes (also known as "large data packets") in XR services. In addition, multiple sets of CGs can be configured to transmit data packets with large data volumes in XR services. When the amount of data transmitted in a certain data transmission is relatively small, it is not necessary to occupy multiple pre-configured PUSCH opportunities. At this time, the terminal device can notify the network device not to use the PUSCH opportunity. Accordingly, the network device can reallocate the unused PUSCH opportunities to other terminal devices for data transmission, thereby improving system efficiency.

[0057] In some scenarios, multiple objects need to be presented to the user in a synchronized or coordinated manner. Currently, synchronization of multiple objects can only be achieved at the application layer. This means caching multiple objects at the application layer and presenting them to the user in a synchronized or coordinated manner based on their timestamps. However, this approach of caching multiple objects at the application layer places certain requirements on the device's storage space, limiting its applicable scenarios.

[0058] In some scenarios, multiple objects may include multi-modality flows. Typically, multi-modality flows may include voice data streams, video data streams, and subtitle data streams, wherein the voice data streams, video data streams, and subtitle data streams need to be displayed to the user synchronously, that is, the multi-modal data streams need to be presented to the user in a synchronous or collaborative manner. Currently, multi-modal data streams can only be synchronized at the application layer, that is, the received multi-modal data streams are cached at the application layer, and the data frames of different data streams in the multi-modal data stream are extracted according to the timestamp of the played data stream, and the data frames of different data streams are synchronously displayed to the user. However, this solution of caching multi-modal data streams at the application layer has certain requirements on the size of the storage space of the device, which limits the scenarios in which the solution is applicable.

[0059] Therefore, in response to the above problems, the applicant proposes that synchronous transmission or collaborative transmission can be performed on at least one object (for example, the multimodal data stream mentioned above). In this way, the at least one object received by the receiving end can be directly presented to the user, which helps to reduce the requirements for device storage space and improve the applicable scenarios of the solution. However, the communication device cannot obtain information related to synchronous transmission or collaborative transmission. For example, the communication device cannot determine which objects need to be synchronously transmitted or collaboratively transmitted. For another example, the communication device cannot determine the parameters for synchronous transmission or collaborative transmission of at least one object, resulting in the inability to achieve synchronous transmission or collaborative transmission of at least one object.

[0060] Therefore, in response to the above problems, the applicant proposed a wireless communication method, in which a first device and a second device can exchange information associated with the synchronous transmission or collaborative transmission of at least one object (also called "first information"), which helps to achieve the synchronous transmission or collaborative transmission of at least one object.

[0061] The following describes a wireless communication method according to an embodiment of the present application in conjunction with FIG2 , which is a schematic flow chart of the wireless communication method according to an embodiment of the present application. The method shown in FIG2 includes step S210 .

[0062] In step S210, the second device sends first information to the first device, where the first information is associated with synchronous transmission or coordinated transmission of at least one object.

[0063] In an embodiment of the present application, a second device may send first information to a first device, where the first information is associated with the synchronous transmission or coordinated transmission of at least one object, thereby helping the first device obtain the transmission requirements (e.g., synchronous transmission requirements or coordinated transmission requirements) of the at least one object based on the first information, thereby achieving synchronization or coordination of the at least one object during the transmission phase. Compared to traditional solutions that rely on the receiving end to store at least one object to achieve synchronous transmission or coordinated transmission of the at least one object, this helps reduce the storage space requirements on the receiving end.

[0064] In some implementations, the aforementioned coordinated transmission can be understood as collaboration, association, or dependency in transmission or processing. For example, the coordinated transmission of multiple objects can be understood as completing the transmission or processing of multiple objects within a period of time, where the multiple objects may include some or all of the at least one object associated with the first information. For example, if data stream 1 and data stream 2 are coordinated for transmission or processing, and the period of time is 5 seconds, then the coordinated transmission or processing can be understood as completing the transmission or processing of data stream 1 and data stream 2 within 5 seconds.

[0065] In some implementations, the aforementioned synchronous transmission may also be referred to as simultaneous transmission. For example, synchronous transmission of multiple objects may be understood as multiple objects communicating or processing at the same clock, where the multiple objects may include some or all of the at least one object associated with the first information. For synchronous transmission of data stream 1 and data stream 2, synchronous transmission may be understood as the transmission time of data stream 1 and data stream 2 being the same or similar. In other examples, synchronous transmission may be understood as the reception time, processing time, or decoding time of data stream 1 and data stream 2 being the same or similar.

[0066] Of course, in the embodiment of the present application, synchronous transmission can be understood as transmission within a range segment or time period, or transmission within a range or time, or transmission according to a time limit.

[0067] In the embodiments of the present application, the term "transmission" is not limited in meaning. In some implementations, transmission includes, but is not limited to, one or more of the following: sending, receiving, decoding, demodulating, encoding, displaying, implementation of a specific layer or function, operation of a specific layer or function (e.g., operation requiring synchronization, or operation requiring a time or time point or time limit), and delivery of a specific layer or function to another layer or function.

[0068] In the embodiments of the present invention, the object is not specifically limited. For example, the object can be one or more of the following: quality of service (QoS) flow, data flow (e.g., any data flow, or associated data flow, or multimodal data flow), terminal device, PDU session, bearer (also known as radio bearer), data packet, data, PDU set, data burst, PDU, SDU.

[0069] If the object is a QoS flow, in some implementations, if the first information is associated with the synchronous transmission of a QoS flow, the synchronous transmission of a QoS flow can be understood as the synchronous transmission between the QoS flow and other QoS flows. Optionally, the above-mentioned one QoS flow is any QoS flow, or a specific QoS flow. If the first information is associated with the synchronous transmission of multiple QoS flows, the synchronous transmission of multiple QoS flows can be understood as the synchronous transmission between multiple QoS flows. Of course, in an embodiment of the present application, the synchronous transmission of multiple QoS flows can also be understood as the synchronous transmission between multiple QoS flows and other QoS flows. Among them, other QoS flows can be understood as QoS flows other than the QoS flow associated with the first information, and / or, other QoS flows can be QoS flows with synchronization requirements.

[0070] In other implementations, if the first information is associated with the collaborative transmission of a QoS flow, the collaborative transmission of a QoS flow can be understood as the collaborative transmission between the QoS flow and other QoS flows. Optionally, the above-mentioned one QoS flow is any QoS flow, or a specific QoS flow. If the first information is associated with the collaborative transmission of multiple QoS flows, the collaborative transmission of multiple QoS flows can be understood as the collaborative transmission between multiple QoS flows. Of course, in an embodiment of the present application, the collaborative transmission of multiple QoS flows can also be understood as the collaborative transmission between multiple QoS flows and other QoS flows. Among them, other QoS flows can be understood as QoS flows other than the QoS flow associated with the first information, and / or, other QoS flows can be QoS flows with collaborative requirements.

[0071] If the object is a data stream, in some implementations, if the first information is associated with the synchronous transmission of a data stream, the synchronous transmission of a data stream can be understood as the synchronous transmission between the data stream and other data streams. Optionally, the above-mentioned one data stream is any data stream, or a specific data stream. If the first information is associated with the synchronous transmission of multiple data streams, the synchronous transmission of multiple data streams can be understood as the synchronous transmission between multiple data streams. Of course, in an embodiment of the present application, the synchronous transmission of multiple data streams can also be understood as the synchronous transmission between multiple data streams and other data streams. Among them, other data streams can be understood as data streams other than the data stream associated with the first information, and / or, other data streams can be data streams with synchronization requirements.

[0072] In other implementations, if the first information is associated with the coordinated transmission of a data stream, the coordinated transmission associated with a data stream can be understood as the coordinated transmission between the data stream and other data streams. Optionally, the above-mentioned one data stream is any data stream, or a specific data stream. If the first information is associated with the coordinated transmission of multiple data streams, the coordinated transmission of multiple data streams can be understood as the coordinated transmission between multiple data streams. Of course, in an embodiment of the present application, the coordinated transmission of multiple data streams can also be understood as the coordinated transmission between multiple data streams and other data streams. Among them, other data streams can be understood as data streams other than the data stream associated with the first information, and / or, other data streams can be data streams with collaborative requirements.

[0073] It should be noted that the data stream may be the multimodal data stream mentioned above, and accordingly, the first information may be referred to as "multimodal information".

[0074] If the object is a terminal device, in some implementations, if the first information is associated with the synchronous transmission of a terminal device, the synchronous transmission of a terminal device can be understood as the synchronous transmission between the terminal device and other terminal devices. Optionally, the above-mentioned terminal device is any terminal device, or a specific terminal device. If the first information is associated with the synchronous transmission of multiple terminal devices, the synchronous transmission of multiple terminal devices can be understood as the synchronous transmission between multiple terminal devices. Of course, in an embodiment of the present application, the synchronous transmission of multiple terminal devices can also be understood as the synchronous transmission between multiple terminal devices and other terminal devices. Among them, other terminal devices can be understood as terminal devices other than the terminal device associated with the first information, and / or, other terminal devices can be data streams with synchronization requirements.

[0075] In other implementations, if the first information is associated with the coordinated transmission of a terminal device, the coordinated transmission associated with a terminal device can be understood as the coordinated transmission between the terminal device and other terminal devices. Optionally, the above-mentioned terminal device is any terminal device, or a specific terminal device. If the first information is associated with the coordinated transmission of multiple terminal devices, the coordinated transmission of multiple terminal devices can be understood as the coordinated transmission between multiple terminal devices. Of course, in an embodiment of the present application, the coordinated transmission of multiple terminal devices can also be understood as the coordinated transmission between multiple terminal devices and other terminal devices. Among them, other terminal devices can be understood as terminal devices other than the terminal device associated with the first information, and / or, other terminal devices can be data streams with collaborative requirements.

[0076] If the object is a PDU session, in some implementations, if the first information is associated with the synchronous transmission of a PDU session, the synchronous transmission of a PDU session can be understood as the synchronous transmission between the PDU session and other PDU sessions. Optionally, the above-mentioned one PDU session is any PDU session, or a specific PDU session. If the first information is associated with the synchronous transmission of multiple PDU sessions, the synchronous transmission of multiple PDU sessions can be understood as the synchronous transmission between multiple PDU sessions. Of course, in an embodiment of the present application, the synchronous transmission of multiple PDU sessions can also be understood as the synchronous transmission between multiple PDU sessions and other PDU sessions. Among them, other PDU sessions can be understood as PDU sessions other than the PDU session associated with the first information, and / or, other terminal devices can be data streams with synchronization requirements.

[0077] In other implementations, if the first information is associated with the coordinated transmission of a PDU session, the coordinated transmission associated with a PDU session can be understood as the coordinated transmission between the PDU session and other PDU sessions. Optionally, the above-mentioned one PDU session is any PDU session, or a specific PDU session. If the first information is associated with the coordinated transmission of multiple PDU sessions, the coordinated transmission of multiple PDU sessions can be understood as the coordinated transmission between multiple PDU sessions. Of course, in an embodiment of the present application, the coordinated transmission of multiple PDU sessions can also be understood as the coordinated transmission between multiple PDU sessions and other PDU sessions. Among them, other PDU sessions can be understood as PDU sessions other than the PDU session associated with the first information, and / or, other terminal devices can be data streams with collaborative requirements.

[0078] If the object is a bearer, in some implementations, if the first information is associated with the synchronous transmission of a bearer, the synchronous transmission of a bearer can be understood as the synchronous transmission between the bearer and other bearers. Optionally, the above-mentioned one bearer is any bearer, or a specific bearer. If the first information is associated with the synchronous transmission of multiple bearers, the synchronous transmission of multiple bearers can be understood as the synchronous transmission between multiple bearers. Of course, in an embodiment of the present application, the synchronous transmission of multiple bearers can also be understood as the synchronous transmission between multiple bearers and other bearers. Among them, other bearers can be understood as bearers other than the bearer associated with the first information, and / or, other bearers can be bearers with synchronization requirements.

[0079] In other implementations, if the first information is associated with the coordinated transmission of a bearer, the coordinated transmission associated with a bearer can be understood as the coordinated transmission between the bearer and other bearers. Optionally, the above-mentioned one bearer is any bearer, or a specific bearer. If the first information is associated with the coordinated transmission of multiple bearers, the coordinated transmission of multiple bearers can be understood as the coordinated transmission between multiple bearers. Of course, in the embodiment of the present application, the coordinated transmission of multiple bearers can also be understood as the coordinated transmission between multiple bearers and other bearers. Among them, other bearers can be understood as bearers other than the bearer associated with the first information, and / or, other bearers can be bearers with coordination requirements.

[0080] In the embodiment of the present application, the above-mentioned bearer is also referred to as a "radio bearer", for example, it may include a data radio bearer (DRB). Optionally, in some scenarios, it may be extended to a signaling radio bearer (SRB). Accordingly, the synchronization or association relationship may be between SRBs, or between an SRB and a DRB, or between DRBs.

[0081] If the object is a data packet, in some implementations, if the first information is associated with the synchronous transmission of a data packet, the synchronous transmission of a data packet can be understood as the synchronous transmission between the data packet and other data packets. Optionally, the above-mentioned data packet is any data packet, or a specific data packet. If the first information is associated with the synchronous transmission of multiple data packets, the synchronous transmission of multiple data packets can be understood as the synchronous transmission between multiple data packets. Of course, in an embodiment of the present application, the synchronous transmission of multiple data packets can also be understood as the synchronous transmission between multiple data packets and other data packets. Among them, other data packets can be understood as data packets other than the data packets associated with the first information, and / or, other data packets can be data packets with synchronization requirements.

[0082] In other implementations, if the first information is associated with the coordinated transmission of a data packet, the coordinated transmission associated with a data packet can be understood as the coordinated transmission between the data packet and other data packets. Optionally, the above-mentioned data packet is any data packet, or a specific data packet. If the first information is associated with the coordinated transmission of multiple data packets, the coordinated transmission of multiple data packets can be understood as the coordinated transmission between multiple data packets. Of course, in an embodiment of the present application, the coordinated transmission of multiple data packets can also be understood as the coordinated transmission between multiple data packets and other data packets. Among them, other data packets can be understood as data packets other than the data packets associated with the first information, and / or, other data packets can be data packets with coordination requirements.

[0083] If the object is data, in some implementations, if the first information is associated with the synchronous transmission of one data, the synchronous transmission of one data can be understood as the synchronous transmission between the data and other data. Optionally, the above-mentioned one data is any data, or specific data. If the first information is associated with the synchronous transmission of multiple data, the synchronous transmission of multiple data can be understood as the synchronous transmission between multiple data. Of course, in an embodiment of the present application, the synchronous transmission of multiple data can also be understood as the synchronous transmission between multiple data and other data. Among them, other data can be understood as data other than the data associated with the first information and / or, other data can be data with synchronization requirements.

[0084] In other implementations, if the first information is associated with the coordinated transmission of one data, the coordinated transmission of one data association can be understood as the coordinated transmission between the data and other data. Optionally, the above-mentioned one data is any data, or specific data. If the first information is associated with the coordinated transmission of multiple data, the coordinated transmission of multiple data can be understood as the coordinated transmission between multiple data. Of course, in an embodiment of the present application, the coordinated transmission of multiple data can also be understood as the coordinated transmission between multiple data and other data. Among them, other data can be understood as data other than the data associated with the first information, and / or, other data can be data with collaborative requirements.

[0085] If the object is a PDU set, in some implementations, if the first information is associated with the synchronous transmission of a PDU set, the synchronous transmission of a PDU set can be understood as the synchronous transmission between the PDU set and other PDU sets. Optionally, the above-mentioned one PDU set is any PDU set, or a specific PDU set. If the first information is associated with the synchronous transmission of multiple PDU sets, the synchronous transmission of multiple PDU sets can be understood as the synchronous transmission between multiple PDU sets. Of course, in an embodiment of the present application, the synchronous transmission of multiple PDU sets can also be understood as the synchronous transmission between multiple PDU sets and other PDU sets. Among them, other PDU sets can be understood as PDU sets other than the PDU set associated with the first information, and / or, other PDU sets can be PDU sets with synchronization requirements.

[0086] In other implementations, if the first information is associated with the coordinated transmission of a PDU set, the coordinated transmission associated with a PDU set can be understood as the coordinated transmission between the PDU set and other PDU sets. Optionally, the above-mentioned one PDU set is any PDU set, or a specific PDU set. If the first information is associated with the coordinated transmission of multiple PDU sets, the coordinated transmission of multiple PDU sets can be understood as the coordinated transmission between multiple PDU sets. Of course, in an embodiment of the present application, the coordinated transmission of multiple PDU sets can also be understood as the coordinated transmission between multiple PDU sets and other PDU sets. Among them, other PDU sets can be understood as PDU sets other than the PDU set associated with the first information, and / or, other PDU sets can be PDU sets with coordination requirements.

[0087] If the object is a PDU, in some implementations, if the first information is associated with the synchronous transmission of a PDU, the synchronous transmission of a PDU can be understood as the synchronous transmission between the PDU and other PDUs. Optionally, the above-mentioned one PDU is any PDU, or a specific PDU. If the first information is associated with the synchronous transmission of multiple PDUs, the synchronous transmission of multiple PDUs can be understood as the synchronous transmission between multiple PDUs. Of course, in an embodiment of the present application, the synchronous transmission of multiple PDUs can also be understood as the synchronous transmission between multiple PDUs and other PDUs. Among them, other PDUs can be understood as PDUs other than the PDU associated with the first information, and / or, other PDUs can be PDUs with synchronization requirements.

[0088] In other implementations, if the first information is associated with the coordinated transmission of a PDU, the coordinated transmission associated with a PDU can be understood as the coordinated transmission between the PDU and other PDUs. Optionally, the above-mentioned one PDU is any PDU, or a specific PDU. If the first information is associated with the coordinated transmission of multiple PDUs, the coordinated transmission of multiple PDUs can be understood as the coordinated transmission between multiple PDUs. Of course, in an embodiment of the present application, the coordinated transmission of multiple PDUs can also be understood as the coordinated transmission between multiple PDUs and other PDUs. Among them, other PDUs can be understood as PDUs other than the PDU associated with the first information, and / or, other PDUs can be PDUs with coordination requirements.

[0089] If the object is an SDU, in some implementations, if the first information is associated with the synchronous transmission of an SDU, the synchronous transmission of an SDU can be understood as the synchronous transmission between the SDU and other SDUs. Optionally, the above-mentioned one SDU is any SDU, or a specific SDU. If the first information is associated with the synchronous transmission of multiple SDUs, the synchronous transmission of multiple SDUs can be understood as the synchronous transmission between multiple SDUs. Of course, in an embodiment of the present application, the synchronous transmission of multiple SDUs can also be understood as the synchronous transmission between multiple SDUs and other SDUs. Among them, other SDUs can be understood as SDUs other than the SDU associated with the first information, and / or, other SDUs can be SDUs with synchronization requirements.

[0090] In other implementations, if the first information is associated with the coordinated transmission of an SDU, the coordinated transmission associated with an SDU can be understood as the coordinated transmission between the SDU and other SDUs. Optionally, the above-mentioned one SDU is any SDU, or a specific SDU. If the first information is associated with the coordinated transmission of multiple SDUs, the coordinated transmission of multiple SDUs can be understood as the coordinated transmission between multiple SDUs. Of course, in the embodiment of the present application, the coordinated transmission of multiple SDUs can also be understood as the coordinated transmission between multiple SDUs and other SDUs. Among them, other SDUs can be understood as SDUs other than the SDU associated with the first information, and / or, other SDUs can be SDUs with coordination requirements.

[0091] If the object is data, in some implementations, if the first information is associated with the synchronous transmission of one data, the synchronous transmission of one data can be understood as the synchronous transmission between the data and other data. Optionally, the above-mentioned one data is any data, or specific data. If the first information is associated with the synchronous transmission of multiple data, the synchronous transmission of multiple data can be understood as the synchronous transmission between multiple data. Of course, in an embodiment of the present application, the synchronous transmission of multiple data can also be understood as the synchronous transmission between multiple data and other data. Among them, other data can be understood as data other than the data associated with the first information, and / or, other data can be data with synchronization requirements.

[0092] In other implementations, if the first information is associated with the coordinated transmission of one data, the coordinated transmission of one data association can be understood as the coordinated transmission between the data and other data. Optionally, the above-mentioned one data is any data, or specific data. If the first information is associated with the coordinated transmission of multiple data, the coordinated transmission of multiple data can be understood as the coordinated transmission between multiple data. Of course, in an embodiment of the present application, the coordinated transmission of multiple data can also be understood as the coordinated transmission between multiple data and other data. Among them, other data can be understood as data other than the data associated with the first information, and / or, other data can be data with collaborative requirements.

[0093] If the object is a data burst, in some implementations, if the first information is associated with the synchronous transmission of a data burst, the synchronous transmission of a data burst can be understood as the synchronous transmission between the data burst and other data bursts. Optionally, the above-mentioned data burst is any data burst, or a specific data burst. If the first information is associated with the synchronous transmission of multiple data bursts, the synchronous transmission of multiple data bursts can be understood as the synchronous transmission between multiple data bursts. Of course, in the embodiment of the present application, the synchronous transmission of multiple data bursts can also be understood as the synchronous transmission between multiple data bursts and other data bursts. Among them, other data bursts can be understood as data bursts other than the data bursts associated with the first information, and / or, other data bursts can be data bursts with synchronization requirements.

[0094] In other implementations, if the first information is associated with the coordinated transmission of a data burst, the coordinated transmission associated with a data burst can be understood as the coordinated transmission between the data burst and other data bursts. Optionally, the above-mentioned data burst is any data burst, or a specific data burst. If the first information is associated with the coordinated transmission of multiple data bursts, the coordinated transmission of multiple data bursts can be understood as the coordinated transmission between multiple data bursts. Of course, in the embodiment of the present application, the coordinated transmission of multiple data bursts can also be understood as the coordinated transmission between multiple data bursts and other data bursts. Among them, other data bursts can be understood as data bursts other than the data bursts associated with the first information, and / or, other data bursts can be data bursts with coordination requirements.

[0095] The above introduces the objects in the embodiments of the present application, and the following introduces the first information involved in the embodiments of the present application.

[0096] In some implementations, the first information is used to indicate one or more of the following: the existence of a synchronous transmission requirement or a collaborative transmission requirement for at least one object; the synchronous transmission parameters or collaborative transmission parameters of at least one object; the identifier corresponding to at least one object; the type corresponding to at least one object; whether at least one object corresponds to a target identifier; whether at least one object corresponds to a target type; the synchronous transmission requirement or collaborative transmission requirement between at least two objects; the synchronous transmission parameters or collaborative transmission parameters between at least two objects; the need to perform synchronous transmission or collaborative transmission between at least two objects; whether at least two objects correspond to the same identifier; whether at least two objects correspond to the same type; whether at least two objects correspond to the target identifier; whether at least two objects correspond to the target type; the association relationship between at least two objects; the binding relationship between at least two objects.

[0097] If the first information is used to indicate that at least one object has a synchronous transmission requirement or a cooperative transmission requirement, alternatively, the first information is used to indicate that one or more objects need to be synchronously transmitted or cooperatively transmitted.

[0098] If the first information is used to indicate the synchronization transmission parameters or cooperative transmission parameters of at least one object, it can be understood that the first information carries the above parameters, or the first information carries the indication information of the above parameters (for example, the index corresponding to the parameter). In the embodiment of the present application, the above parameters are not limited. For example, the parameters may include one or more of transmission delay, sending time, arrival time, processing time, decoding time, encoding time, and delivery time.

[0099] If the first information is used to indicate an identifier corresponding to at least one object, the identifier is not limited in the embodiments of the present application. For example, if the object is a terminal device, the identifier may be a terminal device identifier. For another example, if the object is a QoS flow, the identifier may be a QoS flow identifier (QFI). For another example, if the object is data, the identifier may be a data identifier. For another example, if the object is a PDU session, the identifier may be a PDU session identifier. For another example, if the object is a bearer, the identifier may be a bearer identifier. For another example, if the object is a data flow, the identifier may be a data flow identifier.

[0100] If the first information is used to indicate a flag corresponding to at least one object, the flag is not limited in the embodiments of the present application. For example, if the object is a terminal device, the flag may be an indication / flag of whether the terminal device supports coordinated or synchronous transmission, or the flag may be used to identify the type of coordinated or synchronous transmission supported by the terminal device, or the flag may be used to identify whether the terminal device has the capability to support coordinated or synchronous transmission.

[0101] If the first information is used to indicate the type corresponding to at least one object, in some implementations, the type may be a service type. For example, the first information may be used to indicate that the type of the at least one object is an XR service or a CG service. In other implementations, the type may include a synchronous transmission type and / or a coordinated transmission type. For example, the first information may be used to indicate that the type of the at least one object is a synchronous transmission service or a coordinated transmission service.

[0102] If the first information is used to indicate whether at least one object corresponds to a target identifier (also called a "specific identifier"), the target identifier can be used to identify objects that require synchronous transmission or collaborative transmission, or in other words, the target identifier is used to identify objects to be synchronously transmitted or collaboratively transmitted.

[0103] In the embodiments of the present application, the method for generating the target identifier is not limited. For example, the target identifier may be predefined by a protocol. For another example, the target identifier may be configured by a network device. For another example, the target identifier may be preconfigured. For another example, the target identifier may be written to a SIM card, or for another example, the target identifier may be stored on a SIM card.

[0104] If the first information is used to indicate whether at least one object corresponds to a target type, the target type can be used to identify a class of objects requiring synchronous transmission or collaborative transmission, or in other words, the target type is the type of object to be synchronously transmitted or collaboratively transmitted.

[0105] If the first information is used to indicate the requirement for synchronous transmission or collaborative transmission between at least two objects, it can be replaced by the first information being used to indicate the need for synchronous transmission or collaborative transmission between at least two objects, or in other words, the first information is used to indicate synchronous transmission or collaborative transmission between at least two objects.

[0106] If the first information is used to indicate a synchronous transmission parameter or a coordinated transmission parameter between at least two objects, it can be understood that the first information carries the above parameters, or the first information carries indication information of the above parameters (for example, an index corresponding to the parameter). In the embodiment of the present application, the above parameters are not limited. For example, the parameters may include transmission delay, sending time, arrival time, processing time, decoding time, encoding time, delivery time, etc.

[0107] If the first information is used to indicate whether the at least two objects correspond to the same identifier, if the at least two objects correspond to the same identifier, then synchronous transmission or coordinated transmission needs to be performed between the at least two objects. Conversely, if the at least two objects correspond to different identifiers, then synchronous transmission or coordinated transmission does not need to be performed between the at least two objects.

[0108] In the embodiment of the present application, the identifier is not limited. For example, the identifier can be used to identify objects that need to be synchronously transmitted or collaboratively transmitted. For another example, the identifier can be used to identify the service type (for example, XR service) corresponding to synchronous transmission or collaborative transmission of at least two objects. For another example, the identifier can be used to identify that at least two objects correspond to a type (or class) of synchronous transmission or collaborative transmission. For another example, the identifier can be used to indicate that at least two objects need or perform synchronous transmission or collaborative transmission.

[0109] If the first information is used to indicate whether the at least two objects correspond to the same flag, if the at least two objects correspond to the same flag, then synchronous transmission or coordinated transmission needs to be performed between the at least two objects, or the synchronous transmission or coordinated transmission corresponding to the flag needs to be performed. Conversely, if the at least two objects correspond to different flags, then synchronous transmission or coordinated transmission does not need to be performed between the at least two objects, or the synchronous transmission or coordinated transmission corresponding to the flag does not need to be performed between the at least two objects.

[0110] In the embodiment of the present application, the flag is not limited. For example, the flag can be used to identify a flag that requires synchronous transmission or collaborative transmission. For another example, the flag can be used to identify the service type (for example, XR service) corresponding to synchronous transmission or collaborative transmission of at least two objects. For another example, the flag can be used to identify that at least two objects correspond to one or a class of synchronous transmission or collaborative transmission. For another example, the flag can be used to indicate that at least two objects need or perform synchronous transmission or collaborative transmission. For another example, the flag can be used to identify which type of synchronous transmission or collaborative transmission corresponds to at least two objects.

[0111] In the case where the first information is used to indicate whether the at least two objects correspond to the same type, if the at least two objects correspond to the same type, synchronous transmission or coordinated transmission needs to be performed between the at least two objects. Conversely, if the at least two objects correspond to different types, synchronous transmission or coordinated transmission does not need to be performed between the at least two objects.

[0112] In the embodiments of the present application, the type is not limited. For example, the type may be the type of the object that needs to be transmitted synchronously or collaboratively. For another example, the type may be a service type (e.g., XR service) corresponding to synchronous transmission or collaborative transmission of at least two objects. For another example, the type may be a transmission type corresponding to synchronous transmission or collaborative transmission of at least two objects.

[0113] If the first information is used to indicate whether at least two objects correspond to a target identifier, the target identifier can be used to identify an object with a synchronous transmission requirement or a cooperative transmission requirement, or in other words, the target identifier is used to identify an object to be subjected to synchronous transmission or cooperative transmission. It should be understood that the introduction to the target identifier can be found above and will not be repeated here for the sake of brevity.

[0114] If the first information is used to indicate whether the at least two objects correspond to a target type, the target type may be a type requiring synchronous transmission or collaborative transmission, or in other words, the target type is a type of object to be synchronously transmitted or collaboratively transmitted. It should be understood that the introduction to target identification can be found above and will not be repeated here for the sake of brevity.

[0115] If the first information is used to indicate an association relationship between at least two objects, the association relationship is used to indicate that there is a synchronous transmission requirement or a collaborative transmission requirement between the at least two objects. In some scenarios, the above association relationship can be replaced by a binding relationship, that is, the binding relationship is used to indicate that there is a synchronous transmission requirement or a collaborative transmission requirement between the at least two objects.

[0116] In an embodiment of the present application, when the at least one object is a plurality of objects, the at least two objects may be at least two objects among the plurality of objects.

[0117] In some implementations, the first information includes identification information, which includes one or more of the following: identification information of the target object; identification information of the first object in at least one object; identification information of each object in at least one object; identification information of at least two objects.

[0118] In some implementations, the identification information may include identification information of a target object, where the target object may be part or all of the at least one object.

[0119] In some implementations, the identification information may include identification information of a first object in the at least one object, where the first object may be a certain object in the at least one object, or in other words, the first object may be a specific object in the at least one object. Of course, in embodiments of the present application, the identification information may include identification information of each object in the at least one object.

[0120] In some implementations, the identification information may include identification information of a first object among at least one object, wherein the identification information of the first object is identification information corresponding to the current object, or identification information corresponding to an object having a synchronization or collaborative transmission association with the current object.

[0121] In some implementations, the identification information may include identification information of at least two objects, or in other words, the identification information is used to identify at least two objects. Wherein, when the at least one object includes multiple objects, the at least two objects belong to the multiple objects.

[0122] In some implementations, the identification information may include identification information of at least two objects. The identification information of the at least two objects is identification information of objects associated with collaborative or synchronous transmission, or the identification information of the at least two objects is identification information corresponding to objects associated with synchronous or collaborative transmission, including the current object, or the corresponding identification information of objects associated with synchronous or collaborative transmission with the current object.

[0123] In the embodiments of the present application, there is no limitation on the manner in which the second device obtains the first information. In some implementations, the first information may be sent from the first protocol layer of the second device to the second protocol layer, where the first protocol layer is located above the second protocol layer. For another example, the first information may be sent from the first protocol layer of the second device to the second protocol layer, with the first information carried in the header or payload of the data packet. For another example, the first information may be transmitted by the inter-layer interaction information between the first protocol layer of the second device and the second protocol layer. In other implementations, the first information may be sent from the core network device to the second device. For example, the core network device may carry the first information by sending a NAS message to the second device. Of course, in the embodiments of the present application, the process by which the second device obtains the first information may also be specified based on the internal implementation of the second device. Optionally, the second device may obtain the first information based on auxiliary information provided by the core network device.

[0124] The above introduces the first information in the embodiment of the present application, and the following introduces the triggering method of the first information in the embodiment of the present application.

[0125] In some implementations, the first information is triggered based on one or more of: a period; a first event; a request from the first device; an enable indication; a capability of the second device, the capability being associated with the first information; whether the first device obtains the first information; whether the second device has available or valid first information.

[0126] If the first information is triggered based on whether the second device has available or valid first information, in the embodiments of the present application, the method for determining whether the first information is available or valid is not limited. For example, whether the first information is available or valid can be determined based on the implementation of the second device. For another example, whether the first information is available or valid can be determined based on a preset rule.

[0127] If the first information is triggered based on a period, that is, the first information is sent periodically, wherein the period may be configured by the network device, or the period may be predefined, or the period may be preconfigured, and this embodiment of the present application does not limit this.

[0128] If the first information is triggered based on the first event, in some implementations, the first event includes one or more of the following: exceeding the first time duration; the second device is configured to send the first information of at least one object; the first information of at least one object has not been sent; the demand for synchronous transmission or the demand for coordinated transmission of at least one object changes; the parameters of synchronous transmission or the parameters of coordinated transmission of at least one object change; the identifier of synchronous transmission or the type of synchronous transmission of at least one object changes; the coordinated transmission identifier or the coordinated transmission type of at least one object changes; the identifier of synchronous transmission or the type of synchronous transmission between at least two objects changes; the coordinated transmission identifier or the coordinated transmission type between at least two objects changes; the demand for synchronous transmission or the demand for coordinated transmission between at least two objects changes; at least two pairs The parameters of synchronous transmission or collaborative transmission between objects change; the change in the demand for synchronous transmission of at least one object is greater than or equal to the first change threshold; the change in the demand for collaborative transmission of at least one object is greater than or equal to the second change threshold; the change in the parameter for synchronous transmission of at least one object is greater than or equal to the third change threshold; the change in the parameter for collaborative transmission of at least one object is greater than or equal to the fourth change threshold; the change in the parameter for synchronous transmission between at least two objects is greater than or equal to the fifth change threshold; the change in the parameter for collaborative transmission between at least two objects is greater than or equal to the sixth change threshold; the change in the demand for synchronous transmission between at least two objects is greater than or equal to the seventh change threshold; the change in the demand for collaborative transmission between at least two objects is greater than or equal to the eighth change threshold.

[0129] In some implementations, the first event may include exceeding a first duration, or in other words, the first event includes not being within the first duration. The first duration is a duration during which the transmission of the first information is prohibited or not allowed, or in other words, a duration during which the first information is not transmitted. Accordingly, the first event may be replaced by not transmitting information associated with the synchronous transmission or cooperative transmission of at least one object for exceeding the first duration.

[0130] In an embodiment of the present application, the first duration can be associated with at least one object, that is, the configuration granularity and / or usage granularity of the first duration can be one of the at least one objects, wherein the usage granularity can be understood as the object for which the first duration is used.

[0131] In the embodiment of the present application, the configuration granularity of the first duration can be understood as configuring the first duration for each object in at least one object, or configuring the first duration for at least one object as a whole.

[0132] In the embodiment of the present application, the usage granularity of the first duration can be understood as using the first duration for each object in the at least one object, or using the first duration for the at least one object as a whole.

[0133] In addition, in an embodiment of the present application, the configuration granularity of the first duration and the usage granularity of the first duration can be the same, that is, the object associated with the configuration and the object targeted by the use of the first duration are the same, which helps to simplify the complexity of configuring and using the first duration. Alternatively, the configuration granularity of the first duration and the usage granularity of the first duration can be different, that is, the object associated with the configuration and the object targeted by the use of the first duration are different, which helps to increase the flexibility of configuring and using the first duration.

[0134] In some implementations, the first duration may be determined based on a first timer. Accordingly, the first event includes the first timer timing out and / or the first timer not running.

[0135] In the embodiment of the present application, the first duration is determined based on the first timer, which can be understood as the first duration being maintained by the first timer, or in other words, the first duration being recorded by the first timer.

[0136] In some implementations, the first timer is started or restarted when the first information is sent, or in other words, the start or restart of the first timer is triggered by the first information, or in other words, the start or restart of the first timer is triggered by the sending of the first information.

[0137] In some implementations, the fact that the first timer is not running can be understood as information (ie, first information) for synchronous transmission or cooperative transmission of at least one object is not sent, and therefore, the first timer is not running.

[0138] In some implementations, the expiration of the first timer may be understood as the duration of the prohibition (or non-permission) of transmission of the first information. At this time, the second device may resend the first information.

[0139] In some implementations, the first device and the second device may each maintain a first timer. In this case, the second device may determine the time to send the first information based on the first timer, and the first device may determine the time to receive the first information based on the first timer. This unifies the first and second devices' understanding of the transmission process of the first information, thereby helping to improve the success rate of the transmission of the first information. Of course, in the embodiment of the present application, one of the first and second devices maintains the first timer.

[0140] In some implementations, the first timer may be configured by the network device, or the first timer may be predefined by a protocol. Of course, in the embodiment of the present application, the first timer may be preconfigured.

[0141] In some implementations, the first event may include that the second device is configured to send first information of at least one object, that is, the first event may include that the second device is configured to report first information of at least one object.

[0142] In some implementations, the first event may include that the first information of the at least one object has not been sent, that is, the second device has not reported the first information of the at least one object.

[0143] In some implementations, the first event may include a change in the synchronous transmission requirement or cooperative transmission requirement of at least one object. If the synchronous transmission requirement changes, the change in the synchronous transmission requirement of at least one object may include one or more of the following: at least one object no longer requires synchronous transmission; a change in the synchronous transmission parameters of at least one object; a change in another object that synchronizes with the at least one object; or a change in the synchronous transmission parameters of another object that synchronizes with the at least one object. Changes in synchronous transmission parameters are described below.

[0144] If the coordinated transmission requirement of at least one object changes, the change in the coordinated transmission requirement of at least one object may include one or more of the following: at least one object no longer requires coordinated transmission; the coordinated transmission parameters of at least one object change; other objects that coordinate transmission with the at least one object change; or other objects that coordinate transmission with the at least one object change. Changes in coordinated transmission parameters are described below.

[0145] In some implementations, the first event may include a change in a parameter of synchronous transmission or a parameter of coordinated transmission of at least one object. If the synchronous transmission parameter includes a delay, the first event occurs if the delay of at least one object changes from 5 seconds to 6 seconds. If the coordinated transmission parameter includes a delay, assuming that before the coordinated transmission parameter changes, the coordinated transmission parameter of at least one object indicates that the at least one object should be transmitted within 5 seconds, and then the coordinated transmission parameter of at least one object changes to indicate that the at least one object should be transmitted within 6 seconds, the first event occurs.

[0146] In some implementations, the first event may include a change in a parameter of synchronous transmission or a parameter of cooperative transmission of at least one object. If the synchronous transmission parameter includes a delay, the first event occurs if the delay of an object in the at least one object changes from 5 seconds to 6 seconds.

[0147] In some implementations, the first event may include a change in a parameter of synchronous transmission or cooperative transmission of at least one object, where the change is greater than a threshold. If the synchronous transmission parameter includes latency, the first event occurs if the latency of at least one object changes from 5 seconds to 8 seconds, and the first change threshold is 2.

[0148] In some implementations, the first event may include a change in a parameter of synchronous transmission or a parameter of cooperative transmission of at least one object and a timeout of a first timer, wherein the first timer may be a first timer for the at least one object, or the first timer may be a first timer for one of the at least one objects. If the synchronous transmission parameter includes a delay, the first event occurs if the delay of an object changes from 5 seconds to 8 seconds and the first timer of the object times out.

[0149] In some implementations, the first event may include a change in a parameter of synchronous transmission or cooperative transmission of at least one object, where the change is greater than a threshold, and a first timer expires, wherein the first timer may be a first timer for the at least one object, or the first timer may be a first timer for one of the at least one objects. If the synchronous transmission parameter includes a delay, the first event occurs if the delay of a certain object changes from 5 seconds to 8 seconds, the first change threshold is 2, and the first timer of the object expires.

[0150] In some implementations, the first event may include a change in the identifier of the synchronous transmission of at least one object or the type of synchronous transmission. If the identifier of the synchronous transmission changes, it can be understood that the synchronous transmission requirement and / or synchronous transmission parameters of the at least one object have changed. If the synchronous transmission requirement changes, such as when at least one object changes from requiring synchronous transmission to not requiring synchronous transmission, the first event occurs. If the type of synchronous transmission changes, such as when at least one object changes from type 1 to type 2, the first event occurs.

[0151] In some implementations, the first event may include a change in the identifier of the coordinated transmission of at least one object or a change in the type of coordinated transmission. A change in the identifier of the coordinated transmission can be understood as a change in the coordinated transmission requirement and / or coordinated transmission parameters of at least one object. If the coordinated transmission requirement changes, such as when at least one object changes from requiring coordinated transmission to not requiring coordinated transmission, the first event occurs. If the type of coordinated transmission changes, such as when at least one object changes from type 1 to type 2, the first event occurs.

[0152] In some implementations, the first event may include a change in an identifier of a synchronous transmission between at least two objects or a change in the type of synchronous transmission. If the identifier of the synchronous transmission changes, it can be understood that the requirement for synchronous transmission between at least two objects and / or the parameters of the synchronous transmission have changed. If the requirement for synchronous transmission changes, such as when the requirement for synchronous transmission between at least two objects changes from existing to not existing, the first event occurs. If the type of synchronous transmission changes, such as when the type of synchronous transmission between at least two objects changes from type 1 to type 2, the first event occurs.

[0153] In some implementations, the first event may include a change in an identifier of a coordinated transmission between at least two objects or a change in the type of coordinated transmission. If the identifier of a coordinated transmission changes, it can be understood that the coordinated transmission requirement and / or coordinated transmission parameters between at least two objects have changed. If the coordinated transmission requirement changes, such as when the requirement for coordinated transmission between at least two objects changes from existing to not existing, the first event occurs. If the type of coordinated transmission changes, such as when the type of coordinated transmission between at least two objects changes from type 1 to type 2, the first event occurs.

[0154] In some implementations, the first event may include a change in a synchronization transmission requirement or a coordinated transmission requirement between at least two objects. If the synchronization transmission requirement between at least two objects changes, such that the synchronization transmission requirement between at least two objects changes from synchronization transmission requirement 1 to synchronization transmission requirement 2, the first event occurs. If the coordinated transmission requirement between at least two objects changes, such that the coordinated transmission requirement between at least two objects changes from coordinated transmission requirement 1 to coordinated transmission requirement 2, the first event occurs.

[0155] If the synchronization transmission requirement between at least two objects changes from object 1 and object 2 to object 2 and object 3, a first event occurs. If the coordination transmission requirement between at least two objects changes from object 1 and object 2 to object 2 and object 3, a first event occurs.

[0156] In some implementations, the first event may include a change in the demand for synchronous transmission or collaborative transmission between at least two objects, and a first timer expiration, wherein the first timer may be a first timer for at least two objects, or the first timer may be a first timer for one of the at least two objects.

[0157] In some implementations, the first event may include a change in a parameter for synchronous transmission or a parameter for collaborative transmission between at least two objects. If the parameter for synchronous transmission between at least two objects changes from parameter 1 to parameter 2, the first event occurs. If the parameter for collaborative transmission between at least two objects changes from parameter 1 to parameter 2, the first event occurs.

[0158] In some implementations, the first event may include a change in a parameter of synchronous transmission or a parameter of collaborative transmission between at least two objects, and a first timer expiration, wherein the first timer may be a first timer for the at least two objects, or the first timer may be a first timer for one of the at least two objects.

[0159] In some implementations, the first event includes a change in the requirement for synchronous transmission or collaborative transmission of at least one object, the amount of which is greater than or equal to a change threshold. If at least one object requires synchronous transmission, if the synchronous transmission requirement of at least one object changes from requirement 1 to requirement 2, and the amount of change between requirements 1 and 2 is greater than or equal to the change threshold, the first event occurs. If at least one object requires collaborative transmission, if the collaborative transmission requirement of at least one object changes from requirement 1 to requirement 2, and the amount of change between requirements 1 and 2 is greater than or equal to the change threshold, the first event occurs.

[0160] In some implementations, the first event includes a change in a parameter of at least one object for synchronous transmission or a parameter for collaborative transmission, the amount of which is greater than or equal to a change threshold. If at least one object is a parameter for synchronous transmission, the first event may include a change in a parameter of at least one object for synchronous transmission from parameter 1 to parameter 2, and the amount of change between parameter 1 and parameter 2 is greater than or equal to the change threshold. If at least one object is a parameter for collaborative transmission, the first event may include a change in a parameter of at least one object for collaborative transmission from parameter 1 to parameter 2, and the amount of change between parameter 1 and parameter 2 is greater than or equal to the change threshold.

[0161] In some implementations, the first event includes a change in a parameter of synchronous transmission or a parameter of collaborative transmission of at least one object, the change amount of which is greater than or equal to a change threshold, and a first timer times out, wherein the first timer may be a first timer for at least one object, or the first timer may be a first timer for one of the at least one objects.

[0162] In some implementations, the first event includes a change in a parameter for synchronous transmission or a parameter for collaborative transmission between at least two objects, the amount of which is greater than or equal to a change threshold. In the case where the change in the parameter for synchronous transmission between at least two objects is greater than or equal to the change threshold, if the parameter for synchronous transmission between at least two objects is changed from parameter 1 to parameter 2, and the amount of change between parameter 1 and parameter 2 is greater than or equal to the change threshold, the first event occurs. In the case where the change in the parameter for collaborative transmission between at least two objects is greater than or equal to the change threshold, if the parameter for collaborative transmission between at least two objects is changed from parameter 1 to parameter 2, and the amount of change between parameter 1 and parameter 2 is greater than or equal to the change threshold, the first event occurs.

[0163] In some implementations, the first event includes a change in a parameter of synchronous transmission or a parameter of collaborative transmission between at least two objects, the change amount of which is greater than or equal to a change threshold, and a first timer times out, wherein the first timer may be a first timer for at least two objects, or the first timer may be a first timer for one of the at least two objects.

[0164] In some implementations, the first event includes a change in the demand for synchronous transmission or the demand for collaborative transmission between at least two objects, the amount of which is greater than or equal to a change threshold. In the case where the change in the demand for synchronous transmission between at least two objects is greater than or equal to the change threshold, if the demand for synchronous transmission between at least two objects changes from demand 1 to demand 2, and the amount of change between demand 1 and demand 2 is greater than or equal to the change threshold, the first event occurs. In the case where the change in the demand for collaborative transmission between at least two objects is greater than or equal to the change threshold, if the demand for collaborative transmission between at least two objects changes from demand 1 to demand 2, and the amount of change between demand 1 and demand 2 is greater than or equal to the change threshold, the first event occurs.

[0165] In the embodiments of the present application, there is no limitation on the manner in which the above-mentioned change threshold is set. For example, the change threshold may be configured by a network device. For another example, the change threshold may be predefined by a protocol. For another example, the change threshold may be preconfigured.

[0166] Based on the above introduction to the first event, it can be seen that in some scenarios, the first event may be related to at least one object as a whole, for example, the parameters of the collaborative transmission (or the parameters of the synchronous transmission) of the at least one object introduced above change. For another example, the demand for collaborative transmission (or the demand for synchronous transmission) of the at least one object introduced above changes. In other scenarios, the first event may be related to a certain object in at least one object, for example, the parameters of the collaborative transmission (or the parameters of the synchronous transmission) of a certain object in at least one object introduced above change. For another example, the demand for collaborative transmission (or the demand for synchronous transmission) of a certain object in at least one object introduced above changes.

[0167] In addition, in an embodiment of the present application, the above-mentioned first events can be used independently of each other. Of course, in an embodiment of the present application, the first events can be used in combination with each other. For example, the first event may include that the second device is configured to send the first information of at least one object, and the second device has not yet sent the first information of at least one object. Of course, in an embodiment of the present application, the first event may also include other content. For example, the first event may include that before sending the first information, the second device has not indicated at least one object for synchronous transmission or collaborative transmission. For another example, the first event may include that before sending the first information, the second device has not indicated information associated with synchronous transmission or collaborative transmission of at least one object.

[0168] In addition, some or all of the change thresholds from the first change threshold to the eighth change threshold mentioned above may be different. Of course, in the embodiment of the present application, the first change threshold to the eighth change threshold may be completely the same.

[0169] If the first information is triggered based on a request message sent by the first device, that is, before the above step S210, the first device sends a request message to the second device, and the request message is used to request the first information.

[0170] In some implementations, the request message is used to request one or more of the following: a requirement for synchronous transmission or collaborative transmission of a target object; parameters for synchronous transmission or collaborative transmission of a target object; an identifier or type of the target object; a requirement for synchronous transmission or collaborative transmission between at least two objects, where, if at least one object includes multiple objects, the multiple objects include at least two objects; parameters for synchronous transmission or collaborative transmission between at least two objects.

[0171] In some implementations, the request message is used to request a target object to perform synchronous transmission or cooperative transmission, wherein the target object includes all or part of at least one object. If the target object includes all objects in the at least one object, the request message can be understood as being used to request the at least one object. If the target object includes part of the at least one object, the request message can be understood as being used to request a specific object in the at least one object. Accordingly, the second device can send first information associated with the synchronous transmission or cooperative transmission of the at least one object to the first device.

[0172] In some implementations, the request message is used to request parameters for synchronous transmission or collaborative transmission of the target object, wherein the target object includes parameters for synchronous transmission or collaborative transmission of all or part of the objects in at least one object. If the target object includes all objects in at least one object, the request message can be understood as a parameter for requesting all or part of the objects in at least one object to be synchronously transmitted or collaboratively transmitted. If the target object includes some objects in at least one object, the request message can be understood as a parameter for requesting a specific object in at least one object to be synchronously transmitted or collaboratively transmitted, and accordingly, the second device can send first information associated with synchronous transmission or collaborative transmission of at least one object to the first device, wherein at least one object can be understood as an object that is synchronously transmitted or collaboratively transmitted with the target object.

[0173] In some implementations, the request message includes at least one of the following information: identification information of the object requested by the request message; a first duration associated with the first information; a reporting period of the first information; a change threshold of the requirement for synchronous transmission or the requirement for collaborative transmission, a change threshold of the parameters of synchronous transmission or the parameters of collaborative transmission; a first timer configuration, and the content of the request message.

[0174] In some implementations, the request message may include identification information of the requested object, wherein the identification of the requested object may be the identification of the target object. If the target object is at least one object, the identification of the requested object may be the identification of the at least one object.

[0175] In some implementations, the request message may include a first duration associated with the first information, wherein the introduction to the first duration can be found above.

[0176] In this scenario, the request message including the first duration can be understood as the first device configuring the first duration for the second device via the request message. In other words, the request message carries the configuration information for the first duration, which helps to simplify the process of configuring the first duration. Of course, in the embodiment of the present application, the configuration information for the first duration can also be transmitted separately without being carried in the request message.

[0177] In some implementations, the request message may include the reporting period of the first information, or in other words, the request message is used to configure the transmission period of the first information for the second device, which helps to simplify the process of configuring the transmission of the first information. Of course, in the embodiment of the present application, the configuration information for configuring the transmission period of the first information may also be transmitted separately without being carried in the request message.

[0178] In some implementations, the request message may include a change threshold for the requirement for synchronous transmission or the requirement for collaborative transmission, wherein the change threshold may be the change threshold involved in the first event described above. For details, please refer to the above description.

[0179] In some implementations, the request message may include a change threshold for parameters of synchronous transmission or collaborative transmission, wherein the change threshold may be the change threshold involved in the first event described above. For details, please refer to the above introduction.

[0180] In some implementations, the above-mentioned request message may include the content of the request message, wherein the content of the request message may include one or more of the following: an identifier corresponding to at least one object, a type of synchronous transmission or collaborative transmission of at least one object, a parameter for synchronous transmission or collaborative transmission of at least one object, and a requirement for synchronous transmission or collaborative transmission of at least one object.

[0181] In the embodiments of the present application, there is no limitation on the transmission method of the request message. For example, the request message can be carried in one or more of the following: system information, paging message, RRC message, uplink control information (UCI), downlink medium access control element (MAC CE) (such as (downlink MAC CE)), non-access stratum (NAS) message, and other configuration (otherconfig).

[0182] In some implementations, the first information may be triggered based on an enable indication, and thus the enable indication may also be referred to as a trigger indication. The enable indication is used to enable the second device to send the first information, or in other words, the trigger indication is used to trigger the second device to send the first information.

[0183] In the embodiment of the present application, there is no limitation on the device that sends the enable indication. For example, the enable indication can be triggered by an access network device, or the enable indication can be triggered by a core network device.

[0184] In some implementations, the first information may be triggered based on a capability of the second device, where the capability of the second device is associated with simultaneous transmission or coordinated transmission of at least one object. For example, the capability of the second device may be used to indicate whether the second device has the capability of simultaneous transmission or coordinated transmission for at least one object.

[0185] Accordingly, the first information is triggered based on the capability of the second device, which means that if the second device has the capability, the second device can trigger the first information. Conversely, if the second device does not have the capability, the second device may not trigger the first information.

[0186] In some implementations, the first information may be triggered based on whether the first device obtains the first information. For example, if the first device obtains the first information, the first device may trigger the first information. Conversely, if the first device does not obtain the first information, the first device may not trigger the first information.

[0187] In some implementations, whether the first device obtains the first information may include whether the first protocol layer of the first device transmits the first information to the second protocol layer of the first device, where the first protocol layer is located above the second protocol layer. That is, if the first protocol layer transmits the first information to the second protocol layer, the first device obtains the first information, and in this case, the first device may trigger the first information. Conversely, if the first protocol layer does not transmit the first information to the second protocol layer, the first device does not obtain the first information, and in this case, the first device may not trigger the first information.

[0188] In the embodiment of the present application, there is no limitation on the interaction mode of the first information between the first protocol layer and the second protocol layer. For example, the first information can be encapsulated in a packet header.

[0189] In other implementations, whether the first device obtains the first information may include whether the core network device sends the first information to the first device. That is, if the core network device sends the first information to the first device, the first device obtains the first information, and in this case, the first device may trigger the first information. Conversely, if the core network device does not send the first information to the first device, the first device does not obtain the first information, and in this case, the first device may not trigger the first information.

[0190] In the embodiment of the present application, there is no limitation on the interaction mode of the first information between the core network device and the first device. For example, the first information can be encapsulated in a NAS message.

[0191] In some implementations, the first information may be triggered based on whether the first device has available or valid first information. Alternatively, the triggering of the first information may be determined based on whether the first device has available or valid first information. For example, if the first device has available or valid first information, the second device may not trigger the first information to reduce the overhead of transmitting the first information. For another example, if the first device does not have available or valid first information, the second device may trigger the first information.

[0192] In an embodiment of the present application, the first device may inform the second device whether the first device has available or valid first information. For example, if the first device does not have available or valid first information, the first device may send an indication message to the second device to indicate that the first device does not have available or valid first information. For another example, if the first device has available or valid first information, the first device may send an indication message to the second device to indicate that the first device has available or valid first information. Of course, in an embodiment of the present application, the indication message may be sent only when the first device does not have available or valid first information, and the indication message may not be sent when the first device has available or valid first information. Alternatively, the indication message may be sent only when the first device has available or valid first information, and the indication message may not be sent when the first device does not have available or valid first information.

[0193] The above describes the triggering method of the first information in the embodiment of the present application. The following describes the transmission method of the first information in the embodiment of the present application in combination with transmission method 1 and transmission method 2.

[0194] Transmission mode 1: the first information is carried in a control plane message, or in other words, the first information is transmitted via the control plane message.

[0195] In some implementations, the control plane information includes an RRC message. For example, the RRC message is UE assistance information (UAI), and the first information can be carried in the UAI. In other words, new UAI reporting content can be introduced to carry the first information. For example, a new IE can be introduced to carry the first information to indicate a requirement for synchronized or coordinated transmission between QoS flows.

[0196] In some other implementations, the control plane information may include a NAS message. For example, the NAS message may be an uplink information transfer (UL information transfer) message.

[0197] In some implementations, the first information is carried in sub-information of the control plane information, and the sub-information carries identification information. Of course, in embodiments of the present application, the first information can be carried in the control plane information, and the control plane information carries identification information. The identification information can be described above.

[0198] Assume that the uplink traffic information (UL-TrafficInfo) carries PDU session uplink traffic information (PDU-SessionUL-TrafficInfo), and the PDU session uplink traffic information carries QoS flow uplink traffic information element (QoS-FlowUL-TrafficInfo IE), and the above information and sub-information can carry identification information QFI, which is used to identify at least one object associated with the first information, that is, at least one QoS flow.

[0199] Accordingly, the above-mentioned carrying of the first information in the control plane information can be understood as carrying the first information in the uplink traffic information (UL-TrafficInfo). The above-mentioned carrying of the first information in the sub-information of the control plane information can be understood as carrying the first information in the PDU-SessionUL-TrafficInfo and / or QoS-FlowUL-TrafficInfo IE.

[0200] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device. The core network device may be one or more of AF, PCF, SMF, and UPF, which is not limited in this embodiment of the present application.

[0201] In an embodiment of the present application, since a terminal device generally more easily obtains the synchronous transmission requirement or cooperative transmission requirement of at least one object, the terminal device sending the first information to the network device helps to improve the accuracy of the first information. In addition, in an embodiment of the present application, if the access network device can obtain the first information, the access network device can assist in achieving the synchronous transmission or cooperative transmission of at least one object on the access network side. In addition, in an embodiment of the present application, if the core network device can obtain the first information, the core network device can assist in achieving the synchronous transmission or cooperative transmission of at least one object on the core network side.

[0202] The above describes a scheme for transmitting the first information between a terminal device and a network device (for example, a core network device or an access network device). The transmission scheme for the first information described below can be used for transmission between network devices. In some implementations, it can be applied to transmit the first information between a core network device and an access network device. For example, the first device is an access network device, and the second device is a core network device. In other implementations, both the first device and the second device can be core network devices. For example, the first information can be sent by a policy control function (PCF) or an application function (AF) to a session management function (SMF). For another example, the first information can be carried by the PCF or AF through a time sensitive communication association container (TSCAC).

[0203] In an embodiment of the present application, if the core network device can know that at least one object needs to be transmitted synchronously or collaboratively, the core network device can send first information to the access network device, which helps to reduce the increase in air interface signaling overhead caused by communication between the terminal device and the access network device.

[0204] In some implementations, the control plane information includes one or more of the following: QoS configuration information, information carrying QoS parameters, and time sensitive communication assistance information (TSCAI).

[0205] In the embodiments of the present application, the specific manner in which the first information is transmitted via the control plane information is not limited. For example, the first information may be carried in the control plane information. If the control plane information includes TSCAI, the TSCAI may carry the first information. If the control plane information includes information carrying QoS parameters, the information carrying the QoS parameters may carry the first information. If the control plane information includes QoS configuration information (QoS profile information), the QoS configuration information may carry the first information.

[0206] For another example, the first information may include the first information transmitted together with the control plane information via the control plane information. If the control plane information includes TSCAI, the first information is sent together with the TSCAI information. If the control plane information includes information carrying QoS parameters, the first information is sent together with the information carrying the QoS parameters. If the control plane information includes QoS configuration information, the first information is sent together with the QoS configuration information.

[0207] In an embodiment of the present application, since TSCAI is based on QoS flow indication, adding the first information associated with the QoS flow corresponding to TSCAI in the TSCAI information helps to make the transmission scheme of the first information compatible with the communication process of the known communication system.

[0208] Transmission mode 2: the first information is carried in user plane information, or the first information is transmitted via user plane information.

[0209] In some implementations, the user plane information includes one or more of the following: a first data packet; a service data adaptation protocol SDAP protocol data unit PDU, a PDCP PDU, a media access control element MAC CE, a MAC PDU, and uplink control information UCI, wherein the SDAP PDU may include an SDAP data PDU and an SDAP control PDU, and in addition, the SDAP control PDU may be an End-Marker Control PDU.

[0210] In some implementations, the first information is carried by a header of the user plane information, or the first information is carried by a payload of the user plane information.

[0211] In some implementations, in order to reduce the complexity of the first device receiving the user plane information, the second information can be carried in the user plane information, wherein the second information is used to indicate that the user plane information carries the first information, or the second information is used to indicate that the user plane information carries the first information, or in other words, the second information is used to indicate that the user plane information is specific information carrying the first information.

[0212] For example, the user plane information may be an SDAP PDU, and the SDAP PDU may carry second information, wherein the second information is used to indicate that the SDAP PDU is a PDU carrying the first information.

[0213] For another example, the user plane information may be a PDCP PDU, and the PDCP PDU may carry second information, wherein the second information is used to indicate that the PDCP PDU is a PDU carrying the first information.

[0214] In the embodiment of the present application, there is no limitation on the manner in which the second information is carried in the user plane information. In some implementations, the second information may be carried in the packet header. In other implementations, the second information may be carried in the payload.

[0215] In some implementations, the second information may be a PDU type to indicate whether the SDAP PDU carries the first information. For example, if the PDU type is 00, it may indicate that the SDAP PDU carries the first information. For another example, if the PDU type is 11, it may indicate that the SDAP PDU does not carry the first information. This will be described below in conjunction with Figure 5.

[0216] In the embodiment of the present application, the number of bits occupied by the second information is not limited. For example, the second information may occupy only one bit. For another example, the second information may occupy multiple bits.

[0217] In some implementations, the at least one object includes at least one QoS flow, and the SDAP PDU includes a first field, which is used to carry one or more of the following: an identifier or type of at least one QoS flow; an indication of whether the QoS flow corresponding to the first field is the QoS flow associated with the first information; a synchronous transmission requirement or a collaborative transmission requirement of at least one QoS flow; a synchronous transmission parameter or a collaborative transmission parameter of at least one QoS flow; an identifier of the QoS flow associated with the first information; an identifier of a QoS flow with a synchronous transmission requirement or a collaborative transmission requirement, and the QoS flow with a synchronous transmission requirement or a collaborative transmission requirement includes at least one QoS flow; an identifier of a QoS flow with a synchronous transmission parameter or a collaborative transmission parameter, and the QoS flow with a synchronous transmission parameter or a collaborative transmission parameter includes at least one QoS flow.

[0218] In the embodiment of the present application, the first field is not limited. For example, the first field can be a reserved field (indicated by "R") or an extended field (indicated by "E") in the SDAP PDU. In other words, for such an SDAP PDU that carries the first information in the reserved field, the first device cannot ignore the information in the reserved field. In this case, such an SDAP PDU can be understood as an SDAP PDU that is different from the traditional SDAP PDU, or in other words, the SDAP PDU that carries the first information can be understood as a newly introduced SDAP PDU.

[0219] Of course, in the embodiments of the present application, whether the first device can ignore the information in the reserved field or the extended field can also be determined based on one or more of the following conditions. For example, the condition includes that the second device supports reporting of the first information, or in other words, the second device has the ability to report the first information. In this case, if the above conditions are met, the first device cannot ignore the information in the reserved field or the extended field, which helps to increase the probability of successful transmission of the first information. For another example, the condition includes that the first device configures the second device to transmit the first information. In this case, if the above conditions are met, the first device cannot ignore the information in the reserved field or the extended field, which helps to increase the probability of successful transmission of the first information.

[0220] In some implementations, enabling the above-mentioned SDAP PDU carrying the first information may be configured by a network device. That is to say, if the network device configures the first device to use (or enable) the above-mentioned SDAP PDU, the first device may carry the first information in the reserved field of the SDAP PDU. On the contrary, if the network device configures the first device not to use (or to disable) the above-mentioned SDAP PDU, the first device may not carry the first information in the reserved field of the SDAP PDU. Of course, in an embodiment of the present application, the above-mentioned SDAP PDU that enables carrying the first information may be predefined by the protocol. For example, it may be stipulated in the protocol that the target device or the target type of device may enable the above-mentioned SDAP PDU carrying the first information. For another example, it may be stipulated in the protocol that other devices except the target device or the target type of device may not enable the above-mentioned SDAP PDU carrying the first information.

[0221] In some implementations, the target device can be understood as a device with a synchronous transmission requirement or a collaborative transmission requirement. Alternatively, the target device is a device with the capabilities described above. Alternatively, the target device can be a device of a specific version that has a synchronous transmission requirement or a collaborative transmission requirement, and / or a device with the capabilities described above. Of course, in an embodiment of the present application, the target device can also be a device to which the first information is to be transmitted (for example, to which the first information is to be reported for the first time, or for example, to which the first information is to be updated for the first device).

[0222] In some implementations, the target type of device can be understood as a type of device with a synchronous transmission requirement or a collaborative transmission requirement. Alternatively, the target type of device is a type of device with the capabilities described above. Alternatively, the target type of device can be a type of device of a specific version, a type of device of this version having a synchronous transmission requirement or a collaborative transmission requirement, and / or a device with the capabilities described above. Of course, in an embodiment of the present application, the target type of device can also be a type of device to which the first information is to be transmitted (for example, the first information is to be reported for the first time, or for example, the first information is to be updated for the first device).

[0223] In some implementations, identification information of a bearer for transmitting at least one object may be carried in an SDAP PDU. Of course, in an embodiment of the present application, the bearer for transmitting the SDAP PDU may be used to determine the bearer for transmitting at least one object. For example, the bearer for transmitting the SDAP PDU may be the bearer for transmitting at least one object. For details, please refer to the introduction of FIG. 7 . For another example, the bearer for transmitting the SDAP PDU and a mapping relationship may be used to determine the bearer for transmitting at least one object. The mapping relationship may be a mapping relationship between the bearer for transmitting the SDAP PDU and the bearer for transmitting at least one object.

[0224] In some implementations, if the first information (such as RDI=1) is carried in the SDAP data PDU, the SDAP layer of the second device (e.g., UE) can store the updated mapping relationship and send the mapping relationship to the lower layer (e.g., PDCP layer), where the mapping relationship is a mapping relationship between at least one object and a bearer.

[0225] For ease of understanding, the structure of the SDAP control PDU in the embodiment of the present application is introduced below with reference to FIG. 3 to FIG. 5 .

[0226] Figure 3 is a schematic diagram of an SDAP control PDU in an embodiment of the present application. As shown in Figure 3 , the SDAP control PDU carries first information and carries second information in the R field. This second information indicates that the SDAP control PDU is a PDU carrying the first information. Accordingly, the receiving end cannot ignore the information in the R field. Furthermore, the QFI / PQFI in the first byte (Oct1) of the SDAP control PDU identifies at least one object associated with the first information.

[0227] Figure 4 is a schematic diagram of an SDAP control PDU in another embodiment of the present application. As shown in Figure 4 , the SDAP control PDU carries first information and carries second information in the E field. This second information indicates that the SDAP control PDU is a PDU carrying the first information. Accordingly, the receiving end cannot ignore the information in the E field. Furthermore, the QFI / PQFI in the first byte (Oct1) of the SDAP control PDU identifies at least one object associated with the first information.

[0228] Figure 5 is a schematic diagram of an SDAP control PDU in another embodiment of the present application. In order to improve compatibility with traditional SDAP control PDUs, a PDU type (PDU type) can be introduced to indicate whether the SDAP control PDU carries the first information. As shown in Figure 5, the PDU type can occupy two bits in the second byte (Oct2) of the SDAP control PDU. And if the PDU type is 00, it means that the SDAP control PDU carries the first information. In addition, the QFI / PQFI in the first byte (Oct1) of the SDAP control PDU is an identifier of at least one object associated with the first information, and the QFI / PQFI in the second byte of the SDAP control PDU is an identifier of other objects that are transmitted synchronously or collaboratively with at least one object.

[0229] The following describes the structure of the SDAP data PDU in the embodiment of the present application in conjunction with FIG6 and FIG7.

[0230] As shown in Figure 6, the D / C identifier in the SDAP data PDU is used to indicate whether the SDAP PDU is a control PDU or a data PDU), the QFI / PQFI in the first byte (Oct1) and the associated QFI / PQFI in the second byte are identifiers of at least one object associated with the first information. The data part in the SDAP data PDU can carry RDI to indicate whether the mapping rule of the uplink QoS flow to the DRB is updated. The data part in the SDAP data PDU can carry RQI to indicate whether to notify the CN NAS that the UL needs to update the mapping of the SDF to the QoS flow. In addition, the data part in the SDAP data PDU can also carry an identifier for indicating the DRB to which at least one object needs to be mapped.

[0231] In an embodiment of the present application, a radio bearer carrying data or a data packet associated with at least one object may be directly carried in an SDAP data PDU to simplify the complexity of determining the radio bearer.

[0232] As shown in Figure 7, the D / C identifier in the SDAP data PDU is used to indicate whether the SDAP PDU is a control PDU or a data PDU. The QFI / PQFI in the first byte (Oct1) and the associated QFI / PQFI in the second byte are identifiers of at least one object associated with the first information. The data portion of the SDAP data PDU can carry an RDI to indicate whether the mapping rules for the uplink QoS flow to the DRB are updated. The data portion of the SDAP data PDU can carry an RQI to indicate whether to notify the CN NAS that the UL needs to update the mapping of the SDF to the QoS flow.

[0233] In addition, the radio bearer for transmitting at least one object associated with the first information can be determined by the radio bearer for transmitting the SDAP data PDU. For example, if the first information is associated with QoS flow 1 and QoS flow 2, then DRB 1 is used to send the SDAP data PDU for both QoS flow 1 and QoS flow 2, indicating that both QoS flow 1 and QoS flow 2 are mapped to DRB 1.

[0234] Alternatively, the first information associates QoS flow 1 and QoS flow 2, and QoS flow 1 has been mapped to DRB1 by other means. At this time, SDAP data PDU is sent for QoS flow 2 using DRB1 to indicate that QoS flow 2 is mapped to DRB1.

[0235] In an embodiment of the present application, a radio bearer for transmitting the SDAP data PDU may be used to implicitly indicate a radio bearer for transmitting at least one object associated with the first information, which helps to reuse the format of the known SDAP PDU as much as possible.

[0236] It should be noted that the above description uses the SDAP PDU to describe the carrying method of the first information. In the embodiment of the present application, the first information can be carried in other PDUs, such as PDCP PDUs. The specific carrying method can be found in the above description of the SDAP PDU. For the sake of brevity, it will not be repeated below.

[0237] In some implementations, the first information is carried in a first data packet, and the first data packet satisfies one or more of the following: the first data packet corresponds to at least one object associated with the first information; the QoS flow of the first data packet is associated with at least one object; the PDU session of the first data packet is associated with at least one object; the data flow to which the first data packet belongs is associated with at least one object; and the bearer corresponding to the first data packet is associated with at least one object.

[0238] In some implementations, if the object is a QoS flow, the first data packet corresponds to at least one object associated with the first information, which can be understood as the first data packet corresponding to the QoS flow associated with the first information. If the object is a data flow, the first data packet corresponds to at least one object associated with the first information, which can be understood as the first data packet being a data packet in the data flow associated with the first information. If the object is a terminal device, the first data packet corresponds to at least one object associated with the first information, which can be understood as the first data packet being a data packet of the terminal device associated with the first information. If the object is a bearer, the first data packet corresponds to at least one object associated with the first information, which can be understood as the first data packet being transmitted through the bearer associated with the first information. If the object is a PDU session, the first data packet corresponds to at least one object associated with the first information, which can be understood as the first data packet being transmitted through the PDU session associated with the first information.

[0239] In some implementations, if the object is a QoS flow, the QoS flow of the first data packet is associated with at least one object, which can be understood as the QoS flow of the first data packet belonging to at least one QoS flow. If the object is a data flow, the QoS flow of the first data packet is associated with at least one object, which can be understood as the QoS flow of the first data packet corresponds to at least one data flow. If the object is a terminal device, the QoS flow of the first data packet is associated with at least one object, which can be understood as the QoS flow of the first data packet is the QoS flow of at least one terminal device. If the object is a bearer, the QoS flow of the first data packet is associated with at least one object, which can be understood as the QoS flow of the first data packet is transmitted through at least one bearer. If the object is a PDU session, the QoS flow of the first data packet is associated with at least one object, which can be understood as the QoS flow of the first data packet is transmitted through the PDU session associated with the first information.

[0240] In some implementations, if the object is a QoS flow, the PDU session of the first data packet is associated with at least one object, which can be understood as the PDU session of the first data packet belonging to at least one QoS flow. If the object is a data flow, the PDU session of the first data packet is associated with at least one object, which can be understood as the PDU session of the first data packet carries at least one data flow. If the object is a terminal device, the PDU session of the first data packet is associated with at least one object, which can be understood as the PDU session of the first data packet is a PDU session of at least one terminal device. If the object is a bearer, the PDU session of the first data packet is associated with at least one object, which can be understood as the PDU session of the first data packet is associated with at least one bearer. If the object is a PDU session, the PDU session of the first data packet is associated with at least one object, which can be understood as the PDU session of the first data packet belongs to at least one PDU session.

[0241] In some implementations, if the object is a QoS flow, the data flow to which the first data packet belongs is associated with at least one object, which can be understood as the data flow to which the first data packet belongs corresponds to at least one QoS flow. If the object is a data flow, the data flow to which the first data packet belongs is associated with at least one object, which can be understood as the data flow to which the first data packet belongs belongs to at least one data flow. If the object is a terminal device, the data flow to which the first data packet belongs is associated with at least one object, which can be understood as the data flow to which the first data packet belongs corresponds to a PDU session of at least one terminal device. If the object is a bearer, the data flow to which the first data packet belongs is associated with at least one object, which can be understood as the data flow to which the first data packet belongs is transmitted through at least one bearer. If the object is a PDU session, the data flow to which the first data packet belongs is associated with at least one object, which can be understood as the data flow to which the first data packet belongs belongs to at least one PDU session.

[0242] In some implementations, if the object is a QoS flow, the bearer corresponding to the first data packet is associated with at least one object, which can be understood as the bearer corresponding to the first data packet corresponding to at least one QoS flow. If the object is a data flow, the bearer corresponding to the first data packet is associated with at least one object, which can be understood as the bearer corresponding to the first data packet is used to transmit at least one data flow. If the object is a terminal device, the bearer corresponding to the first data packet is associated with at least one object, which can be understood as the bearer corresponding to the first data packet is a data packet of at least one terminal device. If the object is a bearer, the bearer corresponding to the first data packet is associated with at least one object, which can be understood as the bearer corresponding to the first data packet belongs to at least one bearer. If the object is a PDU session, the bearer corresponding to the first data packet is associated with at least one object, which can be understood as the bearer corresponding to the first data packet corresponds to at least one PDU session.

[0243] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device. In other implementations, the first device is an access network device, and the second device is a core network device. In other implementations, the first device is a core network device, and the second device is an access network device or a terminal device. For example, the access network device or the terminal device may send first information to the core network device, wherein the synchronous transmission or coordinated transmission of at least one object associated with the first information may be applicable to uplink transmission.

[0244] The above introduces the transmission scheme of the first information in the embodiment of the present application. The following introduces the processing scheme for at least one object in the embodiment of the present application, which helps to achieve synchronous transmission or collaborative transmission during the transmission process.

[0245] In some implementations, at least one object-associated QoS flow is carried through the same DRB, or in other words, at least one object-associated QoS flow can be mapped to the same DRB, which helps reduce the impact on some protocol layers (e.g., PDCP layer, RLC layer, MAC layer) and reduces the complexity of terminal device implementation.

[0246] In some implementations, QoS flows associated with at least one object can be associated with the same DRB via RRC configuration. For example, in an SDAP configuration, at least one object is associated with a DRB / SDAP configuration. In other words, in the SDAP configuration corresponding to a DRB, the at least one object is added to the "MappedQoS-FlowsToAdd" IE.

[0247] In some implementations, if one of the at least one object in the SDAP configuration is deleted, then the object (ie, at least one object) that has a synchronous transmission requirement or a collaborative transmission requirement with the object is also deleted.

[0248] In other implementations, at least one object-associated QoS flow can be associated with a default DRB through RRC configuration. For example, in an SDAP configuration, at least one object-associated QoS flow can be associated with a default DRB. In other words, in an SDAP configuration corresponding to a default DRB, at least one object-associated QoS flow is added to the mappedQoS-FlowsToAdd IE.

[0249] In some implementations, if one of the at least one object in the SDAP configuration is deleted, then the object (ie, at least one object) that has a synchronous transmission requirement or a collaborative transmission requirement with the object is also deleted.

[0250] In other implementations, a DL SDAP header may be used to indicate a mapping relationship between a QoS flow associated with at least one object and a DRB. For example, if the second device is a terminal device, then according to the indication of the DL SDAP header, the terminal device performs an uplink reflective mapping between QOS flow and DRB. That is to say, after the terminal device receives a DL SDAP data PDU, its DL SDAP header carries a QFI and RDI indicates a specific value (such as 1, indicating that the mapping rules between DRB and QoS flow need to be updated, or indicating that the mapping rules between DRB and QoS flow need to be stored), then the terminal device performs an uplink reflective mapping between the QoS flow and the DRB, or modifies the mapping relationship between the uplink QoS flow and the DRB.

[0251] In other implementations, at least one object-associated QoS flow is carried through different DRBs, or in other words, at least one object-associated QoS flow can be carried through multiple different DRBs, or in other words, at least one object-associated QoS flow can be mapped to multiple different bearers, which helps reduce the impact on some protocol layers (for example, the SDAP layer).

[0252] In some implementations, the above-mentioned multiple DRBs satisfy one or more of the following: the configuration parameters of at least two DRBs among the multiple DRBs match; the configuration parameters of at least two DRBs among the multiple DRBs are the same or similar; the LCP mapping restrictions corresponding to at least two DRBs among the multiple DRBs match; the LCP mapping restrictions corresponding to at least two DRBs among the multiple DRBs are the same or similar, which helps to achieve synchronous transmission or coordinated transmission of at least one object.

[0253] In the embodiments of the present application, the similarity of the aforementioned multiple configuration parameters is not limited. In some implementations, each configuration parameter may include multiple sub-parameters. Accordingly, similarity between multiple configuration parameters can be understood as the number of different sub-parameters in the multiple configuration parameters being less than a threshold. In other implementations, similarity between multiple configuration parameters can be understood as the difference between the multiple configuration parameters being less than a threshold.

[0254] In some implementations, if the QoS flows associated with at least one object are carried through different DRBs, the data associated with at least one object performs LCH to MAC PDU data multiplexing with the same LCH priority, which helps to achieve coordinated transmission or synchronous transmission of at least one object.

[0255] In some implementations, the QoS flows associated with at least one object are carried over the same LCH or LCG, which facilitates coordinated or synchronized transmission of at least one object. Of course, in embodiments of the present application, the QoS flows associated with at least one object can be carried over different LCHs or LCGs.

[0256] In some implementations, if QoS flows associated with at least one object are carried by multiple different LCHs, configuration parameters of at least two of the multiple LCHs match, thereby facilitating synchronous transmission or coordinated transmission of the at least one object. Matching the configuration parameters of at least two LCHs may mean that the configuration parameters of at least two LCHs are identical, or that the configuration parameters of at least two LCHs are similar.

[0257] In some implementations, if QoS flows associated with at least one object are carried by multiple different LCGs, matching configuration parameters of at least two of the multiple LCGs facilitates synchronized or coordinated transmission of the at least one object. Matching configuration parameters of at least two LCGs can be understood as the same configuration parameters of at least two LCGs, or similar configuration parameters of at least two LCGs.

[0258] In some implementations, if QoS flows associated with at least one object are carried by multiple different LCGs, the configuration parameters of the LCHs in the multiple LCGs match, thereby facilitating synchronous or coordinated transmission of the at least one object. The matching of the configuration parameters of the LCHs in the multiple LCGs can be understood as the same configuration parameters of the LCHs in the multiple LCGs, or the similar configuration parameters of the LCHs in the multiple LCGs.

[0259] In some implementations, at least one object-associated DRB or bearer is mapped to the same LCH, which helps to achieve coordinated transmission or synchronous transmission of at least one object. Of course, in an embodiment of the present application, at least one object-associated DRB or bearer can also be mapped to different LCHs.

[0260] In some implementations, at least one object-associated DRB or bearer is mapped to the same LCG, which helps to achieve coordinated transmission or synchronous transmission of at least one object. Of course, in an embodiment of the present application, at least one object-associated DRB or bearer is mapped to a different LCG.

[0261] The above describes the coordinated transmission or synchronous transmission scheme of the embodiment of the present application from the perspectives of DRB, bearer, LCH and LCG, etc. The following describes the coordinated transmission or synchronous transmission scheme of the embodiment of the present application from the perspective of multiplexing MAC PDU.

[0262] In some implementations, the at least one object satisfies one or more of the following: data or data packets associated with at least one object multiplex the same MAC PDU; data or data packets associated with at least one object multiplex multiple consecutive MAC PDUs; data or data packets associated with at least one object are transmitted together to the first device; data or data packets associated with at least one object are transmitted to the first device within a target time period.

[0263] In some implementations, data or data packets associated with at least one object reuse the same MAC PDU, or in other words, data or data packets associated with at least one object are carried on the same MAC PDU, which helps to achieve synchronous transmission or coordinated transmission of at least one object.

[0264] In some implementations, data or packets associated with at least one object are multiplexed across multiple consecutive MAC PDUs, or in other words, at least one object is carried across multiple consecutive MAC PDUs, thereby facilitating synchronous or coordinated transmission of the at least one object. The multiple consecutive MAC PDUs may include multiple MAC PDUs transmitted consecutively.

[0265] In some implementations, data or data packets associated with at least one object are transmitted to the first device together, where "transmitted to the first device together" can be understood as being transmitted to the first device at a similar time or simultaneously. For example, data or data packets associated with at least one object are transmitted to the first device in a MAC PDU.

[0266] In some implementations, data or data packets associated with at least one object are transmitted to the first device within a target time period, thereby facilitating synchronous or coordinated transmission of at least one object. For example, if the target time period is 5 seconds, data or data packets associated with at least one object are transmitted to the first device within 5 seconds.

[0267] In the embodiments of the present application, the data or data packets associated with at least one object are not limited. In some implementations, the data or data packets associated with at least one object may include data packets related to at least one object, wherein the related data packets may include data packets transmitted synchronously with the at least one object, or data packets transmitted in coordination with the at least one object.

[0268] Of course, in an embodiment of the present application, the data packets associated with at least one object may include data packets in at least one object. If at least one object is a QoS flow, the data packets associated with at least one object may include data packets associated with at least one QoS flow. If at least one object is a data packet, the data packets associated with at least one object may include data packets in at least one data packet. If at least one object is a data stream, the data packets associated with at least one object may include data packets included in at least one data stream. If at least one object is a bearer, the data packets associated with at least one object may include data packets transmitted via at least one bearer. If at least one object is a terminal device, the data packets associated with at least one object may include data packets received or sent via at least one terminal device.

[0269] The above describes the scheme for synchronous transmission or collaborative transmission in the embodiment of the present application from the perspective of at least one object. The following describes it from the perspective of at least two objects and the perspective of the target object. For related introduction, please refer to the above.

[0270] In some implementations, at least one object includes multiple objects, the multiple objects include at least two objects, and the at least two objects satisfy one or more of the following: data or data packets associated with at least two objects multiplex the same MAC PDU; data or data packets associated with at least two objects multiplex multiple consecutive MAC PDUs; data or data packets associated with at least two objects are transmitted to the first device together; data or data packets associated with at least two objects are transmitted to the first device within a target time period; data or data packets associated with at least two objects are carried in one MAC PDU; data or data packets associated with at least two objects are carried in multiple consecutive MAC PDUs.

[0271] In some implementations, one or more objects among at least one object are target objects, and the target objects satisfy one or more of the following: the data or data packets associated with the target object multiplex the same MAC PDU; the data or data packets associated with the target object multiplex multiple consecutive MAC PDUs; the data or data packets associated with the target object are transmitted to the first device within the target time period; the data or data packets associated with the target object are transmitted to the first device within the target time period; the data or data packets associated with the target object are carried in one MAC PDU; the data or data packets associated with the target object are carried in multiple consecutive MAC PDUs.

[0272] In an embodiment of the present application, the target object may be a specific object among at least one object, wherein the specific object may be understood as an object having synchronous transmission requirements or collaborative transmission requirements, and details may be referred to the above introduction.

[0273] In the embodiments of the present application, the format of the above-mentioned data packet or data is not limited. In some implementations, the format corresponding to the above-mentioned data packet or data may include at least one of the following: PDU, SDU, PDU set, data burst, PDU associated with data or data packet, SDU associated with data or data packet, PDU set associated with data or data packet, and data burst associated with data or data packet.

[0274] In other implementations, the aforementioned data packets may be specific data packets. For example, they may be data packets of a specific importance. In another example, they may be data packets of a specific priority. In another example, they may be data packets of a specific latency. In another example, they may be data packets for a specific PDB. In another example, they may be data packets for a PSDB. Of course, in the embodiments of the present application, the aforementioned data packets may be any data packets.

[0275] In other implementations, the data may be specific data. For example, data of a specific importance. Another example is data of a specific priority. Another example is data of a specific latency. Of course, in the embodiments of the present application, the data may be any data.

[0276] In some implementations, the second device may send third information to the first device to indicate the first information to be transmitted. That is, before step S210, the second device sends the third information to the first device.

[0277] In some implementations, the third information is used to indicate one or more of the following: part or all of the objects in the target object to be transmitted; associated data or data packets in the target object to be transmitted; the size of the transmission resources required to transmit the target object; the size of the transmission resources required to transmit the objects to be transmitted in the target object; the data volume or data volume information of the objects to be transmitted in the target object; the remaining delay or allowed delay information of the data of the objects to be transmitted in the target object; the data volume information corresponding to the specific remaining delay or allowed delay in the objects to be transmitted in the target object; and the data volume information corresponding to the delay status reporting information in the objects to be transmitted in the target object.

[0278] In some implementations, the remaining latency can be calculated for a group of data. During the transmission process, the transmission latency for that group of data begins to be calculated when the data begins to be transmitted. Accordingly, the remaining latency for the data to be transmitted can be calculated as the total transmission latency minus the latency after the data begins to be transmitted. In other words, the remaining latency for the data to be transmitted can be understood as the remaining latency for the data to be transmitted.

[0279] In some implementations, the allowed delay may be for one or more data, that is, the allowed delay required to transmit the data is the allowed delay.

[0280] As described above, the third information is associated with the first information. The third information can be associated with a target object, where the target object can be at least one object. Of course, in the embodiments of the present application, the target object can be one or more objects within the at least one object. Alternatively, the target object can be a specific object within the at least one object. For more information about the target object, please refer to the above description of the at least one object. For the sake of brevity, we will not elaborate on this here.

[0281] In some implementations, the third information is used to indicate that some or all of the target objects are to be transmitted. That is, if the target object is at least one object, the third information is used to indicate that some or all of the at least one object are to be transmitted. If the target object is one or more objects in the at least one object, the third information is used to indicate that one or more of the at least one object are to be transmitted. If the target object is a specific object in the at least one object, the third information is used to indicate that the specific object in the at least one object is to be transmitted.

[0282] In some implementations, the third information is used to indicate that data or data packets associated with the target object are to be transmitted. That is, if the target object is at least one object, the third information is used to indicate that data or data packets associated with the at least one object are to be transmitted. If the target object is one or more objects within the at least one object, the third information is used to indicate that data or data packets associated with the one or more objects within the at least one object are to be transmitted. If the target object is a specific object within the at least one object, the third information is used to indicate that data or data packets associated with the specific object within the at least one object are to be transmitted.

[0283] In the embodiments of the present application, the data or data packets associated with at least one object are not limited. For example, the data associated with at least one object may include partial data associated with at least one object or all data associated with at least one object. For another example, the data packets associated with at least one object may include partial data packets associated with at least one object or all data packets associated with at least one object.

[0284] In some implementations, the third information is used to indicate the size of the transmission resources required to transmit the target object. That is, if the target object is at least one object, the third information is used to indicate the size of the transmission resources required to transmit the at least one object. If the target object is one or more objects within the at least one object, the third information is used to indicate the size of the transmission resources required to transmit the one or more objects within the at least one object. If the target object is a specific object within the at least one object, the third information is used to indicate the size of the transmission resources required to transmit the specific object within the at least one object.

[0285] In some implementations, the third information indicates the size of transmission resources required to transmit an object to be transmitted in the target object. The object to be transmitted in the target object may be an object that has not been transmitted or has been transmitted unsuccessfully in the target object. Alternatively, the object to be transmitted may be part or all of the objects in the target object.

[0286] That is, if the target object is at least one object, the third information is used to indicate the size of the transmission resources required to transmit the object to be transmitted in the at least one object. If the target object is one or more objects in the at least one object, the third information is used to indicate the size of the transmission resources required to transmit the object to be transmitted in the one or more objects. If the target object is a specific object in the at least one object, the third information is used to indicate the size of the transmission resources required to transmit the object to be transmitted in the specific object.

[0287] In some implementations, the third information is used to indicate the data volume of the objects to be transferred in the target object. The objects to be transferred in the target object may be objects that have not been transferred or have been transferred unsuccessfully. Alternatively, the objects to be transferred may be part or all of the objects in the target object.

[0288] That is, if the target object is at least one object, the third information is used to indicate the data volume information of the object to be transmitted in the at least one object. If the target object is one or more objects in the at least one object, the third information is used to indicate the data volume information of the object to be transmitted in the one or more objects. If the target object is a specific object in the at least one object, the third information is used to indicate the data volume information of the object to be transmitted in the specific object.

[0289] In the embodiment of the present application, the data volume information may include information indicating the data volume, or in other words, the data volume information may include information determining the data volume. Of course, in the embodiment of the present application, the data volume information may be the data volume itself. Therefore, the third information indicating the data volume information of the object to be transferred in the target object may be replaced with the third information indicating the data volume of the object to be transferred in the target object.

[0290] In some implementations, the third information indicates a remaining latency or an allowed latency for data of objects to be transmitted in the target object. The objects to be transmitted in the target object may be objects that have not been transmitted or have been transmitted unsuccessfully. Alternatively, the objects to be transmitted may be some or all objects in the target object.

[0291] That is, if the target object is at least one object, the third information is used to indicate the remaining delay or allowed delay for transmitting data of the object to be transmitted in the at least one object. If the target object is one or more objects in the at least one object, the third information is used to indicate the remaining delay or allowed delay for transmitting data of the object to be transmitted in the one or more objects. If the target object is a specific object in the at least one object, the third information is used to indicate the remaining delay or allowed delay for transmitting the object to be transmitted in the specific object.

[0292] In some implementations, the third information is used to indicate the data volume information of the object corresponding to the target remaining delay or the target allowed delay among the objects to be transmitted of the target object, or in other words, if object 1 among the objects to be transmitted of the target object corresponds to the target remaining delay or the target allowed delay, then the third information is used to indicate the data volume information of object 1, wherein the data volume information can be referred to the introduction above.

[0293] That is, if the target object is at least one object, the third information is used to indicate the data volume information of the object corresponding to the target remaining delay or target allowed delay in the objects to be transmitted of the at least one object. If the target object is one or more objects among at least one object, the third information is used to indicate the data volume information of the object corresponding to the target remaining delay or target allowed delay in the objects to be transmitted of the one or more objects. If the target object is a specific object among at least one object, the third information is used to indicate the data volume information of the object corresponding to the target remaining delay or target allowed delay in the objects to be transmitted of the specific object.

[0294] In the embodiments of the present application, the target residual delay is not limited. For example, the target residual delay may be the minimum residual delay among the residual delays corresponding to the objects to be transmitted. In another example, the target residual delay may be the average residual delay among the residual delays corresponding to the objects to be transmitted. In another example, the target residual delay may be the maximum residual delay among the residual delays corresponding to the objects to be transmitted.

[0295] In the embodiments of the present application, the target allowable delay is not limited. For example, the target allowable delay may be the minimum allowable delay among the allowable delays corresponding to the objects to be transmitted. In another example, the target allowable delay may be the average allowable delay among the allowable delays corresponding to the objects to be transmitted. In another example, the target allowable delay may be the maximum allowable delay among the allowable delays corresponding to the objects to be transmitted.

[0296] In the embodiment of the present application, the object to be transmitted in the target object may be an object that has not been transmitted or has not been successfully transmitted in the target object. In addition, the object to be transmitted may be part or all of the objects in the target object.

[0297] In some implementations, the third information is used to indicate the data volume information of the object corresponding to the delay status reporting information in the object to be transmitted of the target object, or in other words, the delay status reporting information carries object 1 among the objects to be transmitted of the target object. At this time, the third information is used to indicate the data volume information of object 1.

[0298] That is, if the target object is at least one object, the third information is used to indicate the data volume information of the object corresponding to the delay status reporting information of the at least one object in the objects to be transmitted. If the target object is one or more objects in the at least one object, the third information is used to indicate the data volume information of the object corresponding to the delay status reporting information of the one or more objects in the objects to be transmitted. If the target object is a specific object in the at least one object, the third information is used to indicate the data volume information of the object corresponding to the delay status reporting information of the specific object in the objects to be transmitted.

[0299] In the embodiment of the present application, the object to be transmitted in the target object may be an object that has not been transmitted or has not been successfully transmitted in the target object. In addition, the object to be transmitted may be part or all of the objects in the target object.

[0300] The above introduces the content of the third information in the embodiment of the present application, and the following introduces the transmission method of the third information in the embodiment of the present application.

[0301] In some implementations, the sending of the third information may be triggered based on the first condition, or in other words, if the first condition is met, the second device sends the third information to the first device.

[0302] In some implementations, the first condition includes one or more of the following: at least one object cannot reuse a MAC PDU; at least one object cannot reuse multiple consecutive MAC PDUs; at least one object cannot be transmitted together to the first device; at least one object cannot be carried in a MAC PDU; at least one object cannot be carried in multiple consecutive MAC PDUs.

[0303] In some implementations, if the first condition includes that at least one object cannot reuse the same MAC PDU, or in other words, the first condition includes that at least one object cannot be carried in a MAC PDU, it may cause the transmission of at least one object to fail to meet synchronous transmission or coordinated transmission.

[0304] In some implementations, if the first condition includes that at least one object cannot reuse multiple consecutive MAC PDUs, or in other words, the first condition includes that at least one object cannot be carried on multiple consecutive MAC PDUs, it may cause the transmission of at least one object to fail to meet synchronous transmission or coordinated transmission.

[0305] In some implementations, if the first condition includes that at least one object cannot be transmitted to the first device together, the transmission of the at least one object may fail to satisfy synchronous transmission or coordinated transmission. The at least one object cannot be transmitted to the first device together, which can be understood as the at least one object cannot be transmitted to the first device simultaneously, or the at least one object cannot be transmitted to the first device within a period of time.

[0306] In some implementations, the data associated with the third information satisfies one or more of the following: the scheduling priority of the data associated with the third information is higher than the scheduling priority of the first data; the transmission priority of the data associated with the third information is higher than the transmission priority of the first data; the LCH priority of the data associated with the third information is higher than the LCH priority of the first data; and the multiplexing priority of the data associated with the third information is higher than the multiplexing priority of the first data.

[0307] In some implementations, the scheduling priority is used to indicate the order in which data is scheduled. Generally, data with a higher scheduling priority is scheduled before data with a lower scheduling priority.

[0308] In some implementations, the transmission priority is used to indicate the order in which data is transmitted. Generally, data with a higher transmission priority is transmitted before data with a lower transmission priority.

[0309] In some implementations, the LCH priority is used to indicate the order in which data is mapped to the LCH. Generally, data with a higher LCH priority is mapped to the LCH before data with a lower LCH priority.

[0310] In some implementations, the multiplexing priority of data associated with the third information is higher than the multiplexing priority of other data, where the multiplexing priority can be understood as the priority of the data multiplexing MAC PDU associated with the third information, that is, the priority of the data multiplexing MAC PDU associated with the third information is higher than the priority of the data multiplexing MAC PDU associated with the third information.

[0311] In some implementations, the data associated with the third information can be understood as data associated with the target object, where the target object can be described above. Furthermore, the "other data" refers to data to be transmitted other than the data associated with the third information, or in other words, refers to data to be transmitted by the second device other than the data associated with the third information.

[0312] In some implementations, if the first information is associated with the synchronous transmission or collaborative transmission of data or data packets of at least one object, the data associated with the first information satisfies one or more of the following: the scheduling priority of the data associated with the first information is higher than the scheduling priority of other data; the transmission priority of the data associated with the first information is higher than the transmission priority of other data; the LCH priority of the data associated with the first information is higher than the LCH priority of other data; the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of other data, which helps to increase the success rate of the synchronous transmission or collaborative transmission of the first information.

[0313] In some implementations, the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of other data, where the multiplexing priority can be understood as the priority of the data multiplexing MAC PDU associated with the first information, that is, the priority of the data multiplexing MAC PDU associated with the first information is higher than the priority of the data multiplexing MAC PDU associated with the first information.

[0314] In some implementations, the data associated with the first information can be understood as data associated with the target object, where the target object can be described above. Furthermore, the "other data" refers to data to be transmitted other than the data associated with the first information, or in other words, refers to data to be transmitted by the second device other than the data associated with the first information.

[0315] In some implementations, LCHs associated with at least one object have the same or similar priorities, which facilitates synchronous transmission or coordinated transmission of the at least one object.

[0316] In the embodiment of the present application, there is no limitation on the similarity of the LCH priorities associated with at least one object. In some implementations, the similarity of the LCH priorities associated with at least one object may include that the difference between the highest priority and the lowest priority among the LCH priorities associated with at least one object is less than or equal to a priority threshold. For example, the priority threshold is one priority, and the highest priority among the LCH priorities associated with at least one object is the first priority, and the highest priority among the LCH priorities associated with at least one object is the second priority, wherein the difference between the first priority and the second priority is one priority, that is, the difference is equal to the priority threshold, then the LCH priorities associated with at least one object are similar.

[0317] In some other implementations, the LCH priority associated with at least one object being similar may include the LCH priority associated with at least one object being within a priority range. For example, if the priority range is [priority 1; priority 2; priority 3], and the LCH priority associated with at least one object is priority 1 and priority 2, respectively, then the LCH priority associated with at least one object is within the priority range, and the LCH priority associated with at least one object is similar.

[0318] In some implementations, the method further includes: the second device sending fourth information to the first device, the fourth information being used to indicate whether the second device supports transmission of the first information, and / or the fourth information being used to indicate whether the second device has available first information.

[0319] That is, before the second device sends the first information to the first device, the second device can send the first information to the first device so that the first device is ready to receive the first information. For example, the second device can send the first information to the first device, and accordingly, the first device can allocate resources for transmitting the first information to the second device.

[0320] In the embodiment of the present application, the fourth information and the third information may be the same information. For example, the third information may indirectly indicate the fourth information. Of course, in the embodiment of the present application, the fourth information may be different from the third information. For example, the fourth information may be transmitted before the third information, or the fourth information may be transmitted simultaneously with the third information.

[0321] In the embodiments of the present application, the first device and the second device are not limited. For example, the first device may be an access network device, and the second device may be a terminal device or a first core network device. In another example, both the first device and the second device may be terminal devices. In another example, the first device may be a second core network device, and the second device may be a terminal device. In another example, the first device may be a second core network device, and the second device may be a first core network device.

[0322] For ease of understanding, the following describes the methods of the embodiments of the present application in conjunction with Example 1 and Example 2. In Example 1, the first information is transmitted via control plane information, and in Example 2, the first information is transmitted via user plane information. Furthermore, in Example 1 and / or Example 2, the first device may be an access network device, and the second device may be a terminal device or a core network device.

[0323] Figure 8 is a schematic flow chart of a wireless communication method in Embodiment 1 of the present application. The method shown in Figure 8 includes step S810 and step S820.

[0324] In step S810, the second device sends first information (also called "multimodal information or demand") to the first device.

[0325] In some implementations, the first information may be sent to the first device when the second device obtains the first information. In other implementations, the second device may notify the first device of the first information when the first device requests to obtain the first information.

[0326] In some implementations, the terminal device may indicate to the base station whether the terminal device supports reporting of the first information. In the embodiment of the present application, only the second device that supports reporting of the first information may report the first information, which facilitates compatibility with second devices of different capabilities. In addition, the solution of the embodiment of the present application does not require all second devices to support the function of reporting the first information, which helps reduce the complexity of the second devices.

[0327] In some implementations, the manner in which the terminal device obtains the first information may include one or more of the following: the high-layer of the terminal device interacts with the low-layer of the terminal device (for example, implemented by the terminal device, or carrying the first information through packet header information, etc.); the core network device informs the terminal device of the first information, for example, the core network device may send the first information to the terminal device through NAS signaling.

[0328] Implementation method 1: The terminal device reports the first information.

[0329] In some implementations, the terminal device reports the first information via a UL RRC message, where the UL RRC message may be UE assistance information.

[0330] In some implementations, the terminal device reports the first information through a UL NAS message, where the UL NAS message can be an uplink information transmission (UL information transfer). Of course, in an embodiment of the present application, the above-mentioned first information can also be carried in other NAS messages. For example, after the core network device obtains the first information from the terminal device, it can forward the first information to the access network device.

[0331] In the embodiment of the present application, since the terminal device is more aware of the uplink transmission requirements or information, the first information sent by the terminal device can more accurately and timely reflect the transmission requirements of the service (for example, coordinated transmission or synchronous transmission).

[0332] In some implementations, the network device carries indication information (e.g., the request message described above) in an other configuration (otherconfig) to instruct the terminal device to report the first information. For example, the first indication is carried in the other configuration to instruct or enable the terminal device to report the first information. For another example, a specific QoS flow index or QoS flow list is indicated in the other configuration (otherconfig), and accordingly, the first channel sent by the terminal device is associated with the specific QoS flow index or QoS flow list.

[0333] In some implementations, the terminal device reports the first information when the first condition is met, wherein the first condition includes at least one of the following: the first information reporting prohibition timer for the terminal device or for the QoS flow is not running; the first information reporting prohibition timer for the terminal device or for the QoS flow has expired; the terminal device has not reported the first information of the terminal device when configuring reporting; the terminal device has not reported the first information for the QoS flow when configuring reporting; the terminal device has not reported the first information for a specific QoS flow when configuring reporting; there is an information change for the first information reported last time; the intensity of the change in the information content of the first information reported last time is greater than a threshold.

[0334] If there is a change in the first information reported last time, the first condition may include one or more of the following: there is a change in the first information reported by the terminal device; there is a change in the first information reported for the QoS flow; there is a change in the first information reported for the specific QoS flow.

[0335] If the magnitude of the change in the content of the first information reported last time is greater than a threshold, the first condition includes that the change in the first information reported for the specific QoS flow is greater than the threshold.

[0336] In an embodiment of the present application, determining whether to report the first information based on the first condition helps to ensure that the terminal device reports the first information in a timely manner, while reducing the possibility of excessive air interface resource overhead caused by frequent sending of the first information.

[0337] In some implementations, the first information indicates QoS flow granularity. For example, the first information is associated with QoS flow 1. In another example, the first information is associated with the identifier of a QoS flow with a synchronous transmission requirement or a collaborative transmission requirement, or a list of QoS flows. In another example, the first information indicates whether QoS flow 1 is flagged. In another example, the first information indicates one or more QoS flows and, for each QoS flow, indicates the identifier of a QoS flow with a synchronous transmission requirement or a list of QoS flows with the flow.

[0338] In an embodiment of the present application, since different QoS flows may support different services, or some QoS flows may not support synchronous transmission or collaborative transmission (also known as multimodal transmission requirements), or some QoS flows may support non-multimodal services, the first information reported based on the QoS flow can accurately reflect the synchronous transmission or collaborative transmission requirements of different QoS flows.

[0339] In some implementations, the first information may be carried in a UL-TrafficInfo->PDU-SessionUL-TrafficInfo->QOS-FlowUL-TrafficInfo IE, where the QFI in the IE may be an identifier of a QoS flow associated with the first information or an identifier of a QoS flow list, or the first information may be used to indicate whether the QFI in the IE is marked.

[0340] In some implementations, a new UAI may be introduced in the UE assistance information to carry the first information. For example, a new UAI may be introduced to carry the first information to indicate a synchronization transmission requirement or a coordinated transmission requirement between QoS flows. For another example, a new UAI may be introduced to carry the first information to indicate one or more QoS flows, and for each QoS flow, the identifiers of the QoS flows with which the synchronization transmission requirement or the coordinated transmission requirement is indicated, or a list of QoS flows. Alternatively, for another example, a new UAI may be introduced to carry the first information to indicate which QoS flows are marked.

[0341] Implementation method 2: The core network device reports the first information.

[0342] In some implementations, the core network device may indicate the first information through a CP message. The CP message may be TSCAI. Since TSCAI is based on QoS flow indication, adding the first information associated with the QoS flow corresponding to TSCAI to the TSCAI information helps to reuse known communication processes. The first information is used to indicate the identifiers or QoS flow lists of other QoS flows that are synchronously transmitted or collaboratively transmitted with the QoS flow corresponding to TSCAI, or the first information is used to indicate whether the QoS flow corresponding to TSCAI is marked. Of course, in an embodiment of the present application, the first information may also be indicated by other CP plane information.

[0343] In this application example, when the CN is able to obtain UL service information (i.e., the first information), the first information is sent to the access network device using existing signaling and process interaction as much as possible, thereby avoiding the terminal device reporting the first information and causing an increase in air interface signaling overhead. In addition, the core network device notifies the base station of both UL and DL related information to reduce the signaling overhead of the CN in transmitting the first information.

[0344] In some implementations, the first information may be used to indicate one or more of the following: associations between QoS flows, bindings between QoS flows, synchronizations between QoS flows, and collaborations between QoS flows. For example, the first information may indicate a QoS flow index or a QoS flow list associated with QoS flow 1. For another example, the first information may indicate whether a QoS flow is marked, where a marked QoS flow has synchronization or collaboration requirements, while an unmarked QoS flow does not have synchronization or collaboration requirements.

[0345] In step S820, the first device performs related operations based on the first information.

[0346] In an embodiment of the present application, the above-mentioned related operations may include one or more of the following: the first device configures the QoS flow associated with the first information based on the first information; the first device schedules the QoS flow associated with the first information based on the first information. For example, the first device allocates resources for the QoS flow associated with the first information based on the first information.

[0347] In some implementations, QoS flows with multimodal requirements (or QoS flows with synchronous transmission or collaborative transmission requirements) can be mapped to the same data radio bearer DRB, which helps avoid affecting the lower layers (such as PDCP layer, RLC layer, MAC layer) of the second device and reduces the complexity of terminal device implementation.

[0348] In some implementations, one or more of the following methods 1 to 3 may be used to map the QoS flows associated with the first information to the same DRB.

[0349] Method 1: Map the QoS flow associated with the first information to a DRB through RRC configuration. For example, in an SDAP configuration, all QoS flows with simultaneous transmission requirements or coordinated transmission requirements are associated with a DRB / SDAP configuration. In other words, in the SDAP configuration corresponding to a DRB, QoS flows with simultaneous transmission requirements or coordinated transmission requirements are added to the mappedQoS-FlowsToAdd IE.

[0350] In some implementations, when a QoS flow among QoS flows with synchronous transmission requirements or cooperative transmission requirements is deleted from the SDAP configuration, other QoS flows associated with the QoS flow in the SDAP configuration are also deleted, where the other QoS flows have synchronous transmission requirements or cooperative transmission requirements with the QoS flow.

[0351] Method 2: Associate the QoS flow associated with the first information to a default data radio bearer (default DRB) through RRC configuration. For example, in the SDAP configuration, all QoS flows with synchronous transmission requirements or coordinated transmission requirements are associated with the default data radio bearer. In other words, in the SDAP configuration corresponding to a default data radio bearer, all flows with synchronous transmission requirements or coordinated transmission requirements are added to the mappedQoS-FlowsToAdd IE.

[0352] In some implementations, when a QoS flow among QoS flows with synchronous transmission requirements or cooperative transmission requirements is deleted from the SDAP configuration, other QoS flows associated with the QoS flow in the SDAP configuration are also deleted, where the other QoS flows have synchronous transmission requirements or cooperative transmission requirements with the QoS flow.

[0353] Method 3: Use the DL SDAP header to indicate the mapping relationship between the QoS flow and the DRB. For example, according to the indication of the DL SDAP header, the terminal device performs the uplink reflective mapping between the QoS flow and the DRB (UL reflective mapping between QoS flow and DRB). That is to say, when the terminal device receives the DL SDAP data PDU, its DL SDAP header carries QFI and RDI indicates a specific value (such as a specific value of 1, indicating that the mapping relationship between the DRB and the QoS flow needs to be updated, or indicating that the mapping rules between the QoS flow and the DRB need to be stored). Accordingly, the terminal device performs the uplink reflective mapping between the QoS flow and the DRB based on the RDI, or modifies the mapping relationship between the UL QoS flow and the DRB.

[0354] In some implementations, when the QoS flow associated with the first information is mapped to the same DRB, the network device can configure the first parameter based on the mapping relationship between the QoS flow and the DRB or the first information, wherein the first parameter includes at least one of the following: a priori bit rate (PBR), a parameter BSD (bucketSizeDuration) indicating the depth of the token bucket, which helps to ensure that QoS flows with multimodal requirements or their data can be transmitted synchronously or collaboratively.

[0355] In other implementations, mapping QoS flows with multimodal requirements to different DRBs helps avoid impact on higher layers (such as the SDAP layer).

[0356] In some implementations, when mapped to different DRBs, one or more of the LCH configuration parameters, PDCP configuration parameters, and DRB configuration parameters corresponding to these DRBs are the same or similar, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0357] In some implementations, when mapped to different DRBs, the LCP mapping restrictions corresponding to these DRBs are the same or similar, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0358] In some implementations, when mapped to different DRBs, data with multimodal requirements can reuse the same MAC PDU, or data multiplexing from LCH to MAC PDU can be performed with the same LCH priority, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0359] It should be understood that the solution of the embodiment of the present application can be applicable to the SL scenario. In this case, the terminal device can report multimodal information of the QoS flow of the SL UE to the network device SL (as an example of the first information). In some implementations, the network device instructs the UE to send the first information in the configuration information "sl-AssistanceConfigNR". In some implementations, the UE can use the information "sl-UE-AssistanceInformationNR" or add other UE assistance information IE to indicate the first information.

[0360] In an embodiment of the present application, a method is introduced for enabling a first device to obtain UL / DL multimodal requirements (as an example of first information) through a control plane to perform multimodal transmission, which helps to achieve coordinated transmission or synchronous transmission.

[0361] Figure 9 is a schematic flowchart of a wireless communication method in embodiment 2 of the present application. The method shown in Figure 9 includes step S910 and step S920.

[0362] In step S910, the second device sends first information (also called "multimodal information or demand") to the first device.

[0363] In some implementations, the first information may be sent to the first device when the second device obtains the first information. In other implementations, the second device may notify the first device of the first information when the first device requests to obtain the first information.

[0364] In some implementations, the terminal device may indicate to the base station whether the terminal device supports reporting of the first information. In the embodiment of the present application, only the second device that supports reporting of the first information may report the first information, which facilitates compatibility with second devices of different capabilities. In addition, the solution of the embodiment of the present application does not require all second devices to support the function of reporting the first information, which helps reduce the complexity of the second devices.

[0365] In some implementations, the access network device instructs the UE to report the first information in one or more information of RRC configuration, DL MAC CE, and DCI.

[0366] In some implementations, the access network device instructs or enables the second device to report the first information in one or more information of RRC configuration, DL MAC CE, and DCI.

[0367] In some implementations, the access network device indicates in one or more information in the RRC configuration, DL MAC CE, and DCI that the first information for a specific QoS flow index or QoS flow list should be reported, which helps to avoid the second device reporting the first information for all QoS flows, or in other words, helps to avoid the situation where the second device reports the first information that the first device does not care about, thereby improving the utilization of transmission resources for transmitting the first information.

[0368] Implementation method 1: The terminal device reports the first information.

[0369] In some implementations, the terminal device may determine to send the first information based on a predefined or preconfigured manner. Of course, in the embodiment of the present application, after obtaining the first information, the terminal device may report the first information to the first device.

[0370] In an embodiment of the present application, after obtaining the first information, the terminal device may include one or more of the following: the upper layer of the terminal device sends the first information to the lower layer of the terminal device; the first information is obtained through the UE; the first information is carried in the header information of the data packet sent to the terminal device, etc.; the core network device informs the terminal device of the first information, for example, the core network device may send the first information to the terminal device through NAS signaling.

[0371] In some implementations, the terminal device UE reports the first information through data plane information, where the data plane information may include one or more of the following: SDAP control PDU, SDAP data PDU, MAC PDU, MAC CE, and UCI.

[0372] In the embodiment of the present application, since the terminal device is more aware of the requirements or information of the uplink transmission, the terminal device reporting the first information helps to reflect the needs and characteristics of the service more accurately and timely.

[0373] In some implementations, the first information is carried via an SDAP control PDU. Since the mapping between the QoS flow and the DRB is implemented at the SDAP layer, carrying the first information via an SDAP control PDU can reduce the impact on other layers while maximizing the reuse of the existing architecture.

[0374] In addition, carrying the first information in the form of an SDAP control PDU helps avoid introducing a new data PDU format and reduces the complexity of the second device.

[0375] In some implementations, the first information is carried by the SDAP control PDU, and the first information is used to indicate one or more of the following: whether the QoS flow is marked; information of the QoS flow associated with the first QoS flow); used to indicate a QoS flow that needs to be mapped to a DRB; used to indicate a QoS flow with an associated or binding relationship.

[0376] In some implementations, transmitting the first information through SDAP control PDU can be used when the network configuration UE is enabled. Of course, in the example of the present application, transmitting the first information through SDAP control PDU can be predefined by the protocol, or the second device with the first information reporting capability can transmit the first information through SDAP control PDU, or the second device with the first information reporting capability to be transmitted can transmit the first information through SDAP control PDU, or the second device of a specific version can transmit the first information through SDAP control PDU.

[0377] To distinguish an SDAP control PDU, the R bit in the existing SDAP control PDU is used to indicate that the control PDU is a new SDAP control PDU, i.e., an SDAP control PDU carrying the first information. For example, as shown in Figure 3, the R bit in the End-Marker Control PDU is reused. If the R bit indicates 1, it indicates that the SDAP control PDU is not an End-Marker Control PDU, or indicates that the SDAP control PDU is an SDAP control PDU carrying the first information. Accordingly, the receiving end cannot ignore the R bit in the SDAP control PDU.

[0378] Continuing to refer to Figure 5, the R bit in the End-Marker Control PDU is used. If the R bit indicates 1, it means that the control PDU is not an End-Marker Control PDU. For compatibility with the previous item, a PDU type can be introduced to indicate the type of control PDU corresponding to the case where the R bit is 1. The PDU type can occupy 1, 2, 3, or X bits. When PDU type = 00, it can be identified as a control PDU carrying the first information. Accordingly, the receiving end cannot ignore the R bit in the control PDU.

[0379] Of course, in an embodiment of the present application, if the UE supports reporting the first information, the receiving end cannot ignore the R bit in the SDAP control PDU, and / or, if the network device instructs the terminal device to report the first information, the receiving end cannot ignore the R bit in the SDAP control PDU.

[0380] In some implementations, the UE UL may carry first information in the SDAP control PDU, wherein the first information is used to indicate one or more of the following: indicating an association relationship between QoS flows; the first information indicates that the corresponding QoS flow in the control PDU needs to be updated or mapped to a DRB; instructing the network to update the mapping relationship between QoS flows and DRBs.

[0381] In some implementations, when the UE receives an ACK reply from the base station for the control PDU, or when the UE sends an SDAP control PDU, the UE SDAP performs one or more of the following: storing the updated mapping relationship; updating the mapping relationship between the QoS flow and the DRB; sending an End-Marker Control PDU to the lower layer, where the lower layer may be, for example, the PDCP layer.

[0382] In some implementations, the first information is carried by an SDAP data PDU. Since QoS flow and DRB mapping are currently implemented at the SDAP layer, carrying the first information by an SDAP data PDU can reduce the impact on other layers while reusing the existing architecture as much as possible.

[0383] In some implementations, a new SDAP data PDU is introduced, where the SDAP data PDU is a UL PDU and is used to indicate the first information.

[0384] In some implementations, the SDAP data PDU is used when the network configures the UE to enable it. For example, if the network device configures the UE to carry an SDAP data PDU with an SDAP header and report the first information, the SDAP data PDU is enabled. For another example, if the network device configures the UE to carry an SDAP data PDU with an enhanced SDAP header and report the first information, the SDAP data PDU is enabled.

[0385] On the contrary, if the network device does not configure the terminal device to carry an SDAP data PDU with an enhanced SDAP header and / or report the first information, the terminal device sends the data according to known rules. For example, if the network device configures the SDAP header for the terminal device, the terminal device sends the data according to the format of 6.2.2.3 of the SDAP specification. For another example, if the network device does not configure the SDAP header, the terminal device sends the data according to the format of 6.2.2.1 of the SDAP specification.

[0386] Of course, in the embodiments of the present application, the protocol may predefine the enabling of SDAP data PDU. For example, the protocol may predefine the enabling of SDAP data PDU for UEs with the capability to report first information. For another example, the protocol may predefine the enabling of SDAP data PDU for UEs that have first information to be transmitted. For another example, the protocol may predefine the enabling of SDAP data PDU for UEs of a specific version. For another example, the protocol may predefine the enabling of SDAP data PDU for UEs that need to update or report first information.

[0387] Continuing with FIG6 , the new SDAP data PDU includes at least one of the following information: a D / C identifier, used to indicate whether the SDAP PDU is a control PDU or a data PDU); a QoS flow identifier (such as QFI); a QoS flow associated with the QoS flow of the QFI (or, an identifier of a QoS flow that needs to be mapped to a DRB (QFI or QFI list), or whether the QoS flow corresponding to the QFI is a marked QoS flow); an RDI indication, used to indicate whether the (UL) QoS flow to DRB mapping rule is updated; an RQI indication, used to indicate whether to notify the CN NAS that the UL needs to update the SDF to QoS flow mapping. In addition, indicating the identifier of the DRB to which the QoS flow needs to be mapped in the data PDU and directly indicating the DRB to be mapped in the SDAP data PDU helps to reduce the complexity of the second device.

[0388] In other implementations, referring to FIG. 7 , the D / C identifier is used to indicate whether the SDAP PDU is a control PDU or a data PDU); the QoS flow identifier (such as QFI); the QoS flow associated with the QoS flow of the QFI (or, the identifier of the QoS flow that needs to be mapped to a DRB (QFI or QFI list), or whether the QoS flow corresponding to the QFI is a marked QoS flow); the RDI indication is used to indicate whether the (UL) QoS flow to DRB mapping rule is updated; the RQI indication is used to indicate whether to notify the CN NAS that the UL needs to update the SDF to QoS flow mapping. In addition, if the associated QoS flows need to be mapped to a DRB, for example, QoS flow 1 and QoS flow 2 are mapped to DRB1, then new data PDUs are sent using DRB1 for both QoS flow 1 and QoS flow 2, indicating that both QoS flow 1 and QoS flow 2 will be mapped to DRB1. Alternatively, assuming that QoS flow 1 has been mapped to DRB1, a new data PDU is sent for QoS flow 2 using DRB1, indicating that QoS flow 2 will also be mapped to DRB1. The SDAP data PDU in the embodiment of the present application can reuse the existing format as much as possible.

[0389] In some implementations, if the first information is carried by the SDAP data PDU and the SDAP data PDU includes specific information (such as RDI=1), the UE SDAP stores the updated mapping relationship (the mapping relationship between the QoS flow and the DRB) and sends an End-Marker Control PDU to the lower layer (e.g., PDCP).

[0390] In some implementations, the first information may be carried by a MAC PDU, for example, in a MAC PDU or using a MAC CE in the MAC PDU to carry the first information.

[0391] Implementation method 2: The core network device reports the first information.

[0392] In some implementations, the core network device may carry the first information in a packet header. For example, the packet header may indicate an identifier of an associated data packet and / or an identifier of a QoS flow. For another example, the packet header may indicate whether the data packet, or the QoS flow of the data packet, is marked.

[0393] In this application example, when the CN is able to obtain UL service information (i.e., the first information), the first information is sent to the access network device using existing signaling and process interaction as much as possible, thereby avoiding the terminal device reporting the first information and causing an increase in air interface signaling overhead. In addition, the core network device notifies the base station of both UL and DL related information to reduce the signaling overhead of the CN in transmitting the first information.

[0394] In some implementations, the first information may be used to indicate one or more of the following: associations between QoS flows, bindings between QoS flows, synchronizations between QoS flows, and collaborations between QoS flows. For example, the first information may indicate a QoS flow index or a QoS flow list associated with QoS flow 1. For another example, the first information may indicate whether a QoS flow is marked, where a marked QoS flow has synchronization or collaboration requirements, while an unmarked QoS flow does not have synchronization or collaboration requirements.

[0395] In step S920, the first device performs related operations based on the first information.

[0396] In an embodiment of the present application, the above-mentioned related operations may include one or more of the following: the first device configures the QoS flow associated with the first information based on the first information; the first device schedules the QoS flow associated with the first information based on the first information. For example, the first device allocates resources for the QoS flow associated with the first information based on the first information.

[0397] In some implementations, QoS flows with multimodal requirements (or QoS flows with synchronous transmission or collaborative transmission requirements) can be mapped to the same data radio bearer DRB, which helps avoid affecting the lower layers (such as PDCP layer, RLC layer, MAC layer) of the second device and reduces the complexity of terminal device implementation.

[0398] In some implementations, one or more of the following methods 1 to 3 may be used to map the QoS flows associated with the first information to the same DRB.

[0399] Method 1: Map the QoS flow associated with the first information to a DRB through RRC configuration. For example, in an SDAP configuration, all QoS flows with simultaneous transmission requirements or coordinated transmission requirements are associated with a DRB / SDAP configuration. In other words, in the SDAP configuration corresponding to a DRB, QoS flows with simultaneous transmission requirements or coordinated transmission requirements are added to the mappedQoS-FlowsToAdd IE.

[0400] In some implementations, when a QoS flow among QoS flows with synchronous transmission requirements or cooperative transmission requirements is deleted from the SDAP configuration, other QoS flows associated with the QoS flow in the SDAP configuration are also deleted, where the other QoS flows have synchronous transmission requirements or cooperative transmission requirements with the QoS flow.

[0401] Method 2: Associate the QoS flow associated with the first information to a default data radio bearer (default DRB) through RRC configuration. For example, in the SDAP configuration, all QoS flows with synchronous transmission requirements or coordinated transmission requirements are associated with the default data radio bearer. In other words, in the SDAP configuration corresponding to a default data radio bearer, all flows with synchronous transmission requirements or coordinated transmission requirements are added to the mappedQoS-FlowsToAdd IE.

[0402] In some implementations, when a QoS flow among QoS flows with synchronous transmission requirements or cooperative transmission requirements is deleted from the SDAP configuration, other QoS flows associated with the QoS flow in the SDAP configuration are also deleted, where the other QoS flows have synchronous transmission requirements or cooperative transmission requirements with the QoS flow.

[0403] Method 3: Use the DL SDAP header to indicate the mapping relationship between the QoS flow and the DRB. For example, according to the indication of the DL SDAP header, the terminal device performs the uplink reflective mapping between the QoS flow and the DRB (UL reflective mapping between QoS flow and DRB). That is to say, when the terminal device receives the DL SDAP data PDU, its DL SDAP header carries QFI and RDI indicates a specific value (such as a specific value of 1, indicating that the mapping relationship between the DRB and the QoS flow needs to be updated, or indicating that the mapping rules between the QoS flow and the DRB need to be stored). Accordingly, the terminal device performs the uplink reflective mapping between the QoS flow and the DRB based on the RDI, or modifies the mapping relationship between the UL QoS flow and the DRB.

[0404] In some implementations, when the QoS flow associated with the first information is mapped to the same DRB, the network device can configure the first parameter based on the mapping relationship between the QoS flow and the DRB or the first information, wherein the first parameter includes at least one of the following: a priori bit rate (PBR), a parameter BSD (bucketSizeDuration) indicating the depth of the token bucket, which helps to ensure that QoS flows with multimodal requirements or their data can be transmitted synchronously or collaboratively.

[0405] In other implementations, mapping QoS flows with multimodal requirements to different DRBs helps avoid impact on higher layers (such as the SDAP layer).

[0406] In some implementations, when mapped to different DRBs, one or more of the LCH configuration parameters, PDCP configuration parameters, and DRB configuration parameters corresponding to these DRBs are the same or similar, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0407] In some implementations, when mapped to different DRBs, the LCP mapping restrictions corresponding to these DRBs are the same or similar, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0408] In some implementations, when mapped to different DRBs, data with multimodal requirements can reuse the same MAC PDU, or data multiplexing from LCH to MAC PDU can be performed with the same LCH priority, which helps to achieve coordinated transmission or synchronous transmission of multimodal services.

[0409] It should be understood that the solution of the embodiment of the present application can be applicable to the SL scenario. In this case, the terminal device can report multimodal information of the QoS flow of the SL UE to the network device SL (as an example of the first information). In some implementations, the network device instructs the UE to send the first information in the configuration information "sl-AssistanceConfigNR". In some implementations, the UE can use the information "sl-UE-AssistanceInformationNR" or add other UE assistance information IE to indicate the first information.

[0410] In an embodiment of the present application, a solution for transmitting the first information via a user plane is introduced, which helps to achieve synchronous transmission or coordinated transmission of QoS flows associated with the first information.

[0411] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 9 . The device embodiment of the present application is described in detail below in conjunction with Figures 10 to 12 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0412] FIG10 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1000 shown in FIG10 is a second device, and the communication device 1000 includes a sending unit 1010 .

[0413] The sending unit 1010 is configured to send first information to a first device, where the first information is associated with synchronous transmission or coordinated transmission of at least one object.

[0414] In some implementations, the first information is used to indicate one or more of the following: whether there is a synchronous transmission requirement for the at least one object; whether there is a collaborative transmission requirement for the at least one object; the synchronous transmission parameters of the at least one object; the collaborative transmission parameters of the at least one object; the identification information corresponding to the at least one object; the type corresponding to the at least one object; whether the at least one object corresponds to the target identification information; whether the at least one object corresponds to the target type; the synchronous transmission requirement between at least two objects; the collaborative transmission requirement between at least two objects; the synchronous transmission parameters between at least two objects; the collaborative transmission parameters between at least two objects; synchronous transmission between at least two objects; collaborative transmission between at least two objects; whether at least two objects correspond to the same identification information; whether at least two objects correspond to the same type; whether at least two objects correspond to the target identification information; whether at least two objects correspond to the target type; the association relationship between at least two objects; the binding relationship between at least two objects; wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

[0415] In some implementations, the object in the at least one object includes one of the following: quality of service QoS flow, data flow, terminal device, protocol data unit PDU session, and radio bearer.

[0416] In some implementations, the identification information includes one or more of the following: identification information of a target object, where the target object is part or all of the objects in the at least one object; identification information of the first object in the at least one object; identification information of each object in the at least one object; and identification information for identifying at least two objects, wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

[0417] In some implementations, the sending of the first information is triggered based on one or more of: a period; a first event; a request message sent by the first device; an enable indication, the enable indication is used to enable the second device to send the first information; the capability of the second device, the capability is associated with the synchronous transmission or collaborative transmission of at least one object; whether the first device obtains the first information; whether the second device has available or valid first information.

[0418] In some implementations, the first event includes one or more of the following: exceeding a first duration; the second device being configured to send the first information of the at least one object; the first information of the at least one object has not been sent; the demand for synchronous transmission of the at least one object has changed; the demand for cooperative transmission of the at least one object has changed; the parameters of synchronous transmission of the at least one object have changed; the parameters of cooperative transmission of the at least one object have changed; the identifier of synchronous transmission of the at least one object has changed; the type of synchronous transmission of the at least one object has changed; the identifier of cooperative transmission of the at least one object has changed; the type of cooperative transmission of the at least one object has changed; the identifier of synchronous transmission between the at least two objects has changed; the type of synchronous transmission between the at least two objects has changed; the identifier of cooperative transmission between the at least two objects has changed; the type of cooperative transmission between the at least two objects has changed; The demand for collaborative transmission changes; the demand for synchronous transmission between the at least two objects changes; the collaborative transmission parameters between the at least two objects change; the synchronous transmission parameters between the at least two objects change; the change in the demand for synchronous transmission of at least one object is greater than or equal to the first change threshold; the change in the demand for collaborative transmission of at least one object is greater than or equal to the second change threshold; the change in the parameter for synchronous transmission of at least one object is greater than or equal to the third change threshold; the change in the parameter for collaborative transmission of at least one object is greater than or equal to the fourth change threshold; the change in the parameter for synchronous transmission between the at least two objects is greater than or equal to the fifth change threshold; the change in the parameter for collaborative transmission between the at least two objects is greater than or equal to the sixth change threshold; the change in the demand for synchronous transmission between the at least two objects is greater than or equal to the seventh change threshold; the change in the demand for collaborative transmission between the at least two objects is greater than or equal to the eighth change threshold.

[0419] In some implementations, the first duration is a duration during which the transmission of the first information is prohibited or not allowed; or the first duration is a duration during which the transmission of the first information of the at least one object is prohibited or not allowed.

[0420] In some implementations, a configuration granularity of the first duration is one of the at least one object; and / or usage of the first duration is for one of the at least one object.

[0421] In some implementations, the object associated with the configuration granularity is different from the object targeted by the use of the first duration, or the object associated with the configuration is the same as the object targeted by the use of the first duration.

[0422] In some implementations, the first duration is determined based on a first timer, the first event includes the first timer timing out, and / or the first timer is not running.

[0423] In some implementations, the first timer is started or restarted when the first information is sent.

[0424] In some implementations, the request message is used to request one or more of the following: a requirement for synchronous transmission of a target object; a requirement for collaborative transmission of the target object; parameters for synchronous transmission of the target object; parameters for collaborative transmission of the target object; an identifier of the target object; a type of the target object; a requirement for synchronous transmission between at least two objects; a requirement for collaborative transmission between at least two objects; parameters for synchronous transmission between at least two objects; parameters for collaborative transmission between at least two objects; wherein the target object includes all or part of the at least one object; if the at least one object includes multiple objects, including the at least two objects.

[0425] In some implementations, the request message includes one or more of the following: identification information of the object requested by the request message; a first duration associated with the first information; a reporting period of the first information; a change threshold of the transmission requirement of synchronous transmission or the transmission requirement of collaborative transmission, a change threshold of the transmission parameters of synchronous transmission or the transmission parameters of collaborative transmission; and a first timer configuration.

[0426] In some implementations, the request message is carried in one or more of the following: system information, paging message, radio resource control RRC message, uplink control information UCI, media access control element MAC CE, and non-access stratum NAS message.

[0427] In some implementations, the first information is carried in control plane information, or the first information is transmitted via control plane information.

[0428] In some implementations, the control plane information includes one or more of the following: RRC message, NAS message, and user equipment UE assistance information.

[0429] In some implementations, the control plane information carries identification information, or the first information is carried in sub-information of the control plane information, and the sub-information carries identification information; wherein, the identification information includes one or more of the following: identification information of the target object, the target object is part or all of the objects in the at least one object; identification information of the first object in the at least one object; identification information of each object in the at least one object; identification information of at least two objects, if the at least one object is multiple objects, the at least two objects belong to the multiple objects.

[0430] In some implementations, the identification information includes one or more of the following: identification information of the user equipment, identification information of the wireless bearer, index of the DRB, QoS flow identifier QFI, identification information of the data flow, index of the data flow, identification information of the PDU session, and index of the PDU session.

[0431] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device.

[0432] In some implementations, the control plane information includes one or more of the following: QoS configuration information, information carrying QoS parameters, and time-sensitive communication TSC assistance information.

[0433] In some implementations, the first information is sent by a policy control function PCF or an application function AF to a session management function SMF, or the first information is carried by the PCF or AF through delay-sensitive communication assistance container TSCAC information.

[0434] In some implementations, the first device is an access network device, and the second device is a core network device.

[0435] In some implementations, the first information is carried in user plane information, or the first information is transmitted via user plane information.

[0436] In some implementations, the user plane information includes one or more of the following: a first data packet; a Service Data Adaptation Protocol (SDAP) protocol data unit (PDU), a Packet Data Convergence Protocol (PDCP) PDU; a MAC CE, a MAC PDU, and an UCI.

[0437] In some implementations, the first information is carried via a header of the user plane information, or the first information is carried via a payload of the user plane information.

[0438] In some implementations, the user plane information carries second information, and the second information is used to indicate that the user plane information carries the first information.

[0439] In some implementations, the at least one object includes at least one QoS flow, and the SDAP PDU includes a first field, which is used to carry one or more of the following: an identifier of the at least one QoS flow; a type of the at least one QoS flow; an indication of whether the QoS flow corresponding to the first field is the QoS flow associated with the first information; the synchronous transmission requirement of the at least one QoS flow; the collaborative transmission requirement of the at least one QoS flow; the synchronous transmission parameters of the at least one QoS flow; the collaborative transmission parameters of the at least one QoS flow; an identifier of the QoS flow associated with the first information; an identifier of a QoS flow with a synchronous transmission requirement, the QoS flow with a synchronous transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a collaborative transmission requirement, the QoS flow with a collaborative transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a synchronous transmission parameter, the QoS flow with a synchronous transmission parameter includes the at least one QoS flow; an identifier of a QoS flow with a collaborative transmission parameter, the QoS flow with a collaborative transmission parameter includes the at least one QoS flow.

[0440] In some implementations, the SDAP PDU is the SDAP control PDU or the SDAP data PDU.

[0441] In some implementations, the first information is carried in a first data packet, and the first data packet satisfies one or more of the following: the first data packet corresponds to the at least one object associated with the first information; the QoS flow of the first data packet is associated with the at least one object; the PDU session of the first data packet is associated with the at least one object; the data flow of the first data packet is associated with the at least one object; and the bearer corresponding to the first data packet is associated with the at least one object.

[0442] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device; or the first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device or a terminal device.

[0443] In some implementations, the at least one object satisfies one or more of the following: the QoS flow associated with the at least one object is carried through the same DRB; the QoS flow associated with the at least one object is carried through different DRBs; the QoS flow associated with the at least one object is carried through the same LCH; the QoS flow associated with the at least one object is carried through different LCHs; the QoS flow associated with the at least one object is carried through different logical channel groups LCG; the DRB or bearer associated with the at least one object is mapped to the same LCH; the DRB or bearer associated with the at least one object is mapped to the same LCG; the DRB or bearer associated with the at least one object is mapped to different LCHs; the DRB or bearer associated with the at least one object is mapped to different LCGs.

[0444] In some implementations, the different DRBs include multiple DRBs, and the multiple DRBs satisfy one or more of the following: the configuration parameters of at least two DRBs among the multiple DRBs match; the mapping restrictions of the logical channel priorities LCPs corresponding to at least two DRBs among the multiple DRBs match.

[0445] In some implementations, the different LCHs include multiple LCHs, and configuration parameters of at least two LCHs in the multiple LCHs match.

[0446] In some implementations, the different LCGs include multiple LCGs, and the multiple LCGs satisfy one or more of the following: configuration parameters of at least two LCGs in the multiple LCGs match; configuration parameters of LCHs in the multiple LCGs match.

[0447] In some implementations, the at least one object satisfies one or more of the following: the data or data packets associated with the at least one object multiplex the same MAC PDU; the data or data packets associated with the at least one object multiplex multiple consecutive MAC PDUs; the data or data packets associated with the at least one object are transmitted synchronously to the first device; the data or data packets associated with the at least one object are transmitted to the first device within a target time period.

[0448] In some implementations, the at least one object includes multiple objects, the multiple objects include at least two objects, and the at least two objects satisfy one or more of the following: the data or data packets associated with the at least two objects multiplex the same MAC PDU; the data or data packets associated with the at least two objects multiplex multiple consecutive MAC PDUs; the data or data packets associated with the at least two objects are transmitted synchronously to the first device; the data or data packets associated with the at least two objects are transmitted to the first device within a target time period.

[0449] In some implementations, one or more objects among the at least one object are target objects, and the target objects satisfy one or more of the following: the data or data packets associated with the target object multiplex the same MAC PDU; the data or data packets associated with the target object multiplex multiple consecutive MAC PDUs; the data or data packets associated with the target object are transmitted synchronously to the first device; the data or data packets associated with the target object are transmitted to the first device within a target time period.

[0450] In some implementations, the sending unit is further used to send third information to the first device, and the third information is used to indicate one or more of the following: part or all of the objects in the target object to be transmitted; data or data packets associated with the target object to be transmitted; the size of the transmission resources required to transmit the target object; the size of the transmission resources required to transmit the objects to be transmitted in the target object; data volume information of the objects to be transmitted in the target object; the remaining delay of the data of the objects to be transmitted in the target object; the allowed delay of the data of the objects to be transmitted in the target object; data volume information of the objects corresponding to the target remaining delay in the objects to be transmitted of the target object; data volume information of the objects corresponding to the target allowed delay in the objects to be transmitted of the target object; data volume information of the objects corresponding to the delay status reporting information in the objects to be transmitted of the target object; wherein, the target object is the at least one object, or the target object is one or more objects among the at least one object.

[0451] In some implementations, the sending unit is used to send the third information when a first condition is satisfied, wherein the first condition includes one or more of the following: at least one object cannot reuse the same MAC PDU; at least one object cannot reuse multiple consecutive MAC PDUs; at least one object cannot be transmitted synchronously to the first device; at least one object cannot be transmitted to the first device within a target time period.

[0452] In some implementations, the data associated with the third information satisfies one or more of the following: the scheduling priority of the data associated with the third information is higher than the scheduling priority of the first data; the transmission priority of the data associated with the third information is higher than the transmission priority of the first data; the LCH priority of the data associated with the third information is higher than the LCH priority of the first data; the multiplexing priority of the data associated with the third information is higher than the multiplexing priority of the first data, wherein the first data is the data to be transmitted other than the data associated with the third information.

[0453] In some implementations, the data associated with the first information satisfies one or more of the following: the scheduling priority of the data associated with the first information is higher than the scheduling priority of the second data; the transmission priority of the data associated with the first information is higher than the transmission priority of the second data; the LCH priority of the data associated with the first information is higher than the LCH priority of the second data; the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of the second data, wherein the second data is data to be transmitted other than the data associated with the first information.

[0454] In some implementations, the data associated with the first information may include data of the at least one object or data in a data packet of the at least one object.

[0455] In some implementations, the LCH priorities associated with the at least one object are the same or similar.

[0456] In some implementations, the sending unit is used to send fourth information to the first device, where the fourth information is used to indicate whether the second device supports transmission of the first information, or the fourth information is used to indicate whether the second device has available first information.

[0457] In some implementations, the first device is an access network device, and the second device is a terminal device or a first core network device, or the first device is a second core network device, and the second device is a terminal device or a first core network device.

[0458] FIG11 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 1100 shown in FIG11 is a first device, and the communication device 1100 includes a receiving unit 1110 .

[0459] The receiving unit 1110 is configured to receive first information sent by a second device, where the first information is associated with synchronous transmission or coordinated transmission of at least one object.

[0460] In some implementations, the first information is used to indicate one or more of the following: whether there is a synchronous transmission requirement for the at least one object; whether there is a collaborative transmission requirement for the at least one object; the synchronous transmission parameters of the at least one object; the collaborative transmission parameters of the at least one object; the identification information corresponding to the at least one object; the type corresponding to the at least one object; whether the at least one object corresponds to the target identification information; whether the at least one object corresponds to the target type; the synchronous transmission requirement between at least two objects; the collaborative transmission requirement between at least two objects; the synchronous transmission parameters between at least two objects; the collaborative transmission parameters between at least two objects; synchronous transmission between at least two objects; collaborative transmission between at least two objects; whether at least two objects correspond to the same identification information; whether at least two objects correspond to the same type; whether at least two objects correspond to the target identification information; whether at least two objects correspond to the target type; the association relationship between at least two objects; the binding relationship between at least two objects; wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

[0461] In some implementations, the object in the at least one object includes one of the following: quality of service QoS flow, data flow, terminal device, protocol data unit PDU session, and radio bearer.

[0462] In some implementations, the first information includes identification information, and the identification information includes one or more of the following: identification information of a target object, where the target object is part or all of the objects in the at least one object; identification information of the first object in the at least one object; identification information of each object in the at least one object; and identification information for identifying at least two objects, wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

[0463] In some implementations, the sending of the first information is triggered based on one or more of: a period; a first event; a request message sent by the first device; an enable indication, the enable indication is used to enable the second device to send the first information; the capability of the second device, the capability is associated with the synchronous transmission or collaborative transmission of at least one object; whether the first device obtains the first information; whether the second device has available or valid first information.

[0464] In some implementations, the first event includes one or more of the following: exceeding a first duration; the second device being configured to send the first information of the at least one object; the first information of the at least one object has not been sent; the first information of the at least one object has not been sent; the need for synchronous transmission of the at least one object; the need for collaborative transmission of the at least one object has changed; the parameters of synchronous transmission of the at least one object have changed; the parameters of collaborative transmission of the at least one object have changed; the identifier of synchronous transmission of the at least one object has changed; the type of synchronous transmission of the at least one object has changed; the identifier of collaborative transmission of the at least one object has changed; the type of collaborative transmission of the at least one object has changed; the identifier of synchronous transmission between the at least two objects has changed; the type of synchronous transmission between the at least two objects has changed; the identifier of collaborative transmission between the at least two objects has changed; the type of collaborative transmission between the at least two objects has changed; the The demand for synchronous transmission between at least two objects changes; the demand for collaborative transmission between the at least two objects changes; the parameters of synchronous transmission between the at least two objects change; the parameters of collaborative transmission between the at least two objects change; the change in the demand for synchronous transmission of at least one object is greater than or equal to the first change threshold; the change in the demand for collaborative transmission of at least one object is greater than or equal to the second change threshold; the change in the parameters for synchronous transmission of at least one object is greater than or equal to the third change threshold; the change in the parameters for collaborative transmission of at least one object is greater than or equal to the fourth change threshold; the change in the parameters for synchronous transmission between the at least two objects is greater than or equal to the fifth change threshold; the change in the parameters for collaborative transmission between the at least two objects is greater than or equal to the sixth change threshold; the change in the demand for synchronous transmission between the at least two objects is greater than or equal to the seventh change threshold; the change in the demand for collaborative transmission between the at least two objects is greater than or equal to the eighth change threshold.

[0465] In some implementations, the first duration is a duration during which the transmission of the first information is prohibited or not allowed; or the first duration is a duration during which the transmission of the first information of the at least one object is prohibited or not allowed.

[0466] In some implementations, a configuration granularity of the first duration is one of the at least one object; and / or usage of the first duration is for one of the at least one object.

[0467] In some implementations, the object associated with the configuration granularity is different from the object targeted by the use of the first duration, or the object associated with the configuration is the same as the object targeted by the use of the first duration.

[0468] In some implementations, the first duration is determined based on a first timer, the first event includes the first timer timing out, and / or the first timer not running.

[0469] In some implementations, the first timer is started or restarted when the first information is sent.

[0470] In some implementations, the request message is used to request one or more of the following: a requirement for synchronous transmission of a target object; a requirement for collaborative transmission of the target object; parameters for synchronous transmission of the target object; parameters for collaborative transmission of the target object; an identifier of the target object; a type of the target object; a requirement for synchronous transmission between at least two objects; a requirement for collaborative transmission between at least two objects; parameters for synchronous transmission between at least two objects; parameters for collaborative transmission between at least two objects; wherein the target object includes all or part of the at least one object; if the at least one object includes multiple objects, including the at least two objects.

[0471] In some implementations, the request message includes one or more of the following: identification information of the object requested by the request message; a first duration associated with the first information; a reporting period of the first information; a change threshold of the transmission requirement of synchronous transmission or the transmission requirement of collaborative transmission, a change threshold of the transmission parameters of synchronous transmission or the transmission parameters of collaborative transmission; and a first timer configuration.

[0472] In some implementations, the request message is carried in one or more of the following: system information, paging message, radio resource control RRC message, uplink control information UCI, media access control element MAC CE, and non-access stratum NAS message.

[0473] In some implementations, the first information is carried in control plane information, or the first information is transmitted via control plane information.

[0474] In some implementations, the control plane information includes one or more of the following: RRC message, NAS message, and user equipment UE assistance information.

[0475] In some implementations, the control plane information carries identification information, or the first information is carried in sub-information of the control plane information, and the sub-information carries identification information; wherein, the identification information includes one or more of the following: identification information of the target object, the target object is part or all of the objects in the at least one object; identification information of the first object in the at least one object; identification information of each object in the at least one object; identification information of at least two objects, if the at least one object is multiple objects, the at least two objects belong to the multiple objects.

[0476] In some implementations, the identification information includes one or more of the following: identification information of the user equipment, identification information of the wireless bearer, index of the DRB, QoS flow identifier QFI, identification information of the data flow, index of the data flow, identification information of the PDU session, and index of the PDU session.

[0477] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device.

[0478] In some implementations, the control plane information includes one or more of the following: QoS configuration information, information carrying QoS parameters, and time-sensitive communication TSC assistance information.

[0479] In some implementations, the first information is sent by the PCF or AF to the SMF, or the first information is carried by the PCF or AF through TSCAC information.

[0480] In some implementations, the first device is an access network device, and the second device is a core network device.

[0481] In some implementations, the first information is carried in user plane information, or the first information is transmitted via user plane information.

[0482] In some implementations, the user plane information includes one or more of the following: a first data packet; a Service Data Adaptation Protocol (SDAP) protocol data unit (PDU), a Packet Data Convergence Protocol (PDCP) PDU; a MAC CE, a MAC PDU, and an UCI.

[0483] In some implementations, the first information is carried via a header of the user plane information, or the first information is carried via a payload of the user plane information.

[0484] In some implementations, the user plane information carries second information, and the second information is used to indicate that the user plane information carries the first information.

[0485] In some implementations, the at least one object includes at least one QoS flow, and the SDAP PDU includes a first field, which is used to carry one or more of the following: an identifier of the at least one QoS flow; a type of the at least one QoS flow; an indication of whether the QoS flow corresponding to the first field is the QoS flow associated with the first information; the synchronous transmission requirement of the at least one QoS flow; the collaborative transmission requirement of the at least one QoS flow; the synchronous transmission parameters of the at least one QoS flow; the collaborative transmission parameters of the at least one QoS flow; an identifier of the QoS flow associated with the first information; an identifier of a QoS flow with a synchronous transmission requirement, the QoS flow with a synchronous transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a collaborative transmission requirement, the QoS flow with a collaborative transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a synchronous transmission parameter, the QoS flow with a synchronous transmission parameter includes the at least one QoS flow; an identifier of a QoS flow with a collaborative transmission parameter, the QoS flow with a collaborative transmission parameter includes the at least one QoS flow.

[0486] In some implementations, the SDAP PDU is the SDAP control PDU or the SDAP data PDU.

[0487] In some implementations, the first information is carried in a first data packet, and the first data packet satisfies one or more of the following: the first data packet corresponds to the at least one object associated with the first information; the QoS flow of the first data packet is associated with the at least one object; the PDU session of the first data packet is associated with the at least one object; the data flow of the first data packet is associated with the at least one object; and the bearer corresponding to the first data packet is associated with the at least one object.

[0488] In some implementations, the first device is an access network device or a core network device, and the second device is a terminal device; or the first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device or a terminal device.

[0489] In some implementations, the at least one object satisfies one or more of the following: the QoS flow associated with the at least one object is carried through the same DRB; the QoS flow associated with the at least one object is carried through different DRBs; the QoS flow associated with the at least one object is carried through the same LCH; the QoS flow associated with the at least one object is carried through different LCHs; the QoS flow associated with the at least one object is carried through different logical channel groups LCG; the DRB or bearer associated with the at least one object is mapped to the same LCH; the DRB or bearer associated with the at least one object is mapped to the same LCG; the DRB or bearer associated with the at least one object is mapped to different LCHs; the DRB or bearer associated with the at least one object is mapped to different LCGs.

[0490] In some implementations, the different DRBs include multiple DRBs, and the multiple DRBs satisfy one or more of the following: the configuration parameters of at least two DRBs among the multiple DRBs match; the mapping restrictions of the logical channel priorities LCPs corresponding to at least two DRBs among the multiple DRBs match.

[0491] In some implementations, the different LCHs include multiple LCHs, and configuration parameters of at least two LCHs in the multiple LCHs match.

[0492] In some implementations, the different LCGs include multiple LCGs, and the multiple LCGs satisfy one or more of the following: configuration parameters of at least two LCGs in the multiple LCGs match; configuration parameters of LCHs in the multiple LCGs match.

[0493] In some implementations, the at least one object satisfies one or more of the following: the data or data packets associated with the at least one object multiplex the same MAC PDU; the data or data packets associated with the at least one object multiplex multiple consecutive MAC PDUs; the data or data packets associated with the at least one object are transmitted synchronously to the first device; the data or data packets associated with the at least one object are transmitted to the first device within a target time period.

[0494] In some implementations, the at least one object includes multiple objects, the multiple objects include at least two objects, and the at least two objects satisfy one or more of the following: the data or data packets associated with the at least two objects multiplex the same MAC PDU; the data or data packets associated with the at least two objects multiplex multiple consecutive MAC PDUs; the data or data packets associated with the at least two objects are transmitted synchronously to the first device; the data or data packets associated with the at least two objects are transmitted to the first device within a target time period.

[0495] In some implementations, one or more objects among the at least one object are target objects, and the target objects satisfy one or more of the following: the data or data packets associated with the target object multiplex the same MAC PDU; the data or data packets associated with the target object multiplex multiple consecutive MAC PDUs; the data or data packets associated with the target object are transmitted synchronously to the first device; the data or data packets associated with the target object are transmitted to the first device within a target time period.

[0496] In some implementations, the receiving unit is further used to receive third information sent by the second device, and the third information is used to indicate one or more of the following: part or all of the objects in the target object to be transmitted; data or data packets associated with the target object to be transmitted; the size of the transmission resources required to transmit the target object; the size of the transmission resources required to transmit the objects to be transmitted in the target object; data volume information of the objects to be transmitted in the target object; the remaining delay of the data of the objects to be transmitted in the target object; the allowed delay of the data of the objects to be transmitted in the target object; data volume information of the objects corresponding to the target allowed delay in the objects to be transmitted of the target object; data volume information of the objects corresponding to the target remaining delay in the objects to be transmitted of the target object; data volume information of the objects corresponding to the delay status reporting information in the objects to be transmitted of the target object; wherein, the target object is the at least one object, or the target object is one or more objects among the at least one object.

[0497] In some implementations, the first device receives the third information sent by the second device, including: the first condition is met, and the first device receives the third information sent by the second device, wherein the first condition includes one or more of the following: the at least one object cannot reuse the same MAC PDU; the at least one object cannot reuse multiple consecutive MAC PDUs; the at least one object cannot be transmitted to the first device synchronously; the at least one object cannot be transmitted to the first device within the target time period.

[0498] In some implementations, the data associated with the third information satisfies one or more of the following: the scheduling priority of the data associated with the third information is higher than the scheduling priority of the first data; the transmission priority of the data associated with the third information is higher than the transmission priority of the first data; the LCH priority of the data associated with the third information is higher than the LCH priority of the first data; the multiplexing priority of the data associated with the third information is higher than the multiplexing priority of the first data, wherein the first data is the data to be transmitted other than the data associated with the third information.

[0499] In some implementations, the first information is associated with the synchronous transmission or coordinated transmission of data or data packets of the at least one object, and the data associated with the first information satisfies one or more of the following: the scheduling priority of the data associated with the first information is higher than the scheduling priority of the second data; the transmission priority of the data associated with the first information is higher than the transmission priority of the second data; the LCH priority of the data associated with the first information is higher than the LCH priority of the second data; the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of the second data, wherein the second data is data to be transmitted other than the data associated with the first information.

[0500] In some implementations, the LCH priorities associated with the at least one object are the same or similar.

[0501] In some implementations, the receiving unit is further used to receive fourth information sent by the second device, where the fourth information is used to indicate whether the second device supports transmission of the first information, or the fourth information is used to indicate whether the second device has available first information.

[0502] In some implementations, the first device is an access network device, and the second device is a terminal device or a first core network device, or the first device is a second core network device, and the second device is a terminal device or a first core network device.

[0503] In an optional embodiment, the sending unit 1010 may be a transceiver 1230. The communication device 1000 may further include a processor 1210 and a memory 1220, as specifically shown in FIG12 .

[0504] In an optional embodiment, the receiving unit 1110 may be a transceiver 1230. The communication device 1100 may further include a processor 1210 and a memory 1220, as specifically shown in FIG12 .

[0505] Figure 12 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 12 indicate that the unit or module is optional. The device 1200 may be used to implement the method described in the above method embodiment. The device 1200 may be a chip, a terminal device, or a network device.

[0506] The device 1200 may include one or more processors 1210. The processor 1210 may support the device 1200 to implement the method described in the above method embodiment. The processor 1210 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0507] The apparatus 1200 may further include one or more memories 1220. The memories 1220 store programs that can be executed by the processor 1210, causing the processor 1210 to perform the methods described in the above method embodiments. The memories 1220 may be independent of the processor 1210 or integrated into the processor 1210.

[0508] The apparatus 1200 may further include a transceiver 1230. The processor 1210 may communicate with other devices or chips via the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips via the transceiver 1230.

[0509] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0510] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0511] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0512] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0513] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0514] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0515] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0516] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0517] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0518] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0519] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0520] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0521] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0522] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0523] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0524] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for wireless communication, characterized in that, Including: The second device sends first information to the first device, and the first information is associated with synchronous transmission or collaborative transmission of at least one object.

2. The method according to claim 1, characterized in that, The first information is used to indicate one or more of the following: there is a synchronous transmission requirement for the at least one object; there is a collaborative transmission requirement for the at least one object; synchronous transmission parameters of the at least one object; collaborative transmission parameters of the at least one object; identification information corresponding to the at least one object; type corresponding to the at least one object; whether the at least one object corresponds to target identification information; whether the at least one object corresponds to target type; synchronous transmission requirement between at least two objects; collaborative transmission requirement between at least two objects; synchronous transmission parameters between at least two objects; collaborative transmission parameters between at least two objects; synchronous transmission between at least two objects; collaborative transmission between at least two objects; whether at least two objects correspond to the same identification information; whether at least two objects correspond to the same type; whether at least two objects correspond to target identification information; whether at least two objects correspond to target type; association relationship between at least two objects; binding relationship between at least two objects; wherein, if the at least one object includes multiple objects, the multiple objects include the at least two objects.

3. The method according to claim 2, wherein The identification information includes one or more of the following: identification information of a target object, where the target object is part or all of the at least one object; identification information of a first object among the at least one object; identification information of each object among the at least one object; Identification information for identifying at least two objects, wherein, if the at least one object includes multiple objects, the multiple objects include the at least two objects.

4. The method according to any one of claims 1-3, characterized in that, The object in the at least one object is one of the following: Quality of Service (QoS) flow, data flow, terminal device, Protocol Data Unit (PDU) session, radio bearer.

5. The method according to any one of claims 1 to 4, characterized in that The sending of the first information is triggered based on one or more of the following: period; first event; request message sent by the first device; enabling indication for enabling the second device to send the first information; capability of the second device, where the capability is associated with synchronous transmission or collaborative transmission of the at least one object; whether the first device has obtained the first information; whether the second device has available or valid first information.

6. The method according to claim 5, characterized in that, The first event includes one or more of the following: exceeding a first duration; The second device is configured to send the first information of the at least one object; the first information of the at least one object has not been sent yet; the requirement for synchronous transmission or the requirement for collaborative transmission of the at least one object changes; the parameters of synchronous transmission or the parameters of collaborative transmission of the at least one object change; the identifier of synchronous transmission of the at least one object; the type of synchronous transmission of the at least one object changes; the identifier of collaborative transmission of the at least one object; the type of collaborative transmission of the at least one object changes; the identifier of synchronous transmission between the at least two objects changes; the type of synchronous transmission between the at least two objects changes; the identifier of collaborative transmission between the at least two objects changes; the type of collaborative transmission between the at least two objects changes; the requirement for synchronous transmission between the at least two objects changes; the requirement for collaborative transmission between the at least two objects changes; the parameters of synchronous transmission between the at least two objects change; the parameters of collaborative transmission between the at least two objects change; the change amount of the requirement for synchronous transmission of the at least one object is greater than or equal to a first change threshold; the change amount of the requirement for collaborative transmission of the at least one object is greater than or equal to a second change threshold; the change amount of the parameters of synchronous transmission of the at least one object is greater than or equal to a third change threshold; the change amount of the parameters of collaborative transmission of the at least one object is greater than or equal to a fourth change threshold; the change amount of the parameters of synchronous transmission between the at least two objects is greater than or equal to a fifth change threshold; the change amount of the parameters of collaborative transmission between the at least two objects is greater than or equal to a sixth change threshold; the change amount of the requirement for synchronous transmission between the at least two objects is greater than or equal to a seventh change threshold; the change amount of the requirement for collaborative transmission between the at least two objects is greater than or equal to an eighth change threshold.

7. The method according to claim 6, wherein The first duration is the duration during which the transmission of the first information is prohibited or not allowed; or, the first duration is the duration during which the transmission of the first information of the at least one object is prohibited or not allowed.

8. The method according to claim 6 or 7, characterized in that, The configuration granularity of the first duration is one of the at least one object; and / or the use of the first duration is for one of the at least one object.

9. The method according to claim 8, wherein The object associated with the configuration granularity is different from the object for which the first duration is used, or, the object associated with the configuration is the same as the object for which the first duration is used.

10. The method according to any one of claims 6-9, characterized in that, The first duration is determined based on a first timer, and the first event includes the timeout of the first timer, and / or, the first timer is not running.

11. The method according to claim 10, characterized in that, The first timer is started or restarted when sending the first information.

12. The method according to claim 5, wherein The request message is used to request one or more of the following: the requirement for the target object to perform synchronous transmission; the requirement for the target object to perform collaborative transmission; the parameters for the target object to perform synchronous transmission; the parameters for the target object to perform collaborative transmission; the identifier of the target object; the type of the target object; the requirement for at least two objects to perform synchronous transmission; the requirement for at least two objects to perform collaborative transmission; the parameters for at least two objects to perform synchronous transmission; the parameters for at least two objects to perform collaborative transmission; wherein, the target object includes all or part of the at least one object; if the at least one object includes multiple objects, it includes the at least two objects.

13. The method according to any one of claims 5-12, characterized in that, The request message includes one or more of the following: the identifier information of the object requested by the request message; the first duration associated with the first information; the reporting period of the first information; the change threshold of the transmission requirement for synchronous transmission or collaborative transmission, the change threshold of the transmission parameters for synchronous transmission or collaborative transmission; the first timer configuration.

14. The method according to any one of claims 5-13, characterized in that, The request message is carried on one or more of the following: system information, paging message, radio resource control (RRC) message, uplink control information (UCI), media access control control element (MAC CE), non-access stratum (NAS) message.

15. The method according to any one of claims 1 to 14, characterized in that, The first information is carried on the control plane information, or the first information is transmitted through the control plane information.

16. The method according to claim 15, wherein The control plane information includes one or more of the following: RRC message, NAS message, user equipment (UE) assistance information.

17. The method according to claim 15 or 16, characterized in that, The control plane information carries identifier information, or the first information is carried in the sub-information of the control plane information, and the sub-information carries identifier information; wherein, the identifier information includes one or more of the following: the identifier information of the target object, the target object being part or all of the at least one object; the identifier information of the first object in the at least one object; the identifier information of each object in the at least one object; the identifier information of at least two objects, if the at least one object is multiple objects, the at least two objects belong to the multiple objects.

18. The method according to claim 17, wherein The identifier information includes one or more of the following: the identifier information of the user equipment, the identifier information of the radio bearer, the index of the data radio bearer (DRB), the QoS flow identifier (QFI), the identifier information of the data stream, the index of the data stream, the identifier information of the PDU session, the index of the PDU session.

19. The method according to any one of claims 15-18, characterized in that, The first device is an access network device or a core network device, and the second device is a terminal device.

20. The method according to claim 15, wherein The control plane information includes one or more of the following: QoS configuration information, information carrying QoS parameters, time-sensitive communication (TSC) assistance information.

21. The method according to claim 20, wherein The first information is sent by the policy control function (PCF) or the application function (AF) to the session management function (SMF), or the first information is carried by the PCF or the AF through the time-sensitive communication assistance container (TSCAC).

22. The method according to claim 20 or 21, characterized in that, The first device is an access network device, and the second device is a core network device.

23. The method according to any one of claims 1-14, characterized in that, The first information is carried on the user plane information, or the first information is transmitted through the user plane information.

24. The method according to claim 23, wherein The user plane information includes one or more of the following: a first data packet; a service data adaptation protocol (SDAP) protocol data unit (PDU), a packet data convergence protocol (PDCP) PDU; a MAC control element (CE), a MAC PDU, and a UCI.

25. The method according to claim 23 or 24, characterized in that, The first information is carried in the header of the user plane information, or the first information is carried in the payload of the user plane information.

26. The method according to any one of claims 23-25, characterized in that, The user plane information carries second information, and the second information is used to indicate that the first information is carried in the user plane information.

27. The method according to any one of claims 23-26, characterized in that, The at least one object includes at least one QoS flow, the user plane information includes an SDAP PDU, and the SDAP PDU includes a first field that is used to carry one or more of the following: an identifier of the at least one QoS flow; a type of the at least one QoS flow; an indication of whether the QoS flow corresponding to the first field is a QoS flow associated with the first information; a synchronous transmission requirement of the at least one QoS flow; a cooperative transmission requirement of the at least one QoS flow; a synchronous transmission parameter of the at least one QoS flow; a cooperative transmission parameter of the at least one QoS flow; an identifier of the QoS flow associated with the first information; an identifier of a QoS flow with a synchronous transmission requirement, where the QoS flow with a synchronous transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a cooperative transmission requirement, where the QoS flow with a cooperative transmission requirement includes the at least one QoS flow; an identifier of a QoS flow with a synchronous transmission parameter, where the QoS flow with a synchronous transmission parameter includes the at least one QoS flow; an identifier of a QoS flow with a cooperative transmission parameter, where the QoS flow with a cooperative transmission parameter includes the at least one QoS flow.

28. The method according to claim 24 or 27, characterized in that, The SDAP PDU is an SDAP control PDU or an SDAP data PDU.

29. The method according to claim 24, wherein The first information is carried in a first data packet, and the first data packet satisfies one or more of the following: the first data packet corresponds to the at least one object associated with the first information; the QoS flow of the first data packet is associated with the at least one object; the PDU session of the first data packet is associated with the at least one object; the data stream of the first data packet is associated with the at least one object; the bearer corresponding to the first data packet is associated with the at least one object.

30. The method according to any one of claims 23-29, characterized in that, The first device is an access network device or a core network device, and the second device is a terminal device; or the first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device or a terminal device.

31. The method according to any one of claims 1-30, characterized in that, The at least one object satisfies one or more of the following: the QoS flows associated with the at least one object are carried by the same data radio bearer (DRB); the QoS flows associated with the at least one object are carried by different DRBs; the QoS flows associated with the at least one object are carried by the same logical channel (LCH); the QoS flows associated with the at least one object are carried by different LCHs; The QoS flows associated with the at least one object are carried by different logical channel groups (LCGs); the DRBs or bearers associated with the at least one object are mapped to the same LCH; The DRBs or bearers associated with the at least one object are mapped to the same LCG; The DRBs or bearers associated with the at least one object are mapped to different LCHs; The DRBs or bearers associated with the at least one object are mapped to different LCGs.

32. The method according to claim 31, wherein, The different DRBs include a plurality of DRBs, and the plurality of DRBs satisfy one or more of the following: the configuration parameters of at least two DRBs among the plurality of DRBs match; the mapping restrictions of the logical channel priorities (LCPs) corresponding to at least two DRBs among the plurality of DRBs match.

33. The method according to claim 31, wherein The different LCHs include a plurality of LCHs, and the configuration parameters of at least two LCHs among the plurality of LCHs match.

34. The method according to claim 31, wherein The different LCGs include a plurality of LCGs, and the plurality of LCGs satisfy one or more of the following: the configuration parameters of at least two LCGs among the plurality of LCGs match; the configuration parameters of the LCHs in the plurality of LCGs match.

35. The method according to any one of claims 1 to 34, characterized in that, The at least one object satisfies one or more of the following: the data or data packets associated with the at least one object are multiplexed into the same MAC PDU; the data or data packets associated with the at least one object are multiplexed into a continuous plurality of MAC PDUs; The data or data packets associated with the at least one object are synchronously transmitted to the first device; The data or data packets associated with the at least one object are transmitted to the first device within a target time period.

36. The method according to any one of claims 1 to 34, characterized in that, The at least one object includes a plurality of objects, and the plurality of objects include at least two objects, and the at least two objects satisfy one or more of the following: the data or data packets associated with the at least two objects are multiplexed into the same MAC PDU; the data or data packets associated with the at least two objects are multiplexed into a continuous plurality of MAC PDUs; The data or data packets associated with the at least two objects are synchronously transmitted to the first device; The data or data packets associated with the at least two objects are transmitted to the first device within a target time period.

37. The method according to any one of claims 1 to 34, characterized in that, One or more of the at least one object are target objects, and the target objects satisfy one or more of the following: the data or data packets associated with the target objects are multiplexed into the same MAC PDU; the data or data packets associated with the target objects are multiplexed into a continuous plurality of MAC PDUs; the data or data packets associated with the target objects are synchronously transmitted to the first device; The data or data packets associated with the target objects are transmitted to the first device within a target time period.

38. The method according to any one of claims 1 to 37, characterized in that, The method further includes: the second device sending third information to the first device, where the third information is used to indicate one or more of the following: some or all of the target objects are to be transmitted; data or data packets associated with the target objects are to be transmitted; the size of the transmission resources required to transmit the target objects; the size of the transmission resources required to transmit the objects to be transmitted in the target objects; the data volume information of the objects to be transmitted in the target objects; the remaining delay of the data transmission of the objects to be transmitted in the target objects; the allowed delay of the data transmission of the objects to be transmitted in the target objects; the data volume information of the objects corresponding to the target remaining delay in the objects to be transmitted of the target objects; the data volume information of the objects corresponding to the target allowed delay in the objects to be transmitted of the target objects; the data volume information of the objects corresponding to the delay status reporting information in the objects to be transmitted of the target objects; where the target objects are the at least one object, or, the target objects are one or more objects among the at least one object.

39. The method according to claim 38, wherein The second device sending third information to the first device includes: when a first condition is satisfied, the second device sending the third information to the first device, where the first condition includes one or more of the following: the at least one object cannot be multiplexed using the same MAC PDU; the at least one object cannot be multiplexed using a continuous plurality of MAC PDUs; the at least one object cannot be synchronously transmitted to the first device; the at least one object cannot be transmitted to the first device within a target time period.

40. The method according to claim 38 or 39, characterized in that, The data associated with the third information satisfies one or more of the following: the scheduling priority of the data associated with the third information is higher than the scheduling priority of the first data; the transmission priority of the data associated with the third information is higher than the transmission priority of the first data; the LCH priority of the data associated with the third information is higher than the LCH priority of the first data; the multiplexing priority of the data associated with the third information is higher than the multiplexing priority of the first data, where the first data is the data other than the data associated with the third information among the data to be transmitted.

41. The method according to any one of claims 1 to 40, characterized in that, The data associated with the first information satisfies one or more of the following: the scheduling priority of the data associated with the first information is higher than the scheduling priority of the second data; the transmission priority of the data associated with the first information is higher than the transmission priority of the second data; the LCH priority of the data associated with the first information is higher than the LCH priority of the second data; the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of the second data, where the second data is the data other than the data associated with the first information among the data to be transmitted.

42. The method according to any one of claims 1 to 41, characterized in that, The LCH priorities associated with the at least one object are the same or similar.

43. The method according to any one of claims 1 to 42, characterized in that, The method further includes: the second device sending fourth information to the first device, where the fourth information is used to indicate whether the second device supports transmitting the first information, or, the fourth information is used to indicate whether the second device has available first information.

44. The method according to any one of claims 1-14 and 32-43, characterized in that, The first device is an access network device, and the second device is a terminal device or a first core network device, or the first device is a second core network device and the second device is a terminal device or a first core network device.

45. A method for wireless communication, characterized in that, It includes: The first device receives first information sent by the second device, and the first information is associated with synchronous transmission or collaborative transmission of at least one object.

46. The method according to claim 45, wherein The first information is used to indicate one or more of the following: there is a synchronous transmission requirement for the at least one object; there is a collaborative transmission requirement for the at least one object; synchronous transmission parameters of the at least one object; collaborative transmission parameters of the at least one object; identification information corresponding to the at least one object; type corresponding to the at least one object; whether the at least one object corresponds to target identification information; whether the at least one object corresponds to a target type; synchronous transmission requirements between at least two objects; collaborative transmission requirements between at least two objects; synchronous transmission parameters between at least two objects; collaborative transmission parameters between at least two objects; synchronous transmission between at least two objects; collaborative transmission between at least two objects; whether at least two objects correspond to the same identification information; whether at least two objects correspond to the same type; whether at least two objects correspond to target identification information; whether at least two objects correspond to a target type; association relationship between at least two objects; binding relationship between at least two objects; wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

47. The method according to claim 46, wherein The identification information includes one or more of the following: identification information of a target object, where the target object is part or all of the at least one object; identification information of a first object in the at least one object; identification information of each object in the at least one object; identification information used to identify at least two objects, wherein, if the at least one object includes multiple objects, the at least one object includes the at least two objects.

48. The method according to any one of claims 45 to 47, characterized in that, The object in the at least one object is one of the following: Quality of Service (QoS) flow, data flow, terminal device, Protocol Data Unit (PDU) session, radio bearer.

49. The method according to any one of claims 45-48, characterized in that, The sending of the first information is triggered based on one or more of the following: period; first event; a request message sent by the first device; an enabling indication used to enable the second device to send the first information; the capability of the second device, where the capability is associated with synchronous transmission or collaborative transmission of the at least one object; whether the first device obtains the first information; whether the second device has available or valid first information.

50. The method according to claim 49, wherein The first event includes one or more of the following: exceeding a first duration; the second device is configured to send the first information of the at least one object; has not sent the first information of the at least one object; the synchronous transmission requirement of the at least one object; The requirement for the collaborative transmission of the at least one object changes; the parameters of the synchronous transmission of the at least one object change; the parameters of the collaborative transmission of the at least one object change; the identifier of the synchronous transmission of the at least one object changes; the type of the synchronous transmission of the at least one object changes; the identifier of the collaborative transmission of the at least one object changes; the type of the collaborative transmission of the at least one object changes; the identifier of the synchronous transmission between the at least two objects changes; the type of the synchronous transmission between the at least two objects changes; the identifier of the collaborative transmission between the at least two objects changes; the type of the collaborative transmission between the at least two objects changes; the requirement for the synchronous transmission between the at least two objects changes; the requirement for the collaborative transmission between the at least two objects changes; the parameters of the synchronous transmission between the at least two objects change; the parameters of the collaborative transmission between the at least two objects change; the change amount of the requirement for the synchronous transmission of the at least one object is greater than or equal to the first change threshold; the change amount of the requirement for the collaborative transmission of the at least one object is greater than or equal to the second change threshold; The change amount of the parameters of the synchronous transmission of the at least one object is greater than or equal to the third change threshold; the change amount of the parameters of the collaborative transmission of the at least one object is greater than or equal to the fourth change threshold; the change amount of the parameters of the synchronous transmission between the at least two objects is greater than or equal to the fifth change threshold; the change amount of the parameters of the collaborative transmission between the at least two objects is greater than or equal to the sixth change threshold; the change amount of the requirement for the synchronous transmission between the at least two objects is greater than or equal to the seventh change threshold; the change amount of the requirement for the collaborative transmission between the at least two objects is greater than or equal to the eighth change threshold.

51. The method according to claim 50, wherein, The first duration is the duration for prohibiting or not allowing the transmission of the first information; or, the first duration is the duration for prohibiting or not allowing the transmission of the first information of the at least one object.

52. The method according to claim 50 or 51, characterized in that, The configuration granularity of the first duration is one object among the at least one object; and / or the use of the first duration is for one object among the at least one object.

53. The method according to claim 52, wherein The object associated with the configuration granularity is different from the object for which the first duration is used, or the object associated with the configuration is the same as the object for which the first duration is used.

54. The method according to any one of claims 50 - 53, characterized in that, The first duration is determined based on a first timer, the first event includes the timeout of the first timer, and / or, the first timer is not running.

55. The method according to claim 54, characterized in that, The first timer is started or restarted when the first information is sent.

56. The method according to claim 49, wherein The request message is used to request one or more of the following: the requirement for the target object to perform synchronous transmission; the requirement for the target object to perform collaborative transmission; the parameters for the target object to perform synchronous transmission; the parameters for the target object to perform collaborative transmission; the identifier of the target object; the type of the target object; the requirement for at least two objects to perform synchronous transmission; the requirement for at least two objects to perform collaborative transmission; the parameters for at least two objects to perform synchronous transmission; the parameters for at least two objects to perform collaborative transmission; wherein, the target object includes all or part of the at least one object; if the at least one object includes multiple objects, it includes the at least two objects.

57. The method according to any one of claims 49 to 56, characterized in that, The request message includes one or more of the following: the identifier information of the object requested by the request message; the first duration associated with the first information; the reporting period of the first information; the change threshold of the transmission requirement for synchronous transmission or collaborative transmission, the change threshold of the transmission parameters for synchronous transmission or collaborative transmission; the first timer configuration.

58. The method according to one or more of claims 49-57, characterized in that, The request message is carried on one or more of the following: system information, paging message, radio resource control (RRC) message, uplink control information (UCI), media access control control element (MAC CE), non-access stratum (NAS) message.

59. The method according to any one of claims 45 - 58, characterized in that, The first information is carried on the control plane information, or the first information is transmitted through the control plane information.

60. The method according to claim 59, characterized in that, The control plane information includes one or more of the following: RRC message, NAS message, user equipment (UE) assistance information.

61. The method according to claim 59 or 60, characterized in that, The control plane information carries identifier information, or the first information is carried in the sub-information of the control plane information, and the sub-information carries identifier information; wherein, the identifier information includes one or more of the following: the identifier information of the target object, the target object being part or all of the at least one object; the identifier information of the first object in the at least one object; the identifier information of each object in the at least one object; the identifier information of at least two objects, if the at least one object is multiple objects, the at least two objects belong to the multiple objects.

62. The method according to claim 61, wherein, The identifier information includes one or more of the following: the identifier information of the user equipment, the identifier information of the radio bearer, the index of the data radio bearer (DRB), the QoS flow identifier (QFI), the identifier information of the data stream, the index of the data stream, the identifier information of the PDU session, the index of the PDU session.

63. The method according to any one of claims 59 - 62, characterized in that, The first device is an access network device or a core network device, and the second device is a terminal device.

64. The method according to claim 59, wherein, The control plane information includes one or more of the following: QoS configuration information, information carrying QoS parameters, time-sensitive communication (TSC) assistance information.

65. The method according to claim 64, wherein The first information is sent by the PCF or AF to the SMF, or the first information is carried by the PCF or AF through the TSCAC information.

66. The method according to claim 64 or 65, characterized in that, The first device is an access network device, and the second device is a core network device.

67. The method according to any one of claims 45 - 58, characterized in that, The first information is carried on the user plane information, or the first information is transmitted through the user plane information.

68. The method according to claim 67, characterized in that, The user plane information includes one or more of the following: a first data packet; a service data adaptation protocol (SDAP) protocol data unit (PDU), a packet data convergence protocol (PDCP) PDU; a MAC control element (CE), a MAC PDU, a UCI.

69. The method according to claim 67 or 68, characterized in that, The first information is carried by the header of the user plane information, or the first information is carried by the payload of the user plane information.

70. The method according to any one of claims 67 - 69, characterized in that, The second information is carried in the user plane information, and the second information is used to indicate that the first information is carried in the user plane information.

71. The method according to any one of claims 67-70, characterized in that, The at least one object includes at least one QoS flow, the user plane information includes an SDAP PDU, and the SDAP PDU includes a first field that is used to carry one or more of the following: an identifier of the at least one QoS flow; a type of the at least one QoS flow; an indication of whether the QoS flow corresponding to the first field is a QoS flow associated with the first information; a synchronous transmission requirement of the at least one QoS flow; a coordinated transmission requirement of the at least one QoS flow; a synchronous transmission parameter of the at least one QoS flow; a coordinated transmission parameter of the at least one QoS flow; an identifier of the QoS flow associated with the first information; an identifier of a QoS flow having a synchronous transmission requirement, where the QoS flow having the synchronous transmission requirement includes the at least one QoS flow; an identifier of a QoS flow having a coordinated transmission requirement, where the QoS flow having the coordinated transmission requirement includes the at least one QoS flow; an identifier of a QoS flow having a synchronous transmission parameter, where the QoS flow having the synchronous transmission parameter includes the at least one QoS flow; an identifier of a QoS flow having a coordinated transmission parameter, where the QoS flow having the coordinated transmission parameter includes the at least one QoS flow.

72. The method according to claim 68 or 71, characterized in that, The SDAP PDU is the SDAP control PDU or the SDAP data PDU.

73. The method according to claim 68, wherein, The first information is carried in a first data packet, and the first data packet satisfies one or more of the following: the first data packet corresponds to the at least one object associated with the first information; the QoS flow of the first data packet is associated with the at least one object; the PDU session of the first data packet is associated with the at least one object; the data stream of the first data packet is associated with the at least one object; the bearer corresponding to the first data packet is associated with the at least one object.

74. The method according to any one of claims 67-73, characterized in that, The first device is an access network device or a core network device, and the second device is a terminal device; or the first device is an access network device, and the second device is a core network device; or The first device is a core network device, and the second device is an access network device or a terminal device.

75. The method according to any one of claims 45-74, characterized in that, The at least one object satisfies one or more of the following: the QoS flows associated with the at least one object are carried by the same data radio bearer (DRB); the QoS flows associated with the at least one object are carried by different DRBs; the QoS flows associated with the at least one object are carried by the same logical channel (LCH); the QoS flows associated with the at least one object are carried by different LCHs; the QoS flows associated with the at least one object are carried by different logical channel groups (LCGs); The DRB or bearer associated with the at least one object is mapped to the same LCH; The DRB or bearer associated with the at least one object is mapped to the same LCG; The DRB or bearer associated with the at least one object is mapped to different LCHs; The DRB or bearer associated with the at least one object is mapped to different LCGs.

76. The method according to claim 75, characterized in that, The different DRBs include multiple DRBs, and the multiple DRBs satisfy one or more of the following: the configuration parameters of at least two DRBs among the multiple DRBs match; the mapping restrictions of the logical channel priorities (LCPs) corresponding to at least two DRBs among the multiple DRBs match.

77. The method according to claim 75, wherein The different LCHs include multiple LCHs, and the configuration parameters of at least two LCHs among the multiple LCHs match.

78. The method according to claim 75, wherein The different LCGs include multiple LCGs, and the multiple LCGs satisfy one or more of the following: the configuration parameters of at least two LCGs among the multiple LCGs match; the configuration parameters of the LCHs in the multiple LCGs match.

79. The method according to any one of claims 45 - 78, characterized in that, The at least one object satisfies one or more of the following: the data or data packets associated with the at least one object are multiplexed into the same MAC PDU; the data or data packets associated with the at least one object are multiplexed into a continuous plurality of MAC PDUs; The data or data packets associated with the at least one object are synchronously transmitted to the first device; The data or data packets associated with the at least one object are transmitted to the first device within a target time period.

80. The method according to any one of claims 45 - 78, characterized in that, The at least one object includes multiple objects, the multiple objects include at least two objects, and the at least two objects satisfy one or more of the following: the data or data packets associated with the at least two objects are multiplexed into the same MAC PDU; the data or data packets associated with the at least two objects are multiplexed into a continuous plurality of MAC PDUs; The data or data packets associated with the at least two objects are synchronously transmitted to the first device; The data or data packets associated with the at least two objects are transmitted to the first device within a target time period.

81. The method according to any one of claims 45 - 78, characterized in that, One or more objects among the at least one object are target objects, and the target objects satisfy one or more of the following: the data or data packets associated with the target objects are multiplexed into the same MAC PDU; the data or data packets associated with the target objects are multiplexed into a continuous plurality of MAC PDUs; the data or data packets associated with the target objects are synchronously transmitted to the first device; The data or data packets associated with the target objects are transmitted to the first device within a target time period.

82. The method according to any one of claims 45 - 78, characterized in that, The method further includes: the first device receives third information sent by the second device, where the third information is used to indicate one or more of the following: some or all of the target objects are to be transmitted; data or data packets associated with the target objects are to be transmitted; the size of the transmission resources required to transmit the target objects; the size of the transmission resources required to transmit the objects to be transmitted in the target objects; the data volume information of the objects to be transmitted in the target objects; the remaining delay of the data of the objects to be transmitted in the target objects; the allowed delay of the data of the objects to be transmitted in the target objects; the data volume information of the objects corresponding to the target remaining delay in the objects to be transmitted in the target objects; the data volume information of the objects corresponding to the target allowed delay in the objects to be transmitted in the target objects; the data volume information of the objects corresponding to the delay status reporting information in the objects to be transmitted in the target objects; where the target objects are the at least one object, or the target objects are one or more of the at least one object.

83. The method according to claim 82, wherein, The first device receiving the third information sent by the second device includes: satisfying a first condition, the first device receives the third information sent by the second device, where the first condition includes one or more of the following: the at least one object cannot be multiplexed in the same MAC PDU; the at least one object cannot be multiplexed in a continuous plurality of MAC PDUs; the at least one object cannot be synchronously transmitted to the first device; the at least one object cannot be transmitted to the first device within a target time period.

84. The method according to claim 82 or 83, characterized in that, The data associated with the third information satisfies one or more of the following: the scheduling priority of the data associated with the third information is higher than the scheduling priority of the first data; the transmission priority of the data associated with the third information is higher than the transmission priority of the first data; the LCH priority of the data associated with the third information is higher than the LCH priority of the first data; the multiplexing priority of the data associated with the third information is higher than the multiplexing priority of the first data, where the first data is the data other than the data associated with the third information in the data to be transmitted.

85. The method according to any one of claims 45-84, characterized in that, The first information is associated with the synchronous transmission or cooperative transmission of the data or data packets of the at least one object, and the data associated with the first information satisfies one or more of the following: the scheduling priority of the data associated with the first information is higher than the scheduling priority of the second data; the transmission priority of the data associated with the first information is higher than the transmission priority of the second data; the LCH priority of the data associated with the first information is higher than the LCH priority of the second data; the multiplexing priority of the data associated with the first information is higher than the multiplexing priority of the second data, where the second data is the data other than the data associated with the first information in the data to be transmitted.

86. The method according to any one of claims 45-85, characterized in that, The LCH priorities associated with the at least one object are the same or similar.

87. The method according to any one of claims 45 - 86, characterized in that, The method further includes: the first device receives fourth information sent by the second device, where the fourth information is used to indicate whether the second device supports transmitting the first information, or the fourth information is used to indicate whether the second device has available first information.

88. The method according to any one of claims 45 - 58 and 76 - 87, characterized in that, The first device is an access network device, and the second device is a terminal device or a first core network device, or, the first device is a second core network device, and the second device is a terminal device or a first core network device.

89. A communication device, characterized in that, The communication device includes a module for performing the method according to any one of claims 1-88.

90. A communication device, characterized in that, It includes a transceiver, a memory, and a processor. The memory is used for storing programs, and the processor is used for calling the programs in the memory and controlling the transceiver to receive or send signals, so that the communication device performs the method according to any one of claims 1-88.

91. A device, characterized in that, It includes a processor for calling a program from a memory, so that the device performs the method according to any one of claims 1-88.

92. A chip, characterized in that, It includes a processor for calling a program from a memory, so that the device installed with the chip performs the method according to any one of claims 1-88.

93. A computer-readable storage medium, characterized in that, A program is stored thereon, and the program causes a computer to perform the method according to any one of claims 1-88.

94. A computer program product, characterized in that, It includes a program that causes a computer to perform the method according to any one of claims 1-88.

95. A computer program, characterized in that, The computer program causes a computer to perform the method according to any one of claims 1-88.

Images