`
`
`
`FLEXTM
`
`FLEXIBLE HIGH SPEED PAGING PROTOCOL
`
`BENCHMARKING
`
`Released 5/14/93
`
`Updated 4/26/94
`
`M07"051:éDLA
`Pagmg Products Glcua
`
`FLEX‘is lrademmk o! Motorota, Inc.
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 1 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 1 of 16
`
`

`

`
`
`INTR D TlN T
`
`PA lN
`
`VER-THE-AIR PR T
`
`L
`
`In the past decade, the "World of Paging" has‘grown significantly, but the
`variety of coding format alternatives have been very few. The intent of the protocol
`analysis that follows will be to make sure the reader is familiar with what has
`existed up to now and what the newly introduced FLEX protocol offers in the way of
`improvements and enhancements. Lets begin with some of the more common
`terms used to describe a paging coding format:
`
`Operating Speed ~ channel rate of the code defined in bits per second (bps).
`
`Preamble - a beginning portion of the coding format's signaling regimen that
`allows a pager to operate in a battery saving mode prior to actual data being
`transmitted and provides the pager with a means to establish bit
`-
`synchronization.
`
`Codewords - a fixed number of bits containing information and parity. provides
`regular sized increments within each protocol to transfer word synchronization,
`operational information, addressing, vectoring and codewords usually provrde
`means for error detection or correction.
`
`Frames - a fixed time period containing"N’ complete codewords.
`each coding format.
`
`is different for
`
`Batch - a structured duration of the POCSAG coding format signaling which
`contains a Synchronization Codeword, 8 Frames each havrng 2 Codewords for
`a total of 17 codewords.
`
`Interleaved codewords - a method of interdigitating codewords such that a signal
`fade over a period of time longer than correctable by one codeword is spread
`over many codewords. Typically defined as a interleaved depth of 'X' words.
`
`Asynchronous ~ a coding format that is not synchronized by a real time clock-
`signal; the coding format may start its operating sequence at any given time,
`usually by sending a preamble.
`‘
`
`Synchronous - a coding format that is regularly scheduled to begin and end its
`signaling events over time periods identified by a real time clock and its code.
`
`Calls per User Hour - a method of defining how many calls a user expects to .
`receive per hour over a given work period; typically a value like 0.2 c/uhr which
`translates to 2 calls per 10 hour day.
`
`- System Capacity - the expected number of subscribers a given system can
`support during peak times without extremely long delays.
`
`- Battery Life - a figure calculated for a known pager supported by a given battery
`size and extracted from the battery saving features built into a paging coding
`format.
`'
`
`GOOG 1033
`IPR of US. Patent No. 8,601,154
`Page 2 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 2 of 16
`
`

`

`~ Battery Save Ratio BSRIs based on the paging receiver being able to operate
`at variable levels of operating current drain. During the time the pager is not
`expecting to be actively searching for its assigned address location it can
`remain in a low standby ldrain condition; when the pager is actively decoding
`received signaling as it searches for its address and messaging it will be
`operating in a fullon 'drain condition The ratio of total time to the duration of
`tull~~on 'draIn is called the BSR
`
`. RF Sensitivity - that minimum field strength that is sufficient to allow a defined
`percentage of address and complete message reception.
`
`This list oi definitions is not all inclusive but is intended to ensure that the
`majority of unique terms associated with coding iormats are understood before we
`go forward
`
`THE P
`
`A .
`
`DI
`
`RMAT ~
`
`HANNEL
`
`APA lTY:
`
`(an Asynchronous non- interleaved code; see
`The POCSAG coding iormat
`Figure 1) was introduced early in the 1980's as a code tor the delivery of digital
`signaling of Numeric messaging. Subsequently the code was structured to allow
`Alphanumeric messaging to also fit into the code. The pages that follow illustrate
`how the structure of the code can be analyzed to determine the System Channel
`Capacity for the stated call rates, batch lengths and messaging events. Today's
`three operating speeds are: 512 bps, 1200 bps and 2400 bps
`.
`
`SUBSEOUENT
`BATCHES
`,
`‘
`F4... PnEAMaLE—~.>H_.._ FlRSTBAiCH ”TH
`:75 BITS 0F REVERSALS
`.
`Imam. ETC.)
`
`PAGWG
`FORMAT
`
`
`
`9 FRAME .
`2 cooewonos
`
`“a
`
`/
`
`
`
`33, amt-mm
`
`roamr SOURCE
`
`' aoonsss
`cooewoeo
`
`I
`
`lDENilFiER
`airs
`
`MESSAGE
`ccoewono
`FORMAT
`
`.
`
`MESSAGE airs
`.
`
`.
`Figure 1
`
`-
`
`
`54am
`
`.
`
`.
`
`mam CHECK aIts
`
`.
`
`EVEN
`PARITY
`
`I
`
`.
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 3 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 3 of 16
`
`

