A method and an apparatus for adding a new member to an active group call in a group communication network

TECHNICAL FIELD OF THE INVENTION

The present invention relates to communication systems, point-to-multipoint. In particular, the present invention relates to a method and apparatus for adding new members to an active group call in a group communication network.

BACKGROUND

Class wireless services intended for quick, efficient connection from point to point two-way or a point-to-multipoint (group communication), has existed in various forms for many years. In general, these services have been half-duplex, i.e. to begin to talk, the user had to press a button switch between transmit / receive (PTT) on your phone / walkie-talkie. Pressing either switches its radio, in some implementations, or in a coordinated system where communication takes place via a server of some type, indicates the user's request to transmit mode ("right words"). If given the transmission mode, or permission to speak, the user usually speaks a few seconds, and then releases the PTT, and other users can request the transfer mode. Communication is generally from one talker to a group of subscribers listeners, but may be implemented in duplex mode. This service has traditionally been used in applications where one person, "manager" needs in connection with a group of people, such as field service personnel or taxi drivers, and hence the name "dispatch" for the service.

Similar services are provided on the Internet and are generally known as an interactive voice session ("voice chat"). These services are typically implemented as computer applications that send vocoder frames in packets of Internet Protocol (IP), which is a voice service over IP (VOIP), the central server group chat, or possibly from client to client in service peer communications devices.

The most important feature of these services is that communication is quick and spontaneous, usually initiated by simply pressing the PTT, without the usual sequence of dialing and ringing. Communication in this type of service is generally very short, discrete lengths conversation lasts typically about a few seconds, "negotiations" lasting possibly a minute or less.

The time delay between when the user requests a transmission mode, and the time when he receives a positive or negative confirmation from the server that it is in the transmission mode and may begin speaking, which is known as delayed transition in the transmission mode is an important parameter for half-duplex systems The group communication. According to the above, the supervisor prefer short, quick negotiations, making the service becomes less effective when the delay in the transition to the mode of transmission is increased.

Existing group communication infrastructures provide limited opportunities for significantly reducing the delay in the transition mode of transmission, ie, actual switching delay in the transmission mode is impossible is reduced below the time required to re-establish a traffic channel dormant packet data session. In addition, traffic channels talker and a listener are installed in series, because the only mechanism by which to start to activate an inactive group is to wait for re-establishment of the traffic channel talker to signal the server. Currently, there is no mechanism for the mobile station triggered the alarm by sending data other than traffic channel - a limitation that requires re-establish traffic channels before they can carry out any connection between the client and the server.

This necessitates a mechanism for reducing the perceived delay in the transmission mode transition, perceived talker and total time required to re-establish traffic channels for participating mobile devices without negatively impacting system capacity, a battery life of power customers or other resources.

In a dispatch model, communication between endpoints occurs within virtual groups, where the broadcasting of speech one "talker" on one or several "listening to customers." One example of this type of communication is typically call or simply a call dispatching. The call is an implementation group, which specifies the characteristics of the call and is, in fact, a list of members, which is connected with some information, such as group name or group ID. Member List - a list of one or more users that are invited to participate in the call.

There is a need for a dispatch model that supports both the chat-room model and the ad hoc model of group call services. In the chat-room model, the groups are pre-defined, which may be stored on the dispatch server. However, special pattern group can be set and / or change in real time.

SUMMARY OF THE INVENTION

The disclosed embodiments provide a communication device a new and improved method for adding a member to an active group call in a group communication network, which includes receiving a member list from a user and sending a server request to add the membership list to the active group call.

According to another aspect of the invention a computer readable medium in a communication device embodies a method for adding a member to an active group call in a group communication network, which method comprises the aforementioned steps.

According to another aspect of the invention a communication device for adding a member to an active group call in a group communication network includes means for receiving a member list from a user and means for sending the server request to add a member list to an active group call.

According to another aspect of the invention a communication device for adding a member to an active group call in a group communication network includes a receiver, a transmitter, and a processor communicatively connected to the receiver and the transmitter. The processor is capable of receiving from the user a list of members and send a request to the server to add to the list of members to an active group call. According to one aspect of the communication device is a device with switching between transmission and reception (PTT).

The disclosed embodiments also provide the server a new and improved method for adding a member to an active group call in a group communication network, which includes the steps of receiving a request for adding a member list from an active group call and adding the member list from the active group call. According to one aspect, the method further includes the advertisement of each member of the member list that they are being added from the group call.

According to another aspect of the invention a computer readable medium at the server implements a method of adding a member to an active group call in a group communication network, which method comprises the aforementioned steps.

According to another aspect of the invention, a server for adding a member to an active group call in a group communication network includes means for receiving a request for adding a member list to an active group call and means for adding the member list to the active group call. In one aspect, the server further comprises means for declaring each member from the list of members that is added to the group call.

According to another aspect of the invention, a server for adding a member to an active group call in a group communication network includes a receiver, a transmitter, and a processor communicatively connected to the receiver and the transmitter. The processor is configured to receive a request for adding a member list to an active group call and adding the member list to the active group call. In one aspect the processor is further configured to ads each member from the list of members that is added to the group call.

LIST OF FIGURES

The features and advantages of the invention will become apparent from the detailed description given below in conjunction with the drawings identify correspondingly throughout:

1 - scheme of the group communication;

2 - scheme of interaction between multiple applications with one another;

Figure 3 - schematic diagram of an exemplary registration process of the user according to one embodiment;

Figure 4 - schematic diagram of an exemplary local intra call setup according to one embodiment;

5 - a diagram of an exemplary process of remote intra call setup according to one embodiment;

6 - a diagram of an exemplary local inter-process call set-up according to one embodiment;

7 - an exemplary remote inter-process call set-up according to one embodiment;

Figure 8 - schematic diagram of an exemplary process exit the group call according to one embodiment;

9 - diagram of an exemplary process for completing a group call according to one embodiment;

10 - an exemplary process of sending notification of the group call according to one embodiment;

11 - an exemplary process of joining the group call according to one embodiment;

12 - an exemplary process of a service interruption of the speaker in accordance with one embodiment;

13 - an exemplary process for adding new members to an active group call according to one embodiment;

14 - an exemplary process exclusion of participants from a group call according to one embodiment;

15 - an exemplary user registration cancellation process according to an embodiment;

16 - scheme of interaction of several communication devices with the control means (manager) link (NMS, SM) according to one embodiment;

17 - buffering scheme useful information on the side of the communication control means according to one embodiment; and

18 - buffering scheme useful information on the client side according to one embodiment.

Detailed description

Before proceeding to a detailed explanation of the invention, it should be understood that the invention is not limited in its application to the details of construction and orgkomponovke components set forth in the following description or illustrated in the drawings. The invention can be implemented in other embodiments, and implemented in various ways. Furthermore, it is understood that as used herein, the phraseology and terminology are intended to describe and not intended to be limiting.

1 illustrates an exemplary functional block diagram of a group communication system 100. Group communication system 100 is known, as well as a system switching between transmission and reception (PTT) service is a broadcasting network (SPM, NBS), dispatch system or communication system is a point-to-multipoint. In one embodiment, group communication system 100 includes application server components, such as dispatchers, local servers, systems management module useful information (MCU, MCU), the registration server uses and clients of the Internet Protocol (IP) (for a wireless and / or wired Due to be connected for IP). Application server components may be deployed either in a centralized structure or a regional structures, depending on the functions of the components. The centralized structure may include a support controller (ML, HD) 102, the support server 104 to determine the location (SIR, HLS) 106, and a database of users / groups. These components may be centrally located in the service provider's network and may be accessible regional structures. The centralized components may be used in locating the roaming users and in initiating inter-regional group calls. Regional structure 108, 110 may include a regional server 112 Positioning (CPR, PLS), the regional dispatcher (RD, RD) 114, a regional set of 116 control module useful information (MCU) and the regional server 118 registration use (MIS, ULS) .

Regional structure can be distributed over a network service provider that ensures minimization of network delays associated with call establishment in order to meet the requirements of the instantaneous response. Load sharing calls for several regional systems also enables the deployment schemes with adequate opportunities to expand to support a large number of users. Regional components of the Application Server provides user registration, establishment and administration of intra-regional calls, as well as the initiation and delivery of notifications to users registered in the region.

Devices 120, 122, the group communication (clients) that may be deployed, for example, the handset cdma2000, requesting a packet data session using a standard option data services and uses this session to register its IP-address via the application server and Initiation of the group calls. In one embodiment, the components 108, 110 of the application server connected to the nodes of the packet data transmission service (PDSN, PDSN) service provider. Clients 120 and 122, the requesting packet data session from the wireless infrastructure, have IP connectivity for the components 108, 110 of the application server via the PDSN.

After power-up, clients 120, 122 may request a packet data session using the data service option. In order to establish the packet data session, the client is assigned IP-address. At this time, the customer also receives a server address 124 Domain Name Service (DNS, DNS). Client 120, 122 queries the DNS server 124, for example, using a search service record (SRV), to find the address of CPR 112. CPR 112 to determine the location, the client 120, 122 may carry out the registration, saying its application server location information, such as IP-address. Registration may be performed using the IP protocol, such as session initiation protocol (SIP) over user datagram protocol (UDP). IP-address of the client 120, 122 may be used to communicate with the client when the user is invited into a group call.

