Ursp rule optimization method, apparatus, terminal, network side device and medium

Abstract

The application discloses a URSP rule optimization method, and belongs to the technical field of communication. The URSP rule optimization method comprises the following steps: a first communication device reevaluates a first URSP rule of a terminal based on target information, and obtains a second URSP rule; and the first communication device sends a first message to the terminal. The target information comprises at least one of the following: a first analysis result, a first evaluation request and abnormal indication information. The first analysis result is an analysis result and / or a prediction result requested by the first communication device, the first evaluation request is used for the terminal to request reevaluation of the first URSP rule, and the abnormal indication information indicates that the first URSP rule is abnormal. The first message comprises the second URSP rule. The second URSP rule is used for the terminal to select and / or establish a PDU session for the traffic of an application.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a URSP rule optimization method, apparatus, terminal, network-side equipment, and medium. Background Technology

[0002] User equipment route selection policy (URSP) rules are strategies defined in the 3rd Generation Partnership Project (3GPP) protocol for terminals to select and / or establish Protocol Data Unit (PDU) sessions. Currently, terminals can match application-related traffic characteristics acquired with traffic descriptors in the URSP rules, and then select and / or establish corresponding PDU sessions for the application based on the route selection descriptor (RSD) under the successfully matched traffic descriptor. How to optimize URSP rules using artificial intelligence technology to intelligently select and / or establish PDU sessions for applications has become an urgent problem to be solved. Summary of the Invention

[0003] This application provides a URSP rule optimization method, apparatus, terminal, network-side device, and medium, which can optimize the URSP rules of the terminal through artificial intelligence technology to intelligently select and / or establish PDU sessions for applications.

[0004] In a first aspect, a URSP rule optimization method is provided, comprising: a first communication device re-evaluating a first URSP rule of a terminal based on target information to obtain a second URSP rule; and the first communication device sending a first message to the terminal. The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; and the anomaly indication information indicates an execution anomaly of the first URSP rule; the first message includes the second URSP rule; and the second URSP rule is used by the terminal to select traffic for applications and / or establish PDU sessions.

[0005] Secondly, a URSP rule optimization method is provided, comprising: a terminal receiving a first message from a first communication device, the first message containing a second URSP rule; and the terminal selecting and / or establishing a PDU session for application traffic based on the second URSP rule. The second URSP rule is a URSP rule obtained by re-evaluating the terminal's first URSP rule.

[0006] Thirdly, a URSP rule optimization method is provided, the method comprising: a second communication device receiving a target message from a target device, the target message including a target analysis identifier, the target message being used by the target device to obtain the analysis result and / or prediction result corresponding to the target analysis identifier; the second communication device obtaining the target analysis result based on the target analysis identifier; and the second communication device sending the target analysis result to the target device, the target analysis result being used by the target device to re-evaluate the first URSP rule of the terminal.

[0007] Fourthly, a URSP rule optimization method is provided, the method comprising: a third communication device receiving a fourth message from a first communication device, the fourth message containing a first URSP rule of the terminal; and the third communication device evaluating the execution status of the first URSP rule based on the first URSP rule.

[0008] Fifthly, a URSP rule optimization method is provided, comprising: a fourth communication device receiving an eighth message from a third communication device, the eighth message including a target PDU session identifier; the fourth communication device evaluating the execution status of the terminal's first URSP rule within the target PDU session corresponding to the target PDU session identifier; and the fourth communication device sending a ninth message to the third communication device. Wherein, the target PDU session is a PDU session where traffic of the target application should not exist; the traffic of the target application is the traffic of the terminal performing PDU session matching according to the first URSP rule; and the ninth message is used to indicate an abnormality in the execution of the first URSP rule.

[0009] Sixthly, a URSP rule optimization apparatus is provided, comprising: a processing module for re-evaluating a first URSP rule of a terminal based on target information to obtain a second URSP rule; and a sending module for sending a first message to the terminal. The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is an analysis result and / or prediction result requested by a first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; and the anomaly indication information indicates an execution anomaly of the first URSP rule; the first message includes the second URSP rule, which is used by the terminal to select traffic for applications and / or establish PDU sessions.

[0010] In a seventh aspect, a URSP rule optimization apparatus is provided, the apparatus comprising: a receiving module for receiving a first message from a first communication device, the first message containing a second URSP rule; and a processing module for selecting and / or establishing a PDU session for application traffic based on the second URSP rule, the second URSP rule being: a URSP rule obtained by re-evaluating a first URSP rule of a terminal.

[0011] Eighthly, a URSP rule optimization apparatus is provided, comprising: a receiving module for receiving a target message from a target device, the target message including a target analysis identifier, the target message being used by the target device to obtain analysis results and / or prediction results corresponding to the target analysis identifier; a processing module for obtaining target analysis results based on the target analysis identifier; and a sending module for sending the target analysis results to the target device. The target analysis results are used by the target device to re-evaluate a first URSP rule of the terminal.

[0012] In a ninth aspect, a URSP rule optimization apparatus is provided, the apparatus comprising: a receiving module for receiving a fourth message from a first communication device, the fourth message containing a first URSP rule of a terminal; and a processing module for evaluating the execution status of the first URSP rule based on the first URSP rule.

[0013] A tenth aspect provides a URSP rule optimization apparatus, comprising: a receiving module for receiving an eighth message from a third communication device, the eighth message including a target PDU session identifier; a processing module for evaluating the execution status of a first URSP rule of a terminal within a target PDU session corresponding to the target PDU session identifier; and a sending module for sending a ninth message to the third communication device. The target PDU session is a PDU session where traffic of a target application should not exist; the traffic of the target application is the traffic used by the terminal to match PDU sessions according to the first URSP rule; and the ninth message is used to indicate an abnormality in the execution of the first URSP rule.

[0014] Eleventhly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0015] In a twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first message from a first communication device, the first message containing a second URSP rule; the processor is used to select and / or establish a PDU session for application traffic based on the second URSP rule. The second URSP rule is a URSP rule obtained by re-evaluating the terminal's first URSP rule.

[0016] In a thirteenth aspect, a network-side device is provided, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect, or the steps of the method described in the fifth aspect.

[0017] In a fourteenth aspect, a first communication device is provided, including a processor and a communication interface, wherein the processor is used to re-evaluate a first URSP rule of a terminal based on target information to obtain a second URSP rule; the communication interface is used to send a first message to the terminal. The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; the anomaly indication information indicates an execution anomaly of the first URSP rule; the first message includes the second URSP rule; the second URSP rule is used by the terminal to select traffic for an application and / or establish a PDU session.

[0018] In a fifteenth aspect, a second communication device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a target message from a target device, the target message including a target analysis identifier, the target message being used by the target device to obtain analysis results and / or prediction results corresponding to the target analysis identifier; the processor is used to obtain target analysis results based on the target analysis identifier; the communication interface is also used to send the target analysis results to the target device, the target analysis results being used by the target device to re-evaluate the first URSP rule of the terminal.

[0019] In a sixteenth aspect, a third communication device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a fourth message from a first communication device, the fourth message containing a first URSP rule of the terminal; and the processor is used to evaluate the execution status of the first URSP rule based on the first URSP rule.

[0020] In a seventeenth aspect, a third communication device is provided, including a processor and a communication interface. The communication interface is used to receive an eighth message from the third communication device, the eighth message including a target PDU session identifier. The processor is used to evaluate the execution status of the terminal's first URSP rule within the target PDU session corresponding to the target PDU session identifier. The communication interface is also used to send a ninth message to the third communication device. The target PDU session is a PDU session where traffic from the target application should not exist; the traffic from the target application is the traffic used by the terminal to match PDU sessions according to the first URSP rule; the ninth message is used to indicate an error in the execution of the first URSP rule.

[0021] Eighteenthly, a communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the URSP rule optimization method as described in the second aspect; and the network-side device is configured to perform the steps of the URSP rule optimization method as described in the first aspect, or the steps of the URSP rule optimization method as described in the third aspect, or the steps of the URSP rule optimization method as described in the fourth aspect, or the steps of the URSP rule optimization method as described in the fifth aspect.

[0022] In a nineteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fourth aspect, or the steps of the method described in the fifth aspect.

[0023] In a twentieth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect, or the method as described in the fourth aspect, or the method as described in the fifth aspect.

[0024] In a twenty-first aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect, or the steps of the method as described in the fourth aspect, or the steps of the method as described in the fifth aspect.

[0025] In this embodiment, during the process of a terminal selecting and / or establishing a PDU session for application traffic, the first communication device can re-evaluate the terminal's first URSP rule based on at least one of a first analysis result, a first evaluation request, and anomaly indication information to obtain a second URSP rule. Then, the first communication device sends the second URSP rule to the terminal, enabling the terminal to select and / or establish a PDU session for application traffic according to the second URSP rule. This allows the terminal to more intelligently select and / or establish a PDU session for application traffic based on the optimized URSP rule, thereby matching application traffic to a PDU session with better performance. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of a possible communication system architecture provided in an embodiment of this application;

[0027] Figure 2 One of the flowcharts for an URSP rule optimization method provided in this application embodiment;

[0028] Figure 3 A second schematic flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0029] Figure 4 A third flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0030] Figure 5 A fourth flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0031] Figure 6 Fifth flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0032] Figure 7 A flowchart illustrating a URSP rule optimization method provided in this application embodiment is shown in Figure 6.

[0033] Figure 8 The seventh flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0034] Figure 9 This is the eighth flowchart illustrating a URSP rule optimization method provided in this application embodiment;

[0035] Figure 10 One of the structural schematic diagrams of a URSP rule optimization device provided in this application embodiment;

[0036] Figure 11A second schematic diagram of a URSP rule optimization device provided in this application embodiment;

[0037] Figure 12 A third schematic diagram of a URSP rule optimization device provided in this application embodiment;

[0038] Figure 13 A fourth schematic diagram of a URSP rule optimization device provided in this application embodiment;

[0039] Figure 14 Fifth schematic diagram of a URSP rule optimization device provided in the embodiments of this application;

[0040] Figure 15 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0041] Figure 16 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application;

[0042] Figure 17 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0044] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0045] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description; however, these technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0046] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0047] The following explains some concepts and / or terms involved in the URSP rule optimization method provided in the embodiments of this application.

[0048] 1. URSP rules

[0049] URSP rules are a policy defined in the 3GPP protocol for terminals (such as user equipment (UE)) to select and / or establish PDU sessions. According to URSP rules, terminals can match application traffic to specific PDU sessions.

[0050] For example, when an application on a terminal wants to send traffic to a server, the application can send its traffic characteristics to the terminal, including but not limited to the destination Internet protocol (IP) address and fully qualified domain name (FQDN). The terminal then matches these traffic characteristics against its own URSP rules. The traffic characteristics specified in the URSP rules include the following traffic descriptors:

[0051] 1) Application descriptors: mainly include operating system (OS) identifier and operating system application identifier (OSAPPID);

[0052] 2) IP descriptors: Destination IP triple (IP address or IPv6 network prefix, port number, protocol ID of a protocol above IP);

[0053] 3) Domain descriptors: FQDNs or regular expressions used as domain name matching conditions, mainly FQDNs;

[0054] 4) Non-IP descriptors: Descriptors for the destination information of non-IP traffic;

[0055] 5) Data network name (DNN): This matches the DNN information provided by the application and describes the data network that the application traffic accesses or connects to;

[0056] 6) Connection capabilities: This matches the information provided by the application when requesting a network connection with certain capabilities, such as "IP multimedia subsystem (IMS)," "multimedia messaging service (MMS), such as MMS," and "internet."

[0057] When an application sends traffic to a terminal with an IP descriptor (e.g., a destination IP triplet), the IP descriptor indicates that the application's traffic needs to be sent to a PDU session with a destination IP of 10.1.1.1 and a port number of 80. If the traffic descriptor exists in the terminal's URSP rules, it means that the application's traffic characteristics match a certain URSP rule.

[0058] After the application's traffic characteristics match the URSP rules, the next step is to select the PDU session to send the application's traffic. Generally, a traffic descriptor includes multiple route selection descriptors (RSDs), each representing a set of attributes or parameters for a PDU session. When the application's traffic matches the traffic descriptor set with destination IP = 10.1.1.1 and port number 80, this traffic descriptor set includes the following RSDs (for illustrative purposes only):

