Communication processing method and device, equipment and readable storage medium

Abstract

The invention discloses a communication processing method, device and equipment and a readable storage medium, and the method comprises the steps that a first element receives first information from a second element, and the first information is related to flow coordination or synchronization; the first element executes a first operation according to the first information; wherein the first element is a first node and the second element is a second node, or the first element is a first entity and the second element is a second entity.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a communication processing method, device, equipment and readable storage medium. Background Art

[0002] Existing extended reality (XR) or cloud gaming (CG) services include multiple packets or multiple streams. Since the Quality of Service (QoS) requirements and operations between each packet or stream are independent, problems such as lag, dizziness, and inconsistency between images or audio may occur in XR or CG services, affecting user service experience. Summary of the invention

[0003] The embodiments of the present application provide a communication processing method, apparatus, device and readable storage medium to solve the problem of how to improve user service experience.

[0004] In a first aspect, a communication processing method is provided, comprising:

[0005] The first element receives first information from the second element, the first information being related to inter-stream coordination or synchronization;

[0006] The first element performs a first operation according to the first information;

[0007] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0008] In a second aspect, a communication processing method is provided, including:

[0009] The second element sends first information to the first element, wherein the first information is related to inter-stream coordination or synchronization;

[0010] Wherein, the first information is used for the first element to perform a first operation;

[0011] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0012] In a third aspect, a communication processing device is provided, applied to a first element, including:

[0013] A first receiving module, configured to receive first information from a second element, wherein the first information is related to inter-stream coordination or synchronization;

[0014] A first processing module, configured to perform a first operation according to the first information;

[0015] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0016] In a fourth aspect, a communication processing device is provided, applied to a second element, including:

[0017] A first sending module, configured to send first information to a first element, where the first information is related to inter-stream coordination or synchronization, and the first information is used by the first element to perform a first operation;

[0018] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0019] In a fifth aspect, a communication device is provided, comprising: a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect or the second aspect.

[0020] In a sixth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor of a sending end, the steps of the method described in the first aspect are implemented, or when the program or instruction is executed by a processor of a receiving end, the steps of the method described in the second aspect are implemented.

[0021] In the seventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect or the second aspect.

[0022] In an eighth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.

[0023] In a ninth aspect, a communication system is provided, the communication system comprising a transmitting end and a receiving end, the transmitting end is used to execute the steps of the method described in the first aspect, and the receiving end is used to execute the steps of the method described in the second aspect.

[0024] In an embodiment of the present application, a first element receives first information from a second element, and the first information is related to coordination or synchronization between streams; the first element performs a first operation based on the first information so that the packets of the first element or the streams meet the synchronization requirements or coordination requirements, avoiding freezes and dizziness caused by asynchrony between streams or packets, or incoordination between pictures or audios, thereby improving the user's business experience. Description of the Drawings

[0025] Figure 1 is a schematic diagram of XR services;

[0026] Figure 2 is a schematic diagram of interactions and operations in XR services

[0027] Figure 3 is a schematic diagram of the 5G architecture;

[0028] Figure 4 is a schematic diagram of the architecture of the wireless communication system according to the embodiment of the present application;

[0029] Figure 5 is one of the flowcharts of a communication processing method provided by the embodiment of the present application;

[0030] Figure 6 is the second flowchart of a communication processing method provided by the embodiment of the present application;

[0031] Figure 7 is one of the schematic diagrams of a communication processing device provided by the embodiment of the present application;

[0032] Figure 8 is the second schematic diagram of a communication processing device provided by the embodiment of the present application;

[0033] Figure 9 is a schematic diagram of the terminal provided by the embodiment of the present application;

[0034] Figure 10 is a schematic diagram of the network-side device provided by the embodiment of the present application;

[0035] Figure 11 is a schematic diagram of the communication device provided by the embodiment of the present application. Detailed Embodiments

[0036] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0037] The terms "first", "second", etc. in this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described here. The objects distinguished by "first" and "second" are usually of the same category, and do not limit the number of objects. For example, the first object can be one or multiple. In addition, "or" in this application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates that the related objects before and after are in an "or" relationship.

[0038] The term "indication" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the receiver of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0039] It is worth noting that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) or LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably. The described technology can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and uses NR terms in most of the following descriptions, but these technologies can also be applied to systems other than NR system applications, such as the 6th generation (6 thGeneration, 6G) communication system.

[0040] To facilitate the understanding of the embodiments of this application, the following technical points are introduced first:

[0041] I. Extended reality (XR) services.

[0042] XR refers to all real and virtual combined environments and human-computer interactions generated by computer technology and wearable devices. As Figure 1 shown, XR includes representative forms such as Augmented Reality (AR), Mixed Reality (MR), Virtual Reality (VR), etc., as well as the cross fields between them. The level of the virtual world ranges from partial sensory input to fully immersive virtual reality. A key aspect of XR is the extension of human experience, especially the experience related to presence (represented by VR) and cognitive acquisition (represented by AR).

[0043] For VR services, the uplink mainly transmits relatively dense small data packets, which can carry information such as gestures and controls and serve as the input and reference for the downlink presentation data. The downlink mainly transmits multimedia data such as video and audio. Through the timely reception and presentation of this multimedia data, an immersive experience is provided to the user. Taking the downlink video data as an example, the data packets arrive periodically or quasi-periodically, the data rate can reach dozens or even hundreds of Megabits PerSecond (Mbps), the typical value of the frame rate (Frames Per Second, FPS) is 60 or 120, the interval between adjacent data packets is approximately 1 / FPS seconds, and these data generally need to be successfully transmitted within 10 milliseconds (ms) over the air interface, and the transmission success rate requirement is not less than 99% or even 99.9%.

[0044] For AR services, in addition to the above-mentioned dense small data packet transmission, multimedia data such as video and audio may also be transmitted. Its service characteristics are similar to those of the downlink, usually with a relatively low data rate, for example, up to dozens of Mbps, and the time limit for over-the-air transmission can also be relaxed, for example, generally need to be successfully transmitted within 60 ms. The downlink data transmission characteristics are basically the same as those of VR services.

[0045] Users hope to interact and operate in extended reality, as Figure 2 shown. Actions and interactions include actions, gestures, and body reactions. Therefore, the Degrees of Freedom (DoF) describes the number of independent parameters used to define the movement of the viewport in 3D space.

[0046] In the application scenarios of XR, users can obtain information on new viewing angles through actions such as turning their heads during virtual reality experiences. At this time, the head-turning actions of XR users can inform the base station by sending an uplink signal. After receiving the uplink signal, the base station will schedule the required downlink data for the XR user for use.

[0047] XR services mainly include video data, audio data, as well as some control signaling and special data with control functions. In a wireless network, the transmission of XR services mainly involves the uplink and downlink video or audio data transmission and interaction between a terminal (e.g., a user terminal (User Equipment, UE)) and a wireless network via a new network (such as Long Term Evolution (LTE) or New Radio (NR), etc.). Among them, while transmitting video and audio data itself, the UE needs to transmit some control signaling and special data with control functions via the wireless network uplink to generate, process, and downlink wirelessly transmit the video and audio service data in the XR services sent by the control network to the UE.

[0048] These control information and special data with control functions include some service control data generated by the UE XR application encoder and control data information included in the service transmission protocol. For example:

[0049] A. At the application layer, it can include but is not limited to:

[0050] (1) I-frames or non-Field of View (non-FOV) frames generated by the video encoder;

[0051] (2) User behavior data collected by sensors, such as pose or control data, etc.; The network can judge user behavior through the reception of these data, such as the above-mentioned head-turning actions of users, and then adjust the content of the video data sent.

[0052] B. At the transmission protocol layer, it can include:

[0053] (1) Transmission Control Protocol Acknowledgment (TCP ACK) signaling (TCP feedback) for downlink audio or video service transmission. The network needs to decide whether to continue sending subsequent frames based on whether the corresponding video or audio frame has been acknowledged by the UE.

[0054] (2) Real-time Transport Control Protocol Acknowledgment (RTCP ACK) signaling, which is a control signaling for controlling real-time data transmission, and is used to confirm the real-time requirements for service data transmission and time synchronization.

[0055] The network usually needs to receive these control signals and special data with control functions from the UE in a timely and reliable manner to obtain the transmission status of the current service and relevant necessary control information; the application server needs to further generate video and audio service data to be transmitted subsequently based on this information, and submit it to the wireless network for processing and transmission, and finally send these service data down to the UE.

[0056] II. Packet Data Convergence Protocol (PDCP) layer and radio bearer.

[0057] The service data generated by the application layer of the UE will be classified into different service data streams according to their corresponding Quality-of-service (QoS) requirements, and each service data stream corresponds to the same or similar QoS requirements. In the NR system, the service data stream corresponds to a QoS flow, while in the LTE system, the service data stream corresponds to an Evolved Packet System (EPS) bearer.

[0058] The service data will be delivered to the Access Stratum (AS) layer in the form of packets, and in the AS layer, it will be further mapped to a radio bearer according to the corresponding QoS flow or EPS bearer. A radio bearer includes a PDCP entity, a Radio Link Control (RLC) entity, and the corresponding logical channel (located at the Medium Access Control (MAC) protocol layer).

[0059] When a data packet delivered to the AS layer is mapped to a radio bearer, it will be delivered to the corresponding PDCP entity for processing in the form of a PDCP service data unit (SDU). The PDCP entity will generate a corresponding PDCP protocol data unit (PDU) for each arriving PDCP SDU and set a PDCP sequence number (SN) to indicate the transmission order corresponding to each PDCP SDU and its corresponding PDCP PDU in the PDCP entity. Among them, the value of the PDCP SN is set according to the order in which the PDCP SDUs are delivered to the PDCP entity. The PDCP SDUs that arrive first have a prior transmission order, and those that are delivered later have a subsequent order. Specifically, the PDCP entity will maintain an internal variable, TX_NEXT, which represents the total number of PDCP PDUs transmitted by the PDCP entity and is used to set the value of the PDCP SN. When the PDCP entity is established, it is initialized to 0. After each PDCP SDU is delivered from the upper layers to the corresponding PDCP entity, the PDCP entity will set the SN of the PDCP PDU corresponding to the PDCP SDU to TX_NEXT and increment TX_NEXT by 1. After that, the PDCP entity will add a header file to each PDCP SDU to generate the corresponding PDCP PDU, which contains the SN value set for the PDCP PDU. The PDCP entity usually delivers the PDCP PDUs to the lower protocol layer (RLC) in the order of the SNs contained in the PDCP PDUs for subsequent processing and transmission. Among them, the SN is an ordinal number indicating which one the PDCP SDU is in terms of transmission order.

[0060] The general principle is that the earlier the PDCP SDU arrives at the PDCP entity, the smaller the SN value and the earlier the transmission.

[0061] III. Fifth-Generation (5G) Mobile Communication Technology Architecture

[0062] See Figure 3 , the 5G system consists of an access network (AN) and a 5G core network (5GC). If considering the non-standalone architecture (NSA) scenario, the network elements of the fourth-generation (4G) mobile communication technology also need to be considered.

[0063] There are two types of ANs:

[0064] (1) Next Generation NodeB (gNB) provides the NR user plane and control plane protocol endpoints for the UE.

[0065] (2) New Generation Enhanced NodeB (ng-eNB) provides the endpoints of the user plane and control plane protocols of Evolved Universal Terrestrial Radio Access (E-UTRA) for the UE.

[0066] Figure 4 The block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 41 and a network side device 42.

[0067] Among them, the terminal 41 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip or a vehicle unit, etc. In addition to the above terminal devices, the terminal involved in this application can also be a chip inside the terminal, such as a modem chip or a system on chip (SoC). It should be noted that the specific type of the terminal 41 is not limited in the embodiments of this application.

[0068] The network-side device 42 may include an access network device or a core network device. Among them, the access network device may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node, etc. The base station may be referred to as Node B (NB), evolved Node B (eNB), next generation Node B (gNB), New Radio Node B (NR Node B), access point, relay base station (RBS), serving base station (SBS), base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home Node B (HNB), home evolved Node B, transmission reception point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0069] The core network device may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), etc. It should be noted that in the embodiments of this application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0070] The following will, with reference to the accompanying drawings, detail the communication processing method, apparatus, communication device, and readable storage medium provided by the embodiments of this application through some embodiments and their application scenarios.

[0071] See Figure 5 , the embodiments of this application provide a communication processing method, and the specific steps include: step 501 and step 502.

[0072] Step 501: The first element receives first information from the second element, and the first information is related to inter-stream coordination or synchronization;

[0073] Optionally, the first information may be information on synchronization requirements or coordination requirements.

[0074] Step 502: The first element performs a first operation according to the first information, and the first operation is used to ensure that synchronization requirements or coordination requirements are met between the flows or packets of the first element;

[0075] In this application, that synchronization requirements are met between packets (per-Packet) or flows (per-Stream) can be understood as at least one of the following: Among multiple packets or multiple flows, a certain synchronization relationship is maintained at the receiving end, that is, the synchronization requirements are met. For example, (1) multiple packets or multiple flows are received at the receiving end with close receiving times or simultaneously, (2) a certain synchronization relationship is maintained in the display buffer at the receiving end for multiple packets or multiple flows, that is, the synchronization requirements or coordination requirements are met. For example, the display buffer times of multiple packets or multiple flows at the receiving end are close or simultaneous, etc.

[0076] That coordination requirements are met between multiple packets or multiple flows can be understood as at least one of the following: (1) Multiple packets or multiple flows are received at the receiving end with close receiving times or simultaneously through coordination, (2) The display buffer times of multiple packets or multiple flows at the receiving end are close or simultaneous through coordination, thereby enhancing the user's service experience.

[0077] Wherein, the first element is the first node, the second element is the second node, or the first element is the first entity and the second element is the second entity.

[0078] In an embodiment of this application, the performing of the first operation includes at least one of the following:

[0079] 1) Map a stream to a corresponding Quality of Service flow (QoS flow);

[0080] Specifically, by controlling the mapping of the stream to the QoS flow, different streams or different packets can meet the synchronization requirements or coordination requirements.

[0081] 2) Map the stream or QoS flow to a corresponding Data Radio Bearer (DRB);

[0082] Specifically, by controlling the mapping of the stream or QoS flow to the DRB, different streams or different packets can meet the synchronization requirements or coordination requirements.

[0083] 3) Map the stream or QoS flow or DRB to a corresponding Bearer;

[0084] Specifically, by controlling the mapping of the stream or QoS flow or DRB to the bearer, different streams or the packets of different streams can meet the synchronization requirements or coordination requirements.

[0085] 4) Map the stream or QoS flow or DRB or Bearer to the corresponding Logic Channel Group (LCG).

[0086] Specifically, by controlling the mapping of the stream or QoS flow or DRB or Bearer to the LCG, different flows or packets of different flows can meet the synchronization requirements or coordination requirements.

[0087] 5) Map the stream or QoS flow or DRB or Bearer to the corresponding Logic Channel Prioritization (LCP).

[0088] Specifically, by controlling the mapping of the stream or QoS flow or DRB or Bearer to the LCP, different flows or packets of different flows can meet the synchronization requirements or coordination requirements.

[0089] 6) Map the stream or QoS flow or DRB or Bearer to the corresponding Logic Channel (LCH).

[0090] For example, by controlling the mapping of the stream or QoS flow or DRB or Bearer to the LCH, different flows or packets of different flows can meet the synchronization requirements or coordination requirements.

[0091] 7) Apply the corresponding discard timer.

[0092] Specifically, by setting different discardTimers for different packets or packets of different flows, different flows or packets of different flows can meet the synchronization requirements or coordination requirements.

[0093] Among them, the synchronization requirement being met between packets means that the delay difference between multiple packets is less than or equal to the first preset threshold.

[0094] Optionally, the delay difference includes one of the following: latency, delay gap, difference.

[0095] Optionally, the first preset threshold value can be defined by the protocol or configured by a Server, core network, base station, or application layer, etc.

[0096] Optionally, the delay difference between multiple packets includes at least one of the following:

[0097] 1) The delay difference of multiple packets received at the receiving end;

[0098] If the delay difference of multiple packets received at the receiving end is less than or equal to the first preset threshold, it means that the multiple packets meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0099] 2) The delay difference of multiple packets sent at the sending end;

[0100] If the delay difference between multiple packets sent at the sending end is less than or equal to the first preset threshold, it means that the multiple packets meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0101] 3) The delay difference between one or more packets being received at the receiving end and other packets being sent at the sending end;

[0102] If the delay difference between one or more packets received at the receiving end and other packets sent at the sending end is less than or equal to the first preset threshold, it means that the "one or more packets" and the "other packets" meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between multiple packets, or the incoordination between the picture or audio, thereby improving the user's business experience.

[0103] 4) The delay difference between one or more packets being sent at the sender and other packets being received at the receiver;

[0104] If the delay difference between one or more packets sent at the sending end and other packets received at the receiving end is less than or equal to the first preset threshold, it means that the "one or more packets" and the "other packets" meet the synchronization requirements or coordination requirements, avoiding the freeze, dizziness, or incoordination between the pictures or audio caused by the asynchrony between multiple packets, thereby improving the user's business experience.

[0105] 5) The delay difference of multiple packets in the display buffer;

[0106] If the delay difference of multiple packets in the display cache is less than or equal to the first preset threshold, it means that the multiple packets meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between multiple packets, or the incoordination between the picture or audio, thereby improving the user's business experience.

[0107] 6) The delay difference when multiple packets arrive at the display cache.

[0108] If the delay difference of multiple packets arriving at the display cache is less than or equal to the first preset threshold, it means that the multiple packets meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between multiple packets, or the incoordination between the picture or audio, thereby improving the user's business experience.

[0109] The synchronization requirement between streams means that the delay difference between multiple streams is less than a second preset threshold.

[0110] Optionally, the delay difference between the multiple streams includes at least one of the following:

[0111] 1) The delay difference of multiple streams sent at the sending end;

