KR20010085327A - A plug and play wireless architecture supporting packet data and ip voice/multimedia services - Google Patents

Abstract

Wireless to one or more public packet data networks, including, for example, but not limited to, the Internet, and one or more public switching circuit networks, such as, but not limited to, public switched telephone networks (PSTNs). A communication network supporting access.

For example, a voice access unit, such as but not limited to a telephone, and a computing device, such as but not limited to a personal computer, are connected to the wireless unit via a wired interface, which is connected to the wireless unit. Itself provides public (ie, wired or wireless) access to one or more public data networks and one or more public switching circuit networks.

The computing device may receive the packetized message (both voice data). The voice access device is connected to the computing device and can receive the voice message converted from the packetized voice message.

The computing device and the computing device / voice access device combination each comprise a subscriber device. The radio access network supports both switching circuit transmission and packet data transmission for one or more network subscribers through each network subscriber device.

Radio access networks include protocols for transmitting packet data messages to network subscribers from public data networks, including, for example, but not limited to, the Internet. The radio access network also includes a protocol for transmitting voice messages to network subscribers in a switching circuit network.

Description

Plug and play wireless system supporting packet data and IP voice / multimedia services {A PLUG AND PLAY WIRELESS ARCHITECTURE SUPPORTING PACKET DATA AND IP VOICE / MULTIMEDIA SERVICES}

In general, known telecommunication systems that have attempted to provide both packet data and voice services have used the concept of an overlay network. In particular, in a known communication system, a network supporting packet data is installed redundantly with an existing basic system supporting voice. In this way, voice and packet data transfers, ie voice and packet data transfers, are for example along separate paths from a forward base station to a point in the network.

Known systems transmit voice in circuit switched mode and packet data in packet switched mode. In packet switched mode, information is transmitted in many sections or packets via one or more physical transport routes, and then reassembled at the receiving end. Because information is transmitted in packets, transmission resources, such as physical transport interfaces, can be shared simultaneously by one or more users and / or one or more data streams.

In contrast, in circuit switched mode, there is only a single, intact connection between the sender and receiver of a voice stream or voice transport. In circuit switched mode, the voice transfer is sent to the section without being split, so that once the transfer connection is made in the network, e.g. for a telephone call, the voice is not broken and maintained even if there is no voice transfer at a particular time. The physical connection is dedicated only to the call transfer except for all other users of the system.

Thus, in known telecommunication systems that have attempted to support both packet data and voice, resources are generally dedicated to packet data support or optionally transmitted to voice support. Moreover, in such known systems, resources can be consumed by voice support except packet data. In addition, such systems do not integrate packet data and voice support throughout the system, thus requiring additional resources to support additional services, such as packet data, such as voice, that is redundant in the original base system.

In addition, since the known systems are switching circuits, voice and central circuits, end-to-end circuits are generally allocated for voice and packet data transmission. This reduces the flexibility of the system to coordinate multiple users accessing both switched circuits and packet data services simultaneously. In addition, such a system lacks the ability to support the "best transmission path" between the various sub-components of the network in end-to-end communication. In such a system, a single communication path, ie end-to-end, is established for communication flow, voice or data. Other paths between components of the network capable of high speed transmission of certain messages, voice or data with good quality are not examined and utilized in these systems.

Accordingly, it is desirable to provide an integrated flexible wireless system capable of supporting both packet data and voice. In addition, it is advantageous to provide an integrated voice / packet data system based on Internet protocols that support equivalent message flow handling for voice and packet data throughout the network. It would also be advantageous to provide an integrated voice / packet data system that supports cost-effective packet data, for example for Internet access and cost-effective switched circuit services, such as access to existing switched circuits (telephone networks).

The present invention relates to a telecommunications system, in particular a system supporting radio access to public data networks and public switched circuit (telephone) networks.

1 illustrates a service of a radio access network.

2 illustrates a preferred embodiment of a radio access network.

2A illustrates a preferred embodiment of a customer premises radio unit (CPRU) in a radio access network.

3 illustrates a procedure and transmission interface executed between an H.323 gatekeeper and an H.323 endpoint.

4 illustrates an IP voice procedure supported by a radio access network.

5 illustrates another embodiment of a radio access network.

6 is a diagram illustrating the centralization management operation of a radio access network.

7 illustrates a subscriber management platform procedure supported by a radio access network.

8 illustrates a communication protocol plane in a radio access network.

9 illustrates a communication protocol plane in a radio access network.

10 illustrates a packet data signal plane supported by a radio access network.

11 illustrates a voice signaling procedure supported by a radio access network.

12 illustrates a protocol stack for a packet data signaling plane in a radio access network.

13 illustrates a terminal management protocol procedure supported by a radio access network.

14 illustrates a protocol stack for a packet data carrier plane in a radio access network.

FIG. 15 illustrates a protocol stack for voice signaling plane in a radio access network. FIG.

16 illustrates a protocol stack for a voice carrier plane in a radio access network.

17 illustrates a local link control procedure supported in a radio access network.

18 illustrates a protocol stack for managing network nodes in a radio access network.

19 illustrates a hierarchy of management platforms within a management system of a radio access network.

20 illustrates management of a base station and a customer premises radio unit (CPRU) by a universal radio access management platform of a radio access network.

21A illustrates a protocol stack for a base station management protocol plane.

21B illustrates a protocol stack for a customer wireless unit management protocol plane.

FIG. 22 illustrates a network component structure for end-to-end packet carrier transport in a radio access network. FIG.

FIG. 23 illustrates a network component structure for end-to-end signaling for authentication and subscriber management in a radio access network. FIG.

FIG. 24 illustrates a network component structure for end-to-end network management signaling for node and charge management in a radio access network. FIG.

The present invention provides an apparatus and mechanism for providing telecommunications system assisted wireless access in an end-to-end format that can coordinate both packet data and voice transmission.

In one embodiment, the voice access unit and the calculation unit are connected to a wireless unit that provides its own public access to the radio access network. The radio access network uses parts of itself to access one or more packet data networks and one or more switched circuit networks.

The computing device may receive the packet data. The voice access device may receive a voice message. The voice access device is connected to the computing device to receive a voice message sent from the radio access network.

In one embodiment, the radio access network supports simultaneous transmission of switched circuit messages and packet data messages to network subscribers. The radio access network includes a protocol for transmitting a packet data message from a packet data network to a subscriber. The radio access network includes a protocol for transmitting voice messages from the switched circuit network to the subscriber.

Radio access networks support protocols for security management of radio access networks. The radio access network further includes a protocol for management of subscriber information, including but not limited to subscriber required services supported by the radio access network. The radio access network includes a protocol for managing the charging of subscribers of the network.

Accordingly, it is an object of the present invention to provide a telecommunication system that supports access to packet data services and voice services. It is another object of the present invention to provide a cost-effective simless wireless access network that regulates the transport or transmission of packet data and voice. Other objects, features and advantages of the present invention will be described in more detail below with reference to the drawings.

Preferred embodiments of a radio access network or system include various services 1 that support radio access voice and data transfer functions as shown in FIG. In particular, preferred embodiments of a radio access network include wireless access to (but not limited to) public data networks, including one or more data networks, such as the Internet, and one or more switched network networks, such as a public switched telephone network (PSTN), but Service 1 to support wireless access to). The services (1) of the radio access network include packet data services (2), voice services (3), fax services (4), security services (5), network management services (6), subscriber management services (7), and charging. Service 8, including but not limited to.

Packet data services 2 of a radio access network include, but are not limited to, point-to-point and point-to-multipoint services. Point-to-point packet data service is a datagram type of connectionless service. That is, messages are transmitted over an unstable transport channel that includes the ability to transmit one or more data packets from a single packet data network, such as, but not limited to, a single network subscriber, i.e., an end user of a radio access network. Alternatively, the point-to-point packet data service includes a service for transmitting one or more data packets from a single network subscriber to a single packet data network.

In a preferred embodiment, a radio access network subscriber terminal transmitting or receiving packet data includes a personal computer (PC) and a wireless modem (WM). In an alternative embodiment, the terminal for receiving or transmitting packet data may be any computing device, such as but not limited to a personal computer, a smart terminal, a farm pilot or workstation, and a wireless unit such as a wireless modem ( WM) (but not limited to this).

In a second preferred embodiment, a radio access network subscriber terminal comprises one or more personal computers (PCs) and a customer wireless premises unit (CPRU). As an alternative to the second embodiment, a terminal for receiving or transmitting packet data includes one or more various computing devices, smart terminals or workstations, including but not limited to a personal computer (PC), and a CPRU.

In a preferred embodiment, each packet data transmission is independent of preceding and consecutive packet data transmissions. In a preferred embodiment, on a radio or air transport interface of a radio access network, the point-to-point packet data service utilizes an acknowledgment transmission mechanism for reliable radio transmission and reception. In a preferred embodiment, the network layer protocol for point-to-point connectionless packet data service is the Internet Protocol (IP).

Point-to-multipoint packet data services include the ability to transfer messages between members of an Internet Protocol Multicast (IP-M) group. Point-to-multipoint packet data service is a datagram type of connectionless service. That is, the message includes the ability to send one or more data packets to two or more network subscribers from a single packet data network, such as, but not limited to, the Internet.

Members sending data to point-to-multipoint services conform to the Internet Protocol (IP).

The voice service 3 of the radio access network includes setting up, maintaining and releasing voice calls between subscribers of the radio access network and between switched circuit networks supported by the radio access network. In a preferred embodiment, the H.323 terminal for receiving or transmitting IP packet voice includes a telephone, a personal computer (PC) and a wireless modem (WM). In an alternative embodiment, the H.323 terminal for receiving or transmitting IP packet voice is any voice access device, such as a telephone (but not limited to), any computing device, such as a personal computer (but not limited to this). And smart terminals, plane pilots or workstations, and wireless units such as, but not limited to, wireless modems (WMs).

In a second preferred embodiment, an H.323 terminal for receiving or transmitting IP packet voice includes a telephone and a customer wireless campus unit (CPRU). As an alternative to this second preferred embodiment, the H.323 terminal for receiving or transmitting IP packet voice includes any voice access device such as, but not limited to, a telephone and a CPRU.

In a preferred embodiment, the voice service is based on the H.323 protocol standard which is duplicated in the Internet Protocol (IP) Basic Packet Data Service (2). In a preferred embodiment, the voice message is sent within the radio access network in the form of an IP packet datagram.

The fax service 4 of the radio access network is supported via the Internet Protocol (IP) basic packet data service 2 and provides a mechanism for sending and receiving fax basic messages.

The security service 5 of the radio access network supports security features including but not limited to subscriber authentication, terminal authentication, user identification confidentiality and user information secret. Subscriber authentication and terminal authentication confirm that each subscriber and terminal identifier used is appropriate, that is, each subscriber for each terminal has been approved upon request for network services. Subscriber and terminal authentication procedures protect the network from unauthorized use and from illegal use of authenticated users.

User identifier confidentiality provides the identifier secret for the subscriber using the radio or public resources of the radio access network. The user identifier secret can prevent (but is not limited to) tracking the subscriber's location in the network by listening to or otherwise intercepting a signal exchange on the network air interface.

User information secrets include, but are not limited to, the encryption and decryption of messages, voice, and data transmitted over a network. User information secrets provide a mechanism to protect the confidentiality of messages, voice, and data transmitted over a network air interface.

The security service 5 of the radio access network supports techniques that allow public entry points to the radio access network to prevent unauthorized access. Security service 5 supports the function of preventing unauthorized access and use of network nodes or elements such as base stations, access routers, gateways and gatekeepers.

In a preferred embodiment, one technique for achieving both secure network services and secure network node management includes authentication based on base station firewalls. In this technique, unauthorized users are prevented from accessing the rest of the network by the base stations of the radio access network. Gateway firewalls are used to prevent unauthorized access to a radio access network via an external network, such as through external packet data or an external switched circuit network supported by the radio access network. The original data authentication procedure is implemented as an additional security method to ensure network node management functions.

The network management service 6 of the radio access network manages network elements or nodes, including but not limited to radio access networks such as base stations, access routers, gateways and keeper. The network management service 6 supports management functions including, but not limited to, configuration management, defect management, performance management, and charge management.

The subscriber management service 7 of the radio access network supports the management of subscriber profiles. The subscriber profile includes (but is not limited to) service subscription information and end parameters, i.e., other parameters assigned to subscribers of the network during the approved contractual approval period. In a preferred embodiment, the subscriber profile includes each subscriber or customer identifier for network service and a quality of service level assigned to each subscriber.

In a preferred embodiment, special service requests can be made valid for each subscriber's subscription profile. For example, if the subscriber is only contracted for packet data services, the packet data request from the subscriber will be valid and executed by the network. However, voice requests from subscribers will be invalidated. Thus, voice services are not provided in the subscriber's subscription profile because they are not contracted by the subscriber. Thus, voice requests from subscribers will not be executed by the network.

The charging service 8 of a radio access network includes a mechanism for charging subscribers, i.e., end users of the network, for radio access, packet data services such as Internet access and voice services. In a preferred embodiment, a centralized charging system is used to consolidate subscriber's fees for all services provided.

The wireless access service is a basic wireless network service, and without this service, all other services cannot be provided. In a preferred embodiment, the mechanism for charging for wireless access is a way of charging a flat rate based on the peak throughput level selected by the subscriber.

The flat fee for wireless access is attractive because the subscriber is already familiar with the flat fee for access to conventional information and communication systems, such as public switched telephone networks (PSTNs) provided by local telephone companies. In addition, a simple network structure can support flat pricing for wireless access.

However, the radio, or public spectrum, of personal communication systems (PCS) is a limited resource. Thus, other flat rate charging is related to the quality of service (QoS) of multiple subscriber required service levels. The charging scheme for wireless access protects radio resources from overuse without the need for complicated charging schemes.

Packet data service resources are subscriber options. In a preferred embodiment, the mechanism for charging fees for packet data services is a flat fee scheme. In another embodiment, the mechanism for charging for packet data services is a usage-based charging scheme. In another embodiment, the mechanism for charging the packet data service is a combination of a flat rate and metering scheme. In a preferred embodiment, the Remote Authentication Dial (RADIUS) calculation protocol of the user service carries calculation information used for charging purposes between external data networks, such as the Internet, access server entities, and wireless access network central billing systems.

Voice service support is a subscriber option. In a preferred embodiment, the mechanism for charging for voice services is based on the scheme used by conventional telephone systems, i.e., call duration and called party destination address.

In a preferred embodiment, the radio access network supports terminal mobility. In a preferred embodiment, a terminal including a wireless modem can change the connection location, i.e., the physical relay location, to a network and then continue to transmit messages, voice, data and signals.

System or network 10 that supports wireless access to one or more external data networks, such as, but not limited to, the Internet and that supports wireless access to one or more external switched circuit networks, such as a public switched telephone network (PSTN). A preferred embodiment is shown in FIG. In a preferred embodiment, network 10 includes a wide area network (WAN). In the preferred embodiment, the system 10 includes three subnetwork.

The first subnetwork is a core packet data network. In a preferred embodiment, the core packet data network consists of (but is not limited to) one or more computing devices 20, such as a personal computer (PC), a smart terminal, a farm pilot, a workstation, or a combination thereof. In a preferred embodiment, the core packet data network consists of one or more wireless units, such as a wireless model (WM) 25. In the preferred embodiment, the network subscriber terminal 21 or other terminal comprises a PC and a WM 25.

In a preferred embodiment, the core packet data network includes one or more base station transceivers (BTSs) 30 and one or more access routes 35 mentioned from the base stations. In a preferred embodiment, the core packet data network comprises an Internet Protocol (IP) network 40, such as, but not limited to, a dedicated IP network, a packet data gateway including the Internet gateway 60 and the Internet 65. Includes one moving packet data network.

The second part network of system 10 is an Internet Protocol (IP) packet voice network. In a preferred embodiment, the IP packet voice network comprises one or more voice access devices, such as a telephone 15 (but not limited to), one or more computing devices 20, such as a PC (but not limited to), one or more Wireless units such as wireless modem (WM) 25 (but not limited to), gateway 45, gatekeeper 55 and one or more external switched circuit network (SCN) 50. In the preferred embodiment, the telephone, PC and WM 25 comprise an H.323 terminal 17, i.e., a terminal capable of supporting IP packet voice services. In a preferred embodiment, the gateway 45 includes an H.323 gateway and the gatekeeper 55 includes an H.323 gatekeeper.

The third part network of the system 10 is an operation support system (OSS) 70. In a preferred embodiment, the computational support system 70 is comprised of a subscriber management platform (SMP) 75 and a network management system (NMS) 80.

The computing device 20, for example the PC of the system 10, is a device that accesses a component or network node of an end user, ie a subscriber, ie a radio access network. In a preferred embodiment, computing device 20 supports a variety of services, including but not limited to packet data, facsimile and IP packet voice services.

In the core packet data network, terminal 21 is provided as an Internet Protocol (IP) destination node. Thus, the terminal 21 has an associated IP address and supports termination of the Internet protocol for the transmission of data and messages in the radio access network. In the preferred embodiment, the IP address of the terminal is changed when the terminal 21 is physically transferred to various connection locations in the system 10. Thus, the IP address of the terminal is dynamically assigned by the system 10 as needed.

In an Internet Protocol (IP) packet voice network, an H.323 terminal 17 is provided as an Internet Protocol (IP) destination node. Thus, the H.323 terminal 17 has an associated IP address and supports terminating processing of the Internet protocol for voice message transmission within the radio access network. In a preferred embodiment, the IP address of the H.323 terminal changes as an H.323 terminal 17 or at least a portion of the H.323 terminal 17, i.e. each PC and WM 25 of the H.323 terminal 17. Are physically delivered to different connection locations in the system 10. Therefore, the IP address of the H.323 terminal is dynamically assigned by the system 10 if necessary.

In a preferred embodiment, for an IP packet voice network, H.323 terminal 17 acts as a network endpoint. Therefore, to support IP packet voice network processing, H.323 terminal 17 supports the elements necessary for H.323 communication. These elements are H.323 for communication processing, vocoding function, and audio / video device function. 323 includes, but is not limited to, a software protocol stack. In a preferred embodiment, the vocoding function is based on the G.7xx series of recommendations referenced in the H.323 protocol criteria. In a preferred embodiment, the H.323 protocol functionality runs as an application via a core packet data network application.

Wireless modem (WM) 25 interfaces with each computing device 20 and provides bridging functionality to enable computing device 20 to connect to a wireless access system. In a preferred embodiment, WM 25 is connected to each computing device 20 via reference wired cabling 22.

For packet data delivery, or for message transmission, the WM 25 manages the interaction between each computing device 20-the WM 25 wired interface 22. The WM 25 connects the transmitting and receiving base station 30, referred to as the base station, with the computing device 20 side of the air interface 27. For packet data delivery, WM 25 provides a process for managing endpoint signaling for functions including authentication, encryption setup, address resolution, and dynamic IP address assignment.

In the preferred embodiment, on the computing device 20 side, each WM 25 is a PCMCIA (Personal Computer Memory Card International Union), with an extended set of synchronous transfer (AT) instructions for control of each computing device of the WM 25. Based physical interface. In one aspect, the computing device 20 and each WM 25, ie, terminal 21, are communicated by a transmit and receive base station, or a deliverable terminal end unit and system 10 of system 10 to base station 30. Represents a supported external data network. Also in the same feature, each WM 25 of the computing device 20 and the H.323 terminal 17 is a deliverable terminal end unit of the system 10 for a base transceiver station or base station 30, and a system 10. Represents an external switched circuit network supported by).

In a preferred embodiment, on the transport side, i.e. in terms of voice and data message transfer protocols, the WM 25 is used as a link layer bridge between the base station 30 and the computing device 20. In the preferred embodiment, the WM 25 is not required to support an IP address or routing function if each terminal 21 or H.323 terminal 17 owns an assigned IP address.

The base transceiver station (BTS) 30 or base station is an integral part of the air function of the system 10. Base station 30 includes the ability to provide wireless coverage to a particular terrain area serviced by system 10. Among other functions, the base station 30 includes access to the backbone of the system 10, i.e., network nodes or elements, and external switched circuit networks and external packet data supported by the system 10, It provides a WM 25 connection to each communication path that supports access to services in the network. Base station 30 includes equipment, components, and software necessary for bidirectional communication with one or more WMs 25. In a preferred embodiment, the base station 30 communicates with the WM 25 over the air, ie over the air interface 27.

In a preferred embodiment, the radio function of the system or network 10, ie air interface communication, is based on GPRS (general packet radio service) and GSM (global system for mobile communication). In another embodiment, the wireless function of system 10 is based on the GSM / Edge (Enhanced Data Rate for Global System / GSM Deployment for Mobile Communications) protocol.

Moreover, the system 10 includes each radio, i.e., IS-95, Global System for Mobile Communications (GSM), Digital AMPS (DAMPS), DECT, Wide Area Code Division Multiple Access (WB-CDMA), Wide Time Division Multiple Access (WB-TDMA). For wireless or public communication, including PHS, IS-661, Personal Communication System (PCS), PACS, and all derivatives thereof, other communication systems or protocols, platforms, or communication criteria may be used.

In the preferred embodiment, base station 30 supports multiple WMs 25. Cell engineering requires that the number of base stations 30 deployed in the geographic area serviced by the system 10 be with each computing device 20 and associated WM 25, ie, terminal 21, or with each telephone 15. It is used to ensure that the computing device 20 and WM 25 associated with it, ie, H.323 terminal 17, that connects to the system 10 from each terrain support area of the base station, are sufficient to provide a connection.

Base station 30 further supports signaling termination and interaction functions, including authentication, encryption setup, address resolution and temporary link layer identification (TLLI), or addressing, assignment for the next voice or packet data message transmission.

On the network side, the base station 30 is connected to one or more external data networks, including the Internet 65, or to provide access to one or more switched circuit networks 50, access routers 35 and IP networks 40. For example, interact via a dedicated IP network. Base station 30 may be configured to provide packet transport traffic between WM 25 and base station 30 and between base station 30 and each upstream network interface, such as the Internet 65 and one or more external switched circuit networks 50, It provides a bridging function for relaying voice or data.

In the preferred embodiment, the base station 30 uses an external IP address and supports the IP layer protocol stack for packet data and voice services and subscriber management functions.

The access router 35 is a base station 30 of the system 10 in an external environment, for example one or more external data networks including the Internet 65 and one or more switched circuit networks 50 via the IP network 40. ) Provide access. In a preferred embodiment, the access router 35 is a stock router that supports IP routing and firewall functionality. In a preferred embodiment, base station 30 communicates with one or more access routers 35 via a wired interface 32.

The access router 35 further provides for termination of network-side functions for mobility management in the system or network 10. In another embodiment, Mobile Internet Protocol (RARP) is used in system 10 to support the transfer characteristics of terminal 21 or H.323 terminal 17. In another embodiment, the General Packet Radio Service (GPRS) protocol is used in the system 10 to support the propagation characteristics of the terminal 21 or the H.323 terminal 17. As mentioned above, in the preferred embodiment, IP network 40 is a dedicated IP network 40. The dedicated IP network 40 is a managed IP network in which the resource management and quality of service features of the system are controlled. The dedicated IP network 40 is connected to a network management element or node of the system 10 and one or more access routers 35. In a preferred embodiment, network-managed elements or nodes include, but are not limited to, Internet gateway 60, switching circuits, i.e. voice, gateway 45 and switching circuits, i.e. voice, gatekeeper 55. In a preferred embodiment, voice gateway 45 includes an H.323 gateway and voice gatekeeper 55 includes an H.323 gatekeeper.

In a preferred embodiment, the dedicated IP network 40 communicates with the access router 35 via a wired interface 37. In the preferred embodiment, the dedicated IP network 40 communicates with the operation support system 70, and in particular with the subscriber management platform (SMP) 75 and the network management system (NMS) 80 via each wired interface 36. do.

In a preferred embodiment, the dedicated IP network 40 is connected to various network managed elements, such as the Internet gateway 60, the H.323 gateway 45, and the H.323 gatekeeper via each wired interface 43. Provide access to 55).

The Internet gateway 60 provides a connection to the Internet 65; The dedicated IP network 40 connects to the Internet gateway 60; This allows the end user, or subscriber, of the system 10 to access the internet 65. In a preferred embodiment, the Internet gateway 60 is an inventory network element that supports IP routing and firewall functionality.

In the preferred embodiment, the system 10 uses an architecture specific to the H.323 protocol criteria for providing IP packet voice services. Within the radio access network, as shown in Figure 3, an IP packet voice message is sent between two endpoints. One endpoint 825 is generally an H.323 terminal 822. The other endpoint 825 is another H.323 terminal 822 or switched circuit network 824 supported by the radio access network. The switched circuit network 824 routes the switched transport format voice message generated from the IP packet voice message to the appropriate non-network destination.

Referring to Figure 2, the H.323 gateway 45 is the primary element in the IP voice service supported by the system 10. The H.323 gateway 45 provides an interaction between H.323 and the switched circuit network transport and signaling format.

At the end user or subscriber side, the H.323 gateway 45 resides as an equivalent entity for the H.323 terminal 17. Voice transport packets and signaling are H.323. It is communicated through the system 10 between the terminal 17 and the H.323 gateway 45.

On the network side, the H.323 gateway 45 communicates with the switched circuit network 50. In a preferred embodiment, H.323 gateway 45 communicates with switched circuit network 50 via wired interface 47.

In terms of voice transport transmission, the H.323 gateway 45 provides an interaction between the transport format for the user, for example H.323 terminal 17 side, and the switched circuit network 50 side. On the user side, the H.323 gateway 45 executes the vocoded transport format used by the H.323 terminal 17. In a preferred embodiment, the vocoded transport format is based on the recommended G.7xx series.

On the switched circuit network 50 side, the H.323 gateway 45 supports the ability to handle the switched transmission format of the switched circuit network 50.

The H.323 gateway 45 performs a transcoding function between the vocoded transmission format of each H.323 terminal 17 and the switched transmission format of each switched circuit network 50. If this function is supported, the H.323 gateway 45 appears as another H.323 terminal 17 to the H.323 terminal 17. The H.323 gateway 45 translates the vocoded transport format voice message from the H.323 terminal 17 into the switch circuit network format voice message in an obvious manner for transmission to the switched circuit network 50. On the other hand, the H.323 gateway 45 also provides an explicit way for each vocoded transport format voice message for transmission to the H.323 terminal 17 from the switch circuit network 50 to the H.323 terminal 17. Translate to.

In terms of voice signaling, the H.323 gateway 45 provides an interaction between H.323 call signaling and signaling towards the switched circuit network 50. If this function is supported, the H.323 gateway 45 appears as another H.323 terminal 17 to the H.323 terminal 17. The H.323 gateway 45 is in an explicit manner with the switched circuit network call control and function exchange signal for transmission of the H.323 call control and function exchange signal from the H.323 terminal 17 to the switched circuit network 50. Translate. In the other direction, H.323 gateway 45 sends H.323 call control and function exchange signals for switching circuit network call control and function exchange signals from switched circuit network 50 to H.323 terminal 17. Translate to.

In the preferred embodiment, H.323 gateway 45 is an inventory element purchased from a reference H.323 gateway / gatekeeper vendor.

In a preferred embodiment, H.323 gatekeeper 55 is another major element in the IP packet voice service supported by system 10. The H.323 gatekeeper 55 is a logically separate element from the H.323 gateway 45. However, the physical execution of H.323 gatekeeper 55 may coexist with H.323 gateway 45.

Referring back to Figure 3, each endpoint 825 of the IP packet voice message transmission communicates via a H.323 gatekeeper 820 on a radio access network. The Registration and Acknowledgment and Status (RAS) channels must be assigned to each endpoint 825 and each H before the establishment of any other channel between the endpoint 825 and each H.323 gatekeeper or H.323 gatekeeper 820. Open or built between .323 gatekeepers 820.

The radio access network supports the discovery procedure 830 between the H.323 gatekeeper 820 and one or more endpoints 825 in the radio access network. Discovery procedure 830 is used to inform the potential endpoint of the presence of H.323 gatekeeper 820 for voice transmission. In a preferred embodiment, a manual discovery procedure is used, and H.323 gatekeeper 820 propagates its delivery, i.e., an IP address, to a terrain location or zone or cell. In another embodiment, an automatic discovery procedure is used, with each endpoint 825 initiating a protocol transfer to discover the H.323 gatekeeper 820 with which they can each associate.

If H.323 gatekeeper 820 is discovered by endpoint 825, endpoint 825 executes registration procedure 832 with H.323 gatekeeper 820. Using the registration procedure 832, the endpoint 825 is associated with a zone or cell managed by each H.323 gatekeeper 820 and its associated address, i.e., the base telephone number or the H.164 address of the E.164 address. 323 Announces gatekeeper 820 and its Internet Protocol (IP) address. Registration procedure 832 is executed between H.323 endpoint 825 and H.323 gatekeeper 820 before any IP packet voice transmission between each endpoint 825 and gatekeeper 820 is performed. . Registration establishes a registration and authorization and status channel (RAS) between the endpoint 825 and the H.323 gatekeeper 820.

Referring back to Figure 2, among other functions, H.323 gatekeeper 55 performs an alias address, such as a reference telephone number or an E.164 address, to convey an IP address translation. This translation provides a mapping between the telephone number or E.164 address and the current IP address of the H.323 terminal 17. H.323 gatekeeper 55 dynamically updates each mapping of phone numbers to IP addresses for H.323 terminal 17, which is relocated within the system 10, i. Communicate with or reflect the current physical location of 17).

Referring back to FIG. 3, when the endpoint 825 is registered at each H.323 gatekeeper 820, the H.323 gatekeeper 820 periodically executes a re-registration procedure 834. Once endpoint 825 registers with each gatekeeper 820, H.323 gatekeeper 820 may use each RAS channel established between them to execute bandwidth management procedure 838. Bandwidth management procedure 838 establishes the bandwidth that endpoint 825 can use for sending each packet voice message.

When endpoint 825 registers with H.323 gatekeeper 820, H.323 gatekeeper 820 establishes each RAS channel established between them to execute status procedure 840 on endpoint 825. Can be used. State procedure 840 provides the H.323 gatekeeper 820 state for the various endpoints 825 registered thereon.

After registration, the endpoint 825 may execute a de-registration procedure 842 at each H.323 gatekeeper 820. Deregistration procedure 842 provides an endpoint 825 mechanism for separating each H.323 gatekeeper 820 from itself.

Moreover, after registration, H.323 gatekeeper 820 and each endpoint 825 can execute call signaling procedure 836. The call signaling procedure 836 establishes a call signaling channel between the H.323 gatekeeper 820 and the endpoint 825 to maintain successive IP packet voice messages, ie, IP phone calls between them. In the preferred embodiment, call signaling procedure 836 uses the H.225.0 protocol to establish a call signaling channel between H.323 gatekeeper 820 and endpoint 825. The established call signaling channel is maintained for the duration of the IP phone call. In a preferred embodiment, the symmetric signaling method of Annex D / Q.931 is used for the call signaling procedure; That is, the Q.931 protocol message is used by the call signaling procedure 836.

An initial call signaling message, i.e., an initial transport message, is sent between the endpoint 825 and the H.323 gatekeeper 820 over a previously established RAS channel. In a preferred embodiment, all successive call signaling messages are sent over the established call signaling channel.

When an IP packet voice message, i.e. an IP telephone call, is between two H.323 terminal endpoints 822, each H.323 gatekeeper, or H.323 gatekeeper 820, calls and calls H. Routes applicable Q.931 protocol messages between 323 terminals 822. When an IP telephone call is between H.323 terminal 822 and switched circuit network 824, each H.323 gatekeeper or H.323 gatekeeper 820 may be assigned a Q.931 on H.323 terminal 822. Route the switched circuit format message generated from the protocol message to the switched circuit network 824 and, in the other direction, route the Q.931 protocol message generated from the switched circuit format message of the switched circuit network 824 to the H.323 terminal ( Route 822).

The H.323 gatekeeper 820 may determine to complete the call signaling protocol at the calling / called endpoint 825. In the case of an H.323 terminal 822 for switched circuit network 824 IP telephone calls, each H.323 gatekeeper, or H.323 gatekeeper 820, handles H.323 call signaling, It directs H.323 call signaling towards each H.323 gateway. The H.323 gateway then provides processing to interact with H.323 signaling in the switched circuit network signaling format.

The H.323 gatekeeper 820 may alternatively direct the calling / called endpoint 825 to connect call signaling through each other without requiring the services of an H.323 gateway.

H.323 gatekeeper 820 also supports call control procedure 844 for IP packet voice call control. As shown in Figure 4, the call control procedure 844 includes a master / slave decision procedure 852, a capacity exchange procedure 854, a logical channel signaling procedure 856, a mode request procedure 858, a round trip delay. Various procedures including, but not limited to, decision procedure 860 and hold loop signaling procedure 862.

The master / slave decision procedure 852 includes functionality for resolving conflicts between two H.323 endpoints 825 attempting to open a bidirectional channel. Therefore, the master / slave decision procedure 852 determines that the H.323 endpoint 825 acts as a mast of the IP packet voice channel and acts as a slave for subsequent call control purposes.

The capacity exchange procedure 854 is intended to support H.323 terminal 822 state, or reporting, their receive and transmit functions, and to operate in various mode combinations simultaneously on each H.323 gatekeeper 820. Includes abilities. In the preferred embodiment, the fixed vocoder type mode of operation and the receive and transmit functions are defect functions of each H.323 terminal 822. In a preferred embodiment, H.323 terminal 822 is required to report their mode of operation, or modes and their reception and transmission capacity for H.323 gatekeeper 820, and no defects are assumed.

The logical channel signaling procedure 856 includes the functionality for opening, ie establishing and closing, or de-allocation of logical channels for IP packet voice transmission. In a preferred embodiment, a unidirectional logical channel is opened, established or allocated for each IP packet voice message, thus symmetric operation is supported, whereby the number and type of message streams differ in two, i.e. in the calling and calling direction. It becomes possible.

The mode request procedure 858 includes a function for the H.323 terminal 822 to indicate the criteria for the other H.323 terminal 822 involved in each IP telephone call transmission mode. H.323 terminal 822 agrees with the desired transport mode request if they can.

The mode request procedure 858 includes a function for the H.323 terminal 822 to indicate the criteria for the transmission mode of each H.323 gatekeeper. Furthermore, H.323 gatekeeper 820 may use mode request procedure 858 to indicate the criteria for the transmission mode of each H.323 terminal. The required entity, i.e., H.323 terminal 822 or H.323 gatekeeper 820, agrees to the preferred transmission mode if they can.

The round trip delay determination procedure 860 includes functionality for determining the transmit and receive H.323 terminals 822 included in the IP telephone call. The round trip delay determination procedure 860 includes functionality for determining a round trip delay between the H.323 terminal 822 and the H.323 gatekeeper 820 involved in the IP telephone call.

The sustain loop signaling procedure 862 includes a function for establishing a sustain transport loop to verify the IP packet voice transport channel in the network.

In a preferred embodiment, H.323 gatekeeper 820 is an inventory element purchased from a reference H.323 gateway / gatekeeper vendor.

Referring to Fig. 2, the switching circuit network 50 is a network to which voice or telephone calls can be routed. The switched circuit network 50 may include, but is not limited to, a public switched telephone network (PSTN) or an integrated service digital network (ISDN).

In a preferred embodiment, network 10 includes one or more customer wireless premises units (CPRUs) as shown in FIG. 2A. CPRU 23 is associated with a home or business premises. CPRU 23 is associated with one or more computing devices 20 such as, for example, personal computers (PCs), smart terminals, or each workstation located in or around each premises. In a preferred embodiment, the CPRU 23 communicates with the computing device 20 in each premises via the wired interface 24. In a preferred embodiment, computing device 20 and CPRU 23 include a terminal 31. Terminal 31 is equivalent to terminal 21 in network 10, except that terminal 31 is considered a fixed terminal and terminal 21 is considered a movable and transferable terminal.

CPRU 23 may be connected to one or more voice access devices, such as, for example, telephone 15 located in or around each premises. In a preferred embodiment, the CPRU 23 communicates with the voice access devices in each premises over the wired interface 24. In the preferred embodiment, the voice access device and CPRU 23 comprise a terminal 33. Terminal 33 is equivalent to terminal 17 in network 10 except that terminal 33 is generally regarded as a fixed terminal and terminal 17 is considered a movable or transferable terminal.

The CPRU 23 communicates with a base transceiver station 30, referred to as a base station that supports cell or terrain location, and the CPRU 23 is located wirelessly, ie on the air interface 27. Base station 30 includes equipment, components, and software needed for bidirectional communication with one or more CPRUs 23.

In a preferred embodiment, base station 30 and CPRU 23 of network 10 are not limited to a single resource description that identifies each resource, namely, resource type, variation of a particular resource type, and resource location. Monitor the state of its own hardware resources for the network 10, including. The hardware resource information of each base station 30 or CPRU 23 is provided to the network 10 by the base station 30 or CPRU 23 when each base station or CPRU power is turned on or reset. Hardware resource information of each base station 30 or CPRU 23 is also provided to the network 10 by the base station 30 or CPRU 23 as part of each hardware defect status recording.

In a preferred embodiment, base station 30 and CPRU 23 of network 10 are not limited to resource type identification and variations of respective software or firmware executing on each base station 30 or CPRU 23. Monitor the status of its own software and firmware resources for the containing network 10. Software / firmware resource information of each base station 30 or CPRU 23 is provided to the network 10 by the base station 30 or CPRU 30 when the power of each base station or CPRU is turned on or reset.

In a preferred embodiment, at least one variant of all the software and firmware files required for base station operation is placed in non-volatile base station memory of each base station 30 of the network 10. As such, in a preferred embodiment, at least one variant of all software and firmware files required for the customer premises radio unit (CPRU) operation is placed in the non-volatile CPRU memory of each CPRU 23 of the network 10. In the preferred embodiment, base station 30 and CPRU 23 of network 10 support respective software and firmware updates. Base station 30 and CPRU 23 of network 10 support each complete software / firmware variant update.

The software and firmware files of each base station 30 and CPRU 23 in the network 10 include customization parameters appropriate for each base station 30 and CPRU 23.

Base station 30 and CPRU 23 in network 10 create and maintain hardware / software / firmware states and provide the states to network 10. The hardware / software / firmware state of base station 30 or CPRU 23 in network 10 includes the ability of each base station 30 or CPRU 23 to support radio access services.

Self-testing is performed by powering on and restoring each base station 30 and CPRU 23 in the network 10 to verify each correct operation. The self test for the base station 30 and the self test for the CPRU 23 each include a loop test for verification of the radio broadcast interface 27.

Each base station 30 and CPRU 23 in the network 10 supports self-management functions for detecting defects due to respective device, processing, communication, quality of service and environmental conditions. Each self-management function further assists in providing fault correction to the network 10 through hardware status fault recording. In the preferred embodiment, the recorded defects include the defect type, defect degree and defect component identification of each base station 30 or CPRU 23. The self management function of each base station 30 and CPRU 23 in the network 10 also includes detecting when an already detected fault is stopped or itself is correct.

In the preferred embodiment, each time the base station 30 of the network 10 operates. Perform a measurement acquisition function. In a preferred embodiment, the measurement collection function is not limited, but uplink radio quality and signal strength, radio broadcast, channel, in-process (on each base station 30) for all to be busy (ie busy). That is, unused signal strength, radio broadcast channel, radio broadcast interface success rate, and base station radio broadcast resource utilization.

The measured and / or collected values or results are recorded in the network 10 based on the network configuration recording period. Any base station 30 of the network 10 may be required by the network 10 to terminate the measurement record.

The radio access system, or network 100 shown in FIG. 5, is an optional radio access system, or network. The wireless access system 100 includes a wireless router and collector (WRC) 90 located above the base station 28. The WRC 90 performs the function of a radio access router. The functions supported by the WRC 90 include the concentration of communication links and processing functions. The WRC 90 also supports subscribers, for example end user, management and authentication functions. In addition, on the network side, the WRC 90 supports suspension of radio broadcast encryption processing for transport, ie voice, data, and message transmission.

In a preferred embodiment of system 100, the radio function, ie, the radio broadcast interface communication of system 100, is based on GPRS (general packet radio service) and SGM (global system for mobile communication) protocols. In another embodiment, the wireless functionality of system 100 is based on the GSM / Edge (Enhanced Data Rate for Global System / GSM Deployment for Mobile Communications) protocol.

In addition, the system 100 is not limited to, but is not limited to, Global System for Mobile Communications (GSM), Digital AMPS (DAMPS), DECT, Wideband Code Division Multiple Access (WB-CDMA), Wideband Time Division Multiple Access (WB-TDMA), PHS Each wireless, ie radio, or other communication system, or protocol, platform, or communication standard, including IS-661, Personal Communication System (PCS), PACS, and all derivatives may be used.

Provides termination of network side functions for mobility management of WRC 90. In a preferred embodiment of the system 100, using the WRC 90 in the system 100, the Reverse Address Resolution Protocol (RARP) may be used to support the transmission characteristics of the terminal 21 or the H.323 terminal 17. Used. In another embodiment, Mobile Internet Protocol (IP) is used in system 100 to support the transport feature of terminal 21 or H.323 terminal 17. In another embodiment, a generic Packet Radio Service (GPRS) protocol is used in the system 100 to support the transmission characteristics of the H.323 terminal 17. In the preferred embodiment of the system 100, a significant amount of functionality has been passed from the base station 28 to the WRC 90. This makes the platform of each base station 28 lighter.

In the preferred embodiment shown in FIG. 6, the centralized operations center is not limited to a wireless access system, or network, and various network nodes including, but not limited to, base stations, Internet gateways, H.323 gateways and H.323 gatekeepers, and protocol platforms. Or support the management of elements. In a preferred embodiment, network management architecture 150 for a radio access network includes network element management layer (NEML) 160, network management layer (NML) 170 and service management layer (SML) and business management layer (BML). (Total 180). In a preferred embodiment, network element management is provided by a mix of off-the-shelf and on-demand platforms that serve as first-level administrators of a particular domain. In a preferred embodiment, network element management layer 160 includes a network management domain 162 for managing a network gateway domain, that is, a gateway element, a router management platform 164 for managing a network router domain, ie, a router element, and It consists of a radio access network management platform 166 for managing network base station domains, i.

Gateway management platform 162 provides the provision, control, status monitoring and performance monitoring of the network gateway. In a preferred embodiment, gateway management platform 162 provides the provision, control, health monitoring and performance monitoring of a network gatekeeper. In a preferred embodiment, the gateway management platform 162 includes off-the-shelf management platforms supported by respective Internet gateways and H.323 gateways and / or H.323 gatekeeper vendors.

The router management platform 164 provides network router provision, control, status monitoring and performance monitoring. In a preferred embodiment, the router management platform 164 is a ready-made management platform supplied by the router vendor.

The radio access network management platform 166 is a general purpose management platform for managing the base station 30 of a radio access network. In one embodiment, the radio access network management platform 166 provides the ability to manage the base station 28 and wireless router and concentrator (WRC) 90 of the network, or system 100.

Network management layer 170 includes a proportional network node management (NNM) platform 172 for providing centralized network node management. In a preferred embodiment, network node management platform 172 integrates the various management needs of the base stations of the various gateways, gatekeepers, routers, and radio access networks into an integrated management view. Network node management platform 172 provides, but is not limited to, standard network management functions including structure, defect, and performance management. Additionally, network node management platform 172 includes an architecture that integrates event management, database control, and general network nodes, or elements, security failures for each radio access network.

In a preferred embodiment, the network node management platform 172 is not limited to a standard API for connecting third party applications to a radio access network to include troubleshooting and error management, property management and system, service and functional analysis. (Application Platform Interface).

The service management and business management layer 180 includes a subscriber management platform (SMP) 182. Referring to FIG. 7, a subscriber management platform (SMP) 182 supports various subscriber-oriented functions or procedures. In a preferred embodiment, the SMP 182 may include a customer registration procedure 191, a customer authentication procedure 192, a customer speed procedure 193, a customer billing procedure 194, and a customer management procedure 195. Support.

