throbber
13436.1
`
`Half-Rate DTC Support
`
`This information element indicates whether or not the mobile station supports half-rate
`DTCs.
`
`
`
`—_
`n Half-Rate DTCs Not Supported
`
`Half-Rate DTCs Supported
`
`HL_FREQ
`
`This information element is used to determine the frequency of channel measurements.
`
`
`
`Hyperband
`
`This information element provides frequency band information as follows;
`
`“—
`,
`
`All other values are reserved 190mm
`
`Hyperband Info
`
`If present, this information element is used to specify the Hyperband associated with the
`specified channel.
`
`—Parameter_ype
`
`
`
`
`
`Hyperframe Counter
`
`This information element is a non—critical counter used to identify which hyperfiame is
`currently being broadcast. This counter ranges from O to 11.
`
`10
`
`ll
`
`12
`[3
`
`202
`
`Dell Inc., Ex. 1018
`
`Page 86 of 170
`
`Dell Inc., Ex. 1018
`Page 86 of 170
`
`

`

`l
`
`10
`
`ll
`
`12
`13
`14
`15
`
`16
`
`17
`18
`
`IS-l36.l
`
`Initial Selection Control
`
`This flag is used to discourage a mobile station executing the Control Channel Selection
`procedure (initial selection) from selecting a DCCH for camping purposes.
`
`IRA Support
`
`This information element indicates whether or not a mobile station or BMI supports IRA
`address encoding in the Address Info information element.
`
`
`
`
`
`
`__
`
`“ IRA Encoding Not Supported
`
`IRA Encoding Supported
`
`
`
`LAREG
`
`Last Try
`
`This flag indicates whether or not the mobile station is to register when the registration
`number of the current DCCH is not part of its registration number list used to define its
`location area.
`
`If a mobile station receives a Directed Retry and attempts a new access on another
`DCCH, it shall set the Last Try flag in the Origination or the Page Response message to
`the value of the Last Try flag received in the Directed Retry message. Otherwise the
`mobile station shall set the Last Try flag to not enabled at system access.
`
`LTM Measurement
`
`This information element provides the Channel Quality and LT.RSS of the current
`channel in the MACA report.
`
`Parameter Type
`
`WER LT_RSS and Full Measurement Indicator
`
`203
`
`Dell Inc, Ex. 1018
`
`Page 87 of 170
`
`Dell Inc., Ex. 1018
`Page 87 of 170
`
`

`

`18-136.]
`
`The WER field is coded as follows:
`
`
`
`>4-8%
`
`
`
`
`
`>16- 32%
`
`>32-64%
`
`>64%
`
`—__
`
`BER shall be encoded using Table 2.4.5.1-1 in 15-1362.
`
`The LT_RSS and Full Measurement Indicator field is defined as follows:
`
`
`
`
`
`
`mess
`
`-
`
`Full Measurement Indicator
`
`
`
`
`LT_RSS shall be encoded using Table 6.9 in Section 6.3.2.3, according to RSS Value.
`
`The Full Measurement Indicator is a flag indicating whether the associated
`measurement is based on a full measurement or not.
`
`MACA_8_CONTROL
`
`together with MACA_TYPE and MACA_STATUS,
`This information element,
`determines the number of channels reported.
`
`
`
`_-
`Peemeeeeyee
`—-—
`
`
`
`
`10
`
`The Banana field is coded as follows:
`
`
`
`
`
`
`_ No MACA Report restrictions
`
`Page Response and Origination restricted to 8 channels
`other than current DCCH, see Table 6-12.
`
`
`
`
`
`
`
`Dell Inc., Ex. 1018
`
`Page 88 of 170
`
`7M
`
`Dell Inc., Ex. 1018
`Page 88 of 170
`
`

`

`IS-l36.1
`
`MACA_LIST
`
`This information element contains information regarding the channels, other than the
`current DCCH,
`the mobile station shall measure for mobile assisted channel allocation.
`
`
`
`_—
`
`
`4
`
`
`
`
`
`
`
`
`
`
`Note 1: N + 1 instances of this field are included.
`
`1 1 per instance
`
`MACA_LIST (Other Hyperband)
`
`This information element contains information regarding the channels other than the
`current DCCH. A mobile station that is not capable of performing measurements on a
`channel specified in this list shall report a RSS value of 00000 for that channel.
`
`
`
`
`
`
`
`Number of MACA Channels (P)
`
`CHAN (Note 1)
`
`Note 1: P + 1 instances of this field are included.
`
`10
`
`ll
`
`MACA__STATUS
`
`This infomation element determines which MACA function combinations are enabled.
`
`
`
`
`__
`
`
`
`
`
`
`
`11
`
`
`
`205
`
`Dell Inc., Ex. 1018
`
`Page 89 of 170
`
`Dell Inc., Ex. 1018
`Page 89 of 170
`
`

`

`18436.1
`
`MACA_TYPE
`
`This information element determines when MACA reporting is to take place.
`
`
`
`7
`
`10
`
`ll
`
`12
`13
`14
`
`Manufacturer Code
`
`This information element indicates the manufacturer of the mobile station. For
`
`administrative purposes, it is anticipated that the same value used in 18-1362, Section
`2.3.2 will be used for this field.
`
`Max Busy/Reserved
`
`This information element identifies the maximum number of times that BRI at Idle can be
`
`detected during any given access attempt before layer 2 declares an access attempt failure
`(see Section 5.3.3).
`
`
`-_
`
`—_ 1 BRI e Idle Allowed
`
`
`10 BRI :6 Idle Allowed
`
`
`
`
`Max Repetitions
`
`This information element identifies the maximum number of times a specific burst within
`any given access attempt may be sent on the RACH before layer 2 declares an access
`attempt failure (see Section 5.3.3).
`
`
`
`I_
`“—
`
`
`
`
`“—
`
`
`
`0M
`
`Dell Inc., Ex. 1018
`
`Page 90 of 170
`
`Dell Inc., Ex. 1018
`Page 90 of 170
`
`

`

`15-136.]
`
`This information element identifies the maximum number of access attempts that layer 2
`can make before it considers the access to have failed (see Section 5.3.3).
`
`Value
`
`Function
`
`1 Access Attempt Allowed
`
`2 Access Attempts Allowed
`
`3 Access Attempts Allowed
`
`4 Access Attempts Allowed
`
`5 Access Attempts Allowed
`
`6 Access Attempts Allowed
`
`7 Access Attempts Allowed
`
`8 Access Attempts Allowed
`
`8 1
`
`10
`
`011
`
`§ 1
`
`01
`
`110
`
`Max Retries
`
`
`
`
`
`
`111 |||l|||||
`
`10
`11
`
`12
`
`13
`
`Max Stop Counter
`
`This information element identifies the maximum number of times that either of the
`
`following conditions can be detected for any given access attempt before layer 2 declares
`an access attempt failure (see Section 5.3.3):
`
`'
`
`-
`
`BRI set to Reserved or Idle after sending an intermediate burst of an access
`attempt.
`
`R/N set to Not Received along with BRI set to Reserved or Idle after sending the
`last burst of an access attempt.
`
`Value
`
`Function
`
`2 Occurrences Allowed
`
`“ 1 Occurrence Allowed
`
`Maximum PFC
`
`This information element indicates the maximum PFC supported by a mobile station.
`
` PFC Supported
`
`3
`
`207
`
`Dell Inc., Ex. 1018
`
`Page 91 of 170
`
`Dell Inc., Ex. 1018
`Page 91 of 170
`
`

`

