Network query method and device and medium

Abstract

The invention provides a network query method and device and a medium, and relates to the technical field of networks, and the method comprises the steps: obtaining a to-be-queried special APN name and a to-be-queried query parameter; according to the special APN name and the query parameter, determining a query progressive relationship between network equipment to be queried and the network equipment; and sequentially combining the query result and the query parameter of the network device queried in the previous step in the progressive query relationship to obtain each query instruction of each network device, and sequentially sending each query instruction to each network device until a final query result is obtained. According to the method and the device, the query progressive relationship between the network devices to be queried is determined according to the special APN name and the query parameters to be queried, the query instruction is sequentially obtained based on the progressive relationship, and the query is completed according to the query instruction in sequence until the final query result is obtained, so that the network device information can be efficiently queried.

Description

Technical Field

[0001] The present disclosure at least relates to the field of network technology, and in particular to a network query method, a network query device, and a computer-readable storage medium. Background Art

[0002] By querying the network devices, you can obtain information on the network devices, which can be used to determine the network status, such as locating network faults based on the network information.

[0003] Current network query tools cannot achieve one-click query, and often require manual login to network elements to extract information and conduct analysis and judgment based on information from multiple network elements, resulting in low query efficiency. Summary of the invention

[0004] The technical problem to be solved by the present disclosure is to provide a network query method, a network query device and a computer-readable storage medium in view of the above-mentioned deficiencies, so as to solve the problem of how to efficiently query network device information.

[0005] In a first aspect, the present disclosure provides a network query method, the method comprising:

[0006] Get the dedicated APN name to be queried and the query parameters to be queried;

[0007] Determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter;

[0008] Combining the query result of the previous step of querying the network device in the query progressive relationship with the query parameters in sequence, obtaining each query instruction of each network device, and sending each query instruction to each network device in sequence until the final query result is obtained;

[0009] APN is the access point name.

[0010] Further, the dedicated APN name to be queried and the query parameters to be queried are obtained, specifically including:

[0011] Receiving fault reporting information from an IoT user, wherein a user-side device of the IoT user establishes a dedicated line connection with a core network-side device based on a GRE tunnel, an L2TP tunnel or a direct optical fiber connection;

[0012] Obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information;

[0013] Among them, GRE is Generic Routing Encapsulation and L2TP is Layer 2 Tunneling Protocol.

[0014] Further, obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information specifically includes:

[0015] directly obtain the dedicated APN name of the Internet of Things user from the fault reporting information, or obtain the dedicated APN name of the Internet of Things user according to the MSISDN obtained from the fault reporting information;

[0016] Obtaining the fault type of the IoT user according to the fault reporting information, and determining, according to the fault type, the query parameter to be queried, including at least one of dedicated line type query and online user query, whitelist user query, speed limit query, and GRE dedicated line test;

[0017] Among them, MSISDN is the International Mobile Subscriber Identity Number.

[0018] Further, wherein:

[0019] In response to the fault type being that the designated user cannot access, determining that the query parameters to be queried include a dedicated line type query and a whitelist user query;

[0020] In response to the fault type being that all users cannot access, determining that the query parameters to be queried include dedicated line type query and online user query;

[0021] In response to the fault type being slow network speed, determining that the query parameters to be queried include dedicated line type query and speed limit query;

[0022] In response to obtaining the leased line type as a GRE leased line through leased line type query, it is determined that the query parameters to be queried include a GRE leased line test.

[0023] Further, determining the query progressive relationship between the network device to be queried and the network device according to the dedicated APN name and the query parameter specifically includes:

[0024] Determine all core network side devices and user side devices involved in the dedicated APN name, the core network side devices include SMF network elements and UPF network elements, and in response to the dedicated line type being a GRE dedicated line, the core network side devices also include a key customer switch;

[0025] According to the query parameters, determining, among all the core network side devices and user side devices, a query progressive relationship between a plurality of network devices that require joint debugging query and the network devices;

[0026] Among them, SMF is the service management function and UPF is the user port function.

[0027] Further, according to the query parameters, among all the core network side devices and user side devices, determining a query progressive relationship between a plurality of network devices that require joint debugging query and the network devices, specifically including:

[0028] Determining a first query order for each of the query parameters and query information that needs to be obtained for each of the query parameters;

[0029] Determining a dependency relationship between each of the query information, and determining a second query order for each of the query information according to the dependency relationship;

[0030] According to the first query sequence and the second query sequence, the network devices where the query information is located and the sequence of the network devices in the query progressive relationship are determined.

[0031] Further, wherein:

[0032] The first query order of each query parameter is: dedicated line type query and other parameters, the query information required for the dedicated line type query is the dedicated line type, the network device where the dedicated line type is located is the SMF network element, and the SMF network element for the dedicated line type query based on the dedicated APN name is determined as the first step of querying the network device in the query progressive relationship;

[0033] In response to the remaining parameters including at least one of online user query, whitelist user query or speed limit query, determining that the UPF network element that performs at least one of online user query, whitelist user query or speed limit query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship;

[0034] In response to the remaining parameters including the GRE dedicated line test, determining that the UPF network element that performs the GRE tunnel number query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship,

[0035] Determine that the UPF network element for performing IP address query according to the dedicated line type, the dedicated APN name and the GRE tunnel number is the third step query network device in the query progressive relationship,

[0036] Determine the UPF network element and the user-side device for performing the IP address reachability test from the UPF network element to the user-side device according to the dedicated line type, the dedicated APN name, the GRE tunnel number and the IP address as the fourth step query network device,

