Information triggering method and device, information transmission method and device, terminal and network equipment

Abstract

The invention provides an information triggering and transmitting method and device, a terminal and network equipment, and the method is executed by a first terminal and comprises the steps: triggering a synchronous time delay state report which is used for indicating the synchronous time delay state of a related flow; wherein the correlation flow comprises one or more of the following items: the flows borne by different QoS flows, and the correlation between the flows is indicated by the correlation between QoS flow IDs (Identity); the streams are carried by different DRBs, and the correlation between the streams is indicated by the correlation between DRB IDs; and the flow is carried by different logical channels, and the correlation between the flows is indicated by the correlation between the LCIDs. According to the scheme, by triggering the synchronous delay state report used for indicating the synchronous delay state of the related flow, the network side is assisted to obtain the transmission and residual synchronous delay information of the related flow, so that the network side can conveniently schedule the data of the related flow in time, and the synchronous transmission of the related flow is ensured.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information triggering, transmission method, device, terminal and network equipment. Background Art

[0002] Currently, QoS parameters are only set for a single flow (from the perspective of the access network, that is, a Quality of Service (QoS) flow), and QoS guarantee is performed during the transmission process.

[0003] Since the late stage of 5G research, Extended Reality (XR) services have been introduced, and XR services are expected to become the killer application of 6G. XR services can be applied to one or more user devices, such as 3D glasses, handle remote controls, etc. There are two basic ways for XR services to connect to wireless networks. One is that all user devices are connected to a user equipment (UE), and XR services access the network through the terminal; the other is that different user devices access the network as different terminals. The way in which different service flows of XR services come from or go to different user devices is called multimodal communication.

[0004] How to ensure the synchronous transmission requirements between different QoS flows of the same XR service is an urgent problem to be solved. Summary of the invention

[0005] The embodiments of the present application provide an information triggering and transmission method, apparatus, terminal and network equipment to achieve synchronous transmission between different QoS flows.

[0006] In order to solve the above technical problem, an embodiment of the present application provides an information triggering method, which is executed by a first terminal and includes:

[0007] Triggering a synchronization delay status report, where the synchronization delay status report is used to indicate a synchronization delay status of a related stream;

[0008] The related streams include one or more of the following:

[0009] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0010] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0011] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0012] Optionally, the related streams are all sent through the first terminal, and the triggering of the synchronization delay status report includes:

[0013] When the first condition is met, triggering the synchronization delay status report;

[0014] The first condition includes at least one of the following:

[0015] After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold;

[0016] After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent;

[0017] When data of the first target stream in the related stream is sent;

[0018] Data of a first target stream in the related streams arrives at the cache;

[0019] The data of the second target flow in the related flow arrives at the cache;

[0020] receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report;

[0021] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0022] Optionally, the first request message includes at least one of the following:

[0023] A group identifier of the related stream;

[0024] The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

[0025] Optionally, the relevant stream is sent through the first terminal and at least one second terminal, and the triggering of the synchronization delay status report includes:

[0026] When the second condition is met, triggering the synchronization delay status report;

[0027] The second condition includes at least one of the following:

[0028] When data of the related stream in the first terminal is sent;

[0029] The data of the related flow in the first terminal arrives at a cache;

[0030] A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

[0031] Optionally, the second request message includes at least one of the following:

[0032] A group identifier of the related stream;

[0033] The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow;

[0034] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0035] Optionally, the triggering of the synchronization delay status report includes:

[0036] After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report;

[0037] The third condition includes at least one of the following:

[0038] A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent;

[0039] The second target stream in the related stream starts to be sent;

[0040] A PDU of a second target flow in the related flow is sent successfully;

[0041] A PDU set of a second target flow in the related flow is sent successfully;

[0042] The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold;

[0043] The first terminal has sent the synchronization delay status report to the network device;

[0044] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0045] Optionally, after triggering the synchronization delay status report, the method further includes:

[0046] When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report;

[0047] The first message includes at least one of the following:

[0048] Radio Resource Control (RRC) signaling;

[0049] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0050] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0051] Radio link control protocol data unit RLC control PDU;

[0052] Media access control element MAC CE;

[0053] Physical layer signaling.

[0054] Optionally, the method further includes:

[0055] Receiving configuration information of the relevant flow sent by a network device or a core network device;

[0056] The configuration information includes at least one of the following:

[0057] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0058] The synchronization threshold of the related stream.

[0059] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0060] The relationship between business flows;

[0061] The relationship between Internet Protocol flows;

[0062] The relationship between QoS flows;

[0063] The association relationship between data radio bearers (DRBs);

[0064] The association relationship between logical channels LCH.

[0065] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0066] a QoS flow, a DRB or a logical channel carrying the related flow;

[0067] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0068] The target information includes at least one of the following:

[0069] an identifier of the at least one second terminal;

[0070] The QoS flow, DRB or logical channel of the at least one second terminal.

[0071] Optionally, the synchronization delay status report includes at least one of the following:

[0072] Time information of synchronization delay;

[0073] Buffer Status Report BSR related to the time information of synchronization delay;

[0074] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0075] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0076] The embodiment of the present application also provides an information acquisition method, which is executed by a network device and includes:

[0077] Receiving a synchronization delay status report reported by the first terminal;

[0078] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0079] The relevant streams include one or more of the following:

[0080] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0081] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0082] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0083] Optionally, the receiving a synchronization delay status report reported by the first terminal includes:

[0084] Receiving a first message sent by a first terminal, where the first message carries the synchronization delay status report;

[0085] The first message includes at least one of the following:

[0086] Radio Resource Control (RRC) signaling;

[0087] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0088] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0089] Radio link control protocol data unit RLC control PDU;

[0090] Media access control element MAC CE;

[0091] Physical layer signaling.

[0092] Optionally, the method further includes:

[0093] Sending configuration information of the relevant flow to the first terminal;

[0094] The configuration information includes at least one of the following:

[0095] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0096] The synchronization threshold of the related stream.

[0097] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0098] The relationship between business flows;

[0099] The relationship between Internet Protocol flows;

[0100] The relationship between QoS flows;

[0101] The association relationship between data radio bearers (DRBs);

[0102] The association relationship between logical channels LCH.

[0103] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0104] a QoS flow, a DRB or a logical channel carrying the related flow;

[0105] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0106] The target information includes at least one of the following:

[0107] an identifier of the at least one second terminal;

[0108] The QoS flow, DRB or logical channel of the at least one second terminal.

[0109] Optionally, the synchronization delay status report includes at least one of the following:

[0110] Time information of synchronization delay;

[0111] Buffer Status Report BSR related to the time information of synchronization delay;

[0112] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0113] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0114] The embodiment of the present application further provides a terminal, which is a first terminal and includes a memory, a transceiver, and a processor:

[0115] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0116] Triggering a synchronization delay status report, where the synchronization delay status report is used to indicate a synchronization delay status of a related stream;

[0117] The related streams include one or more of the following:

[0118] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0119] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0120] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0121] Optionally, the related streams are all sent through the first terminal, and the processor is configured to read a computer program in the memory and perform the following operations:

[0122] When the first condition is met, triggering the synchronization delay status report;

[0123] The first condition includes at least one of the following:

[0124] After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold;

[0125] After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent;

[0126] When data of the first target stream in the related stream is sent;

[0127] Data of a first target stream in the related streams arrives at the cache;

[0128] The data of the second target flow in the related flow arrives at the cache;

[0129] receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report;

[0130] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0131] Optionally, the first request message includes at least one of the following:

[0132] A group identifier of the related stream;

[0133] The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

[0134] Optionally, the relevant stream is sent through the first terminal and at least one second terminal, and the processor is configured to read the computer program in the memory and perform the following operations:

[0135] When the second condition is met, triggering the synchronization delay status report;

[0136] The second condition includes at least one of the following:

[0137] When data of the related stream in the first terminal is sent;

[0138] The data of the related flow in the first terminal arrives at a cache;

[0139] A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

[0140] Optionally, the second request message includes at least one of the following:

[0141] A group identifier of the related stream;

[0142] The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow;

[0143] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0144] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0145] After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report;

[0146] The third condition includes at least one of the following:

[0147] A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent;

[0148] The second target stream in the related stream starts to be sent;

[0149] A PDU of a second target flow in the related flow is sent successfully;

[0150] A PDU set of a second target flow in the related flow is sent successfully;

[0151] The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold;

[0152] The first terminal has sent the synchronization delay status report to the network device;

[0153] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0154] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0155] When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report;

[0156] The first message includes at least one of the following:

[0157] Radio Resource Control (RRC) signaling;

[0158] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0159] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0160] Radio link control protocol data unit RLC control PDU;

[0161] Media access control element MAC CE;

[0162] Physical layer signaling.

[0163] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0164] Receiving, through a transceiver, configuration information of the related flow sent by a network device or a core network device;

[0165] The configuration information includes at least one of the following:

[0166] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0167] The synchronization threshold of the related stream.

[0168] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0169] The relationship between business flows;

[0170] The relationship between Internet Protocol flows;

[0171] The relationship between QoS flows;

[0172] The association relationship between data radio bearers (DRBs);

[0173] The association relationship between logical channels LCH.

[0174] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0175] a QoS flow, a DRB or a logical channel carrying the related flow;

[0176] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0177] The target information includes at least one of the following:

[0178] an identifier of the at least one second terminal;

[0179] The QoS flow, DRB or logical channel of the at least one second terminal.

[0180] Optionally, the synchronization delay status report includes at least one of the following:

[0181] Time information of synchronization delay;

[0182] Buffer Status Report BSR related to the time information of synchronization delay;

[0183] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0184] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0185] The embodiment of the present application also provides a network device, including a memory, a transceiver, and a processor:

[0186] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0187] Receiving, by a transceiver, a synchronization delay status report reported by the first terminal;

[0188] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0189] The relevant streams include one or more of the following:

[0190] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0191] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0192] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0193] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0194] Receiving, by a transceiver, a first message sent by a first terminal, wherein the first message carries the synchronization delay status report;

[0195] The first message includes at least one of the following:

[0196] Radio Resource Control (RRC) signaling;

[0197] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0198] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0199] Radio link control protocol data unit RLC control PDU;

[0200] Media access control element MAC CE;

[0201] Physical layer signaling.

[0202] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0203] Sending the configuration information of the related flow to the first terminal through a transceiver;

[0204] The configuration information includes at least one of the following:

[0205] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0206] The synchronization threshold of the related stream.

[0207] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0208] The relationship between business flows;

[0209] The relationship between Internet Protocol flows;

[0210] The relationship between QoS flows;

[0211] The association relationship between data radio bearers (DRBs);

[0212] The association relationship between logical channels LCH.

[0213] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0214] a QoS flow, a DRB or a logical channel carrying the related flow;

[0215] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0216] The target information includes at least one of the following:

[0217] an identifier of the at least one second terminal;

[0218] The QoS flow, DRB or logical channel of the at least one second terminal.

[0219] Optionally, the synchronization delay status report includes at least one of the following:

[0220] Time information of synchronization delay;

[0221] Buffer Status Report BSR related to the time information of synchronization delay;

[0222] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0223] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0224] The embodiment of the present application further provides an information triggering device, applied to a first terminal, including:

[0225] A triggering unit, used to trigger a synchronization delay status report, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related stream;

[0226] The related streams include one or more of the following:

[0227] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0228] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0229] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0230] The embodiment of the present application also provides an information acquisition device, which is applied to a network device, including:

[0231] A first receiving unit, configured to receive a synchronization delay status report reported by a first terminal;

[0232] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0233] The relevant streams include one or more of the following:

[0234] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0235] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0236] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0237] An embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the above method.

[0238] The beneficial effects of this application are:

[0239] The above scheme, by triggering a synchronization delay status report for indicating the synchronization delay status of the relevant flow, assists the network side in obtaining the transmission and remaining synchronization delay information of the relevant flow, so as to facilitate the network side to timely schedule the data of the relevant flow and ensure the synchronous transmission of the relevant flow. BRIEF DESCRIPTION OF THE DRAWINGS

[0240] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0241] Figure 1 A structural diagram showing a network system applicable to an embodiment of the present application;

[0242] Figure 2 A schematic diagram showing a flow chart of an information triggering method according to an embodiment of the present application;

[0243] Figure 3 A schematic diagram showing a flow chart of an information acquisition method according to an embodiment of the present application;

[0244] Figure 4 A schematic diagram showing a unit of an information triggering device according to an embodiment of the present application;

[0245] Figure 5 A structural diagram showing a terminal according to an embodiment of the present application;

[0246] Figure 6 A schematic diagram showing a unit of an information acquisition device according to an embodiment of the present application;

[0247] Figure 7 A structural diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0248] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0249] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein, for example, are implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0250] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0251] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0252] The relevant concepts mentioned in this application are briefly described below.

[0253] In existing protocols, QoS parameters are only set for a single flow (from the perspective of the access network, that is, a Quality of Service (QoS) flow), and QoS guarantee is performed during the transmission process.

[0254] Since the late stage of 5G research, Extended Reality (XR) services have been introduced, and XR services are expected to become the killer application of 6G. XR services can be applied to one or more user devices, such as 3D glasses, handle remote controls, etc. There are two basic ways for XR services to connect to wireless networks. One is that all user devices are connected to a user equipment (UE), and XR services access the network through the terminal; the other is that different user devices access the network as different terminals. The way in which different service flows of XR services come from or go to different user devices is called multimodal communication.

[0255] Multimodal communication refers to the input or output coming from different modalities, such as:

[0256] video / audio media;

[0257] Information from environmental sensors, such as brightness, temperature, humidity, etc.;

[0258] Tactile data: includes tactile sensations such as pressure, texture, vibration, temperature, or kinesthetic sensations such as gravity, tension, or position perception.

[0259] A notable feature of multimodal communication is the synchronization requirement between multimodal applications. For immersive multimodal virtual reality (VR) applications, synchronization of different media units is crucial, otherwise the user experience will be reduced. The synchronization threshold between different modes may even be lower than the delay index of a single application. For example, if touch precedes hearing, the delay threshold of hearing relative to touch is 50ms; if hearing precedes touch, the delay threshold of touch relative to hearing is 25ms. When the relative delay of two service flows is greater than the threshold value, the immersive service experienced by the user will experience delays, stagnation and other unpleasant feelings. Specifically, the synchronous transmission of multimodal services means that the transmission time difference of related services is lower than the synchronization threshold requirement.

[0260] The services of related media units in multimodal communication appear as different service flows in the wireless network, and are then mapped to QoS flows that need to be transmitted in the access network. We call flows with synchronization requirements related flows. Ensuring the synchronous transmission of related flows specifically means that the transmission time difference of the related flows is lower than the synchronization threshold requirement.

[0261] The related streams may be multiple streams transmitted at one terminal, or multiple streams transmitted at different terminals.

[0262] See also Figure 1 , Figure 1 is a structural diagram of a network system to which the embodiments of the present application can be applied, such as Figure 1As shown, it includes a user terminal 11 and a base station 12, wherein the user terminal 11 may be a user equipment (UE), for example, it may be a terminal side device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (PDA for short), a mobile Internet device (Mobile Internet Device, MID) or a wearable device (Wearable Device). It should be noted that the specific type of the user terminal 11 is not limited in the embodiment of the present application. The above-mentioned base station 12 may be a base station of 5G and later versions (for example: gNB, 5G NR NB), or a base station in other communication systems or a gateway station supporting satellite communication, or referred to as a node B. It should be noted that in the embodiment of the present application, only a 5G base station is taken as an example, but the specific type of the base station 12 is not limited.

[0263] The following is an introduction to the embodiments of the present application in conjunction with the accompanying drawings. The information triggering, transmission method, device, terminal and network equipment provided in the embodiments of the present application can be applied to a wireless communication system. The wireless communication system can be a system using the fifth generation (5th Generation, 5G) mobile communication technology (hereinafter referred to as a 5G system). Those skilled in the art can understand that the 5G NR system is only an example and is not a limitation.

[0264] The embodiments of the present application provide an information triggering and transmission method, apparatus, terminal and network equipment to realize the synchronous transmission requirements between different QoS flows.

[0265] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0266] like Figure 2 As shown, an embodiment of the present application provides an information triggering method, which is executed by a first terminal and includes:

[0267] Step S201, triggering a synchronization delay status report, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0268] The related streams include one or more of the following:

[0269] A11, flows carried by different QoS flows, the correlation between the flows being indicated by the correlation between QoS flow IDs;

[0270] In this case, the first terminal sending a flow can be understood as the first terminal sending data of a QoS flow.

[0271] A12, flows carried by different data radio bearers (DRBs), the correlation between the flows being indicated by the association between data radio bearer identifiers (DRB IDs);

[0272] In this case, the first terminal sending a stream can be understood as the first terminal sending data of a DRB.

[0273] A13, the correlation between the flows carried by different logical channels (LCH) is indicated by the association between the logical channel identifiers LCID;

[0274] In this case, the first terminal sending a stream can be understood as the first terminal sending data of an LCH.

[0275] It should be noted that the embodiment of the present application assists the network side in obtaining the transmission and remaining synchronization delay information of the relevant flow by triggering a synchronization delay status report for indicating the synchronization delay status of the relevant flow, so as to facilitate the network side to timely schedule the data of the relevant flow and ensure the synchronous transmission of the relevant flow.

[0276] Optionally, in one implementation, the synchronization delay status report includes at least one of the following:

[0277] B11, time information of synchronization delay;

[0278] Optionally, the time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents a synchronization threshold value, and T represents a waiting time for sending the second target flow after data of the first target flow is sent;

[0279] It should be noted here that the first target stream is the first stream among the related streams that initiates data transmission, and the first target stream can also be called the first stream. The second target stream is one or more streams among the related streams except the first target stream, and the data transmission time of the second target stream is after the data transmission time of the first target stream.

[0280] Optionally, the synchronization threshold refers to the time interval between the sending time of the second target stream and the sending time of the first target stream, i.e., the time period within which the second target stream is allowed to be sent after the first target stream is sent. The synchronization threshold may also be referred to as the synchronization threshold between the sending time of the second target stream and the sending time of the first target stream.

[0281] It should be noted that, usually, the time information refers to the remaining time for sending another stream after sending one stream. Optionally, if the above-mentioned second target stream refers to a stream other than the first target stream, then the remaining time indicated by the time information is only one; optionally, if the above-mentioned second target stream refers to multiple streams other than the first target stream, then the remaining time indicated by the time information is multiple, that is, there will be one remaining time corresponding to each stream.

[0282] Taking the first target flow as the first flow and the second target flow as the second flow as an example, the time information of the synchronization delay indicates the remaining time for sending the second flow.

[0283] B12, Buffer Status Report (BSR) related to the time information of synchronization delay;

[0284] It should be noted that the amount of buffered data indicated by the BSR is positively correlated with the data transmission time, that is, the time information of the synchronization delay can be indirectly reflected through the BSR.

[0285] Optionally, triggering the synchronization delay status report in the embodiment of the present application can be understood as generating a synchronization delay status report, and after acquiring the sending resources of the synchronization delay status report, sending the synchronization delay status report on the corresponding sending resources.

[0286] It should be noted that the relevant streams mentioned in the embodiments of the present application can be sent by a single terminal (i.e., only the first terminal) or by multiple terminals (i.e., the first terminal and at least one second terminal). Under different sending modes, the specific method of triggering the synchronization delay status report is also different. The specific implementation of triggering the synchronization delay status report for different sending modes is described in detail below.

[0287] 1. The related streams are all sent through the first terminal

[0288] Optionally, in an implementation manner in this case, the triggering of the synchronization delay status report includes:

[0289] When the first condition is met, triggering the synchronization delay status report;

[0290] The first condition includes at least one of the following:

[0291] C11, after the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within the first time threshold;

[0292] It should be noted that the first time threshold, as a triggering condition for the synchronization delay status report, may be agreed upon by a protocol or configured by a network device.

[0293] C12, after the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold;

[0294] It should be noted that the second time threshold, as a triggering condition for the synchronization delay status report, may be agreed upon by a protocol or configured by a network device.

[0295] C13, when data of the first target stream in the related stream is sent;

[0296] It can be understood that when the terminal sends data of the first target flow, the synchronization delay status report is triggered.

[0297] C14, data of the first target stream in the related streams arrives at the cache;

[0298] It can be understood that as long as the data of the first target flow reaches the cache, the first terminal triggers the synchronization delay status report.

[0299] C15, data of the second target stream in the related stream arrives at the cache;

[0300] It can be understood that as long as the data of the second target flow arrives at the cache, the first terminal triggers the synchronization delay status report.

[0301] C16. A first request message sent by a network device is received, where the first request message is used to instruct the first terminal to report the synchronization delay status report;

[0302] It should be noted that this situation refers to the triggering of the synchronization delay status report by the network device actively requesting, that is, the network device first sends a first request message to the first terminal, and the first terminal immediately triggers the synchronization delay status report after receiving the first request message, and then triggers the synchronization delay status report at a preset time.

[0303] Optionally, the first request message may be a medium access control (MAC) layer signaling or a physical layer signaling.

[0304] Optionally, the first request message includes at least one of the following:

[0305] C161, a group identifier of the related flow;

[0306] C162. an identifier of a first target stream in the related streams for which a synchronization delay status report needs to be reported, and / or an identifier of a second target stream;

[0307] Optionally, the identifier of the flow may be QoS flow ID, DRB ID, LCH ID, etc.

[0308] Optionally, C11-C15 in the first condition may be a protocol agreement or a network device configuration.

[0309] 2. The relevant stream is sent through the first terminal and at least one second terminal

[0310] Optionally, in an implementation manner in this case, the triggering of the synchronization delay status report includes:

[0311] When the second condition is met, triggering the synchronization delay status report;

[0312] The second condition includes at least one of the following:

[0313] C21, when data of the related stream in the first terminal is sent;

[0314] It can be understood that when the first terminal sends data of any one of the related streams, the first terminal triggers the synchronization delay status report.

[0315] C22: Data of the related stream in the first terminal arrives at the cache;

[0316] It can be understood that as long as the data of one of the related flows arrives at the cache, the first terminal triggers the synchronization delay status report.

[0317] C23. receiving a second request message sent by a network device, where the second request message is used to instruct the first terminal to report the synchronization delay status report;

[0318] It should be noted that this situation refers to the triggering of the synchronization delay status report by the network device actively requesting, that is, the network device first sends a second request message to the first terminal, and the first terminal immediately triggers the synchronization delay status report after receiving the second request message, and then triggers the synchronization delay status report at a preset time.

[0319] Optionally, the second request message may be a medium access control (MAC) layer signaling or a physical layer signaling.

[0320] Optionally, in an implementation manner, the second request message includes at least one of the following:

[0321] C231, a group identifier of the related flow;

[0322] C232, an identifier of a first target stream for which a synchronization delay status report needs to be reported, and / or an identifier of a second target stream;

[0323] Optionally, the identifier of the flow may be QoS flow ID, DRB ID, LCH ID, etc.

[0324] Optionally, C21 and C22 in the second condition may be protocol agreed upon or network device configured.

[0325] It should be noted that, regardless of which of the above-mentioned sending modes the relevant stream adopts, after triggering the synchronization delay status report, the first terminal can cancel the triggered synchronization delay status report, and canceling the triggered synchronization delay status report can be understood as deleting the generated synchronization delay status report or determining that the generated synchronization delay status report is invalid (or ineffective). Optionally, in one implementation, the specific implementation of triggering the synchronization delay status report includes:

[0326] After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report;

[0327] The third condition includes at least one of the following:

[0328] D11, a packet data unit (PDU) or a packet data unit set (PDU set) in the first target flow in the related flow fails to be sent;

[0329] D12, the second target stream in the related stream starts to be sent;

[0330] It should be noted that if the relevant streams other than the first stream start to be transmitted, it means that the network side no longer needs to determine the remaining time of the streams other than the first stream. At this time, there is no need to perform the synchronization delay status report. The first terminal can cancel the triggered synchronization delay status report.

[0331] D13. A PDU of the second target stream in the related stream is sent successfully;

[0332] It should be noted that if a PDU of a stream other than the first stream in the related streams is sent successfully, it indicates that the transmission of this stream has begun, and the network side no longer needs to determine the remaining time of the streams other than the first stream. At this time, there is no need to perform the synchronization delay status report, and the first terminal can cancel the triggered synchronization delay status report.

[0333] D14. A PDU set of the second target stream in the related stream is sent successfully;

[0334] It should be noted that if a PDU set of a stream other than the first stream in the related streams is sent successfully, it indicates that the transmission of this stream has begun, and the network side no longer needs to determine the remaining time of the streams other than the first stream. At this time, there is no need to perform the synchronization delay status report, and the first terminal can cancel the triggered synchronization delay status report.

[0335] D15, the sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold;

[0336] This situation can be understood as the time corresponding to the sending waiting time of the second target flow has exceeded or reached the time indicated by the synchronization delay threshold.

[0337] It should be noted that if the sending waiting time of the relevant streams except the first stream is greater than or equal to the synchronization delay threshold, it indicates that the relevant streams are within the synchronization transmission requirements. At this time, there is no need to report the synchronization delay status report to reduce the signaling overhead, and the first terminal can cancel the triggered synchronization delay status report.

[0338] D16. The first terminal has sent the synchronization delay status report to the network device;

[0339] It should be noted that if the first terminal has sent the triggered synchronization delay status report to the network device, it means that the synchronization delay status report has been transmitted and there is no need to send the synchronization delay status report again. The first terminal can cancel the triggered synchronization delay status report.

[0340] Optionally, the third condition may be a protocol agreement or a network device configuration.

[0341] It should be noted that, when triggering the synchronization delay status report, if there are resources for sending the synchronization delay status report, the terminal also needs to send the synchronization delay status report to the network device. Optionally, in one implementation, after the synchronization delay status report is triggered, the method further includes:

[0342] When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report;

[0343] The first message includes at least one of the following:

[0344] E11, Radio Resource Control (RRC) signaling;

[0345] E12, Service Data Adaptation Protocol Control Protocol Data Unit (SDAP control PDU);

[0346] E13, Packet Data Convergence Protocol Control Protocol Data Unit (PDCP control PDU);

[0347] E14, Radio Link Control Protocol Data Unit (RLC control PDU);

[0348] E15, Media Access Control Element (MAC CE);

[0349] E16. Physical layer signaling.

[0350] It should be noted that by sending the synchronization delay status report to the network device, the network device allocates uplink resources to the relevant terminals (the first terminal and / or at least one second terminal) within the synchronization threshold, so that the relevant terminals send data of the relevant streams on the uplink resources, thereby ensuring that the data sending time difference of the relevant streams does not exceed the synchronization threshold value, so that the sending of the relevant streams meets the synchronization requirements.

[0351] Optionally, in one implementation, the method further includes:

[0352] Receiving configuration information of the relevant flow sent by a network device or a core network device;

[0353] The configuration information includes at least one of the following:

[0354] F11, first indication information, where the first indication information is used to indicate the association relationship of the related flows;

[0355] Optionally, in an implementation manner, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0356] F1101, the relationship between business flows;

[0357] It should be noted that the association relationship can be indicated by a business flow identifier, for example, indicating that business flow 1 and business flow 2 are related flows; it can also be indicated by a business flow group identifier, for example, indicating a group identifier that is used to indicate a group of associated business flows.

[0358] F1102, the relationship between Internet Protocol flows (IP flows);

[0359] It should be noted that the association relationship can be indicated by an IP flow identifier, for example, indicating that IP flow1 and IP flow 2 are related flows; it can also be indicated by an IP flow group identifier, for example, indicating a group identifier used to indicate a group of associated IP flows.

[0360] F1103, the relationship between QoS flows;

[0361] It should be noted that the association relationship can be indicated by a QoS flow identifier, for example, indicating that QoS flow1 and QoS flow 2 are related flows; it can also be indicated by a QoS flow group identifier, for example, indicating a group identifier (for example, Common ID), which is used to indicate a group of associated QoS flows.

[0362] F1104, the relationship between DRBs;

[0363] It should be noted that the association relationship can be indicated by a DRB identifier, for example, indicating that DRB1 and DRB 2 have an association relationship, which means that DRB1 and DRB 2 are mapped to related streams; it can also be indicated by a DRB group identifier, for example, indicating a group identifier (for example, Related DRB index), which is used to indicate a group of associated DRBs.

[0364] The relationship between F1105 and LCH;

[0365] It should be noted that the association relationship can be indicated by an LCH identifier, for example, indicating that LCH1 and LCH2 have an association relationship, which means that LCH1 and LCH2 are mapped to related streams; it can also be indicated by an LCH group identifier, for example, indicating a group identifier (for example, Related LCH index), which is used to indicate a group of associated LCHs.

[0366] It should also be noted here that since the core network side is only visible to service flows, IP flows and QoS flows, and the mapping of DRB, LCH and QoS flows is implemented on the network device side, if the configuration information of the relevant flow is configured by the core network device for the first terminal, then the configuration information can usually only include one or more of F1101-F1103, and the core network device sends the configuration information of the relevant flow to the first terminal via non-access layer signaling; if the configuration information of the relevant flow is configured by the network device for the first terminal, then the configuration information can usually only include one or more of F1101-F1105, and the network device sends the configuration information of the relevant flow to the first terminal via access layer signaling.

[0367] Optionally, in an implementation manner, the relevant stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0368] F1111, a QoS flow, a DRB or a logical channel carrying the related flow;

[0369] It should be noted that this situation is to notify the first terminal which of its available QoS flows, DRBs or logical channels correspond to the relevant flows; optionally, it can be indicated by the identifier of the QoS flow, DRB or logical channel; it can also be indicated by the group identifier. Usually in this case, the correlation between the terminals is only known by the network device, and the terminal only knows that the specified QoS flow, DRB, LCH has a relevant flow related to it.

[0370] F1112, QoS flow, DRB or logical channel carrying the related flow, and target information;

[0371] The target information includes at least one of the following:

[0372] F11121, identification of the at least one second terminal;

[0373] The QoS flow, DRB or logical channel of the second terminal is related to the QoS flow, DRB or logical channel of the first terminal.

[0374] F11122. QoS flow, DRB or logical channel of the at least one second terminal;

[0375] Optionally, the QoS flow, DRB or logical channel in this case refers to a QoS flow, DRB or logical channel of the second terminal that is related to the QoS flow, DRB or logical channel of the first terminal;

[0376] It should be noted that, in the case of F1112 described above, the terminal needs to know which terminal has a related flow with it.

[0377] F12, synchronization threshold value of the related stream;

[0378] It should be noted here that if the association relationship of QoS flow is configured, the synchronization threshold value of the related flow is used to indicate the synchronization threshold between different QoS flows; if the association relationship of DRB is configured, the synchronization threshold value of the related flow is used to indicate the synchronization threshold between different DRBs; if the association relationship of LCH is configured, the synchronization threshold value of the related flow is used to indicate the synchronization threshold between different LCHs.

[0379] Taking the case where the related flows include two QoS flow flows as an example, in the case where the related flows are all sent through the first terminal, the configuration method of the synchronization threshold value of the related flows in the configuration information is as shown in Table 1.

[0380] Table 1 Synchronization threshold value mode of single terminal transmission related stream

[0381] QoS flow1-QoS flow2 QoS flow2-QoS flow1 Synchronization Threshold Th1 Th2

[0382] It should be noted that the flow data before the minus sign in Table 1 is transmitted first. As can be seen from Table 1, if QoS flow1 is sent before QoS flow2, the synchronization threshold of QoS flow2 relative to QoS flow1 is Th1; if QoS flow2 is sent before QoS flow1, the synchronization threshold of QoS flow1 relative to QoS flow2 is Th2.

[0383] Taking the case where the related flows include two QoS flows, for example, in the case where the related flows are sent through the first terminal and the second terminal, the configuration method of the synchronization threshold of the related flows in the configuration information is as shown in Table 2 or Table 3.

[0384] Table 2 One of the synchronization threshold values ​​for multi-terminal transmission related streams

[0385] QoS flow1 Synchronization Threshold Th1

[0386] Table 3 Synchronization threshold value method 2 for multi-terminal transmission related streams

[0387] QoS flow2 Synchronization Threshold Th2

[0388] It should be noted that, from Table 2 and Table 3, if the first terminal sends QoS flow1, the first terminal receives the configuration of Table 2; if the first terminal sends QoS flow2, the first terminal receives the configuration of Table 3.

[0389] It should be noted that other representations of the related flows are similar to those in Table 1, Table 2, and Table 3, and will not be repeated here.

[0390] Taking the network device as a base station as an example, the specific application examples of the embodiments of the present application are illustrated as follows.

[0391] Application scenario 1: Single terminal (the base station configures related flows, and the terminal triggers the sending of synchronization delay status reports on its own)

[0392] The implementation process on the base station side includes:

[0393] Step 111: Send an RRC message to a terminal (i.e., a first terminal), where the RRC message includes configuration information of related streams, where the configuration information includes one or more of the following (two streams are taken as an example below. If more than two streams have a related relationship, each pair or group of related streams needs to be configured separately):

[0394] S101, first indication information, indicating related flows and their associations; for example, it may indicate an association between two QoS flows or two DRB IDs or two LCH IDs. Optionally, the configuration message further includes a group identifier of the related flows. An example of a group identifier of the related flows is: Common ID1, Common ID1 includes QoS flow1 and QoS flow2.

[0395] S102. Synchronization threshold values ​​of related streams. An example of synchronization threshold values ​​of related streams is shown in Table 1.

[0396] Optionally, the base station may further configure configuration information of a synchronization delay status report for the terminal, where the configuration information includes at least one of the following:

[0397] S111, allowing the terminal to trigger and report the synchronization delay status report;

[0398] S112, a condition for triggering a synchronization delay status report, which may be any one or more of C11-C15. Optionally, if the base station does not configure this condition, the condition may be agreed upon by a protocol;

[0399] S113, cancelling condition of the triggered synchronization delay status report, which condition may be any one or more of D11-D16. Optionally, if the base station does not configure this item, the condition may be agreed upon by the protocol.

[0400] It should be noted that the configuration information of the related flow and the configuration information of the synchronization delay status report can be sent to the terminal together in an RRC message.

[0401] Step 112: Receive a synchronization delay status report sent by the terminal.

[0402] Optionally, the base station also needs to receive the data of the first stream sent by the terminal. It should be noted that due to the complexity of wireless transmission, the data of the first stream may be successfully received by the base station later than the synchronization delay status report.

[0403] Step 113: allocate uplink resources to the terminal within the synchronization threshold, and the terminal sends data of the related stream on the uplink resources, that is, use the synchronization threshold as the delay budget of the second stream in the related stream so that the time difference of the related stream data transmission does not exceed the synchronization threshold value.

[0404] The implementation process on the terminal side includes:

[0405] Step 121: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related flows and configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: related flows and their associations, synchronization thresholds of related flows, whether to allow sending a synchronization delay status report, triggering conditions for the synchronization delay status report, and cancellation conditions for the synchronization delay status report.

[0406] Step 122: Send data of the first flow in the relevant flows to the base station, and trigger and send the synchronization delay status report according to the triggering condition of the synchronization delay status report.

[0407] Step 123: Receive a scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station, wherein the uplink data includes data of a related flow.

[0408] Application scenario 2: Single terminal (the core network configures related flows, and the terminal triggers the sending of synchronization delay status reports on its own)

[0409] The implementation process on the core network side includes:

[0410] Step 211: Send NAS signaling to the terminal. The NAS signaling is sent through the N1 interface. The NAS signaling includes configuration information of related flows. The configuration information includes one or more of the following:

[0411] S201, first indication information, indicating related flows and their associations; for example, the associations between two IP flows or two QoS flows may be indicated. Optionally, the configuration message further includes a group identifier of the related flows. An example of a group identifier of the related flows is Common ID1, where Common ID1 includes QoS flow1 and QoS flow2.

[0412] S202: Synchronization threshold of related streams.

[0413] Step 212: Send configuration information of relevant flows of the terminal to the base station.

[0414] The implementation process on the base station side includes:

[0415] Step 220: Receive configuration information of related flows of the terminal sent by the core network.

[0416] Step 221: Send an RRC message to the terminal, where the RRC message includes configuration information of a synchronization delay status report, where the configuration information includes one or more of the following:

[0417] S211, allowing the terminal to trigger and report the synchronization delay status report;

[0418] S212, a condition for triggering a synchronization delay status report, which may be any one or more of C11-C15. Optionally, if the base station does not configure this condition, the condition may be agreed upon by a protocol;

[0419] S213, cancelling condition of the triggered synchronization delay status report, which condition may be any one or more of D11-D16. Optionally, if the base station does not configure this item, the condition may be agreed upon by the protocol.

[0420] Optionally, if the core network does not notify the terminal of the synchronization threshold value of the relevant flow, or the base station needs to indicate the synchronization threshold value between DRBs or logical channels, that is, the QoS flow has been mapped to the corresponding DRB or logical channel, then the base station also needs to send the synchronization threshold value of the relevant flow to the terminal. An example of the synchronization threshold value of the relevant flow is shown in Table 1.

[0421] Step 222: Receive the synchronization delay status report sent by the terminal.

[0422] Optionally, the base station also needs to receive the data of the first stream sent by the terminal. It should be noted that due to the complexity of wireless transmission, the data of the first stream may be successfully received by the base station later than the synchronization delay status report.

[0423] Step 223: Allocate uplink resources to the terminal within the synchronization threshold, and the terminal sends data of related flows on the uplink resources.

[0424] The implementation process on the terminal side includes:

[0425] Step 230: Receive configuration information of related flows sent by the core network, and determine related flows and their associations and / or synchronization thresholds of related flows according to the configuration information of the related flows.

[0426] Step 231: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: a synchronization threshold of a related stream, whether to allow sending a synchronization delay status report, a trigger condition for the synchronization delay status report, and a cancellation condition for the synchronization delay status report.

[0427] Step 232: Send data of the first flow in the relevant flows to the base station, and trigger and send the synchronization delay status report according to the triggering condition of the synchronization delay status report.

[0428] Step 233: Receive a scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station, wherein the uplink data includes data of a related flow.

[0429] Application scenario 3: Single terminal (base station configures related flows, base station indicates triggering the sending of synchronization delay status report)

[0430] The implementation process on the base station side includes:

[0431] Step 311: Send an RRC message to the terminal, where the RRC message includes configuration information of the relevant flow, and the configuration information includes a combination of one or more of the following:

[0432] S301, first indication information, indicating related flows and their associations; for example, it may indicate an association between two QoS flows or two DRB IDs or two LCH IDs. Optionally, the configuration message further includes a group identifier of the related flows. An example of a group identifier of the related flows is: Common ID1, Common ID1 includes QoS flow1 and QoS flow2.

[0433] S302: synchronization threshold of related streams. An example of synchronization threshold of related streams is shown in Table 1. Optionally, the base station may also configure synchronization delay status report configuration information for the terminal. The configuration information includes: whether to allow sending the synchronization delay status report.

[0434] Step 312: Send a first request message to the terminal, where the first request message is used to request the terminal to send a synchronization delay status report. The first request message may carry one or more of the following contents: a group identifier of related flows, an identifier of the first flow corresponding to the synchronization delay status report that needs to be reported (such as QoS flow ID / DRB ID / LCH ID), and an identifier of the second flow corresponding to the synchronization delay status report that needs to be reported.

[0435] Step 313: Receive the synchronization delay status report sent by the terminal.

[0436] Step 314: allocate uplink resources to the terminal within the synchronization threshold, and the terminal sends data of the related stream on the uplink resources, that is, use the synchronization threshold as the delay budget of the second stream in the related stream so that the time difference of the related stream data transmission does not exceed the synchronization threshold value.

[0437] The implementation process on the terminal side includes:

[0438] Step 321: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related flows and configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: related flows and their associations, synchronization thresholds of related flows, and whether to allow sending a synchronization delay status report.

[0439] Step 322: Receive a first request message sent by the base station side.

[0440] Step 323: Generate and send a synchronization delay status report.

[0441] It should be noted that if the terminal cannot generate a valid synchronization delay status report, such as there is no data of the second stream in the cache, or the time difference between the time when the synchronization delay status report reporting request is received and the data transmission of the first stream exceeds the synchronization threshold, a specified value or a special value can be fed back to the base station. The specified value or special value is used to indicate that the synchronization delay status report cannot be obtained.

[0442] Step 324: Receive a scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station, wherein the uplink data includes data of a related flow.

[0443] Application Scenario 4: Single Terminal (Core Network configures related flows, base station indicates triggering the sending of synchronization delay status report)

[0444] The core network implementation process includes:

[0445] Step 411: Send NAS signaling to the terminal. The NAS signaling is sent through the N1 interface. The NAS signaling includes configuration information of related flows. The configuration information includes one or more of the following:

[0446] S401, first indication information, indicating related flows and their association relationship; for example, it may indicate the association relationship between two IP flows or two QoS flows. Optionally, the configuration message further includes a group identifier of the related flows. An example of a group identifier of the related flows is: Common ID1, Common ID1 includes QoS flow1 and QoS flow2.

[0447] S402: Synchronization threshold of related streams.

[0448] Step 412: Send configuration information of relevant flows of the terminal to the base station.

[0449] The implementation process on the base station side includes:

[0450] Step 420: Receive configuration information of related flows of the terminal sent by the core network.

[0451] Step 421: Send an RRC message to the terminal, where the RRC message includes configuration information of a synchronization delay status report, and the configuration information includes: allowing the terminal to trigger and report a synchronization delay status report.

[0452] Optionally, if the core network does not notify the terminal of the synchronization threshold value of the relevant flow, or the base station needs to indicate the synchronization threshold value between DRBs or logical channels, that is, the QoS flow has been mapped to the corresponding DRB or logical channel, then the base station also needs to send the synchronization threshold value of the relevant flow to the terminal. An example of the synchronization threshold value of the relevant flow is shown in Table 1.

[0453] Step 422: Send a first request message to the terminal, where the first request message is used to request the terminal to send a synchronization delay status report. The first request message carries one or more of the following: a related flow group identifier, an identifier of the first flow corresponding to the synchronization delay status report that needs to be reported (such as QoS flow ID / DRB ID / LCH ID), and an identifier of the second flow corresponding to the synchronization delay status report that needs to be reported.

[0454] Step 423: Receive the synchronization delay status report sent by the terminal.

[0455] Step 424: Allocate uplink resources to the terminal within the synchronization threshold, and the terminal sends data of related flows on the uplink resources.

[0456] The implementation process on the terminal side includes:

[0457] Step 430: Receive configuration information of related flows sent by the core network, and determine related flows and their associations and / or synchronization thresholds of related flows according to the configuration information of the related flows.

[0458] Step 431: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: a synchronization threshold of a related flow, and whether to allow sending a synchronization delay status report.

[0459] Step 432: Receive a first request message sent by the base station side.

[0460] Step 433: Generate and send a synchronization delay status report.

[0461] It should be noted that if the terminal cannot generate a valid synchronization delay status report, for example, there is no data for the second stream in the cache, or the time difference between the time when the synchronization delay status report reporting request is received and the data transmission of the first stream exceeds the synchronization delay threshold, a specified value or a special value can be fed back to the base station. The specified value or special value is used to indicate that the synchronization delay status report cannot be obtained.

[0462] Step 434: Receive a scheduling command sent by the base station, and send uplink data on the resources allocated by the base station, wherein the uplink data includes data of a related flow.

[0463] Application scenario 5: Multiple terminals (base station configures related flows, and the terminal triggers the sending of synchronization delay status reports on its own)

[0464] Assume that QoS flow1 of the first terminal and QoS flow2 of the second terminal are associated. If QoS flow1 is sent first, the synchronization threshold is Th1; if QoS flow2 is sent first, the synchronization threshold is Th2.

[0465] The implementation process on the base station side includes:

[0466] Step 511: Send an RRC message to a terminal (sent to the first terminal and the second terminal respectively), where the RRC message includes configuration information of a related flow, and the configuration information includes a combination of one or more of the following:

[0467] S501, first indication information, indicating related flows and their associations;

[0468] For example, the flow identifier of the terminal indicating that there is a related flow with other terminals can be represented by QoS flow ID or DRBindex or LCID; or, the flow identifier of the terminal with related flows with other terminals, and the group identifier of the corresponding related flows (such as Common ID / Related DRB index / Related LCH index). An example of a group identifier of a related flow is (Common ID, QoS flow ID1). Or, for example, in addition to the flow identifier of the terminal indicating that there is a related flow with other terminals, the terminal is also notified of the identifier of another terminal related to it and / or the related flow information under the related terminal.

[0469] S502. Synchronization threshold values ​​of related streams. An example of synchronization threshold values ​​of related streams is shown in Table 2 (configured for the first terminal).

[0470] Optionally, the base station may further configure configuration information of a synchronization delay status report for the terminal, where the configuration information includes at least one of the following:

[0471] S511, allowing the terminal to trigger and report a synchronization delay status report;

[0472] S512, triggering a synchronization delay status report condition, the condition may be any one or more of C11-C15, and optionally, if the base station does not configure this condition, the condition may be agreed upon by a protocol;

[0473] S513: The cancellation condition of the triggered synchronization delay status report may be D11 or D16. Optionally, if the base station does not configure this item, the condition may be agreed upon by the protocol.

[0474] It should be noted that the configuration information of the related flow and the configuration information of the synchronization delay status report can be sent to the terminal together in an RRC message.

[0475] Step 512: Receive the synchronization delay status report sent by the terminal.

[0476] Optionally, the base station also receives data of the first stream. It should be noted that, due to the complexity of wireless transmission, the data of the first stream may be successfully received by the base station later than the synchronization delay status report.

[0477] Step 513: Allocate uplink resources to the associated terminal within the synchronization threshold, so that the associated terminal completes the transmission of related stream data within the synchronization threshold.

[0478] The implementation process of the first terminal side (the terminal sending the first stream data) includes:

[0479] Step 521: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related flows and configuration information of a synchronization delay status report. According to the configuration information, determine one or more of the following: related flows and their associations, synchronization thresholds of related flows, whether to allow triggering and reporting of synchronization delay status reports, triggering conditions for synchronization delay status reports, and cancellation conditions for synchronization delay status reports.

[0480] Step 522: Send data of the relevant flow to the base station, and trigger and send the synchronization delay status report according to the triggering condition of the synchronization delay status report.

[0481] The implementation process of the second terminal side (the terminal sending the second stream data) includes:

[0482] Step 531: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related flows and configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: related flows and their associations, synchronization thresholds of related flows, whether triggering and reporting of synchronization delay status reports are allowed, triggering conditions for synchronization delay status reports, and cancellation conditions for synchronization delay status reports.

[0483] Step 532: Receive the scheduling command sent by the base station, and send uplink data on the resources allocated by the base station.

[0484] It should be noted that in the above example, UE1 sends the data of the first stream, and UE2 sends the data of the second stream in the related stream. Since UE1 cannot determine whether it is sending the first stream in the related stream, the simplest method is for UE1 and UE2 to send a synchronization delay status report (both believe that they are sending the first stream) according to the trigger conditions when or after sending the related stream data according to the configuration, and the base station determines the related stream and subsequent scheduling according to the received data and the synchronization delay status report.

[0485] Application scenario 6: Multiple terminals (the core network configures related flows, and the terminal triggers the sending of synchronization delay status reports on its own)

[0486] The core network implementation process includes:

[0487] Step 611: Send NAS signaling to the terminal. The NAS signaling is sent through the N1 interface. The NAS signaling includes configuration information of related flows. The configuration information includes one or more of the following:

[0488] S601, first indication information, indicating related flows and their association relationships;

[0489] For example, for a specified terminal, one or more of the following information is indicated:

[0490] a QoS flow, a DRB or a logical channel carrying the related flow;

[0491] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0492] The target information includes at least one of the following:

[0493] an identifier of the at least one second terminal;

[0494] The QoS flow, DRB or logical channel of the at least one second terminal.

[0495] S602: Configure synchronization thresholds of related flows.

[0496] Step 612: Send configuration information of relevant flows of the terminal to the base station.

[0497] The implementation process on the base station side includes:

[0498] Step 620: Receive relevant flow information for a specific terminal sent by the core network.

[0499] Step 621: Send an RRC message to a terminal (sent to the first terminal and the second terminal respectively), where the RRC message includes synchronization delay status report configuration information, where the configuration information includes a combination of one or more of the following:

[0500] S611, allowing the terminal to trigger and report a synchronization delay status report;

[0501] S612: a condition for triggering a synchronization delay status report, which may be any one or more of C11-C15. Optionally, if the base station does not configure this condition, the condition may be agreed upon by a protocol.

[0502] S613: The cancellation condition of the triggered synchronization delay status report may be D11 or D16. Optionally, if the base station does not configure this item, the condition may be agreed upon by the protocol.

[0503] Optionally, if the core network does not notify the terminal of the synchronization threshold value of the relevant flow, or the base station needs to indicate the synchronization threshold value for the DRB or logical channel, that is, the QoS flow has been mapped to the corresponding DRB or logical channel, then the base station also needs to send the synchronization threshold value of the relevant flow to the terminal. An example of the synchronization threshold value of the relevant flow is shown in Table 2 (configured for the first terminal).

[0504] Step 622: Receive the synchronization delay status report sent by the terminal.

[0505] Step 623: Allocate uplink resources to the associated terminal within the synchronization threshold, so that the associated terminal completes the transmission of related stream data within the synchronization threshold.

[0506] The implementation process of the first terminal side (the terminal sending the first stream data) includes:

[0507] Step 630: Receive configuration information of related flows sent by the core network, and determine related flows and / or synchronization thresholds of related flows according to the configuration information of related flows.

[0508] Step 631: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: a synchronization threshold of a related stream, whether to allow sending a synchronization delay status report, a trigger condition for the synchronization delay status report, and a cancellation condition for the synchronization delay status report.

[0509] Step 632: Send data of the first flow in the related flows, and trigger and send the synchronization delay status report according to the triggering condition of the synchronization delay status report.

[0510] The implementation process of the second terminal side (the terminal sending the second stream data) includes:

[0511] Step 640: Receive configuration information of related flows sent by the core network, determine related flows according to the configuration information of related flows, and / or obtain synchronization threshold values ​​of related flows.

[0512] Step 641: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: a synchronization threshold of a related stream, whether to allow sending a synchronization delay status report, a trigger condition for the synchronization delay status report, and a cancellation condition for the synchronization delay status report.

[0513] Step 642: Receive the scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station.

[0514] It should be noted that the solution to the problem of related flow order in this application case is the same as that in application case five.

[0515] Application Scenario 7: Multiple Terminals (Base Station Configures Related Flows, Base Station Instructions Trigger the Sending of Synchronous Delay Status Reports)

[0516] Assume that QoS flow1 of the first terminal and QoS flow2 of the second terminal are associated. If QoS flow1 is sent first, the synchronization threshold is Th1; if QoS flow2 is sent first, the synchronization threshold is Th2.

[0517] The implementation process on the base station side includes:

[0518] Step 711: Send an RRC message to a terminal (sent to the first terminal and the second terminal respectively), where the RRC message includes configuration information of a related flow, and the configuration information includes a combination of one or more of the following:

[0519] S701, first indication information, indicating related flows and their association relationships;

[0520] For example, the flow identifier of the terminal indicating that there are related flows with other terminals can be represented by QoS flow ID or DRBindex or LCID; or, the flow identifier of the terminal with related flows with other terminals, and the group identifier of the corresponding related flows (such as Common ID / Related DRB index / Related LCH index). An example is (Common ID, QoSflow ID1). Or, for example, in addition to the flow identifier of the terminal indicating that there are related flows with other terminals, the terminal is also notified of the identifier of another terminal related to it and / or the related flow information under the related terminal.

[0521] S702. Synchronization threshold values ​​of related streams. An example of synchronization threshold values ​​of related streams is shown in Table 2 (configured for the first terminal).

[0522] Optionally, the base station may also configure the terminal with configuration information of the synchronization delay status report, where the configuration information includes: whether to allow sending the synchronization delay status report.

[0523] Step 712: Send a second request message to the terminal, where the second request message is used to request the terminal to send a synchronization delay status report. The second request message carries one or more of the following contents: a related flow group identifier, and / or a related flow identifier (such as QoS flow ID / DRB ID / LCH ID) corresponding to the synchronization delay status report that needs to be reported.

[0524] Step 713: Receive the synchronization delay status report sent by the terminal.

[0525] Step 714: Allocate uplink resources to the associated terminal within the synchronization threshold, so that the associated terminal completes the transmission of related stream data within the synchronization threshold.

[0526] The implementation process of the first terminal side (the terminal sending the first stream data) includes:

[0527] Step 721: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related streams and configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: related stream information, synchronization threshold of related streams, and whether to allow triggering and reporting of a synchronization delay status report.

[0528] Step 722: Receive a second request message sent by the base station side.

[0529] Step 723: Generate and send a synchronization delay status report.

[0530] It should be noted that if the terminal cannot generate a valid synchronization delay status report, such as the data transmission of the first stream exceeds the synchronization delay threshold, a specified value or a special value can be fed back to the base station, and the specified value or the special value is used to indicate that the synchronization delay status report cannot be obtained.

[0531] The implementation process of the second terminal side (the terminal sending the second stream data) includes:

[0532] Step 731: Receive an RRC message sent by the base station side, where the RRC message includes configuration information of related flows and configuration information of a synchronization delay status report, and determine one or more of the following based on the configuration information: related flow information, synchronization threshold of related flows, and whether to allow triggering and reporting of a synchronization delay status report.

[0533] Step 732: Receive the scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station.

[0534] In the above example, UE1 sends data of the first stream, and UE2 sends data of the second stream in the related stream. In this embodiment, the terminal sends the synchronization delay status report based on the request of the base station, and does not need to determine whether it is the first stream. The base station determines the related stream and subsequent scheduling based on the received data and the synchronization delay status report.

[0535] Application scenario 8: Multiple terminals (core network configuration related flows, base station instructions trigger the sending of synchronization delay status reports)

[0536] The core network implementation process includes:

[0537] Step 811: Send NAS signaling to the terminal. The NAS signaling is sent through the N1 interface. The NAS signaling includes configuration information of related flows. The configuration information includes one or more of the following:

[0538] S801, first indication information, indicating related flows and their associations;

[0539] For example, for a specified terminal, one or more of the following information is indicated:

[0540] a QoS flow, a DRB or a logical channel carrying the related flow;

[0541] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0542] The target information includes at least one of the following:

[0543] an identifier of the at least one second terminal;

[0544] The QoS flow, DRB or logical channel of the at least one second terminal.

[0545] S802: Configure synchronization thresholds of related flows.

[0546] Step 812: Send configuration information of relevant flows of the terminal to the base station.

[0547] The implementation process on the base station side includes:

[0548] Step 820: Receive relevant flow information for a specific terminal sent by the core network.

[0549] Step 821: Send an RRC message to a terminal (sent to the first terminal and the second terminal respectively), where the RRC message includes synchronization delay status report configuration information, and the configuration information includes: allowing the terminal to trigger and report the synchronization delay status report.

[0550] Optionally, if the core network does not notify the terminal of the synchronization threshold value of the relevant flow, or the base station needs to indicate the synchronization threshold value for the DRB or logical channel, that is, the QoS flow has been mapped to the corresponding DRB or logical channel, then the base station also needs to send the synchronization threshold value of the relevant flow to the terminal. An example of the synchronization threshold value of the relevant flow is shown in Table 2 (configured for the first terminal).

[0551] Step 822: Send a second request message to the terminal, where the second request message is used to request the terminal to send a synchronization delay status report. The second request message carries one or more of the following contents: a related flow group identifier, and / or an identifier of a related flow corresponding to the synchronization delay status report that needs to be reported (such as QoS flow ID / DRB ID / LCH ID).

[0552] Step 823: Receive the synchronization delay status report sent by the terminal.

[0553] Step 824: Allocate uplink resources to the associated terminal within the synchronization threshold, so that the associated terminal completes the transmission of related stream data within the synchronization threshold.

[0554] The implementation process of the first terminal side (the terminal sending the first stream data) includes:

[0555] Step 830: Receive configuration information of related flows sent by the core network, and determine the existence of QoS flows or DRBs or logical channels of related flows according to the configuration information, and / or obtain synchronization thresholds of related flows.

[0556] Step 831: Receive RRC signaling sent by the base station side, where the RRC signaling includes configuration information of the synchronization delay status report, and determine one or more of the following according to the configuration information: a synchronization threshold of a related flow, and whether to allow sending the synchronization delay status report.

[0557] Step 832: Receive a second request message sent by the base station side.

[0558] Step 833: Generate and send a synchronization delay status report.

[0559] It should be noted that if the terminal cannot generate a valid synchronization delay status report, such as the data transmission of the relevant stream exceeds the synchronization delay threshold, a specified value or a special value can be fed back to the base station, and the specified value or the special value is used to indicate that the synchronization delay status report cannot be obtained.

[0560] The implementation process of the second terminal side (the terminal sending the second stream data) includes:

[0561] Step 840: Receive configuration information of related flows sent by the core network, and determine related flows and / or synchronization thresholds of related flows according to the configuration information.

[0562] Step 841: Receive RRC signaling sent by the base station side, where the RRC signaling includes configuration information of the synchronization delay status report, and determine one or more of the following based on the configuration information: a synchronization threshold of a related flow, and whether to allow sending the synchronization delay status report.

[0563] Step 842: Receive the scheduling command sent by the base station, and send uplink data on the uplink resources allocated by the base station.

[0564] It should be noted that the embodiments of the present application enable the network side to obtain the transmission and remaining synchronization delay information of the synchronous flow, so as to facilitate the network side to timely schedule the data of the related flow and ensure the synchronous transmission of the related flow.

[0565] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminals (also referred to as terminal equipment) and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0566] The terminal involved in the embodiment of the present application may also be referred to as a terminal device, which may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be referred to as a user equipment (UE). A wireless terminal device may communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0567] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay terminal node (relay node), a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0568] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.

[0569] like Figure 3 As shown, an embodiment of the present application provides an information acquisition method, which is executed by a network device and includes:

[0570] Step S301, receiving a synchronization delay status report reported by a first terminal;

[0571] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0572] The relevant streams include one or more of the following:

[0573] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0574] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0575] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0576] Optionally, in an implementation manner, the receiving a synchronization delay status report reported by the first terminal includes:

[0577] Receiving a first message sent by a first terminal, where the first message carries the synchronization delay status report;

[0578] The first message includes at least one of the following:

[0579] Radio Resource Control (RRC) signaling;

[0580] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0581] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0582] Radio link control protocol data unit RLC control PDU;

[0583] Media access control element MAC CE;

[0584] Physical layer signaling.

[0585] Optionally, in one implementation, the method further includes:

[0586] Sending configuration information of the relevant flow to the first terminal;

[0587] The configuration information includes at least one of the following:

[0588] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0589] The synchronization threshold of the related stream.

[0590] Optionally, in an implementation manner, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0591] The relationship between business flows;

[0592] The relationship between Internet Protocol flows;

[0593] The relationship between QoS flows;

[0594] The association relationship between data radio bearers (DRBs);

[0595] The association relationship between logical channels LCH.

[0596] Optionally, in an implementation manner, the relevant stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0597] a QoS flow, a DRB or a logical channel carrying the related flow;

[0598] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0599] The target information includes at least one of the following:

[0600] an identifier of the at least one second terminal;

[0601] The QoS flow, DRB or logical channel of the at least one second terminal.

[0602] Optionally, in one implementation, the synchronization delay status report includes at least one of the following:

[0603] Time information of synchronization delay;

[0604] Buffer Status Report BSR related to the time information of synchronization delay;

[0605] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0606] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0607] It should be noted that all implementation methods in the above embodiments are applicable to the embodiments of the information acquisition method applied to the network device side, and can achieve the same technical effect, which will not be repeated here.

[0608] like Figure 4 As shown, the embodiment of the present application provides an information triggering device 400, which is applied to a first terminal and includes:

[0609] A triggering unit 401 is used to trigger a synchronization delay status report, where the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0610] The related streams include one or more of the following:

[0611] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0612] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0613] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0614] Optionally, the related streams are all sent through the first terminal, and the triggering unit 401 is configured to:

[0615] When the first condition is met, triggering the synchronization delay status report;

[0616] The first condition includes at least one of the following:

[0617] After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold;

[0618] After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent;

[0619] When data of the first target stream in the related stream is sent;

[0620] Data of a first target stream in the related streams arrives at the cache;

[0621] The data of the second target flow in the related flow arrives at the cache;

[0622] receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report;

[0623] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0624] Optionally, the first request message includes at least one of the following:

[0625] A group identifier of the related stream;

[0626] The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

[0627] Optionally, the relevant stream is sent through the first terminal and at least one second terminal, and the triggering unit 401 is configured to:

[0628] When the second condition is met, triggering the synchronization delay status report;

[0629] The second condition includes at least one of the following:

[0630] When data of the related stream in the first terminal is sent;

[0631] The data of the related flow in the first terminal arrives at a cache;

[0632] A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

[0633] Optionally, the second request message includes at least one of the following:

[0634] A group identifier of the related stream;

[0635] The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow;

[0636] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0637] Optionally, the trigger unit 401 is used to:

[0638] After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report;

[0639] The third condition includes at least one of the following:

[0640] A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent;

[0641] The second target stream in the related stream starts to be sent;

[0642] A PDU of a second target flow in the related flow is sent successfully;

[0643] A PDU set of a second target flow in the related flow is sent successfully;

[0644] The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold;

[0645] The first terminal has sent the synchronization delay status report to the network device;

[0646] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0647] Optionally, after the triggering unit 401 triggers the synchronization delay status report, the device further includes:

[0648] A first sending unit, configured to send a first message to a network device when a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, wherein the first message carries the synchronization delay status report;

[0649] The first message includes at least one of the following:

[0650] Radio Resource Control (RRC) signaling;

[0651] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0652] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0653] Radio link control protocol data unit RLC control PDU;

[0654] Media access control element MAC CE;

[0655] Physical layer signaling.

[0656] Optionally, the device further comprises:

[0657] A second receiving unit, configured to receive configuration information of the relevant flow sent by a network device or a core network device;

[0658] The configuration information includes at least one of the following:

[0659] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0660] The synchronization threshold of the related stream.

[0661] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0662] The relationship between business flows;

[0663] The relationship between Internet Protocol flows;

[0664] The relationship between QoS flows;

[0665] The association relationship between data radio bearers (DRBs);

[0666] The association relationship between logical channels LCH.

[0667] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0668] a QoS flow, a DRB or a logical channel carrying the related flow;

[0669] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0670] The target information includes at least one of the following:

[0671] an identifier of the at least one second terminal;

[0672] The QoS flow, DRB or logical channel of the at least one second terminal.

[0673] Optionally, the synchronization delay status report includes at least one of the following:

[0674] Time information of synchronization delay;

[0675] Buffer Status Report BSR related to the time information of synchronization delay;

[0676] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0677] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0678] It should be noted that the device embodiment is a device that corresponds one-to-one to the above-mentioned method embodiment. All implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0679] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0680] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0681] like Figure 5 As shown, the embodiment of the present application further provides a terminal, which is a first terminal, including a processor 500, a transceiver 510, a memory 520, and a program stored in the memory 520 and executable on the processor 500; wherein the transceiver 510 is connected to the processor 500 and the memory 520 through a bus interface, wherein the processor 500 is used to read the program in the memory and execute the following process:

[0682] Triggering a synchronization delay status report, where the synchronization delay status report is used to indicate a synchronization delay status of a related stream;

[0683] The related streams include one or more of the following:

[0684] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0685] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0686] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0687] The transceiver 510 is configured to receive and send data under the control of the processor 500 .

[0688] Among them, Figure 5In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 500 and various circuits of memory represented by memory 520 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 510 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 530 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0689] The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 can store data used by the processor 500 when performing operations.

[0690] Optionally, the processor 500 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0691] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0692] Optionally, the related streams are all sent through the first terminal, and the processor is configured to read a computer program in the memory and perform the following operations:

[0693] When the first condition is met, triggering the synchronization delay status report;

[0694] The first condition includes at least one of the following:

[0695] After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold;

[0696] After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent;

[0697] When data of the first target stream in the related stream is sent;

[0698] Data of a first target stream in the related streams arrives at the cache;

[0699] The data of the second target flow in the related flow arrives at the cache;

[0700] receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report;

[0701] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0702] Optionally, the first request message includes at least one of the following:

[0703] A group identifier of the related stream;

[0704] The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

[0705] Optionally, the relevant stream is sent through the first terminal and at least one second terminal, and the processor is configured to read the computer program in the memory and perform the following operations:

[0706] When the second condition is met, triggering the synchronization delay status report;

[0707] The second condition includes at least one of the following:

[0708] When data of the related stream in the first terminal is sent;

[0709] The data of the related flow in the first terminal arrives at a cache;

[0710] A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

[0711] Optionally, the second request message includes at least one of the following:

[0712] A group identifier of the related stream;

[0713] The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow;

[0714] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0715] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0716] After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report;

[0717] The third condition includes at least one of the following:

[0718] A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent;

[0719] The second target stream in the related stream starts to be sent;

[0720] A PDU of a second target flow in the related flow is sent successfully;

[0721] A PDU set of a second target flow in the related flow is sent successfully;

[0722] The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold;

[0723] The first terminal has sent the synchronization delay status report to the network device;

[0724] Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0725] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0726] When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report;

[0727] The first message includes at least one of the following:

[0728] Radio Resource Control (RRC) signaling;

[0729] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0730] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0731] Radio link control protocol data unit RLC control PDU;

[0732] Media access control element MAC CE;

[0733] Physical layer signaling.

[0734] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0735] Receiving, through a transceiver, configuration information of the related flow sent by a network device or a core network device;

[0736] The configuration information includes at least one of the following:

[0737] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0738] The synchronization threshold of the related stream.

[0739] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0740] The relationship between business flows;

[0741] The relationship between Internet Protocol flows;

[0742] The relationship between QoS flows;

[0743] The association relationship between data radio bearers (DRBs);

[0744] The association relationship between logical channels LCH.

[0745] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0746] a QoS flow, a DRB or a logical channel carrying the related flow;

[0747] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0748] The target information includes at least one of the following:

[0749] an identifier of the at least one second terminal;

[0750] The QoS flow, DRB or logical channel of the at least one second terminal.

[0751] Optionally, the synchronization delay status report includes at least one of the following:

[0752] Time information of synchronization delay;

[0753] Buffer Status Report BSR related to the time information of synchronization delay;

[0754] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0755] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0756] It should be noted here that the above-mentioned terminal provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0757] The embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the information triggering method applied to the first terminal. The processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), etc.), optical storage (such as a CD, a DVD, a BD, a HVD, etc.), and semiconductor storage (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid-state drive (SSD)), etc.

[0758] like Figure 6 As shown, the embodiment of the present application provides an information acquisition device 600, which is applied to a network device, including:

[0759] The first receiving unit 601 is used to receive a synchronization delay status report reported by the first terminal;

[0760] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0761] The relevant streams include one or more of the following:

[0762] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0763] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0764] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0765] Optionally, the first receiving unit 601 is configured to:

[0766] Receiving a first message sent by a first terminal, where the first message carries the synchronization delay status report;

[0767] The first message includes at least one of the following:

[0768] Radio Resource Control (RRC) signaling;

[0769] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0770] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0771] Radio link control protocol data unit RLC control PDU;

[0772] Media access control element MAC CE;

[0773] Physical layer signaling.

[0774] Optionally, the device further comprises:

[0775] A second sending unit, configured to send the configuration information of the related flow to the first terminal;

[0776] The configuration information includes at least one of the following:

[0777] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0778] The synchronization threshold of the related stream.

[0779] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0780] The relationship between business flows;

[0781] The relationship between Internet Protocol flows;

[0782] The relationship between QoS flows;

[0783] The association relationship between data radio bearers (DRBs);

[0784] The association relationship between logical channels LCH.

[0785] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0786] a QoS flow, a DRB or a logical channel carrying the related flow;

[0787] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0788] The target information includes at least one of the following:

[0789] an identifier of the at least one second terminal;

[0790] The QoS flow, DRB or logical channel of the at least one second terminal.

[0791] Optionally, the synchronization delay status report includes at least one of the following:

[0792] Time information of synchronization delay;

[0793] Buffer Status Report BSR related to the time information of synchronization delay;

[0794] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0795] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0796] It should be noted that the device embodiment is a device that corresponds one-to-one to the above-mentioned method embodiment. All implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0797] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0798] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0799] like Figure 7 As shown, the embodiment of the present application further provides a network device, including a processor 700, a transceiver 710, a memory 720, and a program stored in the memory 720 and executable on the processor 700; wherein the transceiver 710 is connected to the processor 700 and the memory 720 through a bus interface, wherein the processor 700 is used to read the program in the memory and execute the following process:

[0800] Receiving, by a transceiver, a synchronization delay status report reported by the first terminal;

[0801] Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow;

[0802] The relevant streams include one or more of the following:

[0803] Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoS flow ID;

[0804] The correlation between flows carried by different data radio bearers (DRBs) is indicated by the correlation between data radio bearer identifiers (DRB IDs);

[0805] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

[0806] The transceiver 710 is configured to receive and send data under the control of the processor 700 .

[0807] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 700 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 710 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including, these transmission media include wireless channels, wired channels, optical cables and other transmission media.

[0808] The processor 700 is responsible for managing the bus architecture and general processing, and the memory 720 can store data used by the processor 700 when performing operations.

[0809] Optionally, the processor 700 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0810] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0811] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0812] Receiving, by a transceiver, a first message sent by a first terminal, wherein the first message carries the synchronization delay status report;

[0813] The first message includes at least one of the following:

[0814] Radio Resource Control (RRC) signaling;

[0815] Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU;

[0816] Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU;

[0817] Radio link control protocol data unit RLC control PDU;

[0818] Media access control element MAC CE;

[0819] Physical layer signaling.

[0820] Optionally, the processor, for reading the computer program in the memory, further performs the following operations:

[0821] Sending the configuration information of the related flow to the first terminal through a transceiver;

[0822] The configuration information includes at least one of the following:

[0823] First indication information, where the first indication information is used to indicate an association relationship between the related flows;

[0824] The synchronization threshold of the related stream.

[0825] Optionally, the related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following:

[0826] The relationship between business flows;

[0827] The relationship between Internet Protocol flows;

[0828] The relationship between QoS flows;

[0829] The association relationship between data radio bearers (DRBs);

[0830] The association relationship between logical channels LCH.

[0831] Optionally, the related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following:

[0832] a QoS flow, a DRB or a logical channel carrying the related flow;

[0833] QoS flow, DRB or logical channel carrying the relevant flow, and target information;

[0834] The target information includes at least one of the following:

[0835] an identifier of the at least one second terminal;

[0836] The QoS flow, DRB or logical channel of the at least one second terminal.

[0837] Optionally, the synchronization delay status report includes at least one of the following:

[0838] Time information of synchronization delay;

[0839] Buffer Status Report BSR related to the time information of synchronization delay;

[0840] The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent;

[0841] The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

[0842] It should be noted here that the above-mentioned network device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0843] The embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the information acquisition method applied to a network device. The processor-readable storage medium may be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0844] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0845] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0846] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0847] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0848] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. An information triggering method, characterized in that: The method is executed by the first terminal and includes: Triggering a synchronization delay status report, where the synchronization delay status report is used to indicate a synchronization delay status of a related stream; The related streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoSflowID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

2. The method according to claim 1, characterized in that The related streams are all sent through the first terminal, and the triggering synchronization delay status report includes: When the first condition is met, triggering the synchronization delay status report; The first condition includes at least one of the following: After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold; After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent; When data of the first target stream in the related stream is sent; Data of a first target stream in the related streams arrives at the cache; The data of the second target flow in the related flow arrives at the cache; receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

3. The method according to claim 2, characterized in that The first request message includes at least one of the following: A group identifier of the related stream; The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

4. The method according to claim 1, characterized in that: The related stream is sent through the first terminal and at least one second terminal, and the triggering synchronization delay status report includes: When the second condition is met, triggering the synchronization delay status report; The second condition includes at least one of the following: When data of the related stream in the first terminal is sent; The data of the related flow in the first terminal arrives at a cache; A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

5. The method according to claim 4, characterized in that The second request message includes at least one of the following: A group identifier of the related stream; The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

6. The method according to claim 1, characterized in that The triggering synchronization delay status report includes: After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report; The third condition includes at least one of the following: A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent; The second target stream in the related stream starts to be sent; A PDU of a second target flow in the related flow is sent successfully; A PDU set of a second target flow in the related flow is sent successfully; The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold; The first terminal has sent the synchronization delay status report to the network device; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

7. The method according to any one of claims 1 to 6, characterized in that: After triggering the synchronization delay status report, the method further includes: When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report; The first message includes at least one of the following: Radio Resource Control (RRC) signaling; Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU; Packet Data Convergence Protocol Control Protocol Data Unit PDCP controlPDU; Radio link control protocol data unit RLC control PDU; Media access control element MAC CE; Physical layer signaling.

8. The method according to claim 1, characterized in that: Also includes: Receiving configuration information of the relevant flow sent by a network device or a core network device; The configuration information includes at least one of the following: First indication information, where the first indication information is used to indicate an association relationship between the related flows; The synchronization threshold of the related stream.

9. The method according to claim 8, characterized in that The related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following: The relationship between business flows; The relationship between Internet Protocol flows; The relationship between QoS flows; The association relationship between data radio bearers (DRBs); The association relationship between logical channels LCH.

10. The method according to claim 8, characterized in that The related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following: a QoS flow, a DRB or a logical channel carrying the related flow; QoS flow, DRB or logical channel carrying the relevant flow, and target information; The target information includes at least one of the following: an identifier of the at least one second terminal; The QoS flow, DRB or logical channel of the at least one second terminal.

11. The method according to any one of claims 1 to 10, characterized in that: The synchronization delay status report includes at least one of the following: Time information of synchronization delay; Buffer Status Report BSR related to the time information of synchronization delay; The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent; The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

12. A method for obtaining information, characterized in that: Performed by network devices, including: Receiving a synchronization delay status report reported by the first terminal; Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow; The relevant streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoSflowID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

13. The method according to claim 12, characterized in that The receiving a synchronization delay status report reported by the first terminal includes: Receiving a first message sent by a first terminal, where the first message carries the synchronization delay status report; The first message includes at least one of the following: Radio Resource Control (RRC) signaling; Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU; Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU; Radio link control protocol data unit RLC control PDU; Media access control element MAC CE; Physical layer signaling.

14. The method according to claim 12, characterized in that Also includes: Sending configuration information of the relevant flow to the first terminal; The configuration information includes at least one of the following: First indication information, where the first indication information is used to indicate an association relationship between the related flows; The synchronization threshold of the related stream.

15. The method according to claim 14, characterized in that The related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following: The relationship between business flows; The relationship between Internet Protocol flows; The relationship between QoS flows; The association relationship between data radio bearers (DRBs); The association relationship between logical channels LCH.

16. The method according to claim 14, characterized in that The related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following: a QoS flow, a DRB or a logical channel carrying the related flow; QoS flow, DRB or logical channel carrying the relevant flow, and target information; The target information includes at least one of the following: an identifier of the at least one second terminal; The QoS flow, DRB or logical channel of the at least one second terminal.

17. The method according to any one of claims 12 to 16, characterized in that: The synchronization delay status report includes at least one of the following: Time information of synchronization delay; Buffer Status Report BSR related to the time information of synchronization delay; The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent; The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

18. A terminal, the terminal being a first terminal, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Triggering a synchronization delay status report, where the synchronization delay status report is used to indicate a synchronization delay status of a related stream; The related streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the association between quality of service flow identifiers QoSflowID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

19. The terminal according to claim 18, characterized in that: The related streams are all sent through the first terminal, and the processor is used to read the computer program in the memory and perform the following operations: When the first condition is met, triggering the synchronization delay status report; The first condition includes at least one of the following: After the data of the first target stream in the related stream is sent, the data of the second target stream is not sent within a first time threshold; After the data of the first target stream in the related stream is sent, the remaining time for sending the second target stream is less than or equal to the second time threshold, and the remaining time=HT, where H represents the synchronization threshold value, and T represents the waiting time for sending the second target stream after the data of the first target stream is sent; When data of the first target stream in the related stream is sent; Data of a first target stream in the related streams arrives at the cache; The data of the second target flow in the related flow arrives at the cache; receiving a first request message sent by a network device, where the first request message is used to instruct the first terminal to report the synchronization delay status report; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

20. The terminal according to claim 19, characterized in that The first request message includes at least one of the following: A group identifier of the related stream; The identifier of the first target stream in the related streams for which the synchronization delay status report needs to be reported, and / or the identifier of the second target stream.

21. The terminal according to claim 18, characterized in that The relevant stream is sent through the first terminal and at least one second terminal, and the processor is used to read the computer program in the memory and perform the following operations: When the second condition is met, triggering the synchronization delay status report; The second condition includes at least one of the following: When data of the related stream in the first terminal is sent; The data of the related flow in the first terminal arrives at a cache; A second request message sent by a network device is received, where the second request message is used to instruct the first terminal to report the synchronization delay status report.

22. The terminal according to claim 21, characterized in that The second request message includes at least one of the following: A group identifier of the related stream; The identifier of the first target flow for which the synchronization delay status report needs to be reported, and / or the identifier of the second target flow; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

23. The terminal according to claim 18, characterized in that The processor is configured to read the computer program in the memory and perform the following operations: After the synchronization delay status report is triggered, if a third condition is met, canceling the triggered synchronization delay status report; The third condition includes at least one of the following: A packet data unit PDU or a packet data unit set PDU set in a first target flow in the related flow fails to be sent; The second target stream in the related stream starts to be sent; A PDU of a second target flow in the related flow is sent successfully; A PDU set of a second target flow in the related flow is sent successfully; The sending waiting time of the second target flow in the related flow is greater than or equal to the synchronization delay threshold; The first terminal has sent the synchronization delay status report to the network device; Among them, the first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

24. The terminal according to any one of claims 18 to 23, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: When a synchronization delay status report is triggered and the synchronization delay status report is not cancelled, sending a first message to a network device, wherein the first message carries the synchronization delay status report; The first message includes at least one of the following: Radio Resource Control (RRC) signaling; Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU; Packet Data Convergence Protocol Control Protocol Data Unit PDCP controlPDU; Radio link control protocol data unit RLC controlPDU; Media access control element MAC CE; Physical layer signaling.

25. The terminal according to claim 18, characterized in that The processor is configured to read the computer program in the memory and further perform the following operations: Receiving, through a transceiver, configuration information of the related flow sent by a network device or a core network device; The configuration information includes at least one of the following: First indication information, where the first indication information is used to indicate an association relationship between the related flows; The synchronization threshold of the related stream.

26. The terminal according to claim 25, characterized in that The related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following: The relationship between business flows; The relationship between Internet Protocol flows; The relationship between QoS flows; The association relationship between data radio bearers (DRBs); The association relationship between logical channels LCH.

27. The terminal according to claim 25, characterized in that The related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following: a QoS flow, a DRB or a logical channel carrying the related flow; QoS flow, DRB or logical channel carrying the relevant flow, and target information; The target information includes at least one of the following: an identifier of the at least one second terminal; The QoS flow, DRB or logical channel of the at least one second terminal.

28. The terminal according to any one of claims 18 to 27, characterized in that: The synchronization delay status report includes at least one of the following: Time information of synchronization delay; Buffer Status Report BSR related to the time information of synchronization delay; The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent; The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

29. A network device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Receiving, by a transceiver, a synchronization delay status report reported by the first terminal; Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow; The relevant streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the correlation between quality of service flow identifiers QoSflow ID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

30. The network device according to claim 29, characterized in that: The processor is configured to read the computer program in the memory and perform the following operations: Receiving, by a transceiver, a first message sent by a first terminal, wherein the first message carries the synchronization delay status report; The first message includes at least one of the following: Radio Resource Control (RRC) signaling; Service Data Adaptation Protocol Control Protocol Data Unit SDAP control PDU; Packet Data Convergence Protocol Control Protocol Data Unit PDCP control PDU; Radio link control protocol data unit RLC control PDU; Media access control element MAC CE; Physical layer signaling.

31. The network device according to claim 30, characterized in that: The processor is configured to read the computer program in the memory and further perform the following operations: Sending the configuration information of the related flow to the first terminal through a transceiver; The configuration information includes at least one of the following: First indication information, where the first indication information is used to indicate an association relationship between the related flows; The synchronization threshold of the related stream.

32. The network device according to claim 31, characterized in that: The related streams are all sent through the first terminal, and the first indication information is used to indicate at least one of the following: The relationship between business flows; The relationship between Internet Protocol flows; The relationship between QoS flows; The association relationship between data radio bearers (DRBs); The association relationship between logical channels LCH.

33. The network device according to claim 31, characterized in that The related stream is sent through the first terminal and at least one second terminal, and the first indication information is used to indicate at least one of the following: a QoS flow, a DRB or a logical channel carrying the related flow; QoS flow, DRB or logical channel carrying the relevant flow, and target information; The target information includes at least one of the following: an identifier of the at least one second terminal; The QoS flow, DRB or logical channel of the at least one second terminal.

34. The network device according to any one of claims 29 to 33, characterized in that: The synchronization delay status report includes at least one of the following: Time information of synchronization delay; Buffer Status Report BSR related to the time information of synchronization delay; The time information is used to indicate the remaining time for sending the second target flow, and the remaining time=HT, wherein H represents the synchronization threshold value, and T represents the waiting time for sending the second target flow after the data of the first target flow is sent; The first target stream is the first stream among the related streams that initiates data transmission, the second target stream is one or more streams among the related streams except the first target stream, and the transmission time of the data of the second target stream is after the transmission time of the data of the first target stream.

35. An information triggering device, applied to a first terminal, characterized in that: include: A triggering unit, used to trigger a synchronization delay status report, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related stream; The related streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the correlation between quality of service flow identifiers QoSflow ID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

36. An information acquisition device, applied to a network device, characterized in that: include: A first receiving unit, configured to receive a synchronization delay status report reported by a first terminal; Wherein, the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow; The relevant streams include one or more of the following: Flows carried by different quality of service flows QoS flows, the correlation between the flows is indicated by the correlation between quality of service flow identifiers QoSflow ID; The correlation between flows carried by different data radio bearers DRB is indicated by the association between data radio bearer identifiers DRBID; The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifiers LCID.

37. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 17.

Images