The customer registration procedure 191 includes, but is not limited to, the collection, storage, and management of customer data for customer provisioning and billing. The customer data includes a subscriber profile of each customer, including but not limited to service subscription information and other parameters assigned to each subscriber of the network for the agreed contract.

The customer authentication procedure 192 provides network protection against fraud. In a preferred embodiment, the radio access network supports both subscriber authentication and terminal authentication functions. For packet data services, subscriber authentication is performed through radio access and Internet Protocol (IP) network nodes in an end-to-end, ie, flow, and generally transparent manner. For voice services, subscriber authentication is typically performed between the H.323 terminal and the gatekeeper. In a preferred embodiment, the challenge / response process and challenge signal change authentication protocol (CHAP) are used for subscriber authentication. In another embodiment, user id / password description and password authentication protocol (PAP) are used for subscriber authentication.

Terminal authentication in a radio access network is used to authenticate terminals or H.323 terminals using the network. In a preferred embodiment, terminal authentication includes three network components: the WM 700 of the terminal or H.323 terminal shown in FIG. 8, and the base station 704 of the cell or zone in which the WM 700 is deployed. ), And a subscriber management platform (SMP) 708 of a radio access network. When using a Customer Premise Radio Unit (CPRU), terminal authentication generally includes each CPRU, the base station of the cell or zone in which the CPRU is located, and the SMP of the radio access network.

The VM 700 automatically executes a terminal authentication process when power is turned on or moved, or transferred, that is, when it is moved from each terminal or H.323 terminal to a new base station cell. In the preferred embodiment, the VM 700 communicates with each base station 704 for terminal authentication via a terminal management protocol (TMP). VM 700 has a secret key installed in a factory; The secret key is associated with a single universal identifier of the WM; That is, WM International Mobile Subscriber Identification (IMSI). The VM 700 includes dedicated circuitry and / or software to calculate a response to the terminal authentication challenge indicated by the subscriber management platform (SMP) 708 of the radio access network using the secret key.

Base station 704 acts as a relay between WM 700 and SMP 708 for terminal authentication. Base station 704 communicates with WM 700 for terminal authentication through a terminal management protocol (TMP). The Secure Logical Link Control (LLC) protocol is an underlying communication protocol as further discussed in connection with FIG. 12.

In a preferred embodiment, the base station 704 communicates with a subscriber management platform (SMP) 708 of the radio access network for terminal authentication via a Remote Authentication Dial In Service (RADIUS) protocol. Insecure User Datagram Protocol (UDP) is an underlying transport protocol for the RADIUS protocol as further discussed in connection with FIG. 12.

After execution of the terminal authentication protocol between the WM 700 and the network, that is, the subscriber management platform (SMP) 708, the base station 704 maintains the terminal authentication state of each WM 700. Base station 704 then uses the WM terminal authentication status to accept or reject WM 700 following access to the network. For example, base station 704 will deny network access to WM 700 that has not been properly authenticated in advance via a terminal authentication procedure.

Subscriber management platform (SMP) 708 stores the WM 700 identification and each secret key pair. When an "Access Request" message is received by the SMP 708 from the WM 700 via the base station 704 requesting access to the network, the SMP 708 responds to an "Access Challenge" message. In a preferred embodiment, the "access challenge" message includes any number. After receiving an "Access Challenge" message from SMP 708 via base station 704, VM 700 responds accordingly. After receiving the WM response back through the base station 704, the SMP 708 will " accept access " to the WM 700 via the base station 704 if the WM receive response is the correct response to the " access challenge " message. Send it. If not, the SMP 708 sends an "access denied" to the WM 700 via the base station 704.

In a preferred embodiment, the "vendor specific" field supported by the RADIUS protocol is included in the "accept access" message sent between each WM 700 and SMP 708. In the preferred embodiment, the "vendor specific" field is included in the "Request access" message sent from the WM 700 to the base station 704 to request access to the services of the network.

The "vendor specific" field is used to carry terminal subscription information. In a preferred embodiment, the "vendor specific" field is used to carry a quality of service (QoS) profile subscribed by an end user, i.e., a subscriber associated with a given WM 700. The QoS profile in the " access request " message is used by receiving base station 704 to polish a service request that is not limited but not covered by WM QoS, for example to reject WM 700.

The CPRU operates in the same manner as the WM 700 for terminal authentication. Each CPRU automatically handles terminal authentication after power up. In a preferred embodiment, the CPRU communicates with each base station for terminal authentication via terminal management protocol (TMP). CPRU has a secret key installed in the factory; The secret key is associated with a CPRU single scale identifier, namely CPRU International Mobile Subscriber Identity (IMSI). The CPRU includes circuitry and / or software to calculate a response using the secret key to provide the terminal authentication challenge indicated by the subscriber management platform (SMP) of the radio access network.

The base station acts as a relay between the CPRU and the SMP for terminal authentication. In addition, after executing the terminal authentication protocol between the CPRU and the network, that is, the subscriber management platform (SMP), each base station maintains the terminal authentication status of each CPRU. The base station then uses the CPRU terminal authentication status to accept or reject the CPRU following access to the network. For example, a base station will deny network access to a CPRU that has not been properly authenticated in advance via a terminal authentication procedure.

With reference to FIG. 7, the customer speed procedure 193 includes, but is not limited to, the formation and maintenance of a flexible pricing plan.

The customer billing procedure 194 supports the generation of flexible customer billing. The customer billing procedure 194 also supports real time and invoice based cost requirements. The customer billing procedure 194 supports one or more multiple call systems, or networks, such as subscriber's billing customer.

The customer management procedure 195 creates and provides network management access to the customer, i.e., subscriber information, including but not limited to subscriber profile, subscription activity, and customer calculation balance. In a preferred embodiment, the subscription profile includes, but is not limited to, customer identification, customer service support requests, and subscribed quality of service (QoS). In a preferred embodiment, subscription activity information includes, but is not limited to, allowing each subscriber on time to use each service supported by the network. In a preferred embodiment, the customer calculation balance includes, but is not limited to, the amount of money, for example dollars, with each subscriber being obligated to pay for the services used on the network.

The radio access network includes four schemes for communication as shown in FIG. Signaling plan 200 includes a packet data signaling plan 205 for packet data delivery, or signaling for transmission. Signaling plan 200 includes a voice signaling plan 210 for communicating packet transmission for packet voice delivery, or transmission.

The delivery plan 220 includes a packet data delivery plan 225 for packet data transmission. The delivery plan 220 includes a voice delivery plan 230 for IP packet voice transmission.

In a preferred embodiment, the packet data signaling plan 205 is a packet data delivery plan 225, i.e., a packet data transmission plan, a function, or procedure for controlling, supporting and maintaining the function as shown in FIG. 240).

The packet data signaling planning procedure 240 includes a procedure 201 for establishing an initial connection of a terminal, that is, setting up a physical transmission path, or connection, or communication channel from the terminal's wireless modem (WM) to the cell's base station. In this case, the terminal is arranged for later reception and transmission of packet data. The connection establishment procedure 201 includes a function for establishing a physical transmission path, or connection, or communication channel from a customer premise radio unit (CPRU) including a terminal to a cell's base station, the terminal being configured for IP packet data. It is arranged for later reception and transmission.

The packet data signaling plane procedure 240 also includes a sequential allocation-release or release procedure 207 of the established packet data transmission path.

Packet data signaling plane procedure 240 also includes a terminal authentication procedure 202. Packet data signaling procedure 240 also includes a dynamic assignment procedure 203 of a radio access network of Internet Protocol (IP) to the terminal.

The packet data signaling plane procedure 240 is also used for the terminal communication addressing in the radio access network, for the radio modem (WM) or CPRU of each terminal to assign a temporary logical link layer address, i.e., network allocation procedure of the temporary logical link identity (TLLI). 204 TLLI is a temporary terminal identity that provides subscriber confidentiality; In other words, using TLLI, user identities on the over-the-air interface of a radio access network are protected from disclosure to unauthorized users, entities or processes. The next purpose of using TTLI is to protect the privacy of the subscriber's identity using the over-the-air resources of the radio access network.

TTLI identifies a network terminal. In a preferred embodiment of the invention, the relationship between the TLLI and the fixed address of the terminal, i.e., the International Mobile Subscriber Identity (IMSI) of the terminal, is each WM of the terminal or each CPRU of the terminal, and a network base station connected with the terminal. Only known. In a preferred embodiment of the present invention, the terminal's IMSI is used as the radio access subscriber authentication value and its billing identity.

IMSI consists of a mobile area code (MCC), a mobile network code (MNC) and a mobile station identification number (MSIN). Specific, unique, mobile network codes are associated with radio access networks.

The TTLI is assigned to a terminal at power up and when the terminal is relocated to a selected base station cell in the network. TLLI is assigned by terminal management protocol (TMP) signaling between each WM of a terminal, or CPRU of a terminal and the base station to which it is connected. The base station connected with the WM assigns a specific TLLI to the WM of the terminal. In addition, the base station connected with the CPRU includes a procedure 206 of establishing an encryption mode for packet data transmission. In a preferred embodiment of the present invention, the encryption scheme is based on the public key scheme using the RC4 algorithm. The encryption configuration allows the key exchange procedure to be performed as a signaling exchange between the WM of the terminal and the base station of the cell in which the terminal is located when the WM is powered and the terminal is relocated to the select base station cell in the network. Similarly, the encryption configuration causes the key exchange procedure to be executed as a signaling exchange between the CPRU of the terminal and the base station of the cell in which the terminal is located when powering up the CPRU. Terminal Management Protocol (TMP) is used to assist in cryptographic signaling.

In a preferred embodiment of the present invention, the encryption procedure 206 is not limited to the above embodiment, but it is possible and impossible to encrypt the packet data transmission on the over-the-air interface between the WM or CPRU and each base station. It includes. Encryption procedure 206 also assists in that if encryption is enabled, the deviation of the key is used to encrypt and decrypt the message. In a preferred embodiment of the present invention, if encryption is enabled, an encryption key is supplied to each logical link control (LLC) layer on which each WM or CPRU and base station protocol is stacked, as discussed further with reference to FIG. 17. .

The packet data transport or transport plane 225 of FIG. 9 is a wireless sub-network that operates the underlying structure of the Internet Protocol (IP). In a preferred embodiment of the present invention, the packet data transport plane 225 includes a stacked protocol structure that supports user information, i.e. packet data transmission, wherein the user information data carries a control procedure. The user information data information is not limited to the present invention and transmits a control procedure including packet data transmission flow control and data transmission error detection, error correction and error recovery.

In a preferred embodiment of the present invention, voice signaling plane 210 includes a function or procedure 245 for controlling, supporting and maintaining voice transport plane 230, i.e., the voice transport plane shown in FIG. .

The voice signal plane procedure 245 is a procedure 211 for initial connection establishment of an H.323 terminal, i.e., H.323 from a wireless modem (WM) of an H.323 terminal for continuous reception and transmission of IP packet voice messages. It includes the establishment of a physical transmission path, or connection, or communication channel to the base station of the cell where the terminal is located. The connection establishment procedure 211 is also used for the cell in which the H.323 channel is located from a Customer Premises Premises Radio Unit (CPRU) including an H.323 terminal for the continuous reception and transmission of IP packet voice messages. It includes functionality for establishing a physical transmission path, or connection, or communication channel to a base station.

Voice signal plane procedure 245 includes a procedure 214 for the continuous de-allocation or release of established IP packet voice transport channels or paths.

Voice signal plane procedure 245 also includes a procedure 216 for subscriber and terminal authentication. Voice signaling procedure 245 also includes a procedure 212 for radio access network dynamic allocation of Internet Protocol (IP) addresses for H.323 terminals.

Voice signal plane procedure 245 is a temporary logical link layer address, i.e., assignment of a network of temporary logical link identity (TTLI) to wireless modems (WMs) or CPRUs of H.323 terminals, respectively, for terminal communication addressing in a radio access network. It further comprises a procedure (213) for. The TTLI identifies network H.323 terminals such as, for example, telephone, personal computer (PC) and wireless modem (WM) combinations or telephone and customer premise radio unit (CPRU) combinations. In an embodiment, the relationship between the TTLI and the fixed address of the H.323 terminal, i.e., the International Mobile Subscriber Identity (IMSI) of the H.323 terminal, is the network with which each WM or CPRU and H.323 of the H.323 terminal communicates. Known for its base station.

TTLI is assigned to H.323 terminals when power-up and H.323 terminals are reassigned to alternative base stations in the network. TTLI is assigned via terminal management protocol (TMP) signals between each WM or CPRU of an H.323 terminal and the base station communicating with them. The base station communicating with the WM or CPRU allocates a specific TTLI for each WM or CPRU of the H.323 terminal.

Voice signal plane procedure 245 also includes a procedure 217 for setting an encryption mode for packet voice transmission. In an embodiment, the encryption procedure 217 enables and disables encryption for packet voice transmission on the broadcast interface between the WM or CPRU and each base station without limitation.

The voice transport element or transport plane 230 of FIG. 9 is a wireless subnetwork that operates under the Internet Protocol (IP). In an embodiment, the voice transport element plane 230 includes a layered protocol structure to support user information, namely voice transmission and associated user information voice transmission control procedures. The user information voice transmission control procedure includes, without limitation, IP packet voice transmission flow control and voice transmission error prevention, error correction and error recovery.

An embodiment of the packet data signal plane structure 250 shown in FIG. 12 for use as a terminal including a wireless modem (WM) includes a protocol stack 255 for the WM, a protocol stack 270 for the base station, and Protocol stack 290 for a subscriber management platform (SMP) of a network management system.

In an embodiment, the protocol stack 255 for a wireless modem (WM) includes radio physical layer (RF PHL) 256, radio link control / media access control (RLC / MAC) layer 259, logical link control (LLC). Layer 260 and terminal management protocol (TMP) layer 261.

In an embodiment, the protocol stack 270 for the base station on the wireless modem (WM) side is a radio physical layer (RF PHL) 271, a radio link control / media access control (RLC / MAC) layer 284, logical Link control (LLC) layer 274 and terminal management protocol (TMP) layer 275.

In an embodiment, the radio physical layer 256 of the WM protocol stack 255 and the radio physical layer 271 of the base station protocol stack 270 are each GPRS / GSM (Global System for General Packet Radio Service / Mobile Communication). It includes a radio interface. In an alternative embodiment, the radio physical layer 256 of the WM protocol stack 255 and the radio physical layer 271 of the base station protocol stack 270 each support GSM / Edge (Wide Area System / GSM Emissions for Mobile Communications). Enhanced data rate). Each radio physical layer 256 and 271 each constitute two sublayers conceptually defined by their respective functionality.

The first sublayer, which is the physical RF sublayer, modulates the physical waveform signal for signal traffic for continuous transmission of the broadcast interface between the WM and the base station. The modulation is based on consecutive bits received from the second sublayer, which is the physical link sublayer. The physical RF sublayer also modulates the received waveform signal into consecutive bits for signal traffic and sends it to the physical link sublayer for interpretation.

The second sublayer, which is the physical link sublayer, provides services for the actual signal traffic transmission over the physical radio channel between the wireless modem (WM) and the base station. Physical link sublayer functionality includes signal traffic transmission and includes, without limitation, signal message transmission, unit configuration, data coding, and detection and correction of physical transmission errors, for example and not limited to parity errors. The physical link sublayer uses the services of the physical RF sublayer to perform its functions.

The radio link control / media access control (RLC / MAC) layer 259 of the wireless modem (WM) protocol stack 255 and the RLC / MAC layer 284 of the base station protocol stack 270 each have a radio link control function ( 258 and 273 and media access control functions 257 and 272. In an embodiment, the RLC / MAC layers 259 and 284 of each WM protocol stack 250 and base station protocol stack 270 are based on the GPRS / GSM (Global System for General Packet Radio Service / Mobile Communication) protocol. do. In an alternative embodiment, the RLC / MAC layers 259 and 284 of each WM protocol stack 250 and base station protocol stack 270 are GSM / Edge (enhanced for wide area system / GSM emission for mobile communications). Data rate) protocol.

Respective medium access control (MAC) layers 257 and 272 are used to provide data and signal multiplexing on the uplink and downlink channels of the broadcast interface between the wireless modem (WM) and the base station. Control for multiple transmission functions between the base station and the WM rests with each base station protocol stack 270.

For WM-generated channel access, the MAC layer 257 of the WM protocol stack 250 also provides contention resolution between channel access attempts. Thus, the MAC layer 257 of the WM protocol stack 255 executes a contention resolution protocol when the WM attempts to acquire a communication channel on each base station for continuous communication with the base station.

For WM-generated channel access, MAC layer 272 of base station protocol stack 270 provides contention resolution between two or more terminal attempts to access the same base station channel (channels).

For network-generated channel access, the MAC layer 272 of the base station protocol stack 270 is used to schedule various access attempts. Thus, the MAC layer 272 of the base station protocol stack 270 coordinates subsequent terminal network access attempts when the network attempts to establish a communication channel with the terminal.

The MAC layer 272 of the base station protocol stack 270 first contains functionality for management and transport element packet data exchange, ie, coordination of packet data message transmission.

The radio link control (RLC) layers 258 and 273 of each wireless modem (WM) protocol stack 255 and base station protocol stack 270 establish a radio dependent reliable link on the wireless modem / base station broadcast transport interface. to provide. The RLC layer 258 of the WM protocol stack 250 is used for the transfer, or transmission, of logical link control (LLC) frames of information, ie, packet data signal messages, on the broadcast interface between each WM and the base station. The RLC layer 258 is also used for segmentation of the LLC frame into one or more Radio Link Control (RLC) blocks for physical transmission on the broadcast interface for each base station. The RLC layer 258 also provides functionality for reconstruction of the RLC block received on the broadcast interface into each LLC frame from the base station. The RLC layer 273 of the base station protocol stack 270 transfers logical link control (LLC) frames of information, ie, packet data signal messages, on a broadcast interface between each base station and the terminal's wireless modem (WM), Or is commonly used for transmission. RLC layer 273 is used for segmentation of the LLC frame into one or more Radio Link Control (RLC) blocks for physical transmission on the broadcast interface for each WM. The RLC layer 273 also provides functionality for reconstruction of the RLC block received on the broadcast interface with each LLC frame from the WM of the terminal.

The RLC layer 258 of the wireless modem (WM) protocol stack 255 and the RLC layer 273 of the base station protocol stack 270 are unmodifiable radios transmitted between the base station and the terminal's WM on the broadcast interface. It is used to maintain and execute a reverse error correction procedure that enables selective transmission of a link control (RLC) block.

The RLC / MAC layer 284 of the base protocol stack 270 supports the execution of algorithms for radio resource management functions including, without limitation, communication resources, namely broadcast channel, management and resource, namely broadcast channel scheduling.

The logical link control (LLC) layer 260 of the wireless modem (WM) protocol stack 255 provides a reliable, radio dependent logical link for communication between each WM and the base station. Similarly, logical link control (LLC) layer 274 of base station protocol stack 270 provides a reliable, radio dependent logical link for communication between each base station and the WM. Logical link control (LLC) links are used to transmit packet data signal traffic between the WM and the base station in the packet data signal plane. Thus, the LLC link is first established between them for continuous packet data signal transmission between the WM and the base station. If the terminal is moved to a new base station cell, each WM establishes a new LLC link with the new cell's base station prior to continuing signal transmission between them.

In an embodiment, the LLC protocol used for the logical link control (LLC) layers 260 and 274 of the WM protocol stack 255 and the base station protocol stack 270 is described in GPRL (General Packet Radio Service) specification 04.64. This LLC protocol is designed independently of the underlying radio protocol for broadcast interface transmission. Temporary logical link identification (TLLI) assigned to the terminal is used for addressing in LLC layers 260 and 274.

The wireless modem (WM) protocol stack 255 and the TMP layer 275 of the base station protocol stack 270 provide peer-to-peer procedures between each WM and base station to support network terminal management procedures. The TMP 261 and 275 layers of each WM protocol stack 255 and base station protocol stack 270 provide various procedures, which are the functions 740 shown in FIG.

Each TMP layer 261 and 275 supports a procedure for terminal authentication 742. In general, terminal authentication procedure 742 prevents unauthorized use of each radio access network. Terminal authentication procedure 742 is also used to prevent fraudulent impersonation of legitimate users or subscribers on the network. The terminal authentication procedure 742 of the embodiment has been described above with reference to FIG.

The TMP layers 261 and 275 of each WM protocol stack 255 and base station protocol stack 270 also support the setup, or setup, 744 of the encryption function for continued transport element packet data exchange transmission. Each TMP layer 261 and 275 supports key exchange signal transmission between them for encryption and decryption of the carrier element packet data exchange transmission between the WM and the base station. The encryption setup function 744 terminates on the base station with which the WM communicates and thus does not require any interaction within the base station for further upstream network management or control.

Each TMP layer 261 and 275 includes a procedure 746 for signal transmission required for the assignment of temporary logical link identification (TLLI) to the wireless modem (WM) of each terminal for terminal communication addressing purposes. . TTLI is used to address terminals in LLC layer 260 of WM protocol stack 255 and LLC layer 274 of base station protocol stack 270. The assigned TTLI is provided to each LLC layer 260 and 274 by each TMP layer 261 and 275. The TTLI assignment signal is between the WM and the base station, and the TTLI is assigned to the WM by the base station.

The TMP layer 261 of the WM protocol stack 255 and the TMP layer 275 of the base station protocol stack 270 are dynamic assignments of the network of IP (Internet Protocol) addresses 748 to the wireless modem (WM) of the associated terminal. Support each signal transmission required for Dynamic IP address assignment supports the transport of terminals within a radio access network.

In an embodiment, the broadcast address resolution signal for IP address assignment is based on Reverse Address Resolution Protocol (RARP). At the network side, the base station with which each WM communicates interacts with the broadcast address resolution signal as a RARP signal for transmission to each access router. The network signal for dynamic IP address assignment establishes a bridge through the base station for the continuous delivery or transmission of packet data, voice and signaling messages between each WM and the access router of the radio access network.

In an embodiment, the base station provides an interaction function between the wireless modem (WM) of the terminal and the subscriber management platform (SMP) of each network management system (NMS). In an embodiment, the protocol stack 270 for interaction of a base station with a subscriber management platform (SMP) includes a T1 interface layer 276, a frame relay layer 277, an Internet protocol (IP) layer 278, a user. Datagram protocol (UDP) layer 279 and RADIUS client 280 layer. In an embodiment, the protocol stack 290 for SMP includes an IP layer, UDP layer 282, and a RADIUS server layer 281.

RADIUS is an Internet Protocol (IP) based on the protocol used to carry authentication and structure information between client entities on the network, that is, subscriber terminals and shared authentication servers. In an embodiment, the base station acts as a proxy RADIUS client for all wireless modems (WMs) located in the cell and implements the RADIUS protocol with the subscriber management platform of each network management system (NMS) in the network. SMP acts as a RADIUS server.

The RADIUS protocol and RADIUS client layer 280 of the base station protocol stack 270 is used to receive and transmit signaling information, or packets or messages, for terminal authentication procedures for subscriber terminals in the network. The RADIUS protocol and RADIUS server layer 281 of the SMP protocol stack 290 are similarly used to send and receive signaling information for terminal authentication procedures.

The base station is a broadcast terminal authentication protocol between each base station and the terminal's wireless modem (WMs) in a cell with a RADIUS client-server protocol running between the base station and the subscriber management platform (SMP), which acts as a network's RADIUS server. To interact with. In an embodiment, the network uses an MD5 authentication algorithm. In a wireless access system running an MD5 authentication algorithm, both endpoints or network nodes are WMs and SMPs that act as RADIUS servers in the network.

The RADIUS protocol and RADIUS server layer 281 of the SMP protocol stack 290 and the RADIUS client layer 280 of the base station protocol stack 270 also provide a subscriber management platform that transmits and receives subscriber profile information to or from the base station. SMP).

As described above, in an embodiment, the protocol stack 270 may include a T1 interface layer 276 and a frame relay layer 277 for interaction of the base station with the subscriber management platform (SMP) of each network management system (NMS). , An Internet Protocol (IP) layer 278, a User Datagram Protocol (UDP) layer 279, and a RADIUS client layer 280. In addition, as described above, the protocol stack 290 for a subscriber management platform (SMP) includes an IP layer 283, a UDP layer 282, and a RADIUS server layer 281.

In an embodiment, the user data protocol (UDP) layer 279 of the base station protocol stack 270 and the UDP layer 282 of the SMP protocol stack 290 are non-secure datagrams, i.e., non-secure, from a network to a peer entity. It provides a basic mechanism for each network entity to send and receive signaling messages. In the packet data signal plane, each UDP layer 279 and 282 is used to transmit the RADIUS protocol between the base station and the subscriber management platform (SMP) of the radio access network.

The Internet protocol (IP) layer 278 of the base station protocol stack 270 and the IP layer 283 of the subscriber management platform (SMP) protocol stack 290 route RADIUS protocol signaling messages between the SMP and the base station of the network. Supports a connectionless network transport layer protocol for configuration. In an embodiment, each IP layer 278 and 283 uses IP version 4. In an alternative embodiment, each IP layer 278 and 283 uses IP version 6.

In an embodiment, IP layer 278 of base station protocol stack 270 meets the requirements described in RFC 1490, a standard for executing IP messages over a frame relay transport channel. In an embodiment, the flame relay layer 277 of the base station protocol stack 270 provides a link layer transport protocol between the base station and the system via an access router, not shown. Typically, frame relay is used for signal information and transport element exchange transfer, i.e. transmission, for example voice and data information or messages. In particular, in the packet data signal plane, the frame relay layer 277 of the base station protocol stack 270 is used to transmit signal information, or messages, between each base station and subscriber management platform (SMP) in the network via an access router. Used.

In an embodiment, for the transmission of signal information, permanent virtual circuits (PVCs) are used for each base station, and the frame layer protocol runs on the Internet Protocol (IP).

The T1 interface layer 276 of the base station protocol stack 270 includes protocols and procedures for maintaining a physical T1 communication interface between each base station and an access router (not shown). The T1 communication interface is a standard wired interface. Especially in the packet data signal plane, the T1 interface layer 276 of the base station protocol stack 270 is used to transmit signal information or messages between the base station and subscriber management platform (SMP) of the network via an access router.

