CN101730069B - Method, system and device for querying HLR user data - Google Patents

Abstract

The invention relates to the mobile communication technology, and discloses a method, a system and a device for querying HLR user data so as to improve the efficiency of querying the HLR user data. The method for querying the HLR user data comprises the following steps: receiving an HLR data remote query service request forwarded by a query terminal, wherein the remote query service request carries identification information of a user to be queried; according to the identification information of the user to be queried carried in the query service request, establishing connection with an HLR to which the user to be queried belongs and performing user data query; and when the connection establishment or the user data query is failed, releasing the connection with the HLR and returning failure indication information to the query terminal, and returning a query result to the query terminal after the query is successful.

Description

A method, system and device for HLR user data inquiry

technical field

The present invention relates to mobile communication technology, in particular to a method, system and device for HLR (Home Location Register, Home Location Register) user data query in mobile communication technology. the

Background technique

Most of the user complaints from the operator are complaints about network problems. For such complaints, the customer service personnel must first query the user data in the HLR according to the user identification information, so as to first determine whether there is a wrong user data setting. Therefore, the customer service Personnel will carry out a large amount of HLR user data inquiry every day. the

However, due to technical conditions and network limitations, customer service personnel cannot directly log in to the HLR in the customer service system to query user data, but use a remote login tool to query, and this query method does not support concurrent queries, that is, when an HLR is in When logging in, the HLR is not allowed to log in again, and there is no error handling mechanism, so when the login HLR fails due to objective reasons, it cannot log out in time, and the HLR cannot be used to log in again. Great inconvenience reduces the efficiency of HLR user data query. the

Contents of the invention

Embodiments of the present invention provide a method, system and device for HLR user data query, so as to improve HLR query efficiency. the

A kind of HLR subscriber data inquiry system, comprises at least one HLR, also comprises:

The query terminal is used to receive the user identification information to be queried, generate and send an HLR data remote query service request, the remote query service request carries the user identification information to be queried, and receive the query result returned according to the HLR data remote query service request and send show;

The query subsystem is configured to receive the HLR data remote query service request sent by the query terminal, establish a connection with the HLR to which the user to be query belongs and perform user data query according to the user identification information to be queried carried in the remote query service request , and when the connection establishment fails or the user data query fails, release the connection with the HLR and return failure indication information to the query terminal, and return the query result to the query terminal after the query succeeds. the

The query subsystem specifically includes:

The WEB server is used to receive and forward the HLR data remote query service request sent by the query terminal;

The query server is configured to receive the HLR data remote query service request forwarded by the WEB server, establish a connection with the HLR to which the user to be queried belongs and perform user data query according to the user identification information to be queried carried in the remote query service request, And when the connection fails to be established or the user data query fails, release the connection with the HLR and return failure indication information to the query terminal through the WEB server, and return the query result to the query terminal through the WEB server after the query succeeds. the

Further, the query server is also used to translate the queried user data into information described in natural language, and return the translated information to the query terminal as a query result. the

The query server is also used to set up a queue of corresponding user identification information to be queried for each HLR according to the receiving sequence of the HLR data remote query service request, and according to the user identification information to be queried in the user identification information queue to be queried, Perform user data query to HLR in turn, or initiate parallel query to HLR. the

Further, the query server is further configured to, according to the queue length threshold value of the user identification information to be queried, when the queue corresponding to the user identification information to be queried carried in the received remote query service request is full, send The query terminal returns the prompt information for later query. the

Furthermore, the query server is also used to set the queue length threshold of the user identification information to be queried corresponding to the HLR to a fixed value, or

Determine the queue length threshold of the user identification information to be queried corresponding to the HLR according to the empirical data. the

More preferably, the query server is set in the network management network, and the WEB server is set at the firewall of the network management network. the

A query server comprising:

The identification unit is used to receive the HLR data remote query service request from the WEB server, and identify the home HLR of the user to be queried according to the user identification information to be queried carried in the remote query service request;

The login unit is used to establish a connection with the HLR of the user to be queried and perform user data query, and when the connection fails to be established or the user data query fails, the connection between the HLR is released and the failure indication information is sent to the WEB server. After success, send the query result to the WEB server. the

The dispatching unit is used for according to the reception sequence of the HLR data remote query service request, for each HLR, establishes a queue of corresponding user identification information to be inquired, and puts the user identification information to be inquired into the queue of user identification information to be inquired, by The login unit logs in to the HLR in turn to query the user data corresponding to the user identification information in the HLR in the queue, or concurrently queries the user data in the HLR corresponding to each user identification information in the queue after logging in to the HLR in parallel. the

Further, the dispatching unit is further configured to, according to the queue length threshold value of the user identification information to be queried, when the queue corresponding to the user identification information to be queried carried in the received remote query service request is full, send The query terminal returns the prompt information for later query. the

Furthermore, the scheduling unit is further configured to determine the queue length threshold value of the user identification information to be queried according to the empirical data. the

Also included in the query server:

The parsing unit is configured to translate the user data information obtained by the login unit into information described in natural language, and send the translated information as a query result. the

A kind of HLR user data query method, comprising:

Receive the HLR data remote query service request forwarded by the query terminal, and the remote query service request carries the user identification information to be queried;

According to the user identification information to be queried carried in the remote query service request, establish a connection with the HLR to which the user to be queried belongs and perform user data query; and

When the connection establishment fails or the user data query fails, the connection with the HLR is released and failure indication information is returned to the query terminal, and the query result is returned to the query terminal after the query succeeds. the

According to the receiving sequence of the HLR data remote query service request, set up a corresponding queue of user identification information to be inquired for each HLR, and after receiving the HLR data remote query service request, put the user identification information to be inquired into carried therein in the corresponding queue; and

The querying of user data specifically includes: performing user data query to the HLR sequentially or in parallel according to the user identification information to be queried in the queue of user identification information to be queried. the

Further, before putting the user identification information to be queried into the corresponding queue, first according to the queue length threshold value of the HLR corresponding to the user identification information to be queried, when the queue of the user identification information to be queried is full, return the query prompt information later , otherwise put the user identification information to be queried into the corresponding queue. the

Furthermore, the queue length threshold value of the user identification information to be queried is a fixed value, or is determined according to time according to empirical data. the

More preferably, after the query is successful, the queried user data is first translated into information described in natural language, and then the translated information is returned as the query result. the

The method for determining the connection establishment failure or the user data query failure specifically includes:

When requesting to establish a connection, when the connection confirmation signal returned by the HLR is not received within the maximum connection time set, it is determined that the connection establishment fails;

When querying user data, if the data is not successfully received or the received data does not contain the keywords carried in the step settings, it is determined that the query fails. the

The embodiment of the present invention provides the HLR user data query method, system and device, in the process of logging into the HLR or the query process, when the login HLR fails or the query fails, the HLR can be exited in time, and the login again is no longer affected, thereby improving the reliability of the HLR. Query efficiency. the

Description of drawings

Fig. 1 is the network connection figure of HLR subscriber data inquiry system in the embodiment of the present invention;

Fig. 2 is the method flowchart of HLR subscriber data inquiry in the embodiment of the present invention;

Fig. 3 is the signal transmission schematic diagram between each network equipment in the HLR user data inquiry process in the embodiment of the present invention;

Fig. 4 is the exit mechanism flow chart in logging in HLR and carrying out user data inquiry process in the embodiment of the present invention;

Fig. 5 is the flowchart of concurrent connection HLR in the embodiment of the present invention;

Fig. 6a and Fig. 6b are device diagrams of the query server in the embodiment of the present invention. the

Detailed ways

In order to improve the efficiency of HLR query, the embodiment of the present invention provides a method for HLR user data query. In the multiple interactions of logging into HLR, an exit mechanism is correspondingly set for possible errors, so that when logging into HLR fails, it can Exit in time, release occupied resources, and no longer affect login again. the

A system provided by an embodiment of the present invention is shown in FIG. 1 . The system mainly includes a query terminal 101 in the customer service network, a WEB server 102 on the firewall at the network management side interface, and a query server 103 in the network management network. the

The WEB server 102 is used to receive the HLR data remote query service request sent by the query terminal 101 and forward it to the query server 103. The WEB server 102 provides the HLR query service in the WEB form. After authenticating the logged-in customer service personnel, it receives the customer service personnel input After the query is completed, the query result returned by the query server is received and displayed to the customer service personnel through the query terminal 101. The connection between the WEB server 102 and the query server 103 can be realized by socket interface. the

Query server 103 is used to receive the HLR data remote query service request forwarded by WEB server 102, according to the user identification information to be queried that is carried in the query service request, establish a connection with the HLR that the user to be queried belongs to and perform user data query, and When connection failure or user data query fails, release the connection with the HLR and return failure indication information to the query terminal 101 by the WEB server 102, after the query is successful, return the query terminal 101 by the WEB server 102 Return query results. After receiving the query service request sent by the WEB server 102, the identification information of the user to be inquired can be identified and judged whether the identification information of the user to be inquired is valid, and then the attribution HLR information of the user to be inquired can be obtained, and then the user to be inquired belongs to The HLR establishes a connection and performs user data query, and can also record the query in a log as required. the

In the process that the inquiry server 103 establishes a connection with the HLR where the user to be inquired belongs to and performs user data inquiry, the inquiry server 103 will release the connection with the HLR and pass through the WEB server when the connection fails to be established or the user data inquiry fails. Return failure indication information to the query terminal, the condition for judging failure can be judging whether the data is received or judging whether the command returned by the HLR contains the specific keyword set, if it is included, it means that the interaction is successful, continue to the next step, If not included, it means that this interaction is unsuccessful, and the connection needs to be exited in time, and the connection with the HLR should be released according to the steps performed. the

Further, the query server 103 can also set up corresponding user identification information queues to be inquired for each HLR according to the receiving order of HLR data remote query service requests. Use multi-thread concurrent login to query the user ID information in the query queue to realize concurrent login of multiple user ID information at the same time. In this way, when multiple customer service personnel query the user ID information belonging to the same HLR at the same time, or when a customer service personnel When querying multiple user identification information belonging to one HLR at the same time, the query can be performed without waiting and retrying. It is also possible to set a maximum concurrency value n, to query the user identification information in n queues concurrently each time, and wait for the information in the queue that is not being queried. the

The query server 103 can also analyze the queried user data, and translate the user data into user data described in natural language that can be easily identified by the customer service personnel, so as to reduce the work difficulty of the customer service personnel and improve the work efficiency of the customer service personnel. the

The inquiry terminal 101 is used for after the customer service personnel remotely log in to the WEB server 102 by the inquiry terminal 101 to input the user identification information to be inquired, generate the HLR data remote inquiry service request carrying the user identification information to be inquired and send it to the WEB server 102, and receive the WEB The query result returned by the server 102. Of course, it is also possible to input directly on the WEB server 102 without querying the terminal 101. The HLR data carrying the user identification information remotely queries the service request and reads the returned query results. the

It is a better mode that the query server 103 is set in the network management network, so that the query terminal 101 to the query server 103 passes through two firewalls, and the security is relatively high. The WEB server 102 can be set at the firewall of the network management network, that is, directly connected to the firewall of the network management network, and adopts the rules of the firewall of the network management network to facilitate management. the

It should be noted that the WEB server 102 and the query server 103 constitute a query subsystem for performing query functions, and the functions of the WEB server 102 and the query server 103 can also be combined and set on one server. the

As shown in Figure 2, HLR user data inquiry method comprises the steps:

Step S201 , the customer service personnel log in to the WEB server 102 at the inquiry terminal 101 at the front desk. When the customer service personnel log in to the WEB server 102 , authentication is required, and they can log in only after passing the identity verification. the

When logging in, you can use the query terminal 101 at the front desk to enter the ip address of the WEB server through the WEB page, open the WEB server page, and then perform authentication and login. You can also use the method of binding the customer service personnel and the query terminal IP at the same time. Personnel can only use their own user names and hosts to log in to the WEB server 102 to inquire, so as to strengthen the security of the system. the

Step S202 , the customer service personnel input the user identification information to be queried at the query terminal 101 through the WEB server 102 , and can input multiple user identification information at one time. the

Step S203, the query server 103 receives the user identification information to be inquired sent by the WEB server 102, the query server 103 queries the HLR to which the input user identification information belongs, and remotely logs in to the HLR, if there is an error or abnormality during login, retry according to the settings or exit. the

When inquiring about the HLR to which the user identification information belongs, the user identification information and the HLR corresponding table are mainly used for querying. A database server 104 is set, and when querying, the query server 103 connects to the database server 104 and queries according to the user data in the data server. the

Step S204, the query server 103 receives the user data returned by the HLR after logging in to the HLR successfully, After receiving the user data, the user data returned by the HLR can be translated into user data described in natural language that can be easily recognized by the front desk customer service personnel, and then displayed to the customer service personnel in the WEB server. The information described in natural language is relative to the original data. In other words, it refers to whether the user has activated roaming, whether to activate international SMS, and similar information. In this way, customer service personnel can intuitively identify user data, and do not need to consult and translate the user data by themselves. Of course, the query server 103 may not translate the returned user data, but directly display it to the customer service personnel. the

