CN101072390B - A Dynamic Group Management Method for Digital Trunking System - Google Patents

Abstract

A method for dynamic group management of a digital trunking system, comprising the following steps: (a) specifying one or several members as administrators of the group in the group user database, and granting them authority to manage the group; (b) The group administrator sends a group management request to the cluster scheduling server through the terminal, specifying the group number and group member number to be operated; (c) the cluster scheduling server forwards the management to the cluster home register after judging that the message is legal Request, after the authentication of the cluster ownership register is successful, return the response of group management success to the cluster scheduling server; (d) the cluster scheduling server sends the response of group management success to the group administrator terminal, and performs dynamic group management on the relevant groups. group management. The method of the invention has the characteristics of simple realization, convenient operation, real-time high efficiency.

Description

A dynamic group management method for digital trunking system

technical field

The invention relates to a digital trunking communication system, and introduces a dynamic group management method of the trunking system. the

Background technique

The trunking communication system is an advanced mobile dispatching system, which represents the development direction of a dedicated mobile communication network, one of the communication systems. The trunking communication system has the function of sharing available channels for all users of the system and automatically selecting channels. It is a multi-purpose and high-efficiency wireless dispatching communication system for sharing resources, sharing costs, and sharing channel equipment and services. the

The basic network frame of the digital trunking communication system is shown in Figure 1, including the trunking terminal 1, the base station subsystem BSS 2, the switching subsystem 3 and the trunking dispatching subsystem 4, where:

cluster terminal 1

The trunking terminal 1 is connected to the trunking system through an air interface, and provides users with various trunking services of the trunking system. At the same time, it has the function of providing traditional ordinary telephone service, supplementary service, short message service and data service. the

Base Station Subsystem (BSS)2

The base station subsystem 2 is connected with the dispatching subsystem and the switching subsystem through standard interfaces to meet various service requirements of the trunking terminal, including trunking service, telephone service and data service. the

Switch Subsystem 3

The switching subsystem 3 belongs to the core network in the mobile communication system, and its network entities include a mobile switching center MSC (Mobile Switching Center) 31 and a home location register HLR (HomeLocation Register) 32, which mainly complete telephone interconnection services, ordinary telephone call services and some Value-added services, and provide storage and management of user information for related service functions, including account opening, logout, service authentication and authorization, etc. for mobile users with ordinary voice services, and assist in completing user calls and business operations. the

Cluster scheduling subsystem 4

The cluster scheduling subsystem 4 is composed of a cluster scheduling server (PDS) 41, a cluster belonging register (PHR) 42, a dispatch server DAS (Dispatching Agent Server) 45, a dispatch console client DAC (Disaptching Agent Client) 44 and a cluster user database 43 . The scheduling subsystem mainly completes the cluster scheduling business. the

The trunking dispatch server 41 is the general control point of trunking calls, and completes the processing of trunking dispatching calls, including identifying trunking users, establishing various trunking calls, judging requests for trunking speaking rights, and so on. The trunking dispatch server 41 also receives the trunking voice data from the reverse link, and redistributes it to the corresponding forward link according to the nature of the call. the

The trunking home register 42 manages the trunking user database and completes the functions of charging, authentication and authorization in the digital trunking system. When the cluster performs paging according to the unified group ID, the authentication and paging functions are independent. the

The cluster user database 43 stores relevant information of all users in the cluster communication system. the

The dispatch platform server 45 processes the service request sent by the dispatch station client. the

The dispatcher console client 44 includes a dispatcher console and a management console. The dispatcher performs dispatching operations by the dispatcher, including initiating calls, querying status, recording, etc.; the

A group call is a half-duplex trunking call in which multiple users participate, and is the most basic trunking call form. Group management is the basis of group calling, which directly determines the composition of group members and related attributes of group members. the

In some group call situations, unlike the trunking system in FIG. 1 , there is no special database system like the trunking home register 42, and the group information is stored on the terminal. Although the group management of terminals has been realized, because the group information is not managed in a centralized manner, the administrator's scheduling ability is weak, the security is poor, and the supported functions are relatively simple, so it is not suitable for professional cluster occasions. the

In the case of a background database, the group management is generally performed by the database administrator, and the group members are added or removed to modify the related attributes of the group members. This method requires the participation of the database administrator, which is slow, inefficient, and poor in real-time performance. In some urgent occasions, it may be necessary to manage group members in real time, such as adding some temporary important users to the group, making secret calls, deleting some group members in real time when there are group members making trouble, and prohibiting group members Speaking, allowing group members to speak, adjusting the attributes of group members, etc., the background database management method is definitely not in line with the needs.

Contents of the invention

The technical problem to be solved by the present invention is to provide a dynamic group management method of a digital trunking system, which has the characteristics of simple implementation and convenient operation. the

In order to solve the above technical problems, the present invention provides a dynamic group management method of a digital trunking system, comprising the following steps:

(a) Designate one or several members for the group in the cluster user database as the administrator of the group, and give them the authority to manage the group;

(b) The group administrator sends a group management request to the cluster scheduling server through the terminal, specifying the group number and group member number to be operated;

(c) After the cluster scheduling server judges that the message is legal, it forwards the management request to the cluster home register, and after the cluster home register authenticates successfully, it returns a successful authentication response to the cluster scheduling server;

(d) The cluster scheduling server sends a group management successful response to the group administrator terminal, and performs dynamic group management on related groups, and the group management results take effect in real time in the activated related groups. the

Further, the above-mentioned dynamic group management method may also have the following characteristics: if the group management request is a request for adding group members, the dynamic group management in the step (d) further includes the following steps:

(d1) The cluster scheduling server judges whether the operating group is in an active state, if yes, execute step (d2), otherwise, end;

(d2) The cluster scheduling server judges whether the user to be added to the group is in other group calls, if yes, execute step (d3), otherwise, execute step (d4);

(d3) The cluster scheduling server adds the information of the added user in this group, and sends a busy prompt to the user terminal, and ends;

(d4) The cluster scheduling server adds the information of the added user to the group, and initiates paging for the added user according to this information until the user joins the call or the call ends. the

Further, the above dynamic group management method may also have the following characteristics: if the group management request is a request to delete group members, the dynamic group management in step (d) further includes the following steps:

(d1) The cluster scheduling server judges whether the operating group is in an active state, if yes, execute step (d2), otherwise, end;

(d2) The cluster scheduling server judges whether the group member to be deleted is in an active state in this group call, if yes, execute step (d3), otherwise execute step (d4);

(d3) The cluster scheduling server clears the information of the deleted user from this group and releases the cluster call of this user, and ends;

(d4) The cluster scheduling server clears the information of the deleted user from the group, and ends. the

Further, the above dynamic group management method may also have the following characteristics: if the group management request is a request to modify the attributes of group members, the dynamic group management in step (d) further includes the following steps:

(d1) The cluster scheduling server judges whether the group operated by the group administrator terminal is in an active state, if yes, execute step (d2), otherwise, end;

(d2) The cluster scheduling server saves the modified group member attribute of the group, and the attribute takes effect immediately in this call, and ends. the

Furthermore, the above dynamic group management method may also have the following features: in the step (d), the cluster scheduling server also sends operation prompt information to the operated group users. the

Further, the above dynamic group management method may also have the following characteristics: after the authentication of the cluster home register in the step (c) is successful, the requested group management operation is first performed in the cluster user database, and then returned to the cluster scheduling server Group management successful response. the

Further, the above-mentioned dynamic group management method may also have the following characteristics: the group management authority granted to the group administrator in the step (a) includes the following or any combination thereof: adding group members, deleting group Group membership and modification of group membership attributes. Correspondingly, the step (c) performing the requested group management operation in the cluster user database is one of the above operations. the

Further, the above-mentioned dynamic group management method may also have the following characteristics: when the cluster home register receives the management request for authentication in the step (c), it includes the following judgment: whether the terminal that initiates the request has the group administrator Whether the user being operated is already a group member; and when adding a user, it is necessary to judge whether the identity of the added user is legal, and when modifying the group member attribute, it is also necessary to judge whether the modified related group member attribute is legal . the

