Method and apparatus for participating in group communication services in an existing communication system

Method and device for participating in group communication service in existing communication system

Background of the Invention I. Field of Invention

The present invention relates to a point-to-multipoint communication system. In particular, the present invention relates to an apparatus and method for enabling group communication services using standard Internet protocols in an existing communication system.

II. Description of related skills

A point-to-multipoint communication system is generally used to provide communication between a central location in the system and multiple users. For example, a dispatch system using ground mobile radio (LMR) can be used for trucks, taxis, buses, and other vehicles to facilitate communication between a central dispatch center and one or more corresponding fleet vehicles. The communication can be directed to a specific vehicle in the fleet, or to all vehicles at the same time.

Another example of a point-to-multipoint communication system is a wireless push-to-talk system. This system allows a group of individuals with a wireless communication device to communicate with other members of the group. Generally, a push-to-talk call relies on a single frequency or dedicated channel to receive communications through a wireless communication device. In most systems, only one member at a time can transmit information to other members. However, all members can listen to the dedicated broadcast channel to receive communications from a single member of the transmission. If members want to transmit to other members of the system, they usually send an access request by pressing a button call button on their respective communication devices, wherein the access request allows the user to access only the dedicated channel.

Push-to-talk systems are usually used in outdoor settings, where a group of people or members request to communicate with each other in a "single-to-multipoint" manner. Examples of the use of push-to-talk systems include work group communication, secure communication, construction field communication, and local military communication. The group of people who require communication with each other is collectively called a "network", and each member of the network is sometimes called a "network member".

In a typical push-to-talk system, a dedicated channel is sometimes called a broadcast channel, which can transmit communication from one member to other members of multiple networks at the same time. A dedicated channel can include a single channel or frequency, or a group of individual channels, managed by a controller, and simulate a single channel. In either case, at any given time, only one member can transmit voice and/or data communications to other member users. If one member tries to transmit on the broadcast channel while another member is transmitting, interference between the two competing communications will occur, causing another network member to receive unintelligible communications.

Summary of the invention

In order to implement a push-to-talk communication system in a traditional wireless communication system, it is usually necessary to make expensive corrections to the infrastructure.

In addition to the high costs associated with current wireless point-to-multipoint communication systems, communication is usually limited to members who use the same or similar technologies and operate relatively close to each other. In other words, point-to-multipoint communication has not been extended to other communication networks or technologies such as the Public Switched Telephone Network (PSTN), or data networks such as the Internet, or the GlobalStar satellite communication system. Satellite communication system.

Therefore, the present invention is a push-to-talk communication device used to participate in a group communication network. The group communication network includes a controller for managing the group communication network and interface with the push-button communication device. A processor converts the information signal into packet data suitable for transmission on a distributed network. The processor can also have identification information, and when its current identification information has been or is about to change, the identification information is updated. Then, the processor transmits the new identification information to the controller. The push-to-talk device also includes a transmitter, which transmits packet data to the controller through a first channel. A receiver receives packet data from the controller through a second channel. The push-button communication device also includes a user activation mechanism, which is used to activate the transmitter when a user of the communication device wishes to transmit packet data to the controller.

In a specific embodiment, the communication device is a wireless communication device. The communication device may further include a memory for storing packet data until the controller is ready to receive the packet data. The memory is used to minimize the latency perceived by a user. The processor may further include a dynamically configurable priority level, wherein the priority level determines whether the communication device has the right to obtain transmission privileges on another communication device, so that the communication device can interrupt the communication device with a lower priority level Transmission of a communication device. At the same time, the processor can receive information about the group communication network from the controller, such as who participates in the network, how many people participate in the network, and where the users are physically located.

The communication device can also operate in a safe mode. The processor may further include identification information. When its current identification information has been or is about to change, the processor updates the identification information and transmits the new identification information to the controller.

The group communication network can be in a standby mode at the same time. The activation of the user activation mechanism prompts the controller to take the communication network out of the standby mode.

The communication device communicates with the communication manager. The communication manager includes a first node and establishes a first channel with a first communication device. At least one second node and at least one second communication device establish at least one second channel. The channel connecting the communication device and the controller or communication manager includes a Signal Initiation Protocol (SIP) channel, a media signaling channel, and a media traffic channel. A controller is also called a communication manager, and electronically connects the first node with at least one second node. The controller further includes a database module. The database module contains identification information of each communication device in the group. The controller can be dynamically configured so that any single communication device in the group can transmit packet data to other communication devices in the group through its respective channels. In a specific embodiment, the packet data includes time-sensitive information. In another embodiment, at least one communication device is a wireless communication device.

The controller further includes a core module and a network or media control unit (MCU) module. The core module and the network module are connected to the distributed network. The core module establishes the identification of each communication device and redirects information from the communication device to the network module. The network module operates and manages the information transmitted between groups of communication devices. In a specific embodiment, the database module is a part of the core module. The core module further includes an accounting log module. The account log module maintains an activity history between communication devices.

The network module further includes a regional log module. The regional log module maintains an activity history between communication devices, and transmits the compiled history to the accounting log module. The controller further includes a top-level server. The top-level server sends and receives data from the communication device. The packet data contains information such as the identification data of the communication device, the location data of the communication device and other information, and controls the data used to establish, modify, or terminate group communication.

The controller further includes a first timer for measuring a first elapsed time period. If the time elapsed before, does not have any communication means the information is transmitted to the controller, the controller transmits a message to each of the communication device for entering a standby section point. The controller further includes a second timer for measuring a second elapsed time period. If no communication device transmits information to the controller within a predetermined period of time, the controller transmits a message to each communication device to trigger a response from the communication device to determine whether the communication device wishes to remain active .

The controller further includes an arbiter for assigning a priority level to each communication device. The priority level is used to determine a transmission privilege level of the communication device, so that the communication device with a higher priority level can interrupt the transmission of the communication device with a lower priority level. The assignment of priority levels can be dynamically configured.

The controller further includes a buffer memory for storing the packet data until the communication device is ready to receive the packet data. The buffer memory is used to minimize the latency perceived by the user.

The communication device can operate on the same network, regardless of whether it operates on a different communication infrastructure, including, but not limited to, CDMA, TDMA, and GSM.

Therefore, one feature and advantage of the present invention is to provide end-to-end voice communication using Internet protocol.

Another feature and advantage of the present invention is that it provides wireless end-to-end voice communication using Internet protocol.

Another feature and advantage of the present invention is that it provides a wireless push-to-talk communication to a group of participants, and uses the Internet protocol to transmit voice as packet data.

Another characteristic and advantage of the present invention is that it provides a push-to-talk system on an existing communication infrastructure without modifying the existing basic communication infrastructure.

Another feature and advantage of the present invention is that it allows a group of wired or wireless communication devices to use the Internet protocol to transmit and receive voice data between each other.

Another feature and advantage of the present invention is that it provides a standby mode of an inactive push-to-talk network.

Another feature and advantage of the present invention is to provide a communication manager for managing and controlling one or more push-to-talk networks.

Another feature and advantage of the present invention is to provide a dedicated media control unit for a specific push-to-talk network.

Another feature and advantage of the present invention is that it provides full duplex on the packet data.

Another feature and advantage of the present invention is that it provides a signaling channel for setting and maintaining a push-to-talk network.

Another feature and advantage of the present invention is that it provides voice security on Internet protocol transmission.

Another feature and advantage of the present invention is that it provides a detailed history of changes in a push-to-talk network.

Another feature and advantage of the present invention is that it provides an arbiter that allows one or more users to replace the authorization to transmit voice or data with an access priority superior to other users in a push-button communication network.

Another feature and advantage of the present invention is that it minimizes the latency perceived by users of a push-to-talk network.

Another feature and advantage of the present invention is that it allows the communication device to discard the data frame to minimize latency.

Another feature and advantage of the present invention is that it allows the communication device to pre-grant a requirement in order to minimize latency.

Another feature and advantage of the present invention is that the voice data is buffered and stored in any user until a given user is ready to receive the data.

Another feature and advantage of the present invention is that it allows a user to multicast to multiple listeners on a single forwarding channel.

Another feature and advantage of the present invention is that it allows a communication device to recognize and report that its identification address has been or will be changed.

Another feature and advantage of the present invention is that it prompts a user to decide whether the user is still an active part of a push-to-talk network.

Another feature and advantage of the present invention is that it allows a user to exchange between multiple push-to-talk networks.

Another feature and advantage of the present invention is that it allows a user to dynamically determine the members of a given push-to-talk network.

Another feature and advantage of the present invention is that it provides a list of potential push-to-talk networks that a user can join.

Another feature and advantage of the present invention is to provide a user with geographic and other user-specific information about other users on the push-to-talk network.

The characteristics and advantages of the present invention can be more clearly understood from the detailed description of the following statements and combined with the diagrams, in which similar reference characters are compared and identified from beginning to end, and among them: FIG. 1 illustrates a network broadcasting system. Figure 2 illustrates a network broadcast service (NBS) network and how communication devices interact with a CM104. Figure 3 illustrates a functional block diagram of the Communications Manager (CM). Figure 4 illustrates an example of a network broadcast service (NBS) session initiation protocol (SIP) signaling protocol stack. Figure 5 illustrates a network broadcast service (NBS) media signaling protocol stack. Figure 6 illustrates the instant protocol voice media protocol stack. Figure 7 illustrates a user datagram protocol (UDP) voice media protocol stack. Figure 8 illustrates a media flow protocol stack. Figure 9 illustrates a DNS client protocol stack. FIG. 10 illustrates the high-level functions of the group service module 500 of the communication device (CD). Figure 11 illustrates dialog initiation protocol (SIP) call signaling 350. Figure 12 illustrates a media signaling message sequence. Figure 13 illustrates the message sequence relative to the media signalling to be used. Figure 14 illustrates a series of network broadcast service (NBS) media signaling messages. Figure 15 illustrates a state diagram of the CM104. Figure 16 illustrates a state diagram of the CD352.

Detailed description of preferred embodiments

The Network Broadcast Service (NBS) system enables Internet Protocol (IP) communication devices to participate in a group voice and data conference. The Internet Broadcasting Service (NBS) is mainly an Internet Protocol (IP) loaded voice (VoIP) application. Voice communication is transmitted from a communication device at a caller's endpoint to one or more listeners by encapsulating the voice frame in an Internet Protocol (IP) datagram. Data with voice can also be transmitted in this way. The NBS system is described in: US Patent Application No. 09/518,985, titled "Method and Apparatus for Providing Group Communication Services in Existing Communication Systems", filed on March 3, 2000 , Attorney Abstract No. 000212, and U.S. Patent Application No. 09/518,776, titled "Methods and Devices for Participating in Group Communication Services in Existing Communication Systems", filed on March 3, 2000, Attorney File No. 000211, especially incorporated by reference here.

FIG. 1 illustrates a functional block diagram of a group communication system 10. The group communication system 10 is also called a push-to-talk system, a network broadcasting service (NBS), a dispatch system, or a point-to-multipoint communication system. A defining characteristic of this type of network broadcast service (NBS) system is that at any given time, usually only one user can transmit information to other users. In a network broadcasting service (NBS) 10, a group of communication device users, each being a network member, communicate with each other using a communication device assigned to each network member.

The term "network" refers to a group of communication device users who are authorized to communicate with each other. Usually, a central database contains information used to identify each member of a particular network. There may be more than one network operations on the same communication system. For example, a first network may be defined as having ten members, and a second network may be defined as having twenty members. The ten members of the first network can communicate with each other, but usually do not communicate with the members of the second network. In other cases, members of different networks can monitor the communications between their members on more than one network, but can only transmit information to members within their own network.

The network can operate on an existing communication system without any substantial changes to the existing infrastructure. Therefore, a controller and user on the network can operate in any system that can transmit and receive packet information through the Internet Protocol (IP), such as a code-scribing multi-directional proximity (CDMA) system, and a time-sharing multi-directional proximity (TDMA) system, Pan-European Digital System (GSM) system, such as Globalstar^T^MOr Iradium^T^MThe satellite communication system, or various other systems.

The members of the network communicate with each other using a designated communication device, such as CD12, 14, 16, and 17 as shown. CD12, 14, 16 and 17 can be wired or wireless communication devices, such as: terrestrial wireless phones, wired phones with button-to-talk capabilities, satellite phones with button-to-talk capabilities, wireless video cameras, cameras, such as music recorders or Audio device of player, laptop or desktop computer, calling device, or any combination thereof. For example, CD12 may include a wireless land phone with a video camera and display. Furthermore, each communication device (CD) can transmit and receive information in any mode of security or no security (clear). In the following discussion, a reference body of an individual communication device (CD) may be expressed as a wireless push-to-talk phone. However, it should be understood that the reference body of the communication device (CD) is not limited to this, and may also include other communication devices, which have the ability to transmit and receive packet information according to the Internet Protocol (IP).

The network broadcasting service (NBS) system 10 of FIG. 2 defines a transmission privilege, which generally allows a single user to transmit information to other network members at any given time. The transmission privilege request of a network member that grants or rejects the request depends on whether the transmission privilege has been assigned to another network member when the network member receiving the request requires it. The processing of granting and denying transmission requirements is called arbitration. Other arbitration schemes evaluate factors such as the priority level assigned to each communication device (CD), where the priority level is used to determine whether to grant a requested network member the transmission privilege.

In order to participate in the NBS system 10, the CDs 12, 14, 16, and 17 respectively have the ability to request transmission privileges from a controller or a CM 18. CM18 is generally used to manage the real-time and administrative operations of the network. A communication manager (CM) is any type of computer-type device with at least one processor and memory. In a specific embodiment, the communication manager (CM) is a SUN workstation Netra T1^T^M。

CM18 maintains a list of defined networks in which the network is defined as clear or secure. The mutual change between clarity and preservation is usually not allowed. The security network relies on the encryption provided by the individual communication device (CD) to provide authentication and protection against eavesdropping. The encryption of the security network is implemented in an end-to-end manner, which means: encryption and decryption occur in each communication device (CD). The operation of CM18 usually does not require knowledge of security algorithms, golden keys, or policies.

Assuming that the service provider provides authorization, CM18 performs remote management through a communication system service provider, network member, or both. CM18 can receive network definitions through an external administrative interface 226. Network members can request administrative actions through their service providers, or perform administrative management of network functions through a member-operated security manager (SM) 20 that conforms to a CM18 administrative interface. CM18 can enable any group trying to build or modify a network to obtain high-level business standards certification.

SM20 is an optional component of the network broadcasting service (NBS) system 10, which is used to perform key management, user authentication, and support related tasks of securing the network. A single group communication system can interact with one or more SM20s. SM20 is usually not included in the real-time control of a network, and the real-time control of the network includes network activation or push-to-talk (PTT) arbitration. SM20 can have administrative capabilities compatible with a CM18 interface to automate administrative functions. The SM20 can also be used as a data endpoint to participate in a network, broadcast network keys, or simply monitor network traffic.

In one embodiment, the device for requesting transmission privilege from a communication device (CD) includes a push-to-talk (PTT) golden key or switch. When a user in the Internet Broadcasting Service (NBS) I0 wants to transmit information to other network members, he presses the button-to-talk switch located on his communication device (CD) to send a request to get it from CM18 Transfer privileges. If the transmission privilege is not currently assigned to other network members, the requesting user is granted the transmission privilege and notified by an auditory, visual, or tactile change through the communication device (CD). After granting the requested user the transmission privilege, the information can be transmitted from the user to other network members.

In an embodiment of the present invention, if possible, each wireless network member establishes a forwarding link and a reverse link with one or more base stations 22 or a satellite gateway 24. The base station 22 describes a communication channel from the base station 22 or the satellite gateway 24 to a communication device (CD). The satellite gateway 24 describes a communication channel from a communication device (CD) to a base station 22 or gateway 24. Voice and/or data are converted into data packets by a communication device (CD), wherein the data packets are suitable for a specific distributed network 26 through which communication can occur with other users. In a specific embodiment, the distributed network 26 is the Internet. In another specific embodiment, each communication system (that is, a terrestrial communication system and a satellite communication system) has a dedicated transmission channel for broadcasting information from each network member to other network members. Each network member receives communications from other network members on a dedicated channel. In another embodiment, each communication system builds a dedicated reverse link to transmit information to the CM18. Finally, a combination of the above schemes may be used. For example, in one solution, a dedicated broadcast channel may be built, but the wireless communication device (CD) is required to transmit information to the CM18 on a separate reverse link assigned to each communication device (CD).

When a member of a first network wants to transmit information to other members of the network, the member of the first network requests the transmission privilege by pressing a button call button on its communication device (CD). As in the case of CDs 12, 14, and 16, the demand is transmitted to one or more base stations 22 over the air. A mobile switching center (MSC) 28 includes a well-known Intermediate Work Function (IWF) for processing data packets between the MSC 28 and the distributed network 26, including this requirement. In CD16, the demand is transmitted to the satellite gateway 24 via satellite. In CD17, the demand is first transmitted to the public switched telephone network (PSTN) 30, and then to a modem memory 32. The modem memory 32 receives the demand and provides it to the distributed network 26. A network broadcast service (NBS) terminal 34 monitors the traffic of the network broadcast service (NBS) system connected to the Internet 26. Since the network broadcast service (NBS) terminal 34 is connected to the Internet 26, it does not need to be geographically close to the network participant.

If no other member holds the transmission privilege when the CM18 receives the transmission privilege request, the CM18 transmits a message to the requested network member, notifying it that the transmission privilege has been granted. Then, the information can be transmitted to the CM18 by using one of the transmission paths just described, and the auditory, visual, or other information from the members of the first network can be transmitted to other network members. Then, in a specific embodiment, CM18 provides the information to the network members by copying the information and sending each copy to the network members. If a single broadcast channel is used, each broadcast channel in use only needs to copy the information once.

In an alternative embodiment, CM18 is incorporated into MSC28, so that data packets from supported base stations are directly routed to CM18 without routing to distributed network 26. In this embodiment, the CM 18 is still connected to the distributed network 26, so that other communication systems and devices can participate in a group communication.

CM18 maintains one or more databases to manage information belonging to individual network members and each defined network. For example, for each member of the network, a database may include user names, account numbers, a telephone number or broadcast number associated with the member's communication device (CD), and the information assigned to the communication device (CD) A mobile identification number, the current network status of the member, such as whether the member is currently participating in the network, a priority code used to determine how to assign the transmission privilege, a data phone number related to the communication device (CD), An Internet Protocol (IP) address related to the communication device (CD), and an indication of which network the member is authorized to communicate with. Other related types of information can also be stored in the database for each network member.

The communication manager (CM) is used as a part of the network broadcast service (NBS) infrastructure to form the connection of individual communication terminals, and then form a call group or network. Communication Manager (CM) contains various useful capabilities on hardware and software, which can be configured in different ways to suit different applications. Usually, the communication manager (CM) provides real-time, administrative, and authentication operations for the management (NBS) network, push-to-talk (PTT) demand arbitration, network membership and registration list maintenance and distribution, and the necessary code is multi-directional Proximity (CDMA) system and network resource call settings and cancellation, as well as the overall control of the network status and other capabilities.

A network broadcast service (NBS) network can be included in a single deployable cellular system, or in a large multi-site configuration. In the case of a large configuration, multiple communication managers (CM) can be deployed geographically to form a single integrated system, and each communication manager operates as a plug-in module in the existing cellular infrastructure. Therefore, the new features introduced by the NBS network can be used by cellular users without modifying the existing cellular infrastructure.

One function of the Communication Manager (CM) is to maintain a list of defined networks of the Network Broadcasting Service (NBS). Each network definition includes a network identifier, a member list, which includes phone numbers or other identifying information, user priority information, and other general administrative information. The static definition of the network is clarity or security, and the mutual change between clarity and security is not allowed. A security network broadcast service (NBS) network usually uses media encryption to provide authentication and protection against eavesdropping. The media encryption of the security network is implemented in an end-to-end manner, which means that encryption and decryption occur in the communication device. The job of the communication manager (CM) does not require knowledge of full algorithms, golden keys, or policies.

The Communications Manager (CM) receives network definitions through an external administrative interface. Customers can request administrative actions through their service providers, or through a customer-operated security manager that conforms to the communication manager (CM) administrative interface for administrative management of network functions through a defined system. The Communications Manager (CM) can enable any group trying to build or modify a network to obtain high-level commercial standards certification.

Before explaining a specific embodiment of the present invention in detail, it should be understood that the present invention is not limited to the details of the structure and arrangement of the components described in the following description or illustrated in the drawings. The present invention can also be used in other specific embodiments, and can be implemented in various ways. At the same time, it should be understood that the phrases and nouns used here are for descriptive purposes only and should not be regarded as limitations.

FIG. 2 illustrates a NBS network 100 and how the communication device interacts with a CM 104. The large network broadcast service (NBS) network 100 can deploy multiple CMs 104 as desired. In Figure 2, a communication device 108 or CD 108 is allowed to transmit media to the network. In this case, the CD 108 is called the caller and transmits the media on one channel. When the CD 108 is designated as the caller, other network participants such as the communication devices 112 and 116 (or CD 112 and CD 116) are not allowed to transmit the media to the network. Therefore, CD 112 and CD 116 are designated as listeners. If CD 116 is designated as the talker, then CD 108 and CD 112 are designated as listeners, and so on.

As described above, CDs 108, 112, and 116 are each connected to CM 104 using at least one channel. In a specific embodiment, the channel is divided into separate channels, including a dialog initiation protocol (SIP) channel 120, a network broadcast service (NBS) media signaling channel 124, and a media traffic channel 128. Regardless of being designated as a caller or a listener, as long as the bandwidth allows, the dialog initiation protocol (SIP) channel 120 and the network broadcasting service (NBS) media signaling channel 124 can be provided at any time, providing CD 108, 112 and 116. A communication device (CD) is used. The Dialogue Initiation Protocol (SIP) is an application layer protocol defined by the Internet Engineering Task Force (IETF), which describes the control mechanism used to build, modify, and terminate multimedia dialogues operated by the Internet Protocol (IP). The Dialogue Initiation Protocol (SIP) supports the device for registering and locating users, defines the mechanism for user capabilities and describes media parameters, and determines the mechanism for user availability, traffic settings, and traffic handling. It provides a general solution to the traffic signaling problem of Internet telephony applications.

The Session Initiation Protocol (SIP) channel 120 is used to start and end a communication device (CD) participating in the network 100. A dialog description protocol (SDP) signal can be selectively used in the dialog initiation protocol (SIP) channel 120 at the same time. When using the dialog initiation protocol (SIP) channel 120 to configure the communication device (CD) to participate in a network broadcast service (NBS) network, use the network broadcast service (NBS) media signaling channel 124 to perform the communication device (CD) and CM 104 real-time traffic control and signaling. In particular, among other tasks, the network broadcast service (NBS) media signaling channel 124 is still used to handle button call demand and release, arbitrate conflicting demand or speech control, announce the start and end of information transmission, and manage network standby. Track endpoint connections, request and exchange network status, notifications and error messages. The agreement of the network broadcast service (NBS) media signaling channel 124 minimizes the length of the most common messages, and simplifies the task of interpreting answers and responding to demands while retaining the enhanced flexibility in the future. The network broadcast service (NBS) media signaling channel 124 protocol also allows retransmission requirements without negatively affecting the protocol status.

The message and traffic on the media channel 124 can be further divided into two categories: traffic setting and control signaling, which are mainly composed of dialog initiation protocol (SIP) invitation requirements and approvals; and media signaling, which mainly includes real-time speech control requirements and Related asynchronous messages. The media traffic on the media traffic channel 128 includes real-time point-to-multipoint voice and/or data broadcasting. Both types of messages have unique functional attributes. In addition, each communication device (CD) can send out domain name service (DNS) customer requirements, and map a fully qualified domain name service (DNS) host name to an Internet network address.

The network broadcast service (NBS) traffic setting and traffic control signaling are implemented according to the dialog initiation protocol (SIP) semantics. Although the dialog initiation protocol (SIP) can be transmitted using the well-known user datagram protocol (UDP) or transmission control protocol (TCP), as illustrated in FIG. 4, in a preferred embodiment, each communication device ( CD) uses User Datagram Protocol (UDP) to perform dialog initiation protocol (SIP)-style signaling functions. Moreover, each communications manager (CM) hopes to receive all dialog initiation protocol (SIP) signaling requirements through the user datagram protocol (UDP). The real-time signaling takes place via the communication manager (CM) and the dynamic UDP/IP interface on each communication device (CD). Other signaling can occur through a fixed TCP/IP interface between the communication manager (CM) and the communication device (CD), using the dialog initiation protocol (SIP).

Figure 3 illustrates the module and physical structure of the CM 104. CM 104 includes a communication manager (CM) core module or compounder 204, at least one network module or media control unit (MCU) 208 and 212, a domain name service (DNS) server 216, and a redirection Reference server 220 and an administrative workstation 224. The communication manager (CM) core compounder 204 is endowed with Java^T^MFunction of a web browser administrative capability. The communication manager (CM) core complex 204 can also include one or more domain name service (DNS) servers 216 at the same time. The communication manager (CM) core complex 204 further includes a communication manager (CM) mode 228 and a database server 232. CM 104 can be separated into at least two parts: a communication manager (CM) core complex 204 and each media control unit (MCU) node 208. After initially connecting to the communication manager (CM) core complex 204, a network route media control unit (MCU) node 208 is operated. When necessary, the media control unit (MCU) node 208 transmits and receives information from the communication manager (CM) core complex 204. The separability of the communication manager (CM) core complex 204 allows multiple functions to be provided. Once a special network is built, a dedicated media control unit (MCU) node 208 operates the network. This allows the communication manager (CM) core complex 204 to provide an initial connection that can be connected to other potential networks, regardless of the type of communication structure that the network wishes to operate on. At the same time, the communication manager (CM) core complex 204 may be geographically separated from the media control unit (MCU) node 208. For example, a single communications manager (CM) core complex 204 may be located in the middle of the United States, and a plurality of media control unit (MCU) nodes 208 may be located in various regions to operate the network from a given region. Therefore, the communication manager (CM) core complex 204 can enable a user to route to a specific media control unit (MCU) node 208 according to its location. At the same time, information can be provided to a user or user group based on location, such as location-based broadcast, location, or landmark recognition.

The Communication Manager (CM) node 228 provides centralized functions combined with the Network Broadcast Service (NBS) network. The communication manager (CM) node 228 includes a session initiation protocol (SIP) user agent server (UAS) server 236, and a CM manager 240, a central accounting log 244, and an administrative server 248. The Session Initiation Protocol (SIP) User Agent Server (UAS) server 236 supports the user's network list requirements, and handles the session initiation protocol (SIP) invitation messages of the network. When receiving a dialog initiation protocol (SIP) invitation message 229 from a communication device, the network assigns the communication device to an appropriate media control unit (MCU) node 208, and guides the communication device to the media control unit (MCU) Node 208.

The CM manager 240 monitors the status of all media control unit (MCU) nodes in a network, and assigns a given media control unit (MCU) node, such as the media control unit (MCU) node 208, for network execution. CM Manager 240 handles administrative functions belonging to network administration, including creating and deleting networks, defining new and deleting existing users, adding and removing network member users, and assigning a user, network, or communication The administrator (CM) and other broad bases can adjust various operating parameters.

The central accounting log 244 maintains time and identification information for accounting purposes. The central accounting log receives accounting log information from a regional log server 260 of the media control unit (MCU) node 208. It maintains detailed log information for each user, such as which communication devices are currently in use on the network, how long they last, where they come from, and when each communication device (CD) becomes a caller or a listener, and continues how long. The administrative server 248 supports an interface that allows the administrative workstation 224 to receive status information through the network status interface 280 to activate database administration and system management functions.

The communication manager (CM) implements a session initiation protocol (SIP) user agent server 236 and a session initiation protocol (SIP) media control unit (MCU) server 252. In order to support the network broadcast service (NBS), each communication device (CD) also implements a session initiation protocol (SIP) user agent client. The communication manager (CM) receives incoming dialogue initiation protocol (SIP) connections from an announced node or an announced port. When the connection occurs, the dialog initiation protocol (SIP) server 236 receives and processes the request according to the dialog initiation protocol (SIP) traffic signaling convention. The SIP server 236 can handle multiple traffic signaling connections in parallel.

In order to save network resources, after successfully (or unsuccessfully) joining the NBS network 100, the communication device (CD) can release the user datagram protocol ( UDP) connection. Thereafter, the User Datagram Protocol (UDP) connection can be re-installed to send additional Dialogue Initiation Protocol (SIP) traffic signaling requirements (for example, leaving the network or switching to another network).

FIG. 4 illustrates an example of a network broadcast service (NBS) session initiation protocol (SIP) signaling protocol stack 300. The stack is a collection of layers that implement the network communication protocol. The agreement related to each layer communicates with the upper and lower layers, and it is assumed that it supports the lower layers. Because the User Datagram Protocol (UDP) is a relatively unreliable connectionless transmission, the application-level reliability is better, which can ensure sound communication. The application-level reliability can be achieved by following the Session Initiation Protocol (SIP) The end point is implemented. Generally, the dialog initiation protocol (SIP) traffic signaling 302 on the user datagram protocol (UDP) stream 304 is encapsulated in the Internet protocol (IP) 306. No specific formatting is required. Dialogue initiation protocol (SIP) traffic signaling Internet protocol (IP) packet 306 in a code-swipe multi-directional proximity (CDMA) cellular communication device (CD) or a dial-up public switched telephone network (PSTN) type communication Exchange between devices (CDs), where these packets are encapsulated in a point-to-point protocol (PPP) message box 308. Therefore, no specific formatting is required. Simultaneously encapsulate the Dialogue Initiation Protocol (SIP) Traffic Signaling Point-to-Point Protocol (PPP) message box 308 exchanged between a coded multidirectional proximity (CDMA) cellular communication device (CD) and a base station in a radio link protocol (RLP) 310. For dial-up public switched telephone network (PSTN) type users, an appropriate modem standard such as V.32-bit or V.90 can replace the Radio Link Protocol (RLP) 310. In either case, no special processing is usually required, and it is not necessary to assume that it is an error-free physical link.

FIG. 5 illustrates a network broadcast service (NBS) media signaling protocol stack 312 that uses the user datagram protocol (UDP) datagram 304 to transmit voice and data traffic on the Internet Protocol (IP) 306. Network Broadcast Service (NBS) media signaling 314 is layered on top of UDP/IP traffic 306 and handled in a manner similar to that described in FIG. 4.

FIG. 6 illustrates an instant voice media protocol stack 320. In this embodiment, the vocoder payload data 322 is layered on the real-time protocol (RTP) 322 layer. Then, the real-time protocol (RTP) 324 is layered on the user datagram protocol (UDP) 304 and the Internet protocol (IP) 306 layer. In an alternative embodiment, the header compression of the compressed real-time protocol (CRTP) 330 further uses the real-time protocol (RTP) 324 at the application layer to encapsulate the media traffic. When the header compression technology is applicable to all UDP/IP incoming and outgoing UDP/IP traffic described in Figure 4-9, it can be applied. The media signaling requirements and responses are encapsulated in a user datagram protocol (UDP) datagram. When available, CRTP header compression can be applied to reduce the impact of transmitting uncompressed UDP/IP headers. In FIG. 6, the compression real-time protocol (CRTP) compression real-time protocol (RTP) layer 324, the user datagram protocol (UDP) layer 304, the Internet protocol (IP) layer 306, and the point-to-point protocol (PPP) layer 308. In FIGS. 4, 5, and 7-9, the compression real-time protocol (CRTP) 320 compression includes various levels between the user datagram protocol (UDP) 304 and the point-to-point protocol (PPP) 308.

In operation, when trying to join a network, each communication device (CD) dynamically selects a user datagram protocol (UDP) port to listen to the network broadcast service (NBS) media signaling requirements, and use the port As part of the SIP invitation it sends, it communicates with the SIP server 236. The media signaling destination address of the network communications manager (CM) (including the user datagram protocol (UDP) port number) is described in the network dialog description, as a successful signal initiation protocol (SIP) invitation request response Part of it, delivered to the communication device (CD). Different from the Signal Initiation Protocol (SIP) signaling address, the media signaling destination address is specified by the network and can be changed when a communication device (CD) joins a network. Generally, multiple networks controlled by the same communication manager (CM) are independent operations and do not share media signaling or media traffic ports. However, considering that multiple networks can still share media signaling and media traffic ports.

Referring to FIG. 6, the voice traffic is encapsulated in an RTP/UDP324 or User Datagram Protocol (UDP) payload 304 by grouping one or more vocoder message frames. Using real-time protocol (RTP) 324 to simultaneously enable compression of real-time protocol (CRTP) 330 can minimize end-to-end media latency and provide interoperability with (IP) telephony applications and services. In either case, when trying to join a network, the communication device (CD) dynamically selects the User Datagram Protocol (UDP) port for receiving media traffic, and uses the port number as the signal initiation protocol (SIP) for its delivery As part of the invitation, it communicates with the Signal Initiation Protocol (SIP) server 236.

The vocoder and transmission encapsulation protocol of the network, and its media traffic destination address (including the user datagram protocol (UDP) port number) are described in the dialog description response in response to the signal initiation protocol (SIP) server 236 A successful Signal Initiation Protocol (SIP) invite request. Like the same network media signaling address, the media traffic destination is designated by the network and can be changed when a communication device (CD) joins a network.

Generally, as shown in FIG. 6, the voice traffic is encapsulated at the application layer using real-time protocol (RTP) 324, where each user datagram protocol (UDP) datagram 304 is segmented into a real-time protocol (RTP) at the application layer The header 324 and the vocoder payload 322. FIG. 7 illustrates a user datagram protocol (UDP) voice media protocol stack 332. Usually when a network member cannot use or does not support Compressed Real Time Protocol (CRTP) header compression 330, the voice traffic can be selectively encapsulated using User Datagram Protocol (UDP) datagram 304 instead of Real Time Protocol (RTP). ) Package. FIG. 8 illustrates a stack 334 of media flow agreements. The media flow protocol stack 334 is used for network participants who do not have application layer real-time protocol (RTP) encapsulation. The data 336 is encapsulated in a user datagram protocol (UDP) datagram 304.