`18436.1
`
`The PFC Supported field is coded as follows:
`
`
`
`
`“a
`——
`“—
`
`__
`—-—~_
`
`
`
`
`
`
`
`
`MAX_SUPPORTED_PFC
`
`This information element identifies the maximum paging frame class supported by a
`DCCH or a mobile station.
`
`
`
`
`“M
`PFC;15 the only PFC supported
`PFC215 the maximum supported Paging Frame Class
`
`—_
`
`—_::
`
`
`— PFCs1s the maximum supported Paging Frame Class
`— PFC615 the maximum supported Paging Frame Class
`
`
`
`
`
`
`MEM
`
`This information element indicates whether or not message encryption algorithm A and
`message encryption domain A (see Message Encryption Algorithm Map information
`element) are enabled on the assigned voice channel.
`
`
`
`
`“ Message Encryption Algorithm A and Domain A Disabled
`
`
`— Message Encryption Algorithm A and Domain A Enabled
`
`
`
`
`
`70R
`
`Dell Inc., Ex. 1018
`
`Page 92 of 170
`
`Dell Inc., Ex. 1018
`Page 92 of 170
`
`

`

`IS-l36.1
`
`Menu Map
`
`This information element identifies the services supported by the BMI.
`
`
`l5§
`
`M 1
`
`
`
`
`
`
`
`
`

`
`XXXIX
`
`XXXXXXXIXX
`
`xxxxxmxx
`
`mx
`
`lifil
`
`
`
`
`
`
`
`XXXlX XXXXX
`Triple Rate Data Supported
`
`All other bit map posmons are reserved
`
`1 XXXXX
`
`Double Rate Data Supported
`
`Message Center Address
`
`This information element identies the Message Center Address for the message being
`sent.
`
`
`
`
`
`
`
`Parameter Type
`Address Info
`
`Message Encryption Algorithm Map
`
`This information element identifies the message encryption algorithms, domains and keys
`supported by a DCCH or a DTC.
`
`
`
`
`
`
`
`
`__
`'
`8
`
`Encryption Algorithms (Note 1)
`
`
`
`
`
`
`
`
`Note 1: The Domain Map field identifies the number of instances and ordering of the
`Encryption Algorithms field. One instance of Encryption Algorithms will be
`present for every bit position in the Domain Map that is set to 1. The ordering of
`instances will reflect the Domain Map scanned from left to right (e.g. if only
`Domain A is supported then the only instance of Encryption Algorithms will be
`associated with Domain A).
`
`209
`
`Dell Inc, Ex. 1018
`
`Page 93 of 170
`
`l
`
`3
`
`10
`ll
`12
`l3
`l4
`
`Dell Inc., Ex. 1018
`Page 93 of 170
`
`

`

`18-136.]
`
`The Domain Map field is coded as follows:
`
`
`
`
`
`
`
`
`
`
`
`
`XXXX XXXI
`
`Domain A Supported (Note 2)
`
`All other bit map positions are reserved
`
`Novomamssuppom
`
`-
`
`Note 2: Domain A consists of those portions of FACCH/SACCH messages and Analog
`Voice Channel messages identified as being subject to encryption according to
`Appendix A.
`
`For Domain A the Encryption Algorithms field is coded as follows:
`
`0000
`
`Code
`
`
`
` %%
`
`
`No Message Encryption Algorithms Supported
`
`Algorithm A Supported (see Appendix A)
`
`Reserved for SOC/BSMC Specific Signaling
`
`All other bit map positions are reserved
`
`
`
`Message Encryption Key Map
`
`This information element identifies the message encryption keys supported by the BMI.
`
`__
`_
`
`
`
`
`
`Message Encryption Mode
`
`
`
`
`
`
`
`
`
`
`
`10
`
`This information element identifies the selected message encryption algorithm, key and
`domain.
`
`Parameter Type
`
`
`
`
`
`
`
`
`
`
`
`4 a
`
`Length
`
`710
`
`Dell Inc., Ex. 1018
`
`Page 94 of 170
`
`Dell Inc., Ex. 1018
`Page 94 of 170
`
`

`

`The MEA field is coded as follows:
`
`-I_
`
`18-136.]
`
`
`
`
`
`“ Message Encryption Algorithm A
`All other values are reserved
`
`The MED field is coded as follows:
`
`—_
`Message Encryption Domain A
`7
`All other values are reserved
`
`
`
`
`
`
`
`
`
`The MEK field is coded as follows:
`
`Value
`
`001
`
`All other values are reserved
`
`Function
`
`
`Message Encryption Key A
`
`Message Type
`
`This information element identifies the function of messages. Unassigned codes are
`reserved.
`
`BSMC Message Delivery
`
`Mobile Assrsted Channel Allocation
`
`00 0101 — 5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`211
`
`Dell Inc., Ex. 1018
`
`Page 95 of 170
`
`Dell Inc., Ex. 1018
`Page 95 of 170
`
`

`

`18-1361
`
`
`
`
`
`|
`E-BCCH Messages
`BSMC Message Delivery
`
`Emergency Information Broadcast
`Mobile Assisted Channel Allocation
`
`Neighbor Cell
`
`Neighbor Service Info
`
`Regulatory Configuration
`Alternate RCI Info
`
`Service Menu
`
`SOC Message Delivery
`SOC/BSMC Identification
`
`Time and Date
`
`Code (binary-dec)
`
`000010-2
`
`001100.- 12
`
`000101-5
`
`001101-13
`
`001110— 14
`
`001111 -15
`
`100110—38
`
`001000-15
`
`001001 -9
`
`001010-10
`
`010000—16
`
`
`i1 l
`SPACH Messages
`Code (binary-flee)
`010001-17
`Analog Voice Channel Designation
`Audit Order
`
`010010- 18
`
`Base Station Challenge Order Continuation
`
`BSMC Message Delivery
`
`Capability Request
`
`Digital Traffic Channel Designation
`
`Directed Retry
`
`Message Waiting
`
`Page
`
`Parameter Update
`R-DATA
`
`R-DATA ACCEPT
`
`R-DATA REJECT
`
`Registration Accept
`
`Registration Reject
`Release
`
`Reorder/Intercept
`
`SOC Message Delivery
`SPACH Notification
`
`SSD Update Order
`
`Test Registration Response
`
`Unique Challenge Order
`User Alert
`
`010011-19
`
`000010- 2
`
`010100 — 20
`
`010101-21
`
`010110 -22
`
`010111 -23
`
`011000 - 24
`
`01 1001 - 25
`
`01 1010-26
`
`01 1011 - 27
`
`011100-28
`
`01 1101 - 29
`
`01 1110 — 30
`
`01 1111 —31
`
`100000- 32
`
`001001-9
`
`10 0001 ~ 33
`
`100010- 34
`
`10 0011 — 35
`
`100100—36
`
`100101 -37
`
`
`
`
`
`
`
`
`
`
`’1")
`
`Dell Inc., Ex. 1018
`Page 96 of 170
`
`Dell Inc., Ex. 1018
`Page 96 of 170
`
`

`