The above steps can complete the query of HLR data. the

FIG. 3 is a schematic diagram of signal transmission between various devices during the HLR data query process. Through FIG. 3 , the HLR data query process and the signal transmission during the query process can be clearly seen. the

In step S203, multiple interactions are involved from logging in to the HLR to the successful return of the required user data. In order to prevent problems in the interaction process from failing to log in but not being able to log out in time, each login interaction is performed. Set up, strictly handle possible errors, release the occupied resources when the connection fails, and return failure indication information to the query terminal or release the connection with the HLR when the user data query fails after the connection is established And return failure indication information to the query terminal through the WEB server to ensure that the HLR remote login is normally carried out. the

When requesting to establish a connection, when the connection confirmation signal returned by the HLR is not received within the maximum connection time set, it is determined that the connection has failed. Since certain resources have been occupied when the connection is requested, when the connection fails to be established Resources also need to be released. When querying user data, if the data is not successfully received or the received data does not contain the keyword set in this step, it is determined that the query fails, such as the keyword that prompts for login is not carried when logging in, and the prompt for input is not carried when a password is required The keyword of the password or the need for secondary login, query command or return of the query result without the corresponding prompt can determine the query failure. the

During each login interaction, if the execution command times out due to network problems, you can retry. The maximum number of retries can be set according to your needs. Once the maximum number of retries is exceeded, it will be treated as an interaction failure; if the login is not successful In the event of received data error, incorrect received data or failure to execute the command, exit the socket that initiated the telnet connection; if there is a received data error after successful login Or if the execution of the command fails, send the exit command to log out. At the same time, in order to facilitate the positioning, tracking, analysis and resolution of the problems that occur, each error that occurs can be recorded in the error log in detail. the

The specific steps of querying the server to log in to the HLR and querying user data are shown in Figure 4:

Step S401: Initiate HLR connection. Generally, HLR provides telnet or ssh for remote login. When connecting, connect to HLR through socket. the

Step S402, judging whether the connection is successful, if successful, execute step S403, if not, execute step S419. the

Step S403, receiving returned data. the

Step S404, judging whether data is received, if yes, execute step S405, if not, execute step S420. the

Step S405, use telnet or ssh protocol to analyze the received data, and judge whether the received data contains a keyword prompting login, such as the "login" keyword, if yes, execute step S406, if not, execute step S420. the

Step S406, sending the user name, and receiving the returned data. the

Step S407, judging whether data is received, if yes, execute step S408, if not, execute step S420. the

Step S408, use the telnet or ssh protocol to analyze the received data, and judge whether the received data contains the keyword of the desired password, such as the "password" keyword, if yes, execute step S409, if not, execute step S420. the

Step S409, sending the password, and receiving the returned data. the

Step S410, judging whether data is received, if yes, execute step S411, if not, execute step S420. the

Step S411, use telnet or ssh protocol to analyze the received data, and judge whether the received data contains the prompt returned by the HLR, such as the ">" keyword, if yes, execute step S412, if not, execute step S420.

Step S412, sending a secondary login command, and receiving returned data. the

Step S413, judging whether data is received, if yes, execute step S414, if not, execute step S421. the

Step S414, use telnet or ssh protocol to analyze the received data, and judge whether the received data contains the prompt returned by HLR, such as the "<" keyword, if yes, execute step S415, if not, execute step S421. the

Step S415 , sending a query command, sending different query commands according to different HLRs, one or more, and receiving the returned data. the

Step S416, judging whether data is received, if yes, execute step S417, if not, execute step S422. the

Step S417, use telnet or ssh protocol to parse the received data, and judge whether the received data contains the prompt returned by HLR, such as the "<" keyword, if yes, execute step S418, if not, execute step S422. the

Step S418, if the query is successful, send an exit command to log out of the second-level login, and then send an exit command to log out of the first-level login and exit the socket. At the same time, you can also query the start and end time of this query, query customer service personnel, query terminal IP, user The identification information is recorded in the log in detail for future statistics and analysis. the

Step S419, prompting that the connection to the HLR fails, releasing the resources occupied during the connection, and performing step S423. the

Step S420: Prompt that the login to the HLR fails, exit the socket, and execute step S423. the

