Traffic redirection control method and apparatus, communication device, and storage medium

Abstract

The application relates to a traffic redirection control method and device, a communication device, a storage medium and a computer program product. The method comprises the following steps: receiving a routing redirection application submitted by an application function (AF), and judging whether the AF is allowed to submit the routing redirection application according to registration information corresponding to the AF; if the AF is allowed to submit the routing redirection application, determining an update condition corresponding to the routing redirection application according to the type of the routing redirection application, and judging whether the routing redirection application meets the update condition; and in the case that the routing redirection application meets the update condition, updating a target redirection route in a unified data repository (UDR) according to the routing redirection application. The method can improve the reliability of the traffic redirection control method.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile communication security, and in particular to a traffic redirection control method and device, a communication device, a storage medium and a computer program product. BACKGROUND

[0002] 3GPP (3rd Generation Partnership Project) specifies that an AF (Application Function) can send a request to 5GC (5th Generation Mobile Communication Technology Core Network) NFs (Network Functions) to influence the traffic routing decision (Traffic Routing) of a PDU Session (Protocol Data Unit Session). When the AF is in an untrusted domain such as MEC, the redirection request is submitted via the NEF.

[0003] The current traffic redirection control method is that the AF submits redirection information to the NEF (Network Exposure Function), and the NEF updates the routing decision in the UDR (Unified Data Repository) according to the redirection information to obtain an updated UDR.

[0004] However, when the edge AF is under unlicensed control, it will submit malicious redirection information to the NEF to divert traffic to suspicious places, resulting in user data leakage or service unavailability. Therefore, the reliability of the current traffic redirection control method is low. SUMMARY

[0005] The embodiments of the present application provide a traffic redirection control method, device, communication device, storage medium and computer program product, which can divert traffic to a trusted place, protect user data, provide services for users, and improve the reliability of the traffic redirection control method.

[0006] In a first aspect, the present application provides a traffic redirection method. The method comprises:

[0007] receiving a routing redirection application submitted by an application function AF, and determining whether to allow the AF to submit the routing redirection application according to registration information corresponding to the AF;

[0008] If the AF is allowed to submit the route redirection application, according to the type of the route redirection application, an update condition corresponding to the route redirection application is determined, and it is judged whether the route redirection application satisfies the update condition;

[0009] In the case where the route redirection application satisfies the update condition, a target redirection route in a unified data repository function (UDR) is updated according to the route redirection application.

[0010] In one of the embodiments, before the route redirection application submitted by the application function (AF) is received, the method further comprises:

[0011] Registration information of the application function (AF) is received, and according to service attribute information contained in the registration information, it is determined whether the AF can perform a traffic redirection request, and an execution result is obtained;

[0012] According to the execution result, a redirection request field corresponding to the AF is determined;

[0013] According to the redirection request field, the registration information of the AF is updated;

[0014] According to a deployment physical position of the AF, a data network access identifier (DNAI) list corresponding to the AF is determined; the DNAI list is used to judge whether a route redirection application satisfies an update condition.

[0015] In one of the embodiments, the route redirection application submitted by the application function (AF) is received, and whether the AF is allowed to submit the route redirection application is judged according to the registration information corresponding to the AF, which comprises:

[0016] The route redirection application submitted by the application function (AF) is received, and based on the identity of the AF in the route redirection application, the registration information corresponding to the AF is queried;

[0017] According to the redirection request field in the registration information corresponding to the AF, it is judged whether the AF is allowed to submit the route redirection application.

[0018] In one of the embodiments, after it is judged whether the AF is allowed to submit the route redirection application according to the registration information corresponding to the AF, the method further comprises:

[0019] In the case where the AF is not allowed to submit the route redirection application, the route redirection application is ignored.

[0020] In one of the embodiments, when the AF is allowed to submit the route redirection application, according to the type of the route redirection application, the update condition corresponding to the route redirection application is determined, and it is judged whether the route redirection application satisfies the update condition, comprising:

[0021] When the AF is allowed to submit the route redirection application, the type of the route redirection application is determined;

[0022] When the type is the creation type or the update type, it is judged whether the destination DNAIs changed by the route redirection application are in the DNAI list corresponding to the AF;

[0023] When the destination DNAIs are in the DNAI list corresponding to the AF, it is determined that the route redirection application satisfies the update condition.

[0024] In one of the embodiments, after the type of the route redirection application is determined when the AF is allowed to submit the route redirection application, the method further comprises:

[0025] When the type is the deletion type, it is judged whether the target AF of the target redirection route is the same as the AF; the target redirection route is the redirection route to be deleted in the route redirection application;

[0026] When the target AF of the target redirection route is the same as the AF, it is determined that the route redirection application satisfies the update condition.

[0027] In one of the embodiments, when the route redirection application satisfies the update condition, according to the route redirection application, the target redirection route in the UDR is updated, comprising:

[0028] When the route redirection application satisfies the update condition, when the type of the route redirection application is the creation type or the update type, according to the route redirection application, the destination DNAIs in the UDR are updated;

[0029] When the type is the deletion type, the target redirection route in the UDR is deleted.

[0030] In a second aspect, the application further provides a traffic redirection control device. The device comprises:

[0031] A receiving module is configured to receive a route redirection application submitted by an AF, and according to the registration information corresponding to the AF, it is judged whether the AF is allowed to submit the route redirection application;

[0032] determining an update condition corresponding to the route redirection application according to a type of the route redirection application, and judging whether the route redirection application meets the update condition, if the AF is allowed to submit the route redirection application;

[0033] updating a target redirection route in a unified data repository function (UDR) according to the route redirection application, if the route redirection application meets the update condition.

[0034] In a third aspect, the present application provides a communication device, comprising a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0035] receiving a route redirection application submitted by an application function (AF), and judging whether the AF is allowed to submit the route redirection application according to registration information corresponding to the AF;

[0036] determining an update condition corresponding to the route redirection application according to a type of the route redirection application, and judging whether the route redirection application meets the update condition, if the AF is allowed to submit the route redirection application;

[0037] updating a target redirection route in a unified data repository function (UDR) according to the route redirection application, if the route redirection application meets the update condition.

[0038] In a fourth aspect, the present application provides a computer readable storage medium. The computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the following steps:

[0039] receiving a route redirection application submitted by an application function (AF), and judging whether the AF is allowed to submit the route redirection application according to registration information corresponding to the AF;

[0040] determining an update condition corresponding to the route redirection application according to a type of the route redirection application, and judging whether the route redirection application meets the update condition, if the AF is allowed to submit the route redirection application;

[0041] updating a target redirection route in a unified data repository function (UDR) according to the route redirection application, if the route redirection application meets the update condition.

[0042] In a fifth aspect, the present application provides a computer program product. The computer program product comprises a computer program, and the computer program is executed by a processor to implement the following steps:

[0043] Receive a route redirection request submitted by an application function (AF), and determine whether to allow the AF to submit the route redirection request based on the registration information corresponding to the AF;

[0044] If the AF is allowed to submit the route redirection request, the update conditions corresponding to the route redirection request are determined according to the type of the route redirection request, and it is determined whether the route redirection request meets the update conditions;

[0045] If the route redirection request meets the update conditions, the target redirection route in the Unified Data Warehouse Function (UDR) is updated according to the route redirection request.

[0046] The aforementioned traffic redirection control method, apparatus, communication device, storage medium, and computer program product receive a route redirection request submitted by an Application Function (AF). Based on the registration information corresponding to the AF, it determines whether the AF is allowed to submit the route redirection request. If the AF is allowed, it determines the update conditions corresponding to the route redirection request based on the type of the request and determines whether the request meets the update conditions. If the request meets the update conditions, it updates the target redirection route in the Unified Data Warehouse Function (UDR) according to the request. This method, by verifying whether the AF is allowed to submit a route redirection request and determining whether the request meets the update conditions, eliminates malicious redirection information, directs traffic to trusted locations, protects user data, provides services to users, and improves the reliability of the traffic redirection control method. Attached Figure Description

[0047] Figure 1 This is a flowchart illustrating a traffic redirection control method in one embodiment;

[0048] Figure 2 This is a flowchart illustrating the AF registration steps in one embodiment;

[0049] Figure 3 This is a flowchart illustrating the steps for determining whether to allow an application to be submitted by an AF in one embodiment;

[0050] Figure 4 This is a flowchart illustrating the steps for determining whether a route redirection request meets the update conditions in one embodiment;

[0051] Figure 5 This is a flowchart illustrating the execution of a non-deletion type redirection request step in one embodiment;

[0052] Figure 6This is a flowchart illustrating the steps for determining whether a route redirection request meets the update conditions, as shown in another embodiment.

[0053] Figure 7 This is a flowchart illustrating the steps of executing a deletion-type redirection request in one embodiment;

[0054] Figure 8 This is a flowchart illustrating the UDR update step in one embodiment;

[0055] Figure 9 This is a structural block diagram of a flow redirection control device in one embodiment;

[0056] Figure 10 This is an internal structural diagram of a traffic redirection control device in one embodiment. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0058] Before introducing specific embodiments of the present invention, the technical terms involved in the present invention will be explained:

[0059] Application Function (AF): refers to various services at the application layer. These can be internal applications of the operator or third-party AFs (such as video servers and game servers). If it is an internal AF of the operator, it is in the same trusted domain as other NFs and can directly interact and access other NFs such as PCF (Policy Control Function). However, third-party AFs are not in the trusted domain and must access other NFs through NEF.

[0060] Network Exposure Function (NEF): Located between the 5G core network and external third-party application functionalities (and possibly some internal AFs), it is responsible for managing the network data exposed to the outside world. All external applications wishing to access data within the 5G core network must go through the NEF. The NEF provides corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, and offers functions such as opening up external application QoS (Quality of Service) customization capabilities, mobility state event subscription, and AF request distribution.

[0061] Unified Data Repository (UDR): A unified data repository for storing user data and policy information. NEF can update user-related data in the UDR, including routing decisions and policy information, as needed based on redirection requests.

[0062] Destination Network Access Identifier (DNAI): A DNAI is a symbol or string used to uniquely identify a target network in a mobile network. It can identify a network area, a specific network operator, or a specific network node. The structure and format of a DNAI may vary depending on different mobile communication standards or protocols.

[0063] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0064] In one embodiment, such as Figure 1 As shown, a traffic redirection method is provided. Taking the application of this method to Network Open Function (NEF) as an example, the method includes the following steps:

[0065] Step 102: Receive the route redirection request submitted by the application function (AF), and determine whether to allow the AF to submit the route redirection request based on the registration information corresponding to the AF.

[0066] Routing redirection requests are used to update routing decisions in the UDR. Furthermore, routing redirection requests include three types: creation, update, and deletion.

[0067] In implementation, the NEF receives route redirection requests submitted by application functions (AFs). Then, the NEF determines the registration information corresponding to the AF based on the AF's identifier in the route redirection request. Finally, based on the registration information corresponding to the AF, the NEF determines whether to allow the AF to submit a route redirection request.

[0068] Step 104: If AF is allowed to submit route redirection requests, determine the update conditions corresponding to the route redirection request based on the type of the route redirection request, and determine whether the route redirection request meets the update conditions.

[0069] Different types of route redirection requests correspond to different update conditions.

[0070] In implementation, if the AF is allowed to submit route redirection requests, the NEF determines the update conditions corresponding to the route redirection request based on its type. Then, the NEF uses the information contained in the route redirection request to determine whether the request meets the update conditions. The update conditions are the criteria used to determine whether a route redirection request is compliant.

[0071] Step 106: If the route redirection request meets the update conditions, update the target redirection route in the Unified Data Warehouse Function UDR according to the route redirection request.

[0072] The target redirect route is the redirect route that needs to be created, updated, or deleted in the route redirection request.

[0073] In practice, if the route redirection request meets the update conditions, the target redirection route is updated in the Unified Data Warehouse (UDR) function based on the information contained in the route redirection request.

[0074] Optionally, NEF may ignore a route redirection request if the update conditions are not met.

[0075] In the above traffic redirection method, by verifying whether AF is allowed to submit a route redirection request and determining whether the route redirection request meets the update conditions, malicious redirection information is excluded, so that traffic is diverted to a trusted location, protecting user data, providing services to users, and improving the reliability of the traffic redirection control method.

[0076] In one embodiment, before receiving a route redirection request submitted by the AF, it is necessary to determine the AF's registration information. For example... Figure 2 As shown, before step 102 is executed, the traffic redirection control method further includes:

[0077] Step 202: Receive the registration information of the application function (AF), and determine whether the AF can execute the traffic redirection request based on the business attribute information contained in the registration information, and obtain the execution result.

[0078] The registration information of the AF includes the AF's business attributes and its physical deployment location. The execution result indicates whether the AF can execute a traffic redirection request.

[0079] In implementation, NEF receives registration information from application function (AF). Then, based on the business attribute information contained in the registration information, NEF determines whether the AF can execute a traffic redirection request and obtains the execution result.

[0080] Step 204: Based on the execution result, determine the redirection request field corresponding to AF.

[0081] In implementation, NEF generates a redirection request field for the AF based on the execution result. NEF can then use this redirection request field to determine whether to allow the AF to submit a route redirection request.

[0082] Step 206: Update the AF registration information based on the redirection request field.

[0083] In practice, NEF adds the redirect request field to the AF's registration information to obtain the updated AF registration information.

[0084] Step 208: Determine the list of Data Network Access Identifiers (DNAIs) corresponding to the AF based on the physical location of the AF deployment.

[0085] The DNAI list is used to determine whether a route redirection request meets the update conditions.

[0086] In implementation, NEF determines the list of DNs (Destination Networks) corresponding to the AF based on the physical location of the AF deployment. Then, NEF determines the DNAI corresponding to each DN in the DN list, thus obtaining the DNAI list.

[0087] In this embodiment, the registration information of the AF is received, and the redirection request field and DNAI list are determined based on the deployment physical location information and attribute information contained in the registration information. The conditions for updating the UDR are obtained, which facilitates subsequent determination of whether to update the target redirection route.

[0088] In one embodiment, such as Figure 3 As shown, the specific processing steps of step 102 include:

[0089] Step 302: Receive the route redirection request submitted by the application function AF, and query the registration information corresponding to the AF based on the AF identifier in the route redirection request.

[0090] The route redirection request includes the target redirection route that needs to be created, updated, or deleted, and the identifier of the AF that sent the route redirection request.

[0091] In implementation, NEF receives route redirection requests submitted by Application Functions (AFs). Then, based on the AF identifier in the route redirection request, NEF queries the AF registration information database for the corresponding AF.

[0092] Step 304: Determine whether to allow the AF to submit a route redirection request based on the redirection request field in the AF's registration information.

[0093] In implementation, NEF determines whether to allow an AF to submit a route redirection request based on the redirection request field in the AF's registration information. Specifically, if the redirection request field indicates that the AF can execute a traffic redirection request, NEF determines that the AF can submit a route redirection request. If the redirection request field indicates that the AF cannot execute a traffic redirection request, NEF determines that the AF cannot submit a route redirection request.

[0094] In this embodiment, by obtaining the registration information of the AF and determining whether the AF is allowed to submit a redirection request based on the registration information, route redirection requests submitted by non-compliant AFs are excluded, malicious redirection information is excluded, and the security of the traffic redirection control method is improved.

[0095] In one embodiment, if AF (Automatic Traffic Assist) is not allowed to submit route redirection requests, the route redirection request will be ignored. After step 102 is executed, the traffic route redirection control method further includes:

[0096] If AF is not allowed to submit route redirection requests, ignore the route redirection requests.

[0097] In practice, NEF ignores this route redirection request if AF is not allowed to submit it.

[0098] In this embodiment, by ignoring the route redirection information submitted by AF, malicious redirection information is avoided, thus improving the security of the traffic redirection control method.

[0099] In one embodiment, such as Figure 4 As shown, the specific processing steps of step 104 include:

[0100] Step 402: If AF is allowed to submit route redirection requests, determine the type of route redirection request.

[0101] In implementation, if AF is allowed to submit route redirection requests, NEF determines the type of route redirection request.

[0102] Step 404: If the type is creation type or update type, determine whether the destination DNAIs to be changed in the route redirection request are in the DNAI list corresponding to AF.

[0103] In implementation, if the type is creation or update, NEF queries the UDR for the DNAI list corresponding to the AF based on the AF's identifier. Then, NEF determines whether the destination DNAIs for the route redirection request change are in the DNAI list corresponding to the AF.

[0104] Step 406: If the destination DNAIs are in the DNAI list corresponding to AF, determine that the route redirection request meets the update conditions.

[0105] In practice, if the destination DNAIs are in the DNAI list corresponding to AF, NEF determines that the route redirection request meets the update conditions.

[0106] Optionally, if the destination DNAIs are not in the DNAI list corresponding to AF, NEF determines that the route redirection request does not meet the update conditions.

[0107] In one exemplary embodiment, such as Figure 5 As shown, the Application Firewall (AF) submits a route redirection request to the Service Provider Engine (NEF) using either the `Nnef_TrafficInfluence Create` or `Nnef_TrafficInfluence Update` method. The NEF determines whether to allow the AF to submit the route redirection request based on the `Application RelocatienPossibility` information in the AF's registration information. If the AF is not allowed to submit the route redirection request, the NEF refuses to execute it. Then, the NEF constructs an alarm message based on the route redirection information and transmits it to the target user. If the AF is allowed to submit the route redirection request, the NEF determines whether the target DNAIs requested to be changed are in the pre-configured DNAI list during registration. If the target DNAIs are not in the pre-configured DNAI list, the NEF determines that the route redirection request is non-compliant and ignores it. If the target DNAIs are in the pre-configured DNAI list, the NEF updates the User Router (UDR).

[0108] In this embodiment, the DNAI list corresponding to AF is used to determine whether to execute a route redirection request of the creation or update type. This excludes malicious redirection information, directs traffic to trusted locations, protects user data, provides services to users, and improves the reliability of the traffic redirection control method.

[0109] In one embodiment, if the route redirection request is of type delete, it is necessary to determine whether the target AF is the same as the AF. For example... Figure 6 As shown, after step 402 is executed, the processing procedure of this traffic redirection control method further includes:

[0110] Step 602: If the type is deletion type, determine whether the target AF of the target redirection route is the same as the AF.

[0111] The target redirect route is the redirect route that needs to be deleted that is included in the route redirection request.

[0112] In implementation, if the route redirection request is of the deletion type, NEF determines whether the target AF of the target redirection route is the same as the AF.

[0113] Step 604: If the target AF of the target redirection route is the same as AF, determine that the route redirection request meets the update conditions.

[0114] In practice, if the target AF of the target redirection route is the same as the AF, the NEF determines that the route redirection request meets the update conditions.

[0115] Optionally, if the target AF of the target redirection route is different from the AF, the NEF determines that the route redirection request does not meet the update conditions.

[0116] In one exemplary embodiment, such as Figure 7 As shown, the Application Filter (AF) submits an Nnef_TrafficInfluence Delete (delete a route affecting service) redirection request to the Service Filter (NEF). The NEF determines whether to allow the AF to submit the redirection request based on the ApplicationRelocatienPossibility information in the AF's registration information. If the AF is not allowed to submit the redirection request, the NEF refuses to execute the request. Then, the NEF constructs an alarm message based on the redirection information and transmits it to the target user. If the AF is allowed to submit the redirection request, the NEF determines whether the deleted redirection was previously requested by the AF. If the deleted redirection was not previously requested by the AF, the NEF determines that the redirection request is non-compliant and ignores it. If the deleted redirection was previously requested by the AF, the NEF updates the User Router (UDR).

[0117] In this embodiment, by determining whether the target AF in the route redirection request is the same as the AF that sent the route redirection request, non-compliant route redirection requests are excluded, allowing traffic to be redirected to a trusted location, protecting user data, providing services to users, and improving the reliability of the traffic redirection control method.

[0118] In one embodiment, such as Figure 8 As shown, the specific processing steps of step 106 include:

[0119] Step 802: If the route redirection request meets the update conditions, and the type of the route redirection request is creation type or update type, update the destination DNAIs in the UDR according to the route redirection request.

[0120] In implementation, if a route redirection request meets the update conditions, and the request type is update, NEF updates the destination DNAIs in the UDR based on the request. If the request type is creation, NEF creates the destination route redirection in the UDR based on the request.

[0121] Step 804: If the type is deletion, delete the target redirect route in the UDR.

[0122] In practice, if the route redirection request is of the deletion type, NEF determines the target redirection route in the UDR and deletes the target redirection route.

[0123] In this embodiment, if the route redirection request meets the update conditions, the UDR is updated according to the route redirection request, and the updated UDR is obtained, thus completing the execution of the compliant route redirection request.

[0124] It should be understood that, although Figures 1 to 8 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figures 1 to 8 At least some of the steps in the process may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0125] In one embodiment, such as Figure 9 As shown, a traffic redirection control device 900 is provided, including: a receiving module 901, a judging module 902, and an updating module 903, wherein:

[0126] The receiving module 901 is used to receive route redirection requests submitted by application function AF, and determine whether to allow AF to submit route redirection requests based on the registration information corresponding to AF.

[0127] The judgment module 902 is used to determine the update conditions corresponding to the route redirection request based on the type of the route redirection request, and to determine whether the route redirection request meets the update conditions, if AF is allowed to submit route redirection requests.

[0128] The update module 903 is used to update the target redirection route in the Unified Data Warehouse Function UDR according to the route redirection request, provided that the update conditions are met.

[0129] In one exemplary embodiment, the traffic redirection control device 900 further includes:

[0130] The second receiving module is used to receive the registration information of the application function (AF), and determine whether the AF can execute the traffic redirection request based on the business attribute information contained in the registration information, and obtain the execution result.

[0131] The first determining module is used to determine the redirection request field corresponding to AF based on the execution result;

[0132] The first update module is used to update the AF registration information based on the redirection request fields.

[0133] The second determining module is used to determine the list of Data Network Access Identifiers (DNAIs) corresponding to the AF based on the physical location of the AF deployment; the DNAIs list is used to determine whether the route redirection request meets the update conditions.

[0134] In one exemplary embodiment, the receiving module 901 includes:

[0135] The first receiving submodule is used to receive route redirection requests submitted by application functions (AFs) and query the registration information corresponding to the AF based on the AF identifier in the route redirection request.

[0136] The first judgment submodule is used to determine whether to allow the AF to submit a route redirection request based on the redirection request field in the AF's registration information.

[0137] In one exemplary embodiment, the traffic redirection control device 900 further includes:

[0138] The ignore module is used to ignore route redirection requests when AF is not allowed to submit route redirection requests.

[0139] In one exemplary embodiment, the determination module 902 includes:

[0140] The first determination submodule is used to determine the type of route redirection request if AF is allowed to submit route redirection requests.

[0141] The second judgment submodule is used to determine whether the destination DNAIs of the route redirection request are in the DNAI list corresponding to AF if the type is creation type or update type.

[0142] The second determination submodule is used to determine whether the route redirection request meets the update conditions if the destination DNAIs are in the DNAI list corresponding to AF.

[0143] In one exemplary embodiment, the traffic redirection control device 900 further includes:

[0144] The second judgment module is used to determine whether the target AF of the target redirection route is the same as the AF if the type is deletion; the target redirection route is the redirection route that needs to be deleted contained in the route redirection request.

[0145] The third determination module is used to determine if the target AF of the target redirection route is the same as the AF, and to determine if the route redirection request meets the update conditions.

[0146] In one exemplary embodiment, the update module 903 includes:

[0147] The update submodule is used to update the destination DNAIs in the UDR if the route redirection request meets the update conditions and the route redirection request type is either creation or update.

[0148] The delete submodule is used to delete the target redirect route in the UDR if the type is delete.

[0149] Specific limitations regarding the flow redirection control device can be found in the limitations of the flow redirection control method described above, and will not be repeated here. Each module in the aforementioned flow redirection control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in a computer device, or stored in software in the memory of a computer device, so that the processor can call and execute the operations corresponding to each module.

[0150] Figure 10 This is a schematic diagram of the structure of the access network device provided in an embodiment of the present invention. Figure 10 The access network device 1000 shown includes at least one processor 1001, a memory 1002, and at least one network interface 1004. The various components in the access network device 1000 are coupled together via a bus system 1005. It is understood that the bus system 1005 is used to implement communication between these components. In addition to a data bus, the bus system 1005 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 10 Various buses are labeled as bus system 1005. Additionally, this embodiment of the invention includes a transceiver 1006, which may consist of multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0151] It is understood that the memory 1002 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1002 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0152] In some implementations, memory 1002 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 10021. Operating system 10021 includes various system programs, such as framework layers, core library layers, driver layers, etc., used to implement various basic business functions and handle hardware-based tasks.

[0153] In this embodiment of the invention, by calling the program or instructions stored in the memory 1002, the processor is configured to determine whether the AF is allowed to submit a route redirection request based on the registration information corresponding to the AF; if the AF is allowed to submit a route redirection request, the processor determines the update conditions corresponding to the route redirection request based on the type of the route redirection request, and determines whether the route redirection request meets the update conditions; if the route redirection request meets the update conditions, the processor updates the target redirection route in the unified data warehouse function UDR according to the route redirection request; the receiver is configured to receive the route redirection request submitted by the application function AF.

[0154] The methods disclosed in the above embodiments of the present invention, in part or in all of them, can also be applied to processor 1001, implemented by processor 1001, or implemented by processor 1001 in conjunction with other components (e.g., transceivers). Processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above methods can be completed by the integrated logic circuit of the hardware in processor 1001 or by instructions in the form of software. The processor 1001 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 1002. Processor 1001 reads the information in memory 1002 and, in conjunction with its hardware, completes the steps of the above method.

[0155] It is understood that the embodiments described in this invention can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.

[0156] For software implementation, the technology described in the embodiments of the present invention can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present invention. The software code can be stored in memory and executed by processor 1001. The memory can be implemented in processor 1001 or external to processor 1001.

[0157] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0158] In one embodiment, a computer program product including instructions is provided, comprising a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0159] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0160] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0161] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A traffic redirection control method, characterized in that, The method includes: Receive the registration information of the application function (AF), and determine whether the AF can execute a traffic redirection request based on the business attribute information contained in the registration information, and obtain the execution result; Based on the execution result, determine the redirection request field corresponding to the AF; Update the AF's registration information according to the redirection request field; Based on the physical location of the AF deployment, determine the data network access identifier (DNAI) list corresponding to the AF; the DNAI list is used to determine whether the route redirection request meets the update conditions. Receive a route redirection request submitted by an application function (AF), and query the registration information corresponding to the AF based on the identifier of the AF in the route redirection request; Based on the redirection request field in the registration information corresponding to the AF, determine whether the AF is allowed to submit a route redirection request; If the AF is allowed to submit the route redirection request, determine the type of the route redirection request; If the type is deletion type, determine whether the target AF of the target redirection route is the same as the AF; the target redirection route is the redirection route that needs to be deleted included in the route redirection request; If the target AF of the target redirection route is the same as the AF, it is determined that the route redirection request meets the update conditions; If the type is a creation type or an update type, determine whether the destination DNAIs to be changed by the route redirection request are in the DNAI list corresponding to the AF; If the destination DNAIs are in the DNAI list corresponding to the AF, it is determined that the route redirection request meets the update conditions; If the route redirection request meets the update conditions, the target redirection route in the Unified Data Warehouse Function (UDR) is updated according to the route redirection request.

