QOS processing method and apparatus based on non-3GPP access, readable medium, and device

Abstract

Embodiments of the present application provide a QoS processing method and apparatus based on non-3GPP access, a readable medium, and a device. The QoS processing method is executed by a target network element connected, via non-3GPP access, to a service processing device, and the target network element is connected to a core network. The QoS processing method comprises: receiving QoS configuration information sent by a session management function network element and corresponding to service data packet transmission performed between the service processing device and a service server; and on the basis of the QoS configuration information, performing QoS processing on the service data packet transmission process between the service processing device and the service server. The technical solutions in the embodiments of the present application enable support for a QoS mechanism in a non-3GPP access scenario, thereby ensuring the interoperability and integration of the QoS mechanism between 3GPP networks and non-3GPP networks, and improving the processing flexibility of service data streams while ensuring the QoS requirements thereof.

Description

QoS processing method, device, readable medium and equipment based on non-3GPP access

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 29, 2023, with application number 202311872016.7 and invention name “QoS processing method, device, readable medium and equipment based on non-3GPP access”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of computer and communication technology, and in particular to a QoS processing method, apparatus, readable medium, and device based on non-3GPP access. Background Art

[0003] In the fifth-generation mobile communication technology (5G) and its subsequent evolution systems (such as 5G-A and 6G), high-bandwidth interactive services are important service types, such as cloud gaming, virtual reality (VR), augmented reality (AR), mixed reality (MR), extended reality (XR), cinematic reality (CR), and XR and media services (XRM). These high-bandwidth interactive services have strict requirements for transmission timeliness and, due to the huge data volume, place higher requirements on the control of quality of service (QoS) during the transmission of these service data packets.

[0004] At the same time, the processing equipment for the above-mentioned interactive services is not limited to the Radio Access Technology (RAT) defined by the 3rd Generation Partnership Project (3GPP), but can also support non-3GPP access methods, such as Wireless Fidelity (Wi-Fi). In this case, how to ensure the QoS requirements of these interactive services is a technical problem that needs to be solved urgently. Summary of the Invention

[0005] The embodiments of the present application provide a QoS processing method, apparatus, readable medium, and device based on non-3GPP access, which can implement support for QoS mechanisms in non-3GPP access modes, ensure the interoperability and integration of QoS mechanisms between 3GPP networks and non-3GPP networks, and improve the processing flexibility of service data flows while ensuring the QoS requirements of service data flows.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by practice of the present application.

[0007] In the first aspect, an embodiment of the present application provides a QoS processing method based on non-3GPP access, wherein the QoS processing method is executed by a target network element to which a service processing device is connected through a non-3GPP access method, and the target network element is connected to a core network. The QoS processing method includes: receiving QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server sent by the session management function network element; performing QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information.

[0008] In the second aspect, an embodiment of the present application provides a QoS processing method based on non-3GPP access, which is executed by an application function network element. The QoS processing method includes: generating QoS requirement information for service data packets, which are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access method; sending the QoS requirement information to a policy control function network element so that the policy control function network element generates QoS policy information corresponding to the service data packet based on the QoS requirement information.

[0009] In the third aspect, an embodiment of the present application provides a QoS processing method based on non-3GPP access, which is executed by a policy control function network element. The QoS processing method includes: obtaining QoS requirement information for a service data packet, which is a data packet transmitted between a service server and a service processing device accessed through a non-3GPP access method; generating QoS policy information corresponding to the service data packet based on the QoS requirement information; and sending the QoS policy information to a session management function network element so that the session management function network element configures QoS processing related information to the processing device of the service data packet based on the QoS policy information.

[0010] In a fourth aspect, an embodiment of the present application provides a QoS processing method based on non-3GPP access, which is executed by a session management function network element. The QoS processing method includes: receiving QoS policy information sent by a policy control function network element for processing service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access method; generating QoS processing-related information corresponding to the processing devices of the service data packets according to the QoS policy information; and configuring the QoS processing-related information to the processing devices of the service data packets.

[0011] In some embodiments of the present application, based on the aforementioned solution, generating QoS processing related information corresponding to each type of processing device of the service data packet according to the QoS policy information includes:

[0012] Generate QoS processing related information corresponding to each type of processing device of the service data packet according to the QoS policy information and the access characteristics of the non-3GPP access mode; or

[0013] The same QoS processing related information is generated for the non-3GPP access mode and the wireless access network access mode according to the QoS policy information.

[0014] In the fifth aspect, an embodiment of the present application provides a QoS processing device based on non-3GPP access, wherein the QoS processing device is applied to a target network element to which a service processing device is connected via a non-3GPP access method, and the target network element is connected to a core network. The QoS processing device includes: a receiving unit, configured to receive QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server sent by the session management function network element; and a processing unit, configured to perform QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information.

[0015] In the sixth aspect, an embodiment of the present application provides a QoS processing device based on non-3GPP access, which is applied to an application function network element, and the QoS processing device includes: a generating unit, configured to generate QoS requirement information for a service data packet, and the service data packet is a data packet transmitted between a service server and a service processing device accessed through a non-3GPP access method; a sending unit, configured to send the QoS requirement information to a policy control function network element, so that the policy control function network element generates QoS policy information corresponding to the service data packet based on the QoS requirement information.

[0016] In the seventh aspect, an embodiment of the present application provides a QoS processing device based on non-3GPP access, which is applied to a policy control function network element, and the QoS processing device includes: an acquisition unit, configured to obtain QoS requirement information for a service data packet, and the service data packet is a data packet transmitted between a service server and a service processing device accessed through a non-3GPP access method; a generation unit, configured to generate QoS policy information corresponding to the service data packet according to the QoS requirement information; and a sending unit, configured to send the QoS policy information to a session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service data packet according to the QoS policy information.

[0017] In the eighth aspect, an embodiment of the present application provides a QoS processing device based on non-3GPP access, and the QoS processing device is applied to a session management function network element, and the QoS processing device includes: a receiving unit, configured to receive QoS policy information sent by a policy control function network element for processing service data packets, and the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access method; a generating unit, configured to generate QoS processing related information corresponding to the processing devices of the service data packets according to the QoS policy information; and a sending unit, configured to configure the QoS processing related information to the processing devices of the service data packets.

[0018] In a ninth aspect, an embodiment of the present application provides a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, the QoS processing method based on non-3GPP access as described in the above embodiment is implemented.

[0019] In the tenth aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; a storage device for storing one or more computer programs, wherein when the one or more computer programs are executed by the one or more processors, the electronic device implements the QoS processing method based on non-3GPP access as described in the above embodiment.

[0020] In an eleventh aspect, embodiments of the present application provide a computer program product, comprising a computer program stored in a computer-readable storage medium. A processor of an electronic device reads and executes the computer program from the computer-readable storage medium, causing the electronic device to perform the QoS processing method based on non-3GPP access provided in the various optional embodiments described above.

[0021] In the technical solutions provided in some embodiments of the present application, after the service processing device is connected to the target network element through a non-3GPP access method, the target network element receives the QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server sent by the core network network element, and then performs QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information, so that the QoS mechanism can be supported in the non-3GPP access method based on the target network element, ensuring the interoperability and integration of the QoS mechanism between the 3GPP network and the non-3GPP network, thereby enabling the service processing device to implement QoS processing of service data flows through both 3GPP RAT and non-3GPP access methods (such as Wi-Fi access methods). On the premise of ensuring the QoS requirements of the service data flow, the processing flexibility of the service data flow is improved, which is conducive to improving the utilization of network bandwidth and service processing quality.

[0022] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a schematic diagram showing an exemplary system architecture to which the technical solutions of the embodiments of the present application can be applied;

[0024] FIG2 is a schematic diagram showing a transmission process of a multimedia data packet according to an embodiment of the present application;

[0025] FIG3 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application;

[0026] FIG4 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application;

[0027] FIG5 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application;

[0028] FIG6 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application;

[0029] FIG7 shows a system architecture diagram of a trusted non-3GPP access method according to an embodiment of the present application;

[0030] FIG8 shows a system architecture diagram of an untrusted non-3GPP access method according to an embodiment of the present application;

[0031] FIG9 shows a block diagram of a QoS processing apparatus based on non-3GPP access according to an embodiment of the present application;

[0032] FIG10 shows a block diagram of a QoS processing apparatus based on non-3GPP access according to an embodiment of the present application;

[0033] FIG11 shows a block diagram of a QoS processing apparatus based on non-3GPP access according to an embodiment of the present application;

[0034] FIG12 shows a block diagram of a QoS processing apparatus based on non-3GPP access according to an embodiment of the present application;

[0035] FIG13 shows a schematic structural diagram of a computer system suitable for implementing an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] Example embodiments will now be described in a more complete manner with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to these examples; rather, these embodiments are provided to make this application more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art.

[0037] In addition, the features, structures or characteristics described in the present application may be combined in one or more embodiments in any suitable manner. In the following description, there are many specific details so that the embodiments of the present application can be fully understood. However, it will be appreciated by those skilled in the art that when implementing the technical solution of the present application, it is not necessary to use all the detailed features in the embodiments, one or more specific details may be omitted, or other methods, elements, devices, steps, etc. may be adopted.

[0038] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0039] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0040] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0041] It should be noted that the term "plurality" used in this document refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. The character " / " generally indicates an "or" relationship between the associated objects.

