Method and device to provide configurable levels and protocols

TECHNICAL FIELD

The present invention relates to wireless communications. More particularly, the present invention relates to a method and apparatus for providing configurable layers and protocols in a communications system.

BACKGROUND

Using multiple access modulation techniques, code division multiple access (CDMA) modulation techniques is one of several methods to ensure communication with a large number of system users. Although it is known in the art, and other communication system using multiple access techniques, such as multiple access, time division multiple access (TDMA and standard GSM - Global System for Mobile Communications), multiple access, frequency division (FDMA) scheme and an amplitude modulation such as audio modulation sideband amplitude companded, spread spectrum modulation techniques of CDMA have significant advantages over other modulation techniques for multiple access communication systems. The use of CDMA techniques in a multiple access communication system is disclosed in U.S. Patent №4901307 "System multiple access communication with spread spectrum USING SATELLITE OR TERRESTRIAL REPEATERS," issued February 13, 1990, and U.S. Patent №5103459 "System and Method for Generating Signal in CDMA CELLULAR TELEPHONE SYSTEM ", issued April 7, 1992, which are assigned to the assignee hereof and incorporated herein by reference.

CDMA systems are typically designed in accordance with one or more particular CDMA standards (CDMA). Examples of such CDMA standards may serve as the "Compatibility Standard mobile station and a base station for Dual-Mode Wideband cellular spread spectrum" TIA / EIA / IS-95-A, "Compatibility Standard mobile station and a base station for Dual-Mode Wideband cellular spread spectrum" TIA / EIA / IS-95-B, "Standard recommended minimum performance for dual-mode mobile stations of mobile broadband systems and personal communication spread spectrum" TIA / EIA / IS-98-A, -B, -C, and "presented a draft cdma2000 ITU-R RTT ". New CDMA standards are constantly proposed and adopted for use.

Each CDMA standard defines an air interface protocol used by the standard to support communication between communicating devices (i.e., between the access terminal and radio network). Radio interface protocol defines mechanisms through which to execute specific functions, and can include a number of protocols that allow the implementation of various functions.

Typically, each CDMA standard adopts a particular air interface protocol that performs a number of functions and is identified uniquely determined version number. New functions can be implemented by defining new attributes, messages, state machines, usually within the framework of an existing radio interface protocol. Next, the new radio interface protocol, which includes the new attributes, messages, and state machines along with other previously defined attributes, messages, and state machines. Similarly, if an existing protocol is modified or updated, it defines a new radio interface and is assigned a new version number.

Typically, each communication device (for example, each access terminal and radio network) is designed to support one or more of the full versions of the radio protocol. Because all the radio interface protocol is defined only version, it requires that each wireless device supports all the functions required in the particular version, if it is desirable to maintain any function in this version. The communication devices are typically designed to support one or more versions (e.g., versions of a series). Communication between the access terminal and radio network is implemented using any of the commonly supported air interface protocol versions.

The desire to expand the functionality and performance of wireless communication systems leads to ever-increasing complexity of the radio interface protocol. In particular, the radio interface protocol is used to perform many complex functions, including voice communication, data transmission, etc.

The usual way to define a new version for each new radio interface protocol was adequate for a "simple" protocols in the initial draft of standard CDMA. As the number of features and complexity of such a conventional method has become cumbersome and inadequate. The conventional method does not provide a simple support for the implementation of additional functions in the existing radio interface protocol or a subset of features in a radio interface protocol.

Thus, there is an urgent need for a radio interface protocol structure that efficiently supports implementation of a variety of functions.

SUMMARY OF THE INVENTION

The present invention provides a method that is used to implement configurable layers and protocols in a communications system. Levels and protocols layered architecture of the radio interface are modular in structure and can be modified and updated to support new features, perform complex tasks and provide added functionality. The access terminal and radio network can communicate using the layers and protocols in a conventional manner supported by both, and this determination can be made at the beginning of a radio session. The base set of layers and protocols supported by the access terminal and radio network, provides a minimum level of compatibility.

In an embodiment of the present invention there is provided a method of configuring the level or protocol before transmitting data between a first object (e.g., access terminal) and a second object (e.g., data network). In accordance with this method, a set of one or more layers and one or more protocols is selected for negotiation, with each selected layer and protocol corresponds to a particular attribute that should be agreed between the first and second objects. For each selected attribute specifies a list of selected attribute values, said the list includes one or more attribute values ​​considered to be acceptable to the first object. The list of selected attributes and their associated attribute values ​​are sent from the first entity, and in response receives a list of processed attributes and their associated lists of processed attribute values. Each list of processed attribute values ​​includes one or more attribute values ​​considered as eligible for the second object. Levels and protocols in the first object is then configured in accordance with the received list of processed attributes and their associated processed attribute values. In an embodiment, each processed attribute is associated with one processed attribute value. In one embodiment, and the Protocol in the first object configured to their default values ​​if the corresponding values ​​of the processed attributes are not taken in the first aspect.

The first or second entity, or both, can implement a state machine having a number of conditions including the following: (1) an inactive state indicative of inactivity prior to a session negotiation; (2) initiated by the state, indicating the approval of the session in the list of selected attributes; and (3) the open state, indicates an active connection between the first and second objects. Initiated state can be implemented to include (1) an access terminal initiated state indicative of the session negotiation on the attributes selected by the access terminal, and (2) a radio network initiated state attributes selected radio access network.

A communication session between the first and second objects may be set by transmitting a request message from the opening of the first object and receiving the discovery response message that indicates an acceptance or rejection of the request. Request message and the response of opening the opening may be transmitted and received on common channels.

The selected attributes and their associated attribute values ​​can be transmitted via one or more configuration request messages, and the processed attributes and their associated attribute values ​​can be received via one or more response messages configuration. The messages can be identified by an object identifier assigned to the first aspect. The elements in each list of selected attribute values ​​can be arranged in a specific order based on preference of the first object, and the elements in the received configuration response messages can be received in the order corresponding to the order of elements in the configuration request messages. The configuration information may be transmitted and received via dedicated communications channels.

The first and second objects can communicate through the levels and protocols established by the default configuration before completing the setting in accordance with the levels agreed upon by and protocols. In an exemplary embodiment, if the first and second objects are choosing a set of attributes for approval, the approval of a set of selected first object is completed before agreeing to a set of selected second object.

Another embodiment of the invention provides a method for providing configurable layers and / or protocols in a communication system. In accordance with the method established by the default set of layers and protocols is maintained for communication between the first object and the second object. Similarly, a set of zero or more configurable layers and one or more configurable protocols, or a combination of both of them is supported to communicate with each configurable layer and protocol respectively attribute that should be agreed between the first and second objects. It provides a set of configuration messages that can be used for transmitting and receiving configuration information related to each configurable attribute. A state machine is provided to track the operating state of the first object. The state machine may include phase and subphase below.

Set established default layers and protocols typically includes a configuration protocol used for sending and receiving messages that support negotiation and configuration of the set of configurable attributes. Configuration messages can be implemented in the session layer of the communication system. Each configuration message can include an object identifier that identifies the first entity and a transaction identifier that identifies a particular instance of the configuration message.

Another embodiment of the invention provides an access terminal in a spread spectrum communication system that includes a controller, an encoder, a modulator and a transmitter. The controller receives and processes data (e.g., traffic data and signaling), the encoder encodes the processed data, the modulator modulates the encoded data, and the transmitter converts the modulated data into an analog signal suitable for transmission over the transmission medium. The controller implements a set of layers and protocols used to support data transmission, with zero or more layers and one or more protocols, or a combination of both, the access terminal configured to transfer data.

An access terminal may also include a receiver, a demodulator and a decoder. The receiver receives a forward link signal, the demodulator demodulates the received forward link signal, the decoder decodes the demodulated signal and the controller configures one or more of the configurable layers and protocols based, in part, the encoded data to the decoder.

The invention also provides a method and apparatus for implementing configurable layers and protocols in a radio network.

BRIEF DESCRIPTION OF DRAWINGS

The features, nature, and advantages of the present invention are explained in the detailed description set forth below with reference to the drawings, wherein like elements are designated by the same reference numerals, and wherein:

Figure 1 - Diagram of a spread spectrum communication that supports a number of users;

Figure 2 - a block diagram of an embodiment of a radio network and an access terminal;

3 - Diagram of an embodiment of a layered architecture of a radio interface supported by the present invention;

4A-4C - diagrams of specific embodiments of a channel structure with a high data rate (HDR) channel structure of the direct and reverse channel structure, respectively;

5 - a diagram of a specific embodiment of levels and corresponding protocols for the layered structure shown in Figure 3;

6A and 6B - state diagram for an embodiment of a session boot protocol for the access terminal and radio network, respectively;

6C and 6D - state diagram for an embodiment of a session boot protocol for the access terminal and radio network, respectively;

7A - a flowchart of a particular implementation session open phase;

7B and 7C - flowchart of a particular implementation subphase matching level / protocol session and subphase activation level / session protocol, respectively;

8 - a timing diagram of an embodiment of subphase coordination and level configuration / protocol session and

9A to 9H - diagram of an embodiment of the format for various messages used in the negotiation and configuration of layers and protocols.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

1 is a system diagram 100 of a spread spectrum communication that supports a number of users. In system 100, a set of terminals 110a-110c are in communication with the radio network through a set of base transceiver stations (BSS) 112a-112f on the radio links. Each base station transceiver 112 is connected with a base station controller (BSC) 114 and a visitor location register (VLR) 116. The controllers 114a and 114b of base stations (transceivers and base stations 112) may also communicate directly with each other as shown by the dotted line in Figure .1.

The access terminal as provided herein, is a device that allows the connectivity data and / or speech connections to the user. An access terminal may be a self contained device such as a cellular phone, a personal digital assistant, a stand alone device or any similar type. An access terminal may be a unit or module configurable for establishing a connection with a computing device such as a desktop or laptop personal computer. Radiocommunication network as used herein, is a network equipment (e.g., base station transceiver 112, base station controller 114, and visitor locations register 116 in Figure 1) that provides connectivity data and / or voice connections between the network data (e.g., a data network with packet-switched network such as the Internet) and the access terminal. Connectivity is typically provided at a link level, as described below.

2 is a block diagram of an embodiment of a radio network 210 and access terminal 250. The radio network 210, traffic data from a buffer 212 and control data from the control system 214 are supplied to an encoder 216 which encodes the data using a particular encoding format. The encoding format may include, for example, using cyclic redundancy check (CRC), convolutional coding, with serial concatenation (clutch) block coding Reed-Solomon coding using covering Walsh sequence pseudonoise (PN) spread spectrum other encoding formats commonly used in CDMA systems standards. The encoded data is provided to modulator 218 which modulates the data using a particular modulation format such as, for example, quadrature phase shift keying (QPSK), Offset VCR and others. The transmitter 220 receives and converts the modulated data into an analog signal, performs the necessary shaping the analog signal and transmits the signal through duplexer 222 and antenna 224 in the radio channel.

The access terminal 250, the transmitted signal is received by antenna 252, passed through duplexer 254 and provided to receiver 256. Within receiver 256 the signal is subjected to necessary conversion, and formed in the resulting signal is supplied to a demodulator 258. This transformation signal may include filtering, amplification, frequency conversion, etc. Demodulator 258 demodulates the conditioned signal with a demodulation format that is complementary to mutually modulation format used at radio network 210. The decoder 260 receives and decodes the demodulated data with a decoding format that is mutually complementary to the encoding format used at radio network 210. The decoded data is then provided to controller 262.

Transmission of traffic data and control data from the access terminal 250 to radio network 210 is carried on supplemental channel signal. The traffic data from a buffer (not shown in Figure 2) and the control data from the controller 262 are encoded by encoder 264, modulated by a modulator 266, converted to a transmitter 268, routed through duplexer 254 and transmitted via antenna 252. At radio network 210, the transmitted signal is received by antenna 224, routed through a duplexer 222, converted to an RF receiver 226 and demodulated by a demodulator 228, decoded by the decoder 230 and fed to the control system 214.

Direct transmission, as used herein, refers to a transmission from radio network 210 to access terminal 250, and the reverse transmission refers to a transmission from access terminal 250 to radio network 210. Formats demodulate and decode the reverse link can be different, and typically different from those in the forward link format.

As in most communication systems, the link between the access terminal and radio network is implemented through a series of "layers" that define the modes of operation supported by the characteristics and capabilities of the communication system. Each layer consists of one or more layer protocols (or simply protocols) that implement the functionality of the level. Each layer communicates with a higher level and / or below at certain interfaces.

In the original version CDMA system compatible with the IS-95 standard supports one air interface protocol that defines the layers and their protocols. Some options standard IS-95 provides a small degree of separation protocols by function. Source radio interface protocol has been modified numerous times to support additional functionality, such as enhanced control of medium access (MAC). To implement the additional functionality in the levels used for this source radio interface protocol makes the necessary changes, and the modified air interface protocol is identified by a new version number (typically defined as a new standard). The modified air interface protocol typically retains the bulk of the original structures of a radio interface protocol (e.g., the same data frame structure, the same frame length, etc.) to provide maximum compatibility with previous generations of systems and standards.

