EP3210400A1 - Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler - Google Patents

Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler

Info

Publication number
EP3210400A1
EP3210400A1 EP15851730.0A EP15851730A EP3210400A1 EP 3210400 A1 EP3210400 A1 EP 3210400A1 EP 15851730 A EP15851730 A EP 15851730A EP 3210400 A1 EP3210400 A1 EP 3210400A1
Authority
EP
European Patent Office
Prior art keywords
poc
lmr
gateway
wireless network
subscriber
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.)
Withdrawn
Application number
EP15851730.0A
Other languages
German (de)
English (en)
Other versions
EP3210400A4 (fr
Inventor
Krishnakant M. Patel
Ramu Kandula
Brahmananda R. Vempati
Pravat Kumar SINGH
Harisha M. Negalaguli
Bibhudatta Biswal
Basem Ahman ARDAH
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kodiak Networks Inc
Original Assignee
Kodiak Networks Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kodiak Networks Inc filed Critical Kodiak Networks Inc
Publication of EP3210400A1 publication Critical patent/EP3210400A1/fr
Publication of EP3210400A4 publication Critical patent/EP3210400A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • AVS PUSH-TO-TALK
  • PUSH-TO-CONFERENCE AND PUSH-TO-MESSAGE ON WIRELESS HANDSETS AND NETWORKS attorney docket number 154.13-US-U1, now U.S. Patent No. 7,738,896, issued June 15, 2010, which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Serial Number 60/573,780 (154.13-US-P1), and which application is a continuation-in-part and claims the benefit under 35 U.S.C. Sections 119, 120 and/or 365 of U.S. Utility Application Serial Number 10/515,556 (154.4-US-WO), P.C.T.
  • Vempati entitled “ENHANCED FEATURES IN AN ADVANCED VOICE SERVICES (AVS) FRAMEWORK FOR WIRELESS COMMUNICATIONS SYSTEMS," attorney docket number 154.18-US-U1, now U.S. Patent No. 7,813,722, issued October 12, 2010, which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Serial Number 60/654,271(154.18-US-Pl);
  • Velayudhan, Ramu Kandula, Syed Vietnameser Khadar, Shiva Koteshwara Kiran Cheedella, and Subramanyam Narasimha Prashanth entitled "VOICE-OVER-IP (VOIP) DENIAL OF SERVICE (DOS) PROTECTION MECHANISMS FROM ATTACK,” attorneys' docket number 154.56-WO-U1, which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Serial Number 61/818,109 (154.56-US- PI); and U.S. Provisional Application Serial Number 61/821,975 (154.56-US-P2);
  • HETEROGENEOUS NETWORKS (HETNETS) AND MULTIMODE SMALL CELL ENVIRONMENTS,” attorneys' docket number 154.60-US-U1 , which application claims the benefit under 35 U.S.C. Section 119(e) of U.S. Provisional Application Serial Number 61/948,429 (154.60-US-P1); P.C.T. International Application Serial Number PCT/US2014/047886, filed on July 23, 2014, by Gorachand Kundu, Giridhar K. Boray, Brahmananda R. Vempati, Krishnakant M. Patel, Ravi Ayyasamy, Harisha Mahabaleshwara Negalaguli, and Ramu Kandula, entitled "RADIO ACCESS NETWORK (RAN) AWARE SERVICE
  • This invention relates in general to advanced voice services in wireless communications networks, and more specifically, to a system and method for intercommunication between Land Mobile Radio (LMR) and Push-to-talk-over-Cellular (PoC) systems.
  • LMR Land Mobile Radio
  • PoC Push-to-talk-over-Cellular
  • AVS Advanced voice services
  • AVS Advanced Group Services
  • P2C Push-to-talk-over- Cellular
  • P2T Push-to-Talk
  • P2M Press-to-Talk
  • P2C Push-to-Conference
  • IC Instant Conferencing
  • P2M Push-to- Message
  • PoC packet or voice-over-IP
  • VoIP voice-over-IP
  • This approach capitalizes on the "bursty" nature of PoC conversations and makes network resources available only during talk bursts and hence is highly efficient from the point of view of network and spectral resources.
  • This approach promises compliance with newer and emerging packet-based standards, such as GPRS (General Packet Radio Service), UMTS (Universal Mobile Telecommunications System), 3G/4G/LTE (3 rd Generation/4 th Generation/Long Term Evolution), etc.
  • the present invention discloses a system and method for inter- communication between Land Mobile Radio (LMR) and Push-to-talk-over-Cellular
  • LMR Land Mobile Radio
  • PoC PoC
  • the PoC system performs a PoC call session for one or more PoC mobile units in a first wireless network, wherein the PoC call session comprises an instant two- way half-duplex voice call within a group of the PoC mobile units.
  • the LMR system performs a Push-to-Talk (PTT) call session for one or more LMR subscriber units in a second wireless network, wherein the PTT call session comprises an instant two-way half-duplex voice call within a group of the LMR subscriber units.
  • PTT Push-to-Talk
  • a network-to- network interface (NNI) gateway provides for inter-communication between the PoC system in the first wireless network and the LMR system in the second wireless network, wherein the gateway bridges the LMR system to the PoC system, such that the PoC system is exposed to the LMR system as an emulated LMR system, the LMR system is exposed to the PoC system as an emulated PoC system, and calls may be placed across the first and second wireless networks between the PoC mobile units and LMR subscriber units.
  • NNI network-to- network interface
  • the gateway creates and manages identifier mappings in order to make the PoC mobile units and their groups addressable by the LMR system, and to make the LMR subscriber units and their groups addressable by the PoC system. Specifically, the gateway exposes the LMR subscriber units and their groups to the PoC system using mobile and group identifiers of the first wireless network, and the gateway exposes the PoC mobile units and their groups to the LMR system using subscriber and group identifiers of the second wireless network.
  • the gateway may emulate an LMR system in another wireless network independent of the second wireless network.
  • one or more of the LMR subscriber units may be homed in the PoC system and visiting the LMR system.
  • the gateway may emulate a second LMR system in the second wireless network independent of the first LMR system.
  • FIG. 1 illustrates the system architecture used in one embodiment of the present invention.
  • FIG. 2 is a state diagram that illustrates the operation of a PoC session according to one embodiment of the present invention.
  • FIG. 3 is a simplified schematic based on FIG. 1 that further explains how intercommunication between the PoC system and the LMR system is accomplished by means of a network-to-network interface (NNI) Gateway that bridges the LMR system to the PoC system.
  • NNI network-to-network interface
  • FIG. 4 is a schematic that illustrates how the Gateway emulates an LMR system in a different network.
  • FIG. 5 is a schematic that illustrates how the Gateway emulates an LMR system in the same network.
  • FIG. 6 is a schematic that illustrates a Master Media Function (MMF) and Subordinate Media Function (SMF) during a unit-to-unit call.
  • MMF Master Media Function
  • SMF Subordinate Media Function
  • FIG. 7 is a call flow diagram for a unit-to-unit call originated in the LMR system.
  • FIG. 8 is a call flow diagram for a unit-to-unit call originated in the PoC system.
  • FIG. 9 is a schematic that illustrates the MMF and SMF during a group call.
  • FIG. 10 is a call flow diagram for a group call originated in the LMR system.
  • FIG. 11 is a call flow diagram for a group call originated in the PoC system.
  • the present invention discloses a system for implementing advanced voice services in wireless communications networks that provides a feature-rich server architecture with a flexible client strategy. Specifically, the present invention is directed to a Push-to-talk-over-Cellular (PoC) system that inter-communicates with a Land Mobile Radio (LMR) system.
  • PoC Push-to-talk-over-Cellular
  • LMR Land Mobile Radio
  • the PoC system disclosed herein system is an Open Mobile Alliance (OMA) standards-compliant solution that can be easily deployed, thereby enabling carriers to increase their profits, improve customer retention and attract new customers without costly upgrades to their network infrastructure.
  • OMA Open Mobile Alliance
  • This system is built on a proven, reliable all-IP (Internet Protocol) platform.
  • the highly scalable platform is designed to allow simple network planning and growth. Multiple servers can be distributed across operator networks for broad geographic coverage and scalability to serve a large and expanding subscriber base.
  • PoC Session A feature enabling a PoC User to establish a PoC Session with another
  • Ad Hoc PoC Group A PoC Group Session established by a PoC User to PoC Users listed Session on the invitation.
  • the list includes PoC Users or PoC Groups or both.
  • Controlling PoC A function implemented in a PoC Server, providing centralized PoC Function Session handling, which includes media distribution, Talk Burst
  • Firewall A device that acts as a barrier to prevent unauthorized or unwanted communications between computer networks and external devices.
  • the PoC Server of the PoC Service Provider that provides PoC service to the PoC User The PoC Server of the PoC Service Provider that provides PoC service to the PoC User.
  • Instant Personal Alert A feature in which a PoC User sends a SIP based instant message to a
  • Law Enforcement An organization authorized by a lawful authorization based on a Agency national law to request interception measures and to receive the results of telecommunications interceptions.
  • Lawful Interception The legal authorization, process, and associated technical capabilities and activities of Law Enforcement Agencies related to the timely interception of signaling and content of wire, oral, or electronic communications .
  • Notification A message sent from the Presence Service to a subscribed watcher when there is a change in the Presence Information of some presentity of interest, as recorded in one or more Subscriptions.
  • Participating PoC A function implemented in a PoC Server, which provides PoC Session Function handling, which includes policy enforcement for incoming PoC
  • the Participating PoC Function may also relay RTP Media between the PoC Client and the PoC Server performing the Controlling PoC Function.
  • PoC Client A functional entity that resides on the User Equipment that supports the PoC service.
  • Pre- Arranged PoC A SIP URI identifying a Pre- Arranged PoC Group.
  • a Pre -Arranged Group Identity PoC Group Identity is used by the PoC Client, e.g., to establish PoC
  • Pre- Arranged PoC A persistent PoC Group.
  • the establishment of a PoC Session to a Pre- Group Arranged PoC Group results in the members being invited.
  • the Pre-Established Session is a SIP Session established between the Session PoC Client and its Home PoC Server.
  • the PoC Client establishes the
  • the PoC Server conferences other PoC Servers or users to the Pre-Established Session so as to create an end-to-end connection.
  • Presence Server A logical entity that receives Presence Information from a multitude of
  • Presence Information may be composed from a multitude of Presence Sources.
  • a Presentity is most commonly a reference for a person, although it may represent a role such as "help desk” or a resource such as "conference room #27".
  • the Presentity is identified by a SIP URI, and may additionally be identified by a tel URI or a pres URI.
  • Serving Server A set of primary and secondary servers.
  • Watcher Any uniquely identifiable entity that requests Presence Information about a Presentity from the Presence Service.
  • WiFi A wireless local area network (WLAN).
  • FIG. 1 illustrates the system architecture used in the present invention. This
  • ATCA ATCA standard to support the advanced voice services of the present invention.
  • ATCA is an open standards-based, high-availability telecommunications platform architecture.
  • the PoC system 100 includes one or more PoC Service Layers 102 and one or more Management Layers 104, each of which is comprised of one or more servers interconnected by one or more IP networks 106.
  • the PoC Service Layer 102 includes one or more XML Document Management (XDM) Servers 108, Presence Servers 110, PoC Servers 112, and Media Servers 114
  • the Management Layer 104 includes one or more Element Management System (EMS) Servers 116, Lawful Intercept (LI) Servers 118, Web Customer Service Representative (WCSR) Servers 120, and Web Group Provisioning (WGP) Servers 122.
  • EMS Element Management System
  • LI Lawful Intercept
  • WCSR Web Customer Service Representative
  • WGP Web Group Provisioning
  • the PoC Service Layer 102 and Management Layer 104 are connected to one or more wireless communications networks, such as cellular phone networks 124 and wireless data networks 126, as well as one or more IP networks 106.
  • the cellular phone networks 124 and wireless data networks 126 may be implemented in a single network or as separate networks.
  • the cellular phone network 124 includes one or more Short Message Service Centers (SMSCs) 128, Mobile Switching Centers (MSCs) 130, and Base Station Components (BSCs) 132, wherein the BSCs 132 include controllers and transceivers that communicate with one or more customer handsets 134 executing a PoC Client 136.
  • SMSCs Short Message Service Centers
  • MSCs Mobile Switching Centers
  • BSCs Base Station Components
  • a handset 134 is also referred to herein as a PoC mobile unit, mobile station, mobile phone, cellular phone, etc. and may comprise any wireless and/or wired device.
  • the wireless data network 126 includes one or more Gateway GPRS Support Nodes (GGSNs) or Packet Gateways (PGWs) 136 and Serving GPRS Support Nodes (SGSNs) or Serving Gate Ways (SGWs) 138, which also communicate with PoC mobile units 134 via BSCs or eNodeBs 132.
  • GGSNs Gateway GPRS Support Nodes
  • PGWs Packet Gateways
  • SGSNs Serving GPRS Support Nodes
  • SGWs Serving Gate Ways
  • the PoC Service Layer 102 and Management Layer 104 are connected to one or more Gateways 140, which are coupled to one or more external wireless networks, such as a Land Mobile Radio (LMR) system 142.
  • LMR Land Mobile Radio
  • the LMR system 142 includes one or more Radio Frequency (RF) Sub- Systems (RFSS's) 144 that communicate with one or more LMR subscriber units 146 as well as Dispatch Consoles 148.
  • RFSS's Radio Frequency Sub- Systems
  • the Gateway 140 performs inter-communication or interworking between the PoC system 100 and the LMR system 142, as described in more detail below in Section 5.
  • the PoC Service Layer 102 interacts with the SMSC 128 on the cellular phone network 124 to handle Short Message Service (SMS) operations, such as routing, forwarding and storing incoming text messages on their way to desired endpoints.
  • SMS Short Message Service
  • the PoC Service Layer 102 also interacts with the following entities on the wireless data network 126:
  • the GGSN/PGW 136 transfers IP packets between the PoC Client 136 and the various servers:
  • bearer traffic exchange i.e., voice packets
  • the SMSC 128 handles authentication:
  • the XDM Server 108 communicates with the SMSC 128 via SMPP/IP for receiving the authentication code required for PoC Client 136 activation from the PoC mobile unit 134.
  • SMPP/IP Secure Digital Protocol
  • the PoC system 100 also has the capability to interact with PoC mobile units 134 on other IP networks (not shown), such as the Internet, as well as private or public wireless or and/or wireline IP networks.
  • IP networks not shown
  • the PoC Service Layer 102 also interacts with the following entities on other IP networks:
  • the Gateway 140 transfers IP packets between the PoC Client 136 and the various servers:
  • PoC Server 114 and PoC Client 136 for bearer traffic exchange (i.e., voice packets) for PoC call sessions.
  • bearer traffic exchange i.e., voice packets
  • the PoC Service Layer 102 is comprised of the following elements:
  • the PoC Server 112 handles the PoC call session management and is the core for managing the PoC services for the PoC Clients 136 using SIP protocol.
  • the PoC Server 112 implements a Control Plane portion of Controlling and Participating PoC Functions.
  • a Controlling PoC Function acts as an arbitrator for a PoC Session and controls the sending of control and bearer traffic by the PoC Clients 136.
  • a Participating PoC Function relays control and bearer traffic between the PoC Client 136 and the PoC Server 112 performing the Controlling PoC Function.
  • the Media Server 114 implements a User Plane portion of the Controlling and Participating PoC Functions.
  • the Media Server 114 supports the Controlling PoC Function by duplicating voice packets received from an originator PoC Client 136 to all recipients of the PoC Session.
  • the Media Server 114 also supports the Participating PoC Function by relaying the voice packets between PoC Clients 136 and the Media Server 114 supporting the Controlling PoC Function.
  • the Media Server 114 also handles packets sent to and received from the PoC Clients 136 for floor control during PoC call sessions.
  • the Presence Server 110 implements a presence enabler for the PoC Service.
  • Presence Server 110 accepts, stores and distributes Presence Information for Presentities, such as PoC Clients 136.
  • the Presence Server 110 also implements a Resource List Server (RLS), which accepts and manages subscriptions to Presence Lists.
  • Presence Lists enable a "watcher" application to subscribe to the Presence Information of multiple Presentities using a single subscription transaction.
  • the Presence Server 1 10 uses certain XDM functions to provide these functions, which are provided by XDM Server 108. 2.4.4 XDM Server
  • the XDM Server 108 implements an XDM enabler for the PoC Service.
  • the XDM enabler defines a common mechanism that makes user-specific service-related information accessible to the functions that need them. Such information is stored in the XDM Server 108 where it can be located, accessed and manipulated (e.g., created, changed, deleted, etc.).
  • the XDM Server 108 uses well-structured XML documents and HTTP protocol for access and manipulation of such XML documents.
  • the XDM Server 108 also connects to the operator SMSC 128 for the purposes of PoC Client 136 activation using SMS. In addition, the XDM Server 108 maintains the configuration information for all PoC subscribers. 2.4.5 Gateway
  • the Gateway 140 implements an inter-communication or interworking solution for the PoC Service to communicate via one or more LMR systems 142. Specifically, the Gateway 140 provides PoC Service to the LMR system 142, and supports a seamless user experience while the transport of IP control messages and IP voice data is transitioned between the PoC system 100 and the LMR system 142. The Gateway 140 also resolves security concerns that arise with such inter-communication or interworking solutions. These and other aspects of the inter-communication or interworking solution are described in more detail below in Section 5.
  • Management Layer 104 is comprised of the following elements:
  • the EMS Server 116 is an operations, administration, and maintenance platform for the PoC system 100.
  • the EMS Server 116 enables System Administrators to perform system-related configuration, network monitoring and network performance data collection functions.
  • the EMS Server 116, or another dedicated server, may also provide billing functions. All functions of the EMS Server 116 are accessible through a web- based interface. 2.5.2 LI Server
  • the LI Server 1 18 is used for tracking services required by various Lawful Enforcement Agents (LEAs).
  • LSAs Lawful Enforcement Agents
  • the LI Server 118 generates and pushes an IRI (Intercept Related Information) Report for all PoC Services used by a target.
  • the target can be added or deleted in to the PoC Server 112 via the LI Server 1 18 using a Command Line Interface (CLI).
  • CLI Command Line Interface
  • the WGP Server 122 provides a web interface for Corporate Administrators to manage PoC contacts and groups.
  • the web interface includes contact and group management operations, such as create, delete and update contacts and groups.
  • the WCSR Server 120 provides access to customer service representatives (CSRs) for managing end user provisioning and account maintenance.
  • CSRs customer service representatives
  • the PoC Server 112 controls PoC call sessions, including 1-1, Ad Hoc and Pre- Arranged PoC call sessions.
  • the PoC Server 112 also controls Instant Personal Alerts.
  • the PoC Server 112 expects the PoC Clients 136 to setup "pre-established sessions" at the time of start up and use these sessions to make outgoing PoC calls.
  • the PoC Server 112 also uses pre-established sessions to terminate incoming PoC calls to the PoC Clients 136.
  • the PoC Clients 136 are setup in auto-answer mode by default. The use of pre-established sessions and auto-answer mode together allow for faster call setup for PoC call sessions.
  • the PoC Server 112 allocates and manages the media ports of the Media Services
  • the PoC Server 112 associated with each SIP INVITE dialog for pre-established sessions and controls the Media Servers 114 to dynamically associate these ports at run time for sending RTP packets during PoC call sessions.
  • Media ports are assigned and tracked by the PoC Server 112 at the time of setting up pre-established sessions.
  • the PoC Server 112 instructs the Media Server 114 to associate the media ports of various subscribers dynamically into a session when a PoC call is originated and this session is maintained for the duration of the call.
  • the PoC Server 112 also controls the floor states of the various participants in a PoC call session by receiving indications from the Media Servers 114 and sending appropriate requests back to the Media Servers 114 to send MBCP messages to the participants in the PoC call.
  • the Media Server 114 uses the media ports association and current talker information to send the RTP packets from the talker's media port onto the listeners' media ports.
  • the PoC Server 112 handles the incoming and outgoing Instant Personal Alerts (IP As) by routing SIP MESSAGE requests to the PoC Clients 136 and remote PoC Servers 112 for final delivery as applicable.
  • IP As Instant Personal Alerts
  • the PoC Server 112 uses static and dynamic data related to each subscriber to perform these functions.
  • Static data include subscriber profile, contacts and groups.
  • Dynamic data include the subscriber's registration state, PoC settings and SIP dialog states are maintained only on the PoC Server 112.
  • the Media Server 114 handles the flow of data to and from the PoC Clients 136 as instructed by the PoC Server 112. Each Media Server 114 is controlled by a single PoC Server 112, although multiple Media Servers 114 may be controlled by a PoC Server 112 simultaneously.
  • the Media Server 114 is completely controlled by the PoC Server 112. As noted above, even the media ports of the Media Server 114 are allocated by the PoC Server 112 and then communicated to the Media Server 114. Likewise, floor control requests received by the Media Server 114 from PoC Clients 136 are sent to the PoC Server 112, and the PoC Server 112 instructs the Media Server 114 appropriately. Based on these instructions, the Media Server 114 sends floor control messages to the PoC Clients 136 and sends the RTP packets received from the talker to all the listeners.
  • the Presence Server 110 accepts presence information published by PoC Clients 136, as well as availability information received from other entities.
  • the Presence Server 110 keeps track of these presence states and sends notifications to various "watcher" applications whenever a presence state changes.
  • the Presence Server 110 maintains separate subscriptions for each watcher and dynamically applies the presence authorization rules for each watcher independently.
  • the Presence Server 110 also accepts resource list subscriptions from the watchers, which identify one or more entities ("Presentities") whose presence should be monitored. The Presence Server 110 then aggregates all the presence information into one or more presence notifications transmitted to each watcher. This allows watchers to subscribe to large number of Presentities without putting strain on the network as well as client and server resources.
  • Presentities entities whose presence should be monitored.
  • the Presence Server 110 then aggregates all the presence information into one or more presence notifications transmitted to each watcher. This allows watchers to subscribe to large number of Presentities without putting strain on the network as well as client and server resources.
  • the XDM Server 108 performs client authentication and subscription functions.
  • the XDM Server 108 also stores subscriber and group information data.
  • the XDM Server 108 also interacts with the SMSC 128 to receive PoC Client 136 activation commands.
  • All subscriber provisioning and CSR operations in the XDM Server 108 are performed through the WCSR Server 120, while corporate administrative operations, as well as contacts and group management, are handled through the WGP Server 122.
  • the XDM Server 108 includes a Subscriber Profile Manager module that provides subscriber management functionality, such as creation, deletion and
  • the subscriber profile includes data such as the MDN, subscriber name, subscriber type, etc. This also determines other system-wide configurations applicable for the subscriber including the maximum number of contacts and groups per subscriber and the maximum number of members per group.
  • the XDM Server 108 includes a Subscriber Data Manager module that manages the subscriber document operations, such as contact and group management operations, initiated by the PoC Clients 136 or the WGP Server 122.
  • Subscriber Data Manager module that manages the subscriber document operations, such as contact and group management operations, initiated by the PoC Clients 136 or the WGP Server 122.
  • the EMS Server 116 is the central management entity in the system and includes the following modules:
  • corresponding client provides a user interface for viewing fault, configuration, performance and security information.
  • the WCSR Server 120 provides a web user interface for customer service representatives (CSRs) to carry out various operations.
  • the web user interface provides access to CSRs for managing subscriber provisioning and account maintenance.
  • the WGP Server 122 allows provides for central management of all corporate subscribers and associated contacts and groups within a corporation.
  • the WGP Server 122 allows Corporate Administrators to manage contacts and groups for corporate subscribers.
  • the WGP Server 122 includes a Corporate Administration Tool (CAT) that is used by Corporate Administrators to manage contacts and groups of corporate subscribers.
  • CAT Corporate Administration Tool
  • the CAT has a Web User Interface for Corporate Administrators that supports the following operations:
  • the CAT of the WGP Server 122 includes the following operations:
  • the CAT of the WGP Server 122 includes the following operations:
  • N contacts may be members of N groups
  • the CAT of the WGP Server 122 includes the following operations:
  • Phone list management e.g., NxN contact add
  • the PoC Client 136 is an OMA-compatible client application executed on a PoC mobile unit 134.
  • the following features are supported by the PoC Client 136: • PoC Calls and Instant Personal Alert,
  • the PoC Client 136 includes a database module, a presence module, an XDM module and a client module.
  • the database module stores configuration information, presence information, contact and group information, user settings, and other information in an optimized and persistent way. Information is preserved when the user unregisters with the PoC Server 112 or power cycles the device.
  • the database module also has a mechanism to reset the data and synchronize from the XDM Server 108 when the data in the database module is corrupt or unreadable.
  • the presence module creates and maintains the presence information for the subscriber. Typically, the presence information supports Available, Unavailable and Do- not-Disturb (DnD) states.
  • the presence module also subscribes to the Presence Server 110 as a "watcher" of all contacts in the PoC mobile unit 134 and updates the user interface of the PoC mobile unit 134 whenever it receives a notification with such presence information.
  • the XDM module communicates with the XDM Server 108 for management of contacts and groups.
  • the XDM module may subscribe with the XDM Server 108 to send and receive any changes to the contacts or group list, and updates the user interface of the PoC mobile unit 134 based on the notifications it receives from the XDM Server 108.
  • the client module provides the most important function of making and receiving PoC calls. To support PoC calls, the client module creates and maintains pre-established sessions with the PoC Server 112. The client module supports 1-1, Ad Hoc and Pre- Arranged PoC calls. The client module also supports sending and receiving Instant Personal Alerts (IP A). 4 State Diagram for a PoC Call Session
  • FIG. 2 is a state diagram that illustrates the operation of a PoC call session in the PoC system 100 according to one embodiment of the present invention.
  • State 200 represents a PoC Client 136 in a NULL state, i.e., the start of the logic.
  • a transition out of this state is triggered by a user making a request to originate a PoC call, or by a request being made to terminate a PoC call at the PoC mobile unit 134.
  • a request to originate a PoC call is normally made by pressing a PoC button, but may be initiated in this embodiment by dialing some sequence of one or more numbers on the PoC mobile unit 134 that are interpreted by the PoC Server 112, by pressing one or more other keys on the PoC mobile unit 134 that are interpreted by the PoC Server 112, by speaking one or more commands that are interpreted by the PoC Server 112, or by some other means.
  • State 202 represents the PoC Client 136 in an active group call state, having received a "floor grant" (permit to speak).
  • the user receives a chirp tone that indicates that the user may start talking.
  • the user responds by talking on the PoC mobile unit 134.
  • the PoC mobile unit 134 uses the reverse traffic channel to send voice frames to the Media Server 114, and the Media Server 114 switches voice frames only in one direction, i.e., from talker to one or more listeners, which ensures the half-duplex operation required for a PoC call.
  • State 204 represents the group "floor" being available to all members of the group.
  • the signal to release the floor is normally made by releasing the PoC button, but may be performed in this embodiment by voice activity detection, e.g., by not speaking for some time period (which is interpreted by the PoC Server 112 as a release command). All members of the group receive a "free floor” tone on their PoC mobile unit 134.
  • a user who requests the floor first (in the "free-floor” state), for example, is granted the floor, wherein the PoC system 100 sends a chirp tone to the successful user.
  • the signal to request the floor is normally made by pressing the PoC button, but may be performed in this embodiment by voice activity detection, e.g., by speaking for some time period (which is interpreted by the PoC Server 112 as a request command).
  • State 206 represents the PoC Client 136 being in an active group call state. In this state, the user is listening to the group call. If a non-talking user requests the floor in the active group call state, the user does not receive any response from the PoC system 100 and remains in the same functional state.
  • the signal to request the floor is normally made by pressing the PoC button, but may be performed in this embodiment by voice activity detection, e.g., by speaking for some time period (which is interpreted by the PoC Server 112 as a request command).
  • State 208 represents a user receiving an "unsuccessful bidding" tone on his PoC mobile unit 134, after the user has requested the floor, but was not granted the floor, of the group call. The user subsequently listens to the voice message of the talking user.
  • Non-talking users can request the PoC system 100 to end their respective call legs explicitly.
  • State 210 represents a terminating leg being released from the call after the user ends the call.
  • State 212 also represents a terminating leg being released from the call after the user ends the call.
  • State 214 represents all terminating legs being released from the call when no user makes a request for the within a specified time period, or after all users have ended their respective call legs. 5 Inter-communication between the LMR and PoC Systems
  • LMR systems serve a large segment of users.
  • This invention describes an implementation for the Gateway 140 that enables the PoC system 100 to connect with the LMR system 142 for the provision of 1-on-l as well as group calls between the systems 100, 142.
  • FIG. 3 is a simplified schematic based on FIG. 1 that further explains how interworking or inter-communication between the PoC system 100 and the LMR system 142 is accomplished by the Gateway 140 that bridges the LMR system 142 to the PoC system 100. Specifically, the Gateway 140 causes the PoC system 100 to be exposed to the LMR system 142 as an emulated LMR system, and causes the LMR system 142 to be exposed to the PoC system 100 as an emulated PoC system. These functions of the Gateway 140 described in more detail below.
  • the Gateway 140 increases the interface options for both the PoC system 100 and the LMR system 142. As a result, the use of the Gateway 140 to bridge the PoC system 100 and the LMR system 142 should increase user adoption and reduce user churn in both systems 100, 142. Moreover, Gateway 140 offers standards-based interfaces that extend the features of both systems 100, 142. 5.2 Project 25 (P25 Description
  • the LMR system 142 is based on the Project 25 (P25) standard.
  • P25 Project 25
  • the P25 standard was developed for public safety wireless networks by the Association of Public Safety Communications Officials (APCO) in conjunction with the Telecommunications Industry Association (TIA).
  • API Association of Public Safety Communications Officials
  • TIA Telecommunications Industry Association
  • other types of standards, wireless networks and/or systems may benefit from the present invention as well.
  • the LMR system 142 is comprised of at least one base station, known as a Radio Frequency (RF) Sub-System (RFSS) 144, that connects via an air interface to one or more portable radios or other mobile devices, known as LMR subscriber units (SUs) 146.
  • RFSS Radio Frequency Sub-System
  • SUs LMR subscriber units
  • An Inter-RF Sub-System Interface (ISSI) is used to connect different RFSS's 144 together to form a larger wireless network with a larger coverage area.
  • Other peripherals may be attached to the RFSS's 144, such as a Dispatch Console 148 connected by means of a Console Sub-System Interface (CSSI).
  • CCSSI Console Sub-System Interface
  • the LMR system 142 can perform a group PTT call among the LMR subscriber units 146, i.e., a call in which one member of a group can speak to all other members simultaneously. For example, all police officers on patrol could constitute one group.
  • a floor control mechanism is used to arbitrate who should speak in the event two and more members request to speak at the same time.
  • a PTT user who wants to speak to the group will push a button on their LMR subscriber unit 146.
  • a message would then be sent to the RFSS 144, which arbitrates all the talk requests and either grants or denies each request by sending a response back to the requesters.
  • a collection of one or more LMR systems 142 is uniquely identified by a Wide Area Communication Network (WACN) ID as a separate and independent wireless network.
  • WACN Wide Area Communication Network
  • Each LMR system 142 which is a collection of one or more RFSS's 144 across a defined coverage area, is uniquely identified by its combined WACN ID and System ID.
  • each RFSS 144 is uniquely identified by its combined WACN ID, System ID and RFSS ID.
  • PoC mobile units 134 are identified by MDNs and Group IDs.
  • LMR subscriber units 146 are identified by subscriber IDs (SU-IDs) and subscriber group IDs (SG-IDs).
  • the Gateway 140 creates and manages ID mappings in order to make PoC mobile units 134 and their groups addressable by the LMR system 142, and to make LMR subscriber units 146 and their groups addressable by the PoC system 100.
  • the Gateway 140 exposes PoC mobile units 134 and their groups to the LMR system 142 using pseudo-SU-IDs and pseudo-SG-IDs, and exposes LMR subscriber units 146 and their groups to the PoC system 100 using pseudo-MDNs and pseudo-Group IDs.
  • the Gateway 140 enables the PoC mobile units 134 of the PoC system 100 to communicate with the LMR system 142 using ISSI/CSSI.
  • the PoC system 100 is connected to the Gateway 140 through a PoC NNI, and this allows the PoC system 100 to be insulated from the different variants of the ISSI/CSSI protocols that may be used between the Gateway 140 and various LMR systems 142.
  • ISSI is an open interface that can connect RFSS's 144 within and among LMR systems 142 in the same or different WACNs via dedicated links or a VPN. ISSI is used to pass voice and call data between systems. ISSI relies on standard IP protocols for voice transport, using Realtime Transport Protocol (RTP), and call signaling, using Session Initiation Protocol (SIP).
  • RTP Realtime Transport Protocol
  • SIP Session Initiation Protocol
  • CSSI is used for interfacing an RFSS 144 with a Dispatch Console 148. CSSI is the same as ISSI with minor extensions for supporting some console specific use cases.
  • ISSI supports authentication and registration of roaming LMR subscriber units 146.
  • ISSI allows LMR subscriber units 146 from network A to operate under the coverage of network B assuming the same frequency band. This includes the capability for network A to track and control its LMR subscriber units 146 when they are under the coverage of network B and to dynamically include them in individual and group calls with no loss of features (including PTT and trunking). It also gives network B control of visiting LMR subscriber units 146 based on inter-agency agreements.
  • the ISSI architecture is based on the concept of a "home” and a "serving" RFSS 144.
  • the home RFSS 144 represents the normal location and radio coverage area under which a particular LMR subscriber unit 146 and their group operate.
  • a serving RFSS 144 represents a foreign location and radio coverage area to which the LMR subscriber unit 146 has roamed.
  • a general principle of ISSI is to be "home oriented," which means that any decision regarding LMR subscriber units 146, groups and calls is taken by the home RFSS 144.
  • Mobility management procedures in ISSI allow an LMR subscriber unit 146 to access services outside of its home RFSS 144.
  • these procedures allow a group to be expanded outside of its home RFSS 144.
  • An LMR subscriber unit 146 moving outside its home RFSS 144 radio coverage will be able to register with the group it is interested in when within the radio coverage of the serving RFSS 144 (assuming compatible radio frequencies), according to a mutual agreement between networks.
  • the serving RFSS 144 to which the LMR subscriber unit 146 has roamed has the responsibility to inform the home RFSS 144 of the new location of the LMR subscriber unit 146.
  • the home RFSS 144 of the LMR subscriber unit 146 updates their databases, so that the networks know where the LMR subscriber unit 146 is located when there is a need to connect a call to the LMR subscriber unit 146.
  • Call control procedures define unit-to-unit calls and group calls using the RFSS's
  • a unit-to-unit call can be set-up dynamically between any two LMR subscriber units 146 that can be each located at their home RFSS 144 or at any serving RFSS 144.
  • the unit-to-unit call is managed by the home RFSS 144 of the calling party and will involve the home RFSS 144 of the called party and the serving RFSS's 144 where each LMR subscriber unit 146 is registered.
  • a group call can be set-up over several RFSS's 144, based on the registrations to that group that have been requested by any serving RFSS 144, and using Mobility Management procedures. Following the "home oriented" principle of the ISSI, the group call is handled by the home RFSS 144 of the group.
  • the call control procedures rely mainly on SIP methods for session initiation (SIP
  • the associated RTP session to support the voice media flows is negotiated, set up and torn down together with the SIP session.
  • PTT management procedures allow for the control of the RTP voice media transmission between the RFSS's 144 involved in a voice call.
  • the PTT management procedures including state behaviors and arbitration rules, are applied by a Master Media Function (MMF) and Subordinate Media Function (SMF).
  • MMF Master Media Function
  • SMF Subordinate Media Function
  • the MMF For a group call, the MMF is located at the home RFSS 144 of the group and the SMFs are located at the serving RFSS's 144. For a unit-to-unit call, the MMF is located at the home RFSS 144 of the called party and the SMFs are located at the serving RFSS's 144.
  • the present invention provides several interoperability models for the PoC system 100 and LMR system 142.
  • the Gateway 140 emulates an LMR system (identified as "System ID 1") in an independent WACN (identified as “PoC WACN").
  • the actual LMR system 142 (identified as “System ID 1") is in a different WACN
  • the Gateway 140 exposes the PoC system 100 to the LMR system 142 as a separate peer WACN.
  • the PoC mobile units 134, LMR subscriber units 146, and their groups, can span both the PoC WACN and P25 WACN. For example, calls can be placed across the PoC WACN and P25 WACN to both PoC mobile units 134 and LMR subscriber units 146. 5.4.2 Subscribers in the LMR System as Subscribers in the PoC WACN
  • one or more of the LMR subscriber units 146 operating in the P25 WACN are configured as being "homed" in the PoC WACN. Specifically, one or more of the LMR subscriber units 146 in the P25 WACN are considered to be visiting the P25 WACN, wherein the RFSS 144 in the P25 WACN registers with the PoC WACN as a serving RFSS 144 for the LMR subscriber units 146 homed in the PoC WACN. These LMR subscriber units 146 homed in the PoC WACN are exposed to the PoC system 100 using pseudo-MDNs.
  • the Gateway 140 emulates an LMR system
  • the Gateway 140 emulates a serving RFSS belonging to the same P25 WACN.
  • One or more of the PoC mobile units 134 in the PoC system 100 are assigned pseudo-SU-IDs for the P25 WACN and are homed in one of the RFSS's 144 in the P25 WACN. These PoC mobile units 134 are considered to be visiting the Gateway 140 in the PoC system 100, and the Gateway 140 registers as the serving RFSS for the pseudo-SU-IDs and pseudo-SG-IDs assigned to these PoC mobile units 134. 5.4.4 Gateway Interoperability
  • the Gateway 140 not only handles 1-to-l calls and group calls between the PoC system 100 and the LMR system 142 by means of a Gateway (GW) function, but also provides Gateway Management Server (GWMS) and Gateway Registrar (GR) functions.
  • GW Gateway Management Server
  • GR Gateway Registrar
  • the Gateway function performs the following:
  • PoC NNI Uses PoC NNI for call signaling with the PoC Server 112, which is based on SIP protocol in one of the embodiments.
  • the Gateway Management Server function performs the following:
  • the Gateway Registrar function performs the following:
  • the Gateway function provides interfaces between the PoC system 100 and LMR system 142. As noted above, ISSI and CSSI protocols are used by the Gateway function for 1-1 and group voice calls with peer LMR systems 142.
  • the PoC NI is used between the Gateway function and the PoC Server 112 for 1-1 and group voice calls involving LMR system 142 subscribers and groups.
  • the Gateway function bridges between the PoC NNI and ISSI/CSSI protocols.
  • the Gateway Management function provides for system and Corporate
  • a System Administrator accesses the Gateway Management Server function to:
  • a Corporate Administrator accesses the Gateway Management Server function to
  • the XDM Server 108 accesses the Gateway Management Server function to exchange information about imported/exported subscribers and groups in order to update databases on both the PoC system 100 and LMR system 142.
  • the Gateway Registrar function accesses the Gateway Management Server function to provide notifications when subscribers and/or groups are imported and/or exported.
  • the Gateway Registrar function uses this information to initiate and/or terminate registration related dialogs.
  • the Gateway function also accesses the Gateway Management Server function to query for routing configurations and subscriber/group ID mappings.
  • the Gateway Registrar function provides an interface for the Gateway function for managing SIP registrations as part of IS SI mobility management functions. This information is used by the Gateway function for receiving and/or originating call segments for group calls involving the LMR system 142.
  • the Corporate Administration Tool (CAT) of the WGP Server 122 is used by Corporate Administrators to manage contacts and groups of corporate subscribers.
  • the CAT has a Web User Interface for Corporate Administrators that supports the following operations:
  • the PoC system 100 provides an XCAP interface between PoC Clients 136 and the XDM Server 108 enables the PoC Clients 136 to present LMR system 142 subscribers and groups to users on the PoC mobile units 134.
  • Identity mappings to make the subscriber and groups of the respective systems routable to each other are configured through the management interfaces.
  • Pseudo-MDN pools also known as the PoC NNI MDN pools, are first provisioned and then these pseudo-MDNs are mapped to actual LMR system 142 subscribers and groups.
  • An NNI Data Management function of the Gateway 140 includes the following: 1. PoC NNI Account Management (P AM) .
  • a PoC Gateway Account enables a corporate account to use PoC service with contacts and groups spanning multiple heterogeneous PoC/LMR systems.
  • the PoC Gateway Account must be created through the provisioning system and the PoC corporate account instances on various PoC systems 100 should be linked to the PoC Gateway Account.
  • the PoC Gateway Account may be linked to corporate accounts from more than one PoC system 100.
  • PoC NNI MDN Once a PoC system 100 corporate account is linked to a PoC Gateway Account, pseudo-MDNs provisioned on that corporate account can be mapped to external subscribers and groups through the Gateway 140. 5.5.1.1 PoC NNI MDN
  • pseudo-MDN pools In order to make non-PoC subscribers and groups addressable to the PoC system 100 users, one or more pseudo-MDN pools must be specifically provisioned for each corporate account. The pseudo-MDNs in this pool are then mapped to specific types of external subscribers and groups by the Gateway 140. A pseudo-MDN that is used for mapping to external subscribers and groups in this manner are referred to as a "PoC NNI MDN”. Further, a pseudo-MDN that is associated with an external subscriber is referred to as a "PoC NNI Alias MDN" and a pseudo-MDN associated with an external group is referred to as a "PoC NNI Group MDN".
  • PoC NNI MDNs are typically provisioned as PoC pseudo-MDN pools through the PAM and they appear as part of the corporate account master list on the CAT.
  • a Corporate Administrator using the CAT can perform the following operations with PoC NNI MDNs:
  • the PoC pseudo-MDN pools created though the provisioning system are identified by specific types.
  • the pseudo-MDN type governs the data management operations permitted for that pseudo-MDN.
  • the following two types of pseudo-MDNs are required for supporting the PoC NNI with the LMR system 142.
  • the PoC NNI MDN pools used for inter-operability with the LMR system 142 should be provisioned through PAM with these client types.
  • LMR Subscriber Unit (SU).
  • the LMR Subscriber Unit client type is used for making external LMR subscribers addressable to the PoC system 100 users.
  • LMR Subscriber Group (SG).
  • An LMR Subscriber Group MDN is similar to the existing PoC Donor Radio (inter-operability) client type. It is used for linking PoC groups with external LMR Groups in order to facilitate creation of groups spanning both the PoC system 100 and the LMR system 142.
  • An LMR Subscriber Group MDN is added to the PoC Group as a group member and it is mapped to a LMR Group on the Gateway 140.
  • a pool of LMR SG type subscribers shall be provisioned through PAM and each MDN in this pseudo-MDN pool will be mapped in this manner to a LMR Group. 5.5.2 User Roles in the Interworking of the PoC System to the LMR System
  • a Gateway Account is created and managed through a Gateway System
  • the Gateway System Administrator interface configures the following as part of the account:
  • the System Administrator may optionally use the functions available to a Corporate Administrator on the PoC system 100 to export and/or import contacts and groups across the systems 100, 142.
  • a Corporate Administrator on the PoC system 100 uses the Gateway
  • Each PoC Client 136 presents LMR system 142 contact and group details to the user on the PoC mobile unit 134, and the user can make and/or receive calls using these LMR system 142 contacts and groups.
  • the Gateway function exposes the PoC system 100 with a WACN ID to LMR systems 142 that support ISSI/CSSI.
  • the Gateway function can be setup to serve multiple PoC systems 100, which may include the following:
  • the WACN ID assigned to the PoC system 100 may be mapped to "Carrier ID + Instance Number" or it may be assigned the same WACN ID as the LMR system 142.
  • each LMR system 142 can serve up to 16M SU-IDs and up to 64K SG-IDs. Hence, depending on number of PoC groups exported to external LMR systems 142, one or more System-IDs need to be added under each WACN-ID.
  • a System-ID When a System-ID is added to PoC system 100, it is associated with a new emulated PoC Server 112 instance in the PoC system 100.
  • the emulated PoC Server 112 that is associated with the System-ID is a logical function and need not have a physical manifestation. 5.5.3.3 Assigning RFSS IDs to the PoC System
  • Each System-ID is normally associated with one or more RFSS's 144 and/or Dispatch Consoles 148. However, in case of a System-ID under a PoC system 100, one and only one RFSS 144 is required. A fully qualified identifier for the RFSS 144 is of the form RFSS-ID.System-ID.WACN-ID. Therefore, an RFSS-ID is assigned to the PoC system 100 as described below:
  • RFSS-ID hardcoded to "01" since there is only one instance of an RFSS 144 (emulated by the Gateway 140) for each System-ID associate with a PoC system 100.
  • System-ID an ID associated with the PoC Server 112 of the PoC system 100 connected with the LMR system 142.
  • WACN-ID as provisioned in the Gateway function by a System
  • Network interface details (such as an IP address, VPN details, etc.) are configured for each RFSS 144 in the PoC system 100.
  • the same IP interface may be used for multiple RFSS's 144 in the PoC system 100.
  • External LMR systems 142 can reach the PoC system 100 through this interface.
  • the Gateway Account is homed in an RFSS 144 under one of the PoC systems 100.
  • Adding a PoC subscriber to the Gateway Account exposes the subscriber to the LMR system 142.
  • a pseudo-SU-ID is assigned to that subscriber.
  • the pseudo-SU-ID assigned to the subscriber is of the form " ⁇ WACN-ID> ⁇ System-ID> ⁇ Unit-ID>, where:
  • WACN-ID as provisioned in the Gateway function by the System
  • System-ID an ID associated with the PoC Server 112 of the PoC system 100 connected with the LMR system 142.
  • Unit-ID 6 hex-digit ID, unique with the scope of the RFSS 144 of the
  • the SU-ID of the PoC subscriber is considered homed in the RFSS 144 of the PoC system 100.
  • Adding a PoC group to the Gateway Account exposes the group to the LMR system 142.
  • the Corporate Administrator can add LMR subscribers as group members to PoC groups that are exported through the Gateway function.
  • a pseudo-SG-ID is assigned to the PoC Group.
  • System-ID an ID associated with the PoC Server 112 of the PoC system 100 connected with the LMR system 142.
  • Unit-ID 4 hex-digit ID, unique with the scope of the RFSS 144 of the PoC system 100.
  • the SG-ID of the PoC group is considered homed in the RFSS 144 of the PoC system 100.
  • mappings required to expose the LMR system 142 as an emulated PoC system 100 This allows the LMR subscribers and groups to be visible from to the PoC system 100.
  • the RFSS 144 of the LMR system 142 must first be added to the Gateway Account.
  • An RFSS 144 may be added to multiple Gateway Accounts.
  • An LMR subscriber is imported into the PoC system 100 by adding the SU-ID of the LMR subscriber into a Gateway Account.
  • the LMR subscriber is assigned a pseudo- MDN when added to the Gateway Account.
  • a different pseudo-MDN is assigned to the LMR subscriber in each account when it is added to multiple accounts.
  • the Corporate Administrator may perform the following:
  • An LMR group is imported into the PoC system 100 by adding the SG-ID of the LMR group into a Gateway Account.
  • the LMR group is assigned a pseudo-Group URI when it added to the Gateway Account.
  • a different pseudo-Group URI is assigned to the LMR group in each account when it is added to multiple accounts.
  • the Corporate Administrator may perform the following:
  • the LMR system 142 In order to enable communication between the PoC system 100 and the LMR system 142, the LMR system 142 must be provisioned in the Gateway function.
  • the "WACN-ID+System-ID” is mapped to the IP interface for routing SIP messages towards the LMR system 142. This is an optimal configuration and can be used when there is only one RFSS 144 in the LMR system 142, or where there is an ingress SIP Gateway in the LMR system 142 that handles the routing based on subscriber/group SIP URIs. 5.5.4.2.2 RFSS Level Routing
  • the "WACN-ID+System-ID+RFSS-ID” is mapped to the IP interface for routing SIP messages towards a specific RFSS 144 in the LMR system 142. This requires the Gateway function to look up LMR subscribers for their mapping from SIP URI to the RFSS 144 in the LMR system 142, in order to identify the destination RFSS 144.
  • PoC subscribers and LMR subscribers can communicate with each other using one of the methods described below:
  • a PoC subscriber can use a PoC Client 136 to call LMR subscriber units 146, as well as Dispatch Consoles 148, by dialing the corresponding Pseudo-MDN associated with the LMR subscriber unit 146 or Dispatch Console 148.
  • the LMR subscriber unit 146 or the Dispatch Console 148 will perceive the calling party identity as the Pseudo-SU-ID that is associated with the PoC Client 136.
  • An LMR subscriber unit 146 or Dispatch Console 148 can call a PoC Client 136 by dialing the Pseudo-SU-ID associated with the PoC Client 136.
  • the PoC Client 136 will perceive the calling party identity as the Pseudo-MDN that is associated with the LMR subscriber unit 146 or Dispatch Console
  • a PoC subscriber can use a PoC Client 136 to call LMR subscriber units 146, as well as Dispatch Consoles 148, by dialing the SU-ID of the LMR subscriber unit 146 or Dispatch Console 148.
  • the LMR subscriber unit 146 or the Dispatch Console 148 will perceive the calling party identity as the Pseudo- SU-ID that is associated with the PoC Client 136.
  • An LMR subscriber unit 146 or Dispatch Console 148 can call a PoC Client 136 by dialing the Pseudo-SU-ID associated with the PoC Client 136.
  • the PoC Client 136 will perceive the calling party identity as the SU-ID of the LMR subscriber unit 146 or the Dispatch Console 148.
  • the originating PoC Server 112 performs the role of controlling PoC in a unit-to-unit call.
  • the terminating PoC Server 112 is modified to act as a Master Media Function (MMF) and take the role of Controlling PoC Function during a unit-to-unit call between a PoC mobile unit 134 and an LMR subscriber unit 146.
  • FIG. 6 illustrates the MMF and Subordinate Media Function (SMF) participation during an unit-to-unit call where the PoC Server 112 is acting as an MMF
  • the PoC Server 112 takes a role of a controlling function.
  • the Gateway 140 translates the message to a corresponding mapped SIP message towards the PoC system 100, and fills in the necessary information required for the PoC system 100.
  • the Gateway 140 acts as a back-to-back user agent (B2BUA) for a call between the two systems 100, 142, and maintains two different dialogs from each system 100, 142.
  • B2BUA back-to-back user agent
  • a LMR subscriber unit 146 in the LMR system 142 calls an SU-ID that is mapped to an MDN for the PoC mobile unit 134 in the Gateway 140, and the request is forwarded to the appropriate PoC system 100 for further processing of the call.
  • FIG. 7 further describes the call flow in this scenario.
  • the Gateway 140 translates INVITE, 200 OK and ACK messages between the LMR system 142 and the PoC system 100 to establish a PTT session.
  • the PoC server 112 decides who would be the initial talker as part of 200 OK response and distributes the MBCP Taken and Granted messages to the PoC users and the Gateway 140.
  • Floor control messages from the LMR system 142 use the RTP protocol, but floor control messages from the PoC system 100 use RTCP messages, which requires the Gateway 140 to convert floor control RTP messages into their respective RTCP messages, and vice versa as below:
  • the Gateway 140 Upon receiving a "PTT Transmit Request" from the LMR system 142, the Gateway 140 responds back with a "PTT Transmit Grant" to the LMR system 142, in the case where the Gateway 140 finds that the PTT floor has already been granted to the LMR subscriber unit 146.
  • the Gateway 140 sends a Heartbeat Query message periodically to the LMR system 142 and handles the Heartbeat response from the LMR system 142.
  • the Gateway 140 Upon receiving a "PTT Transmit Progress" from the LMR system 142 while the floor is taken by an LMR subscriber unit 146, the Gateway 140 extracts the voice payload from this message and transmits this voice payload towards the PoC system 100 by encapsulating it in RTP messages.
  • the Gateway 140 Upon receiving a "PTT Transmit End" from the LMR system 142, the Gateway 140 translates the message to a "MBCP Release" for the PoC system 100. Before sending or after receiving "PTT Transmit End,” all of the buffered media frames have to be delivered to the peer network.
  • the Gateway 140 translates the message to a "PTT Start" for the LMR system 142.
  • the Gateway 140 Upon receiving a RTP voice packets from the PoC system 100, the Gateway 140 translates it to a "PTT Transmit Progress" message for the LMR system 142, where the floor is taken by a PoC subscriber.
  • Any unstoppable media from the LMR system 142 is handled by the Gateway 140 and is given as a higher priority than the PoC user.
  • Either the PoC system 100 or the LMR system 142 can send a BYE message to terminate the session.
  • the Gateway 140 In the case where the unit-to-unit call is originated in the PoC system 100, the Gateway 140 translates the messages to their corresponding mapped SIP messages for the LMR system 142 and fills in the necessary information required. An SU-ID is mapped to an MDN in the Gateway 140. During a call from the PoC system 100, the MDN is converted to the SU-ID and the request is forwarded to the appropriate LMR system 142 for further processing of the call.
  • FIG. 8 further describes the call flow in this scenario.
  • the Gateway 140 translates INVITE, 200 OK and ACK messages between the PoC system 100 and the LMR system 142 to establish a PTT session.
  • the PoC server 112 decides who would be the initial talker after receiving a 200 OK response and distributes the MBCP Taken and Granted messages to the PoC mobile units 134 accordingly.
  • Floor control messages from the LMR system 142 use the RTP protocol, but floor control messages from the PoC system 100 use RTCP messages, which requires the Gateway 140 to convert floor control RTP messages into their respective RTCP messages, and vice versa as below:
  • the Gateway 140 sends a "PTT Transmit Request" to the LMR system 142 and the LMR system 142 responds back with an appropriate message, such as "PTT Transmit Grant” or "PTT Deny".
  • the Gateway 140 receives a Heartbeat Query message periodically from the LMR system 142 and handles the Heartbeat response to the LMR system 142.
  • the Gateway 140 Upon receiving RTP packets with payloads from the PoC system 100, the Gateway 140 translates these RTP packets to "PTT Transmit Progress" messages to the LMR system 142.
  • the Gateway 140 Upon receiving an "MBCP Release" from the PoC system 100, the Gateway 140 translates this message to a "PTT Transmit End" for the LMR system 142.
  • the Gateway 140 translates the message to a "PTT Start" for the LMR system 142.
  • the LMR system 142 transmits the audio packets to the Gateway 140 to send to the PoC system 100. 10. Any unstoppable media from the LMR system 142 is handled by the Gateway 140 and is given a higher priority than the PoC user.
  • Either system 100, 142 can send a BYE message to terminate the session. 5.6.3 Group Call
  • the RFSS 144 where the group is hosted always acts as an MMF. If the group is hosted in the PoC network 100, then the PoC Server 112 performs a controlling function.
  • FIG. 9 illustrates MMF and SMF participation during a group call, where the group is hosted in the PoC system 100
  • the serving RFSS 144 in the LMR system 142 extends a call leg towards the Gateway 140, where an SG-ID is mapped to an SG-MDN, which is an addressable identity in the PoC system 100.
  • the SG-MDN is an MDN created in the PoC system 100, which is unique in the PoC system 100, and is added as a member to a PoC group.
  • FIG. 10 further describes the call flow in this scenario.
  • the Gateway 140 translates INVITE, 200 OK and ACK messages between the PoC system 100 and the LMR system 142 to establish a PTT session.
  • the PoC server 112 decides who would be the initial talker after receiving a 200 OK response and distributes the MBCP Taken and Granted messages to the PoC mobile units 134 accordingly.
  • the Gateway 140 starts a Heartbeat Query message periodically to LMR system 142 and handles the Heartbeat response from the LMR system 142.
  • the Gateway 140 Upon receiving a "PTT Transmit Progress" from the LMR system 142 while floor is taken by an LMR subscriber unit 146, the Gateway 140 sends RTP messages with voice message payloads towards the PoC system 100.
  • the Gateway 140 Upon receiving a "PTT Transmit End" from the LMR system 142, the Gateway 140 translates the message to a "MBCP Release" towards the PoC system 100.
  • the Gateway 140 translates the message to a "PTT Start" towards the LMR system 142.
  • the Gateway 140 Upon receiving RTP voice packets from the PoC system 100, the Gateway 140 translates them into "PTT Transmit Progress" messages towards the LMR system 142, when the floor is taken by a PoC subscriber.
  • Unstoppable media comprises RTP voice packets received from the LMR system 142 without it sending a "PTT Transmit Start.” If a PoC subscriber has the floor, then the unstoppable media is considered to be an implicit floor revoke.
  • Either system 100, 142 can send a BYE message to terminate the session. However, the PoC Server 112 does not terminate the call unit unless there is only one participant remaining.
  • the Gateway 140 In the case of a group call originated in the PoC system 100, the Gateway 140 translates the message to corresponding mapped SIP messages towards the LMR system 142 and fills in the necessary information required.
  • An SG-ID is mapped to an SG-MDN on the Gateway 140.
  • the SG-MDN is converted to an SG-ID in the LMR system 142, and the request is forwarded to the appropriate LMR system 142 for further processing of the call.
  • FIG. 11 further describes the call flow in this scenario.
  • the Gateway 140 translates INVITE, 200 OK and ACK messages between the PoC system 100 and the LMR system 142 to establish a PTT session.
  • the PoC server 112 decides who would be the initial talker after receiving a 200 OK response and distributes the MBCP Taken and Granted messages to the PoC mobile units 134 accordingly.
  • Floor control messages from the LMR system 142 use the RTP protocol, but floor control messages from the PoC system 100 use RTCP messages, which requires the Gateway 140 to convert floor control RTP messages into their respective RTCP messages, and vice versa.
  • the Gateway 140 sends a "Transmit Start” after receiving a "MBCP
  • the Gateway 140 starts a Heartbeat Query message periodically to LMR system 142 and handles the Heartbeat response from the LMR system 142.
  • the Gateway 140 Upon receiving RTP voice packets from the PoC system 100, the Gateway 140 translates them into "PTT Transmit Progress" messages towards the LMR system
  • the Gateway 140 Upon receiving a "PTT Idle" from the PoC system 100, the Gateway 140 translate the message to a "PTT Transmit End” towards the LMR system 142.
  • the Gateway 140 Upon receiving a "PTT Transmit Request" from the LMR system 142, the Gateway 140 responds back with a "PTT Transmit Grant” or “PTT Deny” to the LMR system 142, and then media flows from the LMR system 142 to the PoC system 100.
  • Any unstoppable media from the LMR system 142 is handled by the Gateway 140 and is given a higher priority than the PoC user.
  • Unstoppable media comprises RTP voice packets received from the LMR system 142 without it sending a "PTT Transmit Start.” If a PoC subscriber has the floor, then the unstoppable media is considered to be an implicit floor revoke.
  • Either system 100, 142 can send a BYE message to terminate the session.
  • the PoC Server 112 does not terminate the call unless there is only one participant left.
  • a different audio codec such as a G.729, Adaptive Multi-Rate (AMR), OPUS or Codec2 codec, can be used instead of an Improved Multi-Band Excitation (IMBE) or
  • IMBE Improved Multi-Band Excitation
  • AMBE Advanced Multi-Band Excitation
  • RTCP for floor control i.e. ISSI packet type and control blocks.
  • This complexity can be reduced by the following: • Provide a static configuration in the LMR system 142 to set up a group call segments to the PoC system 100, i.e. consider that the Gateway 140 has an implicit registration for a group as a serving RFSS 144.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une passerelle d'interface réseau-à-réseau (NNI) pour l'inter-communication entre un système cellulaire de type appuyer-pour-parler (PoC) dans un premier réseau sans fil et un système de radio mobile terrestre (LMR) dans un second réseau sans fil. Le système PoC effectue une session d'appel PoC pour des unités mobiles PoC dans le premier réseau sans fil. Le système LMR effectue une session d'appel appuyer-pour-parler (PTT) pour des unités d'abonnés LMR dans le second réseau sans fil. Les deux sessions d'appel PoC et PTT comprennent un appel vocal en semi-duplex à deux voies instantané dans un groupe des unités mobiles PoC et/ou des unités d'abonnés LMR. La passerelle relie le système LMR au système PoC de telle sorte que le système PoC est exposé au système LMR en tant que système LMR émulé, le système LMR est exposé au système PoC en tant que système PoC émulé, et les appels sont passés via les premier et second réseaux sans fil entre les unités mobiles PoC et les unités d'abonnés LMR.
EP15851730.0A 2014-10-21 2015-10-21 Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler Withdrawn EP3210400A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201462066533P 2014-10-21 2014-10-21
PCT/US2015/056712 WO2016065036A1 (fr) 2014-10-21 2015-10-21 Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler

Publications (2)

Publication Number Publication Date
EP3210400A1 true EP3210400A1 (fr) 2017-08-30
EP3210400A4 EP3210400A4 (fr) 2018-04-18

Family

ID=55761493

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15851730.0A Withdrawn EP3210400A4 (fr) 2014-10-21 2015-10-21 Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler

Country Status (4)

Country Link
EP (1) EP3210400A4 (fr)
CA (1) CA2963688A1 (fr)
MX (1) MX2017005197A (fr)
WO (1) WO2016065036A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836208A (zh) * 2019-04-22 2020-10-27 海能达通信股份有限公司 话权控制方法和装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10735180B2 (en) * 2016-12-16 2020-08-04 Clever Devices Ltd. Dual fallback hardened VoIP system with signal quality measurement
US10582009B2 (en) * 2017-03-24 2020-03-03 Motorola Solutions, Inc. Method and apparatus for a cloud-based broadband push-to-talk configuration portal
US11381374B2 (en) 2018-09-12 2022-07-05 Tait International Limited Communication between half duplex and full duplex systems
US10477362B1 (en) * 2018-11-21 2019-11-12 Saudi Arabian Oil Company Interface and authorization for cross-network communications

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE0302920D0 (sv) * 2003-11-03 2003-11-03 Ericsson Telefon Ab L M Improvements in or relating to group calls
US9137646B2 (en) * 2004-11-23 2015-09-15 Kodiak Networks, Inc. Method and framework to detect service users in an insufficient wireless radio coverage network and to improve a service delivery experience by guaranteed presence
FI119314B (fi) * 2006-02-01 2008-09-30 Teliasonera Ab Järjestelmien välinen viestintä matkaviestintäjärjestelmässä
US7809390B2 (en) * 2006-10-30 2010-10-05 Cisco Technology, Inc. Method and system for providing information about a push-to-talk communication session
US7774012B2 (en) * 2007-01-30 2010-08-10 Alcatel-Lucent Usa Inc. Method for RTP setup coordination for talk groups when interconnecting public safety wireless networks and commercial wireless networks
US7974650B2 (en) * 2007-02-20 2011-07-05 Alcatel-Lucent Usa Inc. Interoperability between different types of wireless networks for push to talk group calls
US8943182B2 (en) * 2008-10-01 2015-01-27 Motorola Solutions, Inc. Method and system for transferring a communication session
US8565760B2 (en) * 2010-09-30 2013-10-22 Motorola Solutions, Inc. Methods, systems and apparatus for recovering registration information
US8976730B2 (en) * 2011-07-22 2015-03-10 Alcatel Lucent Enhanced capabilities and efficient bandwidth utilization for ISSI-based push-to-talk over LTE

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836208A (zh) * 2019-04-22 2020-10-27 海能达通信股份有限公司 话权控制方法和装置

Also Published As

Publication number Publication date
WO2016065036A1 (fr) 2016-04-28
MX2017005197A (es) 2017-10-04
EP3210400A4 (fr) 2018-04-18
CA2963688A1 (fr) 2016-04-28

Similar Documents

Publication Publication Date Title
US10085124B2 (en) System and method to leverage web real-time communication for implementing push-to-talk solutions
CA2804368C (fr) Solutions d'interfonctionnement wifi pour messagerie vocale instantanee sur reseau cellulaire
US20170231014A1 (en) System for inter-communication between land mobile radio and push-to-talk-over-cellular systems
US9775179B2 (en) Method to achieve a fully acknowledged mode communication (FAMC) in push-to-talk over cellular (PoC)
US10367863B2 (en) Method for providing dynamic quality of service for push-to-talk service
US20170238152A1 (en) Method for multiplexing media streams to optimize network resource usage for push-to-talk-over-cellular service
CA2936083C (fr) Procedes optimises destines aux appels dans de grands groupes au moyen de supports de transport de diffusion individuelle et multidiffusion pour la messagerie vocale instantanee ( poc)
US9510165B2 (en) Push-to-talk-over-cellular (PoC) service in heterogeneous networks (HETNETS) and multimode small cell environments
US10178513B2 (en) Relay-mode and direct-mode operations for push-to-talk-over-cellular (PoC) using WiFi-technologies
EP3210400A1 (fr) Système pour intercommunication entre un système de radio mobile terrestre et un système cellulaire de type appuyer-pour-parler
US20170280306A1 (en) System for Inter-Communication Between Integrated Digital Enhanced Network Systems and Push-To-Talk-Over-Cellular Systems
EP3216248B1 (fr) Procédé et système pour fournir une qualité de service dynamique pour service "appuyer-pour-parler"
CA2958215C (fr) Operations en mode relais et en mode direct pour des communications poc au moyen de technologies wifi
EP3025529A1 (fr) Distribution de service sensible au réseau d'accès radio (ran) pour réseaux de messagerie vocale instantanée cellulaire (poc)
CA2966610A1 (fr) Cadre d'architecture servant a realiser des services de poussee vers x utilisant des services de stockage nuagiques
WO2015013449A1 (fr) Distribution de service sensible au réseau d'accès radio (ran) pour réseaux de messagerie vocale instantanée cellulaire (poc)
WO2016073515A1 (fr) Procédé de multiplexage de flux multimédias visant à optimiser l'utilisation de ressources réseau pour un service de conversation cellulaire

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20170412

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20180321

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/45 20180101ALI20180315BHEP

Ipc: H04L 29/08 20060101ALI20180315BHEP

Ipc: H04W 4/10 20090101AFI20180315BHEP

Ipc: H04W 84/04 20090101ALI20180315BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20180702