[0042] With the development of 5G and its subsequent evolution systems (such as 5G-A and 6G), many multimedia services requiring high data volumes and short latency have been adopted, such as cloud gaming, VR, AR, MR, XR, and CR interactive services.

[0043] For example, in the cloud gaming scenario shown in FIG1 , the cloud server 101 is used to run the cloud game. The cloud server 101 can render the game screen, encode the audio signal and the rendered image, and finally transmit the encoded data obtained by the encoding process to each game client through the network. The game client can be a user equipment (UE) with basic streaming media playback capabilities, human-computer interaction capabilities, and communication capabilities, such as a smartphone, tablet computer, laptop computer, desktop computer, smart TV, smart home, car terminal, aircraft, etc.; or the game client can be an application running in a terminal device. Specifically, the game client can decode the encoded data transmitted by the cloud server 101 to obtain an analog audio and video signal and play it.

[0044] It should be understood that FIG1 is only an exemplary representation of the system architecture of the cloud gaming system and does not limit the specific architecture of the cloud gaming system; for example, in other embodiments, the cloud gaming system may also include a background server for scheduling, etc. The cloud server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The game client and the cloud server 101 can be directly or indirectly connected via wired or wireless communication, which is not limited in this application.

[0045] In the various multimedia-based interactive service application scenarios mentioned above, multimedia data packets are large in size and therefore need to be split into multiple packets for transmission. Specifically, as shown in Figure 2, taking the 5G system as an example, the user plane mainly includes the application server, the user plane function (UPF), the base station (next generation nodeB, gNB), and the UE. For some typical service scenarios, the transmission of multimedia data packets is mainly in the downlink direction, such as from the application server (AS) to the UPF, and then sent to the UE through the gNB. During transmission, the multimedia data packet (using the XR data packet as an example in Figure 2) is split at the application layer of the application server. After the split data packet reaches the UPF from the application server as an Internet Protocol (IP) packet, the 5G system transmits the sub-data packet to the UE through the PDU session. At the UE, the sub-data packet is handed up through the protocol stack step by step and reassembled to recover the multimedia data packet.

[0046] In the system shown in Figure 2, the L1 layer refers to the physical layer, which is used to ensure that the original data can be transmitted on various physical media; the L2 layer refers to the data link layer, which provides services to the network layer based on the services provided by the physical layer; the IP layer is the network layer, which is used to realize data transmission between two end systems; UDP is the User Datagram Protocol, which is called User Datagram Protocol in Chinese; GTP-U is the GPRS (General Packet Radio Service) Tunneling Protocol, which is called General Packet Radio Service Tunneling Protocol User Plane in Chinese; PHY is the abbreviation of Physical, which is called Physical Layer in Chinese; MAC is Media Access Control, which is called Media Access Control in Chinese; RLC is Radio Link Control, which is called Radio Link Control Layer Protocol in Chinese; PDCP is the Packet Data Convergence Protocol, which is called Packet Data Convergence Protocol in Chinese; SDAP is the Service Data Adaptation Protocol, which is called Service Data Adaptation Protocol in Chinese.

[0047] As mentioned earlier, for multimedia services (such as XRM), it's common to split a single multimedia data packet into multiple packets for transmission. A single multimedia service frame or group of packets (GoP) can also be quite large, requiring a series of IP packets to carry it. These IP packets are somewhat correlated, and processing them based on this correlation can effectively conserve wireless network bandwidth.

[0048] For example, assuming that data is transmitted through multiple IP packets, these multiple IP packets can form a PDUset (PDU set). If some packets in the PDUset are lost, the entire frame, GoP or other video content may be unable to be decoded, and the remaining data in the PDUset is meaningless to the decoding end. However, if application layer forward error correction (FEC) or other mechanisms are introduced, the media application layer has a certain packet loss recovery capability or anti-packet loss capability, then the remaining data in the PDUset can still be recovered and decoded after some messages are discarded, which means that the remaining data in the PDUset is still meaningful for the receiving end to decode.

[0049] In addition, if different PDU sets are distinguished based on the relevance of application layer data packets in the QoS processing mechanism, then PDUsets with high rates but that can tolerate a certain percentage of packet loss rate or delay excess rate can continue to be processed. In other words, the processing method of multimedia services can be more flexible. At the same time, when processing multimedia services, it is not limited to the RAT defined by the 3GPP organization, but can also support non-3GPP access methods. This is because in actual scenarios, it is common to use devices defined by non-3GPP organizations (such as Wi-Fi devices) to process multimedia services. In this case, how to ensure the QoS requirements of multimedia services when processing (especially when multimedia services are transmitted through PDUsets) is a technical problem that needs to be solved urgently.

[0050] It is precisely based on the above problems that the technical solution of the embodiment of the present application proposes a new QoS processing solution based on non-3GPP access, which can realize the support of QoS mechanism under non-3GPP access mode, and ensure the interoperability and integration of QoS mechanism between 3GPP network and non-3GPP network, thereby enabling service processing equipment to realize QoS processing of service data flow through 3GPPPRAT and non-3GPP access mode (such as Wi-Fi access mode), which is conducive to improving network bandwidth utilization and service processing quality, so as to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

[0051] The following is a detailed description of the implementation details of the technical solution of the embodiment of the present application:

[0052] FIG3 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application. The QoS processing method can be executed by a target network element to which a service processing device is connected via a non-3GPP access method, wherein the target network element is connected to a core network. For example, in a trusted non-3GPP access scenario, the QoS processing method shown in FIG3 can be executed by a trusted non-3GPP access network (TNAN) network element, which can be one or more of a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF), or other network elements. For another example, in an untrusted non-3GPP access scenario, the QoS processing method shown in FIG3 can be executed by a non-3GPP interworking function (N3IWF) network element, or other network elements. 3 , the QoS processing method based on non-3GPP access includes at least S310 to S320, which are described in detail as follows:

[0053] In S310 , QoS configuration information corresponding to service data packet transmission between a service processing device and a service server is received, which is sent by a session management function network element.

[0054] In some optional embodiments, the service data packets between the service processing device and the service server can be transmitted in the form of a data packet set (i.e., PDU set). In this case, the QoS parameters included in the QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server can be at least one of the following parameters: PDU set delay budget (PDUSetDelayBudget, PSDB), PDU set error rate (PDU Set Error Rate, PSER), maximum data burst volume (MaximumDataBurstVolume, MDBV), and packet delay variation / jitter (Packet Delay Variation, PDV).

[0055] Optionally, service data packets between the service processing device and the service server may be transmitted in a per-packet format, rather than in a PDU set format. In this case, the QoS parameters included in the QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server may be at least one of the following parameters: packet delay budget (PDB), packet error rate (PER), maximum data burst size, etc.

[0056] In some optional embodiments, the process of the target network element obtaining the QoS configuration information corresponding to the service data packet may include: AF generates QoS requirement information for the service data packet and sends it to PCF, PCF generates QoS policy information for the service data packet based on the QoS requirement information and sends it to SMF, SMF configures QoS processing related information to the processing device of the service data packet according to the QoS policy information, wherein the QoS processing related information corresponding to the target network element is the above-mentioned QoS configuration information.

[0057] In some optional embodiments, after generating QoS configuration information corresponding to the transmission of service data packets between the service processing device and the service server, the SMF may send the QoS configuration information to the Access and Mobility Management Function (AMF), and the AMF may then send the QoS configuration information to the target network element. Optionally, after generating QoS configuration information corresponding to the transmission of service data packets between the service processing device and the service server, the SMF may send the QoS configuration information to the UPF, and the UPF may then send the QoS configuration information to the target network element.

[0058] In S320, QoS processing is performed on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information.

[0059] In some optional embodiments, the process of performing QoS processing on the service data packet transmission process between the service processing device and the service server by the target network element according to the QoS configuration information may be performing QoS processing on the uplink data packets between the service processing device and the service server, or performing QoS processing on the downlink data packets between the service server and the service processing device.

[0060] In some optional embodiments, when the target network element performs QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information, if at least one of the following situations occurs during the service data packet transmission process detected according to the QoS configuration information, the corresponding service data packet is discarded: congestion occurs during the service data packet transmission process, the transmission delay information of the service data packet cannot meet the delay requirement, the bit error rate of the service data packet cannot meet the bit error rate requirement, and the service data packet is determined to be a useless redundant data packet.

[0061] Specifically, if the target network element detects that the transmission delay information of a downlink data packet from the service server does not meet the delay requirement contained in the QoS configuration information, it may discard the downlink data packet. For downlink data packets transmitted using the PDU set method, the delay requirement contained in the QoS configuration information is the PSDB; for downlink data packets transmitted using the per-packet method, the delay requirement contained in the QoS configuration information is the PDB.

[0062] Optionally, if the target network element detects that the bit error rate of a downlink data packet from the service server does not meet the bit error rate requirement contained in the QoS configuration information, the downlink data packet may be discarded. For downlink data packets transmitted using the PDU set method, the bit error rate contained in the QoS configuration information is the PSER; for downlink data packets transmitted using the per-packet method, the bit error rate contained in the QoS configuration information is the PER.

[0063] Optionally, if the target network element detects that congestion occurs during the transmission of downlink data packets from the service server, the target network element may discard the downlink data packets, for example, in descending order of priority.

[0064] Optionally, if the target network element detects that there are useless redundant data packets in the downlink data packets from the service server, for example, the downlink data packets use FEC or other mechanisms resulting in redundant data packets, then if the valid data packets corresponding to the redundant data packets are all transmitted normally, it means that the redundant data packets are invalid data packets, that is, they do not need to be transmitted again, and therefore can be discarded.

