Communication processing method and apparatus, device and readable storage medium

Abstract

Disclosed in the present application are a communication processing method and apparatus, a device, and a readable storage medium; the method comprises: a first element receives first information from a second element, the first information being related to inter-stream coordination or synchronisation; on the basis of the first information, the first element executes a first operation; 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

Communication processing method, device, equipment and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311782617.9 filed on December 21, 2023, the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] Existing extended reality (XR) or cloud gaming (CG) services include multiple packets or multiple streams. Since the Quality of Service (QoS) requirements and operations of 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 the user service experience. Summary of the Invention

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

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

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

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

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

[0010] In a second aspect, a communication processing method is provided, comprising:

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

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

[0013] The first element is a first node, and the second element is a second node; alternatively, the first element is a first entity, and the second element is a second entity.

[0014] According to a third aspect, a communication processing device is provided, which is applied to a first element and includes:

[0015] 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;

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

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

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

[0019] 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;

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

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

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

[0023] 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 programs or instructions to implement the steps of the method described in the first aspect or the second aspect.

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

[0025] In a ninth aspect, a communication system is provided, comprising a transmitting end and a receiving end, wherein 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.

[0026] 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 the freeze and dizziness caused by the lack of synchronization between the streams or packets, or the lack of coordination between the pictures or audio, thereby improving the user's business experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0030] FIG4 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the present application;

[0031] FIG5 is a flowchart of a communication processing method according to an embodiment of the present application;

[0032] FIG6 is a second flowchart of a communication processing method provided in an embodiment of the present application;

[0033] FIG7 is a schematic diagram of a communication processing device according to an embodiment of the present application;

[0034] FIG8 is a second schematic diagram of a communication processing device provided in an embodiment of the present application;

[0035] FIG9 is a schematic diagram of a terminal provided in an embodiment of the present application;

[0036] FIG10 is a schematic diagram of a network-side device provided in an embodiment of the present application;

[0037] FIG11 is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0039] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0040] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0041] It is worth noting that the technology described in the embodiments of the present 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, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR system applications, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0042] To facilitate understanding of the embodiments of the present application, the following technical points are first introduced below:

[0043] 1. Extended reality (XR) business

[0044] XR refers to all combined real and virtual environments and human-computer interactions generated by computer technology and wearable devices. As shown in Figure 1, XR includes representative forms such as augmented reality (AR), mixed reality (MR), virtual reality (VR), and their intersections. The levels of virtual worlds range from partial sensory input to fully immersive virtual reality. A key aspect of XR is the expansion of human experience, especially those related to presence (represented by VR) and cognitive learning (represented by AR).

[0045] For VR services, the uplink is mainly based on the transmission of relatively dense small data packets. These small data packets can carry information such as gestures and controls, serving as input and reference for downlink presentation data. The downlink is mainly based on the transmission of multimedia data such as video and audio. The timely reception and presentation of these multimedia data provide users with an immersive experience. Taking downlink video data as an example, data packets arrive periodically or quasi-periodically, with data rates reaching tens or even hundreds of megabits per second (Mbps), and frame rates (FPS) are typically 60 or 120. The interval between adjacent data packets is roughly 1 / FPS second. This data generally needs to be successfully transmitted within 10 milliseconds (ms) over the air interface, and the transmission success rate must be no less than 99% or even 99.9%.

[0046] For AR services, in addition to the aforementioned dense transmission of small data packets, uplink data may also transmit multimedia data such as video and audio. Its service characteristics are similar to those of downlink services, with relatively low data rates, such as a maximum of tens of Mbps. The air interface transmission time limit can also be relaxed, for example, generally requiring successful transmission within 60ms. Downlink data transmission characteristics are basically the same as those of VR services.

[0047] Users want to interact and manipulate in extended reality, as shown in Figure 2. Actions and interactions include movements, gestures, and body reactions. Therefore, the degrees of freedom (DoF) describe the number of independent parameters used to define the movement of the viewport in 3D space.

[0048] In XR applications, users can gain information about new perspectives by turning their heads during a virtual reality experience. This head-turning action can be communicated to the base station via an uplink signal. Upon receiving the uplink signal, the base station dispatches the required downlink data for the XR user.

[0049] XR services mainly include video data, audio data, and some control signaling and special data with control functions. In wireless networks, XR service transmission mainly involves uplink and downlink video or audio data transmission and interaction between terminals (for example, user equipment (UE)) and wireless new networks (such as Long Term Evolution (LTE) or New Radio (NR), etc.). Among them, while transmitting the video and audio data itself, the UE needs to transmit some control signaling and special data with control functions through the wireless network uplink, in order to control the generation, processing and downlink wireless transmission of video and audio service data in the XR service sent by the control network to the UE.

