MXPA06008826A - System and method for queueing and moderating group talk - Google Patents

Abstract

Systems and methods for performing queued and moderated talk groups in a system featuring network provided half duplex communications talk group sessions. For queuing, rather than dropping a talk request from a user which is listening, the request is forwarded to the network and maintained in a list which is the used to grant access to the talk channel. For moderated talk groups, a wireless device is designated to be a moderator network device. The requests for he talk channel are then forwarded to the moderator network device. The moderator network device is equipped with functionality allowing a user of the device to select the order in which devices are granted the talk channel. In other implementations, meta-groups are provided, and rules of order for talk group sessions are implemented.

Description

SYSTEM AND METHOD FOR PLACING AND MODERING GROUP CONVERSATION DESCRIPTION OF THE INVENTION The present application concerns wireless communication systems and more particularly, call groups in wireless communication systems that provide semi-duplicated voice communication services.

BACKGROUND OF THE INVENTION The available communication systems provide an operation similar to walkie-talkie or semi-duplicate voice-like operation that can take the pttTM mode (push to talk ™) over a communication service, PTT ™ over cellular services (PoC) (part of the OMA standard) or otherwise. As referred to herein, walkie-talkie operation or semi-duplicate voice-like operation are generally considered to mean any voice communication operation released by a network or networks that is capable of transmitting voice communication from time to time. of a call or a transmission device of departure to where it is heard, or a device for receiving games, but the voice communication of the device for receiving games is not transmitted simultaneously to the game communication device, while the game communication device transmits the voice to the game receiving device. It is noted that these devices generally do not exclude other means of data communication, such as fully wireless Instant Messaging (chat), which is in fact defined as part of the OMA spectrum that is allowed during a PoC session. During an active PTT ™ session or call session dispatch, only one user device (the "talk" device) participates in the session that can be designated as the transmitter or device to talk at any time. A user device sends the performance of the transmission device by requiring the transmission / call channel of the network and by sending the transmission / call channel of the network. While a device to talk is taken by the transmission channel (during the call period), the other devices (devices on hold) in the active call session dispatch are in standby mode and the voice can not be transmitted until the transmission device requests the network to terminate the call period and release the transmission / call channel. The times when the transmit / call channel is not busy are idle times. In conventional PTT ™ implementations, the user interface of for example, a wireless device, includes a PTT ™ button to allow the user to control the sending of 'requirements to acquire and release the transmission / call channel, these requirements are sent over a logical control channel to the network. An example of a system that provides PTT ™ functionality as part of its walkie-talkie services is Motorola's iDEN ™ system. Other exemplary systems that can provide services such as PTT ™ are CDMA lxRTT, UMTS, GSM / GPRS, TDMA and the 802.11 family of standards. The push to talk ™ service can be provided as a semi-duplicate service over existing network systems that are also provided for full duplicate communication, or can be provided as a service in network systems that provide only semi-duplicate communication.

BRIEF DESCRIPTION OF THE INVENTION According to a broad aspect, the invention provides a call order controller for use in a network adapted to release communications with similar walkie-talkie skills within a group of call devices such as the group, a device simple is given with aptitudes to be transmitted while other devices have the aptitude to receive, the call order controller is adapted to carry out the control of the order of calls by: the reception of requirements through the network with aptitudes to transmit and keep a record of the requirements that are pending. In some modalities, the call order controller that is part of and is in combination with the network is adapted to carry out the control of the call order of each of the plurality of call groups. In some modalities, the walkie-talkie communications are released using wireless communication channels to the devices, the devices can be wireless devices. In some modalities, the registry of pending requirements includes a list of requirements that are pending and arranged in an order in which they are received and where the requirements with capacity to transmit are conferred from the oldest to the newest. In some embodiments, the call order controller is adapted to detect or receive an indication that the transmission capability can occur and have the ability to transmit responses that are given by transmitting a spoken message ready to the next device to send the transmission capability . In some embodiments, the call order controller is further adapted to receive the requirements of a device that requires that the device is not considerably delayed to wait for the transmission capability. In some embodiments, the messages are transmitted associated with the call group, the messages comprise at least one of: release of the call message from the device to the network; ready call message from the network to the device; interrupt the message from the network to the device; order of silence from the network towards the wireless device. In some embodiments, the call order controller is further adapted to post the number of requirements received from each device and guarantee a prior priority of transmission privilege based on the number of requirements received in each device. In some embodiments, the call order controller in combination with the plurality of wireless device groups. In some embodiments, the call order controller is adapted to the group of devices and designed to be a regulatory device for the group. In some embodiments, the call order controller is part of and is in combination with one of the devices in the device group. According to another broad aspect, the application provides a network adapted to release communications with walkie-talkie-like abilities within call groups of devices such as within each group, a single device is given capable of transmitting while the other devices have capacity. of receiving, in combination with a controller of the order of calls as summarized above for each group of calls, the network is adapted within each group to: maintain a designation of the particular device which is the regulatory device of the group; receive requirements with transmission capacity and send the requirements to the regulatory device; receiving from the regulating device the capacity to transmit and allow the sending in at least one respective sending device. In some embodiments, the call order controller is further adapted to: maintain the information privilege of each group of call devices; receive control of the call message group of the wireless devices according to the information privilege. In some embodiments, the information privilege comprises an indication in which at least one of the following privileges is in accordance with that stipulated in the wireless device: controller capacity; ability to regulate a meta-group; private messages within the group; Broadcasting capacity; access to the requirements of the call channel; unique access to the waiting list. In some embodiments, the call order controller in combination with the device groups, where the call order controller of each group of devices is part of one of the devices in the group. In some embodiments, the regulating device is adapted to receive by means of the network requirements of other devices capable of being transmitted; the regulating device has a user interface to receive a user selection from a device where a requirement with aptitudes to be transmitted has been received upon being selected and sent with aptitudes to be transmitted; response to user selection by the regulatory device adapted to transmit a sent message capable of being transmitted to the device through the network. * * In some modes, the call order controller is part of and in combination with the network, the network is adapted to: maintain a series of order rules for the call group; allow interaction between the group of calls according to the rules of order. In some modalities, the rules of order include: rights to make movements; movement priority order; rules regarding movements. In some embodiments, the call order controller as described above is implemented using one of the CDMA-based communications, communications based on 802.11, iDEN, GPRS, Bluetooth, ÜMTS, PoC (press to talk on cell phone). In some modalities, the messages are transmitted using DTMF signals. In some modalities, the walkie-talkie communications are released using wireless communication channels to the devices, the devices are wireless devices. According to another broad aspect, the application provides a method comprising sequentially: establishing a network that releases walkie-talkie communication sessions among a plurality of wireless devices; send with aptitudes to be transmitted towards one of the wireless devices and a privileged wait towards the remaining wireless devices; receive requirements with aptitudes to be transmitted from wireless devices that have the privilege of waiting; send with the ability to transmit in response to the requirements of the ability to transmit.

In some modalities, the sending with aptitudes to be transmitted in response to the requirements with transferability is done in the order in which the requirements are received. In some modalities, the sending with aptitudes to be transmitted in response to the requirements with capacity to transmit is done under the control of a regulator. In some modalities, the sending with aptitudes to be transmitted in response to the requirements with aptitudes to be transmitted is done according to a definite series of rules of order. In some embodiments, a compatible computer medium is provided with a processor that executes the instructions stored therein to implement a method as described above. According to another broad aspect, the application provides a PoC network adapted to provide a controlled call control through: the regulation of the background requirements that are triggered from the network to indicate to a wireless regulatory device that a request has been made by a particular user; and regulation of background responses that are actions of the wireless regulatory device to require the network to send the wireless user device through a command.

