CN100403819C - A method for channel resource allocation in trunking service - Google Patents

Abstract

The invention discloses a method for allocating channel resources according to the call type and call service of a group user in a group service. The method signs the VPN information to which the cluster user belongs in the HLR, and sets each VPN call type resource allocation priority configuration table in the MSC. When the cluster user initiates a cluster call, the following steps are included: A.MSC reports the cluster user through the mobile station Identify and obtain the VPN information of the group user who initiated the call; B.MSC searches the call type resource allocation priority configuration table through the VPN information and call type information to obtain resource allocation priority information; C.MSC sends channel resources to the BSS system Request, the request carries the resource allocation priority information of the call type; the D.BSS performs resource allocation according to the call type resource allocation priority information and eMLPP priority information. The present invention realizes the solution of jointly determining user allocation resources based on call type and call service.

Description

A method for channel resource allocation in trunking service

technical field

The invention relates to the field of communication, in particular to a method for allocating channel resources according to call types and call services of trunking users in trunking services.

Background technique

Compared with the cluster private network, the cluster shared network has outstanding advantages in terms of network construction and maintenance costs, so the cluster shared network is the development trend of the cluster system; because the GSM system is the public mobile network with the most extensive user base in the world, Therefore, developing the trunking system based on GSM is the natural choice of our country's trunking system. For example, our country's GT800 system with independent intellectual property rights is a new generation of trunking system.

The service objects of the cluster system are some cluster departments, such as: public security, fire protection, armed police, national security bureau, army, large enterprises and institutions, etc. Since the service objects of the cluster system are not the general public, the number of users of the cluster system is relatively large. The number of public network users is very limited. Due to the lack of extensive user support, the investment in the trunking system is very limited, which determines the large area system of the trunking system (the cell coverage radius is large, which can greatly reduce the number of sites), and the channel resources of the cell are tight ( It can greatly reduce frequency resource requirements and site construction costs), because all users in the large area share very limited channel resources, and these users have different call rights; therefore, it is a cluster system to realize network resource allocation according to business priorities basic functions. As shown in FIG. 1 , it is a schematic diagram of a system of a cluster shared network in the prior art. It can be seen from the figure that the system mainly makes certain changes on the basis of the existing mobile network to complete the cluster network function.

Since the cluster network provides cluster services for multiple cluster departments, and each cluster department has different requirements on the priorities of various services, different cluster departments have different priority sequences. For example: for the trunking department A, its call type resource allocation priority order from high to low is emergency call service=>broadcast call service=>group call service=>single call service=>duplex telephone service=>data service; For the trunking department B, the call type resource allocation priority order from high to low is emergency call service=>group call service=>single call service=>broadcast call service=>duplex telephone service=>data service. The above priority information is configured through the MSC maintenance console and set on the MSC host, so that corresponding services can be provided in accordance with the set priority order during the cluster business process.

In the cluster network, such as the GSM system, the priority function based on specific services has been realized, that is, the enhanced multi-level priority and preemption service, referred to as eMLPP service. The eMLPP service allocates channel resources according to the specific eMLPP priority setting of the call service initiated. Each user is allowed to select a subscription priority when signing up for the eMLPP service. Different priorities determine the call establishment time. properties such as occupancy capacity. The operator provides different service qualities for different users and different calls according to the priority of user subscription.

The eMLPP service defines a total of 7 priority levels (A, B, 0, 1, 2, 3, 4) for calls, where A level is the highest level and level 4 is the lowest level. The highest two priorities are reserved for internal network use and can only be used locally. If an outgoing call occurs, the priorities of A and B need to be converted to 0.

Users can sign a priority in the HLR as the highest priority that they can use in the network. The two priorities of A and B are reserved within the network, and ordinary users are not allowed to sign. The signing data is determined by the network operator;

The user can subscribe a default call priority in the HLR, which cannot be higher than the highest priority subscribed by the user, and the user is allowed to modify the priority through the operation of the terminal.

When a user initiates a call without specifying the priority of the call, the network processes the call according to the default priority.

The eMLPP scheme of the GSM system has the following disadvantages:

1. The priority is based on the specific call service, and the priority allocation of network resources based on the call type cannot be realized; for example, the group call priority and the point-to-point call priority have the same authority, and for some trunking departments, the group call priority is in the It enjoys a higher priority than point-to-point calls during resource allocation;

2. The number of call priorities is limited. There are only 7 priority levels for all cluster users in the whole system, which cannot meet the priority definition requirements of different cluster departments;

3. It is impossible to realize the different requirements of different trunking departments for the priority allocation of network resources for call types.

Contents of the invention

The invention provides a method for allocating channel resources in trunking services, which is used to solve the problem in the prior art that network resource priority allocation based on call types cannot be realized. For this reason, the present invention adopts following technical scheme:

A method for allocating channel resources in a cluster service, which is applied in a cluster shared network system, wherein the cluster shared network system includes a home location register ( HLR), and the mobile switching center (MSC) that configures the cluster user information, and the base station subsystem (BSS) that allocates resources for the cluster user,

In the HLR, subscribe the virtual private network (VPN) information that the cluster user belongs to, and set each VPN call type resource allocation priority configuration table in the MSC, and the resource allocation priority of VPN to each service type is set in this configuration table;

When a cluster user initiates a cluster call, the following steps are included:

A, MSC obtains the VPN information of the group user who initiates the call through the group user ID reported by the mobile station;

B. The MSC searches the call type resource allocation priority configuration table to obtain the resource allocation priority information through the VPN information and the call type information;

C. The MSC sends a channel resource request to the BSS system, and the request carries the resource allocation priority information of the call type;

D. The BSS performs resource allocation according to the call type resource allocation priority information and the eMLPP priority information.

In the step A, the cluster subscriber identity may be an International Mobile Subscriber Identity (IMSI) or a Temporary Mobile Subscriber Identity (TMSI).

In the step A, the VPN information is the VPN information of the cluster user acquired by the MSC through the cluster user ID querying the Visitor Location Register (VLR).

In the step A, when the location of the mobile station changes, the VPN information is the VPN information refreshed by the HLR to the VLR.

In the step C, the channel resource request may include a voice group call service assignment request, a voice group call service assignment request, or a switching request.

In the step D, the resource allocation priority of the call type is higher than the eMLPP priority.

In the step D, when the resource allocation priorities of the call types are the same, resource allocation is performed according to the eMLPP priority.

The call type resource allocation priority information in the call type resource allocation priority configuration table is carried in 8-bit bytes.

In the HLR, the cluster users only sign one VPN to which they belong.

When the call initiated by the cluster user is a cross-VPN call, the call type resource allocation priority is the service priority corresponding to the VPN signed by the cluster user.

The introduction of the solution of the present invention enables different cluster departments to have different call type network resource allocation priorities for different call types in the cluster shared network system, and user allocation resources can be jointly determined based on the call type and call service, making the cluster service more flexible , The function is more complete. . For example: for the trunking department A, its call type resource allocation priority order from high to low is emergency call service=>broadcast call service=>group call service=>single call service=>duplex telephone service=>data service; For the trunking department B, the call type resource allocation priority order from high to low is emergency call service=>group call service=>single call service=>broadcast call service=>duplex telephone service=>data service.

Description of drawings

Fig. 1 is a schematic diagram of the system structure of the present invention;

FIG. 2 is a schematic flow diagram of a call initiated by a trunking user in the present invention.

Detailed ways

The specific implementation manners of the present invention will be described below in conjunction with the accompanying drawings.

As shown in Figure 1, it is a schematic structural diagram of a simplified cluster shared network system of the present invention, as can be seen from the figure, the network environment of the present invention can include:

A home location register (HLR) storing enhanced multi-level priority and preemption service (eMLPP) priority information for cluster users;

Configure the mobile switching center (MSC) of the cluster user information;

Visitor Location Register (VLR);

and a Base Station Subsystem (BSS) that allocates resources to cluster users.

Here, MSC and VLR are usually one entity physically, but they are different network elements logically, so it is not necessary to write it as MSC/VLR.

The invention signs the virtual private network (VPN) information of cluster users in the HLR, where each user signs the VPN to which he belongs in the HLR, and each user signs a VPN at the same time. For example, the VPN signed by public security personnel in the HLR can only be the VPN of the Public Security Bureau, and the VPN signed by firefighters in the HLR can only be the VPN of the Fire Department.

When the location of the mobile station changes, refresh the updated latest data to the visitor location register (VLR), including the VPN signed by the mobile station.

In addition, a resource allocation priority configuration table for each VPN call type is set in the MSC, and resource allocation priorities for each service type by the VPN are set in the configuration table. The resource allocation priority information of the above service types can be configured through the MSC maintenance console.

The present invention sets a VPN service type resource allocation priority configuration table in MSC, and this table has provided each VPN group to various service types (emergency call service, broadcast call service, group call service, single call service, duplex service) Telephone service, data service, etc.) resource allocation priority (Service Priority) value; the Service Priority value is carried by an ordinary 8-bit binary value, representing the level of service priority; the more BITs, the more the number of priorities, and vice versa .

In the present invention, the Service Priority domain is set to 8 BITs, so that 256 values can actually be obtained. In addition, the present invention can set the service of emergency call, voice group call service (VGCS), voice group call service (VBS), private call (VPCS), ordinary point-to-point call (PTP), and circuit data service (CSD) of all VPNs. The default value of Priority is 128, so that when the VPN group has special needs, the resource allocation priority can be flexibly moved up or down. Since the 8-bit binary range is 0 to 255, the default 128 represents an intermediate priority, and the specific priority can be high or low when setting, so that it can have the greatest flexibility. For example, priority offset deletion may be performed when the priority needs to be changed.

As shown in Figure 2, it is a schematic flow diagram of when a trunking user initiates a trunking call at a mobile station. As can be seen from the figure, it mainly includes the following steps:

S1. The MSC obtains the VPN information of the trunking user who initiates the call through the trunking user ID reported by the mobile station.

During the call, the MS reports the IMSI or TMSI identity information in the first full layer 3 message, and the MSC queries the VLR through the IMSI or TMSI to obtain the VPN of the call originator. VPN refresh to VLR). In the GSM-based system, the identity of the mobile station is characterized by IMSI or TMSI, which is usually carried in the first layer 3 message, so that the network side can quickly obtain the identity of the mobile station. VPN is the information registered by the user on the network side. In the HLR Storage, when the location of the mobile station is updated (when the location area changes), the HLR will refresh the relevant information of the user to the VLR, including the VPN registered by the user. Therefore, the MSC queries the VLR through the user identity information (IMSI or TMSI) Obtain the VPN information registered by the user.

S2. The MSC searches the call type resource allocation priority configuration table through the VPN information and the call type information to obtain the resource allocation priority information.

After the MSC obtains the VPN, through the VPN and the call type, query the resource allocation priority Service Priority of the call service through the service type resource allocation priority configuration table.

In the present invention, the call type can be determined according to the Setup message or the Immediate Setup message. For example, we can set the Immediate Setup of the cluster emergency call as shown in the following table:

Cell ID cell type/reference Is it necessary Format length 0x03 Protocol ID Call Control Protocol Discriminator must field value 1/2 transaction identifier transaction identifier must field value 1/2 0x0a message type message type must field value 1 half a byte free half a byte free must field value 1/2 key serial number The key serial number refers to GSM 04 08, 10 5 1 2 must field value 1/2 mobile class label Mobile station class standard 2 refers to GSM 04 08, 10 5 1 6 must length + field value 4 mobile station identity The mobile station identity refers to GSM 04 08, 10.5 1 4 must length + field value 2-9 reserve

The most critical thing here is the definition of the following domain, which determines the call type:

0x0a message type message type Required field value 1

S3. The MSC sends a channel resource request to the BSS system, and the request carries resource allocation priority information of the call type.

The MSC sends a channel resource request to the BSS system. The channel resource request includes channel resource request information such as voice group call service (VGCS) assignment request, voice group call service (VBS) assignment request, and handover request. The channel resource request message carries This call type resource allocation priority ServicePriority.

S4. The BSS performs resource allocation according to the call type resource allocation priority information and the eMLPP priority information.

BSS performs resource allocation according to Service Priority and eMLPP priority, and preempts and queues according to Service Priority and eMLPP when resources are tight. In the solution of the present invention, the ServicePriority field is set to take precedence over the eMLPP field; and when the Service Priority field value is the same, Resource allocation, preemption or queuing is performed according to the eMLPP domain value of the call priority. For example, when the channel resources in the cell are tight, an emergency call is received. If the Service Priority field of the emergency call and the ordinary point-to-point call have the same setting, the emergency call (with high eMLPP priority) will preempt the ordinary point-to-point call in the cell ( The channel resource occupied by eMLPP with low priority).

In the solution of the present invention, there is a special case processing, that is, the processing of group calls across VPN groups. When an ordinary user initiates a cross-VPN call, the Service Priority domain value of this call service takes the service priority corresponding to the VPN signed by the user, and the cross-VPN group call initiated by the cross-VPN group call administrator also uses the service priority corresponding to the VPN signed by the administrator. Service priority, if the administrator can initiate multiple cross-VPN group calls, since the service priority of these group calls is the same, the resource allocation priority for initiating cross-VPN group calls is determined by each cross-VPN group call determined by the eMLPP domain.

The introduction of the scheme of the present invention enables different cluster departments to have different call type network resource allocation priorities for different call types in the cluster shared network system, and realizes a scheme of jointly determining user allocation resources based on call types and call services. For example: for the trunking department A, its call type resource allocation priority order from high to low is emergency call service=>broadcast call service=>group call service=>single call service=>duplex telephone service=>data service; For the trunking department B, the call type resource allocation priority order from high to low is emergency call service=>group call service=>single call service=>broadcast call service=>duplex telephone service=>data service.

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

Claims (10)

1. carry out the method for channel resource allocation in the group service, be applied in the cluster common network system, described cluster common network system comprises that storing cluster user strengthens multipriority and the attaching position register HLR that seizes professional eMLPP precedence information, moving exchanging center MSC with allocation cluster user profile, and be the base station sub-system BSS of cluster user Resources allocation, it is characterized in that:

Virtual private network information under the signature cluster user in HLR, and each Virtual Private Network call resource type distribution priority allocation list is set in MSC, be provided with the priority of resource allocation of VPN in this allocation list to each type of service;

When cluster user is initiated trunked call, may further comprise the steps:

The cluster user sign that A, MSC report by travelling carriage is obtained the VPN information of the cluster user that makes a call;

B, MSC search type of call priority of resource allocation allocation list to obtain priority of resource allocation information by described VPN information and call type;

C, MSC carry this type of call priority of resource allocation information to BSS system transmitting channel resource request in this request;

D, BSS carry out resource allocation according to type of call priority of resource allocation information and eMLPP precedence information.

2. the method for claim 1 is characterized in that, in the described steps A, described cluster user sign is IMSI International Mobile Subscriber Identity IMSI or Temporary Mobile Subscriber Identity TMSI.

3. the method for claim 1 is characterized in that, in the described steps A, and described VPN information, the VPN information of the cluster user that obtains by cluster user sign inquiry VLR Visitor Location Register VLR for MSC.

4. the method for claim 1 is characterized in that, in the described steps A, and when location of mobile station changes, described VPN information, the VPN information that refreshes to VLR for HLR.

5. the method for claim 1 is characterized in that, among the described step C, described channel resource request comprises voice group call service assignment request, the assignment request of voice group call service or handoff request.

6. the method for claim 1 is characterized in that, among the described step D, described type of call priority of resource allocation is higher than eMLPP priority.

7. method as claimed in claim 6 is characterized in that, among the described step D, when the type of call priority of resource allocation is identical, carries out resource allocation according to eMLPP priority.

8. the method for claim 1 is characterized in that, the type of call priority of resource allocation information in the described type of call priority of resource allocation allocation list is carried with the byte of 8 bits.

9. the method for claim 1 is characterized in that, described cluster user is only signed the VPN under in the of in HLR.

10. method as claimed in claim 9 is characterized in that, the calling of initiating when described cluster user is when striding the calling of VPN, and described type of call priority of resource allocation is the signatory VPN corresponding service priority of this cluster user.

Images