Step S421 , prompting that the login to the HLR fails, sending an exit command, exiting the first-level login, and exiting the socket. the

Step S422, prompting that the execution of the command fails, sending an exit command to exit the second-level login, and sending an exit command again to exit the first-level login and exit the socket. the

Step S423, record the failure data of login and query HLR into the log, so as to locate, track, analyze and solve the problem, the recorded data can include the time of login and query, error steps, login user identification information, Operating customer service personnel, etc. Since the error steps are recorded in detail, the location of the fault can be located more precisely, which is convenient for problem analysis and solution.

Of course, for different HLRs, the login process is also different. Some HLRs do not need to perform secondary login, so there is no need to make judgments about secondary login interactions. Some HLRs require the user to log in when initiating a connection Username and password are sent to the past to log in directly, so that there is no need to make interactive judgments about user name and password, and it is enough to directly judge whether the first-level login is successful. The login process can be set according to different HLRs. the

In step S202, the customer service personnel input the user identification information to be inquired through the WEB server, and can input a plurality of user identification information at one time. At this time, a queue of corresponding user identification information to be inquired can be set up for each HLR, which will belong to the same HLR The user identification information to be queried is put into the corresponding queue, and then the query is performed sequentially, or concurrently. For example, there are 500 user identification information input by the customer service personnel to be queried at the same time, and the 500 user identification information may be different. The customer service personnel input it at a close time, or one customer service personnel needs to query multiple user identification information. Assuming that 20 user identification information among the 500 user identification information belong to the same HLR, then put these 20 HLR Enter a queue, query sequentially or use multi-threading to achieve concurrent query, in order to prevent customer service personnel from waiting too long, the queue length threshold can be set, generally set according to the waiting time acceptable to customer service personnel, if the queue is already If it is full, the corresponding reminder will be given to the customer service personnel, and the user identification information will not be put into the queue any more. the

During concurrent query, the queue length threshold of concurrent query can be set according to the load capacity of HLR, subject to not affecting the communication network, the queue length threshold of concurrent query can be set to a fixed value, for example: set to 300, Then when the user identification information logged into this HLR is within 300, if the user identification information has been added in the queue, the connection of the user identification information can be initiated to perform concurrent queries. If the user identification information logged into the HLR reaches 300, no more Put the new user ID information into the queue, and prompt the customer service personnel that the queue is full. The queue length threshold can also be dynamically adjusted according to the load capacity of the HLR. If the HLR load is heavy for a certain period of time, the queue length threshold will be reduced accordingly. On the contrary, if the HLR is relatively idle for a certain period of time, the queue length threshold will be increased accordingly. limit. You can also adjust the queue length threshold based on empirical data. The main adjustment is based on the experience value of holidays and normal times, and the experience value of each time period of the day. Then, during this period of time, reduce the threshold value of the queue length correspondingly, and increase the threshold value of the queue length correspondingly after 12:00 p.m. Reduce the threshold value of queue length correspondingly at time, and increase the threshold value of queue length correspondingly according to empirical data after 2 o'clock in the evening. the

As shown in Figure 5, the steps for user identification information to enter the queue for concurrent query include:

Step S501, the customer service personnel input the user identification information to be queried through the WEB server 102, and can input multiple user identification information at a time. the

Step S502, the query server 103 receives the user identification information to be inquired from the WEB server, and judges whether these user identification information meet the requirements, mainly according to the conditions such as the length of the user identification information, the beginning number, etc., if it meets the requirements, execute step S504, if not If the requirements are met, go to step S503. the

Step S503, prompting the customer service personnel that the input user identification information is incorrect. the

Step S504, querying the HLR that belongs to the user identification information through the pre-stored correspondence table between the user identification information segment and the HLR. the

Step S505, obtaining the current number of connections of the HLR belonging to the queried user identification information, and calculating the maximum number of connections allowed by the HLR according to the current load of the HLR. the

Step S506. According to the maximum number of connections allowed by the HLR and the obtained current number of connections, it is judged whether the queue is full. If the queue is full, execute step S508. If the queue is not full, execute step S507. the

Step S507, put the user identification information to be queried carried in the HLR data remote query service request into the queue of the corresponding HLR according to the request sequence, initiate HLR connection, and perform concurrent query. the

Step S508, prompting the customer service personnel that the number of connections to the HLR to which the user identification information belongs is too large, please try again later. the

It is also possible to set up a cache. When the queue is full, the user identification information that cannot enter the queue is temporarily put into the cache. Once there is a free position in the queue, the user identification information in the cache is automatically entered into the queue, which can be further simplified. The operation of customer service personnel, of course, can also set a cached The maximum number, when the maximum number is reached, the user identification information will no longer be stored in the cache, and corresponding prompts will be given to the customer service personnel to reduce the waiting time of the customer service personnel. the

As shown in Figure 6a, the query server 103 in the embodiment of the present invention includes the following units:

The identifying unit 601 is configured to identify the user identification information, and after confirming that the user identification information is valid, query the HLR that the user identification information belongs to, and obtain the configuration information of the HLR. the

The login unit 602 is used to establish a connection with the HLR where the user to be inquired belongs to according to the configuration information of the HLR and inquire about the user data corresponding to the user identification information in the HLR, and when the connection fails to be established or the user data query fails, the connection with the HLR is released. and send failure indication information to the WEB server. After the query is successful, send the query result to the WEB server, and then log out of the HLR. the

Further, as shown in Figure 6b, in order to realize concurrent login of several user identification information belonging to one HLR, the query server 103 also includes:

Scheduling unit 603, for scheduling the process of concurrent inquiry, inquire about the current connection number of the HLR to which the user identification information belongs, and when the current connection number does not reach the maximum connection number set for it, put the user identification information into In the queue, when the current number of connections reaches the maximum number of connections set for it, the customer service personnel will be prompted that there are too many connections, and the query will be performed later. the

At this time, the login unit 602 performs concurrent login on the user identification information in the queue, and the concurrent login can be realized by using multiple threads. the

Furthermore, for the convenience of customer service personnel and simplified operation, a cache unit 604 can also be set in the query server 103 to temporarily store the user identification information that the scheduling unit 603 does not put into the queue. Once there is a vacant position in the queue, the scheduling unit 603 immediately and automatically read the user identification information stored in the storage unit and put it into the queue. the

More preferably, in order to facilitate customer service personnel to identify the information carried in the returned data and improve work efficiency, the query server 103 also includes:

The parsing unit 605 is configured to parse the user data acquired by the login unit 602, and translate the user data into user data described in natural language that is easy for customer service personnel to identify, such as whether the user has activated roaming or not.

The embodiment of the present invention provides the method, system and device for HLR user data query, and in the multiple interactions involved in the process of logging into the HLR, corresponding settings have been made for possible errors, so that when the login to the HLR fails, it can be timely Logout will no longer affect login again, which improves the efficiency of HLR query. the

Apparently, those skilled in the art can make various changes and modifications to the embodiments of the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies thereof, the present invention also intends to include these modifications and variations.

Claims (18)

1. an attaching position register HLR user data query system comprises at least one HLR, it is characterized in that, also comprises:

Inquiry terminal; Be used to receive user totem information to be checked; Generate HLR remote data query service request and transmission, carry user totem information to be checked in the said remote inquiry services request, and the Query Result that reception is returned according to HLR remote data query service request also shows;

The inquiry subsystem; Be used to receive the HLR remote data query service request that said inquiry terminal sends; According to the user totem information to be checked that carries in the said remote inquiry services request, connect with the HLR of user attaching to be checked and carry out the user data query and the resource of release busy when connecting failure; And return the failure indication information or connecting back user data query when failure to said inquiry terminal; Discharge with HLR between be connected and return the failure indication information to said inquiry terminal, after successful inquiring, return Query Result to said inquiry terminal.

2. the system of claim 1 is characterized in that, said inquiry subsystem specifically comprises:

The WEB server is used to receive HLR remote data query service request and the forwarding that said inquiry terminal sends;

Querying server; Be used to receive the HLR remote data query service request of said WEB server forwards; According to the user totem information to be checked that carries in the said remote inquiry services request; Connect with the HLR of user attaching to be checked and carry out user data query, and when connecting the failure of failure or user data query, discharge with HLR between be connected and return the failure indication information to inquiry terminal through said WEB server; After successful inquiring, return Query Result to inquiry terminal through said WEB server.

3. system as claimed in claim 2 is characterized in that, said querying server also is used for the user data that inquires is translated into the information of using natural language description, and the information after will translating returns to inquiry terminal as Query Result.

