Method and apparatus for updating routing policy, related device and storage medium

Abstract

Embodiments of the present application disclose a routing policy updating method and device, related equipment and a storage medium. The method comprises: receiving a routing policy issued by a network device, wherein the issued routing policy comprises a policy generation attribute; and when it is determined that the routing policy needs to be updated according to the policy generation attribute in the issued routing policy, updating a stored routing policy by using the issued routing policy. By introducing the parameter of the policy generation attribute into the routing policy, the updating mechanism of the routing policy can be optimized, the routing policy can be updated in time and effectively, and the waste of processing resources can be avoided.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, related equipment and storage medium for updating a routing strategy. Background Technology

[0002] In a communication system, user equipment (UE) can obtain a UE route selection policy (URSP) from the network device, and then perform operations such as establishing and binding Protocol Data Unit (PDU) sessions based on this URSP. Currently, each time the UE receives a URSP from the network device, it usually updates its stored URSP directly using the URSP sent by the network device. However, in practical applications, there may be situations where the URSP sent by the network device is the same as the URSP already stored in the UE, and the UE cannot determine whether the URSP sent by the network device is the same as the URSP already stored in the UE. In this case, updating the URSP in this way can lead to a waste of processing resources on the UE side. Furthermore, the network device cannot determine whether the URSP already stored by the UE is the latest URSP, and therefore cannot determine whether the UE's URSP needs to be updated. Summary of the Invention

[0003] This application provides a method, apparatus, related devices, and storage medium for updating routing policies, which can optimize the updating mechanism of routing policies, realize timely and effective updating of routing policies, and avoid waste of processing resources.

[0004] In a first aspect, embodiments of this application provide a method for updating a routing policy, the method being executable by a user equipment, the method comprising:

[0005] Receive routing selection policies sent by network devices, wherein the sent routing selection policies include policy generation attributes;

[0006] When it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

[0007] On the other hand, embodiments of this application provide a routing policy update apparatus, which can operate in a user equipment and may include:

[0008] A receiving unit is used to receive a routing policy sent by a network device, wherein the sent routing policy includes a policy generation attribute.

[0009] The update unit is used to update the stored routing policy using the issued routing policy when it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy.

[0010] On the other hand, embodiments of this application provide a user equipment, the user equipment including an input interface and an output interface, and the computer equipment further includes:

[0011] A processor, adapted to implement one or more instructions; and,

[0012] A computer-readable storage medium storing one or more instructions adapted for loading by the processor and performing the following steps:

[0013] Receive routing selection policies sent by network devices, wherein the sent routing selection policies include policy generation attributes;

[0014] When it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

[0015] In another aspect, embodiments of this application provide a computer-readable storage medium storing one or more instructions adapted for loading by a processor and executing the aforementioned method for updating the routing strategy.

[0016] This application's embodiments introduce a policy generation attribute parameter into the routing policy. This allows the user equipment (UE) to, upon receiving a routing policy from the network device, first determine, based on the policy generation attribute in the policy, whether an update to the routing policy already stored in its local space is necessary. If an update is deemed required, the UE then uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving efficient routing policy updates. Furthermore, it optimizes the routing policy update mechanism without changing the Policy Segment Identifier (PSI) of the routing policy, avoiding misjudgments that the routing policy does not need updating due to PSI comparison, thereby reducing routing policy mismatch problems and achieving timely routing policy updates.

[0017] Secondly, embodiments of this application provide a method for updating a routing policy, which can be executed by a network device and may include:

[0018] Receive policy generation attributes reported by user devices;

[0019] If it is determined from the reported policy generation attributes that the routing policy of the user equipment needs to be updated, then the routing policy is sent to the user equipment, and the sent routing policy includes the policy generation attributes.

[0020] The policy generation attribute in the issued routing policy is used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0021] On the other hand, embodiments of this application provide a routing policy update apparatus, which can operate in a network device and may include:

[0022] The receiving unit is used to receive policy generation attributes reported by user equipment;

[0023] The sending unit is used to send a routing policy to the user equipment if it is determined from the reported policy generation attributes that the routing policy needs to be updated. The sent routing policy includes policy generation attributes.

[0024] The policy generation attribute in the issued routing policy is used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0025] Furthermore, embodiments of this application provide a network device, which includes an input interface and an output interface, and the computer device further includes:

[0026] A processor adapted to implement one or more instructions; and a computer-readable storage medium storing one or more instructions adapted to be loaded by the processor and executed as follows:

[0027] Receive policy generation attributes reported by user devices;

[0028] If it is determined from the reported policy generation attributes that the routing policy of the user equipment needs to be updated, then the routing policy is sent to the user equipment, and the sent routing policy includes the policy generation attributes.

[0029] The policy generation attribute in the issued routing policy is used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0030] In another aspect, embodiments of this application provide a computer-readable storage medium storing one or more instructions adapted for loading by a processor and executing the aforementioned method for updating the routing strategy.

[0031] This application embodiment introduces a policy generation attribute parameter into the routing policy, enabling user equipment (UE) to report the policy generation attribute of its stored routing policy to the network device. The network device can then determine whether a routing policy update for the UE is necessary based on the reported policy generation attribute. If an update is required, the network device sends the current routing policy to the UE. This avoids misjudging the need for an update due to PSI comparison, reducing routing policy mismatch issues and ensuring timely updates. Furthermore, by sending a routing policy containing the policy generation attribute to the UE, the network device allows the UE to more accurately determine whether an update to its locally stored routing policy is needed based on the policy generation attribute. When an update is deemed necessary, the network device then uses the routing policy sent by the network device to update the stored routing policy promptly. This update method avoids the problem of performing policy update operations even when the issued routing policy is the same as the stored routing policy. It ensures the effectiveness of the policy update operation, avoids wasting processing resources, and achieves effective updating of routing policies.

[0032] Thirdly, embodiments of this application provide a method for updating a routing policy, the method being executable by a user equipment, the method comprising:

[0033] Receive routing selection policies and corresponding policy segment identifiers (PSIs) sent by network devices. The sent PSIs include the policy generation attributes of the sent routing selection policies.

[0034] When it is determined that a routing policy update is required based on the policy generation attributes in the issued PSI, the issued routing policy is used to update the stored routing policy.

[0035] On the other hand, embodiments of this application provide a routing policy update apparatus, which can operate in a user equipment and may include:

[0036] The receiving unit is used to receive the routing policy and the corresponding policy segment identifier (PSI) sent by the network device. The sent PSI includes the policy generation attribute of the sent routing policy.

[0037] The update unit is used to update the stored routing policy using the issued routing policy when it is determined that a routing policy update is required based on the policy generation attributes in the issued PSI.

[0038] On the other hand, embodiments of this application provide a user equipment, the user equipment including an input interface and an output interface, and the computer equipment further includes:

[0039] A processor adapted to implement one or more instructions; and a computer-readable storage medium storing one or more instructions adapted to be loaded by the processor and executed as follows:

[0040] Receive routing selection policies and corresponding policy segment identifiers (PSIs) sent by network devices. The sent PSIs include the policy generation attributes of the sent routing selection policies.

[0041] When it is determined that a routing policy update is required based on the policy generation attributes in the issued PSI, the issued routing policy is used to update the stored routing policy.

[0042] In another aspect, embodiments of this application provide a computer-readable storage medium storing one or more instructions adapted for loading by a processor and executing the aforementioned method for updating the routing strategy.

[0043] This application's embodiments introduce a policy generation attribute parameter into the PSI of the routing policy. This allows the user equipment (UE) to, upon receiving the routing policy and corresponding PSI from the network device, first determine, based on the policy generation attribute in the PSI, whether to update the routing policy already stored locally. When an update is deemed necessary, the UE uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving effective routing policy updates. Furthermore, it optimizes the routing policy update mechanism, preventing misjudgments due to comparing existing content in the PSI, thus reducing routing policy mismatches and achieving timely updates.

[0044] Fourthly, embodiments of this application provide a method for updating a routing policy, which can be executed by a network device, and the method may include:

[0045] The routing selection policy and the corresponding policy segment identifier (PSI) are sent to the user equipment. The sent PSI includes the policy generation attribute of the routing selection policy.

[0046] The policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0047] On the other hand, embodiments of this application provide a routing policy update apparatus, which can operate in a network device and may include:

[0048] The distribution unit is used to distribute routing selection policies and corresponding policy segment identifiers (PSIs) to user equipment. The distributed PSIs include the policy generation attributes of the distributed routing selection policies.

[0049] The policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0050] Furthermore, embodiments of this application provide a network device, which includes an input interface and an output interface, and the computer device further includes:

[0051] A processor adapted to implement one or more instructions; and a computer-readable storage medium storing one or more instructions adapted to be loaded by the processor and executed as follows:

[0052] The routing selection policy and the corresponding policy segment identifier (PSI) are sent to the user equipment. The sent PSI includes the policy generation attribute of the routing selection policy.

[0053] The policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0054] In another aspect, embodiments of this application provide a computer-readable storage medium storing one or more instructions adapted for loading by a processor and executing the aforementioned method for updating the routing strategy.

[0055] This application's embodiments introduce a policy generation attribute parameter into the PSI of the routing policy. This allows the network device to send a PSI containing the policy generation attribute to the user equipment. The user equipment can then use this attribute to more accurately determine whether to update the routing policy already stored locally. When an update is deemed necessary, the user equipment uses the routing policy sent by the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the sent and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving efficient routing policy updates. Furthermore, it optimizes the routing policy update mechanism, preventing misjudgments due to comparing existing content in the PSI, thus reducing routing policy mismatches and achieving timely updates.

[0056] Fifthly, embodiments of this application provide a computer program product, which includes a computer program; when the computer program is executed by a processor, it implements the update method of any of the routing selection strategies mentioned above. Attached Figure Description

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

[0058] Figure 1b This is a system architecture diagram of another communication system provided in the embodiments of this application;

[0059] Figure 2 This is a flowchart illustrating a method for updating a routing strategy according to an embodiment of this application;

[0060] Figure 3 This is a schematic diagram illustrating the logic of a user equipment determining whether to update its routing policy, as provided in an embodiment of this application.

[0061] Figure 4 This is a flowchart illustrating a method for updating a routing strategy according to another embodiment of this application;

[0062] Figure 5a This is a schematic diagram illustrating the logic of a network device determining whether to update its routing policy, provided in another embodiment of this application.

[0063] Figure 5b This is a schematic diagram illustrating the logic of another network device in another embodiment of this application for determining whether to update the routing policy;

[0064] Figure 6 This is a flowchart illustrating a method for updating a routing strategy according to another embodiment of this application;

[0065] Figure 7 This is a schematic diagram of the structure of a routing strategy update device provided in an embodiment of this application;

[0066] Figure 8 This is a schematic diagram of the structure of a routing strategy update device provided in another embodiment of this application;

[0067] Figure 9 This is a schematic diagram of the structure of a user equipment provided in an embodiment of this application;

[0068] Figure 10 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0070] In this application embodiment, the Routing Selection Policy (URSP) can be understood as a policy used by the UE to select different PDU sessions for service flows, which can contain multiple Rules (referred to as URSP rules). Specifically, URSP rules can include, but are not limited to, Traffic descriptors and Route Selection descriptors (RSDs), where the Traffic descriptors can include Application identifiers, Internet Protocol (IP) descriptors, non-IP descriptors, etc. Each UE's URSP can be identified by the UE policy section identifier (UPSI), which can also be abbreviated as PSI (policy section identifier). This application embodiment addresses the issue of updating the routing selection policy by proposing a policy update scheme to optimize the update mechanism of the routing selection policy, achieve timely and effective updates of the routing selection policy, and avoid waste of processing resources.

[0071] In practical implementation, this strategy update scheme can be applied to various communication systems, such as: Global System of Mobile communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), New Radio (NR), Worldwide Interoperability for Microwave Access (WiMAX), 5th Generation Mobile Communication Technology (5G), or future mobile communication technology systems.

[0072] Specifically, the communication system in which the policy update scheme proposed in this application is applied may include at least: a UE (User Equipment) 11 and a network device 12. The UE 11 may be a mobile or fixed device, and may be configured for wired or wireless interface communication, without limitation. Optionally, the UE 11 may include any of the following: an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, an Internet of Things (IoT) device, a terminal device in a 5G network, or a terminal device in a future Public Land Mobile Network (PLMN), etc.

[0073] Network device 12 refers to a device capable of sending URSP (Route Selection Policy) to UE 11. For example, network device 12 can be a core network device on the network side. The core network device mentioned here can be a 5G core network device, such as a Policy Control Function (PCF), Access and Mobility Management Function (AMF), or Session Management Function (SMF). Alternatively, the core network device mentioned here can also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF + PGW-C) device. It should be understood that this is merely an illustrative example of several specific implementations of network device 12, and not an exhaustive list; in other embodiments, network device 12 can also be other devices capable of communicating with UE 11, and this is not limited. Furthermore, for ease of explanation, the following description will use PCF as an example of network device.

[0074] When network device 12 is a core network device, the communication system used in this embodiment may further include access network device 13; the access network device 13 can provide communication coverage for a specific geographical area and communicate with user equipment located within that coverage area, and the access network device 13 can communicate with the core network device. That is, in this case, UE11 is located within the coverage area of ​​access network device 13, and UE11 and network device 12 transmit data through access network device 13. Optionally, the access network device 13 can be a network-side device in a 5G network; or, the access network device 13 can be a network-side device in a PLMN; or, the access network device 13 can be a base station (gNB) in a Radio Access Network (RAN) or NR system; or, the access network device 13 can be a network-side device (Base Transceiver Station, BTS) in a GSM or CDMA system; or, the access network device 13 can be a network-side device (NodeB, NB) in a WCDMA system; or, the access network device 13 can be an evolved network device (Evolutionary Node B, eNB or eNodeB) in an LTE system; or, the access network device 13 can be a radio controller in a Cloud Radio Access Network (CRAN); or, the access network device 13 can be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, or router, etc.

[0075] Taking access network device 13 as a base station as an example, the communication system used in this application embodiment can be found in [reference needed]. Figure 1a As shown. It should be understood that, Figure 1a This illustration merely demonstrates the system architecture of the communication system used in the embodiments of this application and does not limit its scope. For example, Figure 1aThe communication system shown only exemplarily illustrates two UEs 11, one network device 12, and one access network device 13. However, in practical applications, the communication system may include more access network devices 13, and the coverage area of ​​each access network device 13 may include other terminal devices; or, the communication system may include more network devices, which is not limited in this application embodiment. For example, the communication system may also include other network elements such as a Unified Data Repository (UDR), a Core Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), Unified Data Management (UDM), and a Signaling Gateway (SGW), which is not limited in this application embodiment. When the communication system includes a UDR 14, the network device 12 can communicate with the UDR 14, such as... Figure 1b As shown; furthermore, network device 12 can also store the URSP and corresponding PSI involved in each UE11 into the UDR.

[0076] In the above Figure 1b In the communication system shown, the UE can trigger the URSP reporting procedure. This reporting procedure can be triggered during the UE's initial registration procedure, during the mobility management procedure when the UE switches from EPS (Evolved Packet System) to a 5G network, or in other procedures; there are no limitations on this. Furthermore, when the UE discovers that its internally stored URSP is lost, invalid, or missing, the UE can use the initial registration procedure to retrieve the URSP; that is, the UE can also trigger the reporting procedure when it discovers that its internally stored URSP is lost, invalid, or missing. When a UE performs a reporting procedure, it can include its stored PSI in the reporting procedure to report the stored PSI to the PCF. After receiving the PSI reported by the UE, the PCF can retrieve the latest PSI corresponding to the UE from the UDR, and then compare the PSI retrieved from the UDR with the PSI reported by the UE. If they are different, the PCF will use the URSP corresponding to the UE stored in the UDR as the updated URSP, and send the corresponding PSI stored in the UDR as the updated PSI to the UE, so that the UE can update its routing policy. The PSI can include the following two parts:

[0077] a) A PLMN ID part containing the PLMN ID of the PLMN of the PCF which provides the UE policies;

[0078] b) A UE policy section code (UPSC) containing a unique value within the PLMN selected by the PCF.

