US20070207731A1 - Intelligent Network Interface - Google Patents

Abstract

The present invention provides methods and apparatus for interconnecting disparate communications systems. A call request that originates from a communications network is directed to a network interface. The network interface consequently redirects the call request to a communications entity, such as a radio or a cellular radio system that serves the user associated with the call request. The network interface may support address translation functionality for identifying the communications entity, control conversion functionality for generating control and signaling with the communications entity, transmission content conversion functionality for converting the transmission content during the call, and security functionality for encrypting and decrypting the transmission content. Also, the present invention enables non-networking communications entities to interact with applications that are being executed on another terminal through the network, enables network management systems to manage non-networking communications entities through a network, and enables non-networking communications entities to utilize networking routing services.

Description

FIELD OF THE INVENTION
• This application is a continuation of co-pending U.S. patent application Ser. No. 10/096,197 filed Mar. 12, 2002, which relates to interfacing a communications network to a communications entity that includes a radio or another communications network and which is incorporated herewith by reference and for which priority is claimed.
BACKGROUND OF THE INVENTION
• The explosive growth of telecommunications has been accompanied by the deployment of communications systems in accordance with different technologies. This fact is exemplified by wireless communications. There are numerous cellular radio standards, including advanced mobile phone service (AMPS), which is a North American standard utilizing analog technology, total access communications system (TACS), which is an analog standard used in the United Kingdom, global system for mobile communications (GSM), which is a time division multiple technology used in many parts of the world, and code division multiple access (CDMA), which is a spread spectrum technology. There are additional standards for the upcoming third generation (3G) generation of cellular radio, including cdma2000, which is an evolution of CDMA and universal mobile telecommunications system (UMTS). In the future, new generations of cellular radio services will occur, and thus the variety of technologies will increase. Moreover, wireless communications also incorporates non-cellular radio communications including land mobile radio service (LMRS) and satellite services. One can quickly conclude that the number of different wireless technologies is numerous and is getting larger with the passage of time.
• A user, nevertheless, expects to communicate with another user regardless of the technology that is serving the user. Substantial capital has been invested in existing communications systems, and consequently the usage of these systems will continue even though communications systems with new technologies are being introduced. With wireless technologies, a converter is typically deployed with a base station radio in order to reconcile technology differences between the base station radio and the user's wireless terminal. With LMRS operation, for example, dedicated cabling between radios or radio control consoles are typically required. Furthermore, the user expects connectivity between wireless communications systems and wireline communications systems such as the Internet and the public switched telephone network (PSTN). There is certainly a need to facilitate the interconnection of disparate communications systems regardless of the underlying technology that is serving the user.
BRIEF SUMMARY OF THE INVENTION
• The present invention provides methods and apparatus for interconnecting disparate communications systems. For example, a voice call request that originates from a communications network is directed to a network interface. The network interface consequently redirects the call request to a communications entity, such as a radio or a cellular radio system, that serves the user associated with the call request. The network interface may support address translation functionality for identifying the communications entity, control conversion functionality for generating control and signaling with the communications entity, transmission content conversion functionality for converting transmission content during the call, and security functionality for encrypting and decrypting the transmission content. The present invention enables network management systems to manage non-networking communications entities (e.g. land mobile radios, public switching telephone networks, and personal communications systems) through a network. Also, the present invention enables non-networking communications entities to utilize networking routing functions and services (e.g. directory services). Moreover, the present invention enables non-networking communications entities to interact with applications that are being executed on another terminal through the network.
• An embodiment is shown for interfacing a communications network with an intelligent network interface (INI) to legacy radios (e.g. land mobile radios), cellular radio systems, and a public switched telephone network (PSTN). The INI comprises a proxy interface, entity control conversion, and entity address translation, security conversion, transmission content conversion. The INI exchanges messages with the network through the proxy interface. In order to establish a call to the user's communications terminal, the INI selects the appropriate entity (e.g. radio or cellular radio system) in accordance with user-associated data and entity address conversion.
• One embodiment includes a signaling scenario for supporting a wireless terminal through a land mobile radio (LMR) in which a call request originates from a 3G (third generation) end user terminal served by a 3G network to a user being served by the LMR. The INI verifies and locates the user by accessing user-associated data. The INI consequently notifies the appropriate radio interface about necessary characteristics of the user's wireless terminal and a call is established. The INI converts voice over IP (VoIP) transmission content to an analog waveform for transmission from the 3G EUT to the wireless terminal. Conversely, the INI converts an analog waveform to VoIP transmission content for transmission from the wireless terminal to the 3G EUT.
• A variation of the embodiment includes a signaling scenario for supporting a wireless terminal through a cellular radio system in accordance with an embodiment of the invention. The INI verifies the user and locates the cellular radio system that is serving the user. The INI generates dual tone multi-frequency (DTMF) signaling to the cellular radio system in order to complete the call connection. Subsequently, the INI converts transmission content during the call.
BRIEF DESCRIPTION OF THE DRAWINGS
• A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features and wherein:
• FIG. 1 shows an architecture of interconnecting disparate wireless systems utilizing an intelligent network interface (INI) in accordance with an embodiment of the invention;
• FIG. 2 shows a functional diagram of an intelligent wireless network interface in accordance with an embodiment of the invention;
• FIG. 3 shows apparatus for an intelligent wireless network interface in accordance with an embodiment of the invention;
• FIG. 4 shows a data structure for storing entity information in accordance with an embodiment of the invention;
• FIG. 5 shows an example of a signaling scenario for supporting a wireless terminal through a land mobile radio (LMR) in accordance with an embodiment of the invention; and
• FIG. 6 shows an example of a signaling scenario for supporting a wireless terminal through a cellular radio system in accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
• In the following description of the various embodiments, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration various embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope of the present invention.
• FIG. 1 shows an architecture of interconnecting disparate wireless systems utilizing intelligent network interface (INI)103 in accordance with an embodiment of the invention. End user terminal (EUT)113, which is served by 3G (third generation)network101 overchannel112, can communicate withwireless terminal109, which is served by land mobile radio (LMR)105 overwireless channel108 or withwireless terminal111, which is served bycellular radio system107 overwireless channel110. (Cellular radio system107 is sometimes referred as a “personal communications system.”)3G network101 can be a wireline network or a wireless network. In the embodiment,cellular radio system107 is a first generation (1G) or a second generation (2G) wireless system (pre-3G). However, other embodiments can support a subsequent generation of wireless services. In one embodiment, EUT113 can be one of a variety of terminals including a 3G wireless terminal or a 3G wireline terminal. EUT113 can provide different services to the associated user, including data services that are associated with the Internet and 3G multimedia services. Variations of the invention can support other types of legacy radios. (“Legacy radio” pertains to a radio that is not deployed in a cellular radio system.) A legacy radio may be dedicated to a user or to a group of users. A major characteristic of a 3G network is the support of the Internet protocol (IP). Moreover, the present invention can support networks that evolve beyond 3G.
• Ifterminal113 originates a call to eitherwireless terminal109 orwireless terminal111 through3G network101,3G network101 directs the call request to INI103. The call request contains an identification of the called wireless terminal and may contain quality of service, cost, and service type requirements. Network101 has a priori knowledge thatwireless terminal109 andwireless terminal111 are associated with INI103. Thus,network101 directs any related messaging toINI103 with a designated IP address. In the embodiment,network101 maintains this relationship through a data structure that is updated by a service provider ofnetwork101. A variation of the embodiment utilizes a registration procedure in which a corresponding entry forwireless terminal109 orwireless terminal111 is updated whenever a status of the wireless terminal changes.INI103 maintains user-associated data about each user (which will be explained in more detail in the context ofFIG. 2) in order to direct the call to wireless terminal109 (thoughpath104 and legacy radio105) or to wireless terminal111 (throughpath106 and cellular radio system107).
• Ifwireless terminal109 orwireless terminal111 originates a call towireless terminal113,INI103 directs the call to network101 throughpath102. In the embodiment,network101 maintains user-associated data associated withterminal113 in order to route the call.
• Network management system (NMS)115 manages3G network101 throughconnection114 using a network management protocol.NMS115 is a system of equipment used for monitoring, controlling, and managing a communications network. The network management protocol enablesNMS115 to support functions at a network management layer. Typically,NMS115 supports configuration management (deals with installing, initializing, “boot” loading, modifying and tracking configuration parameters of network hardware and software), fault location and repair management (indicates faults with equipment and facilities and supports repairing the faults), security management tools (allows the network manager to restrict access to various resources in the network), performance management tools (provides real-time and historical statistical information about the network's operation), and accounting management applications (helps operators to allocate costs of various network resources).
• The present invention extends the span ofNMS115 to includeLMR105 andcellular radio system107. In the embodiment,NMS115 verifies the operation ofLMR105 by activatingLMS105 and receiving status information fromLMS105.NMS115 utilizes the network management protocol (e.g. signaling network management protocol (SNMP)), andINI103 converts the corresponding commands (e.g. activating LMR105) into a format that is compatible withLMR105. (In particular,proxy interface201, which is discussed in the context ofFIG. 2, does the protocol conversion.) Equipment and configuration information aboutLMR105 can reside at eitherINI103 orNMS115. The embodiment also extends the span ofNMS115 tocellular radio system107.NMS115 can test radios and facilities associated with radio base stations that are controlled bycellular radio system107.
• FIG. 2 shows a functional diagram of intelligentwireless network interface103 in accordance with an embodiment of the invention.Proxy interface201 provides an interface to network101 in order to receive messaging to and fromnetwork101. Messaging associated with a call includes signaling messages as well as transmission content such as voice over IP (VoIP). The transmission content can support voice, data, or multimedia information that is transported during a call between users. (Messaging is explained in more detail in the context ofFIGS. 5 and 6.) In the embodiment,proxy interface201 is implemented by utilizing Joint Tactical Radio System (JTRS) software communications architecture (SCA). SCA is an open, standardized architecture that supports different network protocols including emerging wideband networking capabilities for voice, data, and video. (One can refer to the Support and Rationale Document for the Software Communications Architecture Specification, MSRC-5000 SRD V1.2, Dec. 21, 2000 that is available at http://www.jtrs.saalt.army.mil.)
• Software for implementingentity control conversion215,transmission content conversion217,security conversion218,entity address translation221,entity selection231, and interfaces205,207,213,211, and209 are based uponframework203. (Framework203 is a set of prefabricated software building blocks.)
• User-associateddata219 contains data about each user that is served byINI103 and is explained in more detail in the context ofFIG. 4. User-associateddata219 contains theentity address403 that is associated with a user.Entity address translation221 uses data from219 in order to direct a call throughentity selection231 to an appropriate communications entity (associated with legacyradio A interface205, legacyradio B interface207, public switching telephone network (PSTN)interface213, cellular radiosystem A interface209, or cellular radio system B interface211).Interfaces205,207,213,209, and211 include software and hardware to support the required physical layer such as appropriate voltage levels and connector pin arrangements. The appropriate communications entity (that can serve the user and may be a radio such asLMR105 or a network such as cellular radio system107) is connected to an interface in order to communicate to a wireless terminal (e.g.109 or111) or to a wireline terminal (e.g. through PSTN interface213).
• Transmission content conversion217 converts transmission content (e.g. VoIP) fromnetwork101 into a format (such as an analog waveform or 64 kbps Mu Law pulse code modulation) that is amenable for the target radio that interfaces toINI103 throughpaths214,218,220,222, and226. (“Transmission content” pertains to the content being sent on the communications connection betweenEUT113 and the wireless terminal being served byINI103. “User-associated data” pertains to data about the corresponding terminal that is served byINI103. An example of “user-associated data” is data rate capability of thewireless terminal109.)Security conversion218 provides encryption and decryption of transmission content in order to provide the necessary degree of security for communications between terminals.Entity control conversion215 converts signaling fromnetwork101 into a control signal that is amenable to the target radio or creates a control signal that is associated with an event during the call throughpaths212,216,224,228, and230. (Operation of entity control conversion is discussed in more detail in the context of the examples inFIGS. 5 and 6.)
• Entity control conversion215,transmission content conversion217,security conversion218, andentity address translation221 interact withproxy interface201 overpath202 in order to obtain messaging to and fromnetwork101. Also,proxy interface201,entity control conversion215,transmission content conversion217,security conversion218, andentity address translation221 interact with user-associateddata219 overpath204.
• FIG. 3 shows apparatus forINI103 in accordance with an embodiment of the invention. Data port301 (corresponding toproxy interface201 inFIG. 2) receives and sends messages (both transmission content and signaling messages) betweenINI103 andnetwork101.Data ports303 and305 interface to communications entities that are supported byINI103 and correspond tointerfaces205,207,213,209, and211.Processor307 executes computer executable instructions frommemory309 through path310 (corresponding to path204) in order to support theentity control conversion215,security conversion218,entity address translation221,entity selection231, and interfaces205,207,213,209, and211. Also,memory309stores data structure419 in order to support user-associateddata219.
• Processor307 interacts withdata port301 over connection302 (corresponding to path202).Processor307 interacts withdata port303 over connection306 (corresponding topaths212,216,224,228, or230) and connection304 (corresponding topaths214,218,220,222, and226).Processor307 interacts withdata port305 overconnection308 andconnection312.
• FIG. 4 showsdata structure419 for storing user-associateddata219 in accordance with an embodiment of the invention.Data structure419 comprises a plurality of records, each includinguser ID field401,entity address field403, and attributesfield405.User ID field401 identifies the user and may be the user's telephone number or IP address.Entity address field403 identifies the communications entity (e.g. legacy radio105 or cellular radio system107) that the user is associated with. User attributesfield405 is a collection of attributes (e.g. type of service, priority, quality of service, cost, and data rate capability) that is associated with the user. In the embodiment, user attributes are provisioned by a service provider throughdata port301 andprocessor307 tomemory309, which containsdata structure419.Processor307 accesses data structure419 (which is contained inmemory309 in the embodiment) to determine how to process a call request that is associated with the user (corresponding to user ID401). The examples inFIGS. 5 and 6 illustrate call processing in greater detail.
• FIG. 5 shows an example of a signaling scenario for supportingwireless terminal109 through land mobile radio (LMR)105 in accordance with an embodiment of the invention. End user terminal (EUT)113 initiates the call by sendingsession request message501 tonetwork101.Network101 consequently sendssession request message503 to INI103 (in particular to proxy interface function201) corresponding to a designated IP address. In the embodiment,network103 is connected to only one intelligent network interface (INI103). However, in alternative embodiments,network103 may maintain information that maps the destination user to a corresponding intelligent network interface.Session request messages501 and503 contain parameters (data fields) that include an identification ofwireless terminal109 and a service type (e.g. video with analog). Additionally,session request501 and503 can include a requested quality of service (QoS) level, a minimum QoS level, cost limitations associated with the call, and data rate capability. With verifyuser action505,proxy interface function201 verifies that the parameters are consistent with user-associateddata219.
• For example, the identification of the user insession request message503 should matchuser ID401 in one of the entries indata structure419. Also, the service type contained insession request message503 should be consistent with user attributes405. Ifproxy interface201 verifies the user (associated with wireless terminal109),proxy interface201 returns acceptmessage507 tonetwork101. However, ifproxy interface201 determines that the user identity does not match any user being served byINI103 or there is an inconsistency between the data fields insession request message503 and user-associateddata219, thenproxy interface201 returns a reject message to network101. (However, with an alternative of the embodiment,INI103 sends a negotiation message to network101 with an alternative parameter value, e.g. an alternative service type or data rate, that is consistent with the user attributes. Ifnetwork101 determines that the alternative parameter value is acceptable forEUT113,network101 returns an accept message toproxy interface201 to continue the processing of the call.)
• With locateentity action509 as performed byaddress conversion function221,address conversion function221 obtainsentity address403 that is contained in the appropriate entry of data structure419 (corresponding to user-associated data219) and locates communications entity (LMR)105 that serveswireless terminal109.LMR105 is connected toradio interface205. In the example shown inFIG. 5, the communications entity is a radio. However, the present invention supports communications entities that include cellular radio networks (as illustrated in the signaling scenario inFIG. 6), public switched telephone networks (PSTN), and data networks (e.g. an Internet network). OnceLMR105 is identified,address conversion function221 instructscontrol conversion215 byaction511 to notify radio interface205 (which interfaces to radio105) about physical characteristics ofradio105 with notifyaction513. The physical characteristics include a frequency of the radio and a format of the transmission content, e.g. an analog waveform. The operation ofradio105 is verified bystatus514. Consequently,control conversion function215 sends proceedmessage515 to network101 throughnetwork proxy interface103.
• The communication betweenEUT113 andwireless terminal109 commences withtalk message517. At this point of time,INI103 has completed the call connection betweenEUT113 andwireless terminal109 throughradio105. Consequently,control conversion function215 generates push to talk (PTT)command519 toradio105 throughradio interface205.
• In one embodiment,EUT113 sends transmission content using a voice over IP (VoIP) format; however,wireless terminal109 can only process an analog format. Thus,VoIP transmission content521 is converted toanalog waveform523 by transmissioncontent conversion function217. In the embodiment,radio105 andwireless terminal109 operate in half duplex operation, i.e. bothradio105 andwireless terminal109 do not transmit at the same time. Whenwireless terminal109 is transmitting,analog waveform527 is converted toVoIP transmission content529 in order to be compatible with the operation ofEUT113. In the embodiment,transmission content conversion217 assesses the activity betweenEUT113 andwireless terminal109. When transmissioncontent conversion function217 determines thatEUT113 is talking, function217 notifiescontrol conversion function215 throughaction525. When transmissioncontent conversion function217 determines thatwireless terminal109 is talking, function217 notifiescontrol conversion function215 throughaction531. In an alternative embodiment, whenwireless terminal109 transmits, a PTT command is sent fromwireless terminal109 to controlfunction215, which in turn sends a talk message to network103.
• Disconnectmessage533 indicates thatEUT113 has disconnected from the call. Control conversion receivesmessage533 throughproxy interface201 and consequently sends disconnectmessage535 toradio105 throughradio interface205.
• The embodiment also supports a call that is originated fromwireless109 toEUT113. With such a scenario,INI103 sends a session request message to network101 with a user identification corresponding toEUT113.Network101 locatesEUT113 in order to complete the call toEUT113. The scenario is similar to the scenario shown inFIG. 5. However, theaddress conversion function221 does not locate the communications entity that is associated withwireless terminal109 becausewireless terminal109 has explicitly identified itself through the call request.
• WithFIG. 6,EUT113 originates a call towireless terminal111, which is currently served bycellular radio system107.Cellular radio system107 is connected toradio interface209. As with the example inFIG. 5, data structure419 (corresponding to user-associated data function219) comprises an entry corresponding towireless terminal111. The entry comprisesentity address field403 that corresponds to an identification ofcellular radio system107.FIG. 6 shows an example of a signaling scenario for supportingwireless terminal111 throughcellular radio system107 in accordance with an embodiment of the invention.Signaling messages601,603,605,607, and609 correspond to signalingmessages501,503,505,507, and509 as shown inFIG. 5. Inaction611,address conversion function221 instructscontrol conversion function215 to generate dual tone multi-frequency (DTMF) signal613 throughradio interface209 tocellular radio system211. In the embodiment,DTMF signal613 corresponds to a telephone number ofwireless terminal111.Signal613 initiatescellular radio system107 topage wireless terminal111. Whenwireless terminal111 responds to paging,cellular radio system107 generatesstatus indication614 throughradio interface209 to controlconversion function215. Consequently,control conversion function215 sends proceedmessage615 throughproxy interface201 tonetwork101 in order that communications is established betweenEUT113 andwireless terminal111. Consequently, a call connection is completed betweenEUT113 andwireless terminal111 throughcellular radio system107.
• Transmission content is sent betweenEUT113 andwireless terminal111.EUT113 transmits and receivesVoIP transmission content621 throughnetwork101 andproxy interface201 in conjunction with transmissioncontent conversion function217. Transmissioncontent conversion function217 convertsVoIP transmission content621 to pulse code modulation (PCM)transmission content623 for transmission to wireless terminal111 and convertsPCM transmission content623 toVoIP transmission content621 for transmission fromwireless terminal111.Message633, which indicates thatEUT113 has terminated the call, is sent throughnetwork101 andproxy interface201 to controlconversion function215. Consequently,control conversion215 sendsmessage635 tocellular radio system107 in order to terminate the call.
• Other embodiments may support other variations of transmission content623 (that may be associated with a voice waveform of a user), including code excited linear prediction (CELP, e.g. Standard G.728), adaptive differential pulse code modulation (ADPCM, e.g. Standard G.726) and voice over IP (VoIP). Moreover, variations of the embodiment may support a call in which transmission content does not represent a voice waveform of a user. In such a case, the call is often referenced as a “data call.” For example,INI103 may support an interface to an X.25 network.
• FIGS. 5 and 6 illustrate signaling messages for a setting up and maintaining a call. Moreover,INI103 enables non-networking communications entities (e.g. LMR105) to exploit networking protocols, including differentiated services (DiffServ), multiprotocol label switching (MPLS), multi-level priority protocol (MLPS), and bandwidth brokers. Networking protocols typically enablenetwork101 to support a designated quality of service (QoS) level when routing traffic (e.g. data packets) throughnetwork101 to terminal113 during the call. In the embodiment, MPLS enables data packets to have added labels so that data packets are forwarded along pre-constructed label-switched paths (LSP's) by routers that are modified to switch MPLS frames innetwork101. In the embodiment, DiffServ typically utilizes a DiffServ code point (DSCP) that indicates differentiated traffic handling corresponding to different QoS levels, in which a QoS level is associated with a data flow of a call.
• In the embodiment,proxy interface201 adds a label for a MPLS frame and includes a DSCP for a data packet if supporting DiffServ.Proxy interface201 utilizes a QoS level as indicated bynetwork101 in a data flow that is sent betweenterminal113 and terminal109 or betweenterminal113 andterminal111.
• In the embodiment,network101 may multiplex a plurality of independent application flows forterminal113 that are based upon port numbers. A port number is typically included in a data packet and is associated with an application that is executing onterminal113. An application is a software program that executes on terminal113 (e.g. a spreadsheet, communications package, or graphics program). An IP address is assigned toterminal113 and determined by an identification ofterminal113 and the designated application. Ifterminal109 and terminal113 are communicating with each other, terminal113 may execute a VoIP application in order to support voice communications. However, the embodiment supports other applications, including e-mail exchanges and file transfer services. In the embodiment,proxy interface201 utilizes an appropriate port number in order to support a service that is associated with communications betweenterminal113 and terminal109 and betweenterminal113 andterminal111.
• The embodiment also supports non-call associated services, including directory services forterminals109 and111. A directory service is provided bydirectory server117 throughfacility116.Server117 determines an IP address that is assigned toterminal113 when queried with identifying attributes of a user, e.g. a user's identification and application type.Terminal109 or terminal111 sends a directory request toINI103.Proxy interface201 translates the request in order to queryserver117 and sends the translated request to an IP address ofserver117.
• As can be appreciated by one skilled in the art, a computer system with an associated computer-readable medium containing instructions for controlling the computer system can be utilized to implement the exemplary embodiments that are disclosed herein. The computer system may include at least one computer such as a microprocessor, digital signal processor, and associated peripheral electronic circuitry.
• While the invention has been described with respect to specific examples including presently preferred modes of carrying out the invention, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and techniques that fall within the spirit and scope of the invention as set forth in the appended claims.

Claims (25)

1. A method for supporting a call between a first terminal and a second terminal through a network interface, the first terminal associated with a communications network and the second terminal associated with a communications entity, the method comprising the steps of:

(a) receiving from the communications network a signaling message associated with the call;

(b) translating a signaling protocol between the communications network and the communications entity;

(c) determining whether the communications entity can serve the second terminal and whether the signaling message associated with the call is intended for the communications entity;

(d) connecting the call between the first terminal and the second terminal through the communications entity, in response to determining that the communications entity can serve the second terminal and that the signaling message associated with the call is intended for the communications entity; and

(e) converting transmission content of the call between the communications network and the communications entity.

2. The method ofclaim 1, further comprising the step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an identification of the communications entity.

3. The method ofclaim 1, further comprising the step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an attribute associated with the second terminal.

4. The method ofclaim 1, wherein step (b) comprises the step of:

(i) generating a control signal to the communications entity that is compatible with the communications entity.

5. The method ofclaim 1, further comprising the steps of:

(f) encrypting transmission content of the call that is sent to the communications network; and

(g) decrypting transmission content of the call that is received from the communications network.

6. The method ofclaim 3, further comprising the steps of:

(g) if the parameter is not consistent in response to step (f), proposing an alternative parameter value that is consistent with the attribute; and

(h) sending a second signaling message that contains the alternative parameter value.

7. The method ofclaim 1, wherein the communications entity comprises a radio and further comprising the step of:

(f) initializing the radio in accordance with radio parameters.

8. The method ofclaim 1, wherein the communications entity is selected from the group consisting of a radio, a cellular radio network, a public switching telephone network (PSTN), and a data network.

9. The method ofclaim 1, further comprising the steps of:

(f) receiving a second signaling message that requests that the call be disconnected;

(g) disconnecting the call to the communications entity in response to step (f).

10. The method ofclaim 1, wherein the communications network comprises a third generation (3G) network and the communications entity comprises a push-to-talk (PTT) radio.

11. The method ofclaim 1, wherein the communications network comprises a third generation (3G) network and the communications entity comprises a pre-3G cellular radio system.

12. The method ofclaim 4, wherein step (i) comprises the steps of:

(1) detecting activity associated with the transmission content during the call; and

(2) generating the control signal in response to step (1).

13. The method ofclaim 1, wherein the transmission content is selected from the group consisting of a voice over IP (VoIP) format, an analog waveform, a pulse code modulation (PCM) format, a code excited linear predictive (CELP) format, and an adaptive differential pulse code modulation (ADPCM) format.

14. The method ofclaim 1, wherein the call is associated with an application that is executing on the first terminal.

15. The method ofclaim 1, further comprising the step of:

(f) inserting an identifier in a network protocol message, the identifier corresponding to a quality of service (QoS) level that is supported by the communications network.

16. A network interface for supporting a call between a first terminal and a second terminal, the first terminal associated with a communications network and the second terminal associated with a communications entity, the network interface comprising:

at least one data port that interfaces to the communications network and to the communications entity; and

a processor communicating through the data port to the communications network and to the communications entity, the processor configured to perform the steps of:

(a) receiving from the communications network a signaling message associated with the call;

(b) translating a signaling protocol between the communications network and the communications entity;

(c) determining whether the communications entity can serve the second terminal and whether the signaling message associated with the call is intended for the communications entity;

(d) connecting the call between the first terminal and the second terminal through the communications entity, in response to determining that the communications entity can serve the second terminal and the signaling message associated with the call is intended for the communications entity; and

(e) converting transmission content of the call between the communications network and the communications entity.

17. The network interface ofclaim 16, wherein the processor is configured to perform the further step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an identification of the communications entity.

18. The network interface ofclaim 16, wherein the processor is configured to perform the further step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an attribute associated with the second terminal.

19. The network interface ofclaim 16, wherein the processor is configured to perform the further steps of:

(f) encrypting transmission content of the call that is sent to the communications network; and

(g) decrypting transmission content of the call that is received from the communications network.

20. The network interface ofclaim 16, wherein the processor is configured to perform the further step of:

(f) inserting an identifier in a network protocol message, the identifier corresponding to a quality of service (QoS) level that is supported by the communications network.

21. A computer-readable medium containing instructions for supporting a call between a first terminal and a second terminal, the first terminal associated with a communications network and the second terminal associated with a communications entity, the computer-readable medium comprising instructions that perform the steps of:

(a) receiving from the communications network a signaling message associated with the call;

(b) translating a signaling protocol between the communications network and the communications entity;

(c) determining whether the communications entity can serve the second terminal and whether the signaling message associated with the call is intended for the communications entity;

(d) connecting the call between the first terminal and the second terminal through the communications entity, in response to determining that the communications entity can serve the second terminal and the signaling message associated with the call is intended for the communications entity; and

(e) converting transmission content of the call between the communications network and the communications entity.

22. The computer-readable medium ofclaim 21, further comprising instructions that perform the step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an identification of the communications entity.

23. The computer-readable medium ofclaim 21, further comprising instructions that perform the step of:

(f) determining whether a parameter that is contained in the signaling message is consistent with an attribute associated with the second terminal.

24. The computer-readable medium ofclaim 21, further comprising instructions that perform the steps of:

(f) encrypting transmission content of the call that is sent to the communications network; and

(g) decrypting transmission content of the call that is received from the communications network.

25. The computer-readable medium ofclaim 21, further comprising instructions that perform the step of:

(f) inserting an identifier in a network protocol message, the identifier corresponding to a quality of service (QoS) level that is supported by the communications network.

Images