4. like claim 2 or 3 described systems; It is characterized in that; Said querying server also is used for the reception order according to said HLR remote data query service request, for each HLR sets up corresponding user totem information formation to be checked, and according to the user totem information to be checked in the user totem information formation to be checked; Carry out user data query to HLR successively, perhaps initiate parallel query to HLR.

5. system as claimed in claim 4; It is characterized in that; Said querying server also is used for according to user totem information queue length threshold value to be checked; When the user totem information corresponding queues to be checked of carrying in the remote inquiry services request that receives expires, return to inquiry terminal through said WEB server and to inquire about information after a while.

6. system as claimed in claim 4 is characterized in that, it is fixed value that said querying server also is used to set the corresponding user totem information queue length threshold value to be checked of this HLR, or

Rule of thumb data are confirmed the user totem information queue length threshold value to be checked that this HLR is corresponding by the time.

7. system as claimed in claim 2 is characterized in that, said querying server is arranged in the webmaster net, and said WEB server is arranged on the fire compartment wall place of webmaster net.

8. a querying server is characterized in that, comprising:

Recognition unit is used for receiving HLR remote data query service request from the WEB server, and discerns user's to be checked ownership HLR according to the user totem information to be checked that carries in the said remote inquiry services request;

Log-in unit; Being used for HLR with user attaching to be checked connects and carries out user data query; And when connecting the failure of failure or user data query; Discharge with HLR between be connected and send the failure indication information to the WEB server, after successful inquiring, send Query Result to the WEB server.

9. querying server as claimed in claim 8 is characterized in that, also comprises:

Scheduling unit; Be used for reception order according to said HLR remote data query service request; For each HLR sets up corresponding user totem information formation to be checked; And user totem information to be checked put into user totem information formation to be checked, and login user totem information corresponding user data in HLR in the HLR query request successively by log-in unit, perhaps parallelly sign in to behind the HLR each user totem information corresponding user data in HLR in the concurrent query request.

10. querying server as claimed in claim 9; It is characterized in that; Said scheduling unit also is used for according to user totem information queue length threshold value to be checked; When the user totem information corresponding queues to be checked of carrying in the remote inquiry services request that receives expires, return to inquiry terminal through said WEB server and to inquire about information after a while.

11. querying server as claimed in claim 10 is characterized in that, said scheduling unit also is used for rule of thumb data and confirms user totem information queue length threshold value to be checked by the time.

12. like the arbitrary described querying server of claim 8 to 11, it is characterized in that, also comprise:

Resolution unit be used for the user data information that said log-in unit gets access to is translated into the information of natural language description, and the information after will translating is sent as Query Result.

13. a HLR user data query method is characterized in that, comprising:

Receive the HLR remote data query service request that inquiry terminal is transmitted, carry user totem information to be checked in the said remote inquiry services request;

According to the user totem information to be checked that carries in the said remote inquiry services request, connect with the HLR of user attaching to be checked and carry out user data query; And

Connecting failure or user data query when failure, discharge with HLR between be connected and return the failure indication information to said inquiry terminal, after successful inquiring, return Query Result to said inquiry terminal.

14. method as claimed in claim 13 is characterized in that, also comprises:

Reception order according to said HLR remote data query service request; For each HLR sets up corresponding user totem information formation to be checked; And after receiving HLR remote data query service request, the user totem information to be checked that wherein carries is put into corresponding queues; And

The described user data query of carrying out specifically comprises: according to the user totem information to be checked in the user totem information formation to be checked, successively or parallel carry out user data query to HLR.

15. method as claimed in claim 14; It is characterized in that; Said user totem information to be checked is put into before the corresponding formation, earlier according to the queue length threshold value of the corresponding HLR of user totem information to be checked institute, when user totem information formation to be checked completely the time; Return and inquire about information after a while, otherwise user totem information to be checked is put into corresponding formation.

16. method as claimed in claim 15 is characterized in that, said user totem information queue length threshold value to be checked is a fixed value, or rule of thumb data were confirmed by the time.

17. method as claimed in claim 13 is characterized in that, after the said successful inquiring, earlier the user data that inquires is translated into the information of using natural language description, the information after will translating is again returned as Query Result.

18., it is characterized in that the said definite method that connects failure or user data query failure specifically comprises like the arbitrary described method of claim 13 to 17:

When request connects, when not receiving the connection confirmation signal that HLR returns in the longest connect hours that is provided with, the failure of confirming to connect;

When user data query, when the data that successfully do not receive data or reception do not comprise this step and set the keyword that carries, confirm the inquiry failure.

Images