Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
  • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/16—Discovering, processing access restriction or access information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
  • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration

Definitions

• This invention relates in general to messaging systems, and more specifically to a communication system in which portable messaging units register for service.
• messages are transmitted to portable messaging units carried by system subscribers.
• messages are provided to portable messaging units over a forward communication channel, and inbound messages, such as acknowledgments and registration requests, from the portable messaging units are transmitted over a reverse communication channel and processed by a radio frequency controller that controls operations of the communication system.
• a registration request is generally transmitted by a portable messaging unit to indicate its presence within a particular region, or zone, of the system so that messages can be provided to the portable messaging unit solely within that region.
• inbound registration requests are not always received by system receivers and forwarded to the radio frequency controller, usually because a relatively low power portable messaging unit is outside the range of the system receivers.
• registration is unsuccessful, the portable messaging unit may be unable to transmit inbound messages.
• messages intended for reception by the unregistered portable messaging unit often have to be transmitted in multiple zones since the location of the portable messaging unit cannot be pinpointed. Continuous transmission of registration requests until registration is achieved would enable the portable messaging unit to become registered as quickly as possible, thereby enabling transmission of inbound messages and efficient outbound message transmission.
• transmission of numerous registration requests from the portable messaging unit would also crowd the inbound channel and rapidly deplete the battery, which is undesirable in small portable messaging units in which battery capacity is already at a premium.
• FIG. 1 is a block diagram of a communication system including zones into which portable messaging units can roam according to the present invention.
• FIG. 2 is an electrical block diagram of a portable messaging unit for registering in the communication system of FIG. 1 according to the present invention.
• FIG. 3 is a flowchart illustrating an operation of an event detector included in the portable messaging unit of FIG. 2 according to the present invention.
• FIG. 1 is a block diagram of a radio communication system 100 that provides outbound communications, such as messages, to portable messaging units (PMUs) 130 over an outbound, or forward, communication channel.
• Inbound communications such as registration requests or message acknowledgments, can also be transmitted by the PMUs 130 over an inbound, or reverse, communication channel.
• the communication system 100 comprises different geographic regions of service referred to as zones 105, 110, 115, and each zone includes one or more transmitters 120 for transmitting the outbound messages.
• the zone also comprises one or more receivers 125 for receiving the inbound communications.
• a radio frequency controller (RFC) 135 is coupled to stationary system devices, e.g., the transmitters 120 and the receivers 125, in the different zones 105, 110, 115 for controlling operations of the communication system 100.
• Two-way PMUs 130 preferably are registered in the respective zones in which they are located. Once a particular PMU 130 has registered, messages intended for the PMU 130 can be transmitted solely within the associated zone, rather than throughout the entire system 100. Additionally, inbound messages received from the PMU 130 registered in the associated zone can be processed by the RFC 135. When, on the other hand, a PMU 130 is not registered in the zone in which it is located, inbound messages are not always recognized or processed. In some cases, inbound messages may not even be transmitted by an unregistered PMU 130. Furthermore, because the location of the unregistered PMU 130 cannot be verified, outbound messages for the PMU 130 are transmitted throughout the system 100, thereby resulting in inefficient use of system resources.
• the PMU 130 When the PMU 130 moves into a different zone, it receives a zone identifier indicative of the new zone, in response to which the PMU 130 transmits a conventional registration request to register in the new zone. When registration has been successful, the PMU 130 receives a registration acknowledgment indicating that the PMU 130 is registered within its current zone.
• the PMU's registration request can sometimes be missed by receivers 125 within the current zone, such as when the PMU 130 is out of range of the receivers 125, when the PMU 130 is in a fringe area, or when interference is present. In such a case, the PMU 130 will subsequently attempt to register at times indicated by a retry algorithm programmed into the PMU 130.
• the retry algorithm can, for instance, indicate that registration is to be attempted at fixed intervals, e.g., thirty- minute time periods, at variable intervals, e.g., once a minute for the first ten minutes and once every ten minutes thereafter, or according to any other computation that does not result in inordinate depletion of the battery powering the PMU 130.
• the PMU 130 monitors internal PMU operations and also attempts to register in response to the occurrence of specified registration events, such as reception of a ⁇ message over the outbound channel or reception of information that is to be transmitted by the PMU 130 over the inbound channel. Unsuccessful attempted registration in response to occurrence of a registration event preferably does not interfere with attempts made in accordance with the retry algorithm. According to the present invention, the PMU 130 will attempt to register at scheduled times, per the retry algorithm, and will also attempt to register when necessary, i.e., when a particular event occurs that makes registration desirable. For instance, attempting registration is desirable in response to reception of a message because the PMU 130 often transmits an acknowledgment of a received message.
• the PMU 130 can, for instance, be a pager or any other portable two-way radio device.
• the PMU 130 comprises a transceiver 205 for transmitting and receiving radio signals in a conventional manner and a processor 220 for processing the radio signals and for controlling operations of the PMU 130.
• the PMU 130 can additionally include a message memory 225 for storing received messages, an alert mechanism 215 for generating an alert to announce message reception, a display 210 for displaying information to a user, and controls 245 for receiving user inputs to operate or program the PMU 130.
• a data entry device could be included for entering information, such as programming information, into the PMU 130.
• a device memory 230 is included in the PMU 130 for storing information used in operating the PMU 130. Such information preferably comprises zone identifiers used by the processor 220 in a conventional manner to identify a current zone and to determine whether the PMU 130 is registered in the current zone.
• the device memory 230 preferably also stores registration status information conventionally set by the processor 220 and registration information in accordance with which registration requests are transmitted.
• Registration event information is stored in the device memory 230 to indicate one or more registration events that trigger the transmission of a registration request. Registration event information can be programmable by a service operator or by the user via the controls 245, another data entry device, or over the air.
• the PMU 130 also comprises a registration manager 235 for managing registration requests that are not linked to occurrences of registration events.
• the registration manager 235 can initiate a registration attempt for many reasons, such as in response to determining that the PMU 130 has entered a new zone or in response to reception of a "where are you" command from the system 100.
• the PMU 130 can, for example, determine that it has entered a new zone by determining that the zone identifier included in a received radio signal is not equivalent to the zone identifier associated with a zone in which the PMU 130 last registered. This information is preferably indicated by the stored registration status information.
• the registration manager 235 sets the registration status information to indicate that the PMU 130 is unregistered. Additionally, the registration manager 235 preferably keeps a log indicating times of registration attempts. Thereafter, the registration manager 235 attempts to register at times indicated by the stored retry algorithm for as long as the PMU 130 remains unregistered. As mentioned, the retry algorithm, which could be programmable via the controls 245, is preferably set to maximize the likelihood of successfully registering while, at the same time, avoiding undue depletion of the battery (not shown). Once the PMU 130 has successfully registered, the registration manager 235 changes the registration status information to indicate that the PMU 130 is registered and to indicate the current zone, such as by storing the zone identifier of the current zone.
• an event detector 240 is included in the PMU 130 for monitoring internal PMU operations to detecF an occurrence of a registration event.
• the event detector 240 initiates a registration attempt regardless of whether a time indicated by the retry algorithm has arrived.
• the registration manager 235 and the event detector 240 preferably comprise firmware stored in the device memory 230 and executed by the processor 220 during operation of the PMU 130.
• the retry algorithm can be stored as a part of the firmware used to implement the registration manager 235.
• the registration manager 235 and the event detector 240 can be implemented using hardware capable of performing equivalent operations, and the retry algorithm can be stored in a memory device, such as the device memory 230, in the form of an equation or formula that yields registration times.
• Use of the event detector 240 according to the present invention is advantageous because registration requests can be transmitted when necessary, as defined by programmed registration event information. Consequently, an unregistered PMU 130 will attempt registration at specified times, pursuant to the retry algorithm, and also when a registration event, such as message reception, occurs. Registration attempts are therefore managed in a way that prevents crowding of the inbound channel with repeated registration requests while ensuring that an attempt will be made in situations in which the PMU 130 needs to be registered for inbound communication, such as when the PMU 130 needs to transmit an acknowledgment of a received message or when the PMU 130 needs to send an inbound message to the RFC 135 or another PMU 130.
• the times at which the registration manager 235 initiates transmission of a registration request are set to avoid inordinate battery depletion, which could occur if continual registration attempts were made.
• use of the registration manager 235 alone could result in situations in which the PMU 130 moves into range of system receivers 125 (FIG. 1) very soon after an attempt to register has been unsuccessfully made.
• an in-range PMU 130 could operate in an unregistered mode for the entire remaining length of an interval or time period specified by the retry algorithm, even though the PMU 130 was capable of successfully registering and then sending inbound transmissions.
• FIG. 3 is a flowchart showing an operation of the event detector 240, which monitors operations internal to the PMU 130.
• the event detector 240 determines, in a conventional manner, whether the PMU 130 is already registered in the current zone, at step 320.
• message reception and message transmission are merely examples of registration events, and that occurrence of any other registration event, at step 315, also results in the event detector 240 determining, at step 320, whether the PMU 130 is registered in the current zone. Detection of occurrences of the registration events can be performed in numerous ways, as will be understood by one of ordinary skill in the art. For example, message reception could be detected by referencing the message memory 225 or by receiving an "incoming message" signal generated by the processor 220. Detection of information to be transmitted could be performed by monitoring user inputs received via the controls 245.
• the event detector 240 activates, at step 325, the registration manager 235 to initiate a registration attempt by conventionally transmitting a registration request.
• the communication system described above includes different zones into which a PMU can roam.
• the PMU attempts to register in that zone. Successful registration enables the PMU to send inbound communications that are processed by the system in a conventional manner. Registration is not always successful, though, because the relatively low-power transmissions from the PMU are not always received properly by system receivers in the zone.
• the PMU can, for instance, be out of range, in a fringe area, or in an area of high interference. In such a situation, the PMU can still operate in a one- way mode to receive the higher-power outbound transmissions over the forward channel.
• inbound communications from the PMU within a particular zone are not necessarily enabled until the PMU has registered within the zone. Therefore, registration requests are transmitted by the PMU in accordance with a programmable retry algorithm so that registration can be attempted at specified times without draining the battery too much.
• registration requests are also made in response to occurrences of registration events, regardless of whether it is time to register.
• Registration events are programmable and preferably include events that trigger actions requiring inbound communications. For instance, message reception will usually be a registration event because the PMU sends an inbound acknowledgment in response to reception of a message.
• user entry of information to be transmitted comprises a registration event since the information is sent by the PMU over the reverse channel for system processing. Other events, such as a simple user request, could also be set as registration events.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (3)

Publications (2)

Family

ID=25095115

Family Applications (1)

Country Status (2)

Citations (3)

Family Cites Families (4)

• 1997
  • 1997-12-01 WO PCT/US1997/021778 patent/WO1998028933A1/en not_active Application Discontinuation
  • 1997-12-01 EP EP97950722A patent/EP0950327A4/de not_active Withdrawn

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events