Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

FLEX SUPER BAlTERY SAVE INTERVAL

IP.com Disclosure Number: IPCOM000008187D
Original Publication Date: 1997-Jun-01
Included in the Prior Art Database: 2002-May-24
Document File: 2 page(s) / 106K

Publishing Venue

Motorola

Related People

Von Mock: AUTHOR [+2]

Abstract

Information and other related services received on the FLEX protocol for the most part have a peri- odic pre-determined transmission time that may not coincide to the most efficient battery save cycle desirable. An example of this would be a news ser- vice that gave headline updates every 15 minutes. The pager upon receiving the information would continue to turn on the decoder and receiver search- ing during the remaining 15 minute time interval for non-existent page data.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 2

@ MOTOROLA Technical Developments

FLEXTM SUPER BAlTERY SAVE INTERVAL

by Von Mock and Eric Eaton

  Information and other related services received on the FLEX protocol for the most part have a peri- odic pre-determined transmission time that may not coincide to the most efficient battery save cycle desirable. An example of this would be a news ser- vice that gave headline updates every 15 minutes. The pager upon receiving the information would continue to turn on the decoder and receiver search- ing during the remaining 15 minute time interval for non-existent page data.

  Another more developed example would show a pager decoding several addresses on multiple frames and at different collapses where one, or more, of these addresses was a dedicated informa- tion service address that had a different battery save cycle than the other addresses. In this situation the pager would continue to waste energy looking for a non-existent message during the time the information service would not be transmitting information for that address.

What the above examples would suggest is that FLEX does not necessarily give the most efficient

battery save cycle when the pre-determined next message time is known to be longer that the longest battery save cycle of 4 minutes. A super battery save interval such as describe below would take advantage of the predictable periodic nature of most information services.

  The super battery save cycle would be achieved by adding enhancements to the existing FLEX protocol that would direct the receiving device to setup for a super battery save interval defined by the transmitted number of FLEX cycles.

  Three parts are required to constitute a super battery save interval. First the block information word is setup to instruct the pager of information in the message field that will define a super battery save interval. Second the message field is setup to where the first two codewords of three define the affected address. Finally the third codeword in the message field defines the number of cycles to battery save if and only if the address found in the two message codewords matches it's own.

BIW2 Address Field Vector Field Message Field

i 'M'M'M'

I

'w'w'w'

'I '2 '3 '

Cycles To

Vector Word A...