Method and system for querying attributes in a cellular communications system

[0001] [Technical field to which the invention belongs] The present invention relates to wireless network communication. In particular, the present invention relates to new and improved protocols that allow wireless network elements to communicate. [0002] [Conventional technology] In a communication network, many functions performed by individual network elements require recognition of information from surrounding network elements. Although other techniques such as propagating the required information individually from the central control element to each network element are known, the present invention has far greater advantages than these other techniques. Propagation of information from the central control element to many network elements is time consuming and error prone. In addition, some attributes (such as resource utilization) change frequently. [0003] In a CDMA communication system, many functions performed by network elements require information from surrounding network elements. The present invention describes protocols for information propagation between network elements, including modem pool transceivers and MPCs. A modem pool transceiver (MPT) is a communications network element that modulates and demodulates radio frequency network traffic, which can also perform scheduling, power control and overhead message processing tasks. The MPC is another element that provides the MPT element with wireless control and signaling services, including power control synchronization, modem session state maintenance and network connection control. The MPC generates and processes the data sent and received by the Modem Pool Transceiver (MPT). The MPT requires the air interface attributes of neighboring MPTs to configure the correct air interface overhead message. The MPC requires the MPT air interface attribute to perform the MPT handoff. MPC requires the MPT's air interface attributes to perform access terminal paging. An access terminal (AT) is a device equipped with a modem and a data interface that allows a user to access an IP network through an access network. In order to perform the MPC handoff, the MPC needs the resource utilization attribute of the surrounding MPC. [0004] [Problems to be Solved by the Invention] At present, there is no ideal way to meet the needs of wireless communication network elements for direct exchange of information. [0005] One problem that arises when network elements cannot exchange information directly is that MPC does not have a convenient way to find information about the surrounding MPT needed to perform AT paging. At any given time, the MPC may be able to make page transfers to one or more dormant ATs. [0006] Dormant refers to the period during which the AT and access network have an established session, but the configured connection does not. The dormant mode allows the AT to remain "always on" while using only limited wireless link capacity and limited AT power when sending and receiving data. [0007] In order to transmit data to the dormant AT, the MPC must be able to locate the AT. The MPC locates the dormant AT by page forwarding to the dormant AT in all MPTs where the dormant AT may be located. This collection of MPTs is called the paging area. In order to page forward to a dormant AT, the MPC must know the paging area. [0008] Currently, there is no ideal way to meet MPC's need to dynamically discover the paging area information needed for AT paging. [0009] [Means for solving problems] The present invention is a new and improved protocol for directly updating attribute information in a communication network. [0010] The present invention provides a general protocol based on the Hypertext Transfer Protocol version 1.1 (HTTP / 1.1) and the Multipurpose Internet Mail Extended Specification (MIME), which separates individual network elements without going through a network manager. It is possible to directly make inquiries about information to the network element of. This greatly reduces system failures caused by propagation errors and trivial information, and facilitates the deployment and removal of additional network elements. [0011] Network elements make their attributes available through the use of HTTP / 1.1. Another network element can use the HTTP GET method to query for specific attributes. The response is a return HTTP header with a MIME part body containing a list of attribute names / value pairs. [0012] The present invention provides a general protocol that allows a communication network element to query another network element for information. As a result, network information can be configured at one location and dynamically queried by another location. It prevents propagation errors and outdated information errors introduced by individually propagating the requested information through the network management interface to each network element by the central network manager. [0013] Embodiments of the present invention also satisfy the paging information discovery needs by providing a protocol that allows the MPC to dynamically query the information required for AT paging from the MPT. The present invention provides a method of determining a cellular paging area of a wireless communication network by directly exchanging network configuration information between network elements, and determining an access terminal paging area from the exchanged network configuration information. [0014] BEST MODE FOR CARRYING OUT THE INVENTION The features and advantages of the present invention will be apparent from the following detailed description and the corresponding drawings consistently with the same reference numerals. Figure<u style="single">2 A</u>Shows an exemplary communication network system in which the present invention is used. Figure<u style="single">2 A</u>Indicates a wireless communication network access point 100 connected by Internet Protocol (IP) network 110. Access port The INT100 provides wireless services to subscribers within a predetermined geographic area. The access point 100 sometimes divides a portion of the geographical coverage area called a sector and serves it independently. Access point sectorization is technically well known, and the rights referenced herein are assigned to the applicant US Pat. No. 5,625,876 ( METHOD AND APPARATUS FOR PERFORMING HANDOFF BETWEEN SECTORS OF It is explained in detail in A COMMON BASE STATION ). The MPT106, which covers the same or RF-close areas, is called the access point neighborhood. In wireless communication systems, the given MPT106 and MPC108 need information MPT106 Is determined by the RF propagation characteristics of the signal transmitted by the network access point. In an exemplary embodiment, the access point 100 is configured with a single hardware platform that includes one or more MPTs (MPTs) 106, one MPC108, and one network access server (NAS) 104. It is a topological element of a communication network. The network access server 104 is a device that controls access to services on the network based on the user identities of the network services in question and the policies of the providers of these services. The NAS104 performs traditional network access server protocol features such as point-to-point (PPP) suits, remote authentication dial-in user server (RADIUS) protocol suits, and Layer 2 Tunneling Protocol (L2TP) suits. .. The MPT106 contains a bank of traffic channel modems, produces the transmitted waveform, and also MPT106 Can receive transmissions from subscribers within the coverage area of. The MPT106 generates and receives waveforms by modulating and demodulating radio frequency network traffic, which also performs scheduling, power control and system parameter message processing tasks. The MPC108 is a network element that generates and processes data to be transmitted and received by the MPT. The MPC108 also provides wireless control and signaling services to the elements of the MPT106, such as power control synchronization, modem session state maintenance and network connection control. [0015] Traditional wireless network configurations: In addition to distributed MPCs and distributed NAS, there are two topological access network reference models. [0016] FIG. 1 illustrates an exemplary embodiment of the invention corresponding to the traditional, i.e., distributed MPT10 radio communication network topography in which the MPC14 is centralized at a point traditionally identified as the base station controller 16. It is a functional block diagram. The functions of NAS18 are located at a point that is sometimes recognized as Packet Data Service Node (PDSN) 20. Figure 1 shows a distributed MPT access network with MPT10 distributed and MPC14 and NAS18 centralized. A distributed MPT access point is formed by grouping two or more MPTs located in one or the same location. An access network is formed by connecting one or more distributed MPT access points, one or more centralized MPCs, and one or more centralized network access servers. [0017] A in Figure 2 shows the distributed NAS wireless communication network topography. For distributed NAS access networks, MPT106, MPC108 and NAS104 Are dispersed. A in Figure 2 shows an access point 100 formed by grouping one or more MPTs, one or more MPCs, and one or more network access servers. An access network is formed by connecting one or more distributed access points. [0018] Figure 2B shows distributed MPC wireless communication network topography. In a distributed MPC access network, MPT206 and MPC200 are distributed and NAS208 is centralized. An access point is formed by grouping one or more MPTs and one or more MPCs. An access network is formed by connecting one or more distributed access points and one or more centralized network access servers. Again, the access point elements use the present invention to communicate directly with each other via IP network 202. In a distributed MPC access network, MPT and MPC are distributed and NAS is centralized. [0019] In a CDMA communication network, operation and network management parameters must be known in many places within the system. Although the present invention has been described in the context of CDMA communication networks, those skilled in the art will recognize that the teachings of the present invention can be easily extended to other wireless communication systems such as GMS and AMPS communication networks. Let's do it. These parameters include information contained in action messages such as handoff instruction messages, power control parameter messages, page messages and neighbor list messages. The content of these messages is technically well known and is the family of the American Telecommunications Industry Association standard IS-95 (MOBILE STATION-BASE STATION COMPATIBILITY STANDARD FOR DUAL-MODE WIDEBAND SPREAD SPECTRUM CELLULAR SYSTEM. These messages are provided for illustration purposes only. Those skilled in the art can extend their teachings to other messages necessary for the operation of the wireless communication system. You will recognize that the network configuration parameters must also be known and updated in many places, for example, the MPT106 will be brought online, offline, or temporary. In the event of a failure, another MPT106 and MPC108 in the system must be notified of resource changes. The present invention provides the information individually requested to each network element from the central network manager through the network management interface. It is an improved technique over the known conventional technique for updating parameters such as propagation. The conventionally known method requires the intervention of a central manager, and a propagation error that causes a system failure occurs. [0020] The present invention makes it possible for wireless CDMA network information propagation to resemble Internet information propagation by eliminating the need for a centralized manager. There is no central manager on the Internet above the Internet, and new information is pushed down to each router 102 on the Internet each time a router is added or removed from the Internet. Internet routers can know their neighbors by address configuration and can directly query information about them via a wired connection. The present invention provides a protocol for an MPT106 element to communicate directly with an element in any other sector without a wired connection, given a list of fully qualified domain names (FQDNs) of neighboring MPT106s. This makes it possible to query information about the neighborhood. MPC108 are the MPT106 they serve Contains a list of. Therefore, the present invention eliminates the need to individually propagate redundant information from the central position through the network management interface to each network element. The present invention allows MPT106 and MPC108 network elements to be added and removed from wireless communication networks in exactly the same way routers are added or removed from the Internet. [0021] [0021] The present invention provides a protocol that allows a network entity to retrieve information from a single network entity whose information is very easily constructed. This protocol is an easy and flexible way to discover information and know how long it is valid. The present invention allows attributes at one location to propagate directly to another location where they are needed. Moreover, since most of the information rarely changes, the protocol returns only that information if the queried information has changed since the last such query. [0022] Figure 3 shows a high-level block diagram of the information query procedure. Block 300 In, the parameters of the network element are changed. At block 302, the parameter list contained in the network element is updated to indicate the change. At block 304, the remote network element requests the information in its list. At block 306, the network element containing the list determines if the list has been updated since it was last queried by the requested element. If the list has been updated since the last query, in block 307 the updated list is returned to the device that made the query. If, in block 306, the network element containing the list determines that no changes have been made, then in block 309 the list is not returned. If the list is returned in block 307, in block 308 the remote network element updates its parameter list accordingly. [0023] Figure 4 shows the information queried from a remote location in block 304, and block 308. Shows the machine interface used to return the updated information in. In an exemplary embodiment, the network element requests attribute information by using the Hypertext Transfer Protocol (HTTP) GET message 418. The element receives information in an HTTP response 420 that includes an HTTP header field 426 and a Multipurpose Internet Mail Extension (MIME) part 427. The MIME part 427 consists of a MIME header 408-414 and a body containing a list of requested attribute names / values vs. 416. [0024] A network element that requests attributes using the HTTP GET418 method because it matches the term HTTP is called a client and provides the attribute 416 requested in response HTTP header 426 and MIME partial response 427. Is called a server. An exemplary embodiment of the invention uses the formats described in HTTP version 1.1 and MIME version 1.0. The remote client queries the updated information from server location 304. [0025] The client requests the desired attribute value using the HTTP GET method with the attribute name contained in the query field of the absolute universal resource identifier (URI). In an exemplary embodiment, URI418 is in partial form: [Number 1]<img file="JP4833472B2_D0001.tif" />have. Where element 402 is the fully qualified domain name of the serving element, port 403 is the port number of protocol 404, and attribute 406 is the desired attribute separated by an &amp;. The HTTP request header may also include the option fields shown in RFC2068. The present invention always sets conditions on the request on the optional IF MODIFIED SINCE field 421. The client uses IF MODIFIED SINCE field 421 to inform the server when it last updated the information. [0026] The server uses IF MODIFIED SINCE field 421 in request 418 to determine if updated information should be returned. If the server has not updated the information since the time specified in IF MODIFIED SINCE field 421, the server returns an abbreviated response 420 to the client containing only the HTTP header 426 field with no MIME part 427 response. [0027] The requested information is IF If it has been updated since the time specified in the MODIFIED SINCE field and therefore meets the IF MODIFIED SINCE 418 condition for the request, the server has HTTP header 426 and attribute name / value vs. 416 for the requested attribute. Respond with MIME part 427 containing the list. The server silently discards unrecognized attributes. The server contains the LAST MODIFIED field 425 in the response header 426. The server sets the value of LAST MODIFIED field 425 to the modification time and date of the most recently modified attribute in the response. [0028] Responses to attribute queries are transmitted in version 1.0 of the experimental MIME subtype 408 text / x-attribute-list. This MIME subtype is indicated by context type field 408. Version parameter 410 indicates the version of the format in x-attribute list 408. The current value for version parameter 410 is 1.0. Character set parameter 412 Indicates the character set used. In an exemplary embodiment, the value valid only for the character set parameter is "US-ASCII". &lt;Element&gt; Parameter 414 indicates the network element type of the server. For example, "modem pool transceiver" and "modem pool controller" indicate that the server is a communication network MPT and a communication network MPC. The body 416 of the MIME part contains zero or more fields. Each field contains a name and value for one attribute. [0029] Some attribute fields 416 are very easily represented as elements of the array. This MIME partial format 427 employs a uniform method for representing an array as a set of fields 416. A multidimensional array is treated as one array of multiple arrays. Array elements are indexed from 0 using integers. With respect to the attribute array having the attribute name "X", the element numbers in the attribute array are represented by the attribute name "X #". The element K in the attribute array is represented by the attribute name X [K] with respect to the attribute array having the attribute name X. [0030] If the request contains an attribute name for an attribute array, response 420 includes the number of elements in that array and each element in that array, and the number of elements in that array is in the array. Appears before any of the elements of. [0031] Some attributes, such as those that represent the characteristics of MPT neighborhoods, are very easily represented as part of the hierarchy. This MIME partial format 427 employs a uniform method of representing certain attributes in the hierarchy as fields. When an attribute in the hierarchy is converted to a field, it is converted to the attribute name "YX", where "X" is the name of the attribute and Y is the attribute name of the parent of that attribute. Figure<u style="single">4 and 5</u>Shows examples of arrays and hierarchies. [0032] The network element makes all of those attributes available by the query protocol of the present invention. [0033] FIG. 5 is a data tree diagram of an exemplary embodiment of a partial data hierarchy of the present invention, showing an MPT data structure. Those skilled in the art will recognize that the hierarchy is shown for illustration purposes and does not contain all of the required attributes. In addition, another structure may be used, which is within the technical scope of the present invention. [0034] Location (LOCATION) 502 is a hierarchical route for all attributes that locate the MPT. [0035] TRANSLATION 504 is a hierarchical root of all attributes that locate the MPT. Latitude (LATITUDE) 506 identifies the latitude of the MPT. Its latitude is expressed in degrees, minutes and seconds, and positive numbers indicate the northern hemisphere. The latitude range is from -90 ° to + 90 °. Longitude (LONGITUDE) 510 Specifies the longitude of the MPT. Longitude is expressed in degrees, minutes and seconds, and positive numbers indicate east longitude. The range of longitude is from -180 ° to + 180 °. Altitude (ALTITUDE) 508 identifies the altitude of the MPT. Altitude is expressed in meters, with positive numbers indicating altitude above sea level. [0036] ROTATION 512 is a hierarchical route of all attributes that identifies the orientation of the MPT with respect to the Earth. Horizontal (HORIZONTAL) 514 identifies the horizontal orientation of the MPT with respect to the true east. Horizontal orientations are expressed in degrees, minutes and seconds, and positive numbers identify the northern hemisphere. Vertical (VERTICAL) 516 identifies the relative vertical orientation of the MPT. Vertical orientation is expressed in degrees, minutes and seconds. The range of vertical orientation is from -90 ° to + 90 °. [0037] Time (TEMPORAL) 518 identifies the MPT's local time offset to Coordinated Universal Time (UTC). Local time offsets are expressed in hours, minutes and seconds. The range of local time offset is from -12 o'clock to +12 o'clock. [0038] Antenna (ANTENNA) 520 Is a hierarchical route of all attributes that characterizes the MPT's antenna. Transmit (TRANSMIT) 522 is an array of hierarchical routes of all attributes that characterize the transmitting antenna of the MPT. LOCATION 540 is a hierarchical route of all attributes that locates the transmitting antenna with respect to the location identified at location 502. Beam width (BEAM WIDTH) 542 is the beam width of the transmitting antenna. Beam width is expressed in degrees. The beam width range is 0 to 360 degrees. Gain (GAIN) 544 is the gain of the transmitting antenna. The gain of the transmitting antenna is expressed in decibels. The gain range is 0 to 100 decibels. [0039] RECEIVE 524 is an array of hierarchical routes of all attributes that characterize the MPT's receiving antenna. Location (LOCATION) 546 is a hierarchical route of all attributes that locates the receiving antenna with respect to the location identified at location 502. Beam width (BEAM WIDTH) 548 Is the beam width of the receiving antenna. Beam width is expressed in degrees. The beam width range is 0 to 360 degrees. Gain (GAIN) 550 is the gain of the receiving antenna. The gain of the receiving antenna is expressed in decibels. The gain range is 0 to 100 decibels. [0040] Neighbor (NEIGHBOR) 526 is an array of hierarchical routes of all attributes that characterize the neighborhood of the MPT. FQDN528 contains the fully qualified domain name (FQDN) of the neighborhood. Cost (COST) 530 includes the cost of using the neighborhood. The lower this cost, the more likely it is that an AT communicating with the MPT will see an MPT in this neighborhood. This cost is useful for prune extras from oversized neighborhood lists. [0041] The CONTROLLER 532 is an array containing each of the MPCs to which the MPT receives service. FQDN534 contains the fully qualified domain name of the controller. [0042] AIR INTERFACE 536 Are all hierarchical routes of the air interface attribute of the wireless communication network. The AIR INTERFACE 526 route is extensible to any air interface protocol. HDR538 is an example of an extension of the hierarchical route of Air Interface 536. HDR is a proposal for an air interface that supplies high-speed digital data.<u style="single">To. Another</u>Possible air interface extensions include, but are not limited to, GSM, IS-95, CDMA2000 and WCDMA. [0043] FIG. 6 is a flowchart of one embodiment illustrating an intermediate level overview of the system parameter query and update mechanism of the present invention. Those skilled in the art will recognize that the order of the steps shown in FIG. 6 is not limited. Further, a request for information is logically integrated like its response, and is typically considered to be a request and response in which only a subset of the information is integrated information. Typically, requests are made in multiple requests for a complex collection of attributes, rather than in sequence for a single attribute, as shown for simplicity. FIG. 6 is a summary of the information exchanged in the exemplary embodiments of the present invention. The information query process starts at block 600 when the client wants to update information about the server. In an exemplary embodiment, the client updates information about attributes that identify the MPT characteristics of the server. [0044] Block 601 In, the client conditionally requests the location information 502. A detailed flowchart of the position attribute request method is shown in FIG. In block 602, if the location information requested by this client changes on the server after the time specified in the IF MODIFIED SINCE field for this information because it was conditioned by the IF MODIFIED SINCE 421 field of request 418. At block 604, the server returns new location attribute information and the process proceeds to block 605. If the requested information has not changed, the server returns header field 426, but does not return MIME part 427 with the new location attribute information, and the process goes directly to block 605. If new attribute information is returned in block 602, the client updates its location attribute information accordingly in block 604. [0045] At block 605, the client has antenna information 520 Conditionally request. A detailed flowchart of the antenna attribute request method is shown in FIG. In block 606, if the requested antenna information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information because it was conditioned by the IF MODIFIED SINCE421 field of request 418, the server Returns new antenna attribute information in block 608 and the process proceeds to block 609. If the requested information has not changed, the server returns header field 426, but does not return MIME part 427 with the new antenna attribute information, and the process goes directly to block 609. If new attribute information is returned in block 606, the client updates its antenna attribute information accordingly in block 608. [0046] At block 609, the client conditionally requests neighborhood information 526. A detailed flowchart of the neighborhood attribute request method is shown in FIG. Block 610 In, if the requested neighbor information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client because it was conditioned by the IF MODIFIED SINCE 421 field of request 418, the server Returning new neighbor attribute information in block 612, the process proceeds to block 613. If the requested information has not changed, the server returns header field 426, but does not return MIME part 427 with new neighbor attribute information, and the process goes directly to block 613. If new attribute information is returned in block 610, the client updates its neighbor attribute information accordingly in block 612. [0047] At block 613, the client conditionally requests controller information 532. A detailed flowchart of the controller attribute request method is shown in FIG. In block 614, request 418 IF MODIFIED SINCE421 If the controller information requested by this client for this information changes on the server after the time specified in the IF MODIFIED SINCE field because it was conditioned by the field, the server will have new controller attribute information in block 616. And the process proceeds to block 617. If the requested information has not changed, the server returns header field 426, but does not return MIME part 427 with the new controller attribute information, and the process goes directly to block 617. If new attribute information is returned in block 614, in block 616 the client updates its controller attribute information accordingly. [0048] At block 617, the client conditionally requests air interface information 536. In block 618, the requested air interface information was IF MODIFIED for this information from this client because it was conditioned by the IF MODIFIED SINCE 421 field of request 418. If the server changes after the time specified in the SINCE field, the server returns new air interface attribute information in block 620 and the process proceeds to block 622. If the requested information has not changed, the server returns header field 426, but no new air interface attribute information, and the process goes directly to block 622. If new attribute information is returned in block 618, in block 620 the client updates its air interface attribute information accordingly. [0049] FIG. 7 is a flowchart of an exemplary embodiment of the system parameter update method for the position attribute 502 that specifies the position of the MPT type network element. Positional attribute 502 is a hierarchical route for all attributes that locate the MPT. Figure 7 shows a detailed flowchart of location attribute request 601. MPT location information query process when ant has desired location updates neighboring MPT server on the wireless communications network, starting from the block 700. [0050] At block 702, the client requests latitude information. Transformation attribute 504 is a hierarchical data structure route for all attributes that describe the physical location of the MPT on Earth. Latitude attribute 506 identifies the latitude of the MPT in degrees, minutes and seconds, and positive numbers identify the northern hemisphere. In block 702, the client is conditioned, for example, from MPT0000.mpt an.net on protocol port 10 based on IF MODIFIED SINCE field 418: [Number 2]<img file="JP4833472B2_D0002.tif" />Request latitude information 506 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested latitude information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will table with the LAST MODIFIED field and as + | -dd.mm.ss.f. Returns the new latitude attribute information in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field of the Location.Translation.Latitude value that is created. The latitude range is from -90 degrees to +90 degrees. [0051] At block 704, the client requests position conversion longitude information. The longitude attribute 510 identifies the longitude of the MPT, expressed in degrees, minutes and seconds, and a positive number identifies the east longitude. Block 704 In, the client is conditioned from an exemplary MPT based on IF MODIFIED SINCE field 418: [Number 3]<img file="JP4833472B2_D0003.tif" />Request longitude information 510 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested longitude information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will table with the LAST MODIFIED field and as + | -dd.mm.ss.f. Returns the new longitude attribute information in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field of the Location.Translation.Longitude value that is created. The range of longitude is from -180 degrees to +180 degrees. [0052] At block 706, the client requests repositioning altitude information. The altitude attribute 508 identifies the altitude of the MPT in meters, and positive numbers indicate altitudes above sea level. Block 706 In, the client is conditioned from an exemplary MPT based on IF MODIFIED SINCE field 418: [Number 4]<img file="JP4833472B2_D0004.tif" />Request altitude information 508 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested altitude information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have the LAST MODIFIED field and + | -mf. Returns the new altitude attribute information in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field of the Location.Translation.ALtitude value represented as. [0053] At block 708, the client requests horizontal orientation information. Rotation attribute 512 is the root of the hierarchical data structure of all attributes that describe the orientation of the MPT with respect to the earth. Horizontal attribute 514 identifies the horizontal orientation of the MPT with respect to the true east. Horizontal orientations are expressed in degrees, minutes and seconds, and positive numbers identify the northern hemisphere. At block 708, the client is conditional on the example MPT0000.mpt an.net on protocol port 10 based on IF MODIFIED SINCE field 418: [Number 5]<img file="JP4833472B2_D0005.tif" />Request horizontal information 514 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested horizontal orientation information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have the LAST MODIFIED field and + | -dd.mm.ss.f. Returns the new horizontal attribute information 514 in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field for the Location.Rotation.Horizontal value represented as. The horizontal range is from -180 degrees to +180 degrees. [0054] At block 710, the client requests vertical orientation information. Vertical attribute 516 Identifies the vertical orientation of the MPT with respect to a line drawn perpendicular to the center of the earth. Vertical orientation is expressed in degrees, minutes and seconds. In block 710, the client is conditional from the exemplary MPT based on IF MODIFIED SINCE field 418: [Number 6]<img file="JP4833472B2_D0006.tif" />Request vertical information 516 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested vertical orientation information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have the LAST MODIFIED field and + | -dd.mm.ss.f. Returns the new vertical attribute information 516 in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field for the Location.Rotation.Horizontal value represented as. The range of vertical orientation is from -90 degrees to +90 degrees. [0055] At block 712, the client requests location-time information. Time attribute 518 is the root of the hierarchical data structure of all attributes that describe the time offset of the MPT. Time attribute 518 Identify the local time offset of the MPT with respect to Coordinated Universal Time (UTC). Local time offsets are expressed in hours, minutes and seconds, with positive numbers indicating the difference between the added time and UTC. At block 712, the client was conditioned from an exemplary MPT based on IF MODIFIED SINCE field 418: [Number 7]<img file="JP4833472B2_D0007.tif" />Request time information 518 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested time information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have the LAST MODIFIED field and + | -hh.mm.ss.f. Returns the new time attribute information in response 427 of the MIME part containing the NAME-ATTRIBUTE NAME-VALUE field of the Location.Temporal value represented as. The range of local time offset is from -12 o'clock to +12 o'clock. When the client completes the location request, the location 502 request ends at block 714. [0056] Figure 8 shows the antenna attribute 520, which identifies the antenna characteristics of the MPT. It is a flowchart of an exemplary embodiment of the system parameter update method of the present invention for all of. FIG. 8 shows a detailed flowchart of antenna attribute request 605. The MPT antenna information query process starts at block 800 when the client wants to update the antenna information from the MPT server in the wireless communication network. [0057] At block 802, the client requests antenna transmission information. Antenna attribute 520 is the root of the hierarchical data structure of all attributes that characterizes the antenna or set of antennas in the MPT. Transmit attribute 522 is an array of hierarchical routes of all attributes that characterize the transmit antenna of the MPT. Position 540 is a hierarchical route of all attributes that locates the transmitting antenna with respect to the position identified at position 502. The beam width 542 is the beam width of the transmitting antenna. Beam width is expressed in degrees. The gain 544 is the gain of the transmitting antenna. The gain of the transmitting antenna is expressed in decibels. [0058] [0058] MPT transmission 522 Some attributes such as are very easily represented as one element of the array. This MIME partial format employs a uniform method of representing an array as a set of fields. A multidimensional array is treated as one array of multiple arrays. Array elements are indexed from 0 using integers. With respect to the attribute array having the attribute name "X", the element numbers in the attribute array are represented by the attribute name "X #". For an attribute array having an attribute name "X", the element K in the attribute array is represented by the attribute name "X [K]". [0059] If the request contains an attribute name for an attribute array, response 420 includes the number of elements in that array and each element in that array, and the number of elements in that array is in the array. Appears before any of the elements of. [0060] In block 802, the client is conditioned based on IF MODIFIED SINCE field 418 from an exemplary MPT with one transmit antenna: [Number 8]<img file="JP4833472B2_D0008.tif" />Request transmit array information 522 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested information changes on the server after the time specified in the IF MODIFIED SINCE field for this information from this client, the server is represented by the LAST MODIFIED field and Antenna.Transmit # 1 as an example. A MIME containing the number of elements in the antenna transmit array, the gain of the transmit antenna, represented as Antenna.Transmit [0] .Gain: df, and the beam width of the transmit antenna, represented as Antenna.Transmit [0] .Beamwidth: df. Returns the new antenna transmit array attribute information in part response 427. The beam width range is 0 to 360 degrees. The gain range is 0 to 100 decibels. [0061] Block 804 In, the client requests the receiving antenna information. Antenna reception attribute 524 is an array of hierarchical data structure routes of all attributes that characterize the MPT's receive antenna or set of receive antennas. Position 546 is a hierarchical route of all attributes that locates the receiving antenna with respect to the position identified at position 502. The beam width 548 is the beam width of the receiving antenna. The beam width range is 0 to 360 degrees. The gain 550 is the gain of the receiving antenna. The gain of the receiving antenna is expressed in decibels. [0062] In block 804, the client is conditioned from an antenna MPT with one receiving antenna based on IF MODIFIED SINCE field 418: [Number 9]<img file="JP4833472B2_D0009.tif" />Request receive antenna array information 524 by issuing on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested information changes on the server after the time specified in the IF MODIFIED SINCE field for this information from this client, the server will be represented by the LAST MODIFIED field and Antenna.Receive #: 1. Includes the number of elements in the receiving array, the gain of the receiving antenna, represented as Antenna.Receive [0] .Gain: df, and the beam width of the receiving antenna, represented as Antenna.Receive [0] .Beamwidth: df. Returns the new antenna receive array attribute information in response 427 of the MIME part. The beam width range is 0 to 360 degrees. The gain range is 0 to 100 decibels. [0063] When the client completes the request for antenna information, the request for antenna information 520 ends in block 806. [0064] FIG. 9 is a flowchart of an example of the neighborhood attribute 526 that identifies the neighborhood characteristics of the MPT. Figure 9 shows a detailed flowchart of Neighbor Attribute Request 609. The MPT neighborhood information query process starts at block 900 when the client wants to update the neighborhood information from the MPT server on the wireless communication network. [0065] At block 902, the client requests neighborhood information 526. Neighbor 526 is an array of hierarchical routes of all attributes that characterize the neighborhood of the MPT. Neighbor information 526 contains FQDN 528 and cost information 530. The FQDN attribute 528 contains the fully qualified domain name (FQDN) of the neighborhood. Cost attribute 530 contains information about the use of the neighborhood. [0066] MPT106 Some attributes, such as attributes that represent the characteristics of the neighborhood of, are very easily represented as part of the hierarchy. This MIME type employs a uniform method of representing certain attributes in the hierarchy as fields. When an attribute in the hierarchy is converted to a field, it is converted to the attribute name "YX", where "X" is the name of the attribute and Y is the attribute name of the parent of that attribute. [0067] The information of neighbor attribute 526 is both an array and a hierarchy. In block 902, the client requests neighbor attribute information 526 from an exemplary hierarchy. This exemplary hierarchy includes a wireless communication network 110 with one MPC108 and three MPT106s. MPC108 has a fully qualified domain name "0000.mpc.an.net". In this example, MPT106 has fully qualified domain names "0000.mpt.an.net", "0001.mpt.an.net" and "0002.mpt.an.net". Each MPT106 is in the vicinity of the other two MPT106s and has no routing costs. [0068] MPT106 Stores the neighbor attribute in the array attribute neighbor 526. The stored information is the fully qualified domain name of the neighborhood with the attribute name FQDN 528 and the routing cost of the neighborhood with the attribute name cost 530. [0069] In block 902, the MPC client 0000.mpc.an.net is conditional on the IF MODIFIED SINCE field 418: [Number 10]<img file="JP4833472B2_D0010.tif" />Request all information about all neighbors of MPT0000.mpt.an.net by generating on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested information changes on the server after the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have all new neighbor array hierarchies in the LAST MODIFIED field and MIME part response 427. Return information. In addition, the body 416 has Neighbor #: 2 that the controller has in an exemplary array. Neighbor number represented as, Neighbor [0] .FQDN: 0001.mpt.an.net, FQDN of the first neighborhood, Neighbor [0] .Cost: 0 of the first neighborhood NAME-ATTRIBUTE NAME for the cost, the FQDN of the second neighbor, represented as Neighbor [1] .FQDN: 0002.mpt.an.net, and the cost of the second neighbor, represented as Neighbor [1] .Cost: 0. -Contains a VALUE field. [0070] When the client completes the request for neighbor hierarchy information, the request for information for neighbor 526 ends in block 904. [0071] FIG. 10 is a flowchart of an embodiment of the system parameter update procedure of the present invention for an attribute that identifies the MPC network type for which the MPT network type has received a service. Figure 10 shows controller attributes 612. Shows a detailed flowchart of the request. The controller information query process starts from block 1000 when the client wants to update the controller information from which the MPT server can receive services. [0072] At block 1002, the client requests controller information 526. Controller attribute 532 is the root of the hierarchical data structure of the attribute array that holds the MPC's FQDN 534 that the MPT can use. [0073] At block 1002, the client requests FQDN array information 534 from an exemplary MPT with one MPC. In block 1002, the client is conditional on IF MODIFIED SINCE field 418: [Number 11]<img file="JP4833472B2_D0011.tif" />Occurs on the network. The server returns a header containing the context type 408 of the text / x attribute list, version 410 of 1.0, the value of the us-ascii character set 412, and the value of element type 414 of the modem pool transceiver. If the requested information has changed on the server since the time specified in the IF MODIFIED SINCE field for this information from this client, the server will have the LAST MODIFIED field and an exemplary controller represented as Controller #: 1. Returns the new controller array attribute information in response 427 of the MIME part containing the element number in the array and the domain name represented as Controller [0] .FQDN: 0001.mpc.an.net. [0074] FIG. 11 is a block diagram showing a device used to perform the attribute query operation of the present invention. Access point 1100A Consists of a network element 1112 and a network interface 1104 such as an IP router. The network interface 1104 is a device that determines the next network point to which a data packet directed to a destination should be transferred and connects the network element to the IP network by various subscriber services. The network element 1112 can be an MPT (10,106 or 206), MPC (14,108 or 200) or a network access server (18,104 or 208). For illustration purposes, only a portion of the network element closely related to the attribute query operation is shown in the network element 1112. [0075] The network element 1112 includes a memory device 1110 that stores the attributes of the network element 1100, the attributes of which include a fully qualified list of domain names of another network element queried by the network element 1112. Control processor 1106A Receives a signal from the request message generator 1102 indicating the need for information from another network element. The control processor 1106A searches the memory element 1100A for a fully qualified domain name in response to the signal from the request message generator 1102, and generates a query message together with this signal and the fully qualified domain name. The control processor 1106 supplies the message to router 1104A, which routes the message to the appropriate network element 1106B. Router 1104B directs the request message to network element 1112B. The request message is fed to control processor 1106B. In response to the request message, control processor 1106B retrieves information about the requested attribute from memory 1110B. Response message generator 1108B supplies message packaging information to control processor 1106B. Control processor 1106B responds to information from memory 1110B, and response message generator 1108B is router 1104B. Generate a response message to supply to. Router 1104B directs the response message to control processor 1106A on access point 1100A. [0076] If the attribute information in the response message from element 1100B is new, control processor 1106A updates the information in memory element 1110A. Those skilled in the art will recognize that reverse query operations can be performed from element 1112B of element 1112A by simply exchanging A and B. [0077] FIG. 12 is a flowchart of an exemplary embodiment of the method of the invention that requests and caches attribute information to reduce processing and network traffic. The client request and server caching method shown in Figure 12 allows the client to request that the server send that information only when the information changes, causing the server to repeatedly generate the same response. It is prevented from returning. [0078] Block 1222 shows a conditional request on the client side. In HTTP, the GET method is conditioned based on several different criteria. This allows the client to request that the server send the information only when the information changes. In particular, its use in this query protocol is a condition of IF MODIFIED SINCE. The use of IF MODIFIED SINCE conditions reduces network traffic and client processing. At block 1200, the client uses the GET method conditional on the IF MODIFIED SINCE field to request attribute information. At block 1202, the client determines whether the server has responded to the updated MIME part 427 attribute information. If the server responds with the attribute information of the updated MIME part 427, in block 1204, the client responds to each different query to each server for use in future queries. To cache. If the client repeatedly queries server 1200, the client sets IF MODIFIED SINCE field 421 to the value of returned LAST MODIFIED field 425. [0079] Block 1224 shows the server-side caching method of the present invention. In many examples, protocols that use this query protocol always use the same query. Moreover, in many examples, protocols that use this query protocol query for rarely changing attributes known as static attributes. As a result, the current server repeatedly generates and returns the same response. By caching query responses containing only static attributes, the present invention reduces server processing. In the present invention, the server tags certain attributes as "static". Attributes tagged as "static" should be attributes that change little. For example, hard-coded attributes (such as protocol revisions) and attributes that change only during network configuration and optimization (such as neighborhood lists) are good candidates to be tagged as static. On the other hand, attributes that change as a function of loading (such as available bandwidth) are unsuitable candidates for being tagged as "static". In block 1206, the server modifies static attributes. In block 1208, the server flushes all cached responses whenever one of the attributes tagged "static" is modified. This unnecessarily flushes some cached pages. However, the "static" attribute, self-evidently, changes little, so the effect of unnecessary cache flushing is minimal. The server ensures that the cache is flushed if the attribute being queried is modified. The server gains many of the benefits of caching using a simple traditional cache flushing algorithm. [0080] [0080] At block 1210, the server receives an attribute query from the client. At block 1212, the server determines if there is a cache for the queried information. If the cache has been previously flushed due to attribute changes, the server forms a new cache in block 1220 and control proceeds to block 1214. Otherwise, control goes directly to block 1214. [0081] At block 1214, the server uses the query's IF MODIFIED SINCE field 421 to determine if the requested information has changed since the last such request. If the information has not changed, only the HTTP response header 426 is returned, as indicated by block 1218. If the requested information has been modified after the time specified in the IF MODIFIED SINCE field, in block 1216 the server returns the response in HTTP response header 426 and MIME part 427 from the cache. [0082] FIG. 13 is a block diagram showing a device used to perform paging information discovery by the access network paging information protocol. The access network paging information protocol allows the MPC1300 to dynamically determine the paging area 1302 of the AT1306 controlled by the MPC. [0083] If the AT is dormant, or if the AT has an active session but no active connection, then the AT1306 allows the access network to perform regular location updates. There are several triggers that cause the access network to update their location by AT. [0084] The MPC element 1300 provides services to a collection of one or more MPT elements 1308 by IP network 1304. The AT1306 either updates its location by sending its location information to the MPT1308 that has located it, or registers it with the MPC1300. MPT1308 transfers location information to MPC1300 via IP network 1304. The MPC1300 determines the position of the AT1306 by performing a page transfer to the AT1306 in all MPT1302s that can determine the position of the AT1306. The group of MPT1302 that can locate the AT is the paging area 1302 of the AT. [0085] FIG. 14 shows the AT paging area. In one embodiment, a protocol for MPC is provided to determine the paging area without the intervention of a central network manager. The paging area is determined by the AT1404 location update procedure known as registration. When AT1404s are moving within the access network, they register their locations with the MPC based on different criteria, including distance 1406 and / or zone 1400, depending on the type of location registration enabled in AT1404. Is required. The registration area is the MPT1402 with the reported location update plus all other MPTs that can be moved without re-registration because the AT1404 does not exceed the range of the distance or boundary zone. In other words, the registration area is the area where the AT1404 can locate it without having to re-register. This area is determined by the registration distance and registration zone. The AT is located within the same registration area if it is located within the same registration zone within the registration distance of the latest AT it has registered. [0086] The paging area is a list of MPT1402,1403 in which the AT can be positioned at any given time. This list includes MPT1402s located within the AT's registration area and all their neighbors 1403. Neighbors 1403 of MPT1402 in the registration area are included in the paging area taking into account that it takes a non-zero AT time to detect that a position update must be done and perform that position update. .. In other words, the AT may have entered the range of nearby MPTs before the location update took place in the MPC. [0087] If the zone-based registration is enabled on the AT1404, the AT1404 must perform a relocation if the AT1401 moves from one zone 1400A to an adjacent zone 1400B. If the distance-based registration is enabled on the AT1404, the AT1404 must perform a position update if the AT1404 has moved farther than the distance R1406 since its last position update. The generated paging area is one ring of MPT1402, which last reported itself so that AT1404 can locate it, and MPT1403 in the vicinity around MPT1402. [0088] The paging area depends on the distance and the value of the zone position update trigger. The values of these triggers can vary between MPTs, but they are AT independent. The registration distance 1406 and zone 1400 are configured by the service provider operator so that each MPT balances the registered traffic volume with respect to the paging traffic volume on the network. The paging discovery protocol and paging area algorithm of the embodiments described herein determine a location for paging to an AT through the access network based on the configured information and the last registered location. To do. [0089] Each MPT has its own paging area. The sector may have one or more MPTs. If the sector has more than one MPT, the MPT is communicating with the AT at different frequencies. Neighboring MPTs within adjacent sectors are known as horizontal neighbors. Neighboring MPTs within the same sector operating at different frequencies are known as vertical neighbors. [0090] FIG. 15 is a high-level block diagram of a method according to one embodiment for performing paging information discovery in a wireless communication system. [0091] Distance and zone update triggers allow the access network to reduce the paging area for a single AT. [0092] If a distance-based position update is enabled, the AT will perform the position update after it has traveled a longer distance than the position update distance since it last performed the position update. If zone-based location updates are enabled, the AT will perform location updates after it has moved into a different location update zone than the location update zone in which it last updated. [0093] Blocks 1500 to 1510 show the paging function of the AT. At block 1500, the AT determines if its distance-based position update is enabled. If distance-based position updates are enabled, at block 1502, AT determines if the distance has changed to be greater than its configured registered distance. If not, control goes directly to block 1506. In block 1502, if the AT determines that the distance has changed and is greater than the distance trigger, in block 1504 the AT updates the position distance and control proceeds to block 1506. If no distance update is required at block 1504, control proceeds to block 1506. [0094] At block 1506, the AT determines if zone-based position updates are enabled. If zone-based location updates are enabled, in block 1508 the AT determines if it has moved into a different location update zone than the one that last updated the location. If zone-based location updates are not enabled, AT processing is aborted until the next update interval. In block 1508, if the AT determines that the zone has changed, in block 1510 the AT updates the position zone and the AT processing is aborted until the next update interval. If zone update is not required in block 1510, AT processing is aborted until the next update interval. The update interval is determined by the state machine that runs each time the AT moves into the coverage of the new MPT. [0095] When the AT performs a location update, the location update is transferred to the MPC that provides the AT service. If the MPC does not service the MPT that received the location update, one of the following two things will happen: If the access network supports MPC handoff, the AT will handoff to the MPC servicing the MPT that received the location update. If the access network does not support MPC handoff, the session ends and the AT will need to set up a new session. The new session is set up by the MPC servicing the MPT that received the location update. As a result, the number of paging areas that a particular MPC must recognize and maintain that information can be reduced. [0096] Blocks 1512-1514 represent the individual paging function tasks of the MPT. In task block 1512, the MPT receives a position update from the AT. In task block 1514, the MPT forwards the location update to the MPC servicing this MPT and forwards the paging message received from the MPC to the AT. In task block 1515, the MPT responds to a paging discovery attribute query from the MPC. [0097] Blocks 1516-1520 represent the individual paging function tasks of the MPC. In task block 1516, the MPC receives the AT position update transferred by the MPT and uses that information in task block 1518 to determine the paging area to be updated for that AT. In task block 1520, the MPC sends a paging message to the dormant AT. The MPC paging area determination and AT paging function will be described in detail with reference to FIG. 17 below. [0098] FIG. 16 is a data tree diagram of an exemplary embodiment of the partial data hierarchy of the present invention, showing the paging information discovery attribute, which is an extension of the air interface 536 route. Those skilled in the art will recognize that the hierarchy is merely an example and does not contain all of the required attributes. In addition, another structure may be used, which is within the technical scope of the present invention. [0099] Air interface 1600 is a hierarchical route of air interface attributes. HDR1602 is a hierarchical route for all HDR air interface attributes. Protocol 1603 is a hierarchical route for all HDR air interface attributes organized by protocol type and protocol subtype. TYPE<u style="single"></u>08 08 1604 is a hierarchical route for all HDR air interface attributes associated with the HDR protocol type 8 overhead protocol. SUBTYPE<u style="single"></u>0000 1606 is a hierarchical route for all HDR air interface attributes associated with the HDR protocol type 8 route update protocol and the protocol subtype 0 default overhead protocol. [0100] Access network ID 1608 identifies the access network to which the MPT belongs. Sector ID 1610 identifies the sector to which the MPT belongs. Channel frequency 1612 identifies the channel frequency of the MPT. [0101] TYPE<u style="single"></u>Ten 1614 is a hierarchical route for all HDR air interface attributes associated with the HDR protocol type 10 route update protocol. SUBTYPE<u style="single"></u>0000 1616 is a hierarchical route for all HDR air interface attributes associated with the HDR protocol type 0x10 route update protocol and the protocol subtype 0 default route update protocol. [0102] Latitude 1618 identifies the latitude of the AT. This attribute is equal to the attribute LOCATION.TRANSLATION.LATITUDE 506. Longitude 1620 identifies the longitude of the AT. This attribute is the attribute LOCATION.TRANSLATION. Equal to LONGITUDE 510. [0103] The position update distance enable 1622 is a Boolean attribute that indicates whether distance-based position updates are enabled. The position update distance 1624 is the position update distance. The position update zone enable 1626 is a Boolean attribute that indicates whether zone-based position update is enabled. Location update zone 1628 is a location update zone. [0104] FIG. 17 is a block diagram showing a paging area determination and an AT paging method according to one embodiment. Paging area determination and AT paging are MPC functions. Each MPC forms a database containing the paging area of each AT that the MPC serves. [0105] A database with a simple configuration has one paging area input per AT. Since the MPC can serve as many as 1000 ATs per MPT, this configuration can generate a very large database. Furthermore, since the mobile station AT moves frequently, a large number of database updates can be performed as a result of this configuration. However, in this embodiment the database is constructed in a more efficient way. [0106] The paging area depends on the distance and the value of the zone position update trigger. The values of these triggers differ between MPTs, but their values are independent of AT. Therefore, the paging area database of this embodiment has one paging area input per MPT instead of one paging area input per AT. Having one input per MPT reduces the size of the database, probably because many ATs are located within the same MPT. [0107] When the AT performs a location update, the location update is transferred to the MPC that provides the AT service. If this MPC is not servicing the MPT that received the location update, one of the two responses will be provided in this embodiment. If the access network supports MPC handoff, the AT will handoff to the MPC servicing the MPT that received the location update. If the access network does not support MPC handoff, the session ends and the AT will need to set up a new session. The new session is set up by the MPC servicing the MPT that received the location update. As a result, the paging area database is made even simpler in this embodiment. [0108] The MPC hands off or releases the repositioning AT in the MPT not serviced by this MPC, so if the database of this embodiment contains only the paging area input for each MPT it serves. Good. If the MPC is located within an access point, the database of this embodiment will contain only inputs to the MPT within the same access point. [0109] At block 1700, the MPC forms the initial population of its database. To form a population of paging area databases, each MPC uses the algorithm of this embodiment to determine the paging area for each MPT it serves. In this embodiment, paging area changes are discovered every 20 minutes by having the MPC redetermine the paging area for each MPT serviced by the MPC every 15 minutes. In addition, the MPC will redetermine the paging area whenever the MPC is reset, such as after a firmware upgrade or power outage. Finally, this embodiment allows the MPC to redetermine the paging area at command from the operator. [0110] At block 1702, the first determination of the paging area is made. First, when determining the paging area for the MPT, the MPC behaves as follows. The MPC starts at the root MPT and recursively traverses the neighborhood list until one of the stop criteria is met. The root MPT is the MPT for which the MPC determines the paging area. If the distance-based position update is enabled on the root MPT, this recursion stops when the distance between the root MPT and the queried MPT exceeds the position update distance of the root MPT. If a zone-based location update is enabled on the root MPT, this recursion will stop when the zone of the queried MPT is different from the zone of the root MPT. The MPT paging area is a list of all MPTs queried. [0111] The paging area contains all MPTs that the AT does not relocate if the AT has repositioned at the root MPT. In addition, the paging area includes the MPT neighborhood described above. Neighbors are included taking into account that it takes a non-zero AT time to detect that a location update must be performed and perform that location update. [0112] The algorithm of this embodiment prunes the MPT to which the AT has paged based on the position update area. However, this algorithm does not prun the MPT to which the AT has paged based on the AT identifier. An access node of an access network is a single coverage, single frequency connection point to an access network. An access node is a basic building block of an access network. Access nodes are identified by their sector (sector ID) 1610 and their carrier frequency (channel frequency). An access network sector is a collection of one or more channels with the same geographic coverage area and sector ID 1610. [0113] If the access port contains a large number of access nodes, page messages for a particular AT need only be sent to the access nodes that the AT hashes, i.e., successfully matches the AT page message address key. Hashing is the conversion of an AT address into a (usually shorter) fixed-length value, or key, which represents the original address. Hashes are used to index and search items in a database. This is because it is faster to find the item using a shorter hash key than using the original value. [0114] The algorithm can further reduce the MPT paging list by removing all access nodes in the access port where the AT does not hash, i.e. does not get address key matching. However, in this embodiment, the MPT paging list is not reduced by removing all access nodes in the access port that the AT does not hash for the following reasons: If an access node in an access port fails, some ATs covered by that access port will hash to different access nodes. If the access node paging list had been pruned to include only the access node that the AT originally hashed, the access node paging list would need to be updated whenever such an access node failure occurs. There is. The reduction in services caused by such access node failures is related to the MPT paging list update rate. As a result, pruning the access node paging list so that the AT contains only hashed access nodes increases the MPT paging list update rate, which is not desirable. [0115] After first determining the paging area, in block 1704 the MPC regularly redetermines the paging area. The re-decision is the same as the first decision 1702, with one exception. In the first decision, if the queried MPT does not respond, the recursion by that MPT will stop. However, in the redetermination, if the queried MPT does not respond, the recursion assumes that its configuration has not changed since the last query and continues. This allows the protocol to tolerate a temporary reduction in MPT. Since the reduction is acceptable in this embodiment, the adjustment of the list does not have to be done at every MPT for each temporary reduction. The list is dynamically constructed, with each cell discovering paging information for itself. This embodiment eliminates the paging area from being recognized by the central manager in the event of a temporary cell failure. A feature of this embodiment eliminates paging area information propagation errors and system failures caused by paging failures. In addition, if the carrier changes the registration distance or zone, the list does not have to be manually changed by the central network manager. Instead, this embodiment provides a method of automatically updating the paging area using the paging information discovery and access network attribute query protocol. [0116] For the initial determination and redetermination of the paging area, the MPC must query the MPT for the information presented in Block 1706. MPC queries using the access network attribute query protocol. MPC is NEIGHBOR.FQDN 528, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>08.SUBTYPE<u style="single"></u>0000 1606 and AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>0000 "Query the MPT with IF MODIFIED SINCE conditional HTTP GET request 418 for each parameter of 1616. [0117] The MPC may not require all of these attributes from a particular MPT. However, the protocol of this embodiment generates a single query, which is a merger of all attributes, rather than a separate query from each MPT for a particular attribute required by the MPC. This is done so that each MPT receives the same query from all each MPC. Therefore, the MPT only needs to cache one query response. However, the MPC needs to discard the attributes it does not need. [0118] MPC is the attribute AIR INTERFACE.HDR.PROTOCOL.TYPE from the query response.<u style="single"></u>08.SUBTYPE<u style="single"></u>0000.ACCESS NETWORK ID 1608, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>08.SUBTYPE<u style="single"></u>0000.SECTOR ID 1610 and AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>08.SUBTYPE<u style="single"></u>Use 0000.CHANNEL FREQUENCY 1612. [0119] If the queried MPT is the root MPT, the MPC will have the additional attribute AIR INTERFACE.HDR.PROTOCOL.TYPE from query response 420.<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LATITUDE 1618, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LONGITUDE 1620, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LOCATION UPDATE DISTANCE ENABLED 1622, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LOCATION UPDATE DISTANCE 1624, AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LOCATION UPDATE ZONE ENABLED 1626 and AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>Use 0000.LOCATION UPDATE ZONE "1628". [0120] If the distance-based position update is enabled in the root MPT, the MPC will have the additional attribute AIR INTERFACE.HDR.PROTOCOL.TYPE from query response 420.<u style="single"></u>10.SUBTYPE<u style="single"></u>0000.LATITUDE 1618 and AIR INTERFACE.HDR.PROTOCOL.TYPE<u style="single"></u>10.SUBTYPE<u style="single"></u>Use with 0000.LONGITUDE 1620. [0121] If a zone-based location update is enabled in the root MPT, the MPC will have the additional attribute AIR INTERFACE.HDR.PROTOCOL.TYPE from query response 420.<u style="single"></u>10.SUBTYPE<u style="single"></u>Use 0000.LOCATION UPDATE ZONE "1628". [0122] At block 1708, the MPC uses the paging protocol of this example to transfer pages to the AT serviced by the MPC. When a page transfer is made to the AT, the MPC sends a page message to one or more MPTs. [0123] Each page message sent by the MPC contains an identifier for the AT to which the page is being forwarded. This allows the MPT to drop the page message based on whether the AT hashes to the MPT access node. [0124] The MPC sends a copy of the page message to each MPT in the page area. The IP address used by the MPT for its paging source may be a unicast, multicast or broadcast address. [0125] The IP address of the MPT's paging resource can be a multicast and broadcast address to reduce the number of page message copies that the MPC must send and thus reduce paging traffic on the access network. [0126] If either distance-based or zone-based location updates are enabled, the pacing message contains a unique radio identifier that includes access network ID 1608 and sector ID 1610 for each MTP in the paging area. This allows the MPT to drop page messages that it does not respond to transmissions. [0127] The preferred embodiments of the present invention have been illustrated and described above. However, one of ordinary skill in the art will recognize that various modifications can be made to the embodiments disclosed herein without departing from the technical scope of the invention. Therefore, the present invention is not limited except in the appended claims.<u style="single">The inventions described in the claims at the time of filing the present application are described below.</u><u style="single">[1] Directly exchange network configuration information between network elements</u><u style="single">A method of determining the cellular paging area of a wireless communication network that includes the step of determining the access terminal paging area from the exchanged network configuration information.</u><u style="single">[2] The method of [1] further comprising the step of transmitting a paging area determination information query from the modem pool controller network element to the modem pool transceiver network element.</u><u style="single">[3] The method of [1] further comprising the step of transmitting a paging area determination information response from at least one modem pool transceiver network element to the modem pool controller network element.</u><u style="single">[4] The method of [1] further comprising the step of receiving a response to a paging area determination information query from a modem pool transceiver network element in a modem pool controller network element.</u><u style="single">[5] The method of [1] further comprising the step of transmitting location update information from the access terminal network element to the modem pool transceiver network element.</u><u style="single">[6] The method of [1] further comprising the step of receiving location update information from the access terminal network element in the modem pool transceiver network element.</u><u style="single">[7] The access terminal network element further includes the step of using the network configuration information to determine the paging area for each access terminal network element, and the access terminal network element performs page transfer in the paging area [1]. Method.</u><u style="single">[8] The method of [1], wherein the paging area is determined without intervention by a central network manager.</u><u style="single">[9] The method of [1], wherein the paging area is determined by zone information.</u><u style="single">[10] The method of [1], wherein the paging area is determined by distance information.</u><u style="single">[11] The method of [1], wherein the paging area is determined by distance and zone information.</u><u style="single">[12] The method of [1] further comprising the step of reducing the paging area according to the network configuration information.</u><u style="single">[13] The method of [1], wherein the network configuration information includes an access network ID.</u><u style="single">[14] The method of [1], wherein the network configuration information includes a network sector ID.</u><u style="single">[15] The method of [1], wherein the network configuration information includes a network channel frequency.</u><u style="single">[16] The method of [1], wherein the network configuration information includes the latitude of the network element.</u><u style="single">[17] The method of [1], wherein the network configuration information includes the longitude of the network element.</u><u style="single">[18] The method of [1], wherein the network configuration information includes distance position update enable information.</u><u style="single">[19] The method of [1], wherein the network configuration information includes zone location update enable information.</u><u style="single">[20] The method of [1], wherein the network configuration information includes a location update distance.</u><u style="single">[21] The method of [1], wherein the network configuration information includes a location update zone.</u><u style="single">[22] A first network element that generates a request message indicating a request from the second network element for paging area information, and a first network element.</u><u style="single">An access point comprising a network interface for an internet protocol that routes the paging area request message to the second network element.</u><u style="single">[23] The first network element is an access point of [22] that includes a memory element that stores paging area information network attributes and a control processor that generates attribute request and response messages.</u><u style="single">[24] The memory element is further an access point of [23] that stores all paging area information attributes of the first network element.</u><u style="single">[25] The control processor further updates the memory element when the response message indicates new paging area attribute information [23].</u><u style="single">[26] The access point of [23], wherein the control processor further generates a response message in response to a paging information attribute inquiry message received by being guided from the second network element to the first network element.</u><u style="single">[27] In the first element of the network element, a query is generated based on the Internet protocol.</u><u style="single">A method of direct information propagation between elements of a wireless communication network, comprising the step of transmitting the query to a second element of the network element.</u><u style="single">[28] The inquiry is received by the second network element, and the inquiry is received.</u><u style="single">A response to the query is generated based on the internet protocol in the second network element.</u><u style="single">The method of [27] further comprising the step of transmitting the response to the first network element.</u><u style="single">[29] The method of [27], wherein the first network element is a modem pool transceiver and the second network element is a modem pool transceiver.</u><u style="single">[30] The method of [27], wherein the wireless communication network is a CDMA wireless communication network.</u><u style="single">[31] The method of [27], wherein the wireless communication network is a GSM wireless communication network.</u><u style="single">[32] The method of [27], wherein the wireless communication network is an IS-95 wireless communication network.</u><u style="single">[33] The method of [27], wherein the wireless communication network is a WCDMA wireless communication network.</u><u style="single">[34] The method of [27], wherein the wireless communication network is a cdma2000 wireless communication network.</u><u style="single">[35] The method of [28] further comprising the step of receiving the response at the first network element and updating the parameter information at the first network element.</u><u style="single">[36] The method of [27], wherein the inquiry request information relates to the position of the second network element.</u><u style="single">[37] The inquiry request information relates to the conversion of the second network element [36].</u><u style="single">[38] The inquiry request information relates to the latitude of the second network element [37].</u><u style="single">[39] The method of [37], wherein the inquiry request information relates to the longitude of the second network element.</u><u style="single">[40] The inquiry request information relates to the altitude of the second network element [37].</u><u style="single">[41] The inquiry request information relates to the rotation of the second network element [36].</u><u style="single">[42] The method of [41], wherein the inquiry request information relates to the horizontal position of the second network element.</u><u style="single">[43] The method of [41], wherein the inquiry request information relates to a vertical position of the second network element.</u><u style="single">[44] The method of [40], wherein the inquiry request information relates to time information of the second network element.</u><u style="single">[45] The inquiry request information relates to the antenna of the second network element [27].</u><u style="single">[46] The method of [45], wherein the inquiry request information relates to a transmitting antenna of the second network element.</u><u style="single">[47] The method of [46], wherein the inquiry request information relates to the position of the second network element.</u><u style="single">[48] The method of [46], wherein the query request information relates to the beamwidth of the second network element.</u><u style="single">[49] The method of [46], wherein the query request information relates to the gain of the second network element.</u><u style="single">[50] The method of [45], wherein the inquiry request information relates to a receiving antenna of the second network element.</u><u style="single">[51] The method of [50], wherein the inquiry request information relates to the position of the second network element.</u><u style="single">[52] The method of [50], wherein the query request information relates to the beamwidth of the second network element.</u><u style="single">[53] The method of [50], wherein the query request information relates to the gain of the second network element.</u><u style="single">[54] The method of [27], wherein the inquiry request information relates to the vicinity of the second network element.</u><u style="single">[55] The method of [54], wherein the query request information relates to a fully qualified domain name of the second network element.</u><u style="single">[56] The inquiry request information relates to the cost of the second network element [54].</u><u style="single">[57] The method of [27], wherein the query request information relates to a modem pool controller of the second network element.</u><u style="single">[58] The method of [57], wherein the query request information relates to a fully qualified domain name of the second network element.</u><u style="single">[59] The inquiry request information relates to the air interface of the second network element [27].</u><u style="single">[60] The method of [59], wherein the inquiry request information relates to air interface parameter information of the second network element.</u><u style="single">[61] The method of [27], wherein the first network element is a modem pool transceiver and the second network element is a modem pool controller.</u><u style="single">[62] The method of [27], wherein the first network element is a modem pool control device and the second network element is a modem pool control device.</u><u style="single">[63] The method of [27], wherein the first network element is a modem pool controller and the second network element is a modem pool transceiver.</u><u style="single">[64] The method of [27], wherein the request is set in the first element of the network element based on the novelty of the information requested from the second element of the network element.</u><u style="single">[65] The response of the second network element to the first network element is a condition in the second element of the network element based on the novelty of the information requested by the first element of the network element. The method of [28] to be set.</u><u style="single">[66] A network element that generates a request message indicating a request from another network element regarding attribute information,</u><u style="single">An access point comprising a network interface for an IP that routes the request message to the other network element.</u><u style="single">[67] The network element is</u><u style="single">A memory element that stores a list of fully qualified domain names,</u><u style="single">An access point [66] that includes a control processor that generates an attribute request message according to at least one fully qualified domain name in the list of fully qualified domain names.</u><u style="single">[68] The memory element is further an access point of [67] that stores all the attributes of the network element.</u><u style="single">[69] The control processor further updates the memory when the response message indicates new attribute information [67].</u><u style="single">[70] The access point of [67], wherein the control processor further generates a response message in response to receiving an attribute query message guided from the other network element to the network element.</u>[Simple explanation of drawings] FIG. 1 is a functional block diagram of an exemplary embodiment of the invention for traditional or distributed MPT wireless communication network topography. FIG. 2 is a schematic diagram of distributed NAS wireless communication network topography and distributed MPC wireless communication network topography. FIG. 3 is a flowchart showing a system parameter update mechanism of the present invention. FIG. 4 is a schematic diagram of an exemplary embodiment of the contents of a machine request and a machine response of the present invention. FIG. 5 is a data structure diagram showing a data hierarchy of the present invention. FIG. 6 is an intermediate level flowchart showing an overview of the system parameter update mechanism. FIG. 7 is a flowchart showing a position updating procedure of the present invention. FIG. 8 is a flowchart showing an antenna attribute updating procedure of the present invention. FIG. 9 is a flowchart showing a procedure for updating a neighboring MPT of the present invention. FIG. 10 is a flowchart showing an MPC update procedure of the present invention. FIG. 11 is a block diagram showing a device used to perform the attribute query operation of the present invention. FIG. 12 is a flowchart showing an information cache method of the present invention. [Fig. 13] The block diagram which shows the device used for paging information discovery in a wireless communication system. FIG. 14 is a schematic view of an AT paging area. FIG. 15 is a high-level flowchart showing a method used to perform paging information discovery in a wireless communication system. FIG. 16 is a data structure diagram showing a data hierarchy of paging information discovery attributes according to an embodiment of the present invention. FIG. 17 is a block diagram showing a paging area determination method.