[0079] Practice has shown that since both parts of the PSI are relatively fixed—meaning the PSI remains unchanged even when the PLMN is determined and the rules in the URSP change—the PSI is merely an identifier and cannot indicate whether the rules in its corresponding URSP are updated (i.e., the latest rules). However, when the UE receives an updated PSI from the PCF, it may fail to update the corresponding URSP in a timely manner due to various reasons (such as a sudden UE crash during policy update or insufficient memory detected during policy update). In this case, after the UE reports the PSI to the PCF through the reporting process, the PCF, when comparing the PSI, may assume that the URSP stored by the UE is the latest URSP (i.e., the rules in the UE's stored URSP are the latest rules), thus mistakenly determining that there is no need to update the UE's URSP, leading to URSP mismatch issues. Furthermore, in practical applications, it is possible that after the PCF issues the URSP, it may issue the URSP repeatedly for some reason, resulting in the URSP issued by the PCF being the same as the URSP already stored in the UE. In this case, if the UE directly uses the URSP issued by the PCF to update the stored URSP, it will lead to a waste of processing resources.

[0080] Based on this, the policy update scheme proposed in this application introduces a policy generation attribute in the URSP (Route Selection Policy) or PSI. Here, the policy generation attribute refers to a parameter allocated to the route selection policy during its generation, used to uniquely identify the route selection policy. For example, the policy generation attribute may include one or more of the following: a version number parameter of the route selection policy, a timestamp parameter of the route selection policy, etc. The version number parameter of the route selection policy can be allocated to the URSP each time the PCF updates the rules in the URSP; and each allocated version number parameter can be generated by incrementing the previous version number parameter by one (+1), or it can be generated by a random algorithm. This application does not limit the generation method of the version number parameter. A timestamp parameter is used to indicate the generation time of the corresponding route selection policy; that is, the timestamp parameter of the route selection policy can be allocated to the URSP based on the current system time each time the PCF updates the rules in the URSP.

[0081] Since policy generation attributes can uniquely identify URSPs, by introducing policy generation attributes into URSPs or PSIs, UEs can report the policy generation attributes corresponding to the stored URSPs to the PCF through the reporting process. After receiving the policy generation attributes reported by the UE, the PCF can accurately determine whether the UE's URSP needs to be updated by comparing the latest policy generation attributes corresponding to the UE in the UDR with the policy generation attributes reported by the UE. If it is determined that an update is needed, the PCF will send the URSP corresponding to the UE stored in the UDR and the corresponding PSI to the UE so that the UE can update its routing policy. This avoids the situation where the routing policy does not need to be updated due to the comparison of the two parts in the PSI, thereby reducing the occurrence of routing policy mismatch problems and realizing timely updates of routing policies. Furthermore, after receiving the URSP and PSI sent by the PCF, the UE can also determine whether to use the URSP sent by the PCF to perform a policy update operation by comparing whether the policy generation attributes in the URSP or PSI sent by the PCF are the same as the policy generation attributes already stored by the UE. This ensures the effectiveness of the policy update operation, avoids waste of processing resources, and achieves effective URSP updates. Therefore, the policy update scheme proposed in this application, by introducing policy generation attributes into the URSP or PSI, can effectively optimize the routing policy update mechanism, achieve timely and effective updates of the routing policy, and avoid waste of processing resources.

[0082] It should be noted that the above is only based on Figure 1bThe example of the communication system shown illustrates the general principle of the policy update scheme proposed in this application, but does not limit it. For instance, the PCF may not store the URSPs and corresponding PSIs of each UE in the UDR, but instead store these data in its own storage space. In this case, the PCF can directly obtain the latest URSPs, corresponding PSIs, policy generation attributes, and other data of the UE from its own storage space, and then perform a series of processes based on the obtained data.

[0083] Based on the foregoing description, this application proposes a method for updating a routing policy, which can be executed by a user equipment in the aforementioned communication system. Please refer to... Figure 2 The method may include the following steps S201-S202:

[0084] S201, Receive routing selection policy sent by network device.

[0085] In this application, any routing policy may include a policy generation attribute; that is, a routing policy issued by a network device may include a policy generation attribute, and a routing policy stored in the local space of a user device may also include a policy generation attribute. Furthermore, any policy generation attribute mentioned in the embodiments of this application may include: a version number parameter or a timestamp parameter of the corresponding routing policy, without limitation. In other words, the policy generation attribute in a issued routing policy includes: a version number parameter of the issued routing policy, or a timestamp parameter of the issued routing policy; the policy generation attribute in a stored routing policy includes: a version number parameter of the stored routing policy, or a timestamp parameter of the stored routing policy.

[0086] In one implementation, after receiving a routing policy from a network device, the user equipment can compare the policy generation attributes in the sent routing policy with the policy generation attributes in stored routing policies. If the policy generation attributes in the sent routing policy are different from those in the stored routing policies, it is determined that a routing policy update is required; if the policy generation attributes in the sent routing policy are the same as those in the stored routing policies, it is determined that no routing policy update is required.

[0087] In another implementation, in addition to issuing routing policies, the network device can also issue a Policy Segment Identifier (PSI) for the routing policies. The issued PSI is used by the user equipment (UE) to determine whether a routing policy update is needed. Correspondingly, the UE can receive not only the routing policies issued by the network device but also the PSIs issued by the network device, such as... Figure 3 As shown in the diagram. The network device can send the routing policy and corresponding PSI to the user equipment via a single signaling message, or it can send the routing policy and corresponding PSI to the user equipment separately via different signaling messages; this is not limited. In this case, the user equipment can compare the sent PSI with the PSI of the stored routing policy, and compare the policy generation attributes in the sent routing policy with the policy generation attributes in the stored routing policy. If the sent PSI is the same as the PSI of the stored routing policy, and the policy generation attributes in the sent routing policy are different from those in the stored routing policy, then a routing policy update is required; if the sent PSI is the same as the PSI of the stored routing policy, and the policy generation attributes in the sent routing policy are the same as those in the stored routing policy, then no routing policy update is required.

[0088] Based on the above description, when the policy generation attribute includes a version number parameter, the logic by which the user equipment (UE) determines whether a routing policy update is needed can be understood as follows: When the UE receives a URSP, it compares the received PSI (i.e., the PSI issued by the network device) with the stored PSI, and also compares the version number parameter in the received URSP with the version number parameter in the stored URSP. When the two PSIs are the same, it can be assumed that the two PSIs refer to the same URSP; however, only when the two version number parameters are also the same is it considered that the received URSP and the stored URSP are the same, and in this case, it can be determined that no routing policy update is needed. If the two version number parameters are different, it can be assumed that the received URSP and the stored URSP are different, and the stored URSP needs to be updated to synchronize with the latest URSP policy generated by the network device.

[0089] Based on the above description, when the policy generation attribute includes a timestamp parameter, the logic by which the user equipment (UE) determines whether a routing policy update is needed can be understood as follows: When the UE receives a URSP, it compares the received PSI (i.e., the PSI issued by the network device) with the stored PSI, and also compares the timestamp parameter in the received URSP with the timestamp parameter in the stored URSP. When the two PSIs are the same, it can be assumed that the two PSIs refer to the same URSP; however, only when the two timestamp parameters are also the same is it considered that the received URSP and the stored URSP are the same, and in this case, it can be determined that no routing policy update is needed. If the two timestamp parameters are different, it can be assumed that the received URSP and the stored URSP are different, and the stored URSP needs to be updated to synchronize with the latest URSP policy generated by the network device.

[0090] It should be noted that when the user equipment performs the steps of comparing the PSI to be issued with the PSI of the stored routing policy, and comparing the policy generation attribute in the issued routing policy with the policy generation attribute in the stored routing policy, these two steps can be performed simultaneously or in a certain order. This embodiment does not limit this. Furthermore, optionally, if the PSI comparison step is performed before the policy generation attribute comparison step, then when the user equipment finds that the two PSIs are different, it can directly determine that the two PSIs target different URSPs. In this case, it can directly determine that a routing policy update is needed, without further performing the policy generation attribute comparison operation, thus effectively saving processing resources.

[0091] S202, when it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

[0092] In practical implementation, when a user equipment updates a stored routing policy using a newly issued routing policy, it can do so using either a full update or a momentum update. A full update includes directly replacing the existing routing policy with the newly issued one. A momentum update involves determining that the newly issued routing policy contains updated content relative to the existing routing policy, and then replacing the corresponding content in the existing routing policy with that updated content.

[0093] This application's embodiments introduce a policy generation attribute parameter into the routing policy. This allows the user equipment (UE) to, upon receiving a routing policy from the network device, first determine, based on the policy generation attribute in the policy, whether an update to the routing policy already stored in its local space is necessary. If an update is deemed required, the UE then uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving efficient routing policy updates. Furthermore, it optimizes the routing policy update mechanism without changing the Policy Segment Identifier (PSI) of the routing policy, avoiding misjudgments that the routing policy does not need updating due to PSI comparison, thereby reducing routing policy mismatch problems and achieving timely routing policy updates.

[0094] Please see Figure 4 This is another method for updating routing strategies provided in the embodiments of this application. For example... Figure 4 As shown, the method may include the following steps S401-S405:

[0095] S401, the user equipment reports the policy generation attribute of the stored routing policy to the network device.

[0096] The stored routing policy's policy generation attribute is used by the network device to determine whether the routing policy for the user equipment needs to be updated. Accordingly, the network device can receive the policy generation attribute reported by the user equipment; and upon receiving the policy generation attribute reported by the user equipment, it executes step S402.

[0097] S402, the network device generates attributes based on the reported policy to determine whether the routing policy for the user equipment needs to be updated.

[0098] In a specific implementation, the network device can compare the reported policy generation attributes with the policy generation attributes in the current routing policy. If the reported policy generation attributes differ from those in the current routing policy, it is determined that the routing policy for the user equipment needs to be updated; if the reported policy generation attributes are the same as those in the current routing policy, it is determined that no routing policy update is needed for the user equipment. Here, the current routing policy refers to the latest URSP corresponding to the user equipment stored in the network device or UDR. In one implementation, when the current routing policy is located in the UDR, the network device can send an attribute query request to the UDR to request the UDR to return the policy generation attributes in the current routing policy, thereby performing subsequent policy generation attribute comparison operations. In another implementation, when the current routing policy is located in the UDR, the network device can send a policy retrieval request to the UDR. The policy retrieval request includes the PSI of the current routing policy. The policy retrieval request is used to request the UDR to return the current routing policy corresponding to the PSI. After receiving the routing policy returned by the UDR, the network device can extract the policy generation attribute from the routing policy returned by the UDR and then perform subsequent policy generation attribute comparison operations.

[0099] In another implementation, when the current routing policy is located in the UDR, the network device can send a policy update judgment request to the UDR, requesting the UDR to determine whether a routing policy update for the user equipment is needed based on the reported policy generation attributes. In this case, the policy update judgment request may include the PSI of the current routing policy and the reported policy generation attributes; the UDR can determine the current routing policy based on the PSI in the policy update judgment request, and compare the policy generation attributes in the policy acquisition request with the policy generation attributes in the current routing policy. This allows the UDR to return the current routing policy corresponding to the PSI and the comparison result to the network device when it detects that the two policy generation attributes are different, and to return the comparison result to the network device when it detects that the two policy generation attributes are the same.

[0100] Optionally, in addition to reporting the policy generation attributes of the stored routing policies to the network device, the user equipment can also report the policy segment identifier (PSI) of the stored routing policies. The PSI of the stored routing policies is used by the network device to determine whether a routing policy update for the user equipment is needed. The user equipment can report the policy generation attributes and corresponding PSI of the stored routing policies to the network device via a single signaling message, or it can report them separately via different signaling messages; there is no limitation on this method.

[0101] In this scenario, the network device can also receive the Policy Segmentation Identifier (PSI) reported by the user equipment. Then, the network device can compare the reported PSI with the PSI of the current routing policy, and compare the reported policy generation attributes with the policy generation attributes in the current routing policy. If the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attributes are different from the policy generation attributes in the current routing policy, then a routing policy update is required; if the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attributes are the same as the policy generation attributes in the current routing policy, then no routing policy update is required. Wherein, when the current routing policy and its corresponding PSI are located in the UDR, the network device can request the UDR to return the policy generation attributes and corresponding PSI of the current routing policy, thereby performing subsequent comparison operations of the policy generation attributes and PSI, such as... Figure 5a As shown; alternatively, the network device can request the UDR to return the current routing policy and the corresponding PSI, and then, upon receiving the routing policy returned by the UDR, extract the policy generation attribute from the routing policy returned by the UDR, and then perform subsequent comparison operations between the policy generation attribute and the PSI, such as... Figure 5b As shown.

[0102] Based on the above description, when the policy generation attribute includes a version number parameter, when the user equipment (UE) sends its own PSI to the network device, it needs to simultaneously send the version number parameter from the stored URSP. In this case, the logic of the network device in determining whether a routing policy update is needed can be understood as follows: comparing the received PSI (i.e., the PSI reported by the UE) with the PSI of the current URSP, and comparing the received version number parameter (i.e., the version number parameter reported by the UE) with the version number parameter in the current URSP. When the two PSIs are the same, but the two version number parameters are different, the network device can determine that a routing policy update is needed. At this time, it can initiate the URSP update process to trigger the issuance of the current URSP to the UE. When both PSIs are the same and both version number parameters are the same, the network device can consider the URSP stored in the UE to be the latest and does not need to be updated.

[0103] Based on the above description, when the policy generation attribute includes a timestamp parameter, when the user equipment (UE) sends its own PSI to the network device, it needs to simultaneously send the timestamp parameter from the stored URSP. In this case, the logic of the network device in determining whether a routing policy update is needed can be understood as follows: comparing the received PSI (i.e., the PSI reported by the UE) with the PSI of the current URSP, and comparing the received timestamp parameter (i.e., the timestamp parameter reported by the UE) with the timestamp parameter in the current URSP. When the two PSIs are the same, but the two timestamp parameters are different, the network device can determine that a routing policy update is needed. At this time, it can initiate the URSP update process to trigger the issuance of the current URSP to the UE. When both PSIs are the same and both timestamp parameters are the same, the network device can consider the URSP stored in the UE to be up-to-date and does not need to be updated.

[0104] It should be noted that when the network device performs the steps of comparing the reported PSI with the PSI of the current routing policy, and comparing the reported policy generation attributes with the policy generation attributes in the current routing policy, these two steps can be performed simultaneously or in a certain order. This embodiment does not limit this. Furthermore, optionally, if the PSI comparison step is performed before the policy generation attribute comparison step, then when the network device finds that the two PSIs are different, it can directly determine that a routing policy update is needed without further performing the policy generation attribute comparison operation, thus effectively saving processing resources.

[0105] Additionally, when the current routing policy is in the UDR, the network device can also send the reported PSI and the reported policy generation attributes to the UDR, so that the UDR can perform the steps of comparing the reported PSI with the PSI of the current routing policy, and comparing the reported policy generation attributes with the policy generation attributes in the current routing policy, thereby returning the comparison results to the network device; and, when it is determined that a routing policy update is required, returning the current routing policy to the network device.

[0106] S403, if it is determined from the reported policy generation attributes that the routing policy for the user equipment needs to be updated, the network device triggers the step of sending the routing policy to the user equipment, that is, triggers the execution of step S404.

[0107] S404, the network device sends a routing policy to the user equipment.

[0108] As mentioned above, the network device sends a routing policy to the user equipment after determining that a routing policy update is needed. Furthermore, the policy generation attribute in the sent routing policy is used by the user equipment to determine whether a routing policy update is necessary. When the user equipment determines that a routing policy update is needed, the sent routing policy is used to update the routing policy already stored in the user equipment.

[0109] S405 When the user equipment determines that a routing policy update is required based on the policy generation attribute in the issued routing policy, it uses the issued routing policy to update the stored routing policy.

[0110] This application's embodiments introduce a policy generation attribute parameter into the routing policy. This allows the network device, upon receiving a policy generation attribute reported by a user equipment (UE), to accurately determine whether the UE's URSP needs updating by comparing the current URSP's policy generation attribute with that reported by the UE. If an update is deemed necessary, the network device sends the current URSP to the UE to update its routing policy. This avoids misjudging the routing policy as unnecessary due to PSI comparison, thus reducing routing policy mismatch issues and ensuring timely updates. Furthermore, upon receiving a URSP from the network device, the UE can also compare the policy generation attribute in the sent URSP with its stored attributes to determine whether to use the sent URSP for policy updates. This ensures the effectiveness of policy updates, avoids wasting processing resources, and achieves efficient URSP updates.

[0111] It should be noted that the above Figure 2 and Figure 4 The method embodiments shown are all illustrated by adding a policy generation attribute to the routing policy. In other embodiments, a policy generation attribute can also be added to the PSI to identify different versions of the URSP rule content; for example, when the policy generation attribute is a version number parameter, the PSI may include the following three parts:

[0112] a) a PLMN ID part containing the PLMN ID of the PLMN of the PCF which provides the UE policies;