`

`. POCSAG Coding Format:
`Acronym for the Eost foice Qode Standardization Advisory Qroup
`
`- Available Operating Speeds - 512 bps, 1200 bps and 2400 bps
`' Unique Codeword Structures:
`(32.21 BCH code)
`' Synchronization Word - FS; unique address codeword
`- Address codeword ~ lst bit is "0"
`
`~ Message codeword ~ lst bit is "1”
`.
`idle codeword - unique Address Codeword
`- Messages must end on Codeword boundaries
`. A POCSAG pager is assigned to look for pages only in its frame
`
`,
`
`The expected Paging System Capacities for the 3 speeds of the POCSAG
`coding format are summarized in Table 1. The specificcall rates are noted for each
`of the categories of signaling represented. The factual details leading to these
`values are given in the Appendix for those interested in the calculations.
`
`Air
`
`interface Protocols - Continued Advances In Channel Capacity
`
`‘
`l
`
`
`
`
`
`
`Paging System Capacities (000)
`
`
`
`Numeric
`Alphanumeric
`Signaling
`
`Snead
`10 Digit,
`40 Char.
`
`
`
`Choice of Coding Format
`’ Tone
`
`
`
`512 ligIlagSAG
`512 bps
`348.8
`69.8
`11.6
`1
`
`
`1200 (FragoOS/XG
`1200 bps
`816.0
`163.2
`27.2
`
`
`2400 (P99538916
`2400 bps
`1,635.2
`327.0
`54.5
`.
`1
`
`
`'
`
`.
`
`one.
`Note: Codewords Required per Page a]1{Seeing Format are:
`POCSAG‘ ~ (32.21)Codewords; l C
`CW Numeric (10 Digit). 15 CW Alphanumeric (do Qhamcxer)
`Call rate per user hour are: Tone 0J5, Numeric 0.25 and Alphanumenc 0.30; at a lOO‘l’. System Eifiaency
`
`the COM as the
`' The POCSAG Coding Format was given inteman'onal reco nidon in 1981 when it was accepted to
`recommended Radiopaging Code No.
`1 (Recommendation
`4) POCSAG IS an acronym Ior the osl Office Code
`Standardization Advisory Group.
`it is today's most prominent Coding Formal.
`
`Table ‘1
`
`. THE MOTOROLA "FLEX" CODING FORMAT - CHANNEL QAPACITY:
`
`The FLEX coding format operates as a' Synchronous 'code and has the added
`signal fade protection in its data field (addressing, vectoring and messaging field)
`of sending the bits at an interleaVed depth of 8. From the details in Figure 2. the
`structure ofthe repetitive frames each'at 1.875 seconds long allow for eleven data
`blocks each containing 8 codewords. The first codeword in Block O is assigned to
`be
`a Block information word which contains
`frame and system structure
`information. This leaves 87 available codewords to be utilized for data delivery.
`The FLEX coding format has 3 signaling speeds in 4 formats to allow its
`implementation into existing infrastructure with a 1600 bps, 2 level FM system;
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 4 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 4 of 16
`
`

`

`l‘4/l
`
`newer infrastructure setups for 3200 bps using either 2 or 4 level FM and the
`highest speed of 6400 bps using'4 level FM. Each of these choices allows the
`system operator to add' on subscribers and infrastructure When system capacity
`increases are deemed appropriate.
`The multiple
`speed feature of FLEX is
`accomplished by multiplexing one. two or tour 1600 bps channels of traffic. Each of
`these 1600 bps channels of traffic are referred to as Phases. As a result. we have
`available data field codewords totaling: 87, 174 and 348 for each of the three ‘
`speeds.
`
`[-4—-————————128 Frame Cycle : 4 Minutes 0 Seconds
`
`l
`
`
`
`Each page! is assigned to decode only frame: which match a code plug
`vows in l specified number olloust significant frame number bits.
`Thus. ll- pngor must match the 4 LSB': it would decode
`ovary 16th frame.
`
`‘
`
`Frame (1 .875 Sec)
`
`,
`
`.
`
`
`
`
`
`
`
`interleaved Blocks = 160 ms
`
`8 X 32 bit: @1600 bps 2 Level FM
`
`16 X 32 bit: @ 32130 bps 2 or 4 Level FM
`
`‘
`32 X 32 bits @ 6400 bp: 4 Level FM
`
`
`:
`
`
`
`
`Sync 1
`
`Frame
`lnlo
`
`Sync 2
`
`l—a———.2- Level FM—a—l
`
`Figure 2
`
`The detailed calculations that illustrate how the structure of the FLEX code can be
`analyzed to determine the System Channel Capacity for the stated call
`rates,
`messaging events and frame operating speeds are also in the Appendix.
`it must
`be noted that part of the structure of the FLEX code is have all Addresses for a
`given paging event within a Frame ,to_ precede the messaging.
`in addition,
`to
`properly locate a given pagers messaging there are Vectoring bits assigned to
`indicate where the message begins and ends within the Frame. Given these
`details the expected Paging System Capacities for the FLEX coding format can be
`summarized in the~following manner.
`I
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 5 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 5 of 16
`
`

`

`
`
`EMILE
`
`P
`
`'
`
`'n
`
`M
`
`4/
`
`We:
`
`167.040
`
`334.080
`
`668.160
`
`E'
`
`.
`
`S
`
`Tone (Function)
`Numeric 10 Digit
`Alphanumeric 40 Character
`
`556,800
`167.000
`32,800
`
`1,113,600
`334,100
`65,500
`
`2,227,200
`668,200
`131,000
`
`The increased capability demonstrated by the versatility of the FLEX coding
`format makes it very attractive to increase the number of subscribers assigned to
`”Alphanumeric paging events and / or increase the average length of Alphanumeric
`messaging. The following figures reflect what can beobtained from 80 character
`and 240 character messaging activity on a FLEX operated channel:
`
`Total FLEX Codewords (Address, Vector and Messaging) required forBO Character
`Messaging z 30
`
`Total FLEX Codewords (Address, Vector and Messaging) required for 240
`Character Messaging = 84
`
`i
`
`_n
`
`1500.005
`
`3200.025
`
`511129.205
`
`167,040
`
`334,080
`
`668,180
`
`if
`
`iv
`
`‘
`
`P
`
`in
`
`:
`
`w.r
`er
`
`m
`
`80 Character Messaging '
`240 Character Messaging
`
`18.560
`6,630
`
`37,120
`13,260
`
`' 74,240
`26.520
`
`Note: Alphanumeric Messaging is again assumed to be at 0.3 calls / user hour
`
`These figures are outstanding when compared to the highest POCSAG offering
`of 2400 bps which would yield for 80 character messaging 28,190 users and for
`240 character messaging a total of 9,620 users.
`'
`
`Referring to Table 2 on the next page, the direct comparison of system channel
`capacities With assumed call rates between the FLEX coding format and today's
`widely accepted POCSAG coding format are summarized. As can be seen the
`FLEX code with its multiple speed capability allows an operator to achieve
`maximum subscriber capacity for a given operating channel. The added feature of
`superb fading performance due to its interleaved structure and ruggedness due to
`its error correction capability will make it a most preferred coding format for those
`operating systems desiring the best possible system performance and subscriber
`list capacity.
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 6 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 6 of 16
`
`

`

`Elexible High Speed Pag’gg Emigggl Egggbmaflgmg
`
`'
`
`Mototola mg 4525515
`
`Summary Overview 01‘ System Channel Capacity
`Alr Interface Protocols - Continued Advances in Channel Capaclty'
`
`Paging vSystem Capacities (000)
`Numeric
`Alphanumeric
`'
`‘
`40 Char.
`
`‘
`
`Tone"
`
`(1993)
`
`Choice of Codino Format
`
`512 POCSAG
`(1960)
`
`1200 POCSAG
`(1990)
`
`2400 POCSAG
`(1992)
`
`FLEX
`(1093)
`
`FLEX
`(1993”
`
`FLEX
`
`Signaling
`S-eed
`
`512 bps
`
`-
`
`1200 bps
`
`2400 bps
`
`15300 bps
`
`3200 bps
`
`6400 bps
`
`
`
`Assuming Call Rates Per User Hour of: Tone O.l5, Numeric 0.25 and Alphanumeric 0.30:.and tOOVu'Sysleml-Iifidancy.
`(Note: Call Rates and System Capacities may vary dramatically between dillerentoperaung systems)
`.
`‘
`' Assumes multilunction capability oi FLEX is employed; multiply FLEX values by 2 lor single luncuon applimuons.
`
`. Table 2
`
`BATTERY LIFE QAPABILITY FRQM PAGINQ CODING FORMAT§1
`
`The capability for power drain conservation is an integral part of these two
`paging coding formats.
`in the paragraphs that tollow. we will identity how the pager
`may operate to minimize its high current drain operation.
`
`THE 'PQQSAQ CQDINQ FQRMAT:
`. To begin we will
`look at the details presented in Figure 1. There are .17 total
`codewords present
`in each Batch.
`It we assume a heavily loaded channel
`operation, the majority oi time the pager will only be looking in a fully powered On—
`mode during its assigned Frame. This equates to the pager once having found bit
`sync in the preceding Preamble, will obtain correct codeword sync by decoding the
`correct Synchronization Word (F5) at the start of each Batch in a high power drain
`mode. The pager can after verifying F5 return to a lower ldrain mode waiting for its
`proper Frame location to repower up as it
`looks for the pagers Address and
`Messaging. This process will continue over subsequent Batches with the only
`interruption being for a new preamble time period.
`If we assume that the preamble
`is a small portion of active signaling, a pager will be searching (in a fully powered
`up mode) over a period of time equal
`to F5 + 2 Frame Codewords. Or properly
`stated. 3 codewords. out of 17 total Batch codewords. Therefore,
`the expected
`Battery Saving Ratio (BSFt) for the POCSAG coding format is:
`‘
`
`17 Codewords + 3 Codewords = 5.67 :l BSR
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`
`Page 7 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 7 of 16
`
`

`

`the pager cycles on and off the high
`When the channel“ is minimally loaded,
`. power mode at a fixed repetitive search rate until preamble and codeword sync'is
`again attained. Overall, this 5.67 : 1 BSR portrayal illustrates what the code offers
`for battery conservation.
`it must be stated that there are some additional
`time
`segments needed for the pager to turn on prior'to these expected time frames as
`well as some turn off delays after these time windows are gone. These additional
`time duration's would lead to a lower BSR than 5.67 : 1. To give added
`improvement to the expected 88R for POCSAG ‘most all manufacturers pagers are
`able to determine from a portion of the received codeword bits that an address or
`message codeword is being received and if it represents their assigned address.
`As a result of these partial decoding enhancements. the length of time the pager
`actually needs to be in a fully powered On~mode can be greatly shortened.
`it is
`possible for most of these pagers to achieve a BSR in the vicinity of 12 : 1 or better.
`
`HT
`
`"F"|NF
`
`Using the details presented in Figure 2, we will now identify what significant
`levels of BSFt enhancement is built into the FLEXcoding format. Pagers can be
`assigned to look for their assigned Frame in the following 2N values:
`1
`(every
`Frame), 2 (every other Frame), every 4th, every 8th, every 16th, every 32nd, every
`64th, or1 time in every 128th Frame within the FLEX coding format. The normally
`accepted level of subscriber
`response to an inbound call would be in the
`neighborhood of 1 minute before the caller becomes impatient. This being the
`case a, single Frame assignment of once every 8th, 16th or 32nd Frames would be
`the more typical latency assigned to a pager user.
`if the pager would be allowed to
`remain on for the entire Frame then the expected BSR for these assigned Frame
`locations is 8 : 1,16 : 1 and 32‘: 1 respectively. Each of these are greater than the
`limited capability of
`the POCSAG code. However.
`there is even more BSR
`potential within the FLEX coding format. We will now discuss several scenarios
`dealing with how the pager need not remain on for the total Frame length.
`
`Let us establish useful time duration's of a Frame (Figure 2) —.
`~ Total Frametime = 1.875 seconds; @ 1600 bps this equals 3000 bits
`- Total Sync time = 115 milliseconds
`-
`~ Total Data'field time = 1.875 .- 0115 -.'= 1.760 seconds; 160 msec per Block»
`
`I
`
`nri1‘
`
`Assume the FLEX based operating system has all varieties of pagers in service.
`Also assume that the Frame / Phase your pager is dedicated to now contains all
`Alphanumeric messaging. For a Frame containing all Alphanumeric 40 character
`messaging at 17 total codewords per event only 5 complete messages would be
`sent out and all Addressing would fall into Block 0. The pager-can go to a standby
`ldrain condition after not finding its Address in Block 0.
`if a pager came up for only
`that portion of the Frame up to and including Block 0 then it has the potential for
`powering down to obtain a BSR iactor of:
`
`1.875 sec. + (0.115 + 0.160) sec. = 6.8 :
`
`1 for Frame impact
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`
`Page 8 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 8 of 16
`
`

`

`
`
`We can determine the lull Impact of the BSR tor a Frame assignment of the pager
`which allows it to operate in a receiving mode for only 1 Frame out of every 16
`Frames in the System Cycle:
`Alphanumeric 4o Char. Scenario 1: Full BSFl impact is (16:1) x (6.8:1) = 108.8
`
`This resUlt can be seen in Figure 3.
`
`FLEX Battery Saving Ratio Vs Channel Traffic
`
`Alphanumeric
`40 Character
`
`20/60/20
`
`Mix
`
`Numeric
`
`Tone Only
`Function
`
`Tone Only
`Addresses
`
`25°
`
`200
`
`150
`
`‘00
`
`Battery
`Saving
`Ratio
`
`50
`
`
`
`32 Frame Cycle
`
`,
`
`‘
`
`~-
`0 i
`.
`
`0
`20K
`40K
`60K
`30K
`100K
`120K
`140K
`150K
`180K
`0
`40K
`80K
`120K
`160K
`200K
`240K
`280K
`320K
`360K
`0
`80K
`160K
`240K
`320K
`400K
`480K
`560K
`640K
`720K
`Calls Per Hour for FLEX Speed: 01
`1600, 3200, and 6400 bps
`Nola: To extract System Capacity item the stated Call: per Hour divide by the expected Call Rate per User Hour.
`For example - lor the Numeric to all
`it value ol 167K at 640mm: with a 0.25 Calls/UsorHr tactor we obtain
`167K . 0.25 a 66312 Subscriber:
`-
`
`Scenarig 2:
`
`Figure 3
`
`Forthe same FLEX based operating system, if we have a Frame containing all
`Numeric 10 Digit messaging at 4 total codewords per event 21 complete messages
`would be‘sent out and all Addressing would fall into Blocks 0,
`1 and 2 (remember 8
`codewords are contained in each Block). The pager can go to standby idrain after
`not finding its Address in Blocks 0,
`1 and 2, The pager needs to only be actively
`searching tor Addressing in the Frame as far as the 3rd Block. The pager then has
`the potential for powering down for an additional BSR factorof:
`
`1.875 sec. + (0.115 + 3 x 0.160) sec. = 8.15 :1 for Frame Impact
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`
`Page 9 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 9 of 16
`
`

`

`'l'i‘
`
`F” Pr
`
`lenhmrk'
`
`‘
`
`4
`
`We can determine the full impact of the BSR for a Frame assignment of the pager
`which allows it to operate in a receiving mode for only 1 Frame out of every 16
`Frames in the System Cycle:
`,
`
`Numeric 10 Digit Scenario 2: Full BSR impact is (16:1) x' (3.15:1) = 50.4
`
`This result can also be seen in Figure 3. All of the estimates portrayed in Figure 3.
`can be used as future reference for projecting expected BSR performance of the
`FLEX coding format.
`
`RF PERFQRMANQE OF PAGING QQDINQ FORMATS:
`
`The ability to receive a messaging event from a..well designed paging system
`depends on the sensitivity of
`the paging receiver. and the coding rformat's
`ruggedness. The ability to correct errors is inherent in all codes. Possible address /
`messaging errors can result when a subscriber is in weak signal locations or where
`signal fades are occurring. The FLEX coding format is able to correct 2 bit errors
`while the POCSAG coding format is limited to Correcting only one bit error. The
`added advantage the FLEX code has over the POCSAG code is the utilization of
`an interleaved data field (Blocks 0 through 10) so that the pager is able to ride
`through longer signal fades which minimizes fade induced errors.
`‘
`'
`
`FLEX Performance on Rayleigh Faded Channel
`
`
`Probability of Misting Page or Rncnlvod Mung. Cont-inn Error:
`no Char anmumri: muting- Oslnolo Genet-tot Rayleigh Fuding
`0051ka Frequency :- 6.35 H:
`JOmah® 150MHz I smonaoooum
`
`
`700 Sunni-- par RF Ltwl
`
`
`
`
`~130 423 '126 424 -122 420 4139115 “IN -\12 410 >108 406 404 402 400 ~93
`dbm
`FIGURE 4
`
`-96
`
`~94
`
`v92
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 10 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 10 of 16
`
`

`

`M
`
`4/
`
`4
`
`The other aspect that must be realized is that as the signaling speed of a coding
`format increases the amount of energy contained in a single bit
`is lower. This
`results in more signal being required to signal the pager.
`if we refer to Figure 4, the
`range of expected performance in a Gaussian environment (standing still or no
`multiple signal sources or reflections) and the faded environment (moving within
`multiple signal sources or reflections on the channel along with the most direct
`signaling)
`is presented for both the FLEX code and the POCSAG code for the
`noted operating speeds. Both of the previously noted aspects that allow the FLEX
`coding format
`to be more rugged results in FLEX outperforming the POCSAG
`coding format at all operating speeds inthe. faded environment. Also. as the
`operating speed increases the average pager sensitivity does become lower.
`From Figure 4 the following performance differences in a fading environment
`between FLEX and POCSAG can be stated:
`'
`
`.
`Gaussian Reference
`Fading Environment
`Fading Degradation
`
`Relative Signal Strength for 99% Success Rate
`
`512
`E99553
`425.3 dBm
`402.2 dam
`23.1 dB
`
`‘
`
`1600
`1200
`ELEX
`EQQSAQ
`-121.7 dBm
`—123.2 dBm
`-95.9 dBm .4072 dBm
`27.3 dB
`14.5 dB
`
`6400
`ELEX
`418.2 dBm
`404.2 dBm
`14.0 dB
`
`(The meaningful reference portion of the Figure 4 curve is the value of le equal to
`0.01. The vertical axis noted asltvP means that for a probability of mrssrng a page
`to have a value 010.01 then the probability P of receiving a page is 0.99.)
`
`From these results. it can be seen that for a FLEX operating system the impact on a
`pager when operating within a fading environment has approximately a 14dB
`degradation for the lowest to fastest FLEX speed compared to its standing still
`(Gaussian) performance. The POCSAG code is impacted by approximately 23dB
`at 512 bps and 27dB at 1200 bps as a comparison. The ruggedness of the FLEX
`code leads to this outstanding performance improvement.
`The net
`system
`infrastructure adjustment to operate at the higher FLEX speeds is to have the
`number of system transmitters increase for a specific coverage area to supply the
`required signal strength.
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 11 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 11 of 16
`
`