[0050] 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, such as:

[0051] A. From the application level, it can include but not be limited to:

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

[0053] (2) User behavior data collected by sensors, such as pose or control data; the network can receive this data to determine user behavior, such as the user turning their head, and then adjust the content of the video data to be sent;

[0054] B. From the transmission protocol level, it can include:

[0055] (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;

[0056] (2) Real-time Transport Control Protocol Acknowledgment (RTCP ACK) signaling is used to control the real-time transmission of data and confirm the real-time requirements and time synchronization of business data transmission.

[0057] The network usually needs to receive these control signaling 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 related necessary control information. Based on this information, the application server needs to further generate the video and audio service data required for subsequent transmission, submit it to the wireless network for processing and transmission, and finally send this service data downlink to the UE.

[0058] 2. Packet Data Convergence Protocol (PDCP) layer and radio bearer.

[0059] The service data generated by the UE's application layer is classified into different service data flows according to their corresponding Quality of Service (QoS) requirements. Each service data flow corresponds to the same or similar QoS requirements. In the NR system, the service data flow corresponds to a QoS flow, while in the LTE system, the service data flow corresponds to an Evolved Packet System (EPS) bearer.

[0060] Service data is delivered to the access stratum (AS) in the form of packets. At the AS, it is mapped to a radio bearer based on the corresponding QoS flow or EPS bearer. A radio bearer consists of a PDCP entity, a radio link control (RLC) entity, and corresponding logical channels (located in the media access control (MAC) protocol layer).

[0061] 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 of each PDCP SDU and its corresponding PDCP PDU in the PDCP entity. The value of the PDCP SN is set according to the order in which the PDCP SDU is delivered to the PDCP entity. The PDCP SDU that arrives first will be transmitted first, and the PDCP SDU that is delivered later will be transmitted later. Specifically, the PDCP entity maintains 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. It is initialized to 0 when the PDCP entity is established. Each time a PDCP SDU is delivered from the upper layers to the corresponding PDCP entity, the PDCP entity sets the SN of the PDCP PDU corresponding to the PDCP SDU to TX_NEXT and adds 1 to TX NEXT. Afterwards, the PDCP entity adds a header file to each PDCP SDU and generates a 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 sequence for subsequent processing and transmission according to the order of the SNs contained in the PDCP PDU. SN is a sequence number that indicates the number of each PDCP SDU transmitted.

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

[0063] 3. Fifth-Generation (5G) Architecture

[0064] As shown in Figure 3, the 5G system consists of the access network (AN) and the fifth-generation mobile communication technology core network (5G Core Network, 5GC). If considering the non-standalone architecture (NSA) scenario, the fourth-generation mobile communication technology (4G) network elements must also be considered.

[0065] There are two types of ANs:

[0066] (1) Next Generation NodeB (gNB), which provides NR user plane and control plane protocol termination points for UE.

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

[0068] FIG4 shows a block diagram of a wireless communication system applicable to embodiments of the present application. The wireless communication system includes a terminal 41 and a network-side device 42 .

[0069] The terminal 41 may be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. In addition to the above-mentioned terminal devices, the terminal involved in this application can also be a chip within 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.

[0070] The network-side device 42 may include an access network device or a core network device, wherein 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 (AS), or a wireless fidelity (WiFi) node. A base station may be referred to as a Node B (NB), an evolved Node B (eNB), the next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP), or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0071] The core network equipment 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 equipment in the NR system is introduced as an example, and the specific type of the core network equipment is not limited.

[0072] The communication processing method, apparatus, communication device, and readable storage medium provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0073] 5 , an embodiment of the present application provides a communication processing method, which specifically includes steps: step 501 and step 502 .

[0074] Step 501: A first element receives first information from a second element, where the first information is related to inter-stream coordination or synchronization;

[0075] Optionally, the first information may be information of a synchronization requirement or a coordination requirement.

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

[0077] In the present application, satisfying the synchronization requirements between packets (per-Packet) or between streams (per-Stream) can be understood as at least one of the following: multiple packets or multiple streams maintain a certain synchronization relationship at the receiving end, that is, the synchronization requirements are satisfied, for example, (1) multiple packets or multiple streams are received at the receiving end at a close time or at the same time, (2) multiple packets or multiple streams maintain a certain synchronization relationship in the display cache at the receiving end, that is, the synchronization requirements or coordination requirements are satisfied, for example, multiple packets or multiple streams are displayed at the receiving end at a close time or at the same time, etc.

[0078] Meeting the coordination requirements between multiple packets or multiple streams can be understood as at least one of the following: (1) multiple packets or multiple streams are coordinated at the receiving end to achieve close or simultaneous reception time, (2) multiple packets or multiple streams are coordinated at the receiving end to achieve close or simultaneous display cache time, thereby improving the user's service experience.

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

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

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

[0082] Specifically, by controlling the mapping of flows to QoS flows, synchronization requirements or coordination requirements can be met between different flows or different packets.

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

[0084] Specifically, by controlling the mapping of streams or QoS flows to DRBs, synchronization requirements or coordination requirements can be met between different flows or different packets.

[0085] 3) Map the stream or QoS flow or DRB to the corresponding radio bearer;

[0086] Specifically, by controlling the mapping of streams or QoS flows or DRBs to bearers, synchronization requirements or coordination requirements can be met between different flows or packets of different flows.

[0087] 4) Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel group (LCG);

[0088] Specifically, by controlling the mapping of streams or QoS flows or DRBs or Bearers to LCGs, synchronization requirements or coordination requirements can be met between different flows or packets of different flows.

[0089] 5) Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel priority (LCP);

[0090] Specifically, by controlling the mapping of streams or QoS flows or DRBs or Bearers to LCPs, synchronization requirements or coordination requirements can be met between different flows or packets of different flows.

[0091] 6) Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel (Logic Channel, LCH);

[0092] For example, by controlling the mapping of streams or QoS flows or DRBs or Bearers to LCHs, synchronization requirements or coordination requirements can be met between different flows or packets of different flows.

[0093] 7) Apply the corresponding discard timer (discardTimer);

[0094] Specifically, different discardTimer controls are set for different packets or packets of different flows, so as to meet synchronization requirements or coordination requirements between different flows or packets of different flows.

[0095] The fact that the packets meet the synchronization requirement means that the delay difference between the multiple packets is less than or equal to a first preset threshold.

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

[0097] Optionally, the first preset threshold value may be defined by a protocol, or configured by a server, a core network, a base station, or an application layer.

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

[0099] 1) The delay difference between multiple packets received at the receiving end;

[0100] If the delay difference between 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 lack of synchronization between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0101] 2) The delay difference between multiple packets sent at the sending end;

[0102] 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 lack of synchronization between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

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

[0104] 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 lack of synchronization between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

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

[0106] If the delay difference between one or more packets sent at the sending end and the delay difference between 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 and dizziness caused by the lack of synchronization between multiple packets, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0107] 5) The delay difference between multiple packets in the display buffer;

[0108] If the delay difference between 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 service experience.

[0109] 6) The delay difference of multiple packets arriving at the display cache.

[0110] If the delay difference between multiple packets reaching 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 service experience.

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

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

[0113] 1) The delay difference between multiple streams sent at the sending end;

[0114] 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 lack of synchronization between multiple streams, or the incoordination between the pictures or audio, thereby improving the user's service experience.

[0115] 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;

[0116] If the delay difference between the reception 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 and dizziness caused by the lack of synchronization between multiple streams, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0117] 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;

[0118] 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 and dizziness caused by the lack of synchronization between multiple streams, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0119] 4) Delay differences between multiple streams in the display cache;

[0120] If the delay difference between 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 lack of synchronization between the multiple streams, or the incoordination between the pictures or audio, thereby improving the user's service experience.

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

[0122] If the delay difference between 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 lack of synchronization between multiple streams, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0123] 6) The delay difference between multiple streams received at the receiving end.

[0124] If the delay difference between 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 lack of synchronization between multiple streams, or the incoordination between the picture or audio, thereby improving the user's service experience.

[0125] Specifically, the average delay of the preset packets in a flow is calculated within a preset window, duration, or period, and the delay difference between the two or more flows is the difference in the calculated average delays. It will be appreciated that the average delay of the preset packets in a flow calculated within a preset window, duration, or period can represent the service speeds or travel speeds of the two or more flows, and a delay difference less than a second preset threshold indicates that the service speeds or travel speeds of the two or more flows are similar.

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

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

[0128] 2) The average delay of multiple streams at the sending end;

[0129] 3) The average delay between the reception of one or more streams at the receiving end and the transmission of other streams at the sending end;

[0130] 4) The average delay between the transmission of one or more streams at the sending end and the reception of other streams at the receiving end;

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

[0132] 6) Average delay of multiple streams reaching the display cache.

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

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

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

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

[0137] It can be understood that between packets refers to between multiple packets, and between flows refers to between multiple flows, wherein multiple packets include two or more packets, and multiple flows include two or more flows.

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

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

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

[0141] It is understood that if the delay difference between packets or flows is less than the first threshold, the packets or flows meet the first requirement. The delay difference between packets or flows includes at least one of the following: a delay difference in transmission time between packets or flows, a delay difference in reception time between packets or flows, a delay difference in arrival at the display buffer between packets or flows, and a delay difference in the display buffer between packets or flows.

[0142] The first requirement, the second requirement, or the third requirement includes at least one of the following: synchronization requirement and coordination requirement.

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

[0144] For example, failure to meet synchronization requirements between packets or between streams includes at least one of the following: (1) failure to maintain a certain synchronization relationship between packets or between streams in the first element, that is, failure to meet synchronization requirements, for example, different reception times of the first element between packets or between streams; (2) failure to maintain a certain synchronization relationship between packets or between streams in the display cache of the first element, that is, failure to meet synchronization requirements, for example, different display cache times of the first element between packets or between streams.

[0145] For example, the coordination requirements between packets or streams are not met, including at least one of the following: (1) the reception time of the first element between packets or streams is different, and coordination is needed to achieve close or simultaneous reception time; (2) the display cache time of the first element between packets or streams is different, and coordination is needed to achieve close or simultaneous display cache time.

[0146] For example, failure to meet the synchronization requirement between two nodes or two entities includes failure to meet the synchronization requirement between packets or flows of the two nodes or between packets or flows of the two entities.

[0147] For example, failure to meet the coordination requirement between two nodes or two entities includes failure to meet the coordination requirement between packets or flows of the two nodes or between packets or flows of two entities.

[0148] In one embodiment of the present application, the first element performs a first operation according to the first information, including:

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

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

[0151] 1) The fourth requirement is not met between packets or flows;

[0152] 2) The fifth requirement is not met between two nodes or two entities;

[0153] 3) The sixth requirement is not met between packets or flows between two nodes, or between packets or flows between two entities;

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

[0155] The fourth requirement, the fifth requirement, or the sixth requirement includes at least one of the following: synchronization requirement and coordination requirement.

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

[0157] In one embodiment of the present application, the first element receives first information from the second element, including at least one of the following:

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

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

[0160] In one embodiment of the present application, the first element receives first information from the second element, including at least one of the following:

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

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

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

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

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

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

[0167] 1) Two entities that need to synchronize or coordinate;

[0168] 2) Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to each other.

[0169] In one embodiment 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.

[0170] In an embodiment 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.

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

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

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

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

[0175] 2) Synchronize or coordinate object information;

[0176] 3) synchronization mark or coordination mark;

[0177] 4) Synchronization requirements;

[0178] Optionally, a synchronization requirement is used to express the need to ensure that packets or flows are transmitted and processed according to a specific time relationship.

[0179] 5) coordination needs;

[0180] Optionally, coordination requirements are used to indicate the need to ensure that packets or flows are sent and processed in a specific order, timing, or condition to ensure the coherence, effectiveness, and correctness of communications.

[0181] 6) Time label or timestamp;

[0182] The above-mentioned time label or time stamp is used to indicate the time information of the corresponding packet, flow, node or entity.

[0183] 7) Synchronization requirements between packages;

[0184] Optionally, inter-packet coordination requirements are used to ensure that data packets can be transmitted and processed in a predefined, coordinated manner.

[0185] 8) Synchronization requirements between streams;

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

[0187] 9) Delay requirements for packets with related relationships or requirements of the eighth requirement;

[0188] Among them, packages with an association relationship refer to packages that have dependencies or sequential requirements.

[0189] Optionally, the delay requirement is used to indicate the maximum time delay allowed for transmission from the source to the destination.

[0190] 10) There are delay requirements for flows that are related or have the ninth requirement;

[0191] Among them, the associated flow refers to the existence of dependency or sequential requirements between flows.

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

[0193] In one embodiment of the present application, whether the packets meet the synchronization requirement includes: whether the delay difference between the packets is less than or equal to a third threshold;

[0194] or,

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

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

[0197] 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 (eg, a server).

[0198] In one embodiment of the present application, 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 other than the first node and the second node, network side nodes, and servers.

[0199] Optionally, the network side node includes but is not limited to at least one of a base station, an access and mobility management function (AMF), and a user plane function (UPF).

[0200] 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 section includes at least one of the following: other network side nodes other than the first node and the second node, a terminal, and a server.

[0201] In one embodiment 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 layer (PHY) entity.

[0202] Taking the coordination of synchronization requirements between PDCP entities as an example, two PDCP entities of the same terminal exchange first information, and further, two SDAP entities of the same terminal exchange first information. For another example, two PDCP entities of different terminals exchange first information, and further, two SDAP entities of different terminals exchange first information. Based on the first information, the PDCP entity performs at least one of the following: mapping streams or packets requiring synchronization to corresponding bearers; mapping streams or packets that meet the second condition to corresponding bearers.

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

[0204] In one embodiment 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 a Radio Resource Control (RRC) entity.

[0205] In one embodiment 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.

[0206] In one embodiment 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.

[0207] In one embodiment 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.

[0208] In one embodiment of the present application, the package includes at least one of the following:

[0209] 1) Multiple packages from the same user;

[0210] 2) Multiple packages from different users;

[0211] For example, different users include different users under the same base station or cell (Cell) or distributed unit (Distributed Unit, DU) or centralized unit (Centralized Unit, CU) or core network (Core Network, CN) or radio access network (Radio Acess Network, RAN) or public land mobile network (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.

[0212] 3) Multiple packets from the same UE;

[0213] 4) Multiple packets from different UEs;

[0214] 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: watches, gloves, head displays, helmets, glasses, mobile phones, AR or VR devices), or different UEs of different users.

[0215] 5) Multiple packets in the same stream;

[0216] 6) Multiple packets from different streams;

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

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

[0219] 8) Multiple packets with different QoS flows;

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

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

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

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

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

[0225] 12) Multiple packets in different bursts;

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

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

[0228] 14) Multiple packages in different Bearers;

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

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

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

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

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

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

[0235] 20) Multiple packets in different PDUs;

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

[0237] 22) Multiple packets in different DRBs;

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

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

[0240] 24) Multiple packages in different services.

[0241] 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).

[0242] 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, etc.

[0243] 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 the freeze and dizziness caused by the lack of synchronization between the streams or packets, or the lack of coordination between the pictures or audio, thereby improving the user's business experience.

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

[0245] 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 is used by the first element to perform a first operation.

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

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

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

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

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

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

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

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

[0254] 7) Apply the corresponding discardTime.

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

[0256] When a first condition is met, the second element sends first information to the first element;

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

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

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

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

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

[0262] The first requirement, the second requirement, or the third requirement includes at least one of the following: synchronization requirement and coordination requirement.

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

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

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

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

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

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

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

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

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

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

[0273] 1) Two entities that need to synchronize or coordinate;

[0274] 2) Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to each other.

[0275] In one 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.

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

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

[0278] 2) Synchronize or coordinate object information;

[0279] 3) synchronization mark or coordination mark;

[0280] 4) Synchronization requirements;

[0281] 5) coordination needs;

[0282] 6) Time label or timestamp;

[0283] 7) Synchronization requirements between packages;

[0284] 8) Synchronization requirements between streams;

[0285] 9) Delay requirements for packets with related relationships or requirements of the eighth requirement;

[0286] 10) There are delay requirements for flows that are related or have the ninth requirement;

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

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

[0289] 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 section includes at least one of the following: other terminals or clients other than the first node and the second node, a network side node, and a server;

[0290] 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 section includes at least one of the following: other network side nodes other than the first node and the second node, a terminal, and a server.

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

[0292] In one embodiment 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;

[0293] In one embodiment 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;

[0294] In one embodiment 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;

[0295] In one embodiment 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.

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

[0297] 1) Multiple packages from the same user;

[0298] 2) Multiple packages from different users;

[0299] 3) Multiple packets from the same UE;

[0300] 4) Multiple packets from different UEs;

[0301] 5) Multiple packets in the same stream;

[0302] 6) Multiple packets from different streams;

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

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

[0305] 8) Multiple packets with different QoS flows;

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

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

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

[0309] 12) Multiple packets in different bursts;

[0310] 13) Multiple packages in the same Bearer;

[0311] 14) Multiple packages in different Bearers;

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

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

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

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

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

[0317] 20) Multiple packets in different PDUs;

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

[0319] 22) Multiple packets in different DRBs;

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

[0321] 24) Multiple packages in different services.

[0322] 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 the freeze and dizziness caused by the lack of synchronization between streams or packets, or the lack of coordination between pictures or audio, and improve the user's business experience.

[0323] 7 , an embodiment of the present application provides a communication processing device, which is applied to a first element. The device 700 includes:

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

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

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

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

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

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

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

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

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

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

[0334] 7) Apply the corresponding discard timer.

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

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

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

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

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

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

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

[0342] The first requirement, the second requirement, or the third requirement includes at least one of the following: synchronization requirement and coordination requirement.

[0343] In one embodiment of the present application, the first processing module 702 is further configured to:

[0344] When a second condition is met, performing a first operation according to the first information;

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

[0346] 1) The fourth requirement is not met between packets or flows;

[0347] 2) The fifth requirement is not met between two nodes or two entities;

[0348] 3) The sixth requirement is not met between packets or flows between two nodes, or between packets or flows between two entities;

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

[0350] The fourth requirement, the fifth requirement, or the sixth requirement includes at least one of the following: synchronization requirement and coordination requirement.

[0351] In one embodiment of the present application, the first receiving module 701 is further configured to perform at least one of the following: directly receiving the first information from the second node; or receiving the first information from the second node through a third node.

[0352] In one embodiment of the present application, the first receiving module 701 is further configured to perform at least one of the following: directly receiving the first information from the second entity; or receiving the first information from the second entity through a third entity.

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

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

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

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

[0357] 1) Two entities that need to synchronize or coordinate;

[0358] 2) Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to each other.

[0359] In one 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.

[0360] In an embodiment 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.

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

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

[0363] 2) Synchronize or coordinate object information;

[0364] 3) synchronization mark or coordination mark;

[0365] 4) Synchronization requirements;

[0366] 5) coordination needs;

[0367] 6) Time label or timestamp;

[0368] 7) Synchronization requirements between packages;

[0369] 8) Synchronization requirements between streams;

[0370] 9) Delay requirements for packets with related relationships or requirements of the eighth requirement;

[0371] 10) There are delay requirements for flows that are related or have the ninth requirement;

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

[0373] In one embodiment of the present application, whether the packets meet the synchronization requirement includes: whether the delay difference between the packets is less than or equal to a third threshold;

[0374] or,

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

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

[0377] In one embodiment of the present application, 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 other than the first node and the second node, network side nodes, and servers.

[0378] 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 section includes at least one of the following: other network side nodes other than the first node and the second node, a terminal, and a server.

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

[0380] In one embodiment 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.

[0381] In one embodiment 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.

[0382] In one embodiment 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.

[0383] In one embodiment 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.

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

[0385] 1) Multiple packages from the same user;

[0386] 2) Multiple packages from different users;

[0387] 3) Multiple packets from the same UE;

[0388] 4) Multiple packets from different UEs;

[0389] 5) Multiple packets in the same stream;

[0390] 6) Multiple packets from different streams;

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

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

[0393] 8) Multiple packets with different QoS flows;

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

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

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

[0397] 12) Multiple packets in different bursts;

[0398] 13) Multiple packages in the same Bearer;

[0399] 14) Multiple packages in different Bearers;

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

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

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

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

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

[0405] 20) Multiple packets in different PDUs;

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

[0407] 22) Multiple packets in different DRBs;

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

[0409] 24) Multiple packages in different services.

[0410] The device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0411] 8 , an embodiment of the present application provides a communication processing device, which is applied to a second element. The device 800 includes:

[0412] A first sending module 801 is 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;

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

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

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

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

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

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

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

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

[0421] 7) Apply the corresponding discardTime.

[0422] In one embodiment of the present application, the first sending module 801 is further configured to:

[0423] When a first condition is met, sending first information to the first element;

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

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

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

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

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

[0429] The first requirement, the second requirement, or the third requirement includes at least one of the following: synchronization requirement and coordination requirement.

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

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

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

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

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

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

[0436] 1) Two entities that need to synchronize or coordinate;

[0437] 2) Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to each other.

[0438] In one 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.

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

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

[0441] 2) Synchronize or coordinate object information;

[0442] 3) synchronization mark or coordination mark;

[0443] 4) Synchronization requirements;

[0444] 5) coordination needs;

[0445] 6) Time label or timestamp;

[0446] 7) Synchronization requirements between packages;

[0447] 8) Synchronization requirements between streams;

[0448] 9) Delay requirements for packets with related relationships or requirements of the eighth requirement;

[0449] 10) There are delay requirements for flows that are related or have the ninth requirement;

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

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

[0452] 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 section 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.

[0453] 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 section includes at least one of the following: other network side nodes other than the first node and the second node, a terminal, and a server.

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

[0455] In one embodiment 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.

[0456] In one embodiment 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.

[0457] In one embodiment 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.

[0458] In one embodiment 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.

[0459] In an embodiment of the present application, the plurality of packages include at least one of the following:

[0460] 1) Multiple packages from the same user;

[0461] 2) Multiple packages from different users;

[0462] 3) Multiple packets from the same UE;

[0463] 4) Multiple packets from different UEs;

[0464] 5) Multiple packets in the same stream;

[0465] 6) Multiple packets from different streams;

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

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

[0468] 8) Multiple packets with different QoS flows;

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

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

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

[0472] 12) Multiple packets in different bursts;

[0473] 13) Multiple packages in the same Bearer;

[0474] 14) Multiple packages in different Bearers;

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

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

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

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

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

[0480] 20) Multiple packets in different PDUs;

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

[0482] 22) Multiple packets in different DRBs;

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

[0484] 24) Multiple packages in different services.