[0113] b)a UE policy section code(UPSC)containing a unique value within the PLMN selected by the PCF;

[0114] c) URSP version number parameter.

[0115] When the PLMN and UPSC are determined, each time the network device updates the URSP rule, it assigns a new version number parameter to the URSP rule, such as incrementing the version number parameter by 1. Based on this, when introducing policy generation attributes into PSI, this application also proposes a corresponding method for updating routing policies; see [link to relevant documentation]. Figure 6 As shown, the method may include the following steps S601-S605:

[0116] S601, the user equipment reports the PSI of the stored routing policy to the network device. The reported PSI is used by the network device to determine whether the routing policy of the user equipment needs to be updated. The reported PSI may include the policy generation attribute of the stored routing policy.

[0117] Correspondingly, the network device can receive the PSI reported by the user equipment; and after receiving the PSI reported by the user equipment, it can first compare a) in the reported PSI with a) in the PSI of the current routing policy, and compare b) in the reported PSI with b) in the PSI of the current routing policy; when a) and b) in the two PSIs are the same, step S602 can be triggered.

[0118] S602, the network device determines whether the routing policy needs to be updated for the user equipment based on the policy generation attributes in the reported PSI.

[0119] In practice, network devices can compare the policy generation attributes in the reported PSI with the policy generation attributes in the current routing policy's PSI. If the policy generation attributes in the reported PSI differ from those in the current PSI, it is determined that the routing policy for the user equipment needs to be updated; if the policy generation attributes in the reported PSI are the same as those in the current PSI, it is determined that the routing policy for the user equipment does not need to be updated.

