Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B5/00—Near-field transmission systems, e.g. inductive or capacitive transmission systems
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/18—Service support devices; Network management devices
  • H04W88/185—Selective call encoders for paging networks, e.g. paging centre devices
  • H04W88/187—Selective call encoders for paging networks, e.g. paging centre devices using digital or pulse address codes
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/022—Selective call receivers
  • H04W88/023—Selective call receivers with message or information receiving capability

Definitions

• the present invention relates to communications protocols.
• the present invention relates to a protocol particularly suited for effectively implementing feature rich voice paging.
• paging provides a mechanism by which one entity sends a message to another entity equipped with a wireless receiver (i.e., a pager).
• a wireless receiver i.e., a pager.
• the wireless nature of the pager allows its carrier to move freely in a predefined service area and still remain accessible.
• pagers were only capable of rudimentary beeping to indicate that the carrier should return a call (using a conventional telephone) to a certain number, or call a pager service provider to retrieve a voice mail message .
• a text messaging pager (often referred to as an alphanumeric pager) receives numerous individual alphanumeric characters that form a text message of limited length.
• the alphanumeric pager may provide potentially important information to its carrier immediately, rather than requiring the carrier to call in for a message.
• voice pagers are capable of receiving, much like an answering machine, actual voice messages for audio playback.
• the benefits of voice pagers are numerous, and allow their owner, for example, to store multiple messages, review messages, and recognize the voice (and emotional characteristics) of the caller. In the past, however (and due in part to their recent emergence), the functionality provided by voice pagers and their communications protocols has been somewhat limited.
• InfoTelecom provides the MobiDARC protocol (an extension of the DARC protocol) that is able to transmit digital voice messages.
• the MobiDARC protocol provides only a relatively slow transmission rate, 6.8 Kbps .
• a 9.7 Kbps rate is available using a non-interleaved code, the lack of interleaving dramatically decreases message and voice quality due to omnipresent fading effects.
• the amount of time required to transmit any message increases with decreasing transmission rate.
• address and message information is typically placed very close together and is not repeated.
• a pager that misses a (typically) short addressing portion misses messages altogether.
• the bandwidth used to transmit the message has been wasted, important messages are not received, and the system transmitter must more frequently retransmit messages.
• service subscribers paying for paging services are not likely to tolerate such unreliable reception.
• missed messages are more than a minor inconvenience. Because voice messages may be many seconds and many thousands of bits in length, the amount of system resources required to retransmit missed voice messages is quite significant. Furthermore, with such long messages, the amount of time between which messages can be repeated is often very lengthy. Thus, a missed message results in a significant delay until a (potentially emergency) message is received. Even though voice paging is poised to become a major market segment, previous protocols supporting voice paging have not provided enhanced message reception over that of simple alphanumeric pagers. User dissatisfaction, wasted bandwidth, and undelivered messages result.
• pager battery life An additional consideration of great importance is pager battery life. Longer battery life, of course, is desirable from a marketing standpoint, but also plays a role in the mechanical longevity of the pager, and the frequency at which battery backed up information in the pager is lost. All pagers, of course, must activate their reception circuitry to receive messages. The particular technique used by the pager to determine that it will receive a message has a profound impact on battery life. In the past, however, voice paging protocols required pagers to remain active for extended periods of time to determine whether they were to receive a message.
• Another object of the present invention is to provide a voice paging protocol that incorporates diversity transmitting techniques within a single frame.
• a still further object of the present invention is to provide a voice paging protocol that incorporates diversity transmitting techniques over multiple frames.
• Another object of the present invention is to provide a voice paging protocol that provides group messaging capabilities.
• a still further object of the present invention is to provide a voice paging protocol that accommodates roaming pagers .
• One preferred embodiment of the present voice paging protocol provides a method of transmitting information to a receiver using a selective call message.
• the selective call message includes an indicator signal indicative of at least one receiver and a data signal destined for the receiver.
• the indicator signal may be, for example, an alert signal (as small as a single bit) assigned to one or more pagers or an address corresponding to one or more pagers, or a combination of both alert and address information .
• the method first transmits the indicator signal a first time and delays for a predetermined time interval. Subsequently, the method transmits at least a portion of the first indicator signal a second time and a message signal for the receiver a first time. Thus, a portion of the indicator signal is repeated after a time interval to provide indicator signal time diversity before transmission of the actual message.
• the method may periodically transmit frames and transmit the indicator signal, for example, in a first frame, while repeating a portion of the indicator signal and message signal in a subsequent frame. As one example, the entirety of an alert and address indicator signal may be repeated in a subsequent frame.
• portion of the indicator signal corresponding to the address may be repeated yet again in the subsequent frame to provide three or more repetitions of an address across multiple frames.
• the present invention further provides a method of transmitting information to a receiver that, among other things, helps the receiver reduce power consumption.
• the method of transmitting information uses a selective call message including an indicator signal indicative of at least one receiver and a message signal destined for the receiver.
• the method proceeds by setting an alert signal indicative of a receiver and transmitting the alert signal. Additionally, an address corresponding to the receiver is set and transmitted, and subsequently, a message signal destined for the receiver is transmitted.
• the alert signal may, for example, be a single alert bit.
• the method may transmit additional messages to additional receivers by contemporaneously setting and transmitting additional alert signals, address signals, and message signals (which may be interleaved and pseudo- randomly distributed in a voice data section of a frame, for example) .
• Receiver groups (sets of pagers sharing common addresses) are also supported.
• the method may, for example, additionally set and transmit several additional alert bits that are indicative of a receivers in a receiver group.
• a single group message signal destined for each receiver in the receiver group is also transmitted.
• the method may set and transmit — o —
• Figure 1 illustrates one embodiment of an alert packet format.
• Figure 2 shows one example of a pointer packet format .
• Figure 3 illustrates one example of housekeeping packets .
• Figure 4 depicts one embodiment of a protocol frame structure.
• Figure 5 illustrates one example of the format of a stream header.
• Figure 6 shows one example of a receiver decision tree that determines the queries and resulting actions that a receiver may perform in receiving messages according to the current paging protocol .
• Figure 7 illustrates one high level flow diagram of transmission according to the present protocol.
• Figure 8 shows one high level flow diagram of reception according to the present protocol.
• Figure 9 depicts a high level block diagram of transmitter and receiver hardware that may be used to implement the present voice paging protocol.
• the present discussion proceeds in several steps. First, the present application presents general background information useful for understanding the protocol. Next, the present discussion turns to several of the structural aspects of the protocol. After the structural aspects, the present application then presents several operational characteristics of the protocol.
• the present protocol is built from a number of individual pieces. At the highest level, the protocol uses a repetitive frame structure, with each frame generally following the same format as the previous frame. Each frame, in turn, is constructed from packets of information. As an example, a frame may include 2922 packets. Packets, in turn, are a collection of predetermined numbers of symbols. As an example, each packet may include 128 symbols. Symbols, in turn, are formed using modulation of a carrier frequency. The modulation, for example, may be Phase Shift Keying at 4 or 8 levels (QPSK and 8-PSK, respectively) .
• the above examples are not presented in a limiting sense, but only provide one specific example of how the protocol may be structured.
• the packets discussed in more detail below, group symbols into packet types, including Alert packets, Pointer packets, and Housekeeping packets. Additionally, data is generally transmitted in a separate voice data section using voice data packets.
• One environment in which the present protocol may be used effectively is that of the standard FM radio broadcasting infrastructure.
• the FM radio infrastructure provides numerous 200 KHz spaced channels over the 87.5 to 108 MHz frequency range.
• the baseband FM signal itself, however, uses 100 KHz of bandwidth in which approximately 53 KHz is used for stereo audio information and the remaining 47 KHz of which is typically divided into two Subsidiary Communications Authorization (SCA) channels centered at approximately 67 KHz and 92 KHz.
• SCA Subsidiary Communications Authorization
• FM broadcasting infrastructure provides, in conjunction with the present protocol, an existing, worldwide transport mechanism for information
• the present protocol may be applied to virtually any other available frequency band or communications infrastructure.
• the protocol below is described particularly with reference to a paging system, the protocol is not limited to any particular use.
• the packets from which frames are partially composed preferably include Alert packets, Pointer packets, and Housekeeping packets.
• the format 100 includes a pilot mark 102, a packet sequence number 104, and a system ID 106. Additionally, the format 100 includes an alert bit field 108, Cyclic Redundancy Check (CRC) field 110, and a flush field 112.
• CRC Cyclic Redundancy Check
• the pilot mark 102 is formed from four symbols of Binary Phase Shift Keying (BPSK) modulated carrier.
• BPSK Binary Phase Shift Keying
• the sequence of symbols in the pilot mark 102 form a predetermined sequence of phase changes used by pagers for clock and packet synchronization.
• the transmitting station and the receiving pagers establish, beforehand, the pilot mark 102 to be transmitted (and therefore to synchronize to during reception) .
• a pilot mark is inserted every 128 symbols to present a consistent synchronization reference to receiving pagers.
• the pilot marks in the pointer packet format 100 are not technically integral parts of the pointer packet, but simply reappear every 128 symbols.
• the packet sequence number 104 is formed, like the pilot mark 102, from four symbols of modulated carrier.
• the packet sequence number 104 is preferably QPSK modulated resulting in 8 bits of information present in the packet sequence number 104. Switching to QPSK modulation aids in the synchronization process noted above with respect to the pilot mark (by providing four symbols, each which better withstands a given amount of noise than the more closely spaced eight symbols of 8- PSK) .
• the packet sequence number 104 indicates the position and type of the packet with which it is associated. As will be described in more detail below, the alert, pointer, and housekeeping packets form a 202 packet (in one embodiment) short message section in a frame.
• Each packet is numbered sequentially from 0 to 201 using the packet sequence number fields.
• the first 80 alert packets are numbered 0-79, the following 10 pointer packets 80-89, and so on.
• a receiver pager may determine, using the packet sequence numbers, the type of packet currently being received and its position within the frame .
• the system ID 106 is formed from 6 symbols of 8-PSK modulated carrier.
• the system ID 106 thus carries 18 bits of raw data.
• the system ID (like the alert bit field 108, CRC field 110, and flush field 112 discussed below) are convolutionally coded, preferably, at a rate of 2/3.
• the system ID 106 therefore, includes 12 bits that actually represent the system ID (i.e., there are 4096 system IDs) .
• the present protocol may use the system ID to designate particular FM stations.
• each station uses a different system ID, and each pager is assigned to a particular station.
• the system ID therefore, may be considered part of the pager's address. It is noted, however, that a single system ID may be shared among several FM stations. In particular, in areas with significant interference, (major cities, for example) , several FM stations may share the same system ID and transmit duplicate sets of frames on different frequencies to provide a pager with at least one alternate FM station for reception.
• the alert bit field 108 as shown in Figure 1, extends over 103 symbols of 8-PSK modulated carrier. After 2/3 rate coding, the alert bit field 108 provides 206 bits of information.
• Each pager supported by a service provider assigns the pager at least one bit in an alert bit field (of which many are provided in the overall frame structure described below) . If a particular alert bit is set, a message will be placed in one of the voice data sections that follow in the present or next frame, thereby providing an indicator signal to the receiver that a message is forthcoming.
• an alert bit field of which many are provided in the overall frame structure described below
• the alert bits may be used as either unique bits or shared bits.
• Unique bits identify only a single pager.
• Shared bits designate more than a single pager, and may, for example, be used for roamers and system expansion. The use of the alert bits in both capacities is described in more detail below.
• the CRC field 110 is formed from 8 symbols of 8-PSK modulated carrier.
• the CRC field, after 2/3 rate encoding thus represents 16 bits of CRC information.
• the CRC in the CRC field 110 may be computed, for example, over the system ID 106, the alert bit field 108, and the CRC field 110 itself.
• the flush field 112 is formed from 3 symbols of 8-PSK modulated carrier and 2/3 rate coded. The flush field 112 thus provides 6 bits which may be used to reset a convolutional decoder to a known state, in preparation for the next packet.
• the pointer packet format 200 includes a pilot mark 206, a packet sequence number 208, and a system ID 210. Further included is a roaming flag 212, a message pointer field 214, CRC field 216, and a flush field 218.
• the pilot mark 206, packet sequence number 208, system ID 210, CRC field 216, and flush field 218 are formed and function substantially as described above with respect to the identical fields in the alert packet format 100.
• the CRC field 216 preferably computes a CRC over the system ID 210, roaming flag 212, message pointer field 214, and the CRC field 216 itself.
• the roaming flag 212 is a single bit that indicates the type of pointers present in the message pointer field 214. As an example, the roaming flag 212, when 0, may indicate that short address pointers 202 are present in the message pointer field 214. When 1, the roaming flag 212 may indicate that long address pointers 204 are present in the message pointer field 214.
• the message pointer field 214 generally contains pointers including address information that allow a pager to determine when a message is being sent to the pager and where to find the message in the voice data section to follow. The pointers thus provide an indicator signal to the pager that a message is forthcoming. In one embodiment, the message pointer field contains 205 bits of actual (before 2/3 rate coding) pointer information.
• the short address pointer 202 includes a first reserved bit 220, a second reserved bit 222, a stream ID 224, a reserved field 226, and a short address 228.
• the reserved bits 220, 222 and the reserved field 226 provide room for future expansion of the present protocol and therefore have no specific function.
• the stream ID 224 in one embodiment of the present protocol, is three bits and determines one of eight unique streams . As will be explained in more detail below, messages are assigned to one of eight streams for transmission. As an initial step in reception, the pager decodes the stream ID 224 and retrieves its message from the appropriate stream.
• the short address 228 contains an address assigned to a particular pager (e.g., a "home" address assigned to the pager in its assigned service area) .
• the short address 228 may be 16 bits in length, thus identifying one of 65,536 pagers or groups. In most instances, a pager will respond to at least one unique address assigned to it.
• the short address may be 16 bits in length, thus identifying one of 65,536 pagers or groups. In most instances, a pager will respond to at least one unique address assigned to it.
• a group address may be allocated to each pager in a set of pagers for a local sales team.
• a message may be sent to the sales team group address.
• a single message may thereby update all the pagers in the sales group.
• An additional use for the group address includes a reserved broadcast address, used to send a message to all pagers.
• a programming address may be used to send digital programming data to a subset of pagers (for example to update the protocol software itself) .
• the group address is placed at the end of any pointers for individual pagers that may be present in the message pointer field 214.
• Another example of a pointer is the long address pointer 204.
• the long address pointer like the short address pointer includes a first reserved bit 230, a second reserved bit 232, a stream ID 234, a reserved field 236, and a long address 238.
• the reserved bits 230, 232, reserved field 236, and the stream ID 234 function as described above with respect to the short address pointer 202.
• the long address 238 typically includes additional information over that provided by the short address 228.
• the long address 238 may support roaming pagers by using a 12-bit system ID concatenated with a 16-bit home address.
• a message transmitted to a roaming user therefore typically involves setting the roaming flag 212, and providing additional addressing information (i.e., a long address 238) to select a pager according to its home system ID and its home address) .
• a roaming pager which uses the same alert bit (and even the same "home" address) as a pager at home in a particular system area may distinguish the message destination by examining the complete long address 238.
• FIG. 3 that figure shows one example of two housekeeping packets 300.
• a first housekeeping packet 302 and a second housekeeping packet 304 are illustrated.
• housekeeping information is distributed over two packets (256 symbols).
• packet sequence number fields 314, 316 and system ID fields 318, 320 Further included are packet sequence number fields 314, 316 and system ID fields 318, 320.
• the pilot marks 306, 308, as noted above are present due to their insertion, every 128 symbols, into the transmitted information stream.
• the system ID fields 318, 320 and flush bits 312 operate as described above with respect to the pointer packets and alert packets .
• the CRC field 310 is computed over all the bits in both housekeeping packets 300, except for the two packet sequence number fields 314 and 316.
• the pilot marks 306 and 308 are not used to convey information in bit form and are also excluded from the CRC computation in the housekeeping packets 300.
• two housekeeping packets are placed at the end of a 202 packet section in a frame.
• the packet sequence numbers 314 and 316 may represent the numbers 200 and 201 (i.e., packets sequence numbers range from 0-201) .
• the housekeeping packets 300 span 256 symbols. Nineteen symbols are used for the pilot marks 306 and 308, CRC field 310, and the flush bits 312. Twenty symbols are used for the packet sequence number fields 314 and 316 and system ID fields 318 and 320. The remaining 217 symbols (434 bits at rate 2/3 8-PSK coding) are used for the actual housekeeping information .
• the housekeeping information may include any type of information generally useful to the receiving pagers.
• the housekeeping information may include 32 bits of system transmitter time information, 16 bits of system transmitter date information, and 16 bits of information representing the current system frequency.
• Additional examples include a system channel list (formatted, for example, as eight 16-bit channel IDs) , a roaming channel list formatted in the same or different fashion, and an 8-bit protocol system revision.
• the examples provided above, and particularly the number of bits used to implement the examples may, of course, vary considerable from implementation to implementation. Of particular interest are the system channel list, roaming channel list, and the current system frequency.
• the pager may use the digital information to tune directly, precisely, and rapidly to the correct frequency. In other words, the pager need not execute an inefficient frequency sweep to find available channels.
• the system channel list may be used to inform the pager of the possible redundant frequencies over which its messages will be transmitted.
• the pager may switch between channels identified in the system channel list for best reception.
• the roaming channel list provides the pager with an indication of which local radio channels support roaming.
• Figure 4 that figure illustrates one way in which the packet types described above may be combined with voice data sections to form frames 400.
• Figure 4 in particular, breaks down the frame 402 into its component pieces shown in the expanded frame 404.
• the expanded frame 404 includes a short message section 406 and a voice data section 408.
• the frame 402 includes 2922 packets, of which 202 form the short message section 406 and 2720 of which form the voice data section 408.
• the short message section 406 generally indicates a section of the frame that includes alerts, pointers, and housekeeping information (as opposed to actual message data) .
• the expanded short message section 410 illustrates a preferred arrangement of the short message section 406, including the alert packets, pointer packets, and housekeeping packets described above.
• the expanded short message section 410 indicates that an alert N section 412 is followed by a pointers N section 414, followed by an alert N+l section 416.
• a pointers N+l section 418, a duplicate pointers N section 420, and a housekeeping section 422 follows the alert N+l section 416.
• the duplicate pointers N section 420 is so named because it typically provides a copy of the pointers N section 414.
• the alert N section 412 is formed from 80 alert packets 100 which contain alert bits corresponding to pagers with messages in the voice data section 408.
• the pointer N section 414 is formed from 10 pointer packets 200 which provide address information for pagers receiving message in the voice data section 408.
• the housekeeping section 422 is formed from the housekeeping packets 300.
• the duplicate pointers N section 420 repeats the content of the pointers N section 414, thereby providing time diversity in the transmission of the pointers. Furthermore, the alerts N+l section 416 and pointers N+l section 418 provide advance alerting and pointer information for messages transmitted in the next frame (frame 424). Furthermore, the pointers N+l section 418 is typically 20 packets in length, including 10 packets of pointer information and 10 packets of data information, for example. The pointers N+l section may thereby provide a combined address and data message useful for sending short pieces of data, or long pieces of data over multiple frames. The preferred format of the short message section 404 provides a pager with numerous chances to recognize that it is to receive a page.
• the pager misses the advance alerting information provided by the alerts N+l section 416 in the frame prior to the one in which the message is sent (the "message frame"), it still may detect the alerting information provided by the alerts N section 412 in the message frame. Similarly, if the pager misses all of its alerts, it may still examine the advance pointer information provided by the pointers N+l section 416 during the prior frame and the two sets of message pointer information provided by the pointer N section and the duplicate pointers N section in the message frame to find its address. If the pager recognizes its address from pointer information, it may then prepare itself for reception of the appropriate stream.
• the pager may then check the pointers to determine if its particular address (as opposed to that of a roamer, for instance) is actually present.
• the multiple time diversity thus provided by the present protocol enhances the ability of the pagers to correctly receive every message sent to them, while reducing power consumption, and is further discussed in more detail below.
• the voice data section 408 is formed from packets that are parts of larger data structures.
• the voice data section 408 is divided into 8 streams of data each comprising 340 packets.
• Each stream is convolutionally coded and interleaved over its entire length (which may include multiple messages, one or more of which may be destined for a single pager) .
• sets of four contiguous packets ("pickets") of data from each stream are distributed throughout the voice data section in a deterministically random manner to form the stream.
• the pager and system transmitter both generate the same pseudo-random sequence identifying the position of the pickets.
• the pager retrieves each of the pickets for a given stream distributed among the voice data section before it reassembles, de- interleaves, and decodes a complete stream. Once the complete stream is decoded, the pager may then extract its particular message from the stream.
• the stream header 500 includes a stream ID 502 and a message count 504.
• the stream ID (which may be, for example, 8 bits) identifies the number of the stream, while the message count 504 identifies the number of messages in the stream itself.
• Each message may be terminated with a multi-bit flush field to reset a convolutional decoder to a known state.
• the stream header 500 For each message in a stream, the stream header 500 provides a message header including a long address 506 (28 bits), a time field 508 (12 bits), a data type field 510 (8 bits) an extended data type field 512 (16 bits), a start location field 514 (16 bits), a length field 516 (16 bits), and a fragment field 518 (8 bits). Also provided for each message is a CRC field 520 (16 bits) . A final CRC field 522 (16 bits) that covers all the preceding message headers and a Flush field 524 (6 bits) are provided at the end of all of the message headers.
• the time field 508 provides the time at which the current message was left for the pager at the service provider, and the data type fields 510 and 512 inform the pager as to the type of data included in the voice data section 408.
• the data type fields 510 and 512 may indicate digitized voice data, digital programming data, advertising, emergency alert information, weather information, stock data, or any other type of data that the system transmitter chooses to send to the pager. Any data, however, and preferably the stream header, may be convolutionally coded at a 1/3 rate (for example, by bit doubling the input bit stream to a convolutional coder) to provide enhanced error protection and correction capabilities .
• the start location field 514 and length field 516 provide the start location and length of the message in the stream for the pager identified by the long address field 506, preferably in units of words (16 bits) .
• the start location field 514 (and stream ID) are two examples of message location information that allow a receiver to determine where its message signal is in the voice data section of a frame. It is further noted, however, that the receiver may also need to collect the pickets or segments of the stream that have been (deterministically) randomly spread through the voice data section.
• the fragment field 518 may be used to indicate the number of frames over which the message for the pager is spread.
• the 8-bit fragment field 518 may use four bits to indicate the total number of frames used to transmit the message, and another four bits to indicate the current frame (fragment) number of the message.
• the stream header 500 preferably includes a terminating CRC field and flush field, similar to those illustrated in the packet types described above.
• the data in the each of the packets is interleaved over the same packet.
• the alert packet, pointer packet, housekeeping packets, and stream header are not limited to the specific implementations described above. Rather, each of the individual fields in each packet or header may be tuned to the application for which the protocol is used. The examples cited above work particularly well in an FM voice paging system and a summary of the relevant parameters may be found in Table 1.
• the protocol structure established above supports a wide range of capabilities. The discussion below proceeds with respect to basic paging, group paging, and roaming. The protocol is not limited to these capabilities, however, nor to any particular environment in which they are used.
• a pager is assigned at least one address that designates the pager as a receiver for a particular message.
• the address may, for example, be a "home" address, group address, or roamer address.
• the pager is assigned an alert bit.
• each SCA band in each FM frequency may be assigned a system ID and carry the protocol structure identified above. An alert bit in such a system thus associates the pager with a particular SCA band of a particular FM frequency.
• a pager may be associated with the same alert bit in a number of different SCA bands and FM frequencies to provide robust reception in a noisy environment.
• the system infrastructure accepts, digitizes, compresses, and stores voice messages left for delivery to a pager.
• voice data may be compressed with a Linear Predictive Coder (LPC) , Residual Excited Linear Predictive Coding (RELP) , Vector Sum Excited Linear Predictive Coding (VSELP) , and the like.
• LPC Linear Predictive Coder
• RELP Residual Excited Linear Predictive Coding
• VSELP Vector Sum Excited Linear Predictive Coding
• Data already in digital form may optionally be compressed and stored for delivery.
• the system transmitter retrieves messages from storage and transmits the messages to the appropriate pager.
• the system transmitter stores numerous messages and packs messages in the frame to minimize slack space (i.e., space in which no message will fit) .
• the system transmitter sets the appropriate alert bit corresponding to the pager, places the pager address in a pointer, assigns the message to a stream, fills in the stream header fields as described above, and sends the message with the appropriate coding and interleaving disclosed above with respect to the message streams.
• Alert bits generally, alert portions
• addresses generally, address portions
• the present protocol may be used, as described in more detail below, to send universal pages. That is, the present protocol supports sending a message signal to the complete set of pagers (i.e., every registered, active pager) supported by the system. In most instances, however, the system transmitter sends message signals to a subset of pagers smaller in number than the complete set of pagers supported by the system.
• the subset of pagers may by a single pager, for example, or may include several individual pagers and pager groups.
• the present discussion proceeds under the assumption that a message will be transmitted for a pager in the next frame 424.
• the system transmitter gives advance warning to the pager by setting the pager's assigned alert bit in the alert N+l field 416, and adding the pager's address and message information to the pointers N+l field 418.
• the pager recognizes its alert bit or address in the frame 402, it need not waste power searching for an alert bit or address in the next frame 424.
• a null address is defined and is used in a pointer field to indicate that no further pager addresses will follow.
• a pager that decodes the null address may save power by disabling its reception circuitry for the remaining portion of the present pointer field under examination .
• the pager then assembles the appropriate stream in the voice data section by gathering and ordering all of the pickets comprising the stream.
• the pager then de-interleaves and decodes the message stream in its entirety. Subsequently, the pager examines the stream header ( Figure 5) to locate the start of its message and the message length.
• the pager once it has recovered the message, may then update its internal list of successfully received messages according to the message number in the pointer.
• a pager need only look for its alert bit or address in a pointer to determine whether it will receive a message in the current or next frame.
• the pager may save substantial amounts of power by only activating its reception circuitry to receive a single alert packet and examine, typically, a single bit in the alert packet.
• the pager's alert bit can deactivate its reception circuitry for the entire voice data section 408, or perform a check for its address in the pointers N+l and pointers N fields. Thus, for example, if the pager could not decode the alert bits due to interference, the pager may still attempt to decode pointer fields in search of its address.
• the pager When the pager matches its predetermined alert bit location with a transmitted alert bit (one example of a selection criteria) , it may continue with active reception to examine the pointers N field 414 and optionally pointers N field 422 (if the pager recognized its alert bit set in the alerts N section 412) as well as the pointers N+l field 418 (if the pager recognized its alert bit set in the alerts N+l section 416) . Note that due to the time diversity of the pointer and alert information (the indicator signals), the pager has numerous chances to determine that the system transmitter is sending the pager a message in the current frame (e.g. frame 402) or next frame (e.g., frame 424). Again, as soon as the pager matches its address (another type of selection criteria) in any of the pointer sections, it may discontinue searching the remainder of the current pointer section or subsequent pointer sections.
• Flexibility in selection criteria allows a pager three opportunities to determine that the system transmitter is sending a message to the pager in the current frame.
• the pager may examine the contents of the alerts N section 412 for its alert bit, the pointers N section 414 for its address, or the duplicate pointers N section 420, again for its address. Finding its alert bit or address indicates that the current frame includes a message for the pager.
• the pager has two opportunities to determine that the system transmitter will send the pager a message in the next frame by examining the alerts N+l field 416 for its alert bit or the pointers N+l field 418 for its address. Finding its alert bit or address indicates that the next frame includes a message for the pager (and therefore that the pager need not search the short message section at all in the next frame) .
• the pager may determine that it has or has not matched its selection criteria. In such cases, the pager may inhibit reception of any repeated indicator signals (as the repeated indicator signals contain information the pager has already decoded) . If, however, the CRC check indicates that some bits have uncorrectable errors (i.e., they are indeterminate) , the pager may enable reception of any repeated indicator signals to have another opportunity to recognize that it will receive a message.
• uncorrectable errors in an alert bit may be overcome by examining repeated alert bits (e.g., alerts N section 412), and complete loss of alert bits may be overcome by examining one or more pointer sections, as necessary.
• the pager may then deactivate its reception circuitry (i.e., the pager need not examine other pointer sections after it has found its pointer once) . Because, as noted above, the streams in the voice data section 408 are interleaved in a deterministically random manner, the pager may proceed to receive the appropriate stream by activating its reception circuitry only during the times corresponding to the particular stream transmission in the voice data section 408.
• Group paging may be accomplished in a number of ways, three of which are addressed in this section.
• the system transmitter may set individual alert bits in alert packets and addresses in pointer packets to cover each pager to which a message will be sent.
• each pager recognizes its alert bit and its individual address and each pager proceeds to retrieve the same message from the voice data section of the appropriate frame.
• the system transmitter may set the alerts and addresses as noted above, but transmit individual copies of the message for each pager.
• a second implementation of group paging may be used, for example, for larger and relatively permanent receiver groups. The second implementation assigns at least one additional address to pagers in the group.
• each pager in a set of pagers for a sales team may include a unique address for individual messages and a group address for messages directed to the entire sales team.
• the system transmitter sets multiple alert bits corresponding to each pager in the sales group, but only provides the single group address in the pointer fields. Each pager therefore knows that a message is arriving, and that the message corresponds to the sales group address assigned to the pager.
• group paging is universal paging.
• the system transmitter sets a predefined universal address in the pointer fields, and optionally sets all of, or a subset of, the alert bits in the alert packets.
• the universal address is recognized by every pager. Universal addressing, therefore, allows the system transmitter to broadcast emergency information, programming information (e.g., system protocol software updates), and the like to every pager.
• programming information e.g., system protocol software updates
• individual and small group addresses are placed at the beginning of the pointer packet, while large group or universal addresses are placed at the end. Pagers thereby receive individual messages in the same frame as messages for large groups without lengthy address lists.
• group paging provides the capability for small group, large group, and universal addressing in its group paging framework.
• groups may be defined according to virtually any criteria.
• subscription services e.g., stock quotes, weather updates, news services, and the like
• the system transmitter may then transmit to the pager a new group address to which the pager should respond and that corresponds to address used to transmit the subscription service information.
• the system transmitter sends the pager a command to delete the subscription service address from its list of responsive addresses .
• Subscription information is transmitted in the same fashion as normal paging message data .
• the present protocol allows pagers to roam without losing messages by using the long address pointers 204.
• the carrier may, for example, specifically setup the forwarding of messages from the home area to the roaming area. For instance, when in the roaming area, the pager may examine the available frequencies, including those found in the system channel list and roaming channel list to find an available channel. The pager may then display the preferred channel (based on signal strength or other criteria) to the user. Subsequently, the carrier may call the system dispatch center in the home area and report (to a live operator, via a touchtone phone, or by tones generated by the pager) the preferred channel and the roaming area system ID.
• the roaming pager may return to its home area without prior notification to the system dispatch center.
• the dispatch center may decide to transmit pages either in the home area or in the roaming area, or both, according, for example, to system loading considerations.
• the user cancels the roaming at the system dispatch center soon after returning to the home area.
• the system transmitter uses the long address pointers 204.
• the roaming flag 212 in the pointer packet format 200 is set to indicate that long address pointers follow.
• the long address pointer 204 provides extended address information used by the pager to resolve the true message destination.
• the long address field 238 provides, in addition to the pager's address, a multi-bit home system ID for the roaming pager (or in general, an extended address) .
• a roaming pager may then easily distinguish itself using the complete system ID and address.
• the pager address may be mapped into one bit in a set of reserved roaming alert bits in the alert packet format 100, for example.
• a modulo function applied against the pager address may map the address into a predefined subset of roaming alert bits. This technique is described below with reference to shared alerts.
• the present protocol provides message reception for the roaming pager without conflict between existing home pagers .
• the short message section 406 provides 16,160 alert bits for each frame (80 packets, each with 202 alerts). Approximately 12,000 of these may be reserved, for example, for home pagers and another 4000 for roaming pagers (allowing a modulo 4000 function to determine which alert bit a roaming pager will use) . If a given system requires more than 12,000 pagers, then alert bits may be shared among pagers. In other words, two or more pagers may use the same alert bit. A particular pager may then determine whether a message is destined for it by examining the address fields in the short address pointers 202 and long address pointers 206, for example. Thus, even though alerts are shared, each pager may distinguish message destination by address.
• the modulo function may map two roamers onto the same alert bit .
• the two roamers similarly distinguish the intended recipient by using the addresses to which they are programmed to respond, compared with the address information in the long address pointers 206.
• the pager may allow itself to receive only those messages transmitted by its home system transmitter or a roaming system transmitter for a system in which the pager knows it is registered.
• Figure 6 that figure illustrates a receiver decision tree 600 that provides a preferred set of queries and actions performed by a receiver receiving communications formatted according to the present protocol.
• the discussion of Figure 6 is supported by the frame format shown in Figure 4.
• the "early alert” of Figure 6 corresponds to the Alerts N+l section 416
• the "early pointer” of Figure 6 corresponds to the Pointers N+l section 418 (in particular, the first 10 (non-reserved) packets).
• the "current alert” of Figure 6 corresponds to an Alerts N section in the frame N+l 424 (i.e., the current frame which includes the actual message)
• the "current pointer” corresponds to Pointers N section in the frame N+l 424
• the "last chance pointer” corresponds to the duplicate Pointers N section in frame N+l 424.
• the "data stream” refers to a voice data section 408 in the frame N+l 424.
• a pager may accurately determine whether certain conditions are matched (a true result) or not matched (a false result) .
• a pager may begin at PROCESS point 602 at which the pager determines whether its alert bit is set in the early alert section. If the pager determines that its alert bit is set, processing proceeds under the True branch 604 (labeled "Alert” in Figure 6) . If the pager determines that its alert bit is not set, processing proceeds under the False branch 606 (labeled "No Alert"), while in the indeterminate case, processing proceeds under indeterminate branch 608 (labeled "Indeterminate"). Starting first with the False branch 606, the pager has determined that it will not receive a message in the frame N+l 424. The pager, therefore, may skip examination, as shown in Figure 6, of the early pointer, current alert, current pointer, and last chance pointer. The pager thus performs no processing ("SKIP”) of the voice data section of frame N+l 424.
• SKIP no
• every frame includes early alerts and pointers for the subsequent frame.
• the repetition indicator 610 illustrates the point in time, according the frame format of Figure 4, in which the next set of early alerts and pointers occur.
• a completely new branching structure begins with the examination of an early pointer.
• the pager determines, at PROCESS point 612, whether a match exists in the early pointer (e.g., a short address or long address corresponding to the pager itself or a pager group) . If a match exists, the pager proceeds through True branch 614 (labeled "Pointer"), skipping examination (i.e., the pager need not waste power receiving) of the current alert, current pointer, and last chance pointer, to process its data stream in the voice data section 408 of the frame N+l 424. Similarly, if the pager recognizes that the correct address is not present in the early pointer, the pager may assume that its alert is being shared, for example, and that the message is destined for another pager.
• a match exists in the early pointer e.g., a short address or long address corresponding to the pager itself or a pager group. If a match exists, the pager proceeds through True branch 614 (labeled "Pointer"), skipping examination (i.e., the page
• the pager determines that uncorrectable errors exist in its decoding of the current pointer, the pager proceeds through the Indeterminate branch 622.
• the present protocol provides yet another ' chance, in the frame N+l 424, for the pager to find its pointer information in a duplicate pointers section (discussed above with reference to duplicate pointers N section
• the pager If the pager successfully finds its pointer, it may then process the stream, otherwise, the pager does no processing of the stream. It is possible, of course, that the frame may include many more duplicate indicator signals (the tradeoff being between diversity capability and available message bandwidth) , each of which may be examiner by the pager.
• the pager proceeds by enabling its receiver and examining the current alert at PROCESS point 624. While Figure 6 shows that the current alert is next examined, it is noted that the pager may first examine the early pointers in an attempt to match its address. Continuing from decision point 624, if the pager determines that its alert is not set, it skips the current pointer and last chance pointer and performs no stream processing.
• the pager determines whether the pager matches its alert, it proceeds under the True branch 626.
• the pager evaluates PROCESS point 628 under the same considerations discussed above with respect to decision point 620.
• the remaining alternative is illustrated in the Indeterminate branch 630.
• the pager may, for example, skip the current pointer section and proceed to examine the last chance pointer at the PROCESS point 632. While Figure 6 shows that the last chance pointer is next examined, it is noted that the pager may, as an alternative, examine the current pointers in an attempt to match its address. Assuming, however, that the pager proceeds with the last chance pointer, the pager reaches the decision point 632.
• the pager if it successfully matches one of the pointers in the last chance pointer, proceeds to process the appropriate data stream (as indicated in the pointer) . Otherwise, the pager performs no stream processing, either because it found no match in the last chance pointer, or because it could not decode the last chance pointer.
• FIG 7 that figure illustrates a high level flow diagram 700 summarizing transmission of information over a first frame 702 and a second frame 704 according to the protocol discussed above.
• the diagram 700 includes a current indicator step 706, an advance indicator step 708, and duplicate pointer step 710. Also included is an housekeeping step 712, and a message preparation step 714.
• the streams bearing the messages are interleaved at step 716 and transmitted at step 718.
• Each of the steps 706-718 occurs during a first frame (e.g., frame N 402) .
• a corresponding set of steps 720-732 occurs in a subsequent frame (e.g., frame N+l 424).
• the system transmitter prepares and transmits an indicator signal, generally including alerts (e.g., alerts N 412), pointers (e.g., pointers N 414), or both in a current frame (e.g., frame N 402) .
• alerts e.g., alerts N 412
• pointers e.g., pointers N 41
• additional alerts and pointers may be set as necessary to send messages to group receivers.
• additional alert bits or pointers may be set for every receiver in a particular receiver group.
• an indicator signal including alerts (e.g., alerts N+l 416) or pointers (e.g., pointers N+l 418) bearing information about the next frame are prepared and transmitted.
• the advance pointers may include extra packets of data to provide a combined address and data message, separate from voice messages in the voice data section 408.
• the system generally prepares and transmits duplicate pointers (e.g., duplicate pointers N section 420), followed by housekeeping in step 712 (e.g., housekeeping section 422) .
• one or more messages e.g., voice messages or digital data
• pseudorandom interleaving is determined (step 716) for each stream, and the streams are transmitted (step 718) .
• the foregoing steps are generally repeated.
• the current indicator step 720 generally provides a repeated indicator signal (including alerts and pointers) corresponding to at least a portion of the advance indicator signal (including alerts and pointers) prepared at step 708.
• the intervening signals (e.g., those transmitted in steps 708-718) thus provide a delay of a predetermined delay interval and impart time diversity to the protocol. Intervening signals and a predetermined delay interval also occur between the indicator steps 706, 720, and the duplicate pointer steps 710, 724, respectively.
• the advance indicator signal step 722 provides advance alerts and pointers for information content in the next frame (e.g., frame N+2) . As with the first frame, duplicate pointers, housekeeping, and messages are also transmitted in steps 724-732.
• the flow diagram 800 includes a selection criteria step 802, an indicator reception step 804, and a condition step 806.
• An enable reception step 808 and a disable reception step 810 are also illustrated.
• an extract message step 812, a deinterleave stream step 814, and an extract message step 816 are also shown.
• a selection criteria is established for the receiver.
• the selection criteria may be the presence of a particular alert bit or address (pointer) for the receiver, either individually or as a group receiver.
• the receiver receives an indicator signal or repeated indicator signal (e.g., an alert packet or pointer packet) with which it will establish a match, no-match, or indeterminate condition (step 806) based on the selection criteria. If the receiver is unable to receive the indicator signal correctly (e.g., the CRC indicates uncorrectable errors), an indeterminate condition is established and processing continues at step 808.
• an indicator signal or repeated indicator signal e.g., an alert packet or pointer packet
• the receiver In the enable reception step 808, the receiver enables reception of repeated indicator signals, if any. Thus, if reception of the alerts N+l section 416 is indeterminate, the receiver may enable reception of the subsequent alerts N section in the next frame. Similarly, if the reception of the pointers N+l section 418 is indeterminate, the receiver may enable reception of the pointer N section 414 or duplicate pointers N section 420 in the next frame. Generally, however, either a match (e.g., a matched alert or address) or no- match condition is established that indicates that a message is present or absent for the receiver in the current frame or next frame .
• a match e.g., a matched alert or address
• processing continues at step 810, where reception of repeated indicator signals is disabled. Furthermore, under the no-match condition, processing continues at step 804 in which the receiver prepares to receive a subsequent indicator signal.
• the receiver determines a no-match condition with respect to the alerts N+l section 416, it may disable reception of the alerts N section in the subsequent frame, but enable reception of the alerts N+l section in that frame.
• the receiver extracts a message location (step 812), typically using a pointer packet 200 and a stream header 500.
• the receiver may then receive the stream (step 814) and deinterleave it in order to extract the particular message (step 816), as discussed above.
• the present protocol operates independently of numerous other considerations that are addressed when designing a service that uses the protocol.
• the system transmitter may be allowed to transmit the messages to a pager once, many times, or a variable number of times depending on system load.
• the pager may apply time diversity combination techniques to the received messages.
• the pager may combine the symbols of two copies of the same message to produce a single message.
• the rate 2/3 convolutional coding using two copies of the same messages, may be treated as a more robust rate 1/3 convolutional code.
• Frequency diversity in which the system transmitter transmits the same message on two frequencies simultaneously, is also possible, provided that an additional receiver is provided in the pager.
• the service provider may transmit advertising to the pagers.
• Predefined voice messages associated with the advertising may be transmitted to the pagers during off peak hours.
• local restaurant advertising may be announced at 11:30 am, for example.
• Emergency services may also be provided.
• a hospital or police department may select emergency notification as part of a pager service plan.
• the system transmitter may then preempt ordinary outgoing messages in favor of transmitting the emergency message to one or more hospital or police department pagers.
• FIG. 9 illustrates a system transmitter 900 and a receiver 902 (e.g., a voice pager) .
• the system transmitter 900 includes an antenna 904, a signal transmitter 906, a controller 908, a clock generator 910, and a memory 912.
• the controller 908 includes general purpose I/O 913, an indicator signal generator 914 and a message signal generator 916.
• the receiver 902 generally includes an antenna 918, a signal receiver 920, a clock generator 922, a controller 924, and a memory 926.
• the controller 924 includes a selection comparator 927, a reception controller 928, a message extractor 930, and general purpose I/O 932.
• the signal transmitter 906 may include, for example, an amplifier, filter, and modulator.
• the controller 908 operates in synchronism with the clock generator 910 and may be implemented, for example, as a single ASIC that includes logic implementing the indicator signal (e.g., alerts and addresses) generator 914 and message signal generator 916 which generates (e.g., selects, formats, and encodes) the indicator signals and messages signals discussed above.
• the clock generator 910 produces the clock signals for overall system control, signal timing, and frame timing.
• the memory 912 may store, for example, individual and group addresses, alerts, and digitized voice messages for transmission using an appropriate combination of SRAM, DRAM, hard disk storage, Flash memory and the like.
• its signal receiver 920 may include, for example, a filter and demodulator that allow the receiver 920 to pass received signals to the controller 924 for digital processing.
• the clock generator 922 produces clock signals for overall system control and frame reception timing, and the memory 926 may be used to store selection criteria including alert bit and address assignments.
• the controller 924 may be implemented in an ASIC that includes logic for implementing the selection comparator 927, the reception controller 928, and the message extractor 930.
• the selection comparator 927 compares a received indicator signal against a selection criteria to determine whether the receiver 902 will receive a message.
• the reception controller 928 may enable or disable reception of repeated indicator signals and messages and discussed above.
• the message extractor 930 retrieves messages from the received signals by examining the indicator information (e.g., the address information) , and extracting a message from a stream, as noted above.

Landscapes

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

Applications Claiming Priority (7)

Publications (1)

Family

ID=27371043

Family Applications (1)

Country Status (12)

Families Citing this family (2)

Family Cites Families (2)

• 1998
  • 1998-11-23 PE PE1998001141A patent/PE20000046A1/es not_active Application Discontinuation
  • 1998-11-23 AU AU15953/99A patent/AU1595399A/en not_active Abandoned
  • 1998-11-23 JP JP2000522571A patent/JP2001524767A/ja active Pending
  • 1998-11-23 WO PCT/US1998/024858 patent/WO1999027508A1/en not_active Application Discontinuation
  • 1998-11-23 EP EP98960335A patent/EP1034519A1/en not_active Withdrawn
  • 1998-11-23 KR KR1020007005649A patent/KR20010032409A/ko not_active Application Discontinuation
  • 1998-11-23 CA CA002310728A patent/CA2310728A1/en not_active Abandoned
  • 1998-11-23 CN CN98811556A patent/CN1280696A/zh active Pending
  • 1998-11-23 IL IL13597198A patent/IL135971A0/xx unknown
  • 1998-11-25 UY UY25269A patent/UY25269A1/es not_active Application Discontinuation
  • 1998-11-25 AR ARP980105978A patent/AR014037A1/es unknown
• 1999
  • 1999-04-26 TW TW087119556A patent/TW418575B/zh not_active IP Right Cessation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events