The structure of the user data report protocol (UDP) payload 304 follows the given definition of the corresponding real-time protocol (RTP) payload 324, in which there is no real-time protocol (RTP) header field. The decision to encapsulate the media directly in the User Datagram Protocol (UDP) 304 is configured by the network manager 248 and promoted through network dialogue announcements. In addition to voice media, the network broadcast service (NBS) network can also support any data broadcast. If a network supports a data broadcast channel, when a communication device (CD) formally joins the network, the signal initiation protocol (SIP) server 236 advertises its media in the description of the signal initiation protocol (SIP) dialogue of the network Types of.

Figure 9 illustrates a DNS client protocol stack 338. Each communication device (CD) includes the ability to use a domain name service (DNS) protocol 340 to resolve the domain name of the Internet into an Internet address. The communication device (CD) operates as a domain name service (DNS) client. As shown in FIG. 9, the communication device (CD) uses the User Datagram Protocol (UDP) 326 to encapsulate the domain name service (DNS) 340 requirements. As shown in FIG. 3, in order for the communication device (CD) to resolve the domain name service (DNS) host name, the Internet protocol (IP) network of the communication device (CD) domain name service (DNS) server 216 will be provided Road address. The DNS address can also be configured by the communication device (CD) service provider and optionally by the user.

In addition to voice media, the network can also support any data broadcast, such as secure network re-deposit keys, e-mails, data files, and so on. If a network supports a data broadcast channel, when the communication device (CD) officially joins the network, the communication manager (CM) advertises its media type in the description of the signal initiation protocol (SIP) dialogue of the network. Like traditional media broadcasts, in a specific embodiment, general data broadcasts operate under the Radio Link Protocol (RLP) (or a corresponding physical layer), but are generally regarded as less reliable transmissions.

The communication device (CD) includes the ability to resolve the domain name of the Internet into an Internet address using the Domain Name Service (DNS) protocol, as defined in RFC1034. Instead, the communication device (CD) operates as a domain name service (DNS) client or resolver, as described in RFC1035.

In order to provide the communication device (CD) to resolve the domain name service (DNS) host name, the communication device (CD) pre-programs the Internet protocol (IP) network address of a domain name service (DNS) server. The DNS address can be configured by the communication device (CD) service provider and optionally by the user.

The CM 104 can be optionally configured as a domain name service (DNS) server 216. Although it can use the Transmission Control Protocol (TCP) as the transmission protocol to respond to the domain name service (DNS) demand from external entities, in order to serve the demand originating from the communication device (CD), the dialog initiation protocol (SIP) server 236 also uses the User Datagram Protocol (UDP) 304 to encapsulate the domain name service (DNS) message according to FIG. 8.

The Internet Broadcasting Service (NBS) also utilizes the development of a cellular multicast channel. This type of channel usually allows a transmitting station to directly address N listening stations on a forwarding channel without the need to rebroadcast the transmitted data separately N times. The emergence of a cellular multicast channel means: change to the network broadcast service (NBS) media stack directly below the Internet Protocol (IP) network layer. In order to make good use of the efficiency provided by a cellular multicast channel, the media signaling and traffic destination address of a network is the traditional Internet Protocol (IP) multicast channel, and the communication manager (CM) originates the media The signaling and traffic broadcast are multicast broadcasts. The media signaling and traffic broadcast and signal initiation protocol (SIP) signaling sent by each communication device (CD) remain in point-to-point communication.

When the link layer (radio link protocol (RLP) message box) is lost, the radio link protocol (RLP) 310 shown in Figure 4-9 can be modified in each communication device (CD) to minimize The latency experienced. This type of modification is optional and does not affect the transmission operation of the application layer protocol, because the transmission control protocol (TCP) and the user datagram protocol (UDP) 304 are not regarded as a reliable network (IP) or link layer service.

There may be multiple radio link protocol (RLP) 310 modification strategies. For example, the radio link protocol (RLP) 310 can be modified to send multiple messages like NAK response at the beginning of the radio link protocol (RLP) timeout, thus prompting the remote transmission of the radio link protocol (RLP) 310 message To limit the lost duplicates, and to improve the chances of successful recovery of the radio link protocol (RLP) 310. The radio link protocol (RLP) 310 can be modified at the same time, (after the radio link protocol (RLP) timeout expires,) a NAK response is not sent, and the discarded radio link protocol (RLP) 310 message box is allowed to force The higher-level protocol stack generates an error. Any application layer protocol is based on the transmission control protocol (TCP) recovery mechanism of the commonly used Transmission Control Protocol (TCP) error recovery mechanism. Traffic that relies on User Datagram Protocol (UDP) 304 is struggling with potential loss.

Referring back to FIG. 2, once the communication device (CD) uses the signal initiation protocol (SIP) channel 120 to build to participate in the network broadcast service (NBS) network 100, the communication device (CD) is ready to be on the media traffic channel 128. A specific media port of the communication device (CD) transmits and receives media from the network 100. If the CD 108 is shown in Figure 2, the communication device (CD) obtains speech control through media signaling, then the communication device (CD) transmits the media to the network 100 and the destination network and transmission location indicated in the dialog description. site. When joining the network 100, the communication device (CD) decodes the media received by its media port according to the vocoder and the media format defined in the dialog description of the network 100 received in an invitation response. When a communication device (CD) joins the network 100, the communication device (CD) will send it to the network 100 according to the vocoder and the media format defined in the dialog description of the network 100 received in an invitation response The media is encoded and packaged.

Each communication device (CD) participating in a network determines the destination network and transmission address of each media channel from the received dialog description, and is used to address the corresponding media transmitted in the network 100, wherein the dialog description The signal initiated protocol (SIP) server 236 from the CM 104, and it is approved during the signal initiated protocol (SIP) traffic setting period. Each communication device (CD) provides a packet data connection to the communication manager (CM). The implementation of the communication device (CD) with this interface can be changed to optimize the performance of the network broadcast service (NBS). It is usually not necessary to change the infrastructure side of this interface. As further described here, the communication device (CD) can use Quick Network Connection (QNC) to selectively support most of the Internet Broadcast Service (NBS) activities.

When delivering to a service provider, the CM manager 240 undergoes basic administrative configuration before supporting NBS activities. The initial configuration includes basic system configuration, such as assigning passwords to operating system-level accounts for root-level system administration, and configuring the CM manager 240 network interface for proper operations on the regional wireless infrastructure network.

Once the CM 104 is configured, general network administration can be performed. The network administration function is carried out through a hypertext markup language (HTML) built on TCP/IP or other network interfaces. The administrative workstation 224 uses a traditional World Wide Web browser to interact with the CM core complex 204. Administration can be done regionally or remotely (anywhere on the Internet, or via dial-up). However, the basic transmission path of administrative access is usually TCP/IP. Multiple (at least three) administrative connections at the same time are allowed at the same time.

When connecting to the CM core compounder 204 for network administration, the administrator workstation 224 successfully authenticates itself to ensure that only authorized administrative actions are accepted. It allows different levels of access; for example, authorized network members can directly connect to the CM administrative interface (248) to modify the list of specific network members. The more general administrative privileges are largely reserved for specific administrative accounts. In order to be clear, the administrative actions are roughly separated into: special processing user definition and network definition. A user definition includes information such as user name, unique communication device (CD) cellular system identifier, communication device (CD) phone number, and user email address. Among them, a unique user identifier is defined, which can be transmitted to the communication device (CD) and used to uniquely identify the user in the signaling message. A network definition includes information such as: network address, network suspension time, dedicated scheduling timeout, and member list. A network member list includes information like a member record list, each including a user identifier and priority level. The member with the lowest priority level usually has listening-only privileges.

The CM manager 248 can monitor the current status of the network with administrative privileges. In particular, the CM manager 248 can determine the current list of network participants and monitor the network status (active, inactive, inactive, waking up, etc.). As long as the network is active, the CM manager 248 can also monitor the identity of the current caller. Additional statistics and status such as the current conversation length, total call time, average number of registered people, etc. can also be provided to the administrator through the administrative interface.

The administrative server 248 interface includes at least two network nodes or ports. One is a TCP/IP-style Hypertext Transfer Protocol (HTTP) interface, through a traditional Java^T^MThe functional web browser supports administrative access. The second is a unique command line interface (CLI) for TCP/IP-based Internet Broadcasting Service (NBS).

The administrative server 248 uses a hypertext transfer protocol (HTTP) web server interface to make all administrative functions available to general web browsers. Among them, the web server interface has one or more web pages, which are used like hypertext transfer protocol (HTTP). An Internet readable medium of HTML grammar is formatted. At least one administrative page can include an embedded Java^T^M A reference for applet. Certain administrative functions can be selectively executed through a web browser using the Hypertext Transfer Protocol (HTTP) GET and POST commands issued by the traditional HTACCESS authority. The supported administrative functions are usually a command line interface (CLI), which is usually a subset of the administrative functions supported by the command line interface (CLI).

The Hypertext Transfer Protocol (HTTP) interface can be used to integrate a Java^T^M The applet is delivered to the web browser. Then, the applet relies on the administrative server 248 command line interface (CLI) to provide additional administrative functions to the user through a web browser interface. Before obtaining the granted access to the command line interface (CLI), a potential administrative workstation 224 connected to the administrative server 248 command line interface (CLI) is authenticated. In a preferred embodiment, the command line interface (CLI) can be reached by a well-known and fixed Transmission Control Protocol (TCP) port address, and it can talk to multiple command line interfaces (CLI) for time management.

The database server 232 is responsible for storing network information and parameters, network user information, and status information related to the media control unit (MCU) 208 and 212 and the communication manager (CM) node 228. The database server 232 also provides this information to the other CM 104, such as the Signal Initiation Protocol (SIP) server 236 and other modules that require such information. The database server 232 maintains a database that captures information used to support network activities of the Internet Broadcasting Service (NBS), including a Network Broadcasting Service (NBS) network database part and a Network Broadcasting Service (NBS) User database section. The information supporting administrative activities and privileges can be stored in any database or a third-purpose database. The database server can be further subdivided into a user part and a network part.

The command line interface (CLI) supports administrative functions, such as the command line interface (CLI) to create users/networks, delete users/networks, modify users/networks, list/display users, list/ Display network, status and help etc. The create user function allows the administrative server 248 to create a new user in the user portion of the database, including specifying all user record fields. The delete user function allows the administrative server 248 to delete existing user records in the user portion of the database 232. The modify user function allows the administrative server 248 to modify the existing user records in the user portion of the database 232, including modifying all the record fields of a specific user.

The network creation function allows the administrative server 248 to create a new network in the user portion of the database 232, including specifying all network definition parameters. The delete network function allows the administrative server 248 to delete the existing network in the user portion of the database 232. The network modification function allows the administrative server 248 to modify the existing network in the user part of the database 232, including modifying all network definition parameters of a specific network. The user list function allows the administrative server 248 to list all users in the database 232 according to the user name, broadcast number, and user identifier.

The network listing function allows the administrative server 248 to list all networks in the network portion of the database 232 according to the network address and network identifier. The display user function allows the administrative server 248 to display all the fields of a specific user identified by the user's user ID. The display network function allows the administrative server 248 to display all the fields of a specific network identified by the network identifier or network address of the network. The status function allows the administrative server 248 to query a static status report of a specific network. The status function also allows the administrative server 248 to query real-time (latest) reports. In particular, the status function can identify the current network participant list, the current caller, the presence or absence of media traffic, and any and all media signaling messages sent or received by the Communications Manager (CM). The help function allows the administrative server 248 to query a short human-readable summary of each supported command line interface (CLI) command, including usage and syntax descriptions.

The network broadcast service (NBS) user portion of the database 232 tracks individual users of the network broadcast service (NBS). The user record contained in the database 232 may or may not be a network member defined in the communication manager (CM) network part of the database 232.

Each record in the user part of the database 232 contains such things as user name, user identification, vocoder list, dial-up number, user type, compression real-time protocol (CRTP) support, communication device (CD) use User address, and fields such as communication device (CD) good privacy (PGP) public key and other fields. The vocoder list is a list of vocoders supported by the user communication device (CD). The dial-up number is the dial-up number of the user communication device (CD). Generally, this field for Internet users is blank or has a zero value. The user type is a type field used to describe whether the user is a CDMA cellular user or a general Internet user. Users who dial and connect through the public switched telephone network (PSTN) are regarded as ordinary Internet users. Compressed Real Time Protocol (CRTP) support is a flag indicating whether the communication device (CD) supports and tries to negotiate the Compressed Real Time Protocol (CRTP) header compression on the Point-to-Point Protocol (PPP) when connected. This flag is valid for cellular and public switched telephone network (PSTN) users. The user address of the communication device (CD) is the global unique user address of the communication device (CD). A communication device (CD) identified by multiple user addresses will have multiple corresponding items in the user portion of the database 232. The PGP public key is a golden key combined with the address of the user of the communication device (CD).

The Network Broadcast Service (NBS) network database defines a collection of networks known to the Communications Manager (CM). The network part of the database 232 also lists the defined members of each network; that is, users who may request to join and become participants in a network. Each record in the network part of the database 232 contains various fields. The field includes a network identifier, which is a unique integer used to identify the background network of the communications manager (CM). The field also includes a network address, which is a SIP compatible network address for the network. The owner of the network is a non-empty user list, which is identified by a user identifier with (separately defined) network administrative privileges. At the same time, the network security status is a flag field to indicate that the network is clear or secured.

The field also includes the arbitration scheme, which is a unique value for identifying the arbitration scheme to resolve push-to-talk (PTT) arbitration conflicts between network participants. A field of network vocoder description, which has a unique value to identify the standard vocoder shown in the description of the networks promotion dialogue. The defined members of the network list this vocoder in the list of supported vocoders. Push-to-talk (PTT) fail-safe timeout is: the maximum number of seconds for a network participant to transmit media to the network before the communications manager (CM) wakes up the speech control with a PTX rejection message. The timeout value of the suspension time is: the maximum number of seconds that the network can remain idle before the communication manager (CM) arranges the network in a standby state. The PTX standby response timeout value is: the maximum number of seconds that the communications manager (CM) waits after deciding to grant a standby network speech and before transmitting the PTX grant response to the requesting communication device (CD) . The wake-up timeout value is: the maximum number of seconds that the communications manager (CM) waits for the network participant to respond to the AYT "wake-up" message before granting an unprocessed push-to-talk (PTT) request. The successor timeout value: before the communication manager (CM) removes the non-responsive communication device (CD) from the list of active participants in the network, the communication manager (CM) waits for a communication device (CD) to respond The maximum number of seconds for the communication manager (CM) to "wake up" the AYT message. The AYT timeout value is: before the communication manager (CM) removes the communication device (CD) from the list of active participants in the network, the communication manager (CM) waits for a communication device (CD) to respond to the communication manager (CM) The maximum number of seconds for its AYT message. The media channel list is: a list of the media channels of the network, including the payload description of the network (the list lists at least one media channel, which is used for voice transmission).

Network membership list definition: A collection of users who are required to join the network as a participant and who require specific privileges on the relevant network. Each item in the list includes a field such as a user identifier, which is a unique identifier of the user listed in the communication manager (CM) user database 232. The field also includes the user's network priority level, which is the user's priority level used by the network's push-to-talk (PTT) arbitration algorithm when the push-to-talk (PTT) conflict is resolved. A priority level of zero means that the user has listening-only privileges and may not be granted network control. The field can also include a user authentication list, which details the network authentication privileges the user has. Such privileges may include the ability to add, edit, or modify items in the network membership list, as well as the ability to modify other network participants.

Each communication device (CD) maintains a database, which is also called a group list, which is used to identify known networks that the communication device (CD) may require to join. Each item in the communication device (CD) database includes fields such as: network address, network security advisory flag, network traffic encryption key, and standby timer. The network address is the official Signal Initiation Protocol (SIP) network address of the network, which is used by the communication device (CD) to request to join the network and become an active participant. The network security advisory flag is a clear/secure advisory flag, which is assigned by the Signal Initiation Protocol (SIP) server 236 in the list of available networks of the Communications Manager (CM), or set by the user to indicate : A network has been defined and will carry Type IV secured media traffic. The network traffic encryption key is: the traffic encryption key used to encrypt and decrypt all media traffic of the Type 4 security network. The standby sitter timer is the length of the interval that the communication device (CD) will wait in the standby/idle state during the transition to the connected state, in seconds, to confirm that the packet data traffic remains valid and the base station does not The connection was not discarded one-sidedly.

The media control unit (MCU) node 208 includes a media control unit (MCU) 252, a media control unit (MCU) node manager 256, and a regional log server 260. The media control unit (MCU) nodes 208 and 212 can optionally include an additional media control unit (MCU) 264 at the same time. The media control unit (MCU) node 212 is essentially the same as the media control unit (MCU) node 208. For descriptive purposes, only the Media Control Unit (MCU) node 208 is discussed here. The Media Control Unit (MCU) 252 is responsible for the control of a single active network. The media control unit (MCU) supports the signal initiation protocol (SIP), media signaling, and media interface of the network, and provides functions related to the normal operation of the network. Each media control unit (MCU) node 208 has a sub-media control unit (MCU) 252, which can be appropriately guided to the management network. Each media control unit (MCU) 252 provides a media control unit (MCU) management interface 268 to support functions such as start, stop, and status reporting.

The media control unit (MCU) node manager 256 monitors the operations of the media control unit (MCU) node 208 and manages the operations of each media control unit (MCU) 252 on the media control unit (MCU) node 256. The media control unit (MCU) node manager 256 also provides the communication manager (CM) core complex 204 with an external interface 272 that allows opening and/or closing, assigning a network to the node, and sharing status information.

The regional log server 260 regionally records all log events of the media control unit (MCU) node 208. The regional log server 260 also responds to requests from the central log server 244 through its log event interface 276. The requirements include uploading certain event categories or priorities. In order to avoid event loss, the message is stored in the regional log server 260 until the central accounting log server 244 receives an approval.

The DNS server 216 provides a network broadcasting service (NBS) communication device name service. The Domain Name Service (DNS) server 216 can serve SRV record requirements. The DNS server 216 can be located anywhere on the network. In a specific embodiment, the domain name service (DNS) server 216 is a part of the communications manager (CM) core complex 204.

Each communication device (CD) maintains a network list or a group list internally, representing a set of known networks that the communication device (CD) can participate in. The list is immutable, but can be updated by interacting with a CM 104 as needed, or updated by user interaction. Users can also decide who and how many users are active or inactive on the network. A network broadcast service (NBS) group maintained internally by a communication device (CD) is functionally similar to a list of names and dial-up numbers maintained in a phone book and used to promote voice services. The network broadcast service (NBS) group list can also be integrated with the traditional phone book of the phone. In either case, the action of selecting a network from the group list can guide the phone to try to join the selected network.

In order to participate in a specific network broadcast service (NBS) network, initially, each communication device (CD) requires the communication manager (CM) to add itself to the list of active network participants of a specific network. Therefore, each communication device (CD) knows or can know the network address of any network it wishes to participate in. Furthermore, at the beginning, each communication device (CD) knows or can be configured with a top-level Signal Initiation Protocol (SIP) server 236 address, and the Signal Initiation Protocol (SIP) request will be sent to this layer. SIP) server 236.

The network address can be supplied or learned by a communication device (CD) in many different ways. For example, in a specific embodiment, initially, the communication device (CD) may be provided with a known or default top-level Signal Initiation Protocol (SIP) server 236 address, so that the communication device (CD) can participate in the network A current list of. At the same time, a group list of communication devices (CD) can be provided, in which at least one network address is defined, and the communication device (CD) is a member of the network. Thereafter, the communication device (CD) can send a request to the top-level Signal Initiation Protocol (SIP) server 236 to update its group list. In the event of an explicit network broadcast service (NBS) supplying the communication device (CD), before using the network broadcast service (NBS), a top-level signal activation protocol (SIP) server 236 and network location The address is provided to the user, and the communication device (CD) is entered interactively. At the same time, users can interactively enter additional network addresses into a group list, which already has items. This configuration step is similar to entering the personal name and dialing number into a traditional phone book.

Please note that although the user can interactively enter a network address into the communication device (CD) group list, it is better to have a corresponding network and a top-level signal initiation protocol (SIP) server 236, and it is necessary List the user as a member of the network so that the communication device (CD) can successfully participate in the network.

At the same time, it can provide the Internet Protocol (IP) network address of the main domain name service (DNS) server 216 of the communication device (CD) for sending the domain name service (DNS) query. Generally, the address of a domain name service (DNS) server 216 operating with a code-stroke multi-directional proximity (CDMA) cellular carrier is provided. At the same time, the communication device (CD) can be provided with the Internet Protocol (IP) network address of an alternate domain name service (DNS) server.

In order to support the Signal Initiation Protocol (SIP) authentication, when the CM 104 requests it, a unique good and private (PGP) user ID and secret key are available for the communication device (CD) to sign the Signal Initiation Protocol (SIP). ) Affairs. The PGP user identifier can also be used as the user address of the communication device (CD) for general signal initiation protocol (SIP) transactions.

FIG. 10 illustrates the high-level functions of the group service module 500 of the communication device (CD). Normally, when the power of the communication device (CD) is turned on, the group service module will be initialized to a default idle state 504. The communication device (CD) can transition from the idle state 504 to other states, allowing it to actively participate in the network broadcast service (NBS) network.

The user may wish to temporarily disable the network broadcast service (NBS) service through a menu option in the user interface of the communication device (CD). If the user has disabled the network broadcasting service (NBS) service, the group service module will default to a disabled state 508 when the power of the communication device (CD) is turned on. When disabled, the communication device (CD) will not try to automatically join any network broadcast service (NBS) network. Furthermore, the communication device (CD) does not perform any signal initiation protocol (SIP) transactions specific to the Internet Broadcasting Service (NBS) (for other Internet Protocol (IP) telephone applications that reside in the communication device (CD), The communication device (CD) can maintain its registration or perform other signal-initiated protocol (SIP) transactions).

Optionally, by providing the group service in the communication device (CD) to an unequipped state 512, the group service can be completely hidden from the user. The unequipped state disables the group service, and the one equipped state enables the group service. Once unequipped, the communication device (CD) requires administrative supply to equip group services. When the group service is unequipped, the network broadcast service (NBS) group service function and related user interface features cannot be used by the user.

The communication device (CD) can support air supply to equip the network broadcast service (NBS) group service. In the event that the group list of the communication device (CD) contains more than one network address, only one network address can be identified as a default network 514. If a network address is selected, the communication device (CD) attempts to automatically change from the idle state 504 by trying to join the selected network immediately after its power is turned on.

When the communication device (CD) is connected, the communication device (CD) is in a quiet state 516, a listening state 520, a talking state 524, and a standby state according to whether the user is in the push-to-talk system described with reference to FIG. 16. Cycle through states 528.

The network broadcast service (NBS) relies on the available network address for the traffic signaling grammar and semantics as defined by the Signal Initiation Protocol (SIP), and the provider for a specific communication device (CD) to officially join or leave the network. CM104 includes: a top-level signal activation protocol (SIP) server 236, one or more multimedia control unit (MCU) 252 and related signal activation protocol (SIP) user agent server, and administrative database 232 for users and The network part is accompanied by other functional entities. The top-level Signal Initiation Protocol (SIP) server 236 serves as a known meeting point for participating in the system. Each media control unit (MCU) 252 performs media signaling and media traffic exchange for one or more networks. The database 232 stores and provides known user, administrative, and network address definitions, and can be installed by a multi-communication manager (CM) or accessed remotely.

Each communication device (CD) has a list of network addresses and one or more layer signal initiation protocol (SIP) server 236 addresses. If the group list is blank, the user can interactively specify an existing network address. If the SIP server 236 is not defined, the user can interactively designate a SIP server 236 address. Once the address of the top-level Signal Initiation Protocol (SIP) server 236 is known, the communication device (CD) can arrange a call to a pre-defined Signal Initiation Protocol (SIP) by using the Signal Initiation Protocol (SIP) invitation method The destination requires an updated list of available networks.

The top-level signal activation protocol (SIP) server 236 can redirect the request to an internal destination, or directly respond. The call invitation response includes the current network list available for the communication device (CD). The communication device (CD) uses this list to update its internal group list.

After selecting a network, the communication device (CD) tries to use the Signal Initiation Protocol (SIP) invitation method, by specifying the network address as the invitation destination, and sending the request to the top-level Signal Initiation Protocol (SIP) server 236, while joining the network. The top-level server 236 attempts to map the network address to a known destination, and if successful, redirects the communication device (CD) to the media control unit (MCU) 252 and its corresponding signal activation protocol (SIP) User agent server. If it cannot be mapped, the invitation is invalidated.

Normally, the destination signal initiation protocol (SIP) user agent server of the media control unit (MCU) 252 confirms that the communication device (CD) is a member of the selected network, and responds to the invitation to transfer the media traffic and the message. Let the description of the parameter be embedded in the content of its response to participate in the network. If the communication device (CD) cannot be confirmed as a legitimate member of the network, or if some other error condition occurs, such as a malfunction that prevents normal network operations, the media control unit (MCU) 252 signal activation protocol ( SIP) User Proxy Server can answer an error at the same time. If the invitation is accepted, the communication device (CD) acknowledges the response through a message such as the signal initiation protocol (SIP) ACK method. Please note that when processing the invitation, the communication device (CD) can also receive other transition response codes to indicate the progress of the traffic.

The communication device (CD) is responsible for updating its group list to a collection that can participate in the network. Even if no network address is selected, the user can still command the communication device (CD) to query the database 232 of the CM 104 to receive the update of its group list. If the communication device (CD) decides that it has been added or removed from a network, it will briefly display an appropriate message (for example: "Add to Group X") and/or a possible prompt for the user to interact. If the communication device (CD) decides that it is not a member of any network, it will also notify the user. The communication device (CD) can automatically incorporate the new network address into its group list, but the user may be prompted first before deleting its lost network address from the group list.

Generally, once selected, only one network in a communication device (CD) group list can be identified. A default network can be selected initially, or the user can select a network from the group list.

Such as embedded content, the media control unit (MCU) 252 and its communication manager (CM) signal initiation protocol (SIP) user agent server responds to an invitation request to join a network, including: network media and real-time media messages Make the destination address, and other network parameters (such as the description of the media payload format). Once confirmed, the communication device (CD) briefly displays feedback to the user, indicating whether the user has the listening-only privilege and the group service function is enabled. If the CM 104 determines that the communication device (CD) is not a member of the selected network, or an error or other unexpected condition occurs, the SIP server 252 responds with a corresponding error response. When this registration is rejected, the communication device (CD) briefly displays a corresponding error message, and the group service function remains idle. If no network is selected, the group service in the communication device (CD) remains idle.

As part of the activation of the group service, the communication device (CD) initializes and opens the real-time protocol (RTP) media traffic channel 128 and the separate address of the communication manager (CM) destination address provided in a successful invitation response. Network Broadcasting Service (NBS) media signaling channel 124. Once these channels are initialized, the group service is activated on the CD 108, and the group service quiet state 516 is entered with the ability to receive voice traffic from the network and request permission to transmit voice traffic to the network.

The CD 108 monitors its media traffic 128 and the signaling channel 124 connected to the communication manager (CM) through the currently used group service. The voice data received on the media flow channel 128 will be decoded according to the current user configuration and presented using a CD 108 far-field speaker or a headphone accessory. The CD 108 displays the current speaker identity according to the identification through the real-time media signaling 124. If the current speaker identity is not available, CD 108 will display the currently selected network name according to the group list. The CD 108 can also list media traffic statistics (for example, the total amount of time consumed for calling, listening, and monitoring the estimated media traffic received packet loss), and use a menu option to provide it to the user as a diagnosis. Although the CD 108 changes to the group service listening state 520 when receiving traffic from the network, it returns to the quiet state 516 when the voice traffic stops.

At any time, the user can press the button to talk (PTT) to cause the CD 108 to signal a speech control request to the CM 104 (especially the media control unit (MCU) 252), requesting permission to talk to the network. Push-to-talk (PTT) button can be any type of activation command, including but not limited to pressing a button or a series of buttons, voice activation, a switch, a two-state trigger device, or a dialing dial. The media control unit (MCU) 252 responds by granting or rejecting the demand. If the communication device (CD) has the listening-only privilege, such as CD 112 (that is, the priority level of the communication device (CD) in the selected network is zero), then the demand is rejected. If rejected, the CD 112 warns the user with an error tone, displays an appropriate error or explanation message, and returns to the quiet state 516. The communication device (CD) insists on releasing it and pressing the button to talk (PTT) again before trying another speech control request. If granted, the CD 112 enters the group service call stack 524, for example, signals the user with a short audible chirp, and only needs to type a push-to-talk (PTT) to start transmitting voice traffic to the CM 104. (When typing Push-to-Talk (PTT),) CM 104 can simultaneously send a signal to CD112 to inform that it has lost control of speech. Upon receiving this signal, the CD 112 stops transmitting voice traffic and warns the user with an error tone until the push-to-talk (PTT) is released, and at the same time it returns to a quiet state 516. Otherwise, once the push-to-talk (PTT) is released, the CD 112 sends a signal to the CM 104 to inform it that the speech has been released, and returns to the quiet state 516.

When the group service in the CD 108 is in the quiet state 516, the listening state 520, or the standby state 528, the user can switch to a different network by selecting another network from the group list. When a new network is selected, the CD 108 sends a signal to the CM 104 to remove it from the current network through a signal-initiated protocol (SIP) call setting mechanism, and then follow a similar protocol to join the new network. If the process of joining a new network fails, the CD 108 is no longer a member of any network, and the group service in the CD 108 returns to the idle state 504.

If the CM 104 decides that the CD 108 requesting to speak in a special network is the only registered member of the considered network, then the CM 104 rejects the speech control request and sends an error message like a single user error for the CD 108 Show to users. Although a network may only have one registered member, if this is the case, the network cannot relay voice traffic unless there are at least two registered members.

The Internet Broadcasting Service (NBS) application is based on two different application layer protocols: Signal Initiation Protocol (SIP) traffic signaling as described with reference to Figure 11, and Network Broadcasting Service (NBS) as described with reference to Figures 12-14. ) Media signaling. The Signal Initiation Protocol (SIP) is dedicated to traffic signaling and traffic setting. Media signaling carries push-to-talk (PTT) requirements (Figure 12), manages network availability (Figure 13), and resolves push-to-talk (PTT) arbitration conflicts (Figure 14).

Figure 11 illustrates Signal Initiation Protocol (SIP) traffic signaling 350. The Signal Initiation Protocol (SIP) provides network broadcast service (NBS) application layer control (signaling) for discovering, joining and leaving the network broadcasting service (NBS) using the Signal Initiation Protocol (SIP) server interface 236 of CM 104 )network. To join a network, the CD 352 initiates a protocol (SIP) server 236 through the top-level signal, and invites the network 100 to participate in a call by name. To leave the network 100, the CD 352 sends a corresponding "Goodbye" to the network.

When necessary, CD 352 uses DNS 216 to resolve the provided primary or secondary Signal Initiation Protocol (SIP) server address into an Internet address to determine the top-level signal initiation protocol (SIP) The Internet Protocol (IP) address of the server 236. As an alternative approach, the Signal Initiation Protocol (SIP) convention allows the CD 352 to query the service records of the domain name service (DNS) 216 related to the network address and the domain portion of the network broadcast service (NBS) host system. , And communicate with the SIP server 236 with the returned address.

Unless alternate port information is determined through the Domain Name Service (DNS) 216, the CD 352 attempts to use a default Signal Initiation Protocol (SIP) port to communicate with the Signal Initiation Protocol (SIP) server 236 according to the default. Before attempting to join a network, the CD 352 can use the Signal Initiation Protocol (SIP) invitation method to arrange a call to request an updated list of available networks.

For example, after establishing an air connection CD 352 obtains an Internet Protocol (IP) address, and hopes to determine its current list of available networks. Therefore, a UDP/IP connection to the SIP server port is opened, and a request is issued. The need to obtain an updated network list will be addressed to a specific destination. If appropriate, CD 352 also includes additional application-specific headers for identifying code-switching multi-directional proximity (CDMA) networks and systems, from which a code-scribing multi-directional proximity (CDMA) cellular CD 352 can obtain services.

The CD 352 may also include a header to indicate that the CD 352 wants the Signal Initiation Protocol (SIP) server 236 to understand and support the Internet Broadcasting Service (NBS) service. The option value assigned with the header can also be used by the CD 352 to notify a server 236, where the server 236 has a specific version or type of Internet Broadcasting Service (NBS) service that the CD 352 wishes to support.

The top-level Signal Initiation Protocol (SIP) server 236 of the Communications Manager (CM) can use the Signal Initiation Protocol (SIP) to redirect the mechanism to redirect the invitation request 356 to a destination, which is specifically defined for receiving and responding The demand for network information. Upon receiving this redirection, the CD 352 acknowledges (ACK) the response 357 and retransmits the request to the destination of the redirection.

The CD 352 may have to determine the appropriate Signal Initiation Protocol (SIP) contact point to redirect the address through the DNS organization. In order to simplify the processing of the CD 352, the server 236 can use its Internet address to clearly specify the redirection destination. Once the server 236 successfully receives and accepts an invitation message 354 requesting a network list, the server 236 sends an invitation request response 356.

The content of the invitation request response 356 includes a list of records, which defines the set that CD352 can subsequently join the network. The server 236 queries the network database 232 that lists the requested CD 352 as a network of defined members to form a response 356 to the invitation request 354. The network in the content is identified using an application-defined record format, where the format includes the official network address of the network. The network can be displayed in any order.

The server 236 may be unable to successfully respond to the CD352 due to various reasons. In this case, the server 236 sends an appropriate Signal Initiation Protocol (SIP) status code instead of the invitation response 356. CD352 must be prepared to accept and interpret such status codes in order to take appropriate action in case of any fatal error (such as displaying an error message on the CD352 user interface display). The server 236 can also open a successful invitation response 356 with a notification status response, where the notification status response indicates the progress of registration. CD352 can accept and interpret the notification status code of successful registration.

The CD 352 sends a signal to the computer manager 240 to initiate a protocol (SIP) invitation request 358 through the server 252 to request to join a network. If the CD 352 does not have an open UDP/IP connection to the Signal Initiation Protocol (SIP) server 252, a new UDP/IP connection to the Signal Initiation Protocol (SIP) server port will be opened.

The CD 352 is ready to be redirected by the top-level Signal Initiation Protocol (SIP) server 236, and if necessary, repost the demand to the redirected destination. The Communication Manager (CM) top-level Signal Initiation Protocol (SIP) server 236 appropriately redirects any incoming invitation requirements to the Media Control Unit (MCU) Signal Initiation Protocol (SIP) server 252 related to the currently considered network . The CD 352 can be redirected more than once.

Assuming that the invitation is successful, the invitation requirement 358 may include a description (such as message content) of the media source initiated by the CD 352. If the description is included, the description becomes the message content, and the field structure is used to describe it.

The dialog description is delivered in a format compatible with the dialog description protocol (SDP). After defining the dialog description protocol (SDP) version (v), the dialog description includes a mandatory origin (o) description. The CD 352 can use any convenient mechanism to select the value of the dialogue identifier and dialogue version. One possible way to define the dialogue identifier is to provide an estimate of the current time. The connection data (c) is specified by defining the network type, address type, and connection address. CD 352 uses Internet Protocol (IP) addresses to mark media traffic (or its source) as connection addresses. The CD 352 uses the name part of the network address of the network as the dialog name(s). The CD 352 provides the best estimate of the start or current time, preferably according to the Network Time Protocol (NTP) format, and specifies the lifetime (t) of the conversation and indicates that the conversation is unbounded (o). The media format (m) is defined in the description: media type, source port, transmission protocol, and payload format for CD 352 to transmit to the network. Finally, the conversation description uses an attribute (a) type definition, indicating that the CD 352 expects the conversation as a network broadcast service (NBS) conference operation. Before granting the invitation, the server 236 must confirm that the invited address is indeed a valid NBS network address.

In order to indicate a successful invitation and specifically notify the CD 352 that it has been added to the participant list of the invited network, the server 236 sends an invitation response 360.

A successful invitation response 360 includes the main dialog description of the invited network, which uses the dialog description protocol (SDP) syntax to describe the supported media traffic ports and formats. The dialog description includes a connection (o) description, which defines the network address to which all media signaling and traffic will be delivered. The media destination network address of the network can be different from the network address of the Signal Initiated Protocol (SIP) user proxy server, where the Signal Initiated Protocol (SIP) user proxy server network address is used Domain Name Service (DNS) resolves from network addresses.

All media and destination media ports are described in the dialog description. The dialog description should also include an identifier assigned to the CD 352 by the media control unit (MCU) 252 to identify the media signaling information transmitted by the CD 352 as the part of the network that it subsequently participates in. Among all active participants on a given network, the value of this identifier is unique, so it must be dynamically generated. The CD 352 does not need to access this identifier at high speed between successful signal activation protocol (SIP) invitations.

The dialog description can also include an announcement of a network broadcast service (NBS) protocol version, which indicates the revision level followed by the media signaling of the network. This declaration can be implemented by expanding the value of the type attribute field or defining a new attribute, where the attribute value is the agreement version number.

After receiving a successful invitation response, the CD 352 sends a signal initiation protocol (SIP) acknowledgment (ACK) request 362 back to the media control unit (MCU) signal initiation protocol (SIP) user agent server of the network 252, and confirm the invitation. After transmitting the ACK request 362, the CD 352 may close its Transmission Control Protocol (TCP) connection with the Signal Initiation Protocol (SIP) server. Before transmitting the ACK request 362, the CD 352 initializes its media signaling and traffic port according to the dialog description delivered in the invitation request 360.

Any time after CD352 transmits a Signal Initiation Protocol (SIP) ACK message 362 in response to a successful invitation response 360, CD352 can send a Signal Initiation Protocol (SIP) goodbye message 364 to the user agent server of the network 252, and officially terminated participation in the network. Before sending the goodbye message 364, the CD 352 may have to open a transmission control protocol (TCP) connection to the user agent server 252. The goodbye message 364 is recognized by the communications manager (CM) with a goodbye response message 366. Once the goodbye response message 366 is approved, the CD 352 may use the user agent server 252 to close its user datagram protocol (UDP) connection. Before approving the goodbye response message 366, the user agent server 252 removes the CD352 from the list of active participants of the indicated network.

Generally, a signal-initiated protocol (SIP) user agent of the CD352 can use an option method to query the capabilities of a signal-initiated protocol (SIP) server. In particular, the CD 352 may wish to query an arbitrary Signal Initiation Protocol (SIP) destination to determine whether the destination provides network broadcast service (NBS) traffic signaling support.

Before receiving the invitation response 360 and sending the approval 362, the CD 352 may wish to suspend a pending invitation request 358. In this case, the CD352 can use a signal initiation protocol (SIP) cancellation (not shown) method to calmly terminate the traffic. Both the top-level signal activation protocol (SIP) redirect server 236 and the signal activation protocol (SIP) user agent server 252 of the communication manager (CM) support this cancellation method.

For example, if the user decides to schedule a voice service call and presses send before the invitation message 358 is completed, the CD 352 can use the cancellation method to suspend an ongoing invitation message 358. In this case, the CD 352 can simply cancel the invitation message 358 immediately, and continue to arrange the requested voice service call instead of waiting for the invitation response 360 to complete and send the goodbye message 364 immediately.

After the CD 108 successfully negotiated the project to become a current member of a network broadcast service (NBS) network using the Signal Initiation Protocol (SIP), all real-time traffic control is through each CD 352 and the media control unit (MCU) of the network The signal-initiated protocol (SIP) server 252 exchanges point-to-point application layer media signaling messages.

The media signaling messages are stacked using the protocol illustrated in FIG. 4 and transmitted according to the sequence illustrated in FIG. 12. Figure 12 illustrates a media signaling message sequence 368. A push-to-talk (PTT) request message 370 is sent from the CD 352 to the signal initiation protocol (SIP) user agent server 252 of the media control unit (MCU) node 208, and signals to those who wish to broadcast the media to the network For a user, usually the media is voice. Generally, each time the CD 352 button is pressed, a push-to-talk (PTT) request message 370 is sent, indicating a speech control request. In addition, when the user releases the CD 352 button call button, the CD 352 sends a push-to-talk (PTT) release message to the signal activation protocol (SIP) user agent server 252, indicating that the "speaking" is normally released.

Push-to-talk (PTT) messages include fields such as opcode, id, src, and reserved. Operation code field definition: Push-to-talk (PTT) message is a speaking control request or release message. The id field provides a unique message identifier, allowing subsequent push-to-talk (PTT) release and PTX messages to refer to a specific push-to-talk (PTT) requirement. In the registration dialog of a special CD 352, the id must be unique. The src field uniquely identifies the CD 352 that sends the push-to-talk (PTT) request 370 to the signal-initiated protocol (SIP) user agent server 252. The reserved field is used to reserve space in the push-to-talk (PTT) message 370 for further functions.

For each push-to-talk (PTT) request 370 transmitted, the CD 352 expects to receive at least one PTX response message 372. If a PTX request 372 is not received within a predetermined timeout period, the CD 352 assumes that the push-to-talk (PTT) demand 370 is lost during the transition, and uses the same push-to-talk (PTT) id to retransmit the push-to-talk (PTT) id. ) Message 370. If within a predetermined number of retransmissions, a PTX response message 372 from the Signal Initiation Protocol (SIP) user agent server 252 is not received, the CD 352 assumes that the Signal Initiation Protocol (SIP) user agent server 252 retransmits It can't be reached, so it changes to the NBS idle mode and indicates an error condition to the user. In a preferred embodiment, the CD 352 uses different push-to-talk (PTT) ids for demand and release messages.

The PTX message 372 is sent by the Signal Initiation Protocol (SIP) user agent server 252 to a CD 352 to recognize and respond to an earlier push-to-talk (PTT) request 370, and to signal asynchronous speech control events . The signal activation protocol (SIP) user agent server 252 uses the PTX message 372 to respond to a push-to-talk (PTT) speech control request or release. The PTX message 372 includes information such as speech control requirements for granting or denying references.

In response to a push-to-talk (PTT) speech control release 370, the PTX message 372 is only used to indicate acceptance of confirmation. When responding to a push-to-talk (PTT) speaking control release 370, the PTX message 372 is only used to indicate acceptance of confirmation. The SIP user agent server 252 can use the PTX message 372 at the same time, and asynchronously reject a speech control request granted earlier (when a higher priority CD 352 sends a speech control request, it will grant PTX Expiration (that is, timeout), or some other event occurs, requesting cancellation of network speech control).

The PTX message 372 includes fields such as opcode, id, action, status, and expiration. Operation code field definition: PTX message 372 is a synchronization request of an unprocessed push-to-talk (PTT) request, or it is an asynchronous message to indicate an error or priority arbitration violation. The id field refers to a push-to-talk (PTT) request received earlier. Action field indication: PTX message 372 controls the authorization, rejection, cancellation, or confirmation of network speech. The status field provides additional information to explain the PTX action, especially when the PTX message 372 is rejected, cancelled, or unable to act according to the previous push-to-talk (PTT) demand. The status field can indicate that network control has been granted to a higher priority caller, or CD 352 has not been listed as a network participant, so it is not allowed to submit media signaling requirements for this network. The expiration field represents the maximum duration of time that the network speech control is granted to receive the CD 352, in whole seconds. The Signal Initiated Protocol (SIP) user agent server 252 starts its timer at the moment when the PTX message 372 needs to be sent, rather than when the CD 352 starts to send media traffic. The value of the expired field is a configurable network parameter.

The CD 352 does not explicitly approve whether to accept the PTX message response 372. Instead, if the transmitted PTX message response 372 is missing, the CD352 push-to-talk (PTT) retransmission timer expires, and the CD 352 retransmits its push-to-talk (PTT) demand 370. Since the retransmitted push-to-talk (PTT) 370 has the same id as the missing PTX response 372, the signal initiation protocol (SIP) user agent server 252 responds by retransmitting the missing PTX message response 370 instead of sending The retransmitted push-to-talk (PTT) message demand 372 is regarded as a separate push-to-talk demand event.

The PTA message 374 is sent by the Signal Initiation Protocol (SIP) user agent server 252 to each CD 352 currently participating in a network to announce the identity of the source of pending media traffic. The PTA message 374 is also used to formally announce the end of a conversation phase.

The PTA message 374 contains fields such as opcode, caller, and reserved. The operation code field indicates whether the PTA message 374 announces whether to grant (or release) the speech of the CD 352 identified by the caller. The caller field identifies CD 352 until the next PTA message 374 is sent, which is the source of media traffic to the network. The reserved field reserves the space in the PTA message 374 for future functions.

A CD 352 with a successful push-to-talk (PTT) speech control requirement 370 may or may not have received a PTA message 374 to declare that it has speech control. The message may arrive before or after receiving the corresponding PTX response 372, because the user datagram protocol (UDP) does not need to preserve the datagram sequence. However, (in the case of a PTA grant announcement,) the signal initiation protocol (SIP) user agent server 252 first transmits the PTA announcement 374 before it wishes to start transferring the media. It is recommended that the requested CD 352 ignore the received PTA message 374, which declares that it has obtained speech control, and only depends on whether it receives a PTX grant message response 374 to determine whether it can start sending media to the network.

A "Are you there?" AYT message 404 (Figure 13) is sent from the Signal Initiation Protocol (SIP) user agent server 252 to another CD 352 to confirm that the CD 352 under consideration can use the Internet Protocol (IP )arrive. A set of AYT messages 404 can be sent to a group of network participants at the same time, so as to signal that a network is no longer in a standby mode.

An AYT message 404 contains fields such as opcode, id, and reserved. The operation code field indicates: whether the media control unit (MCU) node 208 sends an AYT message 404 to determine whether the CD 352 is still reachable, or whether the signal initiation protocol (SIP) user server 252 uses the AYT message 404 flow, The network and its related multi-directional proximity (CDMA) cellular traffic channel take away from the standby mode. The id field provides a unique message identifier, allowing a subsequent "I am here" IAH response message 408 to refer to a specific AYT demand message 404. The id may include a time stamp reference to generate latency estimates. The reserved field is used to reserve the space in the AYT message 404 for future functions.

When sending an AYT message 404, the CD 352 may or may not be in standby mode. In either case, the CD 352 can respond to a received AYT message 404 with an IAH response message 408.

The SIP user server 252 assumes that the CD 352 usually responds to an AYT message 404 with an IAH response 408. If an IAH response 408 is not received within a reasonable timeout, the SIP user agent server 252 transmits a new AYT message 404 with a new id. If after a configurable number of retransmissions, a response from CD 352 to AYT message 404 is not received, then it is assumed that CD 352 cannot be reached, and the Signal Initiation Protocol (SIP) user agent server 252 removes it from the current Remove from the list of network participants. The future media signaling messages from the removed CD352 will be ignored (or an error response will be generated) until the CD352 successfully rejoins the network.

The IAH message 408 is sent from the CD352 to the Signal Initiation Protocol (SIP) user agent server 252 to approve the acceptance of an AYT message 404 sent earlier. The IAH message 408 includes fields such as id, src, and reserved. The id field refers to an AYT message 404 received earlier that CD352 has approved. The scr field uniquely identifies the CD352, and is used to send the IAH message 408 response to the Signal Initiation Protocol (SIP) user agent server 252. The reserved field is used to reserve the space in the IAH message 408 for optional functions.

The SIP user agent server 252 assumes that the CD352 acknowledges all reserved AYT messages 404 with an IAH response message 408. If the referenced AYT message 404 is sent to confirm: a CD352 is still connected in the quiet state of the network broadcast service (NBS) to passively monitor the network broadcast service (NBS) media traffic and signaling, the signal is activated The SIP user agent server 252 will pay attention to the time when the IAH accepts 408 for future reference.

Since the signal-initiated protocol (SIP) user agent server 252 is responsible for defining the value of the id field, the signal-initiated protocol (SIP) user agent server 252 can use the id to determine and track whether a specific CD 352 is still reachable.

The ZZZ or sleep message (indicated by reference numeral 412 in FIG. 13) is sent to the CD352 by the Signal Initiation Protocol (SIP) user agent server 252 to encourage the CD352 to release its air resources and enter the standby mode. CD352 can choose to ignore this message (especially if it supports other packet applications at the same time).

The ZZZ message contains fields such as id and reserved fields. The id field provides a unique message identifier, allowing the CD 352 to distinguish multiple receptions of ZZZ messages. The reserved field is used to reserve space in the ZZZ message for optional or future functions.

CD 352 did not recognize the acceptance of ZZZ messages. If the ZZZ message is missing, usually no error recovery is attempted. To prevent the loss of a ZZZ message, the Signal Initiation Protocol (SIP) user agent server 252 can send multiple copies of the same ZZZ message to a separate CD 352. The Signal Initiation Protocol (SIP) user agent server 252 guarantees that copies of the same sleep message are sent within a defined interval, and the CD 352 receives (with a new id) before releasing its air link and changing to a standby state. When the first sleep message starts, it will wait for a period of time longer than this interval.

As illustrated in Figure 15, an ASK message 382 is sent from the CD 352 as a query 384 to the signal-initiated protocol (SIP) user agent server 252 for confirmation and the signal-initiated protocol (SIP) user agent Connectivity of server 252. The ASK message 382 also allows CD 352 to determine whether CD 352 is still listed as a participant. After a service interruption or other periods when the connection with the Signal Initiation Protocol (SIP) user agent server 252 may be temporarily lost, the CD 352 can confirm whether to participate.

The ASK message 382 contains fields such as id, src, and reserved. The id field provides a unique non-zero message identifier, allowing a subsequent FYI response message to refer to a specific ASK request message. The src field uniquely identifies the CD 352, where the CD 352 sends the ASK message 382 request to the signal-initiated protocol (SIP) user agent server 252. The reserved field is used to reserve the space in the ASK message 382 for optional or future functions.

The CD 352 assumes that the SIP user agent server 252 responds to a received ASK message 382 with a FYI response request 386. If a FYI response 386 is not received within a predetermined timeout period, the CD 352 transmits a new ASK message 382 with a new id. If after a configurable number of retransmissions, a response from the Signal Initiation Protocol (SIP) user agent server 252 to the ASK message 382 is not received, assume the Signal Initiation Protocol (SIP) user agent server 252 Unreachable, and CD 352 changed to a group service idle state.

The FYI message 386 is sent from the Signal Initiated Protocol (SIP) user agent server 252 to the CD 352 to acknowledge the acceptance of an ASK message 382 sent earlier, or is sent by the Signal Initiated Protocol (SIP) user agent server 252 Asynchronous transmission is used to notify the CD 352 of an unexpected situation.

The FYI message 386 contains fields such as opcode, action, status, id, and reserved. The operation code field defines whether the FYI message 386 is a synchronous response to an unprocessed ASK request 382, or whether it is an asynchronous message indicating an unexpected condition. Action field indication: Whether FYI message 386 has confirmed to participate in the network, inform CD 352: It has been administratively deleted from the network member list, or perform some other rejected functions. The status field provides additional information to explain the FYI response 386, especially when the FYI message 386 indicates that the CD352 is not a network participant or member. The id field refers to an ASK message 382 received earlier that the CD 352 has approved. Asynchronous FYI response is not defined in the value of the id field. The reserved field is used to reserve the space in the IAH message 408 for optional or future functions.

The CD 352 generally does not recognize the acceptance of the FYI message 386 response. If an asynchronous FYI message 386 response is missing, the CD 352 sends a new ASK message 382 request. Since the CD 352 does not require asynchronous FYI message 386 requirements, in a preferred embodiment, the Signal Initiation Protocol (SIP) user agent server 252 creates at least three interleaved transmissions of any asynchronous FYI message 386 responses.

A participating CD 352 sends a signal instruction: a user wants to broadcast the media to the network by sending a push-to-talk (PTT) message request 376 to the signal initiation protocol (SIP) user agent server 252. The signal-initiated protocol (SIP) user agent server 252 responds to a push-to-talk (PTT) request 376 with a PTX message response 378, which may grant or deny the request. If the demand is granted, a PTA announcement message 380 is broadcast to all network participants. The user interface of the requested CD 352 can indicate to the user that as long as the authorization of response 378 to the PTX message is received, the authorization has been granted to talk to the network. Normally, the CD 352 can broadcast media traffic until the user releases the push-to-talk (PTT) button. At this time, it releases a push-to-talk (PTT) to the SIP user agent server 252. Message 376, and a signal indicating that the conversation phase is over. The Signal Initiation Protocol (SIP) user agent server 252 responds with a PTX confirmation message 378 and broadcasts an announcement to indicate the end of the conversation phase to all network participants.

When any CD 352 has a network speech (that is, the right to talk), it means that the network is active, otherwise, it is inactive. If a network continues to be inactive for longer than the suspension time of the network, the signal initiation protocol (SIP) user agent server 252 can instruct all registered mobile stations to release their air traffic channels by individually signaling The network is arranged in standby mode. A connection will be maintained to allow a speech control demand or other traffic to bring the network out of standby mode faster. Network members can ignore the "to be used" message. The Signal Initiated Protocol (SIP) user agent server 252 does not explicitly or secretly track the standby status of individual network members.

As illustrated in Figure 15, when a successful speech control request 704 is received during the standby period, the Signal Initiation Protocol (SIP) user agent server 252 will "wake up" a network and take it out of the standby mode 618 . Once the speech control request 704 is granted, the Signal Initiation Protocol (SIP) user agent server 252 sends a signal to indicate each message by requesting the "are you there" (AYT) message 716 on the media signaling channel The CD 352 has been registered, and an internal wake-up timer 724 is started. If each CD 352 wishes to remain registered in the network, the signal initiation protocol (SIP) user agent server 252 accepts its AYT message 716. A standby CD 352 can start from the user keying in a push-to-talk (PTT) until the CD 352 flow channel (re)connects, selectively buffering and storing the media flow 740. The Signal Initiated Protocol (SIP) user agent server 252 can buffer and store the media traffic 740 received from the call CD 352 until the wake-up timer 724 exceeds the wake-up timeout, and then, at this time, it starts to forward the media traffic to Each registered CD 352 includes any members who have not yet responded to AYT demand 716. Therefore, CD Both the 352 and the media control unit (MCU) node 208 are capable of buffering and storing data until the recipient is ready to receive the buffered data. In a specific embodiment, the data part is stored in the CD 352 and the media control unit (MCU) node 208 at the same time.

The Signal Initiation Protocol (SIP) user agent server 252 periodically retransmits the AYT request 716 to any registered CD 352 that has not yet approved the acceptance of the AYT request 716. Once the wake-up timer 724 continues to expire after a second longer, the Signal Initiation Protocol (SIP) user agent server 252 deregisters any member CD 352 recognized by AYT as unprocessed, and stops the wake-up timerDevice724. The SIP user agent server 252 ignores the copied AYT request.

If the CD 352 attempts to join a network that is currently inactive, the Signal Initiation Protocol (SIP) user agent server 252 normally processes the request, and then signals the CD 352 to be inactive. The CD 352 that accepts the signal instruction can be ignored to the standby command.

During the period when the expanded network is inactive, the network broadcast service (NBS) allows a packet data service call to be placed in a standby/idle state 528 (see Figure 11). The Signal Initiated Protocol (SIP) user agent server 252 independently manages a similar stand-by concept of each NBS network 100 to facilitate transitions into and out of the stand-by/idle state 528.

FIG. 13 illustrates the media signaling message sequence related to the standby 400 between the CD 352 and the Signal Initiation Protocol (SIP) user agent server 252. Usually, according to a timer in each communication device (CD), a message is transmitted to all communication devices (CD) in the network according to a control signal from the communication manager (CM), and then it is ready for use. In this way, the resources allocated to the network will be released and can be used by other users. On a configurable schedule, the Signal Initiation Protocol (SIP) user agent server 252 sends a message request (AYT) 404 to each CD 352 to confirm that the CD 352 in a quiet state remains reachable. Therefore, the CM 104 maintains centralized polling of the current users of the network and their status. At the same time, individual communication devices (CDs) are allowed to dynamically join or leave the network. The CD 352 responds to the AYT request 404 with an information response (IAH) 408. The AYT message 404 need not be broadcast to every CD 352 at the same time. The Signal Initiated Protocol (SIP) user agent server 252 can stagger the AYT message 404 and send it to each network participant, avoiding receiving a large number of IAH message responses 408 at the same time.

After the network has been idle for a long time and the configurable suspension time of the network expires, the Signal Initiation Protocol (SIP) user agent server 252 broadcasts a ZZZ request message 412 to each network participant. In response, each CD 352 can release its air resources and enter the standby mode. The network participant does not necessarily have to respond to the ZZZ demand message 412.

A successful push-to-talk (PTT) request 416 from CD 352 takes the network out of standby mode. In a specific embodiment, it is necessary to respond to a predetermined number of users to bring the network out of the standby mode. Before granting the request with a PTX message 420, the Signal Initiation Protocol (SIP) user agent server 252 sends an AYT message request 424 to each CD 352 to force each CD 352 that participated earlier to leave the standby state. If the CD 352 chooses to release its air resources in response to the ZZZ message 412, and confirms that the participating CD 352 is still reachable, it is completed. In another specific embodiment, after a configurable but fixed delay, the Signal Initiation Protocol (SIP) user agent server 252 is deemed to be defined as a PTX standby response timer, and transmits the PTX grant request 420 to the request The CD352. Once the second wake-up timer (its value is usually not less than the PTX standby response timer) expires, the signal initiation protocol (SIP) user agent server 252 announces the caller to all network participants via a PTA message 428 , And can start transferring media.

The Media Control Unit (MCU) node 208 is responsible for receiving incoming data packets from the transmitting CD 352, and is responsible for transmitting copies of the received data packets to other members of the network to which the transmitting CD 352 belongs. When the media control unit (MCU) node 208 receives each data packet, it stores it in a memory (not shown). The transmitted CD352 can be identified by interrogating the data packet. In a specific embodiment, an Internet Protocol (IP) address representing the transmission communication device (CD) is included in each data packet as a way to perform identification.

After the transmitted CD352 is identified, the media control unit (MCU) node manager 256 retrieves a list of network members from the regional memory, the members of which belong to the network associated with the special media control unit (MCU) node 208 (usually every A media control unit (MCU) is only assigned to a network). A destination address is associated with each active network member in the local memory, that is, the network member currently registered on the media control unit (MCU) node 208. In a specific embodiment, the destination address is an Internet Protocol (IP) address. Then, the media control unit (MCU) node manager 256 creates a copy of the original data packet. In addition, the destination address identified in the data packet will be modified to reflect the destination address of the first network member. Secondly, the media control unit (MCU) 208 creates a second copy data packet, which is addressed to the second network member. This process will continue until the original data packets are recovered and sent to all active network members identified in the local memory. During the end of any buffer storage medium, the CM 104 regards the network as active, even if the talking CD 352 has released its speech. Therefore, the CM 104 does not allow a CD 352 to interrupt the end of the buffer storage medium unless the interrupted CD 352 has a higher priority than the source of the buffer storage medium.

Please note that after taking the network out of standby mode, the Signal Initiation Protocol (SIP) user agent server 252 can receive an extended interval of IAH message response 432 and grant pending push-to-talk (PTT) requests Before 416, the Signal Initiation Protocol (SIP) user agent server 252 did not wait for responses from all network participants. The last responder of the IAH response 432 that arrived after the transmission of the PTX grant message response 420 is still listed as a network participant, but may not be able to receive all the initial media traffic and signaling. It is generally assumed that any CD 352 that has not responded to the AYT request 424 after a third larger (and configurable) delay is no longer reachable, and it is removed from the list of active participants in the network.

FIG. 14 illustrates a series of network broadcast service (NBS) media signaling messages 440 for demonstrating that a higher priority CD 444 interrupts a lower priority CD 442 by using network speech control.

Initially, a lower priority CD 442 makes a push-to-talk (PTT) message request 446 to the signal-initiated protocol (SIP) user agent server 252, which is granted by the signal-initiated protocol (SIP) user agent server 252. The Signal Initiation Protocol (SIP) user agent server 252 announces that the CD 442 has Internet speech control.

When the lower priority CD 442 transmits the media 443, a second CD 444 attempts to send a push-to-talk (PTT) message request 448 of the same network to the signal-initiated protocol (SIP) user agent server 252. Interrupted. The Signal Initiation Protocol (SIP) user agent server 252 determines that the second CD444 has a higher priority than the calling CD442, and immediately cancels the network speech control from the calling CD442 by sending an asynchronous PTX rejection message 450. Then, the Signal Initiation Protocol (SIP) user agent server 252 responds 452 with a normal PTX grant message to the higher-priority CD444 grant push-to-talk (PTT) request 448, and announces that the higher-priority CD444 has a network Speech control.

If the Signal Initiation Protocol (SIP) user agent server 252 determines that the interrupted CD444 does not have a higher priority, the Signal Initiation Protocol (SIP) user agent server 252 immediately responds with a PTX message 452 to reject the PTT request 448, and Continue to distribute the media 456 from the call communication device (CD) to the network participants without interruption.

Although the priority assigned to a special communication device (CD) is a fixed value defined in the database maintained by the signal-initiated protocol (SIP) user agent server 252, the signal-initiated protocol (SIP) user agent server The device 252 can use other arbitration algorithms as described here, and it is not necessary to always grant speeches to the highest-priority participants. The push-to-talk (PTT) arbitration algorithm used to arbitrate conflicts can be individually configured on a network basis.

At the very least, the Signal Initiation Protocol (SIP) user agent server 252 supports an arbitration policy that allows the communication device (CD) to be interrupted only if the communication device (CD) has a priority level over the current caller The current caller. A communication device (CD) with the smallest priority can listen to the media traffic, but cannot obtain network speech control.

Figures 15 and 16 illustrate the operations of the CM 104 and the CD 352 during various states, respectively. The CM 104 maintains an inactive timer or suspended time timer 620 for each network. When the inactive timer 620 reaches a configurable predetermined value, the timer triggers the CM 104 to place the network in a standby state 618 by broadcasting a media signaling message 696 to all network participants. When receiving a message, a participating CD 352 can release its flow channel and enter a standby/idle state 844, or the CD 352 can ignore the message and maintain a connected state 820. Especially, network participants who are not operating on a channel, such as dial-up public switched telephone network (PSTN) users, should ignore the media signaling message.

During the influence period of a PTX grant message response 632, the suspension time timer 620 of the network does not advance. When the PTX grant message 632 is transmitted, the timer 620 is reset to zero and remains at zero until the PTX grant 632 expires or the CD 352 releases the network speech 872. Once the speech is released, the suspension timer will advance until the next PTX grant message response 632 is transmitted.

If a participating CD 352 enters the inactive/idle state 844, it remains inactive until the packet data addressed to the CD 352 reaches the CD 352MA cellular infrastructure, or the CD 352 generates data and uses the packet data service to transmit it. The former can be triggered by the flow of CM 104 (908) sent to CD 352. The latter can be triggered by allowing the user to key in a push-to-talk (PTT) button, and request permission for Internet broadcasting. It is also possible to use other triggers that are not related to the Internet Broadcast Service (NBS).

The network itself will remain inactive until one or more participants trigger the transmission of a push-to-talk (PTT) request 704. If the CM 104 decides that it can grant a push-to-talk (PTT) demand message 704 (including performing any necessary arbitration to handle multiple demands), it will send a demand 716 to each listed network participant to trigger The transition from the standby/idle state 844. For any particular CD 352, a trigger may or may not be required, but each CD 352 still responds to that demand. In this case, when a network transition leaves the standby state 618, the CM 104 suppresses and does not transmit the initial PTX grant response message 756 until a fixed but configurable delay, that is, the PTX standby response timer 728 expires. After the timer 728 expires, its default value is usually zero, and the CM 104 usually transmits the PTX grant 756. However, the CM 104 continues to refrain from transferring the media to the network until a second related timer, namely the Wake-on-LAN timer 724 expires. When the CM 104 decides that the standby network speech can be granted, the two timers will be reset. The value of the wake-up timer 724 should not be less than the value of the PTX standby response timer 728. After the wake-up timer 724 expires, the CM 104 starts to forward media and media signaling, and the traffic flows normally. Both timers can be configured on a per network basis.

If the CM 104 decides that it cannot grant a push-to-talk (PTT) request 704, it immediately signals the requested CD 352 with a PTX rejection message 708, while the network remains in standby.

A CD 352 that has entered the standby/idle state 844 can request the system to change to change the service options. Otherwise, if it experiences some other service interruption, it will no longer be able to receive and respond to the AYT "wake up" message 908. The CM 104 maintains a third-longest timer, which is also reset with the wake-up and PTX standby response timers. This longer successor timer (not shown) can also be configured on a per network basis. After the successor time expires, the CM 104 removes any CD352 that has not been received in the IAH response 916 in response to the AYT wake-up message 908 from the list of active participants in the network. Any such removed CD 352 re-registers with the CM 104's Signal Initiation Protocol (SIP) server 236 to become a network participant again.

Due to the potential delay associated with making a CD 352 transition out of the standby/idle state 844 and enter the connected state, both the CD 352 and the CM 104 can perform voice buffer storage to reduce the transition delay perceived by the user.

Generally, the CD 352 user interface signals the user through visual or auditory mechanisms that there are at least two milestones in a push-to-talk (PTT) button processing. First, the CD 352 signals to indicate that a push-to-talk (PTT) button has been detected. After that, the CD 352 signals to indicate that the PTX message response 868 from the CM 104 has been received. If the PTX message responds to the 868 granting permission to broadcast media, the CD 352 user interface provides an instruction indicating that the user can start talking to the network; otherwise, the CD 352 user interface indicates that permission has been denied (856) user Talk to this network.

When the network is not in use, the latency between transmitting a push-to-talk (PTT) demand message and receiving the corresponding PTX response message is relatively small, and users are getting accustomed to typing in a push-to-talk (PTT) button and getting the authorization only Short talks are allowed. However, when the network is standby, a relatively significant delay separates the transmission of a push-to-talk (PTT) request 852 from receiving the corresponding PTX message 856 or 868. The delay may occur because the CD 352 has released its traffic channel and experienced a delay in the process of rebuilding the packet data service. At the same time, a delay may occur because the CM 104 has been waiting until the wake-up timer of the network expires before sending the PTX message response 856 or 868. In this case, the CD 352 can optimistically assume that the CM 104 finally responds with a PTX grant response 868, and signals the user that the push-to-talk (PTT) request 876 has been granted. In order to allow the user to start speaking "early", the CD 352 internally buffers and stores the voice until the PTX demand is reached, or all available internal buffer space is consumed.

If the PTX message response arrives and the demand is granted, the CD 352 can start to transmit (buffer stored) voice, and proceed normally. If the PTX message response arrives and the demand is rejected, the CD 352 signals to the user that it has refused permission to talk to the network. Since the user has already started the call, subsequent rejections may violate its priority. In this case, special attention should be paid to avoid unnecessary confusion for users. Under the assumption that the unprocessed push-to-talk (PTT) demand will eventually be granted, the CM 104 will signal the PTX rejection message 856 as soon as possible if it is possible to limit the length of the user's talk time.

If the PTX message has not arrived before all available internal buffer space is exhausted, the CD 352 can simulate a PTX rejection message 856 and signal the user to stop the call (856). If the CD 352 has been unable to rebuild the service, other wrong actions may need to be taken at the same time, and the user will then be notified. Alternatively, if the packet data service has been re-established before this time, the CD 352 can start to transmit the voice media to the CM 104 in this situation without first receiving a PTX grant message response 868.

While waiting for the wake-up timer to expire, the CM 104 buffers and stores any voice media received on a network media channel from a CD 352, where the CD 352 previously sent an unprocessed push-to-talk (PTT) request 852, and finally sent a The corresponding PTX grant response 868. Once the wake-up timer expires, the CM 104 transmits the PTX grant response 868 to the requested CD 352, broadcasts a PTA announcement to the network, and starts broadcasting the buffered voice media. If the internal voice buffer of the CM104 is exhausted before the wake-up timer expires, the CM104 immediately transmits a PTX rejection message 856 to the requesting CD352. Although the processing of the buffered voice is not defined, after the wake-up timer expires, the CM104 can transmit the content in its voice buffer to the network. Once the wake-up timer expires, network operations proceed normally.

The size of the voice media buffer in CD352 is selected based on the expected maximum time for transition from IS-707.5 inactive/idle state 844 to IS-707.5 connected state 812. Similarly, the size of the media buffer in the CM104 should be selected according to the (maximum) value of the Wake-on-LAN timer specified in the CM104 network database 232.

The following is a more complete description of the status of CM104. The CM 104 implements a network broadcast service (NBS) media signaling state diagram 600 as shown in FIG. 15 in each instance of a network. When a network is established, the CM 104 is initialized to an idle state 604. The network may remain idle 604 because there is no push-to-talk (PTT) 608 requested by the network participant, and obtain the granted speech control 612 and become non-standby 616. When entering the idle state 604, the CM 104 resets the suspension time timer 620 to zero. When receiving a push-to-talk (PTT) request 608 from a network participant, the CM 104 transitions from the idle state 604 to the authorized state 612. When the suspension time timer expires, the CM 104 transitions from the idle state 604 to the standby state 624.

If the arbitration algorithm rejects the speech control of the requested CD 352, the CM 104 transitions from the granted state 612 to the idle state 604, and transmits a PTX rejection 626 response to the requested CD 352. If the arbitration grants the requested (or interrupted) speech control of the CD 352, the CM 104 transitions from the grant state 612 to the announce state 628, and transmits a PTX grant response 632 to the requested CD 352. After transmitting the PTX grant response 632, the CM104 regards the requested (or interrupted) CD352 as the current caller of the network. Immediately after entering the announcement state 628, the CM 104 transitions from the announcement state 628 to the call state 636, and transmits a PTA message 640 to all network participants to announce the new caller. As long as the push-to-talk (PTT) request 644 or release message 648 from a network participant is not received, and the fail-safe timer 652 of the network has not expired, the current caller remains in the conversation state 636. When entering the call state 636, the CM104 resets the fail-safe timer 652 of the network. In the call state 636, the CM104 broadcasts media from the current caller to the network.

When receiving a push-to-talk (PTT) request message 644 from a network participant, the CM 104 changes from the talking state 636 to the arbitration state 656. When receiving a push-to-talk (PTT) release message 648 from the CD352 with network speaking control, the CM 104 changes from the talking state 636 to the release confirmation state 660. When the fail-safe timer 652 expires, the CM 104 transitions from the talking state 636 to the fail-safe recovery state 664. Before the fail-safe timer expires, the user is usually given a remaining amount of time. When the call is on hold 636, the CM104 broadcasts the received media traffic from the current caller to the network. If the media buffer of the network is not blank, when the media traffic is broadcast to the network, the CM104 continues to buffer and store the media received from the current caller on the network.

In the talking state 636, if a push-to-talk (PTT) request message 644 is received, the result is that the CM 104 enters the arbitration state 656. The CD 352 of the PTT request message 644 is called an interrupt participant. If the interrupted participant is the same as the current caller, the CM 104's PTX grant message 668 will be lost, and the current caller retransmits his push-to-talk (PTT) request 644. If the interrupted participant is the same as the current caller on the network, the CM 104 transitions from the arbitration state 656 to the talking state 636, and transmits the PTX grant message 668 to the interrupted participant. If the interrupted participant is different from the current caller on the network, after entering the arbitration state 656, the CM 104 applies the arbitration algorithm to the current caller and the interrupted participant of the network.

If the arbitration algorithm verdict supports the current caller, the CM 104 transitions from the arbitration state 656 to the call state 636, and sends a PTX rejection message 672 to the interrupted participant. If the decision of the arbitration algorithm supports interruption of participants, the CM 104 transitions from the arbitration state 656 to the grant state 612, and sends a PTX interruption message 676 to the current caller on the network. Immediately after entering the release announcement state 680, the CM 104 changes from the release confirmation state 660 to the release announcement state 680, and sends a PTX confirmation message 684 to the current caller.

Immediately after entering the fail-safe recovery state 664, the CM 104 transitions from the fail-safe recovery state 664 to the release announcement state 680, and transmits a PTX rejection message 688 to the current caller. Immediately after entering the release announcement state 680, the CM 104 transitions from the release announcement state 680 to the idle state 604, and transmits a PTA release announcement 692 to all network participants. A moment after entering the "into-standby" state 624, the CM 104 transitions from the in-standby state 624 to the inactive state 618, and sends a ZZZ message 696 to all network participants to announce that the network has entered standby . As long as no network participant requests speech control, the state machine of the network remains in a standby state 618. When receiving a PTT request 704 from a network participant, the CM 104 transitions from the inactive state 618 to the awake state 706.

If the arbitration algorithm rejects the speech control of the requested CD 352, the CM 104 transitions from the awake state 708 to the best state 618, and transmits a PTX rejection response 708 to the requested CD 352. Since the network is inactive, it can only happen when the requested CD 352 has listening-only privileges. If the arbitration grants the required speech control of the CD 352, the CM 104 transitions from the wake-up state 706 to a wake-up pending state 712, and transmits an AYT wake-up request 716 to all network participants. After sending the AYT wake-up request 716, CM104 treats the requested CD 352 as a pending caller on the network.

As long as the PTT demand message 720 from a network participant is not received, a wake-up timer 724 has not expired, and a PTX standby response timer 728 has not expired, the CM 104 maintains the wake-up pending state 712. When entering the wake-up pending state 712, the CM 104 resets the wake-up timer 724 and the PTX standby response timer 728. When receiving a push-to-talk (PTT) request message 720 from a CD 352 that is different from a pending caller on the network, the CM 104 changes from the wake-up pending state 712 to the standby arbitration state 732. When the wake-up timer 724 of the network expires, the CM 104 transitions from the wake-up pending state 712 to a standby grant state 736. When the PTX standby response timer 728 expires, the CM 104 transitions from the wake-up pending state 712 to a buffer storage grant state 740.

Immediately after entering the standby arbitration state 732, the CM 104 applies the arbitration algorithm to the pending callers and interrupted participants of the network. If the arbitration algorithm verifies that the pending caller is supported, the CM 104 transitions from the standby arbitration state 732 to the wake-up pending state 712, and transmits a PTX rejection message 744 to the interrupted participant. If the arbitration algorithm decides that it supports interrupting the participant, the CM104 transitions from the standby arbitration state 732 to the wake-up pending state 712, transmits the PTX rejection message 744 to the pending caller, and treats the interrupted participant as a new pending call for the network Caller.

Immediately after entering the standby grant state 736, the CM 104 transitions from the standby grant state 736 to the announce state 628, and transmits a PTX grant response 748 to the pending caller on the network. When entering the buffer storage grant state 740, the CM 104 transitions from the buffer storage grant state 740 to a buffer storage state 752, and sends a PTX grant response 756 to the pending caller on the network. As long as the wake-up timer 724 has not expired, the state machine of the network maintains the buffer storage state 752. In the buffer storage state 752, the CM 104 buffers and stores any media traffic received from pending callers on the network.

When the wake-up timer 724 expires, the CM 104 transitions from the buffer storage state 752 to the announce state 628. In the buffer storage state 752, the CM 104 buffers and stores any media traffic received from the pending callers on the network in the media buffer of the network. The CM 104 responds to any media signaling request that includes invalid or reserved field values by sending an error response 760 to the CD 352 that sent the message in an error state 764, or ignores the request.

When a user joins a network, the CD 352 implements the network broadcast service (NBS) media signaling state diagram 800 shown in FIG. 16. After the CD 352 sends a signal activation protocol (SIP) ACK message 808 to the CM 104 and accepts the description of the network conversation, the CD 352 is initialized to the active state 804. Immediately after entering the activated state 812, the CD 352 transitions from the activated state 804 to the start-up waiting state 812, and sends an ASK request message 816 to the CM 104.

As long as the user does not press the button-to-talk button 824, does not receive the PTA message 828 from the CM104, and does not receive the sleep ZZZ message 832 from the CM104, the CD352 remains in a listening state 820. When the user presses the button 824, the CD 352 changes from the listening state 820 to a speaking demand state 836. When receiving the PTA message 828 from the CM 104, the CD 352 changes from the listening state 820 to a caller announcement state 840. When receiving the sleep ZZZ message 832 from the CM 104, the CD 352 changes from the listening state 820 to a standby idle state 844. Immediately after entering the speech demand state 836, the CD 352 changes from the speech demand state 836 to a speech waiting state 848, and transmits a push-to-talk (PTT) grant request 852 to the CM 104.

As long as the PTX response message 856 from the CM 104 is not received, and the one-push-to-talk (PTT) termination timer 860 has not expired, the CD 352 remains in the speaking waiting state 848. When entering the speech waiting state 848, the CD352 resets its push-to-talk (PTT) suspension timer 860 and one-push-to-talk (PTT) retransmission timer (not shown). When receiving a PTX grant 868 response message from the CM 104, the CD 352 transitions from the speaking waiting state 848 to a talking state 864, and informs the user that it has been granted network speaking control. When receiving the PTX rejection message 856 from the CM 104, the CD 352 changes from the speech waiting state 848 to a speech loss state 872. After the push-to-talk (PTT) retransmission timer expires, the CD352 remains in the speaking waiting state 848 and retransmits the same push-to-talk (PTT) request 876 to the CM 104. After the push-to-talk (PTT) termination timer 860 expires, the CD 352 transitions from the speaking waiting state 848 to the listening state 820. While still waiting for a PTX response, if the user releases the button call button 884, the CD 352 changes from the call state 864 to a speech release state 880.

As long as the PTX interrupt message 888 from the CM 104 is not received, and the user has not released the button call button 884, the CD 352 remains in the call state 864. When receiving the PTX interrupt response message 888 from the CM 104, the CD 352 changes from the talking state 864 to the speech loss state 872. When the user releases the button talk button, the CD 352 changes from the talking state 864 to the speaking release state 880. When receiving the PTX grant response message 868 from the CM 104, the CD 352 remains in the talking state 864. Immediately after entering the speech loss state 872, the CD 352 changes from the speech loss state 872 to the listening state 820, and warns the user 892 with a message indicating that the control of the network speech has been lost.

Immediately after entering the speaking request state 836, the CD 352 changes from the speaking release state 880 to a release waiting state 896, and transmits a push-to-talk (PTT) release request 900 to the CM 104. As long as the PTX confirmation response message 904 from the CM 104 is not received, and the push-to-talk (PTT) termination timer 860 has not expired, the CD 352 remains in the release waiting state 896. When entering the release waiting state 896, the CD 352 resets its push-to-talk (PTT) suspension timer 860 and one-push-to-talk (PTT) retransmission timer. Each time a push-to-talk (PTT) is requested or released, a push-to-talk (PTT) retransmission timer is started.

When receiving the PTX confirmation response message 904 from the CM 104, the CD 352 changes from the release waiting state 896 to the listening state 820. After the push-to-talk (PTT) retransmission timer expires, the CD352 remains in the release waiting state 896, and retransmits the same push-to-talk (PTT) release request 900 to the CM104. After the push-to-talk (PTT) termination timer 860 expires, the CD 352 transitions from the release waiting state 896 to the listening state 820.

Immediately after entering the caller announcement state 840, the CD 352 changes from the caller announcement state 840 to the listening state 820, and announces the caller. This announcement may indicate: a new caller has speech control, the current caller has released his speech, or no caller currently has speech control.

As long as the AYT demand message 908 from the CM 104 is not received, and the user does not press the button call key 824, the CD 352 remains in the standby idle state 844. When receiving the AYT demand message 908 from the CM 104, the CD 352 transitions from the standby idle state 844 to the standby wake state 912. When the user presses the button call key 824, the CD 352 changes from the standby idle state 844 to the speaking demand state 836.

In the standby idle state 844, the CD 352 discards any sleep ZZZ message 916. Immediately after entering the standby wake-up state, the CD 352 transitions from the standby wake-up state 912 to the listening state 820, and sends an IAH response message 916 to the CM 104.

When receiving an AYT ping request 920 from the CM104 in any state other than the standby idle state 844, the CD352 saves its current state, temporarily changes to an IAH reply state 924, creates and sends an IAH response message 928 to the CM104, And return to its previous state. When receiving a media signaling error and entering an error state 936, the CM 104 transmits an ERR response 932 to the CD 352, such as a disguised demand for using invalid or reserved field values.

When receiving the ERR response 932 from the CM 104 in any state, the CD352 warns the user that an error has occurred, disables the CD 352 (940), and executes any appropriate signal initiation protocol (SIP) signaling to end it calmly Join the network (944).

When the CD 352 enters one of the standby states (844), the CD 352 can receive peer-to-peer voice service traffic via another IS-707 service option, but is still a participant of a standby network. After the voice service traffic is terminated, the CD 352 switches back to the IS-707.5 standby/idle state 844.

However, if the network leaves the inactive state 844 when the CD 352 chooses to receive the point-to-point voice service option traffic, the CD 352 may miss the AYT "wake up" message request 908 and be removed from the active participant list. In this type of example, the CD 352 can determine its participant status by sending an ASK request 382 to the CM 104. Once the CD 352 is removed from the list of active participants in the network, the CD 352 re-registers with the CM 104 signal-initiated protocol (SIP) server to participate in the network again.

CD 352 allows users to initiate and receive traditional public switched telephone network (PSTN) point-to-point traffic and participate in group service discussions. Although the CD 352 can operate internally in one of several modes, the CD 352 avoids restricting certain functions in the context of different operating modes that the user needs to clearly operate. Therefore, when the group service is enabled and activated, it is necessary to seamlessly receive and arrange the point-to-point voice service traffic.

As long as the CD 352 does not become a caller at the same time, regardless of whether the group service is currently in use, the CD 352 can arrange point-to-point voice services or secure point-to-point packetized voice traffic at any time. If the CD 352 is already registered as a member of a network, then the CD 352 is unregistered from the network. If the selected point-to-point traffic is arranged via a voice service option, the CD 352 terminates the data service. Once the point-to-point traffic is completed, CD 352 can naturally enable packet data services and register as a member of the currently selected network.

Within the restrictions imposed by the cellular infrastructure, when the group service is enabled, the CD 352 can be used to receive the public switched telephone network (PSTN) or secure point-to-point packetized voice traffic. If CD 352 joins a network, and the selected network is active, CD 352 seems to be busy with an incoming public switched telephone network (PSTN) traffic, and the cellular infrastructure will give the traffic proper busy handling . If the selected network is quiet, but the suspension time 620 of the network has not expired, the cellular infrastructure is also used to give the traffic busy processing. However, if the suspension time 620 of the selected network has expired, the network has been arranged in the standby mode 618, and the CD 352 has released its air resources, the traffic may not be busy handled by the infrastructure, and it can be Call CD 352 to initiate the acceptance of incoming traffic.

When a voice service traffic is active, the CD 352 cannot receive any network broadcast service (NBS) network traffic. After the completion of a voice service call, if one or more AYT requests 716 may have been missed, the CD 352 may be requested to rejoin the network. Whenever the CD 352 seems to be busy with an incoming voice service call, according to the cellular infrastructure, define any busy processing (such as traffic forwarding, voice mail, etc.) desired by the called CD 352, and redirect the Caller. When a network is selected and the CD 352 is registered as a member, a user can optionally configure the CD 352 to be able to accept point-to-point calls.

CD 352 also detects whether its Internet Protocol (IP) network address has been or will be changed. As discussed with reference to FIG. 11, if the CD 352 joins a network when the address changes, the CD 352 invites itself to join the network again.

For example, a roaming CD 352 can exchange cellular systems or cellular networks to negotiate a new Internet Protocol (IP) network address. Otherwise, the CD 352 may experience a service interruption or discard the packet data service option traffic for any reason, and obtain a new Internet Protocol (IP) network address assigned when the service is rebuilt. If the CD 352 participates in a network during the period of an address change and does not re-join the selected network in time, the final membership of the CM 104 will expire, and the CD 352 will be removed from the list of the selected network. If the CD 352 does not respond to a series of media signaling AYT request messages 716 at the end, it is removed from the list of active network participants.

When the IS-707.5 packet data service option does not appear, the Internet Broadcast Service (NBS) can operate on the existing and commonly available Quick Internet Connection (QNC) packet service. However, Quick Internet Connection (QNC) is currently not supported for use. Therefore, application layer messages like "to be used" can be ignored by operating a network broadcast service (NBS) on a fast network connection (QNC) with a CD 352.

