Methods for informing subscribers in a channelized network of adjacent sites
Summary by NHIP
Adjacent Site List Exchange
The method informs mobile devices of adjacent sites across two distinct networks by exchanging location data. A site in the second network broadcasts a first list derived from maintained information, while an adjacent site information gateway determines and sends a second list of nearby sites in the first network to that site.
Claim Score by NHIP
Abstract
A method for informing a mobile device of adjacent sites in a RF communication system is disclosed. The RF communication system comprises a first network and a second network. At a site in the second network of the RF communication system, information is maintained of adjacent sites wherein the adjacent sites are within the first network, and a first list of adjacent sites is broadcast to at least one mobile device within coverage of the site in the second network.

Term
Term ended
Expired 28 May 2025, 1.3 years ago.
- Priority and filed
- Granted
- Expired
- Today
18 claims: 2 independent, 16 dependent
- 1A method for informing a mobile device of adjacent sites in a RF communication system wherein the RF communication system comprises a first network and a second network comprising the steps of:at a site in the second network of the RF communication system: maintaining information of adjacent sites wherein the adjacent sites are within the first network;and broadcasting a first list of adjacent sites to at least one mobile device within coverage of the site in the second network, wherein the first list of adjacent sites is created from the maintained information;at a site in the first network of the RF communication system: updating an adjacent site information gateway with information of a site in the first network;and at the adjacent site information gateway: determining a second list of adjacent sites in the first network that are near the site in the second network;and sending the second list to the site in the second network.
- 18Broadest claimClaim Score 54, average(NHIP)A system for informing a mobile device of adjacent sites in a RF communication system wherein the RF communication system comprises a first network and a second network comprising the steps of:means for maintaining information of adjacent sites at a site in the second network of the RF communication system, wherein the adjacent sites are within the first network;means for broadcasting a first list of adjacent sites to at least one mobile device within coverage of the site in the second network, wherein the first list of adjacent sites is created from the maintained information;means for updating an adjacent site information gateway with information of a site in the first network;means for determining a second list of adjacent sites in the first network that are near the site in the second network;means for sending the second list to the site in the second network.
Independent claims2
35 paragraphs in 5 sections, as filed
RELATED APPLICATION(S)
0001This application is related to a co-pending application entitled “METHODS FOR PROVIDING SUBSCRIBERS OF ADJACENT SITES,” filed on Mar. 29, 2005 with application Ser. No. 11/092,089, and assigned to the assignee of the instant application.
FIELD OF THE INVENTION
0002The present invention relates generally to wireless communication systems and in particular to the field of adjacent site updates in wireless communication systems.
BACKGROUND
0003A wireless communication system generally comprises a number of “mobile devices,” where the mobile devices are typically the endpoints of a communication link, and communications infrastructure comprising sites, where the communications infrastructure is typically stationary and the intermediaries by which a communication link to a mobile device may be established or maintained. As a mobile device moves in a geographic area, the mobile device may handoff from one site to another site in the communications infrastructure, so that the communication link is maintained. It is generally desirable to allow for the rapid establishment of communication links between a mobile device and the communications infrastructure without errors and without inadvertently dropping or losing a communication link.
0004Where the communications infrastructure comprises of one type of network, e.g. a traditional channelized network, such as a radio network, the ability to establish communication links between the mobile device and the communications infrastructure is generally accommodated by informing the mobile device of adjacent sites so that when the mobile device has the need to hand off from one site to another, the mobile device has knowledge of adjacent sites. Such a solution is not available where the communications infrastructure comprises of two different types of networks, e.g. a channelized network and a packet data network.
0005If a mobile device requires the need to switch from a site (also generally referred to as a “base station” or a “transmitter”) of a first network to a site of a second network, the mobile device has no knowledge of the sites in the second system. For example, when the mobile device moves between areas serviced by a first network that is a channelized network and areas serviced by a second network that is a packet data network, the mobile device needs to be able to hand off from the first network to the second network without affecting the communication taking place by the mobile device. For example, when a police officer moves from his squad car served by a first network to go inside police headquarters building served by a second network, the police officer should be able to continue his/her conversation using the same communication unit and without having his or her communication delayed or dropped.
0006Accordingly, there is a need for informing a mobile device in a first network of adjacent sites in a second network.
BRIEF DESCRIPTION OF THE FIGURES
0007The present invention is illustrated by way of example and not limitation in the accompanying figures, in which like references indicate similar elements, and in which:
0008<figref idref="DRAWINGS">FIG. 1</figref> is an example of a simple block diagram illustrating an RF communication system in accordance with some embodiments of the invention.
0009<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart illustrating a method for a site in a first network to be informed of sites in a second network in accordance with some embodiments of the invention.
0010Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.
DETAILED DESCRIPTION
0011Before describing in detail adjacent site updates in accordance with an embodiment of the present invention, it should be observed that the present invention resides primarily in combinations of method steps and apparatus components related to adjacent site updates. Accordingly, the apparatus components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
0012In this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “comprises . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
0013Referring to <figref idref="DRAWINGS">FIG. 1</figref>, a radio frequency (RF) communication system <b>100</b> according to an embodiment of the present invention illustratively comprises an adjacent site information gateway <b>106</b> which interfaces between a first network, namely Network A, <b>102</b> and a second network, namely Network B, <b>104</b>, and mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b>. Network A <b>102</b> comprises sites <b>118</b>, <b>120</b> and Network B <b>104</b> comprises sites <b>116</b>, <b>122</b>. In <figref idref="DRAWINGS">FIG. 1</figref>, each network is illustrated with only two sites for the purpose of ease of illustration. However, it should be understood by those of ordinary skill in the art that both networks may be designed with any number of sites. Further, in <figref idref="DRAWINGS">FIG. 1</figref>, only two networks are shown for ease of illustration. However, it should be understood by those of ordinary skill in the art that more than two networks may co-exist where the adjacent site information gateway interfaces between the more than two networks.
0014As used herein, the term “site” is generally composed of at least one co-located transceiver having a substantially similar coverage area or antenna pattern. As is known in the art, the transceiver is generally referred to as a “base station,” “base radio,” “repeater,” or “access point.” Further, the term “site” generally has specific meaning depending on the type of network that the “site” is associated with, but in any case the “site” provides RF coverage over a specific geographic area. For example, referring to <figref idref="DRAWINGS">FIG. 1</figref>, sites <b>116</b>, <b>122</b> of Network B <b>104</b> are generally fixed in location and comprise a control and voice channel that adheres to a TIA <b>102</b> (also known as APCO 25) standard and sites <b>118</b>, <b>120</b> of Network A may be fixed or mobile and may adhere to IEEE 802 standards. In an exemplary embodiment of the present invention, sites <b>116</b>, <b>122</b> of Network B <b>104</b> further comprise a database of adjacent site information.
0015In an exemplary embodiment of the present invention, the adjacent site information gateway <b>106</b> is an interface which provides signaling for the two networks. That is, the adjacent site information gateway <b>106</b> receives messages from one network and provides information to a second network. As mentioned above, the information contained in the messages is kept in a database of site <b>116</b> where the database includes information about sites in the two networks and has information such as site IDs, capacity, and site location. Further yet, a typical adjacent site information gateway <b>106</b> includes a main processing unit such as a computer with appropriate control software that controls the operation of the gateway <b>106</b>.
0016Network A <b>102</b> and Network B <b>104</b> are separate networks where the two networks differ in at least one characteristic. The two networks may differ in ownership. For example, Network A <b>102</b> may be owned by one governmental entity, and Network B <b>104</b> may be owned by another governmental entity. The two systems may differ in whether they are managed or not, where management refers to the level of central control of the network. For example, Network A <b>102</b> may be an unmanaged network, such as a wireless local area network (WLAN) and Network B <b>104</b> may be a managed network, such as a Trans European Trunked Radio (TETRA) network. The two systems may differ in protocol. For example, Network A <b>102</b> may be an Association of Public Safety Communication Officers Project 25 (APCO 25) radio network and Network B <b>104</b> may be an Internet Protocol (IP) network. The two systems may differ in the type of switching. For example, Network A <b>102</b> may be a packet data network having no switching and Network B <b>104</b> may be a circuit switched network. The two systems may differ in channelization. For example, Network A <b>102</b> may be a single channel network and Network B <b>104</b> may be a channelized network. The two systems may differ in capacity. For example, Network A <b>102</b> may support high bitrate traffic and Network B <b>104</b> may support only low bitrate traffic. The two systems may differ in Quality of Service guarantees. For example, Network A <b>102</b> may support only best effort QoS and Network B <b>104</b> may support a guaranteed QoS. The two systems may differ in the ability to support communication with a mobile device that is in motion. For example, Network A <b>102</b> may communicate with stationary mobile devices and Network B <b>104</b> may communicate with mobile devices traveling at high speeds. In any case, the characteristic that differentiates the two networks is at least one of ownership, management, protocol, switching, channelization, capacity, Quality of Service guarantees, and ability to support communication with a mobile device that is in motion.
0017The endpoints of communication in the RF communication system <b>100</b> are the mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b>. The mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b> are generally communication devices that may be either sources or recipients of payload and/or control messages routed through the RF communication system <b>100</b>. As such, the mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b> may be any suitable type of wireless communications device capable of communicating within the RF communication system <b>100</b>, for instance, a laptop computer, a personal digital assistant, a voice handset, or any other suitable device as will be appreciated by those of skill in the art. In an exemplary embodiment, the mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b> are P25 radios equipped with a WLAN modem. The mobile devices may also be connected to a fixed communications infrastructure, if desired.
0018In operation, the mobile device, e.g. mobile device <b>124</b>, may roam from a first coverage area serviced by Network B <b>102</b> to a second coverage area serviced by Network A <b>102</b> while receiving a communication. The communication may be voice, video, or a multi-media communication encompassing both voice and video and may be received from another mobile device or from another communications device either within the RF communication system <b>100</b> or without. Thus, the mobile device <b>124</b> may be connected to Network B <b>104</b> and move into an area serviced by Network A <b>102</b>. As is known in the art, the two areas may physically overlap and the two networks may serve the same physical area. In an embodiment of the present invention, the mobile devices <b>124</b>, <b>126</b> are informed of the sites, e.g. sites <b>118</b>, <b>120</b>, in Network A <b>102</b> so that a mobile device in Network B <b>104</b> can switch without disruption to Network A <b>102</b>.
0019While an embodiment of the present invention has been described in broad terms regardless of the types of networks, an embodiment of the present invention is contemplated to work with many types of networks. For example, both Network A <b>102</b> and Network B <b>104</b> may be APCO 25 voice radio systems owned by different entities. For example, Network A <b>102</b> may be owned by a local police department and Network B <b>104</b> may be owned by the federal government. Another example, Network A <b>102</b> may be an APCO 25 voice network and Network B <b>104</b> may be an APCO 25 data network. Another example, Network A <b>102</b> may be an IP system and Network B <b>104</b> may be an APCO 25 voice or data network. In yet another example, Network A <b>102</b> may be a public cellular network and Network B <b>104</b> may be an APCO 25 voice or data network. Regardless of the type of network, as mentioned above, the two networks differ in at least one characteristic.
0020Further, examples of either Network A <b>102</b> or Network B <b>104</b> encompass radio frequency (RF) technologies, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Mutiplexing (OFDM), and the like, implemented in any currently available radio network, such as, for example, Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications Service (UMTS), Trans-European Trunked Radio service (TETRA), APCO Project 25 (as mentioned above), Personal Communication Service (PCS), Advanced Mobile Phone Service (AMPS) and the like. In such examples, the sites <b>116</b>, <b>118</b>, <b>120</b>, <b>122</b> may be termed base radios, base stations and/or transmitters. In the alternative, Network A or Network B may encompass other wireless technologies, such as those now known or later to be developed and including, but not limited to, infrared, Bluetooth, electric field, electromagnetic, and electrostatic transmissions. Further yet, examples of either Network A <b>102</b> or Network B <b>104</b> may support IP networks, where the IP network may be an 802.11 wireless local area network (WLAN), wherein the mobile devices <b>110</b>, <b>112</b>, <b>114</b>, and the sites <b>118</b>, <b>120</b> are configured to operate in accordance with the ANSI/IEEE (American National Standards Institute/Institute of Electrical and Electronics Engineers) 802.11 wireless LAN standards. Alternatively, packet data network, e.g. Network A <b>102</b>, may adhere to another ANSI/IEEE 802 wireless standard, such as 802.15.1, 802.15.3, 802.15.4, 802.16, 802.20, 802.22, and the like. The mention of ANSI/IEEE 802.11 is not to be construed as a limitation. In such an example, the sites <b>116</b>, <b>118</b>, <b>120</b>, <b>122</b> may be termed access points (APs) and/or transmitters.
0021Practitioners skilled in the art will appreciate that the RF communication system <b>100</b> may include various other communication devices not specifically shown in <figref idref="DRAWINGS">FIG. 1</figref>. For example, either Network A <b>102</b> or Network B <b>104</b> may comprise a link, such as, for example a T1 line or E1 digital carrier system that connects a site, e.g. site <b>116</b> to a public switched telephone network (PSTN) via a telephone gateway, a paging network or short message system via a paging gateway, and a facsimile machine or similar device via fax gateway or modem. In addition, either network <b>102</b>, <b>104</b> may be connected via a site, e.g. site <b>118</b>, to an underlying network that may be implemented, for instance, as a wired network or as a mesh network having fixed or mobile sites.
0022In any case, the communication between the sites <b>116</b>, <b>118</b>, <b>120</b>, <b>122</b> and the mobile devices <b>110</b>, <b>112</b>, <b>114</b>, <b>124</b>, <b>126</b> may comprise multiple RF channels such as pairs of frequency carriers, TDMA time slots, CDMA channels, and the like or may comprise a single RF channel with a single OFDM channel, and the like. Thus, the communications between the sites and the mobile devices takes place on the channel(s).
0023Referring to <figref idref="DRAWINGS">FIG. 2</figref>, shown is a flow chart for the process performed by a site, e.g. site <b>116</b>, that is in Network B <b>104</b> to be informed of sites that are in Network A <b>102</b>. In an exemplary embodiment, each site in Network B <b>104</b> maintains information of adjacent sites in Network A <b>102</b> (Block <b>202</b>). In a further embodiment, adjacent sites are those that are geographically close to the site. In one embodiment, each site in Network B <b>104</b> maintains information of adjacent sites in Network A by preprogramming and/or preconfiguration of the site in Network B <b>104</b>. For example, site <b>120</b> is geographically close to site <b>116</b>, so site <b>116</b> may be preconfigured with site <b>120</b>'s information. In an alternate embodiment, each site in Network B <b>104</b> may receive information of adjacent sites in Network A <b>102</b> from an adjacent site gateway <b>106</b>.
0024In any case, information relating to the adjacent sites in Network A <b>102</b> that each site in Network B <b>104</b> may maintain includes the site in Network A's <b>102</b> identification, location, and attributes where attributes is at least one of an access technology, bandwidth availability, and quality of service. In an exemplary embodiment, Network B is a channelized network and site <b>116</b> is a base station of the channelized network. Further, in such an example, Network A <b>102</b>is a packet data network and site <b>120</b> is an access point (AP) of the packet data network. In such an embodiment, site <b>116</b> maintains site <b>120</b>'s site name and/or site identifier, e.g. as is known to one or ordinary skill in the art, an SSID, geographic location, access technology, bandwidth availability, and Quality of Service (QoS) capability.
0025Knowing the adjacent site information, the site in Network B <b>104</b> broadcasts information about the sites in Network A <b>102</b> to mobile devices within coverage of the site in Network B <b>104</b> (Block <b>204</b>). In one embodiment, the site in Network B <b>104</b> sends the adjacent site information in a signaling message to the mobile device within coverage of the site in Network B <b>104</b>. In an exemplary embodiment, the signaling message is a proprietary message that is sent on a control channel where the signaling message adheres to an APCO 25 standard.
0026As the mobile device moves in Network B <b>104</b>, the mobile device may receive further signaling messages with adjacent site information that are unique to the site. For example, site <b>122</b> may broadcast different adjacent site information, such as information relating to a Network C (not shown) where a site in Network C is geographically close to site <b>122</b>.
0027In one embodiment, the sites in Network A <b>102</b> are mobile. Because the sites in Network A <b>102</b> can change position, it is advantageous to provide adjacent site information to mobile devices in Network B <b>104</b>, e.g. mobile device <b>124</b>. In such a case, an adjacent site information gateway <b>106</b> can be used to inform the mobile device <b>124</b> of the sites of Network A <b>102</b> that are physically near the mobile device in Network B <b>104</b>. Thus, when the mobile device in Network B <b>104</b> hands off from Network B <b>104</b> to a site in Network A <b>102</b>, it will have information of the adjacent sites in Network A <b>102</b> that are near to the mobile device.
0028The mobile site, e.g. site <b>120</b>, in Network A <b>102</b> updates the adjacent site information gateway <b>106</b> with its position. In one embodiment, updating the adjacent site information gateway <b>106</b> with position information occurs periodically based upon an elapsed time. In another embodiment, updating the adjacent site information gateway <b>106</b> with position information occurs whenever the mobile site, e.g. site <b>120</b>, has moved a fixed distance. For example, the site <b>120</b> may update the adjacent site information gateway <b>106</b> with its position every 5 miles. In yet another embodiment, updating the adjacent site information gateway <b>106</b> with position information occurs when the adjacent site information gateway <b>106</b> requests such an update. For example, the adjacent site information gateway <b>106</b> may send a signaling message, such as a broadcast message, requesting that all the mobile sites within the network provide the adjacent site information gateway <b>106</b> with position information.
0029Upon receiving the position information of the mobile site, the adjacent site information gateway <b>106</b> determines a list of sites (whether mobile or not) in Network A <b>102</b> that are near the site in Network B <b>104</b> and sends the list to the site in Network B <b>104</b> (Block <b>202</b>). In one embodiment, the mobile device in Network B <b>104</b> may receive updates to the list of sites that are near the mobile device whenever the site in Network A <b>102</b> updates the adjacent site information gateway with the site's position.
0030In one embodiment, the adjacent site information gateway <b>106</b> functions as an interface between Network A <b>102</b> and Network B <b>104</b> and maintains information of the sites in Network A <b>102</b> to transfer the information to the sites in Network B <b>104</b>. Such information includes site parameters where site parameters comprise information relating to RF channels supported by the site, system identification, geographical location of the site, the number of mobile devices supported by the site, the number of mobile devices capable of being supported by the site, the number of communications supported by the site, the bitrate capacity supported by the site, the current bandwidth utilization of the site, the Quality of Service (QoS) guarantees supported by the site, the ability of the site to support communication with a mobile device that is in motion, and the relative preference for this site to be part of a handoff. For example, the adjacent site information gateway <b>106</b> may have information of the location of site <b>118</b>, the capacity as measured by the number of mobile devices supported by the site <b>118</b>, the RF frequencies of the control and voice channels, etc.
0031From the information of the sites in Network A <b>102</b> and in Network B <b>104</b>, the adjacent site information gateway <b>106</b> determines a list of sites that are near the site in Network B <b>104</b> that are impacted by the movement of sites in Network A <b>102</b>. In one embodiment, the adjacent site information gateway determines a list of sites in Network A <b>102</b> that are near the sites in Network B <b>104</b> by calculating a distance between the sites in Network B <b>104</b> and each site in Network A <b>102</b> where a site is near if the distance is the smallest calculated number. In another embodiment, a site is near if it is closer than a threshold distance.
0032In any case, the adjacent site information gateway <b>106</b> sends a list of sites in Network A <b>102</b> to the sites in Network B <b>104</b>. In one embodiment, the list is sent directly to each site in Network B <b>104</b> and in a signaling message to the mobile devices associated with each site. In another embodiment, an updated list is sent to each mobile device whenever the site in Network B <b>104</b> receives an updated list from the adjacent site information gateway <b>106</b>. For example, if the adjacent site information gateway has received new position information from a site in Network A <b>102</b>, the adjacent site information gateway will send an updated list of sites to each site in Network B <b>104</b> where each site sends an updated list to each mobile device associated with the site.
0033Having received the list of adjacent sites in Network A <b>102</b> from the site, the mobile device, e.g. mobile device <b>124</b>, in Network B <b>104</b> can handoff to a site in Network A <b>102</b>. The mobile device may choose one site from the list of adjacent sites and determine a site in Network A <b>102</b> to handoff to. In one embodiment, as the mobile device moves, the mobile device may request a list of adjacent sites in the first network from a site in Network B <b>104</b> that the mobile device is affiliated with. In response to the request, the site in Network B <b>104</b> sends a list of adjacent sites in Network A <b>102</b> to the mobile device in Network B <b>104</b>. In such an embodiment, the request from the mobile device may be sent when the mobile device has moved a significant distance where significant distance means a distance greater than a threshold value.
0034It will be appreciated the adjacent site updates described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the adjacent site updates described herein. The non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power source circuits, and user input devices. As such, these functions may be interpreted as steps of a method to perform adjacent site updates. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
0035In the foregoing specification, the invention and its benefits and advantages have been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
Contents5
3 sheets
Sheet 1 Sheet 2 Sheet 3
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9113368B2 | Cited by | United States of America | Applicant |
| US9444651B2 | Cited by | United States of America | Applicant |
| US9609555B2 | Cited by | United States of America | Applicant |
| US8964767B2 | Cited by | United States of America | Applicant |
| US8830835B2 | Cited by | United States of America | Applicant |
| US10686663B2 | Cited by | United States of America | Applicant |
| US10931481B2 | Cited by | United States of America | Applicant |
| US9209998B2 | Cited by | United States of America | Applicant |
| US9112811B2 | Cited by | United States of America | Search report |
| US11743123B2 | Cited by | United States of America | Applicant |
| US2015257061A1 | Cited by | United States of America | Pre-grant |
| US2013058354A1 | Cited by | United States of America | Pre-grant |
| US10193708B2 | Cited by | United States of America | Applicant |
| US11641321B2 | Cited by | United States of America | Applicant |
| US9288081B2 | Cited by | United States of America | Applicant |
| US2011228687A1 | Cited by | United States of America | Pre-grant |
| US10038597B2 | Cited by | United States of America | Applicant |
| US9137052B2 | Cited by | United States of America | Applicant |
| US9277468B2 | Cited by | United States of America | Search report |
| US11804987B2 | Cited by | United States of America | Applicant |
| US10091028B2 | Cited by | United States of America | Applicant |
| US2002071404A1 | Cites | United States of America | Search report |
| US2004058679A1 | Cites | United States of America | Search report |
| US2005026617A1 | Cites | United States of America | Search report |
| US5577168A | Cites | United States of America | Search report |
| US6188904B1 | Cites | United States of America | Search report |
| US7058405B2 | Cites | United States of America | Search report |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 11543805 | United States of America | A | |
| US20050115438 | – | – | – |
53 transactions on the USPTO file
Allowed after 2 non-final rejections, 1 final rejection and 1 appeal.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Post Issue Communication - Certificate of CorrectionN423 | N423 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief FiledAP.B | AP.B | |
| Notice of Appeal FiledN/AP | N/AP | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| New or Additional Drawing FiledC614 | C614 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reference capture on IDSRCAP | RCAP | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Preliminary AmendmentA.PE | A.PE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Certificate of correctionCC | CC | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 07369852
- Publication, DOCDB
- 7369852
- Publication, EPODOC
- US7369852
- Application
- 11115438
- Application, DOCDB
- 11543805
- Application, EPODOC
- US20050115438
Titles
- English
- Methods for informing subscribers in a channelized network of adjacent sites
Patent term adjustment
- A delay
- +55 daysthe office missed an examination deadline
- Applicant delay
- −24 days
- Net adjustment
- 31 days
Classification
- CPC, 1
- H04W48/10
- IPC, 2
- H04Q7 20
- H04W48 10
- USPC, 11
- 455435100
- 370328000
- 370329000
- 370330000
- 370331000
- 370338000
- 455435200
- 455435300
- 455436000
- 455439000
- 455446000