Information transmission method and communication apparatus

Abstract

The present application provides an information transmission method and a communication apparatus. The method comprises: a first network element may design related PFS information on the basis of the type of a PDU session requested by a terminal, wherein the PFS information may be a PFS of RDMA; and the first network element may send the PFS information. In this way, a device (such as a terminal, an access network device, and a second network element) in a network receives the PFS information, and identifies an RDMA packet in the PDU session on the basis of the PFS of the RDMA, thereby realizing differentiated QoS control.

Description

An information transmission method and communication device

[0001] This application claims priority to Chinese Patent Application No. 202410673906.3, filed on May 27, 2024, entitled "An Information Transmission Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to an information transmission method and communication device. Background Technology

[0003] Remote direct memory access (RDMA) technology allows direct access to memory data through the network interface without the intervention of the operating system kernel. Therefore, RDMA is suitable for high-throughput, low-latency network communication, especially in large-scale parallel computer clusters. For example, when data transmission rates reach 40 gigabits per second (Gbps), traditional transmission control protocol / Internet protocol (TCP / IP) results in 100% CPU utilization; while using an RDMA network card, CPU utilization is only 5%. With the development of mobile communication networks, for example, future communication systems may have peak rates of 50Gbps / 100Gbps / 200Gbps. In such high-peak-rate scenarios, if TCP / IP is still used for data transmission, the terminal CPU will be overwhelmed by the high-throughput TCP / IP packet encapsulation / disassembly. Therefore, how to design relevant packet filter sets (PFS) to support RDMA packet recognition in high-throughput scenarios has become an unsolved problem. Summary of the Invention

[0004] This application provides an information transmission method and communication device. The method designs a PFS information, which is beneficial for network devices (such as terminals, base stations, user plane function (UPF) network elements, etc.) to perform quality of service (QoS) control.

[0005] Firstly, this application provides an information transmission method applied to a first network element. For example, the method can be executed by the first network element, which may be a session management function (SMF), a component of the SMF (e.g., a processor, chip, or chip system), or a logic module capable of implementing all or part of the SMF's functions. The first network element determines PFS information based on the protocol data unit (PDU) session type requested by the terminal. The PDU session type requested by the terminal includes at least one of the following: infinite bandwidth (IB) session, a first remote direct memory access over converged Ethernet (RDMA) session (RoCE), and a second RoCE session. The PFS information includes at least one of the following: IB-level PFS, a first RoCE-level PFS, and a second RoCE-level PFS. The first network element then transmits the PFS information.

[0006] In this method, the first network element can design relevant PFS information based on the PDU session type requested by the terminal. This PFS information can be an RDMA PFS, which is beneficial for network devices (such as terminals, access network devices, second network elements, etc.) to identify RDMA packets in the PDU session based on the RDMA PFS, thereby achieving differentiated QoS control. Optionally, the first RoCE can be represented as RoCEv1, and the second RoCE can be represented as RoCEv2.

[0007] In one possible implementation, the first network element receives a QoS policy at the service data flow (SDF) granularity, which is associated with RDMA messages and PFS information. The first network element then transmits the QoS policy.

[0008] In this implementation, the first network element can receive a QoS policy, which is related to RDMA messages and PFS information. Furthermore, the first network element can send the QoS policy to devices in the network (such as terminals, base stations, UPFs, etc.), which facilitates QoS control of data in the RDMA session by devices in the network based on the QoS policy.

[0009] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source global identifier (GID), destination GID, destination queue pair number (QPN), and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0010] This embodiment describes the specific implementation of IB-level PFS or first RoCE-level PFS (the software protocol stacks of IB-level sessions and first RoCE-level sessions are similar). It can be an IB quadruple or an IB quintuple. For example, the IB quadruple or IB quintuple includes information such as GID, QPN, and protocol type. The protocol type in the IB quadruple or IB quintuple includes RMDA protocol types such as IB / RoCEv1, which is beneficial for devices in the network to perform QoS control on data in the RDMA session based on PFS information and QoS policies.

[0011] In one possible implementation, the second RoCE level PFS includes an Internet protocol (IP) six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type. Optionally, the destination port number can be a specific value such as 4791.

[0012] This embodiment describes a specific implementation of the second RoCE-level PFS, which can be an IP six-tuple or an IP seven-tuple. For example, the IP six-tuple or IP seven-tuple includes information such as IP address, port number, QPN, and protocol type. The protocol type in the IP six-tuple or IP seven-tuple includes RDMA protocol types such as RoCEv2, which facilitates QoS control of data in the RDMA session by network devices based on PFS information and QoS policies. Optionally, the software protocol stack of the second RoCE-level session differs from that of the first RoCE-level session, primarily in the network layer protocol stack; therefore, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple.

[0013] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0014] In this implementation, the PFS information is related to the service type of the IB transport layer message; for example, the first indication information in the PFS information can indicate that the service type of the IB transport layer message is RDMA connection service or RDMA data packet service, which is beneficial for devices in the network to perform QoS control on the data in the RDMA session based on the PFS information and QoS policy.

[0015] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0016] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0017] In the above embodiments, when the first indication information indicates that the IB transport layer message is of a different service type, the corresponding PFS information also includes different content.

[0018] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0019] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information also includes a datagram extended transport header (DETH), which includes the source QPN.

[0020] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0021] The above embodiments describe the specific implementation of the first indication information. For example, the first indication can be represented by 8 bits, and the first indication information can represent different meanings when the values ​​of each bit are different.

[0022] In one possible implementation, PFS information is sent from the first network element to the second network element; the second network element is a UPF, or a traffic plane function (TPF) network element, or a computing executor (CE) network element.

[0023] In this embodiment, the first network element sends PFS information, which can be the first network element sending PFS information to the second network element; correspondingly, the second network element receives the PFS information.

[0024] In one possible implementation, PFS information is sent by the first network element to the access network device or terminal through the access and mobility management (AMF) network element.

[0025] In this embodiment, the first network element sending PFS information can be the first network element sending PFS information to the access network device (such as a base station) or terminal. Specifically, the first network element can send PFS information to the access network device or terminal through AMF.

[0026] Secondly, this application provides an information transmission method applied to a terminal. This method can be executed by the terminal, applied to a communication module or component of the terminal, or applied to a circuit or chip of the terminal (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip, etc.). The terminal receives PFS information; this PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, second RoCE-level PFS. Based on the PFS information, the terminal performs quality of service control on uplink data packets.

[0027] In this method, the terminal can receive PFS information, which can be RDMA PFS. This is beneficial for the terminal to identify RDMA messages in the PDU session based on RDMA PFS, thereby achieving QoS control.

[0028] In one possible implementation, the terminal receives a QoS policy that is associated with RDMA messages and PFS information.

[0029] In this embodiment, the terminal can receive a QoS policy, which is related to RDMA messages and PFS information. The terminal can then perform QoS control on the data in the RDMA session based on the QoS policy and PFS information.

[0030] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0031] This embodiment describes the specific implementation of IB-level PFS or first RoCE-level PFS (the software protocol stacks of IB-level sessions and first RoCE-level sessions are similar). It can be an IB quadruple or an IB quintuple. For example, the IB quadruple or IB quintuple includes information such as GID, QPN, and protocol type. The protocol type in the IB quadruple or IB quintuple includes RMDA protocol types such as IB / RoCEv1, which is beneficial for devices in the network to perform QoS control on data in the RDMA session based on PFS information and QoS policies.

[0032] In one possible implementation, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0033] This embodiment describes a specific implementation of the second RoCE-level PFS, which can be an IP six-tuple or an IP seven-tuple. For example, the IP six-tuple or IP seven-tuple includes information such as IP address, port number, QPN, and protocol type. The protocol type in the IP six-tuple or IP seven-tuple includes RDMA protocol types such as RoCEv2, which facilitates QoS control of data in the RDMA session by network devices based on PFS information and QoS policies. Optionally, the software protocol stack of the second RoCE-level session differs from that of the first RoCE-level session, primarily in the network layer protocol stack; therefore, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple.

[0034] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0035] In this implementation, the PFS information is related to the service type of the IB transport layer message; for example, the first indication information in the PFS information can indicate that the service type of the IB transport layer message is RDMA connection service or RDMA data packet service, which is beneficial for devices in the network to perform QoS control on the data in the RDMA session based on the PFS information and QoS policy.

[0036] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0037] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0038] In the above embodiments, when the first indication information indicates that the IB transport layer message is of a different service type, the corresponding PFS information also includes different content.

[0039] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0040] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0041] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0042] The above embodiments describe the specific implementation of the first indication information. For example, the first indication can be represented by 8 bits, and the first indication information can represent different meanings when the values ​​of each bit are different.

[0043] Thirdly, this application provides an information transmission method. This method is applied to an access network device (such as a base station), or to a component of the access network device (such as a processor, chip, or chip system), and can also be applied to a logic module capable of implementing all or part of the functions of the access network device. Specifically, the access network device receives PFS information; this PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. Based on the PFS information, the access network device performs quality of service control.

[0044] In this method, the access network device can receive PFS information, which can be RDMA PFS. This is beneficial for the access network device to identify RDMA packets in the PDU session based on RDMA PFS, thereby performing QoS control. For example, the access network device can map RDMA service flow to the corresponding QoS flow or data radio bearer (DRB).

[0045] In one possible implementation, the access network device receives a QoS policy that is related to RDMA messages and PFS information.

[0046] In this embodiment, the access network device can receive a QoS policy, which is related to RDMA messages and PFS information. The access network device can then map the RDMA service flow to the corresponding QoS flow or DRB based on the QoS policy and PFS information.

[0047] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0048] This embodiment describes the specific implementation of IB-level PFS or first RoCE-level PFS (the software protocol stacks of IB-level sessions and first RoCE-level sessions are similar). It can be an IB quadruple or an IB quintuple. For example, the IB quadruple or IB quintuple includes information such as GID, QPN, and protocol type. The protocol type in the IB quadruple or IB quintuple includes RMDA protocol types such as IB / RoCEv1, which is beneficial for devices in the network to perform QoS control on data in the RDMA session based on PFS information and QoS policies.

[0049] In one possible implementation, the second RoCE level PFS includes an Internet protocol (IP) six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0050] This embodiment describes a specific implementation of the second RoCE-level PFS, which can be an IP six-tuple or an IP seven-tuple. For example, the IP six-tuple or IP seven-tuple includes information such as IP address, port number, QPN, and protocol type. The protocol type in the IP six-tuple or IP seven-tuple includes RDMA protocol types such as RoCEv2, which facilitates QoS control of data in the RDMA session by network devices based on PFS information and QoS policies. Optionally, the software protocol stack of the second RoCE-level session differs from that of the first RoCE-level session, primarily in the network layer protocol stack; therefore, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple.

[0051] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0052] In this implementation, the PFS information is related to the service type of the IB transport layer message; for example, the first indication information in the PFS information can indicate that the service type of the IB transport layer message is RDMA connection service or RDMA data packet service, which is beneficial for devices in the network to perform QoS control on the data in the RDMA session based on the PFS information and QoS policy.

[0053] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0054] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0055] In the above embodiments, when the first indication information indicates that the IB transport layer message is of a different service type, the corresponding PFS information also includes different content.

[0056] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0057] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0058] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0059] The above embodiments describe the specific implementation of the first indication information. For example, the first indication can be represented by 8 bits, and the first indication information can represent different meanings when the values ​​of each bit are different.

[0060] Fourthly, this application provides an information transmission method applied to a second network element. For example, the method can be executed by a second network element, which may be a UPF, a TPF, or a CE. The second network element receives PFS information; this PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. Based on the PFS information, the second network element performs quality of service control.

[0061] In this method, the second network element can receive PFS information, which can be RDMA PFS. This is beneficial for access network devices to identify RDMA packets in PDU sessions based on RDMA PFS, thereby achieving QoS control; for example, performing uplink QoS flow ID (QFI) verification, or downlink QFI marking and control, etc.

[0062] In one possible implementation, the second network element receives a QoS policy that is related to RDMA messages and PFS information.

[0063] In this implementation, the second network element can receive a QoS policy, which is related to RDMA messages and PFS information. The second network element can then perform uplink QFI verification or downlink QFI marking and control based on the QoS policy and PFS information.

[0064] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0065] This embodiment describes the specific implementation of IB-level PFS or first RoCE-level PFS (the software protocol stacks of IB-level sessions and first RoCE-level sessions are similar). It can be an IB quadruple or an IB quintuple. For example, the IB quadruple or IB quintuple includes information such as GID, QPN, and protocol type. The protocol type in the IB quadruple or IB quintuple includes RMDA protocol types such as IB / RoCEv1, which is beneficial for devices in the network to perform QoS control on data in the RDMA session based on PFS information and QoS policies.

[0066] In one possible implementation, the second RoCE level PFS includes an Internet protocol (IP) six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0067] This embodiment describes a specific implementation of the second RoCE-level PFS, which can be an IP six-tuple or an IP seven-tuple. For example, the IP six-tuple or IP seven-tuple includes information such as IP address, port number, QPN, and protocol type. The protocol type in the IP six-tuple or IP seven-tuple includes RDMA protocol types such as RoCEv2, which facilitates QoS control of data in the RDMA session by network devices based on PFS information and QoS policies. Optionally, the software protocol stack of the second RoCE-level session differs from that of the first RoCE-level session, primarily in the network layer protocol stack; therefore, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple.

[0068] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0069] In this implementation, the PFS information is related to the service type of the IB transport layer message; for example, the first indication information in the PFS information can indicate that the service type of the IB transport layer message is RDMA connection service or RDMA data packet service, which is beneficial for devices in the network to perform QoS control on the data in the RDMA session based on the PFS information and QoS policy.

[0070] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0071] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0072] In the above embodiments, when the first indication information indicates that the IB transport layer message is of a different service type, the corresponding PFS information also includes different content.

[0073] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0074] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0075] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0076] The above embodiments describe the specific implementation of the first indication information. For example, the first indication can be represented by 8 bits, and the first indication information can represent different meanings when the values ​​of each bit are different.

[0077] Fifthly, this application provides a communication device. This communication device is a first network element (such as an SMF), or a component of the first network element (e.g., a processor, chip, or chip system), or a device compatible with the first network element. In one possible implementation, the communication device has the functions described in the first aspect. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0078] In one possible implementation, the communication device includes a communication unit and a processing unit. The processing unit is used to determine PFS information based on the PDU session type requested by the terminal. The PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. The communication unit is used to send the PFS information.

[0079] In this embodiment, the communication device can design relevant PFS information based on the PDU session type requested by the terminal. This PFS information can be designed separately for different PDU session types; for example, an IB-level PFS can be designed for an IB session; a first RoCE-level PFS can be designed for a first RoCE session; or a second RoCE-level PFS can be designed for a second RoCE session. Furthermore, the first network element can send this PFS information to devices in the network (such as terminals, base stations, UPFs, etc.), which facilitates QoS control by devices in the network based on this PFS information.

[0080] Optionally, other possible implementations of the fifth aspect can be referred to the descriptions of other possible implementations of the first aspect, which will not be repeated here.

[0081] Sixthly, this application provides a communication device. This communication device is a terminal, a component of a terminal (e.g., a processor, chip, or chip system), or a device compatible with a terminal. In one possible implementation, the communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0082] In one possible implementation, the communication device includes a communication unit and a processing unit. The communication unit receives PFS information related to the PDU session type requested by the terminal. The PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session. The PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. The processing unit performs quality of service control on uplink data packets based on the PFS information.

[0083] In this embodiment, the communication device can receive PFS information to obtain IB-level PFS, first RoCE-level PFS, or second RoCE-level PFS, and thus perform QoS control based on the PFS information.

[0084] Optionally, other possible implementations of the sixth aspect can be referred to the descriptions of other possible implementations of the second aspect, which will not be repeated here.

[0085] Seventhly, this application provides a communication device. This communication device is an access network device, or a component of an access network device (e.g., a processor, chip, or chip system), or a device compatible with an access network device. In one possible implementation, the communication device has the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0086] In one possible implementation, the communication device includes a communication unit and a processing unit. The communication unit receives PFS information related to a PDU session type requested by a terminal. The PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session. The PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. The processing unit performs quality of service control based on the PFS information.

[0087] In this embodiment, the communication device can receive PFS information to obtain IB-level PFS, first RoCE-level PFS, or second RoCE-level PFS, and thus perform QoS control based on the PFS information; for example, the communication device can map RDMA service flows to the corresponding QoS flows or DRBs.

[0088] Optionally, other possible implementations of the seventh aspect can be referred to the descriptions of other possible implementations of the third aspect, which will not be repeated here.

[0089] Eighthly, this application provides a communication device. This communication device is a second network element (such as a UPF / TPF / CE), or a component of a second network element (such as a processor, chip, or chip system), or a device capable of being used in conjunction with a second network element. In one possible implementation, the communication device has the functions described in the fourth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fourth aspect above. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0090] In one possible implementation, the communication device includes a communication unit and a processing unit. The communication unit receives PFS information related to a PDU session type requested by a terminal. The PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session. The PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. The processing unit performs quality of service control based on the PFS information.

[0091] In this embodiment, the communication device can receive PFS information to obtain IB-level PFS, first RoCE-level PFS, or second RoCE-level PFS, and thus perform QoS control based on the PFS information; for example, the communication device performs uplink QoS flow ID (QFI) verification, or downlink QFI marking and control, etc.

[0092] Optionally, other possible implementations of the eighth aspect can be found in the descriptions of other possible implementations of the fourth aspect, which will not be repeated here.

[0093] Ninthly, this application provides a communication device, including: a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices and transmit them to the processor or send signals from the processor to other communication devices, the processor being configured to implement at least one of the following through logic circuits or executing code instructions: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect.

[0094] Tenthly, this application provides a communication device including a memory and one or more processors. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in at least one of the first, second, third, or fourth aspects. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to perform at least one of the following: the method of the first aspect and any possible implementation of the first aspect; the method of the second aspect and any possible implementation of the second aspect; the method of the third aspect and any possible implementation of the third aspect; and the method of the fourth aspect and any possible implementation of the fourth aspect. Optionally, the memory and processor are decoupled.

[0095] In one possible design, the communication device may also include interface circuitry, wherein the processor is used to communicate with other devices or components via the interface circuitry.

[0096] In one possible design, the communication device may also include a memory.

[0097] In one aspect, this application provides a communication system comprising at least one of the means or apparatuses of the fifth to tenth aspects, such that the at least one means or apparatus performs at least one of the following: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect.

[0098] In a twelfth aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform at least one of the following: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect.

[0099] In a thirteenth aspect, this application provides a computer program product including instructions that, when executed on a computer, cause the computer to perform at least one of the following: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect.

[0100] In a fourteenth aspect, this application provides a chip including a processor (or logic circuit). Optionally, the chip may further include a communication interface (or interface) for implementing at least one of the following: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect. In one possible implementation, if the chip is the smallest processing unit in a complete machine, the chip may be a processor, or may include a processor and a memory, or may include a processor, a memory, and a transceiver for implementing at least one of the following: the method of the first aspect and any possible implementation of the first aspect, the method of the second aspect and any possible implementation of the second aspect, the method of the third aspect and any possible implementation of the third aspect, and the method of the fourth aspect and any possible implementation of the fourth aspect.

[0101] In a fifteenth aspect, this application provides a chip system. The chip system includes a processor and an interface. Optionally, it may also include memory for implementing at least one of the following: the method of the first aspect and any possible implementation of the first aspect; the method of the second aspect and any possible implementation of the second aspect; the method of the third aspect and any possible implementation of the third aspect; and the method of the fourth aspect and any possible implementation of the fourth aspect. The chip system may be composed of a chip or may include chips and other discrete devices. Attached Figure Description

[0102] Figure 1 shows a network architecture provided in this application;

[0103] Figure 2 is a schematic diagram of the RDMA protocol stack;

[0104] Figure 3 is a flowchart illustrating an information transmission method provided in this application;

[0105] Figure 4 is a flowchart illustrating another information transmission method provided in this application;

[0106] Figure 5 is a schematic diagram of a communication device provided in this application;

[0107] Figure 6 is a schematic diagram of another communication device provided in this application. Detailed Implementation

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

[0109] For ease of understanding, the definitions of relevant terms used in this application are provided below:

[0110] Network Architecture: For example, the information transmission method provided in this application can be applied to the network architecture shown in Figure 1. The network architecture shown in Figure 1 includes an access network portion and a core network portion. The access network portion may include, but is not limited to, terminals and access network devices. The core network portion may include one or more functional network elements, such as AMF / SMF / UPF / TPF / CE / policy control function (PCF) / unified data management (UDM), etc. Optionally, Figure 1 is only an example, and the network architecture may also include other functional network elements or devices; this application does not limit this. Optionally, the network architecture shown in Figure 1 also includes a data network (DN), and the core network can be connected to the DN through the UPF.

[0111] The information transmission method provided in this application can be applied to mobile communication systems. For example, the mobile communication system can be a fourth-generation (4G) communication system (e.g., a long-term evolution (LTE) system), a worldwide interoperability for microwave access (WiMAX) communication system, a wireless local area network (WLAN), a fifth-generation (5G) communication system (e.g., a new radio (NR) system), and future mobile communication systems, etc.; it can also be applied to narrowband Internet of Things (NB-IoT) systems, satellite communication systems, high altitude platform station (HAPS) communication, UAVs and other NTN systems, such as integrated communication and navigation (IcaN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit satellite communication systems, etc.

[0112] Access network equipment is a device with wireless transceiver capabilities used to communicate with terminal devices. For example, access network equipment is a radio access network (RAN) node that connects terminal devices to a wireless network. In this application, access network equipment may include, but is not limited to: evolved node B (eNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission reception point (TRP) in a wireless fidelity (WIFI) system. This access network equipment can also be a gNB, TRP, or TP in a 5G system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network controlled repeater (NCR), or an integrated access and backhaul (IAB) node. Furthermore, this access network equipment can also be a network node constituting a gNB or TP, such as a BBU, or a distributed unit (DU). Alternatively, the access network device can also be a device that performs network-side functions in a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, or other communication systems, such as a satellite.

[0113] In this context, a terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from access network devices. The term "terminal" as used in this application includes various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, specifically referring to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. Terminal devices can also be satellite phones, cellular phones, smartphones, wireless data cards, wireless modems, machine-type communication devices, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices or wearable devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine or remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, terminal devices in 5G networks or future communication networks, etc.

[0114] Access network devices and terminals can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network devices and terminals.

[0115] RDMA technology: RDMA technology can directly access memory data through the network interface (without requiring data to be moved from the CPU to the kernel and then from the kernel to the network card), without the intervention of the operating system kernel (the RDMA network card directly reads application (APP) data from memory, without CPU intervention for data movement), thus allowing high-throughput, low-latency network communication, especially suitable for use in large-scale parallel computer clusters. When the speed is as high as 40Gbps, traditional TCP / IP transmission methods result in CPU utilization of up to 100%; while using an RDMA network card, CPU utilization is only 5%.

[0116] As RDMA technology evolves, so too does the RDMA protocol stack. For example, Figure 2 shows a schematic diagram of the RDMA protocol stack. The RDMA protocol stack includes the InfiniBand protocol, the RoCE protocol, and the iWARP protocol. This application mainly relates to the InfiniBand and RoCE protocols; therefore, Figure 2 only shows the protocol stacks for the InfiniBand and RoCE protocols.

[0117] InfiniBand is an RDMA technology based on the InfiniBand architecture. It provides a channel-based point-to-point message queue forwarding model, allowing each application to directly obtain application data messages through a created virtual channel without the intervention of other operating systems and protocol stacks. The application layer of the InfiniBand architecture uses RDMA technology, providing RDMA read and write access between remote nodes and completely offloading the CPU workload; high-bandwidth transmission is used for network transmission; and a specific retransmission mechanism is set up at the link layer to ensure service quality without the need for data buffering.

[0118] The RoCE protocol has two versions: RoCE v1 and RoCE v2. RoCE v1 is based on Ethernet carrying RDMA and is deployed in Layer 2 networks. Its message structure adds a Layer 2 Ethernet header to the existing IB architecture message, identifying RoCE messages using Ethertype 0x8915. RoCE v2 is based on User Datagram Protocol (UDP) / Internet Protocol (IP) carrying RDMA and can be deployed in Layer 3 networks. Its message structure adds a UDP header, an IP header, and a Layer 2 Ethernet header to the existing IB architecture message, identifying RoCE messages using the UDP destination port number 4791.

[0119] The basic communication unit of RDMA is the queue pair (QP), and there are many communication models based on QP, also known as RDMA service types. The IB protocol describes a service type through two dimensions: reliability and connectivity. Reliability in communication refers to ensuring that all sent data packets are received correctly through mechanisms. In other words, a reliable service guarantees that information is transmitted at most once between the sender and receiver, and that it is received completely in the order it was sent. RDMA can guarantee reliability through three mechanisms:

[0120] (1) Acknowledgment Mechanism: Suppose A sends a data packet to B, and B replies with a "received" message to A to indicate that B has correctly received the data packet. This reply is called an acknowledgment packet or an acknowledgement (ACK) message. In the reliable service type of the IB protocol, the acknowledgment mechanism is used to ensure that data packets are received by the other party. In the reliable service type of IB, the receiver does not have to reply for every packet; it can also reply with ACKs for multiple packets at once.

[0121] (2) Data verification mechanism: The data sender can use a certain algorithm to obtain a checksum for the header and payload (i.e., the actual data to be sent and received), and place this checksum at the end of the data packet. After receiving the data packet, the data receiver can use the same algorithm to calculate the checksum and then compare it with the checksum in the data packet; if the checksums do not match, it means that the data contains erroneous data (usually caused by a link problem), and the data receiver can discard the erroneous data packet.

[0122] (3) Order Preservation Mechanism: This ensures that the data receiver receives the data packets that were first sent to the physical link, and then receives the data packets that were sent later. For example, the IB protocol has the concept of a packet sequence number (PSN), where each packet has an incrementing number. The PSN can be used to detect packet loss; for example, if the data receiver receives PSN 1 but receives PSN 3 before receiving PSN 2, it indicates that an error occurred during data transmission. The data receiver can then send a non-ACK (NACK) message to the data sender to retransmit the lost data packets.

[0123] In communications, a connection is an abstract logical concept, distinct from a physical connection. A connection is a communication "pipeline"; once established, data sent from one end can travel along the pipeline to the other. A datagram, on the other hand, is the opposite of a connection. There is no connection (pipeline) between the data sender and receiver. As long as the data sender and receiver are physically reachable, the data sender can send data from any path to any data receiver. Through combinations of reliable / unreliable and connection / datagram, RDMA can support four different types of services: reliable connection (RC), unreliable connection (UC), reliable datagram (RD), and unreliable datagram (UD). This application categorizes RDMA service types into RDMA connection service or RDMA datagram service. Specifically, RDMA connection service includes RC and UC services, while RDMA datagram service includes RD and UD services.

[0124] The basic message of the RDMA transport layer (IB transport layer) includes several fields, such as OpCode and QP indicator field. OpCode indicates the service type of the IB transport layer message. For example, OpCode uses 8 bits, where the high 3 bits are 000 for RC service type, 001 for UC service type, 010 for RD service type, and 011 for UD service type. The QP indicator field is 24 bits in size, and the QP number ranges from 0 to 2. 24 -1.

[0125] RDMA messages consist of multiple parts, such as the RDMA link layer header (local routing header, LRH), the RDMA network layer header (global routing header, GRH), the RDMA base transport header (BTH), and the RDMA extended transport header (ETH). There are several different types of ETH, such as RDETH (reliable DETH), DETH, and RETH (RDMA ETH), etc. This application primarily concerns DETH.

[0126] QoS policy generation and distribution: Before initiating an application session for service data transmission, the application function (AF) provides the PCF with the requirements for application-layer services. If it is a trusted AF, it can provide information directly to the PCF. If it is an untrusted third-party AF, the operator can provide information through the network exposure function (NEF) element. Application-layer service requirements generally include flow description information for SDF inspection. For IP packets, the flow description information can be IP 5-tuple information, including source address, destination address, source port number, destination port number, and protocol type above the IP layer. Application-layer service requirements also include QoS-related requirements, such as bandwidth requirements and service types.

[0127] The PCF (Power Processing Function) obtains information from various Network Functions (NFs) and combines it with pre-configured information to generate policy and charging control (PCC) rules. NFs include the SMF (Software-Defined Function), AMF (Active Network Function), Charging Function (CHF), Network Data Analytics Function (NWDAF), Unified Data Repository (UDR), and AF (Active Network Function). The PCF generates PCC rules, which can then be sent to the SMF. PCC rules are at the SDF (Software-Defined Function) granularity.

[0128] The Service Flow Manager (SFM) combines PCC rules from the PCF, SMF configuration information, and UE registration information obtained from the UDM to bind PCC rules to corresponding QoS flows. A single QoS flow may correspond to multiple PCC rules, and one QoS flow can be used to transmit multiple SDFs with the same QoS requirements. A QoS flow is the smallest granularity for 5G QoS management. A PDU session may contain multiple QoS flows, and QoS flows within the same PDU session are characterized by QFIs. All data within a QoS flow shares the same air interface resource scheduling and guarantees. The SMF can send packet detection rules (PDR) and QoS enforcement rules (QER) to the UPF. The UPF identifies SDFs based on this information and assigns them to the QoS flows of the specified QFIs. The SMF can also send a QoS profile to the 5G-AN. Based on the QoS profile, the 5G-AN maps QoS flows to DRBs at the Service Data Adaptation Protocol (SDAP) layer. SMF can send QoS rules to UE. Based on the QoS rules, the UE can identify the SDF, determine the QoS flow QFI corresponding to the SDF, and complete the mapping between the QoS flow and the air interface DRB. Therefore, how to design RDMA-related PFS in wireless RDMA scenarios to support RDMA packet identification and further perform QoS control is an issue to be solved.

[0129] To address the aforementioned issues, this application provides an information transmission method that incorporates a PFS (Programmable Frame Filter) information, which facilitates QoS control for network devices (such as terminals, base stations, and UPFs).

[0130] For example, Figure 3 is a flowchart of an information transmission method provided in this application. The method is executed by a first network element and includes the following steps:

[0131] S101, the first network element determines the PFS information based on the PDU session type requested by the terminal.

[0132] The PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, and second RoCE session. Correspondingly, the PFS determined by the first network element based on the PDU session type requested by the terminal includes at least one of the following: IB-level PFS, first RoCE-level PFS, and second RoCE-level PFS. For example, when the PDU session type requested by the terminal is an IB session, the first network element can determine the IB-level PFS (infiniband PFS) for that IB session; when the PDU session type requested by the terminal is a first RoCE session (RoCE v1 session), the first network element can determine the first RoCE-level PFS (RoCE v1 PFS) for that first RoCE session; when the PDU session type requested by the terminal is a second RoCE session (RoCE v2 session), the first network element can determine the second RoCE-level PFS (RoCE v2 PFS) for that second RoCE session.

[0133] Optionally, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes source GID, destination GID, destination QPN, source QPN, and protocol type. For example, source / destination GID represents the source / destination address of the IB session, and source / destination QPN represents the source / destination QP information of the IB session. Another example is that the protocol type in the IB quadruple or IB quintuple includes RMDA protocol types such as IB / RoCEv1. It is understood that the difference between the IB quadruple and IB quintuple lies in whether or not a source QPN is included. Optionally, the IB-level PFS also includes PFS direction information; for example, PFS direction includes uplink or downlink, indicating that the IB session or RoCE v1 session is an uplink or downlink service. Optionally, the IB protocol type and the RoCEv1 protocol type PFS are the same; for example, both the IB protocol type and the RoCEv1 protocol type include the IB network layer and the IB transport layer.

[0134] Optionally, the IB 5-tuple or IB 4-tuple is associated with the service type of the IB transport layer message. For example, if the service type of the IB transport layer message includes RDMA connection service or RDMA data packet service, then the IB 5-tuple or IB 4-tuple can be associated with different service types of IB transport layer messages. Optionally, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes the IB 4-tuple; for example, when the service type of the IB transport layer message is RDMA connection service, it indicates that the current IB session has established a connection, then the IB-level PFS may not include the source QPN (if the connection has been established, there is no need to indicate the source QPN, only the destination QPN). Optionally, when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes the IB 5-tuple; for example, when the service type of the IB transport layer message is RDMA data packet service, it indicates that the current IB session uses connectionless data packet transmission, then the IB-level PFS includes both the source QPN and the destination QPN.

[0135] Optionally, the second RoCE level PFS includes an IP six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type. For example, according to the description in Figure 2's RDMA protocol stack, the network layer of the RoCE v2 protocol stack uses the UDP / IP protocol, then the second RoCE level PFS includes an IP six-tuple or an IP seven-tuple; where the source / destination IP represents the source / destination IP address of the RoCE v2 session, the source / destination port number represents the source / destination medium access control (MAC) address of the RoCE v2 session, and the source / destination QPN represents the source / destination QP information of the RoCE v2 session. As another example, the protocol type in the IP six-tuple or IP seven-tuple includes RoCE v2 and other RDMA protocol types. It is understandable that the difference between the IP six-tuple and the IP seven-tuple lies in whether or not the source QPN is included. Optionally, the second RoCE level PFS also includes PFS direction information; for example, the PFS direction includes uplink or downlink, indicating that the RoCE v2 session is an uplink or downlink service. Optionally, the destination port number of RoCE v2 can be a fixed value, for example, the destination port number is 4791, then the first network element can inform the intermediate device or the destination end of the RDMA transport layer protocol used by the specified port number. Optionally, the RoCEv2 protocol type is different from the IB protocol type or the RoCEv1 protocol type, for example, the RoCEv2 protocol type uses UDP / IP on the network side and the IB protocol on the transport layer.

[0136] Optionally, the IP 6-tuple or IP 7-tuple is associated with the service type of the IB transport layer message. For example, if the service type of the IB transport layer message includes RDMA connection service or RDMA datagram service, then the IP 6-tuple or IP 7-tuple can be associated with different service types of IB transport layer messages. Optionally, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes the IP 6-tuple; for example, when the service type of the IB transport layer message is RDMA connection service, it indicates that the current RoCE v2 session has established a connection, then the RoCE v2 level PFS may not include the source QPN (if the connection has been established, there is no need to indicate the source QPN, only the destination QPN). Optionally, when the first indication information indicates RDMA datagram service, the second RoCE level PFS includes the IP 7-tuple; for example, when the service type of the IB transport layer message is RDMA datagram service, it indicates that the current RoCE v2 session uses connectionless datagram transmission, then the RoCE v2 level PFS includes both the source QPN and the destination QPN.

[0137] Optionally, the PFS information includes an IB transport layer message, the header of which includes first indication information used to indicate the service type of the IB transport layer message. The service type of the IB transport layer message includes RDMA connection service or RDMA data packet service. For example, as described above, an RDMA message includes multiple parts, such as an RDMA transport layer basic header and an RDMA transport layer extended header; and according to the description of the RDMA protocol stack in Figure 2, the RDMA transport layer is also the IB transport layer. Therefore, the PFS information includes the IB transport layer message (RDMA transport layer), and the IB transport layer message header (RDMA transport layer message header) includes the first indication information used to indicate the service type of the IB transport layer message (RDMA transport layer message). As described above, RDMA connection services include RC services and UC services, and RDMA data packet services include RD services and UD services; therefore, the service types of IB transport layer messages also include RDMA connection services (such as RC services and UC services) and RDMA data packet services (such as RD services and UD services).

[0138] Optionally, the IB transport layer message header includes first indication information. For example, the IB transport layer message header includes an OpCode, which is used to indicate the service type of the IB transport layer message. The OpCode is represented by 8 bits, and the first indication information can also be represented by 8 bits (that is, the first indication information includes 8 bits), which is used to indicate the service type of the IB transport layer message.

[0139] Optionally, when the high 3 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service. For example, the OpCode is represented by 8 bits, where the high 3 bits are 000 to indicate RC service type and 001 to indicate UC service type; similarly, the high 3 bits of the first indication information are 000 to indicate RC service type and 001 to indicate UC service type.

[0140] Optionally, when the high 3 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data message service. For example, if the OpCode is represented by 8 bits, a high 3 bit value of 010 indicates RD service type, and a high 3 bit value of 011 indicates UD service type; similarly, a high 3 bit value of 010 in the first indication information indicates RD service type, and a high 3 bit value of 011 indicates UD service type.

[0141] Optionally, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH; DETH includes the source QPN. For example, when the service type of an IB transport layer message is RDMA data packet service, the IB transport layer message includes a DETH extension header, and the DETH extension header includes the source QPN, thereby indicating the source QPN.

[0142] Optionally, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information satisfy the values ​​00000 to 01100, and / or satisfy the values ​​10011 to 10101. For example, when the high 3 bits of the first indication information are 010, it indicates that the service type of the IB transport layer message is RD service type; according to the description in the protocol standard, when the low 5 bits of the 8 bits satisfy the values ​​00000 to 01100 and / or satisfy the values ​​10011 to 10101, it indicates that the IB transport layer message includes a DETH extension header, and the DETH extension header includes the source QPN.

[0143] S102, the first network element sends PFS information.

[0144] For example, the first network element can send PFS information to other devices in the network (such as terminals, base stations, other functional network elements, etc.), which is beneficial for other devices in the network to perform quality of service control based on the PFS information.

[0145] Optionally, the PFS information is sent from the first network element to the second network element; the second network element is a UPF, TPF, or CE. For example, the first network element can send PFS information to the second network element; such as sending PFS information to the UPF, the TPF, or the CE. Correspondingly, the second network element receives the PFS information.

[0146] Optionally, the PFS information is sent by the first network element to the access network device or terminal via the AMF. For example, the first network element can send PFS information to the RAN, specifically by sending the PFS information to the RAN via the AMF; or, for another example, the first network element can send PFS information to the UE, specifically by sending the PFS information to the UE via the AMF.

[0147] In this embodiment, the first network element can design relevant PFS information based on the PDU session type requested by the terminal. This PFS information can be RDMA PFS, which is beneficial for devices in the network to identify RDMA packets in the PDU session based on RDMA PFS, thereby realizing differentiated QoS control.

[0148] The method provided in this application will be further described below in conjunction with multiple devices in the network and the QoS policy generation process. For example, Figure 4 is a flowchart of another information transmission method provided in this application. This method is implemented through the interaction between the first network element (SMF), AMF, the second network element (UPF / TPF / CE), access network equipment, and the terminal, and includes the following steps:

[0149] S201, the first network element determines the QoS policy.

[0150] For example, the SMF can send a first request message to the UDM to request subscribed QoS information. After obtaining the subscribed QoS information, the SMF can send a second request message to the PCF to request authorized PCC rule information; this second request message may carry the subscribed QoS information obtained from the UDM. After obtaining the PCC rule information, the SMF can generate corresponding QoS policies based on the PCC rule information; for example, the SMF can create a new QoS flow or modify the attributes of an existing QoS flow.

[0151] S202, the first network element determines the PFS information based on the PDU session type requested by the terminal.

[0152] For example, for an IB session, an IB-level PFS is designed; or for the first RoCE session, a first RoCE-level PFS is designed; or for the second RoCE session, a second RoCE-level PFS is designed. The specific implementation of S202 can be found in the corresponding description in S101, such as the description of IB-level PFS, first RoCE-level PFS, second RoCE-level PFS, IB transport layer messages, etc., which will not be repeated here.

[0153] S203a, the first network element sends QoS policy.

[0154] For example, the first network element can send a QoS policy to the UPF; or the first network element can send a QoS policy to the access network device; or the first network element can send a QoS policy to the terminal. Optionally, when the first network element sends a QoS policy to the access network device or terminal, it can specifically send (e.g., transparently transmit) the QoS policy to the access network device or terminal through the AMF.

[0155] S203b, the first network element sends PFS information.

[0156] For example, the first network element can send PFS information to the second network element, or to the access network device, or to the terminal. For specific implementation details, please refer to the corresponding description in S102, which will not be repeated here.

[0157] Optionally, the execution order of S203a and S203b is not limited in this application. For example, S203a can be executed first and then S203b, or S203b can be executed first and then S203a, or both S203a and S203b can be executed simultaneously. Optionally, if S203a and S203b are executed simultaneously, the specific implementation method can be:

[0158] The first network element can send QoS policies and PFS information to the second network element. For example, the SMF sends a PDR to the UPF / TPF / CE, which includes SDFs, etc.; the SDF includes a QoS rule ID, QoS rule priority, PFS information, etc. Among them, the QoS rule is used to complete the SDF identification and determine the QFI of the QoS flow corresponding to the SDF.

[0159] The first network element can send QoS policies and PFS information to the access network device. For example, the SMF sends a QoS profile to the access network device. The QoS profile includes rate information for guaranteed bit rate (GBR) QoS flow, QoS information for non-GBR QoS flow, and PFS information.

[0160] The first network element can send QoS policies and PFS information to the terminal. For example, the SMF sends a QoS Rule through the terminal, which includes QoS Rule priority, QFI, QoS Rule ID, PFS information, etc. The QoS Rule can also be pre-configured by the terminal; in this case, the SMF sends PFS information separately.

[0161] S204a, the terminal performs quality of service control on uplink data packets based on PFS information.

[0162] For example, based on QoS policies and PFS information, the terminal can determine the corresponding QoS Rule and perform QoS control on uplink data packets based on the QoS Rule.

[0163] S204b: Access network devices perform quality of service control based on PFS information.

[0164] For example, based on QoS policies and PFS information, access network devices can determine the corresponding QoS profile, thereby establishing a DRB and mapping service flows to the corresponding QoS Flow / DRB based on QoS policies, thus providing the corresponding quality of service.

[0165] S204c, the second network element performs quality of service control based on PFS information.

[0166] For example, based on QoS policies and PFS information, access network devices can perform uplink QFI authentication or downlink QFI marking and control operations.

[0167] In this embodiment, the first network element and the devices in the network can interact with QoS policies and PFS information, thereby enabling QoS control of data in the RDMA session based on RDMA packet detection rules.

[0168] It is understood that, in order to achieve the functions described in the above embodiments of the device, the base station and the terminal include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0169] Figures 5 and 6 are schematic diagrams of the communication devices provided in this application. These communication devices can be used to implement the functions of the first network element, terminal, access network device, or second network element in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0170] As shown in Figure 5, the communication device 500 includes a processing unit 510 and a transceiver unit 520. The communication device 500 is used to implement the functions of the first network element, terminal, access network device, or second network element in the method embodiments shown in Figures 3 and 4. Optionally, the transceiver unit 520 includes a sending unit and a receiving unit; the transceiver unit 520 can also be referred to as a communication unit.

[0171] When the communication device 500 is used to implement the function of the first network element in the method embodiments shown in Figures 3 and 4: the processing unit 510 is used to determine PFS information based on the PDU session type requested by the terminal; wherein, the PDU session type requested by the terminal includes at least one of the following: infinite bandwidth (IB) session, first remote direct memory access over converged Ethernet (RDMA over converged Ethernet, RoCE) session, and second RoCE session; the PFS information includes at least one of the following: IB level PFS, first RoCE level PFS, and second RoCE level PFS. The transceiver unit 520 is used to send the PFS information.

[0172] In one possible implementation, the transceiver unit 520 is used to receive a QoS policy, which is at the SDF granularity, the SDF being associated with RDMA messages, and the SDF being associated with PFS information. The transceiver unit 520 is also used to transmit the QoS policy.

[0173] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0174] In one possible implementation, the second RoCE level PFS includes an Internet protocol (IP) six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0175] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0176] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0177] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0178] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0179] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0180] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0181] In one possible implementation, the PFS information is sent from the first network element to the second network element; the second network element is either a UPF, a TPF, or a CE.

[0182] In one possible implementation, the PFS information is sent by the first network element to the access network device or terminal via AMF.

[0183] As can be seen, when the communication device 500 is used to implement the function of the first network element in the method embodiment shown in Figures 3 and 4, the communication device 500 can design relevant PFS information based on the PDU session type requested by the terminal. The PFS information can be the PFS of RDMA, which is beneficial for devices in the network to identify RDMA messages in the PDU session based on the PFS of RDMA, thereby realizing differentiated QoS control.

[0184] When the communication device 500 is used to implement the terminal functions in the method embodiments shown in Figures 3 and 4: the transceiver unit 520 is used for the terminal to receive PFS information; the PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, second RoCE-level PFS. The processing unit 510 is used to perform quality of service control of uplink data packets based on the PFS information.

[0185] In one possible implementation, the transceiver unit 520 is used to receive a QoS policy, which is related to RDMA messages and PFS information.

[0186] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0187] In one possible implementation, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0188] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0189] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0190] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0191] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0192] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0193] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0194] As can be seen, when the communication device 500 is used to implement the terminal function in the method embodiment shown in Figures 3 and 4, the communication device 500 can receive PFS information, which can be RDMA PFS, which is beneficial for the terminal to identify RDMA messages in the PDU session based on RDMA PFS, thereby realizing QoS control.

[0195] When the communication device 500 is used to implement the functions of the access network device in the method embodiments shown in Figures 3 and 4: the transceiver unit 520 is used to receive PFS information; the PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, second RoCE-level PFS. The processing unit 510 is used to perform quality of service control based on the PFS information.

[0196] In one possible implementation, the transceiver unit 520 is used to receive a QoS policy, which is related to RDMA messages and PFS information.

[0197] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0198] In one possible implementation, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0199] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0200] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0201] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0202] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0203] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0204] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0205] As can be seen, when the communication device 500 is used to implement the function of the access network device in the method embodiment shown in Figures 3 and 4, the communication device 500 can receive PFS information, which can be the PFS of RDMA. This is beneficial for the access network device to identify RDMA packets in the PDU session based on the PFS of RDMA, thereby performing QoS control. For example, the access network device can map the RDMA service flow to the corresponding QoS flow or DRB.