`

`'Hi
`
`l
`
`4//
`
`APPENDIX _
`
`
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`
`Page 12 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 12 of 16
`
`

`

`MQIQt‘QIg lng. FLEX Qgging Fgrmai
`1500 bps, 3200 bps. 6400 bps
`
`1 Frame Structure:
`
`- Sync + Data Blocks = 1.875 seconds
`.- Data Blocks 2 11 with 8 codewords each; interleaved depth of 8
`- Available Codewords ‘a 11 x 8 . 1 Overhead = 87 codewords
`
`- Available Frames per Hour :1: 3600 + 1.875 = 1.920 frames
`Available Codewords per Hour = 87 x 1920 = 167.040 codewords
`- Effective Codewords per Hour at 100% efficiency = 167,040 codewords
`
`- Page Structure: Codewords are (32.21 BCH code):
`
`
`
`Vector/
`Message
`Total
`
`A
`ddress Overhead Check Sum Messa-e Codewords'
`
`
`
`2
`21 bits
`4
`21 bits
`
`17
`280 bits
`10 bits
`39 bits
`21 bits
`Alphanumeric (40 Char)
`
`‘ Using (32.21) BCH codewords, 21 information bits are available in each codeword. Total codewords are
`calculated by dividing total bits by 21 and rounding upto‘ a whole number.
`
`Tone (Function)
`Numeric (10 Digit)
`
`
`
`5 bits
`17 bits
`
`4 bits
`5 bits
`
`12 bits
`40 bits
`
`- Data Block Speeds:
`
`- 1600 bps: yields 167,040 elfeclive codewords
`- 3200 bps; yields 334.080 effective codewords
`- 5400 bps; yields 668,160 efleclive codewords
`
`- System Structure and Calls per User Hour Influence:
`
`
`Codewords
`Expected Peak Call
`
`
`-er Pae
`S stem Structure
`Rate .er UseriHour
`
`
`Effective
`
`Codewords
`
`
`
`100% Tone (Function) '
`
`0.15
`
`100% Numeric
`,
`0.25
`'
`4
`1.00
`
` 100% Alphanumeric
`
`
`~ System Capacity for 100% efficiency:
`
`codewords available pg: 1150:
`Effective Codewords‘
`
`:
`
`0W.
`Effective Codewords
`
`37.750
`
`S stem Structure
`
`1002/o Tone (Function)
`100% Numeric
`‘
`
`100% Alphanumeric
`
`2,227,200
`558,150
`
`131,010
`
`3200 bps
`Ca-acit
`
`1,113,500
`334,080
`
`55.505
`
`1500 bps
`Canacit
`
`555,000
`167.040
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 13 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 13 of 16
`
`