BRIEF DESCRIPTION OF THE FIGURES Preferred embodiments of the application will be described with reference to the accompanying figures wherein: Figure 1 is a schematic diagram of an exemplary implementation of a wireless device provided by a modality of the request; Figures 2-4 are block diagrams illustrating an example of a standby transmission channel that requires a message in an active semi-duplicate session according to a mode of the request; Figure 5 is a block diagram illustrating an example of the prioritized call waiting order according to a modality of the request; Figures 6 and 7 are block diagrams illustrating an example of the call order control switch according to one embodiment of the request; Figure 8 is a block diagram illustrating an example of the control of the control of the order of calls according to a modality of the request; Figures 9A, 9B and 9C are a signal flow diagram of an implementation example of the call group regulator connection in a PoC implementation; Figure 10 is a flow map illustrating an example of a method of a call order control regulator with rules according to a mode of the request; and Figure 11 is a flow map illustrating an example of a movement processing method according to a modality of the request.

DETAILED DESCRIPTION OF THE PREFERRED MODALITIES In the following particular examples, similar walkie-talkie capacity is assumed to be PTT skills. More generally, the modalities of the application can be employed with any system that provides a network that releases the walkie-talkie skills that are not limited to the PTT skills of the examples. Users in the final reception of a call group session in known systems have no way of communicating to the user of the transmission device, since the transmission / call channel is occupied by the transmission device until it is released. With the. conventional devices, when a user presses the "button to talk" while the device is in standby mode, a request is made to the channel, the device simply doses the requirement without sending it to the network. In the request, a message is sent to the network whenever the device is in standby mode.The message sent can be in the same way as if it was generated when activating the button to talk during the availability of the channel or it can be a In this case, the message will be referred to here as a request message 'in the transmission channel or TCRM.This is transmitted over a channel of the device to the network.This can be transmitted over a separate control channel, or on the traffic channel normally used for voice communications In a modality implemented in the Motorola iDEN ™ system, a preferred logical control channel is used to send a TCRM 36 which is the data link layer sometimes referred to as the layer 2. The TCRM can be sent over the control channel L2, which can be sent over a dedicated control channel (DCCH) or an associated control channel (ACCH). In the event where the TCRM is sent over a specific channel device, it is not necessary to include an identification device in the TCRM as in the network that can be determined with the sending device in a TCRM of the channel where the message is received. Note that iDEN is an example of a network that releases similar walkie-talkie skills not based on SIP. In SIP-based systems, preferably SIP over IP messages are used for the TCRM. Referring to Figure 1, an example implementation of a wireless device 300-with PTT capabilities is provided by a mode of the request that will not be described. It is clearly understood that this is only an example of a wireless device that can be used in request modalities that allow waiting and / or regulated control of the group of calls that require processing. It is also clearly understood that many other strictures will generally be included in a recent wireless device. These structures are not shown for the purpose of clarity. In the embodiment described in Figure 1, the wireless device 300 has a call request interface in the form of a key 312 and has a display 340. Other modes may include any other suitable local input / output elements. The call request interface is coupled to a processing element 320. The processing element 320 is coupled to a message transmission element 332. The message transmission element 332 may take part in the resources with a receiving element of the message. messages 334. The message reception element 334 is coupled to the processing element 320. The elements 332, 334 preferably form part of the conventional transmission and reception capabilities in the wireless device. The processing element 320 represents any suitable processing capability implemented within the wireless device to handle the generation of the TCRMs and to handle the reception of other messages including those described below as "ready to speak" (CTTM) messages. This element may be implemented as one or a combination of physical elements, programming elements, permanent elements In a preferred embodiment, the processing element 320 is included as an addition to the skills of the program in either a provided or existing wireless device. In operation, the wireless device 300 described in Figure 1 is capable of operating in a network providing semi-duplicated walkie-talkie communication skills in the THD (semi-duplicate transmission) mode and in the RHD (semi-reception) mode. duplicate.) While in RHD mode the wireless device is capable of receiving inputs to Starting from the 312 talk request interface to start sending a TCRM to the network that is added to a list that is kept by the network as detailed below. Since the request enters, the processing element 300 and the sending through the message transmission element 332 on a suitable transmission resource to the network. In some embodiments, a fitness that is appreciated is provided in such a way that the wireless device can be noticed as the TCRM (or any message) that is received by the network.

