CN118102382B - Data processing method and related equipment - Google Patents

Abstract

The present application provides a data processing method and related equipment, including: a terminal receives a network-side preconfigured first protocol data unit set importance PSI sent by an access network device, the first PSI is sent by a user plane function UPF network element when receiving a session modification request; the terminal obtains multiple protocol data unit PDUs to be sent, the multiple PDUs include a first PDU that does not belong to the PDU set and a second PDU that belongs to the PDU set, the PDU header of the second PDU includes a second PSI, and the second PSI is the PSI of the PDU set to which the second PDU belongs; when receiving a network congestion event notification, the terminal configures the PSI of the first PDU to be the first PSI; the terminal determines the PSI threshold according to the first PSI, the second PSI and the congestion status, and performs a discard operation on the target PDU in the multiple PDUs whose relationship with the PSI threshold meets the threshold condition. When the network is congested, the method uniformly configures the PSI of the first PDU that does not belong to the PDU set to be the first PSI, so as to achieve reasonable discarding of the PDU, alleviate the congestion level, and ensure the service experience.

Description

A data processing method and related equipment

Technical Field

The present application relates to the field of communication technology, and in particular to a data processing method, an electronic device, a communication system, and a computer-readable storage medium.

Background Art

With the development of mobile communication technology, especially the fifth generation mobile networks (5G) and other new generation mobile communication technologies, the functions of communication systems are constantly being enhanced. Specifically, 5G communication systems can provide enhanced mobile broadband (eMBB), with faster connections, higher throughput and greater capacity, as well as ultra-reliable low-latency communications (uRLLC), so that the network can be applied to mission-critical scenarios that require uninterrupted and stable data links, such as extended reality (XR) scenarios or cloud gaming scenarios, meeting the ultra-high reliability and low latency requirements of wireless communication networks in these scenarios.

A service flow of an application may include multiple data packets, including but not limited to Real-time Transport Protocol (RTP), Real-time Transport Control Protocol (RTCP), Session Traversal Utilities for NAT (STUN), Datagram Transport Layer Security- Secure Real-time Transport Protocol (DTLS-SRTP), or WebRTC data channel. For example, a service flow of an XR application may be a video stream, which may include Protocol Data Units (PDUs) in both RTP and RTCP formats, where RTP carries video frame data and RTCP carries control information.

Among them, the PDU header in RTP format carries PDU Set related information, such as PDU Set Importance (PSI), while the RTCP header does not contain PSI. When the network indicates that a congestion event has occurred in the UE, the UE will perform a PSI-based discard operation to alleviate the congestion. However, for RTCP or other formats of data packets that do not include PDUSet related information, since they do not contain PSI, it is difficult for the UE to perform PSI-based discard, affecting the service experience.

Summary of the invention

The present application provides a data processing and related equipment, which aims to solve the problem that data packets in a service flow do not include information such as PSI, which makes it difficult for UE to perform PSI-based discarding, affecting the service experience.

In order to achieve the above objectives, this application provides the following technical solutions:

The first aspect of the present application provides a data processing method. The method can be executed by a terminal. The terminal can be a user device, a mobile station or a user agent, or a user apparatus. Taking the user device as an example, the user device can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an extended reality (XR) terminal, a wireless terminal in industrial control, a tactile terminal device, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, etc.

Specifically, the terminal receives the first protocol data unit set importance PSI pre-configured on the network side sent by the access network device. The first PSI is sent by the user plane function UPF network element when it receives a session modification request. Then the terminal obtains multiple protocol data unit PDUs to be sent. The multiple PDUs include a first PDU that does not belong to the PDU set and a second PDU that belongs to the PDU set. The PDU header of the second PDU includes a second PSI, and the second PSI is the PSI of the PDU set to which the second PDU belongs. When receiving a network congestion event notification, the terminal configures the PSI of the first PDU to the first PSI. The terminal determines the PSI threshold based on the first PSI of the first PDU, the second PSI of the second PDU, and the congestion status, and performs a discard operation on the target PDU among the multiple PDUs. Among them, the relationship between the PSI of the target PDU and the PSI threshold meets the threshold condition.

When network congestion occurs, the method uniformly configures the PSI of the first PDU that does not belong to the PDU set as the first PSI. In this way, the PDU to be discarded and the number of discards can be determined according to the PSI of each PDU in multiple PDUs, thereby achieving reasonable discard of PDUs, alleviating the congestion level and ensuring service experience.

In some possible implementations, the congestion state is characterized by the data transmission rate and the number of PDUs to be sent in the buffer. The terminal can determine the number of discards based on the data transmission rate and the number of PDUs to be sent in the buffer, and then sort the first PDU and the second PDU from high to low according to the PSI, and determine the PSI threshold based on the discarded number and the sorting result.

In this method, the terminal can determine a reasonable number of discards based on the data transmission rate and the number of PDUs to be sent in the cache, and decide the PDUs to be discarded according to the PSI size, thereby alleviating congestion as much as possible while ensuring the service experience.

In some possible implementations, the terminal may receive a radio resource control (RRC) reconfiguration message sent by an access network device. The RRC reconfiguration message is sent when the access network device establishes a data radio bearer (DRB). The RRC reconfiguration message includes packet data convergence protocol (PDCP) configuration information, and the PDCP configuration information includes a first PSI.

