Browse Prior Art Database

User based voice/data call pre-emption for Astro/P25 systems

IP.com Disclosure Number: IPCOM000202696D
Original Publication Date: 2010-Dec-22
Included in the Prior Art Database: 2010-Dec-22
Document File: 3 page(s) / 179K

Publishing Venue

Motorola

Related People

Seaborn, Mark: INVENTOR [+3]

Abstract

Our idea is to have the Zone Controller in the system be modified to use end-user credentials to make decisions to grant calls and to grant floor control of a current call based on an additional parameter of the validated user identity that may be ranked along side of the current method of granting calls. For example, once the user has logged into the system, they can optionally be added to the prioritization mechanism in the zone controller so that the ZC weighs the decision to grant a call based on the user?s rank against other users and talkgroups. The first embodiment adds the validation of the user?s identity to the existing logic used for Astro system talkgroup floor control: 1. The user is prompted to log into his device via a password/PIN entry or via a form of biometric identification. 2. The user?s credentials are sent to the ZC for authentication. 3. Once successfully authenticated, the ZC associates the device ID with the identity of the user in possession of the device 4. During a talkgroup call, the user may make a PTT request on the control channel, even while another member of the talkgroup is sourcing audio 5. Upon receiving the floor control request, the ZC checks the identity of the user making the request, and based on customer policy, the ZC may grant the request, even if it means preempting the current audio source. The policy check can include looking up the authorization level of the user (e.g. ACLs) or of the role the user to which the user is assigned (Role Based Access Control). The second embodiment enables user authentication to be utilized to preempt one private or group call over other calls since the identity of the user requesting the call can be determined with high assurance. 1. The user is prompted to log into his device via a password/PIN entry or via a form of biometric identification (same as above). 2. The user?s credentials are sent to the ZC for authentication (same as above). 3. Once successfully authenticated, the ZC associates the device ID with the identity of the user in possession of the device (same as above). 4. At the start of a group or private call, the ZC checks the user identity of the PTT request and sets the priority level of the call request not only via the device ID or talkgroup ID, but also on the validated user identity. Customer policy can dictate what combination and weighting of talkgroup ID and user ID is utilized to determine priority level. 5. If no channel resources are currently available for the call request, and the user?s priority level (individual level via ACLs or the user?s role via RBAC (Role Based Access Control)) warrants preemption, the ZC will preempt the currently active call with the lowest priority level. This second embodiment allows for much more flexible application of priority/preemption rules. Today?s systems only tie the priority of the call to the talkgroup associated with the call request. Now that user authentication is added to the system, the ZC can take into account the user?s priority level of the person making the call request, in combination with the talkgroup selected, or completely independent of the talkgroup selected. This capability would be important for an incident commander wishing to make important announcements on any talkgroups the commander deems appropriate, with the ZC taking the commander?s rank and RBAC rules into account for granting the call and possibly preempting other calls as needed. This will also enable the ability to dynamically promote a talkgroup to a higher priority based on the members currently affiliated to the group.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

User based voice/data call pre-emption for Astro/P25 systems

By Mark Seaborn, George Popovich, Adam Lewis

Motorola, Inc.

Enterprise

Mobility Solutions

 

ABSTRACT

The issue that was recognized previous to this publication was the need for individuals fulfilling certain public safety roles, such as an incident commander, be given privileges over other users of a network during times of crisis.

In our invention, users would identify themselves through the end subscriber and the Zone Controller would make decisions as to network access based on the user’s role and potentially the state of the system. Specifically, the Zone Controller grants priority voice and data channels to users such as commanders at incident scenes based on the individual’s role in the agency. 

PROBLEM

The problem that is being solved in this publication has to do with assuring that an individual in a critical role within a public safety organization gets access to networks in time of need.

Mission

critical communications can often mean the difference in a first responder’s ability to save lives of the general public and to protect their own lives during hazardous events. This invention allows customers to define who the set of individuals are that need priority access to the system in a priority situation.

SOLUTION

The solution is to modify the Zone Controller in the system to use end-user credentials to make decisions to grant calls and to grant floor control of a current call based on an additional parameter of the validated user identity. This parameter is used to rank individuals needs along side of the current method of granting calls. For example, once the user has logged into the system, they can optionally be added to the prioritization mechanism in the Zone Controller so that the Zone Controller weighs the decision to grant a call based on the user’s rank against other users and talkgroups. This ranking is defined as part of the customer’s policies.

OPERATION

The operational scenario works as follows. A step is added in the Zone Controller for validation of the user’s identity to the existing logic used for Astro system talkgroup floor control: 1. The user is prompted to log into his device via a password/PIN entry or via a form of biometric identification. 2. The user’s credentials are sent to the Zone Controller for authentication. 3. Once successfully authenticated, the Zone Controller associates the device ID with the identity of the user in possession of the device. 4. During a talkgroup call, the user may make a PTT request on the control channel, even while another member of the talkgroup is sourcing audio. 5. Upon receiving the floor control request, the Zone Controller checks the identity of the user making the request, and based on customer policy, the Zone Controller may grant the request, even if it means preempting the current audio source. The policy check can include looking up the...