Quality of service processing method and apparatus, computer-readable medium, and electronic device

Abstract

Embodiments of the present application provide a quality of service (QoS) processing method and apparatus, a computer-readable medium, and an electronic device. The QoS processing method is executed by a terminal device that accesses a core network by means of an access network element; the terminal device is communicationally connected to a service processing device; and the service processing device performs service interaction with a service server by means of the terminal device. The QoS processing method comprises: establishing a protocol data unit (PDU) session with a core network; acquiring QoS rule information for PDU session-based service data packet transmission between a service processing device and a service server; and performing QoS processing on the service data packet transmission between the service processing device and the service server on the basis of the QoS rule information. By means of the technical solution in the embodiments of the present application, a service processing device that does not directly access a core network supports a QoS mechanism, thereby improving the utilization rate of network bandwidth and the service processing quality.

Description

Service quality processing method, device, computer-readable medium and electronic device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 29, 2023, with application number 202311870077.X and invention name “Service Quality Processing Method, Device, Computer-Readable Medium and Electronic Device”, 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 method, device, computer-readable medium, and electronic device for processing quality of service. 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 indirect access through other terminals. For example, the service processing equipment is connected to the User Equipment (UE) through a Tether, and the UE is connected to the core network through the base station. 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 service quality processing method, device, computer-readable medium and electronic device, which realize the support of QoS mechanism by business processing equipment that is not directly connected to the core network, which is conducive to improving network bandwidth utilization and business processing quality.

[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, which is executed by a terminal device that accesses the core network through an access network network element, the terminal device is communicated with a service processing device, and the service processing device interacts with the service server through the terminal device. The QoS processing method includes: establishing a protocol data unit (PDU) session with the core network; obtaining QoS rule information for the service data packet transmission between the service processing device and the service server based on the PDU session; and performing QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS rule information.

[0008] In the second aspect, an embodiment of the present application provides a QoS processing method, which is executed by an application function network element, and the QoS processing method includes: generating QoS requirement information for service data packets, wherein the service data packets are data packets transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to a core network through an access network network element, and the service processing device interacts with the service server through the terminal device; and 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, which is executed by a policy control function network element, and the QoS processing method includes: obtaining QoS requirement information for a service data packet, the service data packet is a data packet transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to the core network through an access network network element, and the service processing device interacts with the service server through the terminal device; generating QoS policy information corresponding to the service data packet according to 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 according to the QoS policy information.

[0010] In some embodiments of the present application, based on the aforementioned solution, generating QoS policy information corresponding to the service data packet according to the QoS requirement information includes at least one of the following methods:

[0011] Obtaining delay information between the terminal device and the service processing device, and generating the QoS policy information according to the QoS requirement information and the delay information;

[0012] The QoS policy information is generated according to a reporting method of the QoS monitoring results and the QoS parameters included in the QoS requirement information. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results in combination or reporting multiple link monitoring results separately.

[0013] In the fourth aspect, an embodiment of the present application provides a QoS processing method, which 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, the service data packets are data packets transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to a core network through an access network network element, and the service processing device interacts with the service server through the terminal device; 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.

[0014] 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 at least one of the following methods:

[0015] generating, according to the load of the uplink service data packets sent by the service processing device and received by the terminal device, QoS configuration information for an access network element, the QoS configuration information being used to instruct the access network element to configure, for the terminal device, wireless transmission resources that match the load;

[0016] generating, based on whether the terminal device has a data packet aggregate processing capability, QoS configuration information for an access network element, the QoS configuration information being used to instruct the access network element whether to perform downlink processing of the data packet aggregate;

[0017] generating, according to the load of the uplink service data packets sent by the service processing device and received by the terminal device, QoS rule information for the terminal device, the QoS rule information being used to configure, for the terminal device, wireless transmission resources that match the load;

[0018] Obtaining delay information between the terminal device and the service processing device, and generating the QoS processing related information according to the QoS policy information and the delay information;

[0019] According to the reporting method of the QoS monitoring results and the QoS parameters contained in the QoS policy information, QoS rule information for the terminal device is generated. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results together or reporting multiple link monitoring results separately.

[0020] In the fifth aspect, an embodiment of the present application provides a QoS processing device, which is applied to a terminal device that accesses the core network through an access network network element, the terminal device is communicated with the service processing device, and the service processing device interacts with the service server through the terminal device. The QoS processing device includes: an establishment unit, configured to establish a PDU session with the core network; an acquisition unit, configured to obtain QoS rule information for the service processing device and the service server to transmit service data packets based on the PDU session; 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 rule information.

[0021] In the sixth aspect, an embodiment of the present application provides a QoS processing device, 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, wherein the service data packet is a data packet transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to a core network through an access network network element, and the service processing device performs service interaction with the service server through the terminal device; 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.

[0022] In the seventh aspect, an embodiment of the present application provides a QoS processing device, 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, wherein the service data packet is a data packet transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to a core network through an access network network element, and the service processing device interacts with the service server through the terminal device; a generation unit, configured to generate QoS policy information corresponding to the service data packet 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 device of the service data packet according to the QoS policy information.

[0023] In the eighth aspect, an embodiment of the present application provides a QoS processing device, which 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, wherein the service data packets are data packets transmitted between a service server and a service processing device, the service processing device is communicated with a terminal device, the terminal device is accessed to a core network through an access network network element, and the service processing device interacts with the service server through the terminal device; 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 configuring unit, configured to configure the QoS processing related information to the processing devices of the service data packets.

[0024] In a ninth aspect, an embodiment of the present application provides a computer-readable medium on which a computer program is stored. When the computer program is executed by a processor, the QoS processing method as described in the above embodiment is implemented.

[0025] 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 as described in the above embodiments.

[0026] In an eleventh aspect, an embodiment of the present application provides a computer program product, the computer program product including 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 methods provided in the various optional embodiments described above.

[0027] In the technical solutions provided in some embodiments of the present application, after the terminal device accesses the core network through the access network element, the service processing device establishes a communication connection with the terminal device so as to perform service interaction with the service server through the terminal device. In this system architecture, the terminal device establishes a PDU session with the core network, and then obtains QoS rule information for the service data packet transmission between the service processing device and the service server based on the PDU session, so as to perform QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS rule information. This makes it possible to implement support for the QoS mechanism by the service processing device that is not directly connected to the core network based on the terminal device. Under the premise of ensuring the QoS requirements of the service data packet, the processing flexibility of the service data packet is improved, which is conducive to improving the utilization rate of network bandwidth and the quality of service processing.

[0028] 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

[0029] 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;

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

[0031] FIG3 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0032] FIG4 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0033] FIG5 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0034] FIG6 shows a flow chart of a QoS processing method according to an embodiment of the present application;

[0035] FIG7 shows a system architecture diagram of a service processing device accessing a terminal device according to an embodiment of the present application;

[0036] FIG8 shows a system architecture diagram of a service processing device accessing a terminal device according to an embodiment of the present application;

[0037] FIG9A shows a flowchart of implementing QoS processing based on a trusted WLAN according to an embodiment of the present application;

[0038] FIG9B shows a flowchart of implementing QoS processing based on a WLAN that is not authenticated as trusted according to an embodiment of the present application;

[0039] FIG10 shows a QoS monitoring flow chart according to an embodiment of the present application;

[0040] FIG11 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0041] FIG12 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0042] FIG13 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0043] FIG14 shows a block diagram of a QoS processing device according to an embodiment of the present application;

[0044] FIG15 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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] 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 service processing devices accessed through the RAT defined by the 3GPP organization, but can also support service processing devices that are not accessed through the 3GPP RAT. This is because in actual scenarios, service processing devices may not have 3GPP RAT capabilities, or are not directly accessed through the 3GPP RAT, but are accessed through other UEs using a Tether method. 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.

