EP2550816A1 - Sessions de communication à haute priorité dans système de communications sans fil - Google Patents

Sessions de communication à haute priorité dans système de communications sans fil

Info

Publication number
EP2550816A1
EP2550816A1 EP11712118A EP11712118A EP2550816A1 EP 2550816 A1 EP2550816 A1 EP 2550816A1 EP 11712118 A EP11712118 A EP 11712118A EP 11712118 A EP11712118 A EP 11712118A EP 2550816 A1 EP2550816 A1 EP 2550816A1
Authority
EP
European Patent Office
Prior art keywords
communication session
call
given
priority
given communication
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
EP11712118A
Other languages
German (de)
English (en)
Inventor
Beth A. Brewer
Hamsini Bhaskaran
Ashutosh Aggarwal
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.)
Qualcomm Inc
Original Assignee
Qualcomm 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
Priority claimed from US12/728,489 external-priority patent/US8755831B2/en
Priority claimed from US12/750,218 external-priority patent/US8738058B2/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2550816A1 publication Critical patent/EP2550816A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • 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

Definitions

  • Embodiments of the invention relate to high-priority communication sessions within a wireless communications system.
  • Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks) and a third-generation (3G) high speed data / Internet-capable wireless service.
  • 1G first-generation analog wireless phone service
  • 2G second-generation digital wireless phone service
  • 3G third-generation
  • technologies including Cellular and Personal Communications Service (PCS) systems.
  • Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDM A), the Global System for Mobile access (GSM) variation of TDMA, and newer hybrid digital communication systems using both TDMA and CDMA technologies.
  • AMPS Cellular and Personal Communications Service
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDM A Time Division Multiple Access
  • GSM Global System for Mobile access
  • the method for providing CDMA mobile communications was standardized in the United States by the Telecommunications Industry Association/Electronic Industries Association in TIA/EIA/IS-95-A entitled "Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System," referred to herein as IS-95.
  • Combined AMPS & CDMA systems are described in TIA/EIA Standard IS-98.
  • Other communications systems are described in the IMT-2000/UM, or International Mobile Telecommunications System 2000/Universal Mobile Telecommunications System, standards covering what are referred to as wideband CDMA (WCDMA), CDMA2000 (such as CDMA2000 lxEV-DO standards, for example) or TD-SCDMA.
  • AN access network
  • RAN radio access network
  • IP Internet Protocol
  • Push-to-talk (PTT) capabilities are becoming popular with service sectors and consumers.
  • PTT can support a "dispatch" voice service that operates over standard commercial wireless infrastructures, such as CDMA, FDMA, TDMA, GSM, etc.
  • a dispatch model communication between endpoints (ATs) occurs within virtual groups, wherein the voice of one "talker" is transmitted to one or more "listeners.”
  • a single instance of this type of communication is commonly referred to as a dispatch call, or simply a PTT call.
  • a PTT call is an instantiation of a group, which defines the characteristics of a call.
  • a group in essence is defined by a member list and associated information, such as group name or group identification.
  • a transmission of data to a single destination is referred to as "unicast".
  • a “broadcast” refers to a transmission of data packets to all destinations or access terminals (e.g., within a given cell, served by a given service provider, etc.), while a “multicast” refers to a transmission of data packets to a given group of destinations or access terminals.
  • the given group of destinations or "multicast group” may include more than one and less than all of possible destinations or access terminals (e.g., within a given group, served by a given service provider, etc.). However, it is at least possible in certain situations that the multicast group comprises only one access terminal, similar to a unicast, or alternatively that the multicast group comprises all access terminals (e.g., within a given cell, etc.), similar to a broadcast.
  • a PTT or PTT over Cellular (PoC) call corresponds to a server mediated communication between two or more identified access terminals, regardless of the various configurations used to conduct the PTT calls.
  • a PTT calls are initiated and maintained by a physical interaction at the access terminal (e.g., pressing and holding a key).
  • a call originator sends, to an application server, a request to initiate a given communication session with at least one call target.
  • the received request configured is to indicate to the application server that the given communication session is associated with a high-priority. If necessary, the application server can reduce its load and/or preempt one or more other users or other sessions to support the given communication session.
  • the application server configures a call announcement to force the at least one call target to accept the given communication session, and transmits the configured call announcement to the at least one call target.
  • the at least one call target receives the call announcement, and determines that the call announcement is configured to force the given access terminal to accept the given communication session. Responsive to the determination, the at least one call target transmits an acknowledgment to the call announcement that indicates that the at least one call target has accepted the given communication session.
  • FIG. 1 is a diagram of a wireless network architecture that supports access terminals and access networks in accordance with at least one embodiment of the invention.
  • FIG. 2A illustrates the carrier network according to an embodiment of the present invention.
  • FIG. 2B illustrates an example of the wireless communication 100 of FIG. 1 in more detail.
  • FIG. 3 is an illustration of an access terminal in accordance with at least one embodiment of the invention.
  • FIG. 4 illustrates a server-arbitrated high-priority communication session set-up process in accordance with an embodiment of the invention.
  • FIGS. 5A and 5B illustrate alternative processes by which a target access terminal participating in the server-arbitrated high-priority communication session of FIG. 4 can send media in accordance with embodiments of the invention
  • a High Data Rate (HDR) subscriber station referred to herein as an access terminal (AT) may be mobile (e.g., wireless) or stationary (e.g., a wired client, such as a dispatch console), and may communicate with one or more HDR base stations, referred to herein as modem pool transceivers (MPTs) or base stations (BS).
  • An access terminal transmits and receives data packets through one or more modem pool transceivers to an HDR base station controller, referred to as a modem pool controller (MPC), base station controller (BSC) and/or packet control function (PCF).
  • Modem pool transceivers and modem pool controllers are parts of a network called an access network.
  • An access network transports data packets between multiple access terminals.
  • the access network may be further connected to additional networks outside the access network, such as a corporate intranet or the Internet, and may transport data packets between each access terminal and such outside networks.
  • An access terminal that has established an active traffic channel connection with one or more modem pool transceivers is called an active access terminal, and is said to be in a traffic state.
  • An access terminal that is in the process of establishing an active traffic channel connection with one or more modem pool transceivers is said to be in a connection setup state.
  • An access terminal may be any data device that communicates through a wireless channel or through a wired channel, for example using fiber optic or coaxial cables.
  • An access terminal may further be any of a number of types of devices including but not limited to PC card, compact flash, external or internal modem, or wireless or wireline phone.
  • the communication link through which the access terminal sends signals to the modem pool transceiver is called a reverse link or traffic channel.
  • the communication link through which a modem pool transceiver sends signals to an access terminal is called a forward link or traffic channel.
  • traffic channel can refer to either a forward or reverse traffic channel.
  • FIG. 1 illustrates a block diagram of one exemplary embodiment of a wireless system 100 in accordance with at least one embodiment of the invention.
  • System 100 can contain access terminals, such as cellular telephone 102, in communication across an air interface 104 with an access network or radio access network (RAN) 120 that can connect the access terminal 102 to network equipment providing data connectivity between a packet switched data network (e.g., an intranet, the Internet, and/or carrier network 126) and the access terminals 102, 108, 110, 112.
  • RAN radio access network
  • the access terminal can be a cellular telephone 102, a personal digital assistant 108, a pager 110, which is shown here as a two-way text pager, or even a separate computer platform 112 that has a wireless communication portal.
  • Embodiments of the invention can thus be realized on any form of access terminal including a wireless communication portal or having wireless communication capabilities, including without limitation, wireless modems, PCMCIA cards, personal computers, telephones, or any combination or subcombination thereof.
  • access terminal including a wireless communication portal or having wireless communication capabilities, including without limitation, wireless modems, PCMCIA cards, personal computers, telephones, or any combination or subcombination thereof.
  • wireless modems including without limitation, wireless modems, PCMCIA cards, personal computers, telephones, or any combination or subcombination thereof.
  • PCMCIA cards personal computers, telephones, or any combination or subcombination thereof.
  • System 100 is merely exemplary and can include any system that allows remote access terminals, such as wireless client computing devices 102, 108, 110, 112 to communicate over-the-air between and among each other and/or between and among components connected via the air interface 104 and RAN 120, including, without limitation, carrier network 126, the Internet, and/or other remote servers.
  • remote access terminals such as wireless client computing devices 102, 108, 110, 112 to communicate over-the-air between and among each other and/or between and among components connected via the air interface 104 and RAN 120, including, without limitation, carrier network 126, the Internet, and/or other remote servers.
  • the RAN 120 controls messages (typically sent as data packets) sent to a base station controller/packet control function (BSC/PCF) 122.
  • the BSC/PCF 122 is responsible for signaling, establishing, and tearing down bearer channels (i.e., data channels) between a packet data service node 100 ("PDSN") and the access terminals 102/108/110/112. If link layer encryption is enabled, the BSC/PCF 122 also encrypts the content before forwarding it over the air interface 104.
  • the function of the BSC/PCF 122 is well-known in the art and will not be discussed further for the sake of brevity.
  • the carrier network 126 may communicate with the BSC/PCF 122 by a network, the Internet and/or a public switched telephone network (PSTN).
  • PSTN public switched telephone network
  • the BSC/PCF 122 may connect directly to the Internet or external network.
  • the network or Internet connection between the carrier network 126 and the BSC/PCF 122 transfers data, and the PSTN transfers voice information.
  • the BSC/PCF 122 can be connected to multiple base stations (BS) or modem pool transceivers (MPT) 124.
  • BS base stations
  • MPT modem pool transceivers
  • the BSC/PCF 122 is typically connected to the MPT/BS 124 by a network, the Internet and/or PSTN for data transfer and/or voice information.
  • the MPT/BS 124 can broadcast data messages wirelessly to the access terminals, such as cellular telephone 102.
  • the MPT/BS 124, BSC/PCF 122 and other components may form the RAN 120, as is known in the art.
  • alternate configurations may also be used and the invention is not limited to the configuration illustrated.
  • the functionality of the BSC/PCF 122 and one or more of the MPT/BS 124 may be collapsed into a single "hybrid" module having the functionality of both the BSC/PCF 122 and the MPT/BS 124.
  • FIG. 2A illustrates the carrier network 126 according to an embodiment of the present invention.
  • the carrier network 126 includes a packet data serving node (PDSN) 160, a broadcast serving node (BSN) 165, an application server 170 and an Internet 175.
  • PDSN packet data serving node
  • BSN broadcast serving node
  • application server 170 and other components may be located outside the carrier network in alternative embodiments.
  • the PDSN 160 provides access to the Internet 175, intranets and/or remote servers (e.g., application server 170) for mobile stations (e.g., access terminals, such as 102, 108, 110, 112 from FIG. 1) utilizing, for example, a cdma2000 Radio Access Network (RAN) (e.g., RAN 120 of FIG. 1).
  • RAN cdma2000 Radio Access Network
  • the PDSN 160 may provide simple IP and mobile IP access, foreign agent support, and packet transport.
  • the PDSN 160 can act as a client for Authentication, Authorization, and Accounting (AAA) servers and other supporting infrastructure and provides mobile stations with a gateway to the IP network as is known in the art.
  • AAA Authentication, Authorization, and Accounting
  • the PDSN 160 may communicate with the RAN 120 (e.g., the BSC/PCF 122) via a conventional A10 connection.
  • the A10 connection is well-known in the art and will not be described further for the sake of brevity.
  • the broadcast serving node (BSN) 165 may be configured to support multicast and broadcast services.
  • the BSN 165 will be described in greater detail below.
  • the BSN 165 communicates with the RAN 120 (e.g., the BSC/PCF 122) via a broadcast (BC) A10 connection, and with the application server 170 via the Internet 175.
  • the BCA10 connection is used to transfer multicast and/or broadcast messaging. Accordingly, the application server 170 sends unicast messaging to the PDSN 160 via the Internet 175, and sends multicast messaging to the BSN 165 via the Internet 175.
  • the RAN 120 transmits multicast messages, received from the BSN 165 via the BCA10 connection, over a broadcast channel (BCH) of the air interface 104 to one or more access terminals 200.
  • BCH broadcast channel
  • FIG. 2B illustrates an example of the wireless communication 100 of FIG. 1 in more detail.
  • ATs 1...N are shown as connecting to the RAN 120 at locations serviced by different packet data network end-points.
  • ATs 1 and 3 connect to the RAN 120 at a portion served by a first packet data network end-point 162 (e.g., which may correspond to PDSN 160, BSN 165, a home agent (HA), a foreign agent (FA), etc.).
  • a first packet data network end-point 162 e.g., which may correspond to PDSN 160, BSN 165, a home agent (HA), a foreign agent (FA), etc.
  • the first packet data network end-point 162 in turn connects, via the routing unit 188, to the Internet 175 and/or to one or more of an authentication, authorization and accounting (AAA) server 182, a provisioning server 184, an Internet Protocol (IP) Multimedia Subsystem (IMS) / Session Initiation Protocol (SIP) Registration Server 186 and/or the application server 170.
  • ATs 2 and 5...N connect to the RAN 120 at a portion served by a second packet data network end- point 164 (e.g., which may correspond to PDSN 160, BSN 165, FA, HA, etc.).
  • the second packet data network end- point 164 in turn connects, via the routing unit 188, to the Internet 175 and/or to one or more of the AAA server 182, a provisioning server 184, an IMS / SIP Registration Server 186 and/or the application server 170.
  • AT 4 connects directly to the Internet 175, and through the Internet 175 can then connect to any of the system components described above.
  • ATs 1, 3 and 5...N are illustrated as wireless cell-phones
  • AT 2 is illustrated as a wireless tablet-PC
  • AT 4 is illustrated as a wired desktop station.
  • the wireless communication system 100 can connect to any type of AT, and the examples illustrated in FIG. 2B are not intended to limit the types of ATs that may be implemented within the system.
  • the AAA 182, the provisioning server 184, the IMS/SIP registration server 186 and the application server 170 are each illustrated as structurally separate servers, one or more of these servers may be consolidated in at least one embodiment of the invention.
  • the application server 170 is illustrated as including a plurality of media control complexes (MCCs) 1...N 170B, and a plurality of regional dispatchers 1...N 170A.
  • MCCs media control complexes
  • the regional dispatchers 170A and MCCs 170B are included within the application server 170, which in at least one embodiment can correspond to a distributed network of servers that collectively functions to arbitrate communication sessions (e.g., half-duplex group communication sessions via IP unicasting and/or IP multicasting protocols) within the wireless communication system 100.
  • the communication sessions arbitrated by the application server 170 can theoretically take place between ATs located anywhere within the system 100, multiple regional dispatchers 170A and MCCs are distributed to reduce latency for the arbitrated communication sessions (e.g., so that a MCC in North America is not relaying media back-and-forth between session participants located in China).
  • the associated functionality can be enforced by one or more of the regional dispatchers 170A and/or one or more of the MCCs 170B.
  • the regional dispatchers 170A are generally responsible for any functionality related to establishing a communication session (e.g., handling signaling messages between the ATs, scheduling and/or sending announce messages, etc.), whereas the MCCs 170B are responsible for hosting the communication session for the duration of the call instance, including conducting an in-call signaling and an actual exchange of media during an arbitrated communication session.
  • an access terminal 200 (here a wireless device), such as a cellular telephone, has a platform 202 that can receive and execute software applications, data and/or commands transmitted from the RAN 120 that may ultimately come from the carrier network 126, the Internet and/or other remote servers and networks.
  • the platform 202 can include a transceiver 206 operably coupled to an application specific integrated circuit ("ASIC" 208), or other processor, microprocessor, logic circuit, or other data processing device.
  • ASIC 208 or other processor executes the application programming interface ("API') 210 layer that interfaces with any resident programs in the memory 212 of the wireless device.
  • API' application programming interface
  • the memory 212 can be comprised of read-only or random-access memory (RAM and ROM), EEPROM, flash cards, or any memory common to computer platforms.
  • the platform 202 also can include a local database 214 that can hold applications not actively used in memory 212.
  • the local database 214 is typically a flash memory cell, but can be any secondary storage device as known in the art, such as magnetic media, EEPROM, optical media, tape, soft or hard disk, or the like.
  • the internal platform 202 components can also be operably coupled to external devices such as antenna 222, display 224, push-to-talk button 228 and keypad 226 among other components, as is known in the art.
  • an embodiment of the invention can include an access terminal including the ability to perform the functions described herein.
  • the various logic elements can be embodied in discrete elements, software modules executed on a processor or any combination of software and hardware to achieve the functionality disclosed herein.
  • ASIC 208, memory 212, API 210 and local database 214 may all be used cooperatively to load, store and execute the various functions disclosed herein and thus the logic to perform these functions may be distributed over various elements.
  • the functionality could be incorporated into one discrete component. Therefore, the features of the access terminal in FIG. 3 are to be considered merely illustrative and the invention is not limited to the illustrated features or arrangement.
  • the wireless communication between the access terminal 102 and the RAN 120 can be based on different technologies, such as code division multiple access (CDMA), WCDMA, time division multiple access (TDMA), frequency division multiple access (FDMA), Orthogonal Frequency Division Multiplexing (OFDM), the Global System for Mobile Communications (GSM), or other protocols that may be used in a wireless communications network or a data communications network.
  • CDMA code division multiple access
  • WCDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDM Orthogonal Frequency Division Multiplexing
  • GSM Global System for Mobile Communications
  • the data communication is typically between the client device 102, MPT/BS 124, and BSC/PCF 122.
  • the BSC/PCF 122 can be connected to multiple data networks such as the carrier network 126, PSTN, the Internet, a virtual private network, and the like, thus allowing the access terminal 102 access to a broader communication network.
  • voice transmission and/or data can be transmitted to the access terminals from the RAN using a variety of networks and configurations. Accordingly, the illustrations provided herein are not intended to limit the embodiments of the invention and are merely to aid in the description of aspects of embodiments of the invention.
  • the application server 170 which is responsible for arbitrating the communication session, receives a request to initiate a communication session and attempts to find a host-computer (e.g., MCC 170B) with sufficient available resources to host the exchange of media for the communication session. If a host-computer due to resource unavailability, the communication session cannot be set-up.
  • a host-computer e.g., MCC 170B
  • the least one target can be configured to auto-reject the call if the at least one target is already engaged in another communication session.
  • a user of the at least one target may simply choose to ignore the announced communication session.
  • the uncertainty regarding session- resource availability and target-acceptance can make setting-up a high-priority (e.g., emergency) call difficult to accomplish.
  • embodiments of the invention are directed to setting-up and conducting a high-priority (e.g., emergency) server-arbitrated communication sessions within the wireless communications system 100.
  • FIG. 4 illustrates a server-arbitrated high-priority communication session set-up process in accordance with an embodiment of the invention. The high-priority communication session established in FIG.
  • server-arbitrated session including but not limited to a full- duplex VoIP session, a half-duplex group session (e.g., push-to-talk (PTT) or push-to- transfer (PTX)) supported either via IP unicasting such that the RAN 120 is instructed to transmit the forwarded media on a downlink dedicated channel to separately to each target AT, or via IP multicasting protocols such that the RAN 120 is instructed to transmit the forwarded media on a downlink shared channel in at least one sector of the wireless communications system 100 potentially to multiple target ATs within the at least one sector at the same time) wherein a single group-member holds the floor at any given time, a full-duplex group session, a hybrid-duplex or fast full-duplex group session wherein more than one group-member and less than all group-members can simultaneously talk and listen at any given time.
  • a full-duplex group session e.g., push-to-talk (PTT) or push-to- transfer (PTX) supported either via IP unicasting such that
  • the operations performed at AT 1 are performed at a multimedia client 21 OA, where the multimedia client 21 OA corresponds to an API among APIs 210 as described with respect to AT 200 of FIG. 3.
  • the multimedia client 21 OA is responsible for managing multimedia communication sessions at AT 1.
  • the multimedia client 21 OA of AT 1 receives user-input that indicates the user of AT 1 wishes to initiate a high-priority communication session, 400.
  • the user-input received in 400 may correspond to the user pressing a dedicated physical button or soft-key for making high- priority calls.
  • the user-input received in 400 may correspond to the user requesting a session to a target AT known, by the multimedia client 21 OA, to be associated with emergencies (e.g., 911, a fire-department's phone number, etc.).
  • the user-input received in 400 may correspond to the user requesting a normal-priority or non-emergency call along with a secondary indication or input that specifies that the call should be placed as high-priority and/or an emergency.
  • the secondary indication may correspond to the user double- tapping the call-button when placing the high-priority call, holding the call-button or send-button for more than a threshold period of time (e.g., 3 seconds) when placing the call, holding the call-button and another button at the same time when the call is placed, selecting a high-priority and/or an emergency-option from a pull-down menu or other menu in a call set-up screen on the display of AT 1, speaking the words "high-priority” and/or the word “emergency” or some other high-priority-indicating word while voice- dialing, and/or any combination thereof.
  • a threshold period of time e.g. 3 seconds
  • the multimedia client 21 OA of AT 1 configures a call message to request initiation of a high-priority communication session, 403.
  • the configuration of 403 may correspond to generating a standard call message to the selected target(s) and then modifying one or more fields of the standard call message to convey, to the application server 170, that AT 1 is attempting to initiate a high-priority communication session.
  • the field may indicate a highest of a plurality of priority levels, with the highest priority level corresponding to an emergency priority level.
  • the field may be binary, such that a first field setting corresponds to a high-priority or emergency call and a second field setting corresponds to a regular-priority or non-emergency call.
  • the modified field of the call message may correspond to a Diffserv Code Point (DSCP) value in a header portion of the call message.
  • DSCP Diffserv Code Point
  • the identification of one or more of the selected target(s) for the communication session are sufficient to inform the application server 170 of the session's high-priority status (e.g., 911, a fire- department's phone number, etc.).
  • the multimedia client 21 OA need not additionally modify the call message if the target selection, by itself, is sufficient to convey the high-priority status.
  • AT 1 transmits the configured call message to the RAN 120 (not shown in this figure), which then forwards the configured call message to a given regional dispatcher 170A of the application server 170, 406.
  • the application server 170 acknowledges receipt of the call message by transmitting an ACK message back to AT 1, 409.
  • the regional dispatcher 170A determines if the target ATs are registered with the application server 170, and if so, obtains their respective IP addresses, also, e.g., for a
  • the regional dispatcher 170 A then generates an announce message to announce the high-priority communication session to the target ATs 2...N, and configures the announce message to indicate, to the target ATs 2...N, that the communication session is a high-priority communication session, 421.
  • the announce message can be configured to include a field that indicates a highest of a plurality of priority levels, with the highest priority level corresponding to an emergency priority level, and/or a binary field such that a first field setting corresponds to a high-priority or emergency call and a second field setting corresponds to a regular priority or nonemergency call.
  • the field used to convey high-priority status may correspond to the DSCP field in a header portion of the announce message.
  • the regional dispatcher 170A then forwards the configured announce message to the RAN 120 (not shown in this figure) for transmission to ATs 2...N, 424.
  • target ATs 2...N receive the configured announce message from 424.
  • each of target ATs 2...N determine that the announce message is announcing a high-priority session, and further determine whether its respective multimedia client 210A is busy (e.g., engaged in another session). If the multimedia client 21 OA of the target ATs 2...N determine the multimedia client 21 OA is not busy in 427, each of target ATs 210 auto-accept the announced high-priority session by sending an announce ACK (accept) message to the application server 170, 433.
  • the multimedia client 21 OA of the target ATs 2...N determines the multimedia client 21 OA is busy in 427, the multimedia client 21 OA notifies a multimedia user-interface (UI) that a high-priority session has been announced, and then auto-accepts the announced high-priority session by sending an announce ACK (accept) message to the application server 170, 433.
  • the notification of 430 may correspond to a user-notification that the user's current session will be cut off within a threshold period of time (e.g., 1 second, 3 seconds, etc.) so that the user at least has the opportunity to say 'goodbye' to one or more other parties of the user's current session.
  • the notification may notify the user of the target ATs 2...N that the user's current session is going to be cut off and transferred to a high-priority call, but does not actually permit the user of the target ATs 2...N time to send any additional media related to the user's current session.
  • FIG. 4 illustrates each of target ATs 2...N auto-accepting the announced high-priority communication session irrespective of whether the respective target is already engaged in a communication session
  • a different call- join policy can be implemented if the targets ATs 2...N are engaged in another high- priority session.
  • the users of target ATs 2...N may not necessarily want to preempt a current high-priority session for another high-priority session. For example, if a doctor is in the middle of providing instructions over-the-phone related to a remote medical procedure in a first high-priority session, it may be counter-productive to transfer the doctor automatically to another emergency for which that the doctor may not necessarily be able to offer assistance.
  • the user(s) of respective target AT(s) may be given the option with regard to whether to accept the announced high-priority session in at least one embodiment (e.g., instead of simply auto-accepting the new high-priority session and disconnecting from the old high-priority session).
  • the regional dispatcher 170A Upon receiving the announce ACK (accept) message from a first of ATs 2...N ("first responder"), the regional dispatcher 170A sends a floor-grant message at least to AT 1, 436, to prompt a user of AT 1 to begin buffering media for eventual transmission to the application server 170 for forwarding to the target ATs 2...N.
  • the target ATs 2...N are also given the opportunity to forward media to the other call participant(s).
  • AT 1 receives the floor-grant message from the regional dispatcher 170A and acknowledges receipt of the floor-grant message with an ACK message, 439.
  • the multimedia client 21 OA then instructs AT 1 to play a tone to inform a user of AT 1 to begin inputting media (e.g., voice data), and the multimedia client 21 OA buffers the media input by the user of AT 1, 442.
  • the regional dispatcher 170A instructs the MCC 170B selected in 445 to begin hosting the communication session as a high-priority session, 445.
  • the selected MCC 170B determines whether it has sufficient call- resources available to support the high-priority communication session, 448. If the MCC 170B determines that sufficient resources are not available in 448, the MCC 170B selectively reduces its current call-resource load in 451. For example, the call-resource load reduction may correspond to dropping one or more currently active calls and/or one or more current call-participants supported by the MCC 170B.
  • the MCC 170B can select the call-resources for load reduction in 451 in a number of different ways. For example, the MCC 170B can evaluate a level of call- resources expected to be necessary to support the high-priority communication session, and can then drop calls in an order of lowest-priority to highest-priority until the MCC 170B has freed a sufficient level of call-resources to support the high-priority communication session.
  • the priority allocations of the calls, or the order by which the MCC 170B will selective drop calls, can be determined in different ways.
  • other high-priority communication sessions already hosted by the MCC 170B may be allocated a highest-possible priority ranking, calls that have been taking place for more than a threshold period of time may be allocated a lower-priority than comparable calls of shorter-duration.
  • calls involving large groups of ATs may be allocated a lower priority than small-group calls or one-to-one calls because more call-resources can be acquired through the sacrifice of a single call.
  • the priority-ranking may be established such that a lowest number of calls are dropped, or such that a lowest number of call participants are dropped.
  • the above-noted priority rankings are only examples, and there are many different ways by which the MCC 170B can drop currently allocated call-resources in order to reserve a given level of call-resources for the high-priority communication session.
  • the MCC 170B After the MCC 170B either (i) determines a sufficient level of call-resources to be available for the high-priority communication session in 448 or (ii) reduces a current call-resource allocation such that the sufficient level of call-resources is obtained, the MCC 170B then sends media control unit (MCU) information to call originator (and current floor-holder) AT 1 as well as target ATs 2...N, 560.
  • MCU media control unit
  • the MCU is a software process or instance that handles a single instance for a call or communication session, and the MCU information corresponds to a contact message and includes the IP address and port number regarding where floor-holders are to forward media for re-transmission to other session participant(s) during the high-priority communication session (e.g., as in 460 below), or signaling messages such as ACKs (e.g., as in 457 and/or 466 below).
  • AT 1 receives the MCU information from the MCC 170B, and acknowledges receipt of the MCU information with an ACK message, 457. Also, upon receiving the MCU information from the MCC 170B, the multimedia client 21 OA begins transmitting the buffered media to the MCC 170B, 460, which in turn buffers the media forwarded from AT 1, 463. Next, the MCC 170B waits to receive at least one ACK from target ATs 2...N to the MCU information transmitted in 454. In an example, the MCC 170B can wait for a first MCU-information ACK from any of target ATs 2...N and can then begin forwarding the buffered media.
  • the MCC 170B can wait for MCU-information ACKs from a given percentage of target ATs 2...N (e.g., of each target to which the announce message was sent in 424, or of each target that accepted the call in 433) before forwarding any of the buffered media.
  • the MCC 170B can wait for MCU-information ACKs from each of target ATs 2...N e.g., of each target to which the announce message was sent in 424, or of each target that accepted the call in 433), such that the given percentage equals 100%, before forwarding any of the buffered media (e.g., if it is important for each target AT to receive the full media- flow).
  • one or more ACKs from target ATs 2...N are received at the MCC 170B in 466.
  • a given threshold e.g., a first MCU-information ACK is received, a MCU-information ACK is received from each target AT to have accepted the call in 433, a given percentage of target ATs 2...N that accepted the call in 433, etc.
  • the MCC 170B forwards the buffered media to target ATs 2...N, 469.
  • MCU-ACKs are illustrated as arriving at the MCC 170B in 466, if a sufficient number of MCU-ACKs (e.g., one) from target ATs 2...N arrive at the MCC 170B before media begins arriving from AT 1, it will be appreciated that the buffering of block 463 can be skipped and the MCC 170B can begin forwarding the media from ATI to ATs 2...N as soon as it is received.
  • a sufficient number of MCU-ACKs e.g., one
  • the high-priority communication session is established as full-duplex or hybrid-duplex, one or more of target ATs 2...N can also send media to the application to be forwarded to the call originator AT 1 and/or to other session participants. Accordingly, if the high-priority communication session in FIG. 4,
  • each call participant e.g., including the call originator
  • TCH traffic channel
  • each call participant can send media (e.g., voice data or other audio data) and each call participant receives either (i) the media from the other party for a full-duplex communication session involving two call parties, or (ii) a mixed version of media from each other party (minus its own media) for a group full-duplex communication session including three or more parties.
  • media e.g., voice data or other audio data
  • each call participant receives either (i) the media from the other party for a full-duplex communication session involving two call parties, or (ii) a mixed version of media from each other party (minus its own media) for a group full-duplex communication session including three or more parties.
  • ATs 1 and 2 are conducting a full-duplex call, AT 1 receives AT 2's media and AT 2 receives AT l 's media.
  • AT 1 receives a mixed version of AT 2 and AT 3's media ("AT 2+3 media")
  • AT 2 receives a mixed version of AT 1 and AT 3's media
  • AT 1+3 media receives a mixed version of AT 1 and AT 2's media
  • the high-priority communication session in FIG. 4 is established as a half-duplex communication session, AT 1 can begin the high- priority communication session as a sole floor-holder speaking to at least one target AT, while the at least one target AT does not have its own TCH for transmitting media to be sent back to the call originator.
  • the target AT requests the floor and speaks once the floor is granted, with only one call participant holding the floor at any given time.
  • more than one floor-holder may have permission to speak.
  • FIGS. 5A and 5B illustrate examples of how a given target AT can send media back to a call originator and/or one or more other target ATs during a half-duplex or hybrid- duplex group communication session. While FIG. 5A is described with respect to a group communication session, FIG. 5A can be modified to accommodate a non-group- session that only involves ATs 1 and 2 simply by omitting the blocks directed to ATs 3...N.
  • FIGS. 5A and 5B have been simplified such that specific reference to the multimedia clients 21 OA, the regional dispatcher 170A and the MCC 170B has been omitted. Instead, FIGS. 5 A and 5B refer simply to ATs 1...N and the application server 170. However, it will be readily apparent how the different components contained within the broader elements referred to in FIGS. 5 A and 5B are involved in the processes described below.
  • a high-priority communication session has been established as either (i) a half- duplex group communication session with AT 1 as the floor-holder or (ii) a hybrid- duplex group communication session wherein AT 1 and at least one and less than all of ATs 2...N share the floor.
  • AT 1 forwards media (e.g., voice data) to the application server 170, 500A
  • the application server 170 forwards AT l 's media to ATs 2...N, 505 A.
  • silence frames can also be forwarded from the other floor-holders in 505 A.
  • ATs 2...N determine whether to send media to AT 1. For convenience of explanation, assume that ATs 3...N determine not to send media in 515A, and ATs 3...N continue to monitor AT l 's media for the high-priority communication session, 520A. Further assume that AT 2 determines to send media back to AT 1 in 51 OA. AT 2 continues to monitor AT l 's media for the high-priority communication session, 525A, and obtains a TCH (e.g., by sending a ConnectionRequest message to the RAN 120 and receiving a TCH assignment), 530A. It will be appreciated that AT 2 may already have obtained the TCH, and if so block 530A can be skipped at this point.
  • TCH e.g., by sending a ConnectionRequest message to the RAN 120 and receiving a TCH assignment
  • AT 2 then sends media over a reverse link of the TCH (R-TCH) to the RAN 120 to be forwarded to the application server 170, 535 A.
  • R-TCH reverse link of the TCH
  • AT 2 can simply send the media to the application server 170 at this point because AT 2 already shares the floor. Otherwise, if the high-priority communication session was initially a hybrid- duplex group communication session and AT 2 did not share the floor or the high- priority communication session was initially a half-duplex group communication session with only AT 1 having the floor, AT 2 may first request the floor from the application server 170 before sending media in 535 A.
  • the application server 170 may elect to maintain AT l 's floor while also grant the floor to AT 2, such that the resultant communication session either remains hybrid-duplex or transitions to hybrid-duplex from half-duplex.
  • AT 2 once AT 2 obtains the floor, AT 2 begins transferring media to the application server 170 for transmission to AT 1, 535 A.
  • the decision with regard to whether to transition an initial half-duplex communication session into a hybrid-duplex communication session can be made by one of the targets (e.g., a target can request to talk also and the rest of the group including the originator will receive the media from the requesting target).
  • the application server 170 mixes the input streams of the media from AT 1 and AT 2, 540A.
  • the mixing of 540A establishes an output stream such that AT 1 receives media frames from AT 2, and ATs 2...N each receive media frames from AT 1. Accordingly, the media frames from AT 1 are forwarded to ATs 2...N, and the media frames from AT 2 are forwarded to AT 1 , 545A.
  • the mixing of 540A can be performed in a different manner, as illustrated in FIG. 5B.
  • 500B through 535B correspond to 500A through 535A of FIG. A, respectively, and as such a further description of 500B through 535B has been omitted for the sake of brevity.
  • the application server 170 mixes the media streams or frames from ATs 1 and B such that AT 1 receives AT 2's media frames, AT 2 receives AT l 's media frames and ATs 3...N each receive a mixed version of media frames from ATs 1 and 2.
  • Mixing media frames is well-known in the art, and as such will not be described further for the sake of brevity (e.g., the mixing of 540B is similar in some respects to mixing that occurs in full-duplex, except the mixing of 540B is limited to media frames from ATs 1 and 2 instead of involving media frames from all of ATs 1...N). Accordingly, in 545B, the media frames from AT 1 are forwarded to AT 2, the media frames from AT 2 are forwarded to AT 1, and a mixed version of the media frames from ATs 1 and 2 are forwarded to ATs 3...N.
  • the above-described high-priority communication sessions can be implemented via IP-multicasting protocols and/or IP-unicasting protocols.
  • the media transmitted by the application server 170 at 469 of FIG. 4 can be sent to the target ATs 2...N individually via IP unicast.
  • the media transmitted by the application server 170 can be sent to the RAN 120 via IP multicast for transmission to ATs 2...N, such that two or more of ATs 2...N can potentially be tuned to the same downlink multicast channel in the same sector for receiving the media from AT 1.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal (e.g., access terminal).
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

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

Abstract

Selon un mode de réalisation de l'invention, un émetteur d'appel envoie, à un serveur d'application, une requête d'ouverture d'une session de communication donnée avec au moins une cible d'appel, la requête reçue étant configurée pour indiquer au serveur d'application que la session de communication donnée est associée à une haute priorité. Le serveur d'application configure une annonce d'appel pour forcer la ou les cibles d'appel à accepter la session de communication donnée, et envoie l'annonce d'appel configurée à la ou aux cibles d'appel. La ou les cibles d'appel reçoivent l'annonce d'appel et déterminent que l'annonce d'appel est configurée pour forcer le terminal d'accès donné à accepter la session de communication donnée. En réponse à la détermination, la ou les cibles d'appel envoient un accusé de réception de l'annonce d'appel qui indique que la ou les cibles d'appel ont accepté la session de communication donnée.
EP11712118A 2010-03-22 2011-03-22 Sessions de communication à haute priorité dans système de communications sans fil Withdrawn EP2550816A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US12/728,489 US8755831B2 (en) 2009-03-24 2010-03-22 Selectively allocating data channel resources to wireless communication devices within a wireless communications system
US12/750,218 US8738058B2 (en) 2009-04-06 2010-03-30 High-priority communications sessions within a wireless communications system
PCT/US2011/029383 WO2011119579A1 (fr) 2010-03-22 2011-03-22 Sessions de communication à haute priorité dans système de communications sans fil