2. The method according to claim 1, characterized in that, The route redirection request includes the target redirection route to be created, updated, or deleted, and the identifier of the AF that sent the route redirection request.

3. The method according to claim 1, characterized in that, The step of determining whether to allow the AF to submit a route redirection request based on the redirection request field in the registration information corresponding to the AF includes: If the redirection request field in the registration information corresponding to the AF indicates that the AF can execute a traffic redirection request, then the AF is allowed to submit a route redirection request. If the redirection request field in the registration information corresponding to the AF indicates that the AF cannot execute a traffic redirection request, then it is determined that the AF is not allowed to submit a route redirection request.

4. The method according to claim 1, characterized in that, After determining whether the AF is allowed to submit the route redirection request based on the registration information corresponding to the AF, the method further includes: If the AF is not allowed to submit a route redirection request, the route redirection request is ignored.

5. The method according to claim 1, characterized in that, When the route redirection request meets the update conditions, updating the target redirection route in the Unified Data Warehouse Function (UDR) according to the route redirection request includes: If the route redirection request meets the update conditions, and if the type of the route redirection request is the creation type or the update type, the destination DNAIs are updated in the UDR according to the route redirection request; If the type is the deletion type, delete the target redirect route in the UDR.

6. The method according to claim 5, characterized in that, If the route redirection request is of the creation type or the update type, updating the destination DNAIs in the UDR according to the route redirection request includes: If the route redirection request is of type update, the destination DNAIs are updated in the UDR according to the route redirection request; If the route redirection request is of type creation, a target route redirection is created in the UDR according to the route redirection request.

7. A flow redirection control device, characterized in that, The device includes: The second receiving module is used to receive the registration information of the application function (AF), and determine whether the AF can execute a traffic redirection request based on the business attribute information contained in the registration information, and obtain the execution result. The first determining module is used to determine the redirection request field corresponding to the AF based on the execution result; The first update module is used to update the registration information of the AF according to the redirection request field; The second determining module is used to determine the Data Network Access Identifier (DNAI) list corresponding to the AF based on the physical location of the AF deployment; the DNAI list is used to determine whether the route redirection request meets the update conditions. The receiving module is specifically used to receive route redirection requests submitted by application functions (AFs), and query the registration information corresponding to the AF based on the identifier of the AF in the route redirection request; and determine whether to allow the AF to submit a route redirection request based on the redirection request field in the registration information corresponding to the AF. The determination module is specifically used to determine the type of the route redirection request if the AF is allowed to submit the route redirection request; if the type is a creation type or an update type, determine whether the destination DNAIs changed by the route redirection request are in the DNAI list corresponding to the AF; if the destination DNAIs are in the DNAI list corresponding to the AF, determine that the route redirection request meets the update conditions; The second judgment module is used to determine whether the target AF of the target redirection route is the same as the AF if the type is deletion type; the target redirection route is the redirection route that needs to be deleted included in the route redirection application; The third determining module is used to determine that the route redirection request meets the update conditions if the target AF of the target redirection route is the same as the AF. The update module is used to update the target redirection route in the Unified Data Warehouse Function (UDR) according to the route redirection request, provided that the update conditions are met.

8. The apparatus according to claim 7, characterized in that, The device further includes: The ignore module is used to ignore the route redirection request if the AF is not allowed to submit a route redirection request.

9. A communication device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images