After taking a new radio interface protocol can be implemented practically by the access terminal and radio network if both are designed to provide support to the protocol of the radio interface. This method for generating new air interface protocols does not provide a simple implementation of new functions and features in the CDMA system.

In accordance with one aspect of the present invention, levels and protocols are created in a modular way, so that each layer (or protocol) can be modified or upgraded without requiring modification of the other levels (or protocols). This can be achieved, in part, by defining and maintaining the interfaces between layers, so that the new functions can readily be supported. This modular design lets you modify individually the level and protocol (s).

Each layer includes one or more protocols that implement the functionality of a given level. In accordance with another aspect of the present invention, the particular level protocols can be individually agreed between the access terminal and radio network (e.g., at the beginning of the session). The access terminal and radio network can be designed to support a different set of protocols, but they can still communicate with each other via the protocols that are common to both of them. Feature agreed levels and protocols provide flexibility in the design and use of different versions of a radio interface protocol, without requiring explicit definitions and supporting each modification as a new radio interface protocol, as is usually the case.

3 shows a diagram of an embodiment of a multi-tier architecture of the radio interface 300 maintained in accordance with the invention. As shown in Figure 3, layered architecture 300 includes seven layers, which are identified as follows: (1) a physical layer 210, (2) the level 314 control access to the transmission medium (MAC), (3) the level of protection 316, (4) level 318 of the compound (5) a session layer 320, (6) the flow rate 322 and (7) application layer 324. For a better understanding of the present invention, the following is a brief description of the main features of each level.

Physical layer 310 defines the "physical" characteristics of the transmission between the access terminal and radio network. These physical characteristics may include, for example, the channel structure, transmission frequency, transmission output power level, modulation format, coding scheme, etc. for the forward and reverse link.

Level 314 MAC defines the procedures used for the transmission and reception of the physical layer 310.

Level 316 provides protection of protected services, which may include, for example, authentication and encryption services.

The level of compound 318 provides a connection for a radio link and Maintenance.

Level 320 provides session-level coordination and protocol, protocol configuration, and maintenance of state services. Level session 320 is described in more detail below.

Level stream 322 provides multiplexing of various application streams. In a specific embodiment, the communications system supports four application flow, indicated as streams 0-3. In an embodiment, stream 0 is used for signaling between the access terminal and radio network, stream 1 is used for packet data streams 2 and 3 are used for other applications. As shown in Figure 3, the signaling stream (e.g., stream 0) is supported by the protocol signaling channel (SLP) 330 and the communication protocol with a high data rate (HMP) 332, and the packet data stream (e.g., stream 1) is supported by the protocol line Radiocommunication (RLP) 340 and a two-point transmission protocol (PPP) 342. In one embodiment, a default signaling stream (i.e., a default protocol HMP / SLP) is used as the default for stream 0 and installed by default packet service (i.e., a default protocol PPP / RLP) is used as the default for stream 1, if these streams have not been agreed between the access terminal and radio network.

Minutes SRL 330 provides a "best possible" delivery mechanisms for signaling messages, the protocol HLP 332 provides messaging services for signaling messages. RLP protocol 340 provides retransmission and detection of duplicate data for a particular specific data stream, one possible implementation is further described in the standard IS-707. It can be designed and used by other implementation protocol RLP 340, differ from those described in the standard IS-707, and it will be included in the scope of the present invention. When used in the context set by the default packet service protocol RLP 340 can be defined as that used for the PPP packet. PPP 342 provides framing and supporting multiprotocol operation mode and further described in W.Simpson, "The Point-to-Point Protocol (PPP)", RFC 1661, July 1994. Protocols running on the basis of PPP 342 can transmit traffic data as well as perform various tasks of network administration.

Figure 3 shows an embodiment of a multilevel structure supported in accordance with the present invention. However, the present invention can also provide support for other multi-level architectures having additional layers, fewer layers, or having different levels.

4A-4C are diagrams of a specific embodiment of the channel structure 410 with a high data rate (HDR) channel structure 420 forward and reverse channel structure 440, respectively, supported by the communication system (e.g., system 100, shown in Figure 1) . HDR channel structure 410 includes forward channel structure 420 that is used to transmit data from the radio network to the access terminal, and reverse channel structure 440 that is used to transmit data from the access terminal to the radio network. Structures of the forward and reverse channels are designed to provide the desired functionality, wherein each channel structure is designed based on the specific characteristics of the data transmission in the forward or reverse link.

4B shows a possible embodiment of a structure 20 forward channel. In this embodiment, forward channel structure 420 includes a channel 422 pilot channel 424 to control access to the transmission medium, one or more traffic channels 426 and one or more control channels 428. Channel 424 controls access to the transmission medium also includes a channel 432 forward link activity channel 434 and a reverse activity channel power control channel is a reverse channel. These channels can be designed in various ways that are within the scope of the present invention. Pilot channel, a medium access control and transmission control are "common" channels shared nearby access terminals communicating with the radio network. The channel (s) the traffic is (are) selected (and) channel (s) designated by (s) to an access terminal after session establishment.

4C is a diagram of an embodiment of reverse channel structure 440. In this embodiment, reverse channel structure 440 includes one or more traffic channels 442 and 444 access channel. The channel (s) 442 and traffic channel 452 includes a pilot channel 454 to control access to the transmission medium and the one or more data channels 456. Channel 454 controls access to the transmission medium may further include a rate indicator channel 462 and reverse channel 464 control channel data rate. Access channel 444 also includes a channel 472 pilot channel 474 to control access to the transmission medium and the one or more data channels 476. Channel 474 controls access to the transmission medium may further include a channel 478 reverse rate indicator channel. Again, all of these channels may be performed in various ways and still fall within the scope of the present invention. As in the case of forward channel structure, the channel (s) the traffic is (are) selected (and) channel (s), and access channel is a common channel shared with other access terminals.

Used to describe the invention several terms are defined below.

The term "session" refers to a project implemented by the operating state between the access terminal and radio network. Jointly implemented by the operating state supports the protocols and configuration protocols that have been agreed and are available for use in communications between the access terminal and radio network. In accordance with one aspect of the present invention, the levels protocols and protocol configurations may be agreed between the access terminal and radio network when a session is established, in some implementations they can be re-aligned at any time during a communication session. In the exemplary embodiment, different from the installation session, the access terminal is unable to communicate with a radio network without opening the communication session (i.e., the access terminal may communicate with a radio access network in order to quickly open the communication session).

