Setting up full-duplex communication session and transitioning between half-duplex and full-duplex modes during communication session in wireless communication system

This patent application claims priority to US provisional application number 61/188590, entitled "SYSTEM AND METHOD FOR TRANSITIONING BETWEEN HALF-DUPLEX AND FULL-DUPLEX COMMUNICATION SESSIONS BETWEEN WIRELESS COMMUNICATION DEVICES", filed August 11, 2008, which is incorporated into this document by reference.

TECHNICAL FIELD OF THE INVENTION

Embodiments of the invention are directed to establishing full-duplex communication session and transitioning between half-duplex and full-duplex mode during a communication session in a wireless communication system.

Description of Related Art

Communication sessions can conventionally be initiated either as half-duplex sessions (e.g., PTT), or both full-duplex sessions (e.g., VoIP). When synchronous full-duplex connection is required between the two communication devices, for example a phone call between the two phones, commonly occurring is to instruct one device to try to begin to communicate and organize the connection by contacting with another device. The telephone system then either sends a signal or organizes channel full-duplex communication based on the channel switching to the other device, and an interactive device then broadcasts a warning such as a buzzer or other audible alert, and can also give a visual alert, such as flashing lights, or Activity display to inform the user next to the device that the other communication device is trying to organize the communication. The user then responds communication devices, and full duplex then arranged, or if the connection is already organized, the channel is maintained.

In the current telephone systems the amount of system overhead in order to start and then try to organize a full-duplex telephone call, can be significant. How to start a call typically starts with a customer that he intends to carry out a phone call, for example by lifting the handset or pressing the button for the active line, and then the telephone system receives telephone number determines the scheduled number, sends the appropriate alarm or arrange channel connection to another device and waits to receive a call. This process lasts on average 10 seconds, and uses a large amount of system overhead during the entire process. In calling device provides some functionality, such as speed dial, which allows you to accelerate the process of the call setup, but it is only partially reduces call setup.

Provided wireless service that provides a rapid half-duplex voice communication, "one-to-one" or "one-to-many", which is generally referred to as a support mode switching between transmission and reception "(PTT). Specific PTT- Group devices recipient to exchange data wireless device is usually installed network operator and the connection PTT-connection is typically initiated by a single button press on the wireless device that activates a line half-duplex communication between the speaker and the device of each member of the group, and when the button is released, the device may take incoming PTT-transmission. In some arrangements, the PTT-speaker has a "permission to transmit" in which other members can not talk at the time when the speaker is activated the PTT-button on his device. Once the speaker releases the PTT-button, any other Individual group members can activate their PTT-button, and he receives permission to transmit.

System PTT-provider does not use a system of "make calls" similar to a standard telephone system, but instead opens a communication channel to the target wireless device after a member of the group given permission to speak, and the user has permission to transfer just starts talking, wherein it is received and broadcasted to the target devices. Thus, in a style of "portable telephone", speech from the initiating wireless device simply is broadcast from the receiving wireless device, and "response" is not required at the receiving wireless device. Since the original is a half-duplex voice communication to the target device can communicate with the initiating wireless device (or other members of the group), the user presses the target device PTT-button sends a request for permission to transmit, to try to get permission to transfer to the session. Thus, multiple group member devices of PTT-exchange group is not parallel to the multimedia data in a half-duplex session, as in full-duplex mode.

Disclosure of invention

In an embodiment, the originating device sends a request to the server to initiate a full-duplex session with a target device. In response to a request for half-duplex full duplex session is established from the originating device to the target device before you installed full-duplex conversation. The target device indicates your acceptance half-duplex session takes half-duplex media from the initiating device and selectively indicates your acceptance full duplex session. In another embodiment, during the session, currently supported by either half duplex or full-duplex mode, the server is responsible for regulation of the session receives a request from one of the participants of the session to session to transfer to another type of duplex. The server then performs selectively replace duplex mode session.

BRIEF DESCRIPTION OF DRAWINGS

1A is a characteristic diagram of a pair of communication devices in which the originating communication device opens a channel half-duplex connection to a target device on the network group connection with the intention to organize the "quick call" to him.

1B is a characteristic diagram of communication devices 1A, in which the target communication device receives the "quick call" from initiating communication device on the network group communication.

1C is a characteristic diagram of communication devices 1A and 1B, in which the full-duplex communication is organized between devices over the wireless network.

2 is a characteristic diagram of a wireless network, wherein said PTT-band wireless devices communicating with a group communication server and other computer devices on the wireless network.

3 is a characteristic diagram of one embodiment of a wireless network in a common cellular configuration, which provides the group communication server, which manages the exchange of data between wireless devices-PTT group members, and the active call controller that can selectively handle full-duplex communication between the devices after establishing connection through the group communication server.

4 is a block diagram illustrating the computer platform of the wireless communication device, here shown as the implementation with PTT-enabled.

5 is a flowchart of processing session establishment process full-duplex communication session by first establishing a half-duplex communication in accordance with an embodiment of the invention.

Figure 6 illustrates a detail of Figure 5 the process in terms of the session target in accordance with an embodiment of the invention.

7 illustrates in detail the process of Figure 5 in terms of a group communication server in accordance with an embodiment of the invention.

8 is a flowchart of processing a session that passes between half duplex and full-duplex communication in accordance with an embodiment of the invention.

9 is another flowchart of processing a session that passes between half duplex and full-duplex communication in accordance with an embodiment of the invention.

10 is a flowchart of a method for one embodiment of the transfer current half-duplex session between an originating device and a target device to a full-duplex session in response to the request for changing duplex, taken from one of the session participants.

11 is a flowchart of a method for one embodiment of the translation of the current full-duplex session between an originating device and a target device to a half-duplex session in response to the request for changing the duplex mode from one of the session participants.

12 is a flowchart of a method for one embodiment of a process performed by a session participant involved in the half-duplex communication session when another session participant half-duplex communication session requests a transfer of a half-duplex mode in a full duplex mode in accordance with an embodiment of the invention.

EMBODIMENTS

Aspects of the invention are disclosed in the following description and related drawings directed to specific embodiments of the invention. Alternate embodiments may be devised without departing from the scope of the invention. Additionally, well-known elements of the invention are not described in detail or omitted so as to not detract from the important details of the invention.

In this specification, the terms "communication device," "wireless device," "wireless device," "PTT-communication device," "handheld device", "mobile device" and "handset" are used interchangeably. The terms "call" and "communication" are also used interchangeably. The term "application" as used herein is intended to encompass executable and nonexecutable software files, raw data, aggregated data, patches, and other code segments. The term "half-duplex" means transmission in only one direction at a time (not simultaneously or bi-directionally), thus, after the exchange data device starts to receive a half duplex signal, it must wait for the termination of the transmission from the transmitter to the response, which is a commonly occurring in PTT-system communications. The term "full duplex" means that the data exchange can be carried out simultaneously in both directions between the devices exchanging data, which is a commonly occurring when a voice telephone call. Further, like numerals refer to like parts in several views, and the articles "a" and "the" include plural references, unless otherwise specified herein.

The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other embodiments. Similarly, the term "embodiments of the invention" does not require that all embodiments of the invention include those described feature, advantage or mode of operation.