[0059] 1) RSD precedence = 1: Single networkslice selection assistance information (S-NSSAI) - a, non-3GPP access;

[0060] 2) RSD precedence = 2: S-NSSAI-a, 3GPP access, DNN = Internet, Session and service continuity (SSC) mode = 3.

[0061] Terminals can select and / or establish PDU sessions for application traffic according to RSD precedence. For example, a terminal can match application traffic to the PDU session corresponding to RSD precedence=1. The characteristics of the PDU session corresponding to RSD precedence=1 are: S-NSSAI=S-NSSAI-a, using non-3GPP access.

[0062] 2. Network Data Analytics Function (NWDAF)

[0063] Currently, the 3GPP protocol incorporates NWDAF for intelligent analysis. NWDAF possesses certain intelligent analysis capabilities, collecting data and using built-in algorithms and analytical capabilities to obtain results, which are then provided to 5G core network elements for operational optimization or statistical analysis.

[0064] For example, NWDAF can provide an observation service experience analysis function, which can collect service quality (QoS) information of a terminal accessing a server, such as uplink or downlink rate, packet loss rate, etc., and output statistical information, which includes the user experience of the terminal accessing the server; or, NWDAF can make predictions based on the historical experience of the terminal accessing the server, for example, what the user experience (e.g. QoS) of the terminal might be if the terminal accesses the server in a certain area at a certain time in the future.

[0065] Typically, the analysis and / or prediction content provided by NWDAF is distinguished by an analysis ID. By sending different analysis IDs and some parameters to NWDAF, NWDAF can provide corresponding analysis and / or prediction results. For example, if analysis ID = Service Experience, then NWDAF provides observation service experience analysis. Therefore, as long as a network element obtains NWDAF service, it can input the analysis ID when requesting analysis or prediction, and NWDAF can provide the corresponding analysis and / or prediction results. The analysis or prediction results corresponding to the analysis IDs that NWDAF can currently provide are shown in Table 1.

[0066] Table 1. Analysis identifiers and corresponding analysis results

[0067]

[0068] It should be noted that in the embodiments of this application, the first communication device can be a PCF or UDM, the second communication device can be an NWDAF, the third communication device can be an SMF, and the fourth communication device can be a UPF. It can also be other network elements with the same function or type. The embodiments of this application do not limit this.

[0069] The technical solutions provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0070] This application provides a URSP rule optimization method, such as... Figure 2 As shown, the method is applied to a first communication device. The URSP rule optimization method provided in this application includes the following steps 201 and 202.

[0071] Step 201: The first communication device re-evaluates the first URSP rule of the terminal based on the target information to obtain the second URSP rule.

[0072] Step 202: The first communication device sends a first message to the terminal.

[0073] The aforementioned target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information. The first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; and the anomaly indication information indicates an anomaly in the execution of the first URSP rule.

[0074] The first message mentioned above contains a second URSP rule; this second URSP rule is used by the terminal to select traffic for the application and / or establish a PDU session.

[0075] In this embodiment, during the process of a terminal selecting and / or establishing a PDU session for application traffic, the first communication device can re-evaluate the terminal's first URSP rule based on at least one of a first analysis result, a first evaluation request, and anomaly indication information to obtain a second URSP rule. Then, the first communication device sends the second URSP rule to the terminal, enabling the terminal to select and / or establish a PDU session for application traffic according to the second URSP rule. This allows the terminal to more intelligently select and / or establish a PDU session for application traffic based on the optimized URSP rule, thereby matching application traffic to a PDU session with better performance.

[0076] Optionally, in this embodiment of the application, the target information may be information received by the first communication device from other devices. Furthermore, the target information may include one or more of the following: a first analysis result, a first evaluation request, and an anomaly indication information.

[0077] Optionally, in this embodiment of the application, the first analysis result can be information received by the first communication device from the second communication device; the first evaluation request can be information received by the first communication device from the terminal; and the anomaly indication information can be information received by the first communication device from the third communication device.

[0078] Optionally, in this embodiment of the application, the first communication device may re-evaluate the first URSP rule based on the first analysis result to obtain the second URSP rule; or, the first communication device may re-evaluate the first URSP rule based on other information to obtain the second URSP rule.

[0079] Optionally, in this embodiment, the other information mentioned above may be terminal contract information, terminal location information, etc., and the specific information can be determined according to actual usage needs. This embodiment does not limit the specific information.

[0080] Optionally, in this embodiment, the first URSP rule is the terminal's original URSP rule, and the second URSP rule is an optimized URSP rule based on the first URSP rule. Compared to the first URSP rule, the second URSP rule can more intelligently select and / or establish appropriate PDU sessions for applications.

[0081] Optionally, in this embodiment of the application, the second URSP rule can be: an updated URSP rule based on the first URSP rule; that is, an URSP rule obtained by adjusting the first URSP rule after the first communication device receives at least one of the first analysis result, the first evaluation request, and the anomaly indication information. Alternatively, the second URSP rule can be: a new URSP rule; that is, the first communication device sends a new URSP rule to the terminal to replace the first URSP rule.

[0082] Optionally, in the embodiments of this application, step 201 can be implemented by the following steps 201a and 201b.

[0083] Step 201a: The first communication device re-evaluates the first URSP rule based on the target information.

[0084] In this embodiment of the application, the above re-evaluation is used to determine whether the first URSP rule needs to be updated.

[0085] Step 201b: When it is necessary to update the first URSP rule, the first communication device performs a target operation on the first URSP rule to obtain the second URSP rule.

[0086] The aforementioned target operations include at least one of the following:

[0087] Adjust the priority of the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0088] Adjust the priority of the first traffic descriptor in the first URSP rule;

[0089] Adjust the parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule;

[0090] Add a new routing descriptor to the first traffic descriptor in the first URSP rule;

[0091] Disable the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0092] Disable the first traffic descriptor in the first URSP rule;

[0093] Generate new URSP rules.

[0094] Optionally, in this embodiment of the application, the first traffic descriptor may be the traffic descriptor corresponding to the parameter with poor performance in the first URSP rule; the first routing descriptor may be the routing descriptor corresponding to the parameter with poor performance in the first traffic descriptor.

[0095] Optionally, in this embodiment of the application, the above-mentioned adjustment of the parameters in the first routing descriptor of the first traffic descriptor in the first URSP rule includes at least one of the following:

[0096] Adjust the access method in the first route selection descriptor and change the access method to the access method whose performance meets the first condition as indicated by the first analysis result;

[0097] Adjust the DNN in the first routing descriptor, and change the DNN to the DNN whose performance, as indicated by the first analysis result, meets the second condition;

[0098] Adjust the S-NSSAI in the first route selection descriptor to change S-NSSAI to the S-NSSAI whose performance, as indicated by the first analysis result, meets the third condition.

[0099] Optionally, in this embodiment of the application, the first condition is that the performance of the access method indicated by the first analysis result is better than the performance of the access method in the first routing descriptor; the second condition is that the performance of the DNN indicated by the first analysis result is better than the performance of the DNN in the first routing descriptor; and the third condition is that the performance of the S-NSSAI indicated by the first analysis result is better than the performance of the S-NSSAI in the first routing descriptor.

[0100] That is, the first communication device can request to analyze the performance of the current S-NSSAI, DNN, and access methods, and adjust the specific parameters in the RSD of the first URSP rule according to the analysis results, so that the traffic of the application on the terminal is matched to the PDU session with better performance.

[0101] For example, taking the target information as the first analysis result, the process of the first communication device performing target operation on the first URSP rule in the URSP rule optimization method provided in the embodiments of this application will be specifically described.

[0102] 1) The target operation includes adjusting the priority of the first routing descriptor in the first traffic descriptor of the first URSP rule.

[0103] In the first traffic descriptor, RSD 1 (e.g., the first routing descriptor) corresponds to 3GPP access (e.g., 5G system (fifth-generation system, 5GS) access), and RSD 2 corresponds to non-3GPP access (e.g., WLAN access). If the performance of the non-3GPP access method indicated by the first analysis result is better than that of the 3GPP access method, the first communication device can increase the priority of RSD 2 and decrease the priority of RSD 1.

[0104] 2) The target operation includes adjusting the priority of the first traffic descriptor in the first URSP rule.

[0105] In the first URSP rule, the first traffic descriptor includes 3GPP access, and the second traffic descriptor includes non-3GPP access. If the performance of the non-3GPP access method, as indicated by the first analysis result, is superior to that of the 3GPP access method, the first communication device can increase the priority of the second traffic descriptor and decrease the priority of the first traffic descriptor. The second traffic descriptor is a traffic descriptor in the first URSP rule other than the first traffic descriptor.

[0106] 3) The target operation includes adjusting the parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule.

[0107] a) Adjust the access method in the first route selection descriptor.

[0108] In the first traffic descriptor, RSD 1 (e.g., the first routing descriptor) corresponds to S-NSSAI-a, DNN=1 and 3GPP access; RSD 2 corresponds to S-NSSAI-a, DNN=1 and WLAN access. If the performance of WLAN access, as indicated by the first analysis result, is superior to that of 3GPP access, the first communication device can change the 3GPP access in the first routing descriptor to WLAN access.

[0109] b) Adjust the DNN in the first routing descriptor

[0110] In the first traffic descriptor, RSD 1 (e.g., the first routing descriptor) corresponds to S-NSSAI-a, DNN=1, and 3GPP access; RSD 2 corresponds to S-NSSAI-a, DNN=2, and WLAN access. If the performance of DNN=2 is better than that of DNN=1 as indicated by the first analysis result, the first communication device can change DNN=1 in the first routing descriptor to DNN=2.

[0111] c) Adjust the S-NSSAI setting in the first route selection descriptor.

[0112] In the first traffic descriptor, RSD 1 (e.g., the first routing descriptor) corresponds to S-NSSAI-b, DNN=1, and 3GPP access; RSD 2 corresponds to S-NSSAI-a, DNN=1, and WLAN access. If the performance of S-NSSAI-a is better than that of S-NSSAI-b as indicated by the first analysis result, the first communication device can change S-NSSAI-b in the first routing descriptor to S-NSSAI-a.

[0113] d) Add new parameters to the first route selection descriptor

[0114] When changing the access method from WLAN access (where SSC mode is not available) to 3GPP access, the first communication device can add SSC mode to the first routing descriptor, that is, specify the SSC mode of the PDU session.

[0115] 4) The target operation includes adding a new route selection descriptor to the first traffic descriptor in the first URSP rule.

[0116] For example, the first communication device can add an RSD related to WLAN access to the first routing descriptor.

[0117] 5) The target operation includes disabling the first routing descriptor in the first traffic descriptor of the first URSP rule.

[0118] In the first traffic descriptor, RSD 1 (e.g., the first routing descriptor) corresponds to 3GPP access (e.g., 5GS access), while RSD 2 corresponds to non-3GPP access (e.g., WLAN access). In cases where 3GPP access performance is poor, the first communication device can disable RSD 1.

[0119] 6) The target operation includes disabling the first traffic descriptor in the first URSP rule.

[0120] In the first URSP rule, the first traffic descriptor includes 3GPP access, and the second traffic descriptor includes non-3GPP access. If the performance of 3GPP access is poor, the first communication device can disable the first traffic descriptor.

[0121] 7) Generate new URSP rules

[0122] When WLAN access performance is superior, the primary communication device can give more consideration to WLAN access when designing URSP rules.

[0123] Optionally, in this embodiment of the application, before step 201 above, the URSP rule provided in this embodiment of the application further includes the following steps 203 and 204.

[0124] Step 203: The first communication device sends a second message to the second communication device.

[0125] In this embodiment of the application, the second message includes a first analysis identifier, which is used to obtain the analysis results and / or prediction results corresponding to the first analysis identifier.

[0126] Step 204: The first communication device receives the third message sent by the second communication device.

[0127] In this embodiment of the application, the third message mentioned above includes the first analysis result corresponding to the first analysis identifier.

[0128] Optionally, in this embodiment, the second message can be a subscription message or a request message, such as Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request, and the third message can be a notification message or a response message, such as Nnwdaf_AnalyticsSubscription_Notify or Nnwdaf_AnalyticsInfo_Response. When the second message is a subscription message, the second communication device notifies the first communication device whenever it detects changes in the access method, data network, etc.; when the second message is a request message, the first communication device sends a request message, and the second communication device replies with a response message.