The compound is a specific state of the radio link, wherein the access terminal is allocated resources are assigned radio link (e.g., forward traffic channel, reverse traffic channel, the associated control channel medium access). During any particular session, the access terminal and radio network can open and close the connection many times. In a possible embodiment, otherwise, in addition to the installation session, the connection does not exist without a session.

The term "flow" is designated channel is used to convey information for a particular application. The stream can be defined to carry signaling information, traffic data, other types of data, or combination thereof. The access terminal and radio network can be designed, and typically are designed to support simultaneous transmission of a plurality of threads. Streams can be used to carry data with different QoS requirements or other applications.

Figure 5 shows a specific embodiment of levels and corresponding protocols for the layered architecture 300 in Figure 3, which are designed to support HDR channel structure 410 shown in Figure 4A-4C. As shown in Figure 5, each layer includes one or more protocols that implement the functionality of the level. Protocols use signaling messages and / or headers to convey information to another object on the other side of the radio link. 5 shows some of the protocols included in the layered architecture 300 levels.

In the embodiment 314 of Figure 5 level medium access control (MAC layer) 314 includes a MAC protocol 514a control channel MAC protocol 514b forward traffic channel MAC protocol 514c, and an access channel MAC protocol 514d reverse channel traffic. MAC protocol 514a provides the procedures for a control channel used for transmission of a radio access network and an access terminal - to receive, control channel 428. MAC protocol 514b provides the forward traffic channel procedure used for transmitting a radio access network and an access terminal - for receiving a forward link 426 traffic. MAC protocol 514c provides the channel access procedures used by the access terminal to transmit, and the radio network - receiving access channel 444. Any MAC protocol 514d reverse traffic channel provides the procedures used by the access terminal to transmit, and the radio network - for receiving a reverse traffic channel 442.

316 Level of protection includes zero or more security protocols designed to protect against unauthorized use of the transmission signals. In an embodiment, the level of protection 316 includes basic security protocol (not shown in Figure 4), which protects against unauthorized use of the service, and unauthorized use of identification data. Sensitive to this data may be typically protected through the use of authentication and encryption, and additional protection to the protection level 316 is typically not needed. However, it provides interfaces that allow to introduce additional security protocols as needed. The level of 318 compounds includes protocol 518a radio link control protocol 518b state initialization protocol 518s standby state, the protocol 518d connected state protocol 518e control of wait states, the protocol 518f control the connected state protocol 518g consolidation package protocol 518h update routing protocol 518i service messages. Protocol 518a Radio Link Control provides overall control of the state machine, which is followed by the access terminal and radio network for connection. 518b state protocol initialization procedure ensures that the access terminal should be to detect the radio network and the procedures followed by the radio network to support network discovery. Minutes 518s pending state provides the procedures followed by the access terminal and radio network and if the connection is not open. Minutes 518d connected state provides the procedures followed by the access terminal and radio network when the connection is open. Minutes 518e monitoring Idle control procedures followed by the access terminal when the connection is not open. Minutes 518f control the connected state provides control procedures followed by the access terminal and radio network when the connection is open. 518g packet consolidation protocol provides prioritization of programs and layout packages to the level of 318 connections. Update protocol 518h provides the routing means to maintain the route between the access terminal and radio network. Both the protocol signaling messages 518i provides broadcast messages containing information used in reports on the level of 318 connections.

Level 320 session includes the protocol and protocol load 520a 520b session management. Session boot protocol 520a provides the initial message exchange used to start a session and further provides the means for excluding the access terminal, which is not currently have a session. The initial message exchange assigns a UATI to the access terminal identifier (identifier addressing a particular access terminal) and selects the session control protocol that in turn negotiates and configures the protocols used in the communication session. Id UATI herein also referred to as a "terminal identifier." In an embodiment, the boot protocol 520a of the session may not provide approval.

Protocol session control 520b provides initial negotiation and configuration of the protocols used during the session, and maintains control of the session and session closing procedures. In an embodiment, the session control protocol 520b supports two phases of negotiation: negotiation initiated by an access terminal (AT), and the coordination initiated a radio access network (CP). In the phase of reconciliation initiated by the TD, the exchange of data in consultation initiated by the access terminal. This phase is typically used to negotiate the protocols that will be used in the session and to negotiate the configurations for the protocols (e.g., authentication key lengths). In the phase of reconciliation initiated by CP communication when negotiating initiated radio network. This phase is typically used to override the default values ​​used in the negotiated protocols. Protocol session control 520b may also provide a mechanism for messages confirming activity. In an embodiment in accordance with the mechanism messages confirming the activity when nothing was followed over a period of time between the access terminal and radio network, one object sends a message confirming the activity, which is responsible for the other object.

Session boot protocol 520a and session control protocol 520b are described in more detail below.

The level of flow 322 includes the protocol stream 522a. In the transmit direction, stream protocol 522a adds a stream header to data packets and ensures that the packets are aligned on bytes. In the receive direction, stream protocol 522a removes the stream header and forwards the packets to the proper application.

In an embodiment, the protocols are defined by their interfaces and protocol state. In a specific embodiment, four types of interfaces are defined, including: (1) headers and messages, (2) commands, (3) indications, and (4) public data. In the following description, the term "object" is used to refer to both the access terminal and radio network.

Headers and messages are used for communication between a protocol executing in one aspect, and the same protocol in the other object.

Teams use higher-level protocol for services from the protocol of a lower level in the same subject. For example, commands can be used at a higher level as primitives, causing the implementation of the protocol of a lower level of some action (for example, interrupt any access attempts are under way). In an embodiment, commands can be transmitted between the protocols on the same level, but are limited to one direction (i.e., the object that receives a command from a particular protocol is prohibited to transmit the command to the other entity in the same protocol).

Lower layer protocol used to transmit guidance information regarding the occurrence of an event (e.g., to provide notifications when certain events occur). In an exemplary higher-level protocols or the same level of reception may register instructions. In yet another embodiment, the directions between protocols at the same level are limited to one direction (that is, if protocol A register receiving instructions from the protocol in at the same level, it is forbidden to register protocols in receiving instructions from protocol A).

These common areas are used to share information in a controlled manner between the protocols. Protocols may provide access to other protocols some of the data that they generate or receive messages through. Shared data may be shared between protocols at the same level as well as between protocols at different levels.

Status reports are used to identify specific operating conditions of a particular protocol. Each protocol state can be associated with a particular set of behavior characteristics that may depend, for example, on the operating conditions, the environment in which the object (such as whether the connection open or not, whether a session is opened or not, etc. ), and other factors. Transitions between states are triggered protocols appearance of specific events that are so fixed operating conditions. Examples of events that may lead to a transition state, can serve as a welcome message, the command of the higher-level protocol, an indication of the lower level protocol, and after a set time of the timer.

The radio network is able to communicate with multiple terminals simultaneously. Radio network creates an instance of the signaling protocol for each access terminal with which it communicates, and then supports protocol state machine for a given access terminal. Network radio has the ability to support multiple independent copies of the signaling protocol, each with its own independent state machine.

In an embodiment, for each of the protocols provided an inactive state, the state of the opening and closing state. Enters a sleep state occurs when the protocol is not functioning at a particular time. For example, the MAC protocol access channel in an access terminal performs login in an inactive state when it has an open connection. It indicates the opening state for opening the session or connection (in application to the protocol), and indicates the closing state for closing the session or connection. In an embodiment, all states of a particular protocol other than the inactive state are collectively called active states, although they may be individually named. For example, the MAC protocol of the forward traffic channel may be designed so as to have three states: inactive, variable rate, and at a constant speed, the state variable and fixed rate together referred to as active states.

Each protocol supports a set of commands that allow the exchange of data with other protocols. Some common commands supported by many protocols include enable, disable, open, close. The "activate" the protocol indicates the need to move from an inactive state to a different state. The "deactivate" the protocol indicates the need to transition to an inactive state. The "open" (or "close") protocol specifies the need to perform a function associated with the opening (or closing) session or opening (or closing) the connection.

In accordance with one aspect of the present invention, a number of applications, layers, protocols, or configurations (i.e., for the applications, layers, and protocols), or a combination thereof may be negotiated and configured when a session setup. Each flow, level and protocol is assigned a uniquely defined identifier (referred to herein as type), which identifies the total flow, level, or protocol (eg, the MAC protocol of the access channel). In a specific embodiment, the identifier has a value of 8 bits. The multilevel structure (for example, as shown in Figure 3) can also be aligned.

In an embodiment, flow, level, or protocol may further be associated with a "subtype" that identifies a particular instance of the level or protocol (e.g., MAC protocol of a default access channel, or perhaps one day advanced and bulky MAC protocol access channel etc.).

Layered architecture shown in Figure 3, supports multiple applications. In accordance with one aspect of the present invention to provide minimum compatibility defined set installed default applications that are supported by all access terminals and radio networks. In an exemplary embodiment, Default applications include is the default application signaling and is the default packet application. Is the default signaling application provides a means to transfer messages between the protocol in the same facility and the same protocol in another object. Is the default packet application provides a byte stream PPP (point to point transmission) between objects.

In an exemplary embodiment is the default application signaling includes (1) messaging protocol (for example, the protocol HDP messaging) and (2) protocol-level communication link that provides message fragmentation, retransmission, and duplicate detection data (eg, SLP channel alarm). In an exemplary embodiment is the default packet application includes (1) PPP (ie, as defined by IETF RFC 1661 document), which provides PPP byte stream, and (2) link layer protocol (for example, a radio link protocol RLP ) which provides byte retransmission and duplicate data detection.

In accordance with one aspect of the present invention, the application to be used, the streams in which the application should be performed, levels, protocols and configurations may be agreed upon as part of a session negotiation. In an embodiment, the session negotiation is implemented at the session level. In accordance with another aspect of the present invention, each access terminal and radio network are designed to support the basic layered architecture and a basic set of protocols. After initiating communication between the access terminal and radio network carried out coordination of the session, and between objects can be coordinated from a base set of protocols and additional protocols.

Set default installed application levels protocols and configurations is used to support communication between the entities until the protocols are yet to be agreed. Each layer includes zero or more default established protocols. Service messages set by default signaling protocol may be used for the exchange of information relating to the installed default levels, protocols and configurations. The access terminal and radio network uses default settings until until complete harmonization of the session, and, from that moment, they use agreed levels, protocols and configuration for further information exchange.

6 is a state diagram of an embodiment relating to a session boot protocol (e.g., session boot protocol 520a, as shown in Figure 5) for the access terminal, which includes an inactive state 610, state 612 and state 614 initialize session. 6A, the session boot protocol for the access terminal transitions from the initial state to inactive state 610 to open a session. In an inactive state 610 is no communication between the access terminal and radio network. After transmitting or receiving the protocol activation message proceeds to initialization state 512 in which the access terminal and radio network exchange messages and query response opening opening. The protocol goes back to the inactive state 610, if the received response message opening indicates that the request is denied, and proceeds to state 614 a session, if the request is accepted. By sharing request message and the response of the opening opening the access terminal is assigned a terminal identifier UATI and session control protocol is selected for use in the session negotiation. In session state 614 or the session is opened, or is in the process of negotiating the session control protocol selected in initialization state 612. The protocol transitions from session state 614 back to inactive state 610 upon transmission and reception of the message upon receiving the closing or reject message from a radio network.

6B shows a state diagram of an embodiment of a session boot protocol for the radio network, which includes an inactive state 620, state 622 and state 624 initialize session. Minutes download session for a radio network enters into an inactive state 620 after receiving an indication to open a session. The protocol transitions from inactive state 610 to initialization state 612 upon receiving a discovery request message from the access terminal. Discovery request message is processed and the protocol transitions back to inactive state 620 after transmitting the response message to the opening indicating deviation open request and the session state 624 after transmitting the response message to the opening indicating reception of the request. The protocol transitions from session state 624 back to inactive state 620 upon sending or receiving messages closure.

6C shows a state diagram of an embodiment of a session control protocol (e.g., session control protocol 520b, as shown in Figure 5) for the access terminal, which includes an inactive state 630, the state of the access terminal 632 initiating, condition 634 and initiate a radio network the state of the opening 636. Session control protocol for the access terminal transitions from the initial state to inactive state 630 for a session negotiation. In inactive state 630 waits protocol activation command and after reception or transmission proceeds to state 632 initiate an access terminal. In the state of initiation of the access terminal 532 is carried out on the initiative of the coordination of the access terminal, and after its completion (for example, as indicated by the transmission complete message configuration) protocol goes into state 634 initiation of a radio network. In the state radio network 634 initiate negotiation is performed at the initiative of the radio network, and after its completion (for example, as indicated by the reception complete message configuration) protocol goes into the opening 636. In the state 636 opening session is open and can be used to exchange application traffic (for example, in streams 0-3) between the access terminal and radio network. The protocol transitions from the opening 636 back to inactive state 630 upon completion of the session (e.g., after transmitting the closure).

6D shows a state diagram of a session control protocol for the radio network, which includes an inactive state 640, the state of the access terminal 642 initiating, condition 644 initiating a radio network, the state of the opening 646 and 648 closing state. Session control protocol for radio network becomes inactive for session negotiation. In inactive state 640 waits protocol activation command and after reception or transmission proceeds to state 642 initiate an access terminal. In the state of initiation of the access terminal 642 runs negotiation, initiated by the access terminal, and after its completion (for example, as indicated by the reception complete message configuration) protocol goes into 644 initiation of a radio network. In the state radio network initiating 644 runs negotiation initiated by a radio access network, and after its completion (for example, as indicated by the transmission complete message configuration) protocol proceeds to state 646 opening. In the state 646 opening session is open and can be used to exchange application traffic between the access terminal and radio network. The protocol transitions from the opening 646 back to inactive state 640 upon receiving a message and closing in the closing state 648 after transmitting the state of closure. From state 648 closing protocol transitions back to inactive state 640 upon receipt of the message or after the closing of the timer.

For simplicity, not all transitions are shown in Figures 6A-6D. For example, deactivate transitions are not shown in Figures 6A and 6B, and holding the transitions are not shown in Figure 6C and 6D.

7A is a block diagram of a specific implementation of the phase 610 of opening session. The protocol discovery phase 610 uses the request message and response message opening opening to allow the access terminal to request and receive an access terminal identifier. The access terminal initiates the message exchange by transmitting a request message to the opening on the reverse common channel (e.g., access channel 444, as shown in Figure 4C) and identifies random access terminal identifier at step 710. The radio network receives and processes the request message at step 712 opening .

In step 714, the radio network determines whether to accept or reject the open request. If the session request is accepted, the radio network assigns an access terminal and generates a response message to the opening, which includes an identifier assigned in step 716. The access terminal identifier to be used by the access terminal during the duration of the communication session. Otherwise, if the session request is rejected, the radio network generates a discovery response message that includes a reason for the rejection, at step 718. The response message also includes opening a random access terminal identifier extracted from request message opening received from the access terminal. Discovery response message is then transmitted to the access terminal on the forward common channel (e.g., control channel 428) in step 720. In the exemplary embodiment, the message in phase 610 are implemented by opening a session (default) session protocol.

As shown in Figure 6, the phase 620 session configuration includes level matching subphase 622 / session protocol, the subphase 624 that configure the / session protocol subphase 626 and the activation level / session protocol. This subphase described below in more detail.

7B is a block diagram of a particular embodiment of the subphase 622 level matching / session protocol. Protocol subphase 622 uses one or more configuration request messages and response messages configuration to allow the access terminal and radio network mutually agree on an acceptable level protocols and configuration.

Initially, the access terminal detects in step 730 a set of layers and protocols (or levels / protocols, which are identified by their types) for approval. For each selected layers and protocols, the access terminal detects in step 732 a set of acceptable configurations (which are identified by their subtypes). The access terminal then generates and transmits in step 734 one or more request messages configuration reverse dedicated channel to the radio network.

Each configuration request message comprises one or more types that identify the corresponding one or more layers / protocols to be agreed. For each type of message also contains a list of one or more suitable subtypes in descending order of preference. In an embodiment, to simplify message processing, each configuration request message includes one or more complete and ordered lists subtypes (i.e., the list is not divided into subtypes configuration request message and not split across multiple configuration request messages).

Radio network receives the message (s) configuration request in step 736 and step 738 identifies each type and the associated list of subtypes. For each recognized type in the request message configuration radio network selects a suitable subtype of the associated subtypes list, the access terminal previously identified as acceptable in step 740. If the radio network does not recognize the type or subtype is acceptable in a linked list, the type is omitted. Radio network then generates and transmits in step 742 a configuration response message that includes the type (s) treated with a radio access network and the Subtype selected for each type. Any type missed radio network, omitted from the response message configuration. In an embodiment, to simplify processing by the access terminal type (s) in the configuration response message are arranged in the same order in which they are in the configuration request message.

An access terminal in step 746 receives a configuration response message and at step 748 compares the type (s) in the configuration response message type (types) configuration request message. For each type of request message configuration, which is not found in the response message configuration, the access terminal determines in step 750 subtype type with default value. For each type of configuration response message, the access terminal determines in step 752 respectively subtype type subtype, found in the received configuration response message.

In an embodiment, the radio network in step 744 notifies the failure is the configuration, if it determines at any time during the message exchange that the types or subtypes selected by the access terminal will not operate.

In an exemplary embodiment, the access terminal at step 754 notifies the failure is the configuration, if it determines at any time during the message exchange that

1) the received configuration response message has no associated configuration request message,

2) configuration response message includes a plurality of attribute values ​​(ie, the set of subtypes) for one attribute (ie, type)

3) configuration response message includes an attribute not found in the associated configuration request message,

4) configuration response message includes an attribute value is not found in the associated configuration request message,

5) configuration response message includes an attribute in a manner that differs from the order in the associated configuration request message, or

6) a configuration selected radio network will not operate.

The failure is a configuration may also be notified to the access terminal and radio network based on some other conditions.

If the failure is notified to the configuration, the party has notified the failure is a configuration session closes. Type and subtype of the closing of closing set according to the type and subtype of link layer protocols. In an exemplary embodiment, if the access terminal and radio network are not able to agree on the configuration for one or more layers / protocols, the session is closed.

Once subphase 622 level translation / protocol for a specific level / protocol is completed, the access terminal and radio network are included in the subphase 624-level configuration / protocol radio session for a given level / protocol. In subphase 624, the access terminal and radio network configuration define levels and protocols agreed during subphase 622 level translation / protocol session. Messages for the subphase 624 transferred their respective types of levels / protocols.

Subphase level configuration / protocol session for one or more selected layers / protocols can be performed sequentially or in parallel to speed up the process of configuration. To improve the compatibility of the radio network can be designed to support both serial and parallel configuration, and the access terminal can be designed to support serial or parallel configuration, or both.

Implementation subphase 624 configuration depends on the particular level / protocol to be configured. Various implementation subphase 624 configurations, all of which are within the scope of the present invention.

7C is a block diagram of an embodiment of the subphase 626 activation level / protocol session. After completion of the subphase 624-level configuration / protocol session for all levels and protocols negotiated access terminal and radio network are included in the subphase activation level 626 / protocol session. In subphase 626, the access terminal and radio network to activate the agreed levels and protocols session. Posts in 626 subphase executed protocol session.

In an exemplary embodiment, the access terminal 780 initiates at step 626 subphase activation request message by transmitting the activation request over a reverse dedicated channel. If the access terminal requires a separation of compounds to activate the agreed levels and protocols, he points out that requirement in the request message activation session. Radio network receives and processes in step 782 the message. Radio network then sends a session activation response message on the forward dedicated channel in step 784. If a connection release is required, the radio network indicates this requirement in the session activation response message.

In step 786 a determination is made whether the access terminal requires a radio network or release compounds to activate agreed levels and protocols. If a connection release is required, the access terminal disconnects the connection in step 788. After the connection release, the access terminal and radio network activate and use the agreed levels and protocols in step 790. Alternatively, it may be determined at step 792 whether a session activation response message to the terminal access. If the session activation response message is received, then the access terminal and radio network activate and use the agreed levels and protocols. The access terminal transmits an acknowledgment message back to the radio network upon receiving a session activation response message.

During the session, if at step 796 it is determined that the required levels of other protocols and / or configuration, the current session is terminated and a new session is established.

In an exemplary embodiment subphase 622 level translation / protocol session can be performed for all selected layers and protocols, and then executed subphase 624 configuration levels / protocols session for each selected level and protocol. Alternatively, subphase 622 level translation / protocol session can be carried out for a specific number of layers and protocols (for example, one level or protocol), and then executed subphase 624 configuration levels / protocols session for selected layers and protocols (eg, subphase coordination and configuration performed as a combination for each level and protocol).

8 is a block diagram of a specific implementation of the subphase 622 level matching / protocol session subphase 624 and level configuration / protocol session initiated by an access terminal to establish a communication link with a radio access network. The access terminal initiates the session by transmitting a message 810 to request the opening of a radio network via a common channel (e.g., access channel 444, as shown in Figure 4, or an access channel in a compatible system IS-95). Discovery request message includes a message identifier and a transaction identifier that identify the message and transaction, respectively, to the radio network. The radio network receives and processes the request message and transmits a discovery response 812 back to the opening of the access terminal. Discovery response message includes the message and transaction identifiers, a result code corresponding to the result of opening request, and an access terminal identifier if the request is accepted.

The access terminal and radio network then determine the layers and protocols to be agreed. This can be realized by exchanging messages 820 and 822 between the access terminal and radio network on the assigned forward and reverse traffic channels (e.g., forward channel 426 and reverse traffic channel traffic 442, as shown in Figure 4). The set of messages may be transmitted by the access terminal and radio network. Messages sent by the access terminal, symbolically represented as message 820 in Figure 8, and the messages transmitted by a radio access network, symbolically represented as message 822.

In an embodiment, the request message and the response of opening the opening of the common channels transmitted by (e.g., access channel and the control) that are shared with other access terminals, but the negotiation and configuration messages are sent via the dedicated channels assigned to a radio access network. Posts query open and create a short opening response. Messages matching configuration and typically are more advanced and are transmitted over the allocated dedicated channel to improve the performance (for example, a shorter response time).

Once the levels and protocols are selected, and then try to negotiate for each selected level and protocol. In an exemplary first agreement and the Protocol, selected a single object (for example, an access terminal) and then fit the levels and protocols, select another object (eg, a radio access network). Object matching specific level or protocol transmits a message to another volume 830 (or 840) the configuration request, which includes one or more selected layers and / or protocols and a list of acceptable configurations for each selected level and protocol. (Negotiated levels and protocols are also called attributes and configurations are also called attribute values.)

Another object receives the request message and responds with appropriate configuration messages 832 (or 842) response configuration, which include concordial levels and / or protocols and selected configuration. Messaging request / response configuration continues as long as the two objects will not consistent attributes. Then the object that initiated the harmonization transmits a message 834 (or 844) confirm to confirm the acceptance of the agreed attribute. Additional selected attributes, if any, in line in a similar manner.

8 posts 830 and 832 834 negotiation and confirmation message are messages for a set of attributes (ie, a level one protocol, etc.). Another set of messages are transmitted for each set of attributes selected for negotiation. In the embodiment shown in Figure 8, the exchange of messages 840 and 842 and a matching confirmation message 844 for the set of attributes selected for negotiation radio network, is performed after the attributes selected by the terminal, the access will be matched.

After completion of the negotiation protocol can be the connection between the access terminal and radio network using the agreed levels and protocols.

In accordance with one aspect of the present invention, the access terminal and radio network are designed to support a basic set of messages. In an exemplary embodiment, the access terminal and radio network support the messages listed in the Table below.

TablitsaSoobschenieIdentifikatorKanalZapros otkrytiya0 00ObschiyOtvet otkrytiya0 × × × 01ObschiyZakrytie0 02ObschiyPrivetstvie0 × 03obschy and vydelennyyZapros konfiguratsii0 04VydelennyyOtvet konfiguratsii0 × × × 05VydelennyyZapros activation konfiguratsii0 06VydelennyyOtvet activation konfiguratsii0 × 07Vydelenny

9A is a diagram of an embodiment of a format for the request message discovery. In this embodiment, the opening request message includes a message identifier field 910 and a transaction-identifier field 912. In an embodiment, field 910, a message identifier is an 8-bit field having a value of 0 × 00, which identifies the request message to the opening, the field 912 transaction identifier is also an 8-bit field having a value that is incremented with each transmission of a new message request the opening.

9B is a diagram of an embodiment of a discovery response message format. In this embodiment, the opening response message includes a message identifier field 920, a transaction-identifier field 922, a result code field 924, field 926 and an access terminal identifier field 928 session inactivity timer. In an embodiment, field 920 of message identifier is an 8-bit field having a value of 0 × 01, which identifies the response message to the opening, the field 922 transaction identifier is also an 8-bit field containing the value of the field 912 the transaction ID in the respective received message open request that is processed. In an embodiment, field 924 result code is an 8-bit field having a value of 0 × 00, if the open request is accepted, a value of 0 × 01, if the open request is rejected for uncertain reasons, and 0 × 02, if the open request is rejected due to lack of resources. They may also be generated and additional or different values ​​for result code field 924.