Further, a plurality of embodiments described with respect to sequences of actions to be performed, e.g., by elements of a computing device. It should be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASIC)), by program instructions executed by one or more processors, or by a combination and order of both. Additionally, the sequence of actions described herein can be considered as fully implemented as part of any form of a computer readable medium with stored thereon an appropriate set of computer instructions that, when executed, should encourage an associated processor to perform the functions described herein. Thus, the various aspects of the invention may be implemented in a number of different forms, all of which are assumed to be within the scope of the claimed subject matter. In addition, for each of the embodiments described herein, the corresponding form of any such embodiments may be described herein as, for example, "logic configured to" perform the described action.

A subscriber station according to the standard high speed data (HDR), referred to herein as an access terminal (AT), may be mobile or stationary, and may communicate with one or more base HDR-stations, referred to herein as a two-way radio modem pool (MPT) or base stations (BS). An access terminal transmits and receives data packets through one or more transceivers modem pool controller-HDR base station controller called a modem pool (MPC), base station controller (BSC) and / or packet control function (PCF). Transceivers and modem pool controllers are parts of a modem pool of a network called an access network. The 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 transceivers modem pool 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 transceivers modem pool 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 only) Card PC Card, the card Compact Flash, external or internal modem, or wireless or wireline phone. The communication link through which the access terminal sends signals to the transceiver modem pool called a reverse link or traffic channel. The communication link through which a transceiver sends signals to the modem pool to an access terminal is called a forward link or traffic channel. As used herein, the term "traffic channel" may be referred to or both forward or reverse traffic channel.

In reference to the drawings, wherein like numerals represent like elements, Figures 1A-1C illustrate and provide a general idea of ​​using half-duplex communication between the devices 10 and 12 bond shown here as mobile telephones, as the initial contact attempt prior to the organization full-duplex communication therebetween. In other words, the embodiment is directed to establishing a temporary half-duplex session from the originator to one or more target devices during the establishment or initiation of the controlled server communication session that may eventually go into full-duplex session. 1A-1C illustrate the general idea of ​​the principle which is described in more detail below with respect to other embodiments.

1A is a characteristic diagram of a pair of devices 10 and 12 of connection, where the originating communication device 12 opening a half-duplex communication channel A to the target communication device 12 over the network 16, the group communication such as mobile communication network, which acts as a host for half-duplex PTT- Communication between the members of the wireless devices. Here, the originating device 10 (or apparatus # 1 in this scenario) should organize the "fast call" to the destination apparatus 12 (or apparatus # 2) displayed on the display 18 of the device 10, and a request for an incoming quick call is displayed on the display 20 of the device 12, informing the user device 12 that the request comes from a quick call to the device 1. As used herein, a "quick call" matches any delay sensitive regulated server communication session (eg half-duplex session, full duplex session, PTT-session, VoIP -seansu etc.). The information displayed on the display 20 on a request for a quick call, can be provided by a group communication server (74 in Figure 2), or alternatively, may have come from the initiating device 10.

Furthermore, in one embodiment, it may be sent from the originating device 10 via a half-duplex PTT communication-to audibly send information to the user at the target device 12, with the request for a quick call. "Warning" for requesting a quick call can be similar to a typical telephone "call", but can be audible or physical (eg, vibration) warning and can last for a predetermined duration, for example 5 seconds to provide the user of the target device 12 is a reasonable time to determine whether he wants to or not to perform a quick call. Thus, if the alert from the initial PTT-call is beep call sent from the originating device 10 wireless communication target device 12 can simply press the "answer", in case of a conventional telephone call, and the use of PTT-connection to establish the dial call can be completely transparent to the users of the devices 10 and 12.

1B shows a receiving apparatus 12 through the communication target shortcut, as shown in the display 20. With regard to Figure 1B, the target communication device 12 sends an acceptance B to a group communications server 74 within the network 16, the group communication, which then forwards an indication regarding receiving target device 12, a triggering device 10. Thus, half-duplex communication channel A is maintained from the originating device 10 for the initial contact with the target device 12 at a time when the reception of the shortcut is processed and full-duplex communication channel C is established between the target device 12 and a triggering device 10.

In this embodiment, after receiving the shortcut is adopted, full-duplex channel C is established between the device 10 and the connection 12, as shown in Figure 1C. Full duplex communication C arranged between devices 10 and 12 over a wireless network connection 22, which may be a group communication network 16 or any other full or partially wireless network. As further described below, the originating device 10 and the target device 12 can have IP-addresses, and thus, control channel full duplex communication may be terminated by the server 74, group communication and maintained as a batch VoIP-traffic between the respective assigned addresses of devices 10 and 12. Communications . Alternatively, as shown in Figures 2 and 3, another device, such as controller 78 of active calls, can be used to serve the set full-duplex communication, to reduce the overhead on the group communication server 74 to maintain the full duplex channels. Nevertheless, the group communication server 74 and group communication network 16 can maintain and / or control the full-duplex communication completely.

In the example as described in more detail below, the channels C full-duplex communication session may correspond to the call sender maintaining its half-duplex channel A and the task for the target (s) of the initial call to receive its own channel. Thus, the half-duplex channel call the sender should not be split and re-initialized during the transition from half-duplex to full-duplex communication mode.

2 illustrates one embodiment of the system 60, wherein the group communication server 74 configured to regulate communication sessions between one or more wireless devices in group PTT-62, such as wireless telephone 64, smart device 66 a paging and / or a personal digital assistant (PDA) 68, and other wireless communication devices over wireless network 70. In the system 60, each device 64, 66, 68 wireless communication permits the selective and direct communication network 70 by wireless communication with the target set of one or more other devices Wireless communication via half duplex and / or full-duplex communication. For example, the target set for mobile telephone 64 can be all devices in the communication group 62 or a subset thereof, such as a paging device 66 and PDA 68. Other communication devices may alternatively be used in the present system that can have other wired network connections, provided that such devices are given the opportunity to participate in half-duplex PTT communication-or full-duplex communication, if such a server 74 through a group communication.

In an embodiment, the computing device to the group communication, shown here as group communication server 74, which is present in the server LAN 72 to the wireless network 70 is adapted to indicate that the wireless device is present, i.e. It is available on the wireless network 70. The group communication server 74 may use this information in conjunction with the set of target wireless communication devices by means of said first wireless communication device, or may also use this information in conjunction with other computer devices resident on a server located in LAN 72 or accessible over the wireless network 70. The group communication server 74 may be connected or accessible database 76 of data to keep the identity of the group for the wireless devices. Thus, the group communication server 74 handles the implementation of the control group communication sessions within the network. Additionally, the group communication server 74 may represent multiple group communication servers 74 in the network, with each group communication server 74 regulates sessions in different areas of the network. It will be appreciated that the number of computer components resident on server-side LAN that are placed in 72 or 70 in a cellular network, or, in general, the Internet is not limited.

In the example, a direct connection, such as PTT-connection can be established via a half-duplex channel between a device to exchange data 64, 66, 68, and a wireless communication with one or more other wireless communications devices of the target set. Computing device 74 for the group communication can also inform device 64, 66, 68 wireless communication of the impossibility to organize direct communication with the target set 62 when either one of wireless communication devices (or at least one) of the target set not inform the computer device 74 for group communication of its presence in the wireless network 70. In addition, although the computing device for group communication 32 is shown here as having a base connected 76 data identification data group computing device 74 for group communication can be the identity of the resident groups and perform all the functions of storage, described herein.

Thus, in an embodiment in an attempt to organize the end full duplex synchronous communication is accomplished by sending an initial request for half-duplex communication with switching between transmission and reception of the originating PTT-member group 62 to another target communication device such as mobile phone 65. The target communication device 65 then receives the PTT-link data shortcut from the initiating communication device (or does not accept, if the target communication device implemented to manage this functionality), and defines the "answer" to whether or not a quick call, as shown in fig.1A- 1C. In this embodiment, the organization is to attempt receiving half-duplex communication at the target device (s) connection, as opposed to the organization of full duplex voice channel to the originating device such as occurs when carrying out conventional telephone call. However, speech or other data (e.g., a notification message is configured to notify the communication session) carried in the half-duplex transmission from the originating communication device require immediate delivery, so such an attempt to communicate is still attempt Synchronous bond.

Also in the embodiment of Figure 2 shows the active call controller 78 that can be used to locate and / or control the full-duplex communication channels after a transition from the 74 half-duplex communication mediated by the group communication server. This embodiment thus provides the group communication server 74 able to transmit full-duplex communication channel service since the establishment in order to reduce the overhead server 74.

While group communication is typically half-duplex voice data are used between members 62 that group communication can be voice, applications, graphic media, such as pictures in JPEG, TIF, and the like, or audio files such as MP3, MP4, WAV, etc. .P. Media can also be streaming media, such as a multimedia application (PowerPoint, MOV-image, etc.).

Thus, in overview, the system 60 provides for the organization of full-duplex communication channel between two wireless communication devices, such as devices 10 and 12 regard 1A-1C, across a network 70 wirelessly. The triggering device 10 is configured to organize one or more channels of full-duplex communication with one or more devices 64, 66, 68 communication network 70 wireless communications and triggering device 10 is further configured to selectively send half-duplex communication to one or more devices 64 66, connection 68, e.g. PTT-connection. At least one device 64, 66, 68 wireless communication similarly configured to organize one or more channels of full-duplex communication with one or more devices 64, 66, 68 communication at least partially over the network 70 the wireless communication, and that the device wireless communication is further arranged to selectively receive half-duplex communication from one or more devices 64, 66, 68 connection. The group communication server 74 controls group communications between the plurality of wireless devices 62 communicate over a network 70 of a wireless communication link with the original group consisting of half-duplex communication between the originating wireless communication device (mobile phone 10) directed to wireless communication devices of other members of the group communication. After sending by the device 10 the wireless communication half-duplex communication to a target wireless device 12 via the server 74, group communication target wireless device 12 then receives the (confirmed) and sends an acceptance to the originating device 10 is a wireless communication via the server 74, group communication, the server 74, group communication Next, a full-duplex communication between the originating wireless communication device 10 and target wireless communication device 12.

In one embodiment, the half-duplex communication and ultimate establishment of a full duplex communication is performed through the exchange of protocol data packets "Voice over Internet Protocol (IP)" (VoIP) exchanging data between devices. Consequently, the group communication server 74 can further be configured to receive the assigned network addresses (typically assigned by a PDSN 82) to the originating wireless communication device 10 and target wireless communication device 12 to stop the control after the establishment of full duplex communication. In the case of full-duplex mode to be appreciated that the group communication server 74 still receives media from group members and forwards the media to other group members, but the group communication server 74 is not responsible for the implementation of control permits the transfer when operating in full duplex mode. As shown in Figures 2 and 3, the group communication server 74 can further be configured to transmit control full-duplex communication to another computer device, such as active call controller 78 or other media controller.

In one embodiment, the originating wireless communication device 10 may further be arranged to selectively instruct the target wireless communication device 12 to take full duplex or half-duplex communication and enable establishment of communication. For example, a mobile device that is intended to be used by a child can be configured to allow the parent to instruct the mobile device to open full-duplex or half-duplex communication to the originating device such that the parent of the child may instruct the phone to answer. The parent can use this feature to monitor the activity of the child, for example, this feature can also be used in child abduction cases, when a child is a mobile device.

3 is a characteristic diagram of one embodiment of a wireless network in a common cellular configuration having a sequence of computer device 74 to the group communication (group communication servers) that controls the exchange of data between wireless communication devices set group members (devices 100 102 104 106) in PTT-system. The wireless network is merely exemplary and can include any system whereby remote modules communicate over a radio interface between them or with components of a wireless network 70, including, without limitation, carriers for a wireless network and servers. A number of group communication servers 74 are connected to the LAN 50 server group communication. Wireless telephones can request packet data sessions from the group communication server 74 using a data service option. Furthermore, in the server LAN 80 shows a controller 78 calls active, like the controller described in Figure 2.

The server (s) 74 is connected to a group communication serving packet data node (PDSN), a wireless service provider, such as PDSN 82, shown here resident being placed on the network operator 84. Each PDSN 82 can interface with a base station controller 94 to base station 90 through a packet control function 92 (PCF). PDSN 82 typically have to assign network address of wireless communication devices, such as network IP-addresses for VoIP-connection. PCF 82 is typically located in the base station 90. The network operator 84 controls messages (generally in the form of data packets) sent to the center 88 mobile switching (MSC). The network service provider 84 communicates with the MSC 88 by a network, the Internet and / or POTS (POTS). Typically, the network or Internet connection between the network operator 84 and the MSC 88 transfers data, and the POTS transfers voice information. MSC 88 may be connected to one or more base stations 90. Similarly, the operator's network, MSC 88 is typically connected to a base transceiver station (sometimes referred to as "channel to the source") (BTS) 96posredstvom network and / or Internet for data transfer and by POTS for voice information. BTS 96 ultimately broadcasts and receives messages wirelessly to and from wireless devices such as cellular telephones 100 102 104 106, by short messaging service (SMS) or other methods of transmission over the radio interface known in the art. Also note that the boundaries of the network operator and / or border-PTT operator network do not interfere or prohibit the sharing of data as described herein.

Cellular telephones and mobile communication devices, such as wireless telephone 100, are produced with enhanced computing capabilities and are becoming tantamount to personal computers and hand-held PDA. These "smart" cellular telephones allow software developers to create software applications that are downloaded and executed by a processor of the wireless device. The wireless device, such as cellular telephone 100, can download many types of applications, such as web pages, applets, MIDlets, games and data. In wireless devices that have a specified connection group 62 (2), the wireless communication device can directly connect with the other member of the set and engage in a communication session and speech. However, all communication sessions that can be "regulated server", which means that the communication sessions must be carried out or managed by the group communication server 74. Each data packet devices need not pass directly through the server 74, group communication, but the server 74, group communication should be able to ultimately control the communication session because it is typically only the server 80 the component that has the information and / or can retrieve the identity of the members of the group communication or guide members of the group identification data 62 to another communication computing device.

4 is a block diagram illustrating one embodiment of a communication device (the initiating or target), which is a mobile phone 110 with the PTT-button 112 that opens the direct communication to a target set of devices, i.e. with other members of the 62 bond. Wireless device 110 is also shown as having a graphics display 114 to the user of the wireless device 110 and microphone 115 which may be used to capture the audio near the device 110. The wireless device 110 also includes a camera 113 that can capture video data from the next device .

The wireless device 110 includes computer platform 116 that can handle voice packets and data packets, and receive and execute applications transmitted across the wireless network 70 to include the group communications. Computer platform 116 includes, among other components, an application specific integrated circuit (ASIC) 122, or other processor, microprocessor, logic circuit, programmable gate array, or other data processing device. ASIC 122 is installed during manufacture of the wireless device and is not normally supported update. ASIC 122 or other processor executes 124 the level application programming interface (API), which includes the resident application environment, and can include the operating system loaded on ASIC 122. Resident programs can be stored in the memory 126 of the wireless device. An example of a resident application environment is the software Binary Runtime Environment For Wireless (BREW), developed by QUALCOMM® platform for wireless devices.

As shown here, while the wireless device can be a cellular telephone 110 with a graphics display 114, in alternative embodiments the wireless device can correspond to any type of wireless device with a computer platform 116, known in the art, such as a personal digital assistant (PDA), device paging a graphics display 114, or even a separate computer platform 116 that has a wireless communication portal, and may otherwise have a wired connection to a network or the Internet. Additionally, memory 116 may include read or random access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory device, for a standard computer platforms. The computer platform 116 also can include a local database 118 for storing data applications not actively used in memory 126. Local database 118 typically includes one or more flash memory cells, but can be any secondary or tertiary storage device, It is known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or a programmable or hard disk.

In this embodiment, the wireless device computer platform 116 of Figure 4 also includes a communication interface 120 that can open communication channels from the wireless device (e.g., for voice calls, full-duplex calls, half-duplex calls, PTT-sessions, VoIP sessions- etc.). Direct communication interface 120 may also be part of the standard communication interface for the wireless device which ordinarily carries the voice and data transmitted to and from the wireless device. Communication interface 120 typically includes hardware as is known in the art.

In the example, when embodied as the target wireless device 12 including a microphone 115 for recording sound and the target wireless device 12 capable of forcibly be instructed to respond to a request for a quick call and open full-duplex communication, the originating device 10 wireless communication may further be operable to selectively activate the microphone 115 at the target communication device 12, after instructing the forced full-duplex communication. The target apparatus 12, respectively, may be further adapted to selectively allow the establishment of full duplex instructing forced channel and selectively allow the activation of the microphone 115, for example, through a predetermined setting on the device.

5 is a flowchart of processing session establishment process full-duplex communication session by first establishing a half-duplex communication in accordance with an embodiment of the invention. With regard to Figure 5, the sender of the session (e.g., PTT-client 132) sends a call request 134 to the group communication server (GCS), the session initiation request to a full-duplex PTT-connection of at least one target of a session ( e.g., PTT client-138), step 500. In the example, the call request at step 500 may contain the address (es) of the intended user group identifier of the application, the request to establish a group, etc. In a further example, the call request may also be sent in the access channel message type "data signal together with service" (DoS). Tip (request message to the user) on the establishment of the call is further configured to indicate to GCS 134, the intention of the sender's session, first establish a session as a half-duplex mode, given that the session may later go into full duplex mode after the target call takes transition in full-duplex mode (for example, by means of answering a call). It will be appreciated that the sender of a session may send messages on the channel access on the reverse link without the need for a dedicated traffic channel over which should be transmitted, so that the access channel message DoS can potentially be sent to GCS 134 more quickly as compared with a setup message a call which is sent to the TCH. GCS 134 (e.g., from the dispatch call processor (DCH)) performs the function of establishing PTT-call step 504 involves finding the target, applying call restrictions, and selection of the vocoder. GCS 134 also checks whether or not to allow the target participate in a communication session, step 508. GCS 134 then sends the notification message via the serving BSC 136 target session which notifies full-duplex communication session, step 512. It should be appreciated that a notification message is configured to notify, "potential" full duplex session, in the sense that the session was originally to be half-duplex, and should go into full duplex mode after the target receives a call transition. In an embodiment, the notification message sent in step 512 may be configured to forcibly accept the session so that the target accepts the call without intervention. Alternatively, the notification message need not be configured in this manner.

Session target (e.g., PTT client-138) receives an incoming call notification message in step 512 and then determines whether or not the target is busy session object, so that the call can not be accepted, step 516. For example, if the session target is already involved in another communication session, the session target may reject notified session. Otherwise, if the target session object determines that it is not busy, the target session sends the call reception on the reverse link channel (e.g., channel access in uplink) to the BSC 136 in order to be redirected in GCS 134 520. In the example, the call reception at step 516 and 520 can be "automatic" or forced in the sense that the user-PTT client 138 is not permitted to reject the session. Alternatively, the PTT-user client 138 may deliberately choose to take the session. Provided that the BSC 136 determines that sufficient resources are available to support the communication session, step 524, BSC 136 forwards the call accept message in GCS 134, step 528. Upon receiving the call from the first receiving transponder for a notification message, step 528, step 532, GCS 134 sends a message to the authorization of the transfer of the sender session, step 536, and the sender of the session acknowledgment message granting permission for the transfer, step 540.

Here, along with the ACK-message granting permission to transfer, the sender starts redirecting the multimedia session to be sent to at least one half-duplex session target object method. In other words, the session target does not necessarily have a traffic channel (TCH), to transmit media back to the sender session, a full-duplex manner. Thus, here, when the sender of the session has permission to transmit, the communication session at this point is half-duplex even though the session requested for initiation at step 500, a full-duplex session. Accordingly, the interim half-duplex session is established to facilitate the redirection of the initial sender of the multimedia session target object session before the session is established full-duplex.

Accordingly, GCS 134 receives the media (e.g., voice and / or other data) from the sender to the session and forwards the media to the BSC 136, step 544, for transmission to the target session object, step 548. During participate in half-duplex session that is initially set between the sender of the session and the target session, the target session either (i) automatically "answers" the call to obtain call resources for participation in the full-duplex communication, or, alternatively, (ii) outputs the message to the target session, to request, the user wants take part in the session only as a student or as an active participant. In this example, assume that the target determines the session to answer the call and take part in a session full duplex manner. Accordingly, at some point, assume that the session target obtains the resources required to participate in the session, a full-duplex manner. In other words, if necessary, the session target can obtain TCH, on which to send the multimedia session back to the sender (for example, even if the session target may already have a TCH, in which case the initialization of additional TCH is not necessary). Here, the session target sends another call accept message to the BSC 136, step 552, which is forwarded to the GCS 134, step 556. It should be appreciated that messages the call reception at step 520 and 552 are sent in response to notification message 512, and the first message receiving a call at step 520 indicates the reception by the target temporary half-duplex session, and the second message receiving a call reception and 552 indicates a willingness by the target to participate in the session through a full-duplex mode. In an alternative embodiment, although not shown in Figure 5, the notification message 512 may be two separate notification message so that the first notification message may be sent to notify the half-duplex communication session and the second notification message can be sent later (step 552 but before ) to notify the full-duplex communication session.

GCS 134 then learns that half-duplex session can pass in a full-duplex conversation. In fact, GCS 134 sends a message to the authorization of a challenge to every active participant session (for example, the sender of the session and the session target object), block 560, and 564. The message of permission to challenge includes instructions about the network object to handle the implementation of Regulation full-duplex session, which is not necessarily the GCS 134. For example, a service session can be transmitted to the controller 78 of the active-call or PTT clients 132 and 138, step 568 (such as, for example, if implemented with network address assignment for VoIP-communication). In the example, the call resources allocated to the sender of the session for the temporary half-duplex session can be maintained and re-used during the full-duplex session, so that the sender's call resources need not be torn again and again initialized. Thus, the half-duplex session may only be terminated in the sense that a return path is added upon conversion to full-duplex in an example.

Accordingly, Figure 5 shows how delay-sensitive call setup procedures typically associated with half-duplex sessions can be used to establish a full-duplex communication session more quickly, such that a temporary half-duplex session is established, and then the final transformation in full duplex mode. In the example, the process of Figure 5 can be implemented for full-duplex sessions that are considered sensitive to delay (for example, "Quick Call"). Alternatively, possible is that the process of Figure 5 can be used to establish a full-duplex communication sessions.

Figure 6 illustrates a detail of Figure 5 the process in terms of the session target in accordance with an embodiment of the invention. With regard to Figure 6, notice of a full-duplex communication session (e.g., PTT), which is temporarily initiated as a half-duplex communication session is received in the target session, step 150 (e.g., a notification message for PTT-call made at step 512 of Figure .5, which can be interpreted as a notification for the half-duplex and full-duplex session session). Session target determines whether or not half-duplex communication session is accepted, in step 152 (e.g., similar to step 516 of Figure 5). If the target session determines that the notification half-duplex communication session can not be taken, the target transmits a session reject the call (for example, notification ACK-message (with deviation)) in GCS 134, step 160. Otherwise, if the target object Session determines that can take a half-duplex communication session, at step 152, then the half-duplex communication session is received at step 154 ​​(e.g., by sending a call accept message, similar to step 520 of Figure 5). In the example, the reception in step 154 ​​or may be automatically provided that the target session is capable of receiving a session half-duplex communication (e.g., if the incoming request to perform communication in step 150 is configured to forcibly accept the session) or alternatively may be based on intentional taking of a user session target session.

Upon receiving the half-duplex communication session in step 154 ​​the session target determines whether or not half-duplex communication session is notified potential for transfer to a full-duplex session. In other words, the notified sessions are typically half-duplex communication half-duplex in nature. Indeed, even in Figures 5 and 6, the session begins as half-duplex even if in the end it is carried out in full-duplex transfer mode. Thus, at step 156, the session target determines whether or not that particular half-duplex communication session potential transfers duplex session (e.g., based on the configuration of the header in the notification message-PTT, etc.). If the target session determines that the session is a half-duplex communication is a "typical" half-duplex session (e.g., destination session is to be half-duplex and not to pass subsequently in a full duplex mode) in step 156, the process returns to step 154, and the target session object participates in the session via half-duplex protocols, as is known in the art.

Alternatively, if the target session determines that the communication is initially a half-duplex session, but has an additional potential for transfer to a full-duplex session in step 156, the target session gives its user a clue as to want or not the user "answer" to the challenge , step 164. In other words, the response to the call in this case means to participate in a communication session as the other speakers, which means to transfer a session in full-duplex mode. In an alternative example, the issuance of tips of step 164 may be skipped, and the target object can forcibly session instructed to transfer to the session in full-duplex mode (for example, if an incoming request for the implementation of communication in step 150 is configured to forcibly take the session). Target session determines whether or not the user receives prompts, step 158. If not, the target transmits a session reject the call in the GCS 134, step 160. In this case, a message rejecting the call can be configured to either (i) to reject full-duplex nature of the call at the same time resolving the target object session to continue to participate in a half-duplex PTT-session character as a listener, or (ii) completely reject the session and in general to interrupt the session. Alternatively, instead of transmitting a message rejecting the call session target may simply refuse to send a second message receiving a call in step 162, and the GCS 134 interprets the absence of the second message as a rejection of the call reception transfer in full-duplex mode. In another embodiment, the second call reception (full-duplex) set optional, and the sender may consider receiving media from the target object as an implicit confirmation that the target takes full duplex.

Otherwise, if the target session determines to answer the call (for example, automatically or on demand by the user) and to participate in full-duplex session, the target session sends to the GCS 134 Post receiving a call, that indicates that the interim half-duplex session can now move into full-duplex session (e.g., similar to 552 of Figure 5). Post the call reception at step 154 ​​(or 520 of Figure 5) and 162 (or 552 of Figure 5) in the example may be configured similarly, with the GCS 134 interprets the first received call accept message as an acceptance half-duplex portion of the session, and the second receiving Message receiving a call as reception transition to full duplex mode for the session. Although not shown in Figure 6, during this period before the transfer is carried out in full-duplex mode, the session target can monitor a downlink channel and receive media from the sender to the session half duplex manner. In step 166 the session target determines that the requested full-duplex session is established within the threshold time period. If not, the session target transmits a call reject message GCS 134, 160. Otherwise, the full-duplex session is established and the establishment process of Figure 6 terminates.

7 illustrates in detail the process of Figure 5 in terms of the group communication server 134 in accordance with an embodiment of the invention. With regard to Figure 7, the server 74 or 134 receives a request for the group communication (e.g., a specially configured call setup message) to initiate a full-duplex communication session by first establishing a half-duplex communication channel from the originating communication device 10, step 170. The server group 74 or 134 Communication then obtains a network address such as an IPv6-address for the originating device 10, step 172, and likewise obtains the network address of the target device 12, step 174, so that the server 74 or 134 of the group communication can control the data exchange between the initiator and target devices 10 and 12 (a straight Immer, using VoIP-packet). The server 134 of the group communication is then set or arrange a half-duplex channel from the originating device 10 to the target apparatus 12, the stage 176 (for example, by instructing the access network to allocate reverse link channel on which the originating device 10 can transmit data, while the dedicated channel downlink on which the target device 12 can receive data). In addition to establishing a half-duplex channel from the originating device 10 to the target device 12, the group communication server 134 sends a notification message notifying the full-duplex communication session to the target communication device 12, step 178. Thus, by first establishing a half-duplex channel, media from the originating device 10 may be sent to the target device 12 more quickly, and the target device 12 can attempt to move in a full-duplex session in parallel with receiving media from the originating device 10 via the half- duplex channel.

After sending the notification message to target device 12, in step 178 the group communication server 134 determines whether or not accept the target device 12 full-duplex communication session, step 180. For example, the determination of step 180 may consist in the fact that the target device 12 receives the full-duplex communication session, if the target device 12 sends a message to call reception at step 162 of Figure 6. If full-duplex communication session is not accepted by the target device 12 at decision step 180, then the failure indication is output (e.g., in the originating device 10) and the process ends. Otherwise, if the full-duplex communication session is accepted at decision step 180, the full-duplex communication channel is arranged between the originating communication device 10 and target communication device 12, step 184. Then a determination is made as to whether or not organized full-duplex communication channel is successfully, Step 186 . When determining that no successful organized channel full-duplex communication, at step 186 the decision, the communication failure is output to the originating device 10, step 182. Otherwise, if the full duplex communication is determined as successful in step 186 organized decision, the service organized full duplex communication is transmitted to the originating wireless communication device 10 and target communication device 12, step 188. For example, handoff full-duplex communication in 188 may mean that VoIP-packet exchange is performed between the network address of the communication without control by the group communication server 134, so that full-duplex communication session establishment is completed, step 190. For example, if the full-duplex session is a VoIP-session, the exchange of media during the VoIP session can-be processed by other network entity, at least in one embodiment.

Although described in Figures 5-7 that the full-duplex communication session is established as an initial half-duplex session, which then goes into full duplex mode, other embodiments are directed to transitions from full-duplex sessions to half-duplex sessions and / or from half-duplex sessions to full-duplex sessions.

8 is a flowchart of processing a communication session that transitions between modes and half-duplex communication, full-duplex communication in accordance with an embodiment of the invention. With regard to Figure 8, the user determines the call sender 200 initiates a communication session, step 800, the call sender 200 determines that the call is initially established as a full-duplex session (e.g., if the default mode for calls from a sender 200 is a full-duplex mode) step 803, and the sender then sends the call setup message (full duplex) call to initiate a full duplex call, the regional dispatcher 202 (e.g., which may be a server 74 or the group communication 134), step 806. In the example setup message (full duplex) call Stage 806 is configured differently from the traditional call setup messages to establish a traditional full-duplex session (ie, full duplex session, which begins and ends as a full-duplex and half-duplex is never). For example, the setup message (full duplex) call at step 806 may include another setting operation code in the header part to indicate the regional dispatcher 202 to establish a full-duplex session as a half- duplex session at least during the initial part of the session. The regional dispatcher 202 acknowledges receipt of the call setup message from step 806 via-ACK messages (reception), step 809. In the example, the initiation of the full-duplex session can be performed at the call originator 200 (e.g., which may correspond to the originating wireless communication device 10) by pressing not-PTT-buttons, such as a button "SEND", which is the prevalent mobile phone, resulting in transmission specially configured message setting (full-duplex) call. After receiving tips on the establishment of full duplex call at 806 202 Regional Manager also is the target object (s) to call and sends a notification message (full duplex) to notify the target 206 call that a full duplex call requested by the sender 200 call. Similarly, the establishment of post (full duplex) call notification message (full duplex) can be specifically configured to specify a target object 206 call that notified session should begin as early as half-duplex mode with the intention of subsequent transition to full duplex mode.

In this embodiment, it is assumed that the sender 200 and call target 206 comprise call customers PTT / full-duplex communication for selectively switching their session between half-duplex and full duplex mode. Specifically, the example of Figure 8 illustrates a duplex mode switching operations on the basis of the requesting messages and the request message may be adapted to request transfer of a half-duplex mode in a full duplex mode (for example, "request message (full duplex)") or full-duplex mode in half-duplex mode (for example, the "request message (half duplex)").

Although the example of Figure 8 is illustrated and described such that transitions between half-duplex and full-duplex mode triggered by an explicit message (e.g., request message) from one of the call participants, other embodiments need not rely on explicit requests for a duplex mode shift initiating changing duplex mode, but instead may be initiated by the server. For example, trigger a change duplex can be "competitive", so that if the user tries to repeatedly and unsuccessfully grab permission to transmit during a half-duplex portion of the session at the time when the permission to transmit has another participant, a transition to full-duplex can be initiated without interfering User. In another alternative example, trigger a change duplex mode may be based on the "utilization factor" so that, as full-duplex calls tend to be more resource-intensive (e.g., include the bandwidth required to transmit background noise), the transition from full-duplex mode to half-duplex can be based on voice activity and other metrics (e.g., if only one participant in full-duplex mode during said given period of time, the call may transition to half-duplex to conserve resources, etc.). When the server-initiated change duplex server or may issue a recommendation to one or more participants in the session (for example, sender, etc.) that the transition to the half-duplex mode is advantageous (for example, the reduction of costs in a row), or, alternatively, the automatic transfer can be performed by means of the control session server (e.g., media control module 204 and / or regional dispatcher 204).

Returning to Figure 8, after receiving the notification message (full duplex), which notifies the session in step 812, assume that the call target 206 accepts the call, step 815. The regional dispatcher 202 receives the indication regarding target 206 receiving a call, and forwards the message status (success) to the sender call 200 to indicate that the call can begin, step 818. The sender 200 call indicates that the call was successfully installed to its user, step 821 (e.g., by playing a melody, display a visual message, etc. .d.), and the sender 200 call answers the call by sending an ACK-message (receive) back to the regional dispatcher 202, step 824.

Then, the regional dispatcher 202 sends instructions to the module 204, the media control (e.g., a server that works with the regional dispatcher 202 for maintenance exchange media for a particular communication session) to serve the actual exchange of media between the sender 200 call and the target object 206 call in the session communications, step 827. The media control module 204 sends a contact message (mcu_info) call sender 200, step 830, and the target object 206 call, step 833, which includes information on how each call participant can send information to the control module 204 multimedia. Sender 200 call and a target 206 call contacts send ACK-messages (reception) in response to the contact posts of the stages 830 and 833 at points 836 and 839 respectively. Then, the media control module 204 regulates the exchange of media between the call participants during a full-duplex portion of the session, step 842. In other words, the media exchanged between the call sender 200 and the target 206, the call may proceed in one direction or in both directions.

In the embodiment of Figure 8 media control module 204 uses a specially configured service messages (for example, ATN-communication (full duplex) and (half duplex)), to notify the wireless communication device when a session is requested to move to full-duplex mode or half duplex, and customers PTT / full-duplex communication devices 200 and 206 use ATX-communication (reception) to receive shift duplex. Although not shown in Figure 8, it is also possible that one or more participants in the session may reject the change duplex mode, which should lead to a failure to perform by the server change the duplex mode, or to the exclusion of session participants who rejected change the duplex mode, from the session after the duplex mode change effected. The media control module 204 may also use message-FYI (updated), to notify the client PTT / full-duplex communication, that requests a change of the duplex mode, that the call goes to the requested duplex.

Accordingly, the sender call 200 determines whether or not to request the translation of the conversation in full duplex mode half-duplex mode, and call the sender 200 is an object that has a resolution on the transfer, after the change of the duplex mode, step 845. As discussed above, the translation of the full-duplex mode in half-duplex mode may be required in order to conserve system resources (e.g., if basically only said call sender 200) to reduce the cost of the session to the call sender 200, etc. Although this determination at step 845 is shown as completed call sender 200, it should be appreciated that the call target 206 may also be able to request such a transfer of at least one embodiment, although this aspect is omitted for convenience 8 explanations. In other words, other embodiments may allow neotpravitelyam request and carry out potentially change the duplex mode.

If the sender call 200 determines not to request translation of a session of the full-duplex mode in half-duplex mode in step 845, the process returns to 842 and full duplex session continues. Otherwise, if the sender 200 call determines the query translation session of the full-duplex mode in half-duplex mode in step 845, the sender 200 call sends a request message (half duplex) module 204 media control, step 848, and the control of multimedia sends ATN-Post (half duplex), the target object 206 call, step 851. ATN-Post (half duplex) serves as a request for the target object 206 call to accept the transfer of the full-duplex mode in half-duplex mode or at least inform the target object 206 call that carried out the change of the duplex mode. Accordingly, assume the target device 206 responds to the ATN-message (half duplex mode) by sending an ATX-communication (reception), Step 854, and the module 204 media control sends a FYI-message (updated) to the sender 200 the call to indicate that the session Communication can now move to half-duplex mode, step 857. The sender 200 call thus sends a request for permission to transmit module 204 media control, step 860, and the media control unit 204 sends a message of permission to transfer the call back to the sender 200, the stage 863 . The sender 200 then sends the call to multimedia at its dedicated channel in the half-duplex media control module 204, step 866, which then forwards the media to the target object 206 call, step 869.

During this part of the half-duplex communication session target 206 call decides whether or not to transfer the call back to full-duplex mode (for example, so that the user of the target object 206 call can talk), step 872. If the target call 206 determines not to request translation session from a half-duplex mode in a full duplex mode in step 872, the process returns to step 869, and the half-duplex session continues. Otherwise, if the target object 206 call determines to request transfer the communication session from the half-duplex mode in a full duplex mode in step 872, the target 206 call sends a request message (full duplex) module 204 controls the media, step 875, and the control of multimedia sends ATN -message (full duplex) call to the sender 200, step 878. ATN-communication (full duplex) acts as a request to send 200 calls to accept the transfer of half-duplex mode, full duplex mode, or at least to inform the sender of the 200 call that the change in duplex mode is carried out. Accordingly, let us assume that the sender 200 call responds to the ATN-communication (full duplex) by sending ATX-messages (reception), step 881, and section 204 media control sends FYI-Post (updated) to the sender 200 call to indicate that the session Communication can now move on to full-duplex mode, step 884. After that, the media can be shared between the sender 200 call and the target 206 call through a full-duplex protocol, step 887.

In the embodiment of Figure 8 queries for full duplex and half duplex transmitted specially signaled users of devices (e.g., after the ATN-message received in step 851 and / or 878, so that the devices other than the device requesting transfer , a notification is sent or given a message for transfer to the user), for example, through a series of warnings, for example, three sound momentum, with PTT-communications, which should indicate to the user that another session participant wants to change the characteristic of the duplex session (eg sender PTT / full-duplex communication 200 wants to participate in the full-duplex communication with the target 206 PTT / full-duplex call, etc.). For example, the sound warning can be the classic ring tones, voice, tones call or other alerts that are sent with the PTT-communications to notify the user that the other participants in the session request a transition to full duplex. Receiving shift duplex may then be done by pressing the not-PTT-button (such as a button "SEND") or menu selection (e.g., so the user can accurately know the nature of the current duplex session). Alternatively, the user of these devices can receive a warning about changing the duplex mode, but it does not necessarily need to be given the opportunity to reject the change duplex mode, so that the change duplex forced instructed users. In any case, even if the session participants is instructed to change the duplex mode, the session participants, in general, always aware of enabled and broadcasts the other side of the microphone and other communication interfaces or not (for example, though, at least In one embodiment, the administering party session, such as a parent, may be permitted otlezhivat another session participant, such as a child, by instructing the transfer in full-duplex mode without notifying the child and thus its audio can be heard).

Although Figure 8 shows, in some cases, participants requesting the transfer of the session in half duplex mode, full duplex mode to send information to another participant (s) of the session, should take into account that the participants in the session may alternatively request a permit for the half-duplex session As it is known in the art. In this case, if a request for permission to transmit repeatedly rejected for this session participants, session participants can then request a change duplex mode.

9 is another flowchart of processing a session that passes between half duplex and full-duplex communication in accordance with an embodiment of the invention. 9 is similar in some respect to Figure 8, though a sender 200 PTT / full-duplex call also allows sending unidirectional media (e.g., voice, data, etc.) while transitioning between half-duplex and full-duplex communication. 9 is a general explanation is omitted for the sake of brevity, although aspects of Figure 9 which differs from Figure 8, are explained more in detail.

With regard to Figure 9, when the notification message (full duplex) is sent to the call target object 206 at step 912 (e.g., similar to 812 of Figure 8), the user of the target object 206 call are prompted to take the full-duplex communication session, step 915, to permit the preparation of its media while media from the call sender 200 (e.g., initiator, transition to full duplex mode) can be played both a half-duplex manner, steps 945 and 948. Thus, the half-duplex media is still played, steps 945 and 948 in While the transfer is the media control module 204. Once the full-duplex session is established in step 951, it should be appreciated that a unidirectional path from stages 945 and 948 can transition into the bi-directional or full-duplex path. Similarly, during the subsequent transfer to full-duplex mode (steps 981-999), after the intermediate transfer in half-duplex mode (steps 954-978), can be installed or half duplex bearer of the target object 206 call to the sender call 200, steps 993 and 995. In this case, a half-duplex channel is established in each direction before the full-duplex channel is established. It will be appreciated that the establishment of unidirectional or half-duplex channel in step 945 and 948 from the sender 200 to the target 206 to establish the initial full-duplex session at step 951 is similar to Figures 5-7 in the sense that a temporary half-duplex session whereby the sender can speak to the target, set at the same time waiting for the start of full-duplex session.

10 is a flowchart of a method for one embodiment of the transfer current half-duplex session between an originating device 10 and destination device 12 to the full-duplex session in response to the request for changing duplex, taken from one of the session participants. Accordingly, in the regulation of half-duplex session between devices 10 and 12 (for example, using the originating device 12 as an object with a resolution of the transmission), the server 134 multicast connection receives a request to establish a full-duplex connection between the originating device 10 and destination device connection 12, step 210, and then half-duplex media (e.g., any media that is buffered by the media control module 204 in the GCS 134 from the session participant that initiates the transfer in full duplex) is delivered to the target communication device 12, step 212. It is to be acknowledge that the service 212 corresponds to sending media to the target device 12 and / or any other devices that participate in half-duplex session along with devices 10 and 12. Full duplex communication between the devices 10 and 12 are further installed, step 216. In this embodiment, the establishment of full-duplex communication channel is automatic and the target device 12 needs to determine eventually participate or not full-duplex communication, as shown in Figure 12.

As for 10, 134 group communication server determines whether or not the full-duplex channel for full-duplex communication session, step 216. If the server 134 determines the group communication that full duplex channel for full-duplex communication session is not set in step 216, an alarm indicating inability to perform the transfer in full-duplex mode, and she sent a conversation participant who requests a transfer to full-duplex mode (for example, a conversation participant, requesting transfer in full-duplex mode, a message is sent that indicates that the transfer should not be carried out), and the process Translation in the full duplex mode is terminated, step 218. For example, a full duplex transfer may fail if the target device 12 ultimately rejects the full-duplex request and / or if there is a technical failure in establishing the full-duplex communication. However, failure to transfer the full duplex mode is not necessarily completes the initial half-duplex session.

Otherwise, if the server 134, group communication determines that full-duplex channel for the session full-duplex communication is set, at step 216, the service session transmitted corresponding device (such as the controller 78 active calls) and the communication session after supports both full-duplex session, at least between devices 10 and 12, step 220, and the process of Figure 10 ends, step 222. Alternatively, although not shown in Figure 10, it is also possible that the group communication server 134 regulates the full-duplex session (e.g. , VoIP-session), when there is no transfer of responsibilities for the implementation of the regulation in step 220, 134 and group communication server continues to exercise control session as a full-duplex mode.

11 is a flowchart of a method for one embodiment of the translation of the current full-duplex session between an originating device 10 and destination device 12 to the half-duplex session in response to the request for changing the duplex mode from one of the session participants in accordance with an embodiment of the invention. With regard to 11, the group communication server 134 receives a request to transfer a session to full-duplex communication session participant to the full-duplex communication session is a half-duplex communication session with the requesting party as the object has permission to transmit, 230. The group communication server 134 determines available or no target device (or devices) for the half-duplex communication (e.g., in this case, the target device can correspond to either the target object 206 calls the initial full-duplex session, a sender 200 calls the initial full-duplex session, depending on which device requests a transfer to a half-duplex ) step 232. If the target call is not available for half-duplex session, an alarm on the device that requests the transfer in half-duplex mode, and the process ends, step 234, and a full duplex session can continue. The determination of how many target devices should be available to continue the half-duplex session may be one or more and can comprise at least another device (i.e. a device that does not request transfer to a half-duplex mode in step 230), who had previously participated in a full-duplex communication session. It should be appreciated that although unsolicited device with a high probability is available for transfer to the half-duplex mode may be reasons why the half-duplex session can not be maintained through unsolicited device (eg, technical failure, the scheme of prioritization in which another session is higher priority in unsolicited device, and / or other restrictions on the requesting device that prevent further PTT-communications, for instance prepaid functionality of PTT-communications, for which payment is not paid, etc.).

Otherwise, if the target device is available at block 232, the group communication server 134 establishes a half-duplex communication, step 236. Half-duplex media (e.g., voice data) from the requesting device is received and buffered at the group communication server 134, step 238, and then initial full-duplex communication session is requested by the group communication server 74 to be terminated by controlling the full-duplex communication session by an appropriate device (such as active call controller 78), step 240. Alternatively, if the group communication server 134 itself operates full-duplex communication session, it should be note that request is sent 240, and the session is full-duplex communication can simply rejected by the server 134 group communication.

After completing a full-duplex portion of the session in step 240 buffered half-duplex media from step 238 is delivered to the target device (s), step 242.

12 is a flowchart of a method for one embodiment of a process performed by a session participant involved in the half-duplex communication session when another session participant half-duplex communication session requests a transfer of a half-duplex mode in a full duplex mode in accordance with an embodiment of the invention. With regard to 12, the session participant (e.g., a target communication device such as wireless device 12, the sender of the session, etc., the session participant receiving the request in step 250 may correspond to either the current speaker in the half-duplex session, any object that does not have permission to transmit in a half-duplex session) receives a request for full-duplex communication session during the half-duplex communication session, step 250. In the example, "request" in step 250 may be configured to forcibly instruct party session to receive a transfer full-duplex mode, even if the session participant corresponds to the current user has permission to transfer to half-duplex session. In this case, a full-duplex channel is established at step 252 before the user of the target device consents to participate in the full- duplex session. Alternatively, in another example, although not shown in Figure 12, the user of the target device can warn of the request for transfer in full-duplex mode (for example, by sending a special call, etc.), and may be given the opportunity to accept or reject inquiry. In a further example, session participants having a low priority (e.g., lower than the participant that requests a change duplexing) may forcibly be instructed to transfer in full-duplex, whereas session participants having a high priority (e.g., higher than the participant, that requests a change of duplex mode) may be able to elect or reject the admission session. With the proviso that any party is instructed to perform session forcibly shift duplex mode, or the user deliberately chooses to perform shift duplex, full-duplex channel is established, step 252. In the example, if the target device does not have a traffic channel (TCH) during the half-duplex session, setting the full-duplex channel at step 252 may comprise receiving by the target device TCH from the access network. The target device (e.g., wireless device 12) then suppresses a communications interface, step 254, such as a microphone 115 and / or camera 113, so that the user of the device at this point should not send data for full-duplex channel (e.g., in order to user privacy), step 254, and then prompts the user to take full-duplex communication, step 256, and it can be a simple audio warning, visual warning, etc. Step 254 suppression may not be necessary if the microphone is already muted or 115 communication interface is disabled in other ways when full duplex is organized with the device.

With regard to 12, the target device determines whether or not it takes the user a full-duplex communication session, step 258. If the target device determines that the user does not accept the full-duplex communication session, a full-duplex communication session is terminated and the establishment of full duplex channel in step 252 is interrupted, step 260. Otherwise, if the target device determines that its user accepts the full-duplex communication session in step 258, then the communication interface is not inhibited, and the user can participate in the established full-duplex communication session, step 260. In the example, the target device can reject full duplex request by simple inaction in acceptance, for example, if the user does not take over 5 seconds, or can press a button, such as the PTT-button 112, to expressly maintain the half-duplex communication session. Accordingly, in the process of Figure 12, half-duplex session need not be interrupted, at least as long as the user is not the target device is able to determine whether to accept a full-duplex session.

In another embodiment, the target apparatus 12 practiced with selective control of a forced activation of the full duplex communication, the method may include selectively enabling the target device 12 communication forced establishing full duplex communication, and thereby selectively enabling the activation of the microphone 115 (e.g., in contrast of 12, which indicates that the microphone 115 is "plugged" up until the target user optionally accepts not full-duplex session after the full-duplex session is established. In such embodiment, a user of the initiating wireless communication device 10 must be able to listen to the audio output to the microphone 115 in the target device 12 communication. It should be appreciated that the privacy of the target user may be disturbed in that case, but it may be desirable under certain conditions. For example, a parent having the originating mobile telephone can force instruct the microphone mobile phone child for full-duplex communication, and the parent can talk and listen to the audio in the child's phone.

Additionally, although the above-described embodiments of the invention include references to the overhead messages which are dependent on the specific implementations and / or protocols (e.g., request, ATN, call establishment, notification, etc.), it should be appreciated that these signals may be modified appropriately in embodiments directed to other implementations and / or protocols. In other words, the call establishment message may correspond to any type of communication with the call request in other embodiments the notification message may correspond to any type of messages that notify the session, in other embodiments, etc.

Those skilled in the art will acknowledge that information and signals may be represented using any of a variety of technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Additionally, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein, embodiments may be implemented as electronic hardware, computer software, or combinations thereof . To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of functionality. Functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein, embodiments may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array ( FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the described functions herein. 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, for example 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.

The methods, sequences and / or algorithms described in connection with the disclosed embodiments herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination thereof. A software module may reside in memory such as RAM, flash memory, memory-type ROM, memory such as EPROM, the memory type EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In an alternative embodiment, 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). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary embodiments, 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. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other storage device on the optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used for to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a Web site, 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, then 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 (disk) and a disk (disc) as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-Ray, wherein the wheels (disk ) usually reproduce data magnetically, while discs (disc) usually reproduce data optically with lasers. Combinations of the above should also be included in the scope of computer readable media.

While the above description shows illustrative embodiments, it should be noted that various changes and modifications may be made therein without departing from the scope of the invention as defined by the appended claims. Functions steps and / or actions in the claims to a method according to embodiments of the invention described herein need not be performed in any particular order. Furthermore, although elements of the invention may be described or listed in the claims in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.