`RACH Messages
`
`Audit Confirmation
`
`
` Base Station Challenge Order
`
`
`
`
`
`
`
`
`
`[$436.1
`
`Code (binary-dec)
`
`00 0001 - 1
`
`
`
`
`
`
`
`
`
`
`Serial Number
`
`SOC Message Delivery
`SPACH Confirmation
`
`00 1101 - 13
`
`00 1110 - 14
`
`Unique Challenge Order Continuation
`
`
`
`
`
`
`
`
`
`00 1010- 10
`—-mm-
`
`
`
`
`Message Waiting Info
`
`This information element indicates the type and number of messages waiting.
`
`
`
`_—
`
`Number of1
`
`
`
`
`Type and Number of Messages Waiting (Note 1)
`
`Note 1: From 1 to 16 instances of this field may be sent, providing that the Type of
`Messages is different for all instances. The number of instances is Number of
`Values + 1.
`
`The Type and Number of Messages Waiting field is defined as 2 subfields as follows:
`
`Subfield
`
`
`Type of Message Waiting
`Number of Messages Waiting n
`
`
`
`
`
`
`
`
`213
`
`Dell Inc., Ex. 1018
`
`Page 97 of 170
`
`Dell Inc., Ex. 1018
`Page 97 of 170
`
`

`

`IS.-136.1
`
`The Type of Message Waiting subfield indicates the type of messages associated with the
`Number of Messages Waiting subfield, and is coded as follows:
`
`
`
`
`
`Voice Messages
`
`SMS Messages
`
`G3-Fax Messages
`
`User Specific Messages
`
`
`
`
`
`
`
`
`
`
`
`
`
`0100 to 701 l 1
`All other values are reserved
`
`
`The Number of Messages Waiting subfield indicates the number of messages waiting
`associated with the Message Waiting Type subfield, and is coded as follows:
`
`000000
`
`No Message
`
`Unknown Number of Messages (One or More)
`
`Message
`
`62 Messages
`
`11 1110
`
`111111
`
`S
`
`10
`
`Mobile Country Code
`
`This information element indicates the Mobile Country Code of the current DCCH.
`
`
`
` Field
`Length
`
`
`II
`Parameter Type
`
`
`10
`
`
`
`Mobile Country Code (MCC)
`
`The MCC is the equivalent of the Mobile Country Code defined in CCITT
`recommendation E212. The MCC values are defined in annex A of E212. The following
`values are extracted from 13.212 and are provided as information only. If other MCC
`values are required, refer to Annex A of E212 for a complete list of MCC values.
`
`711"
`
`Dell Inc., Ex. 1018
`
`Page 98 of 170
`
`Dell Inc., Ex. 1018
`Page 98 of 170
`
`

`

`15-136.]
`
`
`
`The 3 decimal digits of the MCC are expressed as the corresponding decimal number
`(000 < = didjdk < = 999) coded in 10 binary bits using a normal decimal to binary
`conversion ( O to 999).
`
`Model Number
`
`
`This information element identifies the mobile station model number (specific to an
`mobile station vendor).
`
`MSID Assignment
`
`This optional information element contains information specifying the MSID the mobile
`station shall use.
`
`
`
`
`
`“—
`
`
`
`
`
`
`-
`
`10
`
`215
`
`Dell Inc., Ex. 1018
`
`Page 99 of 170
`
`Dell Inc., Ex. 1018
`Page 99 of 170
`
`

`

`15-136.]
`
`1
`
`$11wa
`
`
`MS_ACC_PWR
`
`This information element identifies the maximum nominal output power that the mobile
`station shall use when accessing the BMI (see Section 2.1.2.2 of IS- 1362 for tolerances)
`The MS__ACC_PWRis also used when determining criteria for control channel selection
`and reselection.
`
`_
`
`716
`
`Dell Inc., Ex. 1018
`
`Page 100 of 170
`
`Dell Inc., Ex. 1018
`Page 100 of 170
`
`

`

`18-136.]
`
`Neighbor Cell
`
`This field provides neighbor DCCH specific information as follows:
`
`E3
`
`
`
`Protocol Version
`
`
`
`PSlD/RSID Support
`
`Network Type
`
`Directed Retry Channel
`
`PSID/RSID Indicator
`
`PSID/RSID Support Length
`
`Neighbor Cell List (Analog)
`
`\lfl‘Ulvh
`
`This optional information element contains information regarding the analog channels the
`mobile station shall measure with regards to the Control Channel Selection and
`Reselection procedures. This information element always specifies analog neighbors in
`the 800 MHz hyperband,
`
`
`if -
`
`ParmterType
`Number of Analog Neighbor Cells (M)
`
`
`
`
`Analog Neighbor Cell (Note 1)
`
`
`
`
`
`
`
`
`Note 1: Up to "M" instances of this field may be sent.
`
`217
`
`Dell Inc., Ex. 1018
`
`Page 101 of 170
`
`Dell Inc., Ex. 1018
`Page 101 of 170
`
`

`

`IS-136.l
`
`.
`
`The Analog Neighbor Cell field is coded as follows:
`
`|Length
`
`11
`
`
`
`
`
`Digital Color Code (DCC) (as defined in 18-1362)
`RESEL OFFSET
`
`
`
`@—
`—2
`_s
`
`
`
`
`—4
`
`
`
`
`
`
`
`2 Neighbor Cell List (Other Hyperband)
`
`3
`4
`
`5
`
`This optional information element contains information specifying the digital channels
`the mobile station may measure in order to acquire service in an alternate frequency band.
`
`
`
`
`
`
`
`
`Note 1: Up to "P" instances of this field may be sent.
`
`
`
`
`
`
`e Neighbor Cell List (TDMA )
`
`7
`8
`
`9
`
`This optional information element specifies the digital channels the mobile station shall
`measure with regards to the Control Channel Selection and Reselection procedures.
`
`
`
`
`
`
`
`
`Parameter Tm
`
`Number of TDMA Neighbor Cells (N)
`
`
`
`Neighbor Cell (Note 1)
`
`
`
`57 - 77 per instance
`
`Note 1: Up to "N" instances of this field may be sent.
`
`7151
`
`Dell Inc., Ex. 1018
`
`Page 102 of 170
`
`Dell Inc., Ex. 1018
`Page 102 of 170
`
`

`

`IS- 1 36.1
`
`Network Type
`
`This information element identifies which Network Types are supported on a control
`channel. See Section 8. 3. 2 for Network Type definitions.
`
`
`
`Networuype —
`
`
`Non-Public Probability Blocks
`
`This information element indicates whether or not each channel probability block for a
`given system configuration contains a DCCH for a non-public system in its current
`service area.
`
`
`
`
`
`
`
`
`-16
`
`
`
`
`
`
`
`
`Non-Public Map Length (N)
`
`Non-Public Block Map (Note 1)
`
`Note 1: The length of this field is N plus 1 long.
`
`10
`
`ll
`)2
`l3
`14
`15
`
`16
`17
`18
`
`19
`
`20
`
`21
`22
`
`23
`
`24
`
`The Non-Public Block Map field indicates which probability blocks within a band are
`likely to contain Non—Public service.
`
`The ordering of the bits in this field reflects the ordering of the probability blocks of a
`band in that the least significant bit is associated with the first probability block of a hand.
`If a bit in this field is set to I, then the associated probability block1n the band'15 likely to
`support Non-Public service. If a bit1n this field15 set to 0, then the associated probability
`block18 not likely to support Non-Public service
`
`For example, if the lst, 2nd, 3rd and 5th probability blacks of a band are likely to support
`Non-Public service, the values of Non-Public Map Length and Non-Public Block Map
`shall be:
`
`Non-Public Map Length = 0100
`
`Non-Public Block Map =
`
`l 0111.
`
`If the 3rd and 16th probability blocks of a band are likely to support Non-Public service,
`the values of Non-Public Map Length and Non-Public Block Map shall be:
`
`Non—Public Map Length = 1111
`
`Non-Public Block Map =
`
`1000 0000 0000 0100.
`
`219
`
`Dell Inc., Ex. 1018
`
`Page 103 of 170
`
`Dell Inc., Ex. 1018
`Page 103 of 170
`
`

`