In an embodiment, a field identifier of the access terminal 926 is a 4-byte field having a value assigned as the access terminal identifier for an access terminal during the duration of the communication session. If the value in the result code field 924 is 0 × 00, the identifier field 926 of the access terminal is set to 0 × 00000000, and the access terminal ignores this value. In an embodiment, field 928 session inactivity timer is an 8-bit field having a value indicating the length of inactivity, in minutes communication session. If the value of the code field 924 of the result is 0 × 00, which indicates the acceptance open request, then the radio network sets the value in the session inactivity timer 928 to a value from a session inactivity timer that is used for the communication session. If the result code field 924 does not correspond to 0 × 00 indicating a deviation discovery request, the box 928 a session inactivity timer is set to 0 × 00, and the access terminal ignores this value.

9C is a diagram of an embodiment of a message format for closure. In this embodiment, the closing message includes a message identifier field 930, a transaction-identifier field 932, a field 934 for closure, the length field 936 and an additional information field 938 additional information. In an embodiment, field 930 of message identifier is an 8-bit field having a value of 0 × 02, which identifies the request message "Close", a field 932 transaction identifier is also an 8-bit field having a value that is incremented with each sending a new message "Close". In an embodiment, field 934 causes the closure is a one-byte field having a value that identifies the reason for closing; length field 936 additional information is 1-byte field having a value that identifies the length (in bytes) of the next field 938 additional information, the additional information field 938 has a variable length, containing additional information pertaining to the closure. The format for the additional information field 938 is dependent on the particular closure.

9D is a diagram of an embodiment of a format for the hello message. In this embodiment, the welcome message includes an 8-bit message identifier field 940 having a value of 0 × 03, which identifies the greeting message.

9E is a diagram of an embodiment of a format for the request message configuration. In this embodiment, the configuration request message contains a field of type 950, the message identifier field 952, field 954, and the transaction ID field 956 of the list of attributes. In an embodiment, field 950 the type is an 8-bit field having a value that identifies the type of configurable protocol field 952 of message identifier is an 8-bit field having a value of 0 × 04, which identifies the connection configuration request, and a field 954 an identifier transaction which is also an 8-bit field having a value that is incremented with each new transmission request message configuration. In an embodiment, attribute-list field 956 is variable in length, includes a list of acceptable subtypes negotiated for each type, each element of the list includes one or more (Type, Subtype) pairs. In an embodiment, if a list includes more than one element, then the elements are sorted in descending order of preference. The receiving entity can determine the length of the configuration request message using the message length.

On 9F is a diagram of an embodiment of a format for a configuration response message. In this embodiment, the configuration of the response message includes a field of type 960, the message identifier field 962, field 964, and the transaction ID field 966 of the list of attributes. In an embodiment, field 960 the type is an 8-bit field having a value that identifies the type of configurable protocol field 962 of message identifier is an 8-bit field having a value 0h05, which identifies the response message to the configuration, and field 922 the transaction ID as a 8-bit field that contains the value of the transaction ID field 954 in the received configuration request to process the message.

In an embodiment, attribute-list field 966 is a variable length field that includes one (or possibly more) acceptable Subtype for each processed Type. The elements of the list of attributes 966 are a pair (type, subtype). Field 966 contains a list of attributes of an element not found in the corresponding configuration request message, and the elements in the list of attributes 966 are arranged in the order in which they are found in the corresponding request message configuration. Again, the receiving entity can determine the length of the response message configuration through the use of message length.

On fig.9G a diagram an embodiment of a format for session activation request message. In this embodiment, a session activation request message includes a message-identifier field 970, a field 972 identifying the transaction and a field 974 indicating the connection release. In an embodiment, field 970 identify the message is an 8-bit field having a value of 0 × 06, which identifies the request message session activation, and the field 972 identifying the transaction is also an 8-bit field having a value that is incremented for each transmitted message request session activation. In an embodiment, field 974 indicating the connection release is a one-byte field with value of 0 × 01, if the access terminal requires the connection to be disconnected to switch to the subphase matching or level configuration / session protocol, and the value 0 × 00 - otherwise.

On fig.9N a diagram an embodiment of a format for session activation response message. In this embodiment, a session activation response message includes a message-identifier field 980, a transaction-identifier field 982 and field 984 indicating the connection release. In an embodiment, field 980 of message identifier is an 8-bit field having a value of 0 × 07, which identifies the response message session activation, and the field 982 identifying the transaction as a 8-bit field containing the value of the field 972 identifying the transaction in the received process the message request activation of the session. In an embodiment, field 984 indicating the connection release is a one-byte field having a value of 0x01 if the access terminal or radio network requires the connection release, to move to the subphase matching or level configuration / session protocol, and the value 0 × 00 - otherwise case.

9A-9H are diagrams of some specific implementations of messages that can be used to configure the applications, layers and protocols. Additional and / or other messages than those described above may also be defined and used (e.g., activation message, a configuration complete message, and many others), and all such variations are within the scope of the present invention. Moreover, the messages can be created with the other (or additional) message formats, fields, and field formats than those shown in Figures 9A-9H, and this is within the scope of the present invention.

The invention provides many advantages. First, the modular design levels and protocol makes it easy to modify and update the communication system to support new features and functionality. The access terminal and radio network can communicate using the layers and protocols commonly supported by both, and this determination can be made at the opening of a session. Second, the basic set of layers and protocols supported by the access terminals and radio networks ensures a minimum level of compatibility among the access terminals and radio networks. To the radio network had compatibility with future generations of equipment in the framework of the signaling protocol, it should implement a limited set of features. For example, the radio network only needs to be able to transmit an "empty" configuration response message in response to the received configuration request. Thus, a signaling protocol according to the invention allows easy implementation of future configurations even if no current configuration is needed.

The invention can be implemented in various ways, it can be implemented in software, hardware or a combination of both. For example, according to Figure 2, the invention may be realized a combination of software and / or hardware in the system control 214 and controller 262, or other blocks associated with the control system 214 and controller 262. The hardware can be implemented as one or more integrated circuits, application specific integrated circuits, digital signal processor, controller, microprocessor, and other circuits designed to perform the functions described herein.

The present invention can be applied in various communication systems, the spread spectrum. The invention is applicable to spread spectrum systems that currently exist and new systems that are continually being created. Specific system code division multiple access (CDMA) is described in the aforementioned U.S. Patent Application №08 / 963,386. Other CDMA system described in the aforementioned U.S. patents and №4901307 №5103459.

The foregoing description of preferred embodiments of the present invention is intended to enable those skilled in the art to make and use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without inventive faculty. Thus, the present invention is not limited to these embodiments, and accorded the widest scope consistent with the principles and novel features disclosed herein.