Information processing method and device and readable storage medium

Abstract

The invention discloses an information processing method and device and a readable storage medium, relates to the technical field of communication, and aims to guarantee synchronous transmission of uplink related streams. The method comprises the following steps: sending a synchronous time delay state report to network equipment through a user plane control message, wherein the synchronous time delay state report is used for indicating a synchronous time delay state of a related flow; wherein the related flow comprises one or more of the following items: flows borne by different QoS flows, and the correlation between the flows is indicated by the correlation between service quality flow identifiers; the streams are carried by different data radio bearers, and the correlation between the streams is indicated by the correlation between the data radio bearer identifiers; and the flow is carried by different logical channels, and the correlation between the flows is indicated by the correlation between the logical channel identifications. According to the embodiment of the invention, synchronous transmission of the uplink related flow can be ensured.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an information processing method, device and readable storage medium. Background Art

[0002] Related technologies introduce extended reality (eXtended Reality, XR) services. There are two basic ways to connect XR services to wireless networks: one is that all user devices are connected to a terminal (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. Among them, multimodal communication refers to services with different modes of input or output, such as input or output can be video / audio media; information from environmental sensors, such as brightness, temperature, humidity, etc.; tactile data: including perceptible pressure, texture, vibration, temperature; kinesthetic perception, such as gravity, tension; position perception, etc.

[0003] In multimodal communication, the services of related media units are expressed as different service flows in the wireless network, which can be expressed as IP flows (IP six), and then mapped to the quality of service (QoS) flows (QoS flows) that need to be transmitted by the access network. A notable feature of multimodal communication is the synchronization requirement between multimodal applications. However, in related technologies, QoS guarantees are only performed on a single flow. Therefore, how to ensure the synchronous transmission between different QoS flows is a technical problem that needs to be solved. Summary of the invention

[0004] The embodiments of the present application provide an information processing method, an apparatus, and a readable storage medium to ensure synchronous transmission of uplink related flows.

[0005] In a first aspect, an embodiment of the present application provides an information processing method, which is applied to a terminal, including:

[0006] Sending a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

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

[0008] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between the quality of service flow identifiers (QoS flowID);

[0009] 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);

[0010] The correlation between the flows carried by different logical channels is indicated by the association between logical channel identifications (LCIDs).

[0011] Optionally, the user plane control message includes one or more of the following:

[0012] Uplink Service Data Adaptation Protocol (SDAP) controls the Protocol Data Unit (PDU);

[0013] Uplink Packet Data Convergence Protocol (PDCP) controlPDU;

[0014] Uplink Radio Link Control (RLC) control PDU;

[0015] Uplink Medium Access Control (MAC) control element (CE).

[0016] Optionally, the user plane control message includes: time information of synchronization delay;

[0017] The time information of the synchronization delay includes any one of the following:

[0018] The data sending time of the first stream among the related streams;

[0019] The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent;

[0020] The time interval between the data sending time of the first flow and the time of triggering or sending the synchronization delay status report.

[0021] Optionally, the data sending time of the first stream includes:

[0022] an initial transmission time of a first packet data unit (PDU) of the first flow; or

[0023] The time when the first PDU of the first flow is successfully sent; or

[0024] The time when a packet data unit set (PDU set) of the first flow is sent successfully.

[0025] Optionally, if the user plane control message includes an uplink SDAP control PDU, the user plane control message further includes one or more of the following:

[0026] A flow identifier (QoS Flow Identifier, QFI) of the first flow;

[0027] A flow identifier QFI of the second flow;

[0028] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0029] Optionally, if the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following:

[0030] A flow identifier QFI of the first flow;

[0031] A flow identifier QFI of the second flow;

[0032] A data radio bearer identifier (DRB ID) of the first flow;

[0033] A data radio bearer identifier DRB ID of the second flow;

[0034] A logical channel identifier LCID of the first stream;

[0035] A logical channel identifier LCID of the second stream;

[0036] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0037] Optionally, if the user plane control message includes an uplink MAC CE, the user plane control message further includes one or more of the following:

[0038] Buffer Status Report (BSR) of the terminal buffer data volume;

[0039] Information about the first stream;

[0040] information of the second stream;

[0041] The information of the related stream group is used to indicate a group of related streams.

[0042] Optionally, the amount of data indicated by the BSR includes any one of the following:

[0043] The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report;

[0044] The amount of cached data of the first flow and / or the second flow in the terminal cache;

[0045] The amount of cached data of the PDUset of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report;

[0046] The data volume of the DRB or logical channel (Logical Channel, LCH) carrying the first flow and / or the second flow;

[0047] The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

[0048] Optionally, the information of the first stream includes any of the following:

[0049] the QFI of the first stream;

[0050] The DRB ID of the first flow;

[0051] The LCID of the first stream;

[0052] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0053] and / or

[0054] The information of the second stream includes any of the following:

[0055] the QFI of the second stream;

[0056] The DRB ID of the second flow;

[0057] the LCID of the second stream;

[0058] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0059] Optionally, the method further comprises one or more of the following steps:

[0060] Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report;

[0061] Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following:

[0062] Related information of related streams;

[0063] Synchronization delay threshold;

[0064] Whether to allow the terminal to feedback synchronization delay status report;

[0065] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0066] Information about the relevant stream groups that trigger the synchronization delay status report;

[0067] Protocol layer configuration information for carrying synchronization delay status reports;

[0068] Trigger conditions for synchronization delay status reporting.

[0069] Optionally, the request message includes one or more of the following:

[0070] Downlink SDAP control PDU;

[0071] Downlink PDCP control PDU;

[0072] Downlink RLC control PDU;

[0073] Downlink MAC CE.

[0074] Optionally, the downlink SDAP control PDU includes one or more of the following:

[0075] The stream identifier QFI of the first stream among the related streams;

[0076] The stream identifier QFI of the second stream in the related streams;

[0077] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0078] Optionally, the downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following:

[0079] The QFI of the first of the related streams;

[0080] The QFI of the second stream in the related stream;

[0081] The DRB ID of the first flow;

[0082] The DRB ID of the second flow;

[0083] The LCID of the first stream;

[0084] the LCID of the second stream;

[0085] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0086] Optionally, the downlink MAC CE includes one or more of the following:

[0087] Information about the first stream in the related streams;

[0088] Information about the second stream in the related stream;

[0089] The information of the related stream group is used to indicate a group of related streams.

[0090] Optionally, the information of the first stream includes any of the following:

[0091] the QFI of the first stream;

[0092] The DRB ID of the first flow;

[0093] The LCID of the first stream;

[0094] an identifier of a logical channel group (LCG ID) to which the logical channel of the first stream belongs;

[0095] and / or

[0096] The information of the second stream includes any of the following:

[0097] the QFI of the second stream;

[0098] The DRB ID of the second flow;

[0099] the LCID of the second stream;

[0100] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0101] In a second aspect, an embodiment of the present application provides an information processing method, which is applied to a network device, including:

[0102] Receiving a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0103] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0105] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0106] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0107] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0108] Optionally, the user plane control message includes one or more of the following:

[0109] Uplink SDAP control PDU;

[0110] Uplink PDCP control PDU;

[0111] Uplink RLC control PDU;

[0112] Uplink MAC CE.

[0113] Optionally, the user plane control message includes: time information of synchronization delay;

[0114] The time information of the synchronization delay includes any one of the following:

[0115] The data sending time of the first flow among the related flows;

[0116] The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent;

[0117] The time interval between the time when the data of the first flow is sent and the time when the synchronization delay status report is triggered or sent.

[0118] Optionally, the data sending time of the first stream includes:

[0119] the initial transmission time of the first PDU of the first flow; or

[0120] The time when the first PDU of the first flow is successfully sent; or

[0121] The time when a PDU set of the first flow is successfully sent.

[0122] Optionally, if the user plane control message includes an uplink SDAP control PDU, the user plane control message further includes one or more of the following:

[0123] A flow identifier QFI of the first flow;

[0124] A flow identifier QFI of the second flow;

[0125] The information of the related flow group is used to indicate a group of related QoS flows.

[0126] Optionally, if the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following:

[0127] A flow identifier QFI of the first flow;

[0128] A flow identifier QFI carrying the second flow;

[0129] DRB identifier DRB ID of the first flow;

[0130] DRB identifier DRB ID of the second flow;

[0131] A logical channel identifier LCID of the first stream;

[0132] An identifier LCID of a logical channel of the second stream;

[0133] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0134] Optionally, if the user plane control message includes a MAC CE, the user plane control message further includes one or more of the following:

[0135] Terminal buffer data volume BSR;

[0136] Information about the first stream;

[0137] information of the second stream;

[0138] The information of the related stream group is used to indicate a group of related streams.

[0139] Optionally, the amount of data indicated by the BSR includes any one of the following:

[0140] The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report;

[0141] The amount of cached data of the PDUset of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report;

[0142] The amount of cached data of the first flow and / or the second flow in the terminal cache;

[0143] the data volume of the DRB or logical channel carrying the first flow and / or the second flow;

[0144] The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

[0145] Optionally, the information of the first stream includes any of the following:

[0146] the QFI of the first stream;

[0147] The DRB ID of the first flow;

[0148] The LCID of the first stream;

[0149] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0150] and / or

[0151] The information of the second stream includes any of the following:

[0152] the QFI of the second stream;

[0153] The DRB ID of the second flow;

[0154] the LCID of the second stream;

[0155] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0156] Optionally, the method further comprises one or more of the following steps:

[0157] Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal;

[0158] Sending configuration information to the terminal, wherein the configuration information includes one or more of the following:

[0159] Related information of related streams;

[0160] Synchronization delay threshold;

[0161] Whether to allow the terminal to feedback synchronization delay status report;

[0162] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0163] Information about the relevant stream groups that trigger the synchronization delay status report;

[0164] Protocol layer configuration information for carrying synchronization delay status reports;

[0165] Trigger conditions for synchronization delay status reporting.

[0166] Optionally, the request message includes one or more of the following:

[0167] Downlink SDAP control PDU;

[0168] Downlink PDCP control PDU;

[0169] Downlink RLC control PDU;

[0170] Downlink MAC CE.

[0171] Optionally, the downlink SDAP control PDU includes one or more of the following:

[0172] The stream identifier QFI of the first stream among the related streams;

[0173] The stream identifier QFI of the second stream in the related streams;

[0174] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0175] Optionally, the downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following:

[0176] The QFI of the first of the related streams;

[0177] The QFI of the second stream in the related stream;

[0178] The DRB ID of the first flow;

[0179] The DRB ID of the second flow;

[0180] The LCID of the first stream;

[0181] the LCID of the second stream;

[0182] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0183] Optionally, the downlink MAC CE includes one or more of the following:

[0184] Information about the first stream;

[0185] information of the second stream;

[0186] The information of the related stream group is used to indicate a group of related streams.

[0187] Optionally, the information of the first stream includes any of the following:

[0188] the QFI of the first stream;

[0189] The DRB ID of the first flow;

[0190] The LCID of the first stream;

[0191] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0192] and / or

[0193] The information of the second stream includes any of the following:

[0194] the QFI of the second stream;

[0195] The DRB ID of the second flow;

[0196] the LCID of the second stream;

[0197] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0198] In a third aspect, an embodiment of the present application provides an information processing device, applied to a terminal, including: a memory, a transceiver, and a processor:

[0199] 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:

[0200] Sending a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

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

[0202] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0203] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0204] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0205] Optionally, the user plane control message includes one or more of the following:

[0206] Uplink SDAP control PDU;

[0207] Uplink PDCP control PDU;

[0208] Uplink RLC control PDU;

[0209] Uplink MAC CE.

[0210] Optionally, the user plane control message includes: time information of synchronization delay;

[0211] The time information of the synchronization delay includes any one of the following:

[0212] The data sending time of the first stream among the related streams;

[0213] The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent;

[0214] The time interval between the data sending time of the first flow and the time of triggering or sending the synchronization delay status report.

[0215] Optionally, the data sending time of the first stream includes:

[0216] the initial transmission time of the first PDU of the first flow; or

[0217] The time when the first PDU of the first flow is successfully sent; or

[0218] The time when a PDU set of the first flow is successfully sent.

[0219] Optionally, if the user plane control message includes an uplink SDAP control PDU, the user plane control message further includes one or more of the following:

[0220] A flow identifier QFI of the first flow;

[0221] A flow identifier QFI of the second flow;

[0222] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0223] Optionally, if the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following:

[0224] A flow identifier QFI of the first flow;

[0225] A flow identifier QFI of the second flow;

[0226] A data radio bearer identifier (DRB ID) of the first flow;

[0227] A data radio bearer identifier DRB ID of the second flow;

[0228] A logical channel identifier LCID of the first stream;

[0229] A logical channel identifier LCID of the second stream;

[0230] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0231] Optionally, if the user plane control message includes an uplink MAC CE, the user plane control message further includes one or more of the following:

[0232] Terminal cache data volume cache status report BSR;

[0233] Information about the first stream;

[0234] information of the second stream;

[0235] The information of the related stream group is used to indicate a group of related streams.

[0236] Optionally, the amount of data indicated by the BSR includes any one of the following:

[0237] The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report;

[0238] The amount of cached data of the first flow and / or the second flow in the terminal cache;

[0239] The amount of cached data of the PDUset of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report;

[0240] the data volume of the DRB or logical channel carrying the first flow and / or the second flow;

[0241] The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

[0242] Optionally, the information of the first stream includes any of the following:

[0243] the QFI of the first stream;

[0244] The DRB ID of the first flow;

[0245] The LCID of the first stream;

[0246] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0247] and / or

[0248] The information of the second stream includes any of the following:

[0249] the QFI of the second stream;

[0250] The DRB ID of the second flow;

[0251] the LCID of the second stream;

[0252] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0253] Optionally, the processor is further configured to read the computer program in the memory and perform one or more of the following operations:

[0254] Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report;

[0255] Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following:

[0256] Related information of related streams;

[0257] Synchronization delay threshold;

[0258] Whether to allow the terminal to feedback synchronization delay status report;

[0259] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0260] Information about the relevant stream groups that trigger the synchronization delay status report;

[0261] Protocol layer configuration information for carrying synchronization delay status reports;

[0262] Trigger conditions for synchronization delay status reporting.

[0263] Optionally, the request message includes one or more of the following:

[0264] Downlink SDAP control PDU;

[0265] Downlink PDCP control PDU;

[0266] Downlink RLC control PDU;

[0267] Downlink MAC CE.

[0268] Optionally, the downlink SDAP control PDU includes one or more of the following:

[0269] The stream identifier QFI of the first stream among the related streams;

[0270] The stream identifier QFI of the second stream in the related streams;

[0271] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0272] Optionally, the downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following:

[0273] The QFI of the first of the related streams;

[0274] The QFI of the second stream in the related stream;

[0275] The DRB ID of the first flow;

[0276] The DRB ID of the second flow;

[0277] The LCID of the first stream;

[0278] the LCID of the second stream;

[0279] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0280] Optionally, the downlink MAC CE includes one or more of the following:

[0281] Information about the first stream in the related streams;

[0282] Information about the second stream in the related stream;

[0283] The information of the related stream group is used to indicate a group of related streams.

[0284] Optionally, the information of the first stream includes any of the following:

[0285] the QFI of the first stream;

[0286] The DRB ID of the first flow;

[0287] The LCID of the first stream;

[0288] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0289] and / or

[0290] The information of the second stream includes any of the following:

[0291] the QFI of the second stream;

[0292] The DRB ID of the second flow;

[0293] the LCID of the second stream;

[0294] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0295] In a fourth aspect, an embodiment of the present application provides an information processing device, which is applied to a network device, including: a memory, a transceiver, and a processor:

[0296] 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:

[0297] Receiving a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0298] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0300] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0301] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0302] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0303] Optionally, the user plane control message includes one or more of the following:

[0304] Uplink SDAP control PDU;

[0305] Uplink PDCP control PDU;

[0306] Uplink RLC control PDU;

[0307] Uplink MAC CE.

[0308] Optionally, the user plane control message includes: time information of synchronization delay;

[0309] The time information of the synchronization delay includes any one of the following:

[0310] The data sending time of the first flow among the related flows;

[0311] The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent;

[0312] The time interval between the time when the data of the first flow is sent and the time when the synchronization delay status report is triggered or sent.

[0313] Optionally, the data sending time of the first stream includes:

[0314] the initial transmission time of the first PDU of the first flow; or

[0315] The time when the first PDU of the first flow is successfully sent; or

[0316] The time when a PDU set of the first flow is successfully sent.

[0317] Optionally, if the user plane control message includes an uplink SDAP control PDU, the user plane control message further includes one or more of the following:

[0318] A flow identifier QFI of the first flow;

[0319] A flow identifier QFI of the second flow;

[0320] The information of the related flow group is used to indicate a group of related QoS flows.

[0321] Optionally, if the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following:

[0322] A flow identifier QFI of the first flow;

[0323] A flow identifier QFI carrying the second flow;

[0324] DRB identifier DRB ID of the first flow;