[0129] Optionally, in this embodiment of the application, the second message may further include a first terminal identifier and / or first location information. When the second message includes a first terminal identifier, the first analysis result is the analysis result corresponding to the terminal indicated by the first terminal identifier; when the second message includes first location information, the first analysis result is the analysis result corresponding to the terminal corresponding to the first location information.

[0130] Optionally, in this embodiment of the application, the first location information can be an area of ​​interest to the first communication device; the terminal corresponding to the first location information can be all terminals within the area of ​​interest to the first communication device.

[0131] It should be noted that this application embodiment is illustrated using a single terminal as an example. For all terminals within the area of ​​interest, the first communication device can employ the URSP rule optimization method provided in this application embodiment to re-evaluate the URSP rules for each terminal. For example, the first communication device requests analysis of the analysis results and / or prediction results corresponding to the analysis identifiers for all terminals within the area of ​​interest.

[0132] Optionally, in this embodiment of the application, the first analysis identifier mentioned above includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0133] Optionally, in the embodiments of this application, step 201 above can be specifically implemented by step 201c below.

[0134] Step 201c: The first communication device re-evaluates the first analysis object in the first URSP rule based on the performance of the first analysis object indicated by the first analysis result, and obtains the second URSP rule.

[0135] The first analysis object mentioned above includes at least one of the following: access method, DN, and slice.

[0136] In this embodiment of the application, the access method, DN, and slice in the first URSP rule can be re-evaluated through access method performance, DN performance, and slice performance.

[0137] Optionally, in this embodiment of the application, when the first analysis identifier is load level information, the first analysis result indicates slice performance; the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0138] When the first analysis identifier is service experience, the first analysis result indicates the performance of the first access method; the first analysis result includes at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, Radio Access Technology (RAT) type, serving cell frequency, access signal quality; and / or,

[0139] When the first analysis is identified as WLAN performance, the first analysis result indicates the performance of the second access method; the first analysis result includes at least one of the following: received signal strength indication (RSSI), uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0140] When the first analysis is identified as DN performance, the first analysis result indicates DN performance; the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metric of the accessed application server address; wherein the performance metric includes at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0141] Understandably, each analysis identifier corresponds to an analysis result indicating the performance of an analyzed object. That is, the first communication device can obtain analysis results indicating slice performance by sending load level information; the first communication device can obtain analysis results indicating the performance of the first access method by sending service experience; the first communication device can obtain analysis results indicating the performance of the second access method by sending WLAN performance; and the first communication device can obtain analysis results indicating DN performance by sending DN performance.

[0142] Optionally, in this embodiment of the application, when the first analysis identifier is service experience, the first analysis result indicates at least one of the following: slice performance, access method performance, and DN performance.

[0143] Where the first analysis result indicates slice performance, the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0144] When the first analysis result indicates access mode performance, the first analysis result includes the performance of the first access mode and / or the performance of the second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0145] In cases where the first analysis result indicates DN performance, the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0146] It is understandable that one analysis identifier corresponds to analysis results indicating the performance of multiple analysis objects. That is, the first communication device can obtain analysis results indicating slice performance, first access method performance, second access method performance, and DN performance by sending service experience.

[0147] It should be noted that, in this embodiment of the application, analysis results indicating the performance of multiple analysis objects can be obtained through a single analysis identifier, thereby improving the efficiency of the first communication device in obtaining analysis results.

[0148] Optionally, in this embodiment of the application, the first access method can be a 3GPP access method (e.g., 5GS access), and the second access method can be a non-3GPP access method (e.g., WLAN access).

[0149] The relevant parameters for different analysis identifiers are illustrated below.

[0150] For example, the relevant parameters for QoS are shown in Table 2.

[0151] Table 2 QoS Parameters and Explanations

[0152]

[0153] For example, the relevant parameters for 5GS access are shown in Table 3.

[0154] Table 3 Parameters and Explanations for 5GS Access

[0155]

[0156]

[0157] For example, the relevant parameters for WLAN access are shown in Table 4.

[0158] Table 4 Parameters and Explanations for WLAN Access

[0159]

[0160] For example, the relevant parameters of the slicing performance are shown in Table 5.

[0161] Table 5. Parameters and descriptions of slice performance

[0162]

[0163] For example, combining Tables 2, 3, and 5, the first communication device subscribes to the analysis corresponding to analytics ID = UE communication or Service Experience to obtain the performance status of 3GPP access. The performance parameters of 3GPP access include: uplink or downlink QoS flow bit rate, uplink or downlink QoS flow packet delay, number of transmitted packets, number of retransmitted packets, reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference plus noise ratio (SINR), etc. The first communication device subscribes to the analysis corresponding to analytics ID = WLANPerformance to obtain the performance status of WLAN access. The performance parameters of WLAN access include: received signal strength indicator (RSSI), round-trip time (RTT), and traffic information; this traffic information includes at least one of the following under the WLAN access point or WLAN network coverage: uplink data rate or downlink data rate, uplink or downlink data traffic, etc.

[0164] Based on the obtained analysis results, the first communication device can compare the performance of 3GPP access and non-3GPP access (such as WLAN access) and select the one with better access performance for terminal access.

[0165] For example, the relevant parameters of DN performance are shown in Table 6.

[0166] Table 6 Parameters and Explanations of DN Performance

[0167]

[0168] For example, referring to Table 6, the first communication device can subscribe to the analysis corresponding to analytics ID = DN performance. Since DN performance can provide data for a specific application server (such as the application server's IP address), including average packet latency, average packet loss rate, throughput, etc., the analysis results and / or prediction results corresponding to DN performance include at least one of the following under the analysis and / or prediction DNN or S-NSSAI: the accessed application server instance address, and the performance metrics of the accessed application server address; these performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate. Therefore, the first communication device can compare the performance of multiple DNs, such as average rate and packet latency, to determine which DN performs better, thus allowing the terminal to access the DN with better performance.

[0169] For example, the relevant parameters of the service experience are shown in Table 7.

[0170] Table 7. Parameters and Explanations of Service Experience

[0171]

[0172]

[0173] For example, the relevant parameters for UE communication are shown in Table 8.

[0174] Table 8 Parameters and Descriptions of UE Communication

[0175]

[0176]

[0177] For example, by combining Tables 5, 6, 7, and 8, the first communication device can subscribe to the analysis corresponding to analytics ID = DNPerformance, UE communication, Service Experience, or load level information to obtain the performance status of multiple slices, such as the current resource usage of the slice, the number of established PDU sessions, the number of registered terminals, and the slice load level. Alternatively, it can compare the performance metrics under each slice, which include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate. Therefore, the first communication device can compare the performance of multiple slices, determine which slice performs better, and thus allow the terminal to access the slice with better performance.

[0178] For example, the relevant parameters for the session management congestion control experience are shown in Table 9.

[0179] Table 9. Parameters and Explanations for Session Management Congestion Control Experience

[0180]

[0181] For example, the relevant parameters of UE mobility are shown in Table 10.

[0182] Table 10 Parameters and Explanations of UE Mobility

[0183]

[0184] Optionally, in the embodiments of this application, step 201 above can be specifically implemented by step 201d below.

[0185] Step 201d: Upon receiving at least one of the first evaluation request and the anomaly indication information, the first communication device re-evaluates the first URSP rule to obtain the second URSP rule.

[0186] Optionally, in this embodiment of the application, when receiving at least one of the first evaluation request and the abnormal indication information, the first communication device can re-evaluate the first URSP rule based on the terminal subscription information, the terminal location information, etc., to obtain the second URSP rule.

[0187] Optionally, in this embodiment of the application, if the first communication device also receives the first analysis result after receiving at least one of the first evaluation request and the anomaly indication information, the first communication device can re-evaluate the first URSP rule based on the first analysis result to obtain the second URSP rule.

[0188] Optionally, in this embodiment of the application, the first evaluation request mentioned above can be a non-access stratum (NAS) message.

[0189] Optionally, in this embodiment of the application, before step 201 above, the URSP rule provided in this embodiment of the application further includes steps 205 and 206 as described below.

[0190] Step 205: The first communication device sends a fourth message to the third communication device.

[0191] In this embodiment of the application, the fourth message includes the first URSP rule, and the fourth message is used to evaluate the execution status of the first URSP rule.

[0192] Step 206: The first communication device receives the abnormal indication information sent by the third communication device.

[0193] In this embodiment of the application, when the first communication device monitors the first URSP rule of the terminal, if the first communication device wants to determine whether the application traffic is correctly matched to the corresponding PDU session, it can send a fourth message to the third communication device so that the third communication device can evaluate the execution status of the first URSP rule of the terminal. If the third communication device determines that the execution of the first URSP rule is abnormal, it sends an abnormal indication message to the first communication device, so that the first communication device can re-evaluate the first URSP rule.

[0194] Optionally, in this embodiment, the fourth message further includes a first IP descriptor, which is used to evaluate the execution status of the first URSP rule. Prior to step 205, the URSP rule provided in this embodiment further includes step 207.

[0195] Step 207: The first communication device maps the first traffic descriptor in the first URSP rule to the first IP descriptor.

[0196] The first traffic descriptor mentioned above includes at least one of the following: application descriptor, domain name descriptor, data network name, and connectivity. The first IP descriptor mentioned above is a destination IP triplet.

[0197] In this embodiment of the application, only IP descriptors (i.e., destination IP address triples) can be used to generate PDRs using UPF or SMF, while other descriptors must first be mapped to IP descriptors before PDRs can be generated.

[0198] Optionally, in this embodiment of the application, the first IP descriptor is used to generate a packet detection rule (PDR) in the UPF. The PDR can be used to evaluate the execution of the first URSP rule, for example, to detect whether the application's traffic has appeared in the PDU session.

[0199] In this embodiment of the application, a new mapping method is introduced, that is, mapping the non-IP descriptors in the first URSP rule to IP descriptors, so that the third communication device evaluates the execution status of the first URSP rule based on the IP descriptor. Thus, when the first communication device receives an anomaly indication information, it re-evaluates the first URSP rule to obtain the second URSP rule, thereby improving the efficiency of the first communication device in optimizing the first URSP rule of the terminal.

[0200] This application provides a URSP rule optimization method, such as... Figure 3 As shown, the method is applied to a terminal. The URSP rule optimization method provided in this application includes the following steps 301 and 302.

[0201] Step 301: The terminal receives the first message from the first communication device.

[0202] In this embodiment of the application, the first message mentioned above includes a second URSP rule.

[0203] Step 302: The terminal selects and / or establishes a PDU session for the application's traffic based on the second URSP rule.

[0204] The second URSP rule mentioned above is the URSP rule obtained after re-evaluating the first URSP rule of the terminal.

[0205] In this embodiment of the application, the terminal can more intelligently select and / or establish PDU sessions for application traffic based on the URSP rules obtained after re-evaluation (i.e., the optimized URSP rules).

[0206] Optionally, in this embodiment of the application, before step 301 above, the URSP rule optimization method provided in this embodiment of the application further includes the following step 303.

[0207] Step 303: The terminal sends a first evaluation request to the first communication device.

[0208] The aforementioned first evaluation request is used to request the first communication device to re-evaluate the first URSP rule.

[0209] Optionally, in this embodiment of the application, the first evaluation request can be sent via a NAS message.

[0210] Optionally, in this embodiment of the application, the NAS message includes at least one of the following:

[0211] Registration request;

[0212] Registration complete;

[0213] PDU session establishment request;

[0214] PDU session modification request;

[0215] PDU session establishment accept;

[0216] PDU session modification command accepted.

[0217] The aforementioned first evaluation request may include the URSP rule that the terminal wishes to re-evaluate. Specifically, the aforementioned first evaluation request includes at least one of the following:

[0218] One or more traffic descriptors to be re-evaluated;

[0219] One or more RSDs under the traffic descriptor to be re-evaluated;

[0220] URSP rules for all terminals.

[0221] Optionally, in this embodiment of the application, before step 303 above, the URSP rule optimization method provided in this embodiment of the application further includes step 304 as described below. Furthermore, step 303 can be specifically implemented through step 303a as described below.

[0222] Step 304: The terminal re-evaluates the first URSP rule based on the second analysis results.

[0223] In this embodiment of the application, the above re-evaluation is used to determine whether the first URSP rule needs to be updated.

[0224] Step 303a: If it is necessary to update the first URSP rule, the terminal sends a first evaluation request to the first communication device.

[0225] The second analysis result mentioned above refers to the analysis result and / or prediction result requested by the terminal.

[0226] Optionally, in this embodiment of the application, the second analysis result can be the analysis result received by the terminal from the second communication device.

[0227] Optionally, in the embodiments of this application, step 304 above can be specifically implemented by step 304a below.

[0228] Step 304a: The terminal re-evaluates the second analysis object in the first URSP rule based on the performance of the second analysis object indicated by the second analysis result.

[0229] The second analysis object mentioned above includes at least one of the following: access method, DN, and slice.

[0230] Optionally, in the embodiments of this application, before step 303 above, the URSP rule optimization method provided in the embodiments of this application further includes the following steps 305 and 306.

[0231] Step 305: The terminal sends the sixth message to the second communication device.

[0232] In this embodiment of the application, the sixth message includes a second analysis identifier, and the sixth message is used to obtain the analysis results and / or prediction results corresponding to the second analysis identifier.

[0233] Step 306: The terminal receives the seventh message sent by the second communication device.

[0234] In this embodiment of the application, the seventh message mentioned above includes the second analysis result corresponding to the second analysis identifier.

[0235] Optionally, in this embodiment, the sixth message can be a subscription message or a request message, and the seventh message can be a notification message or a response message. When the sixth message is a subscription message, the second communication device notifies the terminal whenever it detects changes in the access method, data network, etc.; when the sixth message is a request message, the terminal sends a request message, and the second communication device replies with a response message.

[0236] Optionally, in this embodiment of the application, the second analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0237] Optionally, in this embodiment of the application, when the second analysis identifier is load level information, the second analysis result indicates slice performance; the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0238] When the second analysis identifier is service experience, the second analysis result indicates the performance of the first access method; the second analysis result includes at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or,