`

`i
`
`'P
`
`nh'
`
`Mr
`
`4/
`
`PQC§AQ diing Format: , System Capacity Analysis
`512 bps
`
`0
`
`Preamble Length a 1.125 seconds (assumed to be sent 1 time for each 30 Batches)
`Batch Length a 1.0625 seconds
`Fully Loaded Paging event with $0 Batches a .33 seconds
`.
`1.125 + 30 (1.0625) s 33 seconds
`-
`in a 1 hour period there are 109 available events with 30 Batches per event
`At 8 Frames available per Batch with 2 codewords each there are:
`-
`16 codewords per Batch
`480 codewords per 30 Batch event
`52,320 codewords available per hour
`
`.
`
`.
`
`- Address & Messaging Structure and Calls per User Hour Influence:
`
`Ettectlve
`
`
`
`Address 4» Message
`Expected Peak Call
`
`Codewords/Hr
`
` Pane Structure
`
`Codewords Re-ulred Rate ner User Hour
`
`
`Tone
`1+0:1
`0.15
`
`
`
`
`
`1+ 2 z 3'
`0.75
`Numeric 10 Dlglt
`Alpha 40 Char
`1+ 14 = 15"..
`
`
`
`10% T,70°/o N,20°/o A
`1, 3, 15
`0.15, 0.25, 0.30
`1-44
`
`
`' A Numeric digit requires 4 bits; with the (32.21) codeword 20 bits are available tor messaging. This yields 5
`digits per codeword and 2 codewords are needed for 10 digits; atotal cl 3 codewords are needed when
`.
`including the address codeword.
`‘
`'
`" An Alphanumeric character requires 7 bits; with the (3221) ooderivord 20 bits are available for messaging.
`This yield 2 6f7 characters per- codeword. This requires 14 codewords for 40 characters; a total of 15
`codewords are needed when including the address codeword.
`
`0.25
`
`0.30
`
`4-50
`
`-
`
`System Capacity for 100% Elticlency:
`
`WWW
`,Ettectlve Codewords
`‘
`Eitectlve Codewords
`
`S stern Structure
`
`100% Tone
`
`100% Numerlc 10 Digit
`
`100% Alpha 40 Char.
`
`10% T,7 % N,20% A
`
`Ellective Codewords
`Reulred
`
`Maxlmum Expected
`Users
`. 100% Ettlclenc
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 14 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 14 of 16
`
`