[0120] Based on the above description, when the policy generation attribute includes a version number parameter, the logic of the network device in determining whether a routing policy update is needed can be understood as follows: The network device compares the contents of each part of the PSI reported by the UE with the contents of each part of the PSI retrieved from the UDR. When a) and b) are the same in both PSIs, but c) are different, the network device considers that the URSP rules in the user equipment need to be updated, and in this case, it can send the updated URSP (i.e., the current URSP) to the UE. When a), b), and c) are completely identical in both PSIs, the network device considers that the URSP rules in the user equipment do not need to be updated. It should be noted that when the policy generation attribute includes a timestamp parameter, the logic of the network device in determining whether a routing policy update is needed is similar to the logic mentioned here, and will not be repeated here.

[0121] S603, if it is determined from the policy generation attributes in the reported PSI that the routing policy needs to be updated for the user equipment, the network device triggers the step of sending the routing policy to the user equipment, that is, triggers the execution of step S604.

[0122] S604: Network devices send routing policies and corresponding PSIs to user equipment.

[0123] Correspondingly, the user equipment can receive routing policies and corresponding PSIs from the network device. Furthermore, after receiving the PSI from the network device, the user equipment can first compare a) in the sent PSI with a) in a previously stored PSI, and compare b) in the sent PSI with b) in a previously stored PSI; when a) and b) in both PSIs are the same, step S605 can be triggered.

[0124] S605: When the user equipment determines that a routing policy update is required based on the policy generation attributes in the issued PSI, it uses the issued routing policy to update the stored routing policy.

[0125] In practice, the user equipment can compare the policy generation attributes in the issued PSI with the policy generation attributes in the stored PSI. If the policy generation attributes in the issued PSI are different from those in the stored PSI, it is determined that the user equipment needs to update its routing policy; if the policy generation attributes in the issued PSI are the same as those in the stored PSI, it is determined that the user equipment does not need to update its routing policy.

[0126] Based on the above description, when the policy generation attribute includes a version number parameter, the logic by which the user equipment (UE) determines whether a routing policy update is needed can be understood as follows: The UE compares the contents of each part of the PSI issued by the network device with the contents of each part of the stored PSI. When a) and b) of the two PSIs are the same, the UE considers the two PSIs to correspond to the same URSP; only when the version number parameter (c) is also the same does the UE consider the issued URSP and the stored URSP to be the same. When the version number parameter (c) is different, the UE considers the stored URSP rules to need to be updated and synchronized with the latest URSP rules issued by the network device. It should be noted that when the policy generation attribute includes a timestamp parameter, the logic by which the UE determines whether a routing policy update is needed is similar to the logic mentioned here, and will not be repeated here.

[0127] This application's embodiments introduce a policy generation attribute parameter into the PSI (Plan-Based Service Indicator). This allows the network device, upon receiving a PSI reported by the user equipment (UE), to accurately determine whether the URSP (Uniform Routing Policy Parameter) in the UE needs updating by comparing the policy generation attributes of the two PSIs. If an update is deemed necessary, the current URSP is sent to the UE to update its routing policy. This avoids misjudging the routing policy as unnecessary due to comparing PSIs a) and b), thus reducing routing policy mismatch issues and ensuring timely updates. Furthermore, upon receiving the URSP and corresponding PSI from the network device, the UE can also determine whether to use the URSP sent by the network device for policy updates by comparing the policy generation attributes of the two PSIs. This ensures the effectiveness of the policy update operation, avoids wasting processing resources, and achieves efficient URSP updates.

[0128] Based on the description of the above method embodiments, this application also discloses a routing policy updating apparatus, which may be a computer program (including program code) running on a user equipment. Please refer to... Figure 7The routing policy update device can operate the following units: receiving unit 701, updating unit 702, and reporting unit 703, etc.

[0129] According to another embodiment of this application, Figure 7 The units in the routing strategy update apparatus shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the routing strategy update apparatus may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0130] According to another embodiment of this application, a computer program (including program code) capable of performing the steps involved in the updating method of the routing strategy mentioned above can be constructed by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), to perform the updating method of the routing strategy mentioned above. Figure 7 The diagram illustrates an apparatus for updating a routing policy, and a method for updating a routing policy to implement embodiments of this application. The computer program may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the same medium, and run therein.

[0131] In one embodiment, the units in the routing policy update apparatus can be used to perform the following operations:

[0132] The receiving unit 701 is used to receive a routing policy sent by a network device, wherein the sent routing policy includes a policy generation attribute.

[0133] The update unit 702 is used to update the stored routing policy using the issued routing policy when it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy.

[0134] In one implementation, the update unit 702 can also be used for:

[0135] Compare the policy generation attributes in the issued routing policy with the policy generation attributes in the stored routing policies;

[0136] If the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, then it is determined that the routing policy needs to be updated.

[0137] If the policy generation attribute in the issued routing policy is the same as the policy generation attribute in the stored routing policy, then it is determined that no routing policy update is required.

[0138] In another embodiment, the receiving unit 701 can also be used to: receive the policy segment identifier (PSI) of the routing policy issued by the network device;

[0139] The update unit 702 can also be used to: compare the issued PSI with the PSI of the stored routing policy, and compare the policy generation attribute in the issued routing policy with the policy generation attribute in the stored routing policy; if the issued PSI is the same as the PSI of the stored routing policy, and the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, then it is determined that a routing policy update is required; if the issued PSI is the same as the PSI of the stored routing policy, and the policy generation attribute in the issued routing policy is the same as the policy generation attribute in the stored routing policy, then it is determined that no routing policy update is required.

[0140] In another implementation, the reporting unit 703 can be used to: report the policy generation attributes in the stored routing policy to the network device;

[0141] The stored routing policy generation attribute is used by the network device to determine whether the routing policy needs to be updated for the user equipment; and the network device issues the routing policy to the user equipment after determining that the routing policy needs to be updated for the user equipment.

[0142] In another embodiment, the reporting unit 703 can also be used for:

[0143] Report the Policy Segment Identifier (PSI) of the stored routing policy to the network device;

[0144] The stored routing policy PSI is used by the network device to determine whether the routing policy needs to be updated for the user equipment.

[0145] This application's embodiments introduce a policy generation attribute parameter into the routing policy. This allows the user equipment (UE) to, upon receiving a routing policy from the network device, first determine, based on the policy generation attribute in the policy, whether an update to the routing policy already stored in its local space is necessary. If an update is deemed required, the UE then uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving efficient routing policy updates. Furthermore, it optimizes the routing policy update mechanism without changing the Policy Segment Identifier (PSI) of the routing policy, avoiding misjudgments that the routing policy does not need updating due to PSI comparison, thereby reducing routing policy mismatch problems and achieving timely routing policy updates.

[0146] In another embodiment, the units in the routing policy update apparatus can be used to perform the following operations:

[0147] The receiving unit 701 is used to receive the routing selection policy and the corresponding policy segment identifier (PSI) sent by the network device. The sent PSI includes the policy generation attribute of the sent routing selection policy.

[0148] The update unit 702 is used to update the stored routing policy using the issued routing policy when it is determined that a routing policy update is required based on the policy generation attributes in the issued PSI.

[0149] In one implementation, the reporting unit 703 can be used for:

[0150] The network device reports the stored routing policy information (PSI). This stored PSI is used by the network device to determine whether the routing policy for the user equipment needs to be updated. The PSI may include policy generation attributes.

[0151] In another embodiment, the receiving unit 701 can also be used to receive routing policies and corresponding PSIs issued by the network device.

[0152] In another embodiment, the update unit 702 can also be used for:

[0153] Compare the policy generation attributes in the issued PSI with the policy generation attributes in the stored PSI;

[0154] If the policy generation attributes in the issued PSI are different from the policy generation attributes in the stored PSI, then it is determined that the routing policy needs to be updated for the user equipment.

[0155] If the policy generation attributes in the issued PSI are the same as those in the stored PSI, then it is determined that there is no need to update the routing policy for the user equipment.

[0156] In another embodiment, the update unit 702 can also be used for:

[0157] Compare a) in the issued PSI with a) in the stored PSI, and compare b) in the issued PSI with b) in the stored PSI;

[0158] When both a) and b) in the two PSIs are the same, the step of comparing the policy generation attributes in the issued PSI with the policy generation attributes in the stored PSI can be triggered.

[0159] This application's embodiments introduce a policy generation attribute parameter into the PSI of the routing policy. This allows the user equipment (UE) to, upon receiving the routing policy and corresponding PSI from the network device, first determine, based on the policy generation attribute in the PSI, whether to update the routing policy already stored locally. When an update is deemed necessary, the UE uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving effective routing policy updates. Furthermore, it optimizes the routing policy update mechanism, preventing misjudgments due to comparing existing content in the PSI, thus reducing routing policy mismatches and achieving timely updates.

[0160] Based on the description of the above method embodiments, this application also discloses a routing policy updating apparatus, which may be a computer program (including program code) running in a network device. Please refer to... Figure 8 The routing policy update device can operate the following units: receiving unit 801, sending unit 803, and processing unit 803, etc.

[0161] According to another embodiment of this application, Figure 8The units in the routing strategy update apparatus shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the routing strategy update apparatus may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0162] According to another embodiment of this application, a computer program (including program code) capable of performing the steps involved in the updating method of the routing strategy mentioned above can be constructed by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), to perform the updating method of the routing strategy mentioned above. Figure 8 The diagram illustrates an apparatus for updating a routing policy, and a method for updating a routing policy to implement embodiments of this application. The computer program may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the same medium, and run therein.

[0163] In one embodiment, the units in the routing policy update apparatus can be used to perform the following operations:

[0164] The receiving unit 801 is used to receive policy generation attributes reported by the user equipment;

[0165] The issuing unit 802 is used to issue a routing policy to the user equipment if it is determined from the reported policy generation attributes that the routing policy needs to be updated. The issued routing policy includes policy generation attributes.

[0166] The policy generation attribute in the issued routing policy is used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0167] In one embodiment, the sending unit 802 can also be used for:

[0168] The user equipment is issued a policy segment identifier (PSI) for the routing policy. The issued PSI is used by the user equipment to determine whether the routing policy needs to be updated.

[0169] In another embodiment, the device may further include a processing unit 803, which may be used for:

[0170] Compare the reported policy generation attributes with the policy generation attributes in the current routing policy;

[0171] If the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that the routing policy of the user equipment needs to be updated.

[0172] If the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that there is no need to update the routing policy for the user equipment.

[0173] In another embodiment, the receiving unit 801 can also be used to receive the Policy Segmentation Identifier (PSI) reported by the user equipment;

[0174] The processing unit 803 can also be used to: compare the reported PSI with the PSI of the current routing policy, and compare the reported policy generation attribute with the policy generation attribute in the current routing policy; if the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that a routing policy update is required; if the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that a routing policy update is not required.

[0175] This application embodiment introduces a policy generation attribute parameter into the routing policy, enabling user equipment (UE) to report the policy generation attribute of its stored routing policy to the network device. The network device can then determine whether a routing policy update for the UE is necessary based on the reported policy generation attribute. If an update is required, the network device sends the current routing policy to the UE. This avoids misjudging the need for an update due to PSI comparison, reducing routing policy mismatch issues and ensuring timely updates. Furthermore, by sending a routing policy containing the policy generation attribute to the UE, the network device allows the UE to more accurately determine whether an update to its locally stored routing policy is needed based on the policy generation attribute. When an update is deemed necessary, the network device then uses the routing policy sent by the network device to update the stored routing policy promptly. This update method avoids the problem of performing policy update operations even when the issued routing policy is the same as the stored routing policy. It ensures the effectiveness of the policy update operation, avoids wasting processing resources, and achieves effective updating of routing policies.

[0176] In another embodiment, the units in the routing policy update apparatus can be used to perform the following operations:

[0177] The sending unit 802 is used to send routing selection policies and corresponding policy segment identifiers (PSIs) to user equipment. The sent PSIs include the policy generation attributes of the sent routing selection policies.

[0178] The policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0179] In one embodiment, the receiving unit 801 can be used to: receive PSI reported by the user equipment;

[0180] The processing unit 803 can be used to: determine whether the routing policy needs to be updated for the user equipment based on the policy generation attributes in the reported PSI.

[0181] In another embodiment, the processing unit 803 may also be used for:

[0182] Compare a) in the reported PSI with a) in the current routing policy PSI, and compare b) in the reported PSI with b) in the current routing policy PSI;

[0183] When both a) and b) in the two PSIs are the same, the step of determining whether the routing policy needs to be updated for the user equipment can be triggered based on the policy generation attributes in the reported PSI.

[0184] In another implementation, when processing unit 803 determines whether a routing policy update for the user equipment is needed based on the policy generation attributes in the reported PSI, it may specifically be used for:

[0185] Compare the policy generation attributes in the reported PSI with the policy generation attributes in the PSI of the current routing policy;

[0186] If the policy generation attributes in the reported PSI are different from the policy generation attributes in the current PSI, then it is determined that the routing policy of the user equipment needs to be updated.

[0187] If the policy generation attributes in the reported PSI are the same as the policy generation attributes in the current PSI, then it is determined that there is no need to update the routing policy for the user equipment.

[0188] This application's embodiments introduce a policy generation attribute parameter into the PSI of the routing policy. This allows the network device to send a PSI containing the policy generation attribute to the user equipment. The user equipment can then use this attribute to more accurately determine whether to update the routing policy already stored locally. When an update is deemed necessary, the user equipment uses the routing policy sent by the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the sent and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving efficient routing policy updates. Furthermore, it optimizes the routing policy update mechanism, preventing misjudgments due to comparing existing content in the PSI, thus reducing routing policy mismatches and achieving timely updates.

[0189] Based on the descriptions of the method and apparatus embodiments above, this application also provides a user equipment. Please refer to... Figure 9The user equipment includes at least a processor 901, an input interface 902, an output interface 903, and a computer-readable storage medium 904. The processor 901, input interface 902, output interface 903, and computer-readable storage medium 904 within the user equipment can be connected via a bus or other means. The computer-readable storage medium 904 can be stored in the user equipment's memory. The computer-readable storage medium 904 stores a computer program, which includes program instructions. The processor 901 executes the program instructions stored in the computer-readable storage medium 904. The processor 901 (or CPU (Central Processing Unit)) is the computing and control core of the user equipment, adapted to implement one or more instructions, specifically adapted to load and execute one or more instructions to achieve a corresponding method flow or function.

[0190] In one embodiment, the processor 901 described in this application can be used to perform a series of routing policy update processes, specifically including: receiving a routing policy issued by a network device, the issued routing policy including a policy generation attribute; when it is determined that a routing policy update is needed based on the policy generation attribute in the issued routing policy, updating a stored routing policy using the issued routing policy, etc. Alternatively, the processor 901 described in this application can be used to perform a series of routing policy update processes, specifically including: receiving a routing policy and a corresponding Policy Segmentation Identifier (PSI) issued by a network device, the issued PSI including a policy generation attribute of the issued routing policy; when it is determined that a routing policy update is needed based on the policy generation attribute in the issued PSI, updating a stored routing policy using the issued routing policy, etc.

[0191] Based on the descriptions of the above method and apparatus embodiments, this application also provides a network device. Please refer to... Figure 10The network device includes at least a processor 1001, an input interface 1002, an output interface 1003, and a computer-readable storage medium 1004. The processor 1001, input interface 1002, output interface 1003, and computer-readable storage medium 1004 within the network device can be connected via a bus or other means. The computer-readable storage medium 1004 can be stored in the network device's memory. The computer-readable storage medium 1004 stores a computer program, which includes program instructions. The processor 1001 executes the program instructions stored in the computer-readable storage medium 1004. The processor 1001 (or CPU (Central Processing Unit)) is the computing and control core of the network device, suitable for implementing one or more instructions, specifically suitable for loading and executing one or more instructions to achieve a corresponding method flow or function.

[0192] In one embodiment, the processor 1001 described in this application embodiment can be used to perform a series of routing policy update processes, specifically including: receiving policy generation attributes reported by a user equipment; if it is determined that the user equipment needs to perform a routing policy update based on the reported policy generation attributes, then issuing a routing policy to the user equipment, wherein the issued routing policy includes policy generation attributes; wherein the policy generation attributes in the issued routing policy are used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment, and so on. Alternatively, the processor 1001 described in this application embodiment can be used to perform a series of routing policy update processes, specifically including: issuing a routing policy and a corresponding policy segment identifier (PSI) to a user equipment, wherein the issued PSI includes a policy generation attribute of the issued routing policy; wherein the policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0193] This application also provides a computer-readable storage medium (Memory), which is a memory device in a computer device (such as the aforementioned user equipment or network device) for storing programs and data. It is understood that the computer-readable storage medium here can include both built-in storage media in the computer device and extended storage media supported by the computer device. The computer-readable storage medium provides storage space that stores the operating system of the computer device. Furthermore, the storage space also stores one or more instructions suitable for loading and execution by a processor, which can be one or more computer programs (including program code). It should be noted that the computer-readable storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0194] (a) When the computer equipment is a user equipment:

[0195] ① In one embodiment, a processor may load and execute one or more instructions stored in a computer-readable storage medium to implement the above-mentioned... Figure 2 or Figure 4 The corresponding steps in the embodiment of the routing policy update method are shown; in specific implementation, one or more instructions in the computer-readable storage medium are loaded by the processor and executed as follows:

[0196] Receive routing selection policies sent by network devices, wherein the sent routing selection policies include policy generation attributes;

[0197] When it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

[0198] In one implementation, the one or more instructions may also be loaded and executed by the processor:

[0199] Compare the policy generation attributes in the issued routing policy with the policy generation attributes in the stored routing policies;

[0200] If the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, then it is determined that the routing policy needs to be updated.

[0201] If the policy generation attribute in the issued routing policy is the same as the policy generation attribute in the stored routing policy, then it is determined that no routing policy update is required.

[0202] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0203] Receive the Policy Segment Identifier (PSI) of the routing policy issued by the network device;

[0204] The issued PSI is compared with the PSI of the stored routing policy, and the policy generation attribute in the issued routing policy is compared with the policy generation attribute in the stored routing policy.

[0205] If the issued PSI is the same as the PSI of the stored routing policy, and the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, then it is determined that a routing policy update is required.

[0206] If the issued PSI is the same as the PSI of the stored routing policy, and the policy generation attribute in the issued routing policy is the same as the policy generation attribute in the stored routing policy, then it is determined that no routing policy update is required.

[0207] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0208] Report the policy generation attributes of the stored routing policies to the network device;

[0209] The stored routing policy generation attribute is used by the network device to determine whether the routing policy needs to be updated for the user equipment; and the network device issues the routing policy to the user equipment after determining that the routing policy needs to be updated for the user equipment.

[0210] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0211] Report the Policy Segment Identifier (PSI) of the stored routing policy to the network device;

[0212] The stored routing policy PSI is used by the network device to determine whether the routing policy needs to be updated for the user equipment.

[0213] ②In another embodiment, a processor may load and execute one or more instructions stored in a computer-readable storage medium to implement the above-mentioned... Figure 6 The corresponding steps in the embodiment of the routing policy update method are shown; in specific implementation, one or more instructions in the computer-readable storage medium are loaded by the processor and executed as follows:

[0214] Receive routing selection policies and corresponding policy segment identifiers (PSIs) sent by network devices. The sent PSIs include the policy generation attributes of the sent routing selection policies.

[0215] When it is determined that a routing policy update is required based on the policy generation attributes in the issued PSI, the issued routing policy is used to update the stored routing policy.

[0216] In one implementation, the one or more instructions may also be loaded and executed by the processor:

[0217] The network device reports the stored routing policy information (PSI). The stored PSI is used by the network device to determine whether the routing policy of the user equipment needs to be updated. The PSI may include policy generation attributes.

[0218] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0219] Receive routing policies and corresponding PSIs from network devices.

[0220] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0221] Compare the policy generation attributes in the issued PSI with the policy generation attributes in the stored PSI;

[0222] If the policy generation attributes in the issued PSI are different from the policy generation attributes in the stored PSI, then it is determined that the routing policy needs to be updated for the user equipment.

[0223] If the policy generation attributes in the issued PSI are the same as those in the stored PSI, then it is determined that there is no need to update the routing policy for the user equipment.

[0224] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0225] Compare a) in the issued PSI with a) in the stored PSI, and compare b) in the issued PSI with b) in the stored PSI;

[0226] When both a) and b) in the two PSIs are the same, the step of comparing the policy generation attributes in the issued PSI with the policy generation attributes in the stored PSI can be triggered.

[0227] (ii) When the computer device is a network device:

[0228] ① In one embodiment, a processor may load and execute one or more instructions stored in a computer-readable storage medium to implement the above-mentioned... Figure 2 or Figure 4 The corresponding steps in the embodiment of the routing policy update method are shown; in specific implementation, one or more instructions in the computer-readable storage medium are loaded by the processor and executed as follows:

[0229] Receive policy generation attributes reported by user devices;

[0230] If it is determined from the reported policy generation attributes that the routing policy of the user equipment needs to be updated, then the routing policy is sent to the user equipment, and the sent routing policy includes the policy generation attributes.

[0231] The policy generation attribute in the issued routing policy is used by the user equipment to determine whether a routing policy update is needed; when the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0232] In one implementation, the one or more instructions may also be loaded and executed by the processor:

[0233] The user equipment is issued a policy segment identifier (PSI) for the routing policy. The issued PSI is used by the user equipment to determine whether the routing policy needs to be updated.

[0234] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0235] Compare the reported policy generation attributes with the policy generation attributes in the current routing policy;

[0236] If the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that the routing policy of the user equipment needs to be updated.

[0237] If the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that there is no need to update the routing policy for the user equipment.

[0238] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0239] Receive the Policy Segmentation Identifier (PSI) reported by the user equipment;

[0240] Compare the reported PSI with the PSI of the current routing policy, and compare the reported policy generation attributes with the policy generation attributes in the current routing policy.

[0241] If the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that a routing policy update is required.

[0242] If the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that no routing policy update is required.

[0243] ②In another embodiment, a processor may load and execute one or more instructions stored in a computer-readable storage medium to implement the above-mentioned... Figure 6 The corresponding steps in the embodiment of the routing policy update method are shown; in specific implementation, one or more instructions in the computer-readable storage medium are loaded by the processor and executed as follows:

[0244] The routing selection policy and the corresponding policy segment identifier (PSI) are sent to the user equipment. The sent PSI includes the policy generation attribute of the routing selection policy.

[0245] The policy generation attribute in the issued PSI is used by the user equipment to determine whether a routing policy update is required; when the user equipment determines that a routing policy update is required, the issued routing policy is used to update the routing policy already stored in the user equipment.

[0246] In one implementation, the one or more instructions may also be loaded and executed by the processor:

[0247] Receive PSI reported by user equipment;

[0248] Determine whether a routing policy update for the user equipment is needed based on the policy generation attributes in the reported PSI.

[0249] In another implementation, the one or more instructions may also be loaded and executed by the processor:

[0250] Compare a) in the reported PSI with a) in the current routing policy PSI, and compare b) in the reported PSI with b) in the current routing policy PSI;

[0251] When both a) and b) in the two PSIs are the same, the step of determining whether the routing policy needs to be updated for the user equipment can be triggered based on the policy generation attributes in the reported PSI.

[0252] In another implementation, when determining whether a routing policy update for the user equipment needs to be performed based on the policy generation attributes in the reported PSI, the one or more instructions can be loaded and executed by the processor:

[0253] Compare the policy generation attributes in the reported PSI with the policy generation attributes in the PSI of the current routing policy;

[0254] If the policy generation attributes in the reported PSI are different from the policy generation attributes in the current PSI, then it is determined that the routing policy of the user equipment needs to be updated.

[0255] If the policy generation attributes in the reported PSI are the same as the policy generation attributes in the current PSI, then it is determined that there is no need to update the routing policy for the user equipment.

[0256] This application's embodiments introduce a policy generation attribute parameter, enabling the user equipment (UE) to accurately determine whether to update the routing policy already stored in its local space after receiving a routing policy from the network device, based on the policy generation attribute in the policy. When an update is determined, the UE then uses the routing policy from the network device to update the stored policy promptly. This update method avoids the problem of performing a policy update operation even when the issued and stored routing policies are identical, ensuring the effectiveness of the update operation, avoiding wasted processing resources, and achieving effective routing policy updates. Furthermore, it optimizes the routing policy update mechanism without changing the Policy Segment Identifier (PSI) of the routing policy, avoiding misjudgments that the routing policy does not need updating due to PSI comparison, thereby reducing routing policy mismatch problems and achieving timely routing policy updates.

[0257] It should be noted that, according to one aspect of the embodiments of this application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the aforementioned actions. Figure 2 or Figure 4 or Figure 6 The method provided in various alternative ways in the embodiments of the routing policy update method shown.

[0258] Furthermore, it should be understood that the above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application are still within the scope of this application.

Claims

1. A method for updating a routing strategy, characterized in that, The method is executed by the user equipment and includes: The receiving network device sends routing selection policies and corresponding policy segment identifiers (PSIs) through different signaling. The sent routing selection policies include policy generation attributes, which are parameters allocated to the corresponding routing selection policies when generating routing selection policies and used to uniquely identify the corresponding routing selection policies. The issued PSI is compared with the PSI of the stored routing policy. If the issued PSI is the same as the PSI of the stored routing policy, the policy generation attribute in the issued routing policy is compared with the policy generation attribute in the stored routing policy. If the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, then it is determined that the routing policy needs to be updated. When it is determined that a routing policy update is required based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

2. The method as described in claim 1, characterized in that, The policy generation attribute in the issued routing policy includes: the version number parameter of the issued routing policy.

3. The method as described in claim 1, characterized in that, The policy generation attribute in the issued routing policy includes: the timestamp parameter of the issued routing policy; The timestamp parameter is used to indicate the generation time of the issued routing policy.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: If the policy generation attribute in the issued routing policy is the same as the policy generation attribute in the stored routing policy, then it is determined that no routing policy update is required.

5. The method according to any one of claims 1-3, characterized in that, The method further includes: Report the policy generation attributes of the stored routing policies to the network device; The stored routing policy generation attribute is used by the network device to determine whether the routing policy needs to be updated for the user equipment; and the network device issues the routing policy to the user equipment after determining that the routing policy needs to be updated for the user equipment.

6. The method as described in claim 5, characterized in that, The method further includes: Report the Policy Segment Identifier (PSI) of the stored routing policy to the network device; The stored routing policy PSI is used by the network device to determine whether the routing policy needs to be updated for the user equipment.

7. A method for updating a routing strategy, characterized in that, include: Receive policy generation attributes reported by user equipment. The policy generation attributes refer to parameters allocated to the corresponding routing policy when generating the routing policy, and used to uniquely identify the corresponding routing policy. If it is determined that the routing policy of the user equipment needs to be updated based on the reported policy generation attributes, then the routing policy and the corresponding policy segment identifier (PSI) are sent to the user equipment through different signaling. The sent routing policy includes the policy generation attributes. The policy generation attribute and the PSI in the issued routing policy are used by the user equipment to determine whether a routing policy update is needed. When the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

8. The method as described in claim 7, characterized in that, The reported policy generation attributes include: the version number parameter of the stored routing policy; The policy generation attribute in the issued routing policy includes: the version number parameter of the issued routing policy.

9. The method as described in claim 7, characterized in that, The reported policy generation attributes include: the timestamp parameter of the stored routing policy; The policy generation attribute in the issued routing policy includes: the timestamp parameter of the issued routing policy; One of the parameters, a timestamp parameter, is used to indicate the generation time of the corresponding routing policy.

10. The method according to any one of claims 7-9, characterized in that, The method further includes: Compare the reported policy generation attributes with the policy generation attributes in the current routing policy; If the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that the routing policy of the user equipment needs to be updated. If the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that there is no need to update the routing policy for the user equipment.

11. The method according to any one of claims 7-9, characterized in that, The method further includes: Receive the Policy Segmentation Identifier (PSI) reported by the user equipment, compare the reported PSI with the PSI of the current routing policy, and compare the reported policy generation attribute with the policy generation attribute in the current routing policy. If the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is different from the policy generation attribute in the current routing policy, then it is determined that a routing policy update is required. If the reported PSI is the same as the PSI of the current routing policy, and the reported policy generation attribute is the same as the policy generation attribute in the current routing policy, then it is determined that no routing policy update is required.

12. A routing policy update apparatus, characterized in that, The device operates in a user equipment and includes: The receiving unit is used to receive routing selection policies and corresponding policy segment identifiers (PSIs) sent by network devices through different signaling. The sent routing selection policies include policy generation attributes, which are parameters allocated to the corresponding routing selection policies when generating routing selection policies and used to uniquely identify the corresponding routing selection policies. The update unit is used to compare the issued PSI with the PSI of the stored routing policy, and when the issued PSI is the same as the PSI of the stored routing policy, compare the policy generation attribute in the issued routing policy with the policy generation attribute in the stored routing policy; if the policy generation attribute in the issued routing policy is different from the policy generation attribute in the stored routing policy, it is determined that a routing policy update is needed; when it is determined that a routing policy update is needed based on the policy generation attribute in the issued routing policy, the issued routing policy is used to update the stored routing policy.

13. A routing policy update apparatus, characterized in that, include: The receiving unit is used to receive policy generation attributes reported by the user equipment. The policy generation attributes refer to parameters allocated to the corresponding routing policy when generating the routing policy, and used to uniquely identify the corresponding routing policy. The sending unit is used to send a routing policy and a corresponding policy segment identifier (PSI) to the user equipment through different signaling if it is determined from the reported policy generation attributes that the routing policy needs to be updated. The sent routing policy includes policy generation attributes. The policy generation attribute and the PSI in the issued routing policy are used by the user equipment to determine whether a routing policy update is needed. When the user equipment determines that a routing policy update is needed, the issued routing policy is used to update the routing policy already stored in the user equipment.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more instructions, which are adapted to be loaded by a processor and executed as a method for updating a routing policy as described in any one of claims 1-6; or, the one or more instructions are adapted to be loaded by a processor and executed as a method for updating a routing policy as described in any one of claims 7-11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for updating the routing policy as described in any one of claims 1-6; or, when the computer program is executed by the processor, it implements the method for updating the routing policy as described in any one of claims 7-11.

Images