[0325] DRB identifier DRB ID of the second flow;

[0326] A logical channel identifier LCID of the first stream;

[0327] An identifier LCID of a logical channel of the second stream;

[0328] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0329] Optionally, if the user plane control message includes a MAC CE, the user plane control message further includes one or more of the following:

[0330] Terminal buffer data volume BSR;

[0331] Information about the first stream;

[0332] information of the second stream;

[0333] The information of the related stream group is used to indicate a group of related streams.

[0334] Optionally, the amount of data indicated by the BSR includes any one of the following:

[0335] The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report;

[0336] The amount of cached data of the PDUset of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report;

[0337] The amount of cached data of the first flow and / or the second flow in the terminal cache;

[0338] the data volume of the DRB or logical channel carrying the first flow and / or the second flow;

[0339] The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

[0340] Optionally, the information of the first stream includes any of the following:

[0341] the QFI of the first stream;

[0342] The DRB ID of the first flow;

[0343] The LCID of the first stream;

[0344] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0345] and / or

[0346] The information of the second stream includes any of the following:

[0347] the QFI of the second stream;

[0348] The DRB ID of the second flow;

[0349] the LCID of the second stream;

[0350] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0351] Optionally, the processor is further configured to read the computer program in the memory and perform one or more of the following operations:

[0352] Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal;

[0353] Sending configuration information to the terminal, wherein the configuration information includes one or more of the following:

[0354] Related information of related streams;

[0355] Synchronization delay threshold;

[0356] Whether to allow the terminal to feedback synchronization delay status report;

[0357] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0358] Information about the relevant stream groups that trigger the synchronization delay status report;

[0359] Protocol layer configuration information for carrying synchronization delay status reports;

[0360] Trigger conditions for synchronization delay status reporting.

[0361] Optionally, the request message includes one or more of the following:

[0362] Downlink SDAP control PDU;

[0363] Downlink PDCP control PDU;

[0364] Downlink RLC control PDU;

[0365] Downlink MAC CE.

[0366] Optionally, the downlink SDAP control PDU includes one or more of the following:

[0367] The stream identifier QFI of the first stream among the related streams;

[0368] The stream identifier QFI of the second stream in the related streams;

[0369] The identifier of the related flow group is used to indicate a group of related QoS flows.

[0370] Optionally, the downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following:

[0371] The QFI of the first of the related streams;

[0372] The QFI of the second stream in the related stream;

[0373] The DRB ID of the first flow;

[0374] The DRB ID of the second flow;

[0375] The LCID of the first stream;

[0376] the LCID of the second stream;

[0377] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

[0378] Optionally, the downlink MAC CE includes one or more of the following:

[0379] Information about the first stream;

[0380] information of the second stream;

[0381] The information of the related stream group is used to indicate a group of related streams.

[0382] Optionally, the information of the first stream includes any of the following:

[0383] the QFI of the first stream;

[0384] The DRB ID of the first flow;

[0385] The LCID of the first stream;

[0386] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0387] and / or

[0388] The information of the second stream includes any of the following:

[0389] the QFI of the second stream;

[0390] The DRB ID of the second flow;

[0391] the LCID of the second stream;

[0392] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0393] In a fifth aspect, an embodiment of the present application provides an information processing device, applied to a terminal, including:

[0394] A first sending unit, configured to send a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

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

[0396] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0397] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0398] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0399] In a sixth aspect, an embodiment of the present application provides an information processing device, applied to a network device, including:

[0400] A first receiving unit, configured to receive a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0401] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0403] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0404] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0405] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0406] In a seventh aspect, an embodiment of the present application further provides a processor-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in the information processing method as described above are implemented.

[0407] In an embodiment of the present application, the terminal sends a synchronization delay status report to the network device, where the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow, so that the network device can perform targeted scheduling to ensure the synchronous transmission of the uplink relevant flow. BRIEF DESCRIPTION OF THE DRAWINGS

[0408] Figure 1It is one of the flow charts of the information processing method provided in the embodiment of the present application;

[0409] Figure 2 is a schematic diagram of synchronization delay information in an embodiment of the present application;

[0410] Figure 3 This is the second flowchart of the information processing method provided in the embodiment of the present application;

[0411] FIG4( a ) is a schematic diagram of the SDAP control PDU format carrying the SDSR request;

[0412] FIG4( b ) is a schematic diagram of the format of the SDAP control PDU carrying the SDSR;

[0413] FIG5( a ) is a schematic diagram of the PDCP control PDU format carrying the SDSR request;

[0414] FIG5( b ) is a schematic diagram of the format of a PDCP control PDU carrying SDSR;

[0415] FIG6( a ) is a schematic diagram of the RLC control PDU format carrying the SDSR request;

[0416] FIG6( b ) is a schematic diagram of the RLC control PDU format carrying SDSR;

[0417] FIG7( a ) is a schematic diagram of an uplink MAC CE;

[0418] FIG7( b ) is a schematic diagram of a downlink MAC CE;

[0419] Figure 8 It is one of the structural diagrams of the information processing device provided in the embodiment of the present application;

[0420] Fig. 9 This is the second structural diagram of the information processing device provided in the embodiment of the present application;

[0421] Fig.10 This is the third structural diagram of the information processing device provided in the embodiment of the present application;

[0422] Fig.11 This is the fourth structural diagram of the information processing device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0423] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: 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.

[0424] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0425] 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 only 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.

[0426] The embodiments of the present application provide an information processing method and device to ensure synchronous transmission of uplink related flows.

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

[0428] See also Figure 1 , Figure 1 is a flowchart of an information processing method provided in an embodiment of the present application, which is applied to a terminal, such as Figure 1 As shown, the following steps are included:

[0429] Step 101: Send a synchronization delay status report (SDSR) to a network device through a user plane control message, where the synchronization delay status report is used to indicate the synchronization delay status of a related flow;

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

[0431] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0432] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0433] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0434] The above-mentioned streams may include service streams, IP streams, data streams, etc. Related streams may be multiple streams transmitted at one terminal, or multiple streams transmitted at different terminals, and the streams with synchronization requirements are related streams. For example, the services of related media units in multimodal communication are presented as different service flows in a wireless network, which may be presented as IP flows, and then mapped to QoS flows to be transmitted by the access network. Ensuring the synchronous transmission of related streams specifically means that the transmission time difference of the related stream data is lower than the synchronization threshold requirement.

[0435] Among them, the association between QoS flow IDs, or the association between DRB IDs, or the association between LCIDs can be set according to actual needs.

[0436] The user plane control message includes one or more of the following:

[0437] Uplink SDAP control PDU;

[0438] Uplink PDCP control PDU;

[0439] Uplink RLC control PDU;

[0440] Uplink MAC CE.

[0441] When the user plane control message is different from the above messages, the included contents may be different.

[0442] 1. The user plane control message includes the uplink SDAP control PDU:

[0443] 1. Time information of synchronization delay; among them, combined with Figure 2 , the time information of the synchronization delay includes any one of the following:

[0444] a. The data sending time TI of the first flow in the related flows may include: the initial sending time of the first PDU of the first flow; or the time when the first PDU of the first flow is successfully sent; or the time when a packet data unit set PDU set of the first flow is successfully sent.

[0445] b. The remaining time T2 for data transmission of the second stream in the related stream, wherein the remaining time for data transmission is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time that the second stream waits to transmit after the data of the first stream is transmitted; wherein the judgment criterion after the data of the first stream is transmitted is any one of the data transmission time of the first stream. That is, after the data of the first stream is transmitted can refer to after the initial transmission time of the first PDU of the first stream, or after the time when the first PDU of the first stream is successfully transmitted, or after the time when a PDU set of the first stream is successfully transmitted.

[0446] c. The time interval T3 between the data sending time of the first flow and the time of triggering or sending the synchronization delay status report.

[0447] Among them, T1 is an absolute time value, T2 and T3 are time lengths, and the reference time of T2 and T3 can be: the time point of the initial transmission of the synchronization delay information report; or the reference time value carried in the synchronization delay report message; or a specified time point, such as the frame boundary of the system frame where the resource transmitting the synchronization delay report information is located. T2 and T3 are reported in absolute values, in units of ms or time slots; or, in quantized values. For example, for 0-15ms, 3 quantized values ​​are used, each value represents a 5ms range, 01 represents 0-5ms, 10 represents 5-10ms, and 11 represents 10-15ms.

[0448] 2. A flow identifier QFI of the first flow;

[0449] 3. A flow identifier QFI of the second flow;

[0450] 4. An identifier of a related flow group, which is used to indicate a group of related QoS flows, such as a commonID.

