Request information processing method, system and device, computer device, readable storage medium and program product

Abstract

The application relates to a request information processing method, system and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: receiving abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when a domain name query request of an evolved packet gateway is received from a user equipment and the domain name of the evolved packet gateway cannot be returned; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service; according to the abnormal request information, an abnormal request scenario of the wireless network voice service is determined; a waiting time corresponding to the abnormal request scenario is obtained; according to the waiting time, a timer is sent to the user equipment; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time. By using the method, a signaling storm can be avoided, and network load can be reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and in particular to a request information processing method, system and device, computer equipment, computer readable storage medium and computer program product. BACKGROUND

[0002] With the development of communication technology, a technology of providing voice service through a wireless network appears. The wireless network voice technology can enable a communication device to make a call under the condition that there is no mobile signal, can complement the voice service based on mobile data, and effectively make up for the shortage of cellular coverage. However, in the application of the wireless network voice service technology, when the request of the communication device for the wireless network voice service is abnormal, a signaling storm is easily formed, and the network load is increased. SUMMARY

[0003] Therefore, it is necessary to provide a request information processing method, system, device, computer equipment, computer readable storage medium and computer program product for the above technical problems.

[0004] In a first aspect, the present application provides a request information processing method, comprising:

[0005] receiving abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when a domain name query request of an evolved packet gateway from a user equipment is received and the domain name of the evolved packet gateway cannot be returned; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service;

[0006] determining an abnormal request scenario of the wireless network voice service according to the abnormal request information;

[0007] obtaining a waiting time length corresponding to the abnormal request scenario;

[0008] sending a timer to the user equipment according to the waiting time length; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time length.

[0009] In one embodiment, the determining of the abnormal request scenario of the wireless network voice service according to the abnormal request information comprises: obtaining first request scenario information according to a network address of the user equipment contained in the abnormal request information; obtaining second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs; and determining the abnormal request scenario according to the first request scenario information and the second request scenario information.

[0010] In one of the embodiments, the first request scenario information is obtained according to the network address of the user equipment contained in the abnormal request information, including: determining the region information of the user equipment according to the network address; judging whether the region of the user equipment is the deployment region of the wireless network voice service according to the region information, to obtain a region abnormality judgment result; and obtaining the first request scenario information according to the region abnormality judgment result; and / or the second request scenario information is obtained according to the operator network to which the domain name system server sending the abnormal request information belongs, including: judging whether the domain name system server is a foreign network server according to the operator network to which the domain name system server belongs, to obtain an access network abnormality judgment result; and obtaining the second request scenario information according to the access network abnormality judgment result.

[0011] In one of the embodiments, the waiting time corresponding to the abnormal request scenario is obtained, including: obtaining an information reception statistical value corresponding to the abnormal request scenario; and obtaining the waiting time corresponding to the abnormal request scenario according to the information reception statistical value.

[0012] In one of the embodiments, the information reception statistical value corresponding to the abnormal request scenario is obtained, including: obtaining a statistical period time corresponding to the abnormal request scenario, an information reception threshold value, and a waiting time coefficient; counting the number of abnormal request information corresponding to the abnormal request scenario received in the current period according to the statistical period time; and obtaining the information reception statistical value according to the product of the proportion of the number of abnormal request information in the information reception threshold value and the waiting time coefficient.

[0013] In a second aspect, the application further provides a request information processing system, including:

[0014] a domain name system server and an authorization server;

[0015] The domain name system server is configured to send abnormal request information of a wireless network voice service to the domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing to return the domain name of the evolved packet gateway; and the domain name query request of the evolved packet gateway is configured to request access to the wireless network voice service.

[0016] The authorization server is configured to receive the abnormal request information of the wireless network voice service.

[0017] The authorization server is further configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information.

[0018] The authorization server is further configured to obtain a waiting time corresponding to the abnormal request scenario.

[0019] The authorization server is further configured to send a timer to the user equipment according to the waiting duration; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting duration.

[0020] In a third aspect, the present application provides a request information processing apparatus, comprising:

[0021] A receiving module is configured to receive abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from user equipment and is unable to return the domain name of the evolved packet gateway; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service.

[0022] A first obtaining module is configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information.

[0023] A second obtaining module is configured to obtain a waiting duration corresponding to the abnormal request scenario.

[0024] A sending module is configured to send a timer to the user equipment according to the waiting duration; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting duration.

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

[0026] Abnormal request information of a wireless network voice service is received; the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from user equipment and is unable to return the domain name of the evolved packet gateway; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service.

[0027] An abnormal request scenario of the wireless network voice service is determined according to the abnormal request information.

[0028] A waiting duration corresponding to the abnormal request scenario is obtained.

[0029] A timer is sent to the user equipment according to the waiting duration; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting duration.

[0030] In a fifth aspect, the present application provides a computer readable storage medium, having stored thereon a computer program, which, when executed by a processor, implements the following steps:

[0031] receiving abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from a user equipment and fails to return a domain name of the evolved packet gateway; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service;

[0032] determining an abnormal request scenario of the wireless network voice service according to the abnormal request information;

[0033] obtaining a waiting time length corresponding to the abnormal request scenario;

[0034] sending a timer to the user equipment according to the waiting time length; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time length.

[0035] In a sixth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0036] receiving abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from a user equipment and fails to return a domain name of the evolved packet gateway; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service;

[0037] determining an abnormal request scenario of the wireless network voice service according to the abnormal request information;

[0038] obtaining a waiting time length corresponding to the abnormal request scenario;

[0039] sending a timer to the user equipment according to the waiting time length; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time length.

[0040] The request information processing method, system, device, computer equipment, computer readable storage medium and computer program product, first receive the abnormal request information of the wireless network voice service, wherein the abnormal request information is sent by the domain name system server when the domain name query request of the evolved packet gateway is received from the user equipment and the domain name of the evolved packet gateway cannot be returned, the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service, then the abnormal request scenario of the wireless network voice service is determined according to the abnormal request information, the waiting time corresponding to the abnormal request scenario is obtained, and the timer is sent to the user equipment according to the waiting time, wherein the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time. The scheme, for the abnormal situation of the user equipment requesting access to the wireless network voice service, determines the specific abnormal request scenario according to the received abnormal request information, and obtains the corresponding waiting time and issues the corresponding timer to the user equipment according to the abnormal request scenario, so that the user equipment can pause sending the domain name query request of the evolved packet gateway within the corresponding waiting time, and the signaling storm that may be generated between the domain name system server and the authorized server of the operator in the abnormal request scenario can be effectively prevented, and the network load is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other related drawings can also be obtained without creative labor.

[0042] Figure 1 The application environment diagram of the request information processing method in one embodiment;

[0043] Figure 2 The flowchart of the request information processing method in one embodiment;

[0044] Figure 3 The flowchart of determining the abnormal request scenario of the wireless network voice service in one embodiment;

[0045] Figure 4 The flowchart of obtaining the information reception statistical value corresponding to the abnormal request scenario in one embodiment;

[0046] Figure 5 The application environment diagram of the request information processing method in another embodiment;

[0047] Figure 6 The flowchart of the request information processing method in another embodiment;

[0048] Figure 7 This is a schematic diagram of the structure of a request information processing system in one embodiment;

[0049] Figure 8 This is a structural block diagram of a request information processing device in one embodiment;

[0050] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

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

[0052] The request information processing method provided in this application embodiment can be applied to, for example, Figure 1 The application environment is illustrated. User equipment can access the wireless network through an access point and communicate with the Domain Name System (DNS) server or authoritative server through a gateway. The DNS server and authoritative server can also communicate via the network. User equipment can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The DNS server and authoritative server can communicate as independent physical servers, as server clusters or distributed systems composed of multiple physical servers, or as cloud servers providing cloud computing services.

[0053] Specifically, user equipment can subscribe to a wireless network voice service (VoWiFi) with an operator network (hereinafter referred to as "First Network"). When a user needs to use the wireless network voice service, the user equipment can access the wireless network through an access point (AP) and send a domain name query request to the evolved packet data gateway (ePDG) of First Network to the Domain Name System (DNS) server in its region through the gateway.

[0054] When the user equipment is located in a region where the wireless network voice service has been deployed, and the access point accessed by the user equipment is the access point of the first network, the domain name query request sent by the user equipment can reach the domain name system server of the first network, which can store the domain name resolution of the evolved packet gateway of the first network, so that the user equipment can connect to the evolved packet gateway of the first network for subsequent use of the wireless network voice service.

[0055] However, when the user equipment is located in a region where the wireless network voice service has not been deployed, and the user equipment accesses the wireless network through the access point of the first network and sends the domain name query request of the evolved packet gateway to the domain name system server, since the domain name system server of the first network in the region does not store the domain name resolution of the evolved packet gateway, the domain name system server will send the request to the authorization server of the first network. When the access point accessed by the user equipment is the access point of the second network different from the operator network to which the user equipment is subscribed (hereinafter referred to as "second network"), the domain name query request sent by the user equipment will reach the domain name system server of the second network, and since the domain name system server of the second network does not have the domain name resolution of the evolved packet gateway of the first network regardless of whether the region where the user equipment is located has deployed the wireless network voice service, the domain name system server will also send the received domain name query request to the authorization server of the first network. Based on this, when multiple users move between multiple access points and initiate the request for the wireless network voice service in the above-mentioned case, a signaling storm between the authorization server and the domain name system server is likely to occur.

[0056] In an exemplary embodiment, as shown in Figure 2 , a request information processing method is provided, which is applied to the authorization server in Figure 1 , and includes the following steps:

[0057] Step S201, receiving abnormal request information of the wireless network voice service.

[0058] Exemplarily, when the user equipment needs to request to access the wireless network voice service, the domain name system server can receive the domain name query request of the evolved packet gateway from the user equipment. When the domain name system server receives the domain name query request but cannot return the corresponding domain name of the evolved packet gateway, the authorization server can send the abnormal request information to the authorization server. The authorization server can receive the abnormal request information from the domain name system server.

[0059] The domain name system server can be the same as the access point to which the user equipment accesses, and the domain name query request can be used to query the domain name of the evolved packet gateway of the operator network to which the user equipment subscribes. The authorization server can be a server of the operator network to which the user equipment subscribes.

[0060] For example, when the region where the user equipment is located is a region where wireless network voice service is not deployed, or when the operator network to which the domain name system server belongs is not the operator network to which the user equipment subscribes, the domain name system server is generally difficult to return the domain name of the evolved packet gateway of the operator network to which the user equipment subscribes, and thus can send abnormal request information to the authorization server of the operator network to which the user equipment subscribes. In some exemplary embodiments, the abnormal request information can include a domain name query request for the evolved packet gateway and a network address of the user equipment.

[0061] In step S202, an abnormal request scenario of the wireless network voice service is determined according to the abnormal request information.

[0062] In some exemplary embodiments, the abnormal request scenario corresponding to the abnormal request information received this time can be determined according to the abnormal request information. For example, different scenarios in which the user equipment receives abnormal request information can be divided into different abnormal request scenarios according to different reasons why the user equipment is difficult to normally access the wireless network voice service.

[0063] For example, a case where the operator network to which the domain name system server belongs is not the operator network to which the user equipment subscribes can correspond to an abnormal request scenario, and a case where the region where the user equipment is located is a region where wireless network voice service is not deployed can correspond to another abnormal request scenario. In some exemplary embodiments, the abnormal request scenario can also be more finely distinguished according to the combination of the operator network to which the domain name system server belongs and the region where the user equipment is located. For example, the authorization server can determine the operator network to which the domain name system server belongs and determine the region where the user equipment is located according to the abnormal request information, so as to determine the specific abnormal request scenario.

[0064] In step S203, a waiting time corresponding to the abnormal request scenario is obtained.

[0065] In some exemplary embodiments, different waiting times can be set for different abnormal request scenarios, or different rules for calculating the waiting time can be set. In this step, the waiting time corresponding to the specific abnormal request scenario can be obtained according to the specific abnormal request scenario.

[0066] In step S204, a timer is sent to the user equipment according to the waiting time.

[0067] The timer is sent to the user equipment according to the waiting time corresponding to the abnormal request scenario of the user equipment accessing the wireless network voice service, so as to instruct the user equipment not to send the connection establishment request of the wireless network voice service, that is, not to send the domain name query request of the evolved packet gateway within the waiting time.

[0068] In the above request information processing method, the abnormal request information of the wireless network voice service is first received, wherein the abnormal request information is sent by the domain name system server when the domain name query request of the evolved packet gateway from the user equipment is received and the domain name of the evolved packet gateway cannot be returned, the domain name query request is used to request access to the wireless network voice service, then the abnormal request scenario of the wireless network voice service is determined according to the abnormal request information, the waiting time corresponding to the abnormal request scenario is obtained, and the timer is sent to the user equipment according to the waiting time, wherein the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time. According to the abnormal request information received by the user equipment requesting access to the wireless network voice service, the specific abnormal request scenario is determined according to the abnormal request information, and the corresponding waiting time is obtained according to the abnormal request scenario and the corresponding timer is sent to the user equipment, so that the user equipment can be suspended to send the domain name query request of the evolved packet gateway within the corresponding waiting time, and the signaling storm between the domain name system server and the authorized server of the operator in the abnormal request scenario can be effectively prevented, and the network load is reduced.

[0069] In an exemplary embodiment, as shown in Figure 3 According to the abnormal request information, the abnormal request scenario of the wireless network voice service can include:

[0070] In step S301, the first request scenario information is obtained according to the network address of the user equipment contained in the abnormal request information.

[0071] According to the network address (Internet Protocol Address, IP address) of the user equipment contained in the abnormal request information, the first request scenario information of the scenario receiving the abnormal request information can be obtained. Exemplarily, the first request scenario information can contain information of the region where the user equipment is located, which can be obtained by parsing the IP address of the user equipment. For example, the first request scenario information can also be information processed according to the information of the region where the user equipment is located, which is used to indicate whether the region has deployed the wireless network voice service.

[0072] In step S302, the second request scenario information is obtained according to the operator network to which the domain name system server sending the abnormal request information belongs.

[0073] In the case that the abnormal request information is received, the domain name system server sending the information can be determined, and the operator network to which the domain name system server belongs can be determined, and then according to the information of the operator network, the second request scene information of the scene in which the abnormal request information is received can be obtained. Exemplarily, the second request scene information can include the information of the operator network to which the domain name system server belongs. For another example, the second request scene information can also be information processed according to the information of the operator network to which the domain name system server belongs, and the information is used to indicate whether the operator network is the operator network to which the authorized server belongs (namely, the operator network to which the user equipment performs the voice service subscription of the wireless network).

[0074] In step S303, the abnormal request scene is determined according to the first request scene information and the second request scene information.

[0075] In the case that the abnormal request information is received, the domain name system server sending the information can be determined, and the operator network to which the domain name system server belongs can be determined, and then according to the information of the operator network, the second request scene information of the scene in which the abnormal request information is received can be obtained. Exemplarily, the second request scene information can include the information of the operator network to which the domain name system server belongs. For another example, the second request scene information can also be information processed according to the information of the operator network to which the domain name system server belongs, and the information is used to indicate whether the operator network is the operator network to which the authorized server belongs (namely, the operator network to which the user equipment performs the voice service subscription of the wireless network).

[0076] Exemplarily, in the embodiment, the corresponding abnormal request scene can be determined according to different combinations of the operator network to which the domain name system server belongs and the region in which the user equipment is located. For example, in the case that the first request scene information indicates that the region in which the user equipment is located is a region in which the wireless network voice service is deployed, and the second request scene information indicates that the operator network to which the domain name system server belongs is a non-subscription operator network, the first abnormal request scene can be corresponded. In the case that the first request scene information indicates that the region in which the user equipment is located is a region in which the wireless network voice service is not deployed, and the second request scene information indicates that the operator network to which the domain name system server belongs is a non-subscription operator network, the second abnormal request scene can be corresponded. In the case that the first request scene information indicates that the region in which the user equipment is located is a region in which the wireless network voice service is not deployed, and the second request scene information indicates that the operator network to which the domain name system server belongs is a subscription operator network, the third abnormal request scene can be corresponded.

[0077] In the embodiment, the first request scene information is obtained according to the network address of the user equipment, the second request scene information is obtained according to the operator network to which the domain name system server belongs, and then the abnormal request scene is determined by combining the two, so that the factors leading to the abnormal request of the wireless network voice service and easy to cause signaling storm can be fully considered, and the abnormal request scene can be finely divided, so that more targeted waiting time can be set for different abnormal request scenes in the subsequent process, and the occurrence of signaling storm in different scenes can be prevented.

[0078] In an example embodiment, obtaining the first request scenario information according to the network address of the user equipment contained in the abnormal request information can include: determining the region information of the user equipment according to the network address; judging whether the region of the user equipment is a deployment region of the wireless network voice service according to the region information, to obtain a region abnormality judgment result; and obtaining the first request scenario information according to the region abnormality judgment result; and / or obtaining the second request scenario information according to the operator network to which the domain name system server sending the abnormal request information belongs can include: judging whether the domain name system server is a cross-network server according to the operator network to which the domain name system server belongs, to obtain an access network abnormality judgment result; and obtaining the second request scenario information according to the access network abnormality judgment result.

[0079] In obtaining the first request scenario information, the network address of the user equipment can be first interpreted to obtain the region information of the user equipment. The region information can be the name of the region of the user equipment or other identifiers capable of indicating the region of the user equipment. Then, whether the region where the user equipment initiates the request for the wireless network voice service is a region where the wireless network voice service is deployed can be judged according to the region information, and a region abnormality judgment result can be further obtained.

[0080] The authorization server can pre-store a list of regions where the wireless network voice service is deployed. When the region information of the user equipment is contained in the list of regions, it can be determined that the region of the user equipment is a region where the wireless network voice service is deployed; otherwise, it can be determined that the region of the user equipment is a region where the wireless network voice service is not deployed. When the region of the user equipment is a region where the wireless network voice service is deployed, the region abnormality judgment result can be non-region abnormality; and when the region of the user equipment is a region where the wireless network voice service is not deployed, the region abnormality judgment result can be region abnormality.

[0081] In obtaining the second request scenario information, whether the operator network to which the domain name system server belongs is the operator network to which the authorization server belongs (i.e. the operator network where the user equipment subscribes to the wireless network voice service) can be judged according to the operator network to which the domain name system server belongs, and an access network abnormality judgment result can be further obtained. When the operator network is different from the operator network to which the authorization server belongs, it can be determined that the domain name system server is a cross-network server, and the corresponding access network abnormality judgment result can be access network abnormality; and when the operator network is the same as the operator network to which the authorization server belongs, it can be determined that the domain name system server is not a cross-network server, and the corresponding access network abnormality judgment result can be non-access network abnormality.

[0082] In this embodiment, the area abnormality judgment result is obtained by judging whether the area is an area where the wireless network voice service has been deployed, and the first request scene information is further obtained, and the network abnormality judgment result is obtained by judging whether the domain name system server is a server in a different network, and the second request scene information is further obtained, so that the first request scene information and the second request scene information can more directly reflect the factors causing the abnormal request for the wireless network voice service, and the efficiency of subsequently determining the specific abnormal request scene is effectively improved.

[0083] In an exemplary embodiment, obtaining the waiting time length corresponding to the abnormal request scene can include: obtaining an information reception statistical value corresponding to the abnormal request scene; and obtaining the waiting time length corresponding to the abnormal request scene according to the information reception statistical value.