[0112] If the delay difference between multiple streams sent at the sending end is less than or equal to the second preset threshold, it means that the multiple streams meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between the multiple streams, or the incoordination between the pictures or audio, thereby improving the user's service experience.

[0113] 2) The delay difference between the reception delay of one or more streams at the receiving end and the transmission delay of other streams at the sending end;

[0114] If the delay difference between the receiving delay of one or more streams at the receiving end and the sending delay of other streams at the sending end is less than or equal to the second preset threshold, it means that the one or more streams and other streams meet the synchronization requirements or coordination requirements, avoiding the freeze, dizziness, or incoordination between the pictures or audio caused by the asynchrony between multiple streams, thereby improving the user's service experience.

[0115] 3) The delay difference between the sending delay of one or more streams at the sending end and the receiving delay of other streams at the receiving end;

[0116] If the delay difference between the sending delay of one or more streams at the sending end and the receiving delay of other streams at the receiving end is less than or equal to the second preset threshold, it means that the one or more streams and other streams meet the synchronization requirements or coordination requirements, avoiding the freeze, dizziness, or incoordination between the pictures or audio caused by the asynchrony between multiple streams, thereby improving the user's service experience.

[0117] 4) The delay difference of multiple streams in the display buffer;

[0118] If the delay difference of multiple streams in the display cache is less than or equal to the second preset threshold, it means that the multiple streams meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between the multiple streams, or the incoordination between the pictures or audio, thereby improving the user's business experience.

[0119] 5) The delay difference between multiple streams reaching the display cache;

[0120] If the delay difference of multiple streams reaching the display cache is less than or equal to the second preset threshold, it means that the multiple streams meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between the multiple streams, or the incoordination between the pictures or audio, thereby improving the user's business experience.

[0121] 6) The delay difference of multiple streams received at the receiving end.

[0122] If the delay difference of multiple streams reaching the display cache is less than or equal to the second preset threshold, it means that the multiple streams meet the synchronization requirements or coordination requirements, avoiding the freeze and dizziness caused by the asynchrony between the multiple streams, or the incoordination between the pictures or audio, thereby improving the user's business experience.

[0123] Specifically, the average delay of a preset packet in a flow is counted within a preset window or duration range or cycle, and the delay difference between the two or more flows is the difference in the average delay counted. It can be understood that the average delay of a preset packet in a flow counted within a preset window or duration or cycle range can represent the service speed or travel speed of the two or more flows, and the delay difference being less than the second preset threshold indicates that the service speed or travel speed of the two or more flows is similar.

[0124] The average delay includes at least one of the following:

[0125] 1) The average delay of multiple streams received at the receiving end;

[0126] 2) The average delay of multiple streams sent at the sender;

[0127] 3) The average delay between one or more streams being received at the receiving end and other streams being sent at the sending end;

[0128] 4) The average delay between one or more streams being sent at the sender and other streams being received at the receiver;

[0129] 5) Average delay of multiple streams in the display buffer;

[0130] 6) Average delay of multiple streams arriving at the display cache.

[0131] In one embodiment of the present application, the first element receives the first information from the second element, including:

[0132] When a first condition is met, the first element receives first information from the second element;

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

[0134] 1) The first requirement is not met between packets or flows;

[0135] It is understandable that "between packets" refers to between multiple packets, and "between flows" refers to between multiple flows, where multiple packets include two or more packets, and multiple flows include two or more flows.

[0136] 2) The second requirement is not satisfied between two nodes or two entities;

[0137] 3) The third requirement is not satisfied between the packets or flows of two nodes, or between the packets or flows of two entities;

[0138] 4) The delay difference between packets or between flows is greater than or equal to the first threshold;

[0139] It is understandable that when the delay difference between packets or between flows is less than the first threshold, the first requirement is satisfied between packets or between flows. Among them, the delay difference between packets or between flows includes at least one of the following: the delay difference in the transmission time between packets or between flows, the delay difference in the reception time between packets or between flows, the delay difference in reaching the display buffer between packets or between flows, and the delay difference in the display buffer between packets or between flows.

[0140] Among them, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0141] Optionally, the first threshold can be defined by the protocol or configured by a server, a core network, a base station, or an application layer, etc.

[0142] For example, the non - satisfaction of the synchronization requirement between packets or between flows includes at least one of the following: (1) There is no certain synchronization relationship between packets or between flows in the first element, that is, the synchronization requirement is not satisfied. For example, the reception times of packets or between flows in the first element are different. (2) There is no certain synchronization relationship between the display buffers of packets or between flows in the first element, that is, the synchronization requirement is not satisfied. For example, the display buffer times of packets or between flows in the first element are different.

[0143] For example, the non - satisfaction of the coordination requirement between packets or between flows includes at least one of the following: (1) The reception times of packets or between flows in the first element are different, and coordination is required to achieve close or simultaneous reception times. (2) The display buffer times of packets or between flows in the first element are different, and coordination is required to achieve close or identical display buffer times.

[0144] For example, the non - satisfaction of the synchronization requirement between two nodes or two entities includes the non - satisfaction of the synchronization requirement between the packets or flows of two nodes or between the packets or flows of two entities.

[0145] For example, the non - satisfaction of the coordination requirement between two nodes or two entities includes the non - satisfaction of the coordination requirement between the packets or flows of two nodes or between the packets or flows of two entities.

[0146] In an implementation manner of the present application, the first element performs a first operation according to the first information, including:

[0147] When a second condition is satisfied, the first element performs a first operation according to the first information;

[0148] Wherein, the second condition includes at least one of the following:

[0149] 1) The fourth requirement is not satisfied between packets or between flows;

[0150] 2) The fifth requirement is not satisfied between two nodes or between two entities;

[0151] 3) The sixth requirement is not satisfied between the packets or flows of two nodes, or between the packets or flows of two entities;

[0152] 4) The delay difference between packets or between flows is greater than or equal to a second threshold;

[0153] Wherein, the fourth requirement, the fifth requirement or the sixth requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0154] Optionally, the second threshold may be defined by a protocol or configured through a server, a core network, a base station or an application layer, etc.

[0155] In an implementation manner of the present application, the first element receives first information from the second element, including at least one of the following:

[0156] 1) The first node directly receives the first information from the second node;

[0157] 2) The first node receives the first information from the second node through a third node.

[0158] In an implementation manner of the present application, the first element receives first information from the second element, including at least one of the following:

[0159] 1) The first entity directly receives the first information from the second entity;

[0160] 2) The first entity receives the first information from the second entity through a third entity.

[0161] In an implementation manner of the present application, the first node and the second node include at least one of the following:

[0162] 1) Two nodes with a synchronization requirement or a coordination requirement;

[0163] 2) Two nodes where two objects with a synchronization requirement or a coordination requirement are located or to which they belong.

[0164] In an implementation manner of the present application, the first entity and the second entity include at least one of the following:

[0165] 1) Two entities with a synchronization requirement or a coordination requirement;

[0166] 2) Two entities where, to which, or corresponding to two objects with a synchronization requirement or a coordination requirement.

[0167] In an implementation manner of the present application, the object includes at least one of the following: service flow, Protocol Data Unit (PDU) session, Bearer, stream, QoS flow, DRB, Radio Link Control (RLC) bearer, LCG, LCH, PDU set, PDU, packet.

[0168] In an implementation manner of the present application, the first entity and the second entity correspond to the same node, or the first entity and the second entity correspond to different nodes.

[0169] Optionally, the first entity and the second entity are two entities of the same terminal. For example, the first information is exchanged between two entities of the same terminal.

[0170] Optionally, the first entity and the second entity are two entities respectively corresponding to two terminals. For example, the first information is exchanged between two entities of different terminals.

[0171] In an implementation manner of the present application, the first information includes at least one of the following:

[0172] 1) Whether the requirements of the seventh requirement are met between packets, between flows, between nodes, or between entities;

[0173] 2) Synchronization or coordination object information;

[0174] 3) Synchronization mark or coordination mark;

[0175] 4) Synchronization requirement;

[0176] Optionally, the synchronization requirement is used to indicate that it is necessary to ensure that packets or flows are transmitted and processed according to a specific time relationship.

[0177] 5) Coordination requirement;

[0178] Optionally, the coordination requirement is used to indicate that it is necessary to ensure that packets or flows need to be sent and processed according to a specific order, timing, or condition to ensure the coherence, effectiveness, and correctness of communication.

[0179] 6) Time tag or timestamp;

[0180] The above-mentioned time tags or timestamps are used to indicate the time information corresponding to packets, flows, nodes, or entities.

[0181] 7) Synchronization requirements between packets;

[0182] Optionally, the coordination requirements between packets are used to ensure that data packets can be transmitted and processed in a predefined and coordinated manner.

[0183] 8) Synchronization requirements between flows;

[0184] Optionally, the coordination requirements between flows are used to ensure that data flows can be transmitted and processed in a predefined and coordinated manner.

[0185] 9) Delay requirements for packets with associated relationships or meeting the eighth requirement;

[0186] Among them, packets with associated relationships refer to packets with dependency or sequential requirements between them.

[0187] Optionally, the delay requirement is used to represent the maximum time delay allowed from the source to the destination.