[0206] When the communication device 500 is used to implement the function of the second network element in the method embodiments shown in Figures 3 and 4: the transceiver unit 520 is used to receive PFS information; the PFS information is related to the PDU session type requested by the terminal; the PDU session type requested by the terminal includes at least one of the following: IB session, first RoCE session, second RoCE session; the PFS information includes at least one of the following: IB-level PFS, first RoCE-level PFS, second RoCE-level PFS. The processing unit 510 is used to perform quality of service control based on the PFS information.

[0207] In one possible implementation, the transceiver unit 520 is used to receive a QoS policy, which is related to RDMA messages and PFS information.

[0208] In one possible implementation, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple or an IB quintuple. The IB quadruple includes the source GID, destination GID, destination QPN, and protocol type; the IB quintuple includes the source GID, destination GID, destination QPN, source QPN, and protocol type.

[0209] In one possible implementation, the second RoCE-level PFS includes an IP six-tuple or an IP seven-tuple. The IP six-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, and protocol type; the IP seven-tuple includes source IP, destination IP, source port number, destination port number, destination QPN, source QPN, and protocol type.

[0210] In one possible implementation, the PFS information includes an IB transport layer message, the header of which includes first indication information for indicating the service type of the IB transport layer message, which may include RDMA connection service or RDMA data packet service.

[0211] In one possible implementation, when the first indication information indicates RDMA connection service, the IB-level PFS or the first RoCE-level PFS includes an IB quadruple; when the first indication information indicates RDMA data packet service, the IB-level PFS or the first RoCE-level PFS includes an IB quintuple.

[0212] In one possible implementation, when the first indication information indicates RDMA connection service, the second RoCE level PFS includes an IP six-tuple; when the first indication information indicates RDMA data packet service, the second RoCE level PFS includes an IP seven-tuple.

[0213] In one possible implementation, the first indication information includes 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates RDMA connection service; or, when the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates RDMA data packet service.

[0214] In one possible implementation, when the first indication information indicates RDMA data packet service, the first indication information further includes DETH, where DETH includes the source QPN.

[0215] In one possible implementation, when the high 3 bits of the first indication information are 010, the low 5 bits of the first indication information are 00000 to 01100, and / or 10011 to 10101.

[0216] As can be seen, when the communication device 500 is used to implement the function of the second network element in the method embodiment shown in Figures 3 and 4, the communication device 500 can receive PFS information. The PFS information can be the PFS of RDMA, which is beneficial for the access network device to identify the RDMA message in the PDU session based on the PFS of RDMA, thereby realizing QoS control; for example, performing uplink QFI verification, or performing downlink QFI marking and control, etc.

[0217] Optionally, a more detailed description of the above-mentioned processing unit 510 and transceiver unit 520 can be found in the relevant descriptions in the method embodiments shown in Figures 3 and 4.

[0218] As shown in Figure 6, the communication device 600 includes a processor 610 and an interface circuit 620. The processor 610 and the interface circuit 620 are coupled to each other. It is understood that the interface circuit 620 can be a transceiver or an input / output interface. Optionally, the communication device 600 may also include a memory 630 for storing instructions executed by the processor 610, or storing input data required for the processor 610 to execute instructions, or storing data generated after the processor 610 executes instructions. Sometimes, the interface circuit 620 can also be understood as part of the processor 610, in which case the communication device 600 includes the processor 610. Optionally, the transceiver includes a transmitter and a receiver.

[0219] When the communication device 600 is used to implement the method embodiments shown in FIG3 and FIG4, the processor 610 is used to implement the functions of the processing unit 510, and the interface circuit 620 is used to implement the functions of the transceiver unit 520.

[0220] A transceiver provides a communication interface or means for communicating with various other devices via a wireless transmission medium. The transceiver may be coupled to an antenna array, and the transceiver and antenna array may be used together for communication with a corresponding network type. At least one interface (e.g., a network interface and / or a user interface) provides a communication interface or means for communication via an internal bus or via an external transmission medium.

[0221] The processor is responsible for managing the bus and general processing, including executing software stored on a computer-readable medium. When executed by the processor, the software causes the processing system to perform the various functions described below for any particular device. Functions that can be implemented by the processor, memory, and computer-readable medium may include: encoding, decoding, rate matching, rate dematching, scrambling, descrambling, modulation, demodulation, layer mapping, fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), inverse discrete Fourier transform (IDFT), precoding, resource element (RE) mapping, channel equalization, RE demapping, digital beamforming (BF), adding CP, removing CP, and so on.

[0222] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0223] In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, wiring, or interfaces.

[0224] It is understandable that information may undergo necessary processing, such as encoding and modulation, between the source and destination, but the destination can understand the valid information from the source. Similar statements in this application can be interpreted in a similar way and will not be elaborated further.

[0225] This application also provides a communication system, which includes one or more of the following: a first network element, a terminal, an access network device, or a second network element. The first network element is used to perform all or part of the steps performed by the first network element in the preceding embodiments. The second network element is used to perform all or part of the steps performed by the second network element in the preceding embodiments. The terminal is used to perform all or part of the steps performed by the terminal in the preceding embodiments. The access network device is used to perform all or part of the steps performed by the access network device in the preceding embodiments.

[0226] This application provides a computer-readable storage medium. The computer-readable storage medium stores a program or instructions. When the program or instructions are executed on a computer, the computer performs the information reporting method shown in the embodiments of FIG3 and FIG4.

[0227] This application provides a computer program product. The computer program product includes instructions. When the instructions are executed on a computer, the computer performs the information reporting method shown in the embodiments of FIG3 and FIG4.

[0228] This application provides a chip or chip system including at least one processor and an interface, the interface and at least one processor being interconnected via a circuit, the at least one processor being used to run computer programs or instructions to perform the information reporting method shown in the embodiments of FIG3 and FIG4.

[0229] The interfaces in the chip can be input / output interfaces, pins, or circuits, etc.

[0230] The aforementioned chip system can be a System-on-a-Chip (SoC) or a baseband chip, etc. The baseband chip can include a processor, channel encoder, digital signal processor, modem, and interface module, etc.

[0231] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).

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

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

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

[0235] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0236] In this application, terms such as "first" and "second" may be used to distinguish technical features that are functionally identical or similar. These terms do not limit the number or execution order, nor do they imply that they are necessarily different. In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or design solutions. The use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

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

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

Claims