[0059] 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, which can realize the support of the QoS mechanism by business processing equipment that is not directly connected to the core network based on the terminal equipment. On the premise of ensuring the QoS requirements of the business data packets, the processing flexibility of the business data packets is improved, which is conducive to improving the utilization of network bandwidth and the quality of business processing, so as to better cope with the challenges of high-bandwidth interactive services to wireless network transmission.

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

[0061] FIG3 shows a flowchart of a QoS processing method according to an embodiment of the present application. The QoS processing method can be executed by a terminal device that accesses the core network through an access network element. The terminal device communicates with the service processing device, and the service processing device interacts with the service server through the terminal device. Alternatively, the technical solution of the embodiment shown in FIG3 can also be executed by other network elements or devices with similar functions. Referring to FIG3, the QoS processing method includes at least S310 to S320, which are described in detail as follows:

[0062] In S310, a PDU session is established with the core network.

[0063] In some optional embodiments, taking the terminal device executing the technical solution of the embodiment shown in Figure 3 as an example, the terminal device can send a PDU session establishment request to the access network network element (such as a base station) to initiate the PDU session establishment process, and then the access network network element can send the PDU session establishment request to the Access and Mobility Management Function (AMF), and the AMF executes the PDU session establishment process, such as AMF executing the selection of the Session Management Function (SMF) and initiating a request to create a session management context, and then through the interaction between network elements such as SMF, AMF and Policy Control Function (PCF), a PDU session is established between the terminal device and the core network element.

[0064] Optionally, after the PDU session is established, the service processing device may transmit data based on the user plane between the terminal device and the service server. Specifically, the service server may send downlink service data packets to the service processing device to the terminal device via the user plane, and then the terminal device may send them to the connected service processing device. The service processing device may send uplink service data packets to the service server to the terminal device, and then the terminal device may send them to the service server via the user plane.

[0065] It should be noted that the service processing device and the terminal device in the embodiments of the present application can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart TV, a smart home, a vehicle terminal, an aircraft, etc. The service processing device may not support 3GPP RAT and may be connected to the terminal device through other means (such as Wi-Fi), or the service processing device may also be a device that supports 3GPP RAT.

[0066] In some optional embodiments, the terminal device can serve as an access point to establish a wireless local area network (WLAN), and then at least one service processing device can access the wireless local area network, thereby establishing a communication connection between the terminal device and the at least one service processing device.

[0067] In some optional embodiments, after establishing a wireless LAN, the terminal device may register the wireless LAN with the core network to authenticate the wireless LAN as a trusted wireless LAN. Alternatively, the wireless LAN established by the terminal device may be treated as a wireless LAN that is not authenticated as a trusted wireless LAN and accessed to the core network through an access network element. A wireless LAN that is not authenticated as a trusted wireless LAN refers to a wireless LAN that has not been authenticated as a trusted wireless LAN. In this case, the wireless LAN may be considered an untrusted wireless LAN by the core network. That is, in the embodiments of the present application, the wireless LAN established by the terminal device may be authenticated as a trusted wireless LAN or not as a trusted wireless LAN.

[0068] In some optional embodiments, after a terminal device establishes a wireless local area network, if a service processing device accesses the wireless local area network, the terminal device may assign a network address to the service processing device, so that the service processing device transmits service data packets to a service server based on the assigned network address. Optionally, the network address may be an Internet Protocol (IP) address.

[0069] In some optional embodiments, after receiving a service data packet sent from a service processing device to a service server, the terminal device may further convert the network address in the service data packet to obtain a converted service data packet, and then transmit the converted service data packet to the service server via a PDU session. That is, in this embodiment, the terminal device has a network address translation (NAT) function, which can shield the service processing device from the user. In this case, when the terminal device receives a downlink service data packet sent from a service server to a certain network address, it can determine to which service processing device the downlink service data packet needs to be sent based on the network address of the downlink service data packet, and then forward it to the service processing device.

[0070] In some optional embodiments, when a terminal device receives a downlink service data packet from a service server, it can select a wireless local area network QoS mechanism corresponding to the priority of the downlink service data packet and send the downlink service data packet to a service processing device based on the priority of the downlink service data packet. Optionally, high-priority service data packets can be given priority to compete for wireless channels; or high-priority service data packets can be given priority to transmission; or the sending rate of high-priority service data packets can be increased, and the sending rate of low-priority data packets can be reduced, etc. It should be noted that the high priority and low priority in this embodiment are relative, and it is generally understood that the priority of high-priority service data packets is greater than the priority of low-priority service data packets.

[0071] In some optional embodiments, when establishing a PDU session with the core network, the terminal device can establish a PDU session with the core network. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to different QoS flows in the PDU session to respectively meet the QoS requirements of the service data packets of different service processing devices.

[0072] In some optional embodiments, when establishing a PDU session with the core network, the terminal device may establish separate PDU sessions corresponding to service data packets of different service processing devices. In this case, if there are multiple service processing devices, the service data packets of different service processing devices may correspond to different PDU sessions, thereby separately meeting the QoS requirements of the service data packets of different service processing devices.

[0073] In some optional embodiments, when the terminal device establishes a PDU session with the core network, it can establish a PDU session with the core network. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to the same QoS flow in the PDU session, which can reduce the complexity of QoS processing.

[0074] In some optional embodiments, the service data packets between the service processing device and the service server may be transmitted in the form of a data packet set (ie, PDU set) or in the form of a single data packet (per-packet).

[0075] It should be noted that in addition to establishing a connection with the terminal device through a wireless LAN, the business processing device can also establish a connection with the terminal device through other short-range wireless communication technologies, such as Bluetooth, ZigBee, etc.

[0076] At the same time, it is worth noting that even if the wireless LAN established by the terminal device is not authenticated as a trusted wireless LAN, the related processing procedures (such as IP address allocation, NAT processing, QoS processing, etc.) are similar to those of a trusted WLAN authentication.

[0077] In S320, QoS rule information for service data packet transmission between the service processing device and the service server based on the PDU session is obtained.

[0078] In some optional embodiments, the process of the terminal device obtaining QoS rule information can be: AF generates QoS requirement information for the business data packet and sends it to PCF, PCF generates QoS policy information for the business 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 business data packet according to the QoS policy information, wherein the QoS processing related information corresponding to the terminal device is the above-mentioned QoS rule information.

[0079] In some implementations, after generating QoS rule information for the terminal device, the SMF sends it to the AMF, and then the AMF sends the QoS rule information to the terminal device through the access network element.

[0080] In some optional embodiments, since the terminal device is not the last hop of the end-to-end transmission, that is, the terminal device needs to transmit the downlink service data packet sent by the service server to the service processing device after receiving it, and the uplink service data packet that the service processing device needs to send to the service server must also be sent to the terminal device first. Therefore, when processing the QoS of the service data packet between the service processing device and the service server, the delay information between the terminal device and the service processing device can be considered.

[0081] Specifically, the terminal device can obtain the delay information between the terminal device and the service processing device, and then send the delay information to the first core network network element, so that the PCF generates policy information (i.e., QoS policy information) for QoS processing of service data packets between the service processing device and the service server based on the delay information obtained from the first core network network element. That is, the PCF can take the delay information between the terminal device and the service processing device into consideration when generating the policy information for QoS processing. Optionally, the first core network network element can be a Network Data Analytics Function (NWDAF), or other network elements such as an AMF and an Application Function (AF).

[0082] In some optional embodiments, the QoS policy information includes: a delay requirement between the service server and the service processing device, wherein the delay requirement is obtained based on the delay information between the terminal device and the service processing device and the delay information between the terminal device and the service server.

[0083] In some optional embodiments, the delay information sent by the terminal device to the first core network element (ie, the delay information between the terminal device and the service processing device) may be the uplink transmission delay from the service processing device to the terminal device.

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

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

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