[0065] Optionally, if the target network element detects that the transmission delay information of an uplink data packet from the service processing device does not meet the delay requirement contained in the QoS configuration information, the uplink data packet may be discarded. For uplink data packets transmitted using the PDU set method, the delay requirement contained in the QoS configuration information is the PSDB; for uplink data packets transmitted using the per-packet method, the delay requirement contained in the QoS configuration information is the PDB.

[0066] Optionally, if the target network element detects that the bit error rate of an uplink data packet from the service processing device does not meet the bit error rate requirement included in the QoS configuration information, it may discard the uplink data packet. For uplink data packets transmitted using the PDU set method, the bit error rate included in the QoS configuration information is the PSER; for uplink data packets transmitted using the per-packet method, the bit error rate included in the QoS configuration information is the PER.

[0067] Optionally, if the target network element detects that congestion occurs during the transmission of uplink data packets from the service processing device, the target network element may discard the uplink data packets, for example, in descending order of priority.

[0068] Optionally, if the target network element detects that there are useless redundant data packets in the uplink data packets from the service processing device, for example, the uplink data packets use FEC or other mechanisms resulting in redundant data packets, then if the valid data packets corresponding to the redundant data packets are all transmitted normally, it means that the redundant data packets are invalid data packets, that is, they do not need to be transmitted again, and therefore can be discarded.

[0069] In some optional embodiments, the target network element may detect the process of transmitting service data packets by the service processing device in the non-3GPP access network environment to determine whether congestion occurs in the transmission process of the service data packets. For example, the target network element may detect the transmission process of downlink service data packets sent to the service processing device to determine whether congestion occurs in the transmission of downlink service data packets; or the target network element may detect the transmission process of uplink service data packets sent by the service processing device to determine whether congestion occurs in the transmission of uplink service data packets.

[0070] Alternatively, if the service processing device accesses the target network element via Enhanced Distributed Channel Access (EDCA), congestion can be determined based on the frequency of backoffs by the service processing device. For example, if the service processing device backs off frequently (e.g., the number of backoffs per unit time reaches a set number), congestion may be present.

[0071] It should be noted that EDCA provides different priorities and access categories, allowing different data flows to obtain different transmission opportunities based on their QoS requirements. EDCA also uses contention and backoff mechanisms to adjust parameters such as backoff time and contention window size to ensure fair competition and priority differentiation for service flows of different priorities on the channel. EDCA defines access categories, each with different priorities and backoff parameter settings. These access categories can be configured based on service needs to meet different QoS requirements, such as setting different access categories for voice, video, and data.

[0072] In some optional embodiments, the target network element can determine the priority of the service data packet based on the field information contained in the service data packet, so as to discard the service data in order from low to high priority when it is necessary to discard the service data. Optionally, the field information can be, for example, PDU set importance (PSI) information, and then the importance of different PDU sets can be determined based on the field information, and the importance is positively correlated with the priority. In other embodiments of the present application, the priority of the service data packet can also be determined based on other field information, such as determining the type of the service data packet based on the field indicating the type of the service data packet, and then determining the priority of the service data packet based on the predetermined priorities of different types of data packets (such as pre-determining that the priority of a video type service data packet is higher than the priority of an audio type service data packet, etc.).

[0073] In some optional embodiments, since the target network element needs to transmit the downlink data packet sent by the service server to the service processing device after receiving it, and the uplink data packet that the service processing device needs to send to the service server must also be sent to the target network element first, when processing the QoS of the service data packet between the service processing device and the service server, the delay information between the target network element and the service processing device can be considered.

[0074] Specifically, when the target network element monitors the transmission delay of the service data packet between the service processing device and the service server, it can determine whether the transmission delay of the service data packet meets the delay requirement contained in the QoS rule information based on the delay information between the target network element and the service processing device. For example, the delay requirement for the downlink data packet sent by the service server to the service processing device is a maximum of 50ms. If the target network element finds that the delay has been 40ms after receiving the downlink data packet, and the delay between the target network element and the service processing device is 15ms, then the target network element can determine that even if the downlink data packet is sent to the service processing device, it will not meet the delay requirement, and therefore the downlink data packet can be discarded. If the target network element finds that the delay has been 30ms after receiving the downlink data packet, and the delay between the target network element and the service processing device is 5ms, then the target network element can determine that the downlink data packet can meet the delay requirement.

[0075] In some optional embodiments, the target network element may obtain delay information between the target network element and the service processing device, and then send the delay information to a designated core network element, so that the Policy Control Function (PCF) generates policy information (i.e., QoS policy information) for performing QoS processing on service data packets between the service processing device and the service server based on the delay information obtained from the designated core network element. That is, the PCF may take the delay information between the target network element and the service processing device into consideration when generating the policy information for QoS processing. Optionally, the designated core network element may be a Network Data Analytics Function (NWDAF), or another network element such as an AMF or an Application Function (AF).

[0076] In some optional embodiments, the delay information between the target network element and the service processing device may be an uplink transmission delay from the service processing device to the target network element.

[0077] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element within a set time period, and then send the monitored average transmission delay as the uplink transmission delay to the designated core network element.

[0078] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element within a set time period, and then send the maximum value of the monitored transmission delay as the uplink transmission delay to the designated core network element.

[0079] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element within a set time period, and then send the minimum value of the monitored transmission delay as the uplink transmission delay to the designated core network element.

[0080] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element for a set number of times (such as 1 time, 2 times or more times), and then send the monitored average transmission delay as the uplink transmission delay to the designated core network element.

[0081] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element for a set number of times (such as 1 time, 2 times or more times), and then send the maximum value of the monitored transmission delay as the uplink transmission delay to the designated core network element.

[0082] In some optional embodiments, the target network element may monitor the uplink transmission process between the service processing device and the target network element for a set number of times (such as 1 time, 2 times or more times), and then send the minimum value of the monitored transmission delay as the uplink transmission delay to the designated core network element.

[0083] It should be understood that the embodiment of the present application does not limit the calculation method of the uplink transmission delay from the service processing device to the target network element.

[0084] In some optional embodiments, the delay information between the target network element and the service processing device may be a downlink transmission delay from the target network element to the service processing device.

[0085] In some optional embodiments, the target network element may monitor the downlink transmission process between the target network element and the service processing device within a set time period, and then send the monitored average transmission delay as the downlink transmission delay to the designated core network element.

[0086] In some optional embodiments, the target network element may monitor the downlink transmission process between the target network element and the service processing device within a set time period, and then send the maximum value of the monitored transmission delay as the downlink transmission delay to the designated core network element.

[0087] In some optional embodiments, the target network element may monitor the downlink transmission process between the target network element and the service processing device within a set time period, and then send the minimum value of the monitored transmission delay as the downlink transmission delay to the designated core network element.

[0088] In some optional embodiments, the target network element can monitor the downlink transmission process between the target network element and the service processing device for a set number of times (such as 1 time, 2 times or more times), and then send the monitored average transmission delay as the downlink transmission delay to the designated core network element.

[0089] In some optional embodiments, the target network element can monitor the downlink transmission process between the target network element and the service processing device for a set number of times (such as 1 time, 2 times or more times), and then send the maximum value of the monitored transmission delay as the downlink transmission delay to the designated core network element.

[0090] In some optional embodiments, the target network element can monitor the downlink transmission process between the target network element and the service processing device for a set number of times (such as 1 time, 2 times or more times), and then send the minimum value of the monitored transmission delay as the downlink transmission delay to the designated core network element.

[0091] It should be understood that the embodiment of the present application does not limit the calculation method of the downlink transmission delay from the service processing device to the target network element.

[0092] In some optional embodiments, the delay information between the target network element and the service processing device may be calculated based on the downlink transmission delay from the target network element to the service processing device and the uplink transmission delay from the service processing device to the target network element.

[0093] In some optional embodiments, the target network element may use the average of the uplink transmission delay and the downlink transmission delay as the delay information between the service processing device and the target network element.

[0094] In some optional embodiments, the target network element may use the maximum value of the uplink transmission delay and the downlink transmission delay as the delay information between the service processing device and the target network element.

[0095] In some optional embodiments, the target network element may use the minimum value of the uplink transmission delay and the downlink transmission delay as the delay information between the service processing device and the target network element.

[0096] The embodiment of the present application does not limit the method for calculating the delay information between the service processing device and the target network element.

[0097] It should be noted that the uplink transmission delay and downlink transmission delay in this embodiment can also be obtained according to the method in the aforementioned embodiment, that is, by calculating the average value, maximum value, and minimum value by monitoring for a set duration or a set number of times, or by a single measurement. The embodiment of the present application does not limit this.

[0098] In some optional embodiments, when the target network element detects congestion in the service data packets between the service processing device and the service server, it can also mark the service data packets (the service data packets can be uplink service data packets or downlink service data packets) with explicit congestion notification (ECN).

[0099] Optionally, when ECN marking an uplink service data packet, the ECN mark can be set in the IP header of the uplink service data packet to indicate that the uplink service data packet has experienced network congestion. After the uplink service data packet is sent to the service server, the service server will detect congestion during transmission based on the ECN mark in the uplink service data packet. The service server will then reply with an ACK message with ECN-echo to the service processing device. When the service processing device receives the ACK message with ECN-echo, it will be aware of congestion in the network path of the uplink service data packet and will adjust the transmission rate of the uplink service data packet accordingly to avoid further congestion.