In the method, the core network element carries a predefined first PSI and transmits the first PSI to the access network device. When the access network device establishes the DRB, it transmits the first PSI to the UE so that the terminal performs a discard operation according to the first PSI to alleviate congestion.

In some possible implementations, the terminal may receive a network congestion event notification sent by an access network device, wherein the network congestion event notification includes a first PSI. In this way, the terminal may configure the PSI of the PDU that does not belong to the PDU set as the first PSI according to the network congestion event notification, thereby performing a PSI-based discard operation on multiple PDUs to alleviate congestion.

In some possible implementations, the first PSI is sent by the UPF to the access network device and is saved by the access network device. Specifically, the UPF of the core network can transmit the preconfigured or predefined first PSI to the access network device during the process of establishing a PDU session or QoS flow. The access network device saves the first PSI, thereby sending the first PSI to the terminal when network congestion occurs, so that the terminal configures the PSI of the PDU that does not belong to the PDU set according to the first PSI, thereby achieving unified discarding of multiple PDUs according to the PSI.

In some possible implementations, the terminal may further identify a first PDU from multiple PDUs, the PDU header of the first PDU not including information of a PDU set, and the information of the PDU set including a PSI. In this way, the first PSI may be configured for the first PDU, so that multiple PDUs to be processed are all configured with a PSI, and the terminal may perform PSI-based discarding on multiple PDUs, thereby alleviating congestion.

In some possible implementations, the first PDU includes a PDU in a real-time transport control protocol RTCP format, a network address translation session traversal application STUN format, or a datagram transport layer security-secure real-time transport protocol DTLS-SRTP format. The PDUs in the above formats usually do not belong to a PDU set. The method can implement PSI-based discarding of multiple PDUs by configuring PSI for PDUs in a specific format, thereby alleviating congestion.

In some possible implementations, the multiple PDUs are PDUs in the service flow of the extended reality XR application. The service flow of the XR application usually includes PDUs of multiple formats, some of which include PSI in the PDU header, while other PDUs do not include PSI in the PDU header. When network congestion occurs, the method can configure a first PSI for the PDU that does not include PSI, so as to perform PSI-based discarding on the PDUs in the service flow of the XR application, thereby alleviating congestion.

In some possible implementations, the first PSI configured by the UPF network element for the uplink service is consistent with the third PSI configured by the UPF network element for the downlink service, and the third PSI is the default PSI configured by the UPF network element for the PDU in the downlink service that does not belong to the PDU set.

During the downlink transmission process, the core network also has the problem that the PDU does not include PSI, which makes it impossible to perform PSI-based discard. For this reason, the relevant protocols or proposals have agreed that the UPF should identify such data packets that do not contain PDU Set information, and the UPF should configure a PSI level by default in the GTP-U header. In order to maintain consistency between the terminal and the network side, the UPF of this application delivers the first PSI to the terminal in some way, so that the terminal can remain consistent with the network side when performing PSI-based discard.

In some possible implementations, when the first PSI configured on the network side is a null value, the terminal obtains the first PSI based on a protocol, which can improve availability and reliability.

The second aspect of the present application provides a terminal, comprising: a memory and at least one processor. The memory is used to store programs, and the at least one processor is used to run the programs, so that the terminal implements the data processing method provided by the first aspect of the present application.

The third aspect of the present application provides a communication system, including a terminal and an access network device. The terminal is used to execute the data processing method provided in the first aspect of the present application.

The fourth aspect of the present application is a computer storage medium for storing a computer program, which, when executed, is used to implement the data processing method provided in the first aspect of the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is an exemplary diagram of a communication system architecture disclosed in an embodiment of the present application;

FIG2 is a schematic diagram of a scenario of a multimodal service in a single terminal disclosed in an embodiment of the present application;

FIG3 is a schematic diagram of a scenario of a multi-modal service in multiple terminals disclosed in an embodiment of the present application;

FIG4 is a schematic diagram of a distribution of a PDU disclosed in an embodiment of the present application;

FIG5 is a flow chart of a data processing method disclosed in an embodiment of the present application;

FIG6 is a schematic diagram of an application scenario of a data processing method disclosed in an embodiment of the present application;

FIG7 is a schematic diagram of an application scenario of another data processing method disclosed in an embodiment of the present application;

FIG8 is a diagram showing an example structure of a terminal disclosed in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one, two or more; "and/or" describes the association relationship of the associated objects, indicating that three relationships may exist; for example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the objects associated before and after are in an "or" relationship.

References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

The multiple involved in the embodiments of the present application means greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the words "first", "second", etc. are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system for mobile communications (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), and future communication systems.

In order to meet the challenges of wireless broadband technology and maintain the leading edge of 3GPP network, 3GPP standard group has formulated the next generation mobile communication network architecture (next generation system), called 5G network architecture. This architecture not only supports wireless technologies defined by 3GPP standard group, such as LTE, to access 5G core network (5GC), but also supports non-3GPP access technology to access 5GC through non-3GPP interworking function (N3IWF), trusted non-3GPP gateway function (TNGF), trusted WLAN interworking function (TWIF) or next generation packet data gateway (NG-PDG). Among them, the core network functions are divided into user plane function (UPF) network element and control plane function (CPF) network element. UPF is mainly responsible for packet forwarding, quality of service (QoS) control, billing information statistics, etc. CPF is mainly responsible for user registration and authentication, mobility management, and issuing data packet forwarding policies and QoS control policies to UPF. It can be further subdivided into access and mobility management function (AMF) and session management function (SMF).