[0451] Among them, the above 2 to 4 or any combination thereof are optional.

[0452] 2. The user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU:

[0453] 1. Time information of synchronization delay: its meaning can refer to the above description.

[0454] 2. A flow identifier QFI of the first flow;

[0455] 3. A flow identifier QFI of the second flow;

[0456] 4. DRB ID of the first flow;

[0457] 5. DRB ID of the second flow;

[0458] 6. The LCID of the first stream;

[0459] 7. The LCID of the second stream;

[0460] 8. An identifier of a related flow group, where the identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels, such as a common ID or a DRB (Data Radio Bearer) Group ID.

[0461] Among them, the above 2 to 8 or any combination thereof are optional.

[0462] 3. The user plane control message includes an uplink MAC CE:

[0463] 1. Time information of synchronization delay: its meaning can refer to the above description.

[0464] 2. The terminal buffer data volume BSR, the data volume indicated by the BSR includes any of the following:

[0465] The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report;

[0466] The amount of cached data of the first flow and / or the second flow in the terminal cache;

[0467] The amount of cached data of the PDUset of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report;

[0468] the data volume of the DRB or logical channel carrying the first flow and / or the second flow;

[0469] The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

[0470] 3. The information of the first stream includes any of the following:

[0471] the QFI of the first stream;

[0472] The DRB ID of the first flow;

[0473] The LCID of the first stream;

[0474] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0475] 4. The information of the second stream includes any of the following:

[0476] the QFI of the second stream;

[0477] The DRB ID of the second flow;

[0478] the LCID of the second stream;

[0479] The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

[0480] 5. Information about a related stream group, where the information about the related stream group is used to indicate a group of related streams, such as a common ID or a DRB Group ID or a logical channel group number LCG (Logical Channel Group).

[0481] Among them, a MAC CE contains synchronization delay information of one or more related flows, and each synchronization delay information value corresponds to: the delay information of a group of related logical channels, or the delay information of two related packet data packets PDU (Packet Data Unit); or the synchronization delay information of two related packet data packet groups PDU set.

[0482] Among them, the above 2 to 5 or any combination thereof are optional.

[0483] In an embodiment of the present application, the terminal sends a synchronization delay status report to the network device, where the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow, so that the network device can perform targeted scheduling to ensure the synchronous transmission of the uplink relevant flow.

[0484] Optionally, the embodiment of the present application further includes one or more of the following steps:

[0485] receiving a request message (SDSR request) sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report;

[0486] Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following:

[0487] Related information of related streams;

[0488] Synchronization delay threshold;

[0489] Whether to allow the terminal to feedback synchronization delay status report;

[0490] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0491] Information about the relevant stream groups that trigger the synchronization delay status report;

[0492] Protocol layer configuration information for carrying synchronization delay status reports;

[0493] Trigger conditions for synchronization delay status reporting.

[0494] Corresponding to the user plane control message, the request message includes one or more of the following:

[0495] Downlink SDAP control PDU;

[0496] Downlink PDCP control PDU;

[0497] Downlink RLC control PDU;

[0498] Downlink MAC CE.

[0499] When the request message is different from the above messages, the included contents may be different.

[0500] 1. Downlink SDAP control PDU, including one or more of the following:

[0501] The stream identifier QFI of the first stream among the related streams;

[0502] The stream identifier QFI of the second stream in the related streams;

[0503] The identifier of the related flow group is used to indicate a group of related QoS flows, such as commonID.

[0504] 2. The downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following:

[0505] The QFI of the first of the related streams;

[0506] The QFI of the second stream in the related stream;

[0507] The DRB ID of the first flow;

[0508] The DRB ID of the second flow;

[0509] The LCID of the first stream;

[0510] the LCID of the second stream;

[0511] The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels, such as a common ID or a DRB Group ID or a logical channel group number LCG (Logical Channel Group).

[0512] 3. The downlink MAC CE includes one or more of the following:

[0513] Information about the first stream in the related streams, including any of the following:

[0514] A flow identifier QFI of the first flow;

[0515] The DRB ID of the first flow;

[0516] The LCID of the first stream;

[0517] An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs;

[0518] Information about the second stream in the related stream, including any of the following:

[0519] A flow identifier QFI of the second flow;

[0520] The DRB ID of the second flow;

[0521] the LCID of the second stream;

[0522] The information of the related stream group is used to indicate a group of related streams, such as a common ID or a DRBGroup ID or a logical channel group number LCG.

[0523] It should be noted that the embodiments of the present application mainly use the example that the related stream includes two streams to illustrate the provided information processing method. The related stream may include multiple streams. The information processing method between the multiple streams may refer to the information processing method between the two streams, or the information processing method between any two streams in the multiple streams is the same as the information processing method between the two streams disclosed in the embodiments of the present application. In the embodiments of the present application, there is no limitation on the number of streams included in the related streams, and the information processing method provided in the embodiments of the present application may also be directly applied to the information processing method for multiple streams.

[0524] See also Figure 3 , Figure 3 is a flowchart of an information processing method provided in an embodiment of the present application, which is applied to a network device (such as a base station, etc.), such as Figure 3As shown, the following steps are included:

[0525] Step 301: receiving a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0526] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0528] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0529] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0530] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0531] Among them, the explanation and meaning of the relevant flow and user plane control message can refer to the description of the aforementioned method embodiment.

[0532] Optionally, in the embodiment of the present application, the network device may further include one or more of the following steps:

[0533] Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal;

[0534] Sending configuration information to the terminal, wherein the configuration information includes one or more of the following:

[0535] Related information of related streams;

[0536] Synchronization delay threshold;

[0537] Whether to allow the terminal to feedback synchronization delay status report;

[0538] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0539] Information about the relevant stream groups that trigger the synchronization delay status report;

[0540] Protocol layer configuration information for carrying synchronization delay status reports;

[0541] Trigger conditions for synchronization delay status reporting.

[0542] Among them, the interpretation and meaning of the request message can refer to the description of the aforementioned method embodiment.

[0543] In an embodiment of the present application, the terminal sends a synchronization delay status report to the network device, where the synchronization delay status report is used to indicate the synchronization delay status of the relevant flow, so that the network device can perform targeted scheduling to ensure the synchronous transmission of the uplink relevant flow.

[0544] The specific implementation process of the embodiments of the present application is described in detail below in combination with different embodiments.

[0545] In the embodiment of the present application, SDAP control PDU is used to carry SDSR. The process may include:

[0546] Step 401: Send SDSR-related configuration information to the terminal, where the configuration information includes one or more of the following: association information of related flows; synchronization delay threshold: whether the terminal is allowed to feedback SDSR; QoS flow ID that triggers SDSR; identifier of the related flow group that triggers SDSR; protocol layer configuration that carries SDSR; and SDSR triggering conditions.

[0547] Step 402: Send an SDAP control PDU of an SDSR request to the terminal. The content of the SDAP control PDU can refer to the description of the above embodiment. This step is optional.

[0548] The SDAP control PDU of the SDSR request may include one or more of the following: the number QFI1 of the first flow; the number QFI2 of the second flow; an identifier of a related flow group, which is used to indicate a related flow group number of a group of related QoS flows.

[0549] As shown in Figure 4(a), it is a schematic diagram of the format of an SDAP control PDU carrying an SDSR request. In Figure 4(a), only QFI1 is included as an example:

[0550] D / C field: indicates whether it corresponds to SDAP data PDU or SDAP control PDU;

[0551] T field: indicates the SDAP control PDU type. If more types of SDAP control PDUs need to be introduced later, the length of the T field can be extended. The specific value of the T field in the figure is used to indicate that the subsequent corresponding SDSR request SDAP control PDU is a SDSR request SDAP control PDU. If there is only one type of downlink SDAP control PDU, there may be no T field, and this position is used as a reserved field R field;

[0552] QFI1: QoS flow number corresponding to the first flow in the related flows.

[0553] If the SDAP control PDU needs to include one or more of QFI2 and the identifier of the related flow group, the corresponding field can be added.

[0554] Step 403: The terminal receives the configuration information related to the SDSR, and determines whether to allow the sending of the SDSR and its corresponding configuration information according to the configuration information.

[0555] Step 404: The terminal receives the SDSR request message sent by the base station, and determines, based on the information carried in the request message, for which relevant flow the SDSR is to be sent. This step is optional.

[0556] Step 405: According to the request of step 402, or based on the SDSR triggering condition configured in step 401, after the triggering condition is met and the SDSR is triggered, an SDAP control PDU is sent to the base station side, and the SDAP control PDU includes:

[0557] Synchronization delay information;

[0558] The relevant flow identifier corresponding to the synchronization delay information is one of the following items or a combination thereof: the number QFI1 of the first flow, the number QFI2 of the second flow, and the identifier of the relevant flow group (such as common ID).

[0559] As shown in Figure 4(b), it is a schematic diagram of the format of an SDAP control PDU carrying SDSR. In Figure 4(b), only QFI1 and synchronization delay information are included as an example.

[0560] D / C field: indicates whether it corresponds to SDAP data PDU or SDAP control PDU;

[0561] T field: indicates the SDAP control PDU type. If more types of SDAP control PDU are introduced later, the length of the T field can be extended. The specific value of the T field in the diagram is used to indicate that the subsequent corresponding SDSR SDAP control PDU;

[0562] QFI1: QoS flow number corresponding to the first flow in the synchronization flow;

[0563] Synchronization delay information: Specific synchronization delay status reporting value.

[0564] If the SDAP control PDU needs to include one or more of QFI2 and the identifier of the related flow group, the corresponding field can be added.

[0565] Step 406: The base station receives the SDAP control PDU sent by the terminal.

[0566] Step 407: The base station schedules the transmission of related stream data according to the SDAP control PDU sent by the terminal.

[0567] Specifically: the base station determines the remaining time for sending data packets in the relevant flow according to the synchronization delay information in the SDAP control PDU (if the data packets of the relevant flow are not sent within the remaining time, the synchronization delay threshold of the relevant flow is exceeded); before the remaining time exceeds, the base station allocates uplink resources to the terminal to send data packets of the relevant flow.

[0568] In the embodiment of the present application, PDCP control PDU is used to carry SDSR. The process may include:

[0569] Step 501: Send SDSR-related configuration information to the terminal, where the configuration information includes one or more of the following: association information of related flows; synchronization delay threshold: whether the terminal is allowed to feedback SDSR; QoS flow ID that triggers SDSR; identifier of the related flow group that triggers SDSR; protocol layer configuration that carries SDSR; and SDSR triggering conditions.

[0570] Step 502: Send a PDCP control PDU of a SDSR request to the terminal. The content of the PDCP control PDU can refer to the description of the above embodiment. This step is optional.

[0571] As shown in Figure 5(a), it is a schematic diagram of the format of a PDCP control PDU carrying an SDSR request. In Figure 5(a), in the PDCP control PDU of the SDSR request: there may be only a PDCP control PDU type identifier, indicating that the PDCP control PDU is used for the SDSR request; it may also further include related flow information, namely one or more of the following: the number QFI1 of the first flow, the number QFI2 of the second flow, and the identifier of the related flow group, which is used to indicate the related flow group number of a group of related flows (such as common ID or DRB Group ID). The following is an SDSR request PDCP control PDU with only a PDCP control PDU type identifier, in which:

[0572] D / C field: indicates whether it corresponds to PDCP data PDU or PDCP control PDU;

[0573] PDU type: PDU (Protocol Data Unit) type indication, its specific value is used to indicate that the current PDCP control PDU is used for SDSR request.

[0574] In this format, the terminal uses the uplink DRB corresponding to the downlink DRB carrying the PDCP control PDU as the uplink DRB for feedback SDSR, and the feedback content is the relevant flow synchronization delay information of the uplink data flow carried in the uplink DRB.

[0575] If the PDCP control PDU needs to include one or more of QFI1, QFI2, and the identifier of the relevant flow group, the corresponding field needs to be added.

[0576] Step 503: The terminal receives the configuration information related to the SDSR, and determines whether to allow the sending of the SDSR and its corresponding configuration information according to the configuration information.

[0577] Step 504: The terminal receives the SDSR request message sent by the base station, and determines, based on the information carried in the request message, for which relevant flow the SDSR is to be sent. This step is optional.

[0578] Step 505: According to the request in step 502, or based on the SDSR triggering condition configured in step 501, after the triggering condition is met and the SDSR is triggered, a PDCP control PDU is sent to the base station side. The PDCP control PDU carrying the SDSR request message includes:

[0579] Synchronization delay information;

[0580] The relevant flow identifier corresponding to the synchronization delay information is one of the following items or a combination thereof: the number QFI1 of the first flow, the number QFI2 of the second flow, and the identifier of the relevant flow group (such as common ID).

[0581] As shown in FIG5( b ), it is a schematic diagram of the format of a PDCP control PDU carrying SDSR.

[0582] In Figure 5(b):

[0583] D / C field: indicates whether it corresponds to PDCP data PDU or PDCP control PDU;

[0584] PDU type: PDU (Protocol Data Unit) type indication, its specific value is used to indicate that the current PDCP controlPDU is used to carry synchronization delay information;

[0585] Synchronization delay information: Specific synchronization delay status reporting value.

[0586] If the PDCP control PDU needs to include one or more of QFI1, QFI2, and the identifier of the relevant flow group, the corresponding field needs to be added.

[0587] Step 506: The base station receives the SDSR PDCP control PDU sent by the terminal.

[0588] Step 507: The base station schedules the transmission of related stream data according to the SDSR PDCP control PDU sent by the terminal.

[0589] Specifically: the base station determines the remaining time for sending data packets in the relevant flow according to the synchronization delay information in the PDCP control PDU (if the data packets of the relevant flow are not sent within the remaining time, the synchronization delay threshold of the relevant flow is exceeded); before the remaining time exceeds, the base station allocates uplink resources to the terminal to send data packets of the relevant flow.

[0590] In the embodiment of the present application, the SDSR is carried by RLC control PDU. The process may include:

[0591] Step 601: Send SDSR-related configuration information to the terminal, where the configuration information includes one or more of the following: association information of related flows; synchronization delay threshold: whether the terminal is allowed to feedback SDSR; QoS flow ID that triggers SDSR; identifier of the related flow group that triggers SDSR; protocol layer configuration that carries SDSR; and SDSR triggering conditions.

[0592] Step 602: Send an RLC control PDU of the SDSR request to the terminal. The content of the RLC control PDU can refer to the description of the above embodiment. This step is optional.

[0593] As shown in Figure 6(a), it is a schematic diagram of the format of an RLC control PDU carrying an SDSR request. In Figure 6(a), in the RLC control PDU of the SDSR request: there may be only a control PDU type identifier, indicating that the RLC control PDU is used for the SDSR request; it may also further include related stream information, namely one or more of the following: the number QFI1 of the first stream, the number QFI2 of the second stream, and the related stream group number (such as common ID or DRBGroup ID or logical channel group number LCG) used to represent a group of related streams. The following is an SDSR request RLC control PDU with only a control PDU type identifier, where:

[0594] D / C domain: indicates whether it corresponds to RLC data PDU or RLC control PDU;

[0595] CPT (Control PDU Type): control PDU type indication, its specific value is used to indicate that the current RLC control PDU is used for SDSR request.

[0596] In this format, the terminal uses the uplink logical channel corresponding to the downlink logical channel carrying the RLC control PDU as the uplink logical channel for feedback SDSR, and the feedback content is the relevant stream synchronization delay information of the uplink data stream carried in the uplink logical channel.

[0597] If the RLC control PDU needs to include one or more of QFI1, QFI2, and the identifier of the relevant flow group, the corresponding field needs to be added.

[0598] Step 603: The terminal receives the configuration information related to the SDSR, and determines whether to allow the sending of the SDSR and its corresponding configuration information according to the configuration information.

[0599] Step 604: The terminal receives the SDSR request message sent by the base station, and determines, based on the information carried in the request message, for which relevant flow the SDSR is to be sent. This step is optional.

[0600] Step 605: According to the request in step 602, or based on the SDSR triggering condition configured in step 601, after the triggering condition is met and the SDSR is triggered, an SDSR RLC control PDU is sent to the base station side.

[0601] The RLC control PDU carrying the SDSR request message includes:

[0602] Synchronization delay information;

[0603] The relevant flow identifier corresponding to the synchronization delay information is one of the following items or a combination thereof: the number QFI1 of the first flow, the number QFI2 of the second flow, and the identifier of the relevant flow group (such as common ID).

[0604] As shown in Figure 6(b), it is a schematic diagram of the format of an RLC control PDU carrying SDSR. In Figure 6(b):

[0605] D / C domain: indicates whether it corresponds to RLC data PDU or RLC control PDU;

[0606] CPT (Control PDU Type): control PDU type indication, its specific value is used to indicate that the current RLC control PDU is used to carry synchronization delay information;

[0607] Synchronization delay information: Specific synchronization delay status reporting value.

[0608] If the RLC control PDU needs to include one or more of QFI1, QFI2, and the identifier of the relevant flow group, the corresponding field needs to be added.

[0609] Step 606: The base station receives the SDSR RLC control PDU sent by the terminal.

[0610] Step 607: The base station schedules the transmission of related stream data according to the SDSR RLC control PDU sent by the terminal.

[0611] Specifically: the base station determines the remaining time for sending data packets in the relevant flow according to the synchronization delay information in the RLC control PDU (if the data packets of the relevant flow are not sent within the remaining time, the synchronization delay threshold of the relevant flow is exceeded); before the remaining time exceeds, the base station allocates uplink resources to the terminal to send data packets of the relevant flow.

[0612] In the embodiment of the present application, MAC CE is used to carry SDSR. The process may include:

[0613] Step 701: Send SDSR-related configuration information to the terminal, where the configuration information includes one or more of the following: association information of related flows; synchronization delay threshold: whether the terminal is allowed to feedback SDSR; QoS flow ID or DRB number or RLC number or logical channel number that triggers SDSR, or logical channel group number LCG ID corresponding to the logical channel; identifier of the related flow group that triggers SDSR; protocol layer configuration that carries SDSR; SDSR triggering condition.

[0614] Step 702: Send a MAC CE of a SDSR request to the terminal. The content of the MAC CE can refer to the description of the above embodiment. This step is optional.

[0615] As shown in Figure 7(a), an example of a MAC CE that includes only the LCG ID corresponding to the first stream is shown. In the MAC CE, the LCGID is used to indicate the logical channel group number to which the relevant streams involved in the synchronization delay information reported by the terminal belong. There can be one or more LCG IDs, and this figure is only a schematic diagram of one LCG ID.

[0616] If the MAC CE includes information of multiple related flows, or includes indication information of multiple related flows for one related flow, a corresponding field needs to be added in the MAC CE.

[0617] In a specific application, a MAC subheader plus a corresponding MAC CE constitutes a transmission unit MAC sub-PDU of the MAC layer, and one or more MAC sub-PDUs are cascaded to form a MAC PDU.

[0618] Step 703: The terminal receives configuration information related to the SDSR, and determines whether to allow the sending of the SDSR and its corresponding configuration information according to the configuration information.

[0619] Step 704: The terminal receives the SDSR request message sent by the base station, and determines, based on the information carried in the request message, for which relevant flow the SDSR is to be sent. This step is optional.

[0620] Step 705: According to the request in step 702, or based on the SDSR triggering condition configured in step 701, after the triggering condition is met and the SDSR is triggered, an SDSR MAC CE is sent to the base station side.

[0621] As shown in Figure 7(b), it is a schematic diagram of a MAC CE carrying a SDSR request and its MAC subheader format. In Figure 7(b):

[0622] MAC subheader:

[0623] LCID+eLCID is used to indicate that the corresponding MAC CE is an SDSR request MAC CE.

[0624] The SDSR MAC CE format contains the following contents as described above. Generally speaking, the MAC CE content includes:

[0625] Synchronization delay information;

[0626] The terminal buffer data volume BSR related to the synchronization delay information;

[0627] Information about the first stream;

[0628] Information of the second stream;

[0629] The information of the related stream group is used to indicate a group of related streams.

[0630] The following is an example of a MACCE that includes synchronization delay information, the corresponding buffer data size, and the LCG ID corresponding to the first flow:

[0631] LCG ID: The logical channel group to which the logical channel carrying the relevant flow corresponding to the synchronization delay information belongs.

[0632] Synchronization delay information: Specific synchronization delay status reporting value.

[0633] Buffer Size: Reports the buffer status of data associated with synchronization delay information.

[0634] If the MAC CE includes information of multiple related flows, or includes indication information of multiple related flows for one related flow, a corresponding field needs to be added in the MAC CE.

[0635] Step 706: The base station receives the SDSR MAC CE sent by the terminal.

[0636] Step 707: the base station schedules the transmission of related stream data according to the SDSR MAC CE sent by the terminal.

[0637] Specifically: the base station determines the remaining time for sending data packets in the relevant flow according to the synchronization delay information in the MAC CE (if the data packets of the relevant flow are not sent within the remaining time, the synchronization delay threshold of the relevant flow is exceeded); before the remaining time exceeds, the base station allocates uplink resources to the terminal to send data packets of the relevant flow.

[0638] It can be seen from the above description that by utilizing the solution of the embodiment of the present application, the base station can quickly acquire the synchronization delay information of the uplink related streams, thereby performing targeted scheduling, ensuring the synchronous transmission of the uplink related streams, and improving the user experience of the XR service.

[0639] 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 air interface (NR) system, etc. These various systems include 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.

[0640] The terminal device involved in the embodiment of the present application 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 called a user equipment (UE). A wireless terminal device can 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.

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

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

[0643] like Figure 8 As shown, the information processing device of the embodiment of the present application is applied to a network device, including: a processor 800, which is used to read the program in the memory 820 and execute the following process:

[0644] Receiving a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0645] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0647] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0648] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0649] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0650] The transceiver 810 is configured to receive and send data under the control of the processor 800 .

[0651] Among them, Figure 8In 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 800 and memory represented by memory 820. 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 810 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. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 800 when performing operations.

[0652] The processor 800 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

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

[0654] Among them, the meaning and interpretation of the user plane control message can refer to the description of the above embodiment.

[0655] The processor 800 is further configured to read the program and execute one or more of the following steps:

[0656] Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal;

[0657] Sending configuration information to the terminal, wherein the configuration information includes one or more of the following:

[0658] Related information of related streams;

[0659] Synchronization delay threshold;

[0660] Whether to allow the terminal to feedback synchronization delay status report;

[0661] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0662] Information about the relevant stream groups that trigger the synchronization delay status report;

[0663] Protocol layer configuration information for carrying synchronization delay status reports;

[0664] Trigger conditions for synchronization delay status reporting.

[0665] Among them, the interpretation and meaning of the request message can refer to the description of the aforementioned method embodiment.

[0666] It should be noted here that the above-mentioned 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 of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0667] like Fig. 9 As shown, the information processing device of the embodiment of the present application is applied to a terminal, including: a processor 900, which is used to read the program in the memory 920 and execute the following process:

[0668] Sending a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

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

[0670] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0671] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0672] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0673] The transceiver 910 is configured to receive and send data under the control of the processor 900 .

[0674] Among them, Fig. 9In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 900 and various circuits of memory represented by memory 920 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 910 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. For different user devices, the user interface 930 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.

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

[0676] The processor 900 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

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

[0678] Among them, the meaning and interpretation of the user plane control message can be referred to the description of the aforementioned method embodiment.

[0679] The processor 900 is further configured to read the program and execute one or more of the following steps:

[0680] Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report;

[0681] Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following:

[0682] Related information of related streams;

[0683] Synchronization delay threshold;

[0684] Whether to allow the terminal to feedback synchronization delay status report;

[0685] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0686] Information about the relevant stream groups that trigger the synchronization delay status report;

[0687] Protocol layer configuration information for carrying synchronization delay status reports;

[0688] Trigger conditions for synchronization delay status reporting.

[0689] Among them, the meaning and interpretation of the request message can refer to the description of the aforementioned method embodiment.

[0690] It should be noted here that the above-mentioned 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 of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0691] like Fig.10 As shown, the information processing device of the embodiment of the present application is applied to a terminal, including:

[0692] A first sending unit 1001 is used to send a synchronization delay status report to a network device through a user plane control message, where the synchronization delay status report is used to indicate the synchronization delay status of a related flow;

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

[0694] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0695] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0696] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0697] Among them, the meaning and interpretation of the user plane control message can be referred to the description of the aforementioned method embodiment.

[0698] Optionally, the device may further include: a first receiving unit, configured to perform one or more of the following:

[0699] Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report;

[0700] Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following:

[0701] Related information of related streams;

[0702] Synchronization delay threshold;

[0703] Whether to allow the terminal to feedback synchronization delay status report;

[0704] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0705] Information about the relevant stream groups that trigger the synchronization delay status report;

[0706] Protocol layer configuration information for carrying synchronization delay status reports;

[0707] Trigger conditions for synchronization delay status reporting.

[0708] Among them, the meaning and interpretation of the request message can refer to the description of the aforementioned method embodiment.

[0709] It should be noted here that the above-mentioned 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 of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0710] like Fig.11 As shown, the information processing device of the embodiment of the present application is applied to a network device, including:

[0711] The first receiving unit 1101 is used to receive a synchronization delay status report sent by a terminal through a user plane control message, where the synchronization delay status report is used to indicate a synchronization delay status of a related flow;

[0712] Scheduling transmission of related flows according to the synchronization delay status report;

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

[0714] Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs;

[0715] The correlation between flows carried by different DRBs is indicated by the association between DRB IDs;

[0716] The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

[0717] Among them, the meaning and interpretation of the user plane control message can be referred to the description of the aforementioned method embodiment.

[0718] Optionally, the device may further include: a first sending unit, configured to perform one or more of the following:

[0719] Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal;

[0720] Sending configuration information to the terminal, wherein the configuration information includes one or more of the following:

[0721] Related information of related streams;

[0722] Synchronization delay threshold;

[0723] Whether to allow the terminal to feedback synchronization delay status report;

[0724] The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCGID of the logical channel group corresponding to the logical channel to which it belongs;

[0725] Information about the relevant stream groups that trigger the synchronization delay status report;

[0726] Protocol layer configuration information for carrying synchronization delay status reports;

[0727] Trigger conditions for synchronization delay status reporting.

[0728] Among them, the meaning and interpretation of the request message can refer to the description of the aforementioned method embodiment.

[0729] It should be noted here that the above-mentioned 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 of this embodiment that are the same as those in the method embodiment will not be described in detail here.

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

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

[0732] An embodiment of the present application further provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor implements the steps in the above-mentioned information processing method when executing the program.

[0733] The embodiment of the present application also provides a processor-readable storage medium, on which a program is stored. When the program is executed by the processor, each process of the above-mentioned information processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0734] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0735] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD), and includes a number of instructions for a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0736] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. An information processing method, characterized in that: Applied to terminals, including: Sending a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; 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.

2. The method according to claim 1, characterized in that The user plane control message includes one or more of the following: Uplink service data adaptation protocol control protocol data unit SDAP control PDU; Uplink packet data convergence protocol control protocol data unit PDCP controlPDU; Uplink radio link control protocol data unit RLC control PDU; Uplink media access control control element MAC CE.

3. The method according to claim 1 or 2, characterized in that: The user plane control message includes: time information of synchronization delay; The time information of the synchronization delay includes any one of the following: The data sending time of the first stream among the related streams; The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent; The time interval between the data sending time of the first flow and the time of triggering or sending the synchronization delay status report.

4. The method according to claim 3, characterized in that The data sending time of the first stream includes: an initial transmission time of a first packet data unit PDU of the first flow; or The time when the first PDU of the first flow is successfully sent; or The time when a packet data unit set PDU set of the first flow is successfully sent.

5. The method according to claim 3, characterized in that: If the user plane control message includes an uplink SDAPcontrol PDU, the user plane control message further includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; The identifier of the related flow group is used to indicate a group of related QoS flows.

6. The method according to claim 3, characterized in that If the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; A data radio bearer identifier (DRB ID) of the first flow; A data radio bearer identifier DRB ID of the second flow; A logical channel identifier LCID of the first stream; A logical channel identifier LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

7. The method according to claim 3, characterized in that If the user plane control message includes an uplink MAC CE, the user plane control message further includes one or more of the following: Terminal cache data volume cache status report BSR; Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

8. The method according to claim 7, characterized in that The amount of data indicated by the BSR includes any of the following: The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report; The amount of cached data of the first flow and / or the second flow in the terminal cache; The amount of cached data of the PDU set of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report; The data volume of the DRB or logical channel LCH carrying the first flow and / or the second flow; The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

9. The method according to claim 7, characterized in that: The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

10. The method according to claim 1, characterized in that The method further comprises one or more of the following steps: Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report; Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following: Related information of related streams; Synchronization delay threshold; Whether to allow the terminal to feedback synchronization delay status report; The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCG ID of the logical channel group corresponding to the logical channel to which it belongs; Information about the relevant stream groups that trigger the synchronization delay status report; Protocol layer configuration information for carrying synchronization delay status reports; Trigger conditions for synchronization delay status reporting.

11. The method according to claim 10, characterized in that The request message includes one or more of the following: Downlink SDAP control PDU; Downlink PDCP control PDU; Downlink RLC control PDU; Downlink MAC CE.

12. The method according to claim 11, characterized in that The downlink SDAP control PDU includes one or more of the following: The stream identifier QFI of the first stream among the related streams; The stream identifier QFI of the second stream in the related streams; The identifier of the related flow group is used to indicate a group of related QoS flows.

13. The method according to claim 11, characterized in that The downlink PDCP control PDU or downlink RLCcontrol PDU includes one or more of the following: The QFI of the first of the related streams; The QFI of the second stream in the related stream; The DRB ID of the first flow; The DRB ID of the second flow; The LCID of the first stream; the LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

14. The method according to claim 11, characterized in that The downlink MAC CE includes one or more of the following: Information about the first stream in the related streams; Information about the second stream in the related stream; The information of the related stream group is used to indicate a group of related streams.

15. The method according to claim 14, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

16. An information processing method, characterized in that: Applied to network equipment, including: Receiving a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; Scheduling transmission of related flows according to the synchronization delay status report; The related streams include one or more of the following: Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs; The correlation between flows carried by different DRBs is indicated by the association between DRB IDs; The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

17. The method according to claim 16, characterized in that The user plane control message includes one or more of the following: Uplink SDAP control PDU; Uplink PDCP control PDU; Uplink RLC control PDU; Uplink MAC CE.

18. The method according to claim 16 or 17, characterized in that The user plane control message includes: time information of synchronization delay; The time information of the synchronization delay includes any one of the following: The data sending time of the first flow among the related flows; The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent; The time interval between the time when the data of the first flow is sent and the time when the synchronization delay status report is triggered or sent.

19. The method according to claim 18, characterized in that The data sending time of the first stream includes: the initial transmission time of the first PDU of the first flow; or The time when the first PDU of the first flow is successfully sent; or The time when a PDU set of the first flow is successfully sent.

20. The method according to claim 18, characterized in that If the user plane control message includes an uplink SDAPcontrolPDU, the user plane control message also includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; The information of the related flow group is used to indicate a group of related QoS flows.

21. The method according to claim 18, characterized in that If the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message also includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI carrying the second flow; DRB identifier DRB ID of the first flow; DRB identifier DRB ID of the second flow; A logical channel identifier LCID of the first stream; An identifier LCID of a logical channel of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

22. The method according to claim 18, characterized in that If the user plane control message includes a MAC CE, the user plane control message also includes one or more of the following: Terminal buffer data volume BSR; Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

23. The method according to claim 22, characterized in that The amount of data indicated by the BSR includes any of the following: The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report; The amount of cached data of the PDU set of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report; The amount of cached data of the first flow and / or the second flow in the terminal cache; The data volume of the DRB or logical channel LCH carrying the first flow and / or the second flow; The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

24. The method according to claim 22, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCGID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

25. The method according to claim 16, characterized in that The method further comprises one or more of the following steps: Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal; Sending configuration information to the terminal, wherein the configuration information includes one or more of the following: Related information of related streams; Synchronization delay threshold; Whether to allow the terminal to feedback synchronization delay status report; The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCG ID of the logical channel group corresponding to the logical channel to which it belongs; Information about the relevant stream groups that trigger the synchronization delay status report; Protocol layer configuration information for carrying synchronization delay status reports; Trigger conditions for synchronization delay status reporting.

26. The method according to claim 25, characterized in that The request message includes one or more of the following: Downlink SDAP control PDU; Downlink PDCP control PDU; Downlink RLC control PDU; Downlink MAC CE.

27. The method according to claim 26, characterized in that The downlink SDAP control PDU includes one or more of the following: The stream identifier QFI of the first stream among the related streams; The stream identifier QFI of the second stream in the related streams; The identifier of the related flow group is used to indicate a group of related QoS flows.

28. The method according to claim 27, characterized in that The downlink PDCP control PDU or downlink RLCcontrol PDU includes one or more of the following: The QFI of the first of the related streams; The QFI of the second stream in the related stream; The DRB ID of the first flow; The DRB ID of the second flow; The LCID of the first stream; the LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

29. The method according to claim 27, characterized in that The downlink MAC CE includes one or more of the following: Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

30. The method according to claim 29, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

31. An information processing device, characterized in that: Applied to terminals, 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: Sending a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; The related streams include one or more of the following: Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs; The correlation between flows carried by different DRBs is indicated by the association between DRB IDs; The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

32. The device according to claim 31, characterized in that The user plane control message includes one or more of the following: Uplink SDAP control PDU; Uplink PDCP controlPDU; Uplink RLC control PDU; Uplink MAC CE.

33. The device according to claim 31 or 32, characterized in that The user plane control message includes: time information of synchronization delay; The time information of the synchronization delay includes any one of the following: The data sending time of the first stream among the related streams; The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent; The time interval between the data sending time of the first flow and the time of triggering or sending the synchronization delay status report.

34. The device according to claim 33, characterized in that The data sending time of the first stream includes: the initial transmission time of the first PDU of the first flow; or The time when the first PDU of the first flow is successfully sent; or The time when a PDU set of the first flow is successfully sent.

35. The device according to claim 33, characterized in that If the user plane control message includes an uplink SDAPcontrol PDU, the user plane control message further includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; The identifier of the related flow group is used to indicate a group of related QoS flows.

36. The device according to claim 33, characterized in that If the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; A data radio bearer identifier (DRB ID) of the first flow; A data radio bearer identifier DRB ID of the second flow; A logical channel identifier LCID of the first stream; A logical channel identifier LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

37. The device according to claim 33, characterized in that If the user plane control message includes an uplink MAC CE, the user plane control message further includes one or more of the following: Terminal cache data volume cache status report BSR; Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

38. The device according to claim 37, characterized in that The amount of data indicated by the BSR includes any of the following: The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report; The amount of cached data of the first flow and / or the second flow in the terminal cache; The amount of cached data of the PDU set of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report; The data volume of the DRB or logical channel LCH carrying the first flow and / or the second flow; The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

39. The device according to claim 37, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

40. The device according to claim 31, characterized in that The processor is further configured to read the computer program in the memory and perform one or more of the following operations: Receiving a request message sent by the network device, wherein the request message is used to request the terminal to send the synchronization delay status report; Receive configuration information sent by the network device, wherein the configuration information includes one or more of the following: Related information of related streams; Synchronization delay threshold; Whether to allow the terminal to feedback synchronization delay status report; The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCG ID of the logical channel group corresponding to the logical channel to which it belongs; Information about the relevant stream groups that trigger the synchronization delay status report; Protocol layer configuration information for carrying synchronization delay status reports; Trigger conditions for synchronization delay status reporting.

41. The device according to claim 40, characterized in that The request message includes one or more of the following: Downlink SDAP control PDU; Downlink PDCP control PDU; Downlink RLC control PDU; Downlink MAC CE.

42. The device according to claim 41, characterized in that The downlink SDAP control PDU includes one or more of the following: The stream identifier QFI of the first stream among the related streams; The stream identifier QFI of the second stream in the related streams; The identifier of the related flow group is used to indicate a group of related QoS flows.

43. The device according to claim 41, characterized in that The downlink PDCP control PDU or downlink RLC control PDU includes one or more of the following: The QFI of the first of the related streams; The QFI of the second stream in the related stream; The DRB ID of the first flow; The DRB ID of the second flow; The LCID of the first stream; the LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

44. The device according to claim 41, characterized in that The downlink MAC CE includes one or more of the following: Information about the first stream in the related streams; Information about the second stream in the related stream; The information of the related stream group is used to indicate a group of related streams.

45. The device according to claim 44, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

46. ​​An information processing device, characterized in that Applied to network equipment, 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 a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; Scheduling transmission of related flows according to the synchronization delay status report; The related streams include one or more of the following: Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs; The correlation between flows carried by different DRBs is indicated by the association between DRB IDs; The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

47. The device according to claim 46, characterized in that The user plane control message includes one or more of the following: Uplink SDAP control PDU; Uplink PDCP control PDU; Uplink RLC control PDU; Uplink MAC CE.

48. The device according to claim 46 or 47, characterized in that The user plane control message includes: time information of synchronization delay; The time information of the synchronization delay includes any one of the following: The data sending time of the first flow among the related flows; The remaining time for sending data of the second stream in the related streams, wherein the remaining time for sending data is equal to the difference between the synchronization delay threshold and the first time, and the first time is the time for the second stream to wait for sending data after the data of the first stream is sent; The time interval between the time when the data of the first flow is sent and the time when the synchronization delay status report is triggered or sent.

49. The device according to claim 48, characterized in that The data sending time of the first stream includes: the initial transmission time of the first PDU of the first flow; or The time when the first PDU of the first flow is successfully sent; or The time when a PDU set of the first flow is successfully sent.

50. The device according to claim 48, characterized in that If the user plane control message includes an uplink SDAPcontrol PDU, the user plane control message also includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI of the second flow; The information of the related flow group is used to indicate a group of related QoS flows.

51. The device according to claim 48, characterized in that If the user plane control message includes an uplink PDCP control PDU or an uplink RLC control PDU, the user plane control message further includes one or more of the following: A flow identifier QFI of the first flow; A flow identifier QFI carrying the second flow; DRB identifier DRB ID of the first flow; DRB identifier DRB ID of the second flow; A logical channel identifier LCID of the first stream; An identifier LCID of a logical channel of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

52. The device according to claim 48, characterized in that If the user plane control message includes a MAC CE, the user plane control message also includes one or more of the following: Terminal buffer data volume BSR; Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

53. The device according to claim 52, characterized in that The amount of data indicated by the BSR includes any of the following: The amount of data for which the remaining time for sending data of the relevant flow in the terminal buffer is less than or equal to the time threshold for triggering the synchronization delay status report; The amount of cached data of the PDU set of the first flow and / or the second flow in the terminal cache that triggers the synchronization delay status report; The amount of cached data of the first flow and / or the second flow in the terminal cache; The data volume of the DRB or logical channel LCH carrying the first flow and / or the second flow; The amount of data of the logical channel group LCG to which the logical channel carrying the first stream and / or the second stream belongs.

54. The device according to claim 52, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

55. The device according to claim 46, characterized in that The processor is further configured to read the computer program in the memory and perform one or more of the following operations: Sending a request message to the terminal, wherein the request message is used to request the synchronization delay status report of the terminal; Sending configuration information to the terminal, wherein the configuration information includes one or more of the following: Related information of related streams; Synchronization delay threshold; Whether to allow the terminal to feedback synchronization delay status report; The QFI of the QoS flow to which the flow that triggers the synchronization delay status report belongs, the DRB ID of the DRB to which it belongs, the RLC identifier of the RLC to which it belongs, the LCID of the logical channel to which it belongs, or the identifier LCG ID of the logical channel group corresponding to the logical channel to which it belongs; Information about the relevant stream groups that trigger the synchronization delay status report; Protocol layer configuration information for carrying synchronization delay status reports; Trigger conditions for synchronization delay status reporting.

56. The device according to claim 55, characterized in that The request message includes one or more of the following: Downlink SDAP control PDU; Downlink PDCP control PDU; Downlink RLC control PDU; Downlink MAC CE.

57. The device according to claim 56, characterized in that The downlink SDAP control PDU includes one or more of the following: The stream identifier QFI of the first stream among the related streams; The stream identifier QFI of the second stream in the related streams; The identifier of the related flow group is used to indicate a group of related QoS flows.

58. The device according to claim 57, characterized in that The downlink PDCP control PDU or downlink RLCcontrol PDU includes one or more of the following: The QFI of the first of the related streams; The QFI of the second stream in the related stream; The DRB ID of the first flow; The DRB ID of the second flow; The LCID of the first stream; the LCID of the second stream; The identifier of the related flow group is used to indicate a group of related QoS flows, or to indicate a group of related DRBs, or to indicate a group of related logical channels.

59. The device according to claim 57, characterized in that The downlink MAC CE includes one or more of the following: Information about the first stream; information of the second stream; The information of the related stream group is used to indicate a group of related streams.

60. The device according to claim 59, characterized in that The information of the first stream includes any of the following: the QFI of the first stream; The DRB ID of the first flow; The LCID of the first stream; An identifier LCG ID of a logical channel group to which the logical channel of the first stream belongs; and / or The information of the second stream includes any of the following: the QFI of the second stream; The DRB ID of the second flow; the LCID of the second stream; The identifier LCG ID of the logical channel group to which the logical channel of the second stream belongs.

61. An information processing device, characterized in that: Applied to terminals, including: A first sending unit, configured to send a synchronization delay status report to a network device through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; The related streams include one or more of the following: Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs; The correlation between flows carried by different DRBs is indicated by the association between DRB IDs; The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

62. An information processing device, characterized in that: Applied to network equipment, including: A first receiving unit, configured to receive a synchronization delay status report sent by a terminal through a user plane control message, wherein the synchronization delay status report is used to indicate a synchronization delay status of a related flow; Scheduling transmission of related flows according to the synchronization delay status report; The related streams include one or more of the following: Flows carried by different QoS flows, the correlation between the flows is indicated by the association between QoS flow IDs; The correlation between flows carried by different DRBs is indicated by the association between DRB IDs; The correlation between flows carried by different logical channels is indicated by the association between LCIDs.

63. 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 30.

Images