[0239] When the second analysis is identified as WLAN performance, the second analysis result indicates the performance of the second access method; the second analysis result includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0240] In the case where the second analysis is identified as DN performance, the second analysis result indicates DN performance; the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0241] Understandably, each analysis identifier corresponds to an analysis result indicating the performance of an analyzed object. That is, by sending load level information, the terminal can obtain analysis results indicating slice performance; by sending service experience information, the terminal can obtain analysis results indicating the performance of the first access method; by sending WLAN performance information, the terminal can obtain analysis results indicating the performance of the second access method; and by sending DN performance information, the terminal can obtain analysis results indicating DN performance.

[0242] Optionally, in this embodiment of the application, when the second analysis identifier is service experience, the second analysis result indicates at least one of the following: slice performance, access method performance, and DN performance.

[0243] Where the second analysis result indicates slice performance, the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0244] When the second analysis result indicates access mode performance, the second analysis result includes the performance of the first access mode and / or the performance of the second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0245] In cases where the second analysis result indicates DN performance, the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0246] Understandably, one analysis identifier corresponds to analysis results indicating the performance of multiple analysis objects. That is, by sending a service experience report, the terminal can obtain analysis results indicating slice performance, first access method performance, second access method performance, and DN performance.

[0247] It should be noted that, in this embodiment of the application, analysis results indicating the performance of multiple analysis objects can be obtained through a single analysis identifier, thereby improving the efficiency of the terminal in obtaining analysis results.

[0248] Optionally, in this embodiment of the application, the first access method can be a 3GPP access method (e.g., 5GS access), and the second access method can be a non-3GPP access method (e.g., WLAN access).

[0249] In other words, the terminal can obtain the performance of the access method, slicing performance, or DN performance, etc. By comparing the performance of different access methods, slicing or DN, if the RSD parameter setting in the first URSP rule is unreasonable, for example, access method 1 has better performance but lower priority, then the terminal can request the first communication device to re-evaluate the first URSP rule.

[0250] This application provides a URSP rule optimization method, such as... Figure 4 As shown, the method is applied to a second communication device. The URSP rule optimization method provided in this application includes the following steps 401 to 403.

[0251] Step 401: The second communication device receives the target message from the target device.

[0252] In this embodiment of the application, the target message includes a target analysis identifier, which is used by the target device to obtain the analysis results and / or prediction results corresponding to the target analysis identifier.

[0253] Step 402: The second communication device obtains the target analysis result based on the target analysis identifier.

[0254] The above target analysis results are used by the target device to re-evaluate the terminal's first URSP rule.

[0255] Step 403: The second communication device sends the target analysis results to the target device.

[0256] In this embodiment of the application, the second communication device can receive a target message from the target device, obtain a target analysis result based on the target analysis identifier in the target message, and then send the target analysis result to the target device so that the target device can re-evaluate the terminal's first URSP rule based on the target analysis result. Finally, based on the URSP rule obtained after re-evaluation (i.e., the optimized URSP rule), the terminal can more intelligently select and / or establish PDU sessions for application traffic.

[0257] Optionally, in this embodiment, the target message can be a subscription message or a request message. When the target message is a subscription message, the second communication device notifies the target device whenever it detects changes in the access method, data network, etc.; when the target message is a request message, the target device sends a request message, and the second communication device replies with a response message.

[0258] Optionally, in this embodiment of the application, the target message may further include a first terminal identifier and / or first location information. When the target message includes a first terminal identifier, the target analysis result is the analysis result corresponding to the terminal indicated by the first terminal identifier; when the target message includes first location information, the target analysis result is the analysis result corresponding to the terminal corresponding to the first location information.

[0259] Optionally, in this embodiment of the application, the first location information can be a region of interest to the target device; the terminal corresponding to the first location information can be all terminals within the region of interest to the target device.

[0260] Optionally, in this embodiment of the application, the target device is a first communication device.

[0261] Among them, the aforementioned target message is the second message; the aforementioned target analysis identifier is the first analysis identifier.

[0262] Optionally, in this embodiment of the application, the target device is a terminal.

[0263] Among them, the aforementioned target message is the sixth message; the aforementioned target analysis identifier is the second analysis identifier.

[0264] Optionally, in this embodiment of the application, step 402 can be implemented by step 402a as described below.

[0265] Step 402a: The second communication device analyzes the target object according to the target analysis identifier and obtains the target analysis result.

[0266] The aforementioned target analysis identifier indicates the target analysis object, which includes at least one of the following: access method, DN, slice.

[0267] Optionally, in this embodiment of the application, when the target analysis identifier is load level information, the target analysis result indicates slice performance; the target analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0268] When the target analysis is identified as service experience, the target analysis results indicate the performance of the first access method; the target analysis results include at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or,

[0269] When the target analysis is identified as WLAN performance, the target analysis results indicate the performance of the second access method. The target analysis results include at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0270] When the target analysis is identified as DN performance, the target analysis results indicate DN performance. The target analysis results include at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0271] Understandably, each analysis identifier corresponds to an analysis result indicating the performance of an analyzed object. That is, the target device can obtain analysis results indicating slice performance by sending load level information; the target device can obtain analysis results indicating the performance of the first access method by sending service experience; the target device can obtain analysis results indicating the performance of the second access method by sending WLAN performance; and the target device can obtain analysis results indicating DN performance by sending DN performance.

[0272] Optionally, in the embodiments of this application, when the target analysis is identified as service experience, the target analysis result indicates at least one of the following: slice performance, access method performance, and DN performance.

[0273] Where the target analysis results indicate slice performance, the target analysis results include at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0274] When the target analysis results indicate access mode performance, the target analysis results include the performance of a first access mode and / or a second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0275] When the target analysis results indicate DN performance, the target analysis results include at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0276] Understandably, one analysis identifier corresponds to analysis results indicating the performance of multiple analysis objects. That is, the target device can obtain analysis results indicating slice performance, first access method performance, second access method performance, and DN performance by sending a service experience. In other words, the second communication device can provide analysis results indicating the performance of multiple analysis objects based on only one analysis identifier.

[0277] Optionally, in this embodiment of the application, the first access method can be a 3GPP access method (e.g., 5GS access), and the second access method can be a non-3GPP access method (e.g., WLAN access).

[0278] Optionally, in the embodiments of this application, the above-mentioned target analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0279] In other words, the second communication device can provide analysis results and / or prediction results on the performance of access methods, DN, slicing, etc., which can provide a basis for the first communication device to conduct the first URSP rule re-evaluation.

[0280] This application provides a URSP rule optimization method, such as... Figure 5 As shown, the method is applied to a third communication device. The URSP rule optimization method provided in this application includes the following steps 501 and 502.

[0281] Step 501: The third communication device receives the fourth message from the first communication device.

[0282] In this embodiment of the application, the fourth message mentioned above includes the terminal's first URSP rule.

[0283] Step 502: The third communication device evaluates the execution status of the first URSP rule based on the first URSP rule.

[0284] Optionally, in this embodiment of the application, after step 502 above, the URSP rule optimization method provided in this embodiment of the application further includes the following step 503.

[0285] Step 503: The third communication device sends an abnormality indication message to the first communication device.

[0286] The aforementioned anomaly indication information indicates that the first URSP rule execution is abnormal.

[0287] In this embodiment of the application, when the first communication device monitors the first URSP rule of the terminal, if the first communication device wants to determine whether the application traffic is correctly matched to the corresponding PDU session, it can send a fourth message to the third communication device so that the third communication device can evaluate the execution status of the first URSP rule of the terminal. If the third communication device determines that the execution of the first URSP rule is abnormal, it sends an abnormal indication message to the first communication device so that the first communication device can re-evaluate the first URSP rule.

[0288] Optionally, in the embodiments of this application, step 502 can be implemented by steps 502a and 502b as described below.

[0289] Step 502a: The third communication device sends the eighth message to the fourth communication device.

[0290] In this embodiment of the application, the eighth message includes a target PDU session identifier. The eighth message is used by the fourth communication device to evaluate the execution status of the first URSP rule within the target PDU session corresponding to the target PDU session identifier.

[0291] The aforementioned target PDU session is a PDU session that should not contain traffic from the target application. The traffic from the target application is the traffic that the terminal uses to match PDU sessions according to the first URSP rule.

[0292] Optionally, in this embodiment of the application, the third communication device can determine which PDU sessions of the current terminal should not contain traffic of the target application according to the first URSP rule, that is, determine the target PDU session, and send an eighth message including the target PDU session identifier to the fourth communication device.

[0293] Step 502b: The third communication device receives the ninth message sent by the fourth communication device.

[0294] In this embodiment of the application, the aforementioned ninth message is used to indicate an error in the execution of the first URSP rule.

[0295] In this embodiment of the application, the third communication device can send an eighth message to the fourth communication device so that the fourth communication device can evaluate the execution status of the first URSP rule. If the fourth communication device determines that the execution of the first URSP rule is abnormal, it sends a ninth message to the third communication device to indicate that the execution of the first URSP rule is abnormal. Then the third communication device sends an abnormality indication information to the first communication device, so that the first communication device can re-evaluate the first URSP rule.

[0296] It should be noted that in related technologies, the traffic of the target application is typically detected in each PDU session. The PDU session in which the target application's traffic is detected indicates that the URSP rule corresponding to the attributes or parameters of that PDU session is the URSP rule used by the terminal. Compared to detecting the target application's traffic in each PDU session, this embodiment only detects PDU sessions where the target application's traffic should not exist. Once the target application's traffic is detected, it indicates that the terminal is misusing or incorrectly using the URSP rule. This avoids the problem of the complex detection process caused by needing to detect each PDU session in related technologies, thereby improving the efficiency of detecting the terminal's URSP rules.

[0297] For example, for a certain application traffic, after matching it using the first URSP rule, it will definitely not match PDU session 1 (the RSD in the Traffic Descriptor of this application traffic does not include the session parameters corresponding to PDU session 1, that is, the PDU session parameters described by the RSD are inconsistent with the session parameters corresponding to PDU session 1). Therefore, the network-side device can configure a packet detection rule (PDR) in the UPF of PDU session 1 carrying the UE to detect this application traffic. If the application traffic is detected in this PDU session 1, it means that the application traffic has been matched to a PDU session that should not be matched, and it is determined that the terminal has incorrectly used the first URSP rule, or that the first URSP rule has been misused.

[0298] Optionally, in this embodiment of the application, the eighth message further includes: a PDR, which is used by the fourth communication device to evaluate the execution status of the first URSP rule.

[0299] Optionally, in this embodiment, the PDR can be generated by a third communication device based on an IP descriptor. This IP descriptor can be obtained by the third communication device based on the traffic descriptor in the first URSP rule, or it can be received by the third communication device from the first communication device.

[0300] Optionally, in one implementation of this application embodiment, before step 502a above, the URSP rule optimization method provided in this application embodiment further includes the following step 504.

[0301] Step 504: The third communication device maps the second traffic descriptor in the first URSP rule to the second IP descriptor.

[0302] The PDR mentioned above is a PDR generated based on the second IP descriptor.

[0303] The second traffic descriptor mentioned above includes at least one of the following: application descriptor, domain name descriptor, data network name, connectivity; the second IP descriptor is a destination IP triplet.

[0304] Optionally, in another implementation of this application embodiment, the fourth message further includes a first IP descriptor. The PDR is generated based on the first IP descriptor.

[0305] In this embodiment of the application, a new mapping method is introduced, that is, mapping the non-IP descriptors in the first URSP rule to IP descriptors. The third communication device can evaluate the execution status of the first URSP rule based on the IP descriptor, thereby improving the efficiency of detecting the URSP rule of the terminal.

[0306] In this embodiment, only IP descriptors (containing the destination IP triplet) can be directly used to generate PDRs. Other descriptors, such as application descriptors, domain name descriptors, data network names, and connectivity attributes, need to be converted into corresponding IP descriptors through this mapping before they can be used to generate PDRs.

[0307] This application provides a URSP rule optimization method, such as... Figure 6 As shown, the method is applied to a fourth communication device. The URSP rule optimization method provided in this application includes the following steps 601 to 603.

[0308] Step 601: The fourth communication device receives the eighth message from the third communication device.

[0309] In this embodiment of the application, the eighth message includes a target PDU session identifier. The target PDU session is a PDU session where there should be no traffic from the target application; the traffic from the target application is the traffic used by the terminal to match PDU sessions according to the first URSP rule.

[0310] Step 602: The fourth communication device evaluates the execution status of the terminal's first URSP rule in the target PDU session corresponding to the target PDU session identifier.

[0311] Step 603: The fourth communication device sends the ninth message to the third communication device.

[0312] In this embodiment of the application, the aforementioned ninth message is used to indicate an error in the execution of the first URSP rule.

[0313] Optionally, in this embodiment of the application, the ninth message is used to indicate that traffic of the target application is detected in the target PDU session.

[0314] In this embodiment of the application, the fourth communication device can receive the eighth message from the third communication device, and evaluate the execution status of the first URSP rule in the target PDU session corresponding to the target PDU session identifier. If the traffic of the target application is detected in the target PDU session, the fourth communication device sends a ninth message to the third communication device to indicate that the execution of the first URSP rule is abnormal.

[0315] It should be noted that in related technologies, the traffic of the target application is typically detected in each PDU session. The PDU session in which the target application's traffic is detected indicates that the URSP rule corresponding to the attributes or parameters of that PDU session is the URSP rule used by the terminal. Compared to detecting the target application's traffic in each PDU session, this embodiment only detects PDU sessions where the target application's traffic should not exist. Once the target application's traffic is detected, it indicates that the terminal is misusing or incorrectly using the URSP rule. This avoids the problem of the complex detection process caused by needing to detect each PDU session in related technologies, thereby improving the efficiency of detecting the terminal's URSP rules.

[0316] Optionally, in this embodiment of the application, the eighth message further includes a PDR. Step 602 can be specifically implemented through step 602a as described below.

[0317] Step 602a: The fourth communication device sets the PDR in the target PDU session and evaluates the execution of the first URSP rule in the target PDU session based on the traffic detection results of the PDR.

[0318] In this embodiment, PDR is set only in PDU sessions where traffic of the target application should not exist. Once traffic of the target application is detected, it indicates that the terminal is using or not using URSP rules correctly, thereby improving the efficiency of detecting the terminal's URSP rules.

[0319] The following example uses PCF as the first communication device, NWDAF as the second communication device, SMF as the third communication device, and UPF as the fourth communication device to illustrate the URSP rule optimization method provided in this application. It should be noted that the network element names in the following examples are merely illustrative; other network element names can be used in practical applications, and this application does not limit their use.

[0320] Example 1:

[0321] like Figure 7 As shown, the technical solution provided in this embodiment can be implemented through the following steps:

[0322] Step A1: PCF sends the first analysis identifier to NWDAF via signaling: Nnwdaf_AnalyticsInfoRequest or Nnwdaf_AnalyticsSubscription Request.

[0323] Step A2: NWDAF obtains a first analysis result based on the first analysis identifier. This first analysis result is the analysis result and / or prediction result corresponding to the first analysis identifier. Specifically, NWDAF can analyze a first analysis object based on the first analysis identifier to obtain the first analysis result. The first analysis identifier indicates the first analysis object, which includes at least one of the following: access method, DN, and slice.

[0324] Step A3: NWDAF sends the first analysis result to PCF via signaling: Nnwdaf_AnalyticsInfoResponse or Nnwdaf_AnalyticsSubscription Notify.

[0325] Step A4: The PCF receives the first analysis result sent by the NWDAF and, based on the first analysis result, performs a re-evaluation on the terminal's first URSP rule to obtain the second URSP rule. This re-evaluation is used to determine whether the first URSP rule needs to be updated. If the first URSP rule needs to be updated, the first communication device performs a target operation on the first URSP rule to obtain the second URSP rule.

[0326] The aforementioned target operation includes at least one of the following:

[0327] Adjust the priority of the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0328] Adjust the priority of the first traffic descriptor in the first URSP rule;

[0329] Adjust the parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule;

[0330] Add a new routing descriptor to the first traffic descriptor in the first URSP rule;

[0331] Disable the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0332] Disable the first traffic descriptor in the first URSP rule;

[0333] Generate new URSP rules.

[0334] Step A5: PCF sends the second URSP rule to the terminal.

[0335] Step A6: The terminal selects and / or establishes a PDU session for the application's traffic based on the second URSP rule.

[0336] Example 2:

[0337] like Figure 8 As shown, the technical solution provided in this embodiment can be implemented through the following steps:

[0338] Step B1: The terminal sends the second analysis identifier to the NWDAF.

[0339] Step B2: NWDAF obtains a second analysis result based on the second analysis identifier. This second analysis result is the analysis result and / or prediction result corresponding to the second analysis identifier. Specifically, NWDAF can analyze a second analysis object based on the second analysis identifier to obtain the second analysis result. The second analysis identifier indicates the second analysis object, which includes at least one of the following: access method, DN, and slice.

[0340] Step B3: NWDAF sends the second analysis result to the terminal.

[0341] Step B4: The terminal receives the second analysis result sent by NWDAF and performs a re-evaluation on the terminal's first URSP rule based on the second analysis result. The re-evaluation is used to determine whether the first URSP rule needs to be updated.

[0342] Step B5: If the first URSP rule needs to be updated, the terminal sends a first evaluation request to the PCF. This first evaluation request is used to request the PCF to re-evaluate the first URSP rule. This first evaluation request can be sent via NAS message.

[0343] Step B6: The PCF receives the first evaluation request sent by the terminal and performs a re-evaluation on the terminal's first URSP rule to obtain the second URSP rule.

[0344] Step B7: PCF sends the second URSP rule to the terminal.

[0345] Step B8: The terminal selects and / or establishes a PDU session for the application's traffic based on the second URSP rule.

[0346] Example 3:

[0347] like Figure 9 As shown, the technical solution provided in this embodiment can be implemented through the following steps:

[0348] Step C1: The PCF sends a fourth message to the SMF. This fourth message contains the terminal's first URSP rule and is used to evaluate the execution status of the first URSP rule. This fourth message is also used by the SMF to generate a PDR to detect whether the target application's traffic has appeared in a certain PDU session.

[0349] Step C2: The SMF receives the fourth message sent by the PCF and determines the target PDU session and PDR according to the first URSP rule. The PDR is used in the target PDU session.

[0350] Step C3: The SMF sends an eighth message to the UPF. This eighth message includes the PDR and the PDU session to which the PDR is applied. The SMF can also instruct the UPF that after detecting traffic of a target application through the PDR, the UPF should send a notification to the SMF. This notification includes parameters of the PDU session that detected the traffic of the target application. These parameters include at least one of the following: SSC mode, DNN, S-NSSAI, and access method.

[0351] The target PDU session is a PDU session that should not contain traffic from the target application, and the traffic from the target application is the traffic that the terminal uses to match PDU sessions according to the first URSP rule.

[0352] Step C4: The UPF receives the eighth message sent by the SMF, sets the PDR in the target PDU session, and evaluates the execution of the first URSP rule in the target PDU session based on the traffic detection results of the PDR.

[0353] Step C5: If the UPF detects traffic of the target application in the target PDU session, it sends a ninth message to the SMF, which is used to indicate that the first URSP rule execution is abnormal.

[0354] Step C6: SMF receives the ninth message sent by UPF and sends an exception indication message to PCF, which indicates that the first URSP rule execution is abnormal.

[0355] Step C7: The PCF receives the anomaly indication information sent by the SMF and performs a re-evaluation on the first URSP rule to obtain the second URSP rule.

[0356] Step C8: PCF sends the second URSP rule to the terminal.

[0357] Step C9: The terminal selects and / or establishes a PDU session for the application's traffic based on the second URSP rule.

[0358] The URSP rule optimization method provided in this application can be executed by a URSP rule optimization device. This application uses the execution of the URSP rule optimization method by a URSP rule optimization device as an example to illustrate the URSP rule optimization device provided in this application.

[0359] This application provides an embodiment of a URSP rule optimization device, applied to a first communication device, such as... Figure 10 As shown, the URSP rule optimization device 700 includes a processing module 701 and a sending module 702. The processing module 701 is used to re-evaluate a first URSP rule of the terminal based on target information to obtain a second URSP rule. The sending module 702 is used to send a first message to the terminal. The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; and the anomaly indication information indicates an execution anomaly of the first URSP rule. The first message includes the second URSP rule; the second URSP rule is used by the terminal to select and / or establish PDU sessions for application traffic.

[0360] Optionally, in this embodiment of the application, the above-mentioned processing module 701 is specifically used to re-evaluate the first URSP rule based on the target information; the re-evaluation is used to determine whether the first URSP rule needs to be updated; and if the first URSP rule needs to be updated, the target operation is performed on the first URSP rule to obtain the second URSP rule.

[0361] The aforementioned target operations include at least one of the following:

[0362] Adjust the priority of the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0363] Adjust the priority of the first traffic descriptor in the first URSP rule;

[0364] Adjust the parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule;

[0365] Add a new routing descriptor to the first traffic descriptor in the first URSP rule;

[0366] Disable the first route selection descriptor in the first traffic descriptor of the first URSP rule;

[0367] Disable the first traffic descriptor in the first URSP rule;

[0368] Generate new URSP rules.

[0369] Optionally, in this embodiment of the application, the above-mentioned adjustment of the parameters in the first routing descriptor of the first traffic descriptor in the first URSP rule includes at least one of the following:

[0370] Adjust the access method in the first route selection descriptor and change the access method to the access method whose performance meets the first condition as indicated by the first analysis result;

[0371] Adjust the DNN in the first routing descriptor, and change the DNN to the DNN whose performance, as indicated by the first analysis result, meets the second condition;

[0372] Adjust the S-NSSAI in the first route selection descriptor to change S-NSSAI to the S-NSSAI whose performance, as indicated by the first analysis result, meets the third condition.

[0373] Optionally, in this embodiment, the URSP rule optimization device 600 further includes a receiving module. The sending module 702 is further configured to send a second message to the second communication device before the processing module 701 re-evaluates the first URSP rule based on the target information. The second message includes a first analysis identifier; the second message is used to obtain the analysis result and / or prediction result corresponding to the first analysis identifier. The receiving module is configured to receive a third message sent by the second communication device, the third message including the first analysis result corresponding to the first analysis identifier.

[0374] Optionally, in this embodiment of the application, the first analysis identifier mentioned above includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0375] Optionally, in this embodiment of the application, the processing module 701 is specifically used to re-evaluate the first analysis object in the first URSP rule based on the performance of the first analysis object indicated by the first analysis result, to obtain the second URSP rule. The first analysis object includes at least one of the following: access method, DN, and slice.

[0376] Optionally, in this embodiment of the application, when the first analysis identifier is load level information, the first analysis result indicates slice performance; the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0377] When the first analysis identifier is service experience, the first analysis result indicates the performance of the first access method; the first analysis result includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, access signal quality; and / or,