In one embodiment, upon completion of the registration, the client may perform another search in the DNS SRV record, to find the address of regional dispatcher 114. The client communicates with the regional dispatcher whenever the user requests a call or transmits a start notification. The interface between regional dispatcher 114 and client 120, 122 may serve as a signaling protocol over UDP.

After the establishment of the group call, the client 120, 122 and MCU complex 116 exchange useful information and signaling messages. In one embodiment, the transmission of useful information between the call participants and MCU complex 116 may be implemented using a transmission protocol in real time (RTP) over UDP. The signaling messages may also correspond to the signaling protocol over UDP. These protocols and they provide functions are described below.

Components

Group communication system 100 may include the IP endpoints, which contain the client software and regional and centralized server components required for providing group communication services. The group communication clients and the application server components are described in more detail in the following sections.

Customers

Client 120, 122 of the group communication can run on any end point IP, which has access to the appropriate vocoder (vocoders). IP endpoints may include applications running on a wireless system, such as cdma2000, an application development platform, such as binary runtime environment for wireless (BREW), and personal computers.

The client may include a software application that can be developed using BREW, and interfaces to software modem mobile station (MMS, MSM), which may be downloaded to the client that contains the BREW environment. BREW - a platform that allows developers to create applications that can run on client communication devices. BREW provides application developers with a layer of insulation, which allows to develop applications without having direct contact with the MMS software and software original equipment manufacturer (OEM, OEM). It allows you to quickly develop and improve the application regardless of the software MMC and / or VET. It also allows you to upload applications to any device containing environment BREW. 2, the client application 202, the group communication may be performed in parallel with other applications 204, 206, 208, 210. While these services may be provided directly through interfaces VET 212 and MMC 214, BREW provides isolation from modifications made by the application at these levels. This makes it possible to develop the VET 212 and MMC 214 separately from the applications 202, 204, 206, 208, 210 transmit data.

For the client to work effectively on a personal computer, a personal computer can provide access to a compatible vocoder, access to sound card drivers and connectivity over IP application servers.

The location server

In one embodiment, the location server (SP, LS) may accept and / or maintain user location information, such as IP-network layer address, the physical location of the user, such as longitude and latitude, and / or packet zone identifier data, i.e. system identifier are sent to live on a direct common channels which identifies opportunities PDSN, providing a packet data service to the sector. According to one embodiment SP may comprise a component that handles the client's registration and issuing the user location information to other applications, such as instant messaging service using a SIP interface.

The joint venture may include two functional elements, namely the regional positioning server 112 (RSP) and the reference server 104 Positioning (GSP). RLS 112 may be deployed in each region, and the HLS 104 may be centralized. Details regarding these items and their functions are described below.

The regional location server

RLS 112 may process the registration and maintain clients in his region. In one embodiment, RLS 112 is a standard SIP-based SP, with which the storage location information of the user. In order to maintain the registry entries, RLS 112 may check the expiration date, the field "expiration" for each registration. RSP allows deleting records, expired, and shall inform the Regional Manager of the CAP and delete records.

As discussed above, customers can carry out registration of IP, to inform the application server of its location. Customers can maintain their registration for the period of availability of group communication services. Customers can carry out the re-registration when changing the IP-address of the client and the approach of the expiry of the registration.

When a client is registered or re-registered, RLS 112 may notify this associated RD 114. This allows RD 114 to pre-load user data in preparation for a call request, thus reducing call setup time. RD 114 may cache the user's location information, eliminating the need for RD 114 to contact with the FPR to retrieve user location information during call setup.

RLS 112 may notify RD 114 in the case of updating a user's location or its removal from the FPR 112. This RLS 112 and RD 114 features the latest information about the users registered in the region.

RLS 112 may also periodically update HLS 104 location information registered users. Where the RSP 112 provides registration HLS 104 for a user who already has a valid registration in another region, CAP can resolve this conflict.

Reference location server

HLS 104 may process queries for user location information. In one embodiment, HLS 104 provides a SIP-based interface, to other applications, such as instant messaging application, may request the location information for a particular user.

If HLS 104 is a centralized component of CPR and servers communicate with him, the CAP can resolve conflicts related to multiple registrations in different regions for roaming users. HLS 104 may receive registration information from each RSP. If HLS 104 receives multiple registrations for the same user, the HLS 104 may keep the most recent registration and request removal of the outdated registration (s) of the user of the port. This in turn can lead to the removal of cached information for that user from RD 114 associated with the FPR, which contains outdated registration.

Controller

Manager can contribute to the call, specifying the location of users and assigning group calls a complex control module 116 useful information (MCU). Manager is a server component, which plays a crucial role in meeting the demand for "instant access." To ensure minimum call setup, the dispatcher may include two functional elements with similar structure and functionality, but have different deployment strategies. These two elements, regional dispatcher (RD) 114 and the reference manager (ML) 102, are described in detail in the following sections.

Regional Manager

RD 114 may be the initial point of contact for the call setup requests and requests for notification. RD 114 may pre-load user information when receiving instructions from RLS 112 that the user is logged. Together with the user information, RD 114 may cache information about group calls operating system currently. RD 114 may use the cached information for users and groups during call setup to keep the setup time at a minimum level of the call, i.e. It eliminates the need for a database search.

In one embodiment, the group information the RD stores in the cache includes the group member list and the address of the MCU complex 116 on which the group. RD 114 may maintain a list of members and the address of the MCU during the time of action call. This helps RD 114 quickly determine whether an incoming call request group definition, which is identical to the definition of a group having an associated call already active in the system, and it allows the RD to quickly respond to requests for call setup and confidently meet or reject the request on the transmission mode in response.

RD 114 may satisfy or reject the request for the transfer mode. RD 114 may decide whether to request MCU complex 116 to add the user to the call as a "joiner" participant or to start a new challenge with the corresponding list of members.

When a request to establish a call, RD 114 may use the cached user information to retrieve location information for the users specified in the call request. If you are unable to locate the user, RD 114 may request the ML 102 to determine the user's location. According to one embodiment, if the determined location of at least one or more target users, the RD 114 continues the call setup. After positioning purposes, RD 114 may decide to which MCU the call should be assigned. This determination may be based on the IP-addresses of users in the group, including the initiator.

RD 114 may handle requests for notification similarly to the call request. In one embodiment, a request for notification assigned local MCU complex 116 for processing, regardless of location purposes.

In one embodiment, the information in the RD's cache may be periodically written to a reliable means of data storage, so that it can be restored in case of failure. In the case of failover RD, information about users and groups, which was recorded on a reliable means of data storage, can be re-loaded into the cache, then the RD proceeds to check the cached information, together with the processing of the incoming call request.

In one embodiment, RD 114 loads the user data into local cache for each user registration notification from the FPR 112. By eliminating the need for the implementation of multiple searches in databases during call establishment, RD 114 significantly reduces the time required for testing and responding to call request or requests for notification.

RD 114 may access database 106 of users / groups during call setup to expand pre-defined group addresses, if present in the request, to lists of individual users and, if necessary, to convert alternate identifiers of users or groups, such as telephone numbers, conference ID, in the canonical address (abresa).

Reference Manager

Reference Manager (ML) 102 can monitor the location information registered users. ML can contain location information to users who have registered in advance with the help of RLS 112.

As discussed above, each RLS 112 may notify its associated RD 114 every time there is a registration, re-registration, cancellation of registration or expiry of registration of the user. RD 114 may use this information to load user information in its local cache, or its removal. Each RD 114 may update the ML 102 user location information. Since ML 102 receives updates from RD 114, the ML 114 can assist in finding users who are geographically dispersed across different regions. RD 114 may request assistance from OD 102, when it receives a request for a user who is not currently registered in the region, ie, It does not appear in the cache RD information about users.

DNS Server

In one embodiment, group communication system 100 may use the DNS server 124 the service provider to provide information about the location of RLS 112 and RD 114 to customers. This information may be configured upon each regional structure and updated to ensure its accuracy.

In one embodiment, each client learns the DNS server's address by matching Control Protocol Internet Protocol (IPCP) during session establishment Point to Point Protocol (PPP), when a client requests a packet data session. Thus, the DNS server 124 may be reported in this way for each region. This allows the client to move from region to region and communicate with DNS server 124 in the region where the client is located. DNS server 124 is deployed for each region, together with each PDSN. According to one embodiment, the DNS server 124 may be updated by each RD 124 and ATN, which serves the PDSN is associated with DNS server 124.

