Data packet information transmission method, data packet information determination method, apparatus and communication device

Abstract

The present application belongs to the technical field of communications. Disclosed are a data packet information transmission method, a data packet information determination method, an apparatus and a communication device. The data packet information transmission method of the embodiments of the present application comprises: a first device executes a first operation, the first operation comprising at least one of the following: sending first information to a terminal; and sending second information to a second device, wherein the first information is used for at least one of the following: data packet identification, data packet classification, data packet matching, and data packet mapping to a quality of service (QoS) flow, and the second information is used for at least one of the following: data packet identification, data packet classification, data packet matching, and data packet mapping to a QoS flow.

Description

Data packet information transmission method, data packet information determination method, device and communication equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410395994.5 filed in China on April 2, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a data packet information transmission method, a data packet information determination method, an apparatus, and a communication device. Background Art

[0004] Interactive media services may send data streams of different media components with different Quality of Service (QoS) requirements. The QoS framework of communication systems in related technologies cannot support differentiated QoS, so how to process data packets is an urgent problem to be solved. Summary of the Invention

[0005] The embodiments of the present application provide a data packet information transmission method, a data packet information determination method, an apparatus, and a communication device, which can solve the technical problem of how to process differentiated data packets.

[0006] In a first aspect, a method for transmitting data packet information is provided, which is performed by a first device. The method includes:

[0007] The first device performs a first operation, where the first operation includes at least one of the following:

[0008] Sending first information to the terminal;

[0009] sending second information to the second device;

[0010] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0011] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0012] In a second aspect, a method for transmitting data packet information is provided, which is executed by a terminal, and the method includes:

[0013] The terminal obtains the first information;

[0014] The terminal performs a second operation based on the first information, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0015] According to a third aspect, a method for transmitting data packet information is provided, which is performed by a second device. The method includes:

[0016] The second device obtains second information;

[0017] The second device performs a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0018] In a fourth aspect, a method for transmitting data packet information is provided, the method comprising:

[0019] The third device sends sixth information to the fourth device, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0020] The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0021] The first device performs a first operation based on the fifth information, where the first operation includes at least one of the following: sending first information to a terminal; sending second information to a second device;

[0022] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0023] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0024] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0025] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0026] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0027] In a fifth aspect, a method for transmitting data packet information is provided, which is performed by a third device, and the method includes:

[0028] The third device sends sixth information to the fourth device or the second device, where the sixth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information.

[0029] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0030] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0031] In a sixth aspect, a method for transmitting data packet information is provided, which is performed by a fourth device, the method comprising:

[0032] The fourth device obtains sixth information, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0033] The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0034] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0035] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0036] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0037] In a seventh aspect, a data packet information transmission device is provided, the device comprising:

[0038] A first sending unit, configured to send first information to a terminal;

[0039] A second sending unit, configured to send second information to a second device;

[0040] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0041] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0042] In an eighth aspect, a device for determining data packet information is provided, the device comprising:

[0043] an acquiring unit, configured to acquire first information;

[0044] The processing unit is configured to perform a second operation based on the first information, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0045] In a ninth aspect, a device for determining data packet information is provided, the device comprising:

[0046] an acquiring unit, configured to acquire second information;

[0047] The processing unit is configured to perform a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0048] In a tenth aspect, a data packet information transmission device is provided, the device comprising:

[0049] A sending unit, configured to send sixth information to the fourth device or the second device, the sixth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information.

[0050] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0051] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0052] In an eleventh aspect, a data packet information transmission device is provided, the device comprising:

[0053] An acquiring unit is configured to acquire sixth information, the sixth information including at least one of the following: a QUIC connection identifier based on a Fast User Datagram Protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0054] A sending unit, configured to send fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information;

[0055] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0056] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0057] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0058] In a twelfth aspect, a terminal is provided, 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 method described in the second aspect are implemented.

[0059] In the thirteenth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to: obtain first information; the processor is used to: perform a second operation based on the first information, the second operation including at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows.

[0060] In the thirteenth aspect, a network side 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, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the fifth aspect are implemented, or the steps of the method described in the sixth aspect are implemented.

[0061] In the fourteenth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to: perform a first operation, the first operation including at least one of the following: sending first information to a terminal; sending second information to a second device; wherein the first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows; the second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows.

[0062] In the fifteenth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to: obtain second information; the processor is used to: perform a third operation based on the second information, and the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows.

[0063] In the sixteenth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to: send sixth information to a fourth device or a second device, the sixth information including at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; third indication information; fourth indication information; wherein the third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; the third device has a tunnel or QUIC; the fourth indication information is used to indicate at least one of the following: the association relationship between the HTTP proxy UDP context identifier and the data packet set; the association relationship between the HTTP proxy UDP context identifier and the data packet media type.

[0064] In the seventeenth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to: obtain sixth information, the sixth information including at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for a media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier; third indication information; fourth indication information; based on the sixth information, send fifth information to the first device, the fifth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track Alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; second indication information; wherein, the second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; having a tunnel or fast UDP network connection QUIC with a third device; the third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; the third device has a tunnel or fast UDP network connection QUIC; the fourth indication information is used to indicate at least one of the following: the association relationship between the HTTP proxy UDP context identifier and the data packet set; the association relationship between the HTTP proxy UDP context identifier and the data packet media type.

[0065] In aspect 18, 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 aspect 1 are implemented, or the steps of the method described in aspect 2 are implemented, or the steps of the method described in aspect 3 are implemented, or the steps of the method described in aspect 4 are implemented, or the steps of the method described in aspect 5 are implemented, or the steps of the method described in aspect 6 are implemented.

[0066] In the nineteenth aspect, a communication system is provided, which can be used to perform the steps of the method described in the fourth aspect.

[0067] In the twentieth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect, or the method as described in the fourth aspect, or the method as described in the fifth aspect, or the method as described in the sixth aspect.

[0068] In aspect 21, 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 method described in aspect 1, or the steps of the method described in aspect 2, or the steps of the method described in aspect 3, or the steps of the method described in aspect 4, or the steps of the method described in aspect 5, or the steps of the method described in aspect 6.

[0069] In an embodiment of the present application, a first device performs a first operation, which includes at least one of the following: sending first information to a terminal; sending second information to a second device; wherein the first information is used for at least one of the following: identifying a data packet; classifying a data packet; matching a data packet; and mapping a data packet to a QoS flow; and the second information is used for at least one of the following: identifying a data packet; classifying a data packet; matching a data packet; and mapping a data packet to a QoS flow. Thus, by sending the first information to the terminal by the first device, the terminal can perform operations such as identifying, classifying, matching, or mapping data packets based on the first information; and by sending the second information to the second device by the first device, the second device can perform operations such as identifying, classifying, matching, or mapping data packets based on the second information, thereby clarifying how to process data packets. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application;

[0071] FIG2a is a schematic diagram of a data packet processing flow in a UP function in the related art;

[0072] FIG2 b is a schematic diagram of a HTTP proxy UDP datagram format in the related art;

[0073] FIG3 is a flow chart of a method for transmitting data packet information provided in an embodiment of the present application;

[0074] FIG4 is a flow chart of a method for determining data packet information provided by an embodiment of the present application;

[0075] FIG5 is a flowchart of a method for determining data packet information provided by an embodiment of the present application;

[0076] FIG6 is a flowchart of a method for transmitting data packet information provided in an embodiment of the present application;

[0077] FIG7 is a flowchart of a method for transmitting data packet information provided in an embodiment of the present application;

[0078] FIG8 is a flowchart of a method for transmitting data packet information provided in an embodiment of the present application;

[0079] FIG9 is a flowchart of UE data packet identification and flow mapping provided in Example 1;

[0080] FIG10 is a flowchart of UPF packet identification and flow mapping provided in Example 2;

[0081] FIG11 is a schematic diagram of an encoding method of QoS rules provided in Example 4;

[0082] FIG12 is a structural diagram of a data packet information transmission device provided in an embodiment of the present application;

[0083] 13 is a structural diagram of a device for determining data packet information provided in an embodiment of the present application;

[0084] 14 is a structural diagram of a device for determining data packet information provided in an embodiment of the present application;

[0085] FIG15 is a structural diagram of a data packet information transmission device provided in an embodiment of the present application;

[0086] FIG16 is a structural diagram of a data packet information transmission device provided in an embodiment of the present application;

[0087] FIG17 is a structural diagram of a communication device provided in an embodiment of the present application;

[0088] FIG18 is a structural diagram of a terminal provided in an embodiment of the present application;

[0089] Figure 19 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0094] 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 (AP) 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 relevant 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.

[0095] 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 subscriber 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.

[0096] Before describing the embodiments of the present application, the following briefly introduces the relevant technologies:

[0097] 1. XR Business

[0098] Extended reality (XR) refers to all businesses related to the combination of real and virtual environments and human-computer interactions generated by computer technology and wearable devices. It includes representative forms of business such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), as well as businesses in the intersection of these areas. The levels of virtual worlds range from partial sensory input to fully immersive virtual reality. A key aspect of the XR business is the expansion of human experience, especially experiences related to presence (represented by VR) and cognitive learning (represented by AR).

[0099] For VR services, the uplink is mainly based on the transmission of relatively dense small data packets. These small data packets can carry information such as gestures and controls, and serve as input and reference for downlink presentation data. The downlink is mainly based on the transmission of multimedia data such as video and audio. The timely reception and presentation of these multimedia data provide users with an immersive experience. Taking downlink video data as an example, video data can be modeled as video frames based on the frame rate (Frame Per Second, FPS), with a typical FPS value of 60 or 120. These video frames arrive periodically or quasi-periodically based on the period determined by the FPS (1 / FPS second), and the size of the video frame changes dynamically. Each video frame is generally required to be successfully transmitted within 10ms on the air interface, and the transmission success rate is required to be no less than 99% or even 99.9%. In addition, downlink video data generally requires a very high data rate, generally up to tens or even hundreds of Mbps (typical values ​​are 30 / 45Mbps).

[0100] For AR services, in addition to the above-mentioned dense transmission of small data packets, uplink may also transmit multimedia data such as video, audio, and scene images. Its service characteristics are similar to those of downlink. The data rate is usually relatively low, for example, at most tens of Mbps (typically 10 / 20 Mbps). The time limit for air interface transmission can also be relaxed. For example, each video frame is generally required to be successfully transmitted within 30ms. The downlink data transmission characteristics are basically the same as those of VR services.

[0101] XR and interactive media services may send data streams of different media components with different Quality of Service (QoS) requirements. Multiple media streams can be multiplexed over the same end-to-end transport layer connection.

[0102] In one example, in an XR service, multiple media streams may be multiplexed on a single Internet Protocol (IP) quintuple using a transport protocol such as IETF QUIC

[0011] , using different Quick UDP Internet Connections (QUIC) or different QUIC streams.

