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

Abstract

The invention 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 exception request information is sent by the domain name system server when the domain name system server receives a domain name query request of an evolved packet gateway from the user equipment and cannot return to the domain name of the evolved packet gateway; the domain name query request of the evolved packet gateway is used for requesting to access a wireless network voice service; determining an abnormal request scene of the wireless network voice service according to the abnormal request information; acquiring waiting duration corresponding to the abnormal request scene; sending a timer to the user equipment according to the waiting duration; the timer is used for indicating that the user equipment does not send the domain name query request of the evolved packet gateway within the waiting duration. By adopting the method, the occurrence of signaling storm can be avoided, and the network load is reduced.

Description

Technical Field

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

[0002] With the development of communication technology, the technology of providing voice services through wireless networks has emerged. Wireless network voice technology enables communication devices to make calls without mobile signals, which can complement the voice services based on mobile data and effectively make up for the lack of cellular coverage. However, in the application of wireless network voice service technology, when the communication device's request for wireless network voice service is abnormal, it is easy to form a signaling storm and increase the network load. Summary of the invention

[0003] Based on this, it is necessary to provide a request information processing method, system, apparatus, computer device, computer-readable storage medium and computer program product to address the above technical issues.

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

[0005] Receive abnormal request information for a wireless network voice service; the abnormal request information is sent by a domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing 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;

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

[0007] Obtain the waiting time corresponding to the abnormal request scenario;

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

[0009] In one of the embodiments, determining the abnormal request scenario of the wireless network voice service based on the abnormal request information includes: obtaining first request scenario information based on the network address of the user equipment contained in the abnormal request information; obtaining second request scenario information based on the operator network to which the domain name system server that sends the abnormal request information belongs; and determining the abnormal request scenario based on the first request scenario information and the second request scenario information.

[0010] In one of the embodiments, obtaining the first request scenario information according to the network address of the user device included in the abnormal request information includes: determining the region information of the user device according to the network address; judging whether the region of the user device is a deployment region of the wireless network voice service according to the region information, and obtaining a region abnormality judgment result; 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 includes: judging whether the domain name system server is a server on a different network according to the operator network to which the domain name system server belongs, and obtaining an access network abnormality judgment result; obtaining the second request scenario information according to the access network abnormality judgment result.

[0011] In one of the embodiments, obtaining the waiting time corresponding to the abnormal request scenario includes: obtaining information reception statistics corresponding to the abnormal request scenario; and obtaining the waiting time corresponding to the abnormal request scenario according to the information reception statistics.

[0012] In one of the embodiments, obtaining the information reception statistics corresponding to the abnormal request scenario includes: obtaining the statistical cycle duration, information reception threshold, and waiting time coefficient corresponding to the abnormal request scenario; according to the statistical cycle duration, counting the number of abnormal request information corresponding to the abnormal request scenario received in the current cycle; and obtaining the information reception statistics according to the product of the proportion of the number of abnormal request information in the information reception threshold and the waiting time coefficient.

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

[0014] Domain Name System Server, Authoritative Server;

[0015] The domain name system server is used to send abnormal request information of the wireless network voice service to the domain name system server when receiving the domain name query request of the evolved packet gateway from the user equipment and failing 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;

[0016] The authorization server is used 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 used to obtain the waiting time corresponding to the abnormal request scenario;

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

[0020] In a third aspect, the present application further provides a request information processing device, including:

[0021] A receiving module, 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 receiving a domain name query request of an evolved packet gateway from a user equipment and failing 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;

[0022] A first acquisition module, configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information;

[0023] A second acquisition module is used to obtain the waiting time corresponding to the abnormal request scenario;

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

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

[0026] Receive abnormal request information for a wireless network voice service; the abnormal request information is sent by a domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing 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;

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

[0028] Obtain the waiting time corresponding to the abnormal request scenario;

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

[0030] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0031] Receive abnormal request information for a wireless network voice service; the abnormal request information is sent by a domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing 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] Obtain the waiting time corresponding to the abnormal request scenario;

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

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

[0036] Receive abnormal request information for a wireless network voice service; the abnormal request information is sent by a domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing 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] Obtain the waiting time corresponding to the abnormal request scenario;

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

[0040] The above-mentioned request information processing method, system, device, computer equipment, computer-readable storage medium and computer program product first receive abnormal request information of wireless network voice service, wherein the abnormal request information is sent by the domain name system server when receiving the domain name query request of the evolved packet gateway from the user equipment and failing 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, and then determine the abnormal request scenario of the wireless network voice service according to the abnormal request information, and then obtain the waiting time corresponding to the abnormal request scenario, and send a timer 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. This 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, obtains the corresponding waiting time according to the abnormal request scenario and sends the corresponding timer to the user equipment, so that the user equipment can suspend sending the domain name query request of the evolved packet gateway within the corresponding waiting time, which can effectively prevent the signaling storm that may be generated between the domain name system server and the operator's authorization server in the abnormal request scenario, and reduce the network load. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0042] Figure 1 A diagram of an application environment of a request information processing method in an embodiment;

[0043] Figure 2 A flowchart of a method for processing request information in one embodiment;

[0044] Figure 3 A schematic diagram of a process for determining an abnormal request scenario for a wireless network voice service in an embodiment;

[0045] Figure 4 A schematic diagram of a process for obtaining information reception statistics corresponding to an abnormal request scenario in an embodiment;

[0046] Figure 5 A diagram of an application environment of a request information processing method in another embodiment;

[0047] Figure 6 A flowchart of a method for processing request information in another embodiment;

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

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

[0050] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0052] The request information processing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the user device can access the wireless network through the access point and communicate with the domain name system server or the authorization server through the gateway. The domain name system server and the authorization server can also communicate through the network. The user device can be, but not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The domain name system server and the authorization server can communicate with each other through independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide cloud computing services.

[0053] Specifically, the user equipment can sign a contract for a wireless network voice service (Voice over Wi-Fi, VoWiFi) with the operator network (hereinafter referred to as the "first network"). When the user needs to use the wireless network voice service, the user equipment can access the wireless network through an access point (Access Point, AP), and send a domain name query request for the first network's evolved packet gateway (evoluted Packet Data Gateway, ePDG) to the domain name system (Domain Name System, DNS) server in its area through a gateway.

[0054] Among them, when the area where the user equipment is located is an area where wireless network voice services have been deployed, and the access point accessed by the user equipment is an access point of the first network, the domain name query request it sends can reach the domain name system server of the first network, and the domain name system server can store the domain name resolution of the evolved packet gateway of the first network, so that the user equipment can be connected to the evolved packet gateway of the first network for subsequent use of the wireless network voice service.

[0055] However, when the area where the user equipment is located is an area where wireless network voice service is not deployed, and the user equipment accesses the wireless network through the access point of the first network and sends a domain name query request for the evolved packet gateway to the domain name system server, since the domain name system server of the first network in the area 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 an access point of another operator network (hereinafter referred to as the "second network") different from the operator network it has signed a contract with, the domain name query request it sends will reach the domain name system server of the second network. 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 area where the user equipment is located has deployed 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 requests for wireless network voice service in the above situation, it is easy to form a signaling storm between the authorization server and the domain name system server.

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

[0057] Step S201: receiving abnormal request information of a wireless network voice service.

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

[0059] Among them, the domain name system server can belong to the same region and operator network as the access point accessed by the user equipment, the domain name query request can be used to query the domain name of the evolved packet gateway of the operator network contracted with the user equipment, and the authorization server can be the server of the operator network contracted by the user equipment.

[0060] Exemplarily, when the area where the user equipment is located is an area where wireless network voice services are 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 has subscribed, the domain name system server usually has difficulty returning the domain name of the evolved packet gateway of the operator network to which the user equipment has subscribed, and thus can send abnormal request information to the authorization server of the operator network to which the user equipment has subscribed. In some exemplary embodiments, the abnormal request information can include a domain name query request for the evolved packet gateway and the network address of the user equipment.