Publications (1)

Publication Number Publication Date
EP2550816A1 true EP2550816A1 (fr) 2013-01-30

Family

ID=44041621

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11712118A Withdrawn EP2550816A1 (fr) 2010-03-22 2011-03-22 Sessions de communication à haute priorité dans système de communications sans fil

Country Status (6)

Country Link
EP (1) EP2550816A1 (fr)
JP (1) JP6012590B2 (fr)
KR (1) KR101441779B1 (fr)
CN (1) CN102907122B (fr)
BR (1) BR112012024000A2 (fr)
WO (1) WO2011119579A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9319850B2 (en) 2013-12-17 2016-04-19 Motorola Solutions, Inc. Group communication method and system
US20150172875A1 (en) * 2013-12-17 2015-06-18 Motorola Solutions, Inc Group communication method and system
CN105099645A (zh) * 2014-05-04 2015-11-25 北京卓越信通电子股份有限公司 一种基于半双工通信设备的多用户并发通信的方法和装置
JP6477700B2 (ja) * 2014-07-04 2019-03-06 アイコム株式会社 中継装置、通信中継方法、プログラムおよび音声通信システム
CN108833197B (zh) * 2018-04-10 2020-10-16 中国科学院信息工程研究所 一种基于云的主动探测方法和探测平台
US11728959B2 (en) * 2020-12-04 2023-08-15 Qualcomm Incorporated Method and apparatus for managing mixed transmission
CN116634589B (zh) * 2023-07-25 2023-10-20 杭州微联智控科技有限公司 一种半双工LoRa网络可靠报文收发的方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040077358A1 (en) * 2002-10-18 2004-04-22 Togabi Technologies Methods and systems for distributed arbitration in a push-to-talk communications system
US20050124365A1 (en) * 2003-12-05 2005-06-09 Senaka Balasuriya Floor control in multimedia push-to-talk
WO2008048273A2 (fr) * 2005-11-04 2008-04-24 Cisco Technology, Inc. Procédé et système permettant de réaliser une session de communication pour messagerie vocale instantanée
US7747269B2 (en) * 2006-02-27 2010-06-29 Qualcomm Incorporated System and method for providing communication resources to wireless dispatch priority users
US20080146203A1 (en) * 2006-12-19 2008-06-19 Motorola, Inc. Method and system for conversation break-in based on selection priority
US8238900B2 (en) * 2007-08-30 2012-08-07 Motorola Mobility Llc Management of anticipated data outages in a Push-to-X communication system
US8427995B2 (en) * 2007-09-24 2013-04-23 Qualcomm Incorporated Reducing an occurrence of false grants for a multicast session within a wireless communications network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2011119579A1 *

Also Published As

Publication number Publication date
CN102907122A (zh) 2013-01-30
KR20120130270A (ko) 2012-11-29
CN102907122B (zh) 2016-12-21
BR112012024000A2 (pt) 2017-07-18
JP6012590B2 (ja) 2016-10-26
KR101441779B1 (ko) 2014-09-17
WO2011119579A1 (fr) 2011-09-29
JP2013523054A (ja) 2013-06-13

Similar Documents

Publication Publication Date Title
EP2417781B1 (fr) Sessions de communication à haute priorité dans un système de communication sans fil
US9730031B2 (en) Uninterruptable group communication sessions within a wireless communications system
US9344942B2 (en) Application-layer handoff of an access terminal from a first system of an access network to a second system of the access network during a communication session within a wireless communications system
US8700081B2 (en) Determining whether to switch between group calls based on priority within a wireless communications system
US8929940B2 (en) Group communication sessions in a wireless communication system
US9025497B2 (en) Media forwarding for a group communication session in a wireless communications system
US8762460B2 (en) Group communication sessions between session participants communicating via two or more different contact protocols within a wireless communications system
KR101441779B1 (ko) 무선 통신 시스템 내의 고-우선순위 통신 세션들
US8731535B2 (en) Group communication sessions in a wireless communications system
JP5283781B2 (ja) ワイヤレス通信システム内の高優先度通信セッション

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: 20120918

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

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20131011

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20140222