In one embodiment, the mechanism used to locate appropriate RD 114 and RLS 112 is based on a combination of DNS and SIP addressing. Search service record (SRV) DNS can be carried out in accordance with section «<domain>» («<domain>"), a unique resource identifier (URI) SIP, which is registered under the client. SRV record request may include the protocol or service that the requesting party is trying to find. For example, in case of attempting to locating RLS 112, the client may request a "registration service" in the DNS SRV record searching. DNS response may include one or more valid network and port addresses for the server, which offers the requested service. DNS server 124 may be used for load balancing between servers that offer the same service, allowing DNS server 124 to cycle between multiple server when returning answers to client requests.

Database users / groups

In one embodiment, the database 106 of users / groups is a central repository of information about users and groups. For each user, the database may include information such as user address, interrupt service rank, authentication information, user contact information, and lawful intercept flag, which indicates whether the user is under surveillance. The database may also include determining the pre-defined groups, which are the lists of users and the corresponding name of the group for the chat-room model of dispatch services. Each group may be uniquely identified, for example, location groups. The client may use the group address to identify the group in the request to establish a group call. RD 114 may use the group address to retrieve the corresponding membership list from the database 106 of users / groups, when it receives a request to establish a group call to a predetermined group therein.

The complex control module useful information

Complex control module useful information (MCU) may include hosts useful management information (HUPI, SIT) and the control unit of useful information (MCU). HUPI can assume the functions of the processing and administration of a number of processes the MCU. Each MCU may perform processing of signaling and useful information in real time for a particular call. The functions performed by the MCU to call, may include the following.

- Assignment process calls from RD 114.

- Sending information and load status HUPI.

- Sending information call origination customer.

- Signaling processing for the call from the customer, such as requests to switch between transmission and reception.

- Ensuring reliable delivery of signaling messages to customers.

- Duplication and dissemination of useful information in the call "from one to many."

- Providing useful information conversion using the appropriate transcoder for calls "one to many" to "mixed" vocoder.

- Monitoring call activity and initiating call termination based on inactivity transfer of useful information.

- Formation of the information used for the registration server 118 use (MNS).

- Transfer of useful and signaling information to the appropriate lawful intercept point on request.

The MCU can handle requests for notification from the RD 114, send a notice informing the customer and expect acknowledgments from clients. After receiving acknowledgments from the targets, the MCU releases any resources assigned to the transaction notice. At this time, the MCU may handle other call destination or requests notification.

Registration Server to use

MIS 118 may exist in every region and may be co-located with the MCU complex 116. HRE 118 can collect events on the use of the MCU complex 116 for each call or notice processing, format them to use the data record (DDA, UDR), and then saves the file in the sequence DDA DDA. DDA records for calls may contain information regarding individual calls including the list of participants and the use of the results to the participants. DDA for notification may contain information that indicates the initiator and target users notice that sent the notice. DDA files may be collected by the service provider for billing analysis, and may be removed after a certain period of time.

MIS 118 may write one DDA call instance on the end of each call. HRE 118 can also record a DDA each time the processing of a request for notification. DDA, MIS recorded 118 may contain the following information.

- Instance ID call or instance ID notification.

- MCU identifier, which also expresses the location of the call. At the beginning of a call, an appropriate MCU may be chosen based on the registered location of all the prospective participants. The MCU may or may not be located in the same region as the initiator.

- Time of the call or notification.

- Time of the call or the end of the notice.

- Name and / or ID of the initiating user.

- IP-address of the initiating user.

- For each participant: user name, user address, IP-address of the user, the total time of participation, which may be zero for notifications, and the total number of seconds during which the participant holds the transfer mode, which can be zero for notifications.

In one embodiment, for each call, it creates a separate DDA, which may represent the total collection of utterances during a call. If you need to register for the event through the DDA each speech fragment, it can be implemented at the expense of additional processing load, file I / O and disk space requirements.

Group communication system 100 performs several different functions for implementing multicast services. The options related to users, include registration, call origination, call termination, sending notices, acquisition, resolution of conflicts between the talker, adding users, exclusion of members, deregistration, addressing and authentication. Functions relating to the preparation and operation of the system include administration and provisioning hardware, scalability and reliability. These functions are described in detail in the following sections.

check in

In a wireless communication system such as code division multiple access (CDMA, CDMA), register - is the process by which the mobile station informs the wireless communication system infrastructure of its location. This location information may include the geographical area where the mobile station and identification data of the base station serving the mobile station, which can be used to promote more efficient use of the paging channels and access.

In one embodiment, the user location information is the IP-address of the client, regardless of whether the client is connected by means of wireless or wired communication. Illustrative of IP, allowing IP applications to locate clients based on their IP-addresses, a Session Initiation Protocol (SIP). Among other functions, SIP provides methods for clients to register their IP-addresses and other location information by using the server SIP. In addition, SIP provides IP applications, interested in "finding" clients, the method of requesting the same SIP server component for location information, such as IP-address of the client.

Registration may include the process, the client IP connection with a SIP server component to declare and maintain its location information, such as IP-addresses. SIP server component, which provides this feature is the location server. The method by which a client notifies the location server of its location or changes to its location, is a way of SIP REGISTER (registration method SIP).

In one embodiment, the clients register their location information using the regional location server. Other applications based on IP, such as instant messaging application, may use information about IP-address of each customer to the location server. Registration may be carried out by external service or the client. 3 illustrates an exemplary sequence of operations for registration function.

After powering up 302, the customer can request a packet data session and begin the process of registering your IP-address with the FPR 112. To register, the client can search 304 SRV records in the DNS to determine the address of the port. After removing the 306 addresses the FPR, the client may register its location information, e.g., using a SIP registration message 308. CPR may authenticate 310 the user and issue a response 312 to the client. CPR may notify 314 the regional dispatcher that the user is registered, and the regional dispatcher may use this information to pre-load the appropriate data record associated with the user, to help reduce the response time during call setup. At this point, the client can be accessed with an invitation to participate in the group call. In one embodiment, clients may need to perform registration for receiving a group call, regardless of their existing types of data connections, i.e. wireless or wired.

With the registration may be due to the "expiry", indicating how long the client's registration information may be considered valid. To ensure that the customer is always available over IP, the client can be aware of the expiry of its registration and re-registration exercise prior to expiry. Registrations may also become invalid or stale due to other circumstances, such as when changing the IP-address of the client or interruption of the transmission of data between the client and the location server. Customers can know the status of their ability to transfer data that has changed if their IP-address.

After completion of the initial registration, the client may allow its packet data session to go dormant mode, which may release the dedicated traffic channel. The client may monitor its packet data session to ensure that it remains valid during periods of extended inactivity. Conditions that may affect the validity of the session include moving to a different packet data zone identifier, fade or loss of service, and receiving and / or placing a call to a telephone network (PSTN, PSTN). IP-address of a client can change, and the client may be required to re-establish the connection to communicate with the infrastructure. When the client re-establishes its packet data session, it receives a new IP-address. The new IP-address to be transmitted to the location server to ensure the client's location information remains accurate. To this can be carried out re-registration.

Customer wireline communication with the location server through means of network protection (firewall), may need to pass through the firewall maintenance, periodically polling the location server. For this re-done.

Group Call Initiation

Upon completion of registration, the user may make or receive calls. Before you initiate the first call after power-up, the client can search the SRV record in DNS to find the location of the regional dispatcher. This can be done during start up.

"Group" is associated with the initiator, the user initiates a creation of the group and a list of terms containing the target user or users. The list of members may comprise one or more users, one or more pre-defined groups, or a combination of both. If the member list contains only one user, the call initiated using that member list is commonly referred to the private call. If the member list contains any pre-defined groups, the regional dispatcher may expand the pre-defined groups into a list of one or more target users, e.g., by replacing a predetermined group identifier in the original member list, the list of members associated with a predetermined group. After the expansion of pre-defined groups, the resulting member list may contain only target user names. At this point, the regional dispatcher attempts to locate the target users in the list of members, for example, by scanning the regional dispatcher cache containing user information. If the targets are in the regional dispatcher's cache, the members of the group may be registered in one region with the regional dispatcher. This type of group call is labeled as "intra" call. If you have users, the location of which the regional dispatcher is not able to determine the regional dispatcher may request assistance from the support manager to determine the location of users. The challenge associated with the group having members from two or more regions, known as "inter-regional" call.

After the regional dispatcher has determined whether the call is intra or inter-regional, it may start the process of determining which control module useful information (MCU) can assume the functions of call processing. For intra-regional calls, the regional dispatcher may assign the call to the MCU located in the same region as the regional dispatcher, if there are MCU resources available in that region. The resulting call using this type of call setup is called "locally hosted" call, or local call. For inter-regional calls, the regional dispatcher may optionally assign a call MCU in the same area or in a remote or the regions. The regional dispatcher may make this decision based on the information the user's location to find the optimal way of transferring IP-packet containing useful information and signaling. If most users are located in a particular region, the call may be assigned to the region. If the users are evenly distributed across regions, the call may be assigned to one of the regions containing the target users. If the inter-regional call is assigned to the MCU in the region other than the region in which the regional dispatcher, the call is referred to as "remotely hosted" or remote call. The Regional Manager may have information about the network topology and / or the possibility of communication between the MCU modules and serve them PDSN and can use this information to make more informed decisions on the call destination.

Intra calls

Group communication system 100 can be deployed so that the calls were mostly intra-regional. The intra-regional calls may eliminate the need for communication between regional dispatcher 114 and a reference manager 102 during call setup. The need for communication between the regions may also be excluded when the targets are in the same region and the call is handled locally, as in the case of intra-regional calls predominance. The following sections describe the sequence of operations of the call, the time characteristics and assessment scheme for intra-messaging call.

Local Call Initiation

4 shows an exemplary diagram of the messaging occurring at the beginning of a local group call. The user may select 402 one or more target users, one or more pre-defined groups, or a combination of both and can press switch between transmission and reception (PTT). The client may send a request 404 to the regional dispatcher to establish a group call, regardless of whether the mobile station has a dedicated traffic channel that will be described in more detail below. After sending the request, if the packet data session is inactive, the client may initiate the process of re-establishing dedicated traffic channels and preparing the packet data session to an active transfer of information. The client may buffer speech input received from the originator for some period of time.

When the regional dispatcher receives the request, it may expand the pre-defined groups, which may be specified in the request, to lists of members to the target users. Then, the regional dispatcher may retrieve 406 the target users' location information. At this point, the regional dispatcher may also determine whether the group is already in the system. 4 shows a scenario in which the group has not yet valid. Scenario join the call, described below, illustrates a case where the group already operates.

Determining the location of at least one of the target users, the regional dispatcher may send a response 408 back to the client indicating that the group call is established. The client may suit optimistic 410 initiator request to talk and start buffering 412 his useful information.

The regional dispatcher may use the locations of target users to determine the region in which the call may be placed. If it is determined that the target users are in the same region as the regional dispatcher, as shown in Figure 4, the regional dispatcher may assign the call to regional MCU. The MCU may send the entire group classified 414 of the beginning of the call. In order to target users, sending ads can condition the output of packet data sessions from the sleep state and re-establish their traffic channels.

After the client will take the announcement of a call by the MCU, and a traffic channel of the mobile station will be re-established, the client may send 416 buffered useful information on the MCU. The MCU may buffer 418 the useful information received from the initiator. In one embodiment, the MCU may buffer the useful information before it is reached or exceeded "target response threshold". Threshold response target indicates the target number of responses needed to go to the sending of information. The threshold may be adjustable parameter. Upon reaching the threshold, the MCU replicates and forwards 420 useful information to target users who responded 422 to the announcement of the call.

Messaging via short data burst

"Immediate response" corresponds to the response time, which is necessary for the application server response to a request to switch between transmission and reception, or call request. The object in response to any request to switch between transmission and reception, including a request for establishing a group call, the uniformity of response is a request for a predetermined period of time, for example one second or less. In many cases, when a user requests the establishment of a group call, the packet data session a user is idle, and there is no dedicated traffic channels. Re-establishing dedicated traffic channels may take considerable time. Therefore, an application server can use other means.

To ensure that the group communication system provides the "instant response" can send short-IP datagram at any time in either direction, i.e. originating from a mobile device or coming to mobile devices regardless of the state of the packet data session. In one embodiment, IP-datagrams can be sent as short data burst message (SDB). When the packet data session is in dormant mode, SDB message will be transmitted on overhead channels. If possible communication via the dedicated traffic channel SDB message is transmitted on the traffic channel.

4, a request 404 to establish a group call can be sent via SDB messages. Response 408 to a request to establish a group call from the application server may also be sent via SDB messages. Posts a request to establish a call and answer transmitted via SDB messages, may allow a group communication system 100 to solve the problem of "instant response".

To complete the process of establishing a group call, the MCU may send out ads about the call users from the list of members, including the initiator. These ads call can be transmitted on the dedicated traffic channels. In most cases, the packet data sessions are inactive members of the group, i.e. dedicated traffic channels have not been established. This means that the MCU may need to re-send a message to the ad call for schedule reliability persevering until they are re-established traffic channels of all members, and the members do not confirm receipt of the message or the timer expires reliability. Sending a call to the announcement of persistent manner ensures that the buffers of useful information on the client and the MCU are at a minimum. The client may send buffered useful information as soon as it is established traffic channel, and he accepts the announcement of the call containing MCU contact information. The MCU can duplicate and forward buffered useful information immediately after reaching or exceeding the threshold response goals. This means that the faster objectives take the announcement of the call and respond to it, the faster can be reached this threshold, and the faster the MCU may stop buffering and start sending useful information.

Announcement of the call initiator can also be sent via SDB. This has two advantages. Firstly, as an advertisement for the call contains the contact information MCU client group call may start sending buffered payload to the MCU as soon re-established traffic channel of the mobile station, which may weaken the requirements for RAM in the mobile station for storing the buffered payload. Secondly, if the initiator decides to abort the call and exit the transmission, which may occur to re-establish the traffic channel when an advertisement for the call comes in the form of SDB, the client may notify the MCU through this information. Sending ads call initiator via SDB increases the load on the common channels and requires special treatment MCU posts ads about the call initiator.

Initiate a remote call

The intra-regional calls may be placed locally if all members are located in the same region. The regional dispatcher may assign the call intra remote region, if local resources are overloaded or unavailable. In such cases, the payload and signaling system may be subject to additional delays and errors due to elongation of communication lines between the user's PDSN and the remote MCU. 5 illustrates an exemplary call setup for a remote intra-regional call.

Initiation of intra-call on a remote host is similar to the call setup scenario considered in connection with Figure 4, with the exception of call destination MCU regional manager. After regional dispatcher extracted location of group members, it may determine the MCU to which the call may be assigned. The regional dispatcher may make this decision based on the location information of users, load and availability of the MCU modules. When intra-call users may be in the same region, therefore the regional dispatcher can monitor the workload and availability of the MCU complex in the local region. If the regional dispatcher receives an indication that the local MCU complex is overloaded or temporarily experiencing malfunctions, it may assign the call to the remote MCU. In one embodiment, the MCU modules may be duplicated with identical features except the call configuration; therefore, the remote MCU may handle the call similar to the local MCU.

Interregional calls

Group communication system 100 can be constructed so that the user can communicate with any other user regardless of their physical location or distance from each other. Group communication system 100 may be deployed so as to limit the number of calls that are inter-regional, because the inter-regional calls require communication between the regional dispatcher and the dispatcher reference during call setup. The call may be assigned to the MCU that is in a remote region with respect to one or more of the call participants. The following sections describe exemplary call flow sequence, assessment and temporal characteristics of the message exchange pattern for the inter-regional calls.

Local Call Initiation

6 shows an exemplary exchange of messages in order to initiate locally hosted group call. Call setup for a local inter-regional call is similar to call setup for a local call intra described in connection with Figure 4, except for the process in which the regional dispatcher retrieves the location information for the target users. In one embodiment, the regional dispatcher attempts to locate the target users in its cache. If some users are not found in the cache, the regional dispatcher may request the assistance of the support manager to determine the location of users. Reference Manager can contain location information for the user who carried out the IP-registration using the regional location server. As discussed above, the regional location server may notify its associated regional dispatcher every time a user registration occurs. Each regional dispatcher may notify the manager of the support user registration. This allows the support manager to assist the regional dispatchers to locate users, separated geographically across different regions.

Initiate a remote call

Figure 7 illustrates an exemplary remote interregional call establishment. Initiation of inter-regional call on a remote host is similar to the call setup scenario, as described in connection with Figure 4, except for the call destination MCU regional dispatcher. After regional dispatcher (RD) 114 retrieves the location information of the group members, it may determine the MCU to which the call may be assigned. RD 114 may make this decision based on the location information of users, load and availability of the MCU modules. Using the location of group members, the RD attempts to find an optimal way to transfer IP-packet containing useful information and signaling over the network service provider for the majority of the members. If many users are in a particular region, the call may be assigned to that region. If the users are evenly distributed across regions, the call may be assigned to one of the regions containing the target users.

Group Call Completion

A group call may end for two reasons: either all participants have requested a way out of the call or all participants have stopped talking for a predetermined period of time, called "hang time". Each participant can optionally participate in a call to terminate before the scheduled end of the call. If all the participants out of the call, the MCU may terminate the call and release all resources assigned to it. If all participants except one, out of the call, the MCU may notify the participant, referred to as the "single user". Single user has the option to immediately withdraw from the call, or wait until the timer expires hang time, which could initiate a call to reset the MCU module.

MCU may terminate the call after the timer time hovering. The MCU may track each talk segment and set a timer upon completion of the segment of conversation. This timer is referred to as the "hang-time timer" and can track the duration of silence, ie lack of conversation or activity on the transfer of useful information during the call. If the call takes place during the silent time freezes, which can be adjusted by the service provider, the MCU may assume the participants are no longer interested in the call, and so complete the call.

Ending a call initiated by the user

8 illustrates an exemplary scenario in which a user has decided to terminate participation in the group call. This scenario indicates the sequence of message exchange for the termination of the participation of the user. When the user 802 decides to terminate participation in the group call, the client may send 804 a request to the MCU module is removed the user from the call. MCU may remove 806 user's call and notify 808 the client that the user is deleted 810.

Ending a call initiated by the server

9 shows an exemplary sequence of messaging that is implemented when the hang-time timer expires and the MCU terminates the group call. After a 902 hang-time timer, the MCU may send 904 the participants a notification of the completion of the call. Each client, who took notice of the completion of the call can be answered by the 906 acknowledgment. Having acknowledgment, the MCU may notify 908 the RD about the end of the call and free the resources assigned to the call.

Sending notices

Notification mechanism can be used to notify target users that another user, the initiator of the notice, expressed a desire in their participation in the group call. The mechanism of the notice may contain a text message that allows the originator to specify the subject call, the desired time of the call, or any other text message on the user's choice. 10 shows an exemplary sequence of messaging that occurs when a user sends a notification.

The initiator 1002 may select one or more target users, one or more pre-defined groups, or a combination of both, and may specify the notification to be sent. The client may send 1004 a request to regional manager mail notification target users specified in the request. When the RD receives 1006 the request, it may expand the pre-defined groups specified in the request, to lists of members to the target users and the RD may retrieve the target users' location information. Determining the location of at least one of the target users, the RD may send a response 1008 back to the client. RD may assign 1010 MCU a request for notification to send messages to target users in 1012 notices.

10, the request for notification can be sent via short data burst (SDB). Sending notifications via SDB messages allows you to leave the packet data sessions in which the parties involved in the sleep mode. Notification of the notice contains the necessary information to target users could set group calls with the initiator and with the rest of the target users, for example, by a notice in the form of notification and pressing PTT. When this happens, the establishment of a group call is similar to the call setup scenario discussed in connection with Figure 4.

Joining

A call request is regarded as attachment, if it is determined that the member list, which may be specified in the call request is identical to the list associated with a call already running in the system. This situation can occur in two cases. Firstly, the user may create a member list identical to one that already has a call is connected, for example, by exactly the same user (s) and / or group (s) and pressing PTT. Second, the user can select the call is still running in the system, from the call history list and press the PTT. In any case, the RD may determine the call, initiation of which the user has requested, already in progress, and qualify the user as a joiner.

11 shows an exemplary case of joining in which the user may select a call from the call history list. The user may select 1102 a call from the call history list and press the PTT. The client may send 1104 a request to initiate a regional manager of the group call. RD may determine the call is already running 1106 and send a response 1108 to the client that the user is added to the existing call. If a call is in progress, then the transmission mode may not be available to the user, as the current call participant may already hold the transmission mode while the user is joining preparing to receive useful information, ie packet data session is derived from a sleep mode. RD may request 1110 the MCU that hosts a call to add the user to the group of joining. MCU adds the user and sends the user 1112 ads containing MCU contact information. After re-establishing the traffic channel by joining the flow of useful information in the call can be transferred to the user. At this time, the joining user may attempt to request the privilege to talk.

The scenario is similar to the scenario of accession of the new group call initiation, considered in connection with Figure 4. The distinguishing feature is that the joining member is rejected in the transmit mode in response to the original request for establishing a group call.

Resolving conflicts between speakers

In one embodiment, each group call user is assigned a grade of service interruption, which determines the level of rights the user has when requesting privileges to switch to the transmission and the beginning of the call. After establishing the group call, the MCU may be responsible for the transition to the mode of transmission and determine whether you can afford to talk party requesting the transfer mode. The MCU can implement conflict resolution (arbitration) between the talker, when two or more call participants are competing for the transmission mode for a particular group.

12 shows exemplary events that may occur in the process of resolving the conflict. Conflict resolution scheme used in this scenario provides an interrupt service user B when user A requests the transmission mode. User B is in the transmit mode, i.e. The user tells the user A requests permission to talk by pressing 1202 the PTT. The client may send 1204 a message to the MCU requesting permission to talk. The MCU can implement the resolution of the conflict between talker 1206, and to determine what can be interrupted by service in the user and enable the user to switch to A mode of transmission. In order to ensure a break in the transfer of useful information, i.e. that the user B may stop talking before transmission of useful information of user A, the MCU first sends 1208 a message to the client for user B, indicating that the transmission mode is intercepted by another user, and then sends a response 1210 with a mode of transmission to the user A.

Adding members to an active group call

Group communication system 100 allows a group call participant to add new users to the existing group call. For this call participant selecting one or more target users, one or more pre-defined groups, or a combination of the two, and indicating that the participant would like to add the target to the group call in which the user is currently located. 13 shows what happens when you add new targets to the existing group call. Call participant may select 302 one or more target users, one or more groups, or a combination of both, to be added to the call. The client may send 1304 a message to the RD requesting the addition of these target users to the existing group call, which can be specified in the request. When the RD receives the request, it may expand the pre-defined groups specified in the request, to lists of members to the target users. Then, the RD may retrieve 1306 the target users' location information. Determining the location of at least one of the target users, the RD may send a response 1308 to the client indicating that the targets are added to the call. RD may send 1310 a request to the MCU module add the specified users to the call. The MCU may send 1312 call announce new targets that can initiate the process of withdrawal of its packet data sessions from the sleep mode. Ads can be sent on a reliable schedule, to ensure that the goals will take a message. After re-establishing traffic channels objectives, targets may send 1314 acknowledgments to the MCU. Additional targets may be included 1316 in the transmission of useful information, and signaling that takes place during the call.

Excluding members of the active group call

Group communication system 100 allows a group call party remove members from an active group. In one embodiment, this calling party selects one or more target participants and indicating that they should be excluded from the group call. 14 shows the exemplary events that may occur under exclusion of participants perform group call. Group call participant may select 1402 one or more target participants to be excluded from the call. The client may send 1404 a message to the RD requesting exemption purposes as may be specified in the message, the group call. Accepting the request, the RD may retrieve 1406 the location information purposes and send a response 1408 to the client, indicating that the deletion is performed purposes. RD may send 1410 a request to the MCU module except for the purposes of the call. The MCU may send 1412 messages goals that can be specified in the request for an exception indicating that performed their exclusion from the call. Targets can send confirmation to the 1414 MCU.

Cancel registration

If a user no longer wishes to communicate with the application server or any other application IP, which uses the user IP-address to contact the user, may be a function of de-registration. Undo registration removes user IP-address and other contact information of the CPR and frees any resources allocated on behalf of the user. Figure 15 shows how the registration of the user is removed from the FPR resulting power off the mobile station, according to one embodiment. The client may receive 1502 an indication that the mobile station on which the client is situated, is switched off. During shutdown, the client may send 1504 a message to the FPR, indicating that the user's location information should be removed. CPR may authenticate 1506 the request to make sure that it comes from a reliable source. After successful authentication, the FPR 1508 client may notify the successful completion of the operation and notify 1510 the RD about the removal of the user. RD may remove the user's data records from its cache and may free the resources that could be allocated to the user. Failing deregistration location information may eventually be removed from the FPR after the time associated with the expiry field.

In one embodiment, group communication system 100 supports both the chat-room model and the special model. In the chat-room model, the groups are pre-defined, which may be stored on the dispatch server. Pre-defined groups can be public, which means that the group has an open member list, ie Any user scheduling is a potential participant. In the chat-room model, the call is started when the first person chooses to join the chat-room, and the call continues, the server resources are allocated call, regardless of the voice activity for a predetermined period of time, which can be controlled by the service provider. Members specially requesting adherence to these types of calls, and out of them. During periods of no speech activity, each call becomes inactive group, which will be discussed below, until the user requests permission to talk.

In a special model, groups may be defined in real-time, associated with them closed membership lists. Private member list may specify which users are permitted to participate in the group may not be available to users outside of the closed member list, and may only exist for the call. The definitions of ad hoc groups can not be stored anywhere; they can be used for call setup and release at the end of the call.

Ad hoc group may be formed when the originating user selects one or more target users and generates a request to initiate a call that is sent to the server. The target users may be sent a notification that they are included in a group and may automatically join the appropriate calls, i.e. no user action is required. As a special challenge becomes inactive, the application servers can "break" the call and free the associated resources, including the task group that is used to start the call.

When working according to the chat-room model, in the group communication system 100, a group of users of communication devices, each of which is individually known as grid members, communicate with one another using a communication device assigned to each member of the grid. The term "grid" refers to a group of users of communication devices authorized to liaise with each other.

In one embodiment, a central database may contain information identifying the members of each particular net. The audio communication system can operate more than one grid. For instance, a first net may be defined as having ten members and a second net may be defined as having twenty members. Ten members of the first network can communicate with each other but can not communicate with the members of the second grid. In another embodiment, members of different nets are able to monitor communications between members of more than one net, but may only transmit information to members within their own net.

The grid may operate over an existing communications system, without requiring substantial changes to the existing infrastructure. Thus, a controller and users in the network may operate in any system capable of transmitting and receiving packet information using Internet protocol (IP), such as a multiple access, code-division multiplexing (CDMA, CDMA), multiple access with time division multiplexing (TDMA, TDMA), Global System for Mobile Communications (GSM), satellite communication system such as Globalstar ™ or Iridium ™, or a variety of other systems.

Grid members may communicate with each other using the assigned communication device, shown as communication devices (DC, CD) 120 and 122. The FF 120 and devices 122 may be wired or wireless, such as terrestrial wireless telephones, wireline telephones, adapted to switch between transmission and reception, satellite phones equipped with a function to switch between transmit and receive digital video cameras with wireless communication capabilities, cameras, audio devices, such as tape recorders or players, laptop or desktop computers, pagers or any combination thereof. For example, CS 120 may comprise a wireless terrestrial telephone having a video camera and display. Furthermore, each CD may be able to send and receive information in either a secure mode, or a non-secure (clear) mode. In the following discussion, reference to a separate CSS involves wireless phone switching between transmission and reception. It should be understood here that it is not intended that the reference to DC is not itself restrictive and may encompass other communication devices adapted to transmit and receive packet information in accordance with the Internet Protocol (IP).

The group communication system 100, the transmission of privilege generally allows a single user to transmit information to other members of the grid at a given time. Transmission privilege to the requesting member provide the grid or deny it depending on whether to designate the currently privilege to another member of the transmission grid, upon receiving a request. The process of satisfaction and rejecting requests to transfer known as conflict resolution. Tiebreaker involve evaluating factors such as priority levels assigned to each CM, the number of unsuccessful attempts to gain the privilege of transmission time interval, during which a grid has the privilege to transfer, or other factors, in determining whether a given if a privilege to transmit requesting members of the network.

To participate in the system 100, each of the DC devices 120 and 122 may be adapted to requesting the transmission privilege from a controller or MCU 116. MCU 116 may manage the real-time operation and administrative operations on groups. The MCU is any type of computer device having at least one processor and memory. MCU 116 may operate remotely through a communication system service provider, members, or all together, assuming that the credentials provided by the service provider. MCU 116 may receive group definitions through an external administration interface. Group members may request administrative actions through their service provider, or administrative functions at predetermined grid system, such as a security manager (MB, SM), operated by the user, which is consistent with the administrative interface MCU. MCU 116 may authenticate the parties trying to create or modify a net.

MB can perform key management, user authentication and related functions to support secure nets. Separate the group communication system may interact with one or more MB. MB can not participate in managing the grid in real time, including the activation of a network or conflict resolution switch between transmission and reception. MB may have administration capabilities compatible with MCU interface to automate administration functions. IB may also be configured to operate as an endpoint for data transmission in order to participate in the network, broadcast keys or simple grid mesh traffic monitoring.

In one embodiment, the means for requesting the transmission privilege from MCU comprises a key or switch between reception and transmission (PTT). When a user in the system 100 desires to transmit information to other members, the user may press the PTT box at its CSS, and thus send a control request to obtain the transmission privilege from MCU 116. If no other member currently not assigned privilege transmission, the requesting user may be granted the privilege to transmit what the user can be notified by an audible, visual or tactile signal means CM. After the requesting user the privilege to transmit information can be transmitted from that user to the other members.

According to one embodiment of the present invention, each wireless mesh member establishes a forward link and a reverse link with one or more base stations 126, or alternatively with a satellite gateway, as appropriate. Speech and / or data may be converted into data packets, for example, using DC, which are suitable for a particular distributed network 128 through which communications can be carried out with other users. In one embodiment, distributed network 128 is the Internet.

According to one embodiment of the forward dedicated channel is established in each communication system, i.e. a terrestrial communication system and a satellite communication system, for broadcasting information from each member of the other members of the mesh grid. Each member of the grid can receive transmissions from other members of the grid on a dedicated channel. In another embodiment, a dedicated reverse link is established in each communication system for transmitting information to MCU 116. In one embodiment, one can use a combination of the above diagrams. For example, a scheme may involve establishing a dedicated forward broadcast channel but requires the wireless communication device to transmit information to MCU 116 over a dedicated reverse link assigned to each CSS.

When the first mesh member wishes to transmit information to other members of the grid, the first grid member requests the transmission privilege by pressing his PTT CSS, which generates a request formatted for transmission over the distributed network 128. In the case of FF 120 and 122, the request may be transmitted over the air on one or more base stations 126. A mobile switching center (MSC, MSC) 130, which may include a well-known functional element interworking (FMSV, IWF), packet data serving node (PDSN) or a functional control transmission of packets (PCF PCF) for processing data packets that can be placed between the BS 126 and the distributed network 128. The request may be transmitted via the public switched telephone network (PSTN) to a bank of modems that can receive the request and to provide its distribution network 128. The terminal can monitor the traffic of 100 through its connection to distributed network 128.

If no other member currently has no privilege to transmit when the MCU 116 receives a request for the transmission privilege, MCU 116 may transmit a message to the requesting net member, notifying it to the transmission privilege grant. Audio, visual, or other information from the first term of the grid can then be transferred to other grid members by sending the information to MCU 116, using one of the above-described transmission paths. In one embodiment, MCU 116 then provides the information to other members of the grid by duplicating the information and sending each copy to other members of the network. If you are using a broadcast channel, the information needed to duplicate only once for each broadcast channel used.

According to an alternative embodiment, MCU 116 is embedded in the MSC 130 so that data packets from supporting base stations are routed directly to MCU 116 without routing the distributed network 128. According to this embodiment, MCU 116 is still connected to distributed network 128 so that other systems and communication devices to participate in the group communication. According to another embodiment of the MCU 116 may be incorporated into the PDSN or the PCF modules of the MSC 130 composition.

In one embodiment, MCU 116 maintains one or more databases for processing data relating to individual members of the grid, as well as to each defined net. For example, for each member of the grid, the database may include information such as user name, account number, telephone number associated with the DC term, the identification number of the mobile device associated with the CM, the current status of the member in the grid, indicating, for example on the is involved if the member is active in the grid, priority code for determining how to assign privileges to the transfer, the phone number for the data associated with the CS, IP-address associated with CSS, and indication with any mesh member is authorized to carry out Us. Other related types of information may also be stored in a database for each member of the grid.

According to one embodiment of the CD may form connections with individual communication terminals to form a negotiation group or mesh. The MCU may comprise a variety of functional capabilities, implemented in hardware and software that can be configured differently in accordance with different applications. The MCU may be configured to control operations of a real-time, administrative operations and authentication against meshes conflict resolution requests to switch between reception and transmission, maintenance and distribution lists members of grids and lists registration, establishing and breaking call for required communications sessions, e.g. CDMA system and network resources, as well as general status management networks.

Grids can be placed in the autonomous deployable cellular system, or may be a larger configuration of a plurality of sites. In the case of a large configuration, a lot of the MCU can be deployed geographically to form a single unified system, each acts as a module connected to the existing cellular infrastructure. Therefore, the new functionality provided by grids, available to users of mobile communication without the need for modifications to existing cellular infrastructure.

MCU may maintain a list of defined nets. In one embodiment, each definition grid mesh contains an identifier, a list of members, including phone numbers or other identifying information, user priority information, and other general administration information. Nets may be statically defined as either clear or both secure, and transitions between clear and secure may not be permitted. Secure mesh normally uses encryption of useful information to provide authentication and protection against eavesdropping. Encryption is useful information for secure nets is implemented on the cross-cutting principle; Encryption and decryption may be implemented in a communication device. The MCU may operate without knowledge of algorithms, keys or security policies.

Figure 16 illustrates an exemplary group 1600 for showing how the device 1602, 1604 and 1606 interact with a MCU communication 1608. Many MCU may be deployed as desired for large groups. According to CSS 16 1602 it has permission to transmit useful information to other members of the group. In this case, DC 1602 is called talker and transmits the useful information on the channel. When the DC 1602 is designated as the talker, the remaining participants, CS 1604 and CS 1604 can not have the permission to transmit useful information to the group. Accordingly, the DC 1604 and the DC 1606 are designated as a listener.

As described above, CM 1602, 1604 and 1606 are connected to MCU 1608, using at least one channel. In one embodiment, the channel is divided into separate channels comprising a channel 1610 Session Initiation Protocol (SIP), the signaling channel 1612 and payload 1614 traffic channel payload. SIP channel 1610 and a channel 1612 signaling payload may be used at any moment, when the bandwidth allows by any of the CM 1602, 1604 and 1606 regardless of whether it is designated as the talker or a listener. SIP is an application layer protocol, approved by the troubled Internet Engineering Task Force (IETF), which describes the control mechanisms for establishing, modifying and terminating multimedia sessions over the functioning of the Internet Protocol (IP). SIP provides a general solution to call-signaling problems for Internet telephony applications by supporting mechanisms for the registration and user location, the mechanisms that define the user experience and describe the options of useful information, and mechanisms for determining the availability of users call setup and call.

In one embodiment, SIP channel 1610 is used to initiate and end participation in a group CM 1600. SIP channel 1610 may be used as a signal session description protocol (SDP). When configuring CM participate in the group, for example, by using SIP channel 1610, the call control takes place in real-time signaling between CD and the MCU, for example by using the signaling channel 1612 payload SPM. In one embodiment, channel 1612 signaling useful information used to process and mode switching between transmission and reception deallocating resources, resolving conflicts between requests transmission mode, offers the beginning and end of information transmission, manage a sleep mode mesh track connectivity of endpoints requesting the status of the grid and the exchange of information on the status of the grid, and notice by any error messages. Protocol signaling channel 1612 minimizes the length of the payload of most common messages, and simplifies the task of interpreting replies and responding to requests while maintaining flexibility for future enhancements. The protocol signaling channel 1612 also allows useful information to re-send, without adversely affecting the status of the protocol.

In one embodiment, signaling traffic on the channel 1612 signaling useful information comprises signaling call setup and call control, which may consist of requests and acknowledgments invitation to the session, and signaling useful information which may include requests transmission mode in real time and the corresponding asynchronous messages . Traffic payload traffic channel 1614 may comprise useful information broadcast voice and / or data in real-time point-to-multipoint. Both categories of messaging have unique functional attributes. Furthermore, each CD may issue a client queries the Domain Name Service (DNS) to facilitate mapping fully qualified DNS hostnames to Internet network addresses.

In one embodiment, the signaling call setup and call control is performed according to SIP semantics. Although SIP may be transported using either the well-known User Datagram Protocol (UDP), a Transmission Control Protocol (TCP), in one embodiment, each CM performs functions based on SIP signaling using UDP. Also, each VTS may expect to receive SIP signaling requests via UDP. Signaling in real time can be performed through a dynamic interface UDP / IP to each CM and WM. Other signaling may be performed via a fixed TCP / IP interface between the CM and WM, e.g., using SIP.

Delay in the transmission mode

According to one embodiment, when the packet data service is active, resources in the infrastructure, such as base transceiver subsystem (BTS, BTS), base station controller (BSC, BSC), a functional element of interconnection (FMSV) and radio link, actively assigned the mobile station (MS, MS). In VoIP dispatch service based IP, while that between group members extends active call, a packet data connection for each user remains active. However, after a period of inactivity, i.e. "Hang time" in the group communication, user communication channels may move into an inactive state.

The transition to an inactive state retains the capacity of the system, reduces maintenance costs and wastage of the batteries and allows the user to receive incoming conventional voice calls. For example, when the user is in an active packet data call, it is generally considered "busy" to incoming voice calls. If the user packet data call is in the idle mode, the user is able to receive incoming voice calls. For these reasons, it is desirable that a packet data call transitions to a dormant state after periods of inactivity packet data.

At the time when packet data calls are active, even if no exchange of data packets occurs, cellular phones can still transmit radio frequency energy, albeit at a low level, to maintain synchronization and power control with the base station. These transmissions may cause a considerable wastage of energy in the phone. However, in the sleep mode, the phone may not perform any RF transmission. To save energy and prolong the phone battery life power, hang time can be configured to transfer the phone to the sleep mode after extended periods of non-transmission of data.

While, as the packet data service is active for all users, requests to switch between reception and transmission, which may be IP datagrams, transmission between the MS and the dispatch server, have very low latency. However, if the user channels have previously been transferred to an inactive state, the delay in transmission mode transition can be significantly longer. During the inactivity of packet data can be supported by the state information associated with the packet data session, including the IP-address of the mobile device. However it is possible to release the state information associated with layers below PPP, such as physical traffic levels and / or cancel the selection.

In some infrastructures, to output connections from a sleep mode needs reisolated traffic channel re-assign resources and re-initialize the radio link protocol layer (RLP). As a result, after the leading talk group has not talked for a while, when a user presses a PTT switch to request transmission mode, delay the transition to the transmission mode for the first segment of conversation is usually considerably longer than for subsequent talk segments. Although this effect might be relatively infrequent, it can affect the quality of service, and should be minimized.

To reduce the transition delay transmission mode in accordance with one embodiment, the signaling of the group call, in particular the control request, replies to requests transmission mode and messages output from a sleep mode, it may be transmitted on some available common channels, without waiting for re-establishing dedicated traffic channels. Such common channels may be always available, regardless of the mobile device and may not need to seek and remapping whenever the user wishes to initiate a group call. Therefore official exchange group call signaling may occur even when the mobile device is in sleep mode, which can provide a means of re-establishing dedicated traffic channels for mobile subscribers speaker and the listener simultaneously.

In one embodiment, the calling wireless device may send a control request on some of wireless infrastructure available common channels, such as reverse access channel and reverse enhanced access channel. The calling wireless device may also receive a response to the request transmission mode available on some direct common channels, such as direct paging channel and forward common control channel. According to one embodiment it is in the inactive state the mobile device listening subscribers can receive messages output from the inactive state to some accessible to direct common channels, such as direct paging channel and forward common control channel.

Call signaling messages as short data bursts

In one embodiment, a significant reduction in the actual total time of exit from the sleep mode and the delay switch to transmission mode, the perceived talker, may be achieved by using messages in short data bursts (SDB), provided, for example, the standard «TIA / EIA / IS -2000 Standarts for cdma2000 Spread Spectrum Systems », hereinafter referred to as" standard cdma2000 ». In one embodiment, the messages SDB can send both dedicated physical channels, such as forward fundamental channel (FCH) or forward dedicated common control channel (F-DCCH), and in general physical channels, such as reverse access channel (R-ACH), reverse enhanced access channel (R-EACH), forward common control channel (F-CCCH), or paging channel (PCH). Messaging SDB can be carried out in accordance with the packet radio protocol (RBP), which displays messages to the appropriate and available physical layer channel. Because SDB messages may carry arbitrary IP-traffic and may be sent on common physical channels, SDB messages provide a mechanism to exchange group call overhead signaling where the mobile device the caller has no dedicated traffic channels.

Call signaling messages from mobile devices

In one embodiment, the signaling message payload may carry IP datagrams over the reverse-link or link with the mobile device. A client mobile station may signal the MCU quickly whenever the user requests the transmission mode, and a reverse dedicated traffic channel is not immediately available. Assuming the client mobile station has released all dedicated traffic channels, the client mobile station may immediately forward control request over a reverse common channel of a wireless infrastructure, which may relay the request to the MCU. For example, either the reverse access channel or the reverse enhanced access channel may be used to send such messages when a dedicated reverse channel is not available. In one embodiment, the client mobile station may transmit a request message transmission mode to the MCU as an SDB message.

4, the one embodiment provides that the client MS may send a request 404 over a reverse transmission mode common channel, such as the access channel or enhanced access channel, before attempting to re-establish its dedicated traffic channel. In one embodiment, the client MS may send a request 404, a transmission mode in SDB message regardless of what channel is used.

Then, the client MS may start re-establishing its dedicated traffic channel, for example, performing "reorganizing service option 33". The client MS may also start radio link synchronization protocol (RLP). In one embodiment, the client MS may re-establish its dedicated traffic channel and synchronize RLP while sending the transmission request mode 404, which is an advantage.

Therefore, use of the available reverse common channels and / or SDB feature to signal requests transfer mode WM when the mobile station does not have active dedicated traffic channels, reduces the total time required for outputting the participating mobile devices from the sleep state. Although the talker client may not take the confirmation of meeting its control request until re-established a direct channel traffic talker, able to quickly signal SUS begin withdrawing involved listening subscribers of inactivity reduces the overall delay.

4, the wireless infrastructure may send a request 404 to the transmission mode of the packet data serving node (PDSN) and then to the MCU. In one embodiment, taking control request, the MCU may arbitrate the query, send messages activation signaling useful information (drive signals) to a group of target participants (listeners subscribers) and / or launch a re-establishing traffic channels 414 participants (listeners subscribers). If the MCU grants the request transmission mode, the MCU may send 408 the provision of the transmission mode to the client MS. In one embodiment, the RD may send a transmission mode giving 408 to the client MS on an available forward common channel, such as forward link paging and forward common control channel, if the client's dedicated traffic channel is not yet installed. In one embodiment, the infrastructure may send 408 to provide the transmission mode to the client MS in SDB form regardless of what channel is used.

In one embodiment, the MCU may wait timer expires response sleep mode before responding to a request transmission mode. If the response timer Sleep group set to zero, the WM can immediately respond to the request transmission mode. According to one embodiment, if the client MS has completed re-establishing its traffic channel and RLP synchronization, the client MS may sequentially transmit useful information to MCU 416, which could be buffered at the client 412 MS.

Call signaling message from network

In one embodiment, taking control request, the MCU may send the activation message payload signal group of target participants (listeners subscribers) and start re-establishing traffic channels participants (listeners subscribers). If the response timer Sleep group set to zero, the MCU may respond immediately to the request transmission mode. According to one embodiment, if a speaker began re-establishing its traffic channel immediately after sending the request to switch between transmission and reception, the channels causing traffic and listening subscribers can reinstall the same time, which is an advantage.

Referring to Figure 4, taking control request, the MCU may send 414 the activation trigger signals addressed to the target users. The MCU may determine whether the packet data session for a target mobile device and sends a trigger packet to the appropriate infrastructure element, such as a base station. Infrastructure can perform paging with respect to each individual target MS to start re-establishing its dedicated traffic channel. The target MS may start re-establishing its dedicated traffic channel, for example, carrying out "the reorganization of 33 service options." The target MS may also start radio link synchronization protocol (RLP). In one embodiment, the target MS may re-establish their dedicated traffic channels and synchronize their RLP in parallel with the same functions performed by the client MS, which is an advantage.

According to one embodiment, completing the re-establishing its dedicated traffic channel and synchronizing its RLP, the target MS may send a response to the activation signal 422 to the MCU, indicating that the target MS is ready to receive useful information. The MCU may send a talker ads to the client MS before streaming payload 420, which could be buffered at the MCU, to the target MS.

In one embodiment, the MCU may send the activation trigger 414 to the target subscriber hears some accessible to direct common channels, such as direct paging channel and forward common control channel, when the target listeners traffic channels the subscriber has not been established. In one embodiment, the MCU may send the activation trigger 414 to the target listener subscriber SDB form, regardless of what channel is used. If the control request is transmitted on a reverse common channel talker a communication SDB, and the response timer Sleep task force is set to zero at the MCU, actual switching delay in transmission mode on the client speaker can be reduced to the time required to send a request message SDB over uplink and then SDB response message on the forward link.

Network interfaces for call signaling messages

To determine what kind of traffic from the network, such as the payload of SDB, is transferred to an inactive mobile station without a dedicated traffic channel, it is possible to implement certain policies or interface infrastructure to distinguish such specific traffic from other traffic.

In a first embodiment, IP-datagrams may be filtered based on their sizes, as the SDB messages may carry a limited user payload. IP-datagrams smaller than a certain size limit may be sent as SDB message, if they are addressed to the mobile device without dedicated traffic channels. The group communication system may use such filters, as the request response message transmission mode application is extremely small, for example 34 bytes including the IP headers.

According to a second embodiment of the infrastructure of a manufacturer may specify an IP-based service for encapsulating IP-traffic destined for delivery to a mobile station. IP-server having information on this service may transmit small IP datagrams, e.g. UDP-datagrams, appropriately encapsulated in IP headers, to this service for delivery to a mobile device, which may not have a dedicated traffic channel. The group communication systems may use this service to indicate to the infrastructure that the request response message transmission mode is delivered to the requesting client MS, for example, in the form of SDB. Coordination of SDB traffic with pending Paging or requests for the initiation of services is also important to ensure fast and reliable delivery of user traffic.

In the third embodiment, IP server may transmit special IP datagrams, e.g., UDP-datagrams with IP headers for delivery to a mobile device may not having a dedicated traffic channel. IP-server can mark the IP datagrams, e.g., setting a special value in the IP header, for causing the infrastructure to deliver the IP datagrams to the client MS. The group communication systems may use this service to indicate to the infrastructure that the request response message transmission mode is delivered to the requesting client MS, for example, in the form of SDB. In the third embodiment, the range may be reserved UDP or TCP port for delivering specific IP datagrams, such as SDB messages.

Initiated by the mobile device initiating services and paging

In one embodiment, the client may send 404 a request transmission mode, which can be SDB form, followed immediately followed by a request to initiate service, addressed to a wireless communication infrastructure, such as CDMA, for fast re-establish its traffic channel. However, if the response timer Sleep set to a small value, the RD may respond quickly to control request and transmit a response 408 back to the client. If this response arrives at the infrastructure during the early phases of the service origination transaction, the infrastructure notes that the talker MS has no active traffic channel and may attempt to answer MS speaker ab onenta on the paging channel. However, this action is to implement paging can interrupt the already existing transaction initiation service. In one embodiment the MS talker may respond to the message transmitted over the paging channel, thereby guaranteeing that the request response message transmission mode delivered to the talker, and again request the initiation of service, but due to the interrupted initial attempts to initiate the service, there is an undesirable a delay in the re-establishment of a traffic channel talker.

According to the first embodiment in order to avoid competition between the process of initiating and paging services, RD can be configured to not respond immediately to a request 404 transmission mode. Accordingly, a sleep mode response timer may be adjusted so that the MCU 408 on the transfer response talker MS after the process of initiating the service.

In a second embodiment the PDSN receiving a response 408, and a mobile switching center (MSC), responding to a request to initiate a talker services, coordinate their actions. This means that, if the PDSN determines that the process of initiating a packet data service to the MS talker is already in progress when response 408 arrives at the infrastructure, the MSC can delay the execution of paging against the talker MS. PDSN may cache the response and send it to forward traffic channel of the mobile device talker after the initiation process services. Alternatively, the MSC may send the response to the talker MS as a message SDB, if the process of creating a service is still going.

According to the third embodiment, the talker MS may avoid the race without issuing a request to initiate service before long until it receives a response to the control request. According to one embodiment, since the talker MS has no active dedicated traffic channel, the MCU may send the response to the talker MS on some available common channels directly, such as a direct paging channel and forward common control channel. In one embodiment, the MCU may send the response to the talker MS in SDB form. Talker MS may rely on the response to the control request generated by the RD to start the re-activation of its traffic channel, in the same manner as activation requests sent by MCU trigger traffic channel re-activation for the listening mobile subscribers. The competition is eliminated by eliminating the ability to simultaneously initiate services initiated by the mobile device, and paging the mobile device, a network-initiated.

Caching trigger signals a packet data network initiated

Datagram IP, comprising a trigger 414 activation, which enters the wireless infrastructure, such as CDMA, and addressed to the mobile device listening party having no dedicated traffic channels may be lost, or the network as a whole, or wireless infrastructure, in particular . In one embodiment, the activation trigger 414 sent to the listener mobile device subscriber, retransmitted in persistent manner on the schedule as long as the listening party does not answer, or until the timer activation group. For example, a trigger activated 414 can retransmit every 500 ms. However, a retransmission trigger signals 414 activated at such intervals may cause a maximum delay of up to 500 ms, or an average delay of 250 ms from the moment of re-establishing traffic channel listening party until the next trigger activation signal addressed to the listener subscriber enters the infrastructure.

In one embodiment, the infrastructure or another entity in the network may cache the activation trigger 414 sent by the unit MCU, and deliver it to a target MS as soon as the target MS to re-establish its traffic channel. This eliminates the need for a retransmission request for the activation of the module and the MCU reduces total time exit from the sleep mode. Caching activation trigger signal 414, as opposed to retransmitting it at intervals, for example 500 ms, can eliminate the delay of 500 ms, the total time of the exit from the sleep mode.

Buffering useful information

In one embodiment, a user may be able to start speaking after he has requested transmission mode due to buffering payload to re-establish dedicated channels between a client and a listener. Due to the buffering of speech talker, the system allows the talker to start talking before the listeners traffic channels subscribers will be fully re-established. This allows the talker to start talking earlier, reducing its perceived delay in the transition to transmit mode. Because a listener does not suffer the transition delay in transmission mode on them is not affected, i.e. delay transition in the transmission mode is shifted from the talker to other parts of the system. Talker just have to wait to receive a listener to his first period of the conversation, but, as noted above, it is already prepared for the answer to his first period of conversation will have to wait longer than the answers to the following sections of the conversation, when he will enter the active conversation. Buffering first segment talk talker can be performed on the MCU side or on the client MS side.

Buffering on the side of the MCU

In one embodiment, the MCU may buffer the first segment talk talker. After the user has pressed the PTT and traffic channels by re-established, he is able to communicate with the MCU. At this time, since the traffic channels listening to customers not yet installed, the MCU buffers 418 the talker speech for onward transmission to the target listener call. MCU buffering may reduce the perceived delay in the transmission mode transition that talker perceives approximately the time required to activate a traffic channel talker. 17 is described below on the side of the MCU buffering according to one embodiment:

(1) No call is executed, the traffic channels of the initiator and targets are in the sleep mode.

(2) The user presses the PTT. The server receives a request from a client to "establish a group call."

(3) The user mode of transmission after the client receives a response from the server "setting is done" or after an adjustable delay time (1 second) and begins buffering user useful information.

(4) Server begins process of re-establishing packet data traffic channels purposes.

(5) The server sends a message to the client "classified group call" in the form of SDB.

(6) Client successfully re-establishes traffic channel, starts to transmit the buffered useful information to the server.

(7) The client performs streaming transmission of useful information to the server.

(8) The traffic channels purposes reinstalled (reach "target response threshold").

(9) User releases the PTT. The client stops buffering useful information.

(10) The client stops streaming buffered useful information to the server, the server requests the output of the transmission mode.

(11) The server sends the client a confirmation to the transmission mode.

Buffering on the client side

In one embodiment, when the perceived need shorter delay speaking subscriber can even speak to re-establish its traffic channel. Because the client MS is not yet in communication with the MCU, the signal talker to start talking gives the client MS. If the talker is allowed to speak to re-establish the traffic channel talker, the client MS may buffer 412 speech. Since the connection to the CMS is not yet established, permission to talk is given "optimistic way." 18 is described below on the client side buffering according to one embodiment:

(1) Not to make calls, the initiator of the traffic channel is idle.

(2) The user presses the PTT. The client sends a request to the server "to establish a group call" in the form of SDB.

(3) Client begins process of re-establishing packet data traffic channel.

(4) The user mode of transmission after the client receives a response from the server "setting is done" or after an adjustable delay time (1 second) and begins buffering user useful information.

(5) The customer receives a message from the server "classified group call" in the form of SDB.

(6) Client successfully re-establishes traffic channel

(7) The client performs streaming buffered payload to the server.

(8) The user releases PTT. The client stops buffering useful information.

(9) The client stops streaming buffered useful information to the server, the server requests the output of the transmission mode.

(10) The customer receives a confirmation from the server out of the transmission mode.

In one embodiment, as buffering 418 side MCU buffering 412 and client-side may be performed simultaneously. Buffering on the client side can afford to reduce the perceived delay in the transition to transmit mode. In one embodiment, the client MS may buffer information useful to control the perceived delay in the transmission mode transition experienced by the user. The combination of SDB mobile devices and buffering of useful information on the client may reduce the delays associated with re-establishing active traffic channels.

Thus, the disclosed embodiments provide for a dispatch model that supports at least two types dispetcherizuemyh calls: the chat-room model and the ad hoc model. In the chat-room model, groups are pre-defined, which may be stored on the dispatch server. A special group model can be defined and / or modified in real time.

The disclosed embodiments also provide a significant reduction in the actual total output time of the sleep mode and the delay switch to a transmission mode by exchanging group call signaling even when the mobile device is idle and no active traffic channels. The method and apparatus provide for the exchange of signaling with the group call signaling messages based on the short data bursts (SDB). The method and apparatus provide for re-establishing dedicated traffic channels for the talker mobile device and inactive mobile subscribers simultaneously listening that is predominantly.

According to another embodiment, the delay output from the inactive state to the network group communication can be reduced by caching trigger activation signals initiated by the network, addressed to the target listener subscribers, and delivering a trigger signal to activate the target mobile station as soon as the target mobile station re-establish its traffic channel .

According to another embodiment of the simultaneous service origination and paging execution on a mobile device operating in a group communication network is eliminated by the transmission request response transmission mode upon completion of the process for initiating services. In one embodiment, response control request may be in SDB form, if the service origination process is not complete. According to another embodiment of the process of initiating services to the communication device after the source begins transmitting the response to the source communication device.