[0061] Step S202: determining an abnormal request scenario of the wireless network voice service according to the abnormal request information.

[0062] According to the abnormal request information, the abnormal request scenario corresponding to the abnormal request information received this time can be determined. Exemplarily, according to different reasons that make it difficult for the user equipment to normally access the wireless network voice service, the scenario of receiving the abnormal request information can be divided into different abnormal request scenarios.

[0063] For example, the situation that the operator network to which the domain name system server belongs is not the operator network contracted by the user device can correspond to one abnormal request scenario, and the situation that the wireless network voice service is not deployed in the area where the user device is located can correspond to another abnormal request scenario. In some exemplary implementations, the abnormal request scenarios can be more finely distinguished according to the combination of the operator network to which the domain name system server belongs and the area where the user device is located. Exemplarily, the authorization server can determine the operator network to which the domain name system server belongs and the area where the user device is located based on the abnormal request information, so as to determine the specific abnormal request scenario.

[0064] Step S203, obtaining the waiting time corresponding to the abnormal request scenario.

[0065] For different abnormal request scenarios, different waiting time periods may be preset, or different rules for calculating the waiting time periods may be set. In this step, the corresponding waiting time period may be obtained according to the specific abnormal request scenario.

[0066] Step S204: Send a timer to the user equipment according to the waiting time.

[0067] Among them, according to the waiting time corresponding to the abnormal request scenario in which the user equipment requesting to access the wireless network voice service is located, a timer can be sent to the user equipment to instruct it not to send a connection establishment request for the wireless network voice service within the waiting time, that is, not to send a domain name query request to the evolved packet gateway.

[0068] In the above request information processing method, firstly, the abnormal request information of the wireless network voice service is received, wherein the abnormal request information is sent by the domain name system server when receiving the domain name query request of the evolved packet gateway from the user equipment and failing to return the domain name of the evolved packet gateway, wherein the domain name query request of the evolved packet gateway is used to request access to the wireless network voice service, and then according to the abnormal request information, the abnormal request scenario of the wireless network voice service is determined, and then the waiting time corresponding to the abnormal request scenario is obtained, and according to the waiting time, a timer is sent to the user equipment, 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. In this scheme, for the abnormal situation of the user equipment requesting access to the wireless network voice service, the specific abnormal request scenario is determined according to the received 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 suspend sending the domain name query request of the evolved packet gateway within the corresponding waiting time, which can effectively prevent the signaling storm that may be generated between the domain name system server and the operator's authorization server in the abnormal request scenario, and reduce the network load.

[0069] In an exemplary embodiment, Figure 3 As shown, determining the abnormal request scenario of the wireless network voice service according to the abnormal request information may include:

[0070] Step S301: obtaining first request scenario information according to the network address of the user equipment included in the abnormal request information.

[0071] Among them, according to the network address (Internet Protocol Address, IP address) of the user device contained in the abnormal request information, the first request scenario information of the scenario where the abnormal request information is received can be obtained. Exemplarily, the first request scenario information can include information about the area where the user device is located, and the information can be obtained by parsing the IP address of the user device. For another example, the first request scenario information can also be information obtained by processing the information about the area where the user device is located to indicate whether a wireless network voice service is deployed in the area.

[0072] Step S302: obtaining second request scenario information according to the operator network to which the domain name system server that sends the abnormal request information belongs.

[0073] Among them, when receiving the abnormal request information, the domain name system server that sent the information can be determined, and the operator network to which the domain name system server belongs can be determined, and then based on the information of the operator network, the second request scenario information of the scenario in which the abnormal request information is received can be obtained. Exemplarily, the second request scenario information can include information about the operator network to which the domain name system server belongs. For another example, the second request scenario information can also be information obtained by processing the information of the operator network to which the domain name system server belongs, and used to indicate whether the operator network is the operator network to which the authorization server belongs (that is, the operator network to which the user device signs a wireless network voice service contract).

[0074] Step S303: Determine an abnormal request scenario according to the first request scenario information and the second request scenario information.

[0075] Among them, based on the first request scenario information and the second request scenario information, it can be determined whether wireless network voice services are deployed in the area where the user device is located, and whether the operator network to which the domain name system server belongs is the operator network for which the user device has signed a contract for wireless network voice services, thereby determining the specific abnormal request scenario in which the abnormal request information is received this time.

[0076] Exemplarily, in this embodiment, the corresponding abnormal request scenario can be determined according to different combinations of the operator network to which the domain name system server belongs and the region where the user equipment is located. For example, the first request scenario information indicates that the region where the user equipment is located is a region where wireless network voice services are deployed, and the second request scenario information indicates that the operator network to which the domain name system server belongs is a non-contracted operator network, which can correspond to the first abnormal request scenario; the first request scenario information indicates that the region where the user equipment is located is a region where wireless network voice services are not deployed, and the second request scenario information indicates that the operator network to which the domain name system server belongs is a non-contracted operator network, which can correspond to the second abnormal request scenario; the first request scenario information indicates that the region where the user equipment is located is a region where wireless network voice services are not deployed, and the second request scenario information indicates that the operator network to which the domain name system server belongs is a contracted operator network, which can correspond to the third abnormal request scenario.

[0077] In this embodiment, by obtaining the first request scenario information according to the network address of the user equipment and obtaining the second request scenario information according to the operator network to which the domain name system server belongs, and then combining the two to determine the abnormal request scenario, the factors that easily cause abnormal requests for wireless network voice services and are prone to signaling storms can be fully considered, and the abnormal request scenarios can be finely divided, so that more targeted waiting times can be set for different abnormal request scenarios in the future to prevent the occurrence of possible signaling storms in different scenarios.

[0078] In an exemplary embodiment, obtaining the first request scenario information based on the network address of the user device contained in the abnormal request information may include: determining the region information of the user device based on the network address; judging whether the region of the user device is a deployment region of the wireless network voice service based on the region information, and obtaining a region abnormality judgment result; obtaining the first request scenario information based on the region abnormality judgment result; and / or obtaining the second request scenario information based on the operator network to which the domain name system server sending the abnormal request information belongs, may include: judging whether the domain name system server is a server on a different network based on the operator network to which the domain name system server belongs, and obtaining an access network abnormality judgment result; obtaining the second request scenario information based on the access network abnormality judgment result.

[0079] Among them, when obtaining the first request scenario information, the network address of the user device can be first interpreted to obtain the location information of the user device. Exemplarily, the location information can be the name of the location of the user device or other identifiers that can indicate the location of the user device. Then, based on the location information, it can be determined whether the area where the user device is located when initiating the wireless network voice service request is an area where the wireless network voice service is deployed, and further obtain the regional abnormality judgment result.

[0080] Exemplarily, the authorization server may pre-store a list of regions where wireless network voice services are deployed, and by comparing the region information of the user device with the regions in the region list, when the region list contains the region information of the user device, it can be determined that the region where the user device is located is a region where wireless network voice services are deployed; otherwise, it can be determined that the region where the user device is located is a region where wireless network voice services are not deployed. Exemplarily, when the region where the user device is located is a region where wireless network voice services are deployed, the region anomaly judgment result may be a non-regional anomaly; and when the region where the user device is located is a region where wireless network voice services are not deployed, the region anomaly judgment result may be a region anomaly.

[0081] Among them, when obtaining the second request scenario information, it is possible to determine whether the operator network to which the domain name system server belongs is the operator network to which the authorization server belongs (that is, the operator network to which the user device signs a wireless network voice service contract), and further obtain the access network abnormality judgment result. Exemplarily, 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 server on a different network, and its corresponding access network abnormality judgment result can be an 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 server on a different network, and its corresponding access network abnormality judgment result can be a non-access network abnormality.

