Communication method, apparatus, and storage medium

Abstract

The application provides a communication method, device and storage medium, and applies to the field of communication. The method comprises the following steps: a first relay node sends media data of a first service to a second relay node, and the first relay node determines PDU set information associated with the media data and sends the media data and the PDU set information associated with the media data to the second relay node. Since the first relay node can forward the PDU set information to the second relay node, the second relay node does not need to identify the PDU set information, thereby reducing the calculation overhead of identifying the PDU set information.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method, apparatus, and storage medium. Background Technology

[0002] Media over QUIC (MoQ) is a media transport protocol optimized for the Quick User Datagram Protocol (QUIC) network connections, enabling direct media transmission via QUIC or WebTransport. The MoQ transport protocol architecture includes clients, relay nodes, and servers, providing end-to-end encryption support. MoQ utilizes a publish / subscribe process, allowing media producers to publish data in response to subscription requests from multiple endpoints.

[0003] Typically, the MoQ transport protocol architecture includes multiple relay nodes that can access the same media data. Each relay node needs to identify protocol data unit (PDU) set information to support PDU set-level quality of service (QoS) processing.

[0004] However, identifying PDU set information currently results in significant computational overhead. Summary of the Invention

[0005] This application provides a communication method, apparatus, and storage medium, which helps to reduce the computational overhead of relay nodes.

[0006] Firstly, a communication method is provided, which can be applied to the first relay node side, such as the first relay node or the communication module in the first relay node, or the circuit or chip responsible for communication functions in the first relay node (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). This application uses the first relay node as an example for description. The first relay node is, for example, a user plane function network element that supports MoQ relay functions.

[0007] The method includes: receiving media data of a first service; determining PDU set information associated with the media data; and sending the media data and the PDU set information.

[0008] The determination of the PDU set information associated with the media data can be replaced by: determining the PDU set information corresponding to the PDU set carrying the media data. Specifically, the application layer PDUs carry the media data, and the transport layer PDU set carries the application layer PDUs that encapsulate the media data.

[0009] The number of PDU sets carrying the media data is one or more, and each PDU set corresponds to one PDU set information.

[0010] Based on the technical solution of this application, the first relay node can forward the PDU set information to other relay nodes. In this way, other relay nodes only need to receive the PDU set information without having to identify the PDU set information, which helps to reduce the computational overhead of the relay nodes.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes storing the PDU set information. Thus, in scenarios involving secondary forwarding of the same media data, the first relay node does not need to re-identify the PDU set information; it can obtain the PDU set information locally and forward it, which helps reduce the computational overhead of identifying the PDU set information.

[0012] In one possible implementation, the PDU set information is stored if the local operation and maintenance settings indicate that the PDU set information should be stored.

[0013] In one possible implementation, the PDU set information is stored if the first network element instructs that it be stored. For example, the first network element is a session management function network element.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving a first request message, the first request message being used to request media data of a first service; obtaining the media data and PDU set information associated with the media data; and sending the media data and the PDU set information associated with the media data.

[0015] For example, in a scenario where the same media data is forwarded twice, the first relay node receives a first request message from the second relay node. The first relay node can obtain the media data and / or the PDU set information associated with the media data from other relay nodes or locally. In this way, the first relay node does not need to identify the PDU set information again, which helps to reduce the computational overhead of identifying the PDU set information.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the PDU set information includes the sequence number of the corresponding PDU set in the current forwarding, wherein the sequence number of the PDU set in the current forwarding is determined based on the sequence number of the PDU set in the previous forwarding and the number of PDU sets forwarded in the previous forwarding.

[0017] In this application, the first relay node can achieve continuous mapping of the sequence number of the PDU set across forwarding instances (i.e., multiple forwarding scenarios of the same media data) through a dynamic offset compensation mechanism, so as to determine the accurate sequence number of the PDU set.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the sequence number S of the PDU set at the i-th forwarding... i Satisfy the following formula:

[0019] S i =S i-1 +N

[0020] Among them, S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the PDU set information is carried in the extension portion of the user plane header of the General Packet Radio Service (GPRS) tunneling protocol, specifically the extension portion of the GTP-U header. The PDU set information is transmitted in units of data packets.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the PDU collection information is carried within an object. The PDU collection information is transmitted in units of objects.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the PDU collection information is carried in the extended portion of the object.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, sending the media data and the PDU set information includes: sending the PDU set information when the local operation and maintenance settings instruct the forwarding of the PDU set information, or when the first network element instructs the forwarding of the PDU set information.

[0025] Secondly, a communication method is provided, which can be applied to the second relay node side, such as the second relay node or the communication module in the second relay node, or the circuit or chip responsible for communication functions in the second relay node (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core). This application describes the second relay node as an example. The second relay node is, for example, a user plane function network element that supports MoQ relay functions.

[0026] The method includes: receiving media data of a first service and PDU set information associated with the media data; and sending the media data and the PDU set information.

[0027] Based on the technical solution of this application, the second relay node receives the PDU set information from other relay nodes. In this way, the second relay node only needs to receive the PDU set information and does not need to identify the PDU set information, which helps to reduce computational overhead.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: storing the PDU set information.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending a first request message, the first request message being used to request media data of the first service; and receiving the media data and the PDU set information.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the PDU set information includes the sequence number of the corresponding PDU set in the current forwarding, wherein the sequence number of the PDU set in the current forwarding is determined based on the sequence number of the PDU set in the previous forwarding and the number of PDU sets forwarded in the previous forwarding.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the sequence number S of the PDU set at the i-th forwarding... i Satisfy the following formula:

[0032] S i =S i-1 +N

[0033] Among them, S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the PDU set information is carried in the extended portion of the GTP-U header.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the PDU collection information is carried in an object.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, the PDU collection information is carried in an extension portion of the object.

[0037] In conjunction with the second aspect, in some implementations of the second aspect, sending the media data and the PDU set information includes: sending the PDU set information when the local operation and maintenance settings instruct the forwarding of the PDU set information, or when the first network element instructs the forwarding of the PDU set information.

[0038] It should be understood that the second aspect of this application corresponds to the technical solution of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here.

[0039] Thirdly, a communication apparatus is provided for executing the method in any possible implementation of any of the above aspects. Specifically, the apparatus includes a module for executing the method in any possible implementation of any of the above aspects.

[0040] In one design, the device may include modules that perform the methods / operations / steps / actions described in any of the above aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0041] In another design, the device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.

[0042] In another design, the device is a relay node, such as a user plane function network element. The relay node may include a transmitter for sending information or data and a receiver for receiving information or data.

[0043] In another design, the device is used to perform the methods in any possible implementation of any of the above aspects, and the device can be configured in a relay node.

[0044] Fourthly, a communication device is provided, comprising at least one processor for calling and running a computer program from a memory, such that the device performs the method in any possible implementation of any of the preceding aspects.

[0045] Optionally, the device further includes a memory for storing instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects.

[0046] Optionally, the device may also include a transmitter and a receiver, which may be separate or integrated together and referred to as a transceiver.

[0047] Fifthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0048] In a sixth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any possible implementation of any of the above aspects.

[0049] In a seventh aspect, a communication system is provided, comprising a first relay node as described in the first aspect and a second relay node as described in the second aspect.

[0050] Optionally, the communication system may also include one or more of the following: terminal equipment, application server, and access network equipment.

[0051] Eighthly, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in any possible implementation of any of the above aspects, such as receiving or processing data involved in the above methods.

[0052] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0053] Optionally, the chip system may consist of chips or may include chips and other discrete components. Attached Figure Description

[0054] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application;

[0055] Figure 2 This is a schematic diagram of a network architecture to which this application applies;

[0056] Figure 3 This is a content distribution architecture diagram that uses UPF as a MoQ relay.

[0057] Figure 4 This is a schematic diagram of a MoQ architecture applicable to an embodiment of this application;

[0058] Figure 5 This is a schematic flowchart illustrating a communication method provided in an embodiment of this application;

[0059] Figure 6 and Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0060] Before introducing the technical solutions provided in the embodiments of this application, the following points should be made first.

[0061] First, in the embodiments shown below, the terms and English abbreviations, such as MoQ, UPF, media data, PDU collection, PDU collection information, etc., are merely exemplary examples given for ease of description and should not constitute any limitation on this application. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0062] Second, in the embodiments shown below, the terms "first," "second," and various numerical designations are merely for descriptive convenience to distinguish identical or similar items with essentially the same function and purpose. For example, "first relay node" and "second relay node" are only used to distinguish different relay nodes and do not limit their order, nor are they used to limit the scope of the embodiments of this application. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., do not necessarily imply that they are different.

[0063] Third, "at least one" means one or more, while "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0064] Fourth, in this application, "instruction" can include direct and indirect instructions, explicit and implicit instructions, and instructions used for determination. The information indicated by a certain piece of information is called the information to be instructed. In specific implementation, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed; or it can only instruct a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction can be implemented by using a pre-agreed (e.g., protocol predefined) arrangement of various information, thereby reducing the instruction overhead to some extent. This application does not limit the specific method of instruction. It is understood that for the sender of the instruction information, the instruction information can be used to instruct the information to be instructed; for the receiver of the instruction information, the instruction information can be used to determine the information to be instructed.

[0065] Fifth, in this application, "send" and "receive" indicate the direction of signal transmission. For example, "send a first request message to the first relay node" can be understood as the destination of the first request message being the first relay node, which can include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive PDU set information from the first relay node" can be understood as the source of the PDU set information being the first relay node, which can include direct reception from the first relay node via the air interface or indirect reception from the first relay node by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0066] In other words, sending and receiving can occur between devices, such as between a terminal device and an access network device; or they can occur within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0067] Sixth, in this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, not to a time limit, nor to requiring the device to perform a judgment action, nor implying any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "under the circumstances" are interchangeable. "When" and "if" / "if" are interchangeable.

[0068] Seventh, in this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0069] Eighth, in this application, the solutions in each embodiment can be used in a reasonable combination, and the explanations or descriptions of various terms, similar operations, or steps appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0070] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application. Figure 1 The communication system 100 shown includes a radio access network (RAN) 101 and a core network (CN) 102. Optionally, the communication system 100 also includes an Internet 103. The radio access network 101 may include at least one RAN node (e.g., Figure 1 110a and 110b in the above), may also include at least one terminal (such as Figure 1 (Referring to devices 120a-120j). Terminals connect wirelessly to the RAN node, and the RAN node connects to the core network 102 wirelessly or via a wired connection. Core network equipment and RAN nodes can be independent physical devices, or the functions of the core network equipment and the logical functions of the RAN node can be integrated into the same physical device. Alternatively, a single physical device can integrate some core network equipment functions and some RAN node functions. Terminals and RAN nodes can connect to each other via wired or wireless connections. Figure 1 This is just an illustration; the communication system may also include other RAN nodes, such as wireless relay equipment and wireless backhaul equipment. Figure 1 Not shown in the image.

[0071] The radio access network 101 can be a cellular system related to the 3rd generation partnership project (3GPP), such as a 5th generation mobile communication technology (5G) mobile communication system (also known as a new radio (NR) system), or it can be applied to future communication systems, etc., which are not limited in this application. The radio access network 101 can also be an open RAN (open-RAN, O-RAN, or ORAN), a cloud radio access network (CRAN). The radio access network 101 can also be a non-terrestrial network (NTN), a satellite communication network, a high altitude platform station (HAPS) communication network, an integrated access and backhaul (IAB) communication network, a reconfigurable intelligent surface (RIS) communication network, etc. The radio access network 101 can also be a communication system that integrates two or more of the above systems.

[0072] RAN nodes, also known as RAN devices or access network devices, are used to help terminals achieve wireless access. Multiple RAN nodes in the communication system 100 can be of the same type or different types.

[0073] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), a transmit / receive point (TRP), a next-generation NodeB (gNB) in 5G, a base station in a future mobile communication system, an access point (AP) in a satellite, an IAB node, or a RAN node in an NTN communication system; that is, it can be deployed on a high-altitude platform or a satellite. A RAN node can also be a macro base station (such as...) Figure 1 110a), micro base stations or indoor stations (such as Figure 1RAN nodes can be 110b), relay nodes or donor nodes, or wireless controllers in CRAN scenarios. RAN nodes can also function as base stations in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, and machine-to-machine (M2M) communication. Optionally, access network devices can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network device can be a roadside unit (RSU).

[0074] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that RAN nodes can be CU nodes, DU nodes, or devices that include both CU and DU nodes. Furthermore, CUs can be classified as access network equipment within the RAN or core network equipment within the core network; this is not limited here.

[0075] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an O-RAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0076] A terminal device is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from RAN nodes. Terminal devices can also be referred to as terminal equipment, terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, including but not limited to at least one of the following: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Specifically, terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, aircraft, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0077] RAN nodes and terminals can be fixed or mobile. RAN nodes and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of RAN nodes and terminals.

[0078] The roles of RAN nodes and terminals can be relative. For example, Figure 1 The helicopter or drone 120i can be configured as a mobile RAN node. For terminals 120j accessing the wireless access network 101 via 120i, terminal 120i is a RAN node; however, for RAN node 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Alternatively, 110a and 120i can also communicate via a RAN node-to-RAN node interface protocol; in this case, 120i is also a RAN node relative to 110a. Therefore, both RAN nodes and terminals can be collectively referred to as communication devices. Figure 1 110a and 110b can be referred to as communication devices with RAN node functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0079] Communication between RAN nodes and terminals, between RAN nodes, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can also be conducted using spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0080] In the embodiments of this application, the functions of the RAN node can be executed by modules (such as chips) within the RAN node, or by a control subsystem that includes RAN node functions. This control subsystem, including RAN node functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0081] Core network equipment refers to the equipment in the core network that provides service support to terminals. Examples of some core network equipment include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, etc., which will not be listed here.

[0082] It should be understood that the network element in this application can also be replaced by entity, network entity, device, communication device, communication module, node, communication node, etc.

[0083] Figure 2 This is a schematic diagram of a network architecture applicable to this application, taking the 5G network architecture based on service-based architecture (SBA) in a non-roaming scenario as defined in the 3GPP standardization process as an example. Figure 2 As shown, the network architecture can include three parts, namely the terminal part (e.g., Figure 1 The network consists of the UE (User Equipment), data network (DN), and carrier network. The carrier network portion may include, but is not limited to, RAN and CN. The functions of the equipment or network elements in each portion are briefly described below.

[0084] The RAN section includes RAN nodes. The specific form of RAN nodes can be found in the description above, and will not be repeated here.

[0085] The CN component includes access and mobility management functions, session management functions, and user plane functions. Figure 2 This application only shows some of the network functions in the CN. The CN may include more network functions, and this application does not limit this.

[0086] The UE accesses the wireless network through the RAN node at its current location. Access and Mobility Management (AMF) functions are primarily used for user equipment attachment, mobility management, and tracking area update procedures in the mobile network. In 5G communication systems, AMF can be used; in future communication systems, AMF may still be called AMF, or it may have other names, which is not limited in this application.

[0087] Session management functions are primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to terminal devices and selecting user plane functions that provide packet forwarding capabilities. In 5G communication systems, the session management function may be an SMF (Session Management Function). In future communication systems, the session management function may still be called an SMF, or it may have other names; this application is not limited to these names.

[0088] User plane functions are primarily used for processing user packets, such as forwarding, billing, and lawful interception. In 5G networks, user plane functions can be UPF (User Plane Function). In future communication systems, user plane functions may still be called UPF, or they may have other names; this application is not limited to any particular name.

[0089] Data networks are primarily used to provide data transmission services for user equipment. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or dedicated networks jointly deployed by operators, such as those configured with Internet Protocol Multimedia Core Network Subsystem (IMS) services.

[0090] The relevant technologies and concepts involved in this application are introduced below.

[0091] Currently, the booming development of various media services on the Internet has also driven the development of diverse media transmission technologies. For example, video conferencing typically uses web real-time communication (WebRTC) technology; traditional streaming media uses real-time streaming protocol (RTSP), real-time transport protocol (RTP), and real-time transport control protocol (RTCP); and long-form video-on-demand and live streaming commonly use dynamic adaptive streaming over HTTP (DASH) based on hypertext transfer protocol (HTTP) and HTTP live streaming (HLS) technologies. These diverse transmission technologies have brought complexity to media services, and the convergence of various media transmission technologies has become a trend.

[0092] For privacy reasons, encrypted traffic now accounts for over 90% of internet traffic. However, existing transport protocols only support end-to-end encryption, resulting in transparent transmission over intermediate networks. This limits the network's ability to optimize media transmission and effectively improve user experience. To address this issue, the Internet Engineering Task Force (IETF) proposed a media over QUIC (MoQ) transport protocol. This protocol aims to integrate media transport protocols and introduce trusted relay nodes into the architecture to achieve collaboration between services and the network, enabling the network to optimize user experience based on network conditions and service needs.

[0093] The QUIC protocol, as the underlying protocol of HTTP / 3, has gained widespread support because its performance in modern networks is significantly superior to that of the Transmission Control Protocol (TCP). Media forwarding based on QUIC is also gradually being adopted by various content delivery network (CDN) vendors. The IETF established the MoQ group to define a standard protocol for media forwarding based on QUIC.

[0094] Media over QUIC transport (MoQT) is a protocol optimized for QUIC, enabling direct media transmission via QUIC or WebTransport. MoQT utilizes a publish / subscribe process, allowing media producers to publish data in response to subscription requests from multiple endpoints. MoQT's development is driven by the following goals:

[0095] (1) Latency: HTTP adaptive atreaming (HAS) has been successfully scaled, but usually at the cost of latency. TCP-based protocols are relatively simple, but they are slow to detect congestion and are affected by head-of-line blocking. Protocols that directly utilize UDP can avoid queuing, but they are too complex. MoQT aims to create a simple and flexible low-latency protocol that can quickly detect and respond to congestion by leveraging the capabilities of QUIC.

[0096] (2) Based on QUIC: The parallel nature of QUIC streams can improve packet loss. MoQT aims to design a streaming protocol that leverages the transmission advantages and flexible loss recovery options provided by parallel QUIC streams.

[0097] (3) Universality: The goal of MoQT is to develop a single protocol that can be used for transport from subscription to distribution.

[0098] (4) Relays: An integral goal of MoQT is to enable large-scale radio transmission of media, which can utilize third-party networks (relays) independent of publishers and subscribers to forward content. MoQT aims to incorporate relays as part of the protocol transmission and ensure that the media data itself remains opaque and private.

[0099] MoQT employs a hierarchical data model, comprising objects, groups, and tracks. Objects are the fundamental data units in MoQT, including metadata and payload. The metadata is unencrypted and visible to relay nodes; it includes the object's sequence information and index. The payload is encrypted, and relay nodes do not combine, split, or modify it. The payload can also be referred to as the load.

[0100] A group of objects is called a group, similar to a group of pictures (GOP) in video or a page in audio, primarily serving as the indexing unit when subscribing to tracks. A track is a sequence of groups, and the track name and track name together constitute the full trackname. The track name is a unique identifier for a single track within the track namespace, while the full track name is a unique index used to identify tracks within a given MoQT range. A track namespace can be viewed as identifying an application or service, while a track name can be viewed as identifying a media stream (e.g., video stream, audio stream, or subtitle stream).

[0101] CDN (Content Delivery Network) is a technology that utilizes distributed nodes to deploy servers globally. Its basic principle is to distribute content from the origin server (such as static or dynamic resources like web, application video, and audio) to the nodes closest to the user for caching. Through intelligent routing and load balancing, it ensures users can access the resources they need quickly and stably. CDN shortens the network transmission distance between the origin server and the user. By using parallel transmission across multiple nodes, it significantly reduces network latency and bandwidth consumption, while also alleviating the pressure on the origin server and improving network or application availability and security. The origin server can also be called an origin content server or origin server.

[0102] Figure 3 This is a content distribution architecture diagram that uses UPF as the MoQ relay. In the MoQ architecture, the MoQ relay is a node that uses the MoQ protocol. The MoQ relay can cache media data locally, and clients (such as...) Figure 3 UE 1 and UE 2 in the network obtain media data from the MoQ relay to reduce latency for client access to the origin station, thereby providing a faster media playback experience. The MoQ relay does not change the content of the media data. For example, a UPF in a 5G network can act as a MoQ relay, and a packet data network gateway (PGW) in a 4G network can act as a MoQ relay. Figure 3 As shown, UPF#1 and UPF#2 act as MoQ relays, caching media data locally. UE#1 can obtain the required media data from UPF#1, and UE#2 can obtain the required media data from UPF#2.

[0103] The MoQ streaming media sent from the origin station to the MoQ relay includes not only media data but also metadata to identify media attributes. The MoQ relay can sense network congestion levels and, based on the characteristics of the media data, perform operations such as priority scheduling, cache management, dependency handling, and selective dropping to optimize transmission, thereby improving the video experience.

[0104] In scenarios where UPF acts as a MoQ relay, although it can effectively solve the problems existing in CDN caching networks, when there are a large number of MoQ relays, each MoQ relay needs to identify PDU set information. Since it cannot directly obtain PDU set information, multiple MoQ relays need to identify PDU set information multiple times, resulting in high computational overhead.

[0105] In view of this, embodiments of this application provide a communication method in which multiple MoQ relays can forward PDU set information, thereby reducing the computational overhead of identifying PDU set information.

[0106] Figure 4 This is a schematic diagram of a MoQ architecture applicable to embodiments of this application, in which multiple user plane functions, such as multiple UPFs, can be deployed. These user plane functions serve as anchor points for mobile data network user terminal sessions, used to forward media data between the terminal device and the data network. Multiple user plane functions can access the same media data. For example... Figure 4 In this system, UPF#1 can receive media data from DN#1 and can forward the media data to the UE. UPF#2 and UPF#3 can obtain the same media data from DN#1 through UPF#1. DN#1 houses the application server for the first application, DN#2 houses the application server for the second application, and DN#3 houses the application server for the third application. UPF#1 can obtain the required media data from DN#1 through CDN#1. UPF#2 can obtain the required media data from DN2 through CDN#2. UPF#3 can obtain the required media data from DN#3 through CDN#3.

[0107] Before introducing the technical solution of this application, the terms involved in this application will be explained:

[0108] PDU: Refers to the data unit transmitted between peer layers. For example, the PDU of the physical layer is a bit, the PDU of the data link layer is a frame, the PDU of the network layer is a packet, the PDU of the transport layer is a segment, and the PDU of other higher layers is a message.

[0109] A PDU set consists of one or more PDUs that carry the payload of an information unit generated at the application layer, such as a frame or video slice in an extended reality (XR) service.

[0110] PDU set information can be the identification information of the PDU set to which the PDU belongs. For example, PDU set information includes a five-tuple: the PDU set sequence number (PSSN), the end PDU of the PDU set, the sequence number of each PDU in the PDU set, the size of the PDU set, and the PDU set importance (PSI). Here, PSSN refers to the sequence number of a PDU set among multiple PDU sets within a QoS flow, and PSI is used to identify the importance of a PDU set relative to other PDU sets within the QoS flow. The end PDU of a PDU set can also be described as an end PDU indicator, used to indicate the end PDU in a PDU set.

[0111] It is understandable that one PDU set information corresponds to one PDU set, and the number of PDU sets transmitted means the number of PDU set information transmitted. Here, one PDU set information includes the aforementioned five-tuple.

[0112] For example, in 5G, in order to support QoS processing based on PDU sets, the UPF needs to identify PDUs belonging to the PDU set and determine the relevant PDU set information, and then send the PDU set information to the access network device. The access network device can use the PDU set information to perform QoS processing based on the PDU set, such as dropping packets at the PDU set level / granularity.

[0113] It is understood that this application uses the example of a PDU set information including the aforementioned five-tuple for illustration, and this application does not preclude the possibility of defining PDU set information to include more or fewer elements than a five-tuple in existing or future protocols. Furthermore, this application does not preclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions as PDU set information.

[0114] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0115] Figure 5This is a schematic flowchart of a communication method 500 provided in an embodiment of this application. The steps of method 500 can be interactively executed by a first relay node and a second relay node. The relay node is a node using the MoQ protocol, referred to as a MoQ relay, used for locally caching media data and forwarding media data. In this embodiment, the relay node can also support forwarding PDU set information. Exemplarily, the relay node is a UPF in a 5G network, or other network elements with user plane functions; this embodiment does not limit the implementation in this way.

[0116] Method 500 includes, but is not limited to, S501 to S503, and each step is described in detail below.

[0117] S501, the application server sends the media data of the first service to the first relay node. Correspondingly, the first relay node receives the media data of the first service.

[0118] The application server can also be called the source content server, source server, or source site.

[0119] The primary service could be a streaming media service, a video service, a video-on-demand service, or a live streaming service. Media data can also be referred to as application data packages.

[0120] The first relay node, also known as the first MoQ relay, is used to forward media data for the first service.

[0121] In one possible implementation, the application server can send media data for the first service to the first relay node based on a request from the first relay node. For example, a terminal device requests media data for the first service from a second relay node. If the second relay node does not find the media data, it then locates the first relay node through the network element controller and requests the media data for the first service from the application server through the first relay node. Based on this request, the application server sends the media data for the first service to the first relay node.

[0122] When a terminal device requests media data for the first service from a second relay node, the request message may include the complete track name related to the media data of the first service. This complete track name can be understood as identifying the media data of the first service. For an explanation of the complete track name, please refer to the above description; it will not be repeated here. Similarly, when the second relay node requests media data for the first service from the first relay node, the request message also includes this complete track identifier. When the first relay node requests media data for the first service from the application server, the request message also includes this complete track identifier.

[0123] The network element controller determines that the first relay node can obtain the media data of the first service and instructs the second relay node to request the media data of the first service from the first relay node. For example, the network element controller is an SMF (Supervisory Element Controller).

[0124] In another possible implementation, the application server can proactively send the media data of the first service to the first relay node. For example, in the event of a first service update / software upgrade, the first service has updated media data, or the application server can proactively send the updated media data to the first relay node.

[0125] In one possible implementation, the application server sends the media data of the first service to the first relay node, including: the application server sends the media data of the first service to the first relay node via CDN.

[0126] In this embodiment, the application layer protocol used to send the media data is not limited to the MoQ protocol. In actual deployment, the application layer protocol can be flexibly selected according to the business scenario, such as using HTTP / 3, WebRTC, or other custom protocols such as the real-time messaging protocol (RTMP) for adaptation.

[0127] S502, the first relay node determines the PDU set information associated with the media data.

[0128] The media data is carried in one or more data packets. The first relay node identifies these data packets to determine the QUIC stream. Optionally, the first relay node can identify the QUIC stream by UDP port, connection ID, and traffic pattern. Multiple QUIC streams can run on a single QUIC connection, including, for example, video streams, audio streams, and subtitle streams.

[0129] A QUIC stream can carry one or more MoQ messages. The first relay node can identify the target MoQ message in the QUIC stream using parameters such as connection ID and port number. This target MoQ message refers to an Announce message. A QUIC stream also includes other types of messages, such as control messages and Subscribe messages. MoQ messages can also be described as MoQ packets.

[0130] The IETF defines official formats for different types of MoQ messages. The first relay node can decode the target MoQ message according to the official format to obtain the metadata and payload. The payload stores media data, which is not decrypted, while the metadata records control information used to map PDU set information.

[0131] The control information includes group sequence number, object sequence number, publisher priority, and object payload length.

[0132] The mapping rules between control information and PDU set information are as follows: group sequence number and object sequence number are mapped to PSSN; release priority is mapped to PSI; the payload length of an object is mapped to the last PDU in the PDU set and the size of the PDU set. The sequence number of the PDU in the PDU set is determined by the first relay node itself and does not need to be mapped based on the control information.

[0133] It is understood that the mapping of A to B described in the embodiments of this application can be interpreted as determining B based on A. For example, mapping group sequence number and object sequence number to PSSN can be understood as determining PSSN based on group sequence number and object sequence number; similarly, mapping release priority to PSI can be understood as determining PSI based on release priority; and similarly, mapping the payload length of an object to the end PDU in the PDU set and the size of the PDU set can be understood as determining the end PDU in the PDU set and the size of the PDU set based on the payload length of the object.

[0134] S503, the first relay node sends the media data and the PDU set information associated with the media data to the second relay node.

[0135] In one possible implementation, the first relay node can forward the PDU set information associated with the media data to the second relay node at the packet forwarding control protocol (PFCP) session granularity, independent of the establishment of a PDU session. This PFCP session-granularity forwarding can also be called node-granularity forwarding. For example, the application server can proactively send the media data of the first service to the first relay node without the terminal device initiating a PDU session establishment request. In this case, there is no PDU session connection between the first and second relay nodes, and the forwarding of the PDU set information between them is node-granularity forwarding. This eliminates the need to establish an independent session for each transmission, reducing session management signaling overhead and state maintenance resource consumption, thereby reducing the transmission latency and computational load of the PDU set information.

[0136] For example, a control plane network element (e.g., SMF or AMF) sends a PFCP message to a first relay node, which instructs the first relay node to forward PDU set information associated with the media data. Based on the PFCP message, the first relay node sends the PDU set information associated with the media data to a second relay node.

[0137] In another possible implementation, the first relay node can forward the PDU set information associated with the media data to the second relay node at the PDU session granularity. This granular forwarding depends on the establishment of the PDU session.

[0138] For example, the first relay node is a UPF and the second relay node is a UPF.

[0139] In this embodiment, in addition to forwarding media data to the second relay node, the first relay node can also forward PDU set information associated with the media data to the second relay node. This eliminates the need for the second relay node to identify the PDU set information, thereby reducing the computational overhead of PDU set information identification. Simultaneously, since the second relay node does not need to identify the PDU set information, the latency overhead caused by PDU set information identification is also reduced, thus contributing to reduced end-to-end latency.

[0140] In one possible implementation, after the second relay node receives the media data and the PDU set information associated with the media data, it can send the media data and the PDU set information associated with the media data to the access network device, and the access network device uses the PDU set information to perform QoS processing based on the PDU set.

[0141] It is understandable that if the media data of the first service is actively sent by the application server, then after the second relay node receives the media data and the PDU set information associated with the media data, it does not need to send the media data and the PDU set information associated with the media data to the access network device.

[0142] It is understood that the embodiments of this application describe the MoQ architecture, which includes a first relay node and a second relay node, as an example. The number of relay nodes in the MoQ architecture is not limited. The number of relay nodes can be two or more, and relay nodes can forward PDU set information to each other.

[0143] For example, the MoQ architecture also includes a third relay node. The terminal device requests media data for the first service from the third relay node through the access network device. The third relay node then requests the same media data from a second relay node, which in turn requests it from the first relay node. Finally, the first relay node requests the same media data from the application server. Correspondingly, the application server sends the media data for the first service to the first relay node, which then sends the media data and associated PDU set information to the second relay node. The second relay node then sends the same media data and associated PDU set information to the third relay node. Optionally, if the media data for the first service is triggered by the terminal device, the third relay node sends the media data and associated PDU set information to the access network device, which then sends the media data for the first service to the terminal device based on the associated PDU set information. Optionally, if the media data of the first service is triggered by the application server, the third relay node does not send the media data of the first service and the PDU set information associated with the media data to the access network device.

[0144] In one possible implementation, the first relay node can send the PDU set information to the second relay node under certain conditions. For example, if the local operation and maintenance settings indicate that the PDU set information should be forwarded, the first relay node will send the PDU set information to the second relay node. In other words, if the local operation and maintenance settings of the first relay node indicate that the PDU set information should not be forwarded, then the first relay node will not send the PDU set information to the second relay node. As another example, if the first network element indicates that the PDU set information should be forwarded, the first terminal device will not send the PDU set information to the second relay node. Here, "local operation and maintenance settings" can also be replaced with "local operation and maintenance policy".

[0145] Furthermore, if the first network element does not indicate whether to forward the PDU set information, it can default to not forwarding or forwarding. Whether to default to not forwarding or forwarding can be based on the protocol predefined, and this application embodiment does not limit this.

[0146] For example, the first network element is an SMF.

[0147] In one possible implementation, the first relay node can distribute media data according to the locally configured operation and maintenance policy, that is, determine which relay nodes to send the media data to.

[0148] In one possible implementation, the first relay node can determine whether to cache the media data based on its locally configured operation and maintenance policies.

[0149] In one possible implementation, the PDU collection information is transmitted via the GTP-U protocol. The PDU collection information is carried in the GTP-U header extension. In this way, when media data is transmitted, the object is cut into multiple data packets at the QUIC layer, and the PDU collection information is transmitted in units of data packets.

[0150] In another possible implementation, PDU collection information is carried within objects, and this PDU collection information is transmitted on an object-by-object basis. An object can be viewed as a data packet. For example, the concept of object extensions is added to the object, and the PDU collection information can be carried within these extensions.

[0151] It is understood that the number of PDU set information forwarded by the first relay node to the second relay node can be one or more, and the number of forwarded PDU set information is the same as the number of forwarded PDU sets. The PDU set described here refers to the transport layer PDU set, including one or more transport layer PDUs. It is understood that application layer PDUs directly carry media data, while transport layer PDUs carry application layer PDUs that encapsulate media data.

[0152] In a scenario where the same media data is forwarded twice, the second relay node sends a first request message to the first relay node, requesting the media data for the first service. Based on the first request message, the first relay node obtains the media data and the PDU set information associated with the media data. Then, the first relay node sends the media data and the PDU set information associated with the media data to the second relay node. In this way, in a scenario where the same media data is forwarded twice, the first and second relay nodes do not need to identify the PDU set information again, which helps reduce the overhead of identifying the PDU set information.

[0153] In one possible implementation, the first relay node obtains PDU set information associated with the media data, including: the first relay node obtains PDU set information associated with the media data from other relay nodes, wherein the other relay nodes store PDU set information associated with the media data.

[0154] In another possible implementation, after determining the set of PDUs associated with the media data, the first relay node stores the PDU set information. Then, when the terminal device requests the media data again, the first relay node can retrieve the PDU set information associated with the media data locally.

[0155] In one possible implementation, the first relay node can determine whether to store the PDU set information associated with the media data based on local operation and maintenance settings. For example, if the local operation and maintenance settings indicate that the PDU set information associated with the media data should be stored, the first relay node will store the PDU set information associated with the media data; if the local operation and maintenance settings indicate that the PDU set information associated with the media data should not be stored, the first relay node will not store the PDU set information associated with the media data. As another example, if the first network element indicates that the PDU set information associated with the media data should be stored, the first relay node will store the PDU set information associated with the media data; if the first network element indicates that the PDU set information associated with the media data should not be stored, the first relay node will not store the PDU set information associated with the media data. Furthermore, if the first network element does not indicate whether to store the PDU set information, it can default to storing the PDU set information or default not to storing it. Whether it defaults to storing or not storing can be based on protocol predefined, and this application embodiment does not limit this.

[0156] It is understandable that the first relay node can forward and store PDU set information. Furthermore, the forwarding and storage of PDU set information by the first relay node can be decoupled; for example, the first relay node can forward PDU set information but not store it, or it can not forward PDU set information but store it.

[0157] In scenarios involving the secondary forwarding of the same media data, the dynamic reassembly mechanism of sequence numbers generated during the encapsulation of PDU sets by relay nodes can cause changes in the sequence numbers of PDU sets generated in different forwarding instances, resulting in a discontinuous characteristic. To address this issue, relay nodes can implement a dynamic offset compensation mechanism to achieve continuous mapping of PDU set sequence numbers across forwarding instances.

[0158] The following section describes the method for continuously mapping the sequence numbers of the PDU set across forwarding instances.

[0159] In one possible implementation, the sequence number of a PDU set in the current forwarding is determined based on the sequence numbers of the PDU set in previous forwardings and the number of PDU sets forwarded in the previous forwardings. It can be understood that when forwarding PDU set information, the sequence number of the PDU set corresponding to that PDU set information is included; specifically, it includes the sequence number of the PDU set corresponding to that PDU set information in the current forwarding.

[0160] For example, the sequence number of a PDU set in the i-th forwarding is determined based on the sequence number of the PDU set in the (i-1)-th forwarding and the number of PDU sets in the (i-1)-th forwarding. Here, i is a positive integer greater than or equal to 2.

[0161] For example, the sequence number S of a PDU set during the i-th forwarding. i Satisfies the following formula: S i =S i-1 +N. Where S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

[0162] In one possible implementation, the first relay node can send the sequence number offset to the second relay node, which can then determine the sequence number of the PDU set in this forwarding based on this offset. This offset is determined based on the number of times the PDU set has been forwarded historically.

[0163] For example, the first relay node stores 100 PDU sets, numbered 1 to 100. In the first forwarding scenario of media data, if the first relay node sends 30 PDU sets to the second relay node, and the first relay node sends an initial offset of 0, then the sequence numbers of these 30 PDU sets are 1 to 30. In the second forwarding scenario of the same media data, since 30 PDU sets were forwarded in the first forwarding, the offset becomes 30. The first relay node sends this offset (30) to the second relay node. If the first relay node sends 100 PDU sets to the second relay node, then the sequence numbers of these 100 PDU sets are offset by 30 from 1 to 100, becoming 31 to 130. In a scenario involving three forwardings of the same media data, since the second forwarding involves 100 PDU sets, the offset increases by 100 from 30, becoming 130. If the first relay node sends 100 PDU sets to the second relay node, the sequence numbers of these 100 PDU sets increase by 130 from 1 to 100, becoming 131 to 230. This process continues to determine the sequence numbers of the PDU sets in each forwarding scenario.

[0164] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0165] In the embodiments provided above, the method provided by the embodiments of this application is described using the execution of a first relay node and a second relay node as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions in the methods provided by the embodiments of this application above, the steps executed by the relay node (such as the first relay node or the second relay node) can be implemented by the relay node itself or by different functional entities constituting the relay node. To achieve the functions in the methods provided by the embodiments of this application above, the relay node can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a certain function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0166] The above text combines Figure 5 The communication method according to the embodiments of this application is described in detail below, in conjunction with Figure 6 and Figure 7 The present application provides a detailed description of a communication apparatus according to embodiments thereof.

[0167] Figure 6 and Figure 7 This is a schematic block diagram of a communication device provided in an embodiment of this application. These communication devices can be used to implement the functions of the first relay node or the second relay node in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0168] like Figure 6 As shown, the communication device 600 includes a transceiver module 610 and a processing module 620. The transceiver module 610 can also be referred to as a communication interface or a communication module.

[0169] The communication device 600 can be used to perform the actions performed by the first relay node or the second relay node in the above method embodiments. Alternatively, the device 600 can be a component (e.g., a chip) configured in the first relay node or the second relay node. The processing module 620 is used to perform processing-related operations of the first relay node or the second relay node in the above method embodiments. The transceiver module 610 is used to perform receiving and transmitting-related operations of the first relay node or the second relay node in the above method embodiments.

[0170] Optionally, the transceiver module 610 may include a sending module and a receiving module. The sending module is used to perform the sending operation in the above method embodiments. The receiving module is used to perform the receiving operation in the above method embodiments.

[0171] It should be noted that the communication device 600 may include a transmitting module but not a receiving module. Alternatively, the communication device 600 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by the communication device 600 includes both transmitting and receiving actions.

[0172] Optionally, the communication device 600 is used to perform the above. Figure 5 The actions performed by the first relay node or the second relay node in the illustrated embodiment are shown above. For details, please refer to the above. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0173] Optionally, the communication device 600 may further include a storage module, which can be used to store data and / or to store computer programs or instructions. The processing module 620 can read the computer programs / instructions and / or data in the storage module so that the communication device 600 can implement the above-described method embodiments.

[0174] When the communication device 600 is used to achieve such Figure 5 In the method embodiment shown, when the first relay node is functioning, the transceiver module 610 is used to: receive media data of the first service; the processing module 620 is used to: determine the PDU set information associated with the media data; the transceiver module 610 is also used to: send the media data and the PDU set information.

[0175] Optionally, the transceiver module 610 is configured to: receive a first request message, the first request message being used to request media data for a first service; the processing module 620 is configured to: acquire the media data and the PDU set information; the transceiver module 610 is further configured to: send the media data and the PDU set information.

[0176] When the communication device 600 is used to achieve such Figure 5 In the method embodiment shown, when the second relay node functions, the transceiver module 610 is used to: receive media data of the first service and PDU set information associated with the media data.

[0177] Optionally, the transceiver module 610 is configured to: send a first request message, the first request message being used to request media data for a first service; and receive the media data and the PDU set information.

[0178] When the communication device 600 is used to achieve such Figure 5 In the method embodiment shown, when the first relay node or the second relay node functions, optionally, the processing module 620 is used to: store the PDU set information. Optionally, the transceiver module 610 is used to: send the PDU set information when the local operation and maintenance settings instruct to forward the PDU set information, or when the first network element instructs to forward the PDU set information.

[0179] Optionally, the PDU set information includes the sequence number of the corresponding PDU set in this forwarding, wherein the sequence number of the PDU set in this forwarding is determined based on the sequence number of the PDU set in previous forwardings and the number of PDU sets forwarded in previous forwardings.

[0180] Optionally, the sequence number S of the PDU set at the i-th forwarding... i Satisfy the following formula:

[0181] S i =S i-1 +N

[0182] Among them, S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

[0183] Optionally, the PDU set information is carried in the extension portion of the GTP-U header.

[0184] Optionally, the PDU collection information is carried in an object.

[0185] Optionally, the PDU collection information is carried in an extension portion of the object.

[0186] For a more detailed description of the transceiver module 610 and the processing module 620 mentioned above, please refer to [link / reference]. Figure 5 The relevant descriptions in the method embodiments shown will not be repeated here.

[0187] Figure 7 This is a schematic block diagram of another communication device 700 provided in the embodiments of this application, such as... Figure 7 As shown, device 700 includes one or more processors 710 and interface circuitry 720. The one or more processors 710 and interface circuitry 720 are coupled to each other. It is understood that interface circuitry 720 can be a transceiver or an input / output interface. Optionally, device 700 may also include memory 730 for storing instructions executed by processor 710, or for storing input data required by processor 710 to execute instructions, or for storing data generated after processor 710 executes instructions. Sometimes, interface circuitry 720 can also be understood as part of the one or more processors 710, in which case device 700 includes the one or more processors 710.

[0188] The one or more processors 710 and memory 730 can be configured separately or integrated, and this application does not limit this.

[0189] When device 700 is used to achieve Figure 5In the method shown, the one or more processors 710 are used to implement the functions of the processing module 620, and the interface circuit 720 is used to implement the functions of the transceiver module 610.

[0190] When the aforementioned device 700 is a chip applied to a first relay node, the chip of the first relay node implements the functions of the first relay node in the above method embodiment. The chip of the first relay node receives information from the second relay node, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the first relay node, and then sent to the chip of the first relay node by these modules. The chip of the first relay node sends information to the second relay node, which can be understood as the information being first sent to other modules (such as radio frequency modules or antennas) in the first relay node, and then sent to the second relay node by these modules.

[0191] When the aforementioned device 700 is a chip applied to a second relay node, the chip of the second relay node implements the functions of the second relay node in the above method embodiments. The chip of the second relay node receives information from the first relay node, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the second relay node, and then sent by these modules to the chip of the first relay node. The chip of the second relay node sends information to the first relay node, which can be understood as the information being first sent to other modules (such as radio frequency modules or antennas) in the second relay node, and then sent by these modules to the first relay node.

[0192] This application also provides a computer-readable storage medium for storing a computer program that, when run on a computer, causes the computer to perform the methods described in the above embodiments. Alternatively, the computer program includes instructions for implementing the methods described in the above embodiments.

[0193] This application also provides a computer program product, including: a computer program or instructions that, when run on a computer, cause the computer to perform the methods described above.

[0194] This application also provides a chip, which includes at least one processor for supporting the implementation of the methods in the above embodiments, such as receiving or processing data involved in the methods in the above embodiments.

[0195] It should be understood that, in the embodiments of this application, the processor may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0196] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, optical discs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the ASIC can reside in a base station or terminal. The processor and the storage medium can also exist as discrete components in the base station or terminal.

[0197] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0198] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0199] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive media data from the first service; Determine the Protocol Data Unit (PDU) set information associated with the media data; Send the media data and the PDU collection information.

2. The method according to claim 1, characterized in that, The method further includes: Store the PDU set information.

3. The method according to claim 2, characterized in that, The method further includes: Receive a first request message, which is used to request media data of the first service; Obtain the media data and the PDU collection information; Send the media data and the PDU collection information.

4. The method according to claim 3, characterized in that, The PDU set information includes the sequence number of the corresponding PDU set in this forwarding, wherein the sequence number of the PDU set in this forwarding is determined based on the sequence number of the PDU set in previous forwardings and the number of PDU sets in previous forwardings.

5. The method according to claim 4, characterized in that, The sequence number S of the PDU set during the i-th forwarding i Satisfy the following formula: S i =S i-1 +N Among them, S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

6. The method according to any one of claims 1 to 5, characterized in that, The PDU set information is carried in the extended portion of the GTP-U header of the General Packet Radio Service Tunneling Protocol user plane.

7. The method according to any one of claims 1 to 5, characterized in that, The PDU collection information is carried in the object.

8. The method according to claim 7, characterized in that, The PDU collection information is carried in the extended portion of the object.

9. The method according to any one of claims 1 to 8, characterized in that, Sending the media data and the PDU set information includes: The PDU set information is sent when the local operation and maintenance settings instruct the forwarding of the PDU set information, or when the first network element instructs the forwarding of the PDU set information.

10. A communication method, characterized in that, include: Receive media data from the first service and PDU set information associated with the media data; Send the media data and the PDU collection information.

11. The method according to claim 10, characterized in that, The method further includes: Store the PDU set information.

12. The method according to claim 11, characterized in that, The method further includes: Send a first request message, which is used to request media data of the first service; Receive the media data and the PDU set information.

13. The method according to claim 12, characterized in that, The PDU set information includes the sequence number of the corresponding PDU set in this forwarding. The sequence number of the PDU set in this forwarding is determined based on the sequence number of the PDU set in previous forwardings and the number of PDU sets in previous forwardings. The PDU set includes one or more PDUs, and the one or more PDUs carry the media data.

14. The method according to claim 13, characterized in that, The sequence number S of the PDU set during the i-th forwarding i Satisfy the following formula: S i =S i-1 +N Among them, S i-1 Let N be the sequence number of the PDU set during the (i-1)th forwarding, and let N be the number of PDU sets during the (i-1)th forwarding.

15. The method according to any one of claims 10 to 14, characterized in that, The PDU set information is carried in the extended portion of the GTP-U header of the General Packet Radio Service Tunneling Protocol user plane.

16. The method according to any one of claims 10 to 14, characterized in that, The PDU collection information is carried in the object.

17. The method according to claim 16, characterized in that, The PDU collection information is carried in the extended portion of the object.

18. The method according to any one of claims 10 to 17, characterized in that, Sending the media data and the PDU set information includes: The PDU set information is sent when the local operation and maintenance settings instruct the forwarding of the PDU set information, or when the first network element instructs the forwarding of the PDU set information.

19. A communication device, characterized in that, It includes modules for implementing the method as described in any one of claims 1 to 9, or includes modules for implementing the method as described in any one of claims 10 to 18.

20. A communication device, characterized in that, The method includes at least one processor coupled to a memory for storing a program or instructions that, when executed by the at least one processor, cause the method of any one of claims 1 to 9 to be performed, or cause the method of any one of claims 10 to 18 to be performed.

21. A computer-readable storage medium, characterized in that, Used to store a computer program that, when run on a computer, causes the method as described in any one of claims 1 to 9 to be performed, or causes the method as described in any one of claims 10 to 18 to be performed.

22. A computer program product, characterized in that, include: A computer program or instruction that, when executed, causes the method as claimed in any one of claims 1 to 9 to be performed, or causes the method as claimed in any one of claims 10 to 18 to be performed.

Images