[0087] In some optional embodiments, the terminal device can monitor the uplink transmission process between the service processing device and the terminal 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 uplink transmission delay to the first core network network element.

[0088] In some optional embodiments, the terminal device can monitor the uplink transmission process between the service processing device and the terminal 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 uplink transmission delay to the first core network network element.

[0089] In some optional embodiments, the terminal device can monitor the uplink transmission process between the service processing device and the terminal 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 uplink transmission delay to the first core network network element.

[0090] It should be understood that the embodiments of the present application do not limit the method for calculating the uplink transmission delay from the service processing device to the terminal device.

[0091] In some optional embodiments, the delay information sent by the terminal device to the first core network element (ie, the delay information between the terminal device and the service processing device) may be the downlink transmission delay from the terminal device to the service processing device.

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

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

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

[0095] In some optional embodiments, the terminal device can monitor the downlink transmission process from the terminal device to 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 first core network network element.

[0096] In some optional embodiments, the terminal device can monitor the downlink transmission process between the service processing device and the terminal 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 first core network network element.

[0097] In some optional embodiments, the terminal device can monitor the downlink transmission process between the service processing device and the terminal 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 first core network network element.

[0098] It should be understood that the embodiments of the present application do not limit the method for calculating the downlink transmission delay from the service processing device to the terminal device.

[0099] In some optional embodiments, the delay information sent by the terminal device to the first core network network element (i.e., the delay information between the terminal device and the service processing device) can be calculated based on the uplink transmission delay from the service processing device to the terminal device, and the downlink transmission delay from the terminal device to the service processing device.

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

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

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

[0103] The embodiment of the present application does not limit the method for calculating the delay information between the terminal device and the service processing device.

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

[0105] In S330 , QoS processing is performed on the service data packet transmission process between the service processing device and the service server according to the QoS rule information.

[0106] 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 rule information 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), packet delay variation / jitter (Packet Delay Variation, PDV), etc.

[0107] Optionally, service data packets between the service processing device and the service server may be transmitted in per-packet form instead of in PDU sets. In this case, the QoS parameters included in the QoS rule information may be at least one of the following parameters: packet delay budget (PDB), packet error rate (PER), maximum data burst size, etc.

[0108] 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 according to the QoS rule information by the terminal device may be performing QoS processing on the uplink service data packets between the service processing device and the service server, or performing QoS processing on the downlink service data packets between the service server and the service processing device.

[0109] In some optional embodiments, when the terminal device performs QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS rule information, if at least one of the following situations occurs during the service data packet transmission process monitored according to the QoS rule 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.

[0110] Specifically, if the terminal device detects that the transmission delay information of a downlink service data packet from the service server does not meet the delay requirement contained in the QoS rule information, the downlink service data packet may be discarded. For downlink service data packets transmitted using the PDU set method, the delay requirement contained in the QoS rule information is the PSDB; for downlink service data packets transmitted using the per-packet method, the delay requirement contained in the QoS rule information is the PDB.

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

[0112] Optionally, if the terminal device detects that congestion occurs during the transmission of downlink service data packets from the service server, the downlink service data packets may be discarded, for example, in descending order of priority.

[0113] Optionally, if the terminal device detects that there are useless redundant data packets in the downlink service data packets from the service server, for example, the downlink service 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.

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

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

[0116] Optionally, if the terminal device detects that uplink service data packets from the service processing device are congested during transmission, the uplink service data packets may be discarded, for example, in descending order of priority.

[0117] Optionally, if the terminal device detects that there are useless redundant data packets in the uplink service data packets from the service processing device, for example, the uplink service 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 can therefore be discarded.

[0118] In some optional embodiments, the terminal device 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 packet in order from low to high priority when it is necessary to discard the service data packet. Optionally, the field information can be, for example, PDU set importance (PSI) information, 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.).

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

[0120] Specifically, when the terminal device 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 in combination with the delay information between the terminal device and the service processing device. For example, the delay requirement for the downlink service data packet sent by the service server to the service processing device is a maximum of 50ms. If the terminal device finds that it has been delayed by 40ms after receiving the downlink service data packet, and the delay between the terminal device and the service processing device is 15ms, then the terminal device can determine that the downlink service data packet can no longer meet the delay requirement. If the terminal device finds that it has been delayed by 40ms after receiving the downlink service data packet, and the delay between the terminal device and the service processing device is 5ms, then the terminal device can determine that the downlink service data packet can meet the delay requirement.

[0121] In some optional embodiments, when the terminal device 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).

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

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

[0124] In some optional embodiments, the terminal device 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.

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

[0126] It can be seen that the technical solution of the embodiment of the present application enables terminal devices to implement congestion marking processing based on L4S technology, which in turn helps to reduce latency, lower packet loss rate, 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 a timely manner, thereby improving the performance and stability of the network. In addition, the embodiment of the present application enables service processing devices that are not directly connected to the core network to perform L4S-based congestion processing, which is conducive to improving network bandwidth utilization and service processing quality.

[0127] In some optional embodiments, the terminal device may also perform QoS monitoring processing according to the QoS rules to obtain a QoS monitoring result, which may include at least one of the following: a communication link monitoring result between the terminal device and the service processing device, a communication link monitoring result between the terminal device and the access network element, and a core network communication link monitoring result. The terminal device may then send the QoS monitoring result to the second core network element; if the QoS monitoring result includes multiple link monitoring results, the terminal device may send the multiple link monitoring results to the second core network element separately, or merge the multiple link monitoring results and send them to the second core network element. For example, it may be determined based on the indication information of the second core network element whether to send the multiple link monitoring results to the second core network element separately, or to merge the multiple link monitoring results and send them to the core network element.

[0128] Optionally, the indication information is used to indicate a method for sending link detection results.

[0129] Optionally, the second core network element can be AMF, SMF, PCF, AF or other core network elements.

[0130] In some optional embodiments, when performing QoS monitoring, if the terminal device detects that the data transmission rate of the communication link between the terminal device and the access network element is less than or equal to a set value, a notification message may be sent to the network element performing QoS monitoring (such as the access network element, the core network element, etc.). If the terminal device detects that the data transmission rate of the communication link between the terminal device and the service processing device is less than or equal to the set value, the communication channel between the terminal device and the service processing device may be adjusted to adjust the data transmission rate of the communication link between the terminal device and the service processing device.

[0131] In some optional embodiments, when a terminal device receives service data packets sent from a service processing device to a service server, it may send a Buffer Status Report (BSR) to an access network element based on the number of service data packets received from the service processing device, thereby requesting the access network element to allocate uplink transmission resources to the terminal device. For example, if the terminal device receives a large number of service data packets, it may request the access network element to allocate more uplink transmission resources to facilitate transmission of these service data packets to the service server via the access network.

[0132] The above describes the technical solution of the embodiment of the present application from the perspective of the terminal device. 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:

[0133] FIG4 shows a flow chart of a QoS processing method 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 includes at least S410 to S420, which are described in detail as follows:

[0134] In S410, QoS requirement information is generated for the service data packet. The service data packet is a data packet transmitted between the service server and the service processing device. The service processing device communicates with the terminal device. The terminal device is connected to the core network through the access network element. The service processing device interacts with the service server through the terminal device.

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

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

[0137] In some optional embodiments, when generating QoS requirement information for a service data packet, the AF may obtain delay information between the terminal device and the service processing device, and then generate the QoS requirement information according to the delay information.

[0138] Specifically, as mentioned above, since the terminal device is not the last hop in the end-to-end transmission, that is, after receiving the downlink service data packet sent by the service server, the terminal device needs to transmit it to the service processing device. At the same time, the uplink service data packet that the service processing device needs to send to the service server must also be sent to the terminal device first. Therefore, when processing the QoS of the service data packet between the service processing device and the service server, the delay information between the terminal device and the service processing device can be considered. For example, the AF can take this delay information into account when generating QoS requirement information. For example, based on this delay information, the delay requirements for the core network and wireless access network can be increased, thereby meeting the end-to-end transmission delay requirements.

[0139] In some optional embodiments, the AF can also generate QoS requirement information based on the QoS parameters and the reporting method of the QoS monitoring results. The reporting method of the QoS monitoring results includes: combining and reporting multiple link monitoring results or reporting multiple link monitoring results separately. Specifically, these multiple link monitoring results include: the monitoring results of the communication link between the terminal device and the service processing device, the monitoring results of the communication link between the terminal device and the access network element, and the monitoring results of the core network communication link. The AF can indicate in the generated QoS requirement information whether these monitoring results are reported in combination or separately.

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

[0141] In some optional embodiments, when the AF sends the QoS requirement information to the PCF, 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.

[0142] FIG5 shows a flow chart of a QoS processing method 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 includes at least S510 to S530, which are described in detail as follows:

[0143] 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. The service processing device communicates with a terminal device. The terminal device is connected to the core network through an access network element. The service processing device interacts with the service server through the terminal device.

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

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

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

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

[0148] In some optional embodiments, when generating QoS policy information corresponding to a service data packet, the PCF may obtain delay information between the terminal device and the service processing device, and then generate QoS policy information corresponding to the service data packet based on the delay information and QoS requirement information.

[0149] Specifically, as mentioned above, since the terminal device is not the last hop in the end-to-end transmission, that is, after receiving the downlink service data packet sent by the service server, the terminal device needs to transmit it to the service processing device. At the same time, the uplink service data packet that the service processing device needs to send to the service server must also be sent to the terminal device first. Therefore, when processing the QoS of the service data packet between the service processing device and the service server, the delay information between the terminal device and the service processing device can be considered. For example, the PCF can take this delay information into account when generating QoS policy information. For example, based on this delay information, the delay requirements for the core network and wireless access network can be increased, thereby meeting the end-to-end transmission delay requirements.

[0150] In some optional embodiments, the PCF may also generate QoS policy information based on the reporting method of the QoS monitoring results and the QoS parameters contained in the QoS requirement information. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results in combination or reporting multiple link monitoring results separately. Specifically, these multiple link monitoring results include: monitoring results of the communication link between the terminal device and the service processing device, monitoring results of the communication link between the terminal device and the access network element, and monitoring results of the core network communication link. The PCF may indicate in the generated QoS policy information whether these monitoring results are reported in combination or separately.

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

[0152] 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 QoS policy information to SMF through the session management policy context data information element (SMPolicyContextData IE).

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

[0154] FIG6 shows a flow chart of a QoS processing method 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 includes at least S610 to S630, which are described in detail as follows:

[0155] In S610, QoS policy information for processing service data packets sent by the policy control function network element is received. The service data packet is a data packet transmitted between the service server and the service processing device. The service processing device communicates with the terminal device. The terminal device is connected to the core network through the access network network element. The service processing device interacts with the service server through the terminal device.

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

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

[0158] In some optional embodiments, the SMF may generate first QoS configuration information for an access network element based on the load of uplink service data packets sent by the service processing device and received by the terminal device. The first QoS configuration information is used to instruct the access network element to configure wireless transmission resources that match the load to the terminal device. For example, if the service processing device sends a large number of uplink service data packets to the terminal device, the access network element may be instructed to configure more wireless transmission resources to the terminal device to improve the transmission efficiency of the uplink data packets. If the service processing device sends a small number of uplink service data packets to the terminal device, the access network element may be instructed to configure fewer wireless transmission resources to the terminal device to save uplink transmission resources.

[0159] In some optional embodiments, the SMF may generate second QoS configuration information for the access network element based on whether the terminal device has the capability to process a data packet set, and the second QoS configuration information is used to instruct the access network element whether to perform downlink processing of the data packet set. For example, if the terminal device has the capability to process a data packet set (i.e., PDUset), the QoS configuration information may be used to instruct the access network element to perform downlink processing of the data packet set; if the terminal device does not have the capability to process a data packet set, the QoS configuration information may be used to instruct the access network element to transmit the downlink service data packet in the form of a single data packet.

[0160] In some optional embodiments, the SMF may generate QoS rule information for the terminal device based on the load of uplink service data packets received by the terminal device from the service processing device. The QoS rule information is used to configure wireless transmission resources that match the load for the terminal device. For example, if the service processing device sends a large number of uplink service data packets to the terminal device, more wireless transmission resources may be configured for the terminal device to improve the transmission efficiency of the uplink data packets. If the service processing device sends a small number of uplink service data packets to the terminal device, fewer wireless transmission resources may be configured for the terminal device to conserve uplink transmission resources.

[0161] In some optional embodiments, the SMF may obtain delay information between the terminal device and the service processing device, and generate QoS processing related information based on the QoS policy information and the delay information.

[0162] Specifically, as mentioned above, since the terminal device is not the last hop of the end-to-end transmission, that is, after receiving the downlink service data packet sent by the service server, the terminal device needs to transmit it to the service processing device. At the same time, the uplink service data packet that the service processing device needs to send to the service server must also be sent to the terminal device first. Therefore, when processing the QoS of the service data packet between the service processing device and the service server, the delay information between the terminal device and the service processing device can be considered. For example, when generating QoS processing related information, the SMF can take this delay information into account. For example, based on this delay information, the delay requirements for the core network and wireless access network can be increased, thereby meeting the end-to-end transmission delay requirements.

[0163] In some optional embodiments, the SMF can also generate QoS rule information for the terminal device based on the reporting method of the QoS monitoring results and the QoS parameters contained in the QoS policy information. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results in combination or reporting multiple link monitoring results separately. Specifically, these multiple link monitoring results include: the monitoring results of the communication link between the terminal device and the service processing device, the monitoring results of the communication link between the terminal device and the access network element, and the monitoring results of the core network communication link. The SMF can indicate in the generated QoS rule information whether these monitoring results are reported in combination or separately.

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

[0165] 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 access network element (such as a base station), and sending the QoS rule information to the terminal device.

[0166] Optionally, when SMF sends the QoS configuration file to the access network element, it may send the QoS configuration information to AMF, and then AMF sends the QoS configuration information to the access network element.

[0167] Optionally, when SMF sends QoS rule information to the terminal device, it may send the QoS rule information to AMF, and then AMF sends the QoS rule information to the access network element, and then the access network element sends it to the terminal device.

[0168] In conjunction with Figures 7 to 11, the following describes in detail the implementation details of the technical solution of the embodiment of the present application, taking the example of a service processing device accessing a terminal device via Wi-Fi.

[0169] As shown in Figure 7, the terminal device builds a WLAN, allowing the service processing device to access the WLAN to establish a communication connection with the terminal device. The terminal device can then act as a tethered device (TetherUE) to implement data exchange between the service processing device and the service server. The TetherUE communicates with the base station (i.e., the access network element) via the Uu interface. The base station accesses the core network via the N2 and N3 interfaces. The core network and the service server exchange data via the N6 interface.

[0170] It should be noted that the attachment device (TetherUE) is only a description in one embodiment of the present application. In other embodiments of the present application, it may also be called a convergence device, or other descriptions. As long as it can achieve similar functions, it is within the scope of protection of the present application.

[0171] In the example shown in FIG7 , the TetherUE can be connected to the core network (e.g., to the 5G core network) through the base station. The service processing device can be a device that processes XRM services (i.e., an XRM device), and one or more service processing devices can be connected to the TetherUE. Optionally, the service processing device may support a non-access stratum (NAS) protocol module or may not support a NAS protocol module, which is not limited in the present embodiment.

[0172] It should be noted that the WLAN established by TetherUE may be a trusted WLAN, or may not be authenticated as a trusted WLAN.