An embodiment of the packet carrying element plane structure 370 shown in FIG. 14 for use as a terminal including a wireless modem (WM) includes a protocol stack 300 for a terminal's personal computer (PC), a terminal's wireless modem ( Protocol stack 320 for WM, protocol stack (or base transceiver station (BTS)) 340 for base station, and protocol stack 360 for access router.

In an embodiment, the protocol stack 300 for a PC includes a physical link layer 306, a modem command layer 304, an internet protocol (IP) layer 306, and an application layer 308. In an embodiment, the protocol stack 320 for each wireless modem (WM) on the PC-side includes a physical link layer 321 and a modem command layer 322. In an embodiment, the WM acts as a bridge entity between each PC and the base station.

PC physical link layer 302 and WM physical link layer 321 both include functionality to mean a physical wired interface between each wireless modem (WM) and each PC that includes a network subscriber terminal. In an embodiment, the PC physical link layer 302 and the WM physical link layer 321 each support the International Computer Memory Card Association (PCMPIA) protocol.

PC modem command layer 304 and WM modem command layer 322 include modem command functionality for commands and status between each PC and each wireless modem (WM) that is the modem of the WM. In an embodiment, each modem command layer 304 and 322 includes an extended set of synchronous transfer (AT) commands, or protocols, based on the Wide Area System (GSM) specification for mobile communications.

The Internet Protocol (IP) layer 306 of the PC protocol stack 300 in the packet data transport element plane supports network IP to transmit packet data messages between an access router in a network and a terminal in which each PC is a part.

The application layer 308 of the PC protocol stack 300 supports application functions for packet data transmission including, without limitation, flow control and error detection, error correction and error recovery.

In an embodiment, at the base station side, the wireless modem (WM) protocol stack 320 may include a radio physical layer (RF PHL) 323, a radio link control / media access control (RLC / MAC) layer 324, a logical link. A control (LLC) layer 325 and a subnetwork dependent convergence protocol (SNDCP) layer 326. In an embodiment, on the WM side, the base station protocol stack 340 includes an RF PHL layer 341, an RLC / MAC layer 348, an LLC layer 344, and an SNDCP layer 345.

Each RF PHL layer 323 and 341 and base station protocol stack 340 of the WM protocol stack 320 is a WM protocol stack except that the RF PHL layers 323 and 341 support packet data rather than signal traffic transmission. Corresponding to the respective RF PHL layers 256 and 271 of 255 and the base station protocol stack 270 of FIG. 12. Each of the RLC / MAC layers 324 and 348 and the base station protocol stack 340 of the WM protocol includes a WM protocol stack (except that the RLC / MAC layers 324 and 348 support packet data rather than signal traffic transmission). 255 corresponds to RLC / MAC layers 259 and 284 and base station protocol stack 270 of FIG. Each of the LLC layers 325 and 344 and the base station protocol stack 340 of the WM protocol stack 320 includes a WM protocol stack 255 except that the LLC layers 325 and 344 support packet data rather than signal traffic transmission. And each of the LLC layers 260 and 274 and the base station protocol stack 270 of FIG.

In an embodiment, the subnetwork dependent convergence protocol (SNDCP) layer 326 of the wireless modem (WM) protocol stack 320 and the SNDCP layer 345 of the base station protocol stack 340 are each the network's physical radio elements. It includes the portion of the wireless middleware of the network that plugs in, or connects, or overlaps the functionality. Subnetwork dependent convergence protocol (SNDCP) is implemented between the WM and the base station. The SNDCP layer 326 of the WM protocol stack 320 and the SNDCP layer 345 of the base station protocol stack 340 are each characteristic of network level mapping, i.e., over Internet Protocol (IP), data packets and basic network protocols. Support. In an embodiment, each SNDCP layer 326 and 345 supports adaptation of an IP data packet into a broadcast logical link control (LLC) frame for transmission between the base station and the terminal's WM. Conversely, or in the alternative transmission direction, each SNDCP layer 326 and 345 supports adaptation of LLC frames with each IP data packet for subsequent transmission through an access router to an IP gateway and / or IP data network. do.

Each SNDCP layer 326 and 345 supports compression and decompression of message headers of packet data transmitted and received on the broadcast interface between each WM and base station. Compression and decompression of message headers includes, without limitation, compression and decompression of Internet Protocol (IP) data messages.

The SNDCP layer 326 of the wireless modem (WM) protocol stack 320 and the SNDCP layer 345 of the base station protocol stack 340 are the lengths of the data messages and their respective data for continued use in the compression / decompression algorithm. It further provides a mechanism for determining packets. In addition, each SNDCP layer 326 and 345 provides the capability to provide a packet type including standard IP packets, full header packets, and context status packets, without limitation to the compression and decompression algorithms required. The SNDCP layer 326 of the wireless modem (WM) protocol stack 320 and the SNDCP layer 345 of the base station protocol stack 340 provide qualitative services, or QoS functions, for packet data transmission. In an embodiment, the QoS profile for the carrying element data exchange is not a real time profile.

In an embodiment, on the network side, the base station protocol stack 340 for the packet data carrying element plane includes a T1 interface layer 346 and a frame relay layer 347. In an embodiment, the protocol stack 360 includes an T1 internet layer 361, a frame relay layer 362 and an internet protocol (IP) layer 363 for the access router for the packet data carrying element plane. The base station, or base transceiver station (BTS), supports an intra-BTS relay function that relays packet data between the wireless modem-base station interface and the base station-access router interface. In the subscriber-network direction, i.e. upstream, the BTS bridge function extracts Internet Protocol (IP) packets from Subnetwork Dependent Convergence Protocol (SNDCP) and sends IP packets to frame relay layer 347 for continued transmission to the access router. To carry. In an alternative direction, ie network-subscriber or downstream direction, the BTS bridge function extracts IP packets from the frame relay layer 347 and sends them to the SNDCP layer 345 for continuous broadcast transmission to each wireless modem (WM). Carries an IP packet

For a wireless modem (WM) -base station interface, the WM is verified at the transport link layer through temporary logical link identification (TTLI) assigned to the WM. For a base station-network, i.e., an access router that is an interface, each WM is verified at the transport link layer via a virtual circuit (SVC) that is relayed in the frame. In an embodiment, the BTS bridge function will maintain a mapping between each TTLIs and the SVCs of the wireless modem (WM) of each terminal. In an embodiment, this mapping, or bridging, is performed on two interfaces, the WM-base station interface and the base station-network, i.e., the Subscriber Management Platform (SMP) interface as part of the customer record procedure executed for each subscriber terminal. It is set dynamically as part of the address assignment procedure.

In addition, the BTS bridge function allows the base station to act as a transport link layer that eliminates the difficulty for establishing an IP data transmission path within the base station.

Each of the T1 interface layers 346 and 361 of the base station protocol stack 340 and the access router protocol stack 360 shows that T1 interface layers 346 and 361 support packet data rather than signal traffic transmission. Corresponding to each T1 interface layer 276 of twelve base station protocol stacks 270. Each of the frame relay layers 347 and 362 of the base station protocol stack 340 and the access router protocol stack 360 shows that the frame relay layers 347 and 362 support packet data rather than signal traffic transmission. Corresponds to the frame relay layer 277 of the base station protocol stack 270 of twelve.

The access router (IP) layer 363 supports Network Internet Protocol (IP) to transfer packets to or from the base station and eventually the subscriber station via or via a access router to a data network such as the Internet, for example. An embodiment of the voice signal plane structure 490 shown in FIG. 15 for use as a terminal including a wireless modem (WM) is a protocol stack 400 and a respective H for a personal computer (PC) of an H.323 terminal. Protocol stack 420 for a wireless modem (WM) of a .323 terminal. Voice signal plane structure 490 also includes a base station, or base transceiver station (BTS), a protocol stack 460 for an access router, and a protocol stack 480 for an H.323 gateway / gatekeeper combination network node. .

In an embodiment, the protocol stack for a personal computer (PC) includes an H.245 protocol layer 401, a Q.931 protocol layer 402, a RAS protocol layer 402, a transmission control protocol (TCP) layer 404, A user data program protocol (UDP) layer 406, an internet protocol (IP) layer 405, a modem command layer 415, and a physical link layer 416. The IP layer 405 of each physical link layer 416, modem command layer 415, and PC protocol stack 400 has traffic to the physical link layer 416, modem command layer 415, and IP layer 405. Except for transmitting voice signals rather than packet data that is the sender, each corresponds to a physical link layer 302, a modem command layer 304, and an IP layer 306 of the PC protocol stack 300 of FIG. In an embodiment, the H.323 gateway / gatekeeper protocol stack includes an H.245 protocol layer 401, a Q.931 protocol layer 422, a RAS protocol layer 423, a transmission control protocol (TCP) layer 424, A user data program protocol (UDP) layer 425, an internet protocol (IP) layer 426, an ethernet layer 427, and a 10 Venice tea interface layer 428.

In an embodiment, the voice signal plane structure 490 conforms to the H.323 specification for the upper transport protocol layer and is a transmission control protocol / Internet protocol (TCP / IP) and user datagram protocol / Internet protocol (the basic transport and network protocol). UDP / IP). According to FIG. 15, all voice signal elements, i.e., respective H.245 protocol layers 401 and 421, respective Q.931 protocol layers 402 and 422, and respective write acknowledgment and status (RAS) protocol layers 403 And 423) are implemented in the PC of the subscriber H.323 terminal and the gateway and gatekeeper of the radio access network.

The H.245 protocol layer 401 of the PC protocol stack 400 and the H.245 protocol layer 421 of the gateway / gatekeeper protocol stack 480 may be configured for H.245 protocol end-to-end channel control, i. Support for the transmission of voice signaling messages governing the operation of each H.323 entity. H.245 protocol control messages include, without limitation, the assignment of logical channel entitlement exchange signals, open or set closing or logical channels, mode reference request signals, flow control message signals and general command and indication signals.

In the radio access network of an embodiment, for example, an H.245 signal between two end points, such as two H.323 terminals, or an H.245 terminal and a respective H.245 signal each running over a TCP / IP connection Routed through a gatekeeper with a message. Each of the TCP layers 404 and 424 and the respective IP layers 405 and 426 of the terminal protocol stack 400 and the gateway / gatekeeper protocol stack 480 are connected between the H.323 terminal PC and the gateway / gatekeeper, respectively. Manage TCP / IP connections

In an embodiment, the call, or voice control signal, is defined within H.225.07, which is part of the H.323 protocol suite. H.225.0 incorporates the DSS-1 recommended Q.931 protocol and defines a set of essential Q.931 control messages. For example, call control signals between two H.323 terminals in a radio access network, or two endpoints, such as an H.323 terminal and a switched circuit network, may be gated with their respective Q.931 executed over a TCP / IP connection. Routed by the keeper. Each of the TCP layers 404 and 424 and each of the IP layers 405 and 426 of the terminal protocol stack 400 and the gateway / gatekeeper protocol stack 480 between the PC and the gateway / gatekeeper of the H.323 terminal. Manage each TCP / IP connection. As described above with respect to FIG. 3, the Write Acknowledgment and Status (RAS) channel executes control signal messages used for gatekeeper recovery, endpoint recording, and endpoint status procedures. The RAS protocol layer 403 of the terminal protocol stack 400 and the RAS protocol layer 423 of the H.323 gateway / gatekeeper protocol stack 480 support protocols for subscriber authentication in a radio access network in the voice signal plane. .

The RAS signal is present between the endpoint, i.e., the H.323 or switched circuit network, and the gatekeeper of the radio access system. In an embodiment, the RAS control message is executed over a UDP / IP channel. Each of the UDP layers 406 and 425 and each of the IP layers 405 and 426 of the terminal protocol stack 400 and the gateway / gatekeeper protocol stack 480 is connected between the PC of the H.323 terminal and the gateway / gatekeeper. Manage each UDP / IP.

In an embodiment, for the network side, the protocol stack 460 for the access router in the voice signal plane structure 490 is the Internet Protocol (IP) layer 433, the Ethernet layer 431 and the 10 base tee interface layer ( 432). The radio access system supports IP packet voice, i.e. IP phone, call, IP layer of the access router protocol stack 460 and IP layer 426 of the H.323 gateway / gatekeeper protocol stack 480, respectively. It supports Internet Protocol (IP) for signaling traffic.

Access routers and gateways or gatekeepers send voice signaling messages between them via an Inetet protocol. Each of the Ethernet layers 431 and 427 of the access router protocol stack 460 and the H.323 gateway / gatekeeper stack 480 supports the Ethernet transport protocol.

The 10BaseT interface layer 432 of the access router protocol stack 460 and the 10BaseT interface layer 428 of the H.323 gateway / gatekeeper protocol stack 480 are each an access router and an H.323 gateway and / or H.323. It contains protocols and procedures for managing physical H.323 communication interfaces between gatekeepers. The 10BaseT communication interface is a standard wired interface. In the voice signaling plane, in particular, each 10BaseT interface layer 432, 428 is used to transmit voice signaling information or messages between the access router and the H.323 gateway and / or gatekeeper.

The subscriber side of the access router protocol stack 460 includes layers equivalent to the access router protocol stack 360 of FIG. 14, except that the layers of the access router protocol stack 460 support voice signaling rather than packet data and traffic transmission. do.

The layer of the wireless modem (WM) protocol stack 420 is the same as the layer of the WM protocol stack 320 of FIG. 4, except that the layer of the WM protocol stack 420 supports voice signaling rather than packet data and traffic transmission. Similarly, the layer of base station protocol stack 440 is equivalent to the base station protocol stack 340 of FIG. 4, except that the base station stack 440 layer supports voice signaling rather than data packet and traffic transmission.

A preferred embodiment of the voice bearer plane structure 500 shown in FIG. 16 is a protocol stack 510 for a personal computer (PC) of an H.323 terminal and a protocol stack for a wireless modem (WM) of each H.323 terminal. 525. The voice bearer plane structure 500 also includes a protocol stack 540 or a base transceiver station (BTS) for a base station, a protocol stack 560 for an access router, and a protocol stack 580 for an H.323 gateway.

In a preferred embodiment, the protocol stack 510 for a personal computer (PC) includes a vocoder layer 501, a real-time protocol (RTP) layer 502, a user datagram protocol (UDP) layer 503, an internet protocol ( IP) layer 504, modem command layer 505, and physical link layer 506.

The physical link layer 506, the modem command layer 505, and the IP layer 504 of the PC protocol stack 510 are the physical link layer 302, the modem command layer 304, and the IP of the PC protocol stack 300, respectively. Equivalent to layer 306, except that physical link layer 506, modem command layer 505, and IP layer 504 support voice rather than packet data and traffic transmission.

In a preferred embodiment, the protocol stack 580 for the H.323 gateway includes the vocoder layer 507, the RTP layer 508, the UDP layer 509, the IP layer 511, the Ethernet layer 512, and the 10BaseT layer 513. ).

The Internet Protocol (IP) layer 511, the Ethernet layer 512, and the 10BaseT layer 513 of the H.323 gateway protocol stack 580 are each the IP of the H.323 gateway / gatekeeper protocol stack 480 of FIG. Equivalent to layer 426, Ethernet layer 427, and 10BaseT layer 428, and that IP layer 511, Ethernet layer 512, and 10BaseT layer 513 support bearer voice rather than voice signaling and traffic transmission. Excluded.

PC protocol stack 510 includes vocoder layer 501 and H.323 gateway protocol stack 580 includes vocoder layer 507 to support voice encoding / decoding. Each vocoder layer 501, 507 includes an audio coder / decoder function, respectively. In a preferred embodiment, each vocoder layer 501, 507 may encode and decode speech, ie speech, in accordance with ITU-T Recommendation G.711. In an alternative embodiment, each vocoder layer 501, 507 uses an ITU-T recommendation including, but not limited to, G.722 protocol, G.728 protocol, G729 protocol, MPEG 1 audio protocol, and G.723.1 protocol. May include functionality for encoding and decoding speech.

In a preferred embodiment, the vocoder layer 501 of the PC protocol stack 510 and the vocoder layer 507 of the H.323 gateway protocol stack 580 are A-law and μ-law coding, i.e. A-law and μ- Can transmit and receive law-encoded speech transmissions.

In a preferred embodiment, the audio algorithm used by the encoder function of the vocoder layer 501 of the PC protocol stack 510 and the vocoder layer 507 of the H.323 gateway protocol stack 580 is described in detail below with reference to FIG. As described above, it is derived through the performance change procedure 854, which is executed in each H.245 voice signaling channel between each H.323 terminal and H.323 gateway via an H.323 gatekeeper.

The real-time protocol (RTP) layer of the PC protocol stack 510 and the RTP layer 508 of the H.323 gateway protocol stack 580 are each used for voice messages in a radio access network or between H.323 terminals and H.323 gateways. It includes a protocol function for transmitting packets or streams.

In a preferred embodiment, RTP voice packets can be sent on unreliable channels and are thus supported by a User Datagram Protocol / Internet Protocol (UDP / IP) connection. UDP layer 503 and IP layer 504 of PC protocol stack 510 and UDP layer 509 and IP layer 511 of H.323 gateway protocol stack 580 are H.323 terminals and H.323, respectively. It supports UDP / IP protocol connection for RTP voice packet transmission between gateways.

Real-time protocol (RTP) transmits audio, i.e. voice, information or messages in a frame. In a preferred embodiment, before the bearer channel for voice transmission is opened or established, the maximum number of frames per IP transport packet is the H.245 signaling message between the H.323 terminal and the H.323 gateway or H.323 gatekeeper in the voice plane. Is set by. The H.323 voice receiving entity may then send any total number of audio frames to the H.323 receiving entity to reach the maximum number of frames signaled by the H.323 receiving entity in each IP packet voice transmission. In a preferred embodiment, the H.323 transmitter does not separate audio frames for IP packet voice transmissions.

The layer of the WM protocol stack 525 is generally equivalent to the WM protocol stack 420 layer of FIG. 15, except that the WM protocol stack 525 layer supports bearer voice rather than voice signaling, traffic transmission. The layer of the base station protocol stack 540 is generally equivalent to the base station protocol stack 440 of FIG. 15, except that the base station protocol stack 540 layer supports bearer voice rather than voice signaling, traffic transmission.

The SNDCP layer 521 of the WM protocol stack 525 and the SNDCP layer 522 of the base station protocol stack 540 for the voice bearer plane have an over-the-air interface between each WM and base station. interface) supports compression and decompression of message headers of packet voice messages sent and received. Compression and decompression of message headers include, but are not limited to, compression and decompression of real-time protocol (RTP) data messages, user datagram protocol (UDP) data messages, and Internet protocol (IP) data messages.

In a preferred embodiment, an end user computing device, eg a PC, may use the RTP / UDP / IP protocol stack for packet voice transmission. However, when describing RTP, it is important that the 12-byte RTP message header is too large for a 12-byte network when the underlying physical transport link is of low throughput type. For additional UDP and IP message headers, the total message header overhead for voice packets can be 40 bytes. This can be interpreted as 33 percent bandwidth efficiency, which is very low and practically excessive in low throughput transmission links, for example in wireless over-the-air links.

In compression and subsequent decompression compression algorithms, RTP / UDP / IP message headers are useful in increasing the radio link efficiency of a radio access network. The Internet design, dratf-ietf-avt-crtp-04.txt, specifies a mechanism for this purpose and is hereby fully referenced by reference. The existing Internet compression algorithm design is similar to the TCP / IP compression algorithm by Van Jacobson, and provides a mechanism for compressing 40-byte message headers from two to four bytes. In addition, existing Internet compression algorithm designs are designed to operate on a link-by-link basis, thus providing flexibility for systems that manage packet voice compression.

In a preferred embodiment, the compression algorithm supported by each SNDCP layer 521, 522 for over-the-air packet voice transmission is such that a number of fields in the RTP / UDP / IP protocol message header are used for the entire voice message. Based on the fact that it does not change from voice to packet voice. For example, in the case of the first packet voice of a voice message, once the uncompressed message header has been transmitted, a consistent field may be omitted from the next compressed header of subsequent packet voices of the voice message.

Another compression factor of the individual SNDCP layer (521, 522) support compression algorithms is that the difference from packet voice to packet voice in voice messages is often constant. Therefore, if an uncompressed RTP / UDP / IP message header is maintained with a certain difference expected at the receiving entity, then the transmitting entity only has to send the uncompressed header if there is any change in the constant difference.

The SNDCP layer 521 of the wireless modem (WM) protocol stack 525 and the SNDCP layer 522 of the base station protocol stack 540 are each used in succession in a mechanism for determining the length of a voice message and a compression / decompression algorithm. To provide individual voice packets. In addition, each SNDCP layer 521, 522 includes, but is not limited to, standard IP packets, full header packets, compressed UDP packets, compressed RTP packets, and syntax status packets for the required compression and decompression algorithms. Support the function to provide.

The SNDCP layer 521 of the wireless modem (WM) protocol stack 525 and the SNDCP layer 522 of the base station protocol stack 540 support quality of service, i.e., function for packet voice transmission (QoS). In a preferred embodiment, the QoS profile for bearer voice traffic is not a real time profile.

The layer of the access router protocol stack 560 is equivalent to the layer of the access router protocol stack 460 of FIG. 15, except that the access router protocol stack 560 layer supports bearer voice rather than voice signaling, traffic transmission.

As described above with reference to Figures 12, 14, 15 and 16, the wireless modem (WM) of the terminal or H.323 terminal and the base station has a protocol stack that includes a logical link control (LLC) layer, respectively. The LLC layer of each WM protocol stack and base station protocol stack provides a reliable and radio-independent logical link for communication between the wireless modem (WM) and the base station, respectively. In particular, the layers of each WM protocol stack and base station protocol stack support various procedures or functions 710 for logical link control as shown in FIG. 17.

Individual LLC layer function 710 includes a procedure 712 for establishing and subsequent release of an LLC link between the WM and the base station. The LLC link is used for the transmission of bearer traffic, voice or data and signaling traffic between subscriber terminals or subscriber H.323 terminals and base stations, and for communication transmission between subscriber terminals or subscriber H.323 terminals and base stations.

The LLC layer function 710 also includes a procedure 714 for transmission or transmission of bearer traffic, data or voice between the WM and the base station. The LLC layer procedure 710 also includes a procedure 716 for the transmission or transmission of packet data or voice signaling traffic for establishing, maintaining, statusing, and releasing communication channels between the WM and the base station. The procedure 714 for the transmission of bearer data and the procedure 716 for the transmission of signaling traffic each include an unrecognized point-to-point message transmission between the WM and the base station. The procedure 714 for the transmission of bearer data and the procedure 716 for the transmission of signaling traffic also include point-to-point message transmission that is recognized and reliable between the WM and the base station.

The LLC layer of the WM protocol stack and the base station protocol stack each include a procedure 718 for detection and recovery from lost or modulated and transmitted logical link control (LLC) frames or messages. The LLC layer function 710 also includes a procedure 720 for controlling the transmission flow of the LLC frame between the WM and the base station. The LLC layer procedure 710 also includes a procedure 722 to support the encryption and decryption function for the LLC frame transmitted between the WM and the base station.

As described above with reference to FIG. 1, a radio access network provides a network management service 6, which, for example, includes nodes or network elements of a network such as, but not limited to, base stations, access routers, gateways, and gatekeepers. Used to manage In a preferred embodiment, management of each network node is accomplished using an internet based protocol including, but not limited to, simple network management protocol (SNMP) and file transfer protocol (FTP). Network node management is managed via network node management platform 172 as described above with reference to FIG.

In a preferred embodiment, a direct network node management approach is used that allows the management of any network node having an Internet Protocol (IP) address. Network node management can be achieved from a number of locations including, but not limited to, remote network operations centers that support key centralized management locations, Internet firewalls, and / or the Internet providing limited remote management capabilities due to local management regulations in node installations. Can be.

A generic protocol stack 600 for remote or local node managers and network nodes or elements such as base stations, access routers, gateways, or gatekeepers are simplified network management supporting Simple Network Management Protocol (SNMP) as shown in FIG. Protocol (SNMP) layers 602 and 603, respectively. The file transfer protocol (FTP) / multicast file transfer protocol (MFTP) layer 604 of the node management protocol stack 600 and the FTP / MFTP layer 605 of the node protocol stack 620 are between a node manager and an individual node. It supports the selection of either File Transfer Protocol (FTP) or Multicast File Transfer Protocol (MFTP) for file transfer.

The basic management use protocols, namely SNMP, FTP and MFTP, are the transmission of management data necessary for security, i.e. Transmission Control Protocol (TCP) / Internet Protocol (IP), TCP / IP, access to a reliable transport channel. TCP layer 606 and IP layer 608 of node manager protocol stack 600 and TCP layer 607 and IP layer 609 of node protocol stack 620 support secure TCP / IP connections.

Also the basic management usage protocols are User Datagram Protocol (UDP) / Internet Protocol (IP), UDP / IP, and Access for the transmission of management data that can be transmitted on untrusted channels. UDP layer 610 and IP layer 608 of node management protocol stack 600 and UDP layer 611 and IP layer 609 of node protocol stack 620 support insecure UDP / IP connections.

The sub-network protocol layer 612 of the node manager protocol stack 600 and the sub-network protocol layer 613 of the node protocol specification 620 support basic transport protocols including the physical transport layer protocol.

The manager application layer 614 of the node manager protocol stack 600 supports application functions for network node management, including but not limited to configuration management, defect management, performance management, account management, and security management. Similarly, agent application layer 615 of node protocol stack 620 supports application functions for network node management including, but not limited to, configuration management, defect management, performance management, account management, and security management.

Using a direct management scheme from a centralized network operating location can result in heavy processing load on the network node management platform 172. The processing load of the network node management platform 172 may be further increased due to the simplicity of the mechanism used in the Simple Network Management Protocol (SNMP) and the general need for frequent polling to detect SNMP mechanism failures. An alternative to the preferred embodiment for the processing load problem is to maintain the hierarchical nature of the management platform for network node management as shown in FIG.

In the management hierarchy system 630 of FIG. 19, one of the managers 632 of the management system is shown. In a preferred embodiment, one of the managers 632 is the network node management platform 172 of FIG. 6. The manager of the managers 632 is two or more node managers 634. In a preferred embodiment, node manager 634 includes gateway management platform 162, router management platform 164, or access network management platform 166. Each node manager 634 manages two or more network nodes 636. Network node 636 includes a base station, an access router, a wireless router and concentrator (WRC), a gateway and a gatekeeper of a radio access network.

In a preferred embodiment, the circuit switched network gateway node is managed from the network layer system 630 using the Simple Network Management Protocol (SNMP) and File Transfer Protocol (FTP). In an alternative embodiment, the circuit switched network gateway node includes its own internal management system, which is then integrated into a general operation center local area network (LAN). In an alternative embodiment, the general operation center LAN also includes a network layer system 630 for the rest of the network node types.

In a preferred embodiment, the access router node is managed from network layer system 630 using Simple Network Management Protocol (SNMP) and File Transfer Protocol (FTP).

Referring to FIG. 20, in a preferred embodiment, a base station network node and a customer premises radio unit (CPRU) network node may meet the needs of the customer as disclosed in the radio access network management platform 166 as described with reference to FIG. 6. It is managed from a customized universal wireless access management platform 640. The radio access management platform 640 manages the CPRU 644 and base station 642 of the radio access network via an Internet Protocol (IP) network or subnetwork 646. In a preferred embodiment, the radio access management platform 640 utilizes both unicast 641, i.e. point-to-point and multicast 643, i.e. point-to-multipoint, IP services, the service being For management of the base station 642 and CPRU 644 of each radio access network.

In a preferred embodiment, the simplified network management protocol (SNMP) utilizes network management of several base stations 642 and CPRU 644, and SNMP uses the access management platform 640 and each of the base stations 642 and CPRU 644. Multicast File Transfer Protocol (MFTP) is used for file transfers.

The basic SNMP / MFTP protocol layer for base station and CPRU management is the transmission of management data necessary for security, that is, Transmission Control Protocol (TCP) / Internet Protocol (IP), TCP / IP, and access to reliable transport channels. In addition, the basic SNMP / MFTP protocol layer for base station and CPRU management provides user datagram protocol (UDP) / Internet protocol (IP), UDP / IP for the transmission of management data that can be transmitted on unreliable or insecure channels. , Connection.

As shown in FIG. 21A, the preferred embodiment of the base station management architecture 650 is a protocol stack 652 for a radio access management platform 640, a protocol stack 654 for a first access router, a second access router. Protocol stack 656, and a protocol stack 658 for a base station or base transceiver station.

The radio access management platform 640 utilizes a multicast file transfer protocol (MFTP) and a simple network management protocol (SNMP) to manage each base station, and the radio access management platform protocol stack 652 and the base station protocol stack 658. ) Includes both SNMP layers 652 and 651 and MFTP layers 654 and 655.

As mentioned above, the basic management utilization protocol, namely SNMP / MFTP, is the transmission of management data necessary for security, i.e. Transmission Control Protocol (TCP) / Internet Protocol (IP), TCP / IP, connection for reliable transmission channels. Therefore, the radio access management platform protocol stack 652 and the base station protocol stack 658 include TCP layers 656 and 657 and IP layers 660 and 661, respectively. As mentioned above, the basic management usage protocols are User Datagram Protocol (UDP) / Internet Protocol (IP), UDP / IP, and Access for the transmission of management data that may be transmitted in unreliable, i.e., unsecured transport channels. to be. The radio access management platform protocol stack 652 and the base station protocol stack 658 therefore also include UDP layers 658 and 659, respectively.

In a preferred embodiment, the wireless management platform 640 communicates with an access router via an Ethernet local area network. Therefore, the radio access management platform protocol stack 652 and the first router, i.e., the router communicating with the radio access management platform 640, the protocol stack 654 each comprise an Ethernet layer 668, 669.

In a preferred embodiment, frame relay is used as a link layer transport protocol between a base station and a radio access network comprising a network radio access management platform 640. Thus, the protocol stack, e.g., protocol stack 654 and protocol stack 656, of each access router in the transport chain between the base station and the radio access management platform 640 includes respective frame relay layers 662,663. In addition, the protocol stack 658 of the base station and the protocol stack 656 of the access router in communication with the base station each include a frame relay layer 687, 657.

The communication between the base station and the radio access network including the network radio access management platform 640 depends on the Internet Protocol (IP). Thus, in the transport chain between the radio access management platform 640 and the base station, the access router protocol stack 654, 656, the base station protocol stack 658, and the radio access management platform protocol stack 652 of the access router are the IP layers 660, 661, 670, 671, respectively. ).

A preferred embodiment of the customer premises radio unit (CPRU) management architecture 680 shown in FIG. 21B is a protocol stack 652 for a radio access management platform 640, a protocol stack 654 for a first access router, a protocol for a base station Stack 682, and protocol stack 684 for CPRU. In a preferred embodiment, the base station and the CPRU communicate over a physical air interface and the base station protocol stack 682 and the CPRU protocol stack 684 respectively manage radios, i.e., radios or over-the-air interfaces between them. (685,686).

The base station protocol stack 682 and the CPRU protocol stack 684 are each a radio link control / media access control (RLC / MAC) layer 689, 688, a local link control (LLC) layer 691, 690 and a subnetwork dependent convergence protocol (SNDCP). ) Layers 693 and 692.

The MAC function of each RLC / MAC layer 689, 688 for base station protocol stack 682 and CPRU protocol stack 684 is a signaling message in the uplink and downlink channels of the over-the-air interface between the base station and CPRU, respectively. Provide multiplexing. The RLC function of each RLC / MAC layer 689, 688 for that portion provides a radio dependent reliability link between the base station and the CPRU. The RLC function of the base station and the CPRU is responsible for the transmission or transmission of logical link control (LLC) frames of information at the over-the-air interface between them.

Base station protocol stack 682 and LLC layer 691,690 of CPRU protocol stack 684 provide a reliable radio dependent logical link for communication between the base station and CPRU. The separate Subnetwork Dependent Convergence Protocol (SNDCP) layers 693, 692 of the base station protocol stack 682 and the CPRU protocol stack 684 support Internet protocol (IP), signaling messages at the network level mapping, i.e., basic network and transport protocols. do.