`

`
`
`l'
`
`_‘
`
`9
`
`'
`
`lnhmrkin
`
`M
`
`P CA Coin Frmat: S
`1200 bps
`
`temCaai Anal
`
`i
`
`Preamble Length = 0.480 seconds (assumed to be sent 1 time for each 30 Batches)
`
`Batch Length . 0.4533 seconds
`Fully Loaded Paging event with 30 Batches = 14.08 seconds
`«
`0.480 + 30 (0.4533) :1 14.08 seconds
`-
`in a 1 hour period there are 255 available events with 30 Batches per event
`At 8 Frames available per Batch with 2 codewords each there are:
`-
`16 codewords per Batch
`.
`480 codewords per 30 Batch event
`
`-
`
`122,400 codewords available per hour
`
`.
`
`.
`
`.
`
`Address & Messaging. Structure and Calls per User Hour influence:
`
`'
`Pa-e Structure
`
`Effective
`Expected Peak Call
`Address + Message
`Codewords R-uired Rate er User Hour Codewords/Hr
`
`‘
`
`Tone
`
`Numeric 10 Digit
`
`1+0=1
`
`1+ 2 = 3'
`
`0.15
`
`0.25
`
`0.15
`
`0.75
`
`
`
`Alpha 40 Char
`
`1 +14 : 15"!
`
`0.30
`
`
`
`
`' A Numeric digit requires 4 bits; with the (32.21) codeword 20 bits are available lor messaging.
`is yields 5
`digits per codeword and 2 codewords are needed for 10 digits; a total of 3 codewords are needed when
`‘
`including the address codeword.
`" An Alphanumeric character requires 7 bits; with the (32,21) codeword 20 bits are available lor messaging.
`This yield 2 6” characters per codeword. This requires 14 codewords lor 40 characters; a total at 15
`codewords are needed when including the address codeword.
`
`
`
`
`10% 170% 11.20% A
`
`1, 3, 15
`
`0.15, 0.25, 0.30
`
`. System Capacity tor 100% Efficiency:
`
`r h
`l
`'v i
`Effective Codewords
`
`r
`
`=
`
`___J_2.2s.4.0_0_..__._-...
`Effective Codewords
`
`s stern Structure
`
`.
`
`0
`
`Effective Codewords
`Reuired
`
`Maxlmum Expected
`Users
`-
`100% Efflcienc
`
`. 85,000
`
`100% Tone
`
`100% Numeric 10 Dlgit
`
`100% Alpha £10 Char.
`
`10% T.70% N,20% A
`
`,
`
`816,000
`
`,
`
`163,200
`
`27,200
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 15 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 15 of 16
`
`

`

`E"EE'E
`
`.
`
`1,1,2“
`
`PQQ§A§3 diing Fgrmat: §y§Iem Cagagity Analygis
`2400 bps
`
`Preamble Length = 0.240 seconds (assumed to be sent 1 time lor each 30 Batches)
`Batch Length = 0.2267 seconds
`I.
`.
`.
`Fully Loaded Paging event with 30 Batches: 7.04 seconds
`-
`0.240 + 30 (0.2267) a 7.04 seconds
`
`in a 1 hour period there are 511 available events with 30 Batches per event
`-
`At 8 Frames available per Batch with 2 codewords each there are:
`.
`16 codewords per Batch
`'
`~
`480 codewords per 30 Batch event
`~ 245,280 codewords available per hour
`
`.
`
`,
`
`0
`
`.
`
`o
`
`Address & Messaging Structure and Calls per User Hour Influence:
`
`Ettectlve
`
`
`
`Address + Message
`Expected Peak Call
`
`Codewords/Hr
` Pa-e Structure
`Codewords Re-ulred Rate oer User Hour
`
`
`
`
`Tone
`1+0=1
`0.15
`0.15
`
`
`
`Numerlc 10 Digit
`
`1+ 2 = 3'
`
`0.25
`
`0.75
`
`
`
`
`
`
`
`1 +14 =15"-
`1, 3, 15
`
`0.30
`0.15, 0.25, 0.30
`
`4.5
`1.44
`
`Alpha 40 Char
`10% 1,70% 14.20% A
`
`' A Numeric digit requires 4 bits; with the (32,21) codeword 20 bits are available for messaging. This yields 5
`digits per codeword and 2 codewords are needed tor 10 digits; 3 total oi 3 codewords are needed when
`_
`including-the address codeword.
`‘
`" An Alphanumeric character requires 7 bits; with the (32.21) codeword 20 bits are available ior massaging.
`This yield 2 6/7 characters per codeword. This requires 14 mdewords for 40 characters; a total 01 15
`codewords are needed when including the address codeword.
`
`- System Capacity for 100% Efficiency:
`
`W =
`Ettectlve Codewords
`
`"aw—2W
`Etiectlve Codewords
`
`'
`'
`S stem‘Structure
`
`,.
`
`Eltectlve Codewords
`Reulred
`
`Maximum Expected
`Users @ 100% Eftlclend
`
`100% Tone
`
`~
`
`'
`
`0.15
`
`1,635,200
`
`100% Numerlc 10 Digit
`
`0.75
`
`
`
`327,040
`54,500
`~
`4.50
`_1OD°/o Alpha 40 Char.
`
` 10% T,70% N,20°/o A 170,330
`
`
`
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 16 of 16
`
`GOOG 1033
`IPR of U.S. Patent No. 8,601,154
`Page 16 of 16
`
`