[0188] 10) Delay requirements for flows with associated relationships or meeting the ninth requirement;

[0189] Among them, flows with associated relationships refer to flows with dependency or sequential requirements between them.

[0190] Among them, the seventh requirement, the eighth requirement, or the ninth requirement includes at least one of synchronization requirements and coordination requirements.

[0191] In an implementation manner of the present application, whether the synchronization requirements are met between the packets includes: whether the delay difference between the packets is less than or equal to a third threshold;

[0192] Or,

[0193] Whether the synchronization requirements are met between the flows includes: whether the delay difference between the flows is less than or equal to a fourth threshold.

[0194] Optionally, the third threshold or the fourth threshold can be defined by the protocol or configured by a server, a core network, a base station, or an application layer, etc.

[0195] In an implementation manner of the present application, the node includes at least one of the following: a terminal, a user, a network-side node (such as a server).

[0196] In an implementation manner of the present application, when the first node is a first terminal and the second node is a second terminal, or when the first node is a first client and the second node is a second client, the third node includes at least one of the following: other terminals or clients except the first node and the second node, network-side nodes, servers.

[0197] Optionally, the network-side node includes at least one of, but is not limited to, a base station, an Access and Mobility Management Function (AMF), and a User Plane Function (UPF).

[0198] In an implementation manner of the present application, when the first node is a first network-side node and the second node is a second network-side node, the third node includes at least one of the following: other network-side nodes except the first node and the second node, terminals, servers.

[0199] In an implementation manner of the present application, the entity includes at least one of the following: a Service Data Adaptation Protocol (SDAP) entity, a Packet Data Convergence Protocol (PDCP) entity, an RLC entity, a Medium Access Control (MAC) entity, and a Physical (PHY) entity.

[0200] Taking the coordination and synchronization requirements between PDCP entities as an example, the first information is exchanged between two PDCP entities of the same terminal. Further, the first information is exchanged between two SDAP entities of the same terminal. For another example, the first information is exchanged between two PDCP entities of different terminals. Further, the first information is exchanged between two SDAP entities of different terminals. The PDCP entity performs at least one of the following according to the first information: mapping the flow or packet with synchronization requirements to the corresponding Bearer; mapping the flow or packet that meets the second condition to the corresponding Bearer.

[0201] Taking the coordination and synchronization requirements between terminals as an example, when the first condition is met, the first terminal (i.e., the first node) receives the first information from the second terminal (i.e., the second node). When the second condition is met, the first terminal performs the first operation according to the first information. Optionally, the first terminal or the second terminal sends the first information to the network-side node. Further, when the third condition is met, the first terminal or the second terminal sends the first information to the network-side node, where the third condition may be the same as or different from the first condition or the second condition.

[0202] In an embodiment of the present application, when the first entity is the first SDAP entity and the second entity is the second SDAP entity, the third entity includes at least one of the following: a PDCP entity, a Radio Resource Control (RRC) entity.

[0203] In an embodiment of the present application, when the first entity is the first PDCP entity and the second entity is the second PDCP entity, the third entity includes at least one of the following: an SDAP entity, an RLC entity, a MAC entity, an RRC entity.

[0204] In an embodiment of the present application, when the first entity is the first RLC entity and the second entity is the second RLC entity, the third entity includes at least one of the following: an SDAP entity, a PDCP entity, a MAC entity, an RRC entity.

[0205] In an embodiment of the present application, when the first entity is the first MAC entity and the second entity is the second MAC entity, the third entity includes at least one of the following: a PDCP entity, an RLC entity, a PHY entity, an RRC entity.

[0206] In an embodiment of the present application, the packet includes at least one of the following:

[0207] 1) Multiple packets of the same user;

[0208] 2) Multiple packets of different users;

[0209] For example, different users include different users under the same base station or cell or Distributed Unit (DU) or Centralized Unit (CU) or Core Network (CN) or Radio Access Network (RAN) or Public Land Mobile Network (PLMN) or network, or different users under different base stations or cells or DUs or CUs or CNs or RANs or PLMNs or networks.

[0210] 3) Multiple packets of the same UE;

[0211] 4) Multiple packets of different UEs;

[0212] For example, different UEs include different UEs of the same user (such as different UEs of the same user, including but not limited to at least one of the following: watch, glove, head-mounted display, helmet, glasses, mobile phone, AR or VR device), or different UEs of different users.

[0213] 5) Multiple packets of the same stream;

[0214] 6) Multiple packets of different streams;

[0215] For example, different streams include different streams of the same UE, or different streams of different UEs.

[0216] 7) Multiple packets of the same QoS flow;

[0217] 8) Multiple packets of different QoS flows;

[0218] For example, different QoS flows include different QoS flows of the same UE, or different QoS flows of different UEs. Alternatively, different QoS flows include different QoS flows of the same stream, or different QoS flows of different streams.

[0219] 9) Multiple packets in the same IP or User Datagram Protocol (UDP) packet;

[0220] 10) Multiple packets in different IP or UDP packets;

[0221] For example, different IP or UDP packets include different IP or UDP packets of the same UE or stream, or different IP or UDP packets of different UEs or streams.

[0222] 11) Multiple packets in the same burst;

[0223] 12) Multiple packets in different bursts;

[0224] For example, different bursts include different bursts of the same stream or IP or UDP packet or QoS flow, or different bursts of different streams or IP or UDP packets or QoS flows.

[0225] 13) Multiple packets in the same bearer;

[0226] 14) Multiple packets in different bearers;

[0227] 15) Multiple packets in the same PDU session;

[0228] 16) Multiple packets in different PDU sessions;

[0229] 17) Multiple packets in the same PDU set;

[0230] 18) Multiple packets in different PDU sets;

[0231] For example, different PDU sets include different PDU sets of the same stream or IP or UDP packet or QoS flow, or different PDU sets of different streams or IP or UDP packets or QoS flows.

[0232] 19) Multiple packets in the same PDU;

[0233] 20) Multiple packets in different PDUs;

[0234] 21) Multiple packets in the same Data Radio Bearer (DRB);

[0235] 22) Multiple packets in different DRBs;

[0236] For example, different DBRs include different DBRs of the same stream or IP or UDP packet or QoS flow, or different DBRs of different streams or IP or UDP packets or QoS flows.

[0237] 23) Multiple packages in the same business;

[0238] 24) Multiple packages in different services.

[0239] The above-mentioned packet may be at least one of the following: Packet, Burst, PDU set, PDU, Service Data Unit (SDU), DRB, Transport Block (TB).

[0240] The above grouping may be at least one of the following: Burst, PDU set, PDU, SDU, DRB, TB. For example, a Packet includes multiple Bursts, a Burst includes multiple PDU sets, a PDU set includes multiple PDUs, and the like.

[0241] In an embodiment of the present application, a first element receives first information from a second element, and the first information is related to coordination or synchronization between streams; the first element performs a first operation based on the first information so that the packets of the first element or the streams meet the synchronization requirements or coordination requirements, avoiding freezes and dizziness caused by asynchrony between streams or packets, or incoordination between pictures or audios, thereby improving the user's business experience.

[0242] See also Figure 6 , an embodiment of the present application provides a communication processing method, the specific steps of which include:

[0243] Step 601: The second element sends first information to the first element, where the first information is related to inter-stream coordination or synchronization, and the first information is used by the first element to perform a first operation;

[0244] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0245] In one implementation of the present application, the performing of the first operation includes at least one of the following:

[0246] 1) Map the stream to the corresponding QoS flow

[0247] 2) Map the stream or QoS flow to the corresponding DRB;

[0248] 3) Map the stream or QoS flow or DRB to the corresponding Bearer;

[0249] 4) Map the stream or QoS flow or DRB or Bearer to the corresponding LCG;

[0250] 5) Map the stream or QoS flow or DRB or Bearer to the corresponding LCP;

[0251] 6) Map the stream or QoS flow or DRB or Bearer to the corresponding LCH;

[0252] 7) Apply the corresponding discardTime.

[0253] In an embodiment of the present application, the second element sends the first information to the first element, including:

[0254] When the first condition is satisfied, the second element sends the first information to the first element;

[0255] Wherein, the first condition includes at least one of the following:

[0256] 1) The first requirement is not satisfied between packets or between flows;

[0257] 2) The second requirement is not satisfied between two nodes or two entities;

[0258] 3) The third requirement is not satisfied between the packets or flows of two nodes, or between the packets or flows of two entities;

[0259] 4) The delay difference between packets or between flows is greater than or equal to the first threshold;

[0260] Wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0261] In an embodiment of the present application, the second element sends the first information to the first element, including at least one of the following:

[0262] 1) The second node directly sends the first information to the first node;

[0263] 2) The second node sends the first information to the first node through a third node.

[0264] In an embodiment of the present application, the second element sends the first information to the first element, including at least one of the following:

[0265] 1) The second entity directly sends the first information to the first entity;

[0266] 2) The second entity sends the first information to the first entity through a third entity.

[0267] In an implementation manner of the present application, the first node and the second node include at least one of the following:

[0268] 1) Two nodes with synchronization requirements or coordination requirements;