Simple Network Management Protocol (SNMP) layer 734 of CPRU protocol stack 684, Multicast File Transfer Protocol (MFTP) layer 732, User Datagram Protocol (UDP) layer 733, Transmission Control Protocol (TCP) Layer 731 and Internet Protocol (IP) layer 730 are the SNMP layer 651, MFTP layer 655, UDP layer 659, TCP layer 657 and IP of the base station protocol stack 658 of FIG. 21A. Equivalent to layer 661, SNMP layer 734, MFTP layer 732, UDP layer 733, TCP layer 731, and IP layer 730 are customer radio premises unit (CPRU) protocols rather than base station protocol stacks. A stack 684.

The frame relay layer 656 of the base station protocol stack 682 is equivalent to the frame relay layer 656 of the base station protocol stack 658 of FIG. 21A. In addition, the radio access management protocol stack 652 is equivalent to the radio access management protocol stack 652 of FIG. 21A, and the first router protocol stack 654 is equivalent to the first router protocol stack 654 of FIG. 21A. The two router protocol stack 656 is equivalent to the second router protocol stack 656 of FIG. 21A.

A preferred embodiment 750 of an end-to-end packet bearer, voice and data, network component or element or node required for transmission as shown in FIG. 22 is frame relay network 755 and one or more sub-network A ( 751).

In one embodiment, network component 750 for end-to-end packet bearer transmission also includes one or more sub-network B 752 if the network includes one or more customer premises radio units (CPRUs). In a preferred embodiment, sub-network B 752 is a local area network (LAN). In a preferred embodiment, sub-network B 752 supports Ethernet protocol transmission.

The frame relay network 755 includes one or more routers 754 that provide access to one or more data networks, such as the Internet, a gateway 756, and one or more data networks 757, including the Internet. Access router 754 also provides a connection to one or more other access routers or routers, such as router 758. Router 758 provides a network connection or connection to one or more voices, such as an H.323 gateway, or voice, eg, an H.323 gateway / gatekeeper combination 759, for one or more circuit switched networks. .

Sub-network A 751 connects access router 754 to one or more base stations 760. Each base station 760 provides access to one or more wireless modems (WMs) and / or one or more customer premises radio units (CPRUs) 753 via an over-the-air interface. Each wireless modem (WM) 761 is connected to a computing device 762, including but not limited to a personal computer (PC), smart terminal, palm pilot, or workstation.

If CPRU 753 is included in a radio access network, sub-network B 752 is connected to one or more computing devices 763 including, but not limited to, a personal computer (PC), smart terminal, or workstation. .

Access router 754 performs direct routing of bearer traffic to computing device 762 via WM 761 in sub-network A 751 based on the IP address assigned to WM 761.

The Access Decision Protocol (ARP) table in the Aggers router 754 is the frame relay virtual circuit (VC) and WM 761 or CPRU 753 used to transmit bearer traffic between the access router 754 and the base station 760. Provides a bond between IP addresses. A separate virtual circuit VC is also set up between the access router 754 and the sub-network A 751 destination, namely the WM 761 and the CPRU 753.

At the over-the-air interface, i.e., between the base station 760 and the WM 761 or CPRU 753, the bearer traffic, voice, and data is logical between the base station 760 and the WM 761 or CPRU 753. Encapsulated and tuned in link control (LLC) links. The base station bridging table is a temporary logical link identity (TLLI) and access router assigned to the WM 761 or CPRU 753 for message transmission at the over-the-air interface between the base station and the WM 761 or CPRU 753. Provides coupling between virtual circuits (VC) for the transmission of bearer traffic between 754 and base station 760.

WM 761 supports computing device 762 in sub-network A 751, and WM 761 provides a direct addressing link to an individual computing device 762.

For computing device 763 of sub-network B 763, access router 754 derives routing of bearer traffic to CPRU 753 based on the IP address assigned to CPRU 763. CPRU 753 is then responsible for routing bearer data to each computing device 763 in sub-network B 752. The Address Determination Protocol (ARP) table of the CPRU 763 provides a combination between the IP address of the CPRU 763 and the Ethernet address used for transmission between the computing device 763 and the CPRU 753.

A preferred embodiment 775 of a network component or element or node is required for end-to-end signaling transmission for terminal authentication and subscriber management, as shown in FIG. 23, with frame relay network 780 and one or more sub- Network A 785. Frame relay network 755 includes one or more access routers 776. Each access router 776 provides a connection to one or more other access routers, or routers 777. The router 777 is then connected to a subscriber management platform (SMP) of the OSS. Sub-network A 785 includes an access router 776 and one or more base stations 779.

The access router 776 performs direct authentication of subscriber management signaling and terminal authentication for the base station 779 based on the IP address of the base station. The Address Determination Protocol (ARP) table in the access router 776 sets the association between the frame relay virtual circuit (VC) used for transmission between the access router 776 and the base station 779 and the IP address of the base station 779. to provide. Each base station 779 needs a single virtual circuit (VC) for terminal authentication and subscriber management signaling. In a preferred embodiment, a single virtual circuit (VC) assigned to base station 779 for terminal authentication and subscriber management signaling may also be used for network management system traffic.

A preferred embodiment of the network component 800 required for end-to-end network management transmission for node and account management as shown in FIG. 24 consists of a frame relay network 810 and one or more sub-networks 805. do. Frame relay network 810 includes one or more access routers. Each access router 801 is connected to one or more access routers or routers 802. The first router 802 provides a connection to an external network 803. The second router 802 provides access to the network node management platform 172 and subscriber management platform (SMP) 182 of the radio access network. In a preferred embodiment, SMP 182 and network node management platform 172 reside in an operational local area network (LAN) 809.

Sub-network 805 includes an access router 801, one or more base stations 807, and in one embodiment one or more customer premises radio units (CPRUs) 808. The access router 801 performs direct routing of account and node management messages for the base station 807 or CPRU 808 based on the IP address of the base station or CPRU. The access decision protocol (ARP) table in the access router 801 is a frame relay virtual circuit (VC) used for the transfer of accounting and node management signaling messages between the CPRU 808 or the base station 807 and the access router 801. And an IP address of the base station 807. Each base station 807 needs a single virtual circuit (VC) for account and node management messages. In a preferred embodiment, a single VC assigned to base station 807 can also be used for terminal authentication and subscriber management signaling. Each CPRU 808 also requires a single virtual circuit (VC) for account and node management messages.

While various embodiments have been described herein, various aspects may be practiced within the scope of the invention. The above aspects are based on the present specification and are limited only by the scope of the claims.

Claims (52)

In a communication system supporting wireless access, Computing device; A wireless modem coupled to the computing device; A base station communicating with the wireless modem through an air interface supporting a wide area wireless protocol; An access router in communication with the base station via a first interface; A gateway communicating with the access router via a second interface and communicating with a data network via a third interface; And And an H.323 gateway in communication with the access router via a fourth interface and in communication with a switching circuit network via a fifth interface. 2. The communications system of claim 1 wherein the computing device comprises a personal computer and the computing device and the wireless modem comprise a terminal. 3. The communication system of claim 2, wherein the communication system further comprises one or more base stations, the terminal comprising a portable terminal, the portable terminal communicating with the first base station at a first time and with a second base station at a second time. A communication system, characterized in that possible. 3. A communication system according to claim 2, wherein said wireless modem is installed in a personal computer, and said wireless modem and said personal computer comprise a portable terminal. 3. The terminal of claim 2, wherein the terminal is assigned a first Internet Protocol (IP) address for communicating within the communication system, and the base station is assigned a second Internet Protocol (IP) address for communicating within the communication system. A communication system, characterized in that. 3. The system of claim 2, wherein the gateway sends a packet data message from the data network to the access router, the access router sends the packet data message to the base station, and the base station sends the packet data message to the terminal. A communication system, characterized in that for transmitting. The communication system of claim 1, wherein the third interface comprises a wired interface and the fifth interface comprises a wired interface. The communication system of claim 1, further comprising a telephone connected to the computing device, wherein the telephone, the computing device, and a wireless modem comprise an H.323 terminal. 10. The system of claim 8, wherein the H.323 gateway sends a voice message from the switching circuit network to the access router, the access router sends the voice message to the base station, and the base station sends the voice message to the H. A communication system characterized by transmitting to a .323 terminal. The communication system of claim 1, wherein said data network comprises the Internet. A communication system according to claim 1, wherein said switching circuit network comprises a public switched telephone network. In a communication system supporting wireless access, A computing device capable of receiving packet data; A wireless unit capable of receiving packet transmissions over an air interface and coupled to the computing device; And And a wireless access network capable of communicating with a packet data network, communicating with a switching circuit network, communicating with the wireless unit via an air interface, and supporting a wide area wireless protocol. 13. The apparatus of claim 12, further comprising a voice access device capable of receiving voice messages, the voice access device being coupled to the computing device, wherein the computing device, the voice access device and the wireless unit are connected to an H.323 terminal. Communication system comprising a. 18. The communications system of claim 13 wherein the wireless unit comprises a wireless modem and the computing device and the wireless modem comprise a portable terminal. 14. The communications system of claim 13 wherein the computing device comprises a personal computer and the voice access device comprises a telephone. 13. The apparatus of claim 12, further comprising a voice access device capable of receiving a voice message, wherein the voice access device is connected to the wireless unit, wherein the voice access device and the wireless unit comprise an H.323 terminal. Characterized by a communication system. 17. The communications system of claim 16, wherein the wireless unit comprises a consumer premises wireless unit (CPRU), and the computing device and the CPRU comprise a terminal. 17. The communications system of claim 16 wherein the computing device comprises a personal computer and the voice access device comprises a telephone. 13. The system of claim 12, further comprising an H.323 gateway, wherein the H.323 gateway communicates with the radio access network through a first interface and communicates with a switching circuit network through a second interface. Receives a switching circuit protocol message on the second interface from the switching circuit network, the H.323 gateway converts a switching circuit protocol message into an internet protocol message, and the H.323 gateway converts the internet protocol message into the second protocol message. And transmit to the radio access network over one interface. 13. The communication system of claim 12, wherein said data network comprises the Internet. 13. A communication system according to claim 12, wherein said switching circuit network comprises a public switched telephone network. A radio access network supporting both switching circuit message transmission and packet data message transmission, At least one subscriber subscribes to the radio access network service and the radio access network supports wide area radio protocol and the radio access network comprises: A protocol for transmitting packet data messages from the data network to the subscriber terminal; A protocol for the transmission of voice messages from the switching circuit network to the subscriber H.323 terminal; A protocol for fax transmission from the switching circuit network to the subscriber terminal; A protocol for security management of the radio access network; A protocol for management of one or more network elements of the radio access network; A protocol for management of subscriber information; And And a protocol for managing charging of the one or more subscribers of the radio access network. 23. The radio access network of claim 22, wherein the protocol for packet data message transmission includes point to point transmission capability. 24. The radio access network of claim 23, wherein said point-to-point transmission capability comprises an acknowledgment transmission mechanism. 23. The radio access network of claim 22, wherein the protocol for packet data message transmission includes point to point transmission capability. 23. The radio access network of claim 22, wherein the protocol for transmitting packet data messages comprises an internet protocol. 23. The radio access network of claim 22, wherein the protocol for transmitting voice messages comprises an H.323 protocol overlying the Internet protocol. 23. The radio access network of claim 22, wherein the protocol for fax transmission comprises an internet protocol. 23. The radio access network of claim 22, wherein the protocol for security management includes a terminal authentication function. 30. The method of claim 29, wherein the protocol for security management includes a user ID confidentiality function, wherein the user ID confidentiality function includes a process for preventing tracking a subscriber's location in the radio access network. Access network. 30. The system of claim 29, further comprising an air interface, wherein the protocol for security management further comprises a user information confidentiality function, wherein the user information confidentiality function transmits a voice message transmitted through an air interface of the radio access network. And a process for maintaining the confidentiality of the packet data message transmission. 23. The radio access network of claim 22, wherein the protocol for management of one or more network elements of the radio access network comprises a configuration management function and a failure management function. 33. The radio access network of claim 32, wherein one network element of the one or more network elements comprises a base station. 23. The method of claim 22, wherein the protocol for management of subscriber information includes the function of managing a subscriber profile for each subscriber of the radio access network, the subscriber profile comprising a quality of service level assigned to each subscriber. And a wireless access network. 23. The method of claim 22, wherein the protocol for managing the charging of one or more subscribers of the radio access network comprises a mechanism for charging a subscriber for wireless access, a packet data message for the subscriber over a wireless access network. And a mechanism for charging the subscriber for voice message transmission to the subscriber over the wireless access network. In a radio access network that supports a light source radio protocol, The wireless access network comprises a wireless modem, the wireless modem including a wireless modem protocol stack, The wireless modem protocol stack is: A wireless physical layer in communication with the base station; A radio link control layer in communication with the base station; A media access control layer in communication with the base station; A logic link control layer in communication with the base station; And And a subnetwork dependent converged protocol layer in communication with the base station. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises one or more protocols including General Packet Radio Service (GPRS) and a Mobile Communication Globalization System (GSM) protocol. 37. The system of claim 36, wherein the wireless physical layer of the wireless modem protocol stack comprises a transport process for an enhanced data rate (EDGE) air interface for global system / GSM evolution for mobile communications globalization system (GSM). Characterized by a wireless access network. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transmission process for a digital AMPS (DMAPS) air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transport process for an IS-95 air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transmission process for a DECT air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transport process for a WB-CDMA air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transport process for a WB-TDMA air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transport process for an IS-661 air interface. 37. The radio access network of claim 36, wherein the wireless physical layer of the radio modem protocol stack comprises a transmission process for a PCS air interface. 37. The radio access network of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a transport process for a PACS air interface. 37. The radio of claim 36, wherein the radio physical layer of the radio modem protocol stack comprises a function of transmitting one or more logical link control (LLC) frames for information over an air interface between the radio modem and a base station. Access network. 37. The method of claim 36, wherein the medium access control layer of the wireless modem protocol stack comprises a function of multiplexing two or more logical link control (LLC) frames of information over an uplink channel of an air interface between the wireless modem and a base station. And a wireless access network. 37. The radio access network of claim 36, wherein the logic link control layer of the radio modem protocol stack comprises the function of generating and transmitting one or more logic link control (LLC) frames of information from the radio modem to the base station. . 37. The method of claim 36, wherein a subnetwork dependent converged protocol layer of a wireless modem protocol stack is capable of mapping Internet protocol messages to one or more logical link control frames for transmission by a wireless modem to a base station over an air interface and from the base station. And mapping the at least one logical link control frame received at the wireless modem to an internet protocol message. 37. The radio access network of claim 36, further comprising a base station and an access router, the base station comprising a base station protocol stack, wherein the base station protocol stack comprises a frame relay layer in communication with the access router. 53. The method of claim 51, wherein the frame relay layer of the base station protocol stack includes the function of mapping a switching virtual circuit address of a message sent from the access router to a temporary logic link ID address to send a message to the wireless modem. Characterized by a wireless access network.