[0100] Optionally, when ECN marking a downlink service data packet, the ECN mark can be set in the IP header of the downlink service data packet to indicate that the downlink service data packet has experienced network congestion. After the downlink service data packet is sent to the service processing device, the service processing device detects, based on the ECN mark in the downlink service data packet, that congestion has occurred during transmission of the downlink service data packet. The service processing device then sends an ACK message with ECN-echo to the service server. When the service server receives the ACK message with ECN-echo, it is informed that congestion has occurred in the network path of the downlink service data packet and will adjust the transmission rate of the downlink service data packet accordingly to avoid further congestion.

[0101] In some optional embodiments, the target network element may perform transit processing on the service data packets transmitted between the service processing device and the service server through low latency, low packet loss, and scalable throughput (Low Latency, Low Loss, and Scalable Throughput, L4S) technology.

[0102] Among them, low latency refers to the time required for data to be transmitted from the sender to the receiver as short as possible. Delay refers to the time delay during the transmission process, which may affect the response speed and performance of the application. Low latency technology can reduce transmission time and improve the response speed of the application and user experience. Low packet loss refers to the fact that the loss rate of data packets is as low as possible during network transmission. Packet loss refers to the situation where some data packets fail to be successfully transmitted to the receiver during network transmission. Low packet loss technology can ensure data integrity and reliability and avoid errors and losses during data transmission. Scalable throughput refers to the data processing capacity of the network or system that can be expanded according to demand. Scalable throughput technology can adjust the processing capacity of the network or system according to actual needs to ensure efficient operation and scalability of the system.

[0103] It can be seen that the technical solution of the embodiment of the present application enables the target network element to implement congestion marking processing based on L4S technology, which helps to reduce delays, reduce packet loss rates, and achieve scalable throughput. At the same time, because the congestion marking processing based on L4S technology provides early congestion feedback, the sending end can adjust the sending rate in time, thereby improving the performance and stability of the network. In addition, the embodiment of the present application can realize the intercommunication and integration of L4S technology between 3GPP networks and non-3GPP networks, thereby ensuring that business processing equipment can implement L4S-based congestion processing through both 3GPP RAT and non-3GPP access methods, which is conducive to improving network bandwidth utilization and business processing quality.

[0104] In some optional embodiments, the process of the target network element performing QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information may include: mapping the QoS parameters contained in the QoS configuration information to the QoS mechanism of the non-3GPP access method, and mapping the downlink service data packet sent by the service server to the bearer corresponding to the non-3GPP access method according to the QoS mechanism of the non-3GPP access method, so as to send the downlink service data packet to the service processing device.

[0105] In some optional embodiments, mapping the QoS parameters included in the QoS configuration information to the QoS mechanism of the non-3GPP access mode may be understood as applying the QoS parameters in the QoS configuration information to the QoS mechanism of the non-3GPP access mode.

[0106] In some optional embodiments, the QoS configuration information includes: data flow QoS parameters.

[0107] It should be understood that the data flow QoS parameters can be 5G QoS parameters, that is, QoS parameters of 5G QoS flow. Of course, the data flow QoS parameters can also be QoS parameters of other forms of data flows, wherein the other forms of data flows can be data flows with finer granularity than 5G QoS flow, but are not limited to this.

[0108] In some optional embodiments, the 5G QoS parameters include: 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), and Maximum Flow Bit Rate (MFBR).

[0109] In some optional embodiments, the 5G QoS parameters further include at least one of the following: a reflective QoS attribute (RQA) and a maximum packet loss rate (Maximum Packet Loss Rate).

[0110] In some optional embodiments, the QoS parameters for other forms of data flows may be similar to the 5G QoS parameters.

[0111] In some optional embodiments, the target network element maps the downlink service data packet sent by the service server to the bearer corresponding to the non-3GPP access mode according to the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device, including: the target network element determines the data flow to which the downlink service data packet belongs; and maps the data flow to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameters, so as to send the downlink service data packet to the service processing device.

[0112] For example, if the service processing device is connected to the target network element via a Wi-Fi access method, the target network element can determine the data flow to which the downlink service data packet belongs, and map the data flow to which the downlink service data packet belongs to the transmission opportunity (TXOP) corresponding to the Wi-Fi access method according to the data flow QoS parameters, such as priority, or map it to part of the transmission resources of the TXOP corresponding to the Wi-Fi access method.

[0113] It should be noted that TXOP can be considered a channel access mechanism used to manage wireless channel access and data transmission. Based on the concept of time-division multiplexing (TDM), TXOP divides the channel into different time intervals, each of which is allocated to a station (SAT) for data transmission. By controlling the TXOP of each station, fair allocation and efficient utilization of channel resources can be achieved, thereby improving network performance and efficiency. Therefore, data streams can be mapped to the TXOP corresponding to the Wi-Fi access method, or the TXOP can be further divided and mapped to a portion of the transmission resources (such as a certain transmission time) of the TXOP corresponding to the Wi-Fi access method.

[0114] In some optional embodiments, the QoS configuration information further includes: PDU aggregate QoS parameters, wherein, as described above, the PDU aggregate QoS parameters include: at least one of: PSDB, PSER, MDBV and PDV.

[0115] In some optional embodiments, the target network element maps the downlink service data packet sent by the service server to the bearer corresponding to the non-3GPP access mode according to the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device, including: the target network element determines the data flow and PDU set to which the downlink service data packet belongs; and maps the data flow and PDU set to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameters and the PDU set QoS parameters, so as to send the downlink service data packet to the service processing device.

[0116] In some implementations, a data stream may include one or more PDU sets.

[0117] For example, if the service processing device is connected to the target network element via a Wi-Fi access method, the target network element can determine the data flow and the PDU set to which the downlink service data packet belongs, and map the data flow and the PDU set to which the downlink service data packet belongs to the TXOP corresponding to the Wi-Fi access method according to the data flow QoS parameters and the PDU set QoS parameters, or map them to part of the transmission resources of the TXOP corresponding to the Wi-Fi access method.

[0118] The above describes the technical solution of the embodiment of the present application from the perspective of the target network element to which the service processing device is connected through a non-3GPP access method. The following further describes the implementation details of the technical solution of the embodiment of the present application from the perspective of other network elements:

[0119] FIG4 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application. The QoS processing method can be executed by an AF or other network elements. Referring to FIG4 , the QoS processing method based on non-3GPP access includes at least S410 to S420, which are described in detail as follows:

[0120] In S410 , QoS requirement information for a service data packet is generated. The service data packet is a data packet transmitted between a service server and a service processing device accessed via a non-3GPP access mode.

[0121] In some optional embodiments, the service data packets between the service processing device and the service server can be transmitted via PDU set. In this case, the QoS parameters included in the QoS requirement information of the service data packets can be at least one of the following parameters: PSDB, PSER, MDBV, PDV.

[0122] Optionally, service data packets between the service processing device and the service server may be transmitted as individual packets (per-packet) rather than as PDU sets. In this case, the QoS parameters included in the QoS requirement information for the service data packets may be at least one of the following parameters: PDB, PER, maximum data burst size, etc.

[0123] In some optional embodiments, the AF may generate QoS requirement information according to the access characteristics of the non-3GPP access mode, so that the generated QoS requirement information can better match the access characteristics of the non-3GPP access mode.

[0124] Optionally, the access characteristics of the non-3GPP access method may include statistical indicators such as bandwidth, latency, jitter, reliability, and packet loss rate, and may also include one or more other information such as supported QoS capabilities. For example, taking the non-3GPP access method as a Wi-Fi access method, the access characteristics of the Wi-Fi access method may also include QoS capabilities for different access classes (ACs), backoff mechanisms, and other media access control (MAC) layer parameters.

[0125] In some optional embodiments, the AF may also generate the same QoS requirement information for non-3GPP access modes and radio access network (RAN) access modes. That is, in this embodiment, a unified set of QoS requirement information may be generated without distinguishing the access mode of the service processing device, thereby simplifying the system processing flow.

[0126] In S420, the QoS requirement information is sent to the PCF, so that the PCF generates QoS policy information corresponding to the service data packet according to the QoS requirement information.

[0127] In some optional embodiments, when the AF sends the QoS requirement information to the core network element, it may send the QoS requirement information directly to the PCF. Alternatively, the AF may send the QoS requirement information to the Network Exposure Function (NEF), which then forwards it to the PCF. Alternatively, the AF may negotiate a Service Level Agreement (SLA) with the PCF to pass the QoS requirement information to the PCF.

[0128] FIG5 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application. The QoS processing method can be executed by a PCF or other network elements. Referring to FIG5 , the QoS processing method based on non-3GPP access includes at least S510 to S530, which are described in detail as follows:

[0129] In S510 , QoS requirement information for a service data packet is obtained. The service data packet is a data packet transmitted between a service server and a service processing device accessed via a non-3GPP access mode.

[0130] In some optional embodiments, the PCF may directly receive QoS requirement information for service data packets sent by the AF, or may receive QoS requirement information from the AF forwarded by the NEF, or the PCF may obtain QoS requirement information by negotiating an SLA with the AF.

[0131] In some optional embodiments, the service data packets between the service processing device and the service server can be transmitted via PDU set. In this case, the QoS parameters included in the QoS requirement information of the service data packets can be at least one of the following parameters: PSDB, PSER, MDBV, PDV.