[0269] 2) Two nodes where or to which two objects with synchronization requirements or coordination requirements belong.

[0270] In an implementation manner of the present application, the first entity and the second entity include at least one of the following:

[0271] 1) Two entities with synchronization requirements or coordination requirements;

[0272] 2) Two entities where or to which two objects with synchronization requirements or coordination requirements belong, or are mapped to, or correspond to.

[0273] In an implementation manner of the present application, the object includes at least one of the following: service flow, PDU session, Bearer, stream, QoS flow, DRB, RLC bearer, LCG, LCH, PDU set, PDU, packet.

[0274] In an implementation manner of the present application, the first information includes at least one of the following:

[0275] 1) Whether the seventh requirement is met between packets, or between streams, or between nodes, or between entities;

[0276] 2) Synchronization or coordination object information;

[0277] 3) Synchronization flag or coordination flag;

[0278] 4) Synchronization requirement;

[0279] 5) Coordination requirement;

[0280] 6) Time tag or timestamp;

[0281] 7) Synchronization requirement between packets;

[0282] 8) Synchronization requirement between streams;

[0283] 9) Delay requirement of packets with an association relationship or meeting the eighth requirement;

[0284] 10) Delay requirement of streams with an association relationship or meeting the ninth requirement;

[0285] Wherein, the seventh requirement, the eighth requirement, or the ninth requirement includes at least one of a synchronization requirement and a coordination requirement.

[0286] In an implementation manner of the present application, the node includes at least one of the following: a terminal, a user, and a network-side node.

[0287] In an implementation manner of the present application, when the first node is a first terminal and the second node is a second terminal, or when the first node is a first client and the second node is a second client, the third node includes at least one of the following: other terminals or clients except the first node and the second node, network-side nodes, and servers;

[0288] In an implementation manner of the present application, when the first node is a first network-side node and the second node is a second network-side node, the third node includes at least one of the following: other network-side nodes except the first node and the second node, terminals, and servers.

[0289] In an implementation manner of the present application, the entity includes at least one of the following: an SDAP entity, a PDCP entity, an RLC entity, a MAC entity, and a PHY entity.

[0290] In an implementation manner of the present application, when the first entity is a first SDAP entity and the second entity is a second SDAP entity, the third entity includes at least one of the following: a PDCP entity and an RRC entity;

[0291] In an implementation manner of the present application, when the first entity is a first PDCP entity and the second entity is a second PDCP entity, the third entity includes at least one of the following: an SDAP entity, an RLC entity, a MAC entity, and an RRC entity;

[0292] In an implementation manner of the present application, when the first entity is a first RLC entity and the second entity is a second RLC entity, the third entity includes at least one of the following: an SDAP entity, a PDCP entity, a MAC entity, and an RRC entity;

[0293] In an implementation manner of the present application, when the first entity is a first MAC entity and the second entity is a second MAC entity, the third entity includes at least one of the following: a PDCP entity, an RLC entity, a PHY entity, and an RRC entity.

[0294] In an embodiment of the present application, the packet includes at least one of the following:

[0295] 1) Multiple packets of the same user;

[0296] 2) Multiple packets of different users;

[0297] 3) Multiple packets of the same UE;

[0298] 4) Multiple packets of different UEs;

[0299] 5) Multiple packets of the same stream;

[0300] 6) Multiple packets of different streams;

[0301] For example, different streams include different streams of the same UE or different streams of different UEs.

[0302] 7) Multiple packets of the same QoS flow;

[0303] 8) Multiple packets of different QoS flows;

[0304] 9) Multiple packets in the same IP or UDP packet;

[0305] 10) Multiple packets in different IP or UDP packets;

[0306] 11) Multiple packets in the same burst;

[0307] 12) Multiple packets in different bursts;

[0308] 13) Multiple packets in the same bearer;

[0309] 14) Multiple packets in different bearers;

[0310] 15) Multiple packets in the same PDU session;

[0311] 16) Multiple packets in different PDU sessions;

[0312] 17) Multiple packets in the same PDU set;

[0313] 18) Multiple packets in different PDU sets;

[0314] 19) Multiple packets in the same PDU;

[0315] 20) Multiple packets in different PDUs;

[0316] 21) Multiple packets in the same DRB;

[0317] 22) Multiple packets in different DRBs;

[0318] 23) Multiple packets in the same service;

[0319] 24) Multiple packets in different services.

[0320] In an embodiment of the present application, the second element sends first information to the first element, and the first information is related to coordination or synchronization between streams. The first information is used by the first element to perform a first operation so that the packets or streams of the first element meet the synchronization requirements or coordination requirements, avoid freezes and dizziness caused by asynchrony between streams or packets, or incoordination between pictures or audios, and improve the user's business experience.

[0321] See also Figure 7 , an embodiment of the present application provides a communication processing device, applied to a first element, the device 700 includes:

[0322] A first receiving module 701, configured to receive first information from a second element, wherein the first information is related to inter-stream coordination or synchronization;

[0323] A first processing module 702, configured to perform a first operation according to the first information;

[0324] The first element is a first node, and the second element is a second node, or the first element is a first entity, and the second element is a second entity.

[0325] In one implementation of the present application, the performing of the first operation includes at least one of the following:

[0326] 1) Map the stream to the corresponding QoS flow;

[0327] 2) Map the stream or QoS flow to the corresponding DRB;

[0328] 3) Map the stream or QoS flow or DRB to the corresponding Bearer;

[0329] 4) Map the stream or QoS flow or DRB or Bearer to the corresponding LCG;

[0330] 5) Map the stream or QoS flow or DRB or Bearer to the corresponding LCP;

[0331] 6) Map the stream or QoS flow or DRB or Bearer to the corresponding LCH;

[0332] 7) Apply the corresponding discard timer.

[0333] In one implementation of the present application, the first receiving module 701 is further configured to:

[0334] When the first condition is met, receiving first information from the second element;

[0335] Among them, the first condition includes at least one of the following:

[0336] 1) The first requirement is not satisfied between packets or flows;

[0337] 2) The second requirement is not satisfied between two nodes or two entities;

[0338] 3) The third requirement is not satisfied between the packets or flows of two nodes, or between the packets or flows of two entities;

[0339] 4) The time delay difference between packets or flows is greater than or equal to the first threshold;

[0340] Among them, the first requirement, the second requirement, or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0341] In an implementation manner of the present application, the first processing module 702 is further configured to:

[0342] When the second condition is satisfied, perform a first operation according to the first information;

[0343] Among them, the second condition includes at least one of the following:

[0344] 1) The fourth requirement is not satisfied between packets or flows;

[0345] 2) The fifth requirement is not satisfied between two nodes or two entities;

[0346] 3) The sixth requirement is not satisfied between the packets or flows of two nodes, or between the packets or flows of two entities;

[0347] 4) The time delay difference between packets or flows is greater than or equal to the second threshold;

[0348] Among them, the fourth requirement, the fifth requirement, or the sixth requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0349] In an implementation manner of the present application, the first receiving module 701 is further configured to at least one of the following: directly receive the first information from the second node; receive the first information from the second node through the third node.

[0350] In an implementation manner of the present application, the first receiving module 701 is further configured to at least one of the following: directly receive the first information from the second entity; receive the first information from the second entity through the third entity.

[0351] In an implementation manner of the present application, the first node and the second node include at least one of the following:

[0352] 1) Two nodes with synchronization requirements or coordination requirements;

[0353] 2) Two nodes where or to which two objects with synchronization requirements or coordination requirements belong.

[0354] In an implementation manner of the present application, the first entity and the second entity include at least one of the following:

[0355] 1) Two entities with synchronization requirements or coordination requirements;

[0356] 2) Two entities where, mapped to, or corresponding to two objects with synchronization requirements or coordination requirements.

[0357] In an implementation manner of the present application, the object includes at least one of the following: service flow, PDU session, Bearer, stream, QoS flow, DRB, RLC bearer, LCG, LCH, PDU set, PDU, packet.

[0358] In an implementation manner of the present application, the first entity and the second entity correspond to the same node, or the first entity and the second entity correspond to different nodes.

[0359] In an implementation manner of the present application, the first information includes at least one of the following:

[0360] 1) Whether the seventh requirement is satisfied between packets, between flows, between nodes, or between entities;

[0361] 2) Synchronization or coordination object information;

[0362] 3) Synchronization flag or coordination flag;

[0363] 4) Synchronization requirement;

[0364] 5) Coordination requirement;

[0365] 6) Time tag or timestamp;

[0366] 7) Synchronization requirement between packets;

[0367] 8) Synchronization requirement between flows;

[0368] 9) Delay requirement of packets with an association relationship or satisfying the eighth requirement;

[0369] 10) Delay requirement of flows with an association relationship or satisfying the ninth requirement;

[0370] Wherein, the seventh requirement, the eighth requirement, or the ninth requirement includes at least one of a synchronization requirement and a coordination requirement.

[0371] In an implementation manner of the present application, whether the synchronization requirement is met between the packets includes: whether the delay difference between the packets is less than or equal to a third threshold;

[0372] Or,