[0378] When the first analysis is identified as WLAN performance, the first analysis result indicates the performance of the second access method; the first analysis result includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0379] In the case where the first analysis is identified as DN performance, the first analysis result indicates DN performance; the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0380] Optionally, in this embodiment of the application, when the first analysis identifier is service experience, the first analysis result indicates at least one of the following: slice performance, access method performance, and DN performance.

[0381] Where the first analysis result indicates slice performance, the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0382] When the first analysis result indicates access mode performance, the first analysis result includes the performance of the first access mode and / or the performance of the second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0383] In cases where the first analysis result indicates DN performance, the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0384] Optionally, in this embodiment of the application, the processing module 701 is specifically used to re-evaluate the first URSP rule to obtain the second URSP rule when at least one of the first evaluation request and the anomaly indication information is received.

[0385] Optionally, in this embodiment of the application, the URSP rule optimization device 700 further includes a receiving module. The sending module 702 is further configured to send a fourth message to the third communication device before the processing module 701 re-evaluates the terminal's first URSP rule based on the target information to obtain a second URSP rule; the fourth message contains the first URSP rule and is used to evaluate the execution status of the first URSP rule. The receiving module is configured to receive anomaly indication information sent by the third communication device.

[0386] Optionally, in this embodiment, the fourth message further includes a first IP descriptor; the first IP descriptor is used to evaluate the execution status of the first URSP rule. The processing module 701 is further configured to map the first traffic descriptor in the first URSP rule to a first IP descriptor before the sending module 701 sends the fourth message to the third communication device. The first traffic descriptor includes at least one of the following: application descriptor, domain name descriptor, data network name, and connectivity; the first IP descriptor is a destination IP triplet.

[0387] In the URSP rule optimization apparatus provided in this application embodiment, during the process of a terminal selecting and / or establishing a PDU session for application traffic, the apparatus can re-evaluate the terminal's first URSP rule based on at least one of a first analysis result, a first evaluation request, and anomaly indication information to obtain a second URSP rule. Then, the apparatus sends the second URSP rule to the terminal, enabling the terminal to select and / or establish a PDU session for application traffic according to the second URSP rule. In this way, the terminal can more intelligently select and / or establish a PDU session for application traffic based on the optimized URSP rule, thereby matching application traffic to a PDU session with better performance.

[0388] This application provides an embodiment of a URSP rule optimization device, applied to a terminal, such as... Figure 11 As shown, the URSP rule optimization device 800 includes a receiving module 801 and a processing module 802. The receiving module 801 is used to receive a first message from a first communication device; the first message contains a second URSP rule, which is a URSP rule obtained after re-evaluating the terminal's first URSP rule. The processing module 802 is used to select and / or establish PDU sessions for application traffic based on the second URSP rule.

[0389] Optionally, in this embodiment of the application, the URSP rule optimization device 800 further includes a sending module. The sending module is configured to send a first evaluation request to the first communication device before the receiving module 801 receives the first message from the first communication device. The first evaluation request is used to request the first communication device to re-evaluate the first URSP rule.

[0390] Optionally, in this embodiment, the processing module 802 is further configured to re-evaluate the first URSP rule based on the second analysis result before the sending module sends the first evaluation request to the first communication device. This re-evaluation is used to determine whether the first URSP rule needs to be updated. Specifically, the sending module is configured to send the first evaluation request to the first communication device if the first URSP rule needs to be updated. The second analysis result is the analysis result and / or prediction result requested by the terminal.

[0391] Optionally, in this embodiment of the application, the processing module 802 is specifically used to re-evaluate the second analysis object in the first URSP rule based on the performance of the second analysis object indicated by the second analysis result. The second analysis object includes at least one of the following: access method, DN, and slice.

[0392] Optionally, in this embodiment, the sending module is further configured to send a sixth message to the second communication device before sending the first evaluation request to the first communication device. The sixth message includes a second analysis identifier and is used to obtain the analysis result and / or prediction result corresponding to the second analysis identifier. The receiving module 801 is further configured to receive a seventh message sent by the second communication device, the seventh message including the second analysis result corresponding to the second analysis identifier.

[0393] Optionally, in this embodiment of the application, the second analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0394] Optionally, in this embodiment of the application, when the second analysis identifier is load level information, the second analysis result indicates slice performance; the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0395] When the second analysis identifier is service experience, the second analysis result indicates the performance of the first access method; the second analysis result includes at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or,

[0396] When the second analysis is identified as WLAN performance, the second analysis result indicates the performance of the second access method; the second analysis result includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0397] In the case where the second analysis is identified as DN performance, the second analysis result indicates DN performance; the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0398] Optionally, in this embodiment of the application, when the second analysis identifier is service experience, the second analysis result indicates at least one of the following: slice performance, access method performance, and DN performance;

[0399] Where the second analysis result indicates slice performance, the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0400] When the second analysis result indicates access mode performance, the second analysis result includes the performance of the first access mode and / or the performance of the second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0401] In cases where the second analysis result indicates DN performance, the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0402] In the URSP rule optimization device provided in the embodiments of this application, the device can more intelligently select and / or establish PDU sessions for application traffic based on the URSP rules obtained after re-evaluation (i.e., the optimized URSP rules).

[0403] This application provides an embodiment of a URSP rule optimization device, applied to a second communication device, such as... Figure 12 As shown, the URSP rule optimization device 900 includes a receiving module 901, a processing module 902, and a sending module 903. The receiving module 901 receives a target message from the target device; the target message includes a target analysis identifier; the target message is used by the target device to obtain the analysis result and / or prediction result corresponding to the target analysis identifier. The processing module 902 obtains a target analysis result based on the target analysis identifier, and this target analysis result is used by the target device to re-evaluate the terminal's first URSP rule. The sending module 903 sends the target analysis result to the target device.

[0404] Optionally, in this embodiment of the application, the processing module 902 is specifically used to analyze the target analysis object according to the target analysis identifier to obtain the target analysis result. The target analysis identifier indicates the target analysis object; the target analysis object includes at least one of the following: access method, DN, and slice.

[0405] Optionally, in this embodiment of the application, when the target analysis identifier is load level information, the target analysis result indicates slice performance; the target analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0406] When the target analysis is identified as service experience, the target analysis results indicate the performance of the first access method; the target analysis results include at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or,

[0407] When the target analysis is identified as WLAN performance, the target analysis results indicate the performance of the second access method. The target analysis results include at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0408] When the target analysis is identified as DN performance, the target analysis results indicate DN performance. The target analysis results include at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0409] Optionally, in this embodiment of the application, when the target analysis is identified as service experience, the target analysis result indicates at least one of the following: slice performance, access method performance, and DN performance;

[0410] Where the target analysis results indicate slice performance, the target analysis results include at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or,

[0411] When the target analysis results indicate access mode performance, the target analysis results include the performance of a first access mode and / or a second access mode; the performance of the first access mode includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access mode includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or,

[0412] When the target analysis results indicate DN performance, the target analysis results include at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of the accessed application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

[0413] Optionally, in the embodiments of this application, the above-mentioned target analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

[0414] Optionally, in this embodiment of the application, the target device is a first communication device. The target message is a second message; the target analysis identifier is a first analysis identifier.

[0415] Optionally, in this embodiment of the application, the target device is a terminal. The target message is the sixth message; the target analysis identifier is the second analysis identifier.

[0416] In the URSP rule optimization device provided in this application embodiment, the device can receive a target message from the target device, obtain a target analysis result based on the target analysis identifier in the target message, and then send the target analysis result to the target device so that the target device can re-evaluate the terminal's first URSP rule based on the target analysis result. Finally, based on the URSP rule obtained after re-evaluation (i.e., the optimized URSP rule), the terminal can more intelligently select and / or establish PDU sessions for application traffic.

[0417] This application provides an embodiment of a URSP rule optimization device, applied to a third communication device, such as... Figure 13 As shown, the URSP rule optimization device 1000 includes a receiving module 1001 and a processing module 1002. The receiving module 1001 is used to receive a fourth message from a first communication device, the fourth message containing the terminal's first URSP rule. The processing module 1002 is used to evaluate the execution status of the first URSP rule based on the first URSP rule.

[0418] Optionally, in this embodiment of the application, the URSP rule optimization device 1000 further includes a sending module. The sending module is configured to send an anomaly indication message to the first communication device after the processing module 1002 evaluates the execution status of the first URSP rule based on the first URSP rule. The anomaly indication message indicates that the execution of the first URSP rule is abnormal.

[0419] Optionally, in this embodiment, the processing module 1002 is specifically used to send an eighth message to the fourth communication device; the eighth message includes a target PDU session identifier; the eighth message is used for: the fourth communication device to evaluate the execution status of the first URSP rule in the target PDU session corresponding to the target PDU session identifier; and to receive a ninth message sent by the fourth communication device, which is used to indicate that the execution of the first URSP rule is abnormal. Here, the target PDU session is a PDU session that should not contain traffic from the target application; the traffic from the target application is the traffic used by the terminal to match the PDU session according to the first URSP rule.

[0420] Optionally, in this embodiment of the application, the eighth message further includes: a PDR, which is used by the fourth communication device to evaluate the execution status of the first URSP rule.

[0421] Optionally, in this embodiment of the application, the processing module 1002 is further configured to map the second traffic descriptor in the first URSP rule to a second IP descriptor before the sending module sends the eighth message to the fourth communication device. The PDR is a PDR generated based on the second IP descriptor; the second traffic descriptor includes at least one of the following: application descriptor, domain name descriptor, data network name, connectivity; the second IP descriptor is a destination IP triplet.

[0422] Optionally, in this embodiment of the application, the fourth message further includes: a first IP descriptor; the PDR is a PDR generated based on the first IP descriptor.

[0423] In the URSP rule optimization device provided in this application embodiment, when the first communication device monitors the first URSP rule of the terminal, if the first communication device wants to determine whether the application traffic is correctly matched to the corresponding PDU session, it can send a fourth message to the third communication device so that the device can evaluate the execution status of the first URSP rule of the terminal, and if it determines that the execution of the first URSP rule is abnormal, it sends an abnormal indication message to the first communication device so that the first communication device can re-evaluate the first URSP rule.

[0424] This application provides an embodiment of a URSP rule optimization device, applied to a fourth communication device, such as... Figure 14As shown, the URSP rule optimization device 1100 includes a receiving module 1101, a processing module 1102, and a sending module 1103. The receiving module 1101 receives an eighth message from a third communication device; the eighth message includes a target PDU session identifier. The processing module 1102 evaluates the execution status of the terminal's first URSP rule within the target PDU session corresponding to the target PDU session identifier. The sending module 1103 sends a ninth message to the third communication device. The target PDU session is a PDU session where traffic for the target application should not exist; the target application traffic is the traffic used by the terminal to match PDU sessions according to the first URSP rule; the ninth message indicates an error in the execution of the first URSP rule.

[0425] Optionally, in this embodiment of the application, the eighth message further includes a PDR. The processing module 1102 is specifically used to set a PDR in the target PDU session and evaluate the execution status of the first URSP rule in the target PDU session based on the traffic detection result of the PDR.

[0426] Optionally, in this embodiment of the application, the ninth message is used to indicate that traffic of the target application is detected in the target PDU session.

[0427] In the URSP rule optimization device provided in this application embodiment, the device can only detect PDU sessions where traffic of the target application should not exist. Once the traffic of the target application is detected, it indicates that the terminal is using or not using URSP rules correctly. This can avoid the problem in related technologies where it is necessary to detect each PDU session, which makes the detection process more complicated, thereby improving the efficiency of detecting the URSP rules of the terminal.

[0428] The URSP rule optimization device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the type.