The core network equipment includes, for example, a mobility management entity (MME), a broadcast multicast service center (BMSC), etc., or may also include corresponding functional entities in the 5G system, such as a core network control plane (CP) or a user plane (UP) network function, such as SMF, AMF, etc. Among them, the core network control plane can also be understood as a core network control plane function (CPF) entity.

Fig. 1 is an example of a communication system architecture applicable to an embodiment of the present application, wherein the functions of the user equipment and each network entity are as described below.

Terminal: can be called terminal equipment, terminal equipment unit (subscriber unit), terminal equipment station, terminal equipment agent, terminal equipment device, access terminal, terminal in V2X communication, user unit, user equipment (user equipment, UE), user station, mobile station, mobile station (mobile station, MS), remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent or user device.

The user device in the embodiments of the present application may also be a mobile phone, a tablet computer, a computer with wireless transceiver function, a holographic projector, a video player, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an extended reality (XR) terminal, a wireless terminal in industrial control, a tactile terminal device, a vehicle-mounted terminal device, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication device, a cellular phone, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device, a wireless communication device assistant, PDA), handheld devices with wireless communication function, computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolution networks, etc.

Among them, wearable devices can also be called wearable smart devices, which are a general term for the intelligent design of daily wearables and the development of wearable devices, such as XR glasses, gloves, watches, clothing and shoes, etc. Among them, XR glasses can include AR glasses or VR glasses. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that focus on a certain type of application functions and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring. It should be noted that wearable devices, such as XR glasses and other XR devices, can also integrate the functions of smartphones. For example, XR devices can also integrate Subscriber Identity Modules (SIM) or Embedded-SIMs (e SIM) for cellular communication.

Radio access network (RAN): A network composed of multiple 5G-RAN nodes that implements wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management functions. 5G-RAN is connected to UPF through the user plane interface N3 to transmit data from terminal devices; 5G-RAN establishes a control plane signaling connection with AMF through the control plane interface N2 to implement functions such as wireless access bearer control. RAN can be any device with wireless transceiver functions, including but not limited to 5G base stations (5G node base, gNB), evolutionary node base (eNB), wireless access point (WiFi AP), world interoperability for microwave access base station (WiMAX BS), transmission receiving point (TRP), wireless relay node, wireless backhaul node, etc.

The access network device in the embodiment of the present application, that is, the network device of the access network can also be a device used to communicate with the terminal device. The access network device can be a base station (base transceiver station, BTS) in the global system of mobile communication (global system of mobile communication, GSM) system or code division multiple access (code division multiple access, CDMA), or a base station (nodeB, NB) in the wideband code division multiple access (wideband code division multiple access, WCDMA) system, or an evolutionary base station (evolutional node base, eNB) in the LTE system, or a wireless controller in the cloud radio access network (cloud radio access network, CRAN) scenario, or the access network device can be a relay station, access point, vehicle-mounted equipment, wearable device, and access network equipment in the future 5G network or access network equipment in the future evolved PLMN network, etc., and the embodiments of the present application are not limited.

In NR, the functions of the base station are divided into two parts, called centralized unit (CU)-distributed unit (DU) separation. From the perspective of the protocol stack, the CU includes the radio resource control (RRC) layer and the packet data convergence protocol (PDCP) layer of the LTE base station, and the DU includes the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer of the LTE base station. In ordinary 5G base station deployments, the CU and DU can be physically connected through optical fiber, and there is a specially defined F1 interface logically for communication between the CU and DU. From a functional perspective, the CU is mainly responsible for radio resource control and configuration, cross-cell mobility management, bearer management, etc. The DU is mainly responsible for scheduling, physical signal generation and transmission.

Among them, the above-mentioned base stations can be macro base stations, micro base stations, pico base stations, small stations, relay stations, balloon stations, etc.

SMF: Mainly responsible for the control plane functions of terminal device session management, including the selection and control of user plane function (UPF), Internet protocol (IP) address allocation, session QoS management, obtaining policy and charging control (PCC) policy from PCF, etc.

UPF: As the anchor point of the protocol data unit (PDU) session connection, it is responsible for data packet filtering, data transmission/forwarding, rate control, generation of billing information, etc. for terminal devices, and provides connection with the data network (DN).

PCF: Provides configuration policy information for terminal devices and policy information for managing and controlling terminal devices for network control plane elements, such as SMF elements; generates terminal device access policies and QoS flow control policies.

AF: interacts with network elements of the core network to provide some services, for example, interacts with PCF to perform service policy control, interacts with NEF to obtain some network capability information or provide some application information to the network, and provides some data network access point information to PCF to generate routing information for corresponding data services.

The terminal device in the embodiment of the present application is connected to the RAN device by wireless means, and the RAN network element is connected to the 5GC device by wireless or wired means. The 5GC device and the RAN network element can be independent and different physical devices, or the functions of the 5GC device and the logical functions of the RAN network element can be integrated on the same physical device, or the functions of some 5GC devices and some RAN network elements can be integrated on one physical device. The terminal device can be fixed or movable.