[0037] In response to the UPF network element being reachable to the user-side device IP address, determining that the UPF network element for inner layer address query according to the dedicated line type, the dedicated APN name, and the GRE tunnel number is the fifth step query network device in the query progressive relationship,

[0038] Determine the UPF network element, key customer switch and user-side device for performing inner address reachability test from UPF network element to key customer switch and from key customer switch to user-side device as the sixth step to query network devices based on the dedicated line type, the dedicated APN name, GRE tunnel number and inner address.

[0039] Further, sequentially combining the query result of the previous step of querying the network device in the query progressive relationship and the query parameter, obtaining each query instruction of each network device, and sequentially sending each query instruction to each network device until the final query result is obtained, specifically including:

[0040] The first step is to query:

[0041] Sending a first step query instruction including the dedicated APN name to the core network SMF network element to obtain the dedicated line type corresponding to the dedicated APN name, where the dedicated line type includes GRE, L2TP or optical fiber direct connection;

[0042] The following steps are for querying:

[0043] The dedicated line type and the dedicated APN name are obtained as the first key information of the next query instruction, the second key information of the next query instruction is extracted from the query result of the previous query of the network device according to the query progressive relationship, and the third key information of the next query instruction is obtained according to the query parameter and the query progressive relationship.

[0044] The first key information, the second key information and the third key information are combined into a next query instruction, and the next query instruction is sent to the next query network device to obtain a query result of the next query network device.

[0045] Repeat the above process until the network fault location information is obtained, and take the network fault location information as the final query result.

[0046] In a second aspect, the present disclosure provides a network query device, the device comprising:

[0047] An acquisition module, used to acquire the dedicated APN name to be queried and the query parameters to be queried;

[0048] A progressive module, connected to the acquisition module, for determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter;

[0049] A query module, connected to the progressive module, for sequentially combining the query result of the previous step of querying the network device in the query progressive relationship and the query parameter, obtaining each query instruction of each network device, and sequentially sending each query instruction to each network device until the final query result is obtained;

[0050] APN is the access point name.

[0051] In a third aspect, the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the network query method as described above is implemented.

[0052] The present disclosure provides a network query method, a network query device and a computer-readable storage medium. According to a dedicated APN name and query parameters to be queried, a query progressive relationship between a network device to be queried and the network device is determined, and query instructions are obtained in sequence based on the progressive relationship. The query is completed in sequence according to the query instructions until a final query result is obtained. The query progressive relationship can be automatically determined to efficiently query network device information with one click. One of the uses of the final query result includes helping users with dedicated APN names to quickly locate faults. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 is a flow chart of a network query method according to an embodiment of the present disclosure;

[0054] Figure 2 is an architecture diagram of an Internet of Things according to an embodiment of the present disclosure;

[0055] Figure 3 is an architecture diagram of a network query system according to an embodiment of the present disclosure;

[0056] Figure 4 is a schematic diagram of an Internet of Things connection according to an embodiment of the present disclosure;

[0057] Figure 5 is a schematic diagram of query parameters of a network query method according to an embodiment of the present disclosure;

[0058] Figure 6 is a schematic diagram of a GRE test result of a network query method according to an embodiment of the present disclosure;

[0059] Figure 7 is a schematic diagram of whitelist details of a network query method according to an embodiment of the present disclosure;

[0060] Figure 8 It is a structural diagram of a network query device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0061] In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the embodiments of the present disclosure will be further described in detail below with reference to the accompanying drawings.

[0062] It should be understood that the specific embodiments and drawings described herein are only used to explain the present disclosure rather than to limit the present disclosure.

[0063] It can be understood that, in the absence of conflict, the various embodiments of the present disclosure and the various features in the embodiments can be combined with each other.

[0064] It can be understood that, for the convenience of description, the drawings of the present disclosure only show parts related to the present disclosure, while parts irrelevant to the present disclosure are not shown in the drawings.

[0065] It can be understood that each unit and module involved in the embodiments of the present disclosure may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0066] It will be understood that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present disclosure may occur in an order different from that marked in the drawings.

[0067] It is understood that the flowcharts and block diagrams of the present disclosure illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present disclosure. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or may be implemented by a combination of hardware and computer instructions.

[0068] It can be understood that the units and modules involved in the embodiments of the present disclosure can be implemented by software or hardware, for example, the units and modules can be located in a processor.

[0069] Embodiment 1:

[0070] like Figure 1 As shown, the present disclosure provides a network query method, the method comprising:

[0071] S1. Obtain the dedicated APN name to be queried and the query parameters to be queried;

[0072] S2. Determine, according to the dedicated APN name and the query parameter, a query progressive relationship between the network device to be queried and the network device;

[0073] S3, sequentially combining the query result of the previous step of querying the network device in the query progressive relationship and the query parameter, obtaining each query instruction of each network device, and sequentially sending each query instruction to each network device until the final query result is obtained;

[0074] APN is the access point name.

[0075] In this embodiment, for a certain query purpose, the network information that needs to be queried and obtained often has a mutually dependent progressive relationship, especially for users with dedicated APN names, which involve some specific network devices. By progressively obtaining information on these devices, the final query result for the query purpose can be obtained. Therefore, this method determines the query progressive relationship between the network device to be queried and the network device based on the dedicated APN name and the query parameters to be queried, and obtains query instructions in sequence based on the progressive relationship, completes the query in sequence according to the query instructions until the final query result is obtained. The query progressive relationship can be automatically determined to query the network device information efficiently with one click. One of the uses of the final query result includes that it can help users with dedicated APN names quickly locate faults.

[0076] Specifically, this embodiment can provide a tool and method for one-click query of network information, and the tool can be applied to Figure 2 In the IoT architecture shown, users achieve IoT access by customizing APN (Access Point Name), and the user's IoT terminal is registered to the operator's core network through the base station. The base station can connect to the core network through 2G, 3G, 4G, and 5G (second, third, fourth, and fifth generation mobile communication technologies, 2 / 3 / 4 / 5th Generation Mobile Communication Technology). The 4G core network is connected to the user side through the SGW (Serving Gate Way) / PGW (Packet Data Network Gateway) router, and the 5G core network is connected to the user's network through UPF (User Port Function). The route from the IoT terminal to the user side network is opened through the GRE tunnel or L2TP. The overall architecture of the provided tool is as follows: Figure 3As shown, it includes a front-end one-key query page 101, which is a query page developed using the flask framework (a lightweight Web application framework written in Python), and a server 102, which is used to receive instructions sent by the one-key query page 101. After the one-key query page 101 submits the instruction through flask, the server 102 receives the corresponding verification APN name and parameters, and sends them to the core network device 103 through instruction conversion. The server 102 receives the data fed back by the core network device 103, performs desensitization processing and translation, and sends it to the front-end one-key query page 101 for display. By using this tool, a series of operations can be automated when performing the next instruction based on the results returned by the previous instruction step by step, and then based on the key information obtained from the query, which greatly improves the query efficiency.

[0077] For example, Figure 3 The figure shows a one-key query tool for fast positioning of medium and low-speed Internet of Things, which can realize fast query of medium and low-speed Internet of Things services. Options (query parameters) and APN are input through the front-end one-key query page 101 and sent to the back-end server 102. The server 102 translates the corresponding content and sends instructions to SMF (Service Management Function, business management function) / UPF / PGW and other Internet of Things core network devices 103 for query. The server 102 receives the feedback result and outputs it to the front-end one-key query page 101. The front-end can be implemented using the flask framework, and the server side can use python to implement instruction sending and result receiving.

[0078] In one implementation, S1, obtaining a dedicated APN name to be queried and a query parameter to be queried, specifically includes:

[0079] Receiving fault reporting information from an IoT user, wherein a user-side device of the IoT user establishes a dedicated line connection with a core network-side device based on a GRE tunnel, an L2TP tunnel or a direct optical fiber connection;

[0080] Obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information;

[0081] Among them, GRE is Generic Routing Encapsulation and L2TP is Layer 2 Tunneling Protocol.

[0082] In this embodiment, the types of dedicated lines for the Internet of Things mainly include GRE (Generic Routing Encapsulation), L2TP (Layer 2 Tunneling Protocol) and optical fiber direct connection, such as Figure 4It is a diagram of the Internet of Things connection, where the customer router 201 is connected to the core network device 103 via an L2TP tunnel 202, and a method is implemented by the GRE tunnel that enables the Internet of Things card to access the user's intranet.

[0083] More specifically, this embodiment can provide a tool and method for one-click rapid location and diagnosis of faults in medium and low-speed Internet of Things. For example, when receiving a fault report from a user, a customer manager or front-line maintenance personnel can first use the number of online PDPs under the APN to determine whether the service impact scope is as the user said, and query the details of the blacklist and whitelist APN to determine whether the abnormal access address mentioned by the user is included in the three-layer and seven-layer address list applied for and opened in the early stage. Combined with the number of online users, it can assist in determining whether a single user terminal is faulty or the entire APN of the user is completely disconnected, which can help locate the fault point, or determine whether it is a false report by the user.

[0084] In one implementation, obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information specifically includes:

[0085] directly obtain the dedicated APN name of the Internet of Things user from the fault reporting information, or obtain the dedicated APN name of the Internet of Things user according to the MSISDN obtained from the fault reporting information;

[0086] Obtaining the fault type of the IoT user according to the fault reporting information, and determining, according to the fault type, the query parameter to be queried, including at least one of dedicated line type query and online user query, whitelist user query, speed limit query, and GRE dedicated line test;

[0087] Among them, MSISDN is the International Mobile Subscriber Identity Number.

[0088] In this embodiment, if Figure 5 As shown, this tool can select parameters through a drop-down menu on the front-end page of the supporting R&D, including the dedicated line type (in the Internet of Things, dedicated lines mainly refer to GRE and L2TP dedicated lines), the number of online PDPs (Packet Data Protocol) under the APN, black and white user lists, speed limit queries, GRE dedicated line disconnection detection and other common query parameters. PDP can be simply understood as the number of online user terminals. Generally, one user corresponds to one PDP. Internet of Things users basically only have data PDPs, and some users will establish a voice PDP. The dedicated APN name can be obtained based on the MSISDN (International Mobile Subscriber Identity Number, Mobile Station International Subscriber Directory Number).

[0089] In one embodiment, wherein:

[0090] In response to the fault type being that the designated user cannot access, determining that the query parameters to be queried include a dedicated line type query and a whitelist user query;

[0091] In response to the fault type being that all users cannot access, determining that the query parameters to be queried include dedicated line type query and online user query;

[0092] In response to the fault type being slow network speed, determining that the query parameters to be queried include dedicated line type query and speed limit query;

[0093] In response to obtaining the leased line type as a GRE leased line through leased line type query, it is determined that the query parameters to be queried include a GRE leased line test.

[0094] In this embodiment, the GRE dedicated line connection and disconnection detection mainly includes ping test (a network diagnostic tool) of the interface address and the inner layer address, which are respectively used to eliminate the transmission bearer problem or the GRE inner layer link problem. A demonstration of the test result is as follows: Figure 6 As shown in the Output section. In 4G communication, PDP activation refers to a mobile device requesting the network to assign an IP address and establish a data communication channel. In 4G LTE (Long Term Evolution) networks, PDP context (also called PDP Context) refers to the data communication connection established between a mobile device (such as a mobile phone or wireless communication module) and the network. It contains all the configuration information required for data transmission, including APN, QoS (Quality of Service), PDP type (usually IP), PDP address (IP address of the device), etc. The black and white list is a type of dedicated APN. Each whitelist APN provides a set of restricted access IP addresses or URLs when applying. It is mainly used to determine whether the address the user wants to access is in the restricted access list provided in the previous application when the user reports a fault, and the existing network has been configured, such as Figure 7 The Output section shows the query results for the Layer 3 IP (Internet Protocol) address and Layer 7 URL.

[0095] In one implementation, S2, determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter, specifically includes:

[0096] Determine all core network side devices and user side devices involved in the dedicated APN name, the core network side devices include SMF network elements and UPF network elements, and in response to the dedicated line type being a GRE dedicated line, the core network side devices also include a key customer switch;

[0097] According to the query parameters, determining, among all the core network side devices and user side devices, a query progressive relationship between a plurality of network devices that require joint debugging query and the network devices;

[0098] Among them, SMF is the service management function and UPF is the user port function.

[0099] In this embodiment, the dedicated APN name of the Internet of Things corresponds to the user. Most large users of the Internet of Things have a dedicated APN name. According to the APN type, some certain core network devices will be involved. For example, GRE users will be involved in the data configuration of SMF / UPF / PGW / large customer switches and other devices of the core network, and L2TP and whitelist users will be involved in the data configuration of SMF / UPF / PGW and other devices. The interface number can be queried through the large customer switch, which involves transmission configuration. L2TP and whitelist users do not involve this device. L2TP is directly linked to the operator's UPF. The user-side device is more complex. The L2TP user side can customize more functions. The operator can check less things. This tool does not currently support deeper queries such as L2TP fault location, but can implement some relatively simple queries. No equipment is required on the whitelist user side. It only involves the accessibility of its layer 3 or layer 7 address, and it can be directly pinged in the operator network.

[0100] The IoT GRE circuit is a new type of communication network. Locating IoT GRE faults requires logging into multiple core network nodes, which takes a long time. Through the fast positioning tool of this embodiment, the fault judgment time can be shortened to minutes, and front-line engineers can judge the fault point more quickly and intuitively. It mainly uses programming methods to allow the front end to receive data, and the back end to automatically log in to the core network element for verification. The verification data is automatically desensitized, which simplifies the work of maintenance personnel and improves the verification efficiency of front-line personnel. According to the APN name entered by the engineer, the program automatically executes a series of related query instructions. According to the return result of the previous step instruction, the program extracts the key information required for the next query operation, and executes step by step until the final required result is obtained, and desensitizes and converts it into easy-to-understand text to feedback to the front desk. The information is automatically processed, saving a lot of time.

[0101] In one embodiment, according to the query parameters, determining the query progressive relationship between a plurality of network devices requiring joint debugging query and the network devices among all the core network side devices and the user side devices specifically includes:

[0102] Determining a first query order for each of the query parameters and query information that needs to be obtained for each of the query parameters;

[0103] Determine a dependency relationship between each of the query information, and determine a second query order for each of the query information according to the dependency relationship;

[0104] According to the first query sequence and the second query sequence, the network devices where the query information is located and the sequence of the network devices in the query progressive relationship are determined.

[0105] In this embodiment, this tool adopts a modular structure during research and development, and each module can be called in combination with each other. When a new query requirement is added, only a new module needs to be compiled. The parameters selected by the user of the front-end page are received through the restful (a design style that defines the WebAPI interface) interface program developed and deployed by the tool, and the query module corresponding to the parameters is selected. The information to be queried is converted into a series of system instructions, which are sent to the device network manager for execution, and the required key information is extracted from the results returned by the network manager using regular expressions and other methods, or directly fed back and output after desensitization, or further converted into the next system instruction as needed and sent to the device network manager for execution until the required query result is obtained, and then fed back and output after desensitization.

[0106] In one embodiment, wherein:

[0107] The first query order of each query parameter is: dedicated line type query and other parameters, the query information required for the dedicated line type query is the dedicated line type, the network device where the dedicated line type is located is the SMF network element, and the SMF network element for the dedicated line type query based on the dedicated APN name is determined as the first step of querying the network device in the query progressive relationship;

[0108] In response to the remaining parameters including at least one of online user query, whitelist user query or speed limit query, determining that the UPF network element that performs at least one of online user query, whitelist user query or speed limit query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship;

[0109] In response to the remaining parameters including the GRE dedicated line test, determining that the UPF network element that performs the GRE tunnel number query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship,

[0110] Determine that the UPF network element for performing IP address query according to the dedicated line type, the dedicated APN name and the GRE tunnel number is the third step query network device in the query progressive relationship,

[0111] Determine the UPF network element and the user-side device for performing the IP address reachability test from the UPF network element to the user-side device according to the dedicated line type, the dedicated APN name, the GRE tunnel number and the IP address as the fourth step query network device,

[0112] In response to the UPF network element being reachable to the user-side device IP address, determining that the UPF network element for inner layer address query according to the dedicated line type, the dedicated APN name, and the GRE tunnel number is the fifth step query network device in the query progressive relationship,

[0113] Determine the UPF network element, key customer switch and user-side device for performing inner address reachability test from UPF network element to key customer switch and from key customer switch to user-side device as the sixth step to query network devices based on the dedicated line type, the dedicated APN name, GRE tunnel number and inner address.

[0114] In this embodiment, medium and low-speed Internet of Things can be implemented based on GRE user tunnels. GRE and L2TP are two different tunnel protocols, each with its own applications and characteristics in network communications. GRE is a network layer tunnel protocol that can encapsulate a variety of network layer protocols, such as IP or IPX (Internetwork Packet Exchange), and transmit them in another network layer protocol. GRE supports point-to-point or point-to-multipoint communications and is often used to build APNs. GRE itself does not provide encryption, but it can be used in conjunction with encryption protocols such as IPSec (Internet Protocol Security) to provide security. GRE can encapsulate a variety of protocols, supports multicast, and can be used to build flexible APN solutions. This tool does not yet involve the precise location of L2TP tunnel user APN faults.

[0115] Specifically, for GRE type APN users, the query progressive relationship includes: first, sending instructions to SMF to query the basic information of APN to obtain the type of APN, and judging the next step of query execution according to the type keyword. For example, first, the first step of query is performed in SMF, and the query with the apn name as the keyword is first sent to obtain the apn type; then the query instruction corresponding to the next step of this type of apn is sent, for example, the instruction to query the tunnel number (the number of the GRE tunnel) of the gre type apn is sent to UPF, and the tunnel number is obtained by regular matching; the apn name and the tunnel number obtained in the previous step will be entered in the next step of the instruction to send the next step of the query instruction, for example, according to the result returned by the device, the IP address of the operator side and user side device interface configured by the gre type apn is obtained by regular matching, and the built-in re module of python ( A module for processing regular expressions) is used to formulate rules, and different rules are used to extract various keywords, which are executed on the UPF; and the first step is to send a ping test command with the operator-side interface IP address as the source address (generally the board used to carry out GRE services on the UPF) and the user-side device interface IP address as the destination address to determine whether the interface address is reachable. This step can locate whether there is a problem with the transmission bearer layer; if it is reachable, the next step is to query, and continue to query the operator core network side (generally the board used to carry out GRE services on the UPF) and the inner address of the user side of the gre type apn configuration according to the tunnel number, so as to carry out subsequent fault location test instructions. The instructions are sent to the UPF and the large customer switch, and first sent to the large customer switch to perform a ping test to the user-side interface address, and then perform a ping test from the UPF to the user-side inner address. The following is an example of the code for extracting the destination address and the matching code for the APN name. The matching process belongs to the matching rule action of the python programming language:

[0116] ipv4_pattern=r′\b(?:[0-9]{1,3}\.){3}[0-9]{1,3}\b′

[0117] vpn_name_pattern=r′Destination VPN name\s*=\s*([^\s]+)′

[0118] ipv4_addresses=re.findall(ipv4_pattern, output3)

[0119] vpn_narne=re.search(vpn_name_pattern, output3)

[0120] In one embodiment, S3, sequentially combining the query result of the previous query of the network device in the query progressive relationship and the query parameter, obtaining each query instruction of each network device, and sequentially sending each query instruction to each network device until the final query result is obtained, specifically includes:

[0121] The first step is to query:

[0122] Sending a first step query instruction including the dedicated APN name to the core network SMF network element to obtain the dedicated line type corresponding to the dedicated APN name, where the dedicated line type includes GRE, L2TP or optical fiber direct connection;

[0123] The following steps are for querying:

[0124] The dedicated line type and the dedicated APN name are obtained as the first key information of the next query instruction, the second key information of the next query instruction is extracted from the query result of the previous query of the network device according to the query progressive relationship, and the third key information of the next query instruction is obtained according to the query parameter and the query progressive relationship.

[0125] The first key information, the second key information and the third key information are combined into a next query instruction, and the next query instruction is sent to the next query network device to obtain a query result of the next query network device.

[0126] Repeat the above process until the network fault location information is obtained, and take the network fault location information as the final query result.

[0127] In this embodiment, the key information mainly includes several IP addresses and device information configured by several devices on the dedicated core network side for joint debugging with the user side devices. When the GRE dedicated line service is opened, this information is configured by the core network maintenance personnel in the SMF, UPF and key customer switches and the user side devices. The specific implementation methods of the corresponding configurations of other types of dedicated lines may be different. L2TP has more information configured by the user, and may not be able to accurately locate the fault, but it can still perform a preliminary fault analysis. Through several progressive device instructions, query in sequence, and continue to make subsequent queries according to the results returned by the progressive instructions. For example, first obtain the APN type through the APN name query, and then send and execute the next query instruction of this type of APN, such as sending an instruction to query the tunnel number of the GRE type APN, and then send the next query instruction according to the tunnel number to obtain the user-side device interface address configured with the GRE type APN, and perform the first step of ping test to determine whether the interface address is reachable. This step can locate whether there is a problem with the transmission bearer layer. If it is reachable, proceed to the next step of query, and continue to query the inner layer address of the Unicom core network side and the user side of the GRE type APN configuration according to the tunnel number, so as to issue subsequent fault location test instructions.