[0429] The URSP rule optimization device provided in this application embodiment can implement the various processes implemented in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0430] Optional, such as Figure 15As shown in the illustration, this application also provides a communication device 1200, including a processor 1201 and a memory 1202. The memory 1202 stores programs or instructions that can run on the processor 1201. For example, when the communication device 1200 is a terminal, the program or instructions executed by the processor 1201 implement the steps corresponding to the terminal in the above-described URSP rule optimization method embodiment, and achieve the same technical effect. When the communication device 1200 is a network-side device, the program or instructions executed by the processor 1201 implement the steps corresponding to the first communication device, second communication device, third communication device, or fourth communication device in the above-described URSP rule optimization method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0431] This application embodiment also provides a terminal, including a processor and a communication interface. The communication interface is used to receive a first message from a first communication device, the first message containing a second URSP rule. The processor is used to select and / or establish a PDU session for application traffic based on the second URSP rule. The second URSP rule is a URSP rule obtained after re-evaluating the terminal's first URSP rule. This terminal embodiment corresponds to the above-described terminal-side method. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 16 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0432] The terminal 1300 includes, but is not limited to, at least some of the following components: radio frequency unit 1301, network module 1302, audio output unit 1303, input unit 1304, sensor 1305, display unit 1306, user input unit 1307, interface unit 1308, memory 1309, and processor 1310.

[0433] Those skilled in the art will understand that the terminal 1300 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1310 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 16 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0434] It should be understood that, in this embodiment, the input unit 1304 may include a graphics processing unit (GPU) 13041 and a microphone 13042. The GPU 13041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1306 may include a display panel 13061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1307 includes a touch panel 13071 and at least one of other input devices 13072. The touch panel 13071 is also called a touch screen. The touch panel 13071 may include a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0435] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1301 can transmit it to the processor 1310 for processing; in addition, the radio frequency unit 1301 can send uplink data to the network-side device. Typically, the radio frequency unit 1301 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0436] The memory 1309 can be used to store software programs or instructions and various data. The memory 1309 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback function, image playback function, etc.). Furthermore, the memory 1309 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1309 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0437] Processor 1310 may include one or more processing units; optionally, processor 1310 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1310.

[0438] The radio frequency unit 1301 is used to receive a first message from the first communication device; the first message contains a second URSP rule, which is a URSP rule obtained by re-evaluating the terminal's first URSP rule. The processor 1310 is used to select and / or establish PDU sessions for application traffic based on the second URSP rule.

[0439] Optionally, in this embodiment of the application, the radio frequency unit 1301 is further configured to send a first evaluation request to the first communication device before receiving the first message from the first communication device. The first evaluation request is used to request the first communication device to re-evaluate the first URSP rule.

[0440] Optionally, in this embodiment, the processor 1310 is further configured to re-evaluate the first URSP rule based on the second analysis result before sending the first evaluation request to the first communication device. This re-evaluation is used to determine whether the first URSP rule needs to be updated. Specifically, the radio frequency unit 1301 is configured to send the first evaluation request to the first communication device when the first URSP rule needs to be updated. The second analysis result is the analysis result and / or prediction result requested by the terminal.

[0441] Optionally, in this embodiment of the application, the processor 1310 is specifically configured to re-evaluate the second analysis object in the first URSP rule based on the performance of the second analysis object indicated by the second analysis result. The second analysis object includes at least one of the following: access method, DN, and slice.

[0442] Optionally, in this embodiment, the radio frequency unit 1301 is further configured to send a sixth message to the second communication device before sending a first evaluation request to the first communication device. The sixth message includes a second analysis identifier and is used to obtain the analysis result and / or prediction result corresponding to the second analysis identifier. The radio frequency unit 1301 is also configured to receive a seventh message sent by the second communication device, the seventh message including a second analysis result corresponding to the second analysis identifier.

[0443] In this embodiment of the application, the terminal can more intelligently select and / or establish PDU sessions for application traffic based on the URSP rules obtained after re-evaluation (i.e., the optimized URSP rules).

[0444] This application also provides a network-side device, including a processor and a communication interface. This network-side device embodiment corresponds to the network-side device method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0445] In one example, the network-side device is a first communication device, including a processor and a communication interface. The processor is used to re-evaluate a first URSP rule of the terminal based on target information to obtain a second URSP rule. The communication interface is used to send a first message to the terminal. The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information. The first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; and the anomaly indication information indicates an execution anomaly of the first URSP rule. The first message includes the second URSP rule; the second URSP rule is used by the terminal to select and / or establish a PDU session for application traffic.

[0446] In one example, the network-side device is a second communication device, including a processor and a communication interface. The communication interface is used to receive a target message from the target device. The target message includes a target analysis identifier. The target message is used by the target device to obtain the analysis result and / or prediction result corresponding to the target analysis identifier. The processor is used to obtain the target analysis result based on the target analysis identifier. The target analysis result is used by the target device to re-evaluate the first URSP rule of the terminal. The communication interface is also used to send the target analysis result to the target device.

[0447] In one example, the network-side device is a third communication device, including a processor and a communication interface, wherein the communication interface is used to receive a fourth message from a first communication device, the fourth message containing a first URSP rule of the terminal; the processor is used to evaluate the execution status of the first URSP rule based on the first URSP rule.

[0448] In one example, the network-side device is a fourth communication device, including a processor and a communication interface. The communication interface is used to receive an eighth message from a third communication device. This eighth message includes a target PDU session identifier. The processor is used to evaluate the execution status of the terminal's first URSP rule within the target PDU session corresponding to the target PDU session identifier. The communication interface is also used to send a ninth message to the third communication device. The target PDU session is a PDU session that should not contain traffic from the target application. The traffic from the target application is the traffic used by the terminal to match PDU sessions according to the first URSP rule. The ninth message indicates an error in the execution of the first URSP rule.

[0449] This application also provides a network-side device, such as... Figure 17As shown, the network-side device 1400 includes a processor 1401, a network interface 1402, and a memory 1403. The network interface 1402 is, for example, a common public radio interface (CPRI).

[0450] Specifically, the network-side device 1400 of this embodiment further includes: instructions or programs stored in memory 1403 and executable on processor 1401, wherein processor 1401 calls the instructions or programs in memory 1403 to execute. Figure 10 or Figure 12 or Figure 13 or Figure 14 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0451] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described URSP rule optimization method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0452] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0453] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described URSP rule optimization method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0454] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0455] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described URSP rule optimization method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0456] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the URSP rule optimization method as described above, and the network-side device can be used to perform the steps of the URSP rule optimization method as described above.

[0457] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0458] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0459] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for optimizing User Equipment Routing Policy (URSP) rules, characterized in that, The method includes: Based on the target information, the first communication device re-evaluates the terminal's first URSP rule to obtain the second URSP rule; The first communication device sends a first message to the terminal; The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; the anomaly indication information indicates that the first URSP rule execution is abnormal; the first message includes the second URSP rule; the second URSP rule is used by the terminal to select traffic for the application and / or establish a Protocol Data Unit (PDU) session; Before the first communication device re-evaluates the first URSP rule based on the target information, the method further includes: The first communication device sends a second message to the second communication device, the second message including a first analysis identifier; the second message is used to obtain the analysis result and / or prediction result corresponding to the first analysis identifier; The first communication device receives a third message sent by the second communication device, the third message including the first analysis result corresponding to the first analysis identifier; The first analysis result indicates the performance of the first analysis object in the first URSP rule, and the first analysis object includes at least one of the following: access method, DN, slice.

2. The method according to claim 1, characterized in that, The first communication device re-evaluates the terminal's first URSP rule based on the target information to obtain a second URSP rule, including: The first communication device re-evaluates the first URSP rule based on the target information, and the re-evaluation is used to determine whether the first URSP rule needs to be updated. When it is necessary to update the first URSP rule, the first communication device performs a target operation on the first URSP rule to obtain the second URSP rule; The target operation includes at least one of the following: Adjust the priority of the first route selection descriptor in the first traffic descriptor of the first URSP rule; Adjust the priority of the first traffic descriptor in the first URSP rule; Adjust the parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule; Add a new route selection descriptor to the first traffic descriptor in the first URSP rule; Disable the first route selection descriptor in the first traffic descriptor of the first URSP rule; Deactivate the first traffic descriptor in the first URSP rule; Generate new URSP rules.

3. The method according to claim 2, characterized in that, The adjustment of parameters in the first route selection descriptor of the first traffic descriptor in the first URSP rule includes at least one of the following: Adjust the access method in the first route selection descriptor and change the access method to the access method whose performance meets the first condition as indicated by the first analysis result; Adjust the data network name (DNN) in the first routing descriptor and change the DNN to the DNN whose performance, as indicated by the first analysis result, meets the second condition; Adjust the Single Network Slice Selection Auxiliary Information (S-NSSAI) in the first routing descriptor, and change the S-NSSAI to the S-NSSAI whose performance, as indicated by the first analysis result, meets the third condition.

4. The method according to claim 1, characterized in that, The first analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, user equipment (UE) mobility, UE communication, abnormal behavior, user data congestion, quality of service sustainability, session management congestion control experience, redundant transmission experience, wireless access network (WLAN) performance, UE deviation, and data network (DN) performance.

5. The method according to claim 4, characterized in that, The first communication device re-evaluates the first URSP rule based on the target information, including: The first communication device re-evaluates the first analysis object in the first URSP rule based on the performance of the first analysis object indicated by the first analysis result.

6. The method according to claim 4 or 5, characterized in that, When the first analysis identifier is the load level information, the first analysis result indicates slice performance; the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the first analysis identifier is the service experience, the first analysis result indicates the performance of the first access method; the first analysis result includes at least one of the following: Quality of Service (QoS) stream bit rate, packet latency of uplink QoS stream or downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, Radio Access Technology (RAT) type, frequency of serving cell, access signal quality; and / or, When the first analysis identifier is the WLAN performance, the first analysis result indicates the second access method performance; the first analysis result includes at least one of the following: Received Signal Strength Indication (RSSI), uplink data rate or downlink data rate, uplink data traffic or downlink data traffic. And / or, When the first analysis identifier is the DN performance, the first analysis result indicates the DN performance; the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

7. The method according to claim 4 or 5, characterized in that, When the first analysis identifier is the service experience, the first analysis result indicates at least one of the following: slice performance, access method performance, DN performance; Wherein, when the first analysis result indicates the slice performance, the first analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the first analysis result indicates the performance of the access method, the first analysis result includes the performance of a first access method and / or the performance of a second access method; the performance of the first access method includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access method includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or, When the first analysis result indicates the performance of the DN, the first analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics of accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

8. The method according to claim 1, characterized in that, The first communication device re-evaluates the terminal's first URSP rule based on the target information to obtain a second URSP rule, including: Upon receiving at least one of the first evaluation request and the anomaly indication information, the first communication device re-evaluates the first URSP rule to obtain the second URSP rule.

9. The method according to claim 1, characterized in that, Before the first communication device re-evaluates the terminal's first URSP rule based on target information to obtain the second URSP rule, the method further includes: The first communication device sends a fourth message to the third communication device; the fourth message contains the first URSP rule, and the fourth message is used to evaluate the execution status of the first URSP rule; The first communication device receives the abnormal indication information sent by the third communication device.

10. The method according to claim 9, characterized in that, The fourth message further includes: a first Internet Protocol (IP) descriptor, which is used to evaluate the execution status of the first URSP rule; Before the first communication device sends the fourth message to the third communication device, the method further includes: The first communication device maps the first traffic descriptor in the first URSP rule to the first IP descriptor; The first traffic descriptor includes at least one of the following: application descriptor, domain name descriptor, data network name, and connectivity; the first IP descriptor is a destination IP triplet.

11. A URSP rule optimization method, characterized in that, The method includes: The terminal receives a first message from the first communication device; the first message contains a second URSP rule; The terminal selects and / or establishes PDU sessions for application traffic based on the second URSP rule; Wherein, the second URSP rule is: the URSP rule obtained after re-evaluation of the first URSP rule of the terminal; The second URSP rule is obtained by the first communication device after re-evaluating the first URSP rule of the terminal based on the target information; the target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device, the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule, and the anomaly indication information indicates that the first URSP rule execution is abnormal; The first analysis result is the analysis result and / or prediction result obtained by the first communication device from the second communication device. The first analysis result indicates the performance of the first analysis object in the first URSP rule. The first analysis object includes at least one of the following: access method, DN, slice.

12. The method according to claim 11, characterized in that, Before the terminal receives the first message from the first communication device, the method further includes: The terminal sends a first evaluation request to the first communication device; The first evaluation request is used to request the first communication device to re-evaluate the first URSP rule.

13. The method according to claim 12, characterized in that, Before the terminal sends the first evaluation request to the first communication device, the method further includes: The terminal re-evaluates the first URSP rule based on the second analysis result. The re-evaluation is used to determine whether the first URSP rule needs to be updated. The terminal sends a first evaluation request to the first communication device, including: If it is necessary to update the first URSP rule, the terminal sends the first evaluation request to the first communication device; The second analysis result is the analysis result and / or prediction result requested by the terminal.