[0132] Optionally, service data packets between the service processing device and the service server may be transmitted as individual packets (per-packet) rather than as PDU sets. In this case, the QoS parameters included in the QoS requirement information for the service data packets may be at least one of the following parameters: PDB, PER, maximum data burst size, etc.

[0133] In S520, QoS policy information corresponding to the service data packet is generated according to the QoS requirement information.

[0134] In some optional embodiments, the PCF may generate QoS policy information corresponding to the service data packet based on the QoS requirement information and the access characteristics of the non-3GPP access method, so that the generated QoS policy information can better match the access characteristics of the non-3GPP access method.

[0135] Optionally, the access characteristics of the non-3GPP access method may include statistical indicators such as bandwidth, latency, jitter, reliability, and packet loss rate, and may also include one or more other information such as supported QoS capabilities. For example, taking the non-3GPP access method as a Wi-Fi access method, the access characteristics of the Wi-Fi access method may also include QoS capabilities for different ACs, backoff mechanisms, and other MAC layer parameters.

[0136] In some optional embodiments, PCF can also generate the same QoS policy information for non-3GPP access methods and RAN access methods based on QoS requirement information. That is, in this embodiment, a unified set of QoS policy information can be generated without distinguishing the access method of the service processing equipment, which can simplify the system processing flow.

[0137] In S530, the QoS policy information is sent to the session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service data packet according to the QoS policy information.

[0138] In some optional embodiments, the process of PCF sending QoS policy information to SMF may be that PCF and SMF interact through the session management policy association establishment (SM Policy Association Establishment) signaling process, or interact through the session management policy association modification (SM Policy Association Modification) signaling process, and then PCF sends the relevant policy information to SMF through the session management policy context data information element (SMPolicyContextData IE).

[0139] Optionally, the process of SMF configuring QoS processing related information to the processing device of the service data packet according to the QoS policy information can refer to the embodiment shown in Figure 6 below.

[0140] FIG6 shows a flowchart of a QoS processing method based on non-3GPP access according to an embodiment of the present application. The QoS processing method can be executed by an SMF or other network elements. Referring to FIG6 , the QoS processing method based on non-3GPP access includes at least S610 to S630, which are described in detail as follows:

[0141] In S610, QoS policy information for processing a service data packet sent by a policy control function network element is received. The service data packet is a data packet transmitted between a service server and a service processing device accessed via a non-3GPP access mode.

[0142] Optionally, the generation process and related description of the QoS policy information sent by the PCF can refer to the technical solution of the aforementioned embodiment and will not be repeated here.

[0143] In S620, QoS processing related information corresponding to each of the processing devices of the service data packet is generated according to the QoS policy information.

[0144] In some optional embodiments, the SMF may generate QoS processing-related information corresponding to each type of processing device for service data packets based on QoS policy information and access characteristics of the non-3GPP access method, so that the generated QoS processing-related information can better match the access characteristics of the non-3GPP access method.

[0145] Optionally, the access characteristics of the non-3GPP access method may include statistical indicators such as bandwidth, latency, jitter, reliability, and packet loss rate, and may also include one or more other information such as supported QoS capabilities. For example, taking the non-3GPP access method as a Wi-Fi access method, the access characteristics of the Wi-Fi access method may also include QoS capabilities for different ACs, backoff mechanisms, and other MAC layer parameters.

[0146] In some optional embodiments, the SMF may also generate the same QoS processing related information for non-3GPP access methods and RAN access methods based on the QoS policy information. That is, in this embodiment, a unified set of QoS processing related information may be generated without distinguishing the access method of the service processing equipment, thereby simplifying the system processing flow.

[0147] In some optional embodiments, the various types of processing devices for service data packets may include a UPF, a target network element, and a service processing device. Specifically, the QoS processing-related information generated by the SMF for the UPF may be a service data flow (SDF) template; the QoS processing-related information generated by the SMF for the target network element may be QoS profiles; and the QoS processing-related information generated by the SMF for the service processing device may be QoS rules.

[0148] In S630, QoS processing related information is configured to the processing device of the service data packet.

[0149] In some optional embodiments, the process of configuring QoS processing related information to the processing device of the service data packet may include: sending the SDF Template to the UPF, sending the QoS configuration file to the target network element, and sending the QoS rule information to the service processing device.

[0150] Optionally, when the SMF sends the QoS configuration file to the target network element, the SMF may send the QoS configuration information to the AMF, which then sends the QoS configuration information to the target network element. Optionally, the SMF may also send the QoS configuration information to the UPF, which then sends the QoS configuration information to the target network element.

[0151] Optionally, when the SMF sends the QoS rule information to the service processing device, it may send the QoS rule information to the AMF, which then sends the QoS rule information to the target network element, which then sends it to the service processing device. Optionally, if the service processing device can also support access to the core network via 3GPP access, the SMF may also send the QoS rule information to the AMF, which then sends it to the service processing device via the RAN.

[0152] In conjunction with FIG7 and FIG8, the implementation details of the technical solution of the embodiment of the present application are described in detail, taking the non-3GPP access mode as a Wi-Fi access mode as an example:

[0153] As shown in Figure 7, in the system architecture of the trusted non-3GPP access method, the TNAN is connected to the core network elements AMF and UPF. The service processing device (i.e., the UE shown in Figure 7) can access the 5G core network through the TNAN, or if the UE has 3GPP RAT capability, it can also access the 5G core network through 3GPP Access. Among them, the TNAN includes TNAP and TNGF, and the service server is located at the back end of the 5G core network and connected to the data network (DN).

[0154] In one embodiment of the present application, in order to enable the system architecture shown in Figure 7 to support the PDU set feature of trusted 3GPP access, TNGF and TNAP can provide NAS signaling and user plane data transmission based on the Wi-Fi network (using the Wi-Fi network as an example).

[0155] In some optional embodiments, in view of the different characteristics of Wi-Fi, it is necessary to introduce the following new functions into the functions of AF and PCF, but not limited to: when the AF generates QoS requirements and the PCF generates PCCrules, it is optimized in combination with the access characteristics of Trusted Wi-Fi Access; when starting QoS monitoring or ECN marking for L4S, it is set in combination with Wi-Fi characteristics.

[0156] Optionally, the access characteristics of Trusted Wi-Fi Access can include statistical indicators such as bandwidth, latency, jitter, reliability, and packet loss rate. They can also include other MAC layer parameters such as supported QoS capabilities, QoS capabilities for different ACs, and backoff mechanisms. By combining the access characteristics of Trusted Wi-Fi Access with optimization when the AF generates QoS requirements, the PCF generates PCCrule, and when QoS monitoring or ECN marking for L4S is initiated, the QoS processing performed can be more closely aligned with the access characteristics of Trusted Wi-Fi Access, ensuring the effectiveness and quality of QoS processing.

[0157] In some optional embodiments, if the UE is a Trusted Wi-Fi Access (TWA), the AF can consider Trusted Wi-Fi Access characteristics when proposing QoS requirements and the PCF can consider generating PCCrules based on the QoS requirements to more easily map to Wi-Fi QoS. For example, because Wi-Fi lacks support for perflow QoS, per-class QoS, such as Differentiated Services Code Point (DSCP), can be considered when the AF provides QoS requirements and the PCF generates PCCrules. This involves class-based QoS, such as assigning access categories (ACs) corresponding to different service data, and setting corresponding QoS requirements and PCC rules for each access category. When selecting the 5G QoS Identifier (5QI), the characteristics of the current Trusted Wi-Fi Access network (including but not limited to bandwidth, latency, jitter, reliability, packet loss rate, and other metrics obtained through QoS monitoring mechanisms) can also be considered to facilitate QoS mapping between 5G and Wi-Fi.

[0158] In some optional embodiments, to simplify the protocol, 5GC may also generate a unified set of QoS parameters for both NG-RAN Access and Trusted Wi-Fi Access to shield the different characteristics of different Trusted Wi-Fi Access.

[0159] In some optional embodiments, the following new functions may be introduced on the SMF, including but not limited to: when configuring the QoS profile, QoS rule, and N4 rule (N4 rule is QoS processing related information sent to the UPF), the SMF may also be optimized in combination with the access characteristics of Trusted Wi-Fi Access to make QoS easier to map between 5G and Wi-Fi.

[0160] In some optional embodiments, the following new functions are introduced on TNAN (specifically, any one of TNGF and TNAP or a combination of both):

[0161] 1. Support wireless access side functions in PDU set QoS processing, including but not limited to discarding data packets in the PDU set when congestion occurs or useless redundant data is detected.

[0162] Optionally, this function can be implemented to perform congestion detection in a Trusted Wi-Fi network environment, for example, by collecting the frequency of UE backoffs. In EDCA mode, both Wi-Fi-connected UEs and Wi-Fi access points (TNAPs) can determine network congestion based on the frequency of backoffs.

[0163] Optionally, the implementation of this function can identify PSI or other fields at N2 / N3 termination points such as TNGF, so as to select appropriate data packets for discarding when congestion occurs.

[0164] Optionally, specific parameters for operations such as PDUset QoS processing and data packet discard under Trusted Wi-Fi Access conditions, such as delay time requirements and packet loss rate requirements, can be determined based on parameters such as PSDB and PSER provided by 5GC.

[0165] 2. Map the downlink PDU set data to Wi-Fi bearer, and map the 5G QoS parameters + PDU set QoS to the Wi-Fi QoS mechanism.