[0084] The waiting time length corresponding to each abnormal request scene can be a time length dynamically adjusted according to the information reception statistical value corresponding to each abnormal request scene. Exemplarily, the information reception statistical value corresponding to the abnormal request scene can be a value obtained by counting the number of abnormal request information corresponding to the same abnormal request scene received by the authorization server, and the greater the value, the more abnormal request information corresponding to the abnormal request scene is received by the authorization server. Based on this, the corresponding waiting time length can be set according to the value of the information reception statistical value corresponding to each abnormal request scene, for example, the greater the value of the information reception statistical value, the longer the waiting time length can be.

[0085] In this embodiment, the information reception statistical value corresponding to the abnormal request scene is obtained, and the waiting time length of the scene is obtained according to the information reception statistical value, so that the time length of the timer corresponding to the scene can be dynamically adjusted according to the number of users who want to access the wireless network voice service in the same abnormal request scene, thereby improving user experience without avoiding signaling storm.

[0086] In an exemplary embodiment, as shown in Figure 4 obtaining the information reception statistical value corresponding to the abnormal request scene can include:

[0087] In step S401, the statistical period time length, the information reception threshold value, and the waiting time length coefficient corresponding to the abnormal request scene are obtained.

[0088] In this embodiment, the information reception statistical value of the abnormal request scene can be obtained according to the statistical period time length, the information reception threshold value, and the waiting time length coefficient. Exemplarily, the statistical period time length, the information reception threshold value, and the waiting time length coefficient corresponding to different abnormal request scenes can be set in advance, and the statistical period time length, the information reception threshold value, and the waiting time length coefficient corresponding to a specific abnormal request scene can be obtained in this step.

[0089] In step S402, the number of abnormal request information corresponding to the abnormal request scenario received in the current period is counted according to the counting period length.

[0090] The counting period length can be used to set the length of time for counting the number of received abnormal request information. According to the counting period length, the time period for counting the number of abnormal request information can be divided, and the number of abnormal request information in the current period is counted.

[0091] In some embodiments, the time period for counting the number of abnormal request information can be divided into a plurality of continuous counting periods according to the counting period length. For example, if the counting length is q hours, a day is divided into 24 / q counting periods. Assuming that the authorization server receives abnormal request information at time t, the counting period in which time t is located is taken as the current period, and the number of abnormal request information corresponding to the same abnormal request scenario received from the beginning of the period to time t is counted.

[0092] In other embodiments, the current period can be determined according to the receiving time of the abnormal request information and the counting period length. For example, if the authorization server receives abnormal request information at time t, and the counting length is q, the period from time t-q to time t is taken as the current period, and the number of abnormal request information corresponding to the same abnormal request scenario received in the period is counted.

[0093] In step S403, the information reception statistical value is obtained according to the product of the proportion of the number of abnormal request information in the information reception threshold and the waiting time length coefficient.

[0094] In this step, the information reception statistical value of the abnormal request scenario corresponding to the received abnormal request information can be calculated according to the number of abnormal request information in the current period, the information reception threshold and the waiting time length coefficient. For example, assuming that the number of abnormal request information in the current period is n, the information reception threshold is m, and the waiting time length coefficient is A, the information reception statistical value can be represented as: (n / m) x A. Optionally, after calculating the information reception statistical value, it can be taken as the waiting time length corresponding to the corresponding abnormal request scenario.

[0095] In this embodiment, by setting the corresponding statistical period length, information receiving threshold and waiting time length coefficient for different abnormal request scenarios, and according to the statistical period length, the number of abnormal request information corresponding to the same abnormal request scenario received in the current period is counted, and then according to the product of the proportion of the number of abnormal request information in the information receiving threshold and the waiting time length coefficient, the information receiving statistical value of the scenario is calculated. The information receiving statistical value of each different abnormal request scenario can be counted according to different strategies, so that a more suitable waiting time length of the timer can be set for each abnormal request scenario.

[0096] In order to further illustrate the request information processing method of the present application, the following will be described in detail by embodiments:

[0097] First, please refer to Figure 5 , which is a schematic diagram of the application scenario of the request information processing method in this embodiment. Among them, the user equipment can perform a Voice over Wi-Fi (VoWiFi) subscription with the first operator network (hereinafter referred to as the "first network") for wireless network voice service. The first network authorization server, the first network domain name system server, the first network gateway, and the access point 2 can be servers or network devices belonging to the first network. The second network domain name system server, the second network gateway, the access point 1, and the access point 3 can be servers or network devices belonging to an operator network (hereinafter referred to as "second network") to which the user equipment does not perform a wireless network voice service subscription.

[0098] As shown in Figure 5 , when the user equipment requests to access the wireless network voice service through the access point 1 of the second network in the area where the wireless network voice service has been deployed (case 1), or when the user equipment requests to access the wireless network voice service through the access point 2 of the first network in the area where the wireless network voice service has not been deployed (case 2), or when the user equipment requests to access the wireless network voice service through the access point 3 of the second network in the area where the wireless network voice service has not been deployed (case 3), the first network authorization server can receive abnormal request information from the first network domain name system server or the second network domain name system server. The first network authorization server can process the received abnormal request information by executing the request information processing method in this embodiment, and send a corresponding timer to the user equipment through the first network gateway or the second network gateway.

[0099] Specifically, please refer to Figure 6 , which is a flowchart of the request information processing method in this embodiment.

[0100] When the user equipment requests to access the wireless network voice service in the above case 1, case 2 or case 3, the corresponding first network domain name system server or the second network domain name system server can receive the domain name query request of the evolved packet data gateway (ePDG) of the first network from the user equipment, and since there is no domain name resolution of the evolved packet data gateway in the first network domain name system server or the second network domain name system server, the first network authorization server can send the abnormal request information containing the domain name query request of the evolved packet data gateway from the user equipment and the network address (Internet Protocol Address, IP address) of the user equipment to the first network authorization server.

[0101] The first network authorization server can parse the abnormal request information by using a query request and address resolution function module, obtain the first request scene information according to the network address of the user equipment contained in the abnormal request information, and obtain the second request scene information according to the operator network to which the domain name system server sending the abnormal request information belongs. For example, the query request and address resolution function module can determine the region information of the user equipment according to the network address, determine whether the region of the user equipment is a deployment region of the wireless network voice service according to the region information, and obtain a region abnormality judgment result, and then obtain the first request scene information according to the region abnormality judgment result. At the same time, the query request and address resolution function module can also determine whether the domain name system server sending the abnormal request information is a cross-network server according to the operator network to which the domain name system server belongs, obtain an access network abnormality judgment result, and then obtain the second request scene information according to the access network abnormality judgment result.

[0102] According to the first request scene information and the second request scene information obtained by the query request and address resolution function module, the first network authorization server can determine the abnormal request scene of the wireless network voice service corresponding to the abnormal request information received this time.

[0103] For example, as shown in Figure 5 When the first request scene information is non-region abnormality (i.e., the region of the user equipment is a region where the wireless network voice service is deployed), and the second request scene information is access network abnormality (i.e., the operator network to which the domain name system server belongs is not the first network), it can be determined that the abnormal request scene is case 1 in Figure 5 When the first request scene information is region abnormality (i.e., the region of the user equipment is a region where the wireless network voice service is not deployed), and the second request scene information is non-access network abnormality (i.e., the operator network to which the domain name system server belongs is the first network), it can be determined that the abnormal request scene is case 3 in Figure 5Case 2 in the table; when the first request scenario information is a non-region exception (i.e. the region where the user equipment is located is a region where the wireless network voice service is not deployed), and the second request scenario information is an access network exception (i.e. the operator network to which the domain name system server belongs is not the first network), it can be determined that the abnormal request scenario is Figure 5 Case 3 in the table.

[0104] When determining a specific abnormal request scenario, the authorization server can obtain the statistical period length, the information receiving threshold, and the waiting time length coefficient corresponding to the scenario, then according to the statistical period length, the number of abnormal request information corresponding to the abnormal request scenario received in the current period is counted, and then according to the product of the proportion of the number of abnormal request information in the information receiving threshold and the waiting time length coefficient, the information receiving statistical value is obtained, and finally according to the information receiving statistical value, the waiting time length corresponding to the abnormal request scenario is obtained, and the corresponding timer is sent to the user equipment.

[0105] Exemplarily, when the abnormal request scenario is Case 1, the authorization server can obtain the statistical period length q1, the information receiving threshold m1, and the waiting time length coefficient A1 corresponding to the scenario, then according to the statistical period length q1, the number of abnormal request information n1 corresponding to the abnormal request scenario received in the current period is counted, and the information receiving statistical value (n1 / m1)×A1 is calculated. Similarly, when the abnormal request scenario is Case 2, the authorization server can obtain the statistical period length q2, the information receiving threshold m2, and the waiting time length coefficient A2 corresponding to the scenario, and count the number of abnormal request information n2, and then calculate the information receiving statistical value (n2 / m2)×A2. When the abnormal request scenario is Case 3, the authorization server can obtain the statistical period length q3, the information receiving threshold m3, and the waiting time length coefficient A3 corresponding to the scenario, and count the number of abnormal request information n3, and then calculate the information receiving statistical value (n3 / m3)×A3. Then, the calculated information receiving statistical value can be used as the waiting time length, and a timer is sent to the user equipment. The timer can instruct the user equipment not to send a connection establishment request for the wireless network voice service within the waiting time length, that is, not to send a domain name query request for the evolved packet gateway.

[0106] Optionally, considering that the user equipment located in the region where the wireless network voice service is deployed may access the wireless network through the access point of the first network and initiate a request to access the wireless network voice service in a short time, the waiting time length coefficients of each abnormal request scenario can be set as A3>A2>A1.

[0107] In the embodiment, the abnormal request information is analyzed to determine whether the region where the user equipment is located is a deployment region of the wireless network voice service and whether the wireless network accessed by the user equipment is a network of an operator that provides the wireless network voice service to which the user equipment is subscribed, and the abnormal request scenarios that are likely to cause a signaling storm are divided into three cases according to the determination result, different timer strategies are given to the three cases, and the waiting time of the timer is dynamically adjusted according to the number of user equipments to be accessed in the current period. The scheme can effectively prevent a signaling storm between the authorization server of the operator network that provides the VoWIFI service and the inter-network / DNS server in the scenario where multiple roaming VoWIFI user equipments move between multiple access points and attempt to make a wireless network voice call, and effectively avoid the risk that the authorization server is paralyzed due to a signaling storm in the case where a large number of VoWIFI users are added.

[0108] It should be understood that, although each step in the flowchart involved in each of the above embodiments is shown in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each of the above embodiments can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least part of other steps or steps or stages in other steps.

[0109] Based on the same inventive concept, the embodiments of the present application also provide a request information processing system for implementing the above-mentioned request information processing method. The implementation scheme for solving the problem provided by the system is similar to the implementation scheme described in the above method, so the specific limitations in one or more request information processing system embodiments provided below can refer to the limitations of the request information processing method in the above text, which will not be repeated here.

[0110] In one exemplary embodiment, as shown in Figure 7 A request information processing system is provided, including a domain name system server, an authorization server;

[0111] The domain name system server is configured to send abnormal request information of a wireless network voice service to the domain name system server when a domain name query request from an evolved packet gateway of user equipment is received and the domain name of the evolved packet gateway cannot be returned; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service;

[0112] The authorization server is configured to receive the abnormal request information of the wireless network voice service.

[0113] The authorization server is further configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information.

[0114] The authorization server is further configured to obtain a waiting duration corresponding to the abnormal request scenario.

[0115] The authorization server is further configured to send a timer to the user equipment according to the waiting duration, where the timer is configured to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting duration.

[0116] In an exemplary embodiment, the authorization server is further configured to obtain first request scenario information according to a network address of the user equipment included in the abnormal request information, obtain second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs, and determine the abnormal request scenario according to the first request scenario information and the second request scenario information.

[0117] In an exemplary embodiment, the authorization server is further configured to determine region information of the user equipment according to the network address, determine whether a region where the user equipment is located is a deployment region of the wireless network voice service according to the region information, obtain a region abnormality judgment result, obtain the first request scenario information according to the region abnormality judgment result, and / or determine whether the domain name system server is a cross-network server according to the operator network to which the domain name system server belongs, obtain an access network abnormality judgment result, and obtain the second request scenario information according to the access network abnormality judgment result.

[0118] In an exemplary embodiment, the authorization server is further configured to obtain an information reception statistical value corresponding to the abnormal request scenario, and obtain the waiting duration corresponding to the abnormal request scenario according to the information reception statistical value.

[0119] In an exemplary embodiment, the authorization server is further configured to obtain a statistical period duration, an information reception threshold value, and a waiting duration coefficient corresponding to the abnormal request scenario, count a number of abnormal request information corresponding to the abnormal request scenario received in a current period according to the statistical period duration, and obtain the information reception statistical value according to a product of a proportion of the number of abnormal request information in the information reception threshold value and the waiting duration coefficient.

[0120] Based on the same inventive concept, the embodiments of the present application further provide a request information processing apparatus for implementing the request information processing method described above. The apparatus provides a solution to the problem similar to the implementation scheme described in the above method, so the specific limitations in one or more request information processing apparatus embodiments provided below can refer to the limitations of the request information processing method described above, which will not be repeated here.

[0121] In one exemplary embodiment, as shown in Figure 8 A request information processing apparatus 800 is provided, comprising:

[0122] A receiving module 801 is configured to receive abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request from a user equipment and fails to return a domain name of an evolved packet gateway; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service;

[0123] A first obtaining module 802 is configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information;

[0124] A second obtaining module 803 is configured to obtain a waiting time length corresponding to the abnormal request scenario;

[0125] A sending module 804 is configured to send a timer to the user equipment according to the waiting time length; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time length.

[0126] In one exemplary embodiment, the first obtaining module 802 is further configured to: obtain first request scenario information according to a network address of the user equipment contained in the abnormal request information; obtain second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs; and determine the abnormal request scenario according to the first request scenario information and the second request scenario information.

[0127] In one exemplary embodiment, the first obtaining module 802 is further configured to: determine region information of the user equipment according to the network address; judge whether a region where the user equipment is located is a deployment region of the wireless network voice service according to the region information, to obtain a region abnormality judgment result; obtain the first request scenario information according to the region abnormality judgment result; and / or judge whether the domain name system server is a foreign network server according to the operator network to which the domain name system server belongs, to obtain an access network abnormality judgment result; and obtain the second request scenario information according to the access network abnormality judgment result.

[0128] In an exemplary embodiment, the second acquisition module 803 is further configured to: acquire the information reception statistics corresponding to the abnormal request scenario; and obtain the waiting time corresponding to the abnormal request scenario based on the information reception statistics.

[0129] In an exemplary embodiment, the second acquisition module 803 is further configured to: acquire the statistical period duration, information receiving threshold, and waiting time coefficient corresponding to the abnormal request scenario; based on the statistical period duration, count the number of abnormal request messages corresponding to the abnormal request scenario received in the current period; and obtain the information receiving statistics value based on the product of the proportion of the number of abnormal request messages in the information receiving threshold and the waiting time coefficient.

[0130] Each module in the aforementioned request information processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0131] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores data such as abnormal request information, information related to abnormal request scenarios, and the waiting time corresponding to the abnormal request scenarios. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a request information processing method.

[0132] Those skilled in the art will understand that Figure 9The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0133] In one embodiment, a computer device is also provided, including a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method embodiments when executing the computer program.

[0134] In one embodiment, a computer readable storage medium is provided, storing a computer program, and the computer program implements the steps in the above method embodiments when executed by a processor.

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

[0136] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0137] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing relevant hardware. The computer program can be stored in a non-volatile computer readable storage medium. When the computer program is executed, the processes of the above-mentioned embodiment methods can be included. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0138] The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combinations of the technical features do not exist contradictory, it should be considered as the scope of the present application.

[0139] The above embodiments only express several implementation ways of the present application, and the description is specific and detailed, but it should not be understood as a limitation to the patent scope of the present application. It should be pointed out that for ordinary skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A request information processing method characterized by comprising: The method comprises: receiving abnormal request information of a wireless network voice service; the abnormal request information is sent by a domain name system server when a domain name query request of an evolved packet gateway from a user equipment is received and a domain name of the evolved packet gateway cannot be returned; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service; obtaining first request scenario information according to a network address of the user equipment contained in the abnormal request information; obtaining second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs; determining an abnormal request scenario of the wireless network voice service according to the first request scenario information and the second request scenario information; obtaining a waiting time length corresponding to the abnormal request scenario; sending a timer to the user equipment according to the waiting time length; the timer is used to instruct the user equipment not to send the domain name query request of the evolved packet gateway within the waiting time length.

2. The method of claim 1, wherein: the obtaining of the first request scenario information according to the network address of the user equipment contained in the abnormal request information comprises: determining region information of the user equipment according to the network address; judging whether a region where the user equipment is located is a deployment region of the wireless network voice service according to the region information, to obtain a region abnormality judgment result; obtaining the first request scenario information according to the region abnormality judgment result; and / or the obtaining of the second request scenario information according to the operator network to which the domain name system server sending the abnormal request information belongs comprises: judging whether the domain name system server is a server in a different network according to the operator network to which the domain name system server belongs, to obtain an access network abnormality judgment result; obtaining the second request scenario information according to the access network abnormality judgment result. the obtaining of the waiting time length corresponding to the abnormal request scenario comprises:

3. The method of claim 1, wherein, obtaining an information reception statistical value corresponding to the abnormal request scenario; obtaining the waiting time length corresponding to the abnormal request scenario according to the information reception statistical value. the obtaining of the information reception statistical value corresponding to the abnormal request scenario comprises:

4. The method of claim 3, wherein, obtaining a statistical period time length, an information reception threshold value, and a waiting time length coefficient corresponding to the abnormal request scenario; statistically counting a number of abnormal request information corresponding to the abnormal request scenario received in a current period according to the statistical period time length; obtaining the information reception statistical value according to a product of a proportion of the number of abnormal request information in the information reception threshold value and the waiting time length coefficient. The system comprises a domain name system server and an authorization server.

5. A request information processing system characterized by comprising: The domain name system server is configured to send abnormal request information of a wireless network voice service to the domain name system server when a domain name query request of an evolved packet gateway from a user equipment is received and a domain name of the evolved packet gateway cannot be returned; the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service. ​ The authorization server is configured to receive the abnormal request information of the wireless network voice service; The authorization server is further configured to obtain first request scenario information according to a network address of the user equipment contained in the abnormal request information, obtain second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs, and determine an abnormal request scenario of the wireless network voice service according to the first request scenario information and the second request scenario information. The authorization server is further configured to obtain a waiting time length corresponding to the abnormal request scenario. The authorization server is further configured to send a timer to the user equipment according to the waiting time length, and the timer is configured to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting time length.

6. An information processing apparatus that requests, characterized by comprising: The apparatus comprises: A receiving module configured to receive abnormal request information of a wireless network voice service, wherein the abnormal request information is sent by a domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from user equipment and is unable to return a domain name of the evolved packet gateway, and the domain name query request of the evolved packet gateway is configured to request access to the wireless network voice service; A first obtaining module configured to obtain first request scenario information according to a network address of the user equipment contained in the abnormal request information, obtain second request scenario information according to an operator network to which the domain name system server sending the abnormal request information belongs, and determine an abnormal request scenario of the wireless network voice service according to the first request scenario information and the second request scenario information. A second obtaining module configured to obtain a waiting time length corresponding to the abnormal request scenario. A sending module configured to send a timer to the user equipment according to the waiting time length, and the timer is configured to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting time length. 7.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-6 when the computer program is executed by the processor. The processor implements the steps of the method of any one of claims 1 to 4 when executing the computer program.

8. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 4.

9. A computer program product comprising a computer program, characterized in that, The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 4. The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 4.

Images