[0173] In one embodiment of the present application, if the WLAN established by the TetherUE is a trusted WLAN, the details of the system architecture diagram shown in Figure 7 can be shown in Figure 8, wherein the TetherUE can include a trusted WLAN access point (TWAP) and a trusted WLAN interworking function (TWIF). The TWIF can be connected to the control plane (gNB-ControlPlane, gNB-CP) of the base station and the user plane (gNB-UserPlane, gNB-UP) of the base station. The gNB-CP interacts with the AMF via the N2 interface; the gNB-UP interacts with the UPF via the N3 interface. The data network (DN) can be a service server, or the service server can also be connected to the data network.

[0174] Based on the system architecture shown in Figure 8, to support the PDUset QoS processing features of the service processing equipment accessed by the TetherUE, the TWAP in the TetherUE transmits WLAN messages over the Yt' interface. Different PDUset packet priorities are implemented on the Yt' interface as WLAN data bearers with different QoS levels. The TWIF in the TetherUE relays N3 messages (i.e., relays user plane messages) and serves as the termination point for N1 NAS signaling. Data and signaling are transmitted between the TWIF and the gNB over the Uu interface (signaling is transmitted over the Uu-CP, and data is transmitted over the Uu-UP).

[0175] TetherUE implements the function of allocating IP addresses to service processing devices through at least one of TWAP and TWIF, and can provide NAT processing function, thereby shielding the IP addresses of service processing devices from the user plane.

[0176] Optionally, TetherUE can register the WLAN access hotspot with the core network, such as the 5G core network (5GCore, 5GC), making it a trusted WLAN access and achieving end-to-end cellular (cellular) + Wi-Fi tether connection. Taking the 5G network as an example, the specific process is shown in Figure 9A, which includes the following steps:

[0177] S901, TetherUE is pre-configured as a trusted WLAN hotspot access through contract signing or other methods.

[0178] S902, TetherUE turns on the hotspot function.

[0179] In step S903, the TetherUE interacts with the 5GC network element to implement UE authentication and authorization. Since the TetherUE is pre-configured to be a trusted WLAN hotspot, the TetherUE can be authenticated as a trusted WLAN access point after authentication.

[0180] S904: Initialize TWAP and TWIF modules.

[0181] S905: If a service processing device is connected to the TetherUE, an IP address is allocated to the service processing device.

[0182] S906: Tether UE initiates a PDU session establishment process according to the QoS requirement information.

[0183] Optionally, the Tether UE can establish a PDU session. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to different QoS flows in the PDU session to meet the QoS requirements of the service data packets of different service processing devices respectively.

[0184] Optionally, the Tether UE can establish separate PDU sessions corresponding to service data packets from different service processing devices. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can be mapped to different PDU sessions, thereby separately meeting the QoS requirements of the service data packets of different service processing devices.

[0185] Optionally, the Tether UE can establish a PDU session with the core network. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to the same QoS flow in the PDU session, which can reduce the complexity of QoS processing.

[0186] S907: After the PDU session is established, the service processing device and the service server (not shown in FIG9A ) perform end-to-end service processing, and support PDU set QoS processing.

[0187] It should be noted that the WLAN established by the TetherUE may not be authenticated as a trusted WLAN. In this case, the establishment of a PDU session and end-to-end service processing between the service processing device and the service server can also be achieved, and PDU set QoS processing is supported. In an example, the process shown in FIG. 9B includes the following steps:

[0188] S901', TetherUE turns on the hotspot function.

[0189] In step S902', the TetherUE exchanges signaling with the 5GC network element to authenticate and authorize the TetherUE. It should be noted that in step S902', the 5GC network element authenticates and authorizes the TetherUE itself, as is done in the traditional authentication and authorization process for UE access to the core network. However, the TetherUE is not authenticated as a trusted WLAN access point. In other words, in this embodiment, the WLAN established by the TetherUE is not authenticated as a trusted WLAN, but the rest of the process is similar to that for a trusted WLAN authentication process.

[0190] S903': If a service processing device is connected to the TetherUE, an IP address is allocated to the service processing device.

[0191] S904', Tether UE initiates a PDU session establishment process according to the QoS requirement information.

[0192] Optionally, the Tether UE can establish a PDU session. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to different QoS flows in the PDU session to meet the QoS requirements of the service data packets of different service processing devices respectively.

[0193] Optionally, the Tether UE can establish separate PDU sessions corresponding to service data packets from different service processing devices. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can be mapped to different PDU sessions, thereby separately meeting the QoS requirements of the service data packets of different service processing devices.

[0194] Optionally, the Tether UE can establish a PDU session with the core network. In this case, if there are multiple service processing devices, the service data packets of different service processing devices can correspond to the same QoS flow in the PDU session, which can reduce the complexity of QoS processing.

[0195] S905': After the PDU session is established, the service processing device and the service server perform end-to-end service processing and support PDU set QoS processing.

[0196] 9A and 9B , the technical solution of the embodiment of the present application enables the business processing device to access the core network by accessing a trusted WLAN or a WLAN that is not authenticated as trusted, and can implement support for PDU Set QoS based on the trusted WLAN and the WLAN that is not authenticated as trusted.

[0197] In some optional embodiments, in order to support PDUsetQoS capability, TetherUE can support the following functions: the service flows of multiple service processing devices are aggregated at TetherUE, and TetherUE initiates PDU session establishment and QoS flow to the 5G system (5GSystem, 5GS).

[0198] Optionally, the TetherUE can identify and label PDUsets in the uplink direction, supporting the gNB in ​​implementing PDUset QoS processing. Furthermore, the TetherUE can initiate a BSR to the gNB to request uplink transmission resources on the Uu interface based on the data volume generated by the service processing device.

[0199] Optionally, in the downlink direction, the TetherUE can further monitor the PSDB parameters based on the PDU set QoS processing already performed by the gNB. If a data packet is found to have exceeded the PSDB, it can be discarded by the TetherUE.

[0200] In some optional embodiments, the following new functions are introduced into the functions of AF and PCF, but not limited to: when AF generates QoS requirements and PCF generates Policy Control and Charging (PCC) rules, QoS parameter generation is optimized in combination with factors such as the delay increase caused by Tether, including but not limited to: according to the value of the delay increase caused by Tether, the delay requirements for the 5GC+Uu part are increased to meet the end-to-end delay requirements.

[0201] Optionally, when enabling QoS monitoring or ECN marking for L4S, the Tether feature can be configured. For example, the performance impact caused by WLAN access can be incorporated into the Uu port performance, or separately provided to the AF, UPF, or other core network elements.

[0202] In some optional embodiments, the SMF may introduce, but is not limited to, the following new functions: when configuring QoS profiles, QoS rules, and N4 rules (N4 rules are QoS processing related information sent to the UPF), optimization may be performed based on the Wi-Fi access characteristics of the TetherUE. Specifically, when the SMF configures the QoS profile for the gNB, it may instruct the gNB to allocate more radio transmission resources to the TetherUE carrying more traffic based on the traffic load of the service packets carried by the TetherUE. The SMF may also determine whether the gNB still performs PDUset downlink processing based on whether the TetherUE has PDUset downlink processing capability.

[0203] Optionally, when the SMF configures a QoS rule for a Tether UE, it may allocate more wireless transmission resources to the Tether UE carrying more traffic, taking into account the traffic load of the service data packets carried by the Tether UE.

[0204] In some optional embodiments, to implement the QoS monitoring function, TetherUE can monitor information such as round-trip time (RTT), data rate, congestion, etc. according to the QoS monitoring related rules generated by the core network, and report it to the core network element (such as AF).

[0205] Optionally, RTT can be monitored by monitoring the Uu port and 5GC delay of the Tether UE, and taking into account the delay of the Tether link (i.e., the link between the Tether UE and the service processing device). Optionally, the delay of the Tether link can be added to the delay of the Uu port, or it can be added to the total delay.