QNC does provide a protocol stack similar to that provided by IS-707.5. The CD 352 can be configured to negotiate a packet connection using Quick Network Connection (QNC) instead of IS-707.5, and if the Quick Network Connection (QNC) service is available, the connection will be treated as a packet data service option The connection does not need to be ready for use, or alternatively, compression real-time protocol (CRTP) header compression support is optional.

In the case of mobile Internet Protocol (IP), the CD 352 is connected to use a foreign agent network, where the foreign agent assigns a forwarding address to the mobile station. The forwarding address is a temporary but legal address that can be used to address Internet Protocol (IP) data reports from anywhere on the Internet. The mobile station uses the forwarding address to connect to its initial agent, and informs the mobile station of the current forwarding address. After confirming the identification of the mobile station, the initiating agent then uses the forwarding address of the mobile station to send the packet address to the mobile stations permanent starting address (by a normal Internet routing agency) Direct delivery to the originating agent, or delivery to the originating agent network).

Although NBS can operate on mobile Internet Protocol (IP), mobile Internet Protocol (IP) may potentially adversely affect end-to-end latency and perception of NBS media traffic And the voice quality of signaling. If CD 352 uses its permanent address to join a network, and the location of the initiating agent is far away from CM 104 and CD 352, this will have special significance from the perspective of network topology. In this case, the media traffic can be selectively routed on the public Internet or various other qualities of the service network. If the mobile Internet protocol (IP) is not used, it is not required. To avoid this, it is better that the CD 352 uses its forwarding address to access the network broadcast service (NBS), and when its forwarding address changes, it rejoins the network.

Signal-initiated protocol (SIP) traffic signaling and good privacy (PGP) public key encryption use a unique CD 352 user identifier, or a similar unique identifier. The user database 232 defines an internal user identifier, which can be forwarded to the CD 352, and the CD 352 uses it for media signaling requirements. Preferably, the CD 352 user ID address does not contain any private data, and the public disclosure of the private data may include an existing cellular infrastructure certification authority.

The CD 352 user address is used in the header of the Signal Initiation Protocol (SIP) registration and invitation, and can be used to form other parts of the required Signal Initiation Protocol (SIP) syntax. The user address is at the same time an input for generating a private good privacy (PGP) key used to authenticate the signal activation protocol (SIP) requirement. The CD 352 user interface allows users to view user addresses. The CD 352 user interface allows the user to change the user address at the risk of interrupting the ability to access the Internet Broadcast Service (NBS) or meeting the signal-initiated protocol (SIP) authentication requirements.

In order to prevent certain service intrusive denials and prevent CD 352 from disguising, before registering or joining a network, CM 104 can optionally request CD 352 to be authenticated. Authorization is executed at the application layer and is independent of other authorization schemes existing at the network or cellular infrastructure level. The implementation and operation of CD 352 authorization are independent of the concept and data structure of supporting encrypted (security) network broadcasting service (NBS) network.

In particular, the CM 104 may require the CD 352 to include an "authorization" header with its Signal Initiation Protocol (SIP) requirements. The authorization header considers a signal-initiated protocol (SIP) message signed by the CD 352 using a good and private (PGP) public key cryptography signature.

Public key cryptography uses a private secret key to generate a public and private key, where the private secret is usually only known by the encryptor (CD 352 in this case). To sign a message, a dedicated key combined with the secret key is required, but the public key can only be used to verify the signature of a signed message. Therefore, to support SIP authorization, preferably, each CD 352 is equipped with a private secret and a dedicated golden key, and it is not shared. The CD 352 to be connected must know the public key of the CD 352 for each CM 104 to be authorized. Since the public key is not secret, it can be stored as a part of the user part of the database 232 maintained by the CM 104, or accessed through a general public key server on the Internet.

CM 104 can request CD 352 authorization at the server, network, or user level. At the server level, the CM 104 requires all clients connected to the CM 104's Signal Initiation Protocol (SIP) server 236 (see FIG. 3) to provide authorization certificates, and reject all unauthorized requests. When the server-level authorization is enabled, only customers whose CM 104 has previously known their identity (that is, the customer's public key) can effectively use the server. Server-level authorization can protect the CM 104 Signal Initiation Protocol (SIP) server 236 from many relatively easy service intrusive denials.

A CM 104 can protect one or more networks it manages through authorization, while leaving other networks "unprotected". If the CD 352 attempts to invite itself into a protected network, the CM 104's Signal Initiation Protocol (SIP) server 236 rejects the request, unless the CD 352 can be authorized by the CM 104.

At the same time, CM 104 can use authorization to ensure that CD 352 (or any general signal initiation protocol (SIP) user agent client) will not try to pretend to be another CD 352, thereby denying service to legitimate network participants, or passively monitoring a network The media channel of the road. If CM104 requires a specific CD352 to be authorized, CM104 will not accept any Signal Initiation Protocol (SIP) requirements from a client connected as CD352, unless the clients Signal Initiation Protocol (SIP) requirements include one that can be verified by CM104 Good and Private (PGP) signature. At the user level, authentication can be configured on a per-user basis (that is, before allowing other users to remain unauthenticated, CM104 can require certain users to be authenticated).

Once the CD352 user address is defined, the PGP special golden key can be provided administratively or created by CD352. The dedicated key does not need to be stored externally, but the related public key can usually be loaded into the user part of the database 232 of any Signal Initiation Protocol (SIP) server that requires CD352 authentication.

In a specific embodiment, the main network broadcast service (NBS) CD352 or participant platform is a CD352MA cell phone. Because the Internet Broadcast Service (NBS) is based on the Internet Protocol (IP) and Internet Protocol (IP) transmission protocols, the Internet Protocol (IP) compatible platform connected to the CM104 can also be used as a network Broadcast Service (NBS) CD352. Therefore, as illustrated in Figure 1, dial-up users can access the public switched telephone network (PSTN) through the existing Internet Protocol (IP) terminal server operated by the Internet Service Provider (ISP) , And connect to CM104. The terminal server acts as a bridge between the public switched telephone network (PSTN) and the Internet Protocol (IP) supported by a local area network (LAN). The terminal server includes a row of modems to provide a high-speed public switched telephone network (PSTN) modem, a server, and a connection point for one or more network interfaces. The server can host multiple independent point-to-point protocol (PPP) dialogs, which are individually related to each connected modem user. The server also acts as a router, routing Internet Protocol (IP) packets between each individual point-to-point protocol (PPP) interface and any active local area network (LAN) interface. The CM 104 may include an integrated (or deployed in conjunction with an external) commercial storeless terminal server.

The dial-up terminal server supports and includes the ability to negotiate compression of real-time protocol (CRTP) header compression in its Point-to-Point Protocol (PPP) dialogue. Similarly, a point-to-point protocol (PPP) stack used by a dial-up client also includes and attempts to compress the real-time protocol (CRTP). However, because of the extra bandwidth available in high-speed modems, if a dial-up user cannot negotiate compression of real-time protocol (CRTP) header compression, there is no need to force a network to avoid using real-time protocol (RTP)-based rewards. Load specifications.

If the terminal server is located on the CD 352MA service providers internal area network, and from a network topology point of view, it is close to the service providers CM 104, then it will be located between the Internet service provider (ISP) terminal server When the path between the device and the CM 104 traverses a part of the public Internet, dial-up users can avoid service quality problems caused by increased end-to-end latency. Since the public switched telephone network (PSTN) modem usually does not support a stand-by concept similar to that implemented in IS-707.5, the dial-up network participant ignores any sleep messages received from the CM 104. Although the user database 232 tracks whether a connected user is cellular or terrestrial, this device still provides it. Therefore, it may or may not be possible for CM104 to send sleep or other media signaling messages to dial-up users.

The network broadcast service (NBS) service area will be designed to integrate allowing users to roam between service areas and join equivalent networks defined in separate service areas. The inter-level communication between multiple CM104 takes the form of Signal Initiation Protocol (SIP) server redirection, user and network database record exchange, and an integrated network broadcast service (NBS) service-specific additional information.

In a specific embodiment of an integrated network broadcast service (NBS) service, it is preferable to allow any CM 104 to assume ownership of a network. Therefore, the operation of a network is not unique to a special CM 104 or a media control unit (MCU) node 208. The choice of CM104 can be dynamically determined based on factors such as the proximity of most mesh participants and the quality of services available on the network between a service provider system. Similarly, any signal-initiated protocol (SIP) redirection server 236 can redirect any CD352 to the appropriate media control unit (MCU) and its signal-initiated protocol (SIP) user agent server, and/or as If necessary, the CD352 is forwarded to another Signal Initiation Protocol (SIP) to redirect the server.

In a specific embodiment of an integrated network broadcast service (NBS) service, the network address of a network is meaningful in the entire network broadcast service (NBS) system. As a result, one or more top-level Signal Initiation Protocol (SIP) servers 236 are responsible for redirecting the invitation request and assigning network participants to the appropriate media control unit (MCU) node 208. The top-level Signal Initiation Protocol (SIP) server 236 can share a common user and network database 232 to provide similar functions and redirect decisions at different network meeting points. As a result, re-directing the CD352 originating invitation provides an important and critical abstraction layer that allows multiple CM104 installations to be integrated into a single homogeneous network broadcast service (NBS) service.

In an integrated network broadcasting service (NBS) service, the system is scaled by replication functions, where these functions are managed by the media control unit (MCU) node manager 256, and its related media control unit (MCU) 252 is set (relaxed) Called an "MCU cluster"), including its Signal Initiation Protocol (SIP) user agent server. A single database 232 and administrative interface 248 are shared by all elements of the system.

Essentially, the process used by a CD352 to join a network in this type of integrated system is the same as the process used by a system to install a single CM104. The CD 352 initially transmits all the signal-initiated protocol (SIP) requirements to the top-level (now global) signal-initiated protocol (SIP) to redirect the server 236. The redirection server 236 redirects the requested CD 352 to an appropriate destination via a signal activation protocol (SIP) mechanism. If the situation is an invitation request to join a network, the destination is the signal initiation protocol (SIP) user agent server 252 related to the media control unit (MCU) node 208 currently in charge of the network under consideration. If the situation is: an invitation request from a current network list available to the requested CD352, the destination is any user agent that can respond to the request.

The redirection server 236 can exchange additional messages with the media control unit (MCU) 252 through inter-application communication, using specific protocols, and/or communication conventions. When the situation is non-integrated, a special activation action is required to ensure that the redirection server 236 can determine a destination for each legal invitation it receives. A specific embodiment has a Signal Initiation Protocol (SIP) registration, which exists in the top-level redirect server 236. At the same time, the top-level server can query the system database and try to map each invitation request to a network definition contained therein.

CD 352 can provide encrypted Internet broadcast communications. In the network user option, the voice and data transmitted on a special network can be encrypted on the transmitted CD 352 and decrypted by all other communication devices (CD) on the network. Encryption is end-to-end, that is, from one communication device (CD) to another communication device (CD). Network communications are usually encrypted by a commercial encryption algorithm incorporated in a network broadcasting service (NBS) compatible communication device (CD). A CD 352 treats a network as the choice of encryption or decryption depends on the network user's choice; that is, CM 104 is not included.

Users can choose to encrypt/decrypt and transmit/receive traffic on the network based on the network. The user obtains a way to enter an encryption key for the network to use, such as a telephone keypad. Therefore, the user can engage in encrypted communication with other users on the network, and these other users also select the encryption option of the network and use the same encryption key at the same time.

The user can enable or disable the network traffic encryption of any network key entered by the user at any time of the CD 352. Media traffic can be symmetrically encrypted by using a symmetric golden key (a traffic encryption key, or TEK) shared by network users. The network traffic encryption key can be generated offline by a network user or network administrator, and then safely distributed to network participants, and the key can be manually entered into their individual communication devices. The key is used for media traffic of a special network until a new key is generated and distributed to network users to replace the previous network TEK.

CD 352 is notified by the message received from CM 104: it is a member of a special network. The network administrator of a special network can set a warning flag indicating that the network may be encrypted. This instruction is usually advisory, not necessarily authoritative: communications on the network are actually encrypted. The CD352 user interface allows a user to designate any network as an encrypted network, and allows the user to enter the network TEK from the CD 352, independent of whether the CM 104 receives an encrypted warning flag for the network.

CD 352 can force the minimum and maximum key length. CD 352 can provide a method for checking and inputting a golden key together with the golden key. If it is provided, check the checksum against the input golden key. If the check sum is not entered, the CD 352 calculates the check sum and displays it to the user. After entering the initial golden key, the CD 352 does not need to display the golden key on the CD 352 display.

Once a golden key is successfully entered into a given network, the media transmission on the network is encrypted with the special golden key, and all the traffic received on the network is decrypted with the special golden key. Encrypted traffic includes additional headers that allow CD 352 to synchronize encryption/decryption procedures to account for subsequent synchronization (synchronization with a transmission that is already in progress), and to confirm that the sender and receiver use the same traffic encryption key, spoon. If a CD 352 receives encrypted traffic on a network (detected by the presence of an encryption header) but is not designated as encrypted, the CD 352 indicates that it has received the encrypted traffic to the user, but does not output the Flow rate (to eliminate audio frequency, or suppress data output). Similarly, if CD 352 receives media traffic that is configured to be encrypted but not encrypted on a network, or if the traffic is not decrypted correctly (for example, if the key is incompatible), CD 352 warns the user, and Eliminate this flow.

The golden key of an encrypted network can simply be a random (binary) number. Generally, the golden key is generated by a party on a network or an administrator on the network, and is securely distributed to network participants. Since the key distribution policy is currently reserved for network users, it is a potential source of network security compromises. Therefore, it is recommended: Use a security method such as PGP encrypted emails to distribute the network encryption key to the network participants. The security administrator 20 (Figure 1) also provides a central repository for the common network key. It may also be other methods, such as a standard telephone call, or a face-to-face meeting. At the same time, it is possible to use a buried good privacy (PGP) secret golden key in a communication device, and automatically distribute the golden key to the communication device (CD) for signal initiation protocol (SIP) authentication.

The previous description of the preferred embodiments is provided to enable those skilled in the art to make or use the present invention. Those skilled in the art will be able to quickly understand the various modifications of these specific embodiments, and can apply the general principles defined here to other specific embodiments without using inventive talent. Therefore, it is not intended to limit the present invention to the specific embodiments shown here, but to comply with the widest scope consistent with the principles and novel features disclosed herein.

Other features and advantages of the present invention are stated in the scope of the following patent applications.

Component symbol comparison table

10 Network Broadcasting Service (NBS) 12, 14, 16, 17 Communication Device (CD) 18, 104 Communication Manager (CM) 20 Security Manager (SM) 22 Base Station 24 Gateway 26 Distributed Network 28 Mobile Switching Center ( MSC) 30 Public Switched Telephone Network (PSTN) 32 Modem Memory 34 NBS Terminal 100 NBS Network 108, 112, 116, 352 Communication Device (CD) 120 Dialogue Initiation Protocol (SIP) Channel 124 NBS Media Signaling Channel 128 Media Traffic Channel 204 CM Core Composite 208 Media Control Unit (MCU) node 212 MCU node 2216 DNS server 224 Administrative workstation 228 CM node 229 SIP invitation message 232 Database layer (user part and network part) 236 SIP UAS server (redirect/ Top layer) 240 CM manager 244 Central accounting log server 248 Administrative server 252 MCU-SIP UAS server (second layer) 256 MCU node manager 260 Regional log server 264 Invite MCU300 NBS SIP signaling protocol stack 302 SIP traffic signaling 304 User Datagram Protocol (UDP) stream 306 Internet Protocol (IP) 308 Point-to-Point (PPP) message box 310 Radio Link Protocol (RLP) 312 Media Signaling Protocol Stack 314 NBS Media Signaling 320 Real Time Protocol (RTP) Voice Media Protocol Stack 322 Vocoder Payload Data 324 RTP330 Compressed Real Time Protocol (CRTP) Header Compression 332 UDP Voice Media Protocol Stack 334 Media Flow Protocol Stack 338 Domain Name Service (DNS) Client Protocol Stack 340 DNS354 invitation message 356 invitation request 357 acknowledgement (ACK) 358 invitation request 360 invitation response 362 SIP acknowledgement (ACK) request 364 goodbye message 366 goodbye response 368 media signaling message sequence 370,376 PTT request 372,378 PTX response 374,380 PTA message 400 media signaling message Sequence 404 AYT message 408 IAH response 412 ZZZ message 416 PTT request 420 PTX grant message response 424 AYT message request 428 PTA message 432 IAH response 440 NBS Media Signaling Message 442 Call CD443 Transmission Media 442 Lower Priority CD444 Higher Priority CD446,448 PTT Message Request 450 PTX Message 452 PTX Grant Message Response 454 PTX Reject Message 456 Distributed Media 500 Group Service Module 504 Idle State 508 Disabled state 512 No equipment state 514 Selected network 516 Quiet state 520 Listening state 524 Calling state 528 Standby state