[0373] whether the synchronization requirement is met between the flows includes: whether the delay difference between the flows is less than or equal to a fourth threshold.

[0374] In an implementation manner of the present application, the node includes at least one of the following: a terminal, a user, a network-side node.

[0375] In an implementation manner of the present application, when the first node is a first terminal and the second node is a second terminal, or when the first node is a first client and the second node is a second client, the third section includes at least one of the following: other terminals or clients except the first node and the second node, network-side nodes, servers.

[0376] In an implementation manner of the present application, when the first node is a first network-side node and the second node is a second network-side node, the third section includes at least one of the following: other network-side nodes except the first node and the second node, terminals, servers.

[0377] In an implementation manner of the present application, the entity includes at least one of the following: an SDAP entity, a PDCP entity, an RLC entity, a MAC entity, a PHY entity.

[0378] In an implementation manner of the present application, when the first entity is a first SDAP entity and the second entity is a second SDAP entity, the third entity includes at least one of the following: a PDCP entity, an RRC entity.

[0379] In an implementation manner of the present application, when the first entity is a first PDCP entity and the second entity is a second PDCP entity, the third entity includes at least one of the following: an SDAP entity, an RLC entity, a MAC entity, an RRC entity.

[0380] In an implementation manner of the present application, when the first entity is a first RLC entity and the second entity is a second RLC entity, the third entity includes at least one of the following: an SDAP entity, a PDCP entity, a MAC entity, an RRC entity.

[0381] In an implementation manner of the present application, when the first entity is a first MAC entity and the second entity is a second MAC entity, the third entity includes at least one of the following: a PDCP entity, an RLC entity, a PHY entity, an RRC entity.

[0382] In an embodiment of the present application, the packet includes at least one of the following:

[0383] 1) Multiple packets of the same user;

[0384] 2) Multiple packets of different users;

[0385] 3) Multiple packets of the same UE;

[0386] 4) Multiple packets of different UEs;

[0387] 5) Multiple packets of the same stream;

[0388] 6) Multiple packets of different streams;

[0389] For example, different streams include different streams of the same UE or different streams of different UEs.

[0390] 7) Multiple packets of the same QoS flow;

[0391] 8) Multiple packets of different QoS flows;

[0392] 9) Multiple packets in the same IP or UDP packet;

[0393] 10) Multiple packets in different IP or UDP packets;

[0394] 11) Multiple packets in the same burst;

[0395] 12) Multiple packets in different bursts;

[0396] 13) Multiple packets in the same bearer;

[0397] 14) Multiple packets in different bearers;

[0398] 15) Multiple packets in the same PDU session;

[0399] 16) Multiple packets in different PDU sessions;

[0400] 17) Multiple packets in the same PDU set;

[0401] 18) Multiple packets in different PDU sets;

[0402] 19) Multiple packets in the same PDU;

[0403] 20) Multiple packets in different PDUs;

[0404] 21) Multiple packets in the same DRB;

[0405] 22) Multiple packets in different DRBs;

[0406] 23) Multiple packets in the same service;

[0407] 24) Multiple packets in different services.

[0408] The apparatus provided by the embodiments of the present application can implement Figure 5 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0409] See Figure 8 , embodiments of the present application provide a communication processing apparatus, which is applied to a second element. The apparatus 800 includes:

[0410] A first sending module 801, configured to send first information to a first element, where the first information is related to inter-stream coordination or synchronization, and the first information is used for the first element to perform a first operation;

[0411] Wherein, the first element is a first node, the second element is a second node, or the first element is a first entity and the second element is a second entity.

[0412] In an implementation manner of the present application, the performing the first operation includes at least one of the following:

[0413] 1) Mapping a stream to a corresponding QoS flow

[0414] 2) Mapping a stream or a QoS flow to a corresponding DRB;

[0415] 3) Mapping a stream or a QoS flow or a DRB to a corresponding Bearer;

[0416] 4) Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding LCG;

[0417] 5) Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding LCP;

[0418] 6) Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding LCH;

[0419] 7) Applying a corresponding discardTime.

[0420] In an implementation manner of the present application, the first sending module 801 is further configured to:

[0421] When the first condition is met, send the first information to the first element;

[0422] Wherein, the first condition includes at least one of the following:

[0423] 1) The first requirement is not met between packets or flows;

[0424] 2) The second requirement is not met between two nodes or two entities;

[0425] 3) The third requirement is not met between the packets or flows of two nodes, or between the packets or flows of two entities;

[0426] 4) The delay difference between packets or flows is greater than or equal to the first threshold;

[0427] Wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

[0428] In an embodiment of the present application, the first sending module 801 is further configured to perform at least one of the following: directly send the first information to the first node; send the first information to the first node through the third node.

[0429] In an embodiment of the present application, the first sending module 801 is further configured to perform at least one of the following: directly send the first information to the first entity; send the first information to the first entity through the third entity.

[0430] In an embodiment of the present application, the first node and the second node include at least one of the following:

[0431] 1) Two nodes with synchronization requirements or coordination requirements;

[0432] 2) Two nodes where two objects with synchronization requirements or coordination requirements are located or belong to.

[0433] In an embodiment of the present application, the first entity and the second entity include at least one of the following:

[0434] 1) Two entities with synchronization requirements or coordination requirements;

[0435] 2) Two entities where two objects with synchronization requirements or coordination requirements are located or mapped or corresponding to.

[0436] In an embodiment of the present application, the object includes at least one of the following: service flow, PDU session, Bearer, stream, QoS flow, DRB, RLC bearer, LCG, LCH, PDU set, PDU, packet.

[0437] In one embodiment of the present application, the first information includes at least one of the following:

[0438] 1) Whether the seventh requirement is satisfied between packets, between flows, between nodes, or between entities;

[0439] 2) Synchronizing or coordinating object information;

[0440] 3) Synchronization markers or coordination markers;

[0441] 4) Synchronization requirements;

[0442] 5) Coordination requirements;

[0443] 6) Time tags or timestamps;

[0444] 7) Synchronization requirements between packets;

[0445] 8) Synchronization requirements between flows;

[0446] 9) Delay requirements of packets having an association relationship or satisfying the eighth requirement;

[0447] 10) Delay requirements of flows having an association relationship or satisfying the ninth requirement;

[0448] Wherein, the seventh requirement, the eighth requirement, or the ninth requirement includes at least one of synchronization requirements and coordination requirements.

[0449] In one embodiment of the present application, the node includes at least one of the following: a terminal, a user, and a network-side node.

[0450] In one embodiment of the present application, when the first node is a first terminal and the second node is a second terminal, or when the first node is a first client and the second node is a second client, the third node includes at least one of the following: other terminals or clients other than the first node and the second node, network-side nodes, and servers.

[0451] In one embodiment of the present application, when the first node is a first network-side node and the second node is a second network-side node, the third node includes at least one of the following: other network-side nodes other than the first node and the second node, terminals, and servers.

[0452] In one embodiment of the present application, the entity includes at least one of the following: an SDAP entity, a PDCP entity, an RLC entity, a MAC entity, and a PHY entity.

[0453] In an implementation manner of the present application, when the first entity is a first SDAP entity and the second entity is a second SDAP entity, the third entity includes at least one of the following: a PDCP entity, an RRC entity.

[0454] In an implementation manner of the present application, when the first entity is a first PDCP entity and the second entity is a second PDCP entity, the third entity includes at least one of the following: an SDAP entity, an RLC entity, a MAC entity, an RRC entity.

[0455] In an implementation manner of the present application, when the first entity is a first RLC entity and the second entity is a second RLC entity, the third entity includes at least one of the following: an SDAP entity, a PDCP entity, a MAC entity, an RRC entity.

[0456] In an implementation manner of the present application, when the first entity is a first MAC entity and the second entity is a second MAC entity, the third entity includes at least one of the following: a PDCP entity, an RLC entity, a PHY entity, an RRC entity.

[0457] In an embodiment of the present application, the multiple packets include at least one of the following:

[0458] 1) Multiple packets of the same user;

[0459] 2) Multiple packets of different users;

[0460] 3) Multiple packets of the same UE;

[0461] 4) Multiple packets of different UEs;

[0462] 5) Multiple packets of the same stream;

[0463] 6) Multiple packets of different streams;

[0464] For example, different streams include different streams of the same UE or different streams of different UEs.

[0465] 7) Multiple packets of the same QoS flow;

[0466] 8) Multiple packets of different QoS flows;

[0467] 9) Multiple packets in the same IP or UDP packet;

[0468] 10) Multiple packets in different IP or UDP packets;

[0469] 11) Multiple packets in the same burst;

[0470] 12) Multiple packets in different Bursts;

[0471] 13) Multiple packets in the same Bearer;

[0472] 14) Multiple packets in different Bearers;

[0473] 15) Multiple packets in the same PDU session;

[0474] 16) Multiple packets in different PDU sessions;

[0475] 17) Multiple packets in the same PDU set;

[0476] 18) Multiple packets in different PDU sets;

[0477] 19) Multiple packets in the same PDU;

[0478] 20) Multiple packets in different PDUs;

[0479] 21) Multiple packets in the same DRB;

[0480] 22) Multiple packets in different DRBs;