While in RHD mode, the wireless device is capable of receiving a CTTM from the network over the message receiving element 334. The CTTM enters the processing element 320, where it is processed to extend what is necessary to recognize that it is a CTTM . A detectable indication of the user is then generated in the wireless device to indicate reception of the CTTM, for example in the form of a listenable tone, a visible signal or any other suitable indication. In some embodiments, the wireless device does not provide current information to the speech channel after receiving the CTTM unless the talk button is pressed. Referring to Figures 2 to 4, an example of a message waiting on the transmission channel according to one embodiment of the request will be described in the context of a walkie-talkie call session from a group of wireless devices in a group of semi-duplicate calls. »As shown, a call group consists of a group of wireless devices 30, 32, 34, 36 that have respective device identifiers such as wireless device_l, wireless device_2, wireless device_3 and wireless device_4. each wireless device may for example be as described with reference to Figure 1, but is not limited to this and is shown participating in an active session with a transmission channel taken by the wireless device 36 as indicated by the "" " call channel "37. At the particular time instant represented in Figure 2, the wireless device 36 is in THD mode since this is the transmission / calling mode and taken over the transmission channel.The remaining wireless devices 0, 32, 34 are in RHD mode or in standby mode and receive call groups on the "waiting channels" 31, 33, 35, respectively, It should be understood that the modalities of the request are more generally applicable in a group of call session involving an arbitrary number of wireless devices, however, it should be understood that these are temporary designations for the particular mode of operation of the device at any time During the active session, users of RHD devices (30, 32, 34) are referred to as on hold, while the user of the THD device 36 is referred to as the one speaking. Each device in the specific example shown in Figure 1 is capable of functioning as either a THD device and an RHD device, depending on which device is in transmit / call mode and which devices are in standby mode during any active session in particular. Each device has a "talk" button or other suitable user interface referred to herein as the "interface required to speak" to access the requirement to transmit over the semi-duplicate channel. This interface for requesting speech may be the same as, or in addition to the "talk" button for wireless devices with similar walkie-talkie capabilities. The establishment of the physical links between the user devices, the route of the data voice packets and the duplication of the data voice packets for each of the devices in the standby mode are specific to each implementation of a PTT. ™ or similar semi-duplicated voice communication system. These functions are represented abstractly by a network 25 which represents all the system components necessary to provide semi-duplicate communications to communicate the sending of voice data by the THD device 36 on the link 37 to all the RHD devices 30, 32 , 34 in links 31, 33, 35 and in general support the functions of an active session. The details of these links are not relevant here. During the active session, the THD device 36 takes the transmission / call channel until the release of the channel is required or the call is terminated. In addition, the call order controller 40 provided by a method of the request is shown. The call order controller in a mode is implemented as part of the network 25. The call order controller 40 is preferably implemented as an extension for the program that runs the existing processing capabilities provided by the network., but more generally, it can be any suitable combination of one or more 'of physical elements, programming elements, permanent elements. The call order controller receives the TCRMs and performs a standby operation as detailed below. In addition to receiving the TCRMs, the call order controller 40 generates "ready to talk" (CTTM) messages where each is transmitted to a particular wireless device to indicate the particular wireless device that follows when the opportunity to use the channel is presented. semi-duplicated transmission. Like the TCRM, the CTTM is transmitted over the network in any suitable channel to a wireless device and can come in any form, the only requirement is that the wireless device in standby mode be able to recognize the message where it comes from. In a PoC implementation, the PoC can, for example, host the call order controller, an example of a TCRM message is the specification "background requirement" and an example of a CTTM message is the specification of the message as "background sending". " The call order controller 40 receives the TCRMs and keeps the device idenified in sequence associated, from the oldest TCRM sequence to the newest known TCRM sequence. When the transmission channel is available ", for example by a previous user who operates the button to speak, the call order controller sends a CTTM to a wireless device whose identifier is in the list for a while. wireless devices in a FIFO buffer (first in, first out) this functionality is logged, once the wireless device has been given the call channel, the associated identifier is removed from the list that is maintained by the order controller 40. Alternatively, the identifier may be maintained in association with a state indicating that the particular device is in the transmission channel In the example of Figure 2, during an active session of a standby device 30 in the mode wait sends a message that requires the transmission channel- (TCRM 41 in response to the external input of the standby mode via the interface of call requirement. The TCRM 41 is received by the network 25 and sent to the call order controller 40, through which the simplicity of the Figure only shows the message that is received directly by the call order controller 40. The order controller of call 40 maintains a list 46 of user device identifiers that have transmitted TCRM messages. Thus, upon receipt of the TCRM 41 from the wireless device 30, the identifier of the wireless device that is the wireless device_l is added to the list 46. In the illustrated example, some time later, the wireless device 34 generates a TCRM 42 that it is further sent to the call order controller 40 and added to the list 46. Time later, the wireless device 32 generates a TCRM 44 which is also routed to the call order controller 40 and is added to the list 46. In the illustrated example, the list 46 is shown to contain inputs of the wireless device_l, wireless device_3, and wireless device_2 for the three wireless devices 30, 34, 32 in the sequence where the TCRMs 41, 42, 44 are received. it is further known by the mobile device 36 that is currently taken by the channel to speak. List 46 is maintained on a progress basis by adding new revenue for the wireless devices that have sent TCRM. The income of each wireless device is any input that can only be associated with the wireless device that transmits the TCRM. This can be, for example, an identifier of the wireless device. In the illustrated example, each entry in the list 46 also has an associated state. The status for the wireless device_4 36 is "talk"; the state for the wireless device_l is "first to speak", the state for the wireless device_3 34 is "second to speak"; the status for the wireless device_2 32 is "third to talk". The additional states are introduced later. In a simple implementation where only waiting is carried out, there is no need to maintain the information status as required by the sequence of information that is totally deductible from the list. The ordering state of Figure 2 is shown as an effective appearance at a later time in Figure 3. Now the wireless device that can use the call channel, the wireless device 36 in the example of Figure 2, has provided the channel and is in standby in the waiting channel 49. The call order controller 40 determines the next wireless device that has the opportunity to take the channel when querying the list 46. In the example illustrated, the wireless device_l, the identifier for the wireless device 30, is the one that remains in the list. The call order controller 40 transmits a CTTM 45. After receiving the CTTM by the wireless device 30, the wireless device 30 is free to communicate by sending the semi-duplicate channel 47 from the wireless device 30 to the network. In the event of sending CTTM in a specific device channel, the wireless device 30 may be the only one to receive the message, so there is no need to include the device identifier in the CTTM. If a broadcasting channel is used to transmit the CTTM, there is a need to accompany it or include the identifier of the device. The ordering state of Figure 3 is shown to appear effectively a time later in Figure 4. Here, the wireless device 30 continues from the talk button (or other user interface to talk) to release the call channel, as indicated at 50. The call order controller 40 determines that the wireless device_3 by the wireless device 34 continues in the list 6 and sends a CTTM 52 in such a way that the wireless device sends this access to the call channel 51. In In another embodiment, a mechanism is provided to modify the order of the list of wireless devices that have an access requirement for the calling channel. In a first implementation of this structure, illustrated by the example in Figure 5, the call order controller 46 keeps a count of how many times each user has sent a TCRM. In the example, the count is maintained in column 60, which shows at a given instant in time, that the wireless device 30 has generated a requirement and is in fact currently taken over by the calling channel, the wireless device 32 has generated a requirement and the wireless device 34 has generated two requirements, the second requirement is indicated at 62. In general, the call order controller 40 checks the received TCRM counts and rearranges the list of the users that have transmitted the most TCRM that are previously prioritized for users who have transmitted few TCRM. In the illustrated example, this is shown by the reordering of the wireless device_2 and the wireless device_3 which is indicated at 63. In another example of implementation of this additional structure, shown in Figure 6, this is an additional message with aptitudes for the controller of the order of calls 40 to the wireless devices that allow to interrupt a wireless device that is currently taken by the call channel. In the example "illustrated in Figure 6, as a switch 80 is shown because it is transmitted from the call order controller 40 to the wireless device 30. In response to this, the wireless device 30 provides the call channel 47 when advancing the button to speak as indicated in 82. In a preferred mode, the wireless device 30 receives automatically, by the reception of the switch 80 and without any input / dialing of the button to speak of a user of the device, provided by the call channel, with an optional notification for cancellation. In another embodiment, the switch 80 serves as a support for the user of the wireless device that later receives the call channel. The interrupted wireless device may either be completely taken out of consideration to access the call channel, or it may be added to the list of wireless devices in line to access the call channel in which case the wireless device may for example be added to the end of the list or to the beginning of the list. In the embodiment exemplified in Figure 6, the wireless devices are further equipped to receive the switch 80 and to process this and generate either an indication to the user or simply disconnect it from the call channel, depending on a given implementation. The example of Figure 6 is shown some time after Figure 7. Now, the wireless device 32 is shown in the interrupted state that has sent a CTTM 72 and has access to the call channel 70.; the wireless device 30 is in the interrupted state and the wireless device 34 is at the bottom of the list 46. In this example, the wireless device 34 will remain interrupted until the wireless device 32 releases the call channel after the call channel returns to the wireless device 30. In some embodiments, a wireless device that is on the waiting list to access the call channel is also able to remove itself from the list. In one embodiment, this is achieved simply by reactivating the call request interface that sends an additional TCRM that is interpreted by the call order controller 40 as required to remove the wireless device from the list. In another embodiment, a different interface is provided on the wireless device that when activated generates a different message to be sent to the network that is interpreted by the call order controller as a requirement to remove the wireless device from the list. The call order controller can be implemented as part of the network, part of one of the devices in the groups or part of any other device. In other embodiments described further in detail, the adjustment skills are provided through a functional element controller. The functional element controller can be considered a specific example of a call order controller. Even in other embodiments described in detail below, the call order controller is responsible for enforcing a series of order rules. In the modalities described below, waiting for the TCRMs is carried out by the call order controller that is part of the network. In another embodiment, control over the call channel is removed away from the network for one or more wireless devices that have a functional element activated controller. Preferably, in this mode, all wireless devices are implemented with the functional element controller, but the capability is only activated in a wireless device or devices at a given time. This capability can, for example, be sent by the controller of the message controller based on the list of the group that the device is activating. The wireless devices have a functional active element regulator that will be referred to as a wireless device regulator. In this mode, a controller of the message controller is provided within the network or is attached to the network to control the flow of messages between the participants of the call group. Preferably, these messages include the previously entered TCRMs that are received by the controller of the message controller and sent to a wireless regulatory device and include the CTTM that is generated by a wireless regulatory device and transmitted to a wireless device that is sent to access the call channel. In an example of the regulated group, a list similar to list 46 of the previous modes is maintained by the regulating wireless device which is communicated by the controller of the message controller and the wireless regulating device has the ability to control the order in which the Wireless devices have required the call channel with access skills and in certain embodiments, the wireless controller also has control over a certain period of time in a given wireless device with access capabilities. I refer now to Figure 8, what is shown is an example of a network with regulatory skills. In this network, this is a controller of the message controller 100 which, as the call order controller of the previous modes, is preferred to be implemented as part of the network 25. For example, this can be included as part of a management function of the group list within the network or as a logical combination of the GLMS and the PoC server. The controller of the message controller 100 maintains an identifier for each group list of the wireless device that is responsible for regulating the group of calls between the list of the group, if the list of the group is regulated. This can be located as a static feature of the group that is configured during the installation of the list. Alternatively, the wireless device that is the controller can be configured in real time. In one mode, group lists are defined by using a network-based interface and the group generator provides the privilege of selecting a controller. In the illustrated example, the wireless devices 0, 32, 34, 36 each have a respective MFE (functional element regulator) 90, 92, 94, 96 which for a given device is active if the regulator is designated. The controller of the message controller 100 acts as a relay to send messages between the devices without a privilege regulator and the regulating device. For example, the generator TCRMs by the waiting lists of the wireless devices are sent by the controller of the message controller 100 to the controller of the group's wireless device. The wireless device's controller generates the CTTMs that indicate a particular wireless device to provide it with the call channel. Thus, a CTTM contains the identifier of the wireless device. The controller of the message controller 100 then sends this message to the particular wireless device, an example of a data structure that can be maintained by the controller of the message controller 100 is illustrated in Figure 8. The data structure has a column 102 for the identifiers of the group list; a column 104 for members of the group list of each group list is identified in column 102 and column 106 is for indicating the identifier of a regulatory wireless device if there is one. This structure is used to determine when and how to send a TCRM that is received. "- .. - • ..." The MFE of the wireless regulatory device receives the TCRMs from other wireless devices through the network 25 and maintains a list of identifiers of wireless devices that transmit the TCRMs. In this embodiment, the release of a call message is also sent to the controller of the message controller when a wireless device is released to the controller, for example in a touch or graphics screen. call channel This can be generated by the wireless device when the call channel is released or alternatively it can be generated autonomously by the controller of the detected message controller or when the channel is notified that it has been released. the MFE responds to the reception of message release by sending a CTTM to the device that is programmed or selected by to continue with the reception of the call channel. In another embodiment, once the call message is received, the MFE generates an indication on the wireless regulatory device to indicate to the user of the device to select the next wireless device to which the call channel is provided, in response to this, the selection of a CTTM is generated from the device. In another modality, a hierarchy of regulation is configured. With this modality, multiple subgroups of devices are regulated independently, for example, each with a respective regulator when using the same performance as indicated above for a simple moderate group. However, access to the call channel through a moderate or other subgroup is controlled by a high level of regulation or by waiting as described above. In this case, the high level of regulation can be carried out in a similar way to that indicated above for a simple regulated group, but instead of the wireless devices competing for the call channel, the regulated subgroups are those that compete for the channel. In another embodiment, a plurality of privileges are defined. Each wireless device is categorized to have privileges as required. Examples of privileges include but are not limited to: skills of the regulator - the device provides the active status of the regulator; meta-group regulator skills - several group regulators form a "meta group", without a meta-group regulator for a meta-group, conventional call-group structures are implemented for the meta-group; private messages within the subgroup - the device sends the right to send private messages within a group of calls; public messages - the device sends the right to send a broadcast message within a group of calls; call channel access requirement - the device allows the TCRMs to be transmitted and sent to the call channel under the control regulator; Standby access only - the device will not send to the call channel but can keep it on hold only. These privileges in some modalities are maintained through the regulation of the message controller, through an administration interface that can be based on the network, for example. The controller of the message controller then processes a message received from a member of the call group according to the privileges that the wireless device has.

DTMF mode In a mode, particularly suitable for, but not limited to, PoC applications, whether by standby or regulation, signaling between the various devices is achieved by using DTMF (dual tone multifrequency) signaling. The DTMF has 16 codes that include 12 of a typical key and four additional codes A, B, C and D that are generally capable of being generated but not used. The DTMF codes that are sent from the wireless devices to the network are filtered out of the network until they do not appear in the audio channel. Similarly, if any of the DTMF codes is sent to a wireless device, preferably the filters of the wireless device come out and process them appropriately. In one embodiment, DTMF tones are used to carry out signaling between wireless devices indicating one or more of: releasing the button to talk; a message ready to talk; interrupt a message; order of silence; ' In the modalities described here, the network participates in placing the required call and the waiting channels. For example, in standby modes, when the next user provides the transmission channel, the previous transmission channel is deactivated if it is not done and a new transmission channel is activated if necessary in addition to placing a new waiting channel for the wireless device previously activated. In some embodiments, a transmission and reception channel can be maintained on a forward basis between each wireless device and the network, but the system only allows transmission and reception in semi-duplicate mode as described herein to release similar functionality to walkie-talkie. Similarly, for regulator modes, when a shipment is received from the regulatory wireless device, the shipment is sent to the appropriate wireless device, but the network can also establish the transmission channel required by the wireless device if the channel is not available . Because existing walkie-talkie-like systems are well established and have the ability to increase call and standby channels around when additional details are required they are not described here. In a preferred embodiment, the request is implemented as a series of changes to a Poc specification as defined in the Specification Industry for PoC, October 6, 2003 incorporated herein by reference in its entirety. The Poc Specification Changes for Call Group Regulation: 1) Add "user classes" and in some implementations also "meta-groups" to the function management list for the GLMS group PoC-List Management defined in the document referred to above. 2) provide two new message background controls to be implemented in the PoC server, associated with new skills in the GLMS group administration list in the document referred to above. The existing capabilities of the PoC server background control are summarized as follows: background requirement: the action provides the ability of a participant in a call session to ask for a permission to call. Background release: the action taken by sending a user to release the call permission. Background Submission: an action by the network to inform of the participant requirement that the fund is inactive. Denial of fund: "an action of the network to inform that the requirement of the participant in the background requirement is denied." Fund intake: an action of the network to inform all the participants that the fund has sent the indicated user.

Background cancellation: an action by the network to withdraw the call permission of a user who has previously sent the fund. The new capabilities of the PoC fund control server that are added in a request mode facilitate the regulation of the call group as follows: requirement of fund regulation: an action of the network to indicate to a UE that a requirement by a particular user; fund regulation response: an action by the UE (regulator) to require the network to send the user a command or send a command for the entire group of calls. The regulation response of the fund is intended to be introduced in any of the conventional background control skills, such as background cancellation, background sending, etc. The ÜE in this case can implement standby requirements manually or automatically for multiple users. With these additional skills, the arbitrary operation of calls is usually carried out through the use of the RTCP (real-time control protocol) that is left in the group's regulator. In the event where the Meta Groups function is implemented, the Meta Groups themselves may preferably remain arbitrary through the RTCP. Meta Groups may consider different call groups, with conventional background control abilities, such as background cancellation, background sending, etc., but only among regulators, once the "Meta-background" is sent to. a particular regulator, the moderator in turn sends the donation to a member of his account group. While the "meta-background" is inactive, the call group is limited to singular groups. While the "meta-background" is sent, all the call groups comprise the meta-group that can listen to the conversation. The GLMS Management Function List includes: Store contact lists used to store contact entries in the GLMS server. (POC server and UE). The list of additional GLMS Administration Functions implemented in this specific modality of the application includes: User Class - Apply particular profiles to the members of the group's list in terms of background requirements as follows: accesses on hold, accesses of request of background and waiting background and waiting request and access response from the background regulator (only for the simple call group regulator).

Meta-Groups' - For a group of regulated call between "n" groups of calls regulated differently. Background overlap concerns the member of the group that contains the Metya background groups at a particular time. Only the regulated groups can be added to the Meta Groups. Access lists are used to define access rules, which are those that allow or can not reach a specific user through PoC .. In some modalities, the covered basic structure of the Regulated Call Group are conventional structures such as a text message Instant / MMS alerts to members within a group and / or private chat groups within a group. Referring now to Figures 9A, 9B and 9C, which show in detail the flow diagram of a call to illustrate an example of implementation or call group regulated in a PoC implementation. For this example of "discussion", it is assumed that there are two separate groups where they are regulated by the respective group regulators. Background access between the two groups is carried out through both the RTCP and the conventional establishment PoC The signage between the Group Regulator is shown A of PoC 200 Clients, the Group B Regulator of Clients PoC 202, PoC Server 204, PoC Group of Clients 206 and PoC Group of Clients 208. PoC Group of Clients 206 represents the group members that are regulated by the PoC Group A Regulator of Clients. Similarly, Group B of PoC 208 Clients represents the clients that are regulated by the Group B Regulator of PoC Clients 202. Starting in Figure 9A the session begins with a Group A member by pressing a PoC button that results in the establishment of a SIP session among all the UEs in Group A as indicated in 210. All detailed PoC messages may not be shown clearly. This is followed by the PoC 200 Client Group A Regulator that sends a 212 background requirement for Group A of the PoC Server 204. The fund intake is sent in 214 to Group A of PoC Clients. In 215, the Group A Regulator of PoC Clients verbally (or by alternative message formats such as IM) tells the members of group A that the discussion begins. After this, the PoC 200 Customer Group A Regulator releases the fund as indicated by 216 after the fund becomes inactive as indicated in 218. Up to this point, while the Group A Regulator of Customers PoC 200 behaves like a regulator, no regulation is established. In 220, the PoC 200 Customer Group A Regulator presses a PoC Group Goal button. More generally, any suitable user interface can be activated by the PoC Client Group A Regulator in order to establish a Target Group regulator to facilitate the regulation of PoC 200 Client Group A and the regulation of Group B of PoC 202 Clients. In step 222, the Group A Regulator of PoC 200 Clients makes a requirement to the fund with the Fund / Sending Target requirement of Group 222 and the fund is taken to 224. The "take of the fund" message 224 indicates that the PoC server informs ak Regulator B that the background was taken. At this point, Regulator A informs the regulator B that the discussion starts as indicated in 225. The regulator of Group A of Clients PoC then releases the fund in 226 and the PoC Server 224 responds with the Meta Inactive Fund Group 228 Subsequently, the Group B 202 regulator presses its PoC button to establish a call group session between the members of Group B as indicated at 230. The Group B Regulator of the PoC 202 Clients requires the fund as it is indicated in 232 after the background is taken as indicated in 234. Then, the Group B Regulator indicates to this group that the discussion starts as indicated in 235. Note that the bottom goal is inactive at this point, which indicates that group A is not deprived of the conversation that the Group B Regulator has with Group B. Following this, the Group B Regulator of PoC 202 releases the fund in 2366 after the fund becomes inactive as indicated in 238.

Continuing with Figure 9B, at 240, the PoC Client Group B Regulator 202 sends the Background Group Requirement message to the PoC Server 204 in response to a Meta Group 242 Background Submission that is sent from the PoC Server 204 to the regulator of Group B of Clients 202. At this point, the fund is taken as indicated in 246. At this point, Regulator B has required the fund and in turn is able to take both Group A and Group B , for example to indicate to the whole group that the discussion has begun. Both groups are online at this point, after this, the Group B Regulator of the PoC 202 Clients releases the fund as indicated in 248 after the fund is inactive by the inactive Fund of the Meta Group 250. At this point, the background overlap of the regulator of the members of the group that contains the Meta Fund Group. As indicated previously, the RTCP can control the Meta Fondo through conventional PoC stages. It continues to sink that Group A uses "JOE" which requires the fund as indicated in 252. This requirement is sent by the PoC Server 204 to the Group A Regulator of PoC 200 Clients as indicated in 254 as a new message, " Requirement of Fund Regulation ". In response to this, the PoC Client Group A Regulator requires the Fund in 256, the fund is sent to 258 after the fund takes the indication in 260 that is generated by the PoC Server 204. Then, the Group Regulator A of Clients PoC 200 sends a response to the Fund Regulator (with a "Send Background" message included) 262 to the PoC Server 204 resulting in the Sending of Fund 264 sent by the PoC Server to the user "JOE" to provide "JOE" the background. Then, as indicated in 265, the user of Group A "JOE" is in position to speak to all the members of Group A and Group B. Some time later, the user of Group A "FRED" requires the Fund as indicates at 266. However, for the purpose of the example, it is assumed that the user "FRED" has only "standby only" privileges with the GLMS and how the Denied Background message 268 is generated by the PoC Server 204 in response to the requirement 266 without any interaction with the required regulator of GrupO a. Some time later, the user of Group B "GABBY" requires the fund as indicated at 270. The Fund Regulation requirement 272 is sent by the PoC Server 204 to the Group B Regulator of PoC Clients 202. In response to this, for reasons of the example, it is assumed that the Group B Customer Regulator PoC 202 generates a Fund Regulation response (with a "Denied Fund" message included) 274 that cancels the fund to "GABBY". In response to this, the Denied Fund message 276 of the PoC Server 204 is for the "GABBY" user of Group B.

Continuing in Figure 9C, some time later.

The user "MARY" of Group B requires the fund as indicated in 278. The Poc Server 204 sends the request of the Fund Regulator to the Group B Regulator of ClC 202 as indicated in 280. The Regulator of Group B of Customers PoC 202 sends a Group 282 Target Fund Request message to PoC Server 204 to require the fund. In this particular example, the implementation involved is such that waiting is ordered in the Meta Group, since the requirement is automatically served in a final period of time by means of a "Meta group" 288.

In another modality, the Meta regulation is provided Group. Alternatively, there is no ordering of Shipments of Goal Groups which means that the Submission of Meta Gruppos is allowed only during the Inactive periods of the Meta Background. When the user "JOE" of Group A ends as indicated by the Release of the 284 Fund, the regulator * of the Group A of Customers PoC 200 also sends a Fund Release of the target Group 286 to ready the Fund so that the next group has access to the fund. In another modality, the "Group Meta Fund Release" can be sent automatically by the PoC server, rather because it involves the Group regulator. A Send Message of the Group Group 288 is generated by the PoC Server 204 and sent to the Group B Regulator of the PoC 202 Clients as soon as the waiting request is sent from the Fund Requirement of the Group Group 282. The Fund then At this point, the PoC Client Group B Regulator 202 generates a Fund Regulation response (with a "Background Send" message included) 292 that is sent to the PoC Server 204. In In response to this, the PoC Server 204 generates the message Send Fund 294 that is sent to the user of Group B "MARY" who is now in position to access the fund as indicated in 295. Some time later, the user of the Group A "ALEX" requires the fund as indicated in 296. This is sent as a requirement of Fund Regulation to the Group A Regulator of PoC 200 Clients. In 300, the Group A Regulator of PoC 200 Clients generates an alert 300 for the Group regulator B of PoC 202 Clients in order to alert Regulator B that searches for the Bottom Goal. These Alerts can for example be implemented by means of the PoC server (not explicitly shown in Figure 9C). Alternatively, a time may be implemented in order to generate an automatic cancellation of the Fund for Group B at a certain point. Alternatively a designated Regulatory Goal may cause a Cancellation to the user "MARY". In response to this Group B Regulator PoC 202, a Fund Regulation response is sent (with a "Background Cancellation" message included) 302 for the PoC Server 204 and the user "MARY" is canceled. This is sent as a Background Delete 200 message to the user of group B "MARY". After this, the PoC Client Group B regulator 202 sends a release message from the Fund to the Target Group 306 to release the fund. The PoC Client Group A Regulator then sends a request message from the Meta Group 308 Fund to the PoC Server 204 in response to the fund being sent as indicated in 310. A message taken from the fund is generated in 312 and sent to the Group B Regulator of PoC Clients. Then, the Fund Regulation response (with a "Background Send" message included) 314 is generated by the PoC Client Group A Regulator for the "ALEX" user. In response to this, the PoC Server 204 sends the Background Sending message 316 to the user "ALEX". In 317, the user of group A "ALEX" is now in position to occupy the background. The modalities presented above provide systems and methods for "ordering calls" and "regular calls". In other modalities, the "call regulation" systems and methods are provided to support consumers as well as the rules for more structured calls, for example, to control businesses. In the call regulation, the terms "order" or "regulation" are integrated into a series of "rules of order" for a session similar to PTT. When the "rules of order" are active, they qualify all communications within the session that takes part in one of several possible movements. The movements are encoded within tables that register a place of priority of movements with respect to each other in such a way that the movement can be done out of order. Moreover, participants can assume positions that impose their additional rights and obligations as a result of one or more movements. A table maintains the dispatch of the assigned position to each participant. For example, a naming movement may ultimately result in a participant sending the "chair" position as well as the rights and obligations associated with this position, while another participant may send the position of "secretary" in a similar manner. All these structures combine to allow a PTT session that provides an assembly of participants, examples of assemblies include meetings of shareholders, meetings of the board of directors, meetings of committees. The "call regulation" structures can be used for sessions in turn and at the moment within well-structured assemblies. For example, a PTT session group can start as an informal discussion. However, if a participant chooses to impose rules of order, a default series of rules is provided and current participants can afford to alter the default rules, for example, by reflecting the desire of the members of the assembly to form a partnership. Similarly, within the assemblies of "call regulations" it is considered that informal discussions can be generated or sub-assemblies or committees can be created with "call regulations" in order to define the purposes, such as the preparation of a report. Operationally, one or more tables can be used to keep the "rules of order". In a modality, a tab of ORDER of PRECEDENCE of MOVEMENTS (OPM) and the table on RULES RELATED to MOVEMENTS (RRM) keep the "rules of order". The OPM and RRM tables define an initial series of movements and rules. The OPM and RRM tables can themselves be altered by movements, such as a movement to adopt "rules of order". Thus, through a series of exemplary OPM and RRM tables that are provided within this application, it is contemplated that through the use of these tables it will be modified to adjust the particular needs of a specific group of participants during one or more sessions.

The OPM and exemplary RRM table is adapted from Robert's Rules of Order, original copyright of 1915 and published in various forms. The next RRO was adapted from http: // www. constitution org / rror / rror-00.htm. An example of a table of Rules of Order of Robert (RRO) ORDER of PRECEDENCE of MOVEMENTS (OPM) is: 1 2 3 4 5 Movement - X to X - Fixes the Time in which it works. - X b - - Work. - X c X - Take a break. - X - - - ask a Privilege Question. - - - - - Place in the Table. - - - - X Previous question. - - - - X Limit or Extend the Limits of the Debate X - - X - Postpone for a Certain Time. X - - X - Amendment. X - - - - Postpone Indefinitely. X - - X - A Main Movement.

An example of Legend for RRO OPM Columns: 1- Debattable 2- Normally Privileged. 3- Not always privileged: a- Privileged only when another question is pending and in an assembly that is made without conditioning another agreement on the same day or the next. b- Loses its privileged nature and is a principal movement if in any qualified means or if its effects, if adopted, are to dissolve the assembly without any provision of this agreement again. c- Privileged only when it is done while other businesses are pending. 4- They can be amended. 2/3 of the votes are required for adoption; the others require only the majority. Movement - brief description of the movement Example of table of RULES RELATED to MOVEMENTS (RRM): 1 234 5 6 7 8 N Movements * _ ** * _ _ _ i Work (when privileged) _ _ _ _ Adopt (Accept or Add to) a report 2 - - - - Adopt Constitutions, through laws, rules of Order - _ _ _ _ _ Adopt Support Rules 4 - - - - 3 Amendments 4 _ * _ _ _ _ _ _ Amend an Amendment 2 5 - - - Amend Constitutions, by laws, rules of the Order - - 6 - - - Amend Rules of Support * - * - - - - - * 7 Personalities, related to the Indecorum, etc. _ _ * _ _ _ _ * _ Personalities, other cases _ _ * _ _ _ * _ _ objectives, Filling - 8 - - - - Committee or Reference, or I recommended * _ * _ _ Discussions, to Close, Limit or Extension * _ ** * _ * * _ Division of the Assembly * * - 10 10 - Division of Question 11 - - - - 1 Set Working Time - - * - 2 - - - - Informal Consideration of a Question * _ ** * _ _ _ _ place in the Table * _ ** _ _ _ _ _ allow Continue Speaking after the Indecoru _ _ _ _ _ _ Main Motion or Question - - * - * - * - - Appointments, To Do * -k * _ _ _ Appointments, for Closing * 2 - - - - Appointments, to re-open • k _ ** 2 12 * * - Objection to the Consideration of a Question * - ** * - * * - Order, Questions of _ _ * _ _ _ order, to Make a Special * _ ** * _ * * _ Orders of the Day, for Call of - "- - - - - Agenda, when it is pending * _ ** * _ * * _ Parliamentary inquiry _ _ _ _ _ postpone Definitely, or by Certain Time - * - - 13 - - - - Postpone Indefinitely * - * * 15 * - - 14 Previous Questions * - ** * - * * Privilege, to Incorporate Questions of _ _ _ _ _ • Privilege, Issues of, when pending * _ ** _ _ _ _ _ Reading Documents 11 * - - - 1 Break, to take one (when privileged) 7 * - * - - * 16 Reconsiderations - * - - 2 18 Rescind or Cancel - _ _ _ _ _ Substitute (same as an Amendment) * - ** * * - - - Suspend the Rules * _ ** * _ _ _ _ To ar of the Table * _ ** * * _ _ _ To ask a question outside of your Own Order * _ _ _ _ _ vote, Movements related to * _ ** 2 - '* - - Design a Movement, Allow for Example of Legend for the RRO RRM Columns: 1- Susceptible 2- Debate Confined to Pending Questions 3- May be Amended 4- Subsidiary Movements May Be Applied 5- Can be reconsidered 6- Requires only the Most Votes 7- Can be Seconded 8- Out of Order when Other has Fund N- Next Note Movement- brief description of the movement The rules in the header of the 8 columns apply to all the original main movements and for all other cases except when an asterisk (*) or a figure indicate that the movement is an exception to these rules. The asterisk shows the exact opposite of the rule in the heading of the column that applies to the movement and a figure refers to a note explaining the extent of the exception. For example, "Place in the Table"; ka Table shows that it is "unattainable" and "can not be amended"; what "does not subsidize the movement to be applied" to this; and that this "can not be reconsidered"; - the fact that four other columns do not have asterisks or figures shows that the rules in the header of these columns apply to this movement, for Placing in the Table, it is the same for the original main movements.

NOTES TO THE RRO RRM TABLE 1. To Fix Working Time is privileged only when it is done while another question is pending and in an assembly that does not have conditions for another assembly on the same day or the next. For the loss of the Work this privileged character and its main movement is done if any qualified route or if its effect, if adopted, is to dissolve the assembly without any condition for it again. To Take a Break is privileged only when it is done while another business is pending. 2. An affirmative vote in this movement can not be reconsidered. 3. An Enmiend can be done by inserting (or adding) words or paragraphs; (b) by eliminating words or paragraphs; (c) by eliminating certain words and inserting others; or (d) by substituting one or more paragraphs for others, or a resolution of another in the same subject. 4. Not actuatable when the movement to be amended or reconsiderable is not updatable. 5. The, by Constitutions, By Laws and Rules of Order before the adoption are always with respect to the main movements and can be amended by a majority of votes, after the adoption is required prior notice of 2/3 of votes for the amendment. 6. Establish rules that can be amended at any time by a majority of votes if prior notification is made, or by 2/3 of the votes without notification. 7. A Personality is not updatable when it is done while a non-updateable question is pending or when it is related to indecorum or because of transgressions of the rules to speak or by the priority of the business. When it is updatable, only one word 'of each member is allowed. It only "links the decision of the vote of the president that remains. 8. It can not be reconsidered after the committee has initiated the issue, but 2/3 of the committee's votes at any time can be downloaded for further consideration of the question. 9. These moves can be made wherever the open question is moot and can apply only to this, unless otherwise specified. 10. If the resolutions or proposals are related to different issues that are independent of each other, these can be divided into the requirements of a single member, which can be done when another has the background. If these are related to the same issue and each part generated can remain isolated, they can be divided only into a regular movement and vote. 11. It is not updatable if it is done when another question is before in the assembly. 12. An objection can be made only when the question is introduced first, before the discussion. 2/3 of the votes may be opposed to the consideration in order to maintain the objection. 13. A negative vote in this movement can not be reconsidered. 14. The Prior Question can be moved whenever the immediately pending question is discussed or amended.

The questions about this movement that takes place must be specified; if they are not specified, this only applies to the immediately pending question. If the cut of the discussion is adopted and once the assembly is generated to vote on the immediately pending question and as others are specified in the movement. 15. It can not be reconsidered after a vote has been taken on this. 16. The movement to be reconsidered can be done while any other question is before the assembly and whenever another has the background, or after it has been voted to work, indicating to the assembly that it has not declared itself to work. It can be withdrawn only during the day or the day after, the vote that was proposed to reconsider that it was taken, and through one that voted with the privileged side. This consideration can not interrupt the business unless the motion to be reconsidered takes precedence over the immediately pending question. This range is the same as the movement to be reconsidered, except because it takes precedence in a general order, or a movement of equivalent rank with the movement to be reconsidered, provides the "considerations that have not been done at present. the main discussion of the question when it is made afterwards can be discussed 18. The cancellation is done under the same rules as well as to amend something that has already been adopted, see notes 2, 5 and 6 above.

ADDITIONAL RRO RULES Incidental movements. The movements are incidental to pending movements that take precedence over these and must be acted upon over the first. See classification below for the list of these movements. The subsidiary non-privileged movement can be loaded into the table, postponed definitively or indefinitely, or deposited. When the main question is loaded in the table, etc., all the subsidies are added with this one.

CLASSIFICATION OF RRO MOVEMENTS Main Incidental Movements Accept or Adopt a Report of a subject referred to a committee Work in or for, a future time Work, if it qualifies in a route, or to work when the effect is to dissolve the assembly without the condition of reconfirm Indicate the time and place of the next assembly, if it is introduced when there are no pending negotiations Amend the Constitution, through laws, establish rules or resolutions, already adopted Ratify or confirm the action taken Rescind or reject the action taken Subsidiary Movements Load in the Table The Previous Question Limit or extend Discussion Limits Define Definately, or at a Certain Time Send or Refer, or Resend Amend Postpone Indefinitely Incidental Movements Questions by Appearance Order Suspension of the Rules Objection to the Consideration of a Question Division of a Question and Consideration of the Paragraph or Seriation Division of the Assembly and Movements related to Methods to Vote, or to Close d Open again the Voting Movements related to the Methods to Make or Close or to Re-open the Appointments Requirements developed outside the Pending Business or that are just pending; as a Parliamentary Inquiry, an Information Request, to Allow the Removal of a Movement, to Read Documents, to withdraw from an Obligation or for any other Privilege Privileged Movements Set Work Time (if done while another question is pending Work (if it is not qualified and does not have the effect of dissolving the assembly) Take a Break (if done while another question is pending) Make a Question of Ablar Privilege for the Orders of the Day Main or Unclassified Movements Take from Table Reconsider Rescind Ratify Take, Absurd, or Frivolous Movements Call from Home Additional details of the Rules of the Order of Robert can be obtained by referring directly to any of the various published versions of the rules of Robert's Order. These rules have been described here for purposes of having a defined example of tables from an OPM table and an RRM table. In addition to the OPM and RRM tables, an optional table performance can be used to define participant positions, as well as to define the RIGHTS that participants can have to perform specific MOVEMENTS (RMM) within a session. Referring now to Figure 10, there is shown a flow map with exemplary steps of a method for a "call regulation", a variant of "sort" and "regular" calls. In step 1010, the assembly is reported to order. For example, a user of a mobile device initiates a group session similar to PTT where the identifier of an assembly or AID is specified. In step 1020, the rules of order (ROO) are retrieved from a store that takes place ROO 1025. At least the controller recovers the ROO. In an alternative mode, all participants retrieve the rules of order in this step. In step 1030, the rules of order (ROO) take place with the participants. In an alternative mode, this step is optional.

In step 1040, the movements are processed according to the ROO. Additional details of this step are shown in Figure 11. In step 1050, the ROO is stored to reflect any changes that result from the processing of the movements. In step 1060, the assembly is dissolved. Referring now to Figure 11, additional details of the movement processing step of Figure 10 are shown. In step 1110, initiate movement processing. In step 1120, at least one participant, such as the regulator, seeks a movement. The movement can come from other participants of the assembly or the regulator. In an alternative modality, all participants expect a movement. In step 1130, it is determined whether or not the participant making the movement has the right to make the movement. For example, through many participants who are part of a samblea for a society, only those participants who have paid their obligations are enabled to make movements. This is determined by analyzing the participant in the ROO Rights to Move (RMM) table 1135, for example.

In step 1140, it is determined when the movement is in order or not. For example, a move to Call the Orders of the Day is out of order if after a move you do not take a break. This is determined by observing movement in the Movement Precedence Order (OPM) 1145, for example. In step 1150, it is determined whether or not the movement respects the rules related to movements. For example, some movements can move whenever the pending question is discussed, and this applies only to this, unless otherwise indicated. This is determined by observing the movement in the Rules Relating to Movements (RRM) 1155, for example. In step 1160, if the movement has been determined to be moved by a participant who has the right to make the movement, if the movement has been determined to be in order and if the movement has been determined by respecting the rules related to movements , if the movement has been acted upon. The actions are considered to include the acquired call channel, answer and carry out a vote, keep a document as a report to "load it into the table", amend a movement or any other communication that has an advance effect for purposes of convenience of the assembly, including the generation of sub-assemblies and committees.

In step 1170, if the movement has been determined to fail in any of steps 1140, 1150 or 1160, then it is canceled. In step 1180, if the movement acts on step 1170 to work, when the method steps up 1190 and the movement proceeds to finish. For the other movements, the method continues in step 1130 and a new movement is expected. It is considered that the determined steps of the method can be carried out in conjunction with a user interface in the mobile communication devices of the assembly participants. Preferably, when a participant wishes to make a movement, only those movements that have the right to do, that are in order, and that on the other hand respect the rules of order that are suggested to the user through the user interface. In some embodiments, the method, system and device are adapted to provide peripheral support of wired devices to participate in a wireless call by means of a network intertrap function, such that the devices are not within the wireless network. , but they appear as they are, and are able to participate here. Therefore, according to this embodiment, not all or necessarily any of the devices in an APTT ™ group are wireless and the message transmission channel occurs analogously as described here above in the APTT ™ groups where one or more of the devices are stationary or on the other hand the device can be wired or not wireless. Accordingly, an APTT ™ session may be wired or have devices based on land lines participating in the APTT ™ session according to the modalities, adapted to transmit and receive messages from the transmission channel's request message. Various modifications are possible in the clarity of the foregoing teachings, this should be understood within the scope of the appended claims, the application may be carried out on the other hand as specifically described herein.

Claims (24)

1. CLAIMS 1. A call order controller for use in a network adapted to provide similar communications capabilities walkie-talkie (portable radio-telephone) in a device call group, such as within the group, is given to a single device transmission capacity, while all other devices have reception capability, characterized in that the call order controller is adapted to perform the call order control by: receiving requests via the network for the transmission capacity and maintaining a record of the outstanding requests and grant requests for the transmission capacity based on the registration of the outstanding requests; wherein the call order controller is part of and is in combination with one of the devices in the device group.
2. 2. The call order controller according to claim 1, characterized in that the walkie-talkie-like communications are provided using wireless communication channels to the devices, the devices are wireless devices.
3. 3. The call order controller according to claim 1 or claim 2, characterized in that the registration of the outstanding requests comprises a list of outstanding requests arranged in an order in which they were received and in which the requests for capacity of transmission are granted from the oldest to the newest.
4. The call order controller according to any of claims 1 to 3, characterized in that it is adapted to detect or receive an indication that transmission capacity has been granted and in response to the transmission capacity that has been granted, transmit a clear message to speak to a device close to being granted the transmission capacity.
5. The call order controller according to any of claims 1 to 4, characterized in that it is further adapted to receive a request for a device to request that the device no longer be considered pending the transmission capacity.
6. 6. The call order controller according to any of claims 1 to 5, characterized in that the transmitted messages are associated with the conversation group, the messages comprise at least one of: message of conversation release of the network to the device; Clear message to talk from the network to the device; message interrupting the network to the device, the interrupt message is used to request a device that has the transmission capacity to give the transmission capacity or mute order of the network to the wireless device.
7. 7. The call order controller according to any of claims 1 to 6, characterized further is adapted to count a number of requests received from each device and reprioritize the granting of the transmission privilege based on the number of requests. requests received from each device, the transmission privilege is a right to grant the transmission capacity.
8. The call order controller according to any of claims 1 to 7, characterized in that it is in combination with the plurality of groups of wireless devices.
9. The call order controller according to any of claims 1 to 8, characterized in that it is further adapted to: maintain a set of order rules for the calling group; allow interaction between the call group according to the rules of order.
10. The call order controller according to claim 9, characterized in that the order rules comprise any or a combination of: rights to make movements; order of precedence of movements or rules with respect to movements.
11. 11. The call order controller according to any one of claims 1 to 8, 9 or 10, characterized in that it is implemented using one of communications based on CDMA, communications based on 802.11, iDEN, GPRS, Bluetooth, UTMS or PoC.
12. 12. The call order controller according to any one of claims 1 to 8, 9 or 11, characterized in that the messages are transmitted using DTMF signals (double tone multifrequency).
13. 13. The call order controller according to any one of claims 1 to 8, 9 or 12, characterized in that the walkie-talkie-like communications are provided using wireless communication channels to the devices, the devices are wireless devices.
14. 14. A network adapted to provide communication capabilities similar to walkie-talkie within a device call group, such as within the group, is given to a single device transmission capacity, while all other devices have reception capability, the network is adapted to provide moderate call control by means of: floor moderation requests that are actions of the network to indicate to a moderator wireless device that a request has been made by a particular user of a wireless device, the wireless device moderator is a wireless device that has the ability to control the order in which wireless devices that have requested a call channel are granted access to that channel and floor moderation responses that are actions of the moderator wireless device to ask the network that sends a relative command to the user's wireless device with your request to access the call channel.
15. 15. The network according to claim 14, characterized in that the network comprises a network to press to talk on cell (Poc).
16. 16. The network according to claim 14, characterized in that the network comprises a call order controller for each call group, the network is adapted to, for each group: maintain a designation that a particular device is the wireless device moderator for the group; receive requests for transmission capacity and send requests to the moderator wireless device; receive from the moderator wireless device concessions of the transmission capacity and send each grant to at least one respective requesting device.
17. 17. The compliance network as claimed in claim 16, characterized in that it is further adapted to: maintain privilege information for each of the device call groups; receive call group control messages from the wireless devices and process the messages according to the privilege information.
18. 18. The compliance network as claimed in claim 17, characterized in that the privilege information comprises an indication of whether at least one of the following privileges is agreed with a given wireless device: moderator capability; meta-group moderator capacity, the meta-group moderator capacity is the ability to moderate a plurality of distinct moderated call groups; private messaging within the group; broadcast messaging; -access to call channel request or access to listen only.
19. The network according to any of claims 16 to 18, characterized in that the call order controller for each group of devices forms part of one of the devices of the group.
20. The network according to claim 18, characterized in that the wireless moderator device is adapted to receive requests from other devices for transmission capacity via the network; the moderator wireless device has interface with the user to receive the selection of the user of a device from which a request for the transmission capacity has been received to be selected and the transmission capacity granted; in response to user selection, the wireless moderator device is adapted to transmit a message that grants the transmission capability to the device via the network.
21. 21. A method, characterized in that it comprises in sequence: establishing a session of communications similar to walkie-talkie provided by network, among a plurality of wireless devices; grant transmission capacity to one of the wireless devices and reception capacity to remaining wireless devices and receive requests for transmission capacity of wireless devices that have reception capability; grant transmission capacity in response to requests for transmission capacity; wherein the concession of transmission capacity in response to the requests for transmission capacity is made under the control of a designated moderator device, the designated moderator device is one of the plurality of wireless devices.
22. 22. The method according to claim 21, characterized in that the granting of the transmission capacity in response to requests for transmission capacity is made in the order in which the requests are received.
23. 23. The method according to claim 21 or claim 22, characterized in that the granting of the transmission capacity in response to requests for transmission capacity is made according to a defined set of order rules.
24. 24. A computer program product, characterized in that it comprises a computer-readable medium, which implements computer program instruction means executable by a processor of a wireless device, the program instruction means, when executed, cause the wireless device to implement the method according to any of claims 21 to 23.