Further, the above-mentioned dynamic group management method may also have the following characteristics: in the step (b), when the group administrator requests to modify the attributes of the group members, in addition to specifying the group number and group member number to be operated, Also specifies the group membership attribute to modify. the

Further, the above-mentioned dynamic group management method can also have the following characteristics: if the authentication of the cluster home register in the step (c) fails, the authentication rejection message will be sent back to the cluster scheduling server, and the cluster debugging server will send a message to the group administrator terminal. Send group management rejection message, end. the

As can be seen from the above, the present invention proposes a method for terminal wireless group management in a digital trunking communication system based on the characteristics of trunking communication. The service has the characteristics of simple implementation, convenient operation, real-time efficiency, and is an excellent choice for operators. the

Description of drawings

Figure 1 shows the basic network architecture of the digital trunking communication system. the

Fig. 2 is a flow chart of a group administrator wirelessly adding group members through a terminal in the digital trunking dispatching system according to an embodiment of the present invention. the

Fig. 3 is a flow chart of a group administrator wirelessly deleting a group member through a terminal in the digital trunking communication system according to an embodiment of the present invention. the

FIG. 4 is a flow chart of a group administrator wirelessly modifying group member attributes through a terminal in a digital trunking communication system according to an embodiment of the present invention. the

Detailed ways

The implementation method of terminal wireless group management in the digital trunking communication system provided by this embodiment, when the database administrator adds the group number and group members, set the basic attributes of the group and group members, the attributes of the group members Including account status, member priority, speech duration, call authority, etc.; at the same time, set a group member (the possibility of setting more than one is not ruled out) as the administrator of the group, and the rights granted to the group management include: add And delete group members, modify group member attributes (such as the priority of group members, speaking authority, speaking duration, etc.). The group administrator initiates the management of the group through the operation of the terminal menu, such as adding group members, deleting group members, modifying group member permissions and attributes, and so on. When the group is idle, these configurations are saved to the cluster home register; when the group is active (meaning that the group is calling), these configurations will also be saved to the cluster home register, and these operations will also be in the cluster home register. It takes effect in real time in the activated group. the

The following describes the specific process for group administrators to manage groups through wireless terminals. the

In the digital trunking dispatching system, the process of adding group members wirelessly by the group administrator through the trunking terminal is shown in Figure 2, including the following steps:

Step 201, the group administrator sends a request to add group members to the PDS through the terminal, which indicates the number of the group member to be added and the group number to be operated;

Step 202, the PDS decodes the signaling and judges whether it is legal, if not, execute step 203, otherwise, execute step 204;

Step 203, abandon the request, end;

Step 204, forwarding the management request of adding group members to the PHR;

Step 205, PHR queries the cluster user database to determine whether the terminal has the operation authority of the group administrator, whether the added user is already a group member or whether the identity is legal, etc., if the authentication is passed, execute step 208, otherwise , execute step 206;

Step 206, the PHR returns an authentication rejection message to the PDS;

Step 207, the PDS sends a group management rejection message to the terminal of the group administrator, and ends;

Step 208, PHR adds group members in the cluster user database according to the request, so that it will take effect in the next group call, and returns an authentication success response to PDS;

Step 209, the PDS sends a group management success response to the group administrator terminal, and sends an operation prompt message to the user added to the group, informing him that he has been added to a certain group;

Step 210, PDS judges whether the group whose group members are to be added is in an active state, if yes, executes step 211, otherwise, the group whose group members are to be added is in an inactive state, and ends;

Step 211, the PDS judges whether the user to be added to the group is in other group calls, if not, the user is in an idle state, and executes step 212, otherwise executes step 213;

In step 212, the PDS adds the information of the added user to the group, and initiates paging for the added user according to the information until the user joins the call or the call ends. the

Step 213, PDS adds the information of the added user in this group, and sends a busy prompt to the user terminal, and ends;

So far, the group administrator has completed the operation of adding group members wirelessly through the terminal. the

In the digital trunking dispatching system, the process of group administrators wirelessly deleting group members through the trunking terminal is shown in Figure 3, including the following steps:

Step 301, the group administrator sends a request to delete a group member to the PDS through the terminal, which indicates the number of the group member to be deleted and the operated group number (GID);

Step 302, the PDS decodes the signaling and judges whether it is legal, if legal, execute step 304, otherwise, execute step 303;

Step 303, abandon the request, end;

Step 304, the PDS forwards the management request of deleting group members to the PHR;

Step 305, the PHR queries the cluster user database to determine whether the terminal has the operation authority of the group administrator, whether the deleted user is already a group member, etc., if the authentication is passed, execute step 308, otherwise execute step 306;

Step 306, the PHR returns an authentication rejection message to the PDS;

Step 307, the PDS sends a group management rejection message to the administrator, and ends;

Step 308, the PHR deletes the member of the group in the cluster user database, so that it will take effect in the next group call, and returns an authentication success response to the PDS;

Step 309, the PDS sends a group management successful response to the group administrator terminal, and sends a prompt message to the deleted group user, informing that it is deleted from a certain group;

Step 310, the PDS judges whether the group whose group members are to be deleted is in an active state, if the group whose group members are to be removed is in an inactive state, the process ends, otherwise, step 311 is performed;

Step 311, PDS judges whether the group member to be deleted is in active state in this group call, if yes, execute step 313, otherwise execute step 312;

Step 312, the deleted group member is in an inactive state in this group call, and the PDS clears the information of the deleted user from this group, and ends;

Step 313, PDS clears the information of the deleted user from this group and releases the group call of this user, and ends;

So far, the group administrator has completed the operation of deleting group members wirelessly through the terminal. the

In the digital trunking dispatching system, the process for the group administrator to modify the group members wirelessly through the trunking terminal is shown in Figure 4, including the following steps:

Step 401, the group administrator sends a request to modify group member attributes to the PDS through the terminal, which indicates the number of the group member to be modified, the group number to be operated, and the related group member attributes to be modified;

Step 402, the PDS decodes the signaling and judges its validity, if not, execute step 403; otherwise, execute step 404;

Step 403, abandon the request, end;

Step 404, the PDS forwards the group management request to the PHR;

Step 405, PHR queries the cluster user database to determine whether the group administrator has authority, whether the user managed by the group is a group member or whether the identity is legal, whether the modified related group member attributes are legal, etc., such as authentication passed , execute step 408, otherwise, execute step 406;

Step 406, the PHR returns an authentication rejection message to the PDS;

Step 407, the PDS sends a group management rejection message to the group administrator terminal, and ends;

Step 408, the PHR revises the attribute information of the relevant group members in the cluster user database, so that it will take effect in the next group call, and returns an authentication success response to the PDS;

Step 409, the PDS sends a response message to the group administrator that the attribute modification of the group member is successful, and sends an operation prompt to the group user whose attribute has been modified, informing them of the modification of the attribute;

Step 410, PDS judges whether the group operated by the group administrator terminal is in an active state, if yes, executes the next step; if the group is not in an active state, the process ends;

In step 411, the PDS saves the modified group member attribute of the group, and the attribute takes effect immediately in this call. the

So far, the operation of the group administrator to modify the attributes of the group members wirelessly through the terminal is completed. the

In another embodiment, if the real-time requirements are not high, it is not necessary to judge whether the operating group is in an active state, that is, the PHR returns an authentication success response to the PDS, and the PDS notifies the terminal that initiated the request, and then the process ends. the

To sum up, the above group management implementation method has three characteristics:

One is to define the role of the group administrator. Group members participate in group calls in real time and understand the various situations of the group. They are the best candidates to act as group managers. Group members who have been granted the group management authority can monitor the status of the group in real time and make adjustments to the group in a timely manner. Non-group administrators cannot manage groups, ensuring the security of group management. the

The second is that the group administrator can manage the group through the terminal in a timely manner as needed without notifying the background administrator. The cluster terminal is carried by the group administrator and is the most convenient tool for group management. You can add and delete group members, modify group member attributes, etc. through the menu of the terminal, and the operation is convenient and fast. the

Third, the result of terminal group management can take effect in real time in the activated group, realizing dynamic group management. The results of group management are stored in the centralized database in the background, and each subsequent call will take effect. At the same time, if the group call is currently activated, group members can be added or removed dynamically, and group member attribute management can be modified, with high real-time performance. the

Claims (10)

1. the dynamic group management method of a digital cluster system may further comprise the steps:

(a) in the cluster user database, be the keeper of one or some members of group's appointment, give the authority of its management group as this group;

(b) management and group person sends management and group request, group number that appointment will be operated and group member number by terminal to trunking dispatch server;

(c) described management request is transmitted to the cluster home location register in the legal back of trunking dispatch server judgement message, after the success of cluster home location register authentication, returns replying of authentication success to trunking dispatch server;

(d) trunking dispatch server sends replying of management and group success to management and group person's terminal, and relevant group is carried out the dynamic group management, and the management and group result comes into force in the relevant group that has activated in real time.

2. dynamic group management method as claimed in claim 1 is characterized in that, the management and group request is the request that increases group member as described, and the dynamic group management in the described step (d) further may further comprise the steps:

(d1) whether the group of trunking dispatch server decision operation is in state of activation, if, execution in step (d2), otherwise, finish;

(d2) trunking dispatch server judges whether the user that will be increased to group is in other group call, if, execution in step (d3), otherwise, execution in step (d4);

(d3) trunking dispatch server is added the information that is increased the user in this group, and sends busy prompt for this user terminal, finishes;

(d4) trunking dispatch server is added the information that is increased the user in this group, and initiates paging according to this information to being increased the user, adds until the user and calls out or end of calling.

3. dynamic group management method as claimed in claim 1 is characterized in that, the management and group request is the request of deletion group member as described, and the dynamic group management in the described step (d) further may further comprise the steps:

(d1) whether the group of trunking dispatch server decision operation is in state of activation, if, execution in step (d2), otherwise, finish;

(d2) trunking dispatch server judges to want deleted group member whether to be in state of activation in this group calls in several, if, execution in step (d3), otherwise execution in step (d4);

(d3) trunking dispatch server is removed deleted user's information and is discharged this user's trunked call from this group, finishes;

(d4) trunking dispatch server is removed deleted user's information from this group, finishes.

4. dynamic group management method as claimed in claim 1 is characterized in that, the management and group request is the request of revising the group member attribute as described, and the dynamic group management in the described step (d) further may further comprise the steps:

(d1) trunking dispatch server judges whether the group of management and group person's terminal operation is in state of activation, if, execution in step (d2), otherwise, finish;

(d2) trunking dispatch server is preserved the group member attribute that this group is modified, and this attribute comes into force in this is called out, and finishes.

5. dynamic group management method as claimed in claim 1 is characterized in that, in the described step (d), trunking dispatch server is returned operated group user transmit operation information.

6. dynamic group management method as claimed in claim 1, it is characterized in that, after the success of cluster home location register authentication, in the cluster user database, carry out the management and group operation of request earlier in the described step (c), return replying of management and group success to trunking dispatch server again.

7. dynamic group management method as claimed in claim 6, it is characterized in that, the operating right of giving management and group person's management group in the described step (a) comprises following several or its combination in any: add group member, deletion group member and revise the group member attribute, correspondingly, described step (c) the management and group operation of carrying out request in the cluster user database is a kind of in the aforesaid operations.

8. dynamic group management method as claimed in claim 7, it is characterized in that, the cluster home location register is received when authentication is carried out in described management request in the described step (c), comprise to judge: whether the terminal of initiating request has this management and group person's operating right, and whether operated user has been group member; And when increasing the user, to judge also whether the user identity that is increased is legal, when revising the group member attribute, will judge also whether the relevant group member attribute of modification is legal.

9. dynamic group management method as claimed in claim 7, it is characterized in that, when management and group person asks to revise the attribute of group member in the described step (b), except that specifying the group number and group member number that to operate, also specify the group member attribute that to revise.

10. dynamic group management method as claimed in claim 1, it is characterized in that described step (c) cluster home location register such as failed authentication then return the authentication refuse information to trunking dispatch server, the cluster debugging server sends the management and group refuse information to management and group person's terminal again, finishes.

Images