[0082] In this embodiment, by determining whether the area has deployed wireless network voice services, a regional anomaly determination result is obtained and then the first request scenario information is obtained. By determining whether the domain name system server is a server on a different network, a network anomaly determination result is obtained and then the second request scenario information is obtained. This enables the first request scenario information and the second request scenario information to more intuitively reflect the factors that lead to abnormal requests for wireless network voice services, and effectively improves the efficiency of subsequent determination of specific abnormal request scenarios.

[0083] In an exemplary embodiment, obtaining the waiting time corresponding to the abnormal request scenario may include: obtaining information reception statistics corresponding to the abnormal request scenario; and obtaining the waiting time corresponding to the abnormal request scenario according to the information reception statistics.

[0084] Among them, the waiting time corresponding to each abnormal request scenario can be a time dynamically adjusted according to the information reception statistics corresponding to each abnormal request scenario. Exemplarily, the information reception statistics corresponding to the abnormal request scenario can be a value obtained by counting the number of abnormal request information corresponding to the same abnormal request scenario received by the authorization server. The larger the value, the more abnormal request information corresponding to the abnormal request scenario received by the authorization server. Based on this, the corresponding waiting time can be set accordingly according to the numerical value of the information reception statistics corresponding to each abnormal request scenario. For example, the larger the numerical value of the information reception statistics, the longer the waiting time can be.

[0085] In this embodiment, by obtaining the information reception statistics corresponding to the abnormal request scenario and obtaining the waiting time of the scenario based on the information reception statistics, the duration of the timer corresponding to the scenario can be dynamically adjusted according to the number of users who want to access the wireless network voice service in the same abnormal request scenario, thereby improving the user experience while avoiding signaling storms.

[0086] In an exemplary embodiment, Figure 4 As shown, obtaining the information reception statistics corresponding to the abnormal request scenario may include:

[0087] Step S401, obtaining the statistical cycle duration, information receiving threshold, and waiting time coefficient corresponding to the abnormal request scenario.

[0088] In this embodiment, the information reception statistics of the abnormal request scenario can be obtained by statistics based on parameters such as the statistical cycle duration, information reception threshold, and waiting time coefficient. Exemplarily, the statistical cycle duration, information reception threshold, and waiting time coefficient corresponding to different abnormal request scenarios can be set in advance. In this step, the statistical cycle duration, information reception threshold, and waiting time coefficient corresponding to the specific abnormal request scenario can be obtained.

[0089] Step S402: according to the duration of the statistical cycle, count the number of abnormal request information corresponding to the abnormal request scenario received in the current cycle.

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

[0091] In some implementations, the time period for counting the number of abnormal request information may be to divide the time into multiple consecutive statistical periods according to the duration of the statistical period, for example, if the statistical duration is q hours, then one day is divided into 24 / q statistical periods. In some implementations, assuming that the authorization server receives the abnormal request information at time t, the statistical period at time t may be 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 may be counted.

[0092] Among them, in some other embodiments, the current period can be determined based on the reception time of the abnormal request information and the statistical period length. For example, the authorization server receives the abnormal request information at time t, and the statistical duration is q. Then the time period between time tq and time t can be taken as the current period, and the number of abnormal request information corresponding to the same abnormal request scenario received during the time period can be counted.

[0093] Step S403: Obtain information reception statistics according to the product of the proportion of the number of abnormal request information in the information reception threshold and the waiting time coefficient.

[0094] In this step, the information reception statistics of the abnormal request scenario corresponding to the abnormal request information received this time can be calculated according to the number of abnormal request information in the current cycle, the information reception threshold and the waiting time coefficient. Exemplarily, assuming that the number of abnormal request information in the current cycle is n, the information reception threshold is m, and the waiting time coefficient is A, the information reception statistics can be expressed as: (n / m)×A. Optionally, after the information reception statistics are calculated, they can be used as the waiting time corresponding to the corresponding abnormal request scenario.

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

[0096] In order to further explain the request information processing method of the present application, the following is a detailed description of the method through an embodiment:

[0097] First, see Figure 5 , which is a schematic diagram of an application scenario of the request information processing method in this embodiment. Among them, the user equipment can sign a wireless network voice service (Voice over Wi-Fi, VoWiFi) with the first operator network (hereinafter referred to as the "first network"); 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 the operator network (hereinafter referred to as the "second network") with which the user equipment has not signed a wireless network voice service contract.

[0098] like Figure 5 As shown, when the user equipment requests to access the wireless network voice service through the access point 1 of the second network in an 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 an 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 an area where the wireless network voice service has not been deployed (case 3), the first network authorization server may 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 may 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] For more information, see Figure 6 , which is a flow chart of the request information processing method in this embodiment.

[0100] Among them, when the user equipment requests to access the wireless network voice service in the above-mentioned situation 1, situation 2 or situation 3, the corresponding first network domain name system server or the second network domain name system server can receive a domain name query request for the evolved packet gateway (evoluted Packet Data Gateway, ePDG) of the first network from the user equipment, and because the first network domain name system server or the second network domain name system server does not have a domain name resolution for the evolved packet gateway, it can send an abnormal request information including the domain name query request of the evolved packet 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] Among them, the first network authorization server can use the query request and address resolution function module to parse the abnormal request information, obtain the first request scenario information according to the network address of the user device contained in the abnormal request information, and obtain the second request scenario information according to the operator network to which the domain name system server that sends the abnormal request information belongs. Exemplarily, the query request and address resolution function module can determine the location information of the user device according to the network address, and then determine whether the location of the user device is the deployment area of ​​the wireless network voice service according to the location information, and obtain the regional abnormality judgment result, and then obtain the first request scenario information according to the regional abnormality judgment result. At the same time, the query request and address resolution function module can also determine whether the domain name system server that sends the abnormal request information is a server on a different network according to the operator network to which the domain name system server belongs, and obtain the access network abnormality judgment result, and then obtain the second request scenario information according to the access network abnormality judgment result.

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

[0103] For example, Figure 5 As shown, when the first request scenario information is non-regional abnormality (i.e., the region where the user equipment is located is a region where wireless network voice services are deployed), and the second request scenario 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 scenario is Figure 5 Case 1 in the example; when the first request scenario information is a regional anomaly (i.e., the user device is located in an area where wireless network voice services are not deployed), and the second request scenario information is a non-access network anomaly (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 scenario is Figure 5Case 2 in the example; when the first request scenario information is non-regional abnormality (i.e., the region where the user device is located is a region where wireless network voice services are not deployed), and the second request scenario 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 scenario is Figure 5 Case 3.

[0104] Among them, when determining a specific abnormal request scenario, the authorization server can obtain the statistical cycle duration, information receiving threshold and waiting time coefficient corresponding to the scenario, and then count the number of abnormal request information corresponding to the abnormal request scenario received in the current period according to the statistical cycle duration, and then obtain the information reception statistical value according to the proportion of the number of abnormal request information in the information receiving threshold and the product of the waiting time coefficient, and finally obtain the waiting time corresponding to the abnormal request scenario according to the information reception statistical value, and send the corresponding timer to the user device.

[0105] Exemplarily, when the abnormal request scenario is situation 1, the authorization server can obtain the statistical cycle duration q1, information receiving threshold m1 and waiting time coefficient A1 corresponding to the scenario, and then count the number of abnormal request information corresponding to the abnormal request scenario received in the current cycle n1 according to the statistical cycle duration q1, and calculate the information receiving statistical value (n1 / m1)×A1. Similarly, when the abnormal request scenario is situation 2, the authorization server can obtain the statistical cycle duration q2, information receiving threshold m2 and waiting time 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 situation 3, the authorization server can obtain the statistical cycle duration q3, information receiving threshold m3 and waiting time 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 to send a timer to the user equipment. The timer may instruct the user equipment not to send a connection establishment request for the wireless network voice service within the waiting time, that is, not to send a domain name query request to the evolved packet gateway.

[0106] Optionally, considering that user devices in areas where wireless network voice services are deployed may access the wireless network through the access point of the first network in a short time and initiate a request to access the wireless network voice service, the waiting time coefficient of each abnormal request scenario can be set to A3>A2>A1.

[0107] In this embodiment, by parsing the abnormal request information, it is determined whether the area where the user equipment is located is the deployment area of ​​the wireless network voice service, and whether the wireless network accessed by the user equipment is the operator network for which it has signed a contract for the wireless network voice service. According to the judgment result, the abnormal request scenario for accessing the wireless network voice service that is prone to signaling storms is divided into three situations, and different timer strategies are assigned respectively. For the three different situations, the waiting time of the timer is dynamically adjusted according to the number of user equipment to be accessed in the current cycle. This solution can effectively prevent the signaling storm between the authorization server of the operator network carrying out the VoWIFI service and the DNS server of the different network / the same network in the scenario where multiple roaming VoWIFI contracted user equipment moves between multiple access points and attempts to make wireless network voice calls, and effectively avoid the risk of paralysis of the authorization server caused by the signaling storm that may be generated when a large number of VoWIFI users increase.

[0108] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages 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 carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0109] Based on the same inventive concept, the embodiment of the present application also provides a request information processing system for implementing the request information processing method involved above. The implementation scheme for solving the problem provided by the system is similar to the implementation scheme recorded 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 above, and will not be repeated here.

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

[0111] The domain name system server is used to send abnormal request information of the wireless network voice service to the domain name system server when receiving the domain name query request of the evolved packet gateway from the user equipment and failing 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;

[0112] The authorization server is used 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 used to obtain the waiting time corresponding to the abnormal request scenario;

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

[0116] In an exemplary embodiment, the authorization server is further used to obtain first request scenario information based on the network address of the user device contained in the abnormal request information; obtain second request scenario information based on the operator network to which the domain name system server that sends the abnormal request information belongs; and determine the abnormal request scenario based on the first request scenario information and the second request scenario information.

[0117] In an exemplary embodiment, the authorization server is further used to determine the location information of the user equipment based on the network address; based on the location information, determine whether the location of the user equipment is the deployment area of ​​the wireless network voice service, and obtain a regional anomaly judgment result; based on the regional anomaly judgment result, obtain the first request scenario information; and / or, based on the operator network to which the domain name system server belongs, determine whether the domain name system server is a server on a different network, and obtain an access network anomaly judgment result; based on the access network anomaly judgment result, obtain the second request scenario information.

[0118] In an exemplary embodiment, the authorization server is further used to obtain 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.

[0119] In an exemplary embodiment, the authorization server is also used to obtain the statistical cycle duration, information receiving threshold, and waiting time coefficient corresponding to the abnormal request scenario; based on the statistical cycle duration, the number of abnormal request information corresponding to the abnormal request scenario received in the current cycle is counted; and the information reception statistical value is obtained based on the proportion of the number of abnormal request information in the information receiving threshold and the product of the waiting time coefficient.

[0120] Based on the same inventive concept, the embodiment of the present application also provides a request information processing device for implementing the request information processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more request information processing device embodiments provided below can refer to the limitations of the request information processing method above, and will not be repeated here.

[0121] In an exemplary embodiment, Figure 8 As shown, a request information processing device 800 is provided, including:

[0122] The receiving module 801 is used to receive abnormal request information of the wireless network voice service; the abnormal request information is sent by the domain name system server when receiving a domain name query request of the evolved packet gateway from the user equipment and failing 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;

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

[0124] The second acquisition module 803 is used to obtain the waiting time corresponding to the abnormal request scenario;

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

[0126] In an exemplary embodiment, the first acquisition module 802 is also used to: obtain first request scenario information based on the network address of the user device contained in the abnormal request information; obtain second request scenario information based on the operator network to which the domain name system server that sends the abnormal request information belongs; and determine the abnormal request scenario based on the first request scenario information and the second request scenario information.

