CN101730069B - Method, system and device for querying HLR user data - Google Patents
Method, system and device for querying HLR user data Download PDFInfo
- Publication number
- CN101730069B CN101730069B CN2008102256233A CN200810225623A CN101730069B CN 101730069 B CN101730069 B CN 101730069B CN 2008102256233 A CN2008102256233 A CN 2008102256233A CN 200810225623 A CN200810225623 A CN 200810225623A CN 101730069 B CN101730069 B CN 101730069B
- Authority
- CN
- China
- Prior art keywords
- hlr
- checked
- user
- totem information
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
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
Technical field
The present invention relates to mobile communication technology, relate in particular to the mthods, systems and devices of a kind of HLR in the mobile communication technology (HomeLocation Register, attaching position register) user data query.
Background technology
In the customer complaint of operator; Great majority are complaints of network problem; For this complaint, the contact staff at first will inquire about the user data among the HLR according to user totem information, at first to judge whether existing user data that wrong situation is set; Therefore, the contact staff will carry out a large amount of HLR user data query every day.
But because the restriction of technical conditions and network, the contact staff can not directly login HLR and carry out the inquiry of user data in customer service system, but inquires about through a remote login tools; And this inquiry mode is not supported concurrent inquiry, promptly when a HLR is in logging status, does not allow this HLR to login once more; And do not have fault processing mechanism, when causing logining the HLR failure owing to odjective cause like this, can not in time withdraw from; And can not use this HLR to login once more; Like this, contact staff's work is just caused very big inconvenience, reduced the efficient of HLR user data query.
Summary of the invention
The embodiment of the invention provides a kind of mthods, systems and devices of HLR user data query, to improve the HLR search efficiency.
A kind of HLR user data query system comprises at least one HLR, 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,, connect with the HLR of user attaching to be checked and carry out user data query according to the user totem information to be checked that carries in the said remote inquiry services request; And when connecting the failure of failure or user data query; 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.
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.
Further, 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.
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.
Further; 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.
Further, 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.
Better, said querying server is arranged in the webmaster net, and said WEB server is arranged on the fire compartment wall place of webmaster net.
A kind of querying server comprises:
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.
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.
Further; 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.
Further, 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.
Also comprise in the querying server:
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.
A kind of HLR user data query method comprises:
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.
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.
Further; Said user totem information to be checked is put into before the corresponding formation; Earlier according to user totem information to be checked the queue length threshold value of corresponding HLR; When user totem information formation to be checked is expired, return and inquire about information after a while, otherwise user totem information to be checked is put into corresponding formation.
Further, 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.
Better, 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.
The said definite method that connects failure or user data query failure specifically comprises:
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.
The embodiment of the invention is through the mthods, systems and devices of the HLR user data query that provides; In login HLR process or query script; Can when login HLR failure or inquiry failure, in time withdraw from HLR, no longer influence login once more, improve the search efficiency of HLR.
Description of drawings
Fig. 1 is the network connection layout of HLR user data query system in the embodiment of the invention;
Fig. 2 is the method flow diagram of HLR user data query in the embodiment of the invention;
Fig. 3 is the signal of each a LA Management Room transmission sketch map in the HLR user data query process in the embodiment of the invention;
Fig. 4 is for login HLR in the embodiment of the invention and carry out the escape mechanism flow chart in the user data query process;
Fig. 5 is the flow chart of concurrent connection HLR in the embodiment of the invention;
Fig. 6 a and Fig. 6 b are the installation drawing of querying server in the embodiment of the invention.
Embodiment
The embodiment of the invention is for improving the efficient of HLR inquiry; A kind of method of HLR user data query is provided; In login HLR repeatedly mutual, for the mistake that possibly occur all relative set escape mechanism, make and when login HLR failure, can in time withdraw from; The resource of release busy, no longer influence login once more.
A kind of system that the embodiment of the invention provides is as shown in Figure 1, mainly is included in the inquiry terminal 101 in the customer service network in the system, the querying server 103 in the WEB server 102 on the webmaster side interface fire compartment wall, webmaster net.
WEB server 102 is used to receive the HLR remote data query service request of inquiry terminal 101 transmissions and be transmitted to querying server 103, and WEB server 102 provides the HLR inquiry service of WEB form; To the login the contact staff carry out authentication after; Receive the user totem information of contact staff's input, and send to querying server 103, after inquiry finishes; Receive the Query Result that querying server returns, and be shown to the contact staff through inquiry terminal 101.WEB server 102 is realized with using the socket interface being connected of querying server 103.
Querying server 103; Be used to receive the HLR remote data query service request that WEB server 102 is transmitted; According to the user totem information to be checked that carries in the query service 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 101 through WEB server 102; After successful inquiring, return Query Result to inquiry terminal 101 through said WEB server 102.After the query service request that receives 102 transmissions of WEB server; Can treat the inquiring user identification information earlier discerns and judges whether this user totem information to be checked is effective; Obtain this user's to be checked ownership HLR information again; Connect with the HLR of user attaching to be checked then and carry out user data query, the record that also can carry out daily record as required to request for information.
Connect and carry out in the process of user data query at the HLR of querying server 103 and user attaching to be checked, querying server 103 can be 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; The condition of judging failure can be to judge whether to receive data or judge the special key words that whether comprises setting in the HLR institute return command; If comprise, this interaction success then is described, proceed next step; If do not comprise; Then explanation is this time mutual unsuccessful, need in time withdraw from connection, according to the step that is proceeded to discharge with HLR between be connected.
Further; Querying server 103 can also be that each HLR sets up corresponding user totem information formation to be checked according to the reception of HLR remote data query service request in proper order, set up formation after, can login inquiry successively according to the user totem information in the formation; Also can utilize the user totem information in the multi-thread concurrent login query request; Realize the concurrent login at one time of a plurality of user totem informations, like this, when a plurality of contact staff inquire about the user totem information that belongs to a HLR simultaneously; Or when a contact staff inquires about a plurality of user totem information that belongs to a HLR simultaneously, need not wait for retry and can inquire about.A concurrent value n of maximum can also be set, the user totem information in n formation of each concurrent inquiry, the not wait of the information in inquiry in the formation.
Querying server 103 can also be resolved the user data that inquires, and user data is translated into the user data of the use natural language description of being convenient to contact staff identification, to reduce contact staff's work difficulty, improves contact staff's operating efficiency.
Inquiry terminal 101; Be used for the contact staff is remotely logged into WEB server 102 inputs user totem information to be checked through inquiry terminal 101 after; The HLR remote data query service request that user totem information to be checked is carried in generation sends to WEB server 102, and receives the Query Result that WEB server 102 returns.Certainly, yet can directly on WEB server 102, not import the HLR remote data query service request of carrying user totem information and read the Query Result that returns through inquiry terminal 101.
It is a kind of preferable mode that querying server 103 is arranged in the webmaster net, 103 has passed through the twice fire compartment wall altogether from inquiry terminal 101 to querying server like this, and fail safe is higher.WEB server 102 can be arranged on the fire compartment wall place of webmaster net, promptly directly is connected on the fire compartment wall of webmaster net, adopts the rule of webmaster net fire compartment wall, is convenient to management.
Need to prove that WEB server 102 has been formed the inquiry subsystem of carrying out query function with querying server 103, the function of WEB server 102 and querying server 103 also can merge and is arranged on the server.
As shown in Figure 2, HLR user data query method comprises the steps:
Step S201, contact staff login WEB servers 102 at the inquiry terminal 101 on foreground, will carry out authentication when the contact staff logins WEB server 102, can login after authentication is passed through.
Can be employed in the ip address of foreground queries terminal 101 during login through WEB page input WEB server; Open the WEB server page; Carry out the mode of authentication login then; The mode that can also adopt contact staff and inquiry terminal IP to bind simultaneously, each contact staff can only use user name of oneself and main frame login WEB server 102 to inquire about, with the fail safe of strengthening system.
Step S202, contact staff through WEB server 102 inputs user totem information to be checked, can once import a plurality of user totem informations at inquiry terminal 101.
Step S203, querying server 103 receive the user totem information to be checked that WEB server 102 sends; The HLR that the querying server 103 inquiry institute user totem information of importing belongs to; And this HLR of Telnet, wrong or unusual during login as if occurring, according to retry being set or withdrawing from.
During the HLR of inquiring user identification information ownership; Main user totem information and the inquiry of HLR correspondence table according to storage in advance; User totem information is mainly Subscriber Number, and the correspondence table of user totem information and HLR can be stored in querying server this locality, also can a database server 104 be set for it; During inquiry, querying server 103 connects database servers 104 and according to the user data query in the data server.
Step S204, querying server 103 login HLR success backs receive the user data that HLR returns; After receiving user data; Can with the user data that HLR returns translate into the foreground contact staff easily the user data of the use natural language description of identification be shown to the contact staff in the WEB server again; The information of using natural language description is meant whether this user opens roaming, whether opens similar information such as international note, like this for initial data; The contact staff can discern user data intuitively, does not need oneself to carry out corresponding consulting and translate in the face of user data.Certainly, querying server 103 can not translated the user data that returns yet, and directly is shown to the contact staff.
Above step can be accomplished the inquiry of HLR data.
Fig. 3 is the signal transmission sketch map of each equipment room in the query script of HLR data, can be clearly seen that the transmission of signal in query script and the query script of HLR data through Fig. 3.
In step S203; HLR successfully returns to needed user data from login, relate to repeatedly alternately, is the situation that prevents to go wrong in the reciprocal process and cause login failure but can not in time withdraw from; When each login is mutual, all be provided with; The mistake that possibly occur is carried out strictness handle, the resource of release busy when connecting failure, and return the failure indication information or when connecting back user data query failure to said inquiry terminal; Discharge with HLR between be connected and return the failure indication information to inquiry terminal through said WEB server, guarantee that the HLR Telnet normally carries out.
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 is owing to when request connects; Taken certain resource, so when connecting failure, also need discharge resource.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; As do not carry when logining the prompting login keyword, do not carry the keyword of prompting input password when needing password or do not carry corresponding prompt when needing secondary login, query statement or returning Query Result, all can confirm the inquiry failure.
When each login was mutual, if because of network problem causes executing instruction overtime, then can carry out retry, the high reps of retry can be formulated as required, in case surpass high reps, then handled according to mutual failure; If error in data when login is not successful, occurs receiving, receive the situation that data are incorrect or execution command is failed, withdraw from and initiate the socket that telnet connects; If the situation of the failure of executing instruction the reception error in data appears or in the back logining successfully, send the exit instruction, log off.Simultaneously, for ease the problem that occurs is positioned, follows the trail of, analyzes and solves, can with the mistake that at every turn occurs all detail record in error log.
The concrete steps of querying server login HLR and inquiring user data are as shown in Figure 4:
Step S401, initiation HLR connect, and general HLR provides the mode of telnet or ssh to supply Telnet to use, and during connection, is connected on the HLR through the socket mode.
Whether step S402, judgement connect successful, if success, execution in step S403, as if unsuccessful, execution in step S419.
The data that step S403, reception are returned.
Step S404, judge whether to receive data, if, execution in step S405, if not, execution in step S420.
Step S405, the data of using telnet or ssh protocol analysis to receive are judged the keyword that whether comprises the prompting login in the data of receiving, like " login " keyword, if, execution in step S406, if not, execution in step S420.
Step S406, transmission user name receive the data of returning.
Step S407, judge whether to receive data, if, execution in step S408, if not, execution in step S420.
Step S408, the data of using telnet or ssh protocol analysis to receive are judged the keyword that whether comprises the password of wanting in the data of receiving, like " password " keyword, if, execution in step S409, if not, execution in step S420.
Step S409, transmission password receive the data of returning.
Step S410, judge whether to receive data, if, execution in step S411, if not, execution in step S420.
Step S411, the data of using telnet or ssh protocol analysis to receive judge in the data of receiving whether comprise the prompt that HLR returns, like ">" keyword, if, execution in step S412, if not, execution in step S420.
Step S412, transmission secondary login instruction receive the data of returning.
Step S413, judge whether to receive data, if, execution in step S414, if not, execution in step S421.
Step S414, the data of using telnet or ssh protocol analysis to receive judge in the data of receiving whether comprise the prompt that HLR returns, as " < " keyword, if, execution in step S415, if not, execution in step S421.
Step S415, transmission query statement send different query statements according to the difference of HLR, can be one, also can be many, receive the data of returning.
Step S416, judge whether to receive data, if, execution in step S417, if not, execution in step S422.
Step S417, the data of using telnet or ssh protocol analysis to receive judge in the data of receiving whether comprise the prompt that HLR returns, as " < " keyword, if, execution in step S418, if not, execution in step S422.
Step S418, successful inquiring are sent the exit instruction, withdraw from the secondary login; The exit that redispatches instruction; Withdraw from one-level login, withdraw from socket, the time that can also this inquiry begun and finish simultaneously, inquire about the contact staff; Inquiry terminal IP, user totem information all detail record in daily record, so that statistics and analysis in the future.
Step S419, prompting connect the HLR failure, discharge the resource that takies when connecting, execution in step S423.
Step S420, prompting login HLR failure are withdrawed from socket, execution in step S423.
The exit instruction is sent in step S421, prompting login HLR failure, withdraws from the one-level login, withdraws from socket.
Step S422, hint instructions are carried out failure, send the exit instruction, withdraw from the secondary login, and the one-level login is withdrawed from the exit that redispatches instruction, withdraws from socket.
Step S423, will login data logging with inquiry HLR failure in daily record; So that the location of problem, tracking, analysis and solution, the data of record can comprise the contact staff of the time of login and inquiry, the user totem information that wrong step, login occur, operation etc.Since detail record and wrong step appears, location of fault appears so can locate more accurately, be convenient to the analysis and the solution of problem.
Certainly, for different HLR, the process of login is also different; The HLR that has need not carry out the secondary login; So just need not carry out the mutual judgement of relevant secondary login, the HLR that has just requires that when initiating to connect username and password is sent the past and directly logins, and so just need not carry out the mutual judgement of relevant username and password; Judge directly whether the one-level login successfully gets final product, and the process of login can be carried out relative set according to the difference of HLR.
In step S202, the contact staff can once import a plurality of user totem informations through WEB server input user totem information to be checked; At this moment, can be each HLR and set up corresponding user totem information formation to be checked, the user totem information to be checked that belongs to a HLR is put into corresponding queues; Inquire about successively again, or carry out concurrent inquiry, for example; 500 user totem informations that have the contact staff to import simultaneously need be inquired about, and these 500 user totem informations possibly be that different contact staff imported in the approaching time, also possibly be that a contact staff need inquire about a plurality of user totem informations; Supposing has 20 user totem informations to belong to same HLR in these 500 user totem informations, so these 20 HLR is put into a formation, inquires about successively or utilizes multithreading to realize concurrent inquiry; Be the overlong time that prevents that the contact staff from waiting for; The queue length threshold value can be provided with, and generally is provided with the receptible stand-by period according to the contact staff, if formation is full; Then give contact staff's corresponding prompt, no longer user totem information is put into formation.
During concurrent inquiry, the queue length threshold value of concurrent inquiry can be provided with according to the load-bearing capacity of HLR, is as the criterion not influence communication network; The queue length threshold value of concurrent inquiry can be arranged to a fixed value, and for example: be set to 300, the user totem information of then logining this HLR is in 300 the time; If increased user totem information in the formation; Then can initiate the connection of this user totem information, carry out concurrent inquiry, if the user totem information of this HLR of login reaches 300; Then no longer new user totem information is put into formation, and prompting contact staff formation is full.The queue length threshold value can also dynamically be adjusted according to the load-bearing capacity of HLR, if certain section time HLR load is bigger, and then corresponding reduction queue length threshold value, otherwise, if certain section time HLR is relatively more idle, then corresponding increase queue length threshold value.Rule of thumb data are adjusted the queue length threshold value; Main adjustment is according to being festivals or holidays and the empirical value of at ordinary times empirical value, every day day part, for example: if empirical data shows that be the conversation peak 6 o'clock to 12 o'clock evening at ordinary times; So; During this period of time corresponding reduction queue length threshold value, 12 the corresponding increase queue length threshold of data values rule of thumb more later at night, and 6 o'clock to 2 o'clock evening of festivals or holidays is the conversation peak; So in the corresponding during this period of time reduction queue length threshold values of festivals or holidays, 2 the corresponding increase queue length threshold of data values rule of thumb more later at night.
As shown in Figure 5, the step that concurrent inquiry is carried out in user totem information entering formation comprises:
Step S501, contact staff once can import a plurality of user totem informations through WEB server 102 inputs user totem information to be checked.
Step S502, querying server 103 receive the user totem information to be checked that the WEB server sends; Judge whether these user totem informations meet the requirements; Mainly judge according to conditions such as user totem information length, beginning numerals, if meet the requirements, execution in step S504; If undesirable, execution in step S503.
Step S503, to import user totem information wrong for the prompting contact staff.
Step S504, the user totem information section of passing through storage in advance and the ownership HLR of HLR mapping table inquiring user identification information.
Step S505, the user totem information that obtains to inquire belong to the current linking number of HLR, and calculate the maximum number that HLR allows connection according to the current load of HLR.
Step S506, the maximum number that allows to connect according to this HLR and the current linking number of acquisition judge whether formation is full, if formation is full, execution in step S508 then is if formation is less than, execution in step S507 then.
Step S507, with the sequencing formation of putting into corresponding HLR of the user totem information to be checked that carries in the HLR remote data query service request by request, initiate HLR and connect, carry out concurrent inquiry.
The linking number of HLR is too much under step S508, this user totem information of prompting contact staff, please tries after a while again.
A buffer memory can also be set, and when formation was expired, the user totem information that can not get into formation was temporarily put into buffer memory; In case occur clear position in the formation, then make the user totem information in the buffer memory get into formation automatically, can further simplify contact staff's operation like this; Certainly, the maximum quantity of a buffer memory also can be set, when reaching maximum quantity; No longer deposit user totem information in buffer memory, give contact staff's corresponding prompt simultaneously, to reduce contact staff's stand-by period.
Shown in Fig. 6 a, querying server 103 comprises like lower unit in the embodiment of the invention:
Log-in unit 602; Be used for that HLR according to the configuration information of this HLR and user attaching to be checked connects and the inquiring user identification information in the HLR corresponding user data; And connecting failure or user data query when failure, 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, withdraw from the HLR login again.
Further, shown in Fig. 6 b, in order to realize several concurrent logins of user totem information that belong to a HLR, this querying server 103 also comprises:
At this moment, the user totem information in 602 pairs of formations of log-in unit carries out concurrent login, and concurrent login can realize with multithreading.
Further; For making things convenient for the contact staff; Simplify the operation, also a buffer unit 604 can be set in querying server 103, be used for temporary transient memory scheduling unit 603 and do not put into the user totem information of formation; In case occur vacant position in the formation, the user totem information of storing in the automatic immediately reading cells of scheduling unit 603 also puts it in the formation.
Better, for entrained information in the data that make things convenient for the contact staff to discern to return, to increase work efficiency, this querying server 103 also comprises:
The embodiment of the invention is through the mthods, systems and devices of the HLR user data query that provides; In login HLR process, relate to repeatedly mutual in; All carried out corresponding setting for the mistake that possibly occur; Make and when login HLR failure, can in time withdraw from that no longer influence login has once more improved the efficient of HLR inquiry.
Obviously, those skilled in the art can carry out various changes and modification to the embodiment of the invention and not break away from the spirit and scope of the present invention.Like this, belong within the scope of claim of the present invention and equivalent technologies thereof if of the present invention these are revised with modification, then the present invention also is intended to comprise these changes and modification interior.
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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102256233A CN101730069B (en) | 2008-10-31 | 2008-10-31 | Method, system and device for querying HLR user data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102256233A CN101730069B (en) | 2008-10-31 | 2008-10-31 | Method, system and device for querying HLR user data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101730069A CN101730069A (en) | 2010-06-09 |
| CN101730069B true CN101730069B (en) | 2012-06-27 |
Family
ID=42450096
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008102256233A Active CN101730069B (en) | 2008-10-31 | 2008-10-31 | Method, system and device for querying HLR user data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101730069B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104125254B (en) * | 2013-04-27 | 2017-10-13 | 博雅网络游戏开发（深圳）有限公司 | Obtain the method and system of platform user data |
| CN106326296A (en) * | 2015-07-01 | 2017-01-11 | 中兴通讯股份有限公司 | Data query method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1164773A2 (en) * | 2000-06-14 | 2001-12-19 | Fujitsu Limited | Service providing apparatus and method, and service verifying apparatus using information terminal |
| CN1487705A (en) * | 2002-09-30 | 2004-04-07 | ��Ϊ��������˾ | Active user's off-line processing method while intercommunicating radio LAN and mobile communication system |
| CN101267652A (en) * | 2007-03-13 | 2008-09-17 | 中兴通讯股份有限公司 | Method for canceling continuous switch from TDCDMA to other networks in HLR amalgamation mode |
-
2008
- 2008-10-31 CN CN2008102256233A patent/CN101730069B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1164773A2 (en) * | 2000-06-14 | 2001-12-19 | Fujitsu Limited | Service providing apparatus and method, and service verifying apparatus using information terminal |
| CN1487705A (en) * | 2002-09-30 | 2004-04-07 | ��Ϊ��������˾ | Active user's off-line processing method while intercommunicating radio LAN and mobile communication system |
| CN101267652A (en) * | 2007-03-13 | 2008-09-17 | 中兴通讯股份有限公司 | Method for canceling continuous switch from TDCDMA to other networks in HLR amalgamation mode |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101730069A (en) | 2010-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106506433B (en) | Login authentication method, authentication server, authentication client and login client | |
| CN101742004A (en) | Call transfer method and device in multi-call central system | |
| CN100589644C (en) | Calling process system and method thereof | |
| CN102281364A (en) | Call center system and method for accessing call center system | |
| CN104079711A (en) | Calling method based on speech recognition | |
| EP2439881B1 (en) | Cluster system and request message distribution method for processing multi-node transaction | |
| CN101420681B (en) | Method and apparatus for processing multi-channel request subscription under service management platform | |
| CN101730069B (en) | Method, system and device for querying HLR user data | |
| CN103813036B (en) | Communication connection allocation method and system thereof | |
| CN102437921A (en) | Memory method and network device of configuration information | |
| CN102025512B (en) | Service operation support system, service fulfillment method and device | |
| CN101677413A (en) | Method and apparatus for provisioning a communication device automatically | |
| CN102801877B (en) | Interactive voice response (IVR)-free virtual switchboard service method and system | |
| KR20100074896A (en) | System and mathod for emoticon transmission | |
| CN109445950A (en) | The mutual exclusion access method and system of OCF resource, server-side, medium, equipment | |
| CN101635774B (en) | CTIEX, system and method for realizing transmission of channel associated data of seat and automatic service | |
| KR20140060637A (en) | Method, system and apparatus for balancing load | |
| CN111132045A (en) | Method and entity for determining sequence of sequence-ringing service call | |
| EP2432206A1 (en) | Method and device for triggering nested service | |
| CN113891263B (en) | Short message service system and synchronous sending method and asynchronous sending method thereof | |
| KR102021792B1 (en) | Wireless Terminal and Recording Medium | |
| JP4852128B2 (en) | Message transmission system and message transmission method | |
| CN101917436A (en) | Method for realizing inter-dialing of group data storage in IMS network, server and system | |
| CN1866874A (en) | Terminal device maintaining method and system | |
| CN102740168A (en) | Method and system for realizing call, office system and enterprise switchboard system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |