Information acquisition method and apparatus, communication device and storage medium

Abstract

The application discloses an information acquisition method and apparatus, a communication device, and a storage medium, belonging to the technical field of communication. The information acquisition method comprises: a first node receiving first information from a second node, the first information being information related to a processing request among a plurality of streams or a plurality of packets. The processing request comprises at least one of the following: a coordination request and a synchronization request. The first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

Description

Information acquisition method, device, communication equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202311775709.4 filed in China 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 an information acquisition method, apparatus, communication equipment and storage medium. Background Art

[0004] Existing Extended Reality (XR) or Cloud Gaming (CG) services can include multiple streams or Quality of Service (QoS) flows. Different streams or QoS flows may be handled differently. However, to improve the user experience, synchronization and coordination between different streams or QoS flows must be guaranteed.

[0005] In the prior art, the QoS requirements and operations between various flows or packets are independent, and coordination and synchronization between multiple flows or multiple packets are not defined, so that effective coordination and synchronization between flows or packets cannot be performed. Summary of the Invention

[0006] The embodiments of the present application provide an information acquisition method, apparatus, communication equipment, and storage medium, which can solve the problem that the QoS requirements and operations between various streams or packets are independent, and coordination and synchronization between multiple streams or multiple packets are not defined, making it impossible to perform effective coordination and synchronization processing between streams or packets.

[0007] In a first aspect, a method for obtaining information is provided, the method comprising: a first node receiving first information from a second node, the first information being information related to processing requirements between multiple streams or multiple packets, the processing requirements comprising at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0008] In a second aspect, an information acquisition device is provided, applied to a first node, the device comprising: a receiving module. The receiving module is configured to receive first information from a second node, the first information being information related to a processing requirement between multiple flows or multiple packets, the processing requirement comprising at least one of the following: a coordination requirement and a synchronization requirement; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers within the same node.

[0009] In a third aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0010] In a fourth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive first information from a second node, the first information being information related to processing requirements between multiple streams or multiple packets, the processing requirements including at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0011] In a fifth aspect, a method for obtaining information is provided, which includes: a second node sends first information to a first node, where the first information is information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0012] In a sixth aspect, an information acquisition device is provided, applied to a second node, the device comprising: a sending module. The sending module is configured to send first information to a first node, the first information being information related to processing requirements between multiple flows or multiple packets, the processing requirements including at least one of the following: a coordination requirement and a synchronization requirement; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers within the same node.

[0013] In the seventh aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the fifth aspect are implemented.

[0014] In an eighth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to send first information to a first node, the first information being information related to processing requirements between multiple streams or multiple packets, the processing requirements including at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0015] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the fifth aspect are implemented.

[0016] In the tenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or implement the steps of the method as described in the fifth aspect.

[0017] In the eleventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the information acquisition method as described in the first aspect, or to implement the steps of the information acquisition method as described in the fifth aspect.

[0018] In the twelfth aspect, a wireless communication system is provided, including: a first node and a second node, wherein the first node can be used to execute the steps of the method described in the first aspect, and the second node can be used to execute the steps of the method described in the fifth aspect.

[0019] In an embodiment of the present application, the first node can receive first information from the second node, that is, information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of coordination requirements and synchronization requirements to obtain coordination requirements, synchronization requirements, etc. between streams. Therefore, the first node can define coordination and synchronization between multiple streams based on the information related to processing requirements between multiple streams or multiple packets, thereby performing effective coordination and synchronization processing between streams or packets to meet the processing requirements between multiple streams or multiple packets. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0021] FIG2A is one of the schematic diagrams of the architecture of a protocol stack provided by the related art;

[0022] FIG2B is a second schematic diagram of the architecture of a protocol stack provided by the related art;

[0023] FIG3 is a flowchart of an information acquisition method according to an embodiment of the present application;

[0024] FIG4 is a second flowchart of an information acquisition method provided in an embodiment of the present application;

[0025] FIG5 is a schematic diagram of a structure of an information acquisition device according to an embodiment of the present application;

[0026] FIG6 is a second structural diagram of an information acquisition device provided in an embodiment of the present application;

[0027] FIG7 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

[0028] FIG8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0029] FIG9 is a schematic diagram of a hardware structure of a network side device according to an embodiment of the present application;

[0030] FIG10 is a second schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

[0034] The terms "at least one" and "at least one of" in this application refer to any one, any two, or a combination of more than two of the objects included. For example, at least one of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two" means two or more, and its meaning is similar to "at least one".

[0035] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 the embodiments of the present 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 illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0036] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. 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. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, 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, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), 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 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.

[0037] 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 mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0038] The following explains some concepts and / or terms involved in an information acquisition method, apparatus, device, and storage medium provided in an embodiment of the present application.

[0039] 1. XR (Extended Reality)

[0040] XR refers to all combined real and virtual environments and human-computer interactions generated by computer technology and wearable devices. It 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).

[0041] For VR services, the uplink primarily involves the transmission of densely packed small data packets. These packets carry information such as gestures and controls, serving as input and reference for downlink presentation data. The downlink primarily transmits multimedia data such as video and audio, providing users with an immersive experience through the timely reception and presentation of this multimedia data. For example, downlink video data arrives periodically or quasi-periodically, with data rates reaching tens or even hundreds of Mbps. The frame rate (FPS) is typically 60 or 120, and the interval between adjacent packets is roughly 1 / FPS second. This data must typically be successfully transmitted over the air interface within 10ms, with a transmission success rate of at least 99% or even 99.9%.

[0042] For AR services, in addition to the above-mentioned intensive transmission of small data packets, uplink may also transmit multimedia data such as video and audio. Its service characteristics are similar to those of downlink. The data rate is usually relatively low, for example, at most tens of Mbps, and the time limit for air interface transmission can be relaxed. For example, successful transmission generally requires within 60ms. The downlink data transmission characteristics are basically the same as those of VR services.

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

[0044] 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 / audio data transmission and interaction between terminals and wireless new networks (such as LTE / NR, etc.). Among them, while transmitting the video and audio data themselves, the terminal needs to uplink transmit some control signaling and special data with control functions through the wireless network 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 terminal.

[0045] These control information and special data with control functions include some service control data generated by the terminal XR application encoder and control data information included in the service transmission protocol, such as:

[0046] From the application level, it can include (but not limited to):

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

[0048] User behavior data collected by sensors; the network can judge user behavior by receiving this data, such as the user turning their head as mentioned above, and then adjust the content of the video data sent.

[0049] From the transport protocol level, this can include:

[0050] For downlink audio / video service transmission, the Transmission Control Protocol (TCP) acknowledgement (ACK) signaling (i.e., TCP feedback) determines whether the network can continue to send subsequent frames based on whether the corresponding video / audio frame has been acknowledged by the terminal.

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

[0052] The network typically needs to promptly and reliably receive these control signaling and special data from the terminal to obtain the current service transmission status 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 terminal.

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

[0054] The service data generated by the terminal's application layer (APP) 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, a service data flow corresponds to a QoS flow, while in the LTE system, a service data flow corresponds to an Evolved Packet System (EPS) bearer.

[0055] Service data is delivered to the access stratum (AS) in the form of packets. The AS then maps these packets to a radio bearer based on the corresponding QoS flow (NR) or EPS bearer (LTE). A radio bearer consists of a PDCP entity (PDCP protocol layer processing entity), a radio link control (RLC) entity (PDCP protocol layer processing entity), and the corresponding logical channels (located in the media access control (MAC) protocol layer).

[0056] When a data packet submitted to the AS is mapped to a radio bearer, it will be submitted 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 submitted to the PDCP entity. The PDCP SDU that arrives first will be transmitted first, and the PDCP SDU that is submitted 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. After that, 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 layer) 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.

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

[0058] 3. Network architecture and air interface protocol stack

[0059] The network system consists of an access network and a core network. There are two types of access networks: gNB, which provides the termination point for the NR user and control plane protocols for terminals; and ng-eNB, which provides the termination point for the user and control plane protocols of the Evolved-UMTS Terrestrial Radio Access (E-UTRA) for terminals.

[0060] As shown in Figure 2A, the user plane protocol stack of the terminal and the base station (gNB) includes the Service Data Adaptation Protocol (SDAP) layer, the PDCP layer, the RLC layer, the MAC layer, and the physical (PHY) layer.

[0061] As shown in Figure 2B, the control plane protocol stack of the terminal includes the non-access stratum (NAS), radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer; the control plane protocol stack of the gNB includes the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer; the control plane protocol stack of the core network (such as the AMF network element) includes NAS.

[0062] The information acquisition method provided by the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0063] The embodiments of the present application can be applied to scenarios with multi-stream services, such as XR services, CG services, etc.

[0064] Currently, the QoS requirements and operations of each flow or packet are independent, and coordination and synchronization between multiple flows or packets are not defined, making it impossible to perform effective coordination and synchronization between flows or packets.

[0065] In order to solve the above problems, an embodiment of the present application provides an information acquisition method, wherein a first node can receive first information from a second node, that is, information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of coordination requirements and synchronization requirements, to obtain coordination requirements, synchronization requirements, etc. between streams. Therefore, the first node can define coordination and synchronization between multiple streams based on the information related to processing requirements between multiple streams or multiple packets, thereby performing effective coordination and synchronization processing between streams or packets to meet the processing requirements between multiple streams or multiple packets.

[0066] The present invention provides an information acquisition method, and Figure 3 shows a flow chart of the information acquisition method provided by the present invention. As shown in Figure 3, the information acquisition method provided by the present invention may include the following steps 201 and 202.

[0067] Step 201: The second node sends first information to the first node.

[0068] Step 202: The first node receives first information from the second node.

[0069] In the embodiment of the present application, the first information is information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of the following: coordination requirements and synchronization requirements.

[0070] In an embodiment of the present application, the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0071] Optionally, in an embodiment of the present application, the multiple streams may be multiple streams of the same service or multiple streams of different services. The service may be a service with multiple streams, such as an XR service or a CG service.

[0072] Optionally, in an embodiment of the present application, the above-mentioned multiple packages may be multiple packages of the same service, or multiple packages of different services. The service may be a service with multiple packages, such as an XR service or a CG service.

[0073] Optionally, in an embodiment of the present application, the above-mentioned first information may include at least one of the following: synchronization requirement information, coordination requirement information, processing object information, uplink indication, downlink indication, processing mark, time label, processing association relationship, and an indication of whether the processing requirement is met.

[0074] The processing object information is information about an object with processing requirements. The uplink indication is used to indicate an uplink processing requirement. The downlink indication is used to indicate a downlink processing requirement. The processing tag is used to indicate that a first flow or first packet has a processing requirement. The time tag is used to indicate time information corresponding to a second flow or second packet. The processing association relationship is used to indicate an association relationship between packets or flows with processing requirements.

[0075] It should be noted that the time label may also be a timestamp. The association relationship refers to an association relationship between packets or flows, such as a coordination association relationship or a synchronization association relationship.

[0076] Optionally, in an embodiment of the present application, the synchronization requirement information is used to indicate that there is a synchronization requirement between the multiple streams or multiple packets.

[0077] Optionally, in an embodiment of the present application, the coordination requirement information is used to indicate that there is a coordination requirement between the multiple flows or multiple packets.

[0078] It should be noted that the synchronization requirement information may be a value indicating a synchronization requirement, and the coordination requirement information may be a value indicating a coordination requirement.

[0079] Optionally, in an embodiment of the present application, the processing object information may include at least one of synchronization object information and coordination object information. The processing object may include an object having at least one of synchronization requirements, coordination requirements, and association requirements.

[0080] Optionally, in the embodiment of the present application, the information of the object having processing requirements may include at least one of the following:

[0081] identification of a terminal pair or terminal group;

[0082] Identification of the flow pair or flow group;

[0083] Identification of QoS flow pair or QoS flow group;

[0084] The identifier of a Data Radio Bearer (DRB) pair or DRB group;

[0085] Identification of the bearer pair or bearer group;

[0086] Identifier of a PDU session pair or a PDU session group;

[0087] The identifier of a business pair or business group.

[0088] Optionally, in the embodiment of the present application, the terminal pair or terminal group includes at least one of the following:

[0089] Terminals with processing requirements;

[0090] The terminal where the stream (steam) with processing requirements is located;

[0091] The terminal where the QoS flow with processing requirements is located;

[0092] The terminal where the DRB with processing requirements is located;

[0093] The terminal where the bearer with the processing requirement is located;

[0094] The terminal where the PDU session with processing requirements is located;

[0095] The terminal where the business with processing requirements is located.

[0096] Optionally, in an embodiment of the present application, the above-mentioned bearer may include at least one of the following: a signaling radio bearer (SRB), a DRB.

[0097] It should be noted that the above pair or group refers to two or more than two. For example, a flow pair identifier or a flow group identifier refers to two or more flow identifiers.

[0098] Optionally, in an embodiment of the present application, the above-mentioned steam pair or steam group (Steam pair / group) may include: a Steam having at least one of a synchronization requirement and a coordination requirement.

[0099] Optionally, in an embodiment of the present application, the above-mentioned QoS flow pair or QoS flow group may include: a QoS flow having at least one of a synchronization requirement and a coordination requirement.

[0100] Optionally, in an embodiment of the present application, the above-mentioned DRB pair or DRB group may include: a DRB having at least one of a synchronization requirement and a coordination requirement.

[0101] Optionally, in the embodiment of the present application, the above-mentioned Bearer pair or Bearer group may include: a Bearer having at least one of a synchronization requirement and a coordination requirement.

[0102] Optionally, in an embodiment of the present application, the above-mentioned PDU session pair or PDU session group may include: a PDU session having at least one of a synchronization requirement and a coordination requirement.

[0103] Optionally, in the embodiment of the present application, the above-mentioned service pair or service group may include: a service having at least one of a synchronization requirement and a coordination requirement.

[0104] Optionally, in an embodiment of the present application, the uplink indication may be used to indicate at least one of an uplink synchronization requirement and an uplink coordination requirement.

[0105] Optionally, in an embodiment of the present application, the above-mentioned downlink indication can be used to indicate at least one of a downlink synchronization requirement and a downlink coordination requirement.

[0106] Optionally, in an embodiment of the present application, the processing mark may include at least one of a synchronization mark and a coordination mark, wherein the synchronization mark is used to indicate that the first flow or the first packet has a synchronization requirement, and the coordination mark is used to indicate that the first flow or the first packet has a coordination requirement.

[0107] Optionally, in the embodiment of the present application, the first flow may include at least one of the following: a flow including a processing mark, a flow associated with a processing mark, or a flow associated with a flow or packet including a processing mark.

[0108] Optionally, in an embodiment of the present application, the first packet may include at least one of the following: a packet containing a processing mark, a packet associated with a processing mark, or a packet associated with a packet or flow containing a processing mark.

[0109] Optionally, the "packet" described in the embodiment of the present application may include at least two packets in the same second object or different second objects. The second object includes at least one of the following: an associated user equipment group, a user equipment (UE), a stream, a QoS flow, an Internet Protocol (IP) layer or a User Datagram Protocol (UDP) layer, a burst, a bearer, a PDU session, a PDU set, a PDU, a DRB, or a service.

[0110] It should be noted that the aforementioned associated user device group can be understood as multiple devices of the same user, or multiple associated devices (Tethered UE), or multiple devices used by the same user, or multiple devices carrying the same type of service. For example, these devices may include: mobile phones, watches, smart gloves, head-mounted displays, helmets, headphones, and in-vehicle equipment.

[0111] The PDU set described in the embodiments of the present application is composed of one or more PDUs carrying the payload of one unit of information generated at the application level. In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing. That is, the protocol definition of PDU Set is: A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level. In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing.

[0112] The burst described in the embodiments of the present application can be understood as a data burst, i.e., data generated by an application in a short period of time, including PDUs from one or more PDU Sets. The protocol definition of a data burst is: Data produced by the application in a short period of time, comprising PDUs from one or more PDU Sets.

[0113] Optionally, the “package” described in the embodiments of the present application may include at least one of the following:

[0114] At least two packages from the same user;

[0115] At least two packages from different users;

[0116] At least two packets from the same UE;

[0117] At least two packets from different UEs;

[0118] At least two packets from the same stream;

[0119] At least two packets from different streams;

[0120] At least two packets of the same QoS flow;

[0121] At least two packets of different QoS flows;

[0122] At least two packets in the same IP / UDP packet;

[0123] At least two packets in different IP / UDP packets;

[0124] At least two packets in the same burst;

[0125] At least two packets in different bursts;

[0126] At least two packets in the same bearer;

[0127] At least two packages in different bearers;

[0128] At least two packets in the same PDU session;

[0129] At least two packets in different PDU sessions;

[0130] At least two packets in the same PDU set;

[0131] At least two packets in different PDU sets;

[0132] At least two packets in the same PDU;

[0133] At least two packets in different PDUs;

[0134] At least two packets in the same DRB;

[0135] At least two packets in different DRBs;

[0136] At least two packages from the same business;

[0137] At least two packages from different businesses.

[0138] Optionally, in an embodiment of the present application, the above-mentioned different users may include different users in the same base station, the same cell, the same distributed unit (DU), the same centralized unit (CU), the same core network, the same RAN, the same public land mobile network (PLMN) or the same network.

[0139] Optionally, in an embodiment of the present application, the above-mentioned different users may include different users in different base stations, different cells, different DUs, different CUs, different core networks, different RANs, different PLMNs or different networks.

[0140] Optionally, in an embodiment of the present application, the different UEs may include different UEs of the same user (e.g., different devices of the same user, including watches, gloves, head-mounted displays, helmets, glasses, mobile phones, AR / VR devices, etc.). Alternatively, the different UEs may include different UEs of different users.

[0141] Optionally, in the embodiment of the present application, the above-mentioned different streams may include different streams of the same UE, or different streams of different UEs.

[0142] Optionally, in an embodiment of the present application, the above-mentioned different QoS flows may include different QoS flows of the same UE, or different QoS flows of different UEs.

[0143] Optionally, in the embodiment of the present application, the above-mentioned different QoS flows may include different QoS flows of the same stream, or different QoS flows of different streams.

[0144] Optionally, in an embodiment of the present application, the above-mentioned different IP / UDP packets may include different IP / UDP packets of the same UE, or different IP / UDP packets of the same stream, or different IP / UDP packets of different UEs, or different IP / UDP packets of different streams.

[0145] Optionally, in an embodiment of the present application, the above-mentioned different bursts may include different bursts of the same stream, or different bursts of the same IP / UDP packet, or different bursts of the same QoS flow, or different bursts of different streams, or different bursts of different IP / UDP packets, or different bursts of different QoS flows.

[0146] Optionally, in an embodiment of the present application, the above-mentioned different PDU sets may include different PDU sets of the same stream, or different PDU sets of the same IP / UDP packet, or different PDU sets of the same QoS flow, or different PDU sets of different streams, or different PDU sets of different IP / UDP packets, or different PDU sets of different QoS flows.

[0147] Optionally, in an embodiment of the present application, the above-mentioned different DBRs may include different DBRs for the same stream, or different DBRs for the same IP / UDP packet, or different DBRs for the same QoS flow, or different DBRs for different streams, or different DBRs for different IP / UDP packets, or different DBRs for different QoS flows.

[0148] Optionally, the "packet" described in the embodiments of the present application refers to at least one of the following: packet, burst, PDU set, PDU, SDU, DRB, transport block (TB), etc.

[0149] Optionally, in an embodiment of the present application, the above-mentioned packet refers to at least one of the following: burst, PDU set, PDU, SDU, DRB, TB.

[0150] Illustratively, a packet includes multiple bursts, a burst includes multiple PDU sets, a PDU set includes multiple PDUs, and so on.

[0151] Optionally, in an embodiment of the present application, the time tag is used to indicate at least one of the following time information:

[0152] Time information of the first object arriving at the first node;

[0153] Time information of when the first object leaves the first node;

[0154] Processing delay of the first object at the first node;

[0155] The remaining latency requirement of the first object;

[0156] The first object includes at least one of the following: stream, QoS flow, DRB, bearer, PDU session, service, and packet.

[0157] Optionally, in an embodiment of the present application, the second flow may include at least one of the following: a flow containing a time tag, a flow associated with a time tag, or a flow associated with a flow or packet containing a time tag.

[0158] Optionally, in an embodiment of the present application, the second packet may include at least one of the following: a packet containing a time tag, a packet associated with a time tag, or a packet associated with a packet or stream containing a time tag.

[0159] For example, assuming that the total delay requirement of the packet is X, and the delay before the second node is Y, the remaining delay requirement is XY.

[0160] Optionally, in an embodiment of the present application, the processing association relationship may include at least one of a synchronization association relationship and a coordination association relationship. The synchronization association relationship is used to indicate the association relationship between packets or flows with synchronization requirements, and the coordination association relationship is used to indicate the association relationship between packets or flows with coordination requirements.

[0161] Optionally, in an embodiment of the present application, the above-mentioned indication of whether the processing requirements are met may include: an indication of whether the processing requirements are met between processing objects, for example, it may include at least one of the following: whether the synchronization requirements are met between synchronization objects, whether the synchronization requirements are met between coordination objects, whether the coordination requirements are met between synchronization objects, and whether the coordination requirements are met between coordination objects.

[0162] It should be noted that a synchronization object can be understood as an object with synchronization requirements, and a coordination object can be understood as an object with coordination requirements.

[0163] Optionally, in an embodiment of the present application, the information of the above-mentioned object with processing requirements may include at least one of the following: an identifier of at least one terminal, an identifier of at least one flow, an identifier of at least one QoS flow, an identifier of at least one DRB, an identifier of at least one bearer, an identifier of at least one PDU session, an identifier of at least one service, identification information of at least one packet, identification information of at least one flow, type information of at least one packet, and type information of at least one flow.

[0164] Optionally, in an embodiment of the present application, the identification information of the above-mentioned packet may include at least one of the following: a packet identifier, a packet index (Index), a packet serial number (Serial Number, SN), etc.

[0165] Optionally, in an embodiment of the present application, the identification information of the above-mentioned flow may include at least one of the following: a flow identifier, a flow index (Index), a flow SN, etc.

[0166] Optionally, in an embodiment of the present application, the type information of the above-mentioned flow may include at least one of the following: QoS flow type, stream type, etc.

[0167] Exemplarily, the first information includes two QoS Flow identifiers and one UE identifier, which means that the two QoS flows (the QoS flows corresponding to the two QoS Flow identifiers) of one UE (the UE corresponding to the one UE identifier) ​​have at least one of synchronization requirements and coordination requirements.

[0168] As another example, the above-mentioned first information includes two QoS Flow identifiers and one stream identifier, which means that the two QoS flows (QoS flows corresponding to the two QoS Flow identifiers) of a steam (the stream corresponding to the one stream identifier) ​​have at least one of a synchronization requirement and a coordination requirement.

[0169] As another example, the first information includes two UE identifiers and one stream identifier, which means that the streams (the stream corresponding to the one stream identifier) ​​of two UEs (the UEs corresponding to the two UE identifiers) have at least one of a synchronization requirement and a coordination requirement.

[0170] Optionally, in the embodiment of the present application, the first node and the second node are different nodes.

[0171] The first node is a base station, and the second node is a terminal; or,

[0172] The first node is a core network node, and the second node is a base station or a terminal; or,

[0173] The first node is a server, and the second node is a core network node or a terminal; or,

[0174] The above-mentioned first node is a terminal, and the above-mentioned second node is any one of the following: a base station, a core network node, and a server.

[0175] Optionally, in an embodiment of the present application, the first node and the second node are different protocol layers in the same node; the first node is the first protocol layer, and the second node is the second protocol layer.

[0176] The first protocol layer is any one of the following: IP layer, TCP layer, UDP layer, and the second protocol layer is SDAP layer; or,

[0177] The first protocol layer is the SDAP layer, and the second protocol layer is the PDCP layer; or,

[0178] The first protocol layer is the PDCP layer, and the second protocol layer is the RLC layer; or,

[0179] The first protocol layer is an RLC layer, and the second protocol layer is a MAC layer; or,

[0180] The first protocol layer is the MAC layer, and the second protocol layer is the PHY layer.

[0181] Optionally, in an embodiment of the present application, the above-mentioned same node may be a base station, a core network node, a server or a terminal, etc.

[0182] Optionally, in an embodiment of the present application, the first information is carried in a user plane message. Alternatively, the first information is carried in a control plane message. Alternatively, the first portion of the first information is carried in a control plane message, and the second portion of the first information is carried in a user plane message.

[0183] Optionally, in an embodiment of the present application, the above-mentioned first information is carried in a user plane message, and the above-mentioned first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, time label, processing association relationship, and an indication of whether the processing requirements are met.

[0184] In the case where the first node receives the first information, the object where the first information is located or associated with has a processing requirement, that is, has at least one of a synchronization requirement and a coordination requirement.

[0185] Optionally, in an embodiment of the present application, the above-mentioned first information includes at least one of the following: processing object information, processing tag, time tag, processing association relationship, and an indication of whether the processing requirements are met; wherein, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PDU set delay budget (PSDB) requirement, packet delay budget (PDB) requirement, and transmission delay requirement.

[0186] It should be noted that satisfying the processing requirement can be understood as satisfying the delay requirement of the first object.

[0187] Optionally, in an embodiment of the present application, when the object where the above-mentioned first information is located or associated with meets the delay requirement of the first object, the object where the above-mentioned first information is located or associated with meets the processing requirement, that is, meets at least one of the synchronization requirement and the coordination requirement.

[0188] Optionally, in an embodiment of the present application, when the object where the above-mentioned first information is located or associated does not meet the delay requirement of the first object, the object where the above-mentioned first information is located or associated does not meet the processing requirement, that is, does not meet the synchronization requirement and coordination requirement.

[0189] Optionally, in an embodiment of the present application, when the first node does not receive the first information, it is determined that the object where the first information is located or the object associated with the first information has no processing requirements, that is, no synchronization requirements and coordination requirements.

[0190] Optionally, in an embodiment of the present application, the first portion of the first information is carried in a control plane message, and the second portion of the first information is carried in a user plane message. The first portion of information includes at least one of the following: a processing flag, a processing association, and an indication of whether processing requirements are met; the second portion of information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, and a time tag.

[0191] In the case where the first node receives the first part of information, the object where the first information is located or associated with has a processing requirement, that is, it has at least one of a synchronization requirement and a coordination requirement.

[0192] Optionally, in an embodiment of the present application, when the first node receives the first part of information and does not receive the second part of information, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

[0193] Optionally, in an embodiment of the present application, when the first node receives the first part of information and the received second part of information includes synchronization requirement information and coordination requirement information, the above-mentioned processing requirement is a synchronization requirement or a coordination requirement.

[0194] It should be noted that the synchronization requirement here is the synchronization requirement corresponding to the synchronization requirement information in the second part of the information, that is, the value corresponding to the synchronization requirement, and the coordination requirement here is the coordination requirement corresponding to the coordination requirement information in the second part of the information, that is, the value corresponding to the coordination requirement.

[0195] Optionally, in an embodiment of the present application, when the first node receives the second part of the first information, it determines that the object where the first information is located or associated with has processing requirements, that is, has at least one of synchronization requirements and coordination requirements.

[0196] Optionally, in an embodiment of the present application, when the first node does not receive the first part of the first information, it is determined that the object where the first information is located or associated with has no processing requirements, that is, no synchronization requirements and coordination requirements.

[0197] Optionally, in this embodiment of the present application, the user plane message may include at least one of the following:

[0198] General Packet Radio Service Tunnel Protocol-User plane (GTP-U) messages or GTP-U message headers in the user plane;

[0199] PDU aggregation message or PDU aggregation message header;

[0200] PDU message or PDU message header;

[0201] SDAP PDU message header;

[0202] PDCP PDU message header;

[0203] RLC PDU message header;

[0204] MAC Control Element (CE) message.

[0205] Optionally, in an embodiment of the present application, the above-mentioned first information is carried in a control plane message, and the above-mentioned first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, processing association relationship, and an indication of whether the processing requirement is met.

[0206] In this case, when the first node receives the first information, the object where the first information is located or associated with has a processing requirement.

[0207] Optionally, in this embodiment of the present application, the control plane message may include at least one of the following:

[0208] General Packet Radio Service Tunnel Protocol-Control plane (GTP-C) message or GTP-C message header;

[0209] RRC message;

[0210] NAS message.

[0211] Optionally, in an embodiment of the present application, when the first information is uplink information, the above-mentioned RRC message includes any one of the following: a user equipment assistance information (UE Assistance Information, UAI) message, and a connection establishment message.

[0212] Optionally, in an embodiment of the present application, when the first information is downlink information, the above-mentioned RRC message includes any one of the following: an RRC configuration message, an RRC reconfiguration message.

[0213] Optionally, in an embodiment of the present application, when the first information is uplink information, the above-mentioned NAS message includes any one of the following: a service request (Service Request) message, a service accept (Service Accept) message, and an identity request (Identity Request) message.

[0214] Optionally, in an embodiment of the present application, when the first information is downlink information, the above-mentioned NAS message includes any one of the following: a service response message, an identity response message.

[0215] Optionally, in an embodiment of the present application, in combination with FIG3 , as shown in FIG4 , after the above step 202 , the information acquisition method provided in the embodiment of the present application further includes the following step 203 .

[0216] Step 203: The first node performs a first process between multiple flows or multiple packets according to the first information.

[0217] In an embodiment of the present application, the above-mentioned first processing includes at least one of the following: coordination processing and synchronization processing.

[0218] In the embodiment of the present application, coordination processing refers to processing that meets coordination requirements, and synchronization processing refers to processing that meets coordination requirements.

[0219] Meeting the synchronization requirements between packets (per-Packet) or streams (per-Stream) can be understood as at least one of the following: (1) multiple packets or multiple streams maintain a certain synchronization relationship at the receiving end, that is, meeting the synchronization requirements, for example, multiple packets or multiple streams are received at the receiving end at close or simultaneous times; (2) multiple packets or multiple streams maintain a certain synchronization relationship in the display cache at the receiving end, that is, meeting the synchronization requirements or coordination requirements, for example, multiple packets or multiple streams are displayed at the receiving end at close or simultaneous times, etc.

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

[0221] As an example, the coordination process or synchronization process includes at least one of the following:

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

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

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

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

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

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

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

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

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

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

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

[0233] Specifically, for example, by controlling the mapping of stream or QoS flow or DRB or Bearer to LCH, synchronization requirements or coordination requirements can be met between different flows or packets of different flows.

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

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

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

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

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

[0239] In an embodiment of the present application, the first information can be used by the first node to perform at least one of coordination and synchronization processing on multiple flows or multiple packets. That is, the first node can perform at least one of coordination and synchronization processing on multiple flows or multiple packets based on the first information. In this way, the first node processes multiple flows or multiple packets to ensure synchronization or coordination between multiple flows or multiple packets of the service; or, to ensure that when asynchrony or incoordination occurs between multiple flows or multiple packets of the service, the first node can process the corresponding flows or packets.

[0240] Optionally, in an embodiment of the present application, the first node may perform coordination processing and synchronization processing on multiple streams or multiple packets of a service (e.g., an XR service) based on the first information to solve problems such as freezes, dizziness, and incoordination between images and / or audio caused by the asynchrony of multiple streams or multiple packets of the service.

[0241] An embodiment of the present application provides an information acquisition method, in which a first node can receive first information from a second node, namely, information related to processing requirements between multiple streams or multiple packets, where the processing requirements include at least one of coordination requirements and synchronization requirements, to obtain coordination requirements, synchronization requirements, etc. between streams. Therefore, the first node can define coordination and synchronization between multiple streams based on the information related to processing requirements between multiple streams or multiple packets, thereby performing effective coordination and synchronization processing between streams or packets to meet the processing requirements between multiple streams or multiple packets.

[0242] It should be noted that in this application, both the first node and the second node can execute the technical solutions of this application, that is, the process executed by the first node can also be executed by the second node, and the relevant solutions that can be implemented by the first node can also be implemented by the second node. The embodiments of this application are described only from the perspective of the first node. The implementation process and solutions of the second node can refer to all descriptions of the first node, and the embodiments of this application are not repeated here.

[0243] Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment, can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation can be determined according to actual usage requirements, and the embodiments of this application do not limit this.

[0244] The information acquisition method provided in the embodiment of the present application can be executed by an information acquisition device. In the embodiment of the present application, the information acquisition device provided in the embodiment of the present application is described by taking the information acquisition method executed by the information acquisition device as an example.

[0245] FIG5 shows a possible structural diagram of an information acquisition device involved in an embodiment of the present application, which can be applied to a first node. As shown in FIG5 , the information acquisition device 40 may include: a receiving module 41 .

[0246] Among them, the receiving module 41 is used to receive first information from the second node, and the first information is information related to the processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0247] An embodiment of the present application provides an information acquisition device, which can receive first information from a second node, namely, information related to processing requirements between multiple streams or multiple packets, where the processing requirements include at least one of coordination requirements and synchronization requirements, to obtain coordination requirements, synchronization requirements, etc. between streams. Therefore, the first node can define coordination and synchronization between multiple streams based on the information related to processing requirements between multiple streams or multiple packets, thereby performing effective coordination and synchronization processing between streams or packets to meet the processing requirements between multiple streams or multiple packets.

[0248] In a possible implementation, the first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, uplink indication, downlink indication, processing mark, time tag, processing association relationship, and indication of whether the processing requirement is met;

[0249] Among them, the processing object information is the information of the object with processing requirements; the uplink indication is used to indicate the uplink processing requirements, and the downlink indication is used to indicate the downlink processing requirements; the processing mark is used to indicate that the first flow or the first packet has processing requirements; the time label is used to indicate the time information corresponding to the second flow or the second packet; the processing association relationship is used to indicate the association relationship between packets or flows with processing requirements.

[0250] In one possible implementation, the information of the object having processing requirements includes at least one of the following:

[0251] identification of a terminal pair or terminal group;

[0252] Identification of the flow pair or flow group;

[0253] Identification of QoS flow pair or QoS flow group;

[0254] The identifier of the DRB pair or DRB group;

[0255] Identification of the bearer pair or bearer group;

[0256] Identifier of a PDU session pair or a PDU session group;

[0257] The identifier of a business pair or business group.

[0258] In one possible implementation, the terminal pair or terminal group includes at least one of the following:

[0259] Terminals with processing requirements;

[0260] The terminal where the flow with the processing requirement is located;

[0261] The terminal where the QoS flow with processing requirements is located;

[0262] The terminal where the DRB with processing requirements is located;

[0263] The terminal where the bearer with processing requirements is located;

[0264] The terminal where the PDU session with processing requirements is located;

[0265] The terminal where the business with processing requirements is located.

[0266] In one possible implementation, the information of the above-mentioned object with processing requirements includes at least one of the following: an identifier of at least one terminal, an identifier of at least one flow, an identifier of at least one QoS flow, an identifier of at least one DRB, an identifier of at least one bearer, an identifier of at least one PDU session, an identifier of at least one service, identification information of at least one packet, identification information of at least one flow, type information of at least one packet, and type information of at least one flow.

[0267] In a possible implementation, the first flow includes at least one of the following: a flow containing a processing mark, a flow associated with a processing mark, and a flow associated with a flow or packet containing a processing mark;

[0268] The first packet includes at least one of the following: a packet containing a processing mark, a packet associated with a processing mark, or a packet associated with a packet or flow containing a processing mark.

[0269] In one possible implementation, the time tag is used to indicate at least one of the following time information:

[0270] Time information of the first object arriving at the first node;

[0271] Time information of when the first object leaves the first node;

[0272] Processing delay of the first object at the first node;

[0273] The remaining latency requirement of the first object;

[0274] The first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, and packet.

[0275] In a possible implementation, the second flow includes at least one of the following: a flow containing a time stamp, a flow associated with a time stamp, or a flow associated with a flow or packet containing a time stamp;

[0276] The second packet includes at least one of the following: a packet containing a time stamp, a packet associated with a time stamp, or a packet associated with a packet or stream containing a time stamp.

[0277] In a possible implementation, the first node and the second node are different nodes;

[0278] The first node is a base station, and the second node is a terminal; or,

[0279] The first node is a core network node, and the second node is a base station or a terminal; or,

[0280] The first node is a server, and the second node is a core network node or a terminal; or,

[0281] The first node is a terminal, and the second node is any one of the following: a base station, a core network node, or a server.

[0282] In a possible implementation, the first node and the second node are different protocol layers in the same node; the first node is a first protocol layer, and the second node is a second protocol layer;

[0283] The first protocol layer is any one of the following: IP layer, TCP layer, UDP layer, and the second protocol layer is SDAP layer; or,

[0284] The first protocol layer is the SDAP layer, and the second protocol layer is the PDCP layer; or,

[0285] The first protocol layer is the PDCP layer, and the second protocol layer is the RLC layer; or,

[0286] The first protocol layer is the RLC layer, and the second protocol layer is the MAC layer; or,

[0287] The first protocol layer is the MAC layer, and the second protocol layer is the PHY layer.

[0288] In a possible implementation, the first information is carried in a user plane message; or,

[0289] The first information is carried in a control plane message; or,

[0290] The first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message.

[0291] In a possible implementation, the first information is carried in a user plane message, and the first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, time tag, processing association relationship, and an indication of whether the processing requirement is met;

[0292] In the case where the first node receives the first information, the object where the first information is located or associated with has processing requirements.

[0293] In a possible implementation, the first information includes at least one of the following: processing object information, a processing mark, a time tag, a processing association relationship, and an indication of whether the processing requirement is met;

[0294] Among them, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

[0295] In a possible implementation, the first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message.

[0296] The first part of information includes at least one of the following: a processing tag, a processing association relationship, and an indication of whether the processing requirement is met; the second part of information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, and a time tag;

[0297] In this case, when the first node receives the first part of information, the object where the first information is located or associated with has processing requirements.

[0298] In one possible implementation, when the first node receives the first part of information and does not receive the second part of information, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

[0299] In a possible implementation, when the first node receives the first part of information and the received second part of information includes synchronization requirement information and coordination requirement information, the processing requirement is a synchronization requirement or a coordination requirement.

[0300] In a possible implementation, the user plane message includes at least one of the following:

[0301] GTP-U message or GTP-U message header;

[0302] PDU aggregation message or PDU aggregation message header;

[0303] PDU message or PDU message header;

[0304] SDAP PDU message header;

[0305] PDCP PDU message header;

[0306] RLC PDU message header;

[0307] MAC CE message.

[0308] In a possible implementation, the first information is carried in a control plane message, and the first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, processing association relationship, and an indication of whether the processing requirement is met;

[0309] In the case where the first node receives the first information, the object where the first information is located or associated with has processing requirements.

[0310] In one possible implementation, the control plane message includes at least one of the following:

[0311] GTP-C message or GTP-C message header;

[0312] RRC message;

[0313] NAS message.

[0314] In a possible implementation, when the first information is uplink information, the RRC message includes any one of the following: a UAI message, a connection establishment message;

[0315] or,

[0316] In the case where the first information is downlink information, the above-mentioned RRC message includes any one of the following: an RRC configuration message, and an RRC reconfiguration message.

[0317] In one possible implementation, when the first information is uplink information, the NAS message includes any one of the following: a service request message, a service accept message, and an identity request message;

[0318] or,

[0319] In the case where the first information is downlink information, the above-mentioned NAS message includes any one of the following: a service response message and an identity response message.

[0320] In one possible implementation, the above-mentioned packet includes at least two packets of the same second object or different second objects; wherein the second object includes at least one of the following: associated user device group, user device, flow, QoS flow, IP layer or UDP layer, burst, bearer, PDU session, PDU set, PDU, DRB, service.

[0321] In one possible implementation, the information acquisition device 40 provided in the embodiment of the present application may further include an execution module. The execution module is configured to, after the receiving module 41 receives the first information from the second node, perform a first process between the multiple streams or multiple packets based on the first information, where the first process includes at least one of the following: coordination processing and synchronization processing.

[0322] The information acquisition device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0323] The information acquisition device provided in the embodiment of the present application can implement each process implemented in the above-mentioned information acquisition method embodiment and achieve the same technical effect. To avoid repetition, it will not be described here.

[0324] FIG6 shows a possible structural diagram of an information acquisition device involved in an embodiment of the present application, which can be applied to a second node. As shown in FIG6 , the information acquisition device 50 may include: a sending module 51 .

[0325] Among them, the sending module 51 is used to send first information to the first node, and the first information is information related to the processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of the following: coordination requirements, synchronization requirements; wherein the first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

[0326] An embodiment of the present application provides an information acquisition device, which can send first information to a first node so that the first node can receive the first information, that is, information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of coordination requirements and synchronization requirements to obtain coordination requirements, synchronization requirements, etc. between streams. Therefore, the first node can define coordination and synchronization between multiple streams based on the information related to processing requirements between multiple streams or multiple packets, thereby performing effective coordination and synchronization processing between streams or packets to meet the processing requirements between multiple streams or multiple packets.

[0327] In a possible implementation, the first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, uplink indication, downlink indication, processing mark, time tag, processing association relationship, and indication of whether the processing requirement is met;

[0328] Among them, the processing object information is the information of the object with processing requirements; the uplink indication is used to indicate the uplink processing requirements, and the downlink indication is used to indicate the downlink processing requirements; the processing mark is used to indicate that the first flow or the first packet has processing requirements; the time label is used to indicate the time information corresponding to the second flow or the second packet; the processing association relationship is used to indicate the association relationship between packets or flows with processing requirements.

[0329] In one possible implementation, the information of the object having processing requirements includes at least one of the following:

[0330] identification of a terminal pair or terminal group;

[0331] Identification of the flow pair or flow group;

[0332] Identification of QoS flow pair or QoS flow group;

[0333] The identifier of the DRB pair or DRB group;

[0334] Identification of the bearer pair or bearer group;

[0335] Identifier of a PDU session pair or a PDU session group;

[0336] The identifier of a business pair or business group.

[0337] In one possible implementation, the terminal pair or terminal group includes at least one of the following:

[0338] Terminals with processing requirements;

[0339] The terminal where the flow with the processing requirement is located;

[0340] The terminal where the QoS flow with processing requirements is located;

[0341] The terminal where the DRB with processing requirements is located;

[0342] The terminal where the bearer with processing requirements is located;

[0343] The terminal where the PDU session with processing requirements is located;

[0344] The terminal where the business with processing requirements is located.

[0345] In one possible implementation, the information of the above-mentioned object with processing requirements includes at least one of the following: an identifier of at least one terminal, an identifier of at least one flow, an identifier of at least one QoS flow, an identifier of at least one DRB, an identifier of at least one bearer, an identifier of at least one PDU session, an identifier of at least one service, identification information of at least one packet, identification information of at least one flow, type information of at least one packet, and type information of at least one flow.

[0346] In a possible implementation, the first flow includes at least one of the following: a flow containing a processing mark, a flow associated with a processing mark, and a flow associated with a flow or packet containing a processing mark;

[0347] The first packet includes at least one of the following: a packet containing a processing mark, a packet associated with a processing mark, or a packet associated with a packet or flow containing a processing mark.

[0348] In a possible implementation, the time tag is used to indicate at least one of the following time information: time information when the first object arrives at the first node; time information when the first object leaves the first node; processing delay of the first object at the first node; remaining delay requirement of the first object;

[0349] The first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, and packet.

[0350] In one possible implementation, the second stream includes at least one of the following: a stream containing a time tag, a stream associated with a time tag, or a stream associated with a stream or packet containing a time tag; the second packet includes at least one of the following: a packet containing a time tag, a packet associated with a time tag, or a packet associated with a packet or stream containing a time tag.

[0351] In a possible implementation, the first node and the second node are different nodes;

[0352] The first node is a base station, and the second node is a terminal; or,

[0353] The first node is a core network node, and the second node is a base station or a terminal; or,

[0354] The first node is a server, and the second node is a core network node or a terminal; or,

[0355] The first node is a terminal, and the second node is any one of the following: a base station, a core network node, or a server.

[0356] In a possible implementation, the first node and the second node are different protocol layers in the same node; the first node is a first protocol layer, and the second node is a second protocol layer;

[0357] The first protocol layer is any one of the following: IP layer, TCP layer, UDP layer, and the second protocol layer is SDAP layer; or,

[0358] The first protocol layer is the SDAP layer, and the second protocol layer is the PDCP layer; or,

[0359] The first protocol layer is the PDCP layer, and the second protocol layer is the RLC layer; or,

[0360] The first protocol layer is the RLC layer, and the second protocol layer is the MAC layer; or,

[0361] The first protocol layer is the MAC layer, and the second protocol layer is the PHY layer.

[0362] In a possible implementation, the first information is carried in a user plane message; or,

[0363] The first information is carried in a control plane message; or,

[0364] The first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message.

[0365] In a possible implementation, the first information is carried in a user plane message, and the first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, time tag, processing association relationship, and an indication of whether the processing requirement is met;

[0366] In the case where the first node receives the first information, the object where the first information is located or associated with has processing requirements.

[0367] In a possible implementation, the first information includes at least one of the following: processing object information, a processing mark, a time tag, a processing association relationship, and an indication of whether the processing requirement is met;

[0368] Among them, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

[0369] In a possible implementation, the first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message.

[0370] The first part of information includes at least one of the following: a processing tag, a processing association relationship, and an indication of whether the processing requirement is met; the second part of information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, and a time tag;

[0371] In this case, when the first node receives the first part of information, the object where the first information is located or associated with has processing requirements.

[0372] In one possible implementation, when the first node receives the first part of information and does not receive the second part of information, the above-mentioned processing requirements are met by meeting the delay requirements of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

[0373] In a possible implementation, when the first node receives the first part of information and the received second part of information includes synchronization requirement information and coordination requirement information, the processing requirement is a synchronization requirement or a coordination requirement.

[0374] In a possible implementation, the user plane message includes at least one of the following:

[0375] GTP-U message or GTP-U message header;

[0376] PDU aggregation message or PDU aggregation message header;

[0377] PDU message or PDU message header;

[0378] SDAP PDU message header;

[0379] PDCP PDU message header;

[0380] RLC PDU message header;

[0381] MAC CE message.

[0382] In one possible implementation, the above-mentioned first information is carried in a control plane message, and the above-mentioned first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, processing mark, processing association relationship, and an indication of whether the processing requirement is met; wherein, when the first node receives the first information, the object where the above-mentioned first information is located or associated with has processing requirements.

[0383] In one possible implementation, the control plane message includes at least one of the following:

[0384] GTP-C message or GTP-C message header;

[0385] RRC message;

[0386] NAS message.

[0387] In one possible implementation, when the first information is uplink information, the above-mentioned RRC message includes any one of the following: UAI message, connection establishment message; or, when the first information is downlink information, the above-mentioned RRC message includes any one of the following: RRC configuration message, RRC reconfiguration message.

[0388] In one possible implementation, when the first information is uplink information, the above-mentioned NAS message includes any one of the following: a service request message, a service acceptance message, and an identity request message; or, when the first information is downlink information, the above-mentioned NAS message includes any one of the following: a service response message and an identity response message.

[0389] In one possible implementation, the above-mentioned packet includes at least two packets of the same second object or different second objects; wherein the second object includes at least one of the following: associated user device group, user device, flow, QoS flow, IP layer or UDP layer, burst, bearer, PDU session, PDU set, PDU, DRB, service.

[0390] The information acquisition device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0391] The information acquisition device provided in the embodiment of the present application can implement each process implemented in the above-mentioned information acquisition method embodiment and achieve the same technical effect. To avoid repetition, it will not be described here.

[0392] As shown in Figure 7, an embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002, wherein the memory 5002 stores a program or instruction that can be run on the processor 5001. For example, when the communication device 5000 is the above-mentioned first node, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned first node side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 5000 is the above-mentioned second node, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned second node side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0393] It should be noted that in the embodiments of the present application, the first node may be a terminal, or the first node may be a base station, core network node, or server of a network-side device. The second node may be a terminal, or the second node may be a base station, core network node, or server of a network-side device. The following embodiments illustrate the hardware structures of the terminal and the network-side device, respectively.

[0394] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the above-mentioned information acquisition method embodiment. This terminal embodiment corresponds to the above-mentioned first node side or second node side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0395] The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of the processor 7010.

[0396] Those skilled in the art will appreciate that the terminal 7000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 7010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG8 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. Detailed descriptions are omitted here.

[0397] It should be understood that in an embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 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 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 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.

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

[0399] The memory 7009 can be used to store software programs or instructions and various data. The memory 7009 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, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 7009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 7009 in the embodiment of the present application includes, but is not limited to, these and any other suitable types of memory.

[0400] The processor 7010 may include one or more processing units. Optionally, the processor 7010 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 the processor 7010.

[0401] The terminal provided in the embodiment of the present application can implement the various processes implemented by the first node or the second node in the above method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above information acquisition method embodiment. To avoid repetition, it will not be repeated here.

[0402] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the above-mentioned information acquisition method embodiment. This network-side device embodiment corresponds to the above-mentioned first node-side or second node-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effect.

[0403] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 9, the network-side device 600 includes an antenna 61, a radio frequency device 62, a baseband device 63, a processor 64, and a memory 65. Antenna 61 is connected to radio frequency device 62. In the uplink direction, radio frequency device 62 receives information via antenna 61 and sends the received information to baseband device 63 for processing. In the downlink direction, baseband device 63 processes the information to be transmitted and sends it to radio frequency device 62. Radio frequency device 62 processes the received information and then sends it through antenna 61.

[0404] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 63 , which includes a baseband processor.

[0405] The baseband device 63 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, one of the chips is, for example, a baseband processor, which is connected to the memory 65 through a bus interface to call the program in the memory 65 and execute the network device operations shown in the above method embodiment.

[0406] The network side device may further include a network interface 66, which is, for example, a Common Public Radio Interface (CPRI).

[0407] Specifically, the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 65 and executable on the processor 64. The processor 64 calls the instructions or programs in the memory 65 to execute the methods executed by the modules shown in the above-mentioned information acquisition device and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0408] Specifically, the embodiment of the present application further provides a network side device. As shown in Figure 10, the network side device 800 includes: a processor 801, a network interface 802, and a memory 803. The network interface 802 is, for example, a Common Public Radio Interface (CPRI).

[0409] Specifically, the network side device 800 of the embodiment of the present application also includes: instructions or programs stored in the memory 803 and can be run on the processor 801. The processor 801 calls the instructions or programs in the memory 803 to execute the methods executed by each module shown in the above-mentioned information acquisition device and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0410] 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 various processes of the above-mentioned information acquisition method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0411] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a 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.

[0412] 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 of the above-mentioned information acquisition method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0414] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information acquisition method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0415] An embodiment of the present application further provides a wireless communication system, including: a first node and a second node, wherein the first node can be used to execute the steps of the above-mentioned information acquisition method, and the second node can be used to execute the steps of the above-mentioned information acquisition method.

[0416] 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 sentence "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 pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the 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.

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

[0418] 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 method for obtaining information, comprising: The first node receives first information from the second node, where the first information is information related to processing requirements between multiple flows or multiple packets, where the processing requirements include at least one of the following: coordination requirements and synchronization requirements; The first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

2. The method according to claim 1, wherein: The first information includes at least one of the following: synchronization requirement information, coordination requirement information, processing object information, uplink indication, downlink indication, processing mark, time label, processing association relationship, and indication of whether the processing requirement is met; Among them, the processing object information is the information of the object having the processing requirement; the uplink indication is used to indicate the uplink processing requirement, and the downlink indication is used to indicate the downlink processing requirement; the processing mark is used to indicate that the first stream or the first packet has the processing requirement; the time tag is used to indicate the time information corresponding to the second stream or the second packet; the processing association relationship is used to indicate the association relationship between packets or streams having the processing requirement.

3. The method according to claim 2, wherein: The information of the object having the processing requirement includes at least one of the following: an identification of a terminal pair or terminal group; Identification of the flow pair or flow group; Identification of a QoS flow pair or QoS flow group; The identifier of a data radio bearer DRB pair or DRB group; an identifier of a bearer pair or bearer group; Identifier of a protocol data unit PDU session pair or a PDU session group; The identifier of a business pair or business group.

4. The method according to claim 3, wherein: The terminal pair or terminal group includes at least one of the following: A terminal having the processing requirement; The terminal where the flow having the processing requirement is located; The terminal where the QoS flow having the processing requirement is located; The terminal where the DRB having the processing requirement is located; The terminal where the bearer having the processing requirement is located; The terminal where the PDU session having the processing requirement is located; The terminal where the service having the processing requirement is located.

5. The method according to claim 2, wherein: The information of the object with the processing requirement includes at least one of the following: an identifier of at least one terminal, an identifier of at least one flow, an identifier of at least one QoS flow, an identifier of at least one DRB, an identifier of at least one bearer, an identifier of at least one PDU session, an identifier of at least one service, identification information of at least one packet, identification information of at least one flow, type information of at least one packet, and type information of at least one flow.

6. The method according to any one of claims 2 to 5, wherein: The first flow includes at least one of the following: a flow including the processing mark, a flow associated with the processing mark, and a flow associated with a flow or a packet including the processing mark; The first packet includes at least one of the following: a packet containing the processing mark, a packet associated with the processing mark, and a packet associated with a packet or flow containing the processing mark.

7. The method according to any one of claims 2 to 6, wherein: The time tag is used to indicate at least one of the following time information: time information of the first object arriving at the first node; time information of the first object leaving the first node; a processing delay of the first object at the first node; The remaining latency requirement of the first object; The first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, and packet.

8. The method according to any one of claims 2 to 7, wherein: The second flow includes at least one of the following: a flow including the time tag, a flow associated with the time tag, and a flow associated with a flow or packet including the time tag; The second packet includes at least one of the following: a packet containing the time stamp, a packet associated with the time stamp, and a packet associated with a packet or stream containing the time stamp.

9. The method according to any one of claims 1 to 8, wherein: The first node and the second node are different nodes; The first node is a base station, and the second node is a terminal; or, The first node is a core network node, and the second node is a base station or a terminal; or, The first node is a server, and the second node is a core network node or a terminal; or, The first node is a terminal, and the second node is any one of the following: a base station, a core network node, and a server.

10. The method according to any one of claims 1 to 8, wherein: The first node and the second node are different protocol layers in the same node; the first node is a first protocol layer, and the second node is a second protocol layer; The first protocol layer is any one of the following: Internet Protocol IP layer, Transmission Control Protocol TCP layer, User Datagram Protocol UDP layer, and the second protocol layer is Service Data Adaptation Protocol SDAP layer; or, The first protocol layer is a SDAP layer, and the second protocol layer is a Packet Data Convergence Protocol PDCP layer; or, The first protocol layer is a PDCP layer, and the second protocol layer is a radio link control RLC layer; or, The first protocol layer is an RLC layer, and the second protocol layer is a medium access control MAC layer; or, The first protocol layer is a MAC layer, and the second protocol layer is a physical PHY layer.

11. The method according to any one of claims 1 to 10, wherein: The first information is carried in a user plane message; or, The first information is carried in a control plane message; or, The first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message.

12. The method according to any one of claims 2 to 11, wherein: The first information is carried in a user plane message, and the first information includes at least one of the following: the synchronization requirement information, the coordination requirement information, the processing object information, the processing mark, the time label, the processing association relationship, and an indication of whether the processing requirement is met; In which, when the first node receives the first information, the object where the first information is located or associated with has the processing requirement.

13. The method according to claim 12, wherein: The first information includes at least one of the following: the processing object information, the processing mark, the time label, the processing association relationship, and an indication of whether the processing requirement is met; Among them, the processing requirement is met by meeting the delay requirement of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PDU set delay budget PSDB requirement, packet delay budget PDB requirement, and transmission delay requirement.

14. The method according to any one of claims 2 to 11, wherein: The first part of the first information is carried in a control plane message, and the second part of the first information is carried in a user plane message; The first part of information includes at least one of the following: the processing mark, the processing association relationship, and an indication of whether the processing requirement is met; the second part of information includes at least one of the following: the synchronization requirement information, the coordination requirement information, the processing object information, and the time tag; In which, when the first node receives the first part of information, the object where the first information is located or associated with has the processing requirement.

15. The method according to claim 14, wherein: When the first node receives the first part of information and does not receive the second part of information, the processing requirement is met by meeting the delay requirement of the first object, and the first object includes at least one of the following: flow, QoS flow, DRB, bearer, PDU session, service, packet, and the delay requirement includes at least one of the following: PSDB requirement, PDB requirement, transmission delay requirement.

16. The method according to claim 14, wherein: In a case where the first node receives the first part of information, and the received second part of information includes the synchronization requirement information and the coordination requirement information, the processing requirement is the synchronization requirement or the coordination requirement.

17. The method according to any one of claims 11 to 16, wherein: The user plane message includes at least one of the following: Tunneling protocol GTP-U message or GTP-U message header in general packet radio service technology of user plane; PDU aggregate message or PDU aggregate message header; PDU message or PDU message header; SDAP PDU message header; PDCP PDU message header; RLC PDU message header; MAC control unit CE message.

18. The method according to any one of claims 2 to 11, wherein: The first information is carried in a control plane message, and the first information includes at least one of the following: the synchronization requirement information, the coordination requirement information, the processing object information, the processing mark, the processing association relationship, and an indication of whether the processing requirement is met; In which, when the first node receives the first information, the object where the first information is located or associated with has the processing requirement.

19. The method according to claim 11, 14 or 18, wherein: The control plane message includes at least one of the following: A tunneling protocol GTP-C message or a GTP-C message header in a general packet radio service technology of a control plane; Radio Resource Control RRC message; Non-access stratum NAS message.

20. The method according to claim 19, wherein: In the case where the first information is uplink information, the RRC message includes any one of the following: a user equipment auxiliary information UAI message, a connection establishment message; or, In the case where the first information is downlink information, the RRC message includes any one of the following: an RRC configuration message, an RRC reconfiguration message.

21. The method according to claim 19, wherein: In the case where the first information is uplink information, the NAS message includes any one of the following: a service request message, a service acceptance message, and an identity request message; or, In the case where the first information is downlink information, the NAS message includes any one of the following: a service response message, an identity response message.

22. The method of claim 2, 5, 6, 7, 8, 12, 13, 14, 15, 16 or 18, wherein: The package includes at least two packages of the same second object or different second objects; The second object includes at least one of the following: an associated user equipment group, a user equipment, a flow, a QoS flow, an IP layer or a UDP layer, a burst, a bearer, a PDU session, a PDU set, a PDU, a DRB, and a service.

23. The method according to any one of claims 1 to 22, wherein: After the first node receives the first information from the second node, the method further includes: The first node performs a first process between multiple streams or multiple packets according to the first information, where the first process includes at least one of the following: coordination processing and synchronization processing.

24. A method for obtaining information, comprising: The second node sends first information to the first node, where the first information is information related to processing requirements between multiple flows or multiple packets, and the processing requirements include at least one of the following: coordination requirements and synchronization requirements; The first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

25. An information acquisition device, applied to a first node, comprising: Receiver module; The receiving module is configured to receive first information from a second node, wherein the first information is information related to a processing requirement between a plurality of flows or a plurality of packets, wherein the processing requirement includes at least one of the following: a coordination requirement and a synchronization requirement; The first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

26. An information acquisition device, applied to a second node, comprising: Send module; The sending module is used to send first information to the first node, where the first information is information related to processing requirements between multiple streams or multiple packets, and the processing requirements include at least one of the following: coordination requirements and synchronization requirements; The first node and the second node are different nodes, or the first node and the second node are different protocol layers in the same node.

27. A communication device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the information acquisition method as described in any one of claims 1 to 23 are implemented, or the steps of the information acquisition method as described in claim 24 are implemented.

28. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the information acquisition method according to any one of claims 1 to 23, or implements the steps of the information acquisition method according to claim 24.

Images