[0128] The above progressive device instructions are a complete progressive query process determined by the program itself based on the query parameters. The goal of the query is to perform a fault location test, including: the first step is to query the APN type from the SMF according to the APN name; the second step is to query the tunnel number from the UPF according to the result of the first step; the third step is to query the device interface IP address from the GRE interface configuration according to the result of the second step; the fourth step is to test whether the user device is reachable through the network according to the result of the third step; if the network is reachable, further confirm whether there are other faults in the network, and then test whether the inner link is normal. For example, the fifth step is generally to query the inner addresses of the Unicom side and the user side from the GRE interface configuration module again, and the sixth step is to ping again. If it is still normal, the maintenance personnel need to contact the user for more in-depth investigation, generally signaling tracking.

[0129] In the tool, the query result of the previous device will affect the query instruction of the next device. The key information required for the next instruction must be extracted based on the result information returned by the previous instruction. The key information is mainly obtained through regular matching and other matching methods. It can realize one-click query of the user's APN type, whitelist details, number of online users, GRE type, speed limit and other functions, automatically log in to the network element to extract information, form a fault judgment idea based on the query route, and analyze and judge based on the information of multiple network elements.

[0130] In addition to helping users quickly locate GRE faults, the tool of this embodiment can also handle IoT complaints based on other situations. For example, if a user reports that a certain address cannot be accessed, this type of user is usually a whitelist APN user. By entering the user's APN name and one-click query, you can get the whitelist details configured in the current network, and then compare it with the address complained by the user, and compare it with the address actually accessed by the user terminal obtained through signaling tracking, and make a preliminary judgment and location of the fault. For another example, the user may say that his network is completely disconnected. Through online user query, you can preliminarily judge whether the user's response is true. Combined with the call bill traffic query of the IoT platform, you can further locate the fault point and judge the actual impact range. The tool builds a B / S (Browser / Server) structure. According to the parameters of the one-click query page 101, it selects GRE dedicated line connection and disconnection detection, the number of online PDPs under APN, the black and white user list, etc., and sends instructions to the core network element (core network equipment 103) on the server 102 to collect data and detect channels. It can make logical judgments based on the input information and comprehensively output information results to help front-line personnel quickly troubleshoot and solve problems.

[0131] The tool provided in this embodiment can quickly locate the cause of the IoT failure when there are many IoT users based on GRE tunnels at the regional IoT scale. According to the process operation of this tool, the module is used for testing to obtain the result of verifying the IoT failure; on the front-end page of the tool supporting R&D, the APN and parameter selection of the IoT card can be used to verify the information with one click, quickly locate the cause of the IoT failure, and shorten the fault verification and processing time; front-line personnel can verify independently to help front-line personnel increase their verification capabilities. In addition, the data has been desensitized and processed to avoid leakage of network element data and user data, and only helps personnel to locate and verify the fault; the front-end and back-end are connected through programming to avoid manual login to the network element to check the time and enter the wrong command.

[0132] Embodiment 2:

[0133] like Figure 8 As shown, the present disclosure provides a network query device, the device comprising:

[0134] Acquisition module 1, used to acquire the dedicated APN name to be queried and the query parameters to be queried;

[0135] A progressive module 2, connected to the acquisition module 1, for determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter;

[0136] The query module 3 is connected to the progressive module 2 and is used to sequentially combine the query result of the previous step of querying the network device in the query progressive relationship and the query parameter to obtain each query instruction of each network device, and sequentially send each query instruction to each network device until the final query result is obtained;

[0137] APN is the access point name.

[0138] In one embodiment, the acquisition module 1 specifically includes:

[0139] A receiving unit, configured to receive fault reporting information from an IoT user, wherein a user-side device of the IoT user establishes a dedicated line connection with a core network-side device based on a GRE tunnel, an L2TP tunnel or a direct optical fiber connection;

[0140] An acquisition unit, connected to the receiving unit, for acquiring the dedicated APN name of the IoT user and a query parameter to be queried for processing the fault reporting information;

[0141] Among them, GRE is Generic Routing Encapsulation and L2TP is Layer 2 Tunneling Protocol.

[0142] In one embodiment, the acquisition unit specifically includes:

[0143] An APN name acquisition unit, configured to directly acquire the dedicated APN name of the Internet of Things user from the fault reporting information, or to acquire the dedicated APN name of the Internet of Things user according to the MSISDN acquired from the fault reporting information;

[0144] A query parameter acquisition unit, configured to acquire the fault type of the IoT user according to the fault reporting information, and determine, according to the fault type, that the query parameter to be queried includes at least one of a dedicated line type query and an online user query, a whitelist user query, a speed limit query, and a GRE dedicated line test;

[0145] Among them, MSISDN is the International Mobile Subscriber Identity Number.

[0146] In one implementation, the query parameter obtaining unit is specifically used to:

[0147] In response to the fault type being that the designated user cannot access, determining that the query parameters to be queried include a dedicated line type query and a whitelist user query;

[0148] In response to the fault type being that all users cannot access, determining that the query parameters to be queried include dedicated line type query and online user query;

[0149] In response to the fault type being slow network speed, determining that the query parameters to be queried include dedicated line type query and speed limit query;

[0150] In response to obtaining the leased line type as a GRE leased line through leased line type query, it is determined that the query parameters to be queried include a GRE leased line test.

[0151] In one embodiment, the progressive module 2 specifically includes:

[0152] A device determination unit, configured to determine all core network side devices and user side devices involved in the dedicated APN name, wherein the core network side devices include SMF network elements and UPF network elements, and in response to the dedicated line type being a GRE dedicated line, the core network side devices also include a large customer switch;

[0153] A sequence determination unit connected to the device determination unit, configured to determine, according to the query parameter, a query progressive relationship between a plurality of network devices that require joint debugging query and the network devices in all the core network side devices and the user side devices;

[0154] Among them, SMF is the service management function and UPF is the user port function.

[0155] In one implementation, the sequence determination unit specifically includes:

[0156] A first order determining unit, used to determine a first query order of each of the query parameters and query information that needs to be obtained for each of the query parameters;

[0157] A second sequence determination unit, connected to the first sequence determination unit, is used to determine a dependency relationship between each of the query information, and determine a second query sequence of each of the query information according to the dependency relationship;

[0158] The progressive relationship determination unit is connected to the second sequence determination unit and is used to determine the network device where each query information is located and the sequence of the network device in the query progressive relationship according to the first query sequence and the second query sequence.

[0159] In one embodiment, in the sequence determination unit:

[0160] The first query order of each query parameter is: dedicated line type query and other parameters, the query information required for the dedicated line type query is the dedicated line type, the network device where the dedicated line type is located is the SMF network element, and the SMF network element for the dedicated line type query based on the dedicated APN name is determined as the first step of querying the network device in the query progressive relationship;

[0161] In response to the remaining parameters including at least one of online user query, whitelist user query or speed limit query, determining that the UPF network element that performs at least one of online user query, whitelist user query or speed limit query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship;

[0162] In response to the remaining parameters including the GRE dedicated line test, determining that the UPF network element that performs the GRE tunnel number query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship,

[0163] Determine that the UPF network element for performing IP address query according to the dedicated line type, the dedicated APN name and the GRE tunnel number is the third step query network device in the query progressive relationship,

[0164] Determine the UPF network element and the user-side device for performing the IP address reachability test from the UPF network element to the user-side device according to the dedicated line type, the dedicated APN name, the GRE tunnel number and the IP address as the fourth step query network device,

[0165] In response to the UPF network element being reachable to the user-side device IP address, determining that the UPF network element for inner layer address query according to the dedicated line type, the dedicated APN name, and the GRE tunnel number is the fifth step query network device in the query progressive relationship,

[0166] Determine the UPF network element, key customer switch and user-side device for performing inner address reachability test from UPF network element to key customer switch and from key customer switch to user-side device as the sixth step to query network devices based on the dedicated line type, the dedicated APN name, GRE tunnel number and inner address.

[0167] In one implementation, the query module 3 specifically includes:

[0168] A first query unit is used to send a first step query instruction including the dedicated APN name to the core network SMF network element to obtain a dedicated line type corresponding to the dedicated APN name, where the dedicated line type includes GRE, L2TP or optical fiber direct connection;

[0169] The subsequent query units, the first query unit and the subsequent query units are connected in sequence, specifically including:

[0170] The instruction information extraction unit is used to obtain the dedicated line type and the dedicated APN name as the first key information of the next query instruction, extract the second key information of the next query instruction from the query result of the previous query of the network device according to the query progressive relationship, and obtain the third key information of the next query instruction according to the query parameter and the query progressive relationship.

[0171] The instruction transceiver unit is connected to the instruction information extraction unit, and is used to combine the first key information, the second key information and the third key information into a next query instruction, and send the next query instruction to the next query network device to obtain the query result of the next query network device.

[0172] The loop control unit is connected to the instruction transceiver unit and is used to repeat the above process until the network fault location information is obtained, and the network fault location information is used as the final query result.

[0173] Embodiment 3:

[0174] Embodiment 3 of the present disclosure provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the network query method as described in Embodiment 1 or the network query device as described in Embodiment 2 is implemented.

[0175] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0176] In addition, the present disclosure may also provide a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the network query method as described in Example 1. The computer device may be a network query device as described in Example 2.

[0177] The memory is connected to the processor, the memory may be a flash memory or a read-only memory or other memory, and the processor may be a central processing unit or a single-chip microcomputer.

[0178] Embodiments 1-3 of the present disclosure provide a network query method, a network query device, and a computer-readable storage medium, which determine the query progressive relationship between the network device to be queried and the network device according to the dedicated APN name and the query parameters to be queried, and obtain query instructions in sequence based on the progressive relationship, and complete the query in sequence according to the query instructions until the final query result is obtained. The query progressive relationship can be automatically determined to efficiently query network device information with one click, and one of the uses of the final query result includes helping users with dedicated APN names to quickly locate faults.

[0179] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present disclosure, but the present disclosure is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and substance of the present disclosure, and these modifications and improvements are also considered to be within the scope of protection of the present disclosure.

Claims

1. A network query method, characterized in that: The method comprises: Get the dedicated APN name to be queried and the query parameters to be queried; Determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter; Combining the query result of the previous step of querying the network device in the query progressive relationship with the query parameters in sequence, obtaining each query instruction of each network device, and sending each query instruction to each network device in sequence until the final query result is obtained; APN is the access point name.

2. The method according to claim 1, characterized in that Get the dedicated APN name to be queried and the query parameters to be queried, including: Receiving fault reporting information from an IoT user, wherein a user-side device of the IoT user establishes a dedicated line connection with a core network-side device based on a GRE tunnel, an L2TP tunnel or a direct optical fiber connection; Obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information; Among them, GRE is Generic Routing Encapsulation and L2TP is Layer 2 Tunneling Protocol.

3. The method according to claim 2, characterized in that Obtaining the dedicated APN name of the IoT user and the query parameters to be queried for processing the fault reporting information, specifically including: directly obtain the dedicated APN name of the Internet of Things user from the fault reporting information, or obtain the dedicated APN name of the Internet of Things user according to the MSISDN obtained from the fault reporting information; Obtaining the fault type of the IoT user according to the fault reporting information, and determining, according to the fault type, the query parameter to be queried, including at least one of dedicated line type query and online user query, whitelist user query, speed limit query, and GRE dedicated line test; Among them, MSISDN is the International Mobile Subscriber Identity Number.

4. The method according to claim 3, characterized in that in: In response to the fault type being that the designated user cannot access, determining that the query parameters to be queried include a dedicated line type query and a whitelist user query; In response to the fault type being that all users cannot access, determining that the query parameters to be queried include dedicated line type query and online user query; In response to the fault type being slow network speed, determining that the query parameters to be queried include dedicated line type query and speed limit query; In response to obtaining the leased line type as a GRE leased line through leased line type query, it is determined that the query parameters to be queried include a GRE leased line test.

5. The method according to any one of claims 1 to 4, characterized in that Determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter specifically includes: Determine all core network side devices and user side devices involved in the dedicated APN name, the core network side devices include SMF network elements and UPF network elements, and in response to the dedicated line type being a GRE dedicated line, the core network side devices also include a key customer switch; According to the query parameters, determining, among all the core network side devices and user side devices, a query progressive relationship between a plurality of network devices that require joint debugging query and the network devices; Among them, SMF is the service management function and UPF is the user port function.

6. The method according to claim 5, characterized in that According to the query parameters, determining the query progressive relationship between a plurality of network devices that need joint debugging query and the network devices among all the core network side devices and user side devices, specifically including: Determining a first query order for each of the query parameters and query information that needs to be obtained for each of the query parameters; Determining a dependency relationship between each of the query information, and determining a second query order for each of the query information according to the dependency relationship; According to the first query sequence and the second query sequence, the network devices where the query information is located and the sequence of the network devices in the query progressive relationship are determined.

7. The method according to claim 6, characterized in that in: The first query order of each query parameter is: dedicated line type query and other parameters, the query information required for the dedicated line type query is the dedicated line type, the network device where the dedicated line type is located is the SMF network element, and the SMF network element for the dedicated line type query based on the dedicated APN name is determined as the first step of querying the network device in the query progressive relationship; In response to the remaining parameters including at least one of online user query, whitelist user query or speed limit query, determining that the UPF network element that performs at least one of online user query, whitelist user query or speed limit query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship; In response to the remaining parameters including the GRE dedicated line test, determining that the UPF network element that performs the GRE tunnel number query according to the dedicated line type and the dedicated APN name is the second step query network device in the query progressive relationship, Determine that the UPF network element for performing IP address query according to the dedicated line type, the dedicated APN name and the GRE tunnel number is the third step query network device in the query progressive relationship, Determine the UPF network element and the user-side device for performing the IP address reachability test from the UPF network element to the user-side device according to the dedicated line type, the dedicated APN name, the GRE tunnel number and the IP address as the fourth step query network device, In response to the UPF network element being reachable to the user-side device IP address, determining that the UPF network element for inner layer address query according to the dedicated line type, the dedicated APN name, and the GRE tunnel number is the fifth step query network device in the query progressive relationship, Determine the UPF network element, key customer switch and user-side device for performing inner address reachability test from UPF network element to key customer switch and from key customer switch to user-side device as the sixth step to query network devices based on the dedicated line type, the dedicated APN name, GRE tunnel number and inner address.

8. The method according to claim 7, characterized in that Combining the query result of the previous query of the network device in the query progressive relationship and the query parameter in sequence, obtaining each query instruction of each network device, and sending each query instruction to each network device in sequence until the final query result is obtained, specifically including: The first step is to query: Sending a first step query instruction including the dedicated APN name to the core network SMF network element to obtain the dedicated line type corresponding to the dedicated APN name, where the dedicated line type includes GRE, L2TP or optical fiber direct connection; The following steps are for querying: The dedicated line type and the dedicated APN name are obtained as the first key information of the next query instruction, and the second key information of the next query instruction is extracted from the query result of the previous query of the network device according to the query progressive relationship, and the third key information of the next query instruction is obtained according to the query parameter and the query progressive relationship. The first key information, the second key information and the third key information are combined into a next query instruction, and the next query instruction is sent to the next query network device to obtain a query result of the next query network device. Repeat the above process until the network fault location information is obtained, and take the network fault location information as the final query result.

9. A network query device, characterized in that: The device comprises: An acquisition module, used to acquire the dedicated APN name to be queried and the query parameters to be queried; A progressive module, connected to the acquisition module, for determining a query progressive relationship between a network device to be queried and the network device according to the dedicated APN name and the query parameter; A query module, connected to the progressive module, for sequentially combining the query result of the previous step of querying the network device in the query progressive relationship and the query parameter, obtaining each query instruction of each network device, and sequentially sending each query instruction to each network device until the final query result is obtained; APN is the access point name.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the network query method according to any one of claims 1 to 8 is implemented.

Images