1. A method of information transmission, characterized in that, The method comprises: The first network element determines a packet filter set (PFS) information based on a protocol data unit (PDU) session type requested by a terminal; The PDU session type requested by the terminal comprises at least one of the following: an infinite bandwidth (IB) session, a first remote direct memory access over converged Ethernet (RoCE) session, and a second RoCE session; The PFS information comprises at least one of the following: an IB level PFS, a first RoCE level PFS, and a second RoCE level PFS; The first network element sends the PFS information.

2. The method of claim 1, wherein, The IB level PFS or the first RoCE level PFS comprises an IB four-tuple or an IB five-tuple; The IB four-tuple comprises a source global identifier (GID), a destination GID, a destination queue pair number (QPN), and a protocol type; The IB five-tuple comprises a source GID, a destination GID, a destination QPN, a source QPN, and a protocol type.

3. The method of claim 1, wherein, The second RoCE level PFS comprises an Internet protocol (IP) six-tuple or an IP seven-tuple; The IP six-tuple comprises a source IP, a destination IP, a source port number, a destination port number, a destination QPN, and a protocol type; The IP seven-tuple comprises a source IP, a destination IP, a source port number, a destination port number, a destination QPN, a source QPN, and a protocol type.

4. The method according to claim 2 or 3, characterized in that, The PFS information comprises an IB transport layer message, and a header of the IB transport layer message comprises first indication information, the first indication information being used to indicate a service type of the IB transport layer message, the service type of the IB transport layer message comprising a remote direct memory access (RDMA) connection service or an RDMA data message service.

5. The method of claim 4, wherein, When the first indication information indicates the RDMA connection service, the IB level PFS or the first RoCE level PFS comprises the IB four-tuple; When the first indication information indicates the RDMA data message service, the IB level PFS or the first RoCE level PFS comprises the IB five-tuple.

6. The method of claim 4, wherein, When the first indication information indicates the RDMA connection service, the second RoCE level PFS comprises the IP six-tuple; When the first indication information indicates the RDMA data message service, the second RoCE level PFS comprises the IP seven-tuple.

7. The method according to claim 5 or 6, characterized in that, The first indication information comprises 8 bits; When the upper 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates the RDMA connection service; or When the upper 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates the RDMA data message service.

8. The method of claim 7, wherein, When the first indication information indicates the RDMA data message service, the first indication information further comprises a data extension transport header (DETH), and the DETH comprises the source QPN.

9. The method of claim 7, wherein, When the upper 3 bits of the 8 bits of the first indication information are 010, the lower 5 bits of the 8 bits of the first indication information satisfy 00000-01100 and / or satisfy 10011-10101.

10. The method of claim 1, wherein, The PFS information is sent by the first network element to a second network element; The second network element is a user plane function network element, a data plane function network element, or a compute execution function network element.

11. The method of claim 1, wherein, The PFS information is sent by the first network element to an access network device or a terminal through an access and mobility management network element.

12. An information transmission method characterized by comprising: The method comprises: A terminal receives PFS information; the PFS information is related to a PDU session type requested by the terminal, and the PDU session type requested by the terminal includes at least one of an IB session, a first RoCE session, and a second RoCE session; the PFS information includes at least one of an IB level PFS, a first RoCE level PFS, and a second RoCE level PFS. The terminal performs quality of service control on an uplink data packet based on the PFS information.

13. An information transmission method, characterized by, The method comprises: An access network device receives PFS information; the PFS information is related to a PDU session type requested by a terminal, and the PDU session type requested by the terminal includes at least one of an IB session, a first RoCE session, and a second RoCE session; the PFS information includes at least one of an IB level PFS, a first RoCE level PFS, and a second RoCE level PFS. The access network device performs quality of service control based on the PFS information.

14. An information transmission method, characterized by, The method comprises: A second network element receives PFS information; the PFS information is related to a PDU session type requested by a terminal, and the PDU session type requested by the terminal includes at least one of an IB session, a first RoCE session, and a second RoCE session; the PFS information includes at least one of an IB level PFS, a first RoCE level PFS, and a second RoCE level PFS. The second network element performs quality of service control based on the PFS information.

15. The method according to any one of claims 12 to 14, characterized in that, The IB level PFS or the first RoCE level PFS includes an IB four-tuple or an IB five-tuple; The IB four-tuple includes a source GID, a destination GID, a destination QPN, and a protocol type; The IB five-tuple includes a source GID, a destination GID, a destination QPN, a source QPN, and a protocol type.

16. The method according to any one of claims 12 to 14, characterized in that, The RoCE level PFS includes a network protocol IP six-tuple or an IP seven-tuple; The IP six-tuple includes a source IP, a destination IP, a source port number, a destination port number, a destination QPN, and a protocol type; The IP seven-tuple includes a source IP, a destination IP, a source port number, a destination port number, a destination QPN, a source QPN, and a protocol type.

17. The method according to claim 15 or 16, characterized in that The PFS information includes an IB transport layer message, and a header of the IB transport layer message includes first indication information, the first indication information is used to indicate a service type of the IB transport layer message, and the service type of the IB transport layer message includes an RDMA connection service or an RDMA data message service.

18. The method of claim 17, wherein, When the first indication information indicates the RDMA connection service, the IB level PFS or the first RoCE level PFS includes the IB four-tuple; When the first indication information indicates the RDMA data message service, the IB level PFS or the first RoCE level PFS includes the IB five-tuple.

19. The method of claim 17, wherein, When the first indication information indicates the RDMA connection service, the second RoCE level PFS includes the IP six-tuple; When the first indication information indicates the RDMA datagram service, the second RoCE level PFS comprises the IP seven-tuple.

20. The method of claim 18 or 19, wherein, The first indication information comprises 8 bits. When the high 3 bits of the 8 bits of the first indication information are 000 or 001, the first indication information indicates the RDMA connection service; or When the high 3 bits of the 8 bits of the first indication information are 010 or 011, the first indication information indicates the RDMA datagram service.

21. The method of claim 20, wherein, When the first indication information indicates the RDMA message service, the first indication information further comprises DETH; and the DETH comprises the source QPN.

22. The method of claim 20, wherein, When the high 3 bits of the 8 bits of the first indication information are 010, the low 5 bits of the 8 bits of the first indication information satisfy 00000-01100, and / or satisfy 10011-10101.

23. The method of claim 14, wherein, The second network element is a user plane function network element or a data plane function network element or a computing execution function network element.

24. A communications device, characterized by The apparatus comprises a module or unit for performing the method of any one of claims 1-11; or a module or unit for performing the method of any one of claims 12, 15-23; or a module or unit for performing the method of any one of claims 13, 15-23; or a module or unit for performing the method of any one of claims 14-23.

25. A communications device, characterized by The apparatus comprises a memory for storing a computer program; and one or more processors for executing the computer program in the memory, so that the communication device performs the method of any one of claims 1-11, or the method of any one of claims 12, 15-23, or the method of any one of claims 13, 15-23, or the method of any one of claims 14-23.

26. A communication system, characterized by The communication system comprises the communication device of claim 24 and / or claim 25.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a computer, implement the method of any one of claims 1-11, or the method of any one of claims 12, 15-23, or the method of any one of claims 13, 15-23, or the method of any one of claims 14-23.

28. A computer program product, characterised in that, When the computer reads and executes the computer program product, the computer executes the method of any one of claims 1-11, or the method of any one of claims 12, 15-23, or the method of any one of claims 13, 15-23, or the method of any one of claims 14-23.

29. A chip or chip system, characterized by The apparatus comprises a processor for executing the method of any one of claims 1-11, or the method of any one of claims 12, 15-23, or the method of any one of claims 13, 15-23, or the method of any one of claims 14-23.

Images