[0166] Optionally, the mechanism can map 5G QoS flows or more fine-grained data flows to Trusted Wi-Fi TXOPs.

[0167] Optionally, the TNAN may map the PDUset data to the transmission resources of the TXOP according to the TXOP resource characteristics.

[0168] 3. In terms of delay monitoring, the delay between UE and TNAN is taken into account and the QoS delay requirements of 5GS are corrected.

[0169] Optionally, if QoS monitoring is enabled in 5GS, latency measurement and reporting are performed between the UE and the TNAN (such as TNGF), and the TNAN (such as TNGF) assumes the role of the N2 / N3 termination point of the NG-RAN.

[0170] 4. Congestion-based ECN marking for L4S can be performed.

[0171] Optionally, after the TNAN (such as TNGF) detects congestion in the Trusted Wi-Fi Access environment, the TNAN (such as TNGF) may perform ECN marking for L4S operation processing.

[0172] In some optional embodiments, the following functions may be introduced on the UE, but are not limited to: after obtaining the QoS rules configured by the SMF, QoS optimization processing may be performed in combination with the access characteristics of Trusted Wi-Fi Access; and QoS monitoring processing may be completed in conjunction with the TNAN (such as TNGF or TNAP), such as delay measurement.

[0173] As shown in Figure 8, in the system architecture of the untrusted non-3GPP access method, the N3IWF is connected to the core network network elements AMF and UPF. The service processing device (i.e., the UE shown in Figure 8) can access the N3IWF through an untrusted non-3GPP access method (UntrustedNon-3GPPAccess) (for example, the UE establishes an Internet Protocol Security (IPSec) tunnel with the N3IWF to connect to the 5G core network through an untrusted non-3GPP access method) and access the 5G core network through the N3IWF, or if the UE has 3GPP RAT capability, it can also access the 5G core network through 3GPPAccess. Among them, the service server is located at the back end of the 5G core network and is connected to the DN.

[0174] In one embodiment of the present application, in order to enable the system architecture shown in Figure 8 to support the PDU set feature of trusted 3GPP access, N3IWF can provide NAS signaling and user plane data transmission based on the Wi-Fi network (taking the Wi-Fi network as an example).

[0175] In some optional embodiments, in view of the different characteristics of Wi-Fi, it is necessary to introduce the following new functions into the functions of AF and PCF, but not limited to: when the AF generates QoS requirements and the PCF generates PCCrules, it is optimized in combination with the access characteristics of Untrusted Wi-Fi Access; when starting QoS monitoring or ECN marking for L4S, it is set in combination with Wi-Fi characteristics.

[0176] Optionally, the access characteristics of Untrusted Wi-Fi Access can include statistical indicators such as bandwidth, latency, jitter, reliability, and packet loss rate. They can also include other MAC layer parameters such as supported QoS capabilities, QoS capabilities for different ACs, and backoff mechanisms. By combining the access characteristics of Untrusted Wi-Fi Access for optimization when the AF generates QoS requirements, the PCF generates PCCrule, and when QoS monitoring or ECN marking for L4S is initiated, the QoS processing performed can be more closely aligned with the access characteristics of Untrusted Wi-Fi Access, ensuring the effectiveness and quality of QoS processing.

[0177] In some optional embodiments, if the UE is Untrusted Wi-Fi Access, then when the AF proposes QoS requirement information and the PCF generates PCCrules based on the QoS requirement information, they can combine the Untrusted Wi-Fi Access characteristics to generate PCCrules that are easier to map with Wi-Fi QoS. For example, because Wi-Fi has less support for perflow QoS, when the AF provides QoS requirement information and the PCF generates PCCrules, per-class QoS such as DSCP can be considered, that is, class-based QoS is adopted, such as dividing the access categories AC corresponding to different service data, and setting corresponding QoS requirement information and PCC rules for different access categories. When selecting 5QI, the characteristics of the current Untrusted Wi-Fi Access network (including but not limited to bandwidth, latency, jitter characteristics, reliability, packet loss rate and other indicators obtained through the QoS monitoring mechanism) can also be combined to make QoS easier to map between 5G and Wi-Fi.

[0178] In some optional embodiments, to simplify the protocol, 5GC can also generate a unified set of QoS parameters for both NG-RAN Access and Untrusted Wi-Fi Access, and shield the different characteristics of different Untrusted Wi-Fi Access types through N3IWF.

[0179] In some optional embodiments, the following new functions may be introduced on the SMF, but are not limited to: when configuring the QoS profile, QoS rule, and N4 rule (N4 rule is QoS processing related information sent to the UPF), the SMF may also be optimized in combination with the access characteristics of Untrusted Wi-Fi Access to make QoS easier to map between 5G and Wi-Fi.

[0180] In some optional embodiments, the following new functions are introduced on N3IWF, but are not limited to:

[0181] 1. Support wireless access side functions in PDU set QoS processing, including but not limited to discarding data packets in the PDU set when congestion occurs or useless redundant data is detected.

[0182] Optionally, this function can be implemented to perform congestion detection in an Untrusted Wi-Fi network environment, for example, by collecting information about the frequency of UE backoffs to detect congestion.

[0183] Optionally, the implementation of this function can identify PSI or other fields at N2 / N3 termination points such as N3IWF, so as to select appropriate packets for discarding when congestion occurs.

[0184] Optionally, specific parameters for PDUset QoS processing and data packet discarding under Untrusted Wi-Fi Access conditions, such as delay time requirements and packet loss rate requirements, can be determined based on parameters such as PSDB and PSER provided by 5GC.

[0185] 2. Map the downlink PDU set data to Wi-Fi bearer, and map the 5G QoS parameters + PDU set QoS to the Wi-Fi QoS mechanism.

[0186] Optionally, the mechanism can map 5G QoS flows or more fine-grained data flows to Trusted Wi-Fi TXOPs.

[0187] Optionally, the N3IWF may map the PDUset data to the transmission resources of the TXOP according to the TXOP resource characteristics.

[0188] 3. In terms of delay monitoring, the delay between UE and N3IWF is taken into account and the QoS delay requirements of 5GS are corrected.

[0189] Optionally, if QoS monitoring is enabled on the 5GS, latency measurement and reporting is performed between the UE and the N3IWF, and the N3IWF acts as the N2 / N3 termination point of the NG-RAN.

[0190] 4. Congestion-based ECN marking for L4S can be performed.

[0191] Optionally, when the N3IWF detects congestion in the Untrusted Wi-Fi Access environment, the N3IWF may perform ECN marking for L4S operation processing.

[0192] In some optional embodiments, the following functions may be introduced on the UE, but are not limited to: after obtaining the QoS rules configured by the SMF, QoS optimization processing may be performed in combination with the access characteristics of Untrusted Wi-Fi Access; and QoS monitoring processing may be completed in cooperation with the N3IWF, such as delay measurement.

[0193] In summary, the technical solution of the embodiment of the present application can extend the PDU set QoS processing mechanism defined by 3GPP 5GS to non-3GPP access scenarios (such as W-Fi access scenarios), so that the PDU set QoS mechanism can achieve interoperability and integration of 3GPP and non-3GPP networks, which is conducive to supporting business processing equipment for 3GPP RAT and non-3GPP access methods to switch according to network environment and other factors (such as tariff factors), improve the processing flexibility of business data flows, and ensure that immersive multimedia services (such as XRM services) are better popularized.

[0194] It should be noted that the above embodiments are based on the example of transmitting service data between the service processing device and the service server through the PDUset method, and the processing method when transmitting service data between the service processing device and the service server through the per-packet method is similar and will not be repeated here. At the same time, non-3GPP access methods refer to wireless access technologies other than 3GPP-defined cellular network access technologies such as 3G, 4G, 5G, and 6G, including but not limited to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series wireless local area networks (WLANs) and the corresponding Wi-Fi technologies defined by the Wi-Fi Alliance.

[0195] The following describes an apparatus embodiment of the present application, which can be used to implement the QoS processing method based on non-3GPP access in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the embodiment of the QoS processing method based on non-3GPP access in the above-mentioned embodiment of the present application.

[0196] Figure 9 shows a block diagram of a QoS processing device based on non-3GPP access according to an embodiment of the present application. The QoS processing device can be applied to a target network element to which a service processing device is connected via a non-3GPP access method, and the target network element is connected to a core network. For example, in a trusted non-3GPP access scenario, the QoS processing device shown in Figure 9 can be applied to a TNAN network element, which can be one or more of a TNAP and a TNGF, or other network elements. For another example, in an untrusted non-3GPP access scenario, the QoS processing device shown in Figure 3 can be applied to an N3IWF, or other network elements.

[0197] 9 , a QoS processing apparatus 900 based on non-3GPP access according to an embodiment of the present application includes: a receiving unit 902 and a processing unit 904 .

[0198] Among them, the receiving unit 902 is configured to receive QoS configuration information corresponding to the service data packet transmission between the service processing device and the service server sent by the session management function network element; the processing unit 904 is configured to perform QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS configuration information.

[0199] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is configured to discard the corresponding business data packet if at least one of the following situations is detected during the transmission of the business data packet according to the QoS configuration information: congestion occurs during the transmission of the business data packet, the transmission delay information of the business data packet cannot meet the delay requirement, the bit error rate of the business data packet cannot meet the bit error rate requirement, and the business data packet is determined to be a useless redundant data packet.