5GC equipment mainly includes the above-mentioned PCF network elements, SMF network elements and UPF network elements.

It should be noted that the above-mentioned "network element" may also be referred to as an entity, device, apparatus or module, etc., which is not specifically limited in this application. Moreover, in this application, for the sake of ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the NEF network element is referred to as NEF. In this case, the "NEF" should be understood as the NEF network element or NEF entity. Hereinafter, the description of the same or similar situations is omitted.

It should be noted that the naming of each network element included in Figure 1 is only a name, and the name does not limit the function of the network element itself. In 5G networks and other future networks, the above-mentioned network elements may also have other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or may be other names, etc., which are uniformly explained here and will not be repeated below.

It should be noted that the network elements in Figure 1 do not have to exist at the same time, and the network elements required can be determined according to needs. The connection relationship between the network elements in Figure 1 is not uniquely determined, and can be adjusted according to needs.

It is understandable that the above-mentioned network elements or functions can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms, such as virtualized functions instantiated on cloud platforms.

FIG2 is a schematic diagram of an application scenario applicable to the present application provided by the present application. As shown in FIG2, the embodiment of the present application can be applied to a multimodal business scenario. The multimodal business scenario includes an AF network element and multiple XR devices, such as XR device 1 and XR device 2. Among them, the AF network element can be an XR server, the XR device can be an XR head-mounted display (HMD), an XR glasses, and the XR device can also include a controller, such as a handle. In this example, XR device 1 can be an XR glasses, and XR device 2 can be a handle. The user can wear XR glasses and hold the handle to play cloud games. XRserver can receive video frames (video frame), audio data (audio data), haptic data (haptic data) or pose and control (pose & control) data on the XR device side, such as video frames and audio data collected by XR glasses, and haptic data, pose and control data collected by the handle, and then return the processed video frames, audio data, haptic data or pose and control data to the XR device. Among them, the XR server and XR devices exchange various commands and data through the communication links in the network architecture to form a global control loop.

In multimodal business application scenarios, multiple data streams are required, such as QoS flows, to transmit different data types such as video, audio, touch, or gesture and control. The data streams are correlated in space and time. For example, when the human body touches objects with different surface textures and materials, the touch sensation is also different. There is a certain correlation between tactile data and the surface image of the object, and this correlation is also a specific form of correlation. This correlation between different data streams can assist in data reconstruction, also known as signal reconstruction.

In the example of Figure 2, the data collected by the XR device, such as video frames, audio data, tactile data, gestures and control data, can be transmitted to the access network through the terminal, for example, to the access network device, such as gNB, and the access network device transmits the above data to 5GC through QoS flow, and then 5GC transmits the above data to the XR server. It should be noted that the XR device can also communicate directly with the access network device. For example, when the XR device integrates eSIM, or the function of UE is integrated into the XR device, the XR device can be directly connected to the access network device, and accordingly, the XR device can transmit the collected data directly to the access network device, for example, directly to the access network device in the form of QoS flow without passing through the UE. Alternatively, the terminal can also be located inside the XR device, for example, terminal 1 is located inside XR device 1, terminal 2 is located inside XR device 2, and XR device 1 and XR device 2 interact directly with the access network device.

Correspondingly, the XR server can return a multimodal data stream to the XR device. Specifically, the XR server can first return a multimodal data stream to the 5GC, and the 5GC transmits the multimodal data stream to the access network device in the form of QoS flow. The access network device transmits the multimodal data stream to the corresponding UE, and then the UE transmits the received data stream to the XR device.

It should be noted that FIG. 2 is an example of a multimodal scenario in which multiple XR devices are connected to the network through different terminals, such as an inter-UE multimodal scenario. In other possible implementation methods of the embodiments of the present application, the application scenario of the present application may also include a multimodal scenario in which multiple XR devices are connected to the network through the same terminal, such as an intra-UE multimodal scenario. As shown in FIG. 3, multiple XR devices can be connected to the network through the same terminal, and the terminal can serve as a unified entrance or exit for multiple XR devices to interact with the XR server. Multiple XR devices may include XR device 1 and XR device 2. In the example of FIG. 3, XR device 1 may be XR glasses, which can collect video data and audio data, and XR device 2 may be a handle, which can collect tactile data, gesture and control data. XR device 1 and XR device 2 are connected to the same terminal, and the data collected by XR device 1 and XR device 2 can be transmitted to the access network device through the terminal.

The above-mentioned Figures 2 and 3 are only illustrated with two XR devices as examples, and the present application can be applied to multiple XR devices, not limited to two. Furthermore, the above-mentioned XR devices can also be replaced with other sensor devices, and the present application does not limit this.

Taking XR applications as an example, the service flow of XR applications may include multiple data packets, such as PDUs in RTP, RTCP, STUN, DTLS-SRTP or WebRTC data channel formats. For example, a service flow of an XR application may be a video stream, which may include PDUs in RTP and RTCP formats, where RTP carries video frame data and RTCP carries control information. As shown in Figure 4, the PDU header in RTP format carries PDU Set related information, such as PSI, while the PDU header in RTCP format does not contain information such as PSI.