14. The method according to claim 13, characterized in that, The terminal re-evaluates the first URSP rule based on the second analysis result, including: The terminal re-evaluates the second analysis object in the first URSP rule based on the performance of the second analysis object indicated by the second analysis result. The second analysis object includes at least one of the following: access method, DN, slice.

15. The method according to claim 13 or 14, characterized in that, Before the terminal sends the first evaluation request to the first communication device, the method further includes: The terminal sends a sixth message to the second communication device, the sixth message including a second analysis identifier; the sixth message is used to obtain the analysis result and / or prediction result corresponding to the second analysis identifier; The terminal receives a seventh message sent by the second communication device, the seventh message including the second analysis result corresponding to the second analysis identifier.

16. The method according to claim 15, characterized in that, The second analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

17. The method according to claim 16, characterized in that, When the second analysis identifier is the load level information, the second analysis result indicates slice performance; the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the second analysis identifier is the service experience, the second analysis result indicates the performance of the first access method; the second analysis result includes at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or, When the second analysis identifier is the WLAN performance, the second analysis result indicates the performance of the second access method; the second analysis result includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; And / or, When the second analysis identifier is the DN performance, the second analysis result indicates the DN performance; the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics for accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

18. The method according to claim 16, characterized in that, When the second analysis identifier is the service experience, the second analysis result indicates at least one of the following: slice performance, access method performance, DN performance; Wherein, when the second analysis result indicates the slice performance, the second analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the second analysis result indicates the performance of the access method, the second analysis result includes the performance of the first access method and / or the performance of the second access method; the performance of the first access method includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access method includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or, When the second analysis result indicates the performance of the DN, the second analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics for accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

19. A URSP rule optimization method, characterized in that, The method includes: The second communication device receives a target message from the target device; the target message includes a target analysis identifier; the target message is used by the target device to obtain the analysis results and / or prediction results corresponding to the target analysis identifier; The second communication device analyzes the target object based on the target analysis identifier to obtain the target analysis result; The second communication device sends the target analysis results to the target device; The target analysis result is used by the target device to re-evaluate the first URSP rule of the terminal; the target analysis identifier indicates the target analysis object; the target analysis object includes at least one of the following: access method, DN, slice; The target device is a first communication device, the target message is a second message, and the target analysis identifier is a first analysis identifier; or, The target device is the terminal, the target message is the sixth message, and the target analysis identifier is the second analysis identifier.

20. The method according to claim 19, characterized in that, When the target analysis identifier is load level information, the target analysis result indicates slice performance; the target analysis result includes at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the target analysis identifier is service experience, the target analysis result indicates the performance of the first access method; the target analysis result includes at least one of the following: QoS stream bit rate, uplink QoS stream packet delay or downlink QoS stream packet delay, number of transmitted data packets, number of retransmitted data packets, RAT type, serving cell frequency, access signal quality; and / or, When the target analysis is identified as WLAN performance, the target analysis result indicates the performance of the second access method, and the target analysis result includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; And / or, When the target analysis is identified as the DN performance, the target analysis result indicates the DN performance, and the target analysis result includes at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics for accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

21. The method according to claim 19, characterized in that, When the target analysis is identified as service experience, the target analysis result indicates at least one of the following: slice performance, access method performance, DN performance; Wherein, when the target analysis results indicate the slice performance, the target analysis results include at least one of the following: number of registered terminals, number of established PDU sessions, number of resource usages, resource usage threshold, time-domain resource usage threshold, load level; and / or, When the target analysis result indicates the performance of the access method, the target analysis result includes the performance of a first access method and / or a second access method; the performance of the first access method includes at least one of the following: QoS stream bit rate, packet delay of uplink QoS stream or packet delay of downlink QoS stream, number of transmitted data packets, number of retransmitted data packets, RAT type, frequency of serving cell, and access signal quality; the performance of the second access method includes at least one of the following: RSSI, uplink data rate or downlink data rate, uplink data traffic or downlink data traffic; and / or, When the target analysis results indicate the performance of the DN, the target analysis results include at least one of the following: the analyzed DNN, the predicted DNN, S-NSSAI, the accessed application server instance address, and the performance metrics for accessing the application server address; wherein the performance metrics include at least one of the following: average traffic rate, maximum traffic rate, average packet latency, maximum packet latency, and average packet loss rate.

22. The method according to any one of claims 19 to 21, characterized in that, The target analysis identifier includes at least one of the following: load level information, service experience, network element load information, network performance, UE mobility, UE communication, abnormal behavior, user data congestion, service quality sustainability, session management congestion control experience, redundant transmission experience, WLAN performance, UE deviation, and DN performance.

23. A URSP rule optimization method, characterized in that, The method includes: The third communication device receives a fourth message from the first communication device, the fourth message containing the terminal's first URSP rule; The third communication device evaluates the execution status of the first URSP rule based on the first URSP rule; The third communication device sends an abnormality indication message to the first communication device; The anomaly indication information indicates that the first URSP rule execution is abnormal. The anomaly indication information is used by the first communication device to re-evaluate the first URSP rule of the terminal to obtain the second URSP rule.

24. The method according to claim 23, characterized in that, The third communication device evaluates the execution of the first URSP rule based on the first URSP rule, including: The third communication device sends an eighth message to the fourth communication device; the eighth message includes a target PDU session identifier; the eighth message is used for: the fourth communication device to evaluate the execution status of the first URSP rule in the target PDU session corresponding to the target PDU session identifier; The third communication device receives a ninth message sent by the fourth communication device; the ninth message is used to indicate that the first URSP rule execution is abnormal. The target PDU session is a PDU session that should not contain traffic from the target application; the traffic from the target application is the traffic that the terminal uses to match PDU sessions according to the first URSP rule.

25. The method according to claim 24, characterized in that, The eighth message also includes: a packet detection rule (PDR), which is used by the fourth communication device to evaluate the execution status of the first URSP rule.

26. The method according to claim 25, characterized in that, Before the third communication device sends the eighth message to the fourth communication device, the method further includes: The third communication device maps the second traffic descriptor in the first URSP rule to a second IP descriptor; Wherein, the PDR is a PDR generated based on the second IP descriptor; The second traffic descriptor includes at least one of the following: application descriptor, domain name descriptor, data network name, and connectivity; the second IP descriptor is a destination IP triplet.

27. The method according to claim 25, characterized in that, The fourth message also includes: a first IP descriptor; The PDR is generated based on the first IP descriptor.

28. A URSP rule optimization method, characterized in that, The method includes: The fourth communication device receives an eighth message from the third communication device; the eighth message includes the target PDU session identifier; The fourth communication device evaluates the execution status of the terminal's first URSP rule in the target PDU session corresponding to the target PDU session identifier; The fourth communication device sends a ninth message to the third communication device; Wherein, the target PDU session is a PDU session that should not contain traffic of the target application; the traffic of the target application is the traffic of the terminal matching the PDU session according to the first URSP rule; the ninth message is used to indicate that the execution of the first URSP rule is abnormal, the ninth message is used by the third communication device to send abnormal indication information to the first communication device, and the abnormal indication information is used to trigger the first communication device to re-evaluate the first URSP rule of the terminal to obtain the second URSP rule.

29. The method according to claim 28, characterized in that, The eighth message also includes a PDR; the fourth communication device evaluates the execution status of the terminal's first URSP rule in the target PDU session corresponding to the target PDU session identifier, including: The fourth communication device sets the PDR in the target PDU session and evaluates the execution status of the first URSP rule in the target PDU session based on the traffic detection result of the PDR.

30. The method according to claim 28 or 29, characterized in that, The ninth message is used to indicate that traffic of the target application was detected in the target PDU session.

31. A URSP rule optimization device, characterized in that, The device includes: The processing module is used to re-evaluate the terminal's first URSP rule based on the target information to obtain the second URSP rule; The sending module is used to send a first message to the terminal; The target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device; the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule; the anomaly indication information indicates that the first URSP rule execution is abnormal; the first message includes the second URSP rule; the second URSP rule is used by the terminal to select traffic for the application and / or establish a PDU session; The sending module is further configured to send a second message to a second communication device, the second message including a first analysis identifier; the second message is used to obtain the analysis result and / or prediction result corresponding to the first analysis identifier; A receiving module is configured to receive a third message sent by the second communication device, the third message including a first analysis result corresponding to the first analysis identifier; The first analysis result indicates the performance of the first analysis object in the first URSP rule, and the first analysis object includes at least one of the following: access method, DN, slice.

32. A URSP rule optimization device, characterized in that, The device includes: A receiving module is configured to receive a first message from a first communication device; the first message contains a second URSP rule; The processing module is used to select and / or establish PDU sessions for the application's traffic based on the second URSP rule; The second URSP rule is: the URSP rule obtained after re-evaluation of the terminal's first URSP rule; The second URSP rule is obtained by the first communication device after re-evaluating the first URSP rule of the terminal based on the target information; the target information includes at least one of the following: a first analysis result, a first evaluation request, and an anomaly indication information; the first analysis result is the analysis result and / or prediction result requested by the first communication device, the first evaluation request is used by the terminal to request a re-evaluation of the first URSP rule, and the anomaly indication information indicates that the first URSP rule execution is abnormal; The first analysis result is the analysis result and / or prediction result obtained by the first communication device from the second communication device. The first analysis result indicates the performance of the first analysis object in the first URSP rule. The first analysis object includes at least one of the following: access method, DN, slice.

33. A URSP rule optimization device, characterized in that, The device includes: A receiving module is configured to receive a target message from a target device; the target message includes a target analysis identifier; the target message is used by the target device to obtain the analysis results and / or prediction results corresponding to the target analysis identifier; The processing module is used to analyze the target analysis object according to the target analysis identifier and obtain the target analysis result; The sending module is used to send the target analysis results to the target device; The target analysis result is used by the target device to re-evaluate the first URSP rule of the terminal; the target analysis identifier indicates the target analysis object; the target analysis object includes at least one of the following: access method, DN, slice; The target device is a first communication device, the target message is a second message, and the target analysis identifier is a first analysis identifier; or, The target device is the terminal, the target message is the sixth message, and the target analysis identifier is the second analysis identifier.

34. A URSP rule optimization device, characterized in that, The device includes: A receiving module is configured to receive a fourth message from a first communication device, the fourth message containing the terminal's first URSP rule; The processing module is used to evaluate the execution status of the first URSP rule based on the first URSP rule; The sending module is used to send an abnormal indication message to the first communication device; The anomaly indication information indicates that the first URSP rule execution is abnormal. The anomaly indication information is used by the first communication device to re-evaluate the first URSP rule of the terminal to obtain the second URSP rule.

35. A URSP rule optimization device, characterized in that, The device includes: A receiving module is configured to receive an eighth message from a third communication device; the eighth message includes a target PDU session identifier; The processing module is used to evaluate the execution status of the terminal's first URSP rule in the target PDU session corresponding to the target PDU session identifier; The sending module is used to send a ninth message to the third communication device; Wherein, the target PDU session is a PDU session that should not contain traffic of the target application; the traffic of the target application is the traffic of the terminal matching the PDU session according to the first URSP rule; the ninth message is used to indicate that the execution of the first URSP rule is abnormal, the ninth message is used by the third communication device to send abnormal indication information to the first communication device, and the abnormal indication information is used to trigger the first communication device to re-evaluate the first URSP rule of the terminal to obtain the second URSP rule.

36. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the URSP rule optimization method as described in any one of claims 11 to 18.

37. A network-side device, characterized in that, The method includes a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the URSP rule optimization method as described in any one of claims 1 to 10, or implement the steps of the URSP rule optimization method as described in any one of claims 19 to 22, or implement the steps of the URSP rule optimization method as described in any one of claims 23 to 27, or implement the steps of the URSP rule optimization method as described in any one of claims 28 to 30.

38. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the URSP rule optimization method as described in any one of claims 1 to 10, or the steps of the URSP rule optimization method as described in any one of claims 11 to 18, or the steps of the URSP rule optimization method as described in any one of claims 19 to 22, or the steps of the URSP rule optimization method as described in any one of claims 23 to 27, or the steps of the URSP rule optimization method as described in any one of claims 28 to 30.

Images