[0206] Optionally, datarate monitoring can monitor the rate bottleneck of the TetherUE's Uu port and the Tether link. If the TetherUE can identify the rate bottleneck as the Uu port, it can report it to the QoS monitoring network element (such as the gNB). If the TetherUE bottleneck is in the WLAN access Tether link, it can be resolved through dynamic channel selection or other methods.

[0207] As shown in FIG10 , the QoS monitoring process according to an embodiment of the present application may include the following steps:

[0208] S1001: AF initiates a QoS monitoring request.

[0209] Optionally, the AF may indicate the indicators to be monitored in the QoS monitoring request, such as monitoring of RTT, congestion, etc.

[0210] S1002: The PCF generates a PCC rule for QoS monitoring according to the QoS monitoring request sent by the AF.

[0211] S1003: PCF configures the PCC rules to SMF.

[0212] S1004: SMF generates a QoS profile for the base station and configures it to the base station through AMF.

[0213] S1005: SMF generates a QoS rule for the Tether UE and configures it to the Tether UE through AMF.

[0214] S1006: Tether UE performs QoS monitoring according to the QoS rule.

[0215] For example, if the AF indicates RTT monitoring, the Tether UE can perform RTT monitoring, including the Uu port delay and Tether link delay of the Tether UE; if the AF indicates congestion monitoring, the Tether UE can perform congestion monitoring, including the Uu port congestion and Tether link congestion of the Tether UE.

[0216] S1007: Tether UE reports the QoS monitoring result to 5GC.

[0217] Optionally, the Tether UE can report the QoS monitoring results of different links to the 5GC separately, or can combine them and report them to the 5GC. For example, if the Tether UE detects both Uu port delay and Tether link delay, the Tether UE can combine the Uu port delay and Tether link delay or report them separately to the 5GC. For another example, if the Tether UE detects both Uu port congestion and Tether link congestion, the Tether UE can combine the Uu port congestion and Tether link congestion or report them separately to the 5GC.

[0218] In summary, the technical solutions of the embodiments of the present application enable terminal devices to establish a wireless local area network, and service processing devices can then access the core network by accessing the wireless local area network. This allows for support for PDU Set QoS in the terminal devices, including uplink or downlink PDU set processing, as well as obtaining the QoS requirements of the service processing devices and assisting in QoS monitoring. The technical solutions of the embodiments of the present application can achieve better QoS support for service processing devices that do not directly access the cellular network through the PDU set mechanism, thereby improving network bandwidth utilization and service processing quality, and better addressing the challenges posed by high-bandwidth interactive services to wireless network transmission.

[0219] It should be noted that the above embodiments are explained by taking the transmission of business data between the business processing device and the business server through the PDUset method as an example, and the processing method when the business processing device and the business server transmit business data through the per-packet method is similar and will not be repeated here. In addition, the wireless LAN established by the terminal device can be a trusted wireless LAN or a wireless LAN that is not certified as trusted. In addition, in addition to establishing a connection with the terminal device through Wi-Fi, the business processing device can also establish a connection with the terminal device through other short-range wireless communication technologies, such as establishing a connection with the terminal device through Bluetooth, ZigBee, etc.

[0220] The following describes an embodiment of the device of the present application, which can be used to implement the QoS processing method in the above embodiment of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the QoS processing method in the above embodiment of the present application.

[0221] Figure 11 shows a block diagram of a QoS processing device according to an embodiment of the present application, which is applied to a terminal device that accesses the core network through an access network element, the terminal device is communicated with a service processing device, and the service processing device interacts with the service server through the terminal device.

[0222] 11 , a QoS processing device 1100 according to an embodiment of the present application includes: an establishing unit 1102 , an acquiring unit 1104 , and a processing unit 1106 .

[0223] Among them, the establishment unit 1102 is configured to establish a protocol data unit PDU session with the core network; the acquisition unit 1104 is configured to obtain QoS rule information for the service processing device and the service server to transmit service data packets based on the PDU session; the processing unit 1106 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 rule information.

[0224] In some embodiments of the present application, based on the aforementioned solution, the establishing unit 1102 is configured to: establish a PDU session with the core network, and the service data packets of different service processing devices correspond to different QoS flows in the PDU session; or

[0225] establishing PDU sessions corresponding to service data packets of different service processing devices with the core network respectively; or

[0226] A PDU session is established with the core network, and service data packets of different service processing devices correspond to the same QoS flow in the PDU session.

[0227] In some embodiments of the present application, based on the aforementioned scheme, the establishing unit 1102 is further configured to: establish a wireless local area network as an access point, and the wireless local area network is used to enable at least one of the business processing devices to access to establish a communication connection between the terminal device and at least one of the business processing devices.

[0228] In some embodiments of the present application, based on the aforementioned solution, the QoS processing device 1100 further includes: an access unit configured to register the wireless local area network with the core network to authenticate the wireless local area network as a trusted wireless local area network; or

[0229] As a wireless local area network that is not authenticated as trustworthy, it accesses the core network through the access network element.

[0230] In some embodiments of the present application, based on the aforementioned scheme, the QoS processing device 1100 also includes: an allocation unit, configured to allocate a network address to the business processing device after the business processing device accesses the wireless local area network, so that the business processing device transmits business data packets with the business server based on the allocated network address.

[0231] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 1106 is further configured to: after receiving the business data packet sent by the business processing device to the business server, convert the network address in the business data packet to obtain a converted business data packet; and transmit the converted business data packet to the business server through the PDU session.

[0232] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 1106 is further configured to: receive a downlink service data packet from the service server; and according to the priority of the downlink service data packet, select a wireless local area network QoS mechanism corresponding to the priority to send the downlink service data packet to the service processing device.

[0233] In some embodiments of the present application, based on the aforementioned scheme, the QoS processing device 1100 also includes: a receiving unit, configured to receive uplink service data packets from the service processing device; a sending unit, configured to send a cache status report to the access network network element based on the number of the uplink service data packets, to request the access network network element to allocate uplink transmission resources to the terminal device.

[0234] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 1106 is configured to discard the corresponding business data packet if at least one of the following situations occurs during the transmission of the business data packet according to the QoS rule 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.

[0235] In some embodiments of the present application, based on the aforementioned scheme, the delay requirement is the delay requirement between the business server and the business processing device; wherein, the delay requirement is obtained based on the delay information between the terminal device and the business processing device and the delay information between the terminal device and the business server.

[0236] In some embodiments of the present application, based on the aforementioned scheme, the acquisition unit 1104 is further configured to: obtain the delay information between the terminal device and the business processing device; the processing unit 1106 is configured to: when monitoring the transmission delay of the business data packet between the business processing device and the business server, determine whether the transmission delay of the business data packet meets the delay requirements contained in the QoS rule information in combination with the delay information.

[0237] In some embodiments of the present application, based on the aforementioned solution, the acquiring unit 1104 is further configured to: acquire delay information between the terminal device and the service processing device; and the QoS processing apparatus 1100 further includes: a sending unit configured to send the delay information to a first core network element, so that a policy control function element generates QoS policy information for processing the service data packet based on the delay information acquired from the first core network element. The QoS rule information is obtained based on the QoS policy information.

[0238] In some embodiments of the present application, based on the above solution, the processing unit 1106 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.

[0239] In some embodiments of the present application, based on the aforementioned solution, the processing unit 1106 is further configured to: perform QoS monitoring processing according to the QoS rule to obtain a QoS monitoring result, where the QoS monitoring result includes at least one of the following: a monitoring result of a communication link between the terminal device and the service processing device, a monitoring result of a communication link between the terminal device and the access network element, and a monitoring result of a core network communication link;

[0240] The QoS processing device 1100 also includes: a sending unit, configured to send the QoS monitoring result to the second core network network element; wherein, if the QoS monitoring result includes multiple link monitoring results, the multiple link monitoring results are sent to the second core network network element separately, or the multiple link monitoring results are merged and sent to the second core network network element.

[0241] In some embodiments of the present application, based on the aforementioned scheme, the processing unit 1106 is further configured to: if it is monitored that the data transmission rate of the communication link between the terminal device and the access network element is less than or equal to a set value, then send a notification message to the network element performing QoS monitoring processing; if it is monitored that the data transmission rate of the communication link between the terminal device and the service processing device is less than or equal to a set value, then adjust the communication channel between the terminal device and the service processing device.

[0242] In some embodiments of the present application, based on the aforementioned solution, the service data packets between the service processing device and the service server are transmitted in the form of data packet sets.

[0243] FIG12 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device is applied to an AF, or may also be applied to other network elements.

[0244] 12 , a QoS processing device 1200 according to an embodiment of the present application includes: a generating unit 1202 and a sending unit 1204 .

[0245] Among them, the generating unit 1202 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, the service processing device is communicated with the terminal device, the terminal device is accessed to the core network through the access network element, and the service processing device interacts with the service server through the terminal device; the sending unit 1204 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 according to the QoS requirement information.

[0246] In some embodiments of the present application, based on the above solution, the generating unit 1202 is configured to generate QoS requirement information for the service data packet in at least one of the following ways:

[0247] Obtaining delay information between the terminal device and the service processing device, and generating the QoS requirement information according to the delay information;

[0248] The QoS requirement information is generated according to QoS parameters and a reporting method of QoS monitoring results. The reporting method of the QoS monitoring results includes: combining and reporting multiple link monitoring results or reporting multiple link monitoring results separately.

[0249] FIG13 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device is applied to a PCF, or may also be applied to other network elements.

[0250] 13 , a QoS processing device 1300 according to an embodiment of the present application includes: an acquiring unit 1302 , a generating unit 1304 , and a sending unit 1306 .

[0251] Among them, the acquisition unit 1302 is configured to obtain QoS requirement information for the service data packet, where the service data packet is a data packet transmitted between the service server and the service processing device, the service processing device is communicated with the terminal device, the terminal device is accessed to the core network through the access network element, and the service processing device interacts with the service server through the terminal device; the generation unit 1304 is configured to generate QoS policy information corresponding to the service data packet according to the QoS requirement information; the sending unit 1306 is configured to send the QoS policy information 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.

[0252] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1304 is configured to generate the QoS policy information corresponding to the service data packet according to at least one of the following methods:

[0253] Obtaining delay information between the terminal device and the service processing device, and generating the QoS policy information according to the QoS requirement information and the delay information;

[0254] The QoS policy information is generated according to a reporting method of the QoS monitoring results and the QoS parameters included in the QoS requirement information. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results in combination or reporting multiple link monitoring results separately.

[0255] FIG14 shows a block diagram of a QoS processing device according to an embodiment of the present application. The QoS processing device is applied to SMF, or may also be applied to other network elements.

[0256] 14 , a QoS processing device 1400 according to an embodiment of the present application includes: a receiving unit 1402 , a generating unit 1404 , and a configuring unit 1406 .

[0257] Among them, the receiving unit 1402 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 device, the service processing device is communicated with the terminal device, the terminal device is accessed to the core network through the access network network element, and the service processing device interacts with the service server through the terminal device; the generating unit 1404 is configured to generate QoS processing related information corresponding to the processing devices of the service data packets according to the QoS policy information; the configuring unit 1406 is configured to configure the QoS processing related information to the processing devices of the service data packets.

[0258] In some embodiments of the present application, based on the aforementioned solution, the generating unit 1404 is configured to generate QoS processing related information corresponding to each type of processing device of the service data packet according to at least one of the following methods:

[0259] generating, according to the load of the uplink service data packets sent by the service processing device and received by the terminal device, QoS configuration information for an access network element, the QoS configuration information being used to instruct the access network element to configure, for the terminal device, wireless transmission resources that match the load;

[0260] generating, based on whether the terminal device has a data packet aggregate processing capability, QoS configuration information for an access network element, the QoS configuration information being used to instruct the access network element whether to perform downlink processing of the data packet aggregate;

[0261] generating, according to the load of the uplink service data packets sent by the service processing device and received by the terminal device, QoS rule information for the terminal device, the QoS rule information being used to configure, for the terminal device, wireless transmission resources that match the load;

[0262] Obtaining delay information between the terminal device and the service processing device, and generating the QoS processing related information according to the QoS policy information and the delay information;

[0263] According to the reporting method of the QoS monitoring results and the QoS parameters contained in the QoS policy information, QoS rule information for the terminal device is generated. The reporting method of the QoS monitoring results includes: reporting multiple link monitoring results together or reporting multiple link monitoring results separately.

[0264] FIG15 shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing an embodiment of the present application. The electronic device may be a terminal device, AF, PCF or SMF in the aforementioned embodiments.

[0265] It should be noted that the computer system 1500 of the electronic device shown in FIG15 is merely an example and should not impose any limitation on the functions and scope of use of the embodiments of the present application.

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

[0267] The following components can be connected to the I / O interface 1505: an input section 1506 including a keyboard, a mouse, and the like; an output section 1507 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 1508 including a hard disk; and a communication section 1509 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to the I / O interface 1505 as needed. Removable media 1511, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1510 as needed, so that computer programs read from the removable media can be installed in the storage section 1508 as needed.

[0268] 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 1509, and / or installed from a removable medium 1511. When the computer program is executed by the central processing unit (CPU) 1501, the various functions defined in the system of the present application are performed.

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

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

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

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

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

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

[0275] For example, the electronic device can be the terminal device in the aforementioned embodiment, then the terminal device can execute the QoS processing method shown in Figure 3; for another example, the electronic device can be an AF, then the AF can execute the QoS processing method shown in Figure 4; for another example, the electronic device can be a PCF, then the PCF can execute the QoS processing method shown in Figure 5; for another example, the electronic device can be an SMF, then the SMF can execute the QoS processing method shown in Figure 6.

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

[0277] 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), characterized in that, The QoS processing method is executed by a terminal device that accesses the core network through an access network element. The terminal device is communicatively connected to a service processing device, and the service processing device performs service interaction with a service server through the terminal device. The QoS processing method includes: Establishing a protocol data unit (PDU) session with the core network; Obtaining QoS rule information for service data packet transmission between the service processing device and the service server based on the PDU session; Performing QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS rule information.

2. The QoS processing method according to claim 1, wherein Establishing a protocol data unit (PDU) session with the core network includes: Establishing one PDU session with the core network, and service data packets of different service processing devices correspond to different QoS flows in the PDU session; or Respectively establishing PDU sessions corresponding to service data packets of different service processing devices with the core network; or Establishing one PDU session with the core network, and service data packets of different service processing devices correspond to the same QoS flow in the PDU session.

3. The QoS processing method according to claim 1 or 2, characterized in that, The QoS processing method further includes: Establishing a wireless local area network (WLAN) as an access point, where the WLAN is used for at least one of the service processing devices to access, so as to establish a communication connection between the terminal device and at least one of the service processing devices.

4. The QoS processing method according to claim 3, wherein The QoS processing method further includes: Registering the WLAN to the core network to authenticate the WLAN as a trusted WLAN; or Acting as a WLAN that is not authenticated as trusted and accessing the core network through the access network element.

5. The QoS processing method according to claim 3 or 4, characterized in that, The QoS processing method further includes: After the service processing device accesses the WLAN, allocating a network address to the service processing device, so that the service processing device transmits service data packets to the service server based on the allocated network address.

6. The QoS processing method according to any one of claims 3-5, characterized in that, The QoS processing method further includes: After receiving a service data packet sent by the service processing device to the service server, performing conversion processing on the network address in the service data packet to obtain a converted service data packet; Transmitting the converted service data packet to the service server through the PDU session.