When the network indicates that a network congestion event has occurred in a terminal (such as a UE), the UE can perform a PSI-based discard operation to alleviate the congestion. However, for RTCP or other formats of PDUs that do not include PDU Set related information, since they do not contain PSI, it is difficult for the UE to perform PSI-based discards, which may result in PDUs that should be discarded first not being discarded, and PDUs that can be discarded later being discarded first, affecting the service experience.

In view of this, the present application provides a data processing method. The method can be executed by a terminal. Specifically, the terminal can receive a first PSI (for example, preconfig-PSI) pre-configured on the network side sent by an access network device (RAN), wherein the first PSI may be sent when the UPF network element receives a session modification request. The terminal obtains multiple PDUs to be sent. The multiple PDUs may include a first PDU that does not belong to a PDU set and a second PDU that belongs to a PDU set. Among them, the PDU header of the second PDU includes a second PSI, and the second PSI is the PSI of the PDU set to which the second PDU belongs. It should be noted that the second PSI carried in the PDU header of the second PDU in different PDU sets may be different. Taking Figure 4 as an example, the PSI of the second PDU in PDU Set1 is 12, and the PSI of the second PDU in PDU Set2 is 9.

When receiving a network congestion event notification, the terminal may configure the PSI of the first PDU as the first PSI, and then determine the PSI threshold according to the first PSI of the first PDU, the second PSI of the second PDU, and the congestion status, and perform a discard operation on the target PDU among the multiple PDUs. The relationship between the PSI of the target PDU and the PSI threshold satisfies the threshold condition. For example, the PSI of the target PDU may be greater than or equal to the PSI threshold.

When network congestion occurs, the method uniformly configures the PSI of the first PDU that does not belong to the PDU set as the first PSI. In this way, the PDU to be discarded and the number of discards can be determined according to the PSI of each PDU in multiple PDUs, thereby achieving reasonable discard of PDUs, alleviating the congestion level and ensuring service experience.

In order to make the technical solution of the present application clearer and easier to understand, the data processing method of the present application is introduced from the perspective of the terminal below.

Referring to the flowchart of a data processing method shown in FIG5 , the method comprises the following steps:

S502: The terminal receives a first PSI pre-configured on the network side and sent by an access network device.

The first PSI is a predefined PSI, and the first PSI may be sent by the UPF network element when receiving a session modification request. For example, the first PSI may be sent by the UPF network element to the access network device through the core network when receiving a session modify request.

The specific manner in which the terminal receives the first PSI is described below.

In some possible implementations, the terminal may receive the first PSI sent by the access network device when the access network device (such as a base station such as a gNodeB) establishes a data radio bearer (DRB). DRB is defined as a radio bearer for user-plane Internet Protocol (IP) data packets only between the air interface of the terminal and the access network device (such as a base station). In the process of establishing a dedicated QoS flow, the UPF may carry the predefined first PSI and transmit the first PSI to the access network device such as the gNodeB. When the gNodeB establishes the DRB, the first PSI may be passed to the terminal such as the UE.

In some other possible implementations, the access network device may send a first PSI to the terminal when the network is congested. Specifically, in the process of establishing a dedicated QoS flow, the UPF carries a predefined first PSI and transmits the first PSI to access network devices such as gNodeB. Access network devices such as gNodeB can save the above-mentioned first PSI. When network congestion occurs, the access network device may send a first PSI to the terminal, for example, it may send a network congestion event notification carrying the first PSI to the terminal. In this way, the terminal can receive the first PSI.

S504: The terminal obtains multiple PDUs to be sent. When receiving a network congestion event notification, execute S506.

Among them, the multiple PDUs can be PDUs in the terminal's buffer. The terminal can read multiple PDUs from the buffer for uplink transmission. Multiple PDUs can be classified according to whether they belong to the PDU Set. Specifically, the multiple PDUs include a first PDU that does not belong to the PDU set and a second PDU that belongs to the PDU set. Among them, the PDU header of the second PDU includes a second PSI, and the second PSI is the PSI of the PDU set to which the second PDU belongs. The PDU header of the first PDU usually does not include PDU Set related information, such as not including PSI.

A network congestion event notification is a message used to notify the network of a congestion event. Specifically, the access network device can determine whether a network congestion event occurs based on the packet loss rate or the transmission delay of the data packet during data transmission. For example, if the packet loss rate is greater than a preset value, or the transmission delay of the data packet is greater than a preset duration, it indicates that a network congestion event occurs. The access network device can send a network congestion event notification to a terminal connected to the access network device.

S506: The terminal configures the PSI of the first PDU as the first PSI.

Considering the network congestion, the terminal can configure the PSI for the first PDU in the multiple PDUs, so as to perform the PSI-based discard operation on the multiple PDUs. In the present application, the terminal can uniformly configure the PSI of the first PDU that does not belong to the PDU Set as the first PSI.

Specifically, the terminal may write the first PSI in the PDU header of the first PDU. For example, the terminal may write the first PSI in a reserved field in the PDU header, or in a field storing information of the PDU Set, thereby configuring the PSI of the first PDU to be the first PSI.

It should be noted that the terminal can identify the first PDU from multiple PDUs, and then configure the PSI of the first PDU as the first PSI. The PDU header of the first PDU does not include PDU Set information, and the PDU Set information includes PSI. Based on this, the terminal can traverse the PDU headers of multiple PDUs, detect whether the PDU header includes PSI, and thus identify the first PDU. For the first PDU, the terminal configures the PSI of the first PDU as the first PSI by writing the first PSI in the PDU header.

Among them, multiple PDUs can be PDUs in the service flow of the application, for example, PDUs in the service flow of the XR application. A service flow of the application may include PDUs in multiple formats, for example, PDUs in RTP format and PDUs in RTCP format. Among them, the PDU header of the PDU in RTP format usually carries PDU Set information, and the PDU header of the PDU in RTCP, STUN, or DTLS-SRTP format usually does not carry PDU Set information. Based on this, the first PDU may include a PDU in RTCP format, STUN format, or DTLS-SRTP format.

S508: The terminal determines a PSI threshold according to the first PSI of the first PDU, the second PSI of the second PDU, and the congestion status.

The PSI threshold is a PSI value used to determine whether to discard a PDU. In some examples, the smaller the PSI value, the higher the priority and the later it is discarded. In this case, the terminal can discard the PDU whose PSI is greater than or equal to the PSI threshold.

Specifically, the congestion state can be characterized by the data transmission rate and the number of PDUs to be sent in the cache. The terminal can determine the number of discards based on the data transmission rate and the number of PDUs to be sent in the cache. Among them, the terminal can model the number of discards, and the model takes the data transmission rate and the number of PDUs to be sent in the cache as inputs and the number of discards as outputs. When the data transmission rate is low and the number of PDUs to be sent in the cache is large, it means that the congestion is serious. The terminal can determine a larger number of discards to reduce the degree of congestion and alleviate the congestion. When the data transmission rate is high and the number of PDUs to be sent in the cache is small, it means that the congestion is slight. The terminal can determine a smaller number of discards. Then the terminal can sort the first PDU and the second PDU from high to low according to the PSI, and determine the PSI threshold according to the number of discards and the sorting result.

For ease of understanding, an example is provided below. In this example, the number of discards may be N, and multiple PDUs (including the first PDU and the second PDU) may be sorted from high to low according to PSI. The PSI of the PDU ranked N is i, and the PSI of the PDU ranked N+1 is j. If i is not equal to j, the PSI threshold may be determined to be i.

S510: The terminal discards a target PDU among multiple PDUs.

The relationship between the PSI of the target PDU and the PSI threshold satisfies the threshold condition. For example, the smaller the PSI, the higher the priority and the later it is discarded. The threshold condition may be that the PSI is greater than or equal to the PSI threshold. Based on this, the terminal may compare the PSI of each PDU in multiple PDUs with the PSI threshold to determine the target PDU, wherein the target PDU may be a PDU whose PSI is greater than the PSI threshold. The terminal may then perform a discard operation on the target PDU.

Based on the above description, it can be known that the data processing method of the present application identifies the first PDU that does not belong to the PDU set, and when the network is congested, uniformly configures the PSI of the first PDU as the first PSI, so as to perform a discard operation according to the PSI of each PDU in multiple PDUs, thereby realizing reasonable discard of the PDU, alleviating the degree of congestion, and ensuring service experience.

In order to make the technical solution of the present application clearer and easier to understand, the data processing method of the present application is described in detail below in combination with specific application scenarios.

In the first scenario, a terminal (such as UE) and an application server (such as AF) establish a PDU session. The PDU session can be the process of establishing communication between the UE and the AF. For services with higher quality of service requirements, the process of establishing communication between the UE and the AF can establish a QoS flow. For example, in the XR scenario, for the service flow of multi-person collaborative XR applications, the network side (such as the core network) can create a new QoS flow to carry voice calls or video calls instead of using the default QoS flow for carrying. When the UE successfully establishes a PDU session with the AF, the UPF carries the predefined first PSI and transmits the first PSI to the gNodeB. When the gNodeB establishes the DRB, it passes the first PSI to the UE so that the UE can perform a discard operation based on the first PSI to alleviate congestion.

The following is a detailed description with reference to the accompanying drawings.

Referring to FIG6 , a data processing method is shown in an application scenario diagram, which specifically includes the following steps:

S600: UE and AF successfully establish a PDU session.

S602: UE sends service initialization signaling to AF.

The service initialization signaling may be a service initialization signaling. Specifically, the service initialization signaling may be an initial access signaling, which is used to implement the initial access of the UE in a communication system such as a 5G communication system.

S604: AF sends an identity authentication and authorization request to PCF.

The Authentication-Authorization-Request (AAR) is used to request identity authentication or authentication of the UE, and to authorize the UE and allow access if the authentication is successful.

S606: SMF initiates a session management policy association modification (SM Policy association modification) to PCF.

Specifically, SMF requests PCF to establish an SM policy for the PDU session. Afterwards, SMF performs operations such as data packet detection, QoS Flow binding, and mapping based on the information obtained from PCF. Among them, SMF selects the PCF that serves the PDU session, and then initiates the SM Policy Association Establishment process to the PCF to establish an SM policy association (SM Policy Association), and downloads the corresponding session rules, policy control and charging (PCC) rules, etc. If the Request Type of the PDU session is "Existing PDU Session", SMF can initiate the SM Policy Association Modification process to the PCF that originally served the PDU Session.

S608. SMF sends an N4 session modification request to UPF.