[0127] In an exemplary embodiment, the first acquisition module 802 is also used to: determine the location information of the user equipment according to the network address; determine whether the location of the user equipment is the deployment area of ​​the wireless network voice service according to the location information, and obtain a regional abnormality judgment result; obtain the first request scenario information according to the regional abnormality judgment result; and / or, determine whether the domain name system server is a foreign network server according to the operator network to which the domain name system server belongs, and obtain an access network abnormality judgment result; 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 used to: acquire information reception statistics corresponding to the abnormal request scenario; and obtain the waiting time corresponding to the abnormal request scenario according to the information reception statistics.

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

[0130] Each module in the above-mentioned request information processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module above.

[0131] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig. 9 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store abnormal request information, relevant information of abnormal request scenarios, waiting time corresponding to abnormal request scenarios and other data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a request information processing method is implemented.

[0132] Those skilled in the art will understand that Fig. 9The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may 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 further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0134] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0135] In one embodiment, a computer program product is provided, including a computer program, which 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 used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

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

[0138] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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 application.

[0139] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A request information processing method, characterized in that: The method comprises: Receive abnormal request information for a wireless network voice service; the abnormal request information is sent by a domain name system server when receiving a domain name query request from an evolved packet gateway of a user equipment and failing 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; Determining an abnormal request scenario of the wireless network voice service according to the abnormal request information; Obtain the waiting time corresponding to the abnormal request scenario; A timer is sent to the user equipment according to the waiting time; the timer is used to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting time.

2. The method according to claim 1, characterized in that The determining, according to the abnormal request information, an abnormal request scenario of the wireless network voice service includes: Obtaining first request scenario information according to the network address of the user device included in the abnormal request information; Obtaining second request scenario information according to the operator network to which the domain name system server that sends the abnormal request information belongs; The abnormal request scenario is determined according to the first request scenario information and the second request scenario information.

3. The method according to claim 2, characterized in that The obtaining the first request scenario information according to the network address of the user equipment included in the abnormal request information includes: Determining the location information of the user equipment according to the network address; According to the location information, determining whether the location of the user equipment is a deployment area of ​​the wireless network voice service, and obtaining a region abnormality determination result; According to the abnormality determination result of the region, the first request scenario information is obtained; and / or, The obtaining the second request scenario information according to the operator network to which the domain name system server sending the abnormal request information belongs includes: According to the operator network to which the domain name system server belongs, determining whether the domain name system server is a server on a different network, and obtaining a judgment result of abnormal access network; The second request scenario information is obtained according to the access network abnormality judgment result.

4. The method according to claim 1, characterized in that: The obtaining of the waiting time corresponding to the abnormal request scenario includes: Obtain information reception statistics corresponding to the abnormal request scenario; The waiting time corresponding to the abnormal request scenario is obtained according to the information reception statistics.

5. The method according to claim 4, characterized in that The obtaining of information reception statistics corresponding to the abnormal request scenario includes: Obtain the statistical cycle duration, information receiving threshold, and waiting time coefficient corresponding to the abnormal request scenario; According to the duration of the statistical cycle, counting the number of abnormal request information corresponding to the abnormal request scenario received in the current cycle; The information reception statistic 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 coefficient.

6. A request information processing system, characterized in that: The system includes: a domain name system server and an authorization server; The domain name system server is used to send abnormal request information of the wireless network voice service to the domain name system server when receiving the domain name query request of the evolved packet gateway from the user equipment and failing 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; The authorization server is used to receive the abnormal request information of the wireless network voice service; The authorization server is further configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information; The authorization server is further used to obtain the waiting time corresponding to the abnormal request scenario; The authorization server is further used to send a timer to the user equipment according to the waiting time; the timer is used to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting time.

7. A request information processing device, characterized in that: The device comprises: A receiving module, 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 receiving a domain name query request of an evolved packet gateway from a user equipment and failing 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; A first acquisition module, configured to determine an abnormal request scenario of the wireless network voice service according to the abnormal request information; A second acquisition module is used to obtain the waiting time corresponding to the abnormal request scenario; The sending module is used to send a timer to the user equipment according to the waiting time; the timer is used to instruct the user equipment not to send a domain name query request of the evolved packet gateway within the waiting time.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

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

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images