7. The QoS processing method according to any one of claims 3-6, characterized in that, The QoS processing method further includes: Receiving a downlink service data packet from the service server; According to the priority of the downlink service data packet, selecting a WLAN QoS mechanism corresponding to the priority to send the downlink service data packet to the service processing device.

8. The QoS processing method according to any one of claims 1-7, characterized in that, The QoS processing method further includes: Receiving an uplink service data packet from the service processing device; According to the quantity of the uplink service data packets, sending a buffer status report to the access network element to request the access network element to allocate uplink transmission resources to the terminal device.

9. The QoS processing method according to any one of claims 1-8, characterized in that Performing QoS processing on the service data packet transmission process between the service processing device and the service server according to the QoS rule information includes: If at least one of the following situations occurs during the transmission of the service data packet as monitored according to the QoS rule information, the corresponding service data packet shall be discarded: Congestion occurs during the transmission of the service data packet, the transmission delay information of the service data packet fails to meet the delay requirement, the bit error rate of the service data packet fails to meet the bit error rate requirement, or the service data packet is determined to be a useless redundant packet.

10. The method according to claim 9, characterized in that, The delay requirement is the delay requirement between the service server and the service processing device; Among them, the delay requirement is obtained based on the delay information between the terminal device and the service processing device and the delay information between the terminal device and the service server.

11. The QoS processing method according to any one of claims 1-10, characterized in that, The QoS processing method further includes: Obtaining the delay information between the terminal device and the service processing device; When monitoring the transmission delay of the service data packet between the service processing device and the service server, determining whether the transmission delay of the service data packet meets the delay requirement included in the QoS rule information in combination with the delay information.

12. The QoS processing method according to any one of claims 1-10, characterized in that, The QoS processing method further includes: Obtaining the delay information between the terminal device and the service processing device; Sending the delay information to a first core 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 first core network element; Among them, the QoS rule information is obtained based on the QoS policy information.

13. The QoS processing method according to any one of claims 1-12, characterized in that, The QoS processing method further includes: If it is monitored that congestion occurs in the service data packet between the service processing device and the service server, perform an explicit congestion notification ECN marking on the service data packet.

14. The QoS processing method according to any one of claims 1-13, characterized in that, The QoS processing method further includes: Performing QoS monitoring processing according to the QoS rule to obtain a QoS monitoring result, where the QoS monitoring result includes at least one of the following: the communication link monitoring result between the terminal device and the service processing device, the communication link monitoring result between the terminal device and the access network element, and the monitoring result of the core network communication link; Sending the QoS monitoring result to a second core network element; among them, if the QoS monitoring result includes multiple link monitoring results, the multiple link monitoring results are respectively sent to the second core network element, or the multiple link monitoring results are merged and then sent to the second core network element.

15. The QoS processing method according to any one of claims 1-14, characterized in that, The QoS processing method further includes: If it is monitored that the data transmission rate of the communication link between the terminal device and the access network element is less than or equal to a set value, send a notification message to the network element performing the QoS monitoring processing; If it is monitored that the data transmission rate of the communication link between the terminal device and the service processing device is less than or equal to a set value, adjust the communication channel with the service processing device.

16. A QoS processing method, characterized in that, The QoS processing method is executed by an application function network element, and the QoS processing method includes: 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, the service processing device is communicatively connected to a terminal device, the terminal device accesses a core network through an access network element, and the service processing device performs service interaction with the service server through the terminal device; 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.

17. The QoS processing method according to claim 16, wherein Generate QoS requirement information for service data packets, including at least one of the following methods: Obtain delay information between the terminal device and the service processing device, and generate the QoS requirement information according to the delay information; Generate the QoS requirement information according to QoS parameters and a reporting method for QoS monitoring results, where the reporting method for QoS monitoring results includes: reporting a combination of multiple link monitoring results or reporting multiple link monitoring results separately.

18. A QoS processing method, characterized in that, The QoS processing method is executed by a policy control function network element, and the QoS processing method includes: 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, the service processing device is communicatively connected to a terminal device, the terminal device accesses a core network through an access network element, and the service processing device performs service interaction with the service server through the terminal device; Generate QoS policy information corresponding to the service data packets according to the QoS requirement information; 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 for a processing device of the service data packets according to the QoS policy information.

19. The method according to claim 18, wherein The generating QoS policy information corresponding to the service data packets according to the QoS requirement information includes at least one of the following methods: Obtain delay information between the terminal device and the service processing device, and generate the QoS policy information according to the QoS requirement information and the delay information; Generate the QoS policy information according to the reporting method for QoS monitoring results and QoS parameters included in the QoS requirement information, where the reporting method for QoS monitoring results includes: reporting a combination of multiple link monitoring results or reporting multiple link monitoring results separately.

20. A QoS processing method, characterized in that, The QoS processing method is executed by a session management function network element, and the QoS processing method includes: 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, the service processing device is communicatively connected to a terminal device, the terminal device accesses a core network through an access network element, and the service processing device performs service interaction with the service server through the terminal device; Generate QoS processing-related information corresponding to a processing device of the service data packets according to the QoS policy information; Configure the QoS processing related information to the processing device of the service data packet.

21. The method according to claim 20, wherein Generating the QoS processing related information corresponding to each type of processing device of the service data packet according to the QoS policy information includes at least one of the following methods: Generate first QoS configuration information for the access network element according to the load of the uplink service data packet sent by the service processing device received by the terminal device, where the first QoS configuration information is used to instruct the access network element to configure wireless transmission resources matching the load for the terminal device; Generate second QoS configuration information for the access network element according to whether the terminal device has the ability to process a packet set, where the second QoS configuration information is used to instruct whether the access network element performs downlink processing of the packet set; Generate QoS rule information for the terminal device according to the load of the uplink service data packet sent by the service processing device received by the terminal device, where the QoS rule information is used to configure wireless transmission resources matching the load for the terminal device; Obtain the delay information between the terminal device and the service processing device, and generate the QoS processing related information according to the QoS policy information and the delay information; Generate QoS rule information for the terminal device according to the reporting method of the QoS monitoring result and the QoS parameters included in the QoS policy information, where the reporting method of the QoS monitoring result includes: reporting the combined monitoring results of multiple links or reporting the monitoring results of multiple links separately.

22. A QoS processing device, characterized in that, The QoS processing device is applied to a terminal device accessing the core network through an access network element. The terminal device is communicatively connected to a service processing device, and the service processing device performs service interaction with a service server through the terminal device. The QoS processing device includes: A establishing unit, configured to establish a PDU session with the core network; An obtaining unit, configured to obtain QoS rule information for the service data packet transmission between the service processing device and the service server based on the PDU session; 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 rule information.

23. A QoS processing device, 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 a service data packet, where the service data packet is a data packet transmitted between a service server and a service processing device. The service processing device is communicatively connected to a terminal device, and the terminal device accesses the core network through an access network element. The service processing device performs service interaction with the service server through the terminal device; 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 according to the QoS requirement information.

24. A QoS processing device, 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 a service data packet, where the service data packet is a data packet transmitted between a service server and a service processing device, the service processing device is communicatively connected to a terminal device, the terminal device accesses a core network through an access network element, and the service processing device performs service interaction with the service server through the terminal device; A generating unit, configured to generate QoS policy information corresponding to the service data packet 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 for a processing device of the service data packet according to the QoS policy information.

25. A QoS processing device, characterized in that, 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 a service data packet, where the service data packet is a data packet transmitted between a service server and a service processing device, the service processing device is communicatively connected to a terminal device, the terminal device accesses a core network through an access network element, and the service processing device performs service interaction with the service server through the terminal device; A generating unit, configured to generate QoS processing related information corresponding to a processing device of the service data packet according to the QoS policy information; A configuring unit, configured to configure the QoS processing related information for the processing device of the service data packet.

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

27. An electronic device, characterized in that, Including: 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 21.

28. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 21 is implemented.

Images