`18-136.]
`
`Non-Public Registration Control
`
`This information element informs the mobile station whether or not a Registration
`attempt is allowed independent of having a PSID or RSID match (see Section 6.3.14),
`and whether or not the Test Registration is allowed.
`
`
`_—
`
`Pamererrype
`
`Non-Public Registration Control
`
`
`
`
`
`
`The Non-Public Registration Control field is coded as follows:
`
`
`
`
`—_
`
`PSlD/RSID match independent registration allowed
`
`
`
`
`
`PSID/RSID match independent registration and Test
`Registration not allowed (Default case if information
`
`
`element not sent)
`
`
`Test Registration allowed
`
`Number of E-BCCH
`
`This information element identifies the number of contiguous dedicated E—BCCH slots
`per superframe. Set to 1 plus the value in this field.
`
`l
`
`6
`
`
`
`1 E-BCCH slot per superframe
`
`001
`
`2 E—BCCH slots per superframe
`
`3 E—BCCH slots per superframe
`
`01 1
`
`4 E-BCCH slots per superframe
`
`Value
`
`
`100
`101
`
`110
`
`111
`
`5 E—BCCH slots per superfrarne'_
`6 E—BCCH slots per superframe
`
`7 E-BCCH slots per superframe
`
`8 E-BCCH slots per superframe
`
`
`
`
`
`
`
`
`
`
`
`970
`
`Dell Inc., Ex. 1018
`
`Page 104 of 170
`
`Dell Inc., Ex. 1018
`Page 104 of 170
`
`

`

`IS-l36.l
`
`Number of F-BCCH
`
`
`This information element identifies the number of contiguous dedicated F-BCCH slots
`per superframe. Set to 3 plus the value in this field.
`
`
`
`
`
`
`
`3 F-BCCH slots per superframe
`
`4 F-BCCH slots per superframe
`
`5 F—BCCH slots per superframe
`
`6 F-BCCH slots per superframe
`
`7 F-BCCH slots per superframe
`
`8 F-BCCH slots per superfiame
`
`9 F-BCCH slots per superframe
`
`10 F—BCCH slots per superfiame
`
`
`
`Number of Non-PCH Subchannel Slots
`
`
`This information element identifies the number of SPACH slots that may not be allocated
`to mobile stations as PCI-I Subchannels.
`
`For a half—rate DCCH, the following values apply:
`
`
`
`Number of Reserved Slots
`
`
`ll)
`11
`
`This information element identifies the number of dedicated Reserved slots per
`superframe.
`
`221
`
`Dell Inc., Ex. 1018
`
`Page 105 of 170
`
`Dell Inc., Ex. 1018
`Page 105 of 170
`
`

`

`l
`
`waeqatu.
`
`10
`
`ll
`
`l2
`
`13
`14
`15
`
`15—136.]
`
`Number of S-BCCH
`
`This information element identifies the number of contiguous dedicated S-BCCH slots
`per superframe.
`
`OLC
`
`This non~critical information element determines whether or not a mobile station can
`make an Origination, Registration or Originated Point—to-Point Teleservice. The mobile
`station must examine the value of the OLC bitmap corresponding to its internally stored
`access overload class assignment. If its bit in the OLC bit map is enabled, the mobile
`station shall continue with its access attempt. Otherwise, it shall not make an access
`attempt.
`
`The values of the Overload Class bit assignments are:
`
`WIXXXX
`
`WIXXXXX
`
`WHIXXXXXH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`XXXIWXXW
`
`XXlxxxxxxxxxxxxx
`
`
`
`
`
`Any combination of bits are allowed to activate many OLCs at once.
`
`For more information, refer to EIA Telecommunications Systems Bulletin No. 16 (March
`1985), "Assignment of Access Overload Classes in the Cellular Telecommunications
`Services“.
`
`777
`
`Dell Inc., Ex. 1018
`
`Page 106 of 170
`
`Dell Inc., Ex. 1018
`Page 106 of 170
`
`

`

`18-136.]
`
`PCH_DISPLACEMENT
`
`This information element identifies the number of additional SPACH slots the mobile
`station shall read when PCON is set.
`
`
`“ 0 additional SPACH slots read
`“ 1 additional SPACH slot read
`2 additional SPACH slots read
`
`7 additional SPACH slots read
`
`
`111
`
`
`
`PDREG
`
`This flag indicates whether Power Down registration is turned on or off.
`
`PFC Assignment
`
`This information element identifies the Paging Frame Class that a mobile station may be
`assigned at registration.
`
`
`
`
`
`
`_-
`
`Parameter—ripe
`M—
`
`
`
`
`
`
`The PFC Minus One field is coded as follows:
`
`ode
`
`010
`
`101
`
`
`
`
`
`ll
`
`
`Paging Frame Class 3
`
`Paging Frame Class 5
`
`PagingFrameClam
`Paging Frame Class 8
`
`
`
`223
`
`Dell Inc., Ex. 1018
`
`Page 107 of 170
`
`Dell Inc., Ex. 1018
`Page 107 of 170
`
`

`

`IS-l36.l
`
`PFC Minus One
`
`This information element is used to indicate the current PFC of a mobile station.
`
`
`
`
`
`-n_pagmg Frame Classl
`- pagmg Frame Classz
`
`“—
`
`
`
`
`
`
`
`
`_—_
`
`Paging Frame Class 7
`
`111
`
`Paging Frame Class 8
`
`PFC Request
`
`This information element identifies the Paging Frame Class requested by a mobile
`station.
`
`— -
`
`——
`
`6
`
`PFM__DIRECTION
`
`This information element defines whether the layer 2 PPM flag is a pull-in (reduce the
`Paging Frame Class by one) or a push-out flag (increment the Paging Frame Class by
`one).
`
`Code
`
`
`“ Pull!in (Decrease Paging Frame Class one unit)
`
`Push-out (Increase Paging Frame Class one unit)
`
`
`
`
`
`
`
`
`70A
`
`Dell Inc., Ex. 1018
`
`Page 108 of 170
`
`Dell Inc., Ex. 1018
`Page 108 of 170
`
`

`

`18-136.]
`
`Present RNUM
`
`
`,_,_
`
`This information element contains the registration number that is used to define a
`particular mobile station's Virtual Mobile Location Area (VMLA).
`
`
`
`
`
`
`
`-—
`TeemeeeType
`
`—-_
`
`Length
`
`
`
`
`Primary Superframe Indicator
`
`This non-critical information element indicates whether or not the current superframe is
`the primary superframe within a hyperframe.
`
`
`
`Protocol Discriminator
`
`This information element is used to identify the layer 3 protocol used for the message
`being sent.
`
`
`
`—_
`
`00
`IS-l36
`All other values are reserved
`
`
`10
`
`ll
`
`Protocol Version
`
`
`This information element identifies the Protocol Version supported:
`
`IA—553 or IS-S4-A
`
`
`_ B
`
`
`
`
`225
`
`Dell Inc., Ex. 1018
`
`Page 109 of 170
`
`Dell Inc., Ex. 1018
`Page 109 of 170
`
`

`

`13—136.]
`
`
`
` i PSIDIRSID Available
`
`This information element indicates the PSID/RSIDs for which a mobile station will
`receive service in the current SID area.
`
`
`
`__
`
`inmeieiiiie
`-—
`
`
`Number of PSID/RSID (Note 1)
`
`
`
`psm/RSID
`
`Note 1: The number of PSID/RSID in this set is 1 plus the value of this field.
`
`The PSID/R811) field is structured as follows:
`
`
`
`The PSID/RSID Type Indicator subfield is coded as follows:
`
`-_
`—_ ismininninn
`
`—_ isminiinion
`
`
`
`
`
`
`When the PSID/RSID Value subfield contains PSID information, values are assigned as
`follows:
`
`2
`3
`
`4
`
`5
`
`s
`
`7
`3
`
`9
`
`
`
`3000~CFFF
`
`
`
`DOOO-DFFF
`
`EOOO—EFFF
`
`FOOD-FFFF
`
`
`,
`
`SOC SpeCIfic PSIDs
`
`Nationwide PSIDs
`International PSIDs
`
`
`Value (hex) _
`
`
`0001-2FFF
`
`SID Specrfic PSIDs
`
`
`
`
`
`See Section 8.3.4 for additional information regarding PSID.
`
`99‘
`
`Dell Inc., Ex. 1018
`
`Page 110 of 170
`
`Dell Inc., Ex. 1018
`Page 110 of 170
`
`

`

`13-136.]
`
`When the PSID/RSID Valuesubfield contains RSID information, values are assigned as
`follows:
`
`
`
`
`We»
`
`
`
`
`SOC Specific RSID
`
`See Section 8.3.5 for additional information regarding RSID.
`
`PSlD/RSID Indicator
`
`This field indicates whether or not the PSID/RSID related mapping fields are present for
`the associated DCCH neighbor. Specifically, if the PSID/RSID Indicator value is set to 1,
`the PSID/RSID Support Length and PSID/RSID Support fields are present. If set to 0, the
`PSID/RSID Support Length and PSID/RSID Support fields are not present.
`
`PSlD/RSID Map
`
`This information element is included in the Test Registration message to indicate which
`private/residential systems have been queried by the mobile station. This information
`element
`is included in the Test Registration Response message to indicate the
`private/residential systems on which the mobile station may receive service. The ordering
`of the PSID/RSID Map reflects the ordering of the PSID/RSID Set sent on the System
`Identity message.
`
`
`
`
`
`
`
`
`
`XXXX XXXX XXXX XXXl
`
`lst PSID/RSID Selected/Accepted
`
`XXXX XXXX XXXX XXXO
`
`lst PSID/RSID Not Selected/Not Accepted
`
`1XXX XXXX XXXX XXXX
`
`16th PSID/RSID Selected/Accepted
`
`OXXX XXXX XXXX XXXX
`
`16th PSID/RSID Not Selected/Not Accepted
`
`
`
`
`
`
`
`PSIDIRSID Set
`
`A DCCH serving one or more private/residential systems shall use this information
`element to identify the PSID/RSID of each private/residential system that it is serving.
`
`
`_—
`
`
`
`
`
`
`
`
`
`
`
`
`-
`
`Note 1: N + 1 instances of this field are present up to a maximum of 16.
`
`ouQChUt
`
`9
`
`10
`ll
`12
`13
`14
`15
`
`I6
`
`17
`18
`
`19
`
`Page 111 of 170
`
`227
`
`Dell Inc., Ex. 1018
`
`Dell Inc., Ex. 1018
`Page 111 of 170
`
`

`

`18-136.]
`
`The PSIDIRSID field is structured as follows:
`
`
`
`The PSID/RSID Type Indicator subfleld is coded as follows:
`
`RSID Indication
`
`PSID Indication
`
`1
`
`When the PSIDIRSID Value subfield contains PSID information, values are assigned as
`follows:
`
`com-2m
`
`soon-cm
`
`moo-um
`
`moo-Em
`
`Value (hex) _
`
`
`
`_
`
`
`
`
`
`
`
`
`Fooo-
`
`See Section 8.3.4 for additional information regarding PSID.
`
`When the PSID/RSID Value subfield contains RSID information, values are assigned as
`follows:
`
`
`
`Value (hex) _
`
`
`
`
`
`socspemsm
`
`See Section 8.3.5 for additional information regarding RSID.
`
`0751
`
`Dell Inc., Ex. 1018
`
`Page 112 of 170
`
`Dell Inc., Ex. 1018
`Page 112 of 170
`
`

`

`PSIDIRSID Support
`
`15-136.]
`
`This field is only present when the PSTD/RSID Indicator field is set to 1. When present,
`the length of this is determined by adding 1 to the value of the PSID/RSID Support
`Length field.
`
`The PSID/RSID Support field indicates which PSID/RSID values identified in the
`PSID/RSID Set information element of the System Identity message of the current DCCH
`are supported by the DCCH neighbor under consideration. The ordering of the bits in this
`field reflects the ordering of the PSID/RSID Set sent in the System Identity message in
`that the least significant bit
`is associated with the first PSID/RSID listed in the
`PSID/RSID Set. If a bit in this field is set to 1, then the associated PSID/RSID entry in
`the PSID/RSID Set is supported by the neighbor cell under consideration. If a bit in this
`field is set to 0, then the associated PSID/RSID entry in the PSID/RSID Set is not
`supported by the DCCH neighbor under consideration.
`
`For example, if 16 PSID/RSIDs are listed in the System Identity message and the
`neighbor cell supports the 1st, 2nd, 3rd and 5th PSID/RSIDs in the PSID/RSID Set, the
`values of PSID/RSID Support Length and PSID/RSID Support shall be:
`
`PSID/RSID Support Length = 0100
`
`PSID/RSID Support = 10111.
`
`If 16 PSID/RSIDs are listed in the System Identity message and the neighbor cell
`supports 3rd and 16th PSID/RSIDs in the PSID/RSID Set, the values of PSID/RSID
`Support Length and PSID/RSID Support shall be:
`
`PSID/RSID Support Length = 1111
`
`PSID/RSID Support = 1000000000000100.
`
`
`PSIDIRSID Support Length
`
`This field is only present when the PSID/RSID Indicator field is set to 1. When present,
`this field is always 4 bits long and is used to determine the length of the PSID/RSID
`Support field.
`
`PUREG
`
`
`This flag indicates whether or not power up registration is enabled.
`
`NOWxIDKLh
`
`10
`11
`I2
`13
`
`14
`15
`16
`
`17
`
`18
`
`19
`20
`21
`
`22
`
`23
`
`24
`
`25
`26
`27
`
`28
`
`29
`
`229
`
`Dell Inc., Ex. 1018
`
`Page 113 of 170
`
`Dell Inc., Ex. 1018
`Page 113 of 170
`
`

`