In the process of establishing a PDU session, an N4 session, also known as a Packet Forwarding Control Protocol (PFCP) session, is established simultaneously. The PFCP session is specifically a communication session between the SMF and the UPF. The PCFP session uses PFCP to define a series of actions that the UPF performs on the PDU, including but not limited to identification, forwarding, caching, marking, reporting, and multi-access.

When one or more QoS parameters between a user (such as a UE) and a network change, a PDU session modification action occurs. In this embodiment, the SMF may generate an N4 session modification request (N4 session modify request) based on the SM Policy association modification sent by the PCF to request modification of the N4 session.

S610. UPF sends an N4 session modification response to SMF.

Specifically, the UPF may identify the N4 session context that needs to be modified based on the N4 session ID, and then update the parameters of the N4 session context using the parameter list sent by the SMF, such as the parameter list in the N4 session modification request. Then, the UPF may generate an N4 session modification response. It should be noted that the N4 session modification response may include any information that the UPF is to provide in response to the received control information.

S612. SMF sends a Namf_communication_N1N2MsgTransfer message to AMF.

Msg can be the full name of the message. Similar to the aforementioned session modification response, Namf_communication_N1N2MsgTransfer can carry the first PSI, such as preconfig-PSI.

In some possible implementations, the Namf_communication_N1N2MsgTransfer message may further include a PDU session ID, a QoS flow identifier (QoS Flow Identifier, QFI), and a QoS profile.

S614. AMF sends an N2 message to gNodeB.

The N2 interface is the interface between gNodeB and AMF. The N2 process can be divided into Class 1 and Class 2. Class 1 requires a response, while Class 2 does not require a response. After the PDU session is established, common N2 processes may include: the network side decides to adjust the UE's QoS or other parameters, triggering PDU session resource modification. N2 process related messages (i.e., N2 message) may include PDUSession Resource Modify Request and PDU Session Resource Modify Response.

In the present application, the N2 message may include PDU session ID, QFI, QoS profile. Similar to the aforementioned message, the N2 message may also carry preconfig-PSI so that the UE may uniformly perform PSI-based discarding on multiple PDUs.

S616. gNodeB sends an RRC reconfiguration message to the UE.

The RRC reconfiguration message may be recorded as RRCReconfiguration. The RRC reconfiguration message may be sent when an access network device (such as gNodeB) establishes a DRB (add DRB). The RRC reconfiguration message includes packet data convergence protocol PDCP configuration information, wherein the PDCP configuration information includes a first PSI, such as preconfig-PSI.

S618. The UE receives the network congestion event notification and configures the PSI of the PDU that does not belong to the PDU Set as preconfig-PSI.

S620: The UE performs a PSI-based discard operation according to the PSI and congestion status of each PDU.

The specific implementation of UE configuring PSI and performing PSI-based discarding operation according to PSI and congestion status of PDU can be found in the description of the relevant contents of the embodiment of FIG. 5 , which will not be repeated here.

In the second scenario, the UE and AF establish a PDU session. For services with higher quality of service requirements, the process of establishing communication between the UE and AF can establish a QoS flow. The QoS flow can be a default QoS flow. Different from the first scenario in which the gNodeB passes the preconfig-PSI to the UE when establishing the DRB, in the second scenario, the gNodeB passes the preconfig-PSI to the UE when network congestion occurs, so that the UE can perform a discard operation according to the preconfig-PSI to alleviate the congestion.

Referring to FIG. 7 , a data processing method is shown as an application scenario diagram, which specifically includes the following steps:

S700: UE and AF successfully establish a PDU session.

S702: UE sends service initialization signaling to AF.

S704. AF sends an identity authentication and authorization request to PCF.

S706. SMF initiates a session management policy association modification (SM Policy association modification) to PCF.

S708. SMF sends an N4 session modification request to UPF.

S710. UPF sends an N4 session modification response to SMF.

S712. SMF sends a Namf_communication_N1N2MsgTransfer message to AMF.

S714. AMF sends an N2 message to gNodeB.

S716. gNodeB saves the preconfig-PSI in the N2 message.

S718. The gNodeB sends a network congestion event notification to the UE. The network congestion event notification carries the preconfig-PSI.

S720. The UE receives a network congestion event notification and configures the PSI of the PDU that does not belong to the PDU Set as preconfig-PSI.

S722: The UE performs a PSI-based discard operation according to the PSI and congestion status of each PDU.

It should be noted that when the first PSI configured on the network side (such as preconfig-PSI) is a null value, or the first PSI is not configured on the network side, the terminal can also obtain the first PSI based on the protocol. When the terminal receives a notification of a network congestion event, the PSI of the PDU that does not belong to the PDU Set among multiple PDUs is configured as the first PSI agreed upon in the above protocol. In this way, the PDU to be discarded and the number of discards are determined based on the PSI of each PDU among multiple PDUs, thereby achieving reasonable discard of PDUs, alleviating the degree of congestion, and ensuring service experience.

Based on the aforementioned data processing method, the present application also provides an electronic device for executing the aforementioned data processing method. The electronic device may be a terminal, including but not limited to mobile phones, smart wearable devices (such as smart watches) and other electronic devices. Taking a mobile phone as an example, referring to FIG8 , the electronic device may include a processor 310, an external memory interface 320, an internal memory 321, a display screen 330, a camera 340, an antenna 1, an antenna 2, a mobile communication module 350, and a wireless communication module 360, etc.