[0485] The device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0486] Figure 9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application. The terminal 900 includes, but is not limited to, at least some of the components including 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.

[0487] Those skilled in the art will appreciate that the terminal 900 may further include a power source (such as a battery) for powering various components. The power source may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0488] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video 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 a touch panel 9071 and at least one of 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. 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, and an operating stick, which will not be repeated here.

[0489] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 901 may transmit the data to the processor 910 for processing. Furthermore, the RF unit 901 may send uplink data to the network-side device. Typically, the RF unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0490] The memory 909 can be used to store software programs or instructions and 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, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 909 may include a volatile memory or a non-volatile memory, or the memory 909 may include a non-transient memory. Among them, the non-volatile memory or non-transient 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0491] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0492] The terminal provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 or Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0493] Please refer to Figure 10, which is a block diagram of a network-side device used in an embodiment of the present invention. As shown in Figure 10, network-side device 1000 includes a processor 1001, a transceiver 1002, a memory 1003, and a bus interface. Processor 1001 may be responsible for managing the bus architecture and general processing. Memory 1003 may store data used by processor 1001 when performing operations.

[0494] In one 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 , which implements the steps of the method shown in FIG. 5 or FIG. 6 when executed by the processor 1001 .

[0495] In Figure 10 , the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 1001 and memory represented by memory 1003. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and are not further described herein. The bus interface provides an interface. The transceiver 1002 can be multiple components, including a transmitter and a receiver, providing a means for communicating with various other devices over a transmission medium.

[0496] Please refer to FIG. 11 , which is a structural diagram of a communication device applied in an embodiment of the present invention. The communication device may be a first element or a second element.

[0497] As shown in Figure 11, an embodiment of the present application also provides a communication device 1100, including a processor 1101 and a memory 1302, and the memory 1102 stores programs or instructions that can be run on the processor 1101. For example, when the communication device 1100 is a transmitting end, the program or instruction is executed by the processor 1101 to implement the various steps of the method embodiment of Figure 5 above. When the communication device 1100 is a receiving end, the program or instruction is executed by the processor 1101 to implement the various steps of the method embodiment of Figure 6 above and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0498] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method of Figure 5 or Figure 6 and the various processes of the above-mentioned embodiments are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0499] The processor is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0500] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes shown in Figure 5 or Figure 6 and the various method embodiments mentioned above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0501] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0502] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes shown in Figure 5 or Figure 6 and the various method embodiments described above, and can achieve the same technical effects. To avoid repetition, they are not described here.

[0503] An embodiment of the present application also provides a communication system, which includes a terminal and a network-side device. The terminal is used to execute the various processes shown in Figure 5 and the above-mentioned method embodiments, and the network-side device is used to execute the various processes shown in Figure 6 and the above-mentioned method embodiments, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0504] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted 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 opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

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

Claims

1. A communication processing method, comprising: The first element receives first information from the second element, the first information being related to inter-stream coordination or synchronization; The first element performs a first operation according to the first information; 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.

2. The method according to claim 1, wherein: The performing of the first operation includes at least one of the following: Map the stream to the corresponding QoS flow; Map the stream or QoS flow to the corresponding data radio bearer DRB; Map the stream or QoS flow or DRB to the corresponding radio bearer; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel group LCG; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel priority LCP; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel LCH; The corresponding discard timer discardTimer is applied.

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

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

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

6. The method according to claim 1 or 3, wherein: The first element receives first information from the second element, including at least one of the following: The first entity directly receives the 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, wherein: The first node and the second node include at least one of the following: Two nodes that need synchronization or coordination; Two nodes where two objects that need to be synchronized or coordinated are located or belong to.

8. The method according to claim 1 or 6, wherein: The first entity and the second entity include at least one of the following: Two entities that have synchronization needs or coordination needs; Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to.

9. The method according to claim 7 or 8, wherein: 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, 6 or 8, wherein: 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, wherein: The first information includes at least one of the following: Whether the seventh requirement is met between packets, flows, nodes or entities; Synchronize or coordinate object information; Synchronous marking or coordination marking; Synchronization requirements; Coordinate needs; time label or timestamp; Synchronization requirements between packages; The need for synchronization between streams; The latency requirements of packets with associated relationships or eighth requirements; There are associated relationships or delay requirements for the ninth requirement of the flow; The seventh requirement, the eighth requirement or the ninth requirement includes at least one of a synchronization requirement and a coordination requirement.

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

13. The method according to claim 3 or 4 or 7 or 10 or 11, wherein: The node includes at least one of the following: a terminal, a user, and a network side node.

14. The method according to claim 5, wherein: In the case where 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 other than the first node and the second node, a network side node, and a server; or, In the case where 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, a terminal, and a server.

15. The method according to claim 3 or 4 or 8 or 10, wherein: 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 media access control MAC entity, and a physical layer PHY entity.

16. The method according to claim 6, wherein: In the case where 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, a radio resource control RRC entity; or, In the case where 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; or, In the case where 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; 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, a RLC entity, a PHY entity, and an RRC entity.

17. The method according to claim 3 or 4 or 9 or 11 or 12, wherein: The package includes: Multiple packages for the same user; Multiple packages for different users; Multiple packages for the same terminal; Multiple packages for different terminals; Multiple packets of the same stream; Multiple packages in different streams; Multiple packets of the same QoS flow; Multiple packets with different QoS flows; Multiple packets in the same IP or 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 packages in the same business; Multiple packages in different businesses.

18. A communication processing method, comprising: The second element sends first information to the first element, wherein 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, and 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: Map the stream to the corresponding QoS flow Map the stream or QoS flow to the corresponding DRB; Map the stream or QoS flow or DRB to the corresponding Bearer; Map the stream or QoS flow or DRB or Bearer to the corresponding LCG; Map the stream or QoS flow or DRB or Bearer to the corresponding LCP; Map the stream or QoS flow or DRB or Bearer to the corresponding LCH; The corresponding discardTime of the application.

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

21. The method according to claim 18 or 20, wherein: The second element sends first information to the first element, including at least one of the following: The second node directly sends the first information to the first node; The second node sends the first information to the first node through the third node.

22. The method according to claim 18 or 20, wherein: 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 the third entity.

23. The method according to claim 18, 20 or 21, wherein: The first node and the second node include at least one of the following: Two nodes that need synchronization or coordination; Two nodes where two objects that need to be synchronized or coordinated are located or belong to.

24. The method according to claim 18, 20 or 22, wherein: The first entity and the second entity include at least one of the following: Two entities that have synchronization needs or coordination needs; Two entities where two objects with synchronization or coordination requirements are located, mapped, or correspond to.

25. The method according to claim 23 or 24, wherein: 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, wherein: The first information includes at least one of the following: Whether the seventh requirement is met between packets, flows, nodes or entities; Synchronize or coordinate object information; Synchronous marking or coordination marking; Synchronization requirements; Coordinate needs; time label or timestamp; Synchronization requirements between packages; The need for synchronization between streams; The latency requirements of packets with associated relationships or eighth requirements; There are associated relationships or delay requirements for the ninth requirement of the flow; The seventh requirement, 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, 23 or 26, wherein: The node includes at least one of the following: a terminal, a user, and a network side node.

28. The method of claim 21, wherein: In the case where 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 other than the first node and the second node, network side nodes, and servers; or, In the case where 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, a terminal, and a server.

29. The method according to claim 20, 24 or 26, wherein: 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.

30. The method of claim 22, wherein: In the case where 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; or, In the case where 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; or, In the case where 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; 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, a RLC entity, a PHY entity, and an RRC entity.

31. The method of claim 20, 25 or 26, wherein: The package includes: Multiple packages for the same user; Multiple packages for different users; Multiple packages for the same terminal; Multiple packages for different terminals; Multiple packets of the same stream; Multiple packages in different streams; Multiple packets of the same QoS flow; Multiple packets with different QoS flows; Multiple packets in the same IP or 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 packages in the same business; Multiple packages in different businesses.

32. A communication processing device, applied to a first element, comprising: 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; A first processing module, configured to perform a first operation according to the first information; 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.

33. The device according to claim 32, wherein: The performing of the first operation includes at least one of the following: Map the stream to the corresponding QoS flow; Map the stream or QoS flow to the corresponding data radio bearer DRB; Map the stream or QoS flow or DRB to the corresponding radio bearer; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel group LCG; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel priority LCP; Map the stream or QoS flow or DRB or Bearer to the corresponding logical channel LCH; Apply the corresponding discardTimer.

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

35. A communication processing device, applied to a second element, comprising: 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; 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.

36. The device according to claim 35, wherein The performing of the first operation includes at least one of the following: Map the stream to the corresponding QoS flow Map the stream or QoS flow to the corresponding DRB; Map the stream or QoS flow or DRB to the corresponding Bearer; Map the stream or QoS flow or DRB or Bearer to the corresponding LCG; Map the stream or QoS flow or DRB or Bearer to the corresponding LCP; Map the stream or QoS flow or DRB or Bearer to the corresponding LCH; The corresponding discardTime of the application.

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

38. A communication device, 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 according to any one of claims 1 to 31.

39. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor of a terminal, implements the steps of the method as claimed in any one of claims 1 to 31.

Images