`IS-136.1
`
`l
`
`R-Cause
`
`This information element is used to qualify a R-DATA REJECT message.
`
`
`__
`
`——
`
`
`
`Code
`
`Direction
`
`Decimal
`
`Binary
`
`
`
`
`
`
`
`
`
`1 1 1
`
`1 10 1 1 11
`
`111 1111
`
`921‘}
`
`Dell Inc., Ex. 1018
`
`Page 114 of 170
`
`
`
`
`
`
`
`Unassngned (unallocated) number
`
`B -> MS
`
`Call barred
`
`Short message transfer ICJCCted
`
`B -) MS
`
`B —) MS
`
`MS —> B
`Memory capacity exceeded
`3—113
`—B.,MS
`B-Ms
`—B—>m
`—B——>MS
`_B—»Ms
`_ms
`Resources unavailable, unspecified
`B -—-) MS
`
`Requested facrhty not implemented
`
`Invalid short message transfer reference
`value
`
`Invalid message, unspecified
`
`B ——) MS
`
`B -—> MS
`
`B —> MS
`
`
`
`
`
`
`
`
`
` B-)MS
`
`
`Mandatory information element error
`
`both
`
`Message type non-existent or not
`implemented
`
`B —-) MS
`
`Message not compatible with short message
`transfer state or message type non—existent
`or not implemented
`Information element non—existent or not
`
`both
`
`implemented
`Invalid information element contents
`
`both
`
`
`
`Message not compatible With the short
`message transfer state
`
`Protocol error, unspecified
`
`both
`
`both
`
`1010
`
`ggssssseggg31’;E?
`
`10101
`
`10110
`
`1 1011
`
`1 1100
`
`1 1101
`
`1 1.110
`
`010 1010
`
`0101111
`
`1000101
`
`t... O ...r g
`
`1011111
`
`21
`
`22
`
`27
`
`28
`
`29
`
`30
`
`38
`
`41
`
`42
`
`47
`
`81
`
`95
`
`97
`
`110
`
`1100001
`
`1100010
`
`1100011
`
`p—d
`
`00
`
`110 0100
`
`101
`
`110 0101
`
`IHIIHIIIIIIIliI
`
`
`Interworking, unspecified
`B —> MS
`127
`
`All other values are reserved.
`
`Dell Inc., Ex. 1018
`Page 114 of 170
`
`

`

`18-136. 1
`
`R-Data Unit
`
`This information element contains the Higher Layer Protocol Data Unit and is mandatory
`in an R-DATA message.
`
`
` Field Length
`
`l
`
`
`Length Indicator in (N) (in octets)
`
`
`
`8*(N-1)
`
`Higher Protocol Identifier
`
`Higher Layer Protocol Data Unit
`
`The Higher Layer Protocol Identifier field is coded as follows:
`
`
`
`
`
`
`—_
`
`
`
`_—
`
`
`R-Transaction Identifier
`
`This information element is used to associate a R-DATA ACCEPT or a R-DATA
`REIECT message to the R-DATA message being acknowledged.
`
`RAND
`
`This information element identifies the random number stored by a mobile station for use
`in selected authentication processes.
`
`RANDBSW
`
`This information element identifies the random number generated by the mobile station
`that is used in the SSD Update procedure.
`
`RANDC
`
`This information element identifies the number used to confirm the last RAND received
`by the mobile station. It is used in selected authentication processes.
`
`RANDSSDW
`
`This information element identifies the random number generated by the Bivfl that is used
`in the SSD Update procedure.
`
`10
`
`11
`
`12
`13
`
`14
`
`15
`16
`
`17
`
`18
`19
`
`231
`
`Dell Inc., Ex. 1018
`
`Page 115 of 170
`
`Dell Inc., Ex. 1018
`Page 115 of 170
`
`

`

`15-1361
`
`
`RANDU
`
`This information element identifies the random number generated by the BMI that is used
`in the Unique Challenge Response procedure.
`
`RCF and AUTH
`
`This information element of type flag indicates whether or not the mobile station is to
`read Control Filler information and send Authentication infomation when making an
`access on an ACC as a result of a Directed Retry received on the DCCH.
`
`_—
`
`m
`
`
`
`
`
`
`
`
`
`
`
`The RCF field is encoded as follows:
`
`
`
`
`0
`
`Do Not Read RCF
`
`The AUTH field is encoded as follows:
`
`
`-_
`
`n Authentication Disabled
`— Authentication Enabled
`
`
`
`
`
`
`
`
`
`
`
`10
`
`ll
`12
`
`
`RCI
`
`This information element identifies a particular radio frequency system allocation,
`together with recommended DCCH allocation, as defined in this standard.
`
`Function
`
`Allocation described in Section 6.3.1.1.4
`
`Allocation described in Section 6.3.1.1.1
`
`Allocation described in Section 6.3.1.1.2
`
`Allocation described in Section 6.3.1.1.3 _
`
`'Yl’!
`
`Dell Inc., Ex. 1018
`
`Page 116 of 170
`
`Dell Inc., Ex. 1018
`Page 116 of 170
`
`

`

`IS- 1 36.1
`
`R-DATA Message Length
`
`This information element identifies the maximum length of an R-DATA message that a
`mobile station may send on the RACH.
`
`001
`
`31 octet R-DATA message on RACH allowed
`
` §I
`
`
`Value _
`
`
`N0 R-DATA message on RACH
`
`
`
`
`
`
`
`
`111
`
`Limited only by layer 2 format
`
`
`
`REG Period
`
`This information element identifies the registration periodicity in number of 94
`superframes. REGPER values are coded from 0 to 511 indicating 94 to 48128
`superframes (approximately 1 minute to 8.5 hours).
`
`
`
`
`
`
`
`
`
`00000 0001
`
`00000 0010
`
`11111 1110
`
`11111 1111
`
`
`
`94 Superfiames
`
`188 Superframes
`
`282 Superframes
`
`48034 Superfiames
`
`48128 Superframes
`
`
`
`
`
`
`
`
`
`
`
`REGH
`
`This flag indicat

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket