Method for sending synchronization information, and apparatus, device and storage medium

Abstract

A method for sending synchronization information, and an apparatus, a device and a storage medium. The method for sending synchronization information comprises: receiving first configuration information sent by a network device, wherein the first configuration information is used for configuring a trigger condition, which is used for triggering a terminal to send synchronization information of at least two quality-of-service (QoS) flows to the network device; and when the trigger condition is met, sending the synchronization information of the at least two QoS flows to the network device. By means of the method, when a trigger condition is met, a terminal reports synchronization information between QoS is reported to a network device, such that the occasion of the terminal reporting the synchronization information is reasonable, and signaling overheads can be saved on compared with a periodic reporting mode.

Description

Method, device, equipment and storage medium for sending synchronization information Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method, apparatus, device, and storage medium for sending synchronization information. Background Art

[0002] The Quality of Service (QoS) model in 5G (5th Generation Mobile Communication Technology) is based on QoS flows. In the Non-Access Stratum (NAS), a QoS flow is the smallest granularity at which QoS can be differentiated within a Protocol Data Unit (PDU) session. A QoS flow can be identified by the QoS Flow ID (QFI) in the packet header.

[0003] Multi-modality communication services can be applied to a variety of technology areas, such as industry, robotics, telepresence, virtual reality, augmented reality, healthcare, road traffic, gaming, education, culture, and smart grids. Applications supported by these multi-modality communication services can input from multiple sources and / or output to multiple destinations, enabling more efficient information delivery.

[0004] Multimodal communication services involve data in different modalities, such as video data, audio data, tactile data, and sensor data. Video data can be either real-time video data captured and transmitted by a mobile phone, or edited video data; audio data can be real-time audio data recorded and transmitted by a mobile phone, or edited audio data; tactile data can be the sensation of touching a surface (such as pressure, texture, vibration, temperature, etc.) or the sensation of movement (such as gravity, tension, and position); and sensor data can be environmental information received by sensors (such as brightness, temperature, and humidity).

[0005] When multimodal communication services are applied to virtual reality, data of different dimensions can form multiple QoS flows. Synchronization between these multiple QoS flows is crucial to avoid negative impact on user experience, that is, viewers find that data of different dimensions are out of sync.

[0006] Summary of the Invention

[0007] In order to optimize the synchronization mechanism between multiple QoS flows, embodiments of the present disclosure provide a method, apparatus, device, and storage medium for sending synchronization information.

[0008] According to a first aspect of an embodiment of the present disclosure, a method for sending synchronization information is provided, which is executed by a terminal.

[0009] receiving first configuration information sent by a network device, where the first configuration information is used to configure a trigger condition, where the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0010] When the trigger condition is met, synchronization information of at least two quality of service (QoS) flows is sent to the network device.

[0011] According to a second aspect of an embodiment of the present disclosure, a method for sending synchronization information is provided, which is performed by a network device.

[0012] Sending first configuration information to the terminal, where the first configuration information is used to configure a trigger condition, and the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0013] Receive synchronization information of at least two quality of service (QoS) flows sent by the terminal.

[0014] According to a third aspect of an embodiment of the present disclosure, there is provided a communication device, configured in a terminal, the device comprising:

[0015] a transceiver module configured to: receive first configuration information sent by a network device, where the first configuration information is used to configure a trigger condition, where the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0016] And when the trigger condition is met, the synchronization information is sent to the network device.

[0017] According to a fourth aspect of an embodiment of the present disclosure, there is provided a communication apparatus, configured in a network device, the apparatus comprising:

[0018] The transceiver module is configured to: send first configuration information to the terminal, where the first configuration information is used to configure a trigger condition, and the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service QoS flows to the network device; and receive synchronization information of at least two quality of service QoS flows sent by the terminal.

[0019] According to a fifth aspect of an embodiment of the present disclosure, one or more processors are provided; wherein the processor is used to execute the method described in the first aspect of the embodiment of the present disclosure.

[0020] According to a sixth aspect of an embodiment of the present disclosure, one or more processors are provided; wherein the processor is used to execute the method described in the second aspect of the embodiment of the present disclosure.

[0021] According to the seventh aspect of an embodiment of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the method described in the first aspect of the embodiment of the present disclosure, and the network device is configured to implement the method described in the second aspect of the embodiment of the present disclosure.

[0022] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect or the second aspect of the embodiment of the present disclosure.

[0023] In the method provided in the embodiment of the present disclosure, by setting trigger conditions, the terminal reports the synchronization information between QoS to the network device when the trigger conditions are met, so that the timing of the terminal reporting the synchronization information is reasonable, which can save signaling overhead compared to the periodic reporting method. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0025] FIG1 is a schematic diagram of a communication system architecture provided according to an embodiment of the present disclosure.

[0026] 2A-2B are schematic diagrams of an interaction for sending synchronization information according to an embodiment of the present disclosure.

[0027] 3A-3D are flowcharts of sending synchronization information according to an embodiment of the present disclosure.

[0028] FIG4 is a flowchart of sending synchronization information according to an embodiment of the present disclosure.

[0029] 5A-5B are structural diagrams of a communication device according to an embodiment of the present disclosure;

[0030] 6A-6B are structural diagrams of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] Embodiments of the present disclosure provide a method, apparatus, device, and storage medium for sending synchronization information.

[0032] In a first aspect, an embodiment of the present disclosure provides a method for sending synchronization information, performed by a terminal, the method comprising:

[0033] receiving first configuration information sent by a network device, where the first configuration information is used to configure a trigger condition, where the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0034] When the trigger condition is met, synchronization information of at least two quality of service (QoS) flows is sent to the network device.

[0035] In the above embodiment, by setting trigger conditions, the terminal reports synchronization information between QoS to the network device when the trigger conditions are met, so that the timing of the terminal reporting synchronization information is reasonable, which can save signaling overhead compared to periodic reporting.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the first configuration information includes: identifiers of at least two QoS flows and at least one threshold.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, when the first configuration information includes identifiers of two QoS flows and a threshold, satisfying the trigger condition includes one of the following:

[0038] The time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to the threshold;

[0039] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the threshold;

[0040] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0041] In the above embodiment, a symmetric threshold is configured to save signaling overhead.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes one of the following:

[0043] A time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to one of the two thresholds;

[0044] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the other threshold value of the two threshold values;

[0045] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0046] In the above embodiment, configuring two asymmetric thresholds can improve reporting accuracy.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes at least one of the following:

[0048] The time difference between the data of the third QoS flow and the data of the fourth QoS flow is greater than or equal to the first threshold value of the two threshold values.

[0049] The time difference between the data of the fourth QoS flow and the data of the third QoS flow is greater than or equal to the second threshold of the two thresholds;

[0050] The third QoS flow is the one with the smallest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows, and the fourth QoS flow is the one with the largest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows.

[0051] In combination with some embodiments of the first aspect, in some embodiments, when the first configuration information includes identifiers of at least three QoS flows and at least one threshold, each threshold corresponds to the time difference of data between two QoS flows.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the identifiers of the two QoS flows corresponding to the threshold are determined according to the following parameters:

[0053] the position of the threshold value in the ranking of the at least one threshold value;

[0054] the number of identifiers of the at least three QoS flows;

[0055] The identifications of the at least three QoS flows are sequenced.

[0056] In combination with some embodiments of the first aspect, in some embodiments, satisfying the trigger condition includes: the time difference between any two QoS flows among the three QoS flows corresponding to the identifiers of the at least three QoS flows is greater than or equal to the threshold corresponding to the any two QoS flows.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the first data of one QoS flow of the two QoS flows has been completely sent to the MAC layer, and the second data of the other QoS flow of the two QoS flows has not been completely sent to the MAC layer, the first data corresponds to the second data, and the time difference between the two QoS flows is:

[0058] a difference between the current time and the time when all first data in one of the two QoS flows are sent to the MAC layer;

[0059] Alternatively, the value may be a difference between the current time and the time at which the first data in one of the two QoS flows is sent over the air interface.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the time difference is determined based on feedback information, where the feedback information is used to indicate whether the data of the QoS flow is successfully received, and the feedback information includes at least one of the following:

[0061] Hybrid Automatic Repeat Request Acknowledgement HARQ ACK feedback information;

[0062] Status report of Radio Link Layer Control Protocol Acknowledgement Mode RLC AM;

[0063] Packet Data Convergence Protocol PDCP status report.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the synchronization information includes at least one of the following:

[0065] The identifier of the QoS flow that meets the trigger condition;

[0066] The time difference information between the QoS flows that meet the trigger condition;

[0067] The data volume of the QoS flow that meets the trigger condition.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the synchronization information includes at least one of the following:

[0069] an identifier of a data radio bearer (DRB), wherein the DRB includes a QoS flow that satisfies the trigger condition;

[0070] The time difference information between the QoS flows that meet the trigger condition;

[0071] The data volume of the QoS flow that meets the trigger condition within the DRB.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the synchronization information includes at least one of the following:

[0073] an identifier of a logical channel group LCG, wherein the LCG includes the QoS flows that meet the trigger condition;

[0074] The time difference information between the QoS flows that meet the trigger condition;

[0075] The data volume of the QoS flow that meets the trigger condition in the LCG.

[0076] In combination with some embodiments of the first aspect, in some embodiments, the time difference information is the numerical value of the time difference between the QoS flows that meet the trigger condition, or the time difference information is time difference related information, and the time difference related information is the difference between the time difference and the corresponding threshold.

[0077] In combination with some embodiments of the first aspect, in some embodiments, the synchronization information includes a time difference information, and the time difference information is calculated based on multiple time differences.

[0078] In combination with some embodiments of the first aspect, in some embodiments, the synchronization information includes multiple time difference information and multiple data amounts corresponding to the time difference information.

[0079] In combination with some embodiments of the first aspect, in some embodiments, the first configuration information is further used to configure activation indication information, and the activation indication information is used to indicate activation of the trigger condition.

[0080] In combination with some embodiments of the first aspect, in some embodiments, the first configuration information is further used to configure the trigger condition and a disable indication, and the disable indication is used to indicate disabling the trigger condition.

[0081] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0082] Receive second configuration information sent by the network device, where the second configuration information is used to configure the duration of a timer, and the timer is used to disable a trigger condition related to at least one QoS flow, wherein the terminal has sent synchronization information between the at least one QoS flow and other QoS flows within a first duration before the current moment.

[0083] In conjunction with some embodiments of the first aspect, in some embodiments, sending synchronization information of the at least two quality of service (QoS) flows to the network device includes:

[0084] A radio link control (RRC) signaling is sent, where the RRC signaling includes synchronization information of the at least two quality of service (QoS) flows.

[0085] In conjunction with some embodiments of the first aspect, in some embodiments, sending synchronization information of the at least two quality of service (QoS) flows to the network device includes:

[0086] A medium access control element MAC CE is sent, where the MAC CE includes synchronization information of the at least two quality of service (QoS) flows.

[0087] In combination with some embodiments of the first aspect, in some embodiments, a new logical channel identifier LCID is indicated in the MAC header corresponding to the MAC CE, and the new LCID is used to indicate that the MAC CE is used to send synchronization information of the at least two quality of service QoS flows.

[0088] In combination with some embodiments of the first aspect, in some embodiments, the MAC header corresponding to the MAC CE includes a new eLCID, and the new eLCID is used to indicate that the MAC CE is used to send synchronization information of the at least two quality of service QoS flows.

[0089] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0090] The priority of the MAC CE in the logical channel priority processing is determined according to the protocol agreement.

[0091] In combination with some embodiments of the first aspect, in some embodiments, when the trigger condition is met, sending synchronization information of at least two quality of service (QoS) flows to the network device includes:

[0092] When the trigger condition is met, generating a report, the report including synchronization information of the at least two quality of service (QoS) flows;

[0093] The generated report is sent to the network device.

[0094] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0095] Cancel sending of the generated report if any of the following conditions are met:

[0096] The service data unit SDU associated with the report has been discarded;

[0097] A MAC PDU is transmitted, wherein the MAC PDU includes an SDU associated with the report;

[0098] A MAC PDU includes a MAC CE for transmitting the synchronization information, and the MAC CE includes an SDU related to the report.

[0099] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0100] In the case that there is at least one report that has been generated and not sent, if there is an uplink shared channel UL-SCH for transmitting new data, and the UL-SCH is capable of transmitting the MAC CE after running the logical channel priority processing LCP, then the MAC CE is generated; if the UL-SCH does not exist and the current processing flow does not include a pending scheduling request triggered by the logical channel corresponding to the report, then a scheduling request is triggered.

[0101] In a second aspect, an embodiment of the present disclosure provides a method for receiving synchronization information, performed by a network device, the method comprising:

[0102] Sending first configuration information to the terminal, where the first configuration information is used to configure a trigger condition, and the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0103] Receive synchronization information of at least two quality of service (QoS) flows sent by the terminal.

[0104] In combination with some embodiments of the second aspect, in some embodiments, the first configuration information is further used to configure activation indication information, and the activation indication information is used to indicate activation of the trigger condition.

[0105] In combination with some embodiments of the second aspect, in some embodiments, the first configuration information is further used to configure the trigger condition and a disable indication, and the disable indication is used to indicate the disablement of the trigger condition.

[0106] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0107] Second configuration information is sent to the terminal, where the second configuration information is used to configure a duration of a timer, where the timer is used to disable a trigger condition related to at least one quality of service flow.

[0108] In conjunction with some embodiments of the second aspect, in some embodiments, the receiving synchronization information of at least two quality of service (QoS) flows sent by the terminal includes:

[0109] A radio link control (RRC) signaling is received, where the RRC signaling includes synchronization information of at least two quality of service (QoS) flows.

[0110] In conjunction with some embodiments of the second aspect, in some embodiments, the receiving synchronization information of at least two quality of service (QoS) flows sent by the terminal includes:

[0111] A medium access control element (MAC CE) is received, where the MAC CE includes synchronization information of at least two quality of service (QoS) flows.

[0112] In a third aspect, an embodiment of the present disclosure provides a communication device, configured in a terminal, the device comprising:

[0113] a transceiver module configured to: receive first configuration information sent by a network device, where the first configuration information is used to configure a trigger condition, where the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0114] When the trigger condition is met, synchronization information of at least two quality of service (QoS) flows is sent to the network device.

[0115] In a fourth aspect, an embodiment of the present disclosure provides a communication device, configured in a terminal, the device comprising:

[0116] a transceiver module configured to: send first configuration information to the terminal, where the first configuration information is used to configure a trigger condition, where the trigger condition is used to trigger the terminal to send synchronization information of at least two quality of service (QoS) flows to the network device;

[0117] as well as

[0118] Receive synchronization information of at least two quality of service (QoS) flows sent by the terminal.

[0119] In a fifth aspect, an embodiment of the present disclosure provides a communication device, including a processor and a memory, wherein:

[0120] The memory is used to store computer programs;

[0121] The processor is configured to execute the computer program to implement the method according to any one of the first aspects.

[0122] In a sixth aspect, an embodiment of the present disclosure provides a communication device, including a processor and a memory, wherein:

[0123] The memory is used to store computer programs;

[0124] The processor is configured to execute the computer program to implement the method according to any one of the second aspects.

[0125] In a ninth aspect, an embodiment of the present disclosure provides a communication device, including a processor and a memory, wherein:

[0126] The memory is used to store computer programs;

[0127] The processor is configured to execute the computer program to implement the method according to any one of the third aspects.

[0128] In the tenth aspect, an embodiment of the present disclosure provides a communication system, comprising a first device, a second device, and a third device, wherein the first device is configured to execute the method described in the first aspect, the second device is configured to execute the method described in the second aspect, and the third device is configured to execute the method described in the third aspect.

[0129] In the eleventh aspect, an embodiment of the present disclosure provides a computer-readable storage medium, in which instructions are stored. When the instructions are called and executed on a computer, the computer executes the method as described in any one of the first aspect, or the method as described in any one of the second aspect, or the method as described in any one of the third aspect.

[0130] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method according to the first aspect or the second aspect.

[0131] The embodiments of the present disclosure are now further described with reference to the accompanying drawings and specific implementation methods.

[0132] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present disclosure. Rather, they are merely examples of devices and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0133] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0134] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first indication information may also be referred to as the second indication information, and similarly, the second indication information may also be referred to as the first indication information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0135] The embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be understood as limiting the present disclosure.

[0136] As shown in Figure 1A, the method provided in the embodiment of the present disclosure can be applied to a wireless communication system 100, which may include a terminal 101 and a network device 102. It should be noted that the wireless communication system 100 may also include other devices, and this application does not limit the devices included in the wireless communication system 100.

[0137] The wireless communication system 100 is applicable to both low-frequency and high-frequency scenarios. Application scenarios of the wireless communication system 100 include, but are not limited to, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, worldwide interoperability for microwave access (WiMAX) communication systems, cloud radio access networks (CRAN) systems, future fifth-generation (5G) systems, new radio (NR) communication systems, future evolved public land mobile networks (PLMN) systems, and Internet of Things systems.

[0138] Terminal 101 may be an access terminal, a terminal unit, a terminal station, a mobile station (MS), a remote station, a remote terminal, a mobile terminal, a wireless communication device, a terminal agent, an Internet of Things terminal, etc. The terminal 101 may have a wireless transceiver function, and may communicate with one or more network devices of one or more communication systems (such as wireless communication) and receive network services provided by the network devices, where the network devices include but are not limited to the network device 102 shown in the figure. Terminal 101 may also be an Internet of Things (Ambient-IoT) terminal. Compared with ordinary terminals, the complexity, manufacturing cost, and maintenance cost of the Internet of Things terminal are all lower. The Internet of Things terminal may not be equipped with a battery and is powered by receiving electromagnetic signals. The Internet of Things terminal may also have a battery with a small amount of electrical storage function, which does not require manual charging, but obtains battery energy from the outside, for example, by obtaining battery energy from external electromagnetic waves, thermal energy, kinetic energy, etc.

[0139] The network device 102 may be a base station, an intermediate node, a core network device, etc.

[0140] The present disclosure provides a method for sending synchronization information. FIG2A is a flowchart of a method for sending synchronization information according to an embodiment of the present disclosure. As shown in FIG2A , the method includes the following steps:

[0141] Step S2101 : The network device 102 sends first configuration information to the terminal 101 .

[0142] In some embodiments, the network device 102 sends Radio Resource Control (RRC) information to the terminal 101, where the RRC information includes first configuration information.

[0143] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, where the RRC configuration information includes first configuration information.

[0144] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, and the IE CellGroupConfig in the RRC configuration information includes the first configuration information.

[0145] In some embodiments, a new IE QSDR-Config is added to the IE CellGroupConfig to indicate the first configuration information, wherein QSDR is used to represent the QoS Synchronization Delay Report.

[0146] In some embodiments, the first configuration information is used to configure a trigger condition, which is used to trigger the terminal 101 to send synchronization information of at least two QoS flows to the network device 102.

[0147] In some embodiments, the synchronization information is synchronization information between two QoS flows in the same service.

[0148] In some embodiments, the synchronization information is synchronization information between two QoS flows in a synchronization relationship in the same service.

[0149] In some embodiments, having a synchronous relationship means occurring at the same time.

[0150] In some embodiments, having a synchronous relationship means that the interval between occurrence times is smaller than a set interval.

[0151] In some embodiments, different QoS flows having a synchronous relationship means that the time interval of corresponding data on the time axis is less than a set interval.

[0152] In one example, the setting interval is 1 millisecond.

[0153] In one example, the two QoS flows with a synchronization relationship in the same service are an audio data flow and a haptic data flow in the same virtual reality service.

[0154] In one example, the two QoS flows with a synchronization relationship in the same service are a video data flow and a haptic data flow in the same virtual reality service.

[0155] In some embodiments, the first configuration information includes: identifiers of at least two QoS flows and at least one threshold.

[0156] In some embodiments, the first configuration information includes: identifiers of two QoS flows and a threshold.

[0157] In some embodiments, a threshold in the first configuration information may be a symmetric threshold.

[0158] The symmetric threshold can be used to determine whether the time difference between the data of QoS flow A and the data of QoS flow B meets the trigger condition, and can also be used to determine whether the time difference between the data of QoS flow B and the data of QoS flow A meets the trigger condition.

[0159] In some embodiments, the time difference may be referred to as a QoS flow synchronization delay.

[0160] In some embodiments, in the IE QSDR-Config, the field qfi-Pair is used to indicate the first QoS flow and the second QoS flow, and the field delayThreshold1 is used to indicate the one threshold. When the IE QSDR-Config includes only the field delayThreshold1 and does not include the field delayThreshold2, it indicates that the first configuration information includes only one threshold, that is, the threshold is a symmetric threshold.

[0161] In some embodiments, the first configuration information includes: identifiers of two QoS flows and two thresholds.

[0162] In some embodiments, the two thresholds in the second configuration information may be asymmetric thresholds.

[0163] One of the two thresholds is used to determine whether the time difference between the data of QoS flow A and the data of QoS flow B meets the trigger condition;

[0164] The other threshold value of the two threshold values ​​is used to determine whether a time difference between the lag of the data of QoS flow B and the data of QoS flow A satisfies a trigger condition.

[0165] In some embodiments, in the IE QSDR-Config, the qfi-Pair field is used to indicate the first QoS flow and the second QoS flow, the delayThreshold1 field is used to indicate the first threshold, and the delayThreshold2 field is used to indicate the second threshold. The delayThreshold1 and delayThreshold2 fields are asymmetric thresholds. For example, delayThreshold1 indicates the time difference threshold by which QoS flow (qfi1) lags behind QoS flow (qfi2), while delayThreshold2 indicates the time difference threshold by which QoS flow (qfi2) lags behind QoS flow (qfi1).

[0166] In some embodiments, the first configuration information includes: identifiers of at least three QoS flows and at least one threshold, wherein each threshold corresponds to a time difference of data between two QoS flows.

[0167] In some embodiments, the ranking of the plurality of thresholds is related to the ranking of the identifications of the plurality of QoS flows.

[0168] In some embodiments, the identifiers of the two QoS flows corresponding to the threshold are determined based on the following parameters:

[0169] the position of the threshold value in the ranking of the at least one threshold value;

[0170] the number of identifiers of the at least three QoS flows;

[0171] The identifications of the at least three QoS flows are sequenced.

[0172] In some embodiments, the order of the multiple thresholds corresponds to the order of the identifiers of the multiple QoS flows according to a set rule.

[0173] In one example, the first configuration information includes three identifiers and three thresholds, the three identifiers being: QFI1, QFI2, and QFI3, and the three thresholds being: Th1, Th2, and Th3.

[0174] The first threshold Th1 corresponds to the threshold between QFI1 and QFI2;

[0175] The second threshold Th2 corresponds to the threshold between QFI1 and QFI3;

[0176] The third threshold Th2 corresponds to a threshold between QFI2 and QFI3.

[0177] In one example, the first configuration information includes four identifiers and six thresholds, the four identifiers being: QFI1, QFI2, QFI3, and QFI4, and the six thresholds being: Th1, Th2, Th3, Th4, Th5, and Th6.

[0178] The first threshold Th1 corresponds to the synchronization threshold between QFI1 and QFI2;

[0179] The second threshold Th2 corresponds to the synchronization threshold between QFI1 and QFI3;

[0180] The third threshold Th3 corresponds to the synchronization threshold between QFI1 and QFI4;

[0181] The fourth threshold Th4 corresponds to the synchronization threshold between QFI2 and QFI3;

[0182] The fifth threshold Th5 corresponds to the synchronization threshold between QFI2 and QFI4;

[0183] The sixth threshold Th6 corresponds to the synchronization threshold between QFI3 and QFI4.

[0184] In some embodiments, the first configuration information is further used to configure enabling indication information, where the enabling indication information is used to indicate an enabling trigger condition.

[0185] In some embodiments, enabling refers to adding or changing.

[0186] In one example, the field qsdr-ConfigToAddModList is used to add or change trigger conditions.

[0187] In this example, when the suffix of qsdr-ConfigToAddModList is r19, it indicates that it was introduced in 3GPP Rel-19.

[0188] In some embodiments, the first configuration information is further used to configure a trigger condition and a disable indication, where the disable indication is used to indicate disabling of the trigger condition.

[0189] In some embodiments, disabling refers to deleting.

[0190] In one example, the field qsdr-ConfigToReleaseList is used to delete the trigger condition, that is, the QFI-Pair contained therein will no longer trigger related reports.

[0191] Step S2102: The network device sends second configuration information to the terminal.

[0192] In some embodiments, the network device 102 sends Radio Resource Control (RRC) information to the terminal 101, where the RRC information includes second configuration information.

[0193] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, where the RRC configuration information includes second configuration information.

[0194] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, and the IE CellGroupConfig in the RRC configuration information includes the second configuration information.

[0195] In some embodiments, the second configuration information is used to configure the duration of the timer.

[0196] In some embodiments, the timer is used to disable a trigger condition related to at least one QoS flow, wherein the terminal has sent synchronization information between the at least one QoS flow and other QoS flows within a first time period before the current moment.

[0197] In some embodiments, the granularity corresponding to the timer can be QoS flow, DRB, LCG, MAC entity or terminal.

[0198] In one example, the timer's granularity is QoS flow, and the timer is used to disable trigger conditions related to QoS 1. After the terminal reports synchronization information for QoS 1 relative to other QoSs, the timer can be started. While the timer is running, the terminal no longer reports synchronization information for QoS 1 relative to any other QoSs.

[0199] In one example, the granularity of the timer is DRB, and the timer is used to disable trigger conditions related to DRB1. After the terminal reports synchronization information of a QoS with respect to other QoS included in DRB1, the timer can be started. While the timer is running, the terminal no longer reports synchronization information of any QoS with respect to any other QoS in DRB1.

[0200] In one example, the granularity of the timer is LCG, and the timer is used to disable trigger conditions related to LCG1. After the terminal reports synchronization information of a QoS with respect to other QoS included in LCG1, the timer can be started. During the timer's operation, the terminal no longer reports synchronization information of any QoS with respect to any other QoS in LCG1.

[0201] Step S2103: The terminal determines the time difference.

[0202] In some embodiments, the terminal determines the time difference between different QoS flows indicated in the first configuration information.

[0203] In one example, the first configuration information includes an identifier of the first QoS flow, an identifier of the second QoS flow, and a threshold, and the terminal determines a time difference between the first QoS flow and the second QoS flow.

[0204] In some embodiments, the time difference between different QoS flows is determined according to whether data of the QoS flow is sent to the media access control MAC layer.

[0205] In some embodiments, first data of one QoS flow of two QoS flows has been completely sent to the MAC layer, second data of the other QoS flow of the two QoS flows has not been completely sent to the MAC layer, the first data corresponds to the second data, and the time difference between the two QoS flows is:

[0206] The difference between the current time and the time when the first data of one of the two QoS flows is completely sent to the MAC layer;

[0207] Alternatively, the difference between the current time and the time when the first data in one of the two QoS flows is sent over the air interface.

[0208] In some embodiments, the first data corresponds to the second data, which means that the first data and the second data are in a synchronous relationship.

[0209] For example, a video frame corresponds to a first QoS flow and a second QoS flow. The first data in the first QoS flow is a frame of audio data within the video frame, and the second data in the second QoS flow is a frame of image data within the video frame. If the first data in the first QoS flow has been completely sent to the MAC layer, but the second data in the second QoS flow has not been sent to the MAC layer, the time difference between the first QoS flow and the second QoS flow is determined as the difference between the current time and the time when the first data in the first QoS flow was completely sent to the MAC layer.

[0210] In some embodiments, the first data, as part of a first QoS flow, may be located within a DRB and may be located within an LCG.

[0211] Similarly, the second data, as part of the second QoS flow, can be located in a DRB and can be located in an LCG.

[0212] In some embodiments, the time difference between the two QoS flows is determined based on feedback information, where the feedback information is used to indicate whether data of the QoS flows is successfully received.

[0213] In some embodiments, the feedback information includes at least one of the following:

[0214] Hybrid Automatic Repeat request-ACKnowledgment (HARQ-ACK) feedback information;

[0215] Radio Link Control Acknowledged Mode (RLC AM) status report;

[0216] Packet Data Convergence Protocol (PDCP) status report.

[0217] Step S2104: The terminal determines whether a trigger condition is met.

[0218] In some embodiments, when the first configuration information includes identifiers of two QoS flows and a threshold, the trigger condition being satisfied includes one of the following:

[0219] The time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to the threshold;

[0220] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the threshold;

[0221] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0222] In some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes one of the following:

[0223] A time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to one of the two thresholds;

[0224] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the other threshold value of the two threshold values;

[0225] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0226] In some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes at least one of the following:

[0227] The time difference between the data of the third QoS flow and the data of the fourth QoS flow is greater than or equal to the first threshold value of the two threshold values.

[0228] The time difference between the data of the fourth QoS flow and the data of the third QoS flow is greater than or equal to the second threshold of the two thresholds;

[0229] The third QoS flow is the one with the smallest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows, and the fourth QoS flow is the one with the largest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows.

[0230] In some embodiments, when the first configuration information includes identifiers of at least three QoS flows and at least one threshold, each threshold corresponds to a time difference between data of two QoS flows.

[0231] In some embodiments, the identifiers of the two QoS flows corresponding to the threshold are determined based on the following parameters:

[0232] the position of the threshold value in the ranking of the at least one threshold value;

[0233] the number of identifiers of the at least three QoS flows;

[0234] The identifications of the at least three QoS flows are sequenced.

[0235] In some embodiments, satisfying the trigger condition includes: a time difference between any two QoS flows among the three QoS flows corresponding to the identifiers of the at least three QoS flows is greater than or equal to a threshold corresponding to the any two QoS flows.

[0236] Step S2105 , the terminal 101 sends synchronization information to the network device 102 .

[0237] In some embodiments, the synchronization information may be referred to as stream synchronization time difference information.

[0238] In some embodiments, when a trigger condition is met, the terminal sends synchronization information to the network device.

[0239] In some embodiments, when a trigger condition is met, the terminal sends synchronization information corresponding to the QoS flow that meets the trigger condition to the network device.

[0240] In some embodiments, the terminal 101 sends synchronization information to the network device 102 based on the granularity of QoS flow.

[0241] In some embodiments, the terminal 101 sends synchronization information corresponding to the QoS flow that meets the trigger condition to the network device 102 based on the granularity of the QoS flow.

[0242] In some embodiments, when the terminal 101 sends synchronization information to the network device 102 at the granularity of QoS flow, the synchronization information includes:

[0243] Identification of the QoS flow that meets the triggering conditions;

[0244] Time difference information between QoS flows that meet the trigger conditions.

[0245] In some embodiments, the QoS flow identifier can be an absolute value of the QFI or a relative index, i.e., an index of the QFIs of all QoS flows configured with synchronization information reporting arranged in order (ascending or descending). The QoS flow configured with synchronization information reporting is the QoS flow indicated by the first configuration information.

[0246] In some embodiments, the synchronization information may further include: the data volume of the QoS flow that meets the trigger condition.

[0247] In some embodiments, the terminal 101 sends synchronization information to the network device 102 at a DRB granularity.

[0248] In some embodiments, the terminal 101 sends synchronization information corresponding to the QoS flow that meets the trigger condition to the network device 102 at a DRB granularity.

[0249] In some embodiments, when the terminal 101 sends synchronization information to the network device 102 at a data radio bearer (DRB) granularity, the synchronization information includes:

[0250] The identifier of the DRB, where the DRB contains the QoS flow that meets the triggering condition;

[0251] Time difference information between QoS flows that meet the trigger conditions.

[0252] In some embodiments, the DRB identifier can be a DRB identifier or a relative index, that is, an index in which the DRB identifiers of all DRBs configured for synchronization information reporting are arranged in order (ascending or descending), or a bitmap is used to indicate which DRBs among all DRBs configured for synchronization information reporting need to report the flow synchronization time difference.

[0253] In some embodiments, the synchronization information may also include: the data volume of the QoS flow that meets the trigger condition within the DRB.

[0254] In some embodiments, the terminal 101 sends synchronization information to the network device 102 at a granularity of a logical channel group (LCG).

[0255] In some embodiments, the terminal 101 sends synchronization information corresponding to the QoS flow that meets the trigger condition to the network device 102 at the LCG granularity.

[0256] In some embodiments, when the terminal 101 sends synchronization information to the network device 102 at the LCG granularity, the synchronization information includes at least one of the following:

[0257] The identifier of the LCG, where the LCG contains the QoS flow that meets the trigger condition;

[0258] Time difference information between QoS flows that meet the trigger conditions;

[0259] In some embodiments, the LCG identifier can be an LCG identifier or a relative index, that is, an index in which the LCG identifiers of all LCGs configured for synchronization information reporting are arranged in order (ascending or descending), or a bitmap is used to indicate which of all LCGs configured for synchronization information reporting need to report flow synchronization information.

[0260] In some embodiments, the synchronization information may further include: the data volume of the QoS flow that meets the trigger condition within the LCG.

[0261] In some embodiments, the time difference information included in the synchronization information is the time difference between the different QoS flows.

[0262] In one example, the time difference is a specific value of the time delay.

[0263] In some embodiments, the time difference information included in the synchronization information is time difference related information.

[0264] In one example, the time difference related information is a difference between the time difference and a corresponding threshold value.

[0265] In some embodiments, when the time difference between multiple pairs of QoS flows meets the trigger condition, terminal 101 sends synchronization information corresponding to one pair of QoS flows to network device 102, or terminal 101 sends synchronization information corresponding to multiple pairs of QoS flows to network device 102.

[0266] In some embodiments, when the time difference between multiple pairs of QoS flows meets the trigger condition, the synchronization information includes a time difference information, which is calculated based on multiple time differences, and the multiple time differences are the time differences between multiple pairs of QoS flows that meet the trigger condition.

[0267] In an example, the piece of time difference information is a maximum value, a minimum value, an average value, or a middle value (ie, a median) of the multiple time differences.

[0268] In some embodiments, when the time difference between multiple pairs of QoS flows meets a trigger condition, the synchronization information includes multiple time difference information and multiple data amounts corresponding to the time difference information, and the data amounts are related to the multiple time difference information.

[0269] In one example, the synchronization information reported by the UE includes time difference 1 and time difference 2, as well as data amount 1 and data amount 2. Data amount 1 may correspond to the data amount for which the time difference satisfies the relationship "time difference 1 ≤ time difference < time difference 2", and data amount 2 may correspond to the data amount for which the time difference satisfies the relationship "time difference ≥ time difference 2".

[0270] In some embodiments, the terminal 101 sends RRC signaling to the network device 102, where the RRC signaling includes the synchronization information.

[0271] In some embodiments, the terminal 101 sends a media access control (MAC CE) control element (CE) to the network device 102, where the MAC CE includes the synchronization information.

[0272] In some embodiments, the MAC CE including synchronization information is called a flow synchronization time difference MAC CE.

[0273] In some embodiments, a new logical channel identifier (LCID) is indicated in the MAC header corresponding to the MAC CE, and the new LCID is used to indicate that the MAC CE is used to send the synchronization information.

[0274] In some embodiments, the MAC header corresponding to the MAC CE includes a new field, and the new field is used to indicate that the MAC CE is used to send the synchronization information.

[0275] In one example, this field occupies one byte.

[0276] In some embodiments, the MAC header corresponding to the MAC CE includes a new eLCID, and the new eLCID is used to indicate that the MAC CE is used to send the synchronization information.

[0277] In one example, the new eLCID occupies one byte.

[0278] In some embodiments, the terminal 101 determines the priority of the MAC CE in the logical channel priority processing according to the protocol agreement.

[0279] In one example, the priority of the MAC CE in the logical channel priority processing is the same as the priority of the MAC of the delay status report.

[0280] In some embodiments, when a trigger condition is met, the terminal 101 generates a report and sends the generated report to the network device 102. The report includes the synchronization information.

[0281] In some embodiments, when a trigger condition is met, the terminal 101 generates a report, marks the report as pending, and sends the pending report that has not been canceled to the network device.

[0282] In some embodiments, sending of a generated report is canceled when at least one of the following conditions is met:

[0283] The service data unit SDU associated with the report has been discarded;

[0284] A MAC PDU is transmitted, wherein the MAC PDU includes an SDU associated with the report;

[0285] A MAC PDU includes a MAC CE for transmitting the synchronization information, and the MAC CE includes an SDU related to the report.

[0286] In some embodiments, when encapsulating a MAC PDU, the terminal includes only one MAC CE including synchronization information in one MAC PDU.

[0287] In some embodiments, when encapsulating a MAC PDU, the terminal includes only one MAC CE including the flow synchronization time difference in one MAC PDU.

[0288] In some embodiments, when one MAC PDU is capable of transporting all SDUs associated with a pending report, the MAC entity may not include a MAC CE including synchronization information in the MAC PDU.

[0289] In some embodiments, when one MAC PDU is capable of transporting all SDUs associated with a pending report, the MAC entity may not include the Stream Synchronization Time Difference MAC CE in the MAC PDU.

[0290] In some embodiments, when there is at least one report that has been generated and not sent, if there is an uplink shared channel UL-SCH for transmitting new data, and the UL-SCH is capable of transmitting the MAC CE after running the logical channel priority processing LCP, the terminal generates the MAC CE; if the UL-SCH does not exist and the current processing flow does not include a pending scheduling request triggered by the logical channel corresponding to the report, a scheduling request is triggered.

[0291] In some embodiments, the format of the MAC CE including synchronization information is shown in Table 1.

[0292] Table 1

[0293] As shown in Table 1, the reporting granularity corresponding to MAC CE is LCG. The field definitions are as follows:

[0294] LCG field: When the specific value of the LCG field is 1, it indicates that the stream synchronization time difference information of the LCG is reported. When the specific value of the LCG field is 0, it indicates that the stream synchronization time difference information of the LCG is not reported.

[0295] QoS Flow Synchronization Delay: This field indicates the QoS Flow Synchronization Delay associated with the PDCP SDU corresponding to the LCG at the first symbol of the first PUSCH transmission of the MAC CE containing this QoS Flow Synchronization Delay. If multiple reports meet the triggering conditions and the corresponding delays are different, the value of this field is as described above (e.g., the maximum value). This field can be 6 bits in length or any other length.

[0296] BT field: This field appears only when the corresponding LCG is configured as additionalBSR-TableAllowed; otherwise, this field is reserved, meaning the network device can ignore it. If the BT field exists, a value of 1 indicates that the buffer size specified in 3GPP TS 38.321 Table 6.1.3.1-3 is used to set the buffer size field value. A value of 0 indicates that the buffer size specified in 3GPP TS 38.321 Table 6.1.3.1-2 is used.

[0297] Buffer Capacity Field: This field indicates the total amount of data in the LCG that meets the trigger conditions after the MAC PDU is constructed. If the corresponding LCG is configured with additionalBSR-TableAllowed and the total amount of data in the LCG that meets the trigger conditions is within the buffer size range specified in Table 6.1.3.1-3 of 3GPP TS 38.321, the MAC entity shall use the buffer size specified in Table 6.1.3.1-3 to set the value of this field; otherwise, the MAC entity shall use the value in Table 6.1.3.1-2 of 3GPP TS 38.321. This field is expressed in bytes. This field can be 8 bits long.

[0298] In some embodiments, the "Stream Sync Delay", "BT" and "Buffer Size" fields of an LCG shall be reported in two consecutive octets. These three fields shall be reported in different LCGs according to the LCG i Included in the Flow Synchronization Delay MAC CE in ascending order.

[0299] The method for sending synchronization information involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2105. For example, step S2105 may be implemented as an independent embodiment, steps S2101 and S2105 may be implemented as independent embodiments, and steps S2101, S2103, S2104, and S2105 may be implemented as independent embodiments, but are not limited thereto.

[0300] In some embodiments, any one or more of steps S2101 to S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, step S2102 may be omitted.

[0301] In some embodiments, the execution order of different steps may be changed.

[0302] In some embodiments, step S2101 and step S2102 can be combined into one step.

[0303] FIG2B is a flow chart of a method for sending synchronization information according to an embodiment of the present disclosure, which is applied to a terminal 101 and includes the following steps as shown in FIG2B :

[0304] Step S2201 : The network device 102 sends first configuration information and second configuration information to the terminal 101 .

[0305] In some embodiments, the network device 102 sends Radio Resource Control (RRC) information to the terminal 101, where the RRC information includes first configuration information and second configuration information.

[0306] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, where the RRC configuration information includes first configuration information and second configuration information.

[0307] In some embodiments, the network device 102 sends RRC configuration information (RRCReconfiguration) to the terminal 101, and the IE CellGroupConfig in the RRC configuration information includes first configuration information and second configuration information.

[0308] The optional implementation of step S2201 can refer to the optional implementation of step S2101 and step S2102 in Figure 2A, and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0309] In step S2202, the terminal 101 determines the time difference.

[0310] The optional implementation of step S2202 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0311] In step S2203, the terminal 101 determines whether a trigger condition is met.

[0312] The optional implementation of step S2203 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0313] Step S2204 , the terminal 101 sends synchronization information to the network device 102 .

[0314] The optional implementation of step S2204 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0315] The method for sending synchronization information involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2204. For example, step S2204 may be implemented as an independent embodiment, steps S2201 and S2204 may be implemented as independent embodiments, and steps S2201, S2203, and S2204 may be implemented as independent embodiments, but are not limited thereto.

[0316] In some embodiments, any one or more of steps S2201 to S2204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0317] FIG3A is a flow chart of a method for sending synchronization information according to an embodiment of the present disclosure, which is applied to a terminal 101 and includes the following steps as shown in FIG3A :

[0318] Step S3101: Receive first configuration information sent by the network device 102.

[0319] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0320] Step S3102 , receiving second configuration information sent by the network device 102 .

[0321] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0322] Step S3103, determine the time difference.

[0323] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0324] Step S3104, determine whether the trigger condition is met.

[0325] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0326] Step S3105 , sending synchronization information to the network device 102 .

[0327] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0328] The method for sending synchronization information involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3105. For example, step S3105 may be implemented as an independent embodiment, steps S3101 and S3105 may be implemented as independent embodiments, and steps S3101, S3103, S3104, and S3105 may be implemented as independent embodiments, but are not limited thereto.

[0329] In some embodiments, any one or more of steps S3101 to S3104 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, step S3102 may be omitted.

[0330] In some embodiments, the execution order of different steps may be changed.

[0331] FIG3B is a flow chart of a method for sending synchronization information according to an embodiment of the present disclosure, which is applied to the terminal 101 and includes the following steps as shown in FIG3B :

[0332] Step S3201: Receive first configuration information and second configuration information sent by the network device 102.

[0333] The optional implementation of step S3101 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0334] Step S3202, determine the time difference.

[0335] The optional implementation of step S3202 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0336] Step S3203: Determine whether the trigger condition is met.

[0337] The optional implementation of step S3203 can refer to the optional implementation of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0338] Step S3204: Send synchronization information to the network device 102.

[0339] The optional implementation of step S3204 can refer to the optional implementation of step S2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0340] The method for sending synchronization information involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step S3204 may be implemented as an independent embodiment, steps S3201 and S3204 may be implemented as independent embodiments, and steps S3201, S3203, and S3204 may be implemented as independent embodiments, but are not limited thereto.

[0341] In some embodiments, any one or more of steps S3201 to S3204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0342] FIG3C is a flow chart of a method for sending synchronization information according to an embodiment of the present disclosure, which is applied to the network device 102. As shown in FIG3C , the method includes the following steps:

[0343] Step S3301: Send first configuration information to terminal 101.

[0344] The optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0345] Step S3302: Send second configuration information to terminal 101.

[0346] The optional implementation of step S3302 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0347] Step S3303: Receive synchronization information sent by terminal 101.

[0348] The optional implementation of step S3303 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0349] The method for sending synchronization information involved in the embodiment of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3303 may be implemented as an independent embodiment, and steps S3301 and S3303 may be implemented as independent embodiments, but are not limited thereto.

[0350] In some embodiments, any one or more of steps S3301 to S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, step S3302 may be omitted.

[0351] In some embodiments, the execution order of different steps may be changed.

[0352] FIG3D is a flow chart of a method for sending synchronization information according to an embodiment of the present disclosure, which is applied to the network device 102. As shown in FIG3D , the method includes the following steps:

[0353] Step S3401: Send first configuration information and second configuration information to terminal 101.

[0354] The optional implementation of step S3401 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0355] Step S3402 , receiving synchronization information sent by terminal 101 .

[0356] The optional implementation of step S3402 can refer to the optional implementation of step S2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0357] The method for sending synchronization information involved in the embodiment of the present disclosure may include at least one of steps S3401 to S3402. For example, step S3402 may be implemented as an independent embodiment, but is not limited thereto.

[0358] In some embodiments, step S3401 may be omitted.

[0359] FIG4 is a flow chart of a method for establishing a connection according to an embodiment of the present disclosure. As shown in FIG4 , the method includes the following steps:

[0360] Step S4101: The network device 102 sends first configuration information to the terminal 101.

[0361] In some embodiments, the first configuration information is used to configure a trigger condition, wherein the trigger condition is used to trigger the terminal to send synchronization information of at least two QoS flows to the network device;

[0362] In some embodiments, the first configuration information includes: identifiers of at least two QoS flows and at least one threshold.

[0363] In some embodiments, the first configuration information includes identifiers of two QoS flows and a threshold.

[0364] In some embodiments, the first configuration information includes: an identifier of a first QoS flow, an identifier of a second QoS flow, and a threshold.

[0365] In some embodiments, the first configuration information includes: an identifier of a first QoS flow, an identifier of a second QoS flow, a first threshold, and a second threshold.

[0366] In some embodiments, the first configuration information includes identifications of at least three QoS flows and at least one threshold.

[0367] In some embodiments, the identifiers of the two QoS flows corresponding to the threshold are determined based on the following parameters:

[0368] the position of the threshold value in the ranking of the at least one threshold value;

[0369] the number of identifiers of the at least three QoS flows;

[0370] The identifications of the at least three QoS flows are sequenced.

[0371] Step S4102: When the trigger condition is met, the terminal 101 sends the synchronization information to the network device.

[0372] In some embodiments, when the first configuration information includes identifiers of two QoS flows and a threshold, satisfying the trigger condition includes one of the following:

[0373] The time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to the threshold;

[0374] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the threshold;

[0375] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0376] In some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes one of the following:

[0377] A time difference between the data of the first QoS flow and the data of the second QoS flow is greater than or equal to one of the two thresholds;

[0378] The time difference between the data of the second QoS flow and the data of the first QoS flow is greater than or equal to the other threshold value of the two threshold values;

[0379] The first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

[0380] In some embodiments, when the first configuration information includes identifiers of two QoS flows and two thresholds, satisfying the trigger condition includes at least one of the following:

[0381] The time difference between the data of the third QoS flow and the data of the fourth QoS flow is greater than or equal to the first threshold value of the two threshold values.

[0382] The time difference between the data of the fourth QoS flow and the data of the third QoS flow is greater than or equal to the second threshold of the two thresholds;

[0383] The third QoS flow is the one with the smallest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows, and the fourth QoS flow is the one with the largest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows.

[0384] In some embodiments, when the first configuration information includes identifiers of at least three QoS flows and at least one threshold, each threshold corresponds to a time difference between data of two QoS flows.

[0385] In some embodiments, the identifiers of the two QoS flows corresponding to the threshold are determined based on the following parameters:

[0386] the position of the threshold value in the ranking of the at least one threshold value;

[0387] the number of identifiers of the at least three QoS flows;

[0388] The identifications of the at least three QoS flows are sequenced.

[0389] In some embodiments, satisfying the trigger condition includes: a time difference between any two QoS flows among the three QoS flows corresponding to the identifiers of the at least three QoS flows is greater than or equal to a threshold corresponding to the any two QoS flows.

[0390] In some embodiments, the method further comprises:

[0391] determining a time difference between the different QoS flows according to whether data of the QoS flow is sent to a media access control MAC layer;

[0392] Alternatively, the time difference between the different QoS flows is determined according to feedback information, wherein the feedback information is used to indicate whether data of the QoS flow is successfully received.

[0393] In some embodiments, the first data of one QoS flow of the two QoS flows has been completely sent to the MAC layer, the second data of the other QoS flow of the two QoS flows has not been completely sent to the MAC layer, the first data corresponds to the second data, and the time difference between the two QoS flows is:

[0394] a difference between the current time and the time when all first data in one of the two QoS flows are sent to the MAC layer;

[0395] Alternatively, the time difference between the current time and the time at which the first data in one of the two QoS flows is sent over the air interface. In some embodiments, the time difference is determined based on feedback information, the feedback information being used to indicate whether the data of the QoS flow is successfully received, the feedback information including at least one of the following:

[0396] Hybrid Automatic Repeat Request Acknowledgement HARQ ACK feedback information;

[0397] Status report of Radio Link Layer Control Protocol Acknowledgement Mode RLC AM;

[0398] Packet Data Convergence Protocol PDCP status report.

[0399] In some embodiments, the synchronization information includes at least one of the following:

[0400] The identifier of the QoS flow that meets the trigger condition;

[0401] The time difference information between the QoS flows that meet the trigger condition;

[0402] The data volume of the QoS flow that meets the trigger condition.

[0403] In some embodiments, the synchronization information includes at least one of the following:

[0404] an identifier of a data radio bearer (DRB), wherein the DRB includes a QoS flow that satisfies the trigger condition;

[0405] The time difference information between the QoS flows that meet the trigger condition;

[0406] The data volume of the QoS flow that meets the trigger condition within the DRB.

[0407] In some embodiments, the synchronization information includes at least one of the following:

[0408] an identifier of a logical channel group LCG, wherein the LCG includes the QoS flows that meet the trigger condition;

[0409] The time difference information between the QoS flows that meet the trigger condition;

[0410] The data volume of the QoS flow that meets the trigger condition in the LCG.

[0411] In some embodiments, the time difference information is the time difference between the different QoS flows, or the time difference information is time difference related information, and the time difference related information is the difference between the time difference and a corresponding threshold.

[0412] In some embodiments, when the time difference between multiple pairs of QoS flows meets the trigger condition, the synchronization information includes a time difference information, which is calculated based on multiple time differences, and the multiple time differences are the time differences between multiple pairs of QoS flows that meet the trigger condition.

[0413] In some embodiments, when the time difference between multiple pairs of QoS flows meets the trigger condition, the synchronization information includes multiple time difference information and multiple data amounts corresponding to the time difference information, and the data amounts are related to the multiple time difference information.

[0414] In some embodiments, the first configuration information is further used to configure enabling indication information, and the enabling indication information is used to indicate enabling of the trigger condition.

[0415] In some embodiments, the first configuration information is further used to configure the trigger condition and a disable indication, and the disable indication is used to indicate disabling of the trigger condition.

[0416] In some embodiments, the method further comprises:

[0417] Receive second configuration information sent by the network device, where the second configuration information is used to configure the duration of a timer, and the timer is used to disable a trigger condition related to at least one QoS flow, wherein the terminal has sent synchronization information between the at least one QoS flow and other QoS flows within a first duration before the current moment.

[0418] In some embodiments, radio link control (RRC) signaling is sent, the RRC signaling including the synchronization information.

[0419] In some embodiments, a Medium Access Control Element (MAC CE) is sent, the MAC CE including the synchronization information.

[0420] In some embodiments, a new logical channel identifier LCID is indicated in the MAC header corresponding to the MAC CE, and the new LCID is used to indicate that the MAC CE is used to send the synchronization information.

[0421] In some embodiments, the MAC header corresponding to the MAC CE includes a new eLCID, and the new eLCID is used to indicate that the MAC CE is used to send the synchronization information.

[0422] In some embodiments, the method further comprises:

[0423] The priority of the MAC CE in the logical channel priority processing is determined according to the protocol agreement.

[0424] In some embodiments, when the trigger condition is met, sending the synchronization information to the network device includes:

[0425] generating a report when the trigger condition is met, the report including the synchronization information;

[0426] The generated report is sent to the network device.

[0427] In some embodiments, the method further comprises:

[0428] Cancel sending of the generated report if any of the following conditions are met:

[0429] The service data unit SDU associated with the report has been discarded;

[0430] A MAC PDU is transmitted, wherein the MAC PDU includes an SDU associated with the report;

[0431] A MAC PDU includes a MAC CE for transmitting the synchronization information, and the MAC CE includes an SDU related to the report.

[0432] In some embodiments, the method further comprises:

[0433] In the case that there is at least one report that has been generated and not sent, if there is an uplink shared channel UL-SCH for transmitting new data, and the UL-SCH is capable of transmitting the MAC CE after running the logical channel priority processing LCP, then the MAC CE is generated; if the UL-SCH does not exist and the current processing flow does not include a pending scheduling request triggered by the logical channel corresponding to the report, then a scheduling request is triggered.

[0434] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided that includes units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0435] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0436] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0437] Figure 5A is a structural diagram of a communication device according to an embodiment of the present disclosure, which is applied to a terminal 101. As shown in Figure 5A, the terminal 101 may include a transceiver module 5101. In some embodiments, the transceiver module 5101 is configured to: receive first configuration information sent by a network device, wherein the first configuration information is used to configure a trigger condition, wherein the trigger condition is used to trigger the terminal to send synchronization information of at least two QoS flows to the network device; and when the trigger condition is met, send synchronization information of at least two QoS flows to the network device. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0438] Figure 5B is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure, which is applied to a network device 102. As shown in Figure 5B, the network device 102 may include a transceiver module 5201. In some embodiments, the transceiver module 5201 is configured to: send first configuration information to a terminal, wherein the first configuration information is used to configure a trigger condition, wherein the trigger condition is used to trigger the terminal to send synchronization information of at least two QoS flows to the network device; and receive synchronization information of at least two quality of service QoS flows sent by the terminal. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the second device 102 in any of the above methods, which will not be repeated here.

[0439] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0440] Figure 6A is a schematic diagram of the structure of a communication device 6100 according to an embodiment of the present disclosure. Communication device 6100 can be a first device (e.g., a terminal, user equipment, IoT device, etc.), a second device (e.g., an intermediate node), or a third device (e.g., an access network device, a core network device, etc.). It can also be a chip, chip system, or processor that implements any of the above methods in a network device, or a chip, chip system, or processor that implements any of the above methods in a terminal. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0441] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. Processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The communication device 6100 is used to perform any of the above methods.

[0442] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may be located outside the communication device 6100.

[0443] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceiver 6103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps.

[0444] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0445] In some embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6102. The interface circuit 6104 may be configured to receive signals from the memory 6102 or other devices, and may be configured to send signals to the memory 6102 or other devices. For example, the interface circuit 6104 may read instructions stored in the memory 6102 and send the instructions to the processor 6101.

[0446] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (8) others, etc.

[0447] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6200 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.

[0448] The chip 6200 includes one or more processors 6201 , and the chip 6200 is configured to execute any of the above methods.

[0449] In some embodiments, the chip 6200 further includes one or more interface circuits 6202. Optionally, the interface circuit 6202 is connected to the memory 6203. The interface circuit 6202 can be used to receive signals from the memory 6203 or other devices, and can be used to send signals to the memory 6203 or other devices. For example, the interface circuit 6202 can read instructions stored in the memory 6203 and send the instructions to the processor 6201.

[0450] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6201 performs at least one of the other steps.

[0451] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0452] In some embodiments, the chip 6200 further includes one or more memories 6203 for storing instructions. Alternatively, all or part of the memories 6203 may be outside the chip 6200.

[0453] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0454] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0455] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods. Industrial Applicability

[0456] The timing for the terminal to report synchronization information is reasonable, which can save signaling overhead compared with the periodic reporting method.

Claims

1. A method for sending synchronization information, which is executed by a terminal. The method includes: Receiving first configuration information sent by a network device, where the first configuration information is used to configure a triggering condition, and the triggering condition is used to trigger the terminal to send synchronization information of at least two Quality of Service (QoS) flows to the network device; When the triggering condition is satisfied, sending synchronization information of at least two QoS flows to the network device.

2. The method according to claim 1, wherein The first configuration information includes: identifiers of at least two QoS flows and at least one threshold.

3. The method according to claim 2, wherein, When the first configuration information includes identifiers of two QoS flows and one threshold, the satisfaction of the triggering condition includes one of the following: The time difference between the data of the first QoS flow being later than the data of the second QoS flow is greater than or equal to the threshold; The time difference between the data of the second QoS flow being later than the data of the first QoS flow is greater than or equal to the threshold; Wherein, the first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

4. The method according to claim 2, wherein, When the first configuration information includes identifiers of two QoS flows and two thresholds, the satisfaction of the triggering condition includes one of the following: The time difference between the data of the first QoS flow being later than the data of the second QoS flow is greater than or equal to one of the two thresholds; The time difference between the data of the second QoS flow being later than the data of the first QoS flow is greater than or equal to the other of the two thresholds; Wherein, the first QoS flow and the second QoS flow are two QoS flows corresponding to the identifiers of the two QoS flows.

5. The method according to claim 2, wherein, When the first configuration information includes identifiers of two QoS flows and two thresholds, the satisfaction of the triggering condition includes at least one of the following: The time difference between the data of the third QoS flow being later than the data of the fourth QoS flow is greater than or equal to the first of the two thresholds, The time difference between the data of the fourth QoS flow being later than the data of the third QoS flow is greater than or equal to the second of the two thresholds; Wherein, the third QoS flow is the one with the smallest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows, and the fourth QoS flow is the one with the largest identifier among the two QoS flows corresponding to the identifiers of the two QoS flows.

6. The method according to claim 2, wherein, When the first configuration information includes identifiers of at least three QoS flows and at least one threshold, each threshold corresponds to the time difference between the data of two QoS flows.

7. The method according to claim 6, wherein, The identifiers of the two QoS flows corresponding to the threshold are determined according to the following parameters: The position of the threshold in the sorting of the at least one threshold; The number of the identifiers of the at least three QoS flows; The sorting of the identifiers of the at least three QoS flows.

8. The method according to claim 6, wherein, The satisfaction of the triggering condition includes: the time difference between any two of the three QoS flows corresponding to the identifiers of the at least three QoS flows is greater than or equal to the threshold corresponding to the two QoS flows.

9. The method according to any one of claims 6 to 8, wherein, The first data of one of the two QoS flows has been completely sent to the MAC layer, and the second data of the other QoS flow among the two QoS flows has not been completely sent to the MAC layer. The first data corresponds to the second data, and the time difference between the two QoS flows is: The difference between the current time and the time when the first data in one of the two QoS flows is completely sent to the MAC layer; Or, the difference between the current time and the time when the first data in one of the two QoS flows is sent over the air interface.

10. The method according to any one of claims 6 to 8, wherein, The time difference is determined according to feedback information, and the feedback information is used to indicate whether the data of the QoS flow is successfully received. The feedback information includes at least one of the following: Feedback information of Hybrid Automatic Repeat reQuest acknowledgement HARQ ACK; Status report of Radio Link Control protocol acknowledgement mode RLC AM; Packet Data Convergence Protocol PDCP status report.

11. The method according to any one of claims 1 to 10, wherein, The synchronization information includes at least one of the following: The identifier of the QoS flow that meets the trigger condition; The time difference information between the QoS flows that meet the trigger condition; The data volume of the QoS flow that meets the trigger condition.

12. The method according to any one of claims 1 to 10, wherein, The synchronization information includes at least one of the following: The identifier of the Data Radio Bearer DRB that contains the QoS flow that meets the trigger condition; The time difference information between the QoS flows that meet the trigger condition; The data volume of the QoS flow that meets the trigger condition within the DRB.

13. The method according to any one of claims 1 to 10, wherein, The synchronization information includes at least one of the following: The identifier of the Logical Channel Group LCG that contains the QoS flow that meets the trigger condition; The time difference information between the QoS flows that meet the trigger condition; The data volume of the QoS flow that meets the trigger condition within the LCG.

14. The method according to any one of claims 11 to 13, wherein, The time difference information is the value of the time difference between the QoS flows that meet the trigger condition, or the time difference information is time difference related information, and the time difference related information is the difference between the time difference and the corresponding threshold.

15. The method according to any one of claims 11 to 13, wherein, The synchronization information includes one time difference information, and the one time difference information is calculated based on multiple time differences.

16. The method according to any one of claims 11 to 13, wherein, The synchronization information includes multiple time difference information and multiple data volumes corresponding to the time difference information.

17. The method according to any one of claims 1 to 16, wherein, The first configuration information is further used to configure an enable indication information, and the enable indication information is used to indicate enabling the trigger condition.

18. The method according to any one of claims 1 to 16, wherein, The first configuration information is further used to configure the trigger condition and a disable indication, and the disable indication is used to indicate disabling the trigger condition.

19. The method according to any one of claims 1 to 18, wherein The method further includes: Receiving second configuration information sent by the network device, where the second configuration information is used to configure the duration of a timer, and the timer is used to disable the trigger condition related to at least one QoS flow, where the terminal has sent the synchronization information of the at least one QoS flow and other QoS flows within a first duration before the current moment.

20. The method according to any one of claims 1 to 19, wherein, Sending the synchronization information of the at least two Quality of Service QoS flows to the network device includes: Send Radio Resource Control (RRC) signaling, where the RRC signaling includes synchronization information of the at least two Quality of Service (QoS) flows.

21. The method according to any one of claims 1 to 19, wherein, The sending of the synchronization information of the at least two QoS flows to the network device includes: Sending a Medium Access Control Element (MAC CE), where the MAC CE includes the synchronization information of the at least two QoS flows.

22. The method according to claim 21, wherein Indicate a new Logical Channel ID (LCID) in the MAC header corresponding to the MAC CE, where the new LCID is used to indicate that the MAC CE is used to send the synchronization information of the at least two QoS flows.

23. The method according to claim 22, wherein, The MAC header corresponding to the MAC CE includes a new extended LCID (eLCID), where the new eLCID is used to indicate that the MAC CE is used to send the synchronization information of the at least two QoS flows.

24. The method according to claim 21, wherein, The method further includes: Determine the priority of the MAC CE in the logical channel priority handling according to protocol agreements.

25. The method according to any one of claims 1 to 24, wherein, The sending of the synchronization information of the at least two QoS flows to the network device when the trigger condition is met includes: Generate a report including the synchronization information of the at least two QoS flows when the trigger condition is met; Send the generated report to the network device.

26. The method according to claim 25, wherein, The method further includes: Cancel sending the generated report when one of the following conditions is met: The Service Data Unit (SDU) related to the report has been discarded; A MAC Protocol Data Unit (PDU) is transmitted and the MAC PDU contains the SDU related to the report; A MAC PDU includes a MAC CE for transmitting the synchronization information, and the MAC CE contains the SDU related to the report.

27. The method according to claim 21, wherein, The method further includes: In the case where there is at least one generated and unsent report, if there is an Uplink Shared Channel (UL-SCH) for transmitting new data and the UL-SCH can transmit the MAC CE after running the Logical Channel Priority (LCP) handling, generate the MAC CE; if there is no UL-SCH and the current processing flow does not include a pending scheduling request triggered by the logical channel corresponding to the report, trigger a scheduling request.

28. A method for receiving synchronization information, executed by a network device, the method includes: Send first configuration information to a terminal, where the first configuration information is used to configure a trigger condition for triggering the terminal to send synchronization information of at least two QoS flows to the network device; Receive the synchronization information of the at least two QoS flows sent by the terminal.

29. The method according to claim 28, wherein, The first configuration information is further used to configure enabling indication information for indicating enabling the trigger condition.

30. The method according to claim 28, wherein, The first configuration information is further used to configure the trigger condition and a disabling indication for indicating disabling the trigger condition.

31. The method according to any one of claims 28 to 30, wherein, The method further includes: Send second configuration information to the terminal, where the second configuration information is used to configure the duration of a timer, and the timer is used to disable a triggering condition related to at least one QoS flow.

32. The method according to any one of claims 28 to 31, wherein, The receiving the synchronization information of at least two Quality of Service (QoS) flows sent by the terminal includes: Receiving Radio Resource Control (RRC) signaling, where the RRC signaling includes the synchronization information of the at least two QoS flows.

33. The method according to any one of claims 28 to 32, wherein, The receiving the synchronization information sent by the terminal includes: Receiving a Medium Access Control Element (MAC CE), where the MAC CE includes the synchronization information of the at least two QoS flows.

34. A communication device, configured in a terminal, the device includes: A transceiver module, configured to: Receive first configuration information sent by a network device, where the first configuration information is used to configure a triggering condition, and the triggering condition is used to trigger the terminal to send synchronization information of at least two QoS flows to the network device; Send synchronization information of at least two QoS flows to the network device when the triggering condition is met.

35. A communication device, configured in a network device, the device includes: A transceiver module, configured to: send first configuration information to a terminal, where the first configuration information is used to configure a triggering condition, and the triggering condition is used to trigger the terminal to send synchronization information of at least two QoS flows to the network device; And Receive the synchronization information of at least two QoS flows sent by the terminal.

36. A communication device, including a processor and a memory, where The memory is used to store a computer program; The processor is used to execute the computer program to implement the method according to any one of claims 1-27.

37. A computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are called and executed by a processor, the processor is caused to execute the method according to any one of claims 1-27.

Images