It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

The processor 310 may include one or more processing units, for example, the processor 310 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

It is understandable that the interface connection relationship between the modules illustrated in this embodiment is only a schematic illustration and does not constitute a structural limitation of the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 310 through the external memory interface 320 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

The internal memory 321 can be used to store computer executable program codes, and the executable program codes include instructions. The processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory 321. The internal memory 321 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, a phone book, etc.), etc. In addition, the internal memory 321 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory 321, and/or the instructions stored in the memory provided in the processor.

The wireless communication function of the electronic device can be implemented through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor.

Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

The mobile communication module 350 can provide solutions for wireless communications including 2G/3G/4G/5G, etc., applied to electronic devices. The mobile communication module 350 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the processor 310. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the same device as at least some of the modules of the processor 310.

In some embodiments, the electronic device initiates or receives a call request through the mobile communication module 350 and the antenna 1 .

In addition, an operating system is running on the above components. For example, an iOS operating system, an Android operating system, a Windows operating system, etc. Applications can be installed and run on the operating system. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the explanation and beneficial effects of the relevant contents in any of the electronic devices provided above can refer to the corresponding method embodiments provided above, and will not be repeated here.

The present application also provides a communication system, which may include a terminal and an access network device (eg, a base station) as shown in FIG. 8 .

In this application, a terminal or access network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the part of the technical solution of the present application that essentially contributes or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the process of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories, random access memories, magnetic disks or optical disks.

As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments can still be modified, or some of the technical features therein can be replaced by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims (12)

1. A data processing method, characterized in that the method comprises: The terminal receives the importance of the first protocol data unit set PSI pre-configured on the network side sent by the access network device, and the first PSI is sent by the user plane function UPF network element when receiving the session modification request; The terminal obtains a plurality of protocol data units (PDUs) to be sent, the plurality of PDUs including a first PDU that does not belong to a PDU set and a second PDU that belongs to a PDU set, a PDU header of the second PDU including a second PSI, and the second PSI is a PSI of the PDU set to which the second PDU belongs; Upon receiving a network congestion event notification, the terminal configures the PSI of the first PDU as the first PSI; The terminal determines a PSI threshold based on the first PSI of the first PDU, the second PSI of the second PDU and the congestion status, and performs a discard operation on a target PDU among the multiple PDUs, and a relationship between the PSI of the target PDU and the PSI threshold satisfies a threshold condition, wherein the congestion status is characterized by a data sending rate and the number of PDUs to be sent in a cache. 2. The method according to claim 1, wherein the congestion state is characterized by a data transmission rate and a number of PDUs to be sent in a buffer, and the terminal determines a PSI threshold according to a first PSI of the first PDU, a second PSI of the second PDU, and the congestion state, comprising: The terminal determines the discarded quantity according to the data transmission rate and the quantity of PDUs to be sent in the buffer; The terminal sorts the first PDU and the second PDU from high to low according to the PSI, and determines the PSI threshold according to the discarded quantity and the sorting result. 3. The method according to claim 1, wherein the terminal receives a first PSI pre-configured on the network side and sent by the access network device, comprising: The terminal receives a radio resource control (RRC) reconfiguration message sent by the access network device, where the RRC reconfiguration message is sent when the access network device establishes a data radio bearer (DRB), and the RRC reconfiguration message includes packet data convergence protocol (PDCP) configuration information, and the PDCP configuration information includes the first PSI. 4. The method according to claim 3, characterized in that the terminal receives the first PSI pre-configured on the network side and sent by the access network device, comprising: The terminal receives a network congestion event notification sent by the access network device, where the network congestion event notification includes the first PSI. 5. The method according to claim 4 is characterized in that the first PSI is sent by the UPF network element to the access network device and then saved by the access network device. 6. The method according to any one of claims 1 to 5, characterized in that the method further comprises: The terminal identifies the first PDU from the plurality of PDUs, the PDU header of the first PDU does not include information of a PDU set, and the information of the PDU set includes a PSI. 7. The method according to any one of claims 1 to 5 is characterized in that the first PDU includes a PDU in a real-time transport control protocol RTCP format, a network address translation session traversal application STUN format, or a datagram transport layer security-secure real-time transport protocol DTLS-SRTP format. 8. The method according to any one of claims 1 to 5 is characterized in that the multiple PDUs are PDUs in the business flow of extended reality XR applications. 9. The method according to any one of claims 1 to 5 is characterized in that the first PSI configured by the UPF network element for the uplink service is consistent with the third PSI configured by the UPF network element for the downlink service, and the third PSI is the default PSI configured by the UPF network element for the PDU in the downlink service that does not belong to the PDU set. 10. The method according to any one of claims 1 to 5, characterized in that the method further comprises: When the first PSI configured on the network side is a null value, the terminal obtains the first PSI based on a protocol. 11. A terminal, characterized in that the terminal comprises: Memory for storing computer programs or computer instructions; A processor, configured to execute a computer program or computer instruction stored in the memory, so that the terminal executes the method according to any one of claims 1 to 10. 12. A computer storage medium, characterized in that the computer storage medium is used to store a computer program, and when the computer program is executed, it is used to implement the method according to any one of claims 1 to 10.