[0103] In another example, video and audio Real-Time Transport Protocol (RTP) streams or different media stream layers with different QoS requirements are multiplexed into a single transport layer connection with the same IP quintuple.

[0104] In the related technologies, the current 5GS QoS framework is generally not suitable for supporting differentiated QoS when multiplexed traffic shares the same IP quintuple. Therefore, to address this key issue, research content is proposed on traffic detection and QoS flow mapping for different media flows in 5GS, which are multiplexed in a single end-to-end transport connection.

[0105] The above research contents may include at least one of the following:

[0106] How to identify multiplexed traffic with different QoS requirements in a single transport connection.

[0107] How to perform QoS traffic mapping for traffic with different QoS requirements.

[0108] What information is required from the AF for traffic detection?

[0109] Whether and how AF provides QoS requirements of different traffic flows to 5GS.

[0110] That is, in some application scenarios, in one example, in XR services, different QUIC connections or different QUIC streams can be used to multiplex multiple media streams on a single IP five-tuple with a transport protocol such as QUIC. In another example, video and audio RTP streams or different media stream layers with different QoS requirements are multiplexed into a single transport layer connection with the same IP five-tuple. However, in related technologies, when data streams use end-to-end encryption, how the UPF distinguishes the QoS of the multiplexed data streams remains to be studied.

[0111] 2. QoS rules

[0112] The User Equipment (UE) performs classification and marking of uplink (UL) user plane traffic according to QoS rules, i.e., associates UL traffic with QoS flows. These QoS rules can be explicitly provided to the UE (i.e., QoS rules explicitly signaled using the PDU session establishment / modification procedure), i.e., they can be pre-configured in the UE, or implicitly derived by the UE by applying reflective QoS. The QoS rules contain the QoS flow identifier (QFI), packet filter set, and priority value of the associated QoS flow. Explicitly signaled QoS rules contain a QoS rule identifier that is unique within a PDU session and is generated by the SMF.

[0113] There can be multiple QoS rules associated with the same QoS flow (ie associated with the same QFI).

[0114] Each PDU Session establishment requires sending a default QoS rule to the UE, and the rule is associated with a QoS flow. For an IP type PDU Session or an Ethernet type PDU Session, the default QoS rule is the only QoS rule for the PDU Session, which may contain a packet filter set that allows all UL packets. In this case, the QoS rule should use the highest priority value.

[0115] For an unstructured type PDU session, the default QoS rule does not contain a packet filter set. In this example, the default QoS rule defines the processing of all packets in the PDU session.

[0116] Generally speaking, data flow classification and identification is based on packet filtering:

[0117] Each packet filter is of variable length and consists of the packet filter direction (2 bits), the packet filter identifier (4 bits), the length of the packet filter contents (1 octet), and the packet filter contents themselves (a variable number of octets).

[0118] The packet filter direction field is used to indicate the direction of traffic to which the filter applies.

[0119] Bit

[0120] 6 5

[0121] 0 0 Reserved

[0122] 0 1 1 downlink only (see Note 2)

[0123] 1 0 Uplink only

[0124] 1 1 Bidirectional

[0125] The Packet Filter Identifier field is used to identify each packet filter in the QoS rule. The least significant 4 bits are used. When the UE requests to "create a new QoS rule", "modify the QoS rule in the related technology and replace all packet filters", or "modify the QoS rule in the related technology and add a packet filter", the Packet Filter Identifier value shall be set to 0.

[0126] The length of the packet filter content field contains the binary-encoded representation of the length of the packet filter content field. The first bit in transmission order is the most significant bit.

[0127] The Packet Filter Content field is of variable size and contains a variable number (at least one) of Packet Filter components. Each Packet Filter component shall be encoded as a sequence of one octet, a Packet Filter Component Type Identifier, and a fixed-length Packet Filter Component Value field. The Packet Filter Component Type Identifier shall be transmitted first.

[0128] Packet filter component type identifier

[0129] Bit

[0130] 8 7 6 5 4 3 2 1

[0131] 0 0 0 0 0 0 0 1 All match types (see Note 2)

[0132] 0 0 0 1 0 0 0 0 IPv4 remote address type

[0133] 0 0 0 1 0 0 0 1 IPv4 local address type

[0134] 0 0 1 0 0 0 0 1 IPv6 remote address / prefix length type

[0135] 0 0 1 0 0 0 1 1 IPv6 local address / prefix length type

[0136] 0 0 1 1 0 0 0 0 Protocol identifier / next header type

[0137] 0 1 0 0 0 0 0 0 Single local port type

[0138] 0 1 0 0 0 0 0 1 Local port range type

[0139] 0 1 0 1 0 0 0 0 Single remote port type

[0140] 0 1 0 1 0 0 0 1 Remote port range type

[0141] 0 1 1 0 0 0 0 0 Security parameter index type

[0142] 0 1 1 1 0 0 0 0 Service type / traffic class type

[0143] 1 0 0 0 0 0 0 Flow label type

[0144] 1 0 0 0 0 0 0 1Destination MAC address type

[0145] 1 0 0 0 0 0 1 0 Source MAC address type

[0146] 1 0 0 0 0 0 1 1 802.1Q C-TAG VID type

[0147] 1 0 0 0 0 1 0 0 802.1Q S-TAG VID type

[0148] 1 0 0 0 0 1 0 1 802.1Q C-TAG PCP / DEI type

[0149] 1 0 0 0 0 1 1 0 802.1Q S-TAG PCP / DEI type

[0150] 1 0 0 0 0 1 1 1Ethertype

[0151] 1 0 0 0 1 0 0 0 Target MAC address range type

[0152] 1 0 0 0 1 0 0 1 Source MAC address range type

[0153] 3. Packet Detection Rule (PDR)

[0154] The PDR contains the information required to classify packets arriving at the UPF. The packet processing flow in the UP function is shown in Figure 2a.

[0155] 4. Media over QUIC Transport (MoQT / MoQ)

[0156] MoQT is a media transport protocol designed to run over QUIC and WebTransport with similar functionality. MoQT allows media producers to publish data and have it consumed by multiple endpoints through subscriptions. It supports intermediary content delivery networks and is designed for large-scale and low-latency distribution.

[0157] MoQT is a protocol optimized for the QUIC protocol that can deliver media directly or through WebTransport. MoQT uses a publish / subscribe workflow in which media producers publish data in response to subscription requests from multiple endpoints. MoQT supports a wide range of use cases with different elasticity and latency requirements (real-time, interactive) without compromising the scalability and cost-effectiveness associated with content delivery networks.

[0158] MoQT is a general-purpose protocol designed to work with multiple MoQ stream formats. These MoQ stream formats define how content is encoded, packaged, and mapped into MoQT objects, as well as discovery and subscription strategies.

[0159] In MoQ, the most important data structures include: object, group, and track.

[0160] The basic data element of MoQT is an object. An object is an addressable unit whose payload is a sequence of bytes. All objects belong to a group, indicating ordering and potential dependencies. Section 2.2 Objects are uniquely identified by their track namespace, track name, group identity (ID), and object ID, and must be the same sequence of bytes regardless of how or where they are retrieved. Objects may become unavailable, but their contents must not change over time.

[0161] Objects consist of two parts: metadata and payload. Metadata is never encrypted and is always visible to relays. The payload portion can be encrypted, in which case it is only visible to producers and consumers. Applications are solely responsible for the content of object payloads. This includes underlying encoding, compression, and any end-to-end encryption or authentication. Relays must not combine, split, or otherwise modify object payloads.

[0162] A group is a collection of objects, a subunit of a track (Section 2.3). Objects in a group should not depend on objects in other groups. A group acts as a join point for subscriptions. A new subscriber may not want to receive the entire track, but may choose to receive only the latest group. The sender then selectively transmits objects based on their group membership.

[0163] A track is a sequence of groups (Section 2.2). It is the entity to which a consumer issues a subscription request. A subscriber can request to receive a single track starting at the group boundary, including any new objects pushed by the creator while the track is active.

[0164] In MoQT, each track has a track name and a track namespace associated with it. The track name identifies a single track within the namespace.

[0165] A MoQT scope is a set of servers (identified by their connection URI) where the tuple of Track Name and Track Namespace is guaranteed to be unique and identifies a specific track.

[0166] If, at a given moment, two tracks within the same scope contain different data, they must have different names and / or namespaces.

[0167] Each track can have one or more associated connection URLs that specify the network hosts through which the track can be accessed.

[0168] Finally, the message structure of MoQ sending application layer data is as follows:

[0169] The OBJECT_DATAGRAM message carries a single object in a datagram. The payload has no explicit length; it is determined by the length of the datagram.

[0170] The object received in the OBJECT_DATAGRAM message has object forwarding preference = datagram. To send an object with object forwarding preference = datagram, determine the length of the fields and payload and send the object as a datagram. In some cases, the object size may be larger than the maximum datagram size for the session, in which case the object will be dropped.

[0171] Subscription ID: A unique subscription identifier within a session. The subscription ID is a monotonically increasing, variable-length integer that must not be reused within a session. Subscribers and publishers use the subscription ID to identify a given subscription. Subscribers specify the subscription ID, which is included in the corresponding SUBSCRIBE_OK or SUBSCRIBE_ERROR message.

[0172] Track Alias: A session-specific identifier for a track. Messages that reference a track, such as OBJECT (Section 6.3), reference this track alias instead of the track name and track namespace to reduce overhead. If a track alias is already in use, the publisher MUST close the session with a duplicate track alias error (Section 3.5).

[0173] Track Namespace: The track namespace defined in Identifier (Section 2.3.1).

[0174] Track Name: The track name as defined in Identification (Section 2.3.1).

[0175] Group ID: The object is a member of the group ID indicated in track section 2.2.

[0176] Object ID:

[0177] 5. Proxying UDP in HTTP

[0178] Proxying UDP in HTTP

[0179] This document (RFC 9298) describes how to proxy UDP in HTTP, similar to how the HTTP CONNECT method allows the Transmission Control Protocol (TCP) to be proxied in HTTP. More specifically, this document defines a protocol that allows an HTTP client to tunnel UDP traffic through an HTTP server that is acting as a proxy.

[0180] The following is the HTTP proxy UDP datagram format:

[0181] UDP Proxying HTTP Datagram Payload{

[0182] Context ID(i),

[0183] UDP Proxying Payload(..),

[0184] }

[0185] FIG2b shows the HTTP proxy UDP datagram format.

[0186] The context ID here is defined as follows:

[0187] A context ID is a 62-bit integer (0 to 262-1). Context IDs are encoded as variable-length integers; see section 16 of [QUIC]. Context ID value 0 is reserved for UDP payloads, while non-zero values ​​are dynamically assigned. Non-zero even-numbered context IDs are assigned by clients, and odd-numbered context IDs are assigned by proxies. The context ID namespace is bound to a given HTTP request; context IDs with the same numeric value may be assigned concurrently in different requests, potentially with different semantics. Context IDs MUST NOT be reassigned within a given HTTP namespace, but may be assigned in any order. Restrictions on context ID allocation exist for the use of even and odd-numbered context IDs to avoid the need for synchronization between endpoints. However, once a context ID is assigned, these restrictions do not apply to its use; it may be used by any client or UDP proxy, regardless of the endpoint that originally assigned it.

[0188] Registration is the act of an endpoint informing its peer of the semantics and format of a given context ID. This document does not define how registration occurs. Future extensions may use HTTP header fields or capsules to register context IDs. Depending on the method used, it is possible to receive a datagram with a context ID that has not yet been registered. This could be due, for example, to reordering of the datagram-containing packet and the registration message-containing packet during transmission.

[0189] In related discussions, some transport protocols, such as QUIC, RTP, and MoQ, have strong application prospects. Solutions based on communication between the UPF and application servers, such as RFC 9298 and N6 tunnels, are also hot topics. However, related technologies have not yet provided solutions for identifying, classifying, and matching MoQ packets, HTTP proxy packets, or how terminals can map and multiplex QoS data flows of multiple media types.

[0190] In view of this, the embodiments of the present application provide a data packet information transmission method, a data packet information determination method, a data packet information transmission device, a data packet information determination device and a communication device to solve the problem in the related art that data packets cannot be correctly identified, classified, matched or mapped.

[0191] The data packet information transmission method and the data packet information determination method provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0192] FIG3 shows a flow chart of a data packet information transmission method provided by an embodiment of the present application. As shown in FIG3 , the data packet information transmission method includes the following steps:

[0193] Step 301: The first device performs a first operation, where the first operation includes at least one of the following:

[0194] Sending first information to the terminal;

[0195] sending second information to the second device;

[0196] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0197] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0198] The first device may include a session management function, such as an SMF.

[0199] The second device may include a user plane function, such as a UPF.

[0200] Identifying data packets can be understood as identifying data packets in a data stream, classifying data packets can be understood as classifying data packets in a data stream, matching data packets can be understood as matching data packets in a data stream with corresponding QoS streams, and mapping data packets to QoS streams can be understood as mapping data packets in a data stream to corresponding QoS streams.

[0201] In an embodiment of the present application, a first device performs a first operation, which includes at least one of the following: sending first information to a terminal; sending second information to a second device; wherein the first information is used for at least one of the following: identifying a data packet; classifying a data packet; or matching a data packet; and the second information is used for at least one of the following: identifying a data packet; classifying a data packet; or matching a data packet. Thus, by sending the first information to the terminal by the first device, the terminal can perform operations such as identifying, classifying, matching, or mapping data packets based on the first information; and by sending the second information to the second device by the first device, the second device can perform operations such as identifying, classifying, matching, or mapping data packets based on the second information.

[0202] In some embodiments, the first information includes at least one of the following: QoS rules; third information;

[0203] Among them, the third information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP (Proxying UDP in HTTP) context identifier.

[0204] The QUIC connection identifier can be understood as a connection identifier used for QUIC, such as a connection ID.

[0205] The MoQT track name can be understood as the track name information used in MoQT, such as track name.

[0206] The MoQT track namespace can be understood as the track namespace information used in MoQT, such as track namespace.

[0207] MoQT track alias can be understood as the track alias information used in MoQT, such as Track alias.

[0208] The MoQT group identifier may be understood as group identifier information used in MoQT, such as Group ID.

[0209] The MoQT object identifier can be understood as the object identification information used in MoQT, such as Object ID.

[0210] The MoQT track identification can be understood as the track identification information used in MoQT, such as Track ID.

[0211] The HTTP proxy UDP context identifier can be understood as information used by an intermediate node (such as a proxy node) to identify the context when forwarding the context, for example, the context ID in the HTTP proxy UDP datagram payload (UDP Proxying HTTP Datagram Payload) defined in RFC 9298.

[0212] For ease of description, the embodiment of the present application uses track information to uniformly represent any one or more of the MoQT track name, MoQT track namespace, MoQT track alias, MoQT group identifier, MoQT object identifier, and MoQT track identifier.

[0213] The QoS rules included in the above-mentioned first information can be ordinary QoS rules (i.e., QoS rules in related technologies) or special QoS rules (or enhanced QoS rules). When the QoS rules are ordinary QoS rules, the first information also includes third information. In this case, the QoS rules and the third information can be transmitted together in the same message, or transmitted separately through different messages. When the QoS rules are special QoS rules, at least one of the following items can be included in the QoS rules: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0214] The following describes the implementation of this special QoS rule.

[0215] In some embodiments, the QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

[0216] Here, the packet filter type is also referred to as the packet filter component type. By adding information indicating the packet filter type to a QoS rule, the QoS rule can be enhanced. This way, the QoS rule contains the information necessary to identify, classify, match, or map packets arriving at the terminal, allowing the terminal to identify, classify, match, or map packets using the QoS rule.

[0217] In some embodiments, the QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0218] By adding packet filters to QoS rules, QoS rules can be enhanced. In this way, QoS rules contain the information needed to identify, classify, match, or map packets arriving at the terminal, allowing the terminal to identify, classify, match, or map packets using QoS rules.

[0219] It should be noted that when the QoS rule is a special QoS rule, the QoS rule may include information for indicating the type of packet filter and the above-mentioned packet filter; or, the QoS rule includes the above-mentioned packet filter but does not include information for indicating the type of packet filter.

[0220] In some embodiments, the second information includes at least one of the following: a PDR; fourth information;

[0221] Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0222] The PDR included in the above-mentioned second information can be an ordinary PDR (i.e., the PDR in the related art) or a special PDR (or enhanced PDR). When the PDR is an ordinary PDR, the second information also includes fourth information. In this case, the PDR and the fourth information can be transmitted together in the same message or separately through different messages. When the PDR is a special PDR, at least one of the following items can be included in the PDR: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0223] The following describes the relevant implementation methods of this special PDR.

[0224] In some embodiments, the PDR includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0225] By adding a packet filter to the PDR, the PDR can be enhanced so that the PDR contains the information required to identify, classify, match, or map packets arriving at the second device, so that the second device can identify, classify, match, or map packets through the PDR.

[0226] In some embodiments, the PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection (Quick UDP Internet Connections, QUIC) with a third device.

[0227] By adding the first indication information to the PDR, the PDR can be enhanced. In this way, the PDR contains the information required to identify, classify, match or map the data packets arriving at the second device, so that the second device can identify, classify and match the data packets through the PDR.

[0228] The third device may include an application function, such as an AF, and may also include an application server (Application Server, AS).

[0229] In some embodiments, the first indication information is included in a protocol description (PD).

[0230] The PD can be understood as an information element (IE) in the PDR. The first indication information is included in the PD, which can be understood as carrying the first indication information through the PD. This can enhance the PD. In this way, there is no need to introduce a new information element in the PDR to carry the above-mentioned first indication information, which makes implementation simpler.

[0231] The following describes relevant implementations of the first device performing the first operation.

[0232] In one embodiment, the method further comprises:

[0233] The first device obtains fifth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0234] The first device performs a first operation, including:

[0235] The first device performs a first operation based on the fifth information;

[0236] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

[0237] In this embodiment, the first device determines the second information (or the first information) based on the obtained fifth information. Specifically, the first device selects all or part of the track information, HTTP proxy UDP context identifier, or QUIC connection identifier included in the fifth information as the second information (or the first information).

[0238] The information included in the second information sent by the first device to the second device may be the full set or a subset of the track information, HTTP proxy UDP context identifier or QUIC connection identifier included in the fifth information. Taking the MoQT track name as an example, the MoQT track name included in the second information may be the full set or a subset of the MoQT track name included in the fifth information. The remaining information can be understood in this way and will not be elaborated on.

[0239] Correspondingly, the information included in the first information sent by the first device to the terminal may also be the full set or subset of the track information, HTTP proxy UDP context identifier or QUIC connection identifier included in the fifth information. To avoid repetition, this will not be elaborated.

[0240] The first information sent by the first device to the terminal may be the same as or partially the same as the second information sent by the first device to the second device.

[0241] Optionally, the first device acquires fifth information including at least one of the following:

[0242] The first device receives fifth information from the fourth device;

[0243] The first device obtains fifth information based on local configuration.

[0244] The fourth device may include a policy control function, such as a PCF.

[0245] Optionally, the first device receives fifth information from the third device, including:

[0246] The first device receives a Policy Control and Charging (PCC) rule from a fourth device, where the PCC rule includes the fifth information.

[0247] Exemplarily, the SMF sends a PDR to the UPF according to the PCC rules sent by the PCF. The PDR contains information required to identify, classify, match or map data packets arriving at the UPF.

[0248] Exemplarily, the SMF sends a PDR to the UPF based on the fifth information of the local configuration, where the PDR contains information required to identify, classify, match or map the data packets arriving at the UPF.

[0249] Exemplarily, the SMF sends a QoS rule to the terminal based on the fifth information configured locally, where the QoS rule includes information required to identify, classify, match, or map data packets arriving at the terminal.

[0250] In one embodiment, the method further comprises:

[0251] The first device receives sixth information from the second device, the sixth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information.

[0252] The first device performs a first operation, including:

[0253] The first device performs the first operation based on the sixth information;

[0254] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0255] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0256] In this embodiment, the first device determines the second information (or the first information) based on the sixth information sent by the second device. Specifically, the first device selects all or part of the track information, HTTP proxy UDP context identifier, or QUIC connection identifier included in the sixth information as the second information (or the first information).

[0257] The information included in the second information sent by the first device to the second device may be the full set or a subset of the track information, HTTP proxy UDP context identifier or QUIC connection identifier included in the sixth information. Taking the MoQT track name as an example, the MoQT track name included in the second information may be the full set or a subset of the MoQT track name included in the sixth information. The remaining information can be understood in this way and will not be elaborated on.

[0258] Correspondingly, the information included in the first information sent by the first device to the terminal may also be the full set or subset of the track information, HTTP proxy UDP context identifier or QUIC connection identifier included in the sixth information. To avoid repetition, this will not be elaborated.

[0259] Exemplarily, the SMF sends a PDR to the UPF based on the track information, HTTP proxy UDP context identifier or QUIC connection identifier sent by the UPF. The PDR contains the information required to identify, classify, match or map the data packets arriving at the UPF.

[0260] Exemplarily, the SMF sends QoS rules to the terminal based on the track information sent by the UPF, the HTTP proxy UDP context identifier or the QUIC connection identifier. The QoS rules contain the information required to identify, classify, match or map the data packets arriving at the terminal.

[0261] In one embodiment, before the first device sends the first information to the terminal, the method further includes:

[0262] The first device receives a first message from the terminal, where the first message is used for at least one of the following:

[0263] Request QoS processing or separation of data flows;

[0264] Request to add new QoS rules;

[0265] Request to bind data flow and QoS flow.

[0266] The above-mentioned data flow may include a user uplink data flow or a service data flow. For example, requesting to bind a data flow and a QoS flow includes at least one of the following: requesting to bind a user uplink data flow and a QoS flow; requesting to bind a service data flow and a QoS flow.

[0267] After receiving the first message, the first device may execute an operation of sending the first information to the terminal.

[0268] That is, the first device performs a first operation including:

[0269] The first device sends first information to the terminal based on the first message.

[0270] Optionally, the first message includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; second indication information;

[0271] The second indication information is used to indicate that the terminal supports, allows or enables MoQT.

[0272] In this embodiment, the first device determines the first information based on the first message sent by the terminal. Specifically, the first device selects all or part of the track information, HTTP proxy UDP context identifier, or QUIC connection identifier included in the first message as the first information.

[0273] The information included in the first information sent by the first device to the terminal may be the full set or a subset of the track information, HTTP proxy UDP context identifier or QUIC connection identifier contained in the first message. Taking the MoQT track name as an example, the MoQT track name included in the second information may be the full set or a subset of the MoQT track name contained in the first message. The remaining information can be understood in this way and will not be elaborated on.

[0274] Optionally, the second indication information is included in a 5G mobility management (5GS Mobility Management, 5GMM) capability information element or a 5G session management (5GS Session Management, 5GSM) capability information element.

[0275] 5GMM or 5GSM can be understood as an information element (IE) in the first message. The second indication information is included in 5GMM or 5GSM, which can be understood as carrying the second indication information through 5GMM or 5GSM, which can achieve an enhancement of 5GMM or 5GSM. In this way, there is no need to introduce a new information element in the first message to carry the above-mentioned second indication information, which is more simple to implement.

[0276] Optionally, the first message satisfies at least one of the following:

[0277] The operation code is set to add a new QoS rule;

[0278] Detach indication is set to request detach;

[0279] The QoS rule identifier is set to indicate that no QoS rule identifier is assigned, or the QoS rule identifier is set to indicate that QoS processing needs to be requested;

[0280] The QoS flow ID is set to indicate that no QoS flow ID is allocated, or the QoS flow ID is set to indicate that QoS processing needs to be requested.

[0281] The first message can be understood as a request message. For example, the request message can be used to request a QoS rule, i.e., a QoS rule request message. For example, the SMF sends a QoS rule to the terminal based on the QoS rule request message sent by the terminal. The QoS rule contains information required to identify, classify, match, or map data packets arriving at the terminal.

[0282] It should be noted that, when the first message contains track information, HTTP proxy UDP context identifier or QUIC connection identifier, the first device determines the first information based on the track information, HTTP proxy UDP context identifier or QUIC connection identifier contained in the first message. Specifically, the first device selects all or part of the MoQT track name, MoQT track namespace, MoQT track alias, MoQT group identifier, MoQT object identifier, MoQT track identifier or HTTP proxy UDP context identifier contained in the first message as the first information. The information included in the first information sent by the first device to the terminal may be the full set or a subset of the corresponding information contained in the first message. Taking the MoQT track name as an example, the MoQT track name included in the first information may be the full set or a subset of the MoQT track name contained in the first message. The remaining information can be understood in this way and will not be elaborated on.

[0283] In the case where the first message does not include track information, HTTP proxy UDP context identifier, or QUIC connection identifier, the first device can determine the first information based on the track information, HTTP proxy UDP context identifier, or QUIC connection identifier included in the fifth or sixth information. For details, please refer to the relevant description above. To avoid repetition, this is not repeated here.

[0284] In summary, in the embodiments of the present application, the first information sent by the first device to the terminal includes information required for identifying, classifying, matching, or mapping data packets arriving at the terminal, enabling the terminal to perform operations such as identifying, classifying, matching, or mapping data packets based on the first information. The second information sent by the first device to the second device includes information required for identifying, classifying, matching, or mapping data packets arriving at the second device, enabling the second device to perform operations such as identifying, classifying, matching, or mapping data packets based on the second information.

[0285] The above is an embodiment of the method on the first device side. The following describes an embodiment of the method on the terminal side.

[0286] FIG4 shows a flow chart of a method for determining data packet information provided by an embodiment of the present application. As shown in FIG4 , the method for determining data packet information includes the following steps:

[0287] Step 401: The terminal obtains first information;

[0288] Step 402: The terminal performs a second operation based on the first information, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0289] Optionally, the first information includes at least one of the following: QoS rules; third information;

[0290] Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

[0291] Optionally, the QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

[0292] Optionally, the QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0293] Optionally, the terminal obtains the first information, including at least one of the following:

[0294] The terminal obtains the first information from the application layer;

[0295] The terminal obtains the first information from a preconfiguration;

[0296] The terminal obtains the first information from the first device;

[0297] The terminal obtains the first information from a fourth device.

[0298] In the embodiment on the first device side, an implementation method is provided in which the first device sends the first information to the terminal, that is, the terminal obtains the first information from the first device. For the terminal, in addition to obtaining the first information from the first device, the terminal can also obtain the first information from other channels. For example, the first information can be obtained from the application layer (which can be understood as obtaining the first information from the AF or AS), obtained from network pre-configured information, or obtained from a fourth device (such as a PCF).

[0299] In some embodiments, before the terminal obtains the first information from the first device, the method further includes:

[0300] The terminal sends a first message, where the first message is used for at least one of the following:

[0301] Request registration;

[0302] Request QoS processing or separation of data flows;

[0303] Request to add new QoS rules;

[0304] Request to bind data flow and QoS flow.

[0305] In an embodiment on the first device side, an implementation method is provided in which the first device receives a request message from the terminal, and the first device provides QoS rules to the terminal based on the request message. For the terminal, in addition to sending a request message to the first device to obtain QoS rules, the terminal can also send a request message to other devices (such as AMF) to obtain QoS rules.

[0306] For example, the terminal may send a first message to the first device to request at least one of the following: requesting QoS processing or separation of a data flow; requesting the addition of a QoS rule; or requesting the binding of a data flow and a QoS flow. In this way, the terminal obtains the QoS rule from the first device.

[0307] Exemplarily, the terminal sends a first message to the AMF to request registration, so that the terminal can also obtain QoS rules during the registration process.

[0308] Optionally, the first message includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; second indication information;

[0309] The second indication information is used to indicate that the terminal supports or allows MoQT.

[0310] Optionally, the second indication information is included in a 5GMM capability information element or a 5GSM capability information element.

[0311] Optionally, the first message satisfies at least one of the following:

[0312] The operation code is set to add a new QoS rule;

[0313] Detach indication is set to request detach;

[0314] The QoS rule identifier is set to indicate that no QoS rule identifier is assigned, or the QoS rule identifier is set to indicate that QoS processing needs to be requested;

[0315] The QoS flow ID is set to indicate that no QoS flow ID is allocated, or the QoS flow ID is set to indicate that QoS processing needs to be requested.

[0316] The Context ID is generated by the UE.

[0317] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0318] generated by the terminal;

[0319] provided by the application layer of the terminal;

[0320] Provided by the operating system (OS) of the terminal.

[0321] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 3, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0322] The above is an embodiment of the method on the terminal side. The following describes an embodiment of the method on the second device side.

[0323] FIG5 is a flowchart of a method for determining data packet information provided by an embodiment of the present application. As shown in FIG5 , the method for determining data packet information includes the following steps:

[0324] Step 501: The second device obtains second information;

[0325] Step 502: The second device performs a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0326] Optionally, the second information includes at least one of the following: PDR; fourth information;

[0327] Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0328] Optionally, the PDR includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0329] Optionally, the PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

[0330] Optionally, the first indication information is included in a protocol description PD.

[0331] Optionally, the second device acquires second information including at least one of the following:

[0332] The second device receives the second information from the first device;

[0333] The second device obtains the second information from a local configuration.

[0334] In the embodiment on the first device side, an implementation method is provided in which the first device sends the second information to the second device, that is, the second device obtains the second information from the first device. For the second device, in addition to obtaining the second information from the first device, the second device can also obtain the second information from other means. For example, obtaining the second information from a local configuration.

[0335] In some embodiments, the method further comprises at least one of the following:

[0336] The second device receives sixth information from the third device;

[0337] The second device sends sixth information to the first device;

[0338] The sixth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; third indication information; fourth indication information;

[0339] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0340] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0341] In the embodiment on the first device side, an implementation method is provided in which the second device sends the sixth information to the first device, that is, the first device obtains the sixth information from the second device. For the second device, the second device can first obtain the sixth information from the third device and then send the obtained sixth information to the first device.

[0342] The second device obtains the sixth information from the third device, which can be understood as the second device obtaining the track information, HTTP proxy UDP context identifier or QUIC connection identifier from the third device through ANNOUNCE.

[0343] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiment of Figure 3, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0344] The above is an embodiment of the method on the second device side. The following describes the overall process of data packet information transmission from the perspective of the communication system.

[0345] FIG6 shows a flow chart of a data packet information transmission method provided by an embodiment of the present application. As shown in FIG6 , the data packet information transmission method includes the following steps:

[0346] Step 601: The third device sends sixth information to the fourth device, where the sixth information includes at least one of the following: a QUIC connection identifier based on a Fast User Datagram Protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0347] Step 602: The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0348] Step 603: The first device performs a first operation based on the fifth information, where the first operation includes at least one of the following: sending first information to a terminal; sending second information to a second device;

[0349] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0350] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0351] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0352] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0353] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0354] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0355] generated by the third device;

[0356] Related to the seventh information;

[0357] containing information indicating the presence or absence of the seventh information;

[0358] The seventh information includes at least one of the following:

[0359] Data packet set sequence number;

[0360] an indication of the end packet of a packet set;

[0361] The packet sequence number within the packet set;

[0362] Packet aggregate size;

[0363] Information indicating the importance of a set of data packets;

[0364] Connection identifier, used for QUIC;

[0365] Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC;

[0366] Information used to identify data flows;

[0367] Information indicating the type of data streaming media;

[0368] Information indicating the priority of a data stream;

[0369] Information indicating the timing of data flow.

[0370] The information used to identify the data stream can be understood as the information used to identify different data streams in the transmission protocol, such as the stream ID in QUIC.

[0371] The information used to indicate the type of data streaming media can be understood as information used in the transmission protocol to identify different types of data streaming media, such as video type, audio type, audio-video type, tactile type, etc.

[0372] The information used to indicate the priority of a data stream can be understood as information used in a transmission protocol to identify the priorities of different data streams, such as the sending order, importance, etc.

[0373] The information used to indicate the time of the data stream can be understood as information used to identify the time of different data streams in the transmission protocol, such as a timestamp.

[0374] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiments in Figures 3 to 5, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0375] The above is a method embodiment of the communication system. The following describes a method embodiment on the third device side.

[0376] FIG7 shows a flow chart of a data packet information transmission method provided by an embodiment of the present application. As shown in FIG7 , the data packet information transmission method includes the following steps:

[0377] Step 701: The third device sends sixth information to the fourth device or the second device, where the sixth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information.

[0378] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0379] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0380] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0381] generated by the third device;

[0382] Related to the seventh information;

[0383] containing information indicating the presence or absence of the seventh information;

[0384] The seventh information includes at least one of the following:

[0385] Data packet set sequence number;

[0386] an indication of the end packet of a packet set;

[0387] The packet sequence number within the packet set;

[0388] Packet aggregate size;

[0389] Information indicating the importance of a set of data packets;

[0390] Connection identifier, used for QUIC;

[0391] Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC;

[0392] Information used to identify data flows;

[0393] Information indicating the type of data streaming media;

[0394] Information indicating the priority of a data stream;

[0395] Information indicating the timing of data flow.

[0396] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiments of Figures 3 to 6, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0397] The above is a method embodiment on the third device side. The following describes a method embodiment on the fourth device side.

[0398] FIG8 is a flow chart of a data packet information transmission method provided by an embodiment of the present application. As shown in FIG8 , the data packet information transmission method includes the following steps:

[0399] Step 801: The fourth device obtains sixth information, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0400] Step 802: The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0401] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0402] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0403] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0404] Optionally, the fourth device sending fifth information to the first device based on the sixth information includes:

[0405] The fourth device sends a control policy and a charging PCC rule to the first device based on the sixth information, where the PCC rule includes the fifth information.

[0406] Optionally, the fourth device acquires sixth information including at least one of the following:

[0407] The fourth device receives sixth information from the third device;

[0408] The fourth device obtains sixth information based on local configuration.

[0409] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0410] generated by a third device;

[0411] Related to the seventh information;

[0412] containing information indicating the presence or absence of the seventh information;

[0413] The seventh information includes at least one of the following:

[0414] Data packet set sequence number;

[0415] an indication of the end packet of a packet set;

[0416] The packet sequence number within the packet set;

[0417] Packet aggregate size;

[0418] Information indicating the importance of a set of data packets;

[0419] Connection identifier, used for QUIC;

[0420] Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC;

[0421] Information used to identify data flows;

[0422] Information indicating the type of data streaming media;

[0423] Information indicating the priority of a data stream;

[0424] Information indicating the timing of data flow.

[0425] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiments of Figures 3 to 7, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0426] In order to better understand the embodiments of the present application, the following specific embodiments are provided to illustrate the solutions of the embodiments of the present application. In the embodiments provided below, the first device is SMF, the second device is UPF, the third device is AF, and the fourth device is PCF.

[0427] Example 1: UL, UE packet identification and flow mapping

[0428] As shown in Figure 9, the following steps are included:

[0429] Step 1a: Optionally, the UE indicates to the AMF that the terminal supports or allows MoQ.

[0430] In some implementations, the UE indicates to the network side that the terminal supports or allows MoQ through the 5GMM capability.

[0431] Step 1b: Optionally, the UE indicates to the SMF that the terminal supports or allows MoQ.

[0432] In some implementations, the UE indicates to the network side that the terminal supports or allows MoQ through the 5G System Session Management (5GS Session Management, 5GSM) capability.

[0433] In step 1c, the UE sends a request message to the network-side device, where the request message is used for at least one of the following: requesting the addition of a QoS rule for identifying, classifying, or marking data packets, where the data flow is related to the XR service; and binding the service data flow to a dedicated QoS flow.

[0434] Optionally, the request message includes at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID. The context ID may be generated by the UE or provided to the UE by an upper layer (such as an operating system OS, an application layer, etc.).

[0435] Optionally, the request message further includes information indicating that the terminal supports or allows MoQ.

[0436] It is worth noting that the above parameters may not be included in the request message, but may be transmitted together with the request message, or sent to the network side device through other NAS messages or NAS processes. That is, the UE sends a request message for QoS rules for identifying, classifying or marking data flows, and at the same time carries at least one of the following items in addition to the request message to the SMF: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; context ID. For example, the network side device can configure QoS rules and configure a matching code for the UE, and the matching code includes at least one of the following items: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; context ID. The UE can determine which QoS flow the data packet should be mapped to by combining the QoS rules and the matching code.

[0437] In some implementations, if the UE needs to request special QoS handling for an XR service data flow, the UE initiates a PDU session modification request message to the network, where the PDU session modification request message includes at least one of the following:

[0438] The Requested QoS rules IE indicates the QoS rules requested for a specific QoS process;

[0439] The Requested QoS flow descriptions IE indicates the QoS flow description requested for a specific QoS process.

[0440] The requested QoS rules IE includes a packet filter and is used to describe the service data flow requested by the UE. The specific QoS parameters requested by the UE are specified in the requested QoS flow description IE.

[0441] At least one of the Requested QoS rules IE and the Requested QoS flow descriptions IE includes at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID.

[0442] In some embodiments, the request message is used to request the network to bind a specific service data flow to a dedicated QoS flow. In this request message, the UE shall create a new QoS rule by setting the Rule Action Code to "Create New QoS Rule" and shall set the Isolation bit of the corresponding QoS rule in the Requested QoS Rule IE to "Requested Isolation." If the QoS rule is newly created, the UE shall set the QRI value in the Requested QoS Rule IE to "Not Assigned QoS Rule Identifier." Otherwise, the UE shall set the QRI value to the value of the QoS rule in the relevant technology for which the specific QoS treatment is applied. If the QoS Flow Description is newly created, the UE shall set the QFI value in the Requested QoS Flow Description IE to "Not Assigned QoS Flow Identifier." Otherwise, the UE shall set the QFI value to the QFI of the QoS Flow Description in the relevant technology for which the specific QoS treatment is applied. The UE shall not request the creation of multiple QoS Flows during a UE-requested PDU Session Modification procedure. If the SMF receives a PDU Session Modification Request message containing multiple QoS rules and a Requested QoS Rule with the Rule Action Code set to "Create New QoS Rule," the SMF shall assign the same QFI to all created QoS rules.

[0443] Step 2: SMF sends QoS rules to UE.

[0444] Optionally, the QoS rule includes at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID.

[0445] The context ID is sent by the UE to the network-side device.

[0446] It is worth noting that the above parameters may not be included in the QoS, but may be transmitted to the UE along with the QoS. That is, when the SMF provides QoS rules, the SMF or other core network elements send at least one of the following to the UE: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; Context ID. These parameters may be sent to the UE along with the PDU Session Modification Accept message, or through other NAS messages or NAS procedures, such as UCU and DL NAS Transport messages.

[0447] Optionally, the QoS rule includes a packet filter set, and the packet filter set includes at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID.

[0448] Step 3: Based on the QoS rule, the UE may map the XR data flow to a specific QoS flow.

[0449] It is worth noting that if parameters such as Track name, Track namespace, Track alias, Group ID, Object ID, Track ID, and context ID are not included in the QoS rule, the UE can map the XR data flow based on the QoS rule and these additional parameters.

[0450] Example 2: DL, UPF packet identification and flow mapping

[0451] The PCC rules are transmitted between the PCF and SMF; the N4rules corresponding to the QoS flow, such as PDR and QoS Enforcement Rule (QER), are transmitted between the SMF and UPF; and the QoS rules corresponding to the QoS flow are transmitted between the SMF and the UE. As shown in Figure 10, the following steps are included:

[0452] Step 1: AF provides flow information.

[0453] Optionally, the AF provides at least one of the following to the PCF:

[0454] Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; context ID;

[0455] The context ID satisfies at least one of the following: generated by an application server; associated with metadata; the context ID carries information indicating the presence or absence of metadata. The metadata includes at least one of the following: a sequence number of a packet set; an indication of the end packet of a packet set; a sequence number of packets within a packet set; a size of a packet set; information indicating the importance of a packet set; a connection identifier used for QUIC; an association identifier used to associate or identify all connection identifiers throughout the life cycle of QUIC; information used to identify a data stream; information used to indicate the type of data streaming media; information used to indicate the priority of a data stream; information used to indicate the time of a data stream.

[0456] In some embodiments, since not all context IDs contain information for identifying or matching data packets, there may be a mapping relationship between the context ID and metadata, or the context ID may contain a field indicating whether metadata exists, or an implicit indication.

[0457] Optionally, the AF also provides at least one of the following to the PCF: a mapping relationship between the context ID and the data packet set information; and a mapping relationship between the context ID and the media type.

[0458] In some embodiments, the data packet set is a PDU set, and the information of the data packet set includes at least one of the following: a PDU set sequence number (PDU Set Sequence Number); an indication of end PDU of the PDU Set (Indication of End PDU of the PDU Set); a PDU sequence number within a PDU Set (PDU Sequence Number within a PDU Set); a PDU set size (in bytes); and a PDU set importance (PDU Set Importance), which is used to identify the relative importance of the PDU set compared to other PDU sets in the QoS flow.

[0459] In some embodiments, the media type includes at least one of the following: video type, audio type, tactile type, audio and video type.

[0460] Step 2: Based on local configuration or information provided by AF, PCF generates PCC rules and sends them to SMF.

[0461] Optionally, the PCC rule includes at least one of the following:

[0462] Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; context ID;

[0463] Step 3: Based on the local configuration or the PCC rules sent by the PCF, the SMF sends a PDR to the UPF, where the PDR contains the information required to classify the data packets arriving at the UPF.

[0464] Optionally, the PDR includes at least one of the following:

[0465] Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; context ID.

[0466] Optionally, the PDR includes first indication information, and the first indication information is used to indicate at least one of the following: Proxying UDP in HTTP; HTTP proxy.

[0467] In some implementations, the PDR includes a Protocol description, and the transport protocol of the Protocol description includes the first indication information.

[0468] In some implementations, the PDR includes a Protocol description, and the Protocol description includes the first indication information.

[0469] In some embodiments, the first indication information indicates at least one of the following: Proxying UDP in HTTP; HTTP proxy.

[0470] In some embodiments, the PDR includes a Packet Filter Set for identifying data packets, and the Packet Filter Set includes at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID.

[0471] Step 4: UPF identifies and matches the received DL data to the corresponding QoS flow based on the PDR.

[0472] It is worth noting that if parameters such as Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID are not included in the PDR, the UPF can identify and match the received downlink (DL) data to the corresponding QoS flow based on the PDR and these additional parameters.

[0473] Example 3: DL, UPF packet identification and flow mapping

[0474] The downlink data stream may include several sub-data streams, such as media data streams, video data streams, etc. This can be described as, in the DL, the second data stream is communicated between the UE and the server, wherein the second data stream includes one or more first data streams.

[0475] To map the received downlink data flow to the QoS flow, the UPF uses a packet filter. The packet filter for the second data flow uses the IP quintuple, while the first data flow matches the data packet using the IP quintuple plus at least one of the following: Track name; Track namespace; Track alias; Group ID; Object ID; Track ID; and context ID.

