Wireless communication method and device thereof

Abstract

A wireless communication method for use in a first node is disclosed. The method includes receiving, from the second node, configuration signaling including configuration information associated with synchronizing the plurality of data streams.

Description

Technical Field

[0001] This document generally deals with wireless communication, especially 5G communication, and even more specifically 6G communication. Background Technology

[0002] Beyond 5G and 6G communications, metaverse and multimodal services are likely to become highly attractive applications, which will pose challenges to the requirements of the air interface. For these applications, a potential problem may be how to synchronize data between different devices or synchronize data across different literacy levels, as the number of devices and literacy levels serving the same user increases. Summary of the Invention

[0003] This document relates to methods, systems, and devices for synchronizing data streams, and in particular to methods, systems, and devices for synchronizing data streams of devices that require coordination.

[0004] This disclosure relates to a wireless communication method used in a first node. The method includes:

[0005] Receive configuration signaling from the second node, which includes configuration information associated with synchronizing multiple data streams.

[0006] Various embodiments may preferably implement the following features:

[0007] Preferably, the wireless communication method further includes performing communication to multiple data streams based on configuration information.

[0008] Preferably, synchronizing multiple data streams includes at least one of the following:

[0009] Simultaneous processing of multiple data streams,

[0010] Simultaneously schedule multiple data streams, or

[0011] Grouping multiple devices associated with multiple data streams.

[0012] Preferably, the configuration signaling is included in the General Packet Radio Service (GPRS) transport protocol packet, the GPRS transport protocol (GTP) header, the quality of service (QoS) parameter set, the predefined radio bearer, or the predefined protocol data unit (PDU) session.

[0013] Preferably, the configuration information includes at least one of a device cluster indication for multiple devices associated with multiple data streams or a synchronization indication for synchronizing multiple data streams.

[0014] Preferably, the device cluster indication includes at least one of the following:

[0015] QoS parameters used for multiple data streams

[0016] Device cluster information associated with device clusters corresponding to multiple data streams, or

[0017] Synchronization indicator for synchronizing multiple data streams.

[0018] Preferably, the device cluster information includes associated device identifiers for a set of device identifiers for the devices, or device cluster identifiers.

[0019] Preferably, the synchronization indication is determined by a synchronization QoS parameter set, synchronization QoS parameters, or synchronization QoS flow.

[0020] Preferably, the synchronization QoS parameter set includes at least one of the following: minimum packet delay budget within the packet delay budget of the data stream, maximum packet delay budget within the packet delay budget of the data stream, average packet delay budget of the packet delay budget of the data stream, offset of the packet delay budget of the data stream, reference packet delay budget within the packet delay budget of the data stream, time interval for synchronizing multiple data streams, common packet delay budget of each data stream, or synchronization level.

[0021] Preferably, the synchronization QoS parameter set includes a set of QoS flow identifiers (QFIs).

[0022] Preferably, the wireless communication method further includes synchronizing the QoS stream corresponding to the QFI in the QoS parameter set.

[0023] Preferably, the performance characteristics of the data stream are determined based on a set of synchronous QoS parameters.

[0024] Preferably, the performance characteristics of each data stream are determined based on a synchronization QoS parameter set and a performance QoS parameter set, wherein the performance QoS parameter set includes at least one of the following for data stream communication: resource type, default priority level, packet delay budget for transmission, packet error rate for transmission, default maximum data burst size, or default average window.

[0025] Preferably, the performance QoS parameter set is determined by the QFI field in the PDU session information.

[0026] Preferably, the determination of the synchronization QoS parameter set is based on the first field in the PDU session information.

[0027] Preferably, the activation / deactivation of the synchronization QoS parameter set is determined based on the second field in the PDU session information.

[0028] Preferably, the synchronization indication is determined by the radio bearers of multiple data streams.

[0029] Preferably, the wireless bearer is a predefined wireless bearer used for synchronization.

[0030] Preferably, the wireless bearer includes at least one QoS stream of the data stream to be synchronized.

[0031] Preferably, the synchronization indication is determined by a PDU session including at least one radio bearer, which includes the QoS stream of the data stream to be synchronized.

[0032] Preferably, the PDU session is determined by the GTP header of the PDU session.

[0033] Preferably, the GTP header of the PDU session indicates the synchronous PDU type.

[0034] Preferably, the synchronization indication is determined by the synchronized GTP header.

[0035] Preferably, the GTP header is an extended header.

[0036] Preferably, the type of the extended header is determined by the value of the next extended header type field.

[0037] Preferably, the synchronization indication is determined by the importance indication of the PDU set of multiple data streams.

[0038] Preferably, the PDU set importance indication includes at least one of the following: the PDU set importance level of multiple data streams, a synchronization request indication for synchronizing multiple data streams, or a QoS parameter set for synchronizing multiple data streams.

[0039] Preferably, the first node is a network node and the second node is a core network node.

[0040] Preferably, synchronizing multiple data streams includes at least one of the following: jointly processing multiple data streams, jointly instructing multiple data streams, or transmitting auxiliary information associated with synchronization to a second node.

[0041] Preferably, the configuration signaling includes at least one of radio resource control signaling, user equipment capability, media access control (MAC) control element (CE) signaling, or downlink control information signaling.

[0042] Preferably, the configuration information includes synchronization instructions for multiple data streams.

[0043] Preferably, the synchronization indication includes a predefined wireless bearer.

[0044] Preferably, the wireless communication further includes receiving RRC signaling from the second node, which includes a predefined radio bearer identifier, and wherein at least one QFI is configured in the predefined radio bearer.

[0045] Preferably, the RRC signaling is configured as SDAP.

[0046] Preferably, the synchronization indication is determined by a predefined PDU session.

[0047] Preferably, the PDU session ID of the predefined PDU session is determined by RRC signaling.

[0048] Preferably, the first node is a user equipment and the second node is a network node.

[0049] This disclosure relates to a wireless communication method used in a second node. The method includes:

[0050] The configuration signaling is transmitted to the first node, which includes configuration information associated with synchronizing multiple data streams.

[0051] Various embodiments may preferably implement the following features:

[0052] Preferably, the wireless communication method further includes performing communication to multiple data streams based on configuration information.

[0053] Preferably, synchronizing multiple data streams includes at least one of the following:

[0054] Simultaneous processing of multiple data streams,

[0055] Simultaneously schedule multiple data streams, or

[0056] Grouping multiple devices associated with multiple data streams.

[0057] Preferably, the configuration signaling is included in the General Packet Radio Service (GPRS) transport protocol packet, the GPRS transport protocol (GTP) header, the quality of service (QoS) parameter set, the predefined radio bearer, or the predefined protocol data unit (PDU) session.

[0058] Preferably, the configuration information includes at least one of a device cluster indication for multiple devices associated with multiple data streams or a synchronization indication for synchronizing multiple data streams.

[0059] Preferably, the device cluster indication includes at least one of the following:

[0060] QoS parameters used for multiple data streams

[0061] Device cluster information associated with device clusters corresponding to multiple data streams, or

[0062] Synchronization indicator for synchronizing multiple data streams.

[0063] Preferably, the device cluster information includes associated device identifiers for a set of device identifiers for the devices, or device cluster identifiers.

[0064] Preferably, the synchronization indication is determined by a synchronization QoS parameter set, synchronization QoS parameters, or synchronization QoS flow.

[0065] Preferably, the synchronization QoS parameter set includes at least one of the following: minimum packet delay budget within the packet delay budget of the data stream, maximum packet delay budget within the packet delay budget of the data stream, average packet delay budget of the packet delay budget of the data stream, offset of the packet delay budget of the data stream, reference packet delay budget within the packet delay budget of the data stream, time interval for synchronizing multiple data streams, common packet delay budget of each data stream, or synchronization level.

[0066] Preferably, the synchronization QoS parameter set includes a set of QoS flow identifiers (QFIs).

[0067] Preferably, the wireless communication method further includes synchronizing the QoS stream corresponding to the QFI in the QoS parameter set.

[0068] Preferably, the performance characteristics of the data stream are determined based on a set of synchronous QoS parameters.

[0069] Preferably, the performance characteristics of each data stream are determined based on a synchronization QoS parameter set and a performance QoS parameter set, wherein the performance QoS parameter set includes at least one of the following for data stream communication: resource type, default priority level, packet delay budget for transmission, packet error rate for transmission, default maximum data burst size, or default average window.

[0070] Preferably, the performance QoS parameter set is determined by the QFI field in the PDU session information.

[0071] Preferably, the determination of the synchronization QoS parameter set is based on the first field in the PDU session information.

[0072] Preferably, the activation / deactivation of the synchronization QoS parameter set is determined based on the second field in the PDU session information.

[0073] Preferably, the synchronization indication is determined by the radio bearers of multiple data streams.

[0074] Preferably, the wireless bearer is a predefined wireless bearer used for synchronization.

[0075] Preferably, the wireless bearer includes at least one QoS stream of the data stream to be synchronized.

[0076] Preferably, the synchronization indication is determined by a PDU session including at least one radio bearer, which includes the QoS stream of the data stream to be synchronized.

[0077] Preferably, the PDU session is determined by the GTP header of the PDU session.

[0078] Preferably, the GTP header of the PDU session indicates the synchronous PDU type.

[0079] Preferably, the synchronization indication is determined by the synchronized GTP header.

[0080] Preferably, the GTP header is an extended header.

[0081] Preferably, the type of the extended header is determined by the value of the next extended header type field.

[0082] Preferably, the synchronization indication is determined by the importance indication of the PDU set of multiple data streams.

[0083] Preferably, the PDU set importance indication includes at least one of the following: the PDU set importance level of multiple data streams, a synchronization request indication for synchronizing multiple data streams, or a QoS parameter set for synchronizing multiple data streams.

[0084] Preferably, the first node is a network node and the second node is a core network node.

[0085] Preferably, synchronizing multiple data streams includes at least one of the following: jointly processing multiple data streams, jointly instructing multiple data streams, or transmitting auxiliary information associated with synchronization to a second node.

[0086] Preferably, the configuration signaling includes at least one of radio resource control signaling, user equipment capability, media access control (MAC) control element (CE) signaling, or downlink control information signaling.

[0087] Preferably, the configuration information includes synchronization instructions for multiple data streams.

[0088] Preferably, the synchronization indication includes a predefined wireless bearer.

[0089] Preferably, the wireless communication further includes receiving RRC signaling from the second node, which includes a predefined radio bearer identifier, and wherein at least one QFI is configured in the predefined radio bearer.

[0090] Preferably, the RRC signaling is configured as SDAP.

[0091] Preferably, the synchronization indication is determined by a predefined PDU session.

[0092] Preferably, the PDU session ID of the predefined PDU session is determined by RRC signaling.

[0093] Preferably, the first node is a user equipment and the second node is a network node.

[0094] This disclosure relates to a wireless communication method used in a first node. The method includes:

[0095] A first signaling message is transmitted to the second node, which is associated with configuration information related to synchronizing multiple data streams.

[0096] Various embodiments may preferably implement the following features:

[0097] Preferably, the first signaling includes downlink transmission assistance information, which includes at least one of the following: offset information for packet delay budget, timing information for communication of multiple data streams, device type information associated with a device corresponding to the multiple data streams, or traffic type information associated with the multiple data streams.

[0098] Preferably, the offset information includes the offset for modifying the packet delay budget.

[0099] Preferably, the offset information includes the synchronization margin of the packet delay budget.

[0100] Preferably, the time information includes a time slot index, a transmission time interval index, or a timestamp associated with communication of multiple data streams.

[0101] Preferably, the first signaling includes uplink transmission assistance information, which includes at least one of the following: indication of multiple uplink data streams in a logical channel group (LCG), indication of multiple LCGs, indication of multiple physical uplink shared channels, indication of multiple HARQ process IDs, offset information for packet delay budget, timing information for communication of multiple data streams, device type information associated with devices corresponding to multiple data streams, device type information associated with devices corresponding to multiple data streams, or traffic type information associated with multiple data streams.

[0102] Preferably, the first signaling includes uplink transmission assistance information, which includes indications of multiple uplink data streams in the LCG logical channel group (LCG).

[0103] Preferably, the data in the multiple uplink data streams in the LCG includes at least one of the data to be synchronized or the data not to be synchronized.

[0104] Preferably, the indication of multiple uplink data streams in the LCG includes at least one of an indication of data to be synchronized or an indication of data not to be synchronized.

[0105] Preferably, the first signaling includes uplink transmission assistance information, which includes indications of association of multiple logical channel groups (LCGs).

[0106] Preferably, the association of multiple LCGs includes synchronizing data in multiple LCGs.

[0107] Preferably, the indication is a bitmap indicating a plurality of LCGs.

[0108] Preferably, the indication is a bit string indicating a group identifier for multiple LCGs, wherein data in LCGs indicated by the same group identifier will be synchronized.

[0109] Preferably, the data in the logical channels within multiple LCGs are scheduled based on scheduling rules.

[0110] Preferably, the scheduling rules include at least one of the following: simultaneous scheduling, scheduling based on synchronization requirements in the configuration information, and compliance with constraints.

[0111] Preferably, the logical channels within multiple LCGs have at least one of the following: the same logical channel priority, the same priority bit rate, or the same bucket size duration.

[0112] Preferably, the first signaling includes at least one of the following: UE capability, UE assistance information, MAC CE signaling, or uplink control information signaling.

[0113] Preferably, the MAC CE signaling is a buffer size report (BSR).

[0114] Preferably, the information included in the first signaling is located in a dedicated octet of the BSR.

[0115] Preferably, the BSR is a short BSR, a long BSR, an extended short BSR, an extended long BSR, or an extended preemptive BSR.

[0116] Preferably, the first signaling includes MAC CE signaling, and the downlink transmission assistance information and / or uplink transmission assistance information included in the first signaling are located in the MAC subheader of the MAC CE signaling.

[0117] Preferably, the uplink control information signaling includes at least one of uplink control information for resource release, HARQACK information, or channel state information.

[0118] Preferably, the first node is a user equipment and the second node is a network node.

[0119] This disclosure relates to a wireless communication method used in a second node. The method includes receiving a first signaling from a first node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

[0120] Various embodiments may preferably implement the following features:

[0121] Preferably, the first signaling includes downlink transmission assistance information, which includes at least one of the following: offset information for packet delay budget, timing information for communication of multiple data streams, device type information associated with a device corresponding to the multiple data streams, or traffic type information associated with the multiple data streams.

[0122] Preferably, the offset information includes the offset for modifying the packet delay budget.

[0123] Preferably, the offset information includes the synchronization margin of the packet delay budget.

[0124] Preferably, the time information includes a slot index, transmission time interval index, or timestamp associated with communication of multiple data streams.

[0125] Preferably, the first signaling includes uplink transmission assistance information, which includes at least one of the following: indication of multiple uplink data streams in a logical channel group (LCG), indication of multiple LCGs, indication of multiple physical uplink shared channels, indication of multiple HARQ process IDs, offset information for packet delay budget, timing information for communication of multiple data streams, device type information associated with devices corresponding to multiple data streams, device type information associated with devices corresponding to multiple data streams, or traffic type information associated with multiple data streams.

[0126] Preferably, the first signaling includes uplink transmission assistance information, which includes indications of multiple uplink data streams in the LCG logical channel group (LCG).

[0127] Preferably, the data in the multiple uplink data streams in the LCG includes at least one of the data to be synchronized or the data not to be synchronized.

[0128] Preferably, the indication of multiple uplink data streams in the LCG includes at least one of an indication of data to be synchronized or an indication of data not to be synchronized.

[0129] Preferably, the first signaling includes uplink transmission assistance information, which includes indications of association of multiple logical channel groups (LCGs).

[0130] Preferably, the association of multiple LCGs includes synchronizing data in multiple LCGs.

[0131] Preferably, the indication is a bitmap indicating a plurality of LCGs.

[0132] Preferably, the indication is a bit string indicating a group identifier for multiple LCGs, wherein data in LCGs indicated by the same group identifier will be synchronized.

[0133] Preferably, the data in the logical channels within multiple LCGs are scheduled based on scheduling rules.

[0134] Preferably, the scheduling rules include at least one of the following: simultaneous scheduling, scheduling based on synchronization requirements in the configuration information, and compliance with constraints.

[0135] Preferably, the logical channels within multiple LCGs have at least one of the following: the same logical channel priority, the same priority bit rate, or the same bucket size duration.

[0136] Preferably, the first signaling includes at least one of the following: UE capability, UE assistance information, MAC CE signaling, or uplink control information signaling.

[0137] Preferably, the MAC CE signaling is a buffer size report (BSR).

[0138] Preferably, the information included in the first signaling is located in a dedicated octet of the BSR.

[0139] Preferably, the BSR is a short BSR, a long BSR, an extended short BSR, an extended long BSR, or an extended preemptive BSR.

[0140] Preferably, the first signaling includes MAC CE signaling, and the downlink transmission assistance information and / or uplink transmission assistance information included in the first signaling are located in the MAC subheader of the MAC CE signaling.

[0141] Preferably, the uplink control information signaling includes at least one of uplink control information for resource release, HARQACK information, or channel state information.

[0142] Preferably, the first node is a user equipment and the second node is a network node.

[0143] This disclosure relates to a first node. This first node includes:

[0144] The communication unit is configured to receive configuration signaling from the second node, the configuration signaling including configuration information associated with synchronizing multiple data streams.

[0145] Various embodiments may preferably implement the following features:

[0146] Preferably, the first node further includes a processor configured to perform any of the above-described wireless communication methods.

[0147] This disclosure relates to a second node. This second node includes:

[0148] The communication unit is configured to transmit configuration signaling to the first node, the configuration signaling including configuration information associated with synchronizing multiple data streams.

[0149] Various embodiments may preferably implement the following features:

[0150] Preferably, the second node further includes a processor configured to perform any of the above-described wireless communication methods.

[0151] This disclosure relates to a first node. This first node includes:

[0152] The communication unit is configured to transmit a first signaling to a second node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

[0153] Various embodiments may preferably implement the following features:

[0154] Preferably, the first node further includes a processor configured to perform any of the above-described wireless communication methods.

[0155] This disclosure relates to a second node. This second node includes:

[0156] The communication unit is configured to receive a first signaling from a first node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

[0157] Various embodiments may preferably implement the following features:

[0158] Preferably, the second node further includes a processor configured to perform any of the above-described wireless communication methods.

[0159] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the wireless communication method described in any of the foregoing methods.

[0160] The exemplary embodiments disclosed herein are intended to provide features that will become apparent when taken in conjunction with the accompanying drawings and by referring to the following description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0161] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0162] This invention is defined by the independent claims. Preferred embodiments are defined in the dependent claims. In the following description, although numerous features may be specified as optional, it should be acknowledged that all features included in the independent claims should not be considered optional. Attached Figure Description

[0163] The above and other aspects and their embodiments will be described in more detail in the accompanying drawings, specification and claims.

[0164] Figure 1 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown.

[0165] Figure 2 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown.

[0166] Figure 3 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown.

[0167] Figure 4 A schematic diagram of a network (architecture) according to an embodiment of the present disclosure is shown.

[0168] Figure 5 A schematic diagram of a data flow according to an embodiment of the present disclosure is shown.

[0169] Figure 6 A schematic diagram of a data flow according to an embodiment of the present disclosure is shown.

[0170] Figure 7 A schematic diagram of a short BSR according to an embodiment of the present disclosure is shown.

[0171] Figure 8 A schematic diagram of a long BSR according to an embodiment of the present disclosure is shown.

[0172] Figure 9 A schematic diagram of a long BSR according to an embodiment of the present disclosure is shown.

[0173] Figure 10 A schematic diagram of a MAC subheading according to an embodiment of the present disclosure is shown.

[0174] Figure 11 A schematic diagram of a MAC subheading according to an embodiment of the present disclosure is shown.

[0175] Figure 12 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0176] Figure 13 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown. Detailed Implementation

[0177] In one embodiment, the metaverse and multimodal services comprise multiple data streams (such as video streams, audio streams, haptic streams, etc.) with different Quality of Service (QoS) requirements. For an immersive experience, these multiple data streams may need to be synchronized to bring the virtual world to life. Note that these multiple data streams can belong to a single device or multiple devices.

[0178] In one embodiment, synchronization information (such as synchronization indications and key performance indicators) can be transmitted via the core network (CN). When the base station receives synchronization information transmitted by the CN, the base station can transmit corresponding information to the UE to request certain auxiliary information for downlink transmission, and / or jointly process the data stream to be synchronized, and / or jointly schedule the data stream to be synchronized and / or group the data streams of different devices to be synchronized (e.g., the device to which the synchronization data stream belongs). Additionally, the UE can transmit auxiliary information to the base station for UL (uplink) synchronization data stream transmission.

[0179] In some embodiments, a device cluster indication (i.e., an indication of a device cluster) is provided.

[0180] In one embodiment, data streams from devices within the same device cluster are tagged with the same set of QoS parameters. That is, the QoS parameter set can be used as an indicator of device cluster size.

[0181] In one embodiment, devices within the same device cluster are indicated by associated device identifiers, such as a set of device identifiers for the devices and a device cluster identifier. In this embodiment, devices indicated by associated device identifiers can be considered to be in the same device cluster.

[0182] In one embodiment, the associated device identifier includes one or more device identifiers or one or more device cluster identifiers.

[0183] In some embodiments, a synchronization instruction is provided.

[0184] In one embodiment, a device may be determined to be in the same device cluster based on one or more device cluster indications for the device, and the synchronization requirements for these devices are determined separately by the synchronization indications.

[0185] In one embodiment, whether a device is located in the same device cluster is determined based on one or more synchronization indications for the device. In this embodiment, the synchronization requirements for these devices are also determined based on one or more synchronization indications for the device.

[0186] In one embodiment, the synchronization indication is either implicit or explicit.

[0187] Figure 1 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown. In this embodiment, a synchronization QoS (parameter set) is configured for QoS flows "A" and "B" to be synchronized.

[0188] Figure 2 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown. Figure 2 In this context, the synchronization radio bearer is configured for QoS flows "A" and "B" that need to be synchronized.

[0189] Figure 3 A schematic diagram of synchronization according to an embodiment of the present disclosure is shown. Figure 3 In this context, the synchronization PDU session is configured for QoS flows "A" and "B" that need to be synchronized.

[0190] Please note that the number of QoS streams to be synchronized can exceed 2.

[0191] Figure 4 A schematic diagram of a network (architecture) according to an embodiment of the present disclosure is shown. Figure 4 In this process, the UE reports auxiliary information (e.g., downlink auxiliary information and / or uplink auxiliary information) to the gNB. The UE may be a mobile edge computing device (e.g., a smartphone) and connected to multiple devices 1, 2, and 3. For example, device 1 may be AR (augmented reality) glasses, device 2 may be headphones, and device 3 may be a controller. Data streams associated with devices 1, 2, and 3 may need to be synchronized, for example, to provide an immersive experience.

[0192] In one embodiment, the reporting of synchronization information may be triggered by the transmission of UE capabilities and / or relevant information from the gNB.

[0193] In one embodiment, synchronization includes at least one of the following:

[0194] - Offset information (e.g., PDB (packet delay budget) revision value, UE synchronization margin);

[0195] - Index of the time slot / TTI (Transmission Time Interval) when data is successfully received;

[0196] - The timestamp when the data was successfully received;

[0197] - Device type;

[0198] - Traffic type;

[0199] - Identifiers for synchronous and asynchronous data (uplink); or

[0200] - Identifiers of synchronization data from different logical channel groups (uplink).

[0201] In one embodiment, the signaling for reporting synchronization information may include at least one of the following:

[0202] -UE auxiliary information (e.g., RRC signaling);

[0203] -MAC CE signaling; or

[0204] -UCI signaling.

[0205] In one embodiment, a method for use in a first node is disclosed. The method includes:

[0206] Receive configuration signaling from the second node, which includes synchronization / configuration information associated with synchronizing multiple data streams.

[0207] In one embodiment, the method further includes determining synchronization / configuration information based on configuration signaling.

[0208] In one embodiment, the method further includes transmitting a first signaling associated with synchronization information to a second node.

[0209] In this disclosure, the following items are further discussed:

[0210] - Explanation of the first and second nodes;

[0211] - Explanation of configuration signaling;

[0212] - Explanation of synchronization information; and

[0213] - Explanation of the first signaling.

[0214] Explanation of the first and second nodes

[0215] In some embodiments, the second node is / includes one of the following: a core network (CN) node or a network node (e.g., a base station).

[0216] In some embodiments, the first node includes one of the following: a network node (e.g., a base station) or a network device (e.g., a UE).

[0217] Interpretation of configuration signaling

[0218] In some embodiments where the second node is a CN node and the first node is a network node, configuration signaling is transmitted or included therein via General Packet Radio Service (GPRS) transport protocol packets.

[0219] In one embodiment, a GPRS transport protocol packet means at least one of the following:

[0220] -GPRS Transport Protocol (GTP) header;

[0221] - Quality of Service (QoS) parameter set;

[0222] -Predefined wireless bearer, or

[0223] - Predefined PDU sessions.

[0224] In some embodiments, if the second node is a CN node and the second node is a network node, the configuration signaling includes configuration information.

[0225] In some embodiments where the second node is a network node and the first node is a network device, configuration signaling is transmitted via at least one of the following:

[0226] -High-level parameters;

[0227] -RRC signaling;

[0228] -UE capabilities;

[0229] -MAC (Media Access Control) CE signaling; or

[0230] -DCI (Downlink Control Information) signaling.

[0231] In some embodiments, if the second node is a network node and the first node is a network device, the configuration signaling includes configuration information.

[0232] Explanation of configuration information

[0233] In some embodiments where the second node is a CN node and the first node is a network node, configuration information transmitted from the CN node to the network node is used to help the network node synchronize multiple data streams. In one embodiment, synchronizing multiple data streams includes or means processing multiple data streams simultaneously.

[0234] In one embodiment, synchronizing multiple data streams includes at least one of the following: collecting / grouping data streams that need to be synchronized, providing associations for the data streams that need to be synchronized, synchronizing the data streams for devices in the group, or jointly encoding the data in the data streams.

[0235] In some embodiments where the second node is a CN node and the first node is a network node, configuration information transmitted from the CN node to the network node is used to help the network node synchronize multiple data streams. In this embodiment, synchronizing multiple data streams includes or implies synchronously scheduling multiple data streams.

[0236] In one embodiment, synchronously scheduling multiple data streams includes at least one of the following: simultaneously scheduling multiple data streams, scheduling multiple data streams within a time constraint, or synchronously scheduling data streams for devices in a group.

[0237] In some cases, time constraints are determined by synchronization requests / requirements in the configuration information.

[0238] In some embodiments where the second node is a CN node and the first node is a network node, configuration information transmitted from the CN node to the network node is used to help the network node synchronize multiple data streams. In this embodiment, synchronizing multiple data streams includes or implies grouping multiple devices associated with multiple data streams or with device coordination.

[0239] In one embodiment, grouping multiple devices associated with multiple data streams includes at least one of the following: identifying devices in the same group (e.g., the same device cluster) or classifying multiple data streams for multiple devices in the same group (e.g., the same device cluster).

[0240] In one embodiment, device coordination means grouping devices that have data streams that need to be synchronized.

[0241] In some embodiments, if the second node is a CN node and the first node is a network node, the configuration information includes at least one of the following:

[0242] - Device cluster indication; or

[0243] - Synchronization indicator.

[0244] In one embodiment, a device cluster indication is used to identify a group of devices for at least one of synchronization, joint scheduling processing, or device coordination.

[0245] In some embodiments, if the second node is a CN node and the first node is a network node, the first information includes a device cluster indication.

[0246] In some embodiments, the device cluster indication includes at least one of the following:

[0247] -QoS parameter set;

[0248] - Device cluster information; or

[0249] - Synchronization indicator.

[0250] In one embodiment, device cluster information includes associated device identifiers for a set of device identifiers.

[0251] In some cases, the set of device identifiers includes / has a single combined / public identifier.

[0252] As an alternative, associated device identifiers are specific (e.g., predefined) device identifiers used to group devices, where devices in the same group (device cluster) are indicated by associated device identifiers.

[0253] As an alternative, the associated device identifier is the anchor device identifier that belongs to the anchor device. Devices belonging to the same group (device cluster) as the anchor device are indicated by the anchor identifier.

[0254] As an alternative, the associated device identifier is a group (device cluster) identifier, where devices in the same group (device cluster) are indicated by the group (device cluster) identifier.

[0255] In some cases, the set of device identifiers includes a set of identifiers, where devices in the same group (device cluster) are indicated by a device identifier from the set of device identifiers.

[0256] For example, for a group (device cluster), the set of device identifiers is {1,2,3,4,5}. In this example, devices with device identifiers of 1, 2, 3, 4, or 5 belong to this group, while devices with device identifiers other than 1 to 5 (e.g., 6) do not belong to this group.

[0257] In one embodiment where the device cluster indication includes a synchronization indication, the device cluster indication indicates both a device cluster of multiple devices and a request for synchronization.

[0258] In some embodiments, if the second node is a CN node and the first node is a network node, the configuration information includes a synchronization indication.

[0259] In one embodiment, the synchronization indication is determined by a set of synchronization QoS parameters.

[0260] In some cases, the synchronized QoS parameter set is the QoS profile.

[0261] In one embodiment, the synchronization QoS parameter set includes a QoS parameter set that includes at least one of the following:

[0262] -Resource type,

[0263] - Default priority level

[0264] -Package delay budget,

[0265] - Packet error rate,

[0266] - Default maximum data burst size

[0267] - Default average window, or

[0268] -Synchronization requirements.

[0269] In some cases, QoS parameters are performance characteristics.

[0270] In some cases, the synchronization requirement is an offset for each data stream, where the offset is a range of values ​​for the QoS parameter "Packet Delay Budget" (PDB) used for each data stream. The latency requirement for a data stream is a joint consideration of the QoS parameter PDB and the offset, for example, PDB + offset. Furthermore, the offset can be one or more negative values, one or more positive values, and / or zero.

[0271] In some cases, synchronization requirements are relative / reference packet delay budgets for the data streams, where the relative / reference packet delay budget (PDB) for each data stream is a PDB associated with a reference point. The reference point can be determined by receiving data streams from the anchor point.

[0272] For example, consider three data streams that need to be synchronized, such as data stream 1, data stream 2, and data stream 3. Data stream 2 is considered / set as the anchor data stream. Assume that data stream 2 is successfully received within 1 millisecond (which is set as the reference point) and is 2 milliseconds relative to the reference PDB. In this case, data stream 1 and data stream 3 are expected to be received no later than 1 + 2 = 3 milliseconds to achieve synchronization of data stream 1, data stream 2, and data stream 3.

[0273] In some cases, synchronization requirements are to synchronize multiple data streams at time intervals, where the time interval indicates the maximum time interval between the reception times of two synchronized data streams.

[0274] For example, there are three data streams that need to be synchronized (i.e., data stream 1, data stream 2, and data stream 3). The time interval between the reception times of data stream 1 and data stream 2 is expected to be less than the maximum time interval between their reception times. Similarly, the time interval between the reception times of data stream 1 and data stream 3 is expected to be less than the maximum time interval between their reception times, and so on.

[0275] In some cases, synchronization requirements are the minimum packet delay budget between data streams.

[0276] For example, data stream 1 has a QoS parameter packet delay budget 1 (PDB1), data stream 2 has a QoS parameter PDB2, and data stream 3 has a QoS parameter PDB3. The QoS parameter synchronization requirement can be derived using Min(PDB1, PDB2, PDB3), where Min(*) is an operator used to find the minimum value among the input values.

[0277] In some cases, synchronization requirements are the maximum packet delay budget between data streams.

[0278] For example, data stream 1 has QoS parameter PDB1, data stream 2 has QoS parameter PDB2, and data stream 3 has QoS parameter PDB3. QoS parameter synchronization requirements can be derived using Max(PDB1, PDB2, PDB3), where Max(*) is an operator used to find the maximum value among the input values.

[0279] In some cases, synchronization requirements are the average packet delay budget between data streams.

[0280] For example, data stream 1 has QoS parameter PDB1, data stream 2 has QoS parameter PDB2, and data stream 3 has QoS parameter PDB3. The QoS parameter synchronization requirement can be derived as Avg(PDB1,PDB2,PDB3), where Avg(*) is an operator used to calculate the average of the input values.

[0281] In some cases, synchronization requirements are shared packet delay budgets for each data stream.

[0282] In some cases, synchronization requirements are synchronization levels, where the synchronization level determines the importance or degree of synchronization.

[0283] As an alternative, different synchronization levels correspond to / refer to different offset values.

[0284] As an alternative, different synchronization levels correspond to / refer to different relative / reference PDBs.

[0285] As an alternative, different synchronization levels correspond to / refer to different maximum synchronization time intervals.

[0286] In one embodiment, the synchronization QoS parameter set includes: synchronization requirements.

[0287] In some cases, synchronization requirements include one or more performance characteristics or are associated with one or more performance characteristics.

[0288] In some cases, synchronization requirements include an offset for each data stream, where the offset indicates the range of values ​​for the QoS parameter PDB for each data stream. That is, latency requirements are a joint consideration of the QoS parameter PDB and the offset, e.g., PDB + offset. Furthermore, the offset can be one or more negative values, one or more positive values, and / or zero.

[0289] In some cases, synchronization requirements include relative / reference PDBs for the data streams, wherein the relative / reference PDB for each data stream indicates a PDB range relative to a reference point. In one embodiment, the reference point is determined by receiving the anchor data stream.

[0290] For example, consider three data streams, 1, 2, and 3, that need to be synchronized, where data stream 2 is considered / set as the anchor stream. In this example, data stream 2 is successfully received within 1 millisecond (which is set as the reference point) and is 2 milliseconds relative to the reference PDB. In this case, data streams 1 and 3 are expected to be received no later than 1 + 2 = 3 milliseconds. If data stream 1 and / or data stream 3 is received after time 1 + 2 = 3, then data streams 1, 2, and 3 are out of sync.

[0291] In some cases, synchronization requirements include synchronizing multiple data streams over time intervals, where the time interval indicates / means the maximum time interval between the reception times of two data streams to be synchronized.

[0292] For example, there are three data streams 1, 2, and 3 that need to be synchronized. The time interval between the reception times of data stream 1 and data stream 2 is expected to be less than the maximum time interval between the reception times of data stream 1 and data stream 2, the time interval between the reception times of data stream 1 and data stream 3 is expected to be less than the maximum time interval between the reception times of data stream 1 and data stream 3, and so on.

[0293] In some cases, synchronization requirements include the minimum packet delay budget within the packet delay budget used for the data stream.

[0294] For example, data stream 1 has QoS parameter PDB1, data stream 2 has QoS parameter PDB2, and data stream 3 has QoS parameter PDB3. The QoS parameter synchronization requirement can be derived using Min(PDB1, PDB2, PDB3), where Min(*) is an operator used to find the minimum value among the input values / variables.

[0295] In some cases, the synchronization requirement is the maximum packet delay budget within the packet delay budget used for the data stream.

[0296] For example, data stream 1 has QoS parameter PDB1, data stream 2 has QoS parameter PDB2, and data stream 3 has QoS parameter PDB3. QoS parameter synchronization requirements can be derived using Max(PDB1, PDB2, PDB3), where Max(*) is an operator used to find the maximum value among input values / variables.

[0297] In some cases, synchronization requirements are the average packet delay budget between data streams.

[0298] For example, data stream 1 has QoS parameter PDB1, data stream 2 has QoS parameter PDB2, and data stream 3 has QoS parameter PDB3. QoS parameter synchronization requirements can be derived using Avg(PDB1,PDB2,PDB3), where Avg(*) is an operator used to calculate the average of input values / variables.

[0299] In some cases, synchronization requirements include a common packet delay budget for each data stream.

[0300] In some cases, synchronization requirements are synchronization levels, where the synchronization level determines the importance or degree of synchronization.

[0301] As an alternative, different synchronization levels correspond to / refer to different offset values.

[0302] As an alternative, different synchronization levels correspond to / refer to different relative / reference PDBs.

[0303] As an alternative, different synchronization levels correspond to / refer to different maximum synchronization time intervals.

[0304] In one embodiment, the synchronization QoS parameter set includes a set of QoS flow identifiers (QFIs), wherein the QFIs are associated with an index (value) of the QoS parameter set.

[0305] In some cases, the index (value) of the QoS parameter set is the 5QI value.

[0306] In some cases, data streams in a QoS stream set indicated by a QoS parameter set need to be synchronized.

[0307] For example, the QoS parameter set includes QFIs, which may include, for example, {1,2,3,4,5}. In this example, there is a data stream 1 with QFI=1, a data stream 2 with QFI=3, and a data stream 3 with QFI=6. Based on QFI{1,2,3,4,5}, data streams 1 and 2 need to be synchronized, while data stream 3 does not need to be synchronized with either data stream 1 or data stream 2.

[0308] In some embodiments, the performance characteristics of the data stream are determined based on a set of synchronous QoS parameters.

[0309] In one embodiment, the data stream is requested to be synchronized.

[0310] In one embodiment, all performance characteristics of the data stream are determined by a set of synchronization QoS parameters, including: resource type, default priority level, packet delay budget, packet error rate, default maximum data burst size, default average window, and synchronization requirements.

[0311] In one embodiment, some performance characteristics of the data stream are determined by a performance QoS parameter set, including: resource type, default priority level, packet delay budget, packet error rate, default maximum data burst size, and default average window, while the remaining performance characteristics of the data stream are determined by a synchronization QoS parameter set, including, for example, synchronization requirements.

[0312] In some embodiments, the synchronization QoS parameter set is determined by protocol data unit (PDU) session information.

[0313] In one embodiment, the first field in the PDU session information is used to determine the set of synchronization QoS parameters.

[0314] In some cases, the synchronization QoS parameter set is determined by selecting an index (value) that corresponds to the synchronization QoS parameter set.

[0315] As an alternative, the index (value) is the 5QI value.

[0316] In some cases, the first field is a specific field in the PDU session information, such as the Synchronization QoS Identifier (SQI).

[0317] In some cases, the first field is the QFI field.

[0318] In one embodiment, the second field in the PDU session information is used to activate / deactivate the use of the synchronous QoS parameter set.

[0319] In some cases, the second field includes at least one bit for activating / deactivating the synchronous QoS parameter set.

[0320] For example, bit "1" indicates that the use of the synchronous QoS parameter set is enabled, and bit "0" indicates that the use of the synchronous QoS parameter set is disabled.

[0321] In some cases, the second field is a specific field, such as Synchronous QoS Activation (SQA) in PDU session information.

[0322] Figure 5 A schematic diagram of a data flow according to an embodiment of the present disclosure is shown. Figure 5 In this implementation, the SQA (Synchronization QoS Activation) field is used to activate / deactivate the use of the synchronization QoS parameter set. Additionally, the SQI (Synchronization QoS Identifier) ​​field is used to indicate the synchronization QoS parameter set (e.g., including synchronization indication or for synchronization). For example, SQI may include the QFI of the QoS parameter set. In this embodiment, data streams 1 and 2 need to be synchronized. The SQA for data streams 1 and 2 activates the (synchronization) QoS parameters indicated by the SQI.

[0323] In some embodiments, the synchronization indication is determined by the radio bearer (e.g., see...). Figure 2 ).

[0324] In one embodiment, the QoS stream of the data stream to be synchronized belongs to a predefined radio bearer. That is, the predefined radio bearer is configured to synchronize the data streams in its contained QoS streams.

[0325] In one embodiment, the predefined radio bearer identifier is determined by the CN node.

[0326] In some embodiments, the synchronization indication is determined by the PDU session (e.g., see...). Figure 3 ).

[0327] In one embodiment, the data streams to be synchronized are transmitted in a predefined PDU session.

[0328] In one embodiment, a predefined PDU session is determined by the GTP header.

[0329] In one embodiment, the PDU session is determined by a dedicated type of PDU session, such as a synchronized PDU session type.

[0330] Figure 6 A schematic diagram of a data flow according to an embodiment of the present disclosure is shown. Figure 5 In this embodiment, data streams 1 and 2 will need to be synchronized. The PDU types of data streams 1 and 2 will be configured as synchronized PDU session types. That is, the PDU session type is an indication used for synchronization.

[0331] In some embodiments, the synchronization indication is determined by the PDU set importance indication.

[0332] In one embodiment, the PDU set importance indication includes: a PDU set importance level for multiple data streams; a synchronization request indication for synchronizing multiple data streams; and a QoS parameter set for synchronizing multiple data streams.

[0333] In one embodiment, the PDU set importance indication includes: a PDU set importance level for multiple data streams and a synchronization request indication for synchronizing multiple data streams.

[0334] In one embodiment, the PDU set importance indication includes: a PDU set importance level for multiple data streams and a QoS parameter set for synchronizing multiple data streams.

[0335] In one embodiment, the importance level of the PDU set for multiple data streams indicates the degree of importance of the data streams. In one embodiment, the most important data streams are processed or scheduled first, and / or cannot be dropped in the event of congestion.

[0336] In some cases, the importance level of a PDU set corresponds to a data stream.

[0337] In some cases, the importance level of a PDU set corresponds to the data stream that needs to be synchronized.

[0338] In one embodiment, a synchronization request indication for synchronizing multiple data streams includes activation / deactivation of the use of a synchronization QoS parameter set and an index (value) corresponding to the synchronization QoS parameter set.

[0339] In one embodiment, a synchronization request for synchronizing multiple data streams includes activation / deactivation of the use of a synchronization QoS parameter set.

[0340] In one embodiment, the synchronization request indication for synchronizing multiple data streams includes an index (value) corresponding to a set of synchronization QoS parameters.

[0341] In one embodiment, the QoS parameter set includes a synchronous QoS parameter set. For example, the QoS parameters within this QoS parameter set include a portion of the QoS parameters in the synchronous QoS parameter set, including, for example, packet error rate, packet delay budget, and synchronization requirements.

[0342] In one embodiment, the QoS parameter set includes a synchronization QoS parameter set and a performance QoS parameter set.

[0343] In one embodiment, the QoS parameter set includes a performance QoS parameter set.

[0344] For example, QoS parameters within a QoS parameter set include a subset of QoS parameters from a performance QoS parameter set, including, for example, packet error rate and packet delay budget.

[0345] In some embodiments, the synchronization indication is determined by the GTP-U header.

[0346] In one embodiment, the synchronization indication is determined by a specific GTP header used for the synchronization indication, namely, the synchronization GTP header.

[0347] In one embodiment, the synchronization indicator is determined by the "Next Extended Header Type" in the GTP header. In this embodiment, the synchronization indicator is one of several types of extended headers.

[0348] For example, the synchronization indicator is located in "Next Extended Header Type" and corresponds to the value 00000100 in Table 1 below:

[0349] Table 1:

[0350]

[0351]

[0352] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) at least one of jointly processing multiple data streams, jointly instructing multiple data streams, or transmitting auxiliary information associated with synchronization to the second node.

[0353] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) jointly processing multiple data streams and jointly directing multiple data streams.

[0354] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) jointly processing multiple data streams and transmitting auxiliary information associated with the synchronization to the second node.

[0355] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) jointly instructing multiple data streams, and transmitting auxiliary information associated with the synchronization to the second node.

[0356] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) the joint processing of multiple data streams.

[0357] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) jointly instructing multiple data streams.

[0358] In some embodiments where the second node is a network node and the first node is a network device, the synchronization of multiple data streams includes (or implies) transmitting auxiliary information associated with the synchronization to the second node.

[0359] In some embodiments where the second node is a network node and the first node is a network device, configuration information transmitted from the network node to the network device is used to instruct the network device to synchronize multiple data streams by processing multiple data streams synchronously.

[0360] In one embodiment, synchronously processing multiple data streams includes at least one of the following: collecting / grouping (required) data streams to be synchronized, providing some associations for the data streams to be synchronized, synchronously receiving (required) data streams to be synchronized, synchronously processing data streams for devices in the group, or jointly encoding data of the data streams.

[0361] In some embodiments where the second node is a network node and the first node is a network device, configuration information transmitted from the network node to the network device is used to instruct the network device to synchronize multiple data streams via joint instruction of multiple data streams.

[0362] In one embodiment, jointly indicating multiple data streams includes: indicating data streams that (need) to be synchronized and / or indicating data streams that (do not need) to be synchronized.

[0363] In some embodiments where the second node is a network node and the first node is a network device, configuration information transmitted from the network node to the network device is used to instruct the network device to synchronize multiple data streams by transmitting auxiliary information associated with synchronization to the network node.

[0364] In some embodiments where the second node is a network node and the first node is a network device, the configuration information includes a synchronization indication.

[0365] In one embodiment, the synchronization indication is determined by a predefined wireless bearer.

[0366] In one embodiment, the QFI in a predefined radio bearer is determined by RRC (Radio Resource Control) signaling.

[0367] In some cases, RRC signaling is SDAP-config.

[0368] As an alternative, the dedicated parameter mappedQoS-FlowSyncToAdd-r18 for SDAP-config in Table 2 below is configured to map the QoS flows that need to be synchronized to predefined radio bearers.

[0369] Table 2:

[0370]

[0371]

[0372] In some embodiments, the synchronization indication is determined by the PDU session.

[0373] In one embodiment, the PDU session used for synchronization is determined by RRC signaling.

[0374] In some cases, RRC signaling is SDAP-config, where at least one synchronized PDU session ID is determined by the parameter pdu-session. For example, the integer {10, 20, 30} used for the parameter pdu-session can be selected as the synchronized PDU session ID.

[0375] Interpretation of the first signaling

[0376] In some embodiments, the first signaling is transmitted by the UE to, for example, a base station or a CN node.

[0377] In one embodiment, the UE transmits the first signaling upon receiving synchronization information.

[0378] In one embodiment, the first signaling includes downlink transmission assistance information, including at least one of the following:

[0379] -Offset information;

[0380] -Time information when the data stream is received / transmitted;

[0381] - Device type information; or

[0382] - Traffic type information.

[0383] In some embodiments, the offset information is a packet delay budget modification.

[0384] In one embodiment, packet delay budget modification is used to adjust the packet delay budget within the performance QoS parameter set for the corresponding data stream.

[0385] For example, a modified set of packet delay budgets, A and B, in the performance QoS parameter set is reported to adjust the delay requirement to A+B or AB.

[0386] In one embodiment, packet delay budget modification is used to adjust the synchronization requirements within the synchronization QoS parameter set for the corresponding data stream.

[0387] In some embodiments, the offset information is a synchronization margin.

[0388] In one embodiment, synchronization margin is used to determine or revise synchronization requirements within a synchronization QoS parameter set.

[0389] In some cases, the synchronization requirements in the synchronization QoS parameter set are replaced by the reported synchronization margin.

[0390] In some embodiments, the time information is a timeslot index for the successful reception of packets in a data stream.

[0391] In one embodiment, the time slot index comes from a first device (e.g., Figure 4 (One of the devices 1 to 3 in the list).

[0392] In some embodiments, the time information is an index of the Transmission Time Interval (TTI) for the successful reception of packets in a data stream.

[0393] In one embodiment, the TTI index comes from a first device.

[0394] In some embodiments, the time information is a timestamp for the successful reception of a packet in the data stream.

[0395] In one embodiment, the timestamp comes from a first device.

[0396] In some embodiments, the first device and the second device (e.g., Figure 4 The second device is connected to a network node (e.g., gNB).

[0397] In some embodiments, multiple data streams exist in a single device or multiple devices, and these multiple data streams need to be synchronized. Time slots, TTIs, or timestamps are reported to adjust the scheduling time for synchronization of subsequent transport blocks or subsequent packets.

[0398] In some embodiments, the first signaling includes uplink transmission assistance information. The uplink transmission assistance information may include at least one of the following:

[0399] - An indication of multiple uplink data streams within a logical channel group (LCG).

[0400] - Indication for multiple LCGs

[0401] - An indication that multiple physical uplinks share a channel.

[0402] - An indication of multiple HARQ process IDs

[0403] - Offset information for packet delay budget used in data streams.

[0404] - Timing information for communication across multiple data streams

[0405] - Device type information associated with devices corresponding to multiple data streams, or

[0406] - Traffic type information associated with multiple data streams.

[0407] In some embodiments, the indication for multiple uplink data streams in an LCG is configured to determine synchronous and asynchronous data.

[0408] In this embodiment, the uplink data stream with an indication is identified as synchronization data. Synchronization data refers to data that needs to be synchronized.

[0409] In this embodiment, the uplink data stream with an indication is identified as asynchronous data. Asynchronous data means data that is not (needs) to be synchronized.

[0410] In some cases, this indication is a bit flag, where bit "1" indicates that the uplink data stream is synchronous, while bit "0" indicates that the uplink data stream is asynchronous.

[0411] In some cases, the indication is a code point, where code point 1 indicates that the uplink data stream is synchronous, while code point 2 indicates that the uplink data stream is asynchronous.

[0412] In some embodiments, the indication of multiple LCGs is configured to determine the association of multiple logical channel groups (LCGs).

[0413] In this embodiment, the association of multiple LCGs includes synchronizing data in multiple LCGs.

[0414] In some cases, LCGs with the same indication are related LCGs, where the data in the related LCGs needs to be synchronized.

[0415] As an alternative, the indication of multiple LCGs is a bitmap indicating the correlation of LCGs, where the LCG indicated by the bit "1" is the correlated LCG.

[0416] For example, there are 8 LCGs (LCG1 to LCG8), with a bitmap length of 8 bits, and each bit corresponds to LCG1 to LCG8 sequentially. For example, bitmap "00100100" means that LCG5 and LCG2 are related. In other words, the data in LCG5 and the data in LCG2 need to be synchronized.

[0417] As an alternative, the indication of multiple LCGs is a bit string indicating the group identifier of multiple LCGs, where data in LCGs indicated by the same group identifier is to be synchronized.

[0418] For example, one or more data streams in LCG 1 are indicated by group identifier 1, and one or more data streams in LCG 2 are also indicated by group identifier 1. In this embodiment, the data streams in LCG 1 and LCG 2 need to be synchronized. Additionally, one or more data streams in LCG 3 are indicated by group identifier 2, and one or more data streams in LCG 4 are also indicated by group identifier 2. The data streams in LCG 3 and LCG 4 need to be synchronized.

[0419] In one embodiment, the data streams that need to be synchronized in its logical channel (indicated by the indications of multiple LCGs or the indications of multiple uplink data streams in an LCG) are scheduled based on or by following predefined rules.

[0420] In one embodiment, the predefined rule includes at least one of the following:

[0421] - Data in the logical channels within the LCG to be synchronized needs to be scheduled simultaneously; or

[0422] - Data in logical channels within an LCG that needs to be synchronized is scheduled using constraints based on synchronization requirements in the synchronization information.

[0423] In some embodiments, the logical channels in the LCG to be synchronized include at least one of the following:

[0424] - Same logical channel priority;

[0425] - Same priority bit rate; or

[0426] - Same bucket size duration.

[0427] In some embodiments, the first signaling is at least one of the following:

[0428] -UE capabilities;

[0429] -UE auxiliary information;

[0430] -Media Access Control (MAC) Control Element (CE) signaling, or

[0431] -Uplink Control Information (UCI) signaling.

[0432] In an embodiment where the first signaling is MAC CE signaling, the first signaling includes downlink transmission assistance information, and the MAC CE signaling is a buffer size report (BSR).

[0433] In this embodiment, the downlink transmission assistance information is located in a dedicated Oct (octet) in the short BSR.

[0434] Figure 7A schematic diagram of a short BSR according to an embodiment of the present disclosure is shown. Figure 7 In this context, downlink transmission auxiliary information is located in Oct 2 of the short BSR.

[0435] In one embodiment, downlink transmission auxiliary information is located in a dedicated Oct within the long BSR.

[0436] Figure 8 A schematic diagram of a long BSR according to an embodiment of the present disclosure is shown. Figure 8 In this context, the downlink transmission auxiliary information is located in Oct m+1 of the long BSR.

[0437] Figure 9 A schematic diagram of a long BSR according to an embodiment of the present disclosure is shown. Figure 9 In the long BSR, the downlink transmission auxiliary information is located in Oct 2.

[0438] In some embodiments, downlink transmission auxiliary information is located in a dedicated Oct within the extended (truncated) short BSR.

[0439] In some embodiments, downlink transmission auxiliary information is located in a dedicated Oct within an extended (truncated) long BSR.

[0440] In some embodiments, downlink transmission auxiliary information is located in a dedicated Oct in an extended (truncated) preemptive BSR.

[0441] In embodiments where the first signaling is a BSR and includes downlink transmission auxiliary information, the BSR is a first BSR indicated by a Logical Channel Identifier (LCID) or an Enhanced Logical Channel Identifier (eLCID).

[0442] In some embodiments, the first signaling includes uplink transmission assistance information, and the MAC CE signaling is a buffer size report (BSR).

[0443] In some embodiments, uplink transmission assistance information is located in a dedicated oct within the short BSR. In one embodiment, the location of the uplink transmission assistance information within the short BSR is... Figure 7 The location of the downlink transmission auxiliary information is similar.

[0444] In some embodiments, uplink transmission assistance information is located in a dedicated oct within the long BSR. In one embodiment, the location of the uplink transmission assistance information within the long BSR is... Figure 8 or Figure 9 The location of the downlink transmission auxiliary information is similar.

[0445] In some embodiments, uplink transmission auxiliary information is located in a dedicated Oct within the extended (truncated) short BSR.

[0446] In some embodiments, uplink transmission auxiliary information is located in a dedicated Oct within an extended (truncated) long BSR.

[0447] In some embodiments, uplink transmission auxiliary information is located in a dedicated Oct in an extended (truncated) preemptive BSR.

[0448] In embodiments where the first signaling is a BSR and includes uplink transmission assistance information, the BSR is a second BSR indicated by an LCID or eLCID. That is, the first BSR including downlink transmission assistance information may be the same as or different from the second BSR including uplink transmission assistance information.

[0449] In some embodiments, downlink transmission assistance information and / or uplink transmission assistance information are transmitted by the MAC subheader.

[0450] In one embodiment, uplink transmission auxiliary information is located in the R field of the MAC subheader.

[0451] In one embodiment, downlink transmission assistance information and / or uplink transmission assistance information are located in a dedicated field in the MAC subheader.

[0452] Figure 10 A schematic diagram of a MAC subheading according to an embodiment of the present disclosure is shown. Figure 10 The MAC sub-header in the packet only shows the LCID. Figure 10 In the MAC subheading, downlink transmission assistance information is located in Oct 2, and uplink transmission assistance information is located in Oct 3.

[0453] Figure 11 A schematic diagram of a MAC subheading according to an embodiment of the present disclosure is shown. Figure 11 The MAC sub-header in the packet contains both LCID and eLCID. Figure 11 In the MAC subheading, downlink transmission assistance information is located in Oct 3 of the MAC subheading, and uplink transmission assistance information is located in Oct 4 of the MAC subheading. Both of these information are located after the eLCID indication.

[0454] In some embodiments, UCI signaling is signaling used for resource release.

[0455] In some embodiments, UCI signaling is signaling used for HARQ ACK (Hybrid Automatic Repeat Request Acknowledgment).

[0456] In some embodiments, UCI signaling is signaling used for CSI (Channel State Information) reporting.

[0457] In some embodiments, a special field in UCI signaling indicates downlink transmission auxiliary information.

[0458] Figure 12 This is a schematic diagram relating to a wireless terminal 120 according to an embodiment of the present disclosure. The wireless terminal 120 may be a user equipment (UE), mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless terminal 120 may include a processor 1200, such as a microprocessor or application-specific integrated circuit (ASIC), a storage unit 1210, and a communication unit 1220. The storage unit 1210 may be any data storage device storing program code 1212 accessed and executed by the processor 1200. Embodiments of the storage unit 1210 include, but are not limited to, a user identity module (SIM), read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage devices. The communication unit 1220 may be a transceiver and is used to transmit and receive signals (e.g., messages or data packets) based on the processing results of the processor 1200. In one embodiment, the communication unit 1220 communicates via… Figure 12 At least one antenna 1222 shown transmits and receives signals.

[0459] In one embodiment, storage unit 1210 and program code 1212 may be omitted, and processor 1200 may include storage unit with the stored program code.

[0460] The processor 1200 may, for example, implement any of the steps in the exemplary embodiment on the wireless terminal 120 by executing program code 1212.

[0461] The communication unit 1220 may be a transceiver. The communication unit 1220 may be used as an alternative or supplement to a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless network node (e.g., a base station).

[0462] Figure 13This diagram relates to a wireless network node 130 according to an embodiment of the present disclosure. The wireless network node 130 may be a satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN) node, next-generation RAN (NG-RAN) node, gNB, eNB, gNB central unit (gNB-CU), gNB distributed unit (gNB-DU), data network, core network, or radio network controller (RNC), and is not limited thereto. Additionally, the wireless network node 130 may include (execute) at least one network function, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), application function (AF), etc. The wireless network node 130 may include a processor 1300, such as a microprocessor or ASIC, a storage unit 1310, and a communication unit 1320. The storage unit 1310 may be any data storage device storing program code 1312 accessed and executed by the processor 1300. Examples of storage unit 1310 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 1320 may be a transceiver and is used to transmit and receive signals (e.g., messages or data packets) based on the processing results of processor 1300. In one example, communication unit 1320 is connected via... Figure 13 At least one antenna 1322 shown transmits and receives signals.

[0463] In one embodiment, storage unit 1310 and program code 1312 may be omitted. Processor 1300 may include storage unit containing the stored program code.

[0464] The processor 1300 may, for example, implement any of the steps described in the exemplary embodiments on the wireless network node 130 via executing program code 1312.

[0465] The communication unit 1320 may be a transceiver. The communication unit 1320 may be used as an alternative or supplement to a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless terminal (e.g., user equipment or another wireless network node).

[0466] While various embodiments of this disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0467] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of these elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0468] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, and symbols that can be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0469] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit"), or any combination of these technologies.

[0470] To clearly illustrate this interchangeability of hardware, firmware, and software, the functionality of various illustrative components, blocks, units, circuits, and steps has been generally described above. Whether such functionality is implemented in hardware, firmware, software, or a combination of these technologies depends on the specific application and design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions do not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., may be configured to perform one or more of the functions described herein. The terms “configured to” or “configured for” as used herein with respect to a specified operation or function refer to processors, devices, components, circuits, structures, machines, units, etc., that are physically constructed, programmed, and / or arranged to perform a particular operation or function.

[0471] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, units, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs), which can include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, units, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0472] Computer-readable media include both computer storage media and communication media, wherein the communication media includes any medium that enables a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0473] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for ease of discussion, various units are described as independent entities; however, it will be apparent to those skilled in the art that two or more units may be combined to form a single unit that performs the relevant functions according to embodiments of this disclosure.

[0474] Additionally, memory or other memory and communication components may be employed in the embodiments of this disclosure. It should be understood that, for clarity, the above description has referenced various functional units and processors in the embodiments of this disclosure. However, it will be apparent that any suitable functional distribution may be used among different functional units, processing logic elements, or domains without departing from this disclosure. For example, functions shown to be performed by different processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and not indications of a strict logical or physical structure or organization.

[0475] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be endowed with the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the claims.

Claims

1. A wireless communication method used in a first node, the method comprising: The configuration signaling is received from the second node, which includes configuration information associated with synchronizing multiple data streams.

2. The wireless communication method according to claim 1, further comprising: Communication with the multiple data streams is performed based on the configuration information.

3. The wireless communication method according to claim 1 or 2, wherein, Synchronizing the multiple data streams includes at least one of the following: Simultaneous processing of the multiple data streams, Synchronously schedule the multiple data streams, or Grouping of multiple devices associated with the multiple data streams.

4. The wireless communication method according to any one of claims 1 to 3, wherein, The configuration signaling is included in the General Packet Radio Service (GPRS) Transport Protocol packet, the GPRS Transport Protocol (GTP) header, the Quality of Service (QoS) parameter set, the predefined radio bearer, or the predefined Protocol Data Unit (PDU) session.

5. The wireless communication method according to any one of claims 1 to 4, wherein, The configuration information includes at least one of the following: a device cluster indication of multiple devices associated with the multiple data streams, or a synchronization indication for synchronizing the multiple data streams.

6. The wireless communication method according to claim 5, wherein, The device cluster indication includes at least one of the following: QoS parameters used for the multiple data streams, Device cluster information associated with the device clusters corresponding to the multiple data streams, or Synchronization indications for the multiple data streams.

7. The wireless communication method according to claim 6, wherein, The device cluster information includes: associated device identifiers for the set of device identifiers of the devices, or device cluster identifiers.

8. The wireless communication method according to any one of claims 5 to 7, wherein, The synchronization indication is determined by a synchronization QoS parameter set, synchronization QoS parameters, or a synchronization QoS stream.

9. The wireless communication method according to claim 8, wherein, The synchronization QoS parameter set includes at least one of the following: The minimum packet delay budget within the packet delay budget of the data stream. The maximum packet delay budget within the packet delay budget of the data stream. The average packet latency budget of the data stream. The offset used for the packet delay budget of the data stream. The reference packet delay budget within the packet delay budget of the data stream. The time interval for synchronizing the multiple data streams, The common packet delay budget for each data stream, or Synchronization level.

10. The wireless communication method according to claim 8, wherein, The synchronous QoS parameter set includes a set of QoS Flow Identifiers (QFIs).

11. The wireless communication method according to any one of claims 8 to 10, wherein, The performance characteristics of the data stream are determined based on the synchronous QoS parameter set.

12. The wireless communication method according to any one of claims 8 to 11, wherein, The determination of the synchronization QoS parameter set is based on the first field in the PDU session information.

13. The wireless communication method according to any one of claims 8 to 12, wherein, The activation / deactivation of the synchronous QoS parameter set is determined based on the second field in the PDU session information.

14. The wireless communication method according to any one of claims 5 to 7, wherein, The synchronization indication is determined by the radio bearer used for the plurality of data streams.

15. The wireless communication method according to claim 14, wherein, The wireless bearer is a predefined wireless bearer used for the synchronization.

16. The wireless communication method according to any one of claims 5 to 7, wherein, The synchronization indication is determined by a PDU session that includes at least one radio bearer, the radio bearer including the QoS stream of the data stream to be synchronized.

17. The wireless communication method according to claim 16, wherein, The PDU session is determined by the GTP header of the PDU session.

18. The wireless communication method according to claim 16 or 17, wherein, The GTP header of the PDU session indicates the synchronous PDU type.

19. The wireless communication method according to any one of claims 5 to 7, wherein, The synchronization indication is determined by the GTP header of the synchronization.

20. The wireless communication method according to claim 18 or 19, wherein, The GTP header is a type of extended header, wherein the type of the extended header is determined by the value of the next extended header type field.

21. The wireless communication method according to any one of claims 5 to 7, wherein, The synchronization indication is determined by the importance indication of the PDU set used for the multiple data streams.

22. The wireless communication method according to claim 21, wherein, The PDU set importance indicator includes at least one of the following: PDU importance levels for the multiple data streams A synchronization request indication used to synchronize the multiple data streams, or A set of QoS parameters used to synchronize the multiple data streams.

23. The wireless communication method according to any one of claims 1 to 22, wherein, The first node is a network node and the second node is a core network node.

24. The wireless communication method according to claim 1 or 2, wherein, Synchronizing the multiple data streams includes at least one of the following: Jointly process the multiple data streams, The combined indication of the multiple data streams, or Transmit auxiliary information associated with the synchronization to the second node.

25. The wireless communication according to claim 24, wherein, The configuration signaling includes at least one of the following: radio resource control signaling, user equipment capability, media access control (MAC) control element (CE) signaling, or downlink control information signaling.

26. The wireless communication method according to any one of claims 24 or 25, wherein, The configuration information includes synchronization instructions for the multiple data streams.

27. The wireless communication method according to claim 26, wherein, The synchronization indication is determined by at least one of a predefined radio bearer or a predefined PDU session.

28. The wireless communication method according to claim 1 or any one of 24 to 27, wherein, The first node is a user equipment and the second node is a network node.

29. A wireless communication method used in a second node, the method comprising: A configuration signaling message is transmitted to the first node, the configuration signaling message including configuration information associated with synchronizing multiple data streams.

30. The wireless communication method according to claim 29, further comprising: Communication with the multiple data streams is performed based on the configuration information.

31. The wireless communication method according to claim 29 or 30, wherein, Synchronizing the multiple data streams includes at least one of the following: Simultaneous processing of the multiple data streams, Synchronously schedule the multiple data streams, or Grouping of multiple devices associated with the multiple data streams.

32. The wireless communication method according to any one of claims 29 to 31, wherein, The configuration signaling is included in the General Packet Radio Service (GPRS) Transport Protocol packet, the GPRS Transport Protocol (GTP) header, the Quality of Service (QoS) parameter set, the predefined radio bearer, or the predefined Protocol Data Unit (PDU) session.

33. The wireless communication method according to any one of claims 29 to 32, wherein, The configuration information includes at least one of the following: a device cluster indication of multiple devices associated with the multiple data streams, or a synchronization indication for synchronizing the multiple data streams.

34. The wireless communication method according to claim 33, wherein, The device cluster indication includes at least one of the following: QoS parameters used for the multiple data streams, Device cluster information associated with the device clusters corresponding to the multiple data streams, or Synchronization indications for the multiple data streams.

35. The wireless communication method according to claim 34, wherein, The device cluster information includes associated device identifiers for the set of device identifiers of the devices, or device cluster identifiers.

36. The wireless communication method according to any one of claims 33 to 35, wherein, The synchronization indication is determined by a synchronization QoS parameter set, synchronization QoS parameters, or a synchronization QoS stream.

37. The wireless communication method according to claim 36, wherein, The synchronization QoS parameter set includes at least one of the following: The minimum packet delay budget within the packet delay budget of the data stream. The maximum packet delay budget within the packet delay budget of the data stream. The average packet latency budget of the data stream. The offset used for the packet delay budget of the data stream. The reference packet delay budget within the packet delay budget of the data stream. The time interval for synchronizing the multiple data streams, The common packet delay budget for each data stream, or Synchronization level.

38. The wireless communication method according to claim 36, wherein, The synchronous QoS parameter set includes a set of QoS Flow Identifiers (QFIs).

39. The wireless communication method according to any one of claims 36 to 38, wherein, The performance characteristics of the data stream are determined based on the synchronous QoS parameter set.

40. The wireless communication method according to any one of claims 36 to 39, wherein, The determination of the synchronization QoS parameter set is based on the first field in the PDU session information.

41. The wireless communication method according to any one of claims 36 to 40, wherein, The activation / deactivation of the synchronous QoS parameter set is determined based on the second field in the PDU session information.

42. The wireless communication method according to any one of claims 33 to 35, wherein, The synchronization indication is determined by the radio bearer used for the plurality of data streams.

43. The wireless communication method according to claim 42, wherein, The wireless bearer is a predefined wireless bearer used for the synchronization.

44. The wireless communication method according to any one of claims 33 to 35, wherein, The synchronization indication is determined by a PDU session that includes at least one radio bearer, the radio bearer including the QoS stream of the data stream to be synchronized.

45. The wireless communication method according to claim 44, wherein, The PDU session is determined by the GTP header of the PDU session.

46. ​​The wireless communication method according to claim 44 or 45, wherein, The GTP header of the PDU session indicates the synchronous PDU type.

47. The wireless communication method according to any one of claims 33 to 35, wherein, The synchronization indication is determined by the GTP header of the synchronization.

48. The wireless communication method according to claim 46 or 47, wherein, The GTP header is a type of extended header, wherein the type of the extended header is determined by the value of the next extended header type field.

49. The wireless communication method according to any one of claims 33 to 35, wherein, The synchronization indication is determined by the importance indication of the PDU set used for the multiple data streams.

50. The wireless communication method according to claim 49, wherein, The PDU set importance indicator includes at least one of the following: PDU importance levels for the multiple data streams A synchronization request indication used to synchronize the multiple data streams, or A set of QoS parameters used to synchronize the multiple data streams.

51. The wireless communication method according to any one of claims 29 to 50, wherein, The first node is a network node and the second node is a core network node.

52. The wireless communication method according to claim 29 or 30, wherein, Synchronizing the multiple data streams includes at least one of the following: Jointly process the multiple data streams, The combined indication of the multiple data streams, or Transmit auxiliary information associated with the synchronization to the second node.

53. The wireless communication according to claim 52, wherein, The configuration signaling includes at least one of the following: radio resource control signaling, user equipment capability, media access control (MAC) control element (CE) signaling, or downlink control information signaling.

54. The wireless communication method according to any one of claims 52 or 53, wherein, The configuration information includes synchronization instructions for the multiple data streams.

55. The wireless communication method according to claim 54, wherein, The synchronization indication is determined by at least one of a predefined radio bearer or a predefined PDU session.

56. The wireless communication method according to any one of claims 29 or 52 to 55, wherein, The first node is a user equipment and the second node is a network node.

57. A wireless communication method used in a first node, the method comprising: A first signaling message is transmitted to the second node, the first signaling message being associated with configuration information related to synchronizing multiple data streams.

58. The wireless communication method according to claim 57, wherein, The first signaling includes downlink transmission assistance information, which includes at least one of the following: Offset information used for packet delay budget The timing information of the communication of the multiple data streams, Device type information associated with the device corresponding to the plurality of data streams, or Traffic type information associated with the multiple data streams.

59. The wireless communication method according to claim 58, wherein, The offset information includes at least one of the following: an offset that modifies the packet delay budget, or a synchronization margin for the packet delay budget.

60. The wireless communication method according to claim 58 or 59, wherein, The time information includes a time slot index, transmission time interval index, or timestamp associated with communication of the plurality of data streams.

61. The wireless communication method according to claims 57 to 60, wherein, The first signaling includes uplink transmission assistance information, which includes at least one of the following: Indication used for multiple uplink data streams within a logical channel group (LCG) Indications for multiple LCGs Indication of multiple physical uplinks sharing a channel. Indication of multiple HARQ process IDs Offset information used for packet delay budget The timing information of the communication of the multiple data streams, Device type information associated with the device corresponding to the plurality of data streams, or Traffic type information associated with the multiple data streams.

62. The wireless communication method according to any one of claims 57 to 61, wherein, The first signaling includes at least one of the following: UE capabilities UE assistance information, MAC CE signaling, or Uplink control information signaling.

63. The wireless communication method according to claim 62, wherein, The MAC CE signaling is a Buffer Size Report (BSR), and The information included in the first signaling is located in a dedicated octet of the BSR.

64. The wireless communication method according to claim 62, wherein, The first signaling includes the MAC CE signaling: and The downlink transmission assistance information and / or uplink transmission assistance information included in the first signaling are located in the MAC subheader of the MAC CE signaling.

65. The wireless communication method according to claim 62, wherein, The uplink control information signaling includes at least one of uplink control information for resource release, HARQ ACK information, or channel state information.

66. The wireless communication method according to any one of claims 57 to 65, wherein, The first node is a user equipment and the second node is a network node.

67. A wireless communication method used in a second node, the method comprising: Receive a first signaling from the first node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

68. The wireless communication method according to claim 67, wherein, The first signaling includes downlink transmission assistance information, which includes at least one of the following: Offset information used for packet delay budget The timing information of the communication of the multiple data streams, Device type information associated with the device corresponding to the plurality of data streams, or Traffic type information associated with the multiple data streams.

69. The wireless communication method according to claim 68, wherein, The offset information includes at least one of the following: an offset that modifies the packet delay budget, or a synchronization margin for the packet delay budget.

70. The wireless communication method according to claim 68 or 69, wherein, The time information includes a time slot index, transmission time interval index, or timestamp associated with the communication of the plurality of data streams.

71. The wireless communication method according to claims 67 to 70, wherein, The first signaling includes uplink transmission assistance information, which includes at least one of the following: Indication used for multiple uplink data streams within a logical channel group (LCG) Indications for multiple LCGs Indication of multiple physical uplinks sharing a channel. Indication of multiple HARQ process IDs Offset information used for packet delay budget The timing information of the communication of the multiple data streams, Device type information associated with the device corresponding to the plurality of data streams, or Traffic type information associated with the multiple data streams.

72. The wireless communication method according to any one of claims 67 to 71, wherein, The first signaling includes at least one of the following: UE capabilities UE assistance information, MAC CE signaling, or Uplink control information signaling.

73. The wireless communication method according to claim 72, wherein, The MAC CE signaling is a Buffer Size Report (BSR), and The information included in the first signaling is located in a dedicated octet of the BSR.

74. The wireless communication method according to claim 72, wherein, The first signaling includes the MAC CE signaling: and The downlink transmission assistance information and / or uplink transmission assistance information included in the first signaling are located in the MAC subheader of the MAC CE signaling.

75. The wireless communication method according to claim 72, wherein, The uplink control information signaling includes at least one of uplink control information for resource release, HARQ ACK information, or channel state information.

76. The wireless communication method according to any one of claims 67 to 75, wherein, The first node is a user equipment and the second node is a network node.

77. A first node, comprising: The communication unit is configured to receive configuration signaling from the second node, the configuration signaling including configuration information associated with synchronizing multiple data streams.

78. The first node of claim 77, further comprising a processor configured to perform the wireless communication method of any one of claims 2 to 28.

79. A second node, comprising: The communication unit is configured to transmit configuration signaling to a first node, the configuration signaling including configuration information associated with synchronizing multiple data streams.

80. The second node of claim 79 further includes a processor configured to perform the wireless communication method of any one of claims 30 to 56.

81. A first node, comprising: The communication unit is configured to transmit a first signaling to a second node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

82. The first node of claim 81, further comprising a processor configured to perform the wireless communication method of any one of claims 58 to 67.

83. A second node, comprising: A communication unit is configured to receive a first signaling from a first node, the first signaling being associated with configuration information related to synchronizing multiple data streams.

84. The second node of claim 83 further includes a processor configured to perform the wireless communication method of any one of claims 68 to 77.

85. A computer program product comprising computer-readable program medium code stored thereon, the code causing the processor, when executed by a processor, to perform the wireless communication method according to any one of claims 1 to 77.

Images