[0481] 23) Multiple packets in the same service;

[0482] 24) Multiple packets in different services.

[0483] The device provided by the embodiments of the present application can implement Figure 6 each process implemented by the method embodiments described above, and achieve the same technical effects. To avoid repetition, details are not described here again.

[0484] Figure 9 FIG. is a schematic diagram of the hardware structure of a terminal according to an embodiment of the present application. The terminal 900 includes, but is not limited to, at least some components such as a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 906, a display unit 905, a user input unit 907, an interface unit 908, a memory 909, and a processor 910.

[0485] Those skilled in the art can understand that the terminal 900 may further include a power source (such as a battery) for powering each component. The power source can be logically connected to the processor 910 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 9The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0486] It should be understood that in the embodiments of the present application, the input unit 904 may include a Graphics Processing Unit (GPU) 9041 and a microphone 9042. The graphics processor 9041 processes the image data of static pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 905 may include a display panel 9051, and the display panel 9051 may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. The other input devices 9032 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, which will not be elaborated here.

[0487] In the embodiments of the present application, after receiving downlink data from a network-side device, the radio frequency unit 901 may transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 may send uplink data to the network-side device. Generally, the radio frequency unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0488] The memory 909 can be used to store software programs or instructions as well as various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 909 may include a volatile memory or a non-volatile memory, or alternatively, the memory 909 may include a non-transitory memory. Among them, the non-volatile memory or the non-transitory memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (Synch link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory 909 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0489] The processor 910 may include one or more processing units; optionally, the processor 910 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor 910 either.

[0490] The terminal provided by the embodiments of the present application can implement Figure 5 or Figure 6 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0491] Please refer to Figure 10 , Figure 10 which is a structural diagram of a network-side device to which the embodiments of the present invention are applied. AsFigure 10 As shown in Figure 10 , the network-side device 1000 includes: a processor 1001, a transceiver 1002, a memory 1003, and a bus interface. Among them, the processor 1001 can be responsible for managing the bus architecture and general processing. The memory 1003 can store the data used by the processor 1001 when performing operations.

[0492] In an embodiment of the present invention, the network-side device 1000 further includes: a program stored in the memory 1003 and executable on the processor 1001. When the program is executed by the processor 1001, it implements the above Figure 5 or Figure 6 the steps in the method shown.

[0493] In Figure 10 , the bus architecture can include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors represented by the processor 1001 and the memory represented by the memory 1003 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 1002 can be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on the transmission medium.

[0494] Please refer to Figure 11 , Figure 11 which is a structural diagram of a communication device to which the embodiments of the present invention are applied. The communication device can be a first element or a second element.

[0495] As Figure 11 shown, an embodiment of the present application further provides a communication device 1100, including a processor 1101 and a memory 1302. A program or instruction executable on the processor 1101 is stored on the memory 1102. For example, when the communication device 1100 is a sending end, when the program or instruction is executed by the processor 1101, it implements the above Figure 5 steps of the method embodiment. When the communication device 1100 is a receiving end, when the program or instruction is executed by the processor 1101, it implements the above Figure 6 steps of the method embodiment and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0496] An embodiment of the present application further provides a readable storage medium. A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, it implements Figure 5 or Figure 6 the method and the various processes of the above-mentioned embodiments, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0497] Among them, the processor is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks, or optical discs, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0498] Another embodiment of the present application provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement Figure 5 or Figure 6 each process of the above-mentioned method embodiments shown and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0499] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0500] Another embodiment of the present application provides a computer program / program product. The computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement Figure 5 or Figure 6 each process of the above-mentioned method embodiments shown and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0501] The embodiments of the present application further provide a communication system, which includes a terminal and a network-side device. The terminal is used to execute each process such as Figure 5 and the above-mentioned method embodiments, and the network-side device is used to execute each process such as Figure 6 and the above-mentioned method embodiments, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0502] It should be noted that in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, the features described with reference to certain examples may be combined in other examples.

[0503] From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0504] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A communication processing method, characterized in that, including: The first element receives first information from the second element, and the first information is related to inter-stream coordination or synchronization; The first element performs a first operation according to the first information; wherein, the first element is a first node, the second element is a second node, or the first element is a first entity and the second element is a second entity.

2. The method according to claim 1, wherein The performing of the first operation includes at least one of the following: mapping a stream to a corresponding Quality of Service flow (QoS flow); mapping a stream or a QoS flow to a corresponding Data Radio Bearer (DRB); mapping a stream or a QoS flow or a DRB to a corresponding Radio Bearer; mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel Group (LCG); mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel Priority (LCP); mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel (LCH); applying a corresponding discard timer.

3. The method according to claim 1 or 2, characterized in that, The first element receives first information from the second element, including: when a first condition is satisfied, the first element receives first information from the second element; wherein, the first condition includes at least one of the following: a first requirement is not satisfied between packets or between streams; a second requirement is not satisfied between two nodes or between two entities; a third requirement is not satisfied between packets or between streams of two nodes, or between packets or between streams of two entities; the delay difference between packets or between streams is greater than or equal to a first threshold; wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

4. The method according to claim 1 or 2, characterized in that, The first element performs a first operation according to the first information, including: when a second condition is satisfied, the first element performs a first operation according to the first information; wherein, the second condition includes at least one of the following: a fourth requirement is not satisfied between packets or between streams; a fifth requirement is not satisfied between two nodes or between two entities; a sixth requirement is not satisfied between packets or between streams of two nodes, or between packets or between streams of two entities; the delay difference between packets or between streams is greater than or equal to a second threshold; wherein, the fourth requirement or the fifth requirement or the sixth requirement includes at least one of the following: synchronization requirement, coordination requirement.

5. The method according to claim 1 or 3, characterized in that, The first element receives first information from the second element, including at least one of the following: the first node directly receives first information from the second node; the first node receives first information from the second node through a third node.

6. The method according to claim 1 or 3, characterized in that The first element receives first information from the second element, including at least one of the following: the first entity directly receives first information from the second entity; the first entity receives first information from the second entity through a third entity.

7. The method according to claim 1 or 5, characterized in that, The first node and the second node include at least one of the following: two nodes with a synchronization requirement or a coordination requirement; two nodes where two objects with a synchronization requirement or a coordination requirement are located or to which they belong.

8. The method according to claim 1 or 6, characterized in that, The first entity and the second entity include at least one of the following: Two entities with synchronization requirements or coordination requirements; Two entities where two objects with synchronization requirements or coordination requirements are located, mapped, or corresponding to; 9. The method according to claim 7 or 8, characterized in that, The object includes at least one of the following: service flow, protocol data unit (PDU) session, bearer, stream, QoS flow, DRB, radio link control (RLC) bearer, LCG, LCH, PDU set, PDU, packet.

10. The method according to claim 1 or 6 or 8, characterized in that, The first entity and the second entity correspond to the same node, or the first entity and the second entity correspond to different nodes.

11. The method according to any one of claims 1 to 10, characterized in that, The first information includes at least one of the following: Whether the seventh requirement is satisfied between packets, between flows, between nodes, or between entities; Synchronization or coordination object information; Synchronization flag or coordination flag; Synchronization requirement; Coordination requirement; Time tag or timestamp; Synchronization requirement between packets; Synchronization requirement between flows; Delay requirement of packets with an association relationship or the eighth requirement; Delay requirement of flows with an association relationship or the ninth requirement; Wherein, the seventh requirement, the eighth requirement, or the ninth requirement includes at least one of synchronization requirement and coordination requirement.

12. The method according to claim 11, wherein Whether the synchronization requirement is satisfied between the packets includes: whether the delay difference between the packets is less than or equal to a third threshold; Or, Whether the synchronization requirement is satisfied between the flows includes: whether the delay difference between the flows is less than or equal to a fourth threshold.

13. The method according to claim 3 or 4 or 7 or 10 or 11, characterized in that The node includes at least one of the following: terminal, user, network-side node.

14. The method according to claim 5, wherein When the first node is a first terminal and the second node is a second terminal, or the first node is a first client and the second node is a second client, the third section includes at least one of the following: other terminals or clients except the first node and the second node, network-side nodes, servers; Or, When the first node is a first network-side node and the second node is a second network-side node, the third section includes at least one of the following: other network-side nodes except the first node and the second node, terminals, servers.

15. The method according to claim 3 or 4 or 8 or 10, characterized in that, The entity includes at least one of the following: service data adaptation protocol (SDAP) entity, packet data convergence protocol (PDCP) entity, RLC entity, media access control (MAC) entity, physical layer (PHY) entity.

16. The method according to claim 6, wherein When the first entity is a first SDAP entity and the second entity is a second SDAP entity, the third entity includes at least one of the following: PDCP entity, radio resource control (RRC) entity; Or, When the first entity is a first PDCP entity and the second entity is a second PDCP entity, the third entity includes at least one of the following: SDAP entity, RLC entity, MAC entity, RRC entity; Or, When the first entity is a first RLC entity and the second entity is a second RLC entity, the third entity includes at least one of the following: SDAP entity, PDCP entity, MAC entity, RRC entity; Or, In the case where the first entity is a first MAC entity and the second entity is a second MAC entity, the third entity includes at least one of the following: a PDCP entity, an RLC entity, a PHY entity, an RRC entity.

17. The method according to claim 3 or 4 or 9 or 11 or 12, characterized in that The packet includes: Multiple packets of the same user; Multiple packets of different users; Multiple packets of the same terminal; Multiple packets of different terminals; Multiple packets of the same stream; Multiple packets of different streams; Multiple packets of the same QoS flow; Multiple packets of different QoS flows; Multiple packets in the same IP or User Datagram Protocol (UDP) packet; Multiple packets in different IP or UDP packets; Multiple packets in the same burst; Multiple packets in different bursts; Multiple packets in the same bearer; Multiple packets in different bearers; Multiple packets in the same PDU session; Multiple packets in different PDU sessions; Multiple packets in the same PDU Set; Multiple packets in different PDU Sets; Multiple packets in the same PDU; Multiple packets in different PDUs; Multiple packets in the same DRB; Multiple packets in different DRBs; Multiple packets in the same service; Multiple packets in different services.

18. A communication processing method, characterized in that Includes: The second element sends first information to the first element, and the first information is related to inter-stream coordination or synchronization; Wherein, the first information is used for the first element to perform a first operation; The first element is a first node, the second element is a second node, or the first element is a first entity and the second element is a second entity.

19. The method according to claim 18, wherein The performing of the first operation includes at least one of the following: Mapping a stream to a corresponding QoS flow Mapping a stream or QoS flow to a corresponding DRB; Mapping a stream or QoS flow or DRB to a corresponding Bearer; Mapping a stream or QoS flow or DRB or Bearer to a corresponding LCG; Mapping a stream or QoS flow or DRB or Bearer to a corresponding LCP; Mapping a stream or QoS flow or DRB or Bearer to a corresponding LCH; Applying a corresponding discardTime.

20. The method according to claim 17, wherein The second element sending first information to the first element includes: When a first condition is satisfied, the second element sends first information to the first element; Wherein, the first condition includes at least one of the following: The first requirement is not satisfied between packets or between streams; The second requirement is not satisfied between two nodes or between two entities; The third requirement is not satisfied between the packets or streams of two nodes or between the packets or streams of two entities; The delay difference between packets or between streams is greater than or equal to a first threshold; Wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

21. The method according to claim 18 or 20, characterized in that, The second element sending first information to the first element includes at least one of the following: The second node directly sends first information to the first node; The second node sends first information to the first node through a third node.

22. The method according to claim 18 or 20, characterized in that, The second element sends first information to the first element, including at least one of the following: The second entity directly sends the first information to the first entity; The second entity sends the first information to the first entity through a third entity.

23. The method according to claim 18 or 20 or 21, characterized in that, The first node and the second node include at least one of the following: Two nodes with a synchronization requirement or a coordination requirement; Two nodes where two objects with a synchronization requirement or a coordination requirement are located or to which they belong.

24. The method according to claim 18 or 20 or 22, characterized in that, The first entity and the second entity include at least one of the following: Two entities with a synchronization requirement or a coordination requirement; Two entities where two objects with a synchronization requirement or a coordination requirement are located or mapped or corresponding to.

25. The method according to claim 23 or 24, characterized in that The object includes at least one of the following: service flow, PDU session, Bearer, stream, QoS flow, DRB, RLC bearer, LCG, LCH, PDU set, PDU, packet.

26. The method according to any one of claims 18 to 25, characterized in that, The first information includes at least one of the following: Whether the seventh requirement is satisfied between packets or between flows or between nodes or between entities; Synchronization or coordination object information; Synchronization flag or coordination flag; Synchronization requirement; Coordination requirement; Time tag or timestamp; Synchronization requirement between packets; Synchronization requirement between flows; Delay requirement of packets with an association relationship or with an eighth requirement; Delay requirement of flows with an association relationship or with a ninth requirement; Wherein, the seventh requirement or the eighth requirement or the ninth requirement includes at least one of a synchronization requirement and a coordination requirement.

27. The method according to claim 20 or 23 or 26, characterized in that The node includes at least one of the following: terminal, user, network-side node.

28. The method according to claim 21, wherein When the first node is a first terminal and the second node is a second terminal, or when the first node is a first client and the second node is a second client, the third entity includes at least one of the following: other terminals or clients except the first node and the second node, network-side nodes, servers; Or, When the first node is a first network-side node and the second node is a second network-side node, the third entity includes at least one of the following: other network-side nodes except the first node and the second node, terminals, servers.

29. The method according to claim 20 or 24 or 26, characterized in that, The entity includes at least one of the following: SDAP entity, PDCP entity, RLC entity, MAC entity, PHY entity.

30. The method according to claim 22, characterized in that, When the first entity is a first SDAP entity and the second entity is a second SDAP entity, the third entity includes at least one of the following: PDCP entity, RRC entity; Or, When the first entity is a first PDCP entity and the second entity is a second PDCP entity, the third entity includes at least one of the following: SDAP entity, RLC entity, MAC entity, RRC entity; Or, When the first entity is a first RLC entity and the second entity is a second RLC entity, the third entity includes at least one of the following: SDAP entity, PDCP entity, MAC entity, RRC entity; Or, When the first entity is a first MAC entity and the second entity is a second MAC entity, the third entity includes at least one of the following: PDCP entity, RLC entity, PHY entity, RRC entity.

31. The method according to claim 20 or 25 or 26, characterized in that, The packet includes: Multiple packets of the same user; Multiple packets of different users; Multiple packets of the same terminal; Multiple packets of different terminals; Multiple packets of the same stream; Multiple packets of different streams; Multiple packets of the same QoS flow; Multiple packets of different QoS flows; Multiple packets within the same IP or User Datagram Protocol (UDP) packet; Multiple packets in different IP or UDP packets; Multiple packets within the same burst; Multiple packets in different bursts; Multiple packets within the same bearer; Multiple packets in different bearers; Multiple packets within the same PDU session; Multiple packets in different PDU sessions; Multiple packets within the same PDU Set; Multiple packets in different PDU Sets; Multiple packets within the same PDU; Multiple packets in different PDUs; Multiple packets within the same DRB; Multiple packets in different DRBs; Multiple packets within the same service; Multiple packets in different services.

32. A communication processing device is applied to a first element, characterized in that, It includes: A first receiving module, configured to receive first information from a second element, where the first information is related to inter-stream coordination or synchronization; A first processing module, configured to perform a first operation according to the first information; Wherein, the first element is a first node, the second element is a second node, or the first element is a first entity and the second element is a second entity.

33. The device according to claim 32, wherein The performing of the first operation includes at least one of the following: Mapping a stream to a corresponding Quality of Service (QoS) flow; Mapping a stream or a QoS flow to a corresponding Data Radio Bearer (DRB); Mapping a stream or a QoS flow or a DRB to a corresponding Radio Bearer; Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel Group (LCG); Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel Priority (LCP); Mapping a stream or a QoS flow or a DRB or a Bearer to a corresponding Logical Channel (LCH); Applying a corresponding discardTimer.

34. The device according to claim 32, wherein The first processing module is further configured to: receive the first information from the second element when a first condition is met; Wherein, the first condition includes at least one of the following: The first requirement is not met between packets or between streams; The second requirement is not met between two nodes or two entities; The third requirement is not met between the packets or streams of two nodes or between the packets or streams of two entities; The delay difference between packets or between streams is greater than or equal to a first threshold; Wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

35. A communication processing device is applied to a second element, characterized in that, It includes: A first sending module, configured to send first information to a first element, where the first information is related to inter-stream coordination or synchronization, and the first information is used for the first element to perform a first operation; Wherein, the first element is a first node, the second element is a second node, or the first element is a first entity and the second element is a second entity.

36. The device according to claim 35, characterized in that The execution of the first operation includes at least one of the following: mapping the stream to the corresponding QoS flow mapping the stream or QoS flow to the corresponding DRB; mapping the stream or QoS flow or DRB to the corresponding Bearer; mapping the stream or QoS flow or DRB or Bearer to the corresponding LCG; mapping the stream or QoS flow or DRB or Bearer to the corresponding LCP; mapping the stream or QoS flow or DRB or Bearer to the corresponding LCH; applying the corresponding discardTime.

37. The device according to claim 35, characterized in that, The first sending module is further configured to: send the first information to the first element when the first condition is satisfied; wherein, the first condition includes at least one of the following: the first requirement is not satisfied between packets or between flows; the second requirement is not satisfied between two nodes or two entities; the third requirement is not satisfied between the packets or flows of two nodes or between the packets or flows of two entities; the delay difference between packets or between flows is greater than or equal to the first threshold; wherein, the first requirement or the second requirement or the third requirement includes at least one of the following: synchronization requirement, coordination requirement.

38. A communication device, characterized in that, comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implement the steps of the method according to any one of claims 1 to 31.

39. A readable storage medium, characterized in that, The program or instructions are stored on the readable storage medium, and when the program or instructions are executed by the processor of the terminal, the steps of the method according to any one of claims 1 to 31 are implemented.

Images