CN101883332A - Method, system and device for realizing call back requesting business in trunking communication system - Google Patents
Method, system and device for realizing call back requesting business in trunking communication system Download PDFInfo
- Publication number
- CN101883332A CN101883332A CN2009101390418A CN200910139041A CN101883332A CN 101883332 A CN101883332 A CN 101883332A CN 2009101390418 A CN2009101390418 A CN 2009101390418A CN 200910139041 A CN200910139041 A CN 200910139041A CN 101883332 A CN101883332 A CN 101883332A
- Authority
- CN
- China
- Prior art keywords
- callback
- message
- dispatch server
- recipient
- trunking dispatch
- 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.)
- Granted
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a method for realizing a call back requesting business in a trunking communication system. A trunking dispatch server sends an authentication requesting message to a trunking home location register after receiving a call back requesting message sent by a call back requesting part; the trunking home location register authenticates the call back requesting part and a call back receiving part, if the authentication passes, then the trunking home location register sends an authentication response message to the trunking dispatch server, and the authentication response message comprises the authentication information of the call back requesting part and the call back receiving part; the trunking dispatch server judges whether the call back receiving part is idle and the call back requesting part is in a roaming state or not, and if the call back requesting part is not in a roaming state, then the trunking dispatch server sends a call back notice message to the idle call back requesting part. The method overcomes the defect of unavailable call back business in the traditional trunking communication system and increases the flexibility and the availability of the system.
Description
Technical field
The present invention relates to the trunked communication system field, specifically, relate to the method that realizes the callback request business in a kind of trunked communication system.
Background technology
Trunked communication system is a kind of senior mobile dispatching patcher, is representing the specialized mobile radio net developing direction of one of communication system, provides the multipurpose of excellent service, high-effect and cheap advanced wireless dispatching communication system to the user.Different with common mobile communication, trunking communication is mainly used in the specialized mobile radio field, is applied to large enterprise, harbour, taxi dispatching, safety etc., provides communication service for being engaged in business such as production scheduling and commander's control.Dispatching desk, can be set up with a plurality of terminals simultaneously and call out by logging on client as the vital tissue person of scheduling and control, has well realized its commander and coordinative role.Cluster communication system provides multiple function selecting by the business at concrete application is provided, and provides convenient, flexible and specialized service to the user, given full play to trunking communication flexibly, quick, characteristics of high efficiency.
The basic network framework of digital clustering communication system as shown in Figure 1, it comprises logic function modules such as colony terminal, base station sub-system, switching subsystem, dispatch service subsystem.
Base station sub-system is mainly finished various group services, the wireless access function of data service and plain old telephone service.Base station sub-system is made of jointly base station transceiver, base station controller and scheduling controller.Wherein radio receiving-transmitting unit is finished the function such as modulation and demodulation, radiofrequency signal transmitting-receiving of baseband signal, base station controller is finished all kinds of switchings of wireless resource allocation, call treatment, power control and support terminal, and scheduling controller is then finished wireless resource allocation, dispatch call control, power control, supports all kinds of switchings under the different areas of coverage of colony terminal, compiled and distribute the cluster audio data stream.
The dispatch service subsystem is mainly finished colony dispatching service, is made up of trunking dispatch server, cluster home location register, dispatching desk server and dispatching desk client.
Trunking dispatch server is the master control point of trunked call, finish the processing of colony dispatching calling, comprise the discriminating cluster user, set up various trunked calls such as individual call and (the PTT request are push to talk, PoC) such as group call, judgement cluster PTT requests.Trunking dispatch server also receives the cluster speech data of reverse link as trunking dispatch server, is distributed to corresponding forward link again according to the character of calling out.If the trunking dispatch server of notified message and the trunking dispatch server of being asked are not simultaneously, need it to transmit operation, at this moment, the trunking dispatch server of notified message is designated as the visit trunking dispatch server, and the trunking dispatch server of being asked is designated as the ownership trunking dispatch server.
The cluster authentication server is finished data base administration and configuration feature, for cluster user provides group registration, group member registration, and provides the local information of cluster member and the service authority record of cluster member, finishes call statistics and billing function.
In the concrete application of group system, can a certain terminal often occur and be in the calling, but another terminal to wish to notify this terminal, and set up the scene of calling out as early as possible, existing group system is not supported this request mode.Dispatching desk is as the special user of a class, form login by client, can participate in multiway calling simultaneously, also with its powerful organizational scheduling and middle rotating function and often be in the multiway calling simultaneously, can occur terminal needs and dispatching desk thus and set up contact, but can't determine whether dispatching desk can add the situation of this calling; In addition, present application also exists wishes that other-end or dispatching desk can initiate the situation to this terminal call, as wishes that the other side bears calling charge etc.Therefore, need provide a kind of method, make terminal or dispatching desk can obtain requesting party's request message, and callback request be initiated in autonomous judging whether.But existing systems does not provide this requesting method.
Callback feature is called calling alarm again, when the callback request party wishes the recipient with the callback oneself of individual calling mode, sends a callback request message to the recipient.The callback recipient can determine whether callback according to actual conditions after receiving callback request message.Its characteristics are exactly: receive a side of request message, can independently determine whether callback, to the user with very big operating flexibility.Existing trunked communication system does not provide callback feature.
Summary of the invention
Technical problem to be solved by this invention is, the method, system and device of realizing the callback request business in a kind of trunked communication system are provided, and overcomes the shortcoming that can't carry out this type of call back service in the existing trunked communication system.
To achieve these goals, the invention provides the method that realizes the callback request business in a kind of trunked communication system, this method comprises:
Trunking dispatch server sends authentication request message to the cluster home location register after receiving the callback request message that the callback request party sends;
Described cluster home location register is to described callback request party and callback recipient authentication, if authentication is passed through, then send authentication response message, carry described callback request party and callback recipient's authorization message in the described authentication response message to described trunking dispatch server;
Described trunking dispatch server judges whether described callback Recipient Status is idle and whether described callback request party is in roaming state, if described callback request party is in non-roaming state, then call back notification message to the callback recipient who is in idle condition.
Further, described trunking dispatch server receives that described method also comprises before the callback request message that the callback request party sends:
The described trunking dispatch server of described callback request direction calls back request message, and carries callback request party's IMSI International Mobile Subscriber Identity IMSI and callback recipient number in described callback request message.
Further, described trunking dispatch server is after described callback recipient calls back notification message, and described method also comprises:
Described callback recipient calls back acknowledge message to described trunking dispatch server after receiving the callback notification message;
Described trunking dispatch server is returned the first callback response message to described callback request party after receiving described callback acknowledge message.
Further, described callback request party is a cluster communication terminal; Described callback recipient is cluster communication terminal or dispatching desk.
Further, described trunking dispatch server is judged described callback recipient type according to the callback recipient's who carries in the described authentication response message authorization message.
Further, if described callback recipient is in busy state, then described trunking dispatch server sends the second callback response message to described callback request party, carries called unreachable indication in the described second callback response message;
If described callback recipient is in idle condition and the callback request party is in roaming state, then described trunking dispatch server sends described callback notification message to described callback request party's ownership trunking dispatch server.
Further, after described callback request party belonged to trunking dispatch server and receives described callback notification message, described method further comprised:
Described callback request party belongs to trunking dispatch server and judges described callback recipient type, described callback notification message is transmitted to the callback recipient of the corresponding types that is in idle condition.
The present invention also provides the system that realizes the callback request business in a kind of trunked communication system, and this system comprises:
Trunking dispatch server is used for after receiving the callback request message that the callback request party sends, and sends authentication request message to the cluster home location register; Be used for also after receiving authentication response message, judging whether described callback Recipient Status is idle and whether described callback request party is in roaming state, and when described callback request party is in non-roaming state, call back notification message for idle callback recipient to state;
The cluster home location register, be used for described callback request party and callback recipient authentication, if authentication is passed through, then send authentication response message, and in described authentication response message, carry described callback request party and callback recipient's authorization message to described trunking dispatch server.
Further, described system also comprises:
The callback request party is used for calling back request message to described trunking dispatch server, and carries callback request party IMSI and callback recipient number in described callback request message;
The callback recipient is used for calling back acknowledge message to described trunking dispatch server after receiving the callback acknowledge message that described trunking dispatch server sends.
The present invention also provides a kind of trunking dispatch server, is used for realizing the callback request business at trunked communication system, comprising:
First receiver module is used to receive the callback request message that the callback request party sends;
First sending module is used for sending authentication request message to the cluster home location register after first receiver module receives described callback request message;
Second receiver module, be used for described cluster home location register authentication by and after described trunking dispatch server sends authentication response message, receive the described authentication response message that described cluster home location register sends;
Judge module, be used for after described second receiver module receives described authentication response message, judge that according to callback request party who carries in the described authentication response message and callback recipient's authorization message whether described callback Recipient Status is idle, and whether described callback request party is in roaming state;
Second sending module is used for calling back notification message according to judged result after described judge module is judged.
Further, described judge module also is used for: the callback recipient's who carries according to described authentication response message authorization message is judged described callback recipient type.
Further, described second sending module calls back notification message according to the judged result of judge module and specifically comprises:
If the callback request party is in non-roaming state, then send described callback notification message to the callback recipient who is in idle condition;
If the callback request party is in roaming state, then belongs to trunking dispatch server and send described callback notification message to described callback request party.
Further, described trunking dispatch server further comprises:
The 3rd receiver module is used to receive the callback acknowledge message that the callback recipient sends;
Timer T1 is provided with module, is used to be provided with timer T1, and sends the authentication request message described timer T1 of startup later at described first sending module, closes described timer T1 after described second receiver module receives authentication response message;
Timer T2 is provided with module, is used to be provided with timer T2, and calls back the notification message described timer T2 of startup later at described second sending module, closes described timer T2 after described the 3rd receiver module receives the callback acknowledge message;
The 3rd sending module is used for calling back response message to the callback request party after the 3rd receiver module receives the callback acknowledge message.
By the method for the invention, system and device, overcome the shortcoming that existing trunked communication system can't callback, increased a kind of by sending the method that particular message requires recipient's callback, give the callback recipient by calling back notification message, whether the callback recipient can determine the callback transmit leg as the case may be, provide greater flexibility to the recipient, strengthened the flexibility and the availability of system.
Description of drawings
Fig. 1 realizes an exemplary group system network frame figure required for the present invention;
Fig. 2 is the flow chart of the request that calls back between the terminal of the inventive method embodiment one;
Fig. 3 is that the terminal of the inventive method embodiment two calls back the processing of request flow chart to dispatching desk;
Fig. 4 calls back the processing of request flow chart between the terminal when transmit leg and recipient are in different scheduler subsystem in the trunked communication system of the inventive method embodiment three;
Fig. 5 is the Organization Chart of system embodiment of the present invention;
Fig. 6 is the structured flowchart of apparatus of the present invention embodiment.
Embodiment
Describe the present invention below in conjunction with drawings and Examples.Need to prove that in the processing of callback request business described in the invention, the callback request party is a cluster communication terminal, the callback recipient can be cluster communication terminal or dispatching desk.
Method embodiment one
Fig. 2 is the flow chart of the request that calls back between the terminal of the embodiment of the invention one.As shown in Figure 2, the flow process that calls back request between the cluster communication terminal comprises the steps:
Judge that whether the callback Recipient Status is idle, promptly judges whether to exist the dispatcher who logins this dispatching desk, i.e. the dispatcher of operating state;
Judge whether the callback request party is roaming state:, show that then the callback request party is a roaming state if the callback request party is belonged to trunking dispatch server and this trunking dispatch server is inconsistent;
Judge callback recipient type: judge that promptly the callback recipient is terminal or dispatching desk.Trunking dispatch server is judged callback recipient type according to whether carrying callback recipient IMSI in the authentication response message.If carry callback recipient IMSI, show that then the callback recipient is cluster communication terminal; If do not carry callback recipient IMSI, show that then the callback recipient is dispatching desk.Through judgement, the callback recipient is a cluster communication terminal in the present embodiment.
After trunking dispatch server is finished as above judgement, it is non-roaming to draw the callback request party, the callback recipient is the conclusion of idle condition cluster communication terminal, and then trunking dispatch server is obtained recipient IMSI and called back notification message to receiving side terminal, starts timer T2.This timer is used for guaranteeing that callback message sends arrival at the appointed time and returns confirmation, does not return if surpass this timer duration, does timeout treatment.Execution in step 205.
If the callback Recipient Status is busy, then trunking dispatch server is returned the callback response message to the callback request party, indicates called unreachable.
After step 205, receiving side terminal are received the callback notification message, return the callback acknowledge message to trunking dispatch server.Callback is confirmed to refer to the system level that need not manual intervention and is confirmed, only shows that message sends to recipient's equipment.After trunking dispatch server is received the callback acknowledge message, timeing closing device T2.Execution in step 206.
As can be seen from the above-described embodiment, the present invention from sending, to returning success, fail the time of replying, has guaranteed the real-time of callback request by restriction of originating calls terminal callback request message.
Method embodiment two
Fig. 3 is that the terminal of the inventive method embodiment two calls back the processing of request flow chart to dispatching desk, and in the present embodiment, the callback recipient of callback request party's appointment is a dispatching desk.As shown in Figure 2, terminal calls back the processing of request flow process to dispatching desk and comprises the steps:
Judge that whether the callback Recipient Status is idle, promptly judges whether to exist the dispatcher who logins this dispatching desk, i.e. the dispatcher of operating state;
Judge whether the callback request party is roaming state:, show that then the callback request party is a roaming state if the callback request party is belonged to trunking dispatch server and this trunking dispatch server is inconsistent.
Judge callback recipient type: judge that promptly the callback recipient is terminal or dispatching desk.Trunking dispatch server is judged callback recipient type according to whether carrying the callback recipient in the authentication response message.If carry callback recipient IMSI, show that then the callback recipient is cluster communication terminal; If do not carry callback recipient IMSI, show that then the callback recipient is dispatching desk.Through judgement, the callback recipient is a cluster communication terminal in the present embodiment;
After trunking dispatch server is finished as above judgement, it is non-roaming to draw the callback request party, the callback recipient is the conclusion of idle condition dispatching desk, and then trunking dispatch server calls back notification message to callback recipient dispatching desk server, starts timer T2. execution in step 305.
If the callback Recipient Status is busy, then trunking dispatch server is returned the callback response message to the callback request party, indicates called unreachable.
Step 305 after callback recipient dispatching desk server is received the callback notification message, need be returned the callback acknowledge message to trunking dispatch server.After trunking dispatch server is received the callback acknowledge message, timeing closing device T2.Execution in step 306.
Method embodiment three
Fig. 2 and the described situation of Fig. 3 are the consistent situations of dispatch server under dispatch server under the callback recipient and callback request party.Further, if requesting party, recipient are positioned at different dispatch service subsystems, be under affiliated trunking dispatch server of recipient and the affiliated inconsistent situation of trunking dispatch server of transmit leg (being that the callback request party is in roaming state with respect to the current scheduling server), is example with terminal to the terminal request of calling back, in conjunction with Fig. 4, describe a kind of terminal and call back the processing of request method to terminal.Fig. 4 calls back the processing of request flow chart between the terminal when transmit leg and recipient are in different scheduler subsystems (being that the callback request party roams) in the trunked communication system of the inventive method embodiment three, as shown in Figure 4, comprises the steps:
Judge that whether the callback Recipient Status is idle, promptly judges whether to exist the dispatcher who logins this dispatching desk, i.e. the dispatcher of operating state;
Judge whether the callback request party is roaming state:, show that then the callback request party is a roaming state if the callback request party is belonged to trunking dispatch server and this trunking dispatch server is inconsistent.
Judge callback recipient type: judge that promptly the callback recipient is terminal or dispatching desk.The visit trunking dispatch server is judged callback recipient type according to whether carrying callback recipient IMSI in the authentication response message.If carry callback recipient IMSI, show that then the callback recipient is cluster communication terminal; If do not carry callback recipient IMSI, show that then the callback recipient is dispatching desk.Through judgement, the callback recipient is a cluster communication terminal in the present embodiment;
After the visit trunking dispatch server is finished as above judgement, draw the callback request party and be roaming state, the callback recipient is the conclusion of idle condition cluster communication terminal, then visit trunking dispatch server and call back notification message, start timer T2. execution in step 405 to the ownership trunking dispatch server.
If the callback Recipient Status is busy, then trunking dispatch server is returned the callback response message to the callback request party, indicates called unreachable.
Step 405 ownership trunking dispatch server is judged the recipient: if recipient's authorization message is carried IMSI, show that the recipient is a colony terminal after receiving the callback notification message.The ownership trunking dispatch server calls back notification message to receiving side terminal.Change step 406 over to.
After receiving the callback request notification message, the recipient of callback request can select callback user at once, also can put into formation, carries out callback again in the follow-up moment.
System embodiment
According to the embodiment of the invention, provide the system that realizes the callback request business in a kind of trunked communication system.As 5 being Organization Charts of system embodiment of the present invention, by shown in Figure 5, this system comprises:
Trunking dispatch server is used for after receiving the callback request message that the callback request party sends, and sends authentication request message to the cluster home location register; Be used for also after receiving authentication response message, judging whether described callback Recipient Status is idle and whether described callback request party is in roaming state, and when described callback request party is in non-roaming state, call back notification message for idle callback recipient to state;
The cluster home location register, be used for described callback request party and callback recipient authentication, if authentication is passed through, then send authentication response message, and in described authentication response message, carry described callback request party and callback recipient's authorization message to described trunking dispatch server.
The callback request party is used for calling back request message to described trunking dispatch server, and carries callback request party IMSI and callback recipient number in described callback request message;
The callback recipient is used for calling back acknowledge message to described trunking dispatch server after receiving the callback acknowledge message that described trunking dispatch server sends.
Device embodiment
According to embodiments of the invention, a kind of trunking dispatch server is provided, be used for trunked communication system and realize the callback request business, Fig. 6 is the structured flowchart of apparatus of the present invention embodiment, below in conjunction with Fig. 6 device of the present invention is done detailed description:
Apparatus of the present invention comprise:
First receiver module is used to receive the callback request message that the callback request party sends;
First sending module is used for sending authentication request message to the cluster home location register after first receiver module receives described callback request message;
Second receiver module, be used for described cluster home location register authentication by and after described trunking dispatch server sends authentication response message, receive the described authentication response message that described cluster home location register sends;
Judge module, be used for after described second receiver module receives described authentication response message, judge that according to callback request party who carries in the described authentication response message and callback recipient's authorization message whether described callback Recipient Status is idle, and whether described callback request party is in roaming state;
Second sending module is used for calling back notification message according to judged result after described judge module is judged.
Further, described judge module also is used for: the callback recipient's who carries according to described authentication response message authorization message is judged described callback recipient type.
Further, described second sending module calls back notification message according to the judged result of judge module and specifically comprises:
If the callback request party is in non-roaming state, then send described callback notification message to the callback recipient who is in idle condition;
If the callback request party is in roaming state, then belongs to trunking dispatch server and send described callback notification message to described callback request party.
Further, this device also comprises:
The 3rd receiver module is used to receive the callback acknowledge message that the callback recipient sends;
Timer T1 is provided with module, is used to be provided with timer T1, and sends the authentication request message described timer T1 of startup later at described first sending module, closes described timer T1 after described second receiver module receives authentication response message;
Timer T2 is provided with module, is used to be provided with timer T2, and calls back the notification message described timer T2 of startup later at described second sending module, closes described timer T2 after described the 3rd receiver module receives the callback acknowledge message;
The 3rd sending module is used for calling back response message to the callback request party after the 3rd receiver module receives the callback acknowledge message.
Above method embodiment has listed several terminals and has called back the specific implementation of crying request.Timer enable the effective real-time that guarantees callback message.Recipient's type can be a terminal, can be dispatching desk also, has embodied the flexibility of callback request.
In sum, by method, system and device of the present invention, under the prerequisite that keeps existing cluster communication system network configuration, provide a kind of terminal that realizes to call back the method for request to dispatching desk or another terminal, can normally set up the mutual of callback message between information receiving and transmitting two sides, effectively guarantee between the terminal and the communication between terminal and the dispatching desk.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (13)
1. realize the method for callback request business in the trunked communication system, it is characterized in that this method comprises:
Trunking dispatch server sends authentication request message to the cluster home location register after receiving the callback request message that the callback request party sends;
Described cluster home location register is to described callback request party and callback recipient authentication, if authentication is passed through, then send authentication response message, carry described callback request party and callback recipient's authorization message in the described authentication response message to described trunking dispatch server;
Described trunking dispatch server judges whether described callback Recipient Status is idle and whether described callback request party is in roaming state, if described callback request party is in non-roaming state, then call back notification message to the callback recipient who is in idle condition.
2. method according to claim 1 is characterized in that,
Described trunking dispatch server receives that described method also comprises before the callback request message that the callback request party sends:
The described trunking dispatch server of described callback request direction calls back request message, and carries callback request party's IMSI International Mobile Subscriber Identity IMSI and callback recipient number in described callback request message.
3. method according to claim 1 is characterized in that,
Described trunking dispatch server is after described callback recipient calls back notification message, and described method also comprises:
Described callback recipient calls back acknowledge message to described trunking dispatch server after receiving the callback notification message;
Described trunking dispatch server is returned the first callback response message to described callback request party after receiving described callback acknowledge message.
4. method according to claim 1 is characterized in that,
Described callback request party is a cluster communication terminal;
Described callback recipient is cluster communication terminal or dispatching desk.
5. method according to claim 1 is characterized in that described method also comprises:
Described trunking dispatch server is judged described callback recipient type according to the callback recipient's who carries in the described authentication response message authorization message.
6. method according to claim 1 is characterized in that described method also comprises:
If described callback recipient is in busy state, then described trunking dispatch server sends the second callback response message to described callback request party, carries called unreachable indication in the described second callback response message;
If described callback recipient is in idle condition and the callback request party is in roaming state, then described trunking dispatch server sends described callback notification message to described callback request party's ownership trunking dispatch server.
7. as method as described in the claim 6, it is characterized in that,
After described callback request party belonged to trunking dispatch server and receives described callback notification message, described method further comprised:
Described callback request party belongs to trunking dispatch server and judges described callback recipient type, described callback notification message is transmitted to the callback recipient of the corresponding types that is in idle condition.
8. realize the system of callback request business in the trunked communication system, it is characterized in that described system comprises:
Trunking dispatch server is used for after receiving the callback request message that the callback request party sends, and sends authentication request message to the cluster home location register; Be used for also after receiving authentication response message, judging whether described callback Recipient Status is idle and whether described callback request party is in roaming state, and when described callback request party is in non-roaming state, call back notification message for idle callback recipient to state;
The cluster home location register, be used for described callback request party and callback recipient authentication, if authentication is passed through, then send authentication response message, and in described authentication response message, carry described callback request party and callback recipient's authorization message to described trunking dispatch server.
9. as system as described in the claim 8, it is characterized in that described system also comprises:
The callback request party is used for calling back request message to described trunking dispatch server, and carries callback request party IMSI and callback recipient number in described callback request message;
The callback recipient is used for calling back acknowledge message to described trunking dispatch server after receiving the callback acknowledge message that described trunking dispatch server sends.
10. a trunking dispatch server is used for realizing the callback request business at trunked communication system, it is characterized in that, comprising:
First receiver module is used to receive the callback request message that the callback request party sends;
First sending module is used for sending authentication request message to the cluster home location register after first receiver module receives described callback request message;
Second receiver module, be used for described cluster home location register authentication by and after described trunking dispatch server sends authentication response message, receive the described authentication response message that described cluster home location register sends;
Judge module, be used for after described second receiver module receives described authentication response message, judge that according to callback request party who carries in the described authentication response message and callback recipient's authorization message whether described callback Recipient Status is idle, and whether described callback request party is in roaming state;
Second sending module is used for calling back notification message according to judged result after described judge module is judged.
11. as trunking dispatch server as described in the claim 10, it is characterized in that,
Described judge module also is used for: the callback recipient's who carries according to described authentication response message authorization message is judged described callback recipient type.
12. as trunking dispatch server as described in the claim 11, it is characterized in that,
Described second sending module calls back notification message according to the judged result of judge module and specifically comprises:
If the callback request party is in non-roaming state, then send described callback notification message to the callback recipient who is in idle condition;
If the callback request party is in roaming state, then belongs to trunking dispatch server and send described callback notification message to described callback request party.
13. as claim 10-12 arbitrary as described in trunking dispatch server, it is characterized in that described trunking dispatch server further comprises:
The 3rd receiver module is used to receive the callback acknowledge message that the callback recipient sends;
Timer T1 is provided with module, is used to be provided with timer T1, and sends the authentication request message described timer T1 of startup later at described first sending module, closes described timer T1 after described second receiver module receives authentication response message;
Timer T2 is provided with module, is used to be provided with timer T2, and calls back the notification message described timer T2 of startup later at described second sending module, closes described timer T2 after described the 3rd receiver module receives the callback acknowledge message;
The 3rd sending module is used for calling back response message to the callback request party after the 3rd receiver module receives the callback acknowledge message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910139041.8A CN101883332B (en) | 2009-05-05 | 2009-05-05 | Method, system and device for realizing call back requesting business in trunking communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910139041.8A CN101883332B (en) | 2009-05-05 | 2009-05-05 | Method, system and device for realizing call back requesting business in trunking communication system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101883332A true CN101883332A (en) | 2010-11-10 |
| CN101883332B CN101883332B (en) | 2015-05-20 |
Family
ID=43055194
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910139041.8A Expired - Fee Related CN101883332B (en) | 2009-05-05 | 2009-05-05 | Method, system and device for realizing call back requesting business in trunking communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101883332B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102131154A (en) * | 2010-11-30 | 2011-07-20 | 华为技术有限公司 | Method, device and system for processing value added services for short message service |
| CN104657207A (en) * | 2015-03-05 | 2015-05-27 | 中国工商银行股份有限公司 | Remote authorization request scheduling method, service server and scheduling system |
| CN108282752A (en) * | 2017-12-29 | 2018-07-13 | 海能达通信股份有限公司 | The method, system and device of group's callback in broadband cluster system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101056432A (en) * | 2006-04-14 | 2007-10-17 | 中兴通讯股份有限公司 | Implementation method for the busy prompt service in the digital cluster communication system |
| CN101136968A (en) * | 2007-02-05 | 2008-03-05 | 中兴通讯股份有限公司 | Busy calling forwarding method |
| EP1926333A1 (en) * | 2005-08-18 | 2008-05-28 | ZTE Corporation | A roaming implemented method for digital trunk communication system |
-
2009
- 2009-05-05 CN CN200910139041.8A patent/CN101883332B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1926333A1 (en) * | 2005-08-18 | 2008-05-28 | ZTE Corporation | A roaming implemented method for digital trunk communication system |
| CN101056432A (en) * | 2006-04-14 | 2007-10-17 | 中兴通讯股份有限公司 | Implementation method for the busy prompt service in the digital cluster communication system |
| CN101136968A (en) * | 2007-02-05 | 2008-03-05 | 中兴通讯股份有限公司 | Busy calling forwarding method |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102131154A (en) * | 2010-11-30 | 2011-07-20 | 华为技术有限公司 | Method, device and system for processing value added services for short message service |
| CN102131154B (en) * | 2010-11-30 | 2013-10-09 | 华为技术有限公司 | Method and device for processing value added services for short message service |
| CN104657207A (en) * | 2015-03-05 | 2015-05-27 | 中国工商银行股份有限公司 | Remote authorization request scheduling method, service server and scheduling system |
| CN104657207B (en) * | 2015-03-05 | 2018-03-23 | 中国工商银行股份有限公司 | Dispatching method, service server and the scheduling system of remote authorization request |
| CN108282752A (en) * | 2017-12-29 | 2018-07-13 | 海能达通信股份有限公司 | The method, system and device of group's callback in broadband cluster system |
| CN108282752B (en) * | 2017-12-29 | 2021-09-28 | 海能达通信股份有限公司 | Method, system, device and storage medium for group callback in broadband cluster system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101883332B (en) | 2015-05-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108449724B (en) | Function number service processing method and device | |
| CN1729706B (en) | Method and apparatus for efficient paging and registration in a wireless communications network | |
| CN100488089C (en) | CDMA digital cluster system and method for implementing group calling service | |
| US20040082352A1 (en) | Enhanced group call implementation | |
| CN110650444B (en) | System and method for realizing public and private combination of TD-LTE network cluster service | |
| EP3187020B1 (en) | User device and method thereof | |
| CN101707745B (en) | Method, system and device for selecting call groups | |
| CN103974206A (en) | Call Control System, Mobile Station And Call Restriction Method | |
| CN101594576B (en) | Method for realizing trans-provincial group calling in digital cluster communication system | |
| CN104254129A (en) | Close business discovery resource configuration method and device | |
| CN101227659B (en) | Method for implementing monitoring and recording for roaming user in numeral cluster communication system | |
| CN101521876A (en) | System and method for remote-closing/ resurrection of value aggregate terminal | |
| CN101119539B (en) | Method to implement inhibition, revival function in digital cluster system | |
| CN101262653A (en) | Dynamic repacking method for digital cluster system | |
| CN101883332B (en) | Method, system and device for realizing call back requesting business in trunking communication system | |
| CN100512549C (en) | System and method for prompting user access failure for digital trunking communication system | |
| CN100461901C (en) | Method for realizing CDMA traditional packet digital calling talk process | |
| CN101931889B (en) | Method for implementing self grouping of terminal in cluster system | |
| CN101854617B (en) | Method and system for querying status of called party in paging | |
| CN101005707B (en) | Method for roaming terminal inquiry, exciting/de-exciting complementary service in cluster system | |
| CN100512555C (en) | Position-based group allocation method | |
| CN100463575C (en) | Method for combining traditional call with enhanced call in CDMA digital packet | |
| CN101137109A (en) | Method to implement timingly cancelling recombined packets of cluster system | |
| CN100518347C (en) | An implementation method for automatically selecting dispatcher access based on caller attributes | |
| CN101094514B (en) | Access control method for prepaid users in cluster communication 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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150520 Termination date: 20190505 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |