Hands-free mode for a half-duplex communications system
Abstract
A communication control method in a half-duplex communication system that includes a control device (11A, 13A, 15A, 17A) and at least two terminals (1A, 1B, 1C) for transmitting and receiving voice data in a session of communication, characterized in that the control device (11A, 13A, 15A, 17A): grants at least one of said terminals (1A) an authorization to speak for a limited period of time, without requiring any action by a user of the terminal (1A) when the terminal (1A) is in a communication session; and when voice data is not detected within the limited period of time, it withdraws the authorization to speak.

Term
Term ended
Projected expiry passed 17 August 2025, 1.1 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
15 claims: 2 independent, 13 dependent
- 1ES 2 315 899 T3 REIVINDICACIONES 1. Un método de control de comunicaciones en un sistema de comunicación semidúplex que incluye un dispositivo de control (11A, 13A, 15A, 17A) y al menos dos terminales (1A, 1B, 1C) para transmitir y recibir datos de voz en una sesión de comunicación, caracterizado porque el dispositivo de control (11A, 13A, 15A, 17A):concede al menos a uno de los mencionados terminales (1A) una autorización para hablar durante un período de tiempo limitado, sin requerir ninguna acción por parte de un usuario del terminal (1A) cuando el terminal (1A) está en una sesión de comunicación;y cuando no se detecta datos de voz dentro del período de tiempo limitado, retira la autorización para hablar.
- 2Un método acorde con la reivindicación 1, en el que cuando se detecta datos de voz al término del período de tiempo limitado, la autorización para hablar se retira una vez que deja de detectarse datos de voz.
- 3Un método acorde con la reivindicación 1 o la 2, y que comprende proporcionar al mencionado terminal (1A) una indicación de que se ha concedido la autorización para hablar.
- 4Un método acorde con la reivindicación 3, en el que la indicación es una indicación visual.
- 5Un método acorde con la reivindicación 3, en el que la indicación es una indicación audible.
- 6Un método acorde con cualquiera de las reivindicaciones 1 a 5, en el que el mencionado al menos un terminal (1A) incluye un modo manos libres, concediéndose la autorización para hablar mediante el dispositivo de control (11A, 13A, 15A, 17A) sin ninguna acción del usuario cuando el terminal (1A) está en modo manos libres.
- 7Un método acorde con la reivindicación 6, en el que el mencionado al menos un terminal (1A) envía una señal al mencionado dispositivo de control (11A, 13A, 15A, 17A) cuando el dispositivo (11A, 13A, 15A, 17A) se pone en modo manos libres, el dispositivo de control (11A, 13A, 15A, 17A) tras la recepción de la mencionada señal, concediendo al mencionado al menos un terminal la autorización para hablar, sin ninguna acción por parte de un usuario del terminal.
- 8Un método acorde con la reivindicación 7, en el que la concesión de la autorización para hablar al mencionado al menos un terminal (1A), conmuta el mencionado al menos un terminal (1A) a un modo de transmisión.
- 9Un método acorde con la reivindicación 6, en el que el dispositivo de control (11A, 13A, 15A, 17A) recibe solicitudes de autorización para hablar procedentes de otros terminales (1B, 1E) en el sistema, el dispositivo de control (11A, 13A, 15A, 17A) verificando si el mencionado al menos un terminal (1A) está comunicando, y concediendo la autorización para hablar a uno de los mencionados otros terminales (1B, 1E) solo si el mencionado al menos un terminal (1A) no está transmitiendo datos de voz.
- 10Un método acorde con cualquiera de las reivindicaciones 7 a 9, en el que el mencionado sistema incluye dos o más terminales (1A, 1B) que tienen un modo de manos libres, el dispositivo de control (11A, 13A, 15A, 17A) recibiendo señales procedentes de los mencionados terminales (1A, 1B) cuando estos están en modo manos libres y, cuando se recibe dos o más de las mencionadas señales, concediendo en sucesión la autorización para hablar a los mencionados terminales (1A, 1B).
- 11Un método acorde con la reivindicación 10, en el que el dispositivo de control (11A, 13A, 15A, 17A) verifica si un terminal (1A, 1B) está transmitiendo datos de voz cuando el terminal (1A, 1B) tiene la autorización para hablar, y concede la autorización para hablar a otro terminal (1A, 1B) solo si no se está transmitiendo datos de voz desde el mencionado terminal (1A, 1B).
- 12Un método acorde con la reivindicación 10, en el que el usuario de un terminal (1A, 2A) proporciona al dispositivo de control (11A, 13A, 15A, 17A) una señal que indica que no se necesita la autorización para hablar, el dispositivo de control (11A, 13A, 15A, 17A) tras la recepción de la mencionada señal, concediendo a otro terminal la autorización para hablar.
- 13Un método acorde con cualquiera de las reivindicaciones 10 a 12, en el que el dispositivo de control (11A, 13A, 15A, 17A) incluye una lista de prioridades para los derechos de autorización para hablar, para terminales (1A, 1B, 1C) que comunican dentro del sistema, el dispositivo de control (11A, 13A, 15A, 17A) concediendo de acuerdo con la mencionada lista la autorización para hablar a los mencionados terminales (1A, 1B, 1C).
- 14Un método acorde con cualquiera de las reivindicaciones 1 a 13, en el que el sistema de comunicación es un sistema de presionar para hablar sobre celular.
- 15Un método acorde con la reivindicación 14, en el que el sistema de comunicación es un sistema GPRS.
Independent claims15
99 paragraphs in 6 sections, as filed
ES 2 315 899 T3
DESCRIPTION
Hands-free mode for a half-duplex communication system.
The invention relates to half-duplex telecommunications systems and specifically, but not exclusively, to push-to-talk over cellular (PoC) systems.
A half-duplex communication system such as PoC includes at least two terminals for transmitting and receiving voice data. These terminals communicate with each other over the system, allowing the establishment of a communication session between the terminals or (if there are more than two terminals) with a group of terminals, in such a way that a user of one of the terminals can speak, and the users of the terminal or of each of the other terminals, listen to the person speaking. Since the system is a half-duplex system, only one user can speak at a time. In view of this, it is necessary for a user to have “authorization to speak”. When a user is authorized to speak, no other user can have such authorization.
As described for example in document PCT / US2003 / 032 531, the authorization to speak can be assigned by a server of the system, according to requests for authorization to speak received from the devices. A similar system is described in document PCT / US2003 / 013 903.
A disadvantage of such systems is that they require user action ("requests to speak") before a user can acquire authority to speak. There may be circumstances where it is difficult or impossible for the user to generate a request to speak. For example, this may be the case when the terminal is in hands-free mode.
From GB-A-2 271 247 a system is known that provides a voice detector in a mobile terminal, which switches the terminal to transmit mode when voice is detected, and to receive mode when voice is not detected, to allow communication half duplex with a fixed unit operating in a bi-directional system. Document US-A-6 563 804 discloses a method for providing two-way communication in a half-duplex system, by configuring an audio card in an idle state, in a listening state, or a speaking state, and in response to events to perform. the card's transition between these states. Document WO 03/100 372 discloses a terminal with a push-to-talk function, which also includes a voice-activated transmission feature, to assist hands-free operation.
According to the invention, a method is provided for controlling communication in a half-duplex communication system that includes a control device and at least two terminals for transmitting and receiving voice data in a communication session, characterized in that the control device : grants an authorization to speak to at least one of said terminals for a limited period of time, without requiring any action from the user of the terminal, when the terminal is in a communication session; and when no voice data is detected within the limited period of time, it withdraws the authorization to speak.
Granting authorization to speak by the control device without action from the terminal user allows the user to obtain authorization to speak without operating the terminal.
In a preferred embodiment of the invention, the at least one terminal includes a hands-free mode, granting the right to speak without user action when the terminal is in hands-free mode. In this way, a user operating the hands-free mode can participate in a communication session without indicating that he needs authorization to speak.
Below is a more detailed description of an embodiment of the invention, by way of example, with reference to the attached drawing which is a schematic view of a push-to-talk over cellular (PoC) system, carried out in a general radiocommunication service by packets (GPRS, General Packet Radio Service) and including a plurality of terminals.
The third generation partnership project (3GPP) has recently defined a new concept known as IMS (IP-based Multimedia Subsystem). The objective of the IMS is to enable users, such as mobile phone network operators, to provide services to their subscribers as efficiently and effectively as possible. For example, the IMS architecture is likely to support the following types of communication: voice, video, instant messaging, “presence” (the availability to contact for a user), location-based services, email, and web pages. Other types of communication are likely to be added in the future.
This diverse collection of communication devices requires efficient session management, due to the number of different applications and services that will be developed to support these types of communication. 3GPP has chosen the Session Initiation Protocol (SIP) to manage these sessions.
The SIP protocol is a session-based protocol, designed to establish IP-based communication sessions between two or more users or endpoints. Once a SIP session has been established, communication between these points or users can take place using a variety of different protocols (e.g.
ES 2 315 899 T3 designed for audio and video in real time). These protocols are defined in the SIP session initiation messages.
One application of IMS is push to talk over cellular (PoC). PoC allows a communication session to be established between a group of devices, such that the user of the devices can speak, and the users of each of the other devices will hear that person speak. During such a communication session, each device functions as a radiotelephone or a two-way radio in a one-to-one or one-to-many group mode. Two-way voice communication between the users of the respective devices during the communication session is not possible - only one user can speak at a time.
One characteristic of PoC is that when communication is established, there is an “always on” communication connection between the devices. When a user wishes to speak to the device, or to each of the other devices associated with the communication session, the user issues an appropriate institution to their device (typically using a programmable key - that is, a key whose function is programmable), and the user's voice is captured by his terminal, and instantly or within a relatively short period of time, transmitted to the other terminal or to each of the other terminals, and reproduced in such terminals. The user does not need to enter the voice data to dial the other device or devices, and the users of the devices receiving voice are not required to take any action to receive the voice data - it is automatically played back through their device as they are received (of course, assuming the device is operating in an appropriate mode that allows PoC communication).
PoC is described in the document "Push to talk over Cellular (PoC) - Architecture, Draft Version 1.0-13 February 2004", available from Open Mobile Alliance Limited (OMA).
In the embodiment to be described, a PoC communication system is established using IMS. However, it should be appreciated that a PoC communication session according to the invention could be established over existing GSM / GPRS networks, by exchanging data packets but without IMS.
One of the advantages of PoC is that less bandwidth may be required for a PoC call (using the packet-switched domain) than for a normal voice call (using the circuit-switched domain). A circuit switched call uses network capacity for the entire duration of the call, from the initial connection attempt to the time the call ends. Network capacity is used even when voice data is not transmitted. In a PoC call, only the actual blocks of data that actually contain speech will be transmitted. A PoC communication session between devices can last one hour. However, if voice is transmitted for only five minutes at that time, only network capacity corresponding to those five minutes is used.
Referring to the drawing, a terminal in the form of a GPRS-enabled mobile device communicates wirelessly with the radio network controller (RNC) 3A (in fact through a "node B", which does not shown for simplicity). A fixed (wired) connection between the RNC 3A and the serving GPRS support node (SGSN) 5A associated with the mobile telecommunications network 7A, allows packet data to be transmitted between the mobile device 1A and the mobile telecommunications network 7A in the packet-switched domain. A gateway GPRS support node (GGSN) 9A provides an interface between the mobile telecommunications network 7A and the IMS core (SIP) 11A. The IMS 11A core contains SIP network servers and SIP registrars. The PoC server 13A is coupled to the IMS core 11A to provide functionality (which will be described in detail below).
The group and list management server 15A is responsible for managing contact lists (containing the addresses of other users), group lists (containing the addresses of other groups), access lists, and permissions. A contact is an identity of a user, or of a group. A contact includes the entity's SIP URI or TEL URI, the entity's type (user or group), and optionally the presentation name. Each PoC user has two access lists: an accept user list and a reject user list. Access lists are used to control whether or not the PoC server is allowed to send chat session requests to the user when they are requested by another user. Each PoC user can define permission management rules that describe who is allowed to contact them using the PoC service. The PoC server implements the access control policy according to these defined rules.
A presence server 17A is provided to provide the IMS core 11A with information indicating whether or not there are devices associated with the mobile telecommunications network 7A, available to contact.
The drawing shows a second network that includes elements corresponding to the elements of the first network described above, and which are designated with the same reference numerals but with the suffix "B". Data is exchanged between the IMS core 11A of the first network, and the IMS core 11B of the second network, using SIP signaling that is transmitted for example through the Internet network.
Of course, it should be appreciated that although only one mobile device 1A and 1B, and one RNC 3A and 3B, are shown associated with each mobile telecommunications network 7A and 7B, there will typically be a multiplicity of RNCs and mobile devices associated with each telecommunications network. mobiles 7A and 7B.
ES 2 315 899 T3
It is also important to note that, although in the described embodiment the mobile terminal 1A is associated with a different network 7A with respect to the mobile terminal 1B, the invention is equally applicable to a scenario in which the users of two mobile terminals associated with it mobile telecommunications network, wish to establish a PoC session.
What happens when the user of the mobile device 1A wishes to establish a PoC communication session with the user of the mobile terminal 1B will now be described.
To establish a PoC communication session, the users of the respective mobile devices will associate with each other in a group, within which PoC messages can be sent by exchanging contact information and possibly other information (such as a password).
The user of the mobile device 1A indicates that he wishes to establish a PoC communication session with the user of the mobile device 1B, by sending a command from mobile terminal 1A to the PoC server 13A, through RNC 3A, SGSN 5A, GGSN 9A and the core IMS 11A. then, the PoC server 13A will query the group and list management server 15A and the presence server 17A, to determine the permissibility and availability of the mobile terminal 1B to take part in a PoC communication session (or this information may obtained from the group and list administration server 15B and the presence server 17B of the network 7B, through the connection between the IMS cores 11A and 11B).
A PoC communication session is then established between the mobile device 1A and the mobile device 1B, by exchanging data between the IMS cores 11A and 11B. The PoC servers 13A, 13B record each user's account with their networks 7A, 7B, so that the appropriate charge can be made (when necessary) for the establishment of the PoC session.
In a PoC communication session there is only one PoC server performing a PoC control function. There could be more than one PoC server performing the participating PoC function, in the PoC session. In the described embodiment, where there are only two devices in the PoC session, the PoC server 13B will carry out a control PoC function and a participation PoC function, and the PoC server 13A will carry out a participation PoC function.
The control PoC function:
• Provides centralized PoC session manipulation.
• Provides centralized media distribution.
• Provides centralized channel control functionality, including speaker identification (for arbitration requests from PoC clients - devices 1A and 1B - for speaking authorization).
• Provides SIP session manipulation, such as SIP session organization, termination, etc..
• Provides the application of policies to participate in group sessions.
• Provide the information of the participants.
• Gather and provide centralized quality media information.
• Provides centralized billing reports.
The Participation PoC feature can:
• Provide PoC session manipulation.
• Provide media relay function between PoC client (device 1A, 1B) and control PoC server.
• Provides user media adaptation procedures.
• Provides the channel control message transmission function between PoC client and PoC control server.
• Provides SIP session manipulation, such as originating, terminating, and so on. SIP session, on behalf of the represented PoC client.
• Provides policy enforcement for incoming PoC session (eg access control, availability status, etc.).
• Gather and provide quality media information.
• Provides billing reports for participants.
ES 2 315 899 T3
Cores 11A and 11B carry out the following instructions, which are necessary to support PoC service.
• They route SIP signaling between the PoC client (devices 1A and 1B) and the PoC server.
• Provide address discovery and resolution services.
• They support SIP compression.
• They perform PoC client authentication and authorization, based on the user's service profile.
• They maintain the status of records.
• Provide billing information.
While the PoC communication session is established, the user of the mobile terminal 1A can speak (i.e. send voice data for playback on the device 1B) by pressing the programmable button 21 after which, during the PoC communication session, displays the legend "push to talk" or "PTT" on the screen 23A of the mobile terminal 1A. Of course, if more than one different terminal is attached to the communication session, a plurality of programmable keys may be provided, or an appropriate graphical user interface may be provided to allow input of a command to send data from voice, to any or the entire group of devices.
Then the mobile terminal 1A issues a SIP INVITE message (message "1.") addressed to the mobile device 1B (and if it is intended for a group of devices, addressed to each of the other devices in the group), to the IMS core 11A (through intermediate elements shown in figure 1). The message "1." may include the following items of information:
to. contact identity information
b. PoC address of the user initiating this PoC session
c. PoC service identification
d. media parameters, from client A PoC (device 1A).
The IMS core 11A passes the SIP INVITE message (message "2.") to the PoC server 13A, which verifies the availability and permissibility of the transmission of voice data to the device 1B, by consulting the group management server and lists 15A / 15B and presence server 17A / 17B, and performs an appropriate registration to upload voice data transmission (if necessary). The message "2." may include:
to. contact identity information
b. PoC address of the user initiating this PoC session
c. PoC service identification
d. media parameters, from client A PoC (device 1A).
If availability and permissibility criteria are satisfied, the PoC server 13A then identifies that the device 1B is not hosted by the PoC server 13A, and sends the SIP INVITE message (message "3.") to the IMS core 11A. The message "3." may include:
to. contact identity information
b. PoC address of the user initiating the PoC session
c. PoC service indication
d. selected media parameters (participating), PoC server 13A.
The IMS core 11A transmits the SIP INVITE message ("4." message) to the IMS core 11B associated with the second mobile telecommunications network 7B. The message "4." may include:
ES 2 315 899 T3
to. contact identity information
b. PoC address of the user initiating the PoC session
c. PoC service indication
d. selected media parameters (participating), PoC server 13A.
The IMS core 11B then transmits the SIP INVITE message ("5." message) to the PoC server 13B. The message "5." may include:
to. contact identity information
b. PoC address of the user initiating the PoC session
c. PoC service indication
d. selected media parameters (participating), PoC server 13A.
The PoC server 13B can make an appropriate registration on the account of the user of the device 1B, so that a charge is made (if necessary) to the user for the reception of the voice data. Next, the PoC server 13B generates an initiation message for the device 1B, which is sent to the IMS core 11B and transmitted to the mobile device 1B via GGSN 9B, SGSN 5A and RNC 3B. (Device 1B is not shown in Figure 3 for simplicity.)
A response message "auto-answer indication" is received from the mobile device 1B (assuming it is in a coverage area of the mobile telecommunications network 7B), and this is passed to the PoC server 13B through the intermediate elements shown in figure 1. An "ok not confirmed" message is transmitted, which warns of the successful reception of the SIP INVITATION message by device 1B (message "6."), from the PoC server 13B to the IMS core 11B, and from there to the IMS core 11A associated with the first mobile telecommunications network 7A (message "7."). The IMS core 11A of the first mobile telecommunications network transmits this message (message "8.") to the PoC server 13A. The message (message "9.") is returned to the IMS core 11A, from where it is transmitted to mobile device 1A (message "10.").
The messages "6." to "8." they may include selected PoC server media parameters 13B. The messages "9." and "10." they may include selected PoC server media parameters 13A.
The audio data received by the microphone of the mobile terminal 1A, is then captured by said mobile terminal and is transmitted to the network 7A and to the IMS core 11A as packet data, allowing the communication of this data to the IMS core 11B of the second net. These data are received by the mobile terminal 1B, where they are automatically reproduced by the mobile terminal loudspeaker as an audio signal, allowing the user of the mobile terminal 1B to receive and understand the utterance of the user of the mobile terminal 1A. The voice data is reproduced by the mobile terminal 1B without requiring any user operation, by the user of the mobile terminal 1B.
Typically, the voice data will be played back by terminal 1B virtually at the same time as it is input to terminal 1A.
The mobile terminal 1B, for example, is capable of being operated in a hands-free mode. When the terminal 1B is in a PoC session and is in hands-free mode, this is observed by the server 13A as the controlling server. The information can be communicated to the server 13A from the terminal 1B via a user-generated signal, or it can be sent as part of the SIP generated when the user registers with the network.
When the server 13A observes that the terminal 1B in a PoC session is in hands-free mode, then the server 13A will offer the authorization to speak to the terminal 1B, without any action by the user of the terminal 1B when the channel is free, it is say when terminal 1A stops talking. The availability of this authorization to speak may be indicated at terminal 1B in any suitable way, for example by generating an audible tone or by generating a visual signal such as a light. If the user of terminal 1B is using a headset, this could take the form of continuous or intermittent background noise.
Server 13A maintains authorization to speak to terminal 1B for a limited period of time. For example this can be five seconds, but it could be any appropriate time. During that time the server 13A monitors the terminal 1B for the presence of voice data. To do this, the server will need to filter out background noise. If the server 13A does not detect voice data then the server 13A will offer the authorization to speak to the next user who has made a request to speak. If server 13A detects the presence of voice data from terminal 1B, then server 13A will maintain authorization to speak to such terminal 1B until voice data is no longer present. The authorization to speak will then be offered again to the other terminal an A.
ES 2 315 899 T3
It will be appreciated that there may be more than one terminal 1B in a hands-free PoC session - for example three terminals 1B, 1C, 1D. In this case, once the channel is free, the server 13A will offer the authorization to speak to the three hands-free terminals 1B, 1C, 1D, moving in succession from one to the next when no voice data is detected, or when it is concluded. a voice data session.
The server 13A may include a priority list that gives certain terminals 1A, 1B, 1C, 1D priority in the authorization to speak against other terminals 1A, 1B, 1C, 1D. In such a case, the authorization to speak will be assigned according to the priority list maintained by the server 13A. In this case, if the hands-free terminal 1B has the authorization to speak and a request to speak is made by the terminal 1A, 1C, 1D which has a higher priority, the server 13A will withdraw the authorization to speak to the terminal 1B and pass it on to the terminal with the highest priority.
The priority list can also be used to determine the order in which authorization to speak is granted to all terminals in the PoC session, including hands-free terminals 1B, 1C, 1D.
Of course, it is possible for a server 13A to define a limit on the time a user is allowed to speak, once the presence of voice data from the user has been detected by the server 13A.
It is possible for a terminal to be enabled for voice data transmission, automatically upon receipt of the authorization to speak from the server 13A. This means that the user terminal does not need to take any action before starting to speak.
It will be appreciated that the system described above need not be implemented in a GPRS system, but could be implemented in any communication system with half-duplex capability.
References cited in description
The list of references cited by the applicant is for the convenience of the reader only. It is not part of the European Patent document. Although special care has been taken in compiling the references, errors or omissions cannot be ruled out and the EPO disclaims all responsibility in this regard.
Patent documents cited in the description • US 2003 032 531 W [0003] • US 2003 013 903 W [0003] • GB 2 271 247 A [0005] • US 6 563 804 A [0005] • WO 03 100 372 A [ 0005]
Non-patent bibliography cited in description • "Push to talk over Cellular (PoC) - Architecture", February 2004, [0015].
Contents6
1 sheet
Sheet 1
13 members in 8 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 0418504 | United Kingdom | A | |
| 0418504 | United Kingdom | A | |
| 20040018504 | United Kingdom | – | |
| 057717760418504 | – | – | – |
| GB20040018504 | – | – | – |
Members13
| Document | Office | Kind | |
|---|---|---|---|
| GB0418504D0 | United Kingdom | D0 | |
| WO2006018635A1 | World Intellectual Property Organization (WIPO) | A1 | |
| GB2417859A | United Kingdom | A | |
| EP1787484A1 | European Patent Office (EPO) | A1 | |
| CN101040547A | China | A | |
| US2008045257A1 | United States of America | A1 | |
| EP1787484B1 | European Patent Office (EPO) | B1 | |
| AT410037T | Austria | T | |
| ATE410037T1 | Austria | T1 | |
| DE602005010098D1 | Germany | D1 | |
| ES2315899T3This record | Spain | T3 | |
| US8170595B2 | United States of America | B2 | |
| CN101040547B | China | B |
Numbers
- Publication
- 2315899
- Publication, DOCDB
- 2315899
- Publication, EPODOC
- ES2315899T
- Application
- 5771776
- Application, DOCDB
- 05771776
- Application, EPODOC
- ES20050771776T
Titles2
- Spanish
- MODO MANOS LIBRES PARA UN SISTEMA DE COMUNICACIONES SEMIDUPLEX.
- English
- HANDS-FREE MODE FOR A SEMIDUPLEX COMMUNICATIONS SYSTEM.
Classification
- CPC, 5
- H04W4/10
- H04W84/08
- H04L65/4061
- H04L65/1016
- H04W76/45
- IPC, 2
- H04W4 10
- H04W84 08