[0476] For other processes and descriptions, please refer to the embodiment shown in FIG10 .

[0477] Example 4: A QoS rule encoding method

[0478] As shown in Figure 11, the QoS rules are encoded as follows:

[0479] Number of Packet Filters (bits 4 to 1 of octet 7) The number of packet filters contains the binary encoding of the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 to 1 of octet 7, where bit 4 is the most significant bit and bit 1 is the least significant bit. For the "Delete QoS rule in related technology" operation and the "Modify QoS rule in related technology without modifying packet filters" operation, the number of packet filters shall be encoded as 0. For the "Create new QoS rule" operation and the "Modify QoS rule in related technology and replace all packet filters" operation, the number of packet filters shall be greater than or equal to 0 and less than or equal to 15. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.

[0480] Packet filter list (octets 8 to m). A packet filter list contains a variable number of packet filters.

[0481] Each packet filter is of variable length and consists of:

[0482] Packet filtering direction (2 bits);

[0483] Packet filter identifier (4 bits);

[0484] The length of the packet filter content (1 octet); and,

[0485] The packet filter content itself (variable number of octets).

[0486] The packet filter direction field indicates the direction of traffic to which the filter applies, as shown in the following example:

[0487] Bit

[0488] 6 5

[0489] 0 0 Reserved

[0490] 0 1 1 downlink only (see Note 2)

[0491] 1 0 Only 1 uplink

[0492] 1 1 Bidirectional

[0493] The Packet Filter Identifier field is used to identify each packet filter in the QoS rule. The least significant 4 bits are used. When the UE requests to "create a new QoS rule", "modify the QoS rule in the related technology and replace all packet filters", or "modify the QoS rule in the related technology and add a packet filter", the Packet Filter Identifier value shall be set to 0.

[0494] The length of the packet filter content field contains the binary-encoded representation of the length of the packet filter content field. The first bit in transmission order is the most significant bit.

[0495] The Packet Filter Content field is of variable size and contains a variable number (at least one) of Packet Filter components. Each Packet Filter component shall be encoded as a sequence of an octet Packet Filter Component Type identifier and a fixed-length Packet Filter Component Value field. The Packet Filter Component Type identifier shall be transmitted first.

[0496] Packet filter component type identifier, an example is as follows:

[0497] Bit

[0498] 8 7 6 5 4 3 2 1

[0499] 8 7 6 5 4 3 2 1

[0500] 0 0 0 0 0 0 0 1 All match types (see Note 2)

[0501] 0 0 0 1 0 0 0 0 IPv4 remote address type

[0502] 0 0 0 1 0 0 0 1 IPv4 local address type

[0503] 0 0 1 0 0 0 0 1 IPv6 remote address / prefix length type

[0504] 0 0 1 0 0 0 1 1 IPv6 local address / prefix length type

[0505] 0 0 1 1 0 0 0 0 Protocol identifier / next header type

[0506] 0 1 0 0 0 0 0 0 Single local port type

[0507] 0 1 0 0 0 0 0 1 Local port range type

[0508] 0 1 0 1 0 0 0 0 Single remote port type

[0509] 0 1 0 1 0 0 0 1 Remote port range type

[0510] 0 1 1 0 0 0 0 0 Security parameter index type

[0511] 0 1 1 1 0 0 0 0 Service type / traffic class type

[0512] 1 0 0 0 0 0 0 Flow label type

[0513] 1 0 0 0 0 0 0 1Destination MAC address type

[0514] 1 0 0 0 0 0 1 0 Source MAC address type

[0515] 1 0 0 0 0 0 1 1 802.1Q C-TAG VID type

[0516] 1 0 0 0 0 1 0 0 802.1Q S-TAG VID type

[0517] 1 0 0 0 0 1 0 1 802.1Q C-TAG PCP / DEI type

[0518] 1 0 0 0 0 1 1 0 802.1Q S-TAG PCP / DEI type

[0519] 1 0 0 0 0 1 1 1Ethertype

[0520] 1 0 0 0 1 0 0 0 Target MAC address range type

[0521] 1 0 0 0 1 0 0 1 Source MAC address range type

[0522] 1 0 0 0 1 0 1 0 MoQT track name type

[0523] 1 0 0 0 1 0 1 1 MoQT track namespace type

[0524] 1 0 0 0 1 1 0 0 MoQT track alias type

[0525] 1 0 0 0 1 1 0 1 MoQT group ID type

[0526] 1 0 0 0 1 1 1 0 MoQT object ID type

[0527] 1 0 0 0 1 1 1 1 MoQT track ID type

[0528] 1 0 0 1 0 0 0 Context ID type

[0529] 1 0 0 1 0 0 0 1 QUIC connection ID

[0530] All other values ​​are reserved.

[0531] The description and valid combinations of packet filter component type identifiers in packet filters are defined in 3GPP TS 23.501[8].

[0532] For "All match types", the packet filter component should not contain the packet filter component value field.

[0533] For "IPv4 Remote Address Type", the Packet Filter Component Value field shall be encoded as a sequence of a four-octet IPv4 Address field and a four-octet IPv4 Address Mask field. The IPv4 Address field shall be transmitted first.

[0534] For "IPv4 Local Address Type", the Packet Filter Component Value field shall be encoded as defined for "IPv4 Remote Address Type".

[0535] For "IPv6 Remote Address / Prefix Length Type", the Packet Filter Component Value field shall be encoded as a sequence of a 16-octet IPv6 Address field and an octet Prefix Length field. The IPv6 Address field shall be transmitted first.

[0536] For "IPv6 Local Address / Prefix Length Type", the Packet Filter Component Value field shall be encoded as defined for "IPv6 Remote Address / Prefix Length".

[0537] For "Protocol Identifier / Next Header Type", the Packet Filter Component Value field shall be encoded as one octet specifying the IPv4 protocol identifier or the IPv6 next header.

[0538] For "Single Local Port Type" and "Single Remote Port Type", the Packet Filter Component Value field shall be encoded as two octets specifying the port number.

[0539] For "Local Port Range Type" and "Remote Port Range Type", the Packet Filter Component Value field shall be encoded as a sequence of a two-octet Port Range Lower Bound field and a two-octet Port Range Upper Bound field. The Port Range Lower Bound field shall be transmitted first.

[0540] For the "Security Parameter Index", the Packet Filter Component Value field shall be encoded as four octets specifying the IPSec Security Parameter Index.

[0541] For Type of Service / Traffic Class Type, the Packet Filter Component Value field shall be encoded as a sequence of a one-octet Type of Service / Traffic Class field and an eight-octet Type of Service / Traffic Class Mask field. The Type of Service / Traffic Class field shall be transmitted first.

[0542] For the "Flow Label Type", the Packet Filter Component Value field shall be encoded as three octets specifying the IPv6 flow label. Bits 8 through 5 of the first octet shall be spare bits, while the remaining 20 bits shall contain the IPv6 flow label.

[0543] For the "Destination MAC Address Type" and "Source MAC Address Type", the Packet Filter Component Value field shall be encoded as 6 octets of the specified MAC address. When the Packet Filter Direction field displays "Bidirectional", the destination MAC address is the remote MAC address and the source MAC address is the local MAC address.

[0544] For "802.1Q C-TAG VID Type", the Packet Filter Component Value field shall be encoded as two octets specifying the VID of the Customer VLAN Tag (C-TAG). Bits 8 through 5 of the first octet shall be spare bits, while the remaining 12 bits shall contain the VID. If there are multiple C-TAGs in the Ethernet frame header, the outermost C-TAG shall be evaluated.

[0545] For "802.1Q S-TAG VID Type", the Packet Filter Component Value field shall be encoded as two octets specifying the VID of the service-VLAN tag (S-TAG). Bits 8 through 5 of the first octet shall be spare bits, while the remaining 12 bits shall contain the VID. If there are multiple S-TAGs in the Ethernet frame header, the outermost S-TAG shall be evaluated.

[0546] For "802.1Q C-TAG PCP / DEI Type", the Packet Filter Component Value field shall be encoded as one octet specifying the 802.1Q C-TAG PCP and DEI. Bits 8 through 5 of the octet shall be spare, bits 4 through 2 shall contain the PCP, and bit 1 shall contain the DEI. If there are multiple C-TAGs in the Ethernet frame header, the outermost C-TAG shall be evaluated.

[0547] For "802.1Q S-TAG PCP / DEI Type", the Packet Filter Component Value field shall be encoded as one octet specifying the 802.1Q S-TAG PCP. Bits 8 through 5 of the octet shall be spare, bits 4 through 2 shall contain the PCP, and bit 1 shall contain the DEI. If there are multiple S-TAGs in the Ethernet frame header, the outermost S-TAG shall be evaluated.

[0548] For "ethertype type", the Packet Filter Component Value field shall be encoded as two octets specifying the ethertype.

[0549] For the "Destination MAC Address Range Type", the Packet Filter Component Value field shall be encoded as a sequence of a 6-octet Destination MAC Address Range Lower Bound field and a 6-octet Destination MAC Address Range Upper Bound field. The Destination MAC Address Range Lower Bound field is transmitted first. When the Packet Filter Direction field indicates "Bidirectional", the Destination MAC Address Range is a Remote MAC Address Range.

[0550] For the "Source MAC Address Range Type", the Packet Filter Component Value field shall be encoded as a sequence of a 6-octet Source MAC Address Range Lower Bound field and a 6-octet Source MAC Address Range Upper Bound field. The Source MAC Address Range Lower Bound field shall be transmitted first. When the Packet Filter Direction field indicates "Bidirectional", the source MAC address is the local MAC address range.

[0551] NOTE 1: If there is no octet m+1, then octet m+2 shall not be included.

[0552] NOTE 2: The "match all" packet filter component type identifier shall not be used with a packet filter direction of "downlink only".

[0553] The data packet information transmission method provided in the embodiment of the present application can be executed by a data packet information transmission device. The data packet information determination method provided in the embodiment of the present application can be executed by a data packet information determination device. In the embodiment of the present application, the data packet information transmission device provided in the embodiment of the present application is described by taking the data packet information transmission method performed by a data packet information transmission device as an example. In the embodiment of the present application, the data packet information determination device provided in the embodiment of the present application is described by taking the data packet information determination method performed by a data packet information determination device as an example.

[0554] 12 , an embodiment of the present application further provides a data packet information transmission device. As shown in FIG12 , the data packet information transmission device 1200 includes at least one of the following:

[0555] The first sending unit 1201 is configured to send first information to a terminal;

[0556] The second sending unit 1202 is configured to send second information to the second device;

[0557] The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows;

[0558] The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0559] Optionally, the first information includes at least one of the following: QoS rules; third information;

[0560] Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

[0561] Optionally, the QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

[0562] Optionally, the QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0563] Optionally, the second information includes at least one of the following: PDR; fourth information;

[0564] Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0565] Optionally, the PDR includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0566] Optionally, the PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; QUIC having a tunnel or fast UDP network connection with a third device.

[0567] Optionally, the first indication information is included in a protocol description PD.

[0568] Optionally, the device further comprises:

[0569] An acquiring unit, configured to acquire fifth information, the fifth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0570] The first sending unit is specifically configured to: send first information to the terminal based on the fifth information;

[0571] The second sending unit is specifically configured to: send second information to the second device based on the fifth information;

[0572] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

[0573] Optionally, the acquiring unit includes at least one of the following:

[0574] a receiving subunit, configured to receive fifth information from a fourth device;

[0575] The acquiring subunit is configured to acquire fifth information based on the local configuration.

[0576] Optionally, the receiving subunit is specifically configured to:

[0577] The first device receives a control policy and a charging PCC rule from a fourth device, where the PCC rule includes the fifth information.

[0578] Optionally, the device further comprises:

[0579] A receiving unit, configured to receive sixth information from a second device, the sixth information comprising at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information.

[0580] The first sending unit is specifically configured to: send first information to the terminal based on the sixth information;

[0581] The second sending unit is specifically configured to: send second information to the second device based on the sixth information;

[0582] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0583] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

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

[0585] 13 , an embodiment of the present application further provides a device for determining data packet information. As shown in FIG13 , the device 1300 for determining data packet information includes at least one of the following:

[0586] An acquiring unit 1301 is configured to acquire first information;

[0587] The processing unit 1302 is configured to perform a second operation based on the first information, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0588] Optionally, the first information includes at least one of the following: QoS rules; third information;

[0589] Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

[0590] Optionally, the QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

[0591] Optionally, the QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0592] Optionally, the acquiring unit is specifically configured to perform at least one of the following:

[0593] Obtaining the first information from the application layer;

[0594] Obtaining the first information from preconfiguration;

[0595] Acquire the first information from the first device;

[0596] The first information is obtained from a fourth device.

[0597] Optionally, the device further comprises:

[0598] A sending unit, configured to send a first message, where the first message is used for at least one of the following:

[0599] Request registration; request QoS processing or separation of data flows; request to add new QoS rules; request to bind data flows and QoS flows.

[0600] Optionally, the first message includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; second indication information;

[0601] The second indication information is used to indicate that the terminal supports or allows MoQT.

[0602] Optionally, the second indication information is included in a 5GMM capability information element or a 5GSM capability information element.

[0603] Optionally, the first message satisfies at least one of the following:

[0604] The operation code is set to add a new QoS rule;

[0605] Detach indication is set to request detach;

[0606] The QoS rule identifier is set to indicate that no QoS rule identifier is assigned, or the QoS rule identifier is set to indicate that QoS processing needs to be requested;

[0607] The QoS flow ID is set to indicate that no QoS flow ID is allocated, or the QoS flow ID is set to indicate that QoS processing needs to be requested.

[0608] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0609] generated by the terminal;

[0610] provided by the application layer of the terminal;

[0611] Provided by the operating system OS of the terminal.

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

[0613] 14 , an embodiment of the present application further provides a device for determining data packet information. As shown in FIG14 , the device 1400 for determining data packet information includes at least one of the following:

[0614] An acquiring unit 1401 is configured to acquire second information;

[0615] The processing unit 1402 is configured to perform a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0616] Optionally, the second information includes at least one of the following: PDR; fourth information;

[0617] Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0618] Optionally, the PDR includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

[0619] Optionally, the PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

[0620] Optionally, the first indication information is included in a protocol description PD.

[0621] Optionally, the acquiring unit includes at least one of the following:

[0622] a receiving subunit, configured to receive the second information from the first device;

[0623] The acquiring subunit is configured to acquire the second information from a local configuration.

[0624] Optionally, the device further comprises at least one of the following:

[0625] a receiving unit, configured to receive sixth information from a third device;

[0626] a sending unit, configured to send sixth information to the first device;

[0627] The sixth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; third indication information; fourth indication information;

[0628] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0629] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0630] The data packet information determination device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0631] 15 , an embodiment of the present application further provides a data packet information transmission device. As shown in FIG15 , the data packet information transmission device 1500 includes at least one of the following:

[0632] The sending unit 1501 is configured to send sixth information to the fourth device or the second device, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0633] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; QUIC with a tunnel or fast UDP network connection with a third device;

[0634] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0635] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0636] generated by the third device;

[0637] Related to the seventh information;

[0638] containing information indicating the presence or absence of the seventh information;

[0639] The seventh information includes at least one of the following:

[0640] Data packet set sequence number;

[0641] an indication of the end packet of a packet set;

[0642] The packet sequence number within the packet set;

[0643] Packet aggregate size;

[0644] Information indicating the importance of a set of data packets;

[0645] Connection identifier, used for QUIC;

[0646] Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC;

[0647] Information used to identify data flows;

[0648] Information indicating the type of data streaming media;

[0649] Information indicating the priority of a data stream;

[0650] Information indicating the timing of data flow.

[0651] The data packet information transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0652] 16 , an embodiment of the present application further provides a data packet information transmission device. As shown in FIG16 , the data packet information transmission device 1600 includes at least one of the following:

[0653] The acquisition unit 1601 is configured to acquire sixth information, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information.

[0654] The sending unit 1602 is configured to send fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information.

[0655] The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device;

[0656] The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device;

[0657] The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

[0658] Optionally, the sending unit is specifically configured to:

[0659] Based on the sixth information, a control policy and charging PCC rules are sent to the first device, where the PCC rules include the fifth information.

[0660] Optionally, the acquiring unit includes at least one of the following:

[0661] a receiving subunit, configured to receive sixth information from a third device;

[0662] The acquiring subunit is configured to acquire sixth information based on the local configuration.

[0663] Optionally, the HTTP proxy UDP context identifier satisfies at least one of the following:

[0664] generated by a third device;

[0665] Related to the seventh information;

[0666] containing information indicating the presence or absence of the seventh information;

[0667] The seventh information includes at least one of the following:

[0668] Data packet set sequence number;

[0669] an indication of the end packet of a packet set;

[0670] The packet sequence number within the packet set;

[0671] Packet aggregate size;

[0672] Information indicating the importance of a set of data packets;

[0673] Connection identifier, used for QUIC;

[0674] Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC;

[0675] Information used to identify data flows;

[0676] Information indicating the type of data streaming media;

[0677] Information indicating the priority of a data stream;

[0678] Information indicating the timing of data flow.

[0679] The data packet information transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 8 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0680] The data packet information transmission device and data packet information determination 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 other device 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.

[0681] As shown in Figure 17, an embodiment of the present application further provides a communication device 1700, including a processor 1701 and a memory 1702. The memory 1702 stores a program or instruction that can be run on the processor 1701. For example, when the communication device 1700 is a terminal, the program or instruction, when executed by the processor 1701, implements the various steps of the above-mentioned terminal-side method embodiment and can achieve the same technical effect. When the communication device 1700 is a network-side device, the program or instruction, when executed by the processor 1701, implements the various steps of the above-mentioned network-side device-side method embodiment and can achieve the same technical effect. To avoid repetition, they are not repeated here.

[0682] 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 of the method embodiment shown in FIG4 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG18 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0683] The terminal 1800 includes but is not limited to: a radio frequency unit 1801, a network module 1802, an audio output unit 1803, an input unit 1804, a sensor 1805, a display unit 1806, a user input unit 1807, an interface unit 1808, a memory 1809 and at least some of the components of the processor 1810.

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

[0685] It should be understood that in an embodiment of the present application, the input unit 1804 may include a graphics processing unit (GPU) 18041 and a microphone 18042, and the graphics processor 18041 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 1806 may include a display panel 18061, and the display panel 18061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1807 includes a touch panel 18071 and at least one of other input devices 18072. The touch panel 18071 is also called a touch screen. The touch panel 18071 may include two parts: a touch detection device and a touch controller. Other input devices 18072 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 a joystick, which will not be repeated here.

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

[0687] The memory 1809 can be used to store software programs or instructions and various data. The memory 1809 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 1809 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

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

[0689] The RF unit 1801 or the processor 1810 is configured to:

[0690] Obtaining first information;

[0691] The processor 1810 is used to:

[0692] Based on the first information, a second operation is performed, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

[0693] In an embodiment of the present application, by obtaining the first information, the terminal can perform operations such as identification, classification, matching or mapping of data packets based on the first information.

[0694] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the terminal side data packet information determination method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0695] An embodiment of the present application further 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 method embodiment shown in Figure 3, Figure 5, Figure 6, Figure 7, or Figure 8. This network-side device embodiment corresponds to the first device-side, second device-side, third device-side, or fourth device-side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0696] Specifically, an embodiment of the present application further provides a network-side device. As shown in FIG19 , the network-side device 1900 includes a processor 1901, a network interface 1902, and a memory 1903. The network interface 1902 is, for example, a common public radio interface (CPRI).

[0697] Specifically, the network side device 1900 of the embodiment of the present application also includes: instructions or programs stored in the memory 1903 and can be run on the processor 1901. The processor 1901 calls the instructions or programs in the memory 1903 to execute the methods executed by the modules shown in Figure 12 or Figure 14 or Figure 15 or Figure 16, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0698] 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 data packet information transmission method embodiment or the data packet information determination method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0700] 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 data packet information transmission method embodiment or the data packet information determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0702] 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 data packet information transmission method embodiment or the data packet information determination method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0703] An embodiment of the present application also provides a communication system, including: a first device, a terminal and a second device, wherein the first device can be used to execute the steps of the data packet information transmission method on the first device side as described above, the terminal can be used to execute the steps of the data packet information determination method on the terminal side as described above, and the second device can be used to execute the steps of the data packet information determination method on the second device side as described above.

[0704] Optionally, the communication system further includes a third device, and the third device can be used to execute the steps of the data packet information transmission method on the third device side as described above.

[0705] Optionally, the communication system further includes a fourth device, which can be used to execute the steps of the data packet information transmission method on the fourth device side as described above.

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

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

[0708] 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 transmitting data packet information, comprising: The first device performs a first operation, where the first operation includes at least one of the following: Sending first information to the terminal; sending second information to the second device; The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to quality of service (QoS) flows; The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

2. The method according to claim 1, wherein The first information includes at least one of the following: QoS rules; Third information; Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

3. The method according to claim 2, wherein: The QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

4. The method according to claim 2 or 3, wherein: The QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

5. The method according to claim 1, wherein The second information includes at least one of the following: Packet detection rule PDR; Fourth information; Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

6. The method according to claim 5, wherein: The PDR includes a data packet filter, and the data packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

7. The method according to claim 5 or 6, wherein: The PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

8. The method according to claim 7, wherein: The first indication information is included in the protocol description PD.

9. The method according to any one of claims 1 to 8, wherein The method further comprises: The first device obtains fifth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information. The first device performs a first operation, including: The first device performs a first operation based on the fifth information; The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

10. The method according to claim 9, wherein: The first device obtains fifth information, including at least one of the following: The first device receives fifth information from the fourth device; The first device obtains fifth information based on local configuration.

11. The method according to claim 10, wherein: The first device receives fifth information from the third device, including: The first device receives a control policy and a charging PCC rule from a fourth device, where the PCC rule includes the fifth information.

12. The method according to any one of claims 1 to 8, wherein The method further comprises: The first device receives sixth information from the second device, the sixth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information. The first device performs a first operation, including: The first device performs the first operation based on the sixth information; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

13. A method for determining data packet information, comprising: The terminal obtains the first information; The terminal performs a second operation based on the first information, where the second operation includes at least one of the following: identifying a data packet; Classify packets; match packets; map packets to QoS flows.

14. The method according to claim 13, wherein The first information includes at least one of the following: QoS rules; Third information; Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

15. The method according to claim 14, wherein The QoS rule includes information for indicating a packet filter type, and the packet filter type includes at least one of the following: QUIC connection identifier type; MoQT track name type; MoQT track namespace type; MoQT track alias type; MoQT group identifier type; MoQT object identifier type; MoQT track identifier type; HTTP proxy UDP context identifier type.

16. The method according to claim 14 or 15, wherein: The QoS rule includes a packet filter, and the packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

17. The method according to any one of claims 13 to 16, wherein The terminal obtains first information, including at least one of the following: The terminal obtains the first information from the application layer; The terminal obtains the first information from a preconfiguration; The terminal obtains the first information from the first device; The terminal obtains the first information from a fourth device.

18. The method according to claim 17, wherein Before the terminal obtains the first information from the first device, the method further includes: The terminal sends a first message, where the first message is used for at least one of the following: Request registration; Request QoS processing or separation of data flows; Request to add new QoS rules; Request to bind data flow and QoS flow.

19. The method according to claim 18, wherein The first message includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; second indication information; The second indication information is used to indicate that the terminal supports or allows MoQT.

20. The method according to claim 19, wherein The second indication information is included in a 5GMM capability information element or a 5GSM capability information element.

21. The method according to any one of claims 18 to 20, wherein The first message satisfies at least one of the following: The operation code is set to add a new QoS rule; Detach indication is set to request detach; The QoS rule identifier is set to indicate that no QoS rule identifier is assigned, or the QoS rule identifier is set to indicate that QoS processing needs to be requested; The QoS flow ID is set to indicate that no QoS flow ID is allocated, or the QoS flow ID is set to indicate that QoS processing needs to be requested.

22. The method of claim 14, 16 or 19, wherein: The HTTP proxy UDP context identifier satisfies at least one of the following: generated by the terminal; provided by the application layer of the terminal; Provided by the operating system OS of the terminal.

23. A method for determining data packet information, comprising: The second device obtains second information; The second device performs a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to quality of service (QoS) flows.

24. The method according to claim 23, wherein The second information includes at least one of the following: Packet detection rule PDR; Fourth information; Among them, the fourth information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

25. The method according to claim 24, wherein The PDR includes a data packet filter, and the data packet filter includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

26. The method according to claim 24 or 25, wherein The PDR includes first indication information, and the first indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

27. The method according to claim 26, wherein The first indication information is included in the protocol description PD.

28. The method according to any one of claims 23 to 27, wherein The second device acquires second information, including at least one of the following: The second device receives the second information from the first device; The second device obtains the second information from a local configuration.

29. The method according to any one of claims 23 to 28, wherein The method further comprises at least one of the following: The second device receives sixth information from the third device; The second device sends sixth information to the first device; The sixth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier; third indication information; fourth indication information; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

30. A method for transmitting data packet information, comprising: The third device sends sixth information to the fourth device, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information. The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information. The first device performs a first operation based on the fifth information, where the first operation includes at least one of the following: sending first information to a terminal; sending second information to a second device; The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to quality of service (QoS) flows; The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to QoS flows; The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or fast UDP network connection QUIC with a third device; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

31. A method for transmitting data packet information, comprising: The third device sends sixth information to the fourth device or the second device, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information. The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

32. The method according to claim 31, wherein The HTTP proxy UDP context identifier satisfies at least one of the following: generated by the third device; Related to the seventh information; containing information indicating the presence or absence of the seventh information; The seventh information includes at least one of the following: Data packet set sequence number; an indication of the end packet of a packet set; The packet sequence number within the packet set; Packet aggregate size; Information indicating the importance of a set of data packets; Connection identifier, used for QUIC; Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC; Information used to identify data flows; Information indicating the type of data streaming media; Information used to indicate the priority of a data stream; Information indicating the timing of data flow.

33. A method for transmitting data packet information, comprising: The fourth device obtains sixth information, where the sixth information includes at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information. The fourth device sends fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information. The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

34. The method according to claim 33, wherein The fourth device sending fifth information to the first device based on the sixth information includes: The fourth device sends a control policy and a charging PCC rule to the first device based on the sixth information, where the PCC rule includes the fifth information.

35. The method according to claim 33 or 34, wherein The fourth device obtains sixth information, including at least one of the following: The fourth device receives sixth information from the third device; The fourth device obtains sixth information based on local configuration.

36. The method of claim 33, wherein: The HTTP proxy UDP context identifier satisfies at least one of the following: generated by a third device; Related to the seventh information; containing information indicating the presence or absence of the seventh information; The seventh information includes at least one of the following: Data packet set sequence number; an indication of the end packet of a packet set; The packet sequence number within the packet set; Packet aggregate size; Information indicating the importance of a set of data packets; Connection identifier, used for QUIC; Association identifier, used to associate or identify all connection identifiers throughout the life cycle of QUIC; Information used to identify data flows; Information indicating the type of data streaming media; Information used to indicate the priority of a data stream; Information indicating the timing of data flow.

37. A data packet information transmission device, the device comprising at least one of the following: A first sending unit, configured to send first information to a terminal; A second sending unit, configured to send second information to a second device; in, The first information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; mapping data packets to quality of service (QoS) flows; The second information is used for at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to QoS flows.

38. The apparatus according to claim 37, wherein The first information includes at least one of the following: QoS rules; Third information; Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

39. The apparatus of claim 37, wherein: The second information includes at least one of the following: Packet detection rule PDR; Fourth information; Among them, the fourth information includes at least one of the following: QUIC connection identifier; MoQT track name; MoQT track namespace; MoQT track alias; MoQT group identifier; MoQT object identifier; MoQT track identifier; HTTP proxy UDP context identifier.

40. The device according to any one of claims 37 to 39, wherein Also includes: An acquiring unit, configured to acquire fifth information, the fifth information including at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information. The first sending unit is specifically configured to: send first information to the terminal based on the fifth information; The second sending unit is specifically configured to: send second information to the second device based on the fifth information; The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device.

41. The device according to any one of claims 37 to 39, wherein The device further comprises: A receiving unit, configured to receive sixth information from a second device, the sixth information comprising at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; third indication information; and fourth indication information. The first sending unit is specifically configured to: send first information to the terminal based on the sixth information; The second sending unit is specifically configured to: send second information to the second device based on the sixth information; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

42. A device for determining data packet information, the device comprising: an acquiring unit, configured to acquire first information; The processing unit is configured to perform a second operation based on the first information, where the second operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to quality of service (QoS) flows.

43. The apparatus according to claim 42, wherein The first information includes at least one of the following: QoS rules; Third information; Among them, the third information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for the media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and a Hypertext Transfer Protocol HTTP proxy User Datagram Protocol UDP context identifier.

44. A device for determining data packet information, the device comprising: an acquiring unit, configured to acquire second information; The processing unit is configured to perform a third operation based on the second information, where the third operation includes at least one of the following: identifying data packets; classifying data packets; matching data packets; and mapping data packets to quality of service (QoS) flows.

45. The apparatus of claim 44, wherein: The second information includes at least one of the following: Packet detection rule PDR; Fourth information; Among them, the fourth information includes at least one of the following: a QUIC connection identifier based on the Fast User Datagram Protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; and an HTTP proxy UDP context identifier.

46. ​​A data packet information transmission device, the device comprising: A sending unit, configured to send sixth information to the fourth device or the second device, the sixth information including at least one of the following: a QUIC connection identifier based on a fast user datagram protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information. The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

47. A data packet information transmission device, the device comprising: An acquiring unit is configured to acquire sixth information, the sixth information including at least one of the following: a QUIC connection identifier based on a Fast User Datagram Protocol network connection; a MoQT track name for media transmitted based on QUIC; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; a Hypertext Transfer Protocol (HTTP) proxy User Datagram Protocol (UDP) context identifier; third indication information; and fourth indication information. A sending unit, configured to send fifth information to the first device based on the sixth information, where the fifth information includes at least one of the following: a QUIC connection identifier; a MoQT track name; a MoQT track namespace; a MoQT track alias; a MoQT group identifier; a MoQT object identifier; a MoQT track identifier; an HTTP proxy UDP context identifier; and second indication information; The second indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The third indication information is used to indicate at least one of the following: QUIC; MoQT; HTTP proxy UDP; HTTP proxy; a tunnel or QUIC with a third device; The fourth indication information is used to indicate at least one of the following: an association relationship between the HTTP proxy UDP context identifier and a data packet set; and an association relationship between the HTTP proxy UDP context identifier and a data packet media type.

48. A communication device, comprising a processor and a memory, the memory storing a program or instruction that can be run on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the data packet information transmission method according to any one of claims 1 to 12, or implements the steps of the data packet information determination method according to any one of claims 13 to 22, or implements the steps of the data packet information determination method according to any one of claims 23 to 29, or implements the steps of the data packet information transmission method according to claim 31 or 32, or implements the steps of the data packet information transmission method according to any one of claims 33 to 36.

49. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the data packet information transmission method according to any one of claims 1 to 12, or implements the steps of the data packet information determination method according to any one of claims 13 to 22, or implements the steps of the data packet information determination method according to any one of claims 23 to 29, or implements the steps of the data packet information transmission method according to claim 30, or implements the steps of the data packet information transmission method according to claim 31 or 32, or implements the steps of the data packet information transmission method according to any one of claims 33 to 36.

50. A computer program product, comprising computer instructions, which, when executed by a processor, implement the steps of the data packet information transmission method according to any one of claims 1 to 12, or implement the steps of the data packet information determination method according to any one of claims 13 to 22, or implement the steps of the data packet information determination method according to any one of claims 23 to 29, or implement the steps of the data packet information transmission method according to claim 30, or implement the steps of the data packet information transmission method according to claim 31 or 32, or implement the steps of the data packet information transmission method according to any one of claims 33 to 36.

Images