[0200] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is further configured to perform at least one of the following processes: detecting the process of the business processing device transmitting business data packets in a non-3GPP access network environment to determine whether congestion occurs in the transmission process of the business data packets; determining the priority of the business data packets based on the field information contained in the business data packets, so as to discard the business data in order from low to high priority when it is necessary to discard the business data.

[0201] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is configured as follows: if the service processing device accesses the target network element via EDCA, then the process of the service processing device transmitting service data packets in a non-3GPP access network environment is detected according to the backoff frequency of the service processing device to determine whether congestion occurs in the transmission process of the service data packets.

[0202] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is configured to: map the QoS parameters contained in the QoS configuration information to the QoS mechanism of the non-3GPP access method, and map the downlink service data packet sent by the service server to the bearer corresponding to the non-3GPP access method according to the QoS mechanism of the non-3GPP access method, so as to send the downlink service data packet to the service processing device.

[0203] In some embodiments of the present application, based on the aforementioned scheme, the QoS configuration information includes: data flow QoS parameters; the processing unit 904 is configured to: determine the data flow to which the downlink service data packet belongs; according to the data flow QoS parameters in the QoS mechanism of the non-3GPP access method, map the data flow to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access method, so as to send the downlink service data packet to the service processing device.

[0204] In some embodiments of the present application, based on the aforementioned solution, the non-3GPP access mode includes a Wi-Fi access mode; and the processing unit 904 is configured to: map the data flow to which the downlink service data packet belongs to a TXOP corresponding to the Wi-Fi access mode or a portion of the transmission resources of the TXOP corresponding to the Wi-Fi access mode according to the data flow QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device.

[0205] In some embodiments of the present application, based on the aforementioned scheme, the QoS configuration information includes: data flow QoS parameters and PDU set QoS parameters; the processing unit 904 is configured to: determine the data flow and PDU set to which the downlink service data packet belongs; according to the data flow QoS parameters and the PDU set QoS parameters in the QoS mechanism of the non-3GPP access method, map the data flow and PDU set to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access method, so as to send the downlink service data packet to the service processing device.

[0206] In some embodiments of the present application, based on the aforementioned solution, the non-3GPP access mode includes a Wi-Fi access mode; and the processing unit 904 is configured to: map the data flow and PDU set to which the downlink service data packet belongs to, according to the data flow QoS parameter and the PDU set QoS parameter in the QoS mechanism of the non-3GPP access mode, to a TXOP corresponding to the Wi-Fi access mode or to part of the transmission resources of the TXOP corresponding to the Wi-Fi access mode, so as to send the downlink service data packet to the service processing device.

[0207] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is further configured to: obtain delay information between the target network element and the service processing device; when monitoring the transmission delay of the service data packet between the service processing device and the service server, determine whether the transmission delay of the service data packet meets the delay requirements contained in the QoS configuration information in combination with the delay information.

[0208] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 904 is further configured to: obtain delay information between the target network element and the service processing device; send the delay information to a designated core network network element, so that the policy control function network element generates QoS policy information for processing the service data packet based on the delay information obtained from the designated core network network element; wherein the QoS configuration information is obtained based on the QoS policy information.

[0209] In some embodiments of the present application, based on the above solution, the processing unit 904 is further configured to: if congestion of the service data packets between the service processing device and the service server is detected, perform an explicit congestion notification (ECN) mark on the service data packets.

[0210] In some embodiments of the present application, based on the aforementioned scheme, if the non-3GPP access method is a trusted non-3GPP access method, the target network element is a trusted non-3GPP access network element; if the non-3GPP access method is an untrusted non-3GPP access method, the target network element is a non-3GPP intercommunication function network element.

[0211] In some embodiments of the present application, based on the aforementioned scheme, the service data packets between the service processing device and the service server are transmitted in the form of data packet sets; wherein, the QoS parameters in the QoS configuration information include at least one of the following parameters: protocol data unit PDU set delay budget, PDU set bit error rate, maximum data burst size, and data packet delay jitter.

[0212] FIG10 shows a block diagram of a QoS processing device based on non-3GPP access according to an embodiment of the present application. The QoS processing device can be applied to an AF or other network elements.

[0213] 10 , a QoS processing apparatus 1000 based on non-3GPP access according to an embodiment of the present application includes: a generating unit 1002 and a sending unit 1004 .

[0214] Among them, the generating unit 1002 is configured to generate QoS requirement information for the service data packet, which is a data packet transmitted between the service server and the service processing device accessed through a non-3GPP access method; the sending unit 1004 is configured to send the QoS requirement information to the policy control function network element, so that the policy control function network element generates QoS policy information corresponding to the service data packet based on the QoS requirement information.

[0215] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1002 is configured to: generate the QoS requirement information according to the access characteristics of the non-3GPP access mode; or

[0216] The same QoS requirement information is generated for the non-3GPP access mode and the wireless access network access mode.

[0217] FIG11 shows a block diagram of a QoS processing device based on non-3GPP access according to an embodiment of the present application. The QoS processing device can be applied to a PCF or other network elements.

[0218] 11 , a QoS processing apparatus 1100 based on non-3GPP access according to an embodiment of the present application includes: an acquiring unit 1102 , a generating unit 1104 , and a sending unit 1106 .

[0219] Among them, the acquisition unit 1102 is configured to obtain QoS requirement information for a service data packet, where the service data packet is a data packet transmitted between a service server and a service processing device accessed through a non-3GPP access method; the generation unit 1104 is configured to generate QoS policy information corresponding to the service data packet based on the QoS requirement information; and the sending unit 1106 is configured to send the QoS policy information to a session management function network element, so that the session management function network element configures QoS processing related information to the processing device of the service data packet based on the QoS policy information.

[0220] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1104 is configured to: generate QoS policy information corresponding to the service data packet according to the QoS requirement information and the access characteristics of the non-3GPP access mode; or

[0221] According to the QoS requirement information, the same QoS policy information is generated for the non-3GPP access mode and the wireless access network access mode.

[0222] FIG12 shows a block diagram of a QoS processing device based on non-3GPP access according to an embodiment of the present application. The QoS processing device can be applied to an SMF or other network elements.

[0223] 12 , a QoS processing apparatus 1200 based on non-3GPP access according to an embodiment of the present application includes: a receiving unit 1202 , a generating unit 1204 and a sending unit 1206 .

[0224] Among them, the receiving unit 1202 is configured to receive QoS policy information sent by the policy control function network element for processing service data packets, where the service data packets are data packets transmitted between the service server and the service processing equipment accessed through a non-3GPP access method; the generating unit 1204 is configured to generate QoS processing related information corresponding to the processing equipment of the service data packets according to the QoS policy information; and the sending unit 1206 is configured to configure the QoS processing related information to the processing equipment of the service data packets.

[0225] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1204 is configured to: generate QoS processing related information corresponding to each type of processing device of the service data packet according to the QoS policy information and the access characteristics of the non-3GPP access mode; or

[0226] The same QoS processing related information is generated for the non-3GPP access mode and the wireless access network access mode according to the QoS policy information.

[0227] Figure 13 shows a schematic structural diagram of a computer system of an electronic device suitable for implementing an embodiment of the present application. The electronic device may be the target network element, AF, PCF or SMF in the aforementioned embodiment.

[0228] It should be noted that the computer system 1300 of the electronic device shown in FIG13 is merely an example and should not impose any limitations on the functions and scope of use of the embodiments of the present application.

[0229] As shown in Figure 13, the computer system 1300 may include a central processing unit (CPU) 1301, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1302 or the program loaded from the storage part 1308 into the random access memory (RAM) 1303, such as executing the method described in the above embodiment. Various programs and data required for system operation are also stored in the RAM 1303. The CPU 1301, ROM 1302 and RAM 1303 are connected to each other via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.

[0230] The following components can be connected to the I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1308 including a hard disk; and a communication section 1309 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the I / O interface 1305 as needed. Removable media 1311, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1310 as needed, so that computer programs read from the removable media can be installed in the storage section 1308 as needed.

[0231] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program is used to perform the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1309, and / or installed from a removable medium 1311. When the computer program is executed by the central processing unit (CPU) 1301, the various functions defined in the system of the present application are performed.

[0232] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a computer program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable computer program. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0233] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and a computer program.

[0234] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. In some cases, the names of these units do not constitute limitations on the units themselves.

[0235] As another aspect, the present application further provides a computer-readable medium, which may be included in the electronic device described in the above embodiments, or may exist independently without being incorporated into the electronic device. The computer-readable medium carries one or more computer programs, and when the one or more computer programs are executed by the electronic device, the electronic device implements the method described in the above embodiments.

[0236] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0237] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable an electronic device to execute the method according to the embodiments of the present application.

[0238] For example, the electronic device may be the target network element in the aforementioned embodiment, then the target network element may execute the QoS processing method based on non-3GPP access shown in Figure 3; for another example, the electronic device may be an AF, then the AF may execute the QoS processing method based on non-3GPP access shown in Figure 4; for another example, the electronic device may be a PCF, then the PCF may execute the QoS processing method based on non-3GPP access shown in Figure 5; for another example, the electronic device may be an SMF, then the SMF may execute the QoS processing method based on non-3GPP access shown in Figure 6.

[0239] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0240] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for processing Quality of Service (QoS) based on non-3GPP access, characterized in that The QoS processing method is executed by a target network element connected by a service processing device through a non-3GPP access mode. The target network element is connected to a core network. The QoS processing method includes: Receiving QoS configuration information corresponding to the transmission of service data packets between the service processing device and a service server sent by a session management function network element; Performing QoS processing on the process of transmitting service data packets between the service processing device and the service server according to the QoS configuration information.

2. The QoS processing method according to claim 1, wherein Performing QoS processing on the process of transmitting service data packets between the service processing device and the service server according to the QoS configuration information includes: If at least one of the following situations occurs during the transmission process of the service data packets is detected according to the QoS configuration information, the corresponding service data packets are discarded: Congestion occurs during the transmission process of the service data packets, the transmission delay information of the service data packets cannot meet the delay requirement, the bit error rate of the service data packets cannot meet the bit error rate requirement, and the service data packets are determined to be useless redundant packets.

3. The QoS processing method according to claim 2, wherein The QoS processing method further includes at least one of the following processes: Detecting the process of transmitting service data packets by the service processing device in a non-3GPP access network environment to determine whether congestion occurs in the transmission process of the service data packets; Determining the priority of the service data packets according to the field information included in the service data packets, so as to discard the service data in the order from low to high priority when it is necessary to discard the service data.

4. The method according to claim 3, characterized in that, The detecting the process of transmitting service data packets by the service processing device in a non-3GPP access network environment to determine whether congestion occurs in the transmission process of the service data packets includes: If the service processing device accesses the target network element through an enhanced distributed channel access (EDCA) mode, detecting the process of transmitting service data packets by the service processing device in a non-3GPP access network environment according to the backoff frequency of the service processing device to determine whether congestion occurs in the transmission process of the service data packets.

5. The QoS processing method according to claim 1, wherein Performing QoS processing on the process of transmitting service data packets between the service processing device and the service server according to the QoS configuration information includes: Mapping the QoS parameters included in the QoS configuration information to the QoS mechanism of the non-3GPP access mode, and mapping the downlink service data packets sent by the service server to the bearer corresponding to the non-3GPP access mode according to the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packets to the service processing device.

6. The QoS processing method according to claim 5, wherein The QoS configuration information includes: data flow QoS parameters; The mapping the downlink service data packets sent by the service server to the bearer corresponding to the non-3GPP access mode according to the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packets to the service processing device includes: Determining the data flow to which the downlink service data packets belong; Map the data flow to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device.

7. The QoS processing method according to claim 6, wherein The non-3GPP access mode includes a Wi-Fi access mode; The mapping of the data flow to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device, includes: Map the data flow to which the downlink service data packet belongs to the TXOP corresponding to the Wi-Fi access mode or a part of the transmission resources of the TXOP corresponding to the Wi-Fi access mode according to the data flow QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device.

8. The QoS processing method according to claim 5, wherein The QoS configuration information includes: a data flow QoS parameter and a PDU set QoS parameter; The mapping of the downlink service data packet sent by the service server to the bearer corresponding to the non-3GPP access mode according to the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device, includes: Determine the data flow and PDU set to which the downlink service data packet belongs; Map the data flow and PDU set to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameter and the PDU set QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device.

9. The QoS processing method according to claim 8, wherein The non-3GPP access mode includes a Wi-Fi access mode; The mapping of the data flow and PDU set to which the downlink service data packet belongs to the bearer corresponding to the non-3GPP access mode according to the data flow QoS parameter and the PDU set QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device, includes: Map the data flow and PDU set to which the downlink service data packet belongs to the TXOP corresponding to the Wi-Fi access mode or a part of the transmission resources of the TXOP corresponding to the Wi-Fi access mode according to the data flow QoS parameter and the PDU set QoS parameter in the QoS mechanism of the non-3GPP access mode, so as to send the downlink service data packet to the service processing device.

10. The QoS processing method according to any one of claims 1-9, characterized in that, The QoS processing method further includes: Obtain the delay information between the target network element and the service processing device; When monitoring the transmission delay of the service data packet between the service processing device and the service server, determine whether the transmission delay of the service data packet meets the delay requirement included in the QoS configuration information in combination with the delay information.

11. The QoS processing method according to any one of claims 1-10, characterized in that, The QoS processing method further includes: Obtaining delay information between the target network element and the service processing device; Sending the delay information to a specified core network element, so that a policy control function network element generates QoS policy information for processing the service data packet based on the delay information obtained from the specified core network element; Wherein, the QoS configuration information is obtained based on the QoS policy information.

12. The QoS processing method according to any one of claims 1-11, characterized in that, The QoS processing method further includes: If it is monitored that service data packets between the service processing device and the service server are congested, then perform explicit congestion notification (ECN) marking on the service data packets.

13. The QoS processing method according to any one of claims 1 to 12, characterized in that If the non-3GPP access mode is a trusted non-3GPP access mode, then the target network element is a trusted non-3GPP access network element; If the non-3GPP access mode is an untrusted non-3GPP access mode, then the target network element is a non-3GPP interworking function network element.

14. The QoS processing method according to any one of claims 1 to 13, characterized in that, Service data packets between the service processing device and the service server are transmitted in the form of a data packet set; Wherein, the QoS parameters in the QoS configuration information include at least one of the following parameters: protocol data unit (PDU) set delay budget, PDU set error rate, maximum data burst volume, data packet delay jitter.

15. A QoS processing method based on non-3GPP access, characterized in that, The QoS processing method is executed by an application function network element, and the QoS processing method includes: Generating QoS requirement information for service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; Sending the QoS requirement information to a policy control function network element, so that the policy control function network element generates QoS policy information corresponding to the service data packets according to the QoS requirement information.

16. The QoS processing method according to claim 15, wherein Generating QoS requirement information for service data packets includes: Generating the QoS requirement information according to the access characteristics of the non-3GPP access mode; or Generating the same QoS requirement information for the non-3GPP access mode and the radio access network access mode.

17. A QoS processing method based on non-3GPP access, characterized in that, The QoS processing method is executed by a policy control function network element, and the QoS processing method includes: Obtaining QoS requirement information for service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; Generating QoS policy information corresponding to the service data packets according to the QoS requirement information; Sending the QoS policy information to a session management function network element, so that the session management function network element configures QoS processing-related information for the service data packet processing device according to the QoS policy information.

18. The QoS processing method according to claim 17, wherein Generating QoS policy information corresponding to the service data packets according to the QoS requirement information includes: Generating QoS policy information corresponding to the service data packets according to the QoS requirement information and the access characteristics of the non-3GPP access mode; or Generate the same QoS policy information for the non-3GPP access mode and the radio access network access mode according to the QoS requirement information.

19. A QoS processing method based on non-3GPP access, characterized in that, The QoS processing method is executed by a session management function network element, and the QoS processing method includes: Receiving QoS policy information sent by a policy control function network element for processing service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; Generating QoS processing-related information corresponding to the processing devices of the service data packets according to the QoS policy information; Configuring the QoS processing-related information to the processing devices of the service data packets.

20. The QoS processing method according to claim 19, characterized in that, Generating QoS processing-related information corresponding to various processing devices of the service data packets according to the QoS policy information, including: Generating QoS processing-related information corresponding to various processing devices of the service data packets according to the QoS policy information and the access characteristics of the non-3GPP access mode; or, Generating the same QoS processing-related information for the non-3GPP access mode and the radio access network access mode according to the QoS policy information.

21. A QoS processing device based on non-3GPP access, characterized in that, The QoS processing device is applied to a target network element connected by a service processing device through a non-3GPP access mode, and the target network element is connected to a core network. The QoS processing device includes: A receiving unit configured to receive QoS configuration information corresponding to the transmission of service data packets between the service processing device and a service server sent by a session management function network element; A processing unit configured to perform QoS processing on the transmission process of service data packets between the service processing device and the service server according to the QoS configuration information.

22. A QoS processing device based on non-3GPP access, characterized in that, The QoS processing device is applied to an application function network element. The QoS processing device includes: A generating unit configured to generate QoS requirement information for service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; A sending unit configured to send the QoS requirement information to a policy control function network element so that the policy control function network element generates QoS policy information corresponding to the service data packets according to the QoS requirement information.

23. A QoS processing device based on non-3GPP access, characterized in that The QoS processing device is applied to a policy control function network element. The QoS processing device includes: An obtaining unit configured to obtain QoS requirement information for service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; A generating unit configured to generate QoS policy information corresponding to the service data packets according to the QoS requirement information; A sending unit configured to send the QoS policy information to a session management function network element so that the session management function network element configures QoS processing-related information to the processing devices of the service data packets according to the QoS policy information.

24. A QoS processing device based on non-3GPP access, characterized in that, The QoS processing device is applied to a session management function network element. The QoS processing device includes: A receiving unit, configured to receive QoS policy information sent by a policy control function network element for processing service data packets, where the service data packets are data packets transmitted between a service server and a service processing device accessed through a non-3GPP access mode; A generating unit, configured to generate QoS processing-related information corresponding to the processing devices of the service data packets according to the QoS policy information; A sending unit, configured to configure the QoS processing-related information to the processing devices of the service data packets.

25. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the QoS processing method according to any one of claims 1 to 20.

26. An electronic device, characterized in that, Comprising: One or more processors; A memory, configured to store one or more computer programs, and when the one or more computer programs are executed by the one or more processors, the electronic device implements the QoS processing method according to any one of claims 1 to 20.

27. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, it implements the method according to any one of claims 1 to 20.

Images