Wireless communication method and device

Abstract

The invention provides a wireless communication method for wireless communication equipment. The wireless communication method comprises the following steps: a protocol layer in sending end equipment receives a plurality of service data units (SDU) for synchronous transmission and synchronous transmission indication information from an upper protocol layer; the protocol layer encapsulates the plurality of SDUs into one or more protocol data units (PDU) for synchronous transmission in the protocol layer based on the synchronous transmission indication information; and the protocol layer provides the one or more PDUs to a lower protocol layer for synchronous transmission.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a wireless communication method and apparatus. Background Technology

[0002] Fifth-generation (5G) wireless communication systems are designed to provide traditional services such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). In 5G or New Radio (NR) systems, features supporting eMBB, URLLC, and mMTC were introduced in Release 15 and further enhanced in Release 16 and Release 17.

[0003] Haptic communication and multimodal communication services support multimodal interaction that combines ultra-low latency with high availability, high reliability, and high security. These services have potential applications in various fields, including industry, robotics, telepresence, virtual reality, augmented reality, healthcare, road transportation, gaming, education, culture, and smart grids. These services can support the use of input from multiple sources and / or output to multiple destinations, thereby delivering information more efficiently. The inputs and outputs can involve different modalities, such as: — Video / audio media; — Environmental sensor data, such as brightness, temperature, humidity, etc.; and / or — Tactile data, including tactile perception (such as pressure, texture, vibration, temperature) and kinesthetic perception (such as gravity, tension, and position).

[0004] Immersive multimodal virtual reality (VR) applications place high demands on strict synchronization between different media components to avoid a decline in user experience (e.g., users perceiving asynchrony between different modalities).

[0005] Technical issues Essentially, multimodal services typically involve multiple Quality of Service (QoS) streams and multiple Data Radio Bearers (DRBs) or Logical Channel Groups (LCHs) derived from these QoS streams. Synchronization requirements can apply to multiple Service Data Units (SDUs) / Protocol Data Units (PDUs) within a single DRB / LCH, or to SDUs / PDUs spanning multiple DRBs / LCHs. However, existing New Radio (NR) Layer 2 architectures and data stream designs are not optimized for synchronous transmission. The main challenge lies in how to enhance the fundamental design principles of Layer 2 architectures and data streams to meet the synchronous transmission requirements of multimodal services.

[0006] Other issues related to synchronous transmission include: Synchronization transmission configuration: It is necessary to determine the appropriate configuration and parameters to achieve synchronization between the relevant components; Base station (gNB) awareness of multimodal services from user equipment (UE): A mechanism needs to be established to enable the gNB to identify and understand the multimodal service requests initiated by the UE; Handling asynchronous SDUs / PDUs and discarding SDUs / PDUs due to congestion: Appropriate strategies need to be developed to handle situations where SDUs / PDUs become out of sync or need to be discarded due to congestion.

[0007] Therefore, there is an urgent need for a wireless communication method to provide an enhancement mechanism for the synchronous transmission of multimodal services.

[0008] Technical solution The purpose of this invention is to provide a user equipment (UE) and a wireless communication method and apparatus.

[0009] In a first aspect, one embodiment of the present invention provides a wireless communication method for a wireless communication device, comprising: Receive multiple Service Data Units (SDUs) for synchronization transmission and synchronization transmission indication information from the upper protocol layer; Based on the synchronization transmission indication information, the plurality of SDUs are encapsulated into one or more Protocol Data Units (PDUs) for synchronization transmission at the protocol layer; and The one or more PDUs are provided to the lower protocol layer for synchronous transmission.

[0010] In a second aspect, one embodiment of the present invention provides a wireless communication device operating as a transmitter, comprising a processor configured to invoke and execute a computer program stored in a memory to cause a device equipped with the processor to perform the methods disclosed above.

[0011] In a third aspect, one embodiment of the present invention provides a wireless communication method for a wireless communication device, comprising: Receive one or more Protocol Data Units (PDUs) for synchronous transmission from the lower protocol layer. Based on the configuration information used for synchronous transmission and / or the PDU format of the PDU used for synchronous transmission, the one or more PDUs are decapsulated into multiple Service Data Units (SDUs) at the protocol layer; and The multiple SDUs are provided to the upper protocol layer for synchronous transmission.

[0012] In a fourth aspect, one embodiment of the present invention provides a wireless communication device operating as a receiver, comprising a processor configured to invoke and execute a computer program stored in a memory to cause a device equipped with the processor to perform the methods disclosed above.

[0013] The methods disclosed above can be implemented in a chip. The chip may include a processor configured to invoke and execute a computer program stored in memory, causing a device on which the chip is mounted to perform the methods disclosed above.

[0014] The methods disclosed above can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. When the non-transitory computer-readable medium is loaded into a computer, it instructs the computer's processor to execute the methods disclosed above.

[0015] The non-transitory computer-readable medium may include, but is not limited to, at least one of the following: hard disk, read-only optical disk (CD-ROM), optical storage device, magnetic storage device, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory.

[0016] The methods disclosed above can be programmed into a computer program product for causing a computer to perform the methods disclosed above.

[0017] The methods disclosed above can be programmed into a computer program that causes a computer to perform the methods disclosed above.

[0018] Beneficial effects This specification provides synchronization information for multimodal services. Synchronization information is a key factor in ensuring service quality and user satisfaction. Multimodal services refer to services that deliver content or functions through different modes or channels, such as audio, video, text, and graphics. The synchronization information is used to indicate the timing relationship between different modes, such as the timing relationship of starting, stopping, pausing, resuming, or switching between different modes. Without proper synchronization information, multimodal services may experience delays, inconsistencies, errors, or interruptions, thereby adversely affecting user experience and service performance. Therefore, providing synchronization information for multimodal services can produce the following technical effects: — Improve the accuracy and reliability of multimodal services by ensuring that different data streams are aligned and coordinated according to the intended design and logic; — Improve the efficiency and scalability of multimodal services by reducing the bandwidth and processing resources required when transmitting and processing different modes; — By supporting dynamic and seamless switching between different modes that emphasize different media components based on user preferences, context information, or device capabilities, the flexibility and adaptability of multimodal services are improved. — Improve the accessibility and ease of use of multimodal services by facilitating the integration of alternative or complementary media components for users with different needs, preferences or capabilities. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A schematic diagram of a system including the core network, radio access network (RAN), and user equipment (UE) is shown.

[0021] Figure 2 A schematic diagram illustrating the data network and application servers.

[0022] Figure 3A schematic diagram showing the protocol layer structure of the transmitting and receiving devices is provided.

[0023] Figure 4 A schematic diagram of the second-level (Layer 2) structure is shown.

[0024] Figure 5 A schematic diagram illustrating the upper second layer (Layer 2) structure.

[0025] Figure 6 Draw a schematic diagram of the second-layer data flow.

[0026] Figure 7 A schematic diagram illustrating an embodiment of the wireless communication method of the present invention implemented in the protocol layer of the transmitting device is shown.

[0027] Figure 8 A schematic diagram illustrating an embodiment of the wireless communication method of the present invention implemented in the protocol layer of the receiving device is shown.

[0028] Figure 9 A schematic diagram illustrating an example of an SDAP data PDU format excluding the SDAP header.

[0029] Figure 10 A schematic diagram illustrating an example of an SDAP data PDU format including an SDAP header.

[0030] Figure 11 A schematic diagram illustrating an example of an uplink SDAP data PDU format including an SDAP header.

[0031] Figure 12 A schematic diagram illustrating an example of a PDCP data PDU format with a 12-bit PDCP sequence number.

[0032] Figure 13 A schematic diagram illustrating an example of a PDCP data PDU format with an 18-bit PDCP sequence number (SN) for data radio bearer.

[0033] Figure 14 A schematic diagram illustrating an example of PDCP data PDU format with a 12-bit PDCP sequence number.

[0034] Figure 15 A schematic diagram illustrating an example of a PDCP data PDU format with an 18-bit PDCP sequence number (SN) for use in a Data Radio Bearer (DRB).

[0035] Figure 16 A schematic diagram illustrating an example of a transparent mode data PDU (TMD PDU).

[0036] Figure 17A schematic diagram illustrating an example of an unacknowledged mode data PDU (UMD PDU) containing multiple complete Radio Link Control (RLC) SDUs.

[0037] Figure 18 A schematic diagram illustrating an example of an unacknowledged mode data PDU (UMD PDU) with a 6-bit sequence number (SN) and excluding segment offset (SO).

[0038] Figure 19 A schematic diagram illustrating an example of an unacknowledged mode data PDU (UMDPDU) with a 6-bit sequence number (SN) and including a segment offset (SO).

[0039] Figure 20 A schematic diagram illustrating an example of an acknowledgment mode data PDU (AMDPDU) with a 12-bit sequence number (SN) and excluding segment offset (SO).

[0040] Figure 21 A schematic diagram illustrating an example of an acknowledgment mode data PDU (AMDPDU) with a 12-bit sequence number (SN) and including segment offset (SO).

[0041] Figure 22 A schematic diagram illustrating an example of data packets from three QoS streams with different periodicities.

[0042] Figure 23 A schematic diagram illustrating an example of a Buffer Status Report (BSR) MAC control unit (MAC CE).

[0043] Figure 24 A schematic diagram illustrating another example of data packets from three QoS streams with different periodicities.

[0044] Figure 25 A schematic diagram illustrating an example of a Logical Channel Group (LCG) where there are arrival time differences between PDU sets of different Logical Channels (LCHs).

[0045] Figure 26 A schematic diagram illustrating an example of a Buffered State Report (BSR) used to represent asynchronous state information.

[0046] Figure 27 A schematic diagram illustrating another example of a Buffered State Report (BSR) used to represent asynchronous state information.

[0047] Figure 28 A schematic diagram of a wireless communication system according to an embodiment of the present invention is shown. Detailed Implementation

[0048] The embodiments of the present invention are described in detail with reference to the accompanying drawings, including technical aspects, structural features, objectives, and effects. Specifically, the terminology used in the embodiments of the present invention is only used to describe the purpose of a particular embodiment and is not intended to limit the disclosure.

[0049] The abbreviations used in this specification are listed below: Table 1

[0050] This invention discloses a wireless communication method for processing synchronous transmission of multimodal services.

[0051] In this specification, for the sake of simplicity, the packets, Protocol Data Units (PDUs), and / or sets of PDUs of services are collectively referred to as service traffic data.

[0052] In this specification, a packet can be a PDU or Service Data Unit (SDU) of a protocol layer. For simplicity, the term "packet" can refer to either a PDU or an SDU, and the term "PDU" can also refer to either a PDU or an SDU. Furthermore, in this specification, the term "resource" includes radio resources in both the time and frequency domains.

[0053] User equipment (UE) can send a Buffer Status Report (BSR) to the base station (gNB). The Buffer Status Report (BSR) procedure is used to provide the serving base station with information on the amount of uplink (UL) data in the UE's Media Access Control (MAC) entity.

[0054] See Figure 1 According to an embodiment of the present invention, a communication system including user equipment UE 10a, user equipment UE 10b, base station (BS) 20a and network entity equipment 30 performs the method of the present invention. Figure 1For illustrative purposes only and not as a limitation, the system may also include additional UEs, BSs, and core network (CN) entities. Connections between devices and device components are illustrated in the diagram using lines and arrows. UE 10a may include processor 11a, memory 12a, and transceiver 13a; UE 10b may include processor 11b, memory 12b, and transceiver 13b; base station 20a may include processor 21a, memory 22a, and transceiver 23a; network entity device 30 may include processor 31, memory 32, and transceiver 33. Each processor 11a, 11b, 21a, and 31 may be configured to implement the functions, processes, and / or methods described in this specification. The various layers of the radio interface protocol may be implemented in processors 11a, 11b, 21a, and 31. Each memory 12a, 12b, 22a, and 32 is used to operatively store various programs and information to drive the corresponding processor. Each transceiver 13a, 13b, 23a, and 33 is operatively connected to a corresponding processor for transmitting and / or receiving wireless or wired signals. UE10a can communicate with UE10b via a sidelink. Base station 20a can be an eNB, gNB, or other type of wireless node and can configure wireless resources for UE10a and UE10b.

[0055] Network entity device 30 may be a node in the core network (CN). The core network may include an LTE core network or a fifth-generation core network (5G Core, 5GC), wherein the 5GC includes User Plane Function (UPF), Session Management Function (SMF), Access and Mobility Management Function (AMF), Unified Data Management (UDM), Policy Control Function (PCF), Control Plane / User Plane Separation (CUPS), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), and Network Exposure Function (NEF).

[0056] In this specification, examples of UEs may include UE 10a or UE 10b, and examples of base stations may include base station 20a. Uplink (UL) transmission of control signaling or data may be a transmission operation from the UE to the base station, and downlink (DL) transmission of control signaling or data may be a transmission operation from the base station to the UE. Downlink control signaling may include downlink control information (DCI) or radio resource control (RRC) signaling sent from the base station to the UE.

[0057] Figure 2 This diagram illustrates a transmission network model for multimodal services supported by a 5G System. User Equipment (UE) 10 is a 5G terminal capable of supporting multimodal services and related applications, and can be referred to as a client, client terminal, or service client. Base Station gNB 20 is a 5G radio node that communicates with UE 10 and provides NR user plane and control plane protocol termination to UE 10 via the New Radio (NR) Uu interface. gNB 20 is connected to the 5G Core (5GC) 300 via the NG interface. User Plane Function (UPF) 30b is a UPF node within the 5GC 300. Data Network (DN) 40 includes an application server 41 for providing multimodal services. The data network 40 can provide network operator services, internet access services, or third-party services. The application server 41 may include a processor 411, a memory 412, and a transceiver 413. The processor 411 can be configured to implement the functions, processes, and / or methods related to multimodal services described in this specification. The various layers of the wireless interface protocol can be implemented in the processor 411. The memory 412 operably stores various programs and information to drive the corresponding processor. The transceiver 413 is operably connected to the corresponding processor for transmitting and / or receiving wireless or wired signals.

[0058] Each processor 411, 11a, 11b, 21a, and 31 may include an Application-Specific Integrated Circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Each memory 412, 12a, 12b, 22a, and 32 may include Read-Only Memory (ROM), Random-Access Memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Each transceiver 413, 13a, 13b, 23a, and 33 may include baseband circuitry and radio frequency (RF) circuitry for processing radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented in the form of modules, processes, functions, entities, etc., to perform the functions described herein. The modules may be stored in memory and executed by the processor. The memory may be located inside or outside the processor and may be communicatively connected to the processor in various ways known in the art. Figure 1 Examples of UE, gNB, base station, core network (CN), and core network entities mentioned in this specification are provided.

[0059] The device performing the wireless communication method can be a transmitting device that sends service traffic of a multimodal service to a receiving device, or a receiving device that receives the service traffic. The service traffic may include one or more service flows of a multimodal service. For example, the device performing the wireless communication method may include a base station gNB 20, an application server 41 in the data network 40, or a UE. That is, in some service traffic transmission scenarios, the application server 41 in the data network 40 can act as a transmitting device to perform the wireless communication method, while one or more service clients (e.g., at least one of UE 10, UE 10a, and UE 10b) act as receiving devices to receive service traffic from the transmitting device. Similarly, in some service traffic transmission scenarios, a service client (e.g., at least one of UE 10, UE 10a, and UE 10b) can also act as a transmitting device to perform the wireless communication method, while another service client or application server 41 acts as a receiving device to receive service traffic from the transmitting device. Alternatively, the transmitting device may also include an intermediate device located between UE 10 and application server 41. UE 10 can be an embodiment of UE 10a or UE 10b, and gNB 20 can be an embodiment of base station 20a. It should be noted that although gNB 20 and UPF 30b are described as examples in this specification, the wireless communication method can also be implemented by other types of base stations, such as another gNB, eNB, a base station integrating eNB and gNB, or a base station suitable for technologies beyond 5G; UPF 30b can also be other network entities in 5GC.

[0060] A multimodal service flow (e.g., service flow 5) is established between UE 10 and application server 41. The service flow 5 includes service traffic 51 from application server 41 to UE 10 and service traffic 52 from UE 10 to application server 41.

[0061] In this specification, layers such as the application layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and physical layer (PHY layer or L1 layer) can be protocol layer entities in the transmitting or receiving device. These protocol layer entities can be implemented through programs or software modules executed by a processor, hardware modules in an integrated circuit (IC), or a combination of the above.

[0062] See Figure 3An example of a transmitting device is shown as transmitting device 10c, and an example of a receiving device is shown as receiving device 10d. Transmitting device 10c includes a user plane protocol stack and a control plane protocol stack. The control plane includes a Physical Layer (PHY layer or L1 layer) 14c, a Media Access Control Layer (MAC layer) 15c, a Radio Link Control Layer (RLC layer) 16c, a Packet Data Convergence Protocol Layer (PDCP layer) 17c, a Radio Resource Control Layer (RRC layer) 18-1c, and a Non-Access Layer (NAS layer) 19-1c. The user plane includes a Physical Layer (PHY layer or L1 layer) 14c, a MAC layer 15c, an RLC layer 16c, a PDCP layer 17c, a Service Data Adaptation Protocol Layer (SDAP layer) 18-2c, an Internet Protocol Layer (IP layer) 19-2c, and an Application Layer 19-3c.

[0063] The receiving device 10d also includes a user plane protocol stack and a control plane protocol stack. The control plane includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, an RRC layer 18-1d, and a NAS layer 19-1d. The user plane includes a physical layer (PHY layer or L1 layer) 14d, a MAC layer 15d, an RLC layer 16d, a PDCP layer 17d, an SDAP layer 18-2d, an IP layer 19-2d, and an application layer 19-3d.

[0064] For example, when the application layer 19-3c of the transmitting device 10c sends a PDU to the application layer 19-3d of the receiving device 10d through lower-layer protocols (i.e., IP layer 19-2c, SDAP layer 18-2c, PDCP layer 17c, RLC layer 16c, MAC layer 15c, and physical layer 14c), each layer in the transmitting device 10c acts as the protocol layer entity on the transmitting side, and each layer in the receiving device 10d acts as the protocol layer entity on the receiving side. Embodiments of the present invention can be implemented in the SDAP layer, PDCP layer, RLC layer, or MAC layer. One or more steps (or functional modules) in the embodiments of the present invention can be implemented in the form of a computer program, instructions, or software module, which is stored in the memory of the transmitting device; or implemented in the processor of the transmitting device in the form of a circuit or hardware module; or implemented in the transmitting device in the form of an integrated circuit chip, circuit, or plug-in. The protocol layer entities described herein are merely examples of protocol layers mentioned in this specification.

[0065] Figure 3 The layers shown can conform to the New Radio (NR) wireless communication system defined by the 3GPP standard, which can be... Figures 4 to 6 express. Figures 4 to 6 The examples of each layer shown can correspond to Figure 3The protocol layer entity. In Figure 4 Examples of UE1 to UEn may include Figure 1 The accompanying drawings illustrate the main components and functions of Layer 2, as well as the interfaces and protocols used for data transmission and reception. The following paragraphs provide a brief description of each sublayer and its role in the NR system.

[0066] See Figure 7 and Figure 8 Sending device (such as Figure 3 The protocol layers (e.g., MAC layer 15c, RLC layer 16c, PDCP layer 17c, or SDAP layer 18-2c) and the receiving equipment (e.g.) Figure 3 The protocol layer (e.g., MAC layer 15d, RLC layer 16d, PDCP layer 17d, or SDAP layer 18-2d) of the present invention implements the wireless communication method for multimodal services.

[0067] The protocol layer of the transmitting device receives multiple Service Data Units (SDUs) for synchronous transmission and synchronous transmission indication information (A101) from the upper protocol layer.

[0068] Based on the synchronization transmission indication information, the protocol layer of the transmitting device encapsulates the plurality of SDUs into one or more Protocol Data Units (PDUs) (A102) for synchronization transmission. In some embodiments of the present invention, when the concatenation length of the plurality of SDUs does not exceed the maximum payload size of a PDU in the protocol layer, the plurality of SDUs are encapsulated into a single protocol layer PDU using an enhanced PDU format; when the concatenation length of the plurality of SDUs exceeds the maximum payload size of a single PDU in the protocol layer, the plurality of SDUs are encapsulated into multiple protocol layer PDUs using enhanced PDU formats. In one embodiment of the present invention, the activation of the enhanced PDU format is based on the set of enhanced PDU formats supported by the user equipment (UE) in the UE capability report, and the set of enhanced PDU formats supported by the base station in broadcast or unicast downlink indication messages.

[0069] The protocol layer of the transmitting device provides one or more of the PDUs to the lower protocol layer for synchronous transmission (A103).

[0070] Whether a PDU includes multiple SDUs for synchronous transmission can be indicated by either a control plane scheme or a user plane scheme. In one embodiment of the invention, control plane signaling indicates whether the PDU format includes multiple SDUs for synchronous transmission. In another embodiment of the invention, a field in the enhanced PDU format of the one or more PDUs indicates whether the PDU format includes multiple SDUs for synchronous transmission.

[0071] The protocol layer of the receiving device receives one or more Protocol Data Units (PDUs) (B101) for synchronous transmission from the lower protocol layer.

[0072] The protocol layer of the receiving device decapsulates one or more PDUs into multiple Service Data Units (SDUs) (B102) based on the configuration information for synchronous transmission and / or the PDU format for synchronous transmission.

[0073] The protocol layer of the receiving device provides the multiple SDUs to the upper protocol layer for synchronous transmission (B103).

[0074] In one embodiment of the present invention, in the transmitting device, when the enhanced encapsulation function is enabled, multiple Service Data Units (SDUs) are encapsulated into one or more Protocol Data Units (PDUs) for synchronous transmission based on synchronization transmission indication information. In the transmitting device, when the enhanced encapsulation function is enabled according to configuration information, the operation of encapsulating multiple SDUs into one or more PDUs for synchronous transmission based on the synchronization transmission indication information is performed. In the receiving device, when the enhanced encapsulation function is enabled according to the configuration information, multiple SDUs are decapsulated from one or more PDUs for synchronous transmission based on the enhanced PDU format. The configuration information is transmitted via Radio Resource Control (RRC) messages. In another example, the configuration information includes control plane signaling and is transmitted via RRC messages, wherein the control plane signaling is used to indicate whether a PDU format supporting multiple SDUs is used for synchronous transmission. The configuration information is configured for the UE and is also used for packet decapsulation processing, for example, in step B102.

[0075] In one embodiment of the present invention, the protocol layer is a Service Data Adaptation Protocol (SDAP) layer; the configuration information of the enhanced encapsulation function includes one or more of the following: One or more QoS flow identifiers of the Quality of Service (QoS) flow associated with the SDU used for synchronization transmission; and Configuration information for synchronizing transmission requirements, the configuration information including at least a latency threshold between QoS streams.

[0076] In one embodiment of the present invention, the protocol layer is a Packet Data Convergence Protocol (PDCP) layer. The configuration information related to the enhanced encapsulation function includes configurations for enabling the enhanced encapsulation function.

[0077] In one embodiment of the present invention, the protocol layer is the Radio Link Control (RLC) layer. The configuration information related to the enhanced encapsulation function includes configurations for enabling the enhanced encapsulation function.

[0078] In one embodiment of the present invention, the protocol layer is a Medium Access Control (MAC) layer. The configuration information for the enhanced encapsulation function further includes at least one of the following: A synchronization DRB group or multiple DRBs used to establish synchronization relationships between Data Radio Bearers (DRBs). - A Logical Channel Group (LCG), comprising logical channels (LCHs) corresponding to DRB / QoS streams used for synchronization transmission, the LCG being configured to establish synchronization relationships between logical channels; and - Configuration information for latency thresholds between QoS streams used for synchronous transmission.

[0079] In one embodiment of the present invention, the configuration information of the synchronized DRB group or multiple DRBs includes at least one of the following: - DRB group identifier for synchronized DRB groups; - The DRB identifier of a member DRB in a synchronized DRB group or multiple DRBs; and - Primary DRB information, which includes the primary DRB identifier in the synchronization DRB group and the timing information of the primary DRB.

[0080] In one embodiment of the present invention, the timing information includes at least one of the following: the periodicity, jitter, and data arrival time of the data corresponding to the main DRB of the main QoS flow.

[0081] In one embodiment of the present invention, radio resource scheduling for SDUs of the primary DRB takes precedence over radio resource scheduling for SDUs of member DRBs.

[0082] In one embodiment of the present invention, the configuration information of the LCG includes at least one of the following: - The LCG identifier for synchronized LCG; - The logical channel identifier of the member logical channel in the LCG; - Main logical channel information, which includes the main logical channel identifier and timing information of the main logical channel in the LCG.

[0083] In one embodiment of the present invention, the timing information includes at least one of the following: the periodicity, jitter, and data arrival time corresponding to the main QoS stream.

[0084] In one embodiment of the present invention, for synchronous uplink transmission scheduling, the Media Access Control (MAC) layer performs buffer size reporting via a Buffer Status Report (BSR) based on one or more of the following information: - Logical Channel Group (LCG) identifier; - The periodicity of data packets in a Quality of Service (QoS) stream / Data RadioBearer (DRB) and the size of one or more buffers determined according to one or more time ranges; - The size of one or more buffers for cached data that conforms to the configuration information used for synchronous transmission requirements; - One or more synchronization status information between different QoS flows, the synchronization status information including: an asynchronous indication, used to indicate whether data from a certain DRB / QoS flow is in a synchronized state relative to data from the main DRB / QoS flow; and a difference time, the difference time being the data arrival time difference between a certain QoS flow and the main DRB / QoS flow.

[0085] In one embodiment of the present invention, the MAC layer performs asynchronous event detection based on synchronous transmission indication information, and triggers the reporting of asynchronous events or triggers BSR for asynchronous event reporting when an asynchronous event is detected, or when the number of asynchronous events occurring within a predefined or configured time range exceeds a predefined or configured threshold, or when the ratio of asynchronous SDU to synchronous SDU exceeds a predefined or configured threshold.

[0086] In one embodiment of the present invention, the BSR for asynchronous event reporting includes one or more of the following information for each LCG in the BSR: - Indication information indicating whether an asynchronous event has occurred in the LCG; - The arrival time difference between two or more SDUs from different service flows in the asynchronous event; and - The ratio of asynchronous SDUs to synchronous SDUs, or the total number of SDUs within a predefined or configured time range.

[0087] Example 1: SDAP Multiplexing In cases where multiple service flows (e.g., XR services) are mapped to one or more QoS flows and synchronous transmission is required, the sending application layer entity (i.e., the application layer entity in the sending device) corresponding to the service identifies multiple PDUs requiring synchronous transmission from one or more QoS flows based on the synchronous transmission indication information carried with the PDU. For example, multiple PDUs from the same QoS flow and belonging to the same PDU set can be synchronously transmitted. For multiple PDUs from multiple QoS flows, the synchronous transmission indication information carried with the PDU can be a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDU used for synchronous transmission; the range can be predefined or configurable. Subsequently, the application layer PDU and the synchronous transmission indication information are received together by the lower-layer SDAP entity.

[0088] For example, in the uplink transmission of a service flow, the PDU and the synchronization transmission indication information can be provided by the UE's sending application layer entity to the UE's SDAP entity.

[0089] For example, in the downlink transmission of a service flow, the PDU and the synchronization transmission indication information can be provided by the sending application layer entity to the user plane function (UPF) in the core network (CN) and further transmitted to the SDAP entity of the base station (gNB). The sending application layer entity can be an application layer entity in the service sending device.

[0090] like Figure 4 and Figure 5As shown, when one or more Quality of Service (QoS) streams are mapped to the same Data Radio Bearer (DRB) and are configured with synchronous transmission requirements, the transmitting SDAP entity corresponding to the DRB can multiplex multiple Service Data Units (SDUs) that need to be transmitted synchronously into one Protocol Data Unit (PDU). For example, multiple SDUs from the same PDU set of the same QoS stream can be multiplexed, or multiple SDUs from two or more QoS streams can be multiplexed. The operation of multiplexing multiple SDUs into one PDU is defined as an enhanced encapsulation function, which is applicable to all of the following embodiments.

[0091] When an SDAP entity needs to support enhanced encapsulation (EIE) functionality, it needs to configure information related to EIE to both the sending and receiving SDAP entities. Specifically, on the UE side, the base station (gNB) can configure EIE-related information to both the sending and receiving SDAP entities via downlink control signaling (e.g., Radio Resource Control (RRC) messages). As an example, some configuration information for EIE is introduced based on the existing standard SDAP configuration information element (IE). The required configuration information includes at least one of the following: - Configuration information for enabling enhanced encapsulation functionality in uplink and / or downlink; and - QoS stream identifiers and related information for enhanced encapsulation functionality used for synchronous transmission in uplink and / or downlink. Within the QoS streams, one QoS stream is designated as the primary QoS stream, which carries a media component of a multimodal service (e.g., XR service) and is used as a reference for other QoS streams carrying media components of multimodal services for synchronization operations such as configuration, detection, and transmission.

[0092] For SDAP entities configured with enhanced encapsulation for synchronous transmission, the transmitting and receiving SDAP entities (i.e., the SDAP layer entities in the transmitting and receiving devices) can support SDU multiplexing using one or more enhanced SDAP PDU formats based on the current SDAP PDU format. See also Figure 9 , Figure 10 and Figure 11 This illustration shows some examples of enhanced SDAP PDU formats designed based on the current 3GPP technical specification TS 37.324.

[0093] The fields in the PDU format are described below: L: Length field, used to indicate the byte length of the corresponding SDAP SDU.

[0094] E: Extended field, used to indicate whether the corresponding SDAP SDU is the last SDAP SDU in the SDAP PDU. When the E field is set to "1", it means that there is at least one more SDAP SDU to follow; when the E field is set to "0", it means that the SDAP SDU is the last one.

[0095] The other fields are the same as those defined in the current 3GPP technical specification TS 37.324.

[0096] For a sending SDAP entity configured and with enhanced encapsulation enabled, the SDAP entity can first identify multiple SDUs that need to be transmitted synchronously from one or more QoS flows. For example, multiple SDUs from the same QoS flow and belonging to the same PDU set can be transmitted synchronously. For multiple SDUs from multiple QoS flows, the synchronization transmission requirement can be identified using synchronization transmission indication information carried with the SDU. For example, the synchronization transmission indication information may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDU used for synchronization transmission; the range may be predefined or configurable. Subsequently, the sending SDAP entity multiplexes the multiple SDUs into a single SDAP PDU and sends it to the lower-layer protocol entity.

[0097] Furthermore, if the total length of two or more SDUs spliced ​​and encapsulated into an SDAP PDU exceeds the maximum size limit of a single SDAPPDU, the transmitting SDAP entity can encapsulate the multiple SDUs into multiple SDAP PDUs.

[0098] At the receiving SDAP entity, based on the relevant configuration for enhanced encapsulation, the SDAP PDU is decapsulated into one or more SDUs according to the SDAP PDU format and sent to the upper-layer protocol entity (e.g., the application layer) in the form of a QoS stream. The decapsulation process may include removing the header and restoring the SDU concatenation operation.

[0099] Example 2: PDCP Multiplexing When one or more QoS flows are mapped to the same DRB and are configured with synchronous transmission requirements, the sending SDAP entity corresponding to the DRB identifies multiple SDUs that need to be synchronously transmitted from the one or more QoS flows based on the synchronous transmission indication information carried with the SDU. For example, multiple SDUs from the same QoS flow and belonging to the same PDU set can be synchronously transmitted. For multiple SDUs from multiple QoS flows, the synchronous transmission indication information can be a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDUs used for synchronous transmission; the range can be predefined or configurable. Subsequently, the SDAP entity sends the SDAP PDU and the synchronous transmission indication information together to the lower-layer PDCP entity. The synchronous transmission indication information here can be the synchronous transmission indication information carried with the SDUs of the QoS flows, or it can be converted but functionally equivalent or similar synchronous transmission indication information.

[0100] Enhanced encapsulation functionality supporting PDCP entities can be implemented in the following two ways: Method 1: Control plane-based configuration When a PDCP entity needs to support enhanced encapsulation functionality, it needs to configure information related to the enhanced encapsulation function to both the transmitting and receiving PDCP entities (i.e., the PDCP layer entities in the transmitting and receiving devices). Specifically, on the UE side, the base station (gNB) can configure relevant information for the enhanced PDCP encapsulation function to the PDCP entity via downlink control signaling (e.g., RRC messages). As an example, based on the existing PDCP configuration information element (IE) in the standard, relevant configuration information for the enhanced encapsulation function is introduced. The required configuration information includes at least the configuration information for enabling the enhanced encapsulation function for SDU splicing for synchronous transmission in the PDCP entity during uplink and / or downlink.

[0101] For PDCP entities configured with enhanced encapsulation for synchronous transmission, the transmitting and receiving PDCP entities can support SDU multiplexing using one or more enhanced PDCP PDU formats based on existing PDCP PDU formats. See also Figure 12 and Figure 13 This illustration shows some examples of enhanced PDCPPDU formats designed based on the current 3GPP technical specification TS 38.323.

[0102] The fields in the PDU format are described below: L: Length field, used to indicate the byte length of the corresponding PDCP SDU.

[0103] E: Extended field, used to indicate whether the corresponding PDCP SDU is the last PDCP SDU in the PDCP PDU list. When the E field is set to "1", it means that there is at least one more PDCP SDU to follow; when the E field is set to "0", it means that the PDCP SDU is the last one.

[0104] The other fields are the same as those defined in the current 3GPP technical specification TS 38.323.

[0105] For a transmitting PDCP entity configured and with enhanced encapsulation enabled, the PDCP entity can encapsulate multiple SDUs into a single PDCP PDU based on the received SDUs and associated synchronization transmission indication information. The synchronization transmission indication information may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDUs used for synchronization transmission; this range may be predefined or configurable. Subsequently, the PDCP PDU is sent to the lower-layer protocol entity in an enhanced PDU format containing multiple SDUs.

[0106] Furthermore, if the total length of two or more SDUs encapsulated in a PDCP PDU exceeds the maximum size limit of a single PDCP PDU, the transmitting PDCP entity can encapsulate the multiple SDUs into multiple PDCP PDUs.

[0107] At the receiving end PDCP entity, based on the relevant configuration for enhanced encapsulation functionality, the PDCP PDU is decapsulated into one or more SDUs according to the PDCP PDU format, and then sent to the SDAP protocol entity in the form of SDAP PDUs. The decapsulation process may include removing the header and restoring the SDU concatenation operation.

[0108] Method 2: User-plane-based instructions.

[0109] For user-plane-based indications of enhanced encapsulation functionality used for synchronous transmission, both the transmitting and receiving PDCP entities should support one or more enhanced PDCP PDU formats, in addition to the existing PDCP PDU formats, to indicate whether a PDCP PDU includes multiple Service Data Units (SDUs). See also Figure 14 and Figure 15 This illustration shows some examples of enhanced PDCP PDU formats designed based on the current 3GPP technical specification TS 38.323.

[0110] One or more of the following methods can be used to confirm whether the sending-end PDCP entity and the receiving-end PDCP entity support the user plane-based enhanced encapsulation feature indication for synchronous transmission: - The base station (gNB) indicates to the UE its support for enhanced encapsulation features and associated enhanced PDCP PDU formats by explicitly or implicitly broadcasting system information (e.g., System Information Block (SIB)) or through dedicated Radio Resource Control (RRC) signaling. For example, the gNB implicitly indicates to the UE the new radio (NR) specification version it supports, which defines one or more enhanced PDCP PDU formats. - The UE reports its capabilities to the gNB via dedicated RRC signaling, indicating that the UE supports enhanced encapsulation functionality and related enhanced PDCP PDU formats; -gNB configures the UE with configuration information based on the UE's reported UE capabilities, including enabling enhanced encapsulation functions and the relevant enhanced PDCP PDU formats supported by the UE.

[0111] The fields in the PDU format are described below: MI: Multiplexing Indicator field, used to indicate whether multiple SDUs are multiplexed in this PDU. When the MI field is set to "1", it means that multiple SDUs are multiplexed in this PDU and the enhanced PDU format is used; when the MI field is set to "0", it means that the existing PDU format is used and the PDU includes only one SDU.

[0112] L: Length field, used to indicate the byte length of the corresponding SDAP SDU.

[0113] E: Extended field, used to indicate whether the corresponding SDAP SDU is the last SDAP SDU in the SDAP PDU. When the E field is set to "1", it means that there is at least one more SDAP SDU to follow; when the E field is set to "0", it means that the SDAP SDU is the last one.

[0114] The other fields are the same as those defined in the current 3GPP technical specification TS 38.323.

[0115] For a transmitting PDCP entity with enhanced encapsulation enabled, the PDCP entity can encapsulate multiple SDUs into a single PDCP PDU based on the received SDUs and associated synchronization transmission indication information. The synchronization transmission indication information may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDUs used for synchronization transmission; the range may be predefined or configurable. Subsequently, the MI field is set accordingly based on the encapsulation configuration, and the PDU in the format containing SDU encapsulation is sent to the lower-layer protocol entity.

[0116] Furthermore, if the total length of two or more SDUs encapsulated in a PDCP PDU exceeds the maximum size limit of a single PDCP PDU, the transmitting PDCP entity can encapsulate the multiple SDUs into multiple PDCP PDUs.

[0117] For a receiving PDCP entity with enhanced encapsulation enabled, the receiving PDCP entity can determine whether a PDU encapsulates multiple SDUs based on the value of the MI field, and process the PDU accordingly. When the MI field is "1", the PDU is decapsulated into multiple SDUs according to the enhanced PDCP PDU format for SDU multiplexing; when the MI field is "0", the PDU is decapsulated into a single SDU according to the existing PDU format. The one or more SDUs are sent to the SDAP protocol entity in the form of SDAPPDU. The decapsulation process may include removing the header and restoring the SDU concatenation operation.

[0118] Example 3: RLC Multiplexing To support RLC reuse (i.e., enhanced packaging functionality), the following approach can be used: - In cases where synchronous transmission is required and one or more Quality of Service (QoS) streams are mapped to the same Data Radio Bearer (DRB), the transmitting SDAP entity and PDCP entity corresponding to the DRB identify one or more Service Data Units (SDUs) that need to be synchronously transmitted based on synchronous transmission indication information associated with one or more SDUs. For example, multiple SDUs from the same QoS stream and belonging to the same PDU set can be synchronously transmitted. For multiple SDUs from multiple QoS streams that need to be synchronously transmitted, the synchronous transmission indication information carried with the SDUs may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDUs used for synchronous transmission. The range may be predefined or configurable.

[0119] - During the processing of SDUs (including receiving SDUs from upper-layer entities and forming PDUs and sending them to lower-layer entities), the sending SDAP and PDCP entities need to maintain the association between the SDUs and / or PDUs and their corresponding synchronization transmission indication information. The synchronization transmission indication information here can be the synchronization transmission indication information carried by the SDUs along with the QoS flow, or it can be a converted synchronization transmission indication information that is functionally equivalent or similar.

[0120] The basic principle of enhanced encapsulation functionality in the RLC layer is similar to that in the PDCP layer. For control plane configuration-based solutions, a similar approach to PDCP multiplexing is required to configure information related to enhanced encapsulation functionality to both the transmitting and receiving RLC entities. The transmitting and receiving RLC entities (i.e., the RLC layer entities in the transmitting and receiving devices) can support enhanced encapsulation functionality using one or more enhanced RLC PDU formats based on existing RLC PDU formats to achieve SDU encapsulation. See also Figures 16 to 21 This illustration shows some examples of enhanced RLC PDU formats designed based on the current 3GPP technical specification TS 38.322.

[0121] The fields in the PDU format are described below: L: Length field, used to indicate the byte length of the corresponding RLC SDU.

[0122] E: Extended field, used to indicate whether the corresponding RLC SDU is the last RLC SDU in the RLC PDU. When the E field is set to "1", it means that there is at least one more RLC SDU to follow; when the E field is set to "0", it means that the RLC SDU is the last one.

[0123] The other fields are the same as those defined in the current 3GPP technical specification TS 38.322.

[0124] Similarly, for a transmitting RLC entity configured and enabled with enhanced encapsulation, the RLC entity can encapsulate multiple SDUs into a single RLC PDU based on the received SDUs and associated synchronization transmission indication information. The synchronization transmission indication information may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDUs used for synchronization transmission; this range may be predefined or configurable. Subsequently, the RLC PDU is sent to the lower-layer protocol entity in PDU format containing the encapsulated SDUs.

[0125] Furthermore, if the total length of two or more SDUs encapsulated in an RLC PDU exceeds the maximum size limit of a single RLC PDU, the transmitting RLC entity can multiplex the multiple SDUs and encapsulate them into multiple RLC PDUs.

[0126] At the receiving RLC entity, based on the relevant configuration for enhanced encapsulation functionality, the RLC PDU is decapsulated into one or more SDUs according to the RLC PDU format, and sent to the PDCP protocol entity in the form of PDCP PDUs. The decapsulation process may include removing the header and restoring the SDU concatenation operation.

[0127] Example 4: MAC Multiplexing MAC multiplexing (i.e., enhanced encapsulation) can be used to multiplex multiple Service Data Units (SDUs) from the same Data Radio Bearer (DRB) or from multiple DRBs for the same User Equipment (UE). To support MAC multiplexing, the following methods can be used: - For each DRB participating in synchronous transmission multiplexing, the sending end SDAP, PDCP, and RLC entities corresponding to that DRB identify one or more SDUs that need to be synchronized based on the synchronization transmission indication information carried with the SDU. For example, multiple SDUs from the same Quality of Service (QoS) stream and belonging to the same PDU set can be synchronized. For multiple SDUs from multiple QoS streams, the synchronization transmission indication information carried with the SDU may include a set or range of timestamps, sequence numbers (SNs), or synchronization sequence numbers (SSNs) associated with the SDU used for synchronization transmission. The range may be predefined or configurable. - During the processing of SDUs (including receiving SDUs from upper-layer entities, encapsulating the received SDUs into PDUs for transmission to lower-layer entities), the sending-end SDAP, PDCP, and RLC layer entities need to maintain the association between the SDUs and / or PDUs and their corresponding synchronization transmission indication information so that the MAC layer entity can perform synchronization transmission scheduling. The synchronization transmission indication information here can be the synchronization transmission indication information carried by the SDUs along with the QoS flow, or it can be converted but functionally equivalent or similar synchronization transmission indication information.

[0128] For scenarios where multiple SDUs are encapsulated or multiplexed for synchronous transmission from multiple DRBs to a single UE, a synchronization DRB group can be configured to establish synchronization relationships between DRBs. One DRB can be configured as a master DRB, serving as a reference for synchronization operations (e.g., synchronization configuration, synchronization detection, and synchronization transmission). The master DRB can also be referred to as a reference DRB. The configuration information of the synchronization DRB group includes at least one of the following: - DRB group identifier for synchronized DRB groups; - The DRB identifier of member DRBs in the synchronization DRB group; and - Primary DRB information, which includes the primary DRB identifier in the synchronization DRB group and the timing information of the primary DRB.

[0129] The timing information includes at least one of the following: the periodicity of the primary DRB, jitter, and data arrival time.

[0130] Synchronization relationships between multiple DRBs can also be configured based on a Logical Channel Group (LCG), where each LCG includes a Logical Channel (LCH) corresponding to a DRB. In other words, logical channels with synchronization relationships can be mapped to the same LCG, and one or more primary logical channels can be optionally configured for each LCG. The configuration information of the LCG includes at least one of the following: - The LCG identifier for synchronized LCG; - The logical channel identifier of the member logical channel in the LCG; - Main logical channel information, which includes the main logical channel identifier and timing information of the main logical channel in the LCG.

[0131] The timing information includes at least one of the following: the periodicity, jitter, and data arrival time of the data corresponding to the main QoS stream / main DRB.

[0132] Among the multiple logical channels in the LCG, one of the logical channels is the main logical channel. The main logical channel carries a media component of a multimodal service (such as an XR service) and is used as a reference for other logical channels carrying media components of multimodal services in synchronization operations (such as synchronization configuration, synchronization detection, and synchronization transmission).

[0133] The above-described configuration for synchronization transmission between DRBs applies to both uplink transmission (UE to gNB) and downlink transmission (gNB to UE). For uplink synchronization DRB groups or synchronization LCGs, the base station (gNB) can configure the relevant information of the aforementioned synchronization DRB group or LCG to the UE via downlink control signaling (e.g., Radio Resource Control (RRC) messages). In one embodiment of the present invention, radio resource scheduling for SDUs of the primary DRB takes precedence over radio resource scheduling for SDUs of member DRBs.

[0134] - Downlink multiplexing for synchronous transmission: When a MAC layer entity performs downlink transmission scheduling, for the same DRB, if multiple RLC SDUs or RLC PDUs have the same or related synchronization transmission indication information, the RLC SDUs or RLC PDUs should be multiplexed into the same MAC PDU, or multiplexed into multiple MAC PDUs that are adjacent to each other or close in time.

[0135] For multiple DRBs, based on the configuration of the synchronous DRB group or synchronous LCG, one or more RLC SDUs or RLC PDUs in the primary DRB are scheduled first, followed by scheduling one or more RLC SDUs or RLC PDUs with the same or related synchronization transmission indication information in other member DRBs in the synchronous DRB group. The RLC SDUs or RLC PDUs are then multiplexed into the same MAC PDU, or multiplexed into multiple MAC PDUs that are adjacent to each other or close in time.

[0136] - Uplink multiplexing for synchronous transmission: To support uplink transmission scheduling, the UE reports the buffer status of data packets to the gNB via a Buffer Status Report (BSR). For synchronous transmission based on synchronous DRB groups or synchronous LCGs, the BSR mechanism based on LCGs can be further enhanced to support synchronous transmission.

[0137] Example 4.1: Buffer size for reporting data to be sent in BSR based on different time ranges.

[0138] In order to report the buffer size of data to be sent in the Buffer Status Report (BSR) based on different time ranges, the BSR needs to include one or more of the following information: - Logical Channel Group (LCG) identifier; - The size of the buffer for one or more time ranges; and - Information on one or more time ranges corresponding to the size of the buffer, including the specific value of each time range, or indication information for indicating each time range, such as an index for looking up the actual value of a time range in a table, or sequence number information for representing a series of predefined time ranges.

[0139] The following is an example in which the buffer size is calculated and reported based on one or more periods of the main QoS flow.

[0140] A multimodal service includes three distinct QoS streams (audio, visual, and haptic), with QoS stream identifiers (QFIs) of 1, 2, and 3, respectively. The three QoS streams are mapped to the same DRB and correspond to the same logical channel (LCH, ID=1) and the same logical channel group (LCG, ID=1); alternatively, the three QoS streams are mapped to different DRBs and correspond to different logical channels (LCH, IDs 1, 2, and 3 respectively), but are all mapped to the same LCG (ID=1). The data packets of the three QoS streams are periodic, but with different periods. Figure 22As shown, the audio stream is used as the primary QoS stream, primary DRB, or primary LCH to calculate the buffer size based on the different periodicity of audio data packets. The sending MAC entity reports the calculated buffer size in a BSR. The buffer size for each period includes all data packets that need to be transmitted synchronously within that period. Using the earliest arriving packet (a PDU or set of PDUs) as a reference point, the buffer size of data arriving in the first period is counted as the buffer size of the first period (or first cycle); the buffer size of data packets arriving in the second period is counted as the buffer size of the second period (or second cycle), and so on. The calculation results for each period are shown in Table 2.

[0141] Table 2

[0142] See Figure 23 To illustrate how to report buffer sizes in a BSR based on different time ranges, an example of an enhanced BSR format supporting only five time ranges is shown, where each time range corresponds to a different period. Values ​​for each field are indicated in parentheses.

[0143] Example 4.2: Reporting buffer size while considering synchronization requirements between different QoS streams.

[0144] The following example shows how the periodicity and synchronization requirements between the main QoS flow and member QoS flows are considered when calculating and reporting the buffer size.

[0145] Table 3 illustrates the synchronization requirements between audio streams, visual streams, and tactile streams: Table 3

[0146] In this example, the audio stream is the primary QoS stream, and the corresponding synchronization requirements can be represented as shown in Table 4: Table 4

[0147] A multimodal service includes three distinct QoS streams (audio, visual, and haptic), with QoS stream identifiers (QFIs) of 1, 2, and 3, respectively. The three QoS streams are mapped to the same DRB and correspond to the same LCH (ID=1) and the same LCG (ID=1); or they are mapped to different DRBs and correspond to different LCHs (IDs 1, 2, and 3 respectively), but are all mapped to the same LCG (ID=1). The data packets of the three QoS streams have different periodicities. Figure 24As shown, the audio stream is carried as the main QoS stream, main DRB, or main LCH. Compared to the audio QoS stream, the synchronization latency requirements for the visual QoS stream and haptic QoS stream are 20ms and 25ms, respectively.

[0148] The BSR configuration is set to use the periodicity of the audio QoS stream as the BSR period, and the buffer size is calculated based on the audio QoS stream data packets (PDUs or sets of PDUs) and the maximum synchronization latency between all QoS streams. That is, for each period, the buffer size includes the audio (voice) QoS stream data packets within that period, as well as data packets from other QoS streams arriving in the subsequent 25 millisecond timeframe. Figure 24 As shown, the buffer sizes for BSR reporting in each period are 100 bytes, 120 bytes, 60 bytes and 30 bytes respectively. In the third and fourth periods, data packets of 70 bytes and 30 bytes respectively were discarded because they exceeded the maximum synchronization delay requirement.

[0149] Example 4.3: Detection and reporting of asynchronous uplink synchronous transmission.

[0150] To enable the gNB to perform uplink synchronous transmission scheduling more efficiently, the UE can detect asynchronous situations in uplink synchronous transmission and report asynchronous status information to the gNB.

[0151] The MAC entity used for uplink synchronization transmission can detect whether two or more arriving SDUs are asynchronous, based on the synchronization transmission indication information of the SDU and / or the configured synchronization requirements. For example... Figure 25 As shown, according to the synchronization transmission indication information, PDU set 2 from LCH1 and LCH2 should be transmitted synchronously. The MAC entity can compare the arrival time difference of the two PDU sets 2 with the configured synchronization requirement. In one embodiment, the synchronization requirement can be a synchronization threshold. When the arrival time difference (Diff-time) between two or more SDUs is greater than the synchronization threshold, the MAC entity can determine that the SDUs are asynchronous. In one embodiment, SDUs from the main LCH are considered as references for comparison with SDUs from other LCHs.

[0152] When an asynchronous event occurs, a status report of the event can be triggered and sent to the gNB. This trigger can be a Buffered Status Report (BSR) used to report asynchronous status information.

[0153] In another embodiment, if the number of asynchronous events occurring within a predefined or configured time range exceeds a predefined or configured threshold, a BSR for reporting asynchronous status information can be triggered.

[0154] In another alternative embodiment, if the ratio of asynchronous SDUs to synchronous SDUs, or the total number of asynchronous SDUs within a predefined or configured time range, exceeds a predefined or configured threshold, a BSR for reporting asynchronous SDU status information can be triggered.

[0155] To report asynchronous status information, a new MAC control unit (MAC CE) needs to be defined for asynchronous status information reporting. An example is shown below. Figure 26 and Figure 27 As shown.

[0156] like Figure 26 As shown, a one-bit indicator field, named Asyncindi, is introduced for each LCG to indicate the asynchronous state. When an asynchronous event occurs in an LCG, the corresponding "Asyncindi" field is set to "1", otherwise it is set to "0".

[0157] like Figure 27 As shown, in addition to the one-bit indicator field, a one-byte parameter named Diff-time is introduced for each LCG, used to report asynchronous status information. When an asynchronous event occurs in an LCG, the corresponding indicator field is set to "1", and the corresponding Diff-time parameter is included in the same BSR; otherwise, the corresponding indicator field is set to "0", and the corresponding Diff-time parameter is not included in the same BSR. The reported Diff-time value can be the maximum, average, or minimum difference between multiple SDUs.

[0158] In another embodiment, the Diff-time can be a row index or column index of a table, in which a corresponding actual time difference is defined for each index. The table can be designed using a linear or exponential incrementing method.

[0159] In another embodiment, the ratio of asynchronous SDUs to synchronous SDUs, or the total number of asynchronous SDUs within a predefined or configured time range, can also be reported in the BSR.

[0160] Example 5: Logical Channel Priority (LCP) and Timing Control For uplink transmissions using Configured Grant (CG) resources, especially when using multi-PUSCH CG resources (i.e., multiple PUSCH CG transmission opportunities exist within a single PUSCH CG cycle), data packets in the buffer can be processed in one or more of the following ways, which are applicable to the MAC multiplexing method described above: Uplink transmission scheduling of data packets in the buffer is performed according to the remaining time order of data packets in the multi-PUSCH configuration grant resources. During this process, the MAC layer performs Logical Channel Prioritization (LCP), where data packets with shorter remaining time are prioritized over data packets with longer remaining time, using either an earlier transmission opportunity or an earlier Physical Uplink Shared Channel (PUSCH) configuration grant (CG) for transmission. The remaining time is used to assess the remaining time required for one or more data packets to complete transmission on the Uu interface. For example, among multiple transmission opportunities (TOs) in the multi-PUSCH configuration grant resources, data packets with shorter remaining time are transmitted using an earlier TO in the time domain, while data packets with longer remaining time are transmitted using a later TO in the time domain; or, among multiple multi-PUSCH configuration grant resources, data packets with shorter remaining time are transmitted using an earlier multi-PUSCH configuration grant resource in the time domain, while data packets with longer remaining time are transmitted using a later multi-PUSCH configuration grant resource in the time domain. The remaining time can be determined based on a timer for a specific SDU, PDU, or set of PDUs, such as a discard timer, a packet delay budget (PDB) for a specific SDU or PDU, or a PDU set delay budget (PSDB) for a set of PDUs. The data packets can be SDUs or PDUs.

[0161] For the same DRB, if multiple RLC SDUs or RLC PDUs have the same or related synchronization transmission indication information, they are preferably encapsulated into one or more adjacent or subsequent MAC PDUs and transmitted in one or more adjacent or subsequent transmission opportunities. For multiple DRBs, depending on the configuration of the synchronization DRB group, multiple DRBs, or logical channel groups (LCGs), one or more RLC SDUs or RLC PDUs with the same or related synchronization transmission indication information in the primary DRB are prioritized for scheduling. Subsequently, one or more RLCSDUs or RLC PDUs with the same or related synchronization transmission indication information in other member DRBs of the synchronization DRB group are scheduled, and the RLC SDUs or RLC PDUs are encapsulated into one or more adjacent or subsequent MAC PDUs and transmitted in one or more adjacent or subsequent transmission opportunities. The adjacent or subsequent transmission opportunities can be multiple transmission opportunities within the same multi-PUSCH configuration grant, or multiple transmission opportunities between multiple multi-PUSCH configuration grants. In this process, the MAC layer performs Logical Channel Priority (LCP), in which radio resource scheduling of data packets with the same or related synchronization transmission indication information in the primary DRB of the synchronization DRB group takes precedence over radio resource scheduling of data packets with the same or related synchronization transmission indication information in the member DRBs of the synchronization DRB group, and the data packets scheduled with priority are transmitted using an earlier transmission opportunity or an earlier PUSCH configuration grant.

[0162] For multiple DRBs or logical channels (LCHs) with synchronous transmission requirements and different priorities, the following rules can be applied: - When scheduling radio resources for data packets in multiple DRBs or LCHs with synchronous transmission requirements and different priorities, the MAC layer performs logical channel priority (LCP) based on the priority of the primary DRB in the synchronous DRB group or the primary LCH in the LCG. - In one embodiment of the present invention, when radio resource scheduling based on data packet synchronization transmission requirements conflicts with radio resource scheduling based on data packet priority, the MAC layer executes Logical Channel Priority (LCP) to make radio resource scheduling based on data packet synchronization transmission requirements take precedence over radio resource scheduling based on data packet priority. - In one embodiment of the present invention, radio resource scheduling of data packets based on synchronization transmission requirements takes precedence over radio resource scheduling of data packets based on data packet priority. - For example, an asynchronous event can be triggered when the delay between data packets of different media components of the same service with synchronous transmission requirements exceeds a predetermined threshold. The threshold can also be configured to the UE by the base station (gNB) via downlink control signaling (e.g., Radio Resource Control (RRC) messages).

[0163] Example 6: Packet Discarding For received data packets that exceed the synchronous transmission requirements between different Quality of Service (QoS) streams in the service, one or more of the following processing methods can be adopted for the SDAP, PDCP, or MAC multiplexing methods mentioned above: - The protocol layer entity directly discards the data packet; - Protocol layer entities perform packet dropping based on configuration information. If a dropping operation is configured for received data packets exceeding synchronization transmission requirements, the MAC layer entity drops the data packets; otherwise, the protocol layer entity processes the data packets normally. For uplink transmissions, the configuration information is sent from the base station (gNB) to the UE via downlink control signaling (e.g., Radio Resource Control (RRC) messages). If the received data packet exceeds the synchronization transmission requirement by a predetermined threshold, the protocol layer entity discards the data packet; otherwise, the MAC layer entity processes the data packet normally. For uplink transmission, the predetermined threshold can be predefined by the standard, or calculated based on synchronization requirement parameters, such as a predefined ratio, or sent by the gNB to the UE via downlink control signaling (e.g., RRC message); alternatively, the predetermined threshold can be directly sent by the gNB to the UE via downlink control signaling (e.g., RRC message).

[0164] In one embodiment of the present invention, the protocol layer performs packet dropping processing on data packets in different QoS streams, different Data Radio Bearers (DRBs), or different Logical Channels (LCHs) with synchronization requirements, the processing being based on one or more of the following attributes: - Different QoS flows with synchronization requirements, different DRBs, or different LCH priorities; - The importance of different QoS flows, different DRBs, or different LCHs with synchronization requirements.

[0165] In one embodiment of the present invention, the protocol layer is a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and / or a Medium Access Control (MAC) layer. The protocol layer performs packet dropping processing on data packets in different QoS streams with synchronization requirements based on one or more of the following attributes: - Prioritization of different QoS flows with synchronization requirements; - The importance of different QoS flows with synchronization requirements; - A membership attribute of a QoS flow carrying at least one of the data packets, wherein the membership attribute indicates whether the QoS flow is the primary QoS flow among a plurality of QoS flows; and - The synchronization transmission parameters of the data packets and the threshold values ​​of these parameters.

[0166] In one embodiment of the present invention, the protocol layer is a Packet Data Convergence Protocol (PDCP) layer or a Radio Link Control (RLC) layer. The protocol layer performs packet dropping processing on data packets in different DRBs with synchronization requirements based on one or more of the following attributes: - Priorities of different DRBs with synchronization requirements; - The importance of different DRBs with synchronization requirements; - A member attribute of a DRB carrying at least one of the data packets, wherein the member attribute indicates whether the DRB is the primary DRB among a plurality of DRBs; and - The synchronization transmission parameters of the data packets and the threshold values ​​of these parameters.

[0167] In one embodiment of the present invention, the protocol layer is a Media Access Control (MAC) layer; the protocol layer performs packet dropping processing on data packets in different logical channels (LCHs) with synchronization requirements based on one or more of the following attributes: - The priority of different LCHs with synchronization requirements; - The importance of different LCHs with synchronization requirements; - A member attribute of an LCH carrying at least one of the data packets, wherein the member attribute indicates whether the LCH is the primary LCH among a plurality of LCHs; and - The synchronization transmission parameters of the data packets and the threshold values ​​of these parameters.

[0168] In one embodiment of the invention, the threshold of the parameter is provided via downlink control signaling (e.g., an RRC message). In another embodiment of the invention, one or more of the above attributes are enabled according to a configuration for packet dropping.

[0169] On the other hand, when transmission congestion occurs, data packets between multiple QoS streams / DRB / LCH with synchronous transmission requirements can be processed in one or more of the following ways, which are applicable to the SDAP, PDCP and MAC multiplexing methods described above: - Protocol layer entities discard data packets based on the priority or importance of QoS streams / DRBs / LCHs without considering synchronization transmission requirements; - While ensuring the normal transmission of data packets in the main QoS stream / DRB / LCH, the protocol layer entity discards data packets of member QoS streams / DRB / LCH in the synchronous QoS stream / DRB / LCH based on priority or importance; - Protocol layer entities discard data packets from one or more QoS streams / DRBs / LCHs in the synchronization QoS stream / DRB / LCH based on indication information dynamically sent by the base station (gNB) to the UE (e.g., via MAC control unit (MAC CE) or downlink control information (DCI)). The indication information may be a threshold value for parameters related to synchronization transmission, such as a priority or importance value or a value index; data packets with parameters greater than or less than the threshold may be discarded. - Protocol layer entities perform packet dropping based on configuration information. For example, in one configuration, the protocol layer entity drops data packets based on the priority or importance of QoS flows / DRB / LCH; alternatively, the protocol layer entity can selectively drop data packets belonging to member QoS flows / DRB / LCHs within synchronous QoS flows / DRB / LCHs based on their priority or relevance, while ensuring the normal transmission of data packets belonging to the main QoS flows / DRB / LCHs. For uplink transmission, the configuration information is sent from the gNB to the UE via downlink control signaling (e.g., RRC messages). - As an alternative, the protocol layer entity can implement a selective dropping policy for data packets belonging to the member QoS stream / DRB / LCH in the synchronous QoS stream / DRB / LCH based on the priority or importance (or relevance) of the member QoS stream / DRB / LCH, while ensuring the normal transmission of data packets belonging to the main QoS stream / DRB / LCH.

[0170] After data packets are discarded, one or more of the following processes can be performed: - The sending entity sends information about the discarded data packets (such as sequence number (SN) information) to the receiving entity through the corresponding control PDU. The receiving entity adjusts the receiving window based on the received SN information. - For uplink transmissions based on MAC multiplexing, a new Buffer Status Report (BSR) is triggered; or, when the size of the dropped data packets exceeds a predetermined threshold, a new BSR is triggered, wherein the predetermined threshold is predefined or sent to the UE by the gNB via downlink control signaling (e.g., RRC message); - For MAC-based uplink transmissions, if an existing BSR is triggered in whole or in part due to dropped data packets, the protocol layer entity cancels the BSR and the associated scheduling request (SR).

[0171] Example 7: Reporting of Upstream Business Perception Information To configure uplink synchronization transmission, the user equipment (UE) can send uplink service-aware information to the base station (gNB) in one of the following ways: - UE Assistance Information (UAI); - Medium Access Control (MAC) control element (CE); and - Uplink Control Information (UCI).

[0172] The uplink service awareness information is sent from the user equipment (UE) to the base station and includes one or more of the following: - Information about the primary Quality of Service (QoS) stream and information about the member QoS streams, wherein the member QoS streams need to be transmitted synchronously with the primary QoS stream; - Information about the primary Data Radio Bearer (DRB) and member DRBs, wherein the member DRBs need to be synchronized with the primary DRB; or - Information about the main logical channel (LCH) and member LCHs, wherein the member LCHs need to be transmitted synchronously with the main LCH.

[0173] The information of the main QoS flow includes the QoS flow identifier, periodicity, jitter, and data arrival time of the main QoS flow; the information of the member QoS flows includes the QoS flow identifier, periodicity, jitter, and data arrival time of each member QoS flow.

[0174] The information of the primary DRB includes the DRB identifier, periodicity, jitter, and data arrival time of the primary DRB; the information of the member DRBs includes the DRB identifier, periodicity, jitter, and data arrival time of each member DRB.

[0175] The information of the main LCH includes the logical channel identifier, periodicity, jitter, and data arrival time of the main LCH; the information of the member LCH includes the logical channel identifier, periodicity, jitter, and data arrival time of each member LCH.

[0176] The timing of the UE sending uplink service awareness information to the gNB includes one or more of the following: - Before allocating relevant radio resources for the service, i.e. before performing the corresponding radio resource control (RRC) reconfiguration process, the uplink service awareness information is sent to the base station or gNB; - Periodic reporting: After completing the allocation of relevant radio resources for the service, the UE periodically sends the uplink service awareness information to the base station or gNB. - Timer-based reporting: The UE can configure and start a timer during the relevant RRC reconfiguration process, and report the uplink service awareness information when the timer expires. That is, after completing the relevant radio resource allocation for the service, the UE sends the uplink service awareness information to the base station or gNB when the timer expires; if there is a new configuration process or other reasons that trigger the reporting of the uplink service awareness information before the timer expires, the timer is reset and restarted. When the change of one or more parameters related to uplink service awareness information exceeds one or more predetermined thresholds, the UE performs a reporting operation during service operation and after the relevant radio resource allocation for the service is completed. Specifically, when the change in uplink service awareness information exceeds the threshold, the UE sends the uplink service awareness information to the base station or gNB. The predetermined thresholds can be predefined by a standard; or, the predetermined thresholds can be calculated based on the uplink service awareness information. For example, the thresholds can be expressed as a ratio, which is predefined, or sent by the gNB to the UE via downlink control signaling (e.g., RRC messages); the predetermined thresholds can also be sent by the gNB to the UE via downlink control signaling (e.g., RRC messages).

[0177] Figure 28A block diagram illustrating a wireless communication example system 700 according to an embodiment of the present invention is shown. The embodiments described herein can be implemented in the system by any suitably configured hardware and / or software. Figure 28 As shown, the system 700 includes a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage device 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, and the above components are coupled to each other as shown in the figure.

[0178] The processing unit 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of a general-purpose processor and a special-purpose processor (e.g., a graphics processor, an application processor). The processor may be coupled to the memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems running in the system.

[0179] The wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuit can provide communication capabilities compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuit can support communication with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments where the baseband circuit is configured to support wireless communication using multiple wireless protocols may be referred to as multimode baseband circuits. In different embodiments, the baseband circuit 720 may further include circuitry for processing signals that are not strictly within the baseband frequency range, such as circuitry for processing intermediate frequency signals between the baseband frequency and the radio frequency.

[0180] In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, or smartphone. In various embodiments, the system may include more or fewer components and / or employ different architectures. Where appropriate, the methods described herein may be implemented as a computer program, which may be stored in a storage medium, such as a non-transitory storage medium.

[0181] Embodiments of the present invention are combinations of a set of technologies and / or processing procedures that can be incorporated into 3GPP technical specifications to form terminal products.

[0182] When software functional units are implemented and used or sold in the form of a product, they can be stored in a computer-readable storage medium. Based on the above understanding, the technical solutions proposed in this invention can be implemented in whole or in part in the form of software products; or, the parts of the technical solutions that have beneficial effects on the prior art can also be implemented in the form of software products. The software product is stored in a storage medium, which includes multiple instructions for causing a computing device (e.g., a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this invention. The storage medium includes, but is not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), floppy disks, or other media capable of storing program code.

[0183] Although the invention has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that the invention is not limited to the disclosed embodiments, but is intended to cover various modifications and equivalent arrangements that may be made without departing from the widest scope of interpretation defined by the appended claims.

Claims

1. A wireless communication method for a wireless communication device, characterized in that, include: Receive multiple Service Data Units (SDUs) for synchronization transmission and synchronization transmission indication information from the upper protocol layer; Based on the synchronization transmission indication information, the plurality of SDUs are encapsulated into one or more Protocol Data Units (PDUs) for synchronization transmission in the protocol layer; as well as The one or more PDUs are provided to the lower protocol layer for synchronous transmission.

2. The wireless communication method according to claim 1, characterized in that: When the combined length of the multiple SDUs does not exceed the maximum payload size of a PDU in the protocol layer, the multiple SDUs are encapsulated into a PDU in the protocol layer in an enhanced PDU format; as well as When the combined length of the multiple SDUs exceeds the maximum payload size of a PDU in the protocol layer, the multiple SDUs are encapsulated into the multiple PDUs of the protocol layer in the enhanced PDU format.

3. The wireless communication method according to claim 2, characterized in that, Send control plane signaling to indicate whether to use a PDU format that supports multiple SDUs for synchronous transmission.

4. The wireless communication method according to claim 2, characterized in that, The fields in the enhanced PDU format of the one or more PDUs indicate whether a PDU format supporting multiple SDUs is used for synchronous transmission.

5. The wireless communication method according to claim 2, characterized in that, The enhanced PDU format is enabled based on at least one of the following: A set of enhanced PDU formats supported by the user equipment (UE) in UE capability reporting; and / or A set of enhanced PDU formats supported by the base station in broadcast or unicast downlink indication messages.

6. The wireless communication method according to claim 1, characterized in that: When the enhanced encapsulation function is enabled according to the configuration information, the plurality of SDUs are encapsulated into one or more PDUs for synchronous transmission based on the synchronization transmission indication information; and The configuration information is transmitted via Radio Resource Control (RRC) messages; or The configuration information includes control plane signaling and is transmitted via Radio Resource Control (RRC) messages, wherein the control plane signaling is used to indicate whether to use a PDU format that supports multiple SDUs for synchronous transmission.

7. The wireless communication method according to claim 6, characterized in that, The protocol layer is the Service Data Adaptation Protocol (SDAP) layer. The configuration information for the enhanced packaging function also includes at least one of the following: The Quality of Service (QoS) stream identifier associated with the SDU used for synchronization transmission; as well as Configuration information used for synchronous transmission requirements, including at least the latency threshold between QoS streams.

8. The wireless communication method according to claim 6, characterized in that, The protocol layer is the Media Access Control (MAC) layer; The configuration information for the enhanced packaging function also includes at least one of the following: A group or multiple DRBs used to establish synchronization relationships between data radio bearers (DRBs); Logical Channel Group (LCG) is used to establish synchronization relationships between logical channels; as well as Configuration information for latency thresholds between QoS streams used for synchronous transmission.

9. The wireless communication method according to claim 8, characterized in that, The configuration information for the DRB group or multiple DRBs includes at least one of the following: DRB group identifier for synchronized DRB groups; The DRB identifier of the member DRB in the synchronized DRB group or multiple DRBs; and The primary DRB information includes the primary DRB identifier in the synchronization DRB group and the timing information of the primary DRB.

10. The wireless communication method according to claim 8, characterized in that, The configuration information used for the LCG includes at least one of the following: The LCG identifier of the LCG; The logical channel identifier of the member logical channel LCH in the LCG; and The main logical channel information includes the main logical channel identifier and the timing information of the main logical channel in the LCG.

11. The wireless communication method according to claim 9 or 10, characterized in that, The timing information includes at least one of the following: the periodicity, jitter, and data arrival time of the data corresponding to the main DRB or main QoS stream.

12. The wireless communication method according to claim 8, characterized in that, For synchronous uplink transmission scheduling, the MAC layer performs buffer status reporting (BSR) based on at least one of the following: LCG logo; Based on the size of one or more buffers corresponding to one or more time ranges of a certain QoS stream / DRB data packets; The size of one or more buffers that conform to the configuration information used for synchronous transmission requirements; as well as One or more synchronization status information between different QoS streams, including: The asynchronous indicator is used to indicate whether data from a particular DRB / QoS stream is synchronized with data from the primary DRB / QoS stream. as well as Differential time is the time difference between the arrival of data between the QoS stream and the main DRB / QoS stream.

13. The wireless communication method according to claim 8, characterized in that, The MAC layer performs asynchronous event detection based on synchronous transmission indication information. When an asynchronous event is detected, or when the number of asynchronous events occurring within a predefined or configured time range exceeds a predefined or configured threshold, or when the ratio of asynchronous SDUs to synchronous SDUs exceeds a predefined or configured threshold, the layer triggers the reporting of asynchronous events or the buffer status report (BSR) for asynchronous event reporting.

14. The wireless communication method according to claim 13, characterized in that, BSRs for asynchronous event reporting include at least one of the following for each LCG: Indication information indicating whether an asynchronous event has occurred in the LCG; The time difference of arrival of two or more SDUs from different flows of the same business in an asynchronous event; as well as The ratio of asynchronous SDUs to synchronous SDUs, or the total number of SDUs within a predefined or configured time range.

15. The wireless communication method according to claim 8, characterized in that, The MAC layer performs Logical Channel Priority (LCP), in which data packets with less remaining time are transmitted using an earlier transmission opportunity or an earlier Multiple Physical Uplink Shared Channel (PUSCH) configuration grant CG relative to data packets with more remaining time. The remaining time is used to assess the remaining time required for one or more data packets to complete transmission on the Uu interface.

16. The wireless communication method according to claim 8 or 9, characterized in that, The MAC layer executes Logical Channel Priority (LCP). In a DRB group, radio resource scheduling of data packets with the same or related synchronization transmission indication information in the primary DRB takes precedence over radio resource scheduling of data packets with the same or related synchronization transmission indication information in the member DRB. The data packets scheduled with priority use an earlier transmission opportunity or an earlier multiple physical uplink shared channel (PUSCH) configuration grant CG for transmission.

17. The wireless communication method according to claim 8, characterized in that, For radio resource scheduling of data packets from multiple DRBs or logical channel LCHs with synchronous transmission requirements and different priorities, the MAC layer performs logical channel priority (LCP) based on the priority of the primary DRB in the DRB group or the primary LCH in the LCG.

18. The wireless communication method according to claim 8, characterized in that, The MAC layer executes Logical Channel Priority (LCP), where when there is a conflict between radio resource scheduling of data packets based on synchronization transmission requirements and radio resource scheduling of data packets based on data packet priority, radio resource scheduling based on synchronization transmission requirements takes precedence.

19. The wireless communication method according to claim 1, characterized in that, The protocol layer performs packet dropping on data packets from different QoS flows, different DRBs, or different LCHs that have synchronization requirements based on at least one of the following attributes: The priorities of different QoS flows, different DRBs, or different LCHs; The importance of different QoS flows, different DRBs, or different LCHs.

20. The wireless communication method according to claim 1, characterized in that, The protocol layer is the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and / or the Media Access Control (MAC) layer. The protocol layer performs packet discarding on data packets requiring synchronization based on at least one of the following attributes: The priority of the data groups; The importance of the data grouping; Member attributes of a QoS flow / DRB / LCH carrying at least one of the data packets, wherein the member attributes indicate whether the QoS flow / DRB / LCH is the primary QoS flow / primary DRB / primary LCH among a plurality of QoS flow / DRB / LCHs; and The synchronization transmission parameters of the data packets and the threshold values ​​of these parameters.

21. The wireless communication method according to claim 1, characterized in that, Uplink service awareness information is sent from the user equipment (UE) to the base station, and the uplink service awareness information includes: Information about the main QoS stream and / or information about the member QoS streams, wherein the member QoS streams need to be transmitted synchronously with the main QoS stream; The information of the main QoS flow includes the QoS flow identifier, periodicity, jitter, and data arrival time of the main QoS flow, and the information of the member QoS flows includes the QoS flow identifier, periodicity, jitter, and data arrival time of each member QoS flow.

22. A wireless communication device, characterized in that, include: A processor configured to invoke and run a computer program stored in a memory to cause a device equipped with the processor to perform the method of any one of claims 1 to 21.

23. A chip, comprising: A processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the method of any one of claims 1 to 21.

24. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer, causes the computer to perform the method of any one of claims 1 to 21.

25. A computer program product comprising a computer program, wherein, when executed by a computer, the computer program causes the computer to perform the method of any one of claims 1 to 21.

26. A computer program, wherein when executed by a computer, the computer program causes the computer to perform the method of any one of claims 1 to 21.

27. A wireless communication method for a wireless communication device, comprising: Receive one or more Protocol Data Units (PDUs) for synchronization transmission from the lower protocol layer; Based on the configuration information for synchronous transmission and / or the PDU format of the PDU for synchronous transmission, the one or more PDUs are decapsulated into multiple Service Data Units (SDUs) for synchronous transmission at the protocol layer. as well as The multiple SDUs are provided to the upper protocol layer for synchronous transmission.

28. The wireless communication method according to claim 27, characterized in that, The concatenation of the multiple SDUs is encapsulated within one or more PDUs of the protocol layer, and adopts an enhanced PDU format.

29. The wireless communication method according to claim 28, characterized in that, Receive control plane signaling to indicate whether the PDU format includes multiple SDUs for synchronous transmission.

30. The wireless communication method according to claim 28, characterized in that, The fields in the enhanced PDU format of the one or more PDUs indicate whether the PDU format includes multiple SDUs for synchronous transmission.

31. The wireless communication method according to claim 27, characterized in that: When the enhanced encapsulation function is enabled according to the configuration information, the plurality of SDUs are decapsulated from the one or more PDUs used for synchronous transmission based on the enhanced PDU format; and The configuration information is transmitted via Radio Resource Control (RRC) messages; or The configuration information includes control plane signaling and is transmitted via Radio Resource Control (RRC) messages, wherein the control plane signaling is used to indicate whether to use a PDU format that supports multiple SDUs for synchronous transmission.

32. The wireless communication method according to claim 27, characterized in that, The protocol layer is the Service Data Adaptation Protocol (SDAP) layer. The configuration information for the enhanced packaging function also includes at least one of the following: The Quality of Service (QoS) stream identifier associated with the SDU used for synchronization transmission; as well as Configuration information used for synchronous transmission requirements, including at least the latency threshold between QoS streams.

33. The wireless communication method according to claim 27, characterized in that, The protocol layer is the Media Access Control (MAC) layer; The configuration information for the enhanced packaging function also includes at least one of the following: A group or multiple DRBs used to establish synchronization relationships between data radio bearers (DRBs); This includes a logical channel group (LCG) corresponding to the logical channel LCH of the DRB; as well as Configuration information for latency thresholds between QoS streams used for synchronous transmission.

34. The wireless communication method according to claim 33, characterized in that, Configuration information used to synchronize DRB groups or multiple DRBs includes at least one of the following: DRB group identifier for synchronized DRB groups; The DRB identifier of the member DRB in the synchronized DRB group or multiple DRBs; and The primary DRB information includes the primary DRB identifier in the synchronization DRB group and the timing information of the primary DRB.

35. The wireless communication method according to claim 33, characterized in that, The configuration information used for the LCG includes at least one of the following: The LCG identifier for synchronized LCG; The logical channel identifier of the member logical channel LCH in the LCG; and The main logical channel information includes the main logical channel identifier and the timing information of the main logical channel in the LCG.

36. The wireless communication method according to claim 34 or 35, characterized in that, The timing information includes at least one of the following: the periodicity, jitter, and data arrival time of the data corresponding to the main DRB or main QoS stream.

37. A wireless communication device, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device equipped with the processor to perform the method of any one of claims 27 to 36.

38. A chip comprising: A processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the method of any one of claims 27 to 36.

39. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer, causes the computer to perform the method of any one of claims 27 to 36.

40. A computer program product comprising a computer program, wherein, when executed by a computer, the computer program causes the computer to perform the method of any one of claims 27 to 36.

41. A computer program, wherein when executed by a computer